If you work in architecture, engineering or construction, you have probably seen "ISO 19650 compliant" in a tender, a job advert or a client brief. For newcomers the standard can look like a wall of acronyms. In reality, its core idea is simple: everyone on a project should know what information is needed, who produces it, when it is due and where it lives. This beginner guide breaks ISO 19650 into plain English.
What Is ISO 19650?
ISO 19650 is an international series of standards for managing information over the whole life of a built asset using building information modelling (BIM). The full title of Part 1 is "Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM)". It covers everything from planning and design through construction, operation, maintenance and eventual end of life, and it is meant to scale from a small extension to a major infrastructure programme.
The series grew out of British practice. Parts 1 and 2 are based on the UK documents BS 1192 and PAS 1192-2, and they were first published in December 2018. Since then the family has grown to six parts. According to ISO, Part 1 is marked for revision, so expect updated editions in the coming years - but the core concepts below are stable.
An important point for beginners: ISO 19650 is not about any particular software. It does not tell you to use Revit, ArchiCAD or any other tool. It describes processes for specifying, producing, checking and sharing information, whatever applications your team prefers.
The Six Parts at a Glance
- Part 1 - Concepts and principles: the vocabulary and big-picture framework.
- Part 2 - Delivery phase of assets: how information is managed during design and construction. This is the part most project teams deal with day to day.
- Part 3 - Operational phase of assets: information management once the building or asset is in use.
- Part 4 - Information exchange: how and when information is exchanged, and how its quality is checked.
- Part 5 - Security-minded approach: balancing open collaboration with protecting sensitive information.
- Part 6 - Health and safety information: managing health and safety information across the project and asset life cycle.
Most introductions focus on Parts 1 and 2, and that is the right place to start. Owners and operators of complex assets will eventually need Parts 3 to 6 too.
Key Roles and Information Requirements
ISO 19650 talks about parties rather than job titles. The appointing party is the organisation receiving the information - usually the client or asset owner. A lead appointed party receives an appointment directly from the client and coordinates its own team, while appointed parties are the organisations that produce information under that lead.
The heart of the standard is a cascade of information requirements, defined before delivery starts:
- OIR (Organisational Information Requirements): what the organisation needs to know to meet its business goals.
- AIR (Asset Information Requirements): the information needed to operate and maintain the asset.
- PIR (Project Information Requirements): the information the client needs to make decisions at key project stages.
- EIR (Exchange Information Requirements): the specific information each appointed party must hand over. This replaces the older term "employer's information requirements".
On the delivery side, teams respond with a BIM Execution Plan (BEP) explaining how they will meet those requirements, and with delivery plans (task and master information delivery plans, often shortened to TIDP and MIDP) that list what will be produced and when. During the project the information builds up into the Project Information Model (PIM); the information handed over for operations becomes part of the Asset Information Model (AIM).
The Common Data Environment (CDE)
The common data environment is the agreed source of information for a project - typically a cloud platform or document management system with defined workflows. ISO 19650 describes information moving through four states:
- Work in progress: being developed by a single task team and not yet visible to others.
- Shared: checked and released so other disciplines can coordinate against it.
- Published: approved for its intended use, such as construction or handover.
- Archived: kept as a historical record of what was issued and when.
The point of these states is control. Nobody should build from a drawing that has not been checked and approved, and everybody should be able to see the history of each container of information.
Practical Tips for Getting Started
- Learn the vocabulary first. Most confusion comes from acronyms. Keep a one-page glossary of OIR, AIR, PIR, EIR, BEP, CDE, PIM and AIM on your desk.
- Read the client's EIR carefully. It tells you exactly what information you owe, in what format and at which stage.
- Agree naming and status conventions early. Consistent file naming and status codes make the CDE workflow far easier to follow.
- Set up your authoring templates to match. In Revit, for example, shared parameters and well-organised sheets make deliverables easier to check. Tools covered in our DiRoots SheetLink review can help manage parameter data in bulk.
- Think about handover from day one. Information that operators will need should be planned in, not scrambled together at the end.
Conclusion
ISO 19650 can feel heavy at first, but its logic is straightforward: define what information is needed, plan who will deliver it, manage it through a controlled common data environment and hand over something useful for the life of the asset. Start with Parts 1 and 2, master the core acronyms, and you will quickly find that the standard is less about bureaucracy and more about avoiding the costly confusion every project team has experienced at least once.