ISO 29481-2: Building Information Models — Part 2: Framework for Collaboration

1. The Role of ISO 29481-2 in BIM Ecosystems

ISO 29481-2 establishes a comprehensive framework for managing information exchange throughout the lifecycle of a building or infrastructure project. While Part 1 of the standard focuses on the methodology and format of the information delivery manual (IDM), Part 2 provides the overarching conceptual framework that defines how IDMs relate to each other, how exchange requirements are specified, and how model view definitions (MVDs) map onto data schemas. This framework is the backbone of openBIM, ensuring that project stakeholders — architects, structural engineers, MEP engineers, contractors, and facility managers — can exchange meaningful information without loss or ambiguity.

The standard is built on three core components: the Information Delivery Manual (IDM) which describes business processes and the information needed at each step; the Exchange Requirements (ER) which specify precisely what data must be exchanged; and the Model View Definition (MVD) which maps those requirements onto a data schema such as IFC (Industry Foundation Classes).

2. Core Framework Components

2.1 Process Maps and Exchange Requirements

Process maps using the Business Process Model and Notation (BPMN) or Unified Modelling Language (UML) activity diagrams describe the sequence of activities in a construction process. Each activity has defined inputs and outputs. The exchange requirements capture the information content needed at each exchange point: which objects (walls, slabs, ducts, pumps), which properties (material, fire rating, thermal transmittance), and which relationships (containment, connection, aggregation) must be included.

When developing exchange requirements, stakeholders must distinguish between mandatory and optional information. Mandatory information is essential for the receiving party to perform their work — for example, a structural engineer needs beam cross-section dimensions and material grade to perform structural calculations. Optional information, while potentially useful, should not block the exchange if missing. This distinction is formalised in the IDM using the “required” attribute on each information element, enabling software tools to automatically check that all mandatory data has been provided before an exchange is considered complete. Over-specification of mandatory information is a common source of workflow inefficiency, as it forces project teams to provide data that may not be available at that stage of the project.

2.2 Model View Definitions and IFC Mapping

MVDs are the technical bridge between exchange requirements and data schemas. An MVD defines a subset of the IFC schema that is sufficient to support one or more exchange requirements. For example, a “Structural Analysis View” might include IFC classes IfcBeam, IfcColumn, IfcStructuralAction, and IfcStructuralReaction, while excluding building service elements irrelevant to structural engineering.

3. Implementation Strategy and Best Practices

Successful adoption of the ISO 29481-2 framework requires organisational commitment and clear governance. Key steps include: (1) appointing a BIM information manager responsible for maintaining process maps and exchange requirements; (2) establishing a project-specific IDM register that tracks all agreed exchanges; (3) training all stakeholders in the terminology and tools; and (4) implementing a quality assurance procedure that validates MVDs against exchange requirements before data is exchanged.

The framework also supports incremental adoption. Organisations can start with the most critical exchanges (e.g., architectural-to-structural coordination) and expand coverage over time. The modular structure of IDMs means that new exchange requirements can be added without disrupting existing workflows.

A critical aspect of implementation is defining the Level of Information Need (LOIN) for each exchange requirement. LOIN specifies not just what information is exchanged but also its level of detail, level of accuracy, and level of assurance. For example, a spatial coordination exchange during design development may require LOD 300 geometry with verified accuracy, while a facility handover exchange may require LOD 500 as-built geometry with associated O&M documentation. Clearly documenting LOIN within each IDM prevents both under-delivery and over-delivery of information, reducing disputes and improving project efficiency. The ISO 19650 series provides complementary guidance on information management processes, and organisations should align their LOIN definitions with the capability and capacity requirements specified in their project’s BIM execution plan.

4. Frequently Asked Questions