Docs · Revit plugin
IFC+SG and CORENET X
CORENET X is Singapore’s building submission system: one submission across seven agencies, with IFC+SG as its mandatory data standard. IFC+SG adds Singapore-specific classes and property sets to IFC.
It is mandatory for new projects of 30,000 m² GFA or more since October 2025, and for 5,000 m² or more from 1 October 2026.
The IFC+SG dictionary
BMC generates its IFC+SG data from the official CORENET X workbook (the ifcsg-dict module):
| Contents | Count |
|---|---|
| IFC+SG elements | 300 |
| Properties | 2,199 |
| Validation rules | 312 |
| Revit shared parameters | 373 |
| IFC ↔ Revit mappings | 964 |
It ships as JSON, a relational SQLite database, and Revit resources: the property-set mapping, shared parameters and a parameter registry with stable identities.
From Revit to IFC+SG
- IFC+SG Parameters binds the shared parameters to the right Revit categories.
- You fill them in Revit.
- Export IFC with the IFC+SG (BMC) mapping writes them into the IFC+SG property sets.
- Singapore in the georeference sets SVY21 (EPSG:3414) as Autodesk does.
How it is checked
Test copies of the samples have every IFC+SG parameter filled with dictionary values: about 30,000 values on RAC and 61,000 on DACH. BMC’s IFC is compared with Autodesk’s:
- RAC: every layer passes.
- DACH: every layer passes except where a built-in and an IFC+SG parameter share a name. There BMC deliberately keeps the parameter you filled (difference 4).
Coming next
The IFC+SG validation rules feed the checker. See the roadmap.