Back to ER Diagram
BIM Coordination

BIM Coordination Logic

BIM model management, clash detection, coordination meetings, issue tracking, quantity extraction, and 4D/5D integration.

PostgreSQL
6 Tables
Schema: bim
3D Models

Overview

BIM (Building Information Modeling) module manages 3D model coordination for construction projects. Models from multiple disciplines (structural, MEP, architectural) are uploaded and versioned. Automated clash detection identifies conflicts between disciplines. Coordination meetings track resolution of clashes. BIM quantities extracted for BOQ validation. 4D scheduling links model elements to project activities.


Upload Model

Run Clashes

Coordinate

Resolve Issues

Extract Qty
6
BIM Tables
Multi
Discipline Models
Auto
Clash Detection
4D/5D
Schedule+Cost

Status States

StatusDescriptionAllowed ActionsNext States
CurrentLatest model version activeView, Run ClashesSuperseded
Under ReviewModel changes being reviewedApprove, RejectCurrent
Clash DetectedUnresolved clashes existCoordinate, ResolveResolved
ResolvedAll clashes resolvedArchive
SupersededOlder model versionView Only

Database Schema

bim.bim_model

  • model_id — PK
  • project_id — FK → project.project
  • discipline — structural | mep | architectural | civil
  • model_name, version — Identification
  • file_url, file_size — Storage reference
  • uploaded_by, upload_date — Tracking
  • status — Current / Under Review / Superseded

bim.clash_detection

  • clash_run_id — PK
  • project_id — FK → project.project
  • models_compared — Array of model_ids compared
  • run_date, total_clashes — Detection results
  • critical_count, major_count, minor_count — Severity breakdown

bim.clash_item

  • clash_id — PK
  • clash_run_id — FK → bim.clash_detection
  • discipline_a, discipline_b — Conflicting disciplines
  • element_a_id, element_b_id — Model element references
  • location, description — Clash details
  • status — Open / Assigned / Resolved
  • assigned_to — FK → admin.user

bim.bim_issue

  • issue_id — PK
  • project_id — FK → project.project
  • issue_type — clash | rfi | design_change | coordination
  • description, location — Issue details
  • priority — low | medium | high | critical
  • raised_by, assigned_to — Workflow tracking
  • status, resolution — Lifecycle and outcome

BIM Workflow

1

Model Upload

Discipline leads upload BIM models (IFC/RVT format) with version tracking. System validates file format and extracts metadata.

2

Clash Detection

Automated clash detection runs between selected discipline pairs. Results categorized as critical/major/minor based on intersection volume.

3

Coordination Meeting

Weekly BIM coordination meetings review open clashes. Clashes assigned to responsible discipline for resolution. Meeting minutes tracked.

4

Issue Resolution

Assigned team modifies design to resolve clash. Updated model uploaded. Re-run clash detection to verify resolution.

5

Quantity Extraction

BIM quantities extracted for material elements (concrete, steel, blockwork). Compared against BOQ for validation and variance analysis.

BIM Queries

Clash Summary

SELECT cd.run_date, cd.total_clashes,
       cd.critical_count, cd.major_count, cd.minor_count,
       COUNT(CASE WHEN ci.status = 'Resolved' THEN 1 END) AS resolved,
       COUNT(CASE WHEN ci.status = 'Open' THEN 1 END) AS still_open
FROM bim.clash_detection cd
LEFT JOIN bim.clash_item ci ON ci.clash_run_id = cd.clash_run_id
WHERE cd.project_id = :project_id
GROUP BY cd.clash_run_id
ORDER BY cd.run_date DESC;

Validation Rules

Business Rules

  • Model Version: Only one Current model per discipline per project
  • Clash Resolution: Critical clashes must be resolved before construction in affected zone
  • IFC Compliance: Uploaded models must be IFC 2x3 or 4.0 compliant
  • Qty Variance: BIM vs BOQ quantity variance above 5% flagged for investigation

Integration Points

Connected Modules

  • Project: BIM model elements linked to WBS activities for 4D
  • Estimation: BIM quantities compared with BOQ for validation
  • Document: BIM models stored in document management with revision control
  • Quality: BIM clash locations feed ITP inspection points

Best Practices

Recommended

  • Run clash detection after every model update
  • Resolve critical clashes within 48 hours
  • Use BIM quantities as cross-check for manual BOQ
  • Maintain model LOD (Level of Development) standards per project phase