Intent
Viewing an IFC model is not the same as checking it
An IFC viewer answers visual and exploratory questions: can the file be opened, where is an element, and which properties does it carry? An IFC model checker starts with a defined requirement or review question and compares the model against it. Keeping those jobs separate prevents a smooth-looking model from being mistaken for a complete or compliant information delivery.
- Visual navigation provides geometry and coordination context.
- Property inspection helps a reviewer understand the information attached to selected elements.
- Structured validation needs explicit requirements and an interpretable result.
Information quality
Check IFC properties in context before automating
Start by sampling representative elements in ExyViewer. Confirm entity mapping, names, classifications, property sets and quantities that matter to the intended use. This manual inspection exposes export conventions and inconsistent data before a broad automated run creates hundreds of failures that the team cannot interpret. A missing value, a value on the wrong entity and a valid project exception are different findings.
- Choose the model areas and element groups that match the delivery scope.
- Inspect representative property sets before defining a pass or fail rule.
- Record the responsible discipline and expected correction path.
IDS validation
Use IDS for defined information requirements
Information Delivery Specification (IDS) provides a machine-readable way to describe selected IFC information requirements. Where an appropriate IDS specification exists, ExyViewer can validate the model against those definitions and present the results for review. IDS is valuable for repeatable property and applicability checks, but the specification must accurately express the project requirement and the results still need professional interpretation.
- Validate a reviewed IDS specification rather than an untested rule set.
- Group and inspect failures to distinguish systematic export problems from isolated exceptions.
- Keep the source requirement, model version and review decision connected.
Issue workflow
Turn meaningful findings into BCF follow-up
A checker result is useful only when the project can act on it. ExyViewer supports a review chain in which meaningful validation or coordination findings can be organized with BCF issue context and included in reports. Promote only findings that need action, give them enough viewpoint and element context to be understood, and route them to the responsible authoring team. The correction itself remains in the appropriate model-authoring workflow.
- Avoid converting every machine result into an issue automatically.
- Preserve viewpoint, selected elements and a concise statement of the requirement.
- Recheck the corrected model version against the same agreed scope.
Limits
What automated BIM validation cannot prove
Automated IFC validation can show whether encoded data matches encoded rules. It cannot prove design quality, engineering adequacy, contractual acceptance or regulatory compliance unless the responsible process and qualified reviewers make those decisions. Geometry that passes a clash tolerance may still be unbuildable, and a property that satisfies an IDS rule may still be wrong for the project. Use the checker as evidence within governance, not as an automatic approval stamp.
Practical sequence
A focused IFC model checking workflow
Open and orient the model, inspect representative properties, define the exact information requirement, then run the relevant IDS or coordination check. Review grouped results in their 3D and data context, promote actionable findings into BCF or a report, and verify the next model version against the same scope. This sequence keeps model validation explainable and reduces false urgency from unscoped result lists.