Tracks BIM coordination across disciplines — clashes detected, resolved, design freeze + handover. Critical for modern projects using BIM-based design + construction.
BIM Session: 14-May-2026. Clashes: 47 total (32 closed, 12 in progress, 3 critical open). Critical: HVAC duct vs structural beam at L3 (rerouting under design). LOD: 300 (federated). Coordination status: 75 % resolved; GFC freeze date: 30-May-2026.
Building Information Modelling (BIM) has become the standard for medium-large Indian commercial / institutional / infrastructure projects. Architectural + structural + MEP + plumbing + fire-safety + landscape teams each produce 3D models; these are federated into a coordinated model that catches conflicts before construction.
The BIM Coordination Log tracks every coordination decision through the design cycle: which clash was discussed, what resolution was agreed, which designer made the change, what date. Without this log, BIM coordination devolves into informal email chains; decisions get lost; the same conflicts re-emerge in later iterations.
For projects following ISO 19650 (the international BIM standard, adopted as IS 16711 in India), maintaining a coordination log is a process requirement. The log is also a defensive document — if a clash emerges during construction that the BIM model should have caught, the log shows whether it was discussed + resolved or genuinely missed.
Workflow (typically weekly during design): 1. Federated model assembly — combine discipline models in Navisworks / BIM 360 / Solibri 2. Clash detection run — automatic geometric collision check 3. Triage — classify clashes by severity (Critical / Major / Minor / False) 4. Coordination meeting — relevant designers + PMC + (for major projects) client BIM lead 5. Resolution discussion — agree on who modifies what + by when 6. Log entry — clash ID, location, assigned designer, agreed resolution, target date, status 7. Updated models issued after resolution; re-run cycle
Coordination Log captures: - Discipline + clash type - Element references (e.g., 'HVAC duct DUC-VAC-031 vs Structural Beam B-303') - Severity classification - Assigned designer + reviewer - Agreed resolution - Target date + actual closure date - Notes / decisions / trade-offs - Cross-reference to clash detection report
1. No formal log — coordination conducted via email + WhatsApp; decisions lost; no audit trail.
2. Designer non-participation — discipline designer doesn't attend coordination meetings; one-sided resolutions; conflicts persist.
3. No CDE (Common Data Environment) — designers working on different model versions; coordination is illusory. ISO 19650 requires a single CDE.
4. Major clashes deferred to construction — 'we'll resolve on site' decisions; cost 5-20× more to fix in steel + concrete than in pixels.
5. Stale model versions — coordination based on a model from weeks ago; current model has new conflicts not addressed.
6. LoD (Level of Detail) mismatches — architectural at LoD 350, MEP at LoD 200; can't meaningfully coordinate. Specify LoD per discipline per phase.
7. No model validation — discipline models accepted without checking against project standards (naming, classification, geometry rules). Garbage in → garbage out.
8. No model archive — at project close, federated model not archived; cannot retrieve as-built for FM (facilities management) handover.
Companion PMC formats: - Design Review Register (PMC-DES-REG-001) — overall design review cycle - Clash Detection Report (PMC-DES-RPT-001) — formal clash analysis output - Drawing Transmittal (PMC-DES-FRM-001) — formal model + drawing issue - GFC Submission Tracker (PMC-DES-LOG-002) — release tracking
Standards: - ISO 19650 Parts 1-5 — BIM information management (the international standard) - IS 16711:2017 — Building Information Modelling — Information Management Standard - PAS 1192-2:2013 — Specification for information management during the capital / delivery phase - BS EN 17412-1:2020 — Level of Information Need (LoIN) - NBIMS-US v3 — US National BIM Standard