What is ISO 19650 and why are the most advanced organizations already working under this standard?

There is an observable gap between organizations that say they do BIM and those that do BIM in a way that consistently produces verifiable results. That gap is rarely technological. It is not a gap in tools, software, or modeling capability. It is a gap in information governance.

ISO 19650 is the international standard that defines exactly that governance. And the organizations that have crossed the gap — those that deliver complex projects with fewer interferences, less rework, and digital assets that actually serve to operate the building — are, for the most part, organizations that have adopted ISO 19650 not as a requirement but as a way of working.

This article explains what the standard is, why it matters beyond regulatory compliance, and what difference it makes in the practice of a complex project.

What does ISO 19650 regulate?

The short answer: ISO 19650 does not regulate BIM modeling. It regulates how information is managed in construction projects.

This distinction is fundamental. The standard does not specify what software to use. It does not define what modeling tools are acceptable. It does not define how models should be built. All of that is deliberately outside its scope.

What it does define with precision is:

• How information requirements are established from the start of a project
• How delivery teams respond to and plan the production of that information
• How the environment where information flows between participants must be structured
• With what maturity states each piece of information must progress before being used
• What must happen with information when the construction project ends and the asset enters operation

The standard is currently organized in six parts:

ISO 19650-1 establishes the concepts and principles. It is the conceptual framework that defines terms, relationships, and the mental model of the system.

ISO 19650-2 defines the requirements for the asset delivery phase: design and construction. This is the most relevant part for most projects in execution.

ISO 19650-3 extends the principles to the asset's operational phase, when the building or infrastructure is already in use and requires maintenance and management.

ISO 19650-4 addresses information management: exchange, flow, and delivery.

ISO 19650-5 deals with information security, particularly relevant for critical infrastructure assets.

ISO 19650-6 covers the health and verification of information management processes.

For a data center, hospital, or industrial plant project, the combination of ISO 19650-1 and ISO 19650-2 provides the complete framework for information management during design and construction.

The requirements hierarchy: from organization to project

One of the most important concepts in ISO 19650 — and one of the least understood — is the information requirements hierarchy. The standard establishes that a project's information does not arise from nowhere: it is derived from organizational and asset needs that exist before the project.

This hierarchy has four levels:

OIR — Organizational Information Requirements

OIR represents the information needs at the strategic level of the owning organization. They answer a business question, not a technical one: what information does our organization need to make strategic decisions about our asset portfolio?

For a company that operates multiple industrial facilities, the OIR might specify the need for standardized information from all assets to feed a centralized maintenance management system. This organizational requirement will determine, in cascade, what information must be produced in each project.

AIR — Asset Information Requirements

AIR translates OIR into specific requirements for each physical asset. For a data center, the AIR would specify what data must be available about each cooling system, each UPS, each electrical panel — because the operator needs that information to manage the asset throughout its useful life.

The critical relationship is: AIR → EIR → AIM. The AIR establishes what information the operator needs. The EIR communicates that requirement to the project delivery team. The AIM (Asset Information Model) is the result the team delivers at the end.

EIR — Employer Information Requirements

The EIR is the most important contractual document in the chain. It is the document the owner or client issues at project inception to communicate information requirements to the delivery team.

A well-developed EIR specifies:

• What information must be produced for each discipline and system
• At what level of detail (LOD/LOI — Level of Detail / Level of Information)
• In what format and classification standard
• With what file nomenclature
• At what project milestones (information delivery milestones)
• On what CDE platform the information will be managed

Without an EIR, the delivery team produces information according to its own interpretation of what the client needs. The frequent result: information that meets the vendor's standards but not the owner's.

BEP — BIM Execution Plan

The BEP is the delivery team's response to the EIR. It is the document where the design and construction team declares how it will produce the required information, with what tools, under what processes, and under what responsibilities.

A complete BEP includes:

• A description of how each EIR requirement will be met
• The MIDP (Master Information Delivery Plan), consolidating the information delivery plans of all teams
• The TIDP (Task Information Delivery Plans) for each discipline or contractor team
• The definition of the CDE structure and approval workflows
• Information management roles and responsibilities
• File nomenclature and CDE folder structure

The BEP transforms EIR requirements into an executable plan. Without it, project information organization depends on the practices of each individual team.

The CDE: the architecture of information flow

The Common Data Environment (CDE) is the infrastructure piece that makes the ISO 19650 framework operational. The standard defines it as the agreed approach to sharing information between project participants, implemented in one or more software platforms.

What distinguishes a CDE from a shared folder are the information states. According to ISO 19650, every piece of information exists in one of four states:

| State | Operational meaning | |-------|---------------------| | Work in Progress (WIP) | Under development. Only the producing team has access. Cannot be referenced as current information by other teams. | | Shared | Available for review or reference by designated teams. Formally distributed but not approved. | | Published | Approved for project use. The version that can be used to make decisions, build, or fabricate. | | Archived | Historical or superseded. Not current but preserved for traceability and audit. |

This state system seems simple but has deep consequences. In a project with a properly implemented CDE, nobody can build using a WIP or Shared version. The Published version is the only one that counts. And when a Published version is replaced, the previous one moves to Archived — preserved, not deleted.

The preservation of archived versions is what makes it possible to answer, years later, what information was used to make a specific decision. Without that preservation, traceability is impossible.

PIM and AIM: asset continuity

One of the most important ISO 19650 concepts for asset owners is the distinction between the Project Information Model (PIM) and the Asset Information Model (AIM).

The PIM is the set of information produced during the design and construction project. It is the information the delivery team generates and manages. It includes BIM models, drawings, specifications, interference records, and field reports.

The AIM is the information delivered to the owner when the asset enters operation. It is not a copy of the PIM. It is a selection, structuring, and complementation of PIM information to be useful during the operational phase: what systems exist, where they are, what their technical specifications are, what their maintenance requirements are.

The distinction matters because many projects produce an excellent PIM but have no defined process for converting it into a useful AIM. The result: the owner receives the "as-built BIM model" but cannot use it to manage the building because the information is not structured for that function.

ISO 19650-3 establishes requirements for the AIM and for information management during the operational phase. Applying it from project inception — designing the AIM before the PIM — is the practice that distinguishes the most mature organizations.

Why advanced organizations adopt it without being required to

In markets where ISO 19650 is not a mandatory contractual requirement — as is the case in most of Mexico currently — organizations that voluntarily adopt it do so for concrete reasons, not philosophy:

Reason 1: It reduces coordination costs

A project with a well-implemented EIR, BEP, and CDE produces information once, in the right format, with the correct approval. Without that framework, information is produced multiple times in different formats, redistributed via email with versions that get confused, and requires reconciliation meetings that consume time.

Reason 2: It eliminates working with wrong versions

The problem of "building with the wrong drawing" has a real and measurable cost. A CDE with information states makes this problem structurally impossible: if a drawing is not in Published state, it is not the approved version for construction.

Reason 3: It protects in contractual disputes

When disputes arise — about changes, about responsibilities, about what information was available when a decision was made — the organization with complete information traceability has a radically better contractual position than the one that lacks it. The CDE is an audit record that can be used as evidence.

Reason 4: The digital asset has value for operations

Organizations that operate multiple assets — data centers, hospital networks, industrial portfolios — are learning that structured asset information has economic value during decades. Managing predictive maintenance, planning expansions, or responding to technical emergencies is significantly more efficient with a well-structured AIM than without one.

The most common implementation errors

ISO 19650 adoption fails with predictable frequency. These are the three most common errors:

Error 1: Implementing the CDE without the BEP

The CDE is the tool. The BEP is the rules. A document management platform without rules about who can publish what, under what approval workflow, and with what nomenclature, is a shared folder with a better interface. The BEP is what converts the tool into a governed system.

Error 2: Writing the EIR at the end of the project

The EIR must exist before the design team starts producing information. Writing it late — or even in advanced design stages — turns the EIR into a retrospective documentation exercise, not a governance instrument. The information was already produced at the vendor's convenience, not at the owner's requirement.

Error 3: Treating ISO 19650 as an IT project

Implementing ISO 19650 is not installing a software platform. It is a change in the working processes of the human teams that participate in the project. The biggest challenge of implementation is not technical — it is habit change. Teams accustomed to sending drawings by email need to adopt new workflows. Without training and follow-up, the CDE becomes an underutilized storage platform.

Practical implementation: where to start

For an organization wanting to begin ISO 19650 implementation, the correct sequence is:

1. Assessment: Evaluate the current state of information management. Identify gaps against the standard. This produces a realistic roadmap.

2. EIR first: If you are an asset owner, the first concrete deliverable is the EIR for your next project. Not the CDE, not the vendor's BEP — the EIR, which is your document as owner.

3. CDE with minimum viable configuration: Implementing the CDE does not mean configuring all functions from day one. It means configuring the information states, the main approval workflows, and file nomenclature. The rest can evolve.

4. BEP aligned with the EIR: Require the delivery team to produce a BEP that responds specifically to each point in the EIR. Not a generic BEP — a project-specific BEP.

5. Compliance monitoring: Implement periodic BEP compliance reviews during project execution. The governance framework only works if someone verifies that it is being followed.

Conclusion

ISO 19650 is not a wall certification. It is not a marketing differentiator to mention in a presentation. It is the operating system of information management in high-complexity projects.

Organizations that adopt it voluntarily do so because it produces projects with fewer interferences, digital assets with real value, and a protected contractual position. The learning curve exists, but organizations that have overcome it do not consider going back.

The high-complexity project market is moving toward structured information governance. Clients that require an EIR before design begins, that require a BEP as a contract condition, and that specify CDE in their tender documents are increasingly common. The relevant question is not whether ISO 19650 will become a market standard — it is when. Organizations that start now arrive with an advantage.

---

Is your organization evaluating ISO 19650 implementation in its projects? At SORA we accompany information management framework implementation from EIR to AIM. Request a technical assessment.