Please complete your details for us to share our training materials
We do not share your information. All responses are kept confidential and used only to improve our training.

This site is an education and upskilling resource focused on the ISO 19650 Series, created to help you understand and apply these international standards.
You might be in education, an academic, a graduate, someone upskilling or moving into a new role, someone refreshing their knowledge, or simply keeping up with developments — this site is for you!
It explains how ISO 19650 supports better information management across construction, asset management, estates, and facilities. It provides clear, practical guidance for learning and applying these standards to improve collaboration and information exchange across the built asset lifecycle.
The ISO 19650 series sets the international standard for managing information across the lifecycle of a built asset. It provides a common framework to improve collaboration, reduce risk, and increase efficiency. Below are the six parts of the series:

ISO Published December 2018
Defines the overall framework, terminology, and principles for information management using BIM across the asset lifecycle.

ISO Published December 2018
Projects: Describes processes and responsibilities for information management during design, construction, and handover phases. CapEx focus.


ISO Published August 2022
Specifies processes based on a Common Data Environment (CDE) to ensure consistency and quality of information before, during, and after exchange between parties.

ISO Published June 2020
Provides guidance for protecting sensitive built asset information through structured security practices and strategies, addressing both physical and digital (cyber) domains and their combined cyber-physical relationship.

ISO Published January 2025
Provides guidance for managing health and safety information across asset lifecycles, focusing on structured capture, sharing, and use of risks, incidents, and treatments to improve safe design, construction, and operation.

ISO Published July 2024
ISO 7817-1:2024 is not part of the ISO 19650 series, but it supports it by defining how to set clear information requirements that ISO 19650 says must be managed.
Its focus is on getting the Level of Information Need right for each stage and requirement. There is no single approach, as schools, bridges, power stations, and highways all need different information.
The standard explains how to define the right level of detail for BIM projects and sets rules for what data, drawings, and documents are needed at each stage.
ISO 7817-1:2024 is based on EN 17412-1:2020 (now withdrawn).


A1. They are series of international standards for managing information over the whole life cycle of a built asset using robust information management (IM) and enabling technologies. There are 6 parts to ISO 19650. As they are international standards, by definition, they are to be used globally. Here is a list of ISO member states.
A. Yes. The ISO 19650 standards are currently under review and being updated to stay aligned with industry needs and best practices.
Updates will include ISO 19650 parts 2 and 3 being combined in to an updated part 2, and part 3 will an implementation guide. There are other changes to terms and diagrams. Sign-up here to get the latest news.
Read the ISO 19650 standards first! Identify your role (appointing, lead appointed, or appointed party). Set the Exchange Information Requirements (EIR), create the BIM Execution Plan (BEP), and configure and use the Common Data Environment (CDE) to align with the standards' requirements. Manage information through production, approval, delivery, and handover into the Asset Information Model. The series has six parts, but this is just an overview.
A4. Part 1: Concepts and principles. Part 2: Delivery phase (project phase). Part 3: Operational phase (including asset management). Part 4: Information Exchange (information quality criteria) Part 5: Security-Minded Approach (cyber-physical security). Part 6: Health and safety.
A5. The series provides an international framework for systematic information management through consistent use of a Common Data Environment (CDE). It covers not only geometric CAD / 'BIM models' (3D, 4D, etc.) but also structured alphanumeric data and documentation to support collaboration.
A6. A single digital environment where all project information is collected, managed, and securely shared. A CDE is a combination of a process and a platform to share. It is not necessarily one software.
A7. OIR (organizational), PIR (project), AIR (asset), and EIR (exchange) requirements define what information is needed at each level.
These all need to be informed by a security strategy, an output from implementing a security-minded approach (ISO 19650-5).
A8. The information container breakdown structure defines how information is organised in the CDE. ISO 19650 does not set out the detailed rules for this, leaving them to national annexes and each project to define and enforce with the Project's Information Standard and the EIR.
The UK National Annex (NA), for example, uses fields such as Project, Originator, Functional Breakdown, Spatial Breakdown, Form, Discipline, and Number (e.g., P01-ABC-FB-SB-DR-A-0001). While this is formally called the information container identification (ID) in the NA for ISO 19650-2, this is commonly known as the 'file naming convention', as historically this is used mainly with naming files.
A9. Yes, the principles can be applied proportionally to projects of any size. They are already being used across the world on single building and small infrastructure projects, right the way up to the largest national-level infrastructure and new city giga projects today!
A10. ISO 19650 does not define specific “BIM roles” in the traditional sense. Instead, information management is embedded as a function within the main parties: the appointing party (client/owner), the lead appointed party (such as a main contractor or lead consultant), and the appointed parties (suppliers, subcontractors).




A11. Key challenges include poor role understanding, incomplete requirements, lack of training, and weak Common Data Environment (CDE) setup. Perhaps the biggest major issue is when ISO 19650 requirements are not embedded in contracts with clear deliverables and a defined RACI (Responsible, Accountable, Consulted, Informed) to set out who does what, when and why (why the information/data is needed - it's criticality).
A12. Yes, and this can be done and is often achieved. It requires re-mapping information container IDs, files, and folders, along with training and cross-checking impacts on contracts and deliverables. Legal, security, data privacy, and Intellectual Property Rights (IPR) impacts must be reviewed, with a clear change roadmap to manage the transition.
A13. Yes, through third-party auditors, such as BSI, who verify organizational and business processes, policies, standards, and supporting governance materials. The use of a Common Data Environment (CDE) is included in scope.
Individual qualifications are also available via training and personal certification.
A14. No single tool / software delivers ISO 19650 compliance. It requires a combination of solutions:
- Authoring and modelling tools to create and update design and asset information (e.g., Revit, Archicad, Civil 3D, Tekla, ArcGIS Pro).
- A Common Data Environments (CDE) to manage, share, and approve information (e.g., Autodesk Construction Cloud, Bentley ProjectWise, Oracle Aconex, Trimble Connect, Asite, Dalux, Viewpoint, Esri ArcGIS GeoBIM).
- Asset and facility management systems to maintain and use information throughout operations, including CAFM platforms and Enterprise Asset Management Systems (EAMS) (e.g., IBM Maximo, Planon, Archibus, FM:Systems, Trimble Manhattan).
Compliance depends on how these tools are configured, aligned and used with the required processes and responsibilities.
A15. No, they cover the full lifecycle including design, construction, handover and operation. Repurposing and decommissioning of built assets should also be considered.
A16. No, BIM is not a single product. It is a process and governance framework, defined in the ISO 19650 Series, that sets out the requirements. Technology helps enable this, but is only one part.
A17. As defined in ISO 19650-1:
BIM is "[the] use of a shared digital representation of a built asset to facilitate design, construction and operation processes to form a reliable basis for decisions."
ASSET - An asset is defined as "item, thing or entity that has potential or actual value to an organization" (from ISO 55000)
A18. No, they apply to all built assets including infrastructure, utilities, and facilities + more! It can also be applied to environmental natural assets and the environmental and there is a link with helping create and maintain connected digital twins.
A19. No, the ISO 19650 Series are not universally mandated by law. However, many countries require their use on public projects (e.g., UK, SE Asia, parts of Europe, Middle East). They also often underpin compliance with other legislation / regulation such as health and safety (e.g., fire safety) and planning regulations, and are typically enforced through commercial contracts.
The ISO 19650 Series further support operations and whole-life facilities and asset management (aligned with the ISO 55000 Series), where their long-term, large-scale application delivers the greatest benefits.
Consider this: The ISO 19650 Series are widely recognised as international best practice for managing digital data and information in the built environment, with clear provenance and proven benefits. The real question is no longer why we should use them, but why we would not.
A20. It reduces risk, improves efficiency, and aligns stakeholders by providing reliable, structured information and accurate digital records to support operation, maintenance, compliance, and lifecycle planning. They see information / data as assets with value.


An Exchange Information Requirements (EIR) document defines what project information is needed, who provides it, and when it must be delivered. It aligns all parties on required data, models, and documents, and how they are shared.
Originally called Employer’s Information Requirements in the now-withdrawn UK standards PAS 1192-2 & 3 (part of the BIM Level 2 framework), the term has been replaced by Exchange Information Requirements under ISO 19650-1 and further detailed in ISO 19650-2 and 19650-3. The new definition reflects a broader, appointment-based view of information management aligned with international standards.
An EIR sets clear expectations between clients and project teams to ensure consistent information management, reduce confusion, and support better decisions. EIRs are typically embedded or cross-referenced in project contract, making information a defined, mandated deliverable. Core elements cover purpose, delivery dates, formats, responsibilities, and quality checks to ensure the right information is delivered at the right time.
Purpose
Define why the information is required and what decisions it supports.
Derived from Organizational (OIR), Asset (AIR), and Project Information Requirements (PIR).
Each purpose links to specific information exchanges at project decision points (for example, design approval, tender, handover).
Information Structure
Specifies how the information is organized and referenced.
Includes schema, classification systems (e.g., Uniclass 2015), and consistent naming conventions.
Must allow interoperability between project systems (e.g., IFC formats, COBie).

Level of Information Need
Defines the granularity and precision of information.
Avoids over-specification and information waste by aligning only to what is required for each purpose.
Read: ISO 7817-1
Information Exchange Dates / Milestones
Specifies when information is to be exchanged.
Tied to information delivery milestones (aligned with key decision points).
Includes submission, review, and acceptance timelines.
Acceptance Criteria
Defines how the information will be checked for compliance.
Criteria should be measurable and, where possible, automated.
Includes syntax rules, metadata accuracy, classification conformity, and data completeness.
Definition of Information
Details what information is needed at each exchange.
Defined through Level of Information Need, which covers:
Geometrical Information (e.g., models, drawings)
Alphanumerical Information (e.g., attributes, schedules, data tables)
Documentation (e.g., reports, certificates, manuals)
Each item specifies content, form, and format.


Roles and Responsibilities
Defines who provides each piece of information and who receives it.
Each EIR is appointment-specific and incorporated into the tender or contract.
Clarifies accountability for information creation, review, approval, and delivery throughout the project lifecycle.
Should reference or align with the project’s RACI matrix to ensure no duplication or omission of responsibilities.
Governance and Protocols
References the Project Information Standard, Information Production Methods and Procedures, and Information Protocol.
Ensures consistent rules for data creation, management, and exchange across the Common Data Environment (CDE).
Presentation Requirements
Specifies how the information should be presented for review.
Covers file structure, visual standards, metadata, and accessibility.
Differentiates between structured (machine-readable) and unstructured (human-readable) information.
Supporting Information
Provides additional detail to help suppliers interpret and meet the EIR.
Includes reference documents, templates, examples, and related standards.
Should not just reproduce standard text but offer project-specific context.
Many countries are implementing the ISO 19650 series. Here are just some examples:

Embedding ISO 19650 clauses into public works contracts. Developing national guidance to support consistent uptake.
France

Major firms are pushing for ISO 19650 compliance to win international bids; national standards groups evaluating annex development.
South Korea

Collecting national case studies and early implementation models to pilot adoption across federal and state projects.
Mexico

Mandated ISO 19650 in all public-sector projects. Has a detailed National Annex for metadata, naming conventions, and classification. Also supported by a national framework.
United Kingdom

Adopted ISO 19650 as AS/NZS ISO versions. Published a joint national guide covering workflow, responsibilities, and implementation practices.
Australia & New Zealand

Issuing national annexes and implementation guidance for infrastructure and public contracts to standardize ISO 19650 usage.
Germany

Cities like Dubai and Abu Dhabi require BIM (aligned with ISO 19650 principles) for large-scale developments.
United Arab Emirates

Working toward SANS versions of ISO 19650. Industry bodies are piloting national frameworks and guidelines.
South Africa

Formalized adoption by producing implementation references and case studies tailored to local projects.
Türkiye

Get your free copy of our ISO 19650 Series Guide. This resource explains key principles and practical steps to help you apply the standard with confidence.
Plus a free guide to certification to ISO 19650-2 (projects)
100% Secure - Privacy Guaranteed

Building Information Modeling (BIM) dimensions is a term used to define how digital building models extend beyond basic 3D geometry. While the meaning up to 3D is generally understood, the specific details if what to include, or not, is not clear.
The risk with BIM 'dimensions' lies in their lack of standardization. While 3D, 4D, and 5D are broadly recognized, dimensions beyond that vary by country, organization, and software vendor.
Each additional 'dimension' integrates new concepts into the model to enhance planning, construction, and operations. However, there are no universally agreed details.
Whilst no single definition exists, typical 'BIM dimensions' are:
3D: Geometry and spatial relationships.
4D: Time and scheduling.
5D: Cost estimation and budgeting.
6D: Sustainability and energy performance.
7D: Facility management and operations.
8D: Safety and risk management.
9D: Lean construction and optimization.
10D... 11D... 12D... there can be more...!
This inconsistency creates problems such as unclear contracts, incompatible data, mismatched training, and models that cannot be used effectively across the lifecycle.
Without agreed global definitions, higher BIM dimensions remain useful as concepts but unreliable as contractual or technical benchmarks.
LoD (Level of Detail / Definition / Development), LoI (Level of Information), and LoX (generic “Level of Something”) have been common BIM terms.
They try to describe how much detail or information a model has or indeed just what type of information should be shared in the first place. As this will vary for different stages.
The most common terms are Detail / Development / Definition (LoD). But, these are not universally defined.
-----------
EXAMPLE
One example of where there is a reference for Level of Development (LoD) is >here. This is a good source to use in the right circumstances, or use to start the conversation about how to define what Level of Information Need is required.
-----------
Level of Information Need solves this. It defines exactly what information is required and how much detail for each stage, covering geometry, alphanumeric data, and documents. It is better than BIM dimensions, which are not universally defined and cannot ensure consistent delivery.
Level of Information Need is broader. It is based on real requirements and applies to all information types: data, documents, models, CAD, reports, and more.
Level of Information Need is broader and based on actual information requirements, covering all information types: tabulated data (alphanumeric) / documents / geometric models / CAD / reports + other kinds of information, as needed.
The standard ISOO 7817-1:2024 - Building information modelling — Level of information need - Part 1: Concepts and principles, can help us. It explores how to specify Level of Information Need, by starting with the basics principles that should be defined for 'lean' information management:
(Note - The same content was published as a European standard: EN 17412‑1:2020 (now withdrawn), before it was published as the current international standard: ISO 7817-1:2024).
Under development: ISO 7817-2 - Building information modelling — Level of information need - Part 2: Guidance for application.

Sign up for our free guide on the ISO 19650 Series to stay updated with the latest standards, guidance, and practical insights.
You will also get an extra guide on certification to ISO 19650-2 (projects)
FREE Videos and Reporst For Construction Professionals, Property Managers, Asset Management Teams, and Industry Stakeholders...

Sign-up for access to our free, simple explainer videos
The Appointing Party is the client or project owner. They set the overall information requirements for the project under ISO 19650. Their role is to define what information is needed, control project objectives, and appoint others to deliver the work. They also establish the Common Data Environment (CDE) or ensure one is in place.
Examples of an Appointing Parties: client organisation, asset owner, developer company, operator company, public authority.
The Lead Appointed Party is the main organization directly contracted by the Appointing Party, often the main contractor, architect, or lead consultant. They manage and coordinate all information delivery across the project team. They are responsible for managing how the CDE is used by their appointed supply chain.
Examples of Lead Appointing Parties: architectural practice, construction contractor, engineering consultancy, project management firm.
The Appointed Party is any subcontractor, consultant, or supplier appointed by the Lead Appointed Party. They provide specific information related to their scope of work. They must upload and share their information correctly through the CDE as directed.
Examples of Appointed Parties: structural engineering firm, civil engineering firm, mechanical engineering firm, electrical engineering firm, public health engineering firm, surveying practice, landscape architecture practice, interior design practice, specialist subcontractor, manufacturing company, BIM consultancy.
Other Parties are groups that support or oversee a project without being part of the three main roles.
Examples of Other Parties include regulators, insurers, financiers, auditors, certifiers, legal advisors, technology providers, health and safety officers, sustainability consultants, commissioning agents, and asset valuers. These are only examples, not a complete list.
Sign up for our free guide on the ISO 19650 Series to stay updated with the latest standards, guidance, and practical insights.
You will also get an extra guide on certification to ISO 19650-2 (projects)
WHY KNOW THESE TERMS?
These terms are not part of the ISO 19650 Series, but they can provide a shared context for defining information needs, roles, and responsibilities, while keeping the purpose of information clear to guide decisions on cost, value, and performance which help shape the information requirements.
Many other terms and jargon exist across all sectors, but these are just a small examples from the built environment that can help build a common language with stakeholders, support conversations, and improve collaboration.
In short, they can help us collectively understand and answer: "Why do we need that specific data / information deliverable? Who is it for and for what purpose? When will they need it and what are the best schemas/formats/forms to share and use the information in?"
iso19650.org is an independent information resource maintained by professionals from across the world working in digital construction, digital engineering and information management. The site is managed by a small team of digital and BIM consultants, standards specialists, and educators who apply ISO 19650 principles in real projects.
Our goal is to make the ISO 19650 framework easier to understand and use across all domains where it can add value. All content is written and reviewed by practitioners experienced in information management under the ISO 19650 series.
iso19650.org is not affiliated with ISO. It exists to clarify, not replace, the official standards and national frameworks.

Sign up for our guide on the ISO 19650 Series to stay updated with the latest standards, guidance, and practical insights.
You will also get an extra guide on certification to ISO 19650-2 (projects)
Disclaimer
iso19650.org is an independent platform, not affiliated with or endorsed by the International Organization for Standardization (ISO), any national standards body, BuildingSMART International, ISO 19650 adoption initiatives, or software vendors.
iso19650.org © 2025. All Rights Reserved.