
🏗️ Construction · Data Flow
How building information modelling (BIM) data flows between designers, contractors and the owner: coordination, clash detection, quantities and handover.
Drawing diagram…
Data flow for BIM: architects, structural engineers and MEP consultants publish models (IFC) to a common data environment, a federated model is built for coordination, clash detection finds conflicts (duct through beam) that go back to designers as issues. Quantity take-off feeds cost estimates, 4D scheduling links model elements to the construction schedule, site progress updates the model, and the final as-built model with asset data (COBie) is handed over to facility management.
flowchart LR ARC[Architecture model] -->|IFC| CDE[(Common Data Environment)] STR[Structure model] -->|IFC| CDE MEP[MEP model] -->|IFC| CDE CDE --> FED[Federated Model] FED --> CLASH[Clash Detection] CLASH -->|Issues| ARC CLASH -->|Issues| MEP FED --> QTO[Quantity Take-off] QTO --> COST[Cost Estimate] FED --> SCH4D[4D Schedule Link] SITE[Site Progress] --> SCH4D FED -->|As-built with asset data - COBie| FM[Facility Management]
A typical schedule for building an independent house, from approvals and foundation to finishing and handover.
How a building project moves through the local authority: plan approval, stage inspections during construction, and the occupancy certificate.
How a construction site orders materials: site request, quotes from suppliers, purchase order, delivery, quality check and payment.
A platform for running building projects: schedules, site diaries, drawings, RFIs, quality and safety checklists, and billing.
A daily safety inspection routine on a construction site: checklists, hazard reporting, stop-work authority and follow-up.
Tables for a construction project system: projects, sites, work packages, subcontractors, materials, daily logs and payments.