Workflows / Clash detection and coordination in the BIM model
Clash detection and coordination in the BIM model
Clash detection step by step in Calq: structure against architecture, services against structure and against each other, a model against its linked models, the clashes grouped by cause with the change that clears them, the safe ones cleared in one step, and the rest kept as BCF issues through every round.
- Available
What clash detection is for
Clash detection finds where two elements want the same space, or come closer than they may. It is the heart of LOD 350: an LOD 400 element made from an uncoordinated model is waste. A clash is not only a hard overlap: a duct that leaves no room for its insulation, a pipe too close to a beam to be hung, a run through a column's punching zone are clashes too.
Most tools detect clashes in a separate program after the models are exported. In Calq the check runs on the live model, with every discipline in it or linked to it, and the fixes are made in the same model.
What Calq checks
Each finding is hard (the sections overlap), soft (closer than the clearance) or a gap, and is grouped by its cause with the one change that clears it and whose change it is.
- Structure against architecture: columns and beams against walls, doors, stairs and rooms
- Services against structure: ducts, pipes and trays against beams, columns and slabs
- Services against architecture and voids: runs through walls and shafts, openings each run needs
- Services against each other: crossings of ducts, pipes and trays
- Each discipline's own faults: open ends of runs, a column on no footing, a member with nothing to stand on
- This model against each linked model, with a tolerance
Run a round, step by step
- Read the clashes: the Building services (MEP) shelf, Clashes, opens the Services coordination plan mode; or ask Calq AI "give me the coordination report of level 3" (coordination_report, clash_report; at the MCP door coordination_report is listed by name).
- Clear what is safe: Fix clashes on the shelf, or coordinate_model: the services are moved clear of the structure and of each other by the coordination priority (gravity drainage stays, then ducts, then sprinkler mains, then pressurised pipes, then cables move), openings are made where runs must pass, and the model is read again until a pass mends nothing. One undo step.
- Say the basis: the clearances, the service zone depths, the shafts and the opening rules the coordination uses are the team's, kept on the model (engineering_basis).
- Keep what needs a person as issues: clash_issues writes each service clash as a BCF topic with its camera, kept in step through the rounds: a new clash opens a topic, a cleared one is resolved with a comment, a clash that comes back is reopened, a topic closed elsewhere stays closed.
- Work the issues: the Issues drawer lists them with status, priority, type, assignee, comments and viewpoint (raise_issue, list_issues, update_issue), and they go out and come back as BCF 2.1 or 3.0 (export_exchange bcf, import_bcf).
Across linked models
- Link the other disciplines' models (link_model) and check them against yours (check_links).
- Coordinate them: each model changes only what is its own; your runs move clear of their beams and ceilings, the openings their runs need in your walls are made by you, and what they must do is said as a request (coordinate_links).
- For a party not in Calq, the requests leave as IFC provisions for voids and BCF topics that both models name the same way (export_link_requests).
Close a round
- The report reads clean, or each clash left is an issue with an owner and a date
- Every opening has its run and every run its opening
- The issue is recorded with its revision, and the next round starts from it
Questions
Does Calq do clash detection?
Yes. It checks structure, architecture and services against each other and against linked models on the live model, groups the clashes by cause and says which change clears each one.
Can Calq fix clashes automatically?
It clears the ones that are safe to clear, by a coordination priority, in one step you can undo, and keeps the rest as issues for a person to decide.
Does Calq read and write BCF?
Yes, BCF 2.1 and 3.0, with viewpoints, and service clashes are kept in step as BCF topics through the rounds.
Can I check my model against a consultant's IFC?
Yes. Link the IFC into your model and check it; what you need from them leaves as IFC provisions for voids and BCF topics.