ISO 19650 — the standard that runs BIM information work
TL;DR — read this first
ISO 19650 is the current, international standard for managing information across the built-asset life cycle. It replaces the UK BIM Level 2 playbook and the PAS 1192 series as the reference for how BIM information is specified, exchanged and delivered. Two parts cover what most projects touch: fundamentals (19650-1) and construction & handover (19650-2).
From "BIM Levels" to information requirements
Between 2011 and 2019 the UK BIM programme (BIM Level 1/2, PAS 1192, the 2016 UK BIM Framework and the NBS/BiDC guidance) drove the first large-scale adoption of BIM in Europe. That framework worked — but it was one country’s procurement language, written for a specific contract model.
ISO 19650 (2018) did something different: it took the concepts that made BIM Level 2 practical — the Common Data Environment, the information workflow, the producer / consumer roles — and turned them into a neutral, international standard. The UK BIM Level 2 playbook was formally superseded. ISO 19650 is now the reference in public-procurement specifications across Europe and the GCC, and the baseline for IFC-based openBIM tooling.
When a document, software vendor or blog still says "BIM Level 2 compliance," ask: are you describing the historical procurement framework, or the information requirements that ISO 19650 now standardises? Those are different answers.
The working vocabulary (what you will actually meet in a contract)
Information requirements. The client states what information a project needs, for which purpose, at which point in the life cycle, and at what level of definition. This is the contract spine.
OIR — Organising Information Requirements. The client’s overall requirements for the whole asset: the asset, its users, the life cycle stages, the data-management standard (ISO 19650-1/-2), and the reference file structure ("reference information model").
EIR — Exchange Information Requirements. For each information deliverable: who needs it, when, what purpose it serves, what information content it must carry (geometric + alphanumeric + documentation), which file format (typically IFC or COBie), and how it will be validated.
PIR — Project Information Requirements. The project team’s internal decomposition of the OIR/EIR into a workable delivery plan: who produces what, in which sequence, against which information model.
Common Data Environment (CDE). A single, agreed source for project information. ISO 19650-1 defines the CDE states a project uses to track information maturity: work-in-progress, shared, published, and archived. A file in the CDE is not "done" until it is published.
Information models and deliverables. The agreed structure of information (the "information model") and the specific deliverable produced from it (an IFC file, a document set, a COBie spreadsheet). Deliverables are validated against the EIR before they are published.
What the two parts actually cover
| ISO 19650-1 | ISO 19650-2 | |
|---|---|---|
| Audience | All built-asset life cycle | Construction, handover & asset management |
| Core content | Fundamental concepts: CDE, information workflow, roles & responsibilities, information requirements vocabulary | Deliverable information requirements: OIR → EIR → PIR, information delivery, asset information model, asset handover |
| What changes day-to-day | How a CDE is governed; how teams communicate information needs | What a contractor / designer actually delivers, in which format, with which metadata |
What this means in practice
- Read the EIR before you bid. The EIR is where the real scope lives — not in a general "BIM required" clause. If the EIR is missing or vague, that is a commercial risk, not just a technical one.
- The CDE is the contract’s nervous system. Agree on state transitions (when a file moves from
sharedtopublished) and on the validation gate before publication. - ISO 19650-2 is where deliverables live. When a buyer asks "what do you deliver?", the answer should be mapped to the information-deliverable structure in 19650-2, not to a software feature list.
- LOIN is the companion standard. ISO 19650 specifies what information is needed; ISO 7817-1 (LOIN) specifies how detailed it must be. See LOIN — Level of Information Need.
Related
- LOIN — Level of Information Need (ISO 7817-1) — how detail and extent of information are specified
- BIM to FAB — from approved model to factory — downstream: where the information becomes a physical asset
- BIM × AI — the operating system for AEC data — where AI fits into an ISO 19650 information workflow
Leave a Reply