FAQ

CORENET X will be rolled out progressively and eventually replace the current CORENET system when CORENET X is implemented (target in end 2023). In the steady state, CORENET X will handle both BIM and non-BIM submission. We will ensure that the transition is smooth, taking into consideration the user experience to QPs to avoid confusion.

All projects are required to be submitted to CORENET X for regulatory approval. The regulatory approval process, which consists of the 3 gateways, will apply to both BIM and non-BIM submission. 

For smaller projects, we are looking into simplifying the process so that they need not go through every gateway. This includes the possibility of lodgement schemes for less complex projects (like landed residential properties).

For BIM e-submission requirements, they will apply to projects above 5,000 sqm. These projects include:

• new building and infrastructure projects; and
• A&A projects involving reconstruction or addition of any new building or infrastructure.

We are also reviewing whether the requirements for BIM e-submission should be extended to other projects less than or equal to 5,000 sqm that do not require BIM e-submission today. 

More details on the projects that will submit to CORENET X will be released later.

In line with the service standards across agencies today, we will strive to give a consolidated multi-agency response within 20 working days for each gateway submission.

In terms of overall approval process duration, we anticipate more time will be needed upfront during the initial planning and design stages, both for QPs to incorporate and coordinate multi-disciplinary inputs, to meet each gateway's level of details required in the consolidated BIM model, and for agencies to collaborate and provide consolidated responses.

However, we anticipate that increased efforts to get the design right upfront will lead to reductions in the possibility of conflicts between responses by agencies, reducing QPs’ resources in resolving these conflicts with relevant agencies much later in the project timeline. This will also lead to less painful downstream design iterations, abortive reworks and demolition of works, especially towards the completion of the project at TOP stage. Overall, this will lead to a much shorter overall approval process duration as compared to that of today.

At each gateway in the new CORENET X regulatory approval process, SCDF will conduct checks on major requirements that may affect cross-agency requirements or piling works. Examples include the provision of fire engine access, exit staircases and fire lifts.

For other technical details that are specific to SCDF only, SCDF may still adopt the self-regulation approach to grant approval first and subject the submission to random audit checks after approval.

SCDF is still assessing this and will update when more details are ready.

Each project team will jointly submit coordinated BIM models from the Architectural, Structural and MEP (Mechanical, Electrical, Plumbing) disciplines, consisting of:

• openBIM format files in the Industry Foundation Classes (IFC) format
• related submissions and supporting documentations (format to be confirmed)

A Code of Practice for CORENET X, including modelling requirements and related templates, is currently under development. As of July 2022, a draft set of IFC-SG configuration files is available here for testing by industry practitioners.

Launched in November 2001, the Construction & Real Estate Network (or CORENET) is a Government to Business system that enables built environment professionals to make project-related electronic submissions to regulatory agencies for approval within a secured environment, from anywhere at any time.

CORENET introduced the first wave of technological adoption and use of technologies in Singapore's built environment. The transition from paper submission into electronic submission in the early 2000s had set a good foundation for our local industry as construction and modelling technologies advanced, along with the introduction of BIM in 2010. 

When CORENET was introduced in 2001, the system allows separate submissions to the various agencies for regulatory approval based on project progress. This supports expedience and is pro-business for the industry. Nonetheless, this is not without trade-offs. The practice of separate submissions based on project progress also meant that the plans are prepared and submitted at different stages of a project. Consequentially, the regulatory agencies would review the plans at different stages and convey their respective comments. Industry practitioners would have to address these comments and incorporate them into their design and re-submissions while ensuring that the changes will not affect what had been previously approved by the other agencies.

The advent of BIM and emerging technologies presents the opportunity for the current modus operandi of the regulatory approval process to transform, becoming more integrated and smarter.

CORENET X will change the current practice of requiring each consultant to deal separately with multiple agencies to one where the project team comes together to produce and submit a coordinated BIM model for respective agencies to extract information for compliance review. Agencies will review the submission collectively and provide a consolidated response to the project team. The integrated submission process will improve regulatory governance and synergy among agencies, providing a One-Stop Integrated Digital Shopfront experience.

The current CORENET is an internet-based portal system for building professionals to make separate, individual electronic submissions to regulatory agencies for approval.

CORENET X will be a cloud-hosted platform that leverages BIM technologies to transform the current process, supporting and complementing projects that adopt the use of Integrated Digital Delivery (IDD).

CORENET X will facilitate and support new workflows that allow project teams to submit a coordinated BIM model to the authorities. The digital platform will help bring different regulatory agencies together to review the submission collectively and provide a consolidated response to the project team.

Key Transformation Shifts from CORENET today to CORENET X in the future

CORENET X is currently in its early development. It adopts an agile approach and is targeted to be rolled out from end 2023.

CORENET X is likely to be rolled out in phases, e.g. by project typologies. More details will be released when ready.

The CORENET X initiative comprises the following key public agencies - BCA, URA, NParks, LTA, NEA, PUB, SCDF, SLA, HDB, JTC and GovTech. 

Currently the CORENET X initiative comprises the following key public agencies - BCA, URA, NParks, LTA, NEA, PUB, SCDF, SLA, HDB, JTC and GovTech. As CORENET X will eventually replace the CORENET system, it will cover the submissions currently made through CORENET (such as IMDA - TFCC submissions and City Gas).

Yes, much like today's process. Approved plans will be made available, upon owner's consent. Further details will be released when ready.

This is currently being explored. In the evisaged workflow, QPs are expected to only interact with one single CORENET X interface irrespective of which agency's fees they are paying to. More details will be shared when ready.

CORENET X will eventually cover all applications available in the current CORENET today. As part of the efforts to redesign and improve the user's experience, we will look into enhancements and improvements to these application types. More details will be shared when ready.

A Service Blueprint is being developed as part of the Code of Practice for CORENET X. A draft as of June 2022 can be accessed here.

The Gateway clearances in CORENET X are fundamentally different from the current regulatory building works approval process. Each Gateway is considered to be cleared only when all relevant requirements by all the 7 agencies are met. At the Design Gateway, project teams should aim to clear strategic planning and design parameters such as building envelope, building form, height, setbacks, plot ratio, site boundaries, vehicular access, etc.

For project teams who submit to the optional Piling gateway, current macro-level requirements for commencement of piling/substructure works need to be fulfilled, e.g. unit layout, structural grid, etc.

The Construction Gateway will be deemed cleared when the proposal results in issuance of URA’s Written Permission (WP), BCA’s Building Plan (BP) and the BP clearances of all other agencies.

No, the submission would be a joint submission by relevant QPs. Thus the statutory responsibilities of each QP remains unchanged.

• QPs only need to make submissions if there are requirements at the respective Gateway related to their statutory responsibilities.
• While it is possible that there are Gateway(s) that a QP does not have to make submissions, e.g. Structural / M&E Engineers in the Design Gateway, these QPs need to provide inputs to the Registered Architect so that the submission encompasses all aspects of planning.
• Between Gateways 2 and 3, independent submissions for agency-specific technical details are allowed for submission by individual professionals to agencies.
• To find out more about Gateways in CORENET X's Redesigned Process, pls go to this link

Yes, agencies' technical departments will be involved if their requirements are required to be submitted at the respective gateway.

No. The Piling Gateway is optional, and applicable for projects which wish to start piling works before obtaining Construction Gateway approval.

CORENET X will leverage BIM technologies to handle BIM submissions, including for Design & Build projects. Instead of industry preparing major or minor amendment plans to highlight the deviations, in CORENET X, officers will carry out model compare, i.e. to take the amended model to compare it with the previously approved one. 

This eliminates the current massive industry efforts in preparing amendment presentations in the BIM model. As CORENET X is currently in early development, requirements related to amendment submissions will be circulated to the industry via circulars and on this website when ready.

If there is any change in design from the approved plan, you will need to submit amendment submissions to clear the relevant gateway again.

A draft of the CORENET X amendment submission workflow, as of June 2022, can be accessed here.

No. A draft of the CORENET X amendment submission workflow, as of June 2022, can be accessed here.

Requirements for TOP Gateway submission is currently being calibrated. To facilitate the TOP progress, it would be challenging to industry if TOP can only be applied when everything is completed. Therefore, for certain works, QPs can proceed to clear the respective agency when the relevant aspect is ready. In CORENET X, a project dashboard would be made available and you can view and monitor the status of each agency's TOP/CSC application. We will release more information to the industry when ready.

Yes, once implemented, TOP processes will be incorporated into the CORENET X process.

We are working on the detailed workflow for waivers and modifications to ensure such application processes will be smooth in CORENET X, and will release details when ready.

No. Multiple agencies will issue one single consolidated reply at each gateway.

All consultants registered as the project team will have access to the consolidated comments. The new system will provide a dashboard / inbox feature that consultants can track the response and obtain the relevant documentation. 

This is currently being explored, we will update if a timeframe for QP response is necessary, and if so, how long it will be.

Multiple QPs would need to provide a consolidated response to address agencies' comments that require responses from multiple QPs in the same project team.

This would increase productivity for both the project team and multiple agencies in the regulatory approval process, potentially reducing the number of WDs issued to the project team.

Yes.

During processing, agencies will collaborate during the review. CORENET X will leverage technologies to automate the issuance of comments and approval. In the event of any conflicting issues that could not be resolved, the project could then be tabled to the Inter-Agency Coordinating Committee (IACC) for conflict resolution. 

Currently conflict resolution among agency requirements are carried out through the Inter-Agency Coordinating Committee (IACC) often at very late stages of the projects, where it is costly to amend design and works on site. CORENET X aims to bring conflict resolution earlier upfront in the project, where there is more flexibility for design changes.

When we were developing the new approval process, we engaged developers through REDAS. Moving ahead, we will be engaging the larger community of developers. When we implement CORENET X, we will communicate the process and timelines to all our stakeholders.

This will be explored with REDAS and related industry stakeholders.

Yes.

Yes.

Only existing development that affect the regulatory compliance of the new extensions in the A&A projects will need to be modelled in the CORENET X submission, e.g. interfacing building elements and structure.

Multi-agency pre-submission consultation is currently being explored. We will update the industry when more details are ready.

This is currently being explored. We will update the industry when more details are ready.

We are working with relevant agencies to streamline the process, including ways to project envelope control outlines from the base of the site topography. We will update the industry when more details are ready. 

Yes, the intention is for GFA checks to be automatically checked as well, and there is an ongoing pilot. For more info, pls go to https://www.ura.gov.sg/Corporate/Guidelines/Development-Control/Planning-Permission/using-CORENET-eSS/GFA-AutoChecker/.

Yes.

We are exploring how FSE solutions will be submitted and will inform the industry when ready.

Yes.

No. Construction Gateway amendment submissions on revised locations or coverage should be made before the M&E Engineer submits for Technical Clearance.

The consolidated BIM model should include details that need to be submitted to the various agencies. For example, if there are sanitary works, the details should be included in the submissions to PUB.

Drains should be in 3D unless there is a suitable representation that makes it easier for the industry to model without compromising on the processing by officers. E.g. PUB will check drain curvature, gradient, width etc. This may be required to be represented as part of the 3D drains in the future, as part of automated model checking. 

Yes. We are exploring how the info will be represented in the model and will inform the industry when ready. 

Many submissions by Licensed Plumbers are for non-development works. As such, these submissions can still be made via PUB's website.

Yes.

Details that cover cross-agency requirements will be submitted jointly by QPs in a project team, to the relevant CORENET X gateways (e.g. location of lift and escalators, height of building that may affect design of lightning protection). For technical details specific to certain agencies (e.g. design of the lift and escalator, design of the lightning protection), it can be submitted directly to agencies under independent submissions after the Construction Gateway. 

Other independent requirements which typically only affect the relevant agency (e.g. demolition, ERSS, and structural details of ancillary components such as barriers and claddings) can be supplemented and submitted with the required info following the Construction Gateway by separate QPs. These plans will need to make reference back to the coordinated model submitted by the main QP at the Construction Gateway. 

All BIM and non-BIM projects are required to be submitted to CORENET X for regulatory approval, including temporary works.

Temporary ERSS submission (e.g. steel struts, sheetpile wall and other ERSS elements which do not form part of the permanent structure) do not need to be incorporated into the BIM model. ERSS that is integrated into the permanent works will have to be incorporated into the BIM model. 

We are still studying the level of detail required to be captured in the BIM submission for CORENET X. We will work with the industry on the reasonable level of details to be modelled.

As long as relevant IFC-SG requirements are embedded in the tree object, we are open to exploring different ways in which trees can be modelled in IFC, e.g. a simple circle or a lollipop BIM object. We are mindful that more elaborate tree models can increase the file size of the BIM model.

We are still studying the representation of demolished trees required to be captured in the BIM submission for CORENET X. We will work with the industry on a reasonable representation for submission.

We are currently looking into the representation required for information from landscape architects, such as internal landscaping and planting schemes, and will share more with industry when ready.

Yes. We are exploring how these 2D details will be submitted and will inform the industry when ready.

Applications currently processed through CORENET today will continue to be processed in CORENET X. However, activities handled by Registered Surveyors (RS) today directly with SLA, such as submission of the certified survey plan or allocation of lot numbers, will still go through the SLA RS-Portal. We are currently exploring linkage between CORENET X and the RS-Portal to streamline submissions.

Due to ongoing development of IFC5 - OpenBIM for Infrastructure by BuildingSMART International, we are exploring what is the extent of modelling required for external works.  

The technology enablers are the openBIM Format, Automated Model Checker and Collaboration Platform. More info can be found here. 

IFC-SG is the extended version of IFC, introducing new representations for localised regulatory requirements.

The IFC4 Reference View is the format supported for CORENET X submissions, and includes local regulatory requirements called IFC-SG.

IFC-SG is based on the IFC4 Reference View MVD.

IFC-SG details will be included in our Code of Practice for CORENET X, which is currently under development. As of July 2022, a draft set of IFC-SG configuration files is available here for testing by industry practitioners.

The IFC-SG configuration files help to structure the building information needed for regulatory compliance, and export these information to the IFC format from respective BIM authoring tools. 

For more info, as of July 2022, a draft set of IFC-SG configuration files is available here for testing by industry practitioners. 

The IFC-SG configuration files include parameters from BCA, LTA, NEA, NParks, PUB, SCDF and URA.

As of July 2022, a draft set of IFC-SG configuration files is available here for testing by industry practitioners. This draft set is available for the past 3 year versions of Revit, i.e. 2020, 2021, 2022. The draft set is also available for Archicad versions up to Archicad 25.

Tekla and Bentley OpenBuildings' IFC-SG configuration files are currently undergoing internal testing and will be released at a later date.

Yes. All submissions must be geo-referenced to SVY 21 and sit properly on the cadastral base, to ensure that project data, including GIS data, are accurately incorporated into the submission model for agencies to process.

Yes. All CORENET X tech enablers are able to federate models within each submission, as long as the models are properly geo-referenced. 

Yes.  

Classification of spaces is being explored. Details will be shared when finalised. 

Yes. The minimum standard for the quality of the BIM model will be included in our Code of Practice for CORENET X, which is currently under development. We will also share the draft with industry for feedback before release. 

The model checker will be in-built with limited level of tolerance regarding variations in spelling. To prevent misspellings and other discrepancies, we strongly encourage users to use our IFC-SG templates and configuration files. We will share the draft with industry for feedback before release. 

The Automated Model Checker is targeted to check as many deterministic rules as possible, across multiple agencies. Deterministic rules refer to the geometric, spatial aspects of building elements and spaces. Rules that are not checked in the Automated Model Checker will still be manually checked by the authorities.

Yes. QPs will be able to use the Automated Model Checker to carry out pre-submission checks, so that the QPs can address any non-compliances identified by the Automated Model Checker, before QPs finalise their submission to CORENET X for multiple agencies' officers to process for approval.

If the waivers have been granted and deviations from regulations allowed by the relevant agencies, the checker will not fail or reject the submission.

No. The Automated Model Checker is a software that is largely rules-based. The use of AI will be explored in the later phase.

No. All correcting and changes to QPs' designs must be made by the QPs themselves.

It is common for users to amend default settings, including for IFC classifications in the various BIM software. Step by step guides on how to amend default settings for IFC-SG can be found at the latest IFC-SG Resource Kit, uploaded here.    

Step by step guides on how to export multiple linked files to any type of IFC file (e.g. international IFC formats or IFC-SG formats) will be created and uploaded here.    

No.    

The first phase of CORENET X training has started, focusing on IFC-SG. For more information and registration of training, please click here.

More about IFC-SG:

• Basics of IFC-SG Knowledge
• IFC-SG Resource Kit

Yes. 

2021

Click here for slides presented at the CORENET X introductory webinars (Sept - Nov 2021).

Click here for resources, recordings and slides of the 1st IFC Industry Webinar Series (July 2021) and 2nd IFC Industry Webinar Series (Nov - Dec 2021)

2022

Click here for slides presented at the Joint-TAC Industry Webinar (Oct 2022).