QVINTOS Coordinate

Find clashes and rule deviations before you issue.

Review one model in depth, or bring the discipline models together and coordinate between them. Each finding shows its method and source, and issues move to and from your coordination tool as BCF.

Available: Model review
Pilot: Multi-model coordination & clashes, Issues / BCF

Book a demo See the workflow

QVINTOS Coordinate, model review: the architect’s model in an X-ray 3D view, with the view presets Top, Front, Side, Iso, Section and Free flight, and the storey rail. — Model review (available) on our demo model, in the X-ray view.

The problem

Clashes and rule deviations are often found late.

Separate models, late meetings
Each discipline models in its own file, and conflicts often surface first at a coordination meeting.
Findings without a method
A finding that does not say how it was measured is hard to verify, and hard to dismiss.
Issues lost between versions
An issue raised on one model version is easy to lose by the next one.

QVINTOS Coordinate reviews the model before it is issued, shows the method behind every finding, and follows issues across versions.

Capabilities

Review one model. Coordinate many.

Model review works on a single model. Clashes between models are handled in coordination, with the architect’s model as the reference.

QVINTOS Coordinate, a detected clash in the X-ray 3D view: a sprinkler pipe from the sprinkler model crossing an emergency luminaire from the electrical model, both highlighted, with the clash marker where they meet. — A detected clash (multi-model coordination, pilot): sprinkler pipe × emergency luminaire, across the sprinkler and electrical models of our demo building.

C-01
Model review
Available

Clashes, room heights, penetrations, shafts and rule checks, each finding with method and source.
- Clashes, room heights, penetrations, shaft space and rule checks
- Each finding with its method, its source and the rule id it follows
- Mark each finding as reviewed, resolved or a deviation
- An AI summary of the findings, which may not contain figures that are not in the findings
What it covers
- Clashes, room heights, penetrations, shaft space and rule checks
- Each finding with its method, its source and the rule id it follows
- Mark each finding as reviewed, resolved or a deviation
- An AI summary of the findings, which may not contain figures that are not in the findings
DeliversFindings · BCF
C-02
Multi-model coordination & clashes
Pilot

Clashes between discipline models, grouped per building element.
- The discipline models read together as one federated model, on the architect’s model
- A check on whether the models line up before clash detection
- Clashes between models, grouped per building element
- Every clash list states what the check does not cover
What it covers
- The discipline models read together as one federated model, on the architect’s model
- A check on whether the models line up before clash detection
- Clashes between models, grouped per building element
- Every clash list states what the check does not cover
DeliversClash groups · BCF
C-03
Issues / BCF
Pilot

Issues tracked across model versions and exchanged with your coordination tool.
- Issues created from clash groups and findings
- Followed across model versions
- Exchanged with your coordination tool as BCF, in both directions
What it covers
- Issues created from clash groups and findings
- Followed across model versions
- Exchanged with your coordination tool as BCF, in both directions
DeliversBCF

The workflow

Five steps, from models to meeting.

The steps follow the coordinator’s work, in the same layout as the rest of QVINTOS: the steps on top, one panel per step, the model in the middle.

1Models

Bring in the discipline models and check that they line up with the architect’s model.
2Clashes

Clashes between the models, grouped per building element, filtered by type, owner and storey.
3Issues

What needs fixing, followed across model versions. BCF in and out.
4Model review

One model in depth: the review checks, questions about the model, and its documents.
5Report

The basis for the coordination meeting, as a PDF.

Findings you can act on

Every finding shows its work.

A review is only useful if the findings can be checked. These are built into Coordinate.

01

Method and source

Each finding says how it was measured and which data it came from, so it can be verified or dismissed.
02

What was not checked

The clash list states its limits, for example clearances and service space, instead of implying full coverage.
03

A decision per finding

Reviewed, resolved or a deviation. The decision is saved with the finding.
04

An AI summary that adds nothing

The summary explains and sorts the findings. It may not contain figures or references that are not in the findings.

Integrations and outputs

What goes in, what comes out.

In

IFCThe models, one per discipline. Revit models through IFC export.
BCFIssues from your coordination tool

Out

BCFIssues and review findings for your coordination tool
PDFThe coordination report for the meeting

Licensing

Licensed as enterprise software.

Start with the modules you need, on one of your own projects, and add more as the results hold up. The scope and the terms are set in the agreement with you.

StartOne module on a live project, judged on your own work.
ExpandMore teams, more disciplines or another product line on the same platform.
DeployDeployment options, including a separate installation, are discussed per customer.

Talk to sales How enterprise licensing works