BIM & takeoff
Get 6D carbon from a BIM model
Turn a converted BIM model into an embodied carbon footprint. Auto-enrich reads quantities…
5 steps12 minOpen
Cases / BIM & takeoff
BIM & takeoff
Raise a design query from BIM coordination
Turn a conflict spotted in the federated model into a formal design query, get it answered by the right discipline, and update the model once the fix lands.
How it works, step by step
3 steps across the platform - what you do at each one, and why it matters.
1
Review the federated model
FederationsOpen the federation and look over the area the coordination meeting flagged, checking which discipline model actually needs to change.
Why: A query raised against the wrong discipline just bounces back a week later. Confirming the source in the federated view first is what gets it to the right desk the first time.
InFederated modelCoordination flagOutLocated conflictResponsible discipline
2
Raise the query
RFIsRaise a formal request naming the element, the model view it was found in and the clash or conflict it causes, with a date tied to when the trade needs the answer.
Why: A conflict mentioned in a meeting and never formalised gets forgotten by the next one. A dated, written query is what keeps it moving until it is actually resolved.
InLocated conflictModel viewpointAnswer deadlineOutFormal design queryTracked RFI
3
Update the model
BIMOnce the answer lands, update the affected model and confirm the fix against the original conflict before it is reissued to the team.
Why: The query only closes the loop when the model itself reflects the fix. Otherwise the same conflict resurfaces the next time someone federates the set.
InQuery answerAffected modelOriginal conflictOutUpdated modelVerified fix
Modules in this playbook
3 / 184 platform modules
