Beyond the Model: Unpacking the ISO/DIS 19650-1:2026 Draft

The foundations of how we manage built environment data are shifting. The recently released ISO/DIS 19650-1:2026 draft is not just a “version 2.0″—it is a fundamental restructuring of the “Concepts and Principles” that govern our industry. It represents a subtle but profound shift toward “Information Management” (IM) as a permanent, lifecycle-centric discipline.

Section 1: Scope & Digital Integration

The 2026 draft acknowledges that “BIM” is no longer a standalone island. The scope now explicitly includes Digital Twins and Smart Assets. It moves the goalposts from simply “handing over a model” to “maintaining a digital thread.”

Expansion: It emphasizes that IM applies to all “interventions”—whether that is a £100m new build or a £50k boiler replacement. The scope is now about the continuity of data across these interventions.

Section 2: Normative References & The ISO 7817 Link

A major change is the “hard-wiring” of ISO 7817-1 (Level of Information Need).

Expansion: In the 2018 version, “Level of Detail” (LOD) was a loose concept. The draft now mandates a framework where you must define the Purpose, Milestone, and Actor for every piece of data. You can’t just say “I want LOD 300”; you must define why you need it and who is producing it according to the ISO 7817 schema.

Section 3: Terms, Definitions, and “The Death of BIM”

This is the most controversial section for industry veterans.

From BIM to IM: The draft argues that “BIM” has become a “siloed” term for 3D modeling. By shifting to Information Management, the standard now covers COBie, sensor data, PDF manuals, and Excel schedules under one umbrella.
IPP & IPR: By changing the BIM Execution Plan to the Information Production Plan (IPP), the standard removes the “model-only” bias. It forces lead contractors to plan how all information—including non-graphical data—is produced.

Section 4: Lifecycle Information Management

This section introduces the “Intervention” mindset.

Expansion: Instead of thinking of a project as a start-to-finish event, the draft views it as an “intervention” into an existing Asset Information Model (AIM).
Unified Model: It suggests that the distinction between PIM and AIM is academic. In practice, there is one Lifecycle Information Model that exists in a state of constant update. This is designed to solve the “Handover Gap” where data is lost when a project finishes.

Section 5: The Information Management Function

The draft moves away from “BIM Manager” as a person and toward IM as a Function.

The IM Team: It formalizes the Information Management Team, which includes representatives from the Client (Appointing Party), the Lead Contractor, and even key Task Teams.
Expansion: It mandates that the Appointing Party must provide a “Project CDE” and “Asset CDE” strategy upfront, rather than leaving it to the contractor to figure out mid-tender.

Section 6: Information Requirements (The Golden Thread)

This section is heavily influenced by post-Grenfell legislation in the UK and similar global safety standards.

Expansion: The “Golden Thread” is woven into the PIR (Project Information Requirements). It specifies that safety-critical information must be flagged at the PIR stage so it can be tracked through the entire lifecycle without being “buried” in a CAD file.

Section 7: The Unified 9-Step Process

This is the “engine room” of the draft. It replaces the old 8-step delivery process with a loop that applies to both construction and maintenance.

Assessment: Defining the need for information.
Invitation: Setting the requirements (IPR).
Response: The prospective lead party submits their IPP.
Appointment: Formalizing the delivery plan.
Mobilization: Testing the CDE and software (vibe coding/automation testing happens here).
Collaborative Production: The actual “work.”
Delivery: Submitting the information container.
Acceptance: The Client formally signs off the data.
Review: Capturing lessons learned for the next “intervention.”

Section 8: Information Production & CDE Metadata

This focuses on data-centricity and interoperability.

Expansion: The draft moves toward Machine-Readable Metadata. It suggests that CDEs should not just rely on human-entered fields. It pushes for “Data Exchange” (API-based) rather than just “File Exchange.” This section sets the groundwork for automated compliance checking.

Section 9: Quality and Governance (Validation vs. Verification)

The draft provides a much clearer distinction here:

Automated Validation: Is the file named correctly? Does the IFC schema match? (Tasks for automated scripts).
Human Verification: Does the model actually represent what was built on-site? This requires a physical check or a laser scan comparison.

Section 10: Information Management Maturity

The final section describes “Maturity” not as a level (like the old Level 2), but as a State of Integration.

Expansion: High-maturity organizations are those that have “integrated IM” into their business systems (ERP, Finance, HR), meaning information about a building’s cost is pulled directly from the Information Model, not entered twice into a separate spreadsheet.

Real-World Application: The Contractor’s “Thread”

While the ISO 19650-1 draft provides the theory, the practical execution of the Golden Thread is where the value is realized on-site. For a contractor, the Golden Thread isn’t about justifying the design—it is about providing the unbroken evidence of installation.

Managing “Passive” Assets in Autodesk Build

We often think of “Assets” as maintainable items like pumps or boilers that end up in a COBie sheet. However, the Golden Thread demands that we track non-maintainable assets—like fire-rated partitions—with equal intensity.

In a platform like Autodesk Build, this means:

The Skeleton: Pulling unique Revit IDs into the Assets module as placeholders.
The Evidence: Linking photos of internal fire-stopping and “closure” stamps to specific asset profiles before walls are plastered.
The Granularity: Using Parent/Child hierarchies to manage composite walls. If an Architect models a cladding panel and a fire lining as one element, we can split them into sub-assets to verify the safety-critical lining independently of the aesthetic finish.

By shifting our focus from “handing over a model” to “managing a database of verified assets,” we align our daily site workflows with the new ISO 19650 principles. We move away from “junk reps” of manual data entry and toward a high-tension, high-quality digital record that keeps people safe.

Coulter BIM Information Management