Coordination software brings models from different teams and tools together so they can be reviewed, checked and coordinated. Most products combine three functions: federation (viewing many models together), checking (clashes and rules) and issue management (tracking problems to resolution, often with BCF). This entry describes the categories neutrally.
At a glance
| Function | Examples of tools |
|---|---|
| Federation and clash detection | Autodesk Navisworks, Autodesk Construction Cloud model coordination, Revizto, BIMcollab Zoom, Dalux |
| Rule-based model checking | Solibri, BIMcollab Zoom smart views, open-source IDS checkers |
| Issue management | BIMcollab Nexus, Revizto, ACC Issues, Trimble Connect, Dalux |
| Viewing and review | Free IFC viewers, Trimble Connect, CDE viewers, web viewers |
What coordination tools typically do
- Load many formats: IFC and native files, point clouds, 2D drawings.
- Align models using their coordinates; flag models that do not line up.
- Search and select sets of elements by discipline, type, property or location.
- Run clash tests with types, tolerances and rules.
- Group results and turn them into issues with viewpoints.
- Run rule checks: properties present, naming, spaces, duplicates.
- Track issues with status, owner, priority and due date, often synchronised with authoring tools through BCF.
- Compare revisions to show what changed.
Desktop and cloud
| Desktop tools | Cloud platforms | |
|---|---|---|
| Strength | Powerful checks on large models, full control of tests | Everyone sees the same models and issues; works in a browser |
| Weakness | Results shared by export; one person runs the tests | Fewer settings; depends on connection and subscriptions |
Many projects use both: a desktop tool for running tests, and a cloud platform for sharing issues.
Choosing and agreeing
- The BEP names the coordination tool, the issue platform and how issues reach the authors.
- If different companies use different tools, BCF is the bridge.
- Search sets and clash tests should be saved and reused each cycle so results are comparable.
Common mistakes
- Re-building tests every cycle by hand, so results cannot be compared.
- Exporting clash reports as PDFs no one acts on, instead of issues with owners.
- Running coordination on outdated models because loading from the CDE is not automated.
Where to read more
Vendor documentation describes each tool's features. The project's coordination procedure, in the BEP, sets how the tools are used.