Coordinating a manufacturing plant is not the same problem as coordinating a new building. The structure already exists, production is running, and the window to install anything is a fixed shutdown. BIM coordination in that setting is less about drawing a clean model and more about proving the install sequence will fit the time you actually have.
What coordination means here
BIM coordination is the multi-trade process of detecting and resolving geometric and clearance conflicts inside a federated 3D model — before construction, not during. On a plant retrofit, "before construction" means before the shutdown starts, because a clash found in the field during a turnaround is measured in lost production, not rework hours.
Start from what is actually there
Brownfield plants rarely match their drawings. Coordination on an existing facility starts with capture: process plant and equipment-area scanning, pipe and equipment 3D modeling, and isometric drawings generated from the scan data. Field work is planned around the plant's reality — confined space and elevated access, hot work and energized equipment protocols, hazardous area-aware protocols, and scheduling that fits around production shifts rather than fighting it. Coordination with operations, EHS, and turnaround planning is part of the scope, not an afterthought.
The weekly cycle
Coordination runs on a repeating cycle:
- Kick-off and BIM Execution Plan — establish the clash matrix, meeting cadence, model exchange protocol, and resolution workflow with the project team.
- Weekly clash detection — run automated clashes across all trade models, categorize by severity and ownership, and distribute reports ahead of the coordination meeting.
- Resolution meeting — walk the model with trade leads, assign owners, agree routing changes, and document the commitments.
- Model update and sign-off — trades update, BimCon verifies the resolutions, closes the issues, and publishes the coordinated federated model.
Not every clash matters
Volume is not the metric. Clashes get triaged by severity and ownership so the team spends the shutdown window on the conflicts that would actually stop an install, rather than working down an undifferentiated list.
Sequencing, not just clearance
On a plant, two questions sit on top of the usual clash question: can the crew physically get the equipment into place in the order the schedule assumes, and is there room left to maintain it afterward. Federated models are used to lock the install sequence before the shutdown starts, package the work in shutdown order, and validate equipment clearances.
What you get
- Clash matrix with trade-by-trade breakdowns
- Weekly coordination meetings facilitated
- An updated coordinated federated model after each cycle
- Issue log management in BIM 360 / Autodesk Construction Cloud
- Area-by-area sign-off documentation
- BIM Execution Plan authoring and maintenance
Tools and standards
Modeling in Autodesk Revit, CAD-MEP, and SysQue; coordination in Navisworks Manage and BIM 360 / Autodesk Construction Cloud. Information management is aligned to ISO 19650 and the US National BIM Standard (NBIMS-US v3), with per-project QA reports and a two-person model review — discipline lead plus independent QC. For industrial owners running engineering platforms, deliverables can be produced for AVEVA E3D and SmartPlant, and models can be equipment-tagged and linked to an asset registry.