Model coordination & clash detection — ABNT NBR ISO 19650 & Decreto 10.306 (Brazil)

The BIM Execution Plan is the coordination contract. Map each task team's deliverables to the master information delivery plan before models start arriving.

• Consolidate task-team capability and capacity assessments (§5.3.2)
• Fix the federation strategy and model breakdown in the BEP
• Agree naming, origin, units and classification conventions up front

Federation quality decides clash-detection quality. Reject models that break the agreed conventions instead of coordinating around them.

• Verify shared coordinates, units and level structures on intake
• Check object classification against ABNT NBR 15965 terminology and process tables
• Stage models through the CDE's shared state (ISO 19650-1 container states)

Follow the AFD.4040 cycle: prepare models, define clash sets and tolerances, run detection, group and triage results, assign owners.

• Prioritise structure–services pairs on dense zones first
• Separate hard clashes from clearance and workflow clashes; set tolerances per discipline pair
• Keep machine results reviewable: group by location and system before assigning

An unresolved clash is an issue with an owner and a due date, not a report line.

• Exchange issues in open formats (BCF) so task teams work in their native tools
• Time-box re-test cycles to the information delivery milestones
• Escalate systemic clashes (repeat offenders by system or zone) to design leadership

Acceptance is against the exchange information requirements, not against zero clashes.

• Evidence clash status at delivery: open, accepted-risk, resolved
• Archive the coordination record with the delivered model state (ISO 19650-2 §5.7–5.8)
• Feed tolerance and convention lessons back into the organisation's BEP templates