BIMinAM Residential Workstream Meeting 31-03-2026

BIMINAM RESIDENTIAL WORKSTREAM MEETING, 31-03-2026

Date: 31 March 2026


Purpose of the Session

The session focused on defining a minimum viable data structure and validation framework for asset information, particularly for fire-critical and safety-related assets in residential buildings. The objective was to establish what information must exist to enable competent people to carry out work safely, verify it, and provide auditable proof—moving beyond formats (BIM/COBie/O&M) toward validation of outcomes.


Key Themes from the Transcript

1. Industry-led baseline: defining “what must exist”

Building on extensive prior industry engagement (roundtables and expert input), the group focused on agreeing core principles rather than tools or formats.

Four consistent requirements emerged:

  • competent people
  • defined lifecycle tasks
  • use of checklists
  • auditable records

However, the key gap remains:

no agreed data structure or validation logic to support these requirements.


2. Four-part information and validation model

A structured framework was collaboratively developed to define required information:

  1. Identify – Locate and define the asset
  • Coordinates (XYZ), location, space/zone
  • Asset ID, type, and context
  • Roles, responsibilities and objectives
  • Terms of appointment and information requirements (AIR/EIR/OIR)
  1. Understand – Define what the asset is and should do
  • Specification, performance and design intent
  • Manufacturer, model, lifecycle and service history
  • System relationships and dependencies
  • Risk, criticality and constraints
  1. Work – Enable safe and effective execution
  • Tasks, schedules and planning
  • Competence requirements and accreditation
  • RAMS, permits and method statements
  • Tools, resources and stakeholder coordination
  1. Prove – Evidence and assurance
  • Testing, commissioning and certification
  • Photos, inspection reports and updated records
  • Compliance with standards and warranties
  • Competent sign-off and auditable records

This creates a repeatable validation logic, applicable across all asset types.


3. Validation over documentation

A key insight was that the challenge is not the absence of processes, but the lack of validation that they have been followed correctly.

The framework shifts focus from:

  • documents and deliverables
    to:
  • verifiable outcomes and evidence of compliance

This reframes the Golden Thread as a validation system, not just an information repository.


4. “Refusal to sign off” as a validation test

The group explored conditions under which an asset should not be signed off, identifying critical failure points such as:

  • incorrect or unidentified asset
  • lack of competence or induction
  • insufficient or unclear specification
  • missing permits or incorrect procedures
  • lack of evidence or auditable records
  • non-compliance or known errors

These represent the negative test of the model—defining when information and validation are insufficient.


5. Importance of roles, responsibility and accountability

A recurring theme was the need to clearly define:

  • who is responsible for information and validation
  • accountability for sign-off and verification
  • alignment across design, construction and operations

This is critical to ensuring that information is trusted and actionable.


6. Defining “as-built” and verified information

The session highlighted a major industry issue:

  • “as-built” means different things to different stakeholders

The group is working toward:

  • a clear, shared definition of verified, accurate information
  • agreement on who is responsible for providing and validating it (likely the principal contractor)
  • mechanisms to ensure it is checked and enforced (e.g. by regulators)

7. Integration with wider regulatory and operational challenges

The discussion linked this work to broader industry issues, including:

  • Awaab’s Law (damp and mould response requirements)
  • energy performance and operational outcomes
  • need for integrated workflows across teams (housing, safety, customer service)

This reinforces that asset information must support multiple real-world use cases, not operate in isolation.