ISO 19650

The ISO 19650 document cascade — clear & free to create

From strategy to delivery, every ISO 19650 information document builds on the previous one. Here is each document type explained in plain language — and generated with a free, guided tool. Then check your IFC model against the requirements (IDS).

Generate documents →
Free & guided — plain language, not acronym soup
ISO 19650-compliant — by Springer author Jakob Hirn
Requirement → checkable IDS — validate against your IFC model
Incl. operations/FM — ISO 41001/55001, Uniclass codes, COBie

Procure BIM and you first drown in acronyms: OIR, AIR, PIR, EIR, BEP, LOIN, TIDP, MIDP. ISO 19650 arranges these documents into a logical cascade — they define which information is delivered when, by whom and to what level of detail. That is what makes BIM controllable and its economics measurable.

The information cascade at a glance

Three levels build on each other — the organisation's strategy, the requirements for the finished asset in operation, and the project-specific requirements with their delivery plans:

OIROrganisational Information RequirementsWhat the organisation strategically needs from its built-asset data — the north star. → Guide AIRAsset Information RequirementsWhich data a finished building or asset needs in operation (FM). → Guide PIRProject Information RequirementsWhat a specific project needs at its decision gates. → Guide EIRExchange Information RequirementsThe client's "order": what is delivered, when and how. → Guide BEPBIM Execution PlanThe delivery team's answer: how it meets the requirements. → Guide LOINLevel of Information NeedHow detailed each element must be — geometry (LOG) & information (LOI). → Guide TIDPTask Information Delivery PlanA single team's delivery plan: who delivers what, by when. → Guide MIDPMaster Information Delivery PlanThe overall delivery plan across all teams — merged from the TIDPs. → Guide
ISO 19650 scope matters: OIR and AIR are organisation- and asset-level and apply across projects. PIR, EIR, BEP, LOIN, TIDP and MIDP are project-level. Keeping these scopes apart isn't bureaucracy — it stops strategy and project detail from being muddled.

Why the order matters

The cascade is requirement inheritance: the OIR shapes AIR and PIR. From the PIR and project context comes the client's EIR, whose per-element detail is set in the LOIN. The delivery team answers with the BEP and plans delivery through TIDP (per team) and MIDP (overall). Skip a step and the next one loses its basis — the most common cause of costly change requests.

Guided, not a blank page

Instead of editing a Word template, you answer targeted questions per document type. Requirements flow automatically from upstream to downstream documents (e.g. from the EIR into the BEP). The result: a consistent, ISO 19650-compliant document as DOCX/PDF.

FAQ

What is the difference between EIR and AIA?

Both mean the client's information requirements. EIR (Exchange Information Requirements) is the ISO 19650 term; "AIA" is the German-language equivalent. Same document.

Do I need every document?

No. At minimum the EIR (requirement) and BEP (response) per project; the LOIN sets the level of detail. OIR/AIR pay off once an organisation thinks about BIM strategically and across operation.

Is this ISO 19650 compliant?

Yes. Scopes and terms follow ISO 19650 (parts 1–3) strictly — that normative rigour, without over-bureaucracy, is the whole point.