What ISO 19650 adoption actually looks like in a small practice

Why we pursued it

Clients in Singapore and increasingly in India started asking for ISO 19650 compliance in tender briefs. The standard is long and written in procurement language — it describes what must happen in an information management process, not how to do it in Revit or ACC.

We spent about four months translating the standard into operating procedures we could actually follow on a live project.

What the standard requires (in plain English)

ISO 19650 parts 1 and 2 define a lifecycle for project information — from the Employer’s Information Requirements (EIR) through the BIM Execution Plan (BEP) to the final Asset Information Model (AIM). The core obligation is traceability: every piece of information must have a named owner, a defined format, and a revision history.

In practice, that means:

• A written BEP signed off by the appointing party before modelling starts
• A Common Data Environment (CDE) with status workflows (S0 → S1 → S2 → S3 → S4)
• Named information managers on both sides of the appointment
• A container naming convention (the standard provides a schema; we use the BCA Singapore adaptation)

What surprised us

The CDE is not the software. We initially assumed ACC was the CDE. It isn’t — the CDE is the workflow and governance layer you impose on the software. ACC, Autodesk Docs, Viewpoint, and even a SharePoint folder can be a CDE if the status workflow is enforced.

The BEP is the hard part. Writing a BEP before a project starts — when the client hasn’t finished the EIR and the design team hasn’t been appointed — requires pushing back on a procurement process that hasn’t historically asked for it. This is a change management problem more than a technical one.

Part 3 (Asset Management) is for FM, not construction. We initially tried to comply with parts 1–3. Part 3 describes COBie-style data handoff and is only relevant if the client has an Asset Information Requirement. For most of our engagements, parts 1 and 2 are sufficient.

What we actually implemented

We wrote three internal procedures:

1. BEP template (12 pages) — covers project goals, model authoring responsibilities, coordination programme, and CDE configuration.
2. Naming convention — a single spreadsheet that maps the ISO 19650 container name schema to our actual file naming in Revit and ACC.
3. CDE status workflow — a documented sequence from S0 (work in progress) to S4 (archived) with named actions at each gate.

All three are now attached to every new project appointment as annexes to the contract.

The outcome

Our last four projects were delivered under ISO 19650-aligned procedures. Two clients specifically cited the BEP and CDE workflow as reasons for re-appointment. The overhead — maybe 2 days per project — is worth it.