I was recently reviewing ISO 29481 to see what could be useful for a BIM Information Manager. In the sea of ISO 19650 parts and various national annexes, ISO 29481—the Information Delivery Manual (IDM)—often sits in the background, yet it holds the keys to how we actually define the “what, who, and when” of digital exchange.
However, looking at these standards in detail often brings up a familiar feeling: the theory is brilliant, but the implementation feels like a tug-of-war.
What is ISO 29481?
At its core, the IDM is designed to bridge the gap between business processes and the technical data at the heart of BIM. It is broken into three distinct parts:
- Part 1: Methodology and Format – This is the “Why” and “Who.” it provides a way to document a business process (like maintenance or cost estimation) and identify exactly what information is required to make that process work.
- Part 2: Interaction Framework – This is the “When.” It defines how different parties coordinate and communicate during an exchange. It maps out the flow of messages to ensure data doesn’t just arrive, but arrives at the right time in the right hands.
- Part 3: Data Schema – This is the “How.” It is a technical layer (idmXML) designed to make the requirements from Part 1 machine-readable. It’s the “engine room” that should allow software to automatically understand and check our project requirements.
The Standardization Paradox
The frustration many of us feel is that while these standards look great on paper, the industry seems perpetually caught between them. We all agree that we should follow a standard, but we can rarely agree on which one.
Too often, it feels like every organization wants everyone else to follow their specific version of a standard. We end up with “Standardization Noise,” where the effort required to navigate the overlap between ISO 19650, ISO 29481, and various local requirements starts to outweigh the benefits of the data itself.
The Problem of “Closed” Software
This brings us to a major bottleneck: software development. ISO 29481 Part 3 was written to help developers create open, interoperable checking tools. Yet, many software providers continue to build “closed” ecosystems.
Instead of building tools that natively read open standards like idmXML or the newer IDS (Information Delivery Specification), many platforms remain “black boxes.” This lack of open-source spirit in AEC tech means that Information Managers are often forced to use manual workarounds to move data between “standardized” models and proprietary management tools.
Finding a Practical Path Forward
So, where does that leave the practicing Information Manager?
While the academic debate over Part 3 and open-source schemas continues, we still have projects to deliver today. Personally, I will keep developing my processes around COBie. Despite the criticisms, COBie remains a Model View Definition (MVD) that actually works on live projects. It provides a “least common denominator” that most stakeholders can understand and most software can—eventually—export.
In an industry still arguing over which manual to read, sticking to a practical, testable output like COBie allows us to maintain “no wiggle room” on data quality while we wait for the rest of the standards landscape to catch up.
Coulter BIM Information Management 
Leave a comment