The Model Checker helps project teams identify IFC schema and model quality issues in their IFC+SG models before and during CORENET X submission, allowing issues to be identified and addressed early.
The Model Checker comprises three checking components, each with a dedicated purpose.
Checks IFC file validity and structure to ensure it can be processed by CORENET X.
Verifies the IFC file's schema, integrity and structure to identify issues that may prevent it from being processed.
Examples of checksIFC version, file integrity, mandatory attributes and spatial hierarchy.
Checks selected IFC+SG model quality requirements and information completeness.
Reviews selected IFC+SG model quality requirements and the completeness of information required by the CORENET X Code of Practice.
Examples of checksRequired model information, property completeness and selected modelling requirements.
Supports checking selected regulatory requirements using BIM model information.
Intended to support automated assessment of selected regulatory requirements using information contained in BIM models.
ImplementationRegulatory checking capabilities are planned for progressive implementation.
The Model Checker is being developed and implemented progressively. The current version supports selected IFC Schema Checks and Quality Checks, with additional checking capabilities to be introduced in subsequent phases.
The Model Checker can be used before formal submission and as part of the CORENET X submission process.
Project teams can use the Pre-Submission Check to identify IFC schema and model quality issues before formal submission.
Upload IFC models, run the available checks, review results and make necessary corrections before submission.
The Model Checker forms part of the formal CORENET X submission workflow.
IFC Schema Check is performed when models are uploaded. Quality Check is initiated as part of the submission workflow.
Learn how to use the Model Checker MVP to check IFC models and review checking results.
The step-by-step industry guide provides instructions for using the Model Checker before and during CORENET X submission.
View Step-by-Step GuideEnter the error code or select an issue below to understand the possible cause and recommended troubleshooting steps.
The Model Checker is unable to read or process the IFC file.
The IFC file may be incomplete or corrupted and cannot be processed correctly.
The IFC file was exported using an IFC version or Model View Definition that is not supported for CORENET X submission.
The IFC export settings in the BIM authoring software may not have been configured for IFC4 Reference View.
The Model Checker cannot identify a valid IfcProject at the top of the IFC spatial hierarchy.
A typical building model should follow the spatial hierarchy from the project down to the building storeys, with model elements contained at the appropriate storey.
IFC exports from BIM authoring software should normally create the required project and spatial hierarchy. The hierarchy may be missing because of incorrect export settings, source model configuration, or subsequent modification of the IFC file.
IfcProject → IfcSite →
IfcBuilding → IfcBuildingStorey
→ building elements.
The Model Checker checks whether the IFC file contains at least one IfcSite entity.
An IFC file without an IfcSite will be flagged.
The expected spatial hierarchy for a typical building model is shown below.
For CORENET X submission, it is recommended to maintain only one IfcSite under the IfcProject to ensure a consistent spatial hierarchy.
The IFC export settings in the BIM authoring software may not be configured correctly, resulting in the IfcSite entity being omitted from the exported IFC file.
The Model Checker detected one or more entity types in the IFC file that are not valid for use under the applicable IFC schema.
The IFC file may contain an entity type that is not defined in the applicable IFC schema, or an IFC entity that exists in the schema but is defined as an abstract entity and should not be used directly in an IFC file.
These issues may be introduced during IFC export, conversion or subsequent modification of the IFC file.
The entity type is not defined in the applicable IFC schema.
The entity exists in the schema but should not be instantiated directly. A valid concrete subtype should be used.
For example, IfcCartesianPointList
is an abstract entity. The applicable concrete
subtype is IfcCartesianPointList2D
or IfcCartesianPointList3D.
The Model Checker detected invalid or incomplete IFC data that does not meet the expected IFC schema requirements.
The specific issue may vary depending on the affected IFC entity or attribute reported in the Model Checker error message.
The IFC file may contain one or more of the following issues:
IfcShapeRepresentation.ContextOfItems
— The required representation context is missing.
IfcShapeRepresentation.RepresentationType
— The representation type is missing or incomplete.
These issues may originate from the BIM authoring software, IFC exporter, or subsequent modification of the IFC file.
Please contact the CORENET X Helpdesk for assistance. Provide the IFC file, error code and detailed error message shown in the Model Checker to support investigation.
Check the error code or try another keyword.
Find answers to common questions about the CORENET X Model Checker, including its usage, checking results and technical support.
Visit the CORENET X Helpdesk to view the latest Model Checker FAQs and answers.
View Model Checker FAQsQuality Check (QC) reviews the completeness and consistency of BIM model information against selected requirements in the CORENET X Code of Practice (CX COP). It helps Qualified Persons (QPs) identify potential modelling and coordination issues.
Quality Check results are classified as Pass, Fail or Alert.
The BIM model has satisfied the requirements of the specific QC check.
The BIM model does not follow the applicable CX COP requirements and needs to be revised.
The BIM model may deviate from CX COP requirements. QPs should review and verify the reported issue.
Explore the six QC categories to understand the checking criteria, common issues and modelling guidance.
Checks whether building storeys follow typical naming conventions.
Name building storeys clearly and logically following standard naming conventions.
Checks for significant clashes between selected building elements, particularly structural elements.
Ensure BIM models across all disciplines are updated and coordinated.
Checks whether required IFC+SG information is correctly provided in BIM models in accordance with Section 4 of the CX COP.
Use IFC+SG interoperability tools to set up BIM models and ensure required information is provided in accordance with Section 4 of the CX COP.
Checks whether rooms and spaces are properly modelled and tagged by assessing the spatial coverage of floor areas.
IfcSpace.SPACE objects
in contact with IfcSlab.
IfcSlab fully covered by
IfcSpace.SPACE objects
is considered compliant.
Ensure habitable spaces (indoor and outdoor), functional spaces such as shafts and maintenance areas, and fully enclosed spaces are properly tagged with rooms.
Refer to Section 4 of the CX COP for modelling requirements.
Checks whether BIM models within the same submission have consistent georeferencing coordinates to support model federation.
Set up BIM models using the recommended georeferencing method and ensure coordinates are coordinated across disciplines.
Checks consistency of building storey names and finished floor levels (FFL) across BIM models in the same submission.
Coordinate among project team members to ensure consistent building storey naming and FFL values across all discipline models.
Upon completion of Quality Check, QPs can download the results in BIM Collaboration Format (BCF) from the CORENET X Submission Portal.
The BCF results can be reviewed using a compatible BCF viewer or BIM authoring software to identify the reported issues.
QPs should review the results and verify that their BIM models meet the applicable CX COP requirements.
For detailed Quality Check rules, examples of report messages and modelling guidance, refer to the CORENET X Model Checker MVP – Step-by-Step Industry Guide.
The guide provides additional information on the checking requirements and how to prepare BIM models for the Model Checker.