CORENET X vs CORENET 2.0: Why You Should Start Using BIM

As part of Singapore’s ongoing digitalisation efforts, the Building and Construction Authority (BCA) continues to drive the adoption of BIM for regulatory approvals. CORENET 2.0 was launched in 2022 to support Qualified Professionals (QPs) with submissions. Since then, BCA has advanced the system with the pilot of CORENET X. From 1 October 2025, all projects above 30,000 sqm must be submitted through the updated CORENET X platform.

This article highlights the key differences between CORENET 2.0 and CORENET X, and how firms can prepare for a BIM-based regulatory process.

Is BIM and IFC Required?

A core feature of CORENET X is the adoption of 3D BIM and the OpenBIM (IFC) schema. 3D BIM allows agencies to review even the most complex projects, checking for issues such as accessibility, fire safety, and compliance with urban planning guidelines.

To support the wide range of BIM tools in the industry, CORENET X adopts the open IFC standard. This ensures that models created in different software can still be validated and reviewed in CORENET X.

Firms must therefore begin modelling in the IFC+SG format to comply with Singapore’s regulatory requirements.

What is IFC+SG?

Singapore’s IFC+SG is an extension of the internationally-recognised IFC4 schema, with additional model parameters required by agencies such as URA, NEA, BCA, PUB, and LTA. These contain additional information that the agencies use as part of their approval workflow.

Here’s an extracted snippet from the industry mapping table:

In this example, URA requires the area of existing earthworks to be captured directly in the BIM model, using a Singapore-specific property set: SGPset_GeographicElementDimension. For an agency like URA, such information is necessary to verify compliance with masterplanning guidelines, ensuring zoning and land-use requirements are being met. The industry mapping table provides a complete reference of the model parameters expected by each agency.

Are 2D Submissions Still Required?

Despite the benefits of 3D coordination, not all data can be represented effectively in a BIM model. Capturing highly detailed elements such as connecting details between specific structures may also affect model performance and load times.

CORENET X does not remove the need for 2D submissions. Agencies still require supporting documents such as detailed drawings and design calculations that cannot be fully expressed in 3D. These information may be independently submitted to the respective agencies via the CORENET X platform portal.

How to Submit via CORENET X

CORENET X is a web-based portal that manages document submissions, permit applications, and project status. A Qualified Person (QP)—an Architect or Professional Engineer—acts as the Project Coordinator. The developer appoints the QP, who then brings other stakeholders into the project.

The approval process is organised into four gateways: Design, Piling, Construction, and Completion. Each stage has specific requirements involving both 3D BIM models and 2D drawings.

Once a federated BIM model is submitted, agencies review it collectively and issue a single consolidated response, typically within 20 working days.

After approval, the Project Coordinator may apply for the necessary permits directly in the CORENET X portal.

CORENET X vs CORENET 2.0

Compared to CORENET 2.0, CORENET X requires earlier subcontractor onboarding and more complete BIM models at the design stage. For instance, contractors handling piping, plumbing, or ducting may need to provide their BIM models during the Design Gateway.

QPs must ensure submitted models are federated, clash-free, and embedded with IFC+SG values. Failure to include the necessary parameters in the model may result in Written Directions issued by the authority. In severe cases, this may lead to delays in the permitting process.

Beyond submissions, the CORENET X portal functions as a central project management environment. It supports plan permissions, site inspection scheduling, and TOP/CSC submissions. With role-based access control, all project stakeholders can track project status in a single environment, improving transparency and accountability.

How to Get Ready

For firms with in-house BIM teams, major software vendors now support IFC+SG workflows. Tools like Revit, OpenBuildings, Tekla, and ArchiCAD each have specific resources to ensure exported models include IFC+SG parameters. For example, a Revit template can be configured so walls, beams, floors, and doors automatically include the required fields.

BCA also provides the CORENET X Sandbox, where firms can simulate the submission process and test different project roles.

Although mandatory submission only begins on 1 October 2025, firms are strongly encouraged to test the system early on smaller projects.

For firms without in-house BIM teams, partnering with BIM Service Providers is a practical way to gain experience before investing in full-time staff.

Validating BIM Models

While BIM tools can export IFC+SG models, workflows often vary across firms and subcontractors. Since QPs must submit a federated model, it is important that all sub-discipline models include the required IFC+SG parameters as defined in the industry mapping table.

IFC+SG model validators allow QPs to check federated models for compliance before submission. Advanced validators like the Bimeco validator support model federation, large model loading, IFC+SG value checks, and editing of parameters directly.

It is essential for all stakeholders to validate models before submission. Critical data—particularly those related to safety and accessibility—must be embedded correctly. Missing or incorrect values may trigger a Written Direction, and if unresolved, can escalate into serious project delays.

Conclusion

CORENET X marks a major step in Singapore’s regulatory digitalisation. With mandatory BIM submissions starting on 1 October 2026, firms should prepare early—whether through in-house teams or external providers—to avoid last-minute complications and ensure smooth compliance.