CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/Construction

πŸ—οΈ Construction Β· Data Flow

BIM Data Flow

How building information modelling (BIM) data flows between designers, contractors and the owner: coordination, clash detection, quantities and handover.

More Construction templates

Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.

Drawing diagram…

What this diagram shows

  • Architecture, structure and MEP models are federated in a common data environment
  • Clash detection finds conflicts before construction
  • As-built data is handed over for facility management

Prompt used

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.

Mermaid code
flowchart LR
subgraph EXT ["External entities"]
arc["Architects"]
stru["Structural Engineers"]
mep["MEP Consultants"]
site["Site Team"]
qs["Cost Planner"]
fm["Facility Management"]
end
subgraph PROC ["Processes"]
p1("1.0 Publish and federate models")
p2("2.0 Detect clashes")
p3("3.0 Take off quantities and estimate cost")
p4("4.0 Link the 4D schedule")
p5("5.0 Update the as-built model")
p6("6.0 Hand over asset data")
end
subgraph STORE ["Data stores"]
d1[("D1 Common Data Environment")]
d2[("D2 Issue Register")]
d3[("D3 Construction Schedule")]
end
arc -->|"Architecture model (IFC)"| p1
stru -->|"Structural model (IFC)"| p1
mep -->|"MEP model (IFC)"| p1
p1 -->|"Federated model"| d1
d1 -->|"Federated model"| p2
p2 -->|"Clash issues"| d2
p2 -->|"Issues to resolve"| arc
p2 -->|"Issues to resolve"| stru
p2 -->|"Issues to resolve"| mep
d1 -->|"Model quantities"| p3
p3 -->|"Cost estimate"| qs
d1 -->|"Model elements"| p4
d3 -->|"Schedule activities"| p4
p4 -->|"4D build sequence"| site
site -->|"Site progress"| p5
p5 -->|"As-built updates"| d1
d1 -->|"As-built model"| p6
p6 -->|"COBie asset data"| fm

Inside this diagram

A data flow diagram with 12 processes and outside parties, 3 data stores and 18 data flows.

Processes and outside parties

  • Architects
  • Structural Engineers
  • MEP Consultants
  • Site Team
  • Cost Planner
  • Facility Management
  • 1.0 Publish and federate models
  • 2.0 Detect clashes
  • 3.0 Take off quantities and estimate cost
  • 4.0 Link the 4D schedule
  • 5.0 Update the as-built model
  • 6.0 Hand over asset data

Data stores

  • D1 Common Data Environment
  • D2 Issue Register
  • D3 Construction Schedule

Data flows

  • Architects β†’ 1.0 Publish and federate models: Architecture model (IFC)
  • Structural Engineers β†’ 1.0 Publish and federate models: Structural model (IFC)
  • MEP Consultants β†’ 1.0 Publish and federate models: MEP model (IFC)
  • 1.0 Publish and federate models β†’ D1 Common Data Environment: Federated model
  • D1 Common Data Environment β†’ 2.0 Detect clashes: Federated model
  • 2.0 Detect clashes β†’ D2 Issue Register: Clash issues
  • 2.0 Detect clashes β†’ Architects: Issues to resolve
  • 2.0 Detect clashes β†’ Structural Engineers: Issues to resolve
  • 2.0 Detect clashes β†’ MEP Consultants: Issues to resolve
  • D1 Common Data Environment β†’ 3.0 Take off quantities and estimate cost: Model quantities
  • 3.0 Take off quantities and estimate cost β†’ Cost Planner: Cost estimate
  • D1 Common Data Environment β†’ 4.0 Link the 4D schedule: Model elements
  • D3 Construction Schedule β†’ 4.0 Link the 4D schedule: Schedule activities
  • 4.0 Link the 4D schedule β†’ Site Team: 4D build sequence
  • Site Team β†’ 5.0 Update the as-built model: Site progress
  • 5.0 Update the as-built model β†’ D1 Common Data Environment: As-built updates
  • D1 Common Data Environment β†’ 6.0 Hand over asset data: As-built model
  • 6.0 Hand over asset data β†’ Facility Management: COBie asset data

Boundaries

  • External entities: Architects, Structural Engineers, MEP Consultants, Site Team, Cost Planner and Facility Management
  • Processes: 1.0 Publish and federate models, 2.0 Detect clashes, 3.0 Take off quantities and estimate cost, 4.0 Link the 4D schedule, 5.0 Update the as-built model and 6.0 Hand over asset data
  • Data stores: D1 Common Data Environment, D2 Issue Register and D3 Construction Schedule

Make your own diagram like this

Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.

Related templates

GanttConstruction

House Construction Project Schedule

A typical schedule for building an independent house, from approvals and foundation to finishing and handover.

FlowchartConstruction

Building Permit and Stage Inspections

How a building project moves through the local authority: plan approval, stage inspections during construction, and the occupancy certificate.

SequenceConstruction

Construction Material Procurement

How a construction site orders materials: site request, quotes from suppliers, purchase order, delivery, quality check and payment.

C4 ArchitectureProConstruction

Construction Project Management Platform

A platform for running building projects: schedules, site diaries, drawings, RFIs, quality and safety checklists, and billing.

FlowchartConstruction

Construction Site Safety Inspection

A daily safety inspection routine on a construction site: checklists, hazard reporting, stop-work authority and follow-up.

Database ERDConstruction

Construction Project Database Schema

Tables for a construction project system: projects, sites, work packages, subcontractors, materials, daily logs and payments.