Model issue exchange with BCF
BIM Collaboration Format (BCF) is a buildingSMART standard for communicating model-related issues across applications. It can carry topic information and model context such as viewpoints and component references. Teams still need access to the relevant model; exchanging an issue is not the same as exchanging its geometry.
Use an issue to describe a condition that needs a decision or correction. Include the scope, expected outcome and responsible owner so the receiving team can assess the issue without attending the original review.
Official references
Make the issue actionable
| Field | What to include | Illustrative example |
|---|---|---|
| Title | The object or location and observed condition | Equipment asset code missing in service zone A |
| Model context | Delivery identifier, revision and affected object IDs | Coordination R03; identifiers attached |
| Expected result | The agreed requirement or acceptance criterion | Required equipment has a non-empty approved asset code |
| Actual result | A factual description of the difference | Three reviewed items have no value in the agreed field |
| Location | A viewpoint and written navigation context | Level 02, service zone A, equipment group |
| Responsibility | Owner, due date and decision needed | Discipline coordinator to confirm and correct source values |
| Closure evidence | What will demonstrate resolution | Updated revision and successful repeat of the data check |
This example is illustrative. Use identifiers from the reviewed file, and include the rule or requirement reference where available. Group related objects only when they share the same cause and can be resolved by the same owner.
Test issue exchange before using it project-wide
- Confirm compatible BCF versions and the file or connected-service workflow supported by both applications.
- Exchange one trial issue against the same model revision on both sides.
- Check that the viewpoint, selected objects, written description and ownership arrive as expected.
- Agree how each system maps statuses and whether attachments or custom fields transfer.
- Document how changed object identifiers and revised models will be handled.
If the recipient cannot locate an object, first compare model revisions and identifiers. Do not close an issue merely because its saved view no longer opens. Preserve a written location and the original delivery reference so the condition can still be investigated.
Separate correction from verification
Triage
Confirm the issue is reproducible, assign an owner and agree the required action.
Correct
The responsible author changes the source or provides an evidence-backed explanation. Record the replacement model revision.
Verify
A reviewer repeats the original check in the corrected delivery and records the result.
Close or reopen
Close with evidence when the criterion is satisfied; reopen with the remaining condition if it is not. Record approved exceptions explicitly.
Check screenshots, comments and attachments for information that should not be shared outside the recipient group. Keep sensitive project details in the approved issue-management location and use only the material necessary to explain the finding.