Skip to content
KitWren
IntermediateFree BIM course about 22 min

ISO 19650 and information management

ISO 19650 is the international framework for managing information on BIM projects. Learn its key terms and workflow so you can follow it on real projects.

In this lesson you will

  • Explain the information requirements hierarchy
  • Name the parties and their roles
  • Describe the CDE workflow states
  • Understand information container naming

What ISO 19650 covers

ISO 19650 (parts 1–6) sets out how to manage information over an asset's life: the concepts (part 1), delivery during design and construction (part 2), operations (part 3), information exchange (part 4), security (part 5) and health and safety (part 6). Many countries publish national annexes with local details such as naming. It doesn't prescribe software.

Information requirements

Responses to the EIR are written in the BIM execution plan (BEP), and deliverables are scheduled in the Master Information Delivery Plan (MIDP) and task plans (TIDPs).

RequirementSet byDescribes
OIR — Organisational Information RequirementsThe client organisationWhat information the organisation needs for its goals
AIR — Asset Information RequirementsClientInformation needed to operate the asset
PIR — Project Information RequirementsClientInformation needed to make project decisions
EIR — Exchange Information RequirementsAppointing partyWhat each appointed party must deliver, when and how

Parties

The appointing party (usually the client) appoints a lead appointed party (e.g. the main contractor or lead designer), who appoints appointed parties (consultants, subcontractors). Delivery teams are made up of task teams.

The common data environment

A CDE is the agreed source of information, with a workflow of states:

  • Work in progress (WIP) — visible to the task team only.
  • Shared — checked and shared with other teams for coordination.
  • Published — authorised for use, e.g. for construction.
  • Archived — the record of everything published.

Each container carries status and revision metadata; moving between states requires checking and approval.

A cycle: brief and requirements, then discipline models, a federated model, coordination and clash review, documentation, construction, and a handover model for operations.RequirementsDiscipline modelsFederated modelClash reviewDocumentationConstructionHandover modelshared, structuredinformation
Figure: Information flows through a BIM project. Original KitWren diagram.

Naming

National annexes define container naming with fields such as Project–Originator–Volume/System–Level/Location–Type–Role–Number, e.g. KW23-ARC-ZZ-01-M3-A-0001 for an architectural model of level 01. Consistent naming lets thousands of files be found and filtered.

Exercise

Name and route a model

  1. Invent a project code and write the file name for your architectural level 1 model using the field pattern above.
  2. Describe its journey through WIP, Shared, Published and Archived, and who checks it at each step.
  3. Write three example EIR requirements a client might set for it.

You should end up with: A practical understanding of containers, states and requirements.

Checklist

0 of 4 checked · saved on this device

Lesson quiz

1 / 5

Which document states what each appointed party must deliver?

Finished this lesson?

Taking the quiz marks it complete too. Your course page picks up where you stopped.

Free KitWren tools that help

Free, independent learning material written for KitWren. We never provide software downloads, licence keys or cracks — use the official sources.