IFC Coordination Workflow: A Singapore Guide From Export to Handover

An IFC coordination workflow on a Singapore project runs in a repeating cycle: each discipline authors and exports its model, the models are federated, the federation is validated, issues are recorded and resolved by the model owners, and a frozen version is released. The cycle then repeats at every milestone until handover. What separates a smooth cycle from a stalled submission is preparation before export: Singapore coordinates, IFC+SG data, unique GUIDs and an agreed exchange protocol. Our consultancy supports Qualified Persons with BIM submissions and authority approvals, so this guide is written from the submission end of the process.

Aectechnicalsg

Prepare IFC Models for Submission

AECTechnicalSG supports Qualified Persons with BIM submissions and authority approvals for Singapore construction projects.

Visit

TL;DR

The cycle is author, export, federate, validate, resolve, update and hand over. A model version is frozen and released only after identified issues are resolved.
Most IFC problems appear after export, not in the native software. Plan export and review early, and never leave them to the last minute.
Singapore models must be geo-referenced to SVY21 (EPSG:3414) for x,y and the Singapore Height Datum for z, and must carry IFC+SG data.
The CORENET X Model Checker runs a schema check, a quality check and a regulatory compliance check. Clean results before upload save review time.
For projects of $10 million or more contract sum, Design for Safety review meetings and a register run alongside the coordination cycle.

What an IFC coordination workflow actually is
The seven stages, in order
How long a cycle takes
Singapore-specific overlays
A practical checklist for your first cycle
Where we fit in
Our perspective
FAQ
Sources

What an IFC coordination workflow actually is

IFC (Industry Foundation Classes) is the open, vendor-neutral format that lets architectural, structural, mechanical and electrical models be combined even when each discipline works in different software. A coordination workflow is the agreed routine for how those exported models are combined, checked, corrected and re-released.

The Singapore BIM Guide describes the typical BIM process as model creation, then model coordination and data exchange. When identified issues such as clashes are resolved at a project milestone, a version of the model is frozen and released to model users. That freeze-and-release logic is the backbone of any IFC workflow you set up.

In Singapore the stakes are higher than for a private coordination exercise, because the same federated model increasingly feeds regulatory submission. Under CORENET X, co-led by BCA and URA, the submitted model is reviewed concurrently by seven agencies: BCA, URA, NParks, LTA, SCDF, PUB and NEA. The same report states that CORENET X is mandatory for new projects with a gross floor area above 30,000 m². A coordination error that a contractor might fix on site becomes, here, a failed check at a submission gateway.

The seven stages, in order

The stages below follow the sequence most openBIM teams use. Each one lists what it takes and where it usually goes wrong.

1. Author to an agreed standard

Every discipline models in its native software, but to a shared set of rules: level of detail, naming, classification, units, and the information each element must carry. These rules sit in the BIM Execution Plan and the data exchange protocol.

Where it goes wrong: teams discover mid-project that two disciplines used different level conventions or element naming. Agree these before modelling starts. Our checklist on BIM level of detail covers the six checks that prevent the rework this causes.

2. Set up coordinates before you export

The CORENET X General Modelling Practices tell teams to set up coordinates and check alignment before IFC export, to keep unique GUIDs across models, and to export gridlines to all storeys. Duplicated GUIDs typically appear when someone creates multiple blocks, copies templates or manages linked discipline models.

Singapore adds a fixed reference frame. The CORENET X Code of Practice states that models are geo-referenced to the SVY21 coordinate system (EPSG:3414) for Easting and Northing and to the Singapore Height Datum for height. The EPSG registry entry defines the combined reference as SVY21 / Singapore TM plus SHD height, with a false easting of 28001.642 m and a false northing of 38744.572 m.

Where it goes wrong: one discipline models on a local origin and another on survey coordinates. The models then appear to be in the same place in the authoring tool and diverge after export. The CORENET X checking levels guidance gives a simple test: open a third-party IFC viewer, pick a point and compare its coordinates with the expected real-world values. Models should also sit in True North orientation, with levels set against SHD.

3. Export and check the IFC file itself

Export is where native-model quality meets file-format reality. CORENET X warns that models perfectly geo-referenced and mapped in the native software may encounter unexpected problems after export into IFC, and that teams should allow enough time to align coordination, planning and management workflows across the project.

Singapore-specific data is the common trap. The Code of Practice defines IFC+SG as new representations for local regulatory requirements within the IFC openBIM standard. A 2026 industry guide explains that IFC+SG extends the IFC4 schema, that Singapore-specific property sets carry the SGPset_ prefix, and that structural engineers often leave ConstructionMethod empty in SGPset_Slab while M&E consultants often omit SGPset_DuctSegmentType and SGPset_PipeSegmentType.

There is also good news on modelling effort. The Code of Practice states that, provided the IFC+SG data and minimum dimensions are represented, components need not replicate their real-life form. A tree can be a simple lollipop object if parameters such as girth, height and status are present. Spend effort on data, not decorative geometry.

4. Federate the models

Federation combines the discipline models into a single project model. The Code of Practice defines a federated model as a combined BIM compiled from multiple disciplines or sections, supporting concurrent authorship and multi-disciplinary coordination.

Before federating, the Singapore BIM Guide expects each discipline model to be checked, approved and validated as fit for coordination, and recommends a common software platform to reduce data loss or errors when models are shared. Its pre-coordination checklist is practical:

Remove drawing sheets and extraneous views.
Purge and compress each model file.
Conform file format and naming to the project data exchange protocol.
Segregate data as set out in the BIM Execution Plan.
Make sure models are up to date and detached from central files.
Remove linked reference files.
Inspect visually that the model is assembled correctly.

Where it goes wrong: a model is sent while still attached to its central file, or with stale linked references, and the federation shows ghost geometry or missing elements. A person reading the federated view assumes a design error where the cause is a file-preparation error.

5. Validate: clashes, data and rules

Validation has three layers, and Singapore teams should run all three.

Geometry and clash checks. The federated model should be free of physical conflicts between disciplines. The Bimeco guide gives examples such as a duct running through a structural beam or a pipe clashing with a cable tray, which flag during automated checks and stall a submission.

Schema and quality checks. The CORENET X Model Checker has three categories:

Check	What it tests	Example finding
IFC Schema Check	First line of validation: does the file meet basic IFC standards?	File structure that does not conform
Quality Check	Completeness of information against the CX Code of Practice	Missing mandatory properties; poor geo-location alignment across disciplines
Regulatory Compliance Check	Automated assessment against selected regulatory requirements	Insufficient headroom clearance; undersized bicycle parking lots

The same page states that when checks return issues, Qualified Persons should revise the models and upload them again. For the Quality Check, QPs should verify consistency and completeness of information across all discipline models before submission, to help agency review move efficiently.

A rule-checking run is only as useful as the person who interprets its output. Our page on the independent design check against the Model Checker sets out how we approach that review for Singapore projects.

6. Record and resolve issues

The Singapore BIM Guide requires that discrepancies found during coordination be recorded, managed and communicated to the relevant model owners through coordination reports. Each report should give the specific location of the interference and a suggested resolution.

A good issue record has the same fields every time: a unique ID, the disciplines involved, the element GUIDs, the location by grid and level, a status, an owner and a due date. Consistent fields are what make a closed-loop process auditable, and the same discipline applies to logging specification and drawing conflicts on the estimating side, where an unlogged conflict becomes a pricing gap.

Where it goes wrong: issues are discussed in a meeting and fixed in one model, but nobody records which model owner is responsible, so the same clash returns in the next cycle. Assign one owner per issue, always.

7. Update, freeze and hand over

After fixes, each owner re-exports, the federation is rebuilt and the affected checks are re-run. The BIM Guide requires that the revised version be frozen and signed off once issues are resolved, and notes that a digital signature can be used. Handover is then the final frozen and signed-off federated model, with its issue log, as the project record.

How long a cycle takes

Cycle times vary by project size, but one practitioner glossary gives a useful planning benchmark. It describes a coordination round as export and upload in one to two days, a clash run of one to two hours, a report review meeting of two to four hours, design decisions and fixes over three to seven days, re-export in one to two days and a recheck with sign-off in one day. That breakdown comes from a Slovak practice, so treat it as a rough rhythm, not a Singapore requirement. The pattern is the point: the fix step dominates, so the earlier issues are found, the cheaper they are.

The CNA report quotes a CORENET X representative as saying that the federated model enables earlier identification of clashes and buildability issues, reducing site rework and construction risk, and that the overall regulatory approval process is expected to take up to 20 per cent less time over the project timeline.

Singapore-specific overlays

CORENET X gateways

The Code of Practice describes the Regulatory Approval Process for Building Works as three sequential submission gateways to all agencies, each with one collective and coordinated approval. It is complemented by pre-submission consultation, waivers and an escalation mechanism at the Inter-agency Coordinating Committee. Each gateway expects the correct level of detail and data inputs, so your coordination cycle should be timed to finish a clean frozen version before each gateway, not after it.

For the submission-readiness view, see our guide to passing CORENET X first time and the four requirements before a BIM submission. For the wider policy picture, Singapore’s BIM mandates are covered in a separate article.

M&E coordination

M&E is where most clash volume sits and where IFC+SG data gaps are common. Our guide to three checks for M&E coordination drawings deals with the drawing side, and the M&E engineering workflow guide covers how to sequence design information.

Civil and infrastructure models

Civil projects share the same reference frame. Alignments, corridors and pipe networks only coordinate with buildings if both sit on SVY21 and SHD. Set the coordinate system once, at the start of the project, and apply it to every model, including temporary works. Our article on BIM for temporary works shows how formwork and scaffolding are brought into the same federated environment.

Design for Safety

Coordination meetings are a natural place to surface design risk, but Design for Safety has its own legal duties. The Workplace Safety and Health (Design for Safety) Regulations 2015 apply to construction projects undertaken by a developer in the course of business with a contract sum of $10 million or more, involving development under section 3(1) of the Planning Act. They also apply to projects that modify a permanent structure for which a DfS register has been kept.

The REDAS Good Practice Guide (September 2025) adds that the developer must ensure foreseeable design risks are eliminated where reasonably practicable, or reduced to as low as reasonably practicable at source using collective protective measures. The developer convenes DfS Review Meetings attended by all relevant designers and contractors and keeps a DfS Register recording the meetings and every residual design risk. Only those two duties, convening the meetings and maintaining the register, may be delegated to a DfS Professional.

In practice, align the calendars: hold DfS reviews against the frozen federated version, and cross-reference residual risks to issue IDs. Our Design for Safety construction guide explains the duties in more detail.

A practical checklist for your first cycle

Confirm the BIM Execution Plan, data exchange protocol and responsibility matrix.
Set SVY21 and SHD in every model, and verify with a third-party IFC viewer.
Run a test export early and fix mapping problems while there is time.
Check that IFC+SG property sets are populated on the elements that need them.
Clean each model: sheets, views, links, central-file detachment.
Federate, run clash and Model Checker validation, and issue a coordination report with locations and suggested resolutions.
Resolve, re-export, re-check, then freeze and sign off the version.
Repeat at every milestone and before each submission gateway.

Where we fit in

The workflow depends on people who can read both the model and the regulations. We provide engineering and architectural consultancy in Singapore, including BIM modelling, PE endorsements for structural and geotechnical engineering, statutory authority submissions and M&E engineering design. That means the person coordinating your model can also see what the authority will ask of it.

If you are preparing a submission, start with our statutory submission and PE endorsement services or contact us through the services page.

Our perspective

We treat the IFC workflow as a compliance workflow that happens to use models. A federated model is no longer only a design tool in Singapore: it is what agencies review, so every coordination decision is also a submission decision.

Our approach is to bring engineering design, BIM modelling and authority submissions into one conversation. When the same team understands structural, M&E and regulatory requirements, an issue found in coordination can be resolved with the submission in mind, and a Model Checker result can be read as an engineering question, not only a file error.

We aim to be responsive and clear in communication, because a coordination cycle is only as fast as its slowest answer. Our focus is timely turnaround on submissions and direct communication with project teams.

Aman

FAQ

What does IFC stand for, and why use it for coordination?

IFC stands for Industry Foundation Classes, an open format that carries geometry and data between different BIM tools. It lets architects, engineers and M&E consultants combine models without sharing one software platform. In Singapore it is also the format used for CORENET X submission, extended with IFC+SG data.

Which coordinate system should Singapore IFC models use?

CORENET X requires SVY21 (EPSG:3414) for Easting and Northing and the Singapore Height Datum for height. Set it before export and verify it by checking a known point in a third-party IFC viewer.

Who is responsible for fixing a clash?

The model owner whose discipline is assigned the issue in the coordination report. The BIM Guide requires discrepancies to be communicated to the relevant model owners with the location and a suggested resolution, so each issue should have one named owner.

Does Design for Safety apply to my project?

The regulations apply to developer-led construction projects with a contract sum of $10 million or more involving development under section 3(1) of the Planning Act, and to certain modifications of permanent structures with a DfS register. Confirm applicability for your own project with your developer’s appointed professionals.