Model coordination in BIM (Building Information Modelling) is the process of integrating and aligning models created by different disciplines involved in a construction project. This coordination identifies and resolves clashes or conflicts between different building systems early in the design phase — streamlining construction and minimising costly rework.
When done well, model coordination ensures that architects, structural engineers, MEP designers, and contractors all work from a single, consistent digital environment where conflicts are resolved before they reach the site.
In this guide, we cover what model coordination is, the five key components to look for in a coordination tool, how clash detection and model merging work, and how to get started in Autodesk Construction Cloud (ACC).
Model Coordination vs BIM Project Coordination: What is the Difference?
These two terms are often used interchangeably, but they describe different scopes of work.
| Aspect | Model Coordination | BIM Project Coordination |
|---|---|---|
| Focus | The technical process of federating, checking, and resolving clashes within 3D models | The broader management of disciplines, stakeholders, and workflows across a project |
| Who leads it | BIM Coordinator or VDC Engineer | BIM Manager or Project Manager |
| Primary tools | Navisworks, ACC Model Coordination, Solibri | ACC, Procore, BEPs, coordination meeting agendas |
| Output | Clash-free federated model, issue reports | Coordinated project delivery across all phases |
Model coordination is a core technical component within the broader BIM project coordination framework. Getting the model coordination process right is what enables effective project-level coordination to happen.
What is Model Coordination in Autodesk Construction Cloud?
Autodesk Construction Cloud (ACC) is Autodesk’s current cloud-based platform for construction project management, replacing the legacy BIM 360 platform. It includes a dedicated Model Coordination module that allows project teams to coordinate and collaborate on 3D models within a centralised, browser-accessible environment.
Model Coordination in ACC allows project teams to:
- Aggregate models: Combine 3D models from multiple disciplines into a unified federated view
- Automate clash detection: Automatically identify interferences between elements in different models (for example, a duct running through a structural beam)
- Manage issues: Create, assign, and track issues directly from detected clashes with a full audit trail
- Visualise progress: Review the coordinated model in a browser, accessible to the entire project team without specialised BIM software
The goal is to catch coordination problems in the design phase before they become expensive problems during construction. The Model Coordination module is included in the BIM Collaborate and BIM Collaborate Pro offerings within ACC.
5 Key Components of Model Coordination Tools
Not all coordination tools are equal. When evaluating a model coordination platform, look for these five components that determine whether a tool can support your team effectively across the project lifecycle.
1. Cloud-Based Detection
Desktop-only coordination tools isolate identified problems on the BIM coordinator’s computer — meaning only one person can see and act on the issues. Cloud-based coordination tools solve this by making clash data visible to the entire design team simultaneously.
Through an open API connected to both your Common Data Environment (CDE) and your BIM authoring tool, issues can be shared instantly across disciplines. This transforms clash resolution from a slow, sequential process into a collaborative, real-time workflow.
2. OpenBIM and BCF File Support
A coordination tool should allow teams to work across different software platforms without being locked into a single vendor ecosystem. This requires support for:
- IFC (Industry Foundation Classes): An open standard that allows models from any BIM authoring tool to be shared and federated without restrictions
- BCF (BIM Collaboration Format): A standardised file format for communicating issues and clash data between platforms, enabling teams using different tools to exchange structured issue information
Openness and interoperability are critical across the full asset lifecycle — from design coordination through to operational facility management.
3. Rule-Driven Validation
The best coordination tools allow you to define clash rules and checking criteria once, then apply them consistently across projects. Rules built on IFC maintain a consistent data framework, letting you automate geometry and data checks based on project standards — eliminating the need to reconfigure checks from scratch for each new project.
4. Usability
A technically capable tool that is difficult to use will not be adopted consistently. Key usability features include a clean interface with logical navigation, classification-based model object organisation for fast element filtering, and a reusable library of rule templates so checking protocols can be standardised across projects.
5. Continuous Improvement and a Healthy Product Roadmap
When you invest in a coordination tool, you are committing to it for the long term. Choose a platform with active, consistent product development that responds to user feedback and evolves as industry standards change. Consider your organisation’s own roadmap: will this tool still serve your coordination needs in two to three years?
After you learn all the main components that you need to look at in model coordination, it’s time to look at those components inside the best computer-aided design software available on the market. Check out our article, “What Is the Best 3D CAD Software? 5 Top Options to Consider” to start your journey.
Clash Detection and Resolution
Clash detection is the core function of model coordination. It identifies conflicts between elements from different discipline models so they can be resolved before construction begins.
Types of Clashes
| Type | Definition | Example |
|---|---|---|
| Hard clash | Two solid elements physically occupy the same space | A structural beam penetrating an HVAC duct |
| Soft clash | Clearance or maintenance access requirements are violated | Insufficient access space around a valve or panel |
| Workflow clash | Construction sequencing conflicts between trades | Two trades scheduled to work in the same zone simultaneously |
How Clash Detection Works in ACC
When project administrators set up a coordination space in ACC, the platform automatically detects clashes as models are uploaded. Supported file formats include RVT, DWG, NWC, and IFC.
Once clashes are identified, team members review each one and take one of the following actions:
- Mark as Not an issue — if the clash is acceptable or intentional (for example, a sleeve through a wall)
- Assign as an issue — with a responsible party, due date, and priority level
- Resolve in the authoring tool — update the model and re-publish to confirm the clash is cleared
Coordination administrators can configure whether clash detection runs automatically when new models are published or on a manual trigger.
Model Merging and Integration
Model merging combines discipline-specific models into a single coordinated federated model. In ACC, this happens through Coordination Spaces — dedicated environments where all discipline models are aggregated, aligned, and reviewed together.
The integration workflow typically involves three parallel activities:
- Clash detection: Automated identification of conflicts between elements from different disciplines
- Issue tracking: Logging detected clashes as issues with assigned ownership, status, and resolution documentation
- Collaborative resolution: Teams update their models to resolve issues and re-publish to the shared coordination space for re-checking
ACC’s Model Coordination module also supports constructability reviews with clash detection turned off — allowing teams to use the federated view for visual inspection and sequencing checks without triggering automated clash tests.
How to Set Up Model Coordination in ACC
The following steps reflect the current ACC interface. You will need Project Administrator permissions and an active BIM Collaborate or BIM Collaborate Pro subscription to access the Model Coordination module.
- Navigate to Project Admin: From your ACC project home, open Project Admin and locate the Services section.
- Activate Model Coordination: Find “Model Coordination” in the services list and click Activate.
- Create a Coordination Space: In the Model Coordination module, click “Create Coordination Space.” Give it a descriptive name (for example, “Level 1 MEP-Structural Review”).
- Link to an Autodesk Docs folder: Select the folder in your Docs module where discipline teams will publish their models. Best practice is to create a dedicated coordination folder separate from working files.
- Configure clash settings: Choose whether clash detection runs automatically when new model packages are published, or on a manual trigger.
- Upload models: Team members with folder access publish their latest Revit (RVT), Navisworks (NWC), AutoCAD (DWG), or IFC models to the linked folder.
- Review clashes: ACC automatically federates the models and generates a clash report. Review clashes by discipline, severity, or location in the coordination space viewer.
- Create and assign issues: Convert clashes into tracked issues with assigned owners and due dates. Use the Revit Issues Add-in to resolve issues without leaving your authoring tool.
Note: For teams using non-Revit software, export models to IFC before uploading to maintain full compatibility with ACC’s clash detection engine.
How to Create a Custom View in ACC Model Coordination
Custom views in ACC allow teams to save specific combinations of models and filters for targeted coordination reviews — for example, showing only MEP and structural models on a specific level.
- Navigate to the Model Coordination module and open your coordination space.
- In the Models panel, select the discipline models you want to include in your view.
- Click Open in Viewer to load the federated model.
- Use the Model Browser panel to navigate the model tree and isolate specific elements by discipline, level, or system.
- Apply property filters using the filter drop-down lists to focus on specific element types or parameters.
- Apply colour overrides to groups of objects for visual clarity during reviews.
- When your view is configured, click Save View.
- Enter a title, description, and privacy status (visible to all project members or restricted).
- The saved view is stored in the Views tool and can be recalled by any team member with access.
Saved views can also generate snapshots sent to Autodesk Docs for mobile viewing or field reference — keeping site teams aligned with the latest coordination status.
Model Coordination Best Practices
- Prepare Revit models correctly before publishing. Set up dedicated 3D coordination views in Revit, disable unnecessary links, and ensure shared coordinates are aligned across all models before the first upload to ACC.
- Run clash detection on a regular schedule. Weekly or biweekly checks during design and detailing phases catch issues while changes are still cheap. Ad hoc checks at milestones are consistently too late.
- Use descriptive coordination space names. “Level 3 MEP-Structural Review” is far more useful than “Coordination Space 1” when multiple spaces exist for different phases or zones.
- Assign every clash to a specific owner. Every issue in ACC should have a named responsible party, a due date, and a priority level before the coordination meeting ends. Unassigned clashes go unresolved.
- Configure rules to filter false positives. Not every geometric intersection is a real clash. Set clash rules to exclude intentional intersections — pipe sleeves through walls, anchor bolts — so your team focuses on genuine coordination issues.
- Train all discipline teams, not just the coordinator. Coordination fails when modellers do not understand how their models will be federated and checked. Training in Revit publishing settings, shared coordinates, and IFC export ensures models arrive in a state that supports effective coordination.
Conclusion
Model coordination is the technical foundation of effective BIM project delivery. When teams invest in the right tools — cloud-based, open-standard, and rule-driven — and apply consistent coordination workflows from the early design phase, the result is fewer site conflicts, lower rework costs, and a coordinated model that supports facility management long after project handover.
For AEC teams across Singapore, Malaysia, and the Philippines, building model coordination capability is increasingly a prerequisite for government-linked infrastructure projects and international commercial developments that require BIM-compliant deliverables.
Interscale Education offers BIM training programmes covering the full coordination workflow — from Revit model preparation and ACC setup to clash detection, issue management, and coordination meeting facilitation.
FAQ
What is Model Coordination in BIM?
Model coordination in BIM is the process of combining discipline-specific 3D models into a single federated environment to identify and resolve clashes before construction begins. It ensures architectural, structural, and MEP models are aligned and conflict-free, reducing costly site rework.
What is the Difference Between BIM 360 and Autodesk Construction Cloud?
BIM 360 was Autodesk’s previous cloud construction management platform. Autodesk Construction Cloud (ACC) is its successor, consolidating BIM 360’s functionality alongside newer tools under a unified platform. The Model Coordination module from BIM 360 now exists within ACC, with an updated interface and deeper integration across Docs, Design Collaboration, and Build.
What File Formats Does ACC Model Coordination Support?
ACC Model Coordination supports RVT (Revit), DWG (AutoCAD), NWC (Navisworks Cache), and IFC files for clash detection. IFC is recommended for teams using non-Autodesk authoring tools, as it maintains full model data and supports open BIM workflows across different software platforms.
What is a Coordination Space in ACC?
A Coordination Space is the dedicated environment within ACC’s Model Coordination module where discipline models are uploaded, federated, and checked for clashes. You can create multiple coordination spaces for different project phases, building levels, or specific clash test combinations — for example, a separate space for MEP-structural coordination and another for architectural-structural review.
Can ACC Model Coordination Replace Navisworks?
For many standard coordination workflows, ACC can handle what previously required Navisworks — without manual NWC exports and with browser-based access for all team members. However, Navisworks still offers more advanced clash rule configuration, 4D sequencing, and offline review capabilities useful for complex multi-discipline projects. The two tools are increasingly used in combination rather than as alternatives.
What is a BCF File and Why Does It Matter?
BCF (BIM Collaboration Format) is an open file format used to exchange coordination issues between different BIM platforms. When your team uses multiple tools, BCF allows issues identified in one platform to be imported and resolved in another — without relying on screenshots or manual transfer. It is the standard format for interoperable issue communication across the AEC industry.
How Does Model Coordination Training Help Teams?
Training in model coordination gives teams the technical skills and platform proficiency to set up coordination workflows correctly from the start. Without training, common problems include misaligned shared coordinates, incorrect Revit publishing settings, and unclear clash rules that generate thousands of false positives. Role-specific training for coordinators, modellers, and project managers ensures each person understands their responsibilities in the coordination workflow.
