IDS v1.0: The New Standard for BIM Information Delivery (South African Context)

The way South African project teams specify, deliver, and verify BIM information is about to change — and the change is overdue.

On 1 June 2024, buildingSMART International approved the Information Delivery Specification (IDS) v1.0 as a final standard. For a construction industry still largely reliant on PDF-based information requirements, ambiguous spreadsheet schedules, and verbal agreements about what a BIM model must contain, this is a significant shift. IDS v1.0 provides the first internationally standardised, machine-readable mechanism for defining exactly what information a BIM model must deliver — and for automatically verifying that it does.

For South African project teams, the timing matters. The CIDB published its BIM Implementation Roadmap in September 2024, signaling that a mandate for public sector BIM delivery is no longer a distant prospect.

SANS 19650-1 was approved as a South African national standard in 2022, with the National Annex under active development. The regulatory framework is assembling itself. IDS v1.0 is the technical instrument that makes compliance verifiable — not assumed.

Dabisa Consulting has developed a SANS 10400-compliant Information Delivery Specification aligned to ISO 19650 and IDS v1.0, purpose-built for the South African built environment. This post explains what IDS v1.0 is, why it matters to project teams, and how it changes the information management conversation across the asset lifecycle.

What IDS v1.0 Actually Is

IDS is a standard for defining information requirements in a form that is both human-readable and computer-interpretable. The buildingSMART definition is precise: it allows project teams to specify what data must be included in a BIM dataset and then validate whether it has been delivered.

The key distinction from everything that came before is machine-readability. Traditionally, information requirements were communicated through PDFs, Excel schedules, and EIR documents — documents that a person could read but a computer could not check. The result was that compliance verification depended on manual audits: time-consuming, inconsistent, and easy to dispute. IDS replaces this with an XML-based specification file that any compatible tool can read and act on automatically.

An IDS file contains named Specifications — each with three components:

• Applicability — which model elements the requirement applies to (the filter): for example, all IfcDoor elements in a fire-rated compartment

  
  

• Requirements — what information those elements must contain: for example, FireRating must be present in Pset_DoorCommon with a value of REI30, REI60, or REI90

  
  

• Description — the human-readable rationale that explains why the requirement exists and which standard it references

Both the filter and the requirements are expressed using six structured building blocks called Facets:

Facet	What It Targets
Entity	IFC class and predefined type (e.g. IfcWall, IfcDoor, IfcBeam)
Attribute	Core IFC attributes such as Name, Description, or GlobalId
Classification	Classification codes from systems such as Uniclass, OmniClass, or SANS-aligned schemes
Property	User-defined properties within property sets — the most commonly used facet
Material	Material assignments (concrete grade, steel specification, fire-resistant board)
Parts	Structural relationships between elements (PartOf hierarchy)

IDS supports four types of value constraints beyond simple exact matches: enumeration (pick lists), pattern (regex naming conventions), bounds (numeric ranges such as concrete grade ≥20 MPa), and length (character count). Every requirement can be flagged as Required, Optional, or Prohibited — giving precise control over what must, may, or must not appear in the model.

What IDS does not do is equally important to understand: it is strictly an information delivery specification. Geometry checks, clash detection, structural calculations, and design rule validation are out of scope. IDS validates that the right information is present in the right place. It is the compliance layer that sits between authoring and exchange — and it is exactly the layer that South African BIM delivery has been missing.

Why the Timing Is Significant for South Africa

South Africa's BIM adoption figures tell a clear story.

Only 15% of South African firms produce federated models, and fewer than 5% deliver ISO 19650-compliant BIM models on public projects.

The pattern is consistent internationally. Jurisdictions that have fused open standards with statutory procurement requirements — the UK's 2016 BIM Level 2 mandate, Singapore's 2010 requirement for projects over 5,000 m², Sweden's model-authenticated payment gates — have produced measurable outcomes:

cost accuracy improvements of 5–10%, carbon savings of 15–20%, and dispute reductions of up to 40%.

South Africa has the policy framework emerging. IDS v1.0 provides the technical instrument.

The practical implications of IDS v1.0 for South African project teams are immediate, even before a formal mandate:

• For contracts that already reference ISO 19650, IDS provides the machine-readable mechanism to enforce the information requirements stated in the EIR

  
  

• For developers and asset owners, IDS shifts the compliance burden from the employer (who currently relies on manual audits) to a verifiable, automated check at each information exchange milestone

  
  

• For BIM managers, IDS replaces ambiguous Employer's Information Requirements documents with specifications that can be loaded into any IDS-compatible tool and checked automatically against submitted IFC models

  
  

• For the CIDB mandate trajectory, firms that have built IDS-aligned information delivery capability before the mandate are positioned to win the first wave of compliant contracts

IDS v1.0 and ISO 19650: How They Work Together

IDS is designed as the technical instrument that makes ISO 19650's information management framework enforceable. ISO 19650 defines the process:

• who specifies information requirements,

  
  

• when they are delivered, and

  
  

• who is responsible for verifying them at each stage of the asset lifecycle.

IDS defines the form:

• a machine-readable file that captures those requirements so they can be validated automatically.

The ISO 19650 information delivery cycle runs from Stage 0 (Need) through to Stage 8 (Operation). At each stage, specific information deliverables are required from specific parties:

• Stage 2–3: Employer's Information Requirements (EIR) drafted; Pre-BIM Execution Plan (Pre-BEP) submitted

  
  

• Stage 4: Post-BEP confirmed; Task Information Delivery Plans (TIDPs) and Master Information Delivery Plan (MIDP) agreed

  
  

• Stage 5–6: Project Information Model (PIM) progressively populated and verified

  
  

• Stage 7: Asset Information Model (AIM) delivered; COBie data transferred to the facilities management system

  
  

• Stage 8: AIM maintained throughout operation

IDS sits at the verification step of this cycle. When the EIR specifies that all mechanical assets must carry an AssetTag, a MaintenanceFrequency, and a reference to the Operations and Maintenance manual — an IDS file encodes those requirements so that when the design team submits their Revit model as an IFC export, the compliance check runs automatically.

As Plannerly notes, IDS allows teams to automate the verification of information deliveries, track compliance across multiple BIM projects, and provide auditable evidence that requirements have been met.

A SANS 10400-Compliant IDS for South Africa

South Africa's national building regulations are codified in SANS 10400. They cover occupancy classification, structural design, foundations, fire protection, accessibility, energy performance, and more across 15+ Parts. Until now, encoding these requirements into a BIM information framework has required manual interpretation — a process that varied from project to project, firm to firm, and auditor to auditor.

Dabisa Consulting has developed a SANS 10400-compliant IDS aligned to IDS v1.0 and ISO 19650, purpose-built for the South African built environment. The specification covers 25 named specifications across 13 Parts of SANS 10400, each structured in the IDS v1.0 format with explicit Applicability (which IFC classes the requirement targets), Requirements (what information those elements must carry), and regulatory references.

Key specifications in the Dabisa SANS 10400 IDS include:

SANS 10400 Part	Requirement	IFC Target	IDS Rule Type
Part A — General Principles	Occupancy class must be one of 30 defined SANS classes	IfcBuilding, IfcBuildingStorey	Enumeration
Part B — Structural Design	Design standard reference (SANS 10100-1, 10162, 10082, or 517)	IfcBeam, IfcColumn, IfcSlab	Presence + Enumeration
Part H — Foundations	Concrete grade ≥20 MPa for strip footings	IfcFooting	Bounds
Part K — Walls	Load-bearing status, fire rating, wall function	IfcWall	Presence + Enumeration
Part T — Fire Protection	Fire door class, sprinkler trigger temperature, fire compartment reference	IfcDoor, IfcFireSuppressionTerminal	Presence + Enumeration
Part XA — Energy	Energy zone (1–6), fenestration ratio ≤15%, roof R-value by zone	IfcBuilding, IfcRoof	Bounds + Enumeration

Each specification includes a custom property set (SA_SANS10400_) for South Africa-specific requirements not covered by standard IFC property sets — ensuring that SANS 10400 requirements that have no IFC equivalent are still captured, validated, and traceable.

This IDS directly feeds the BIM Model Compliance & Asset Readiness System — Dabisa's rule-based compliance engine that validates models from Revit, Civil 3D, IFC and Navisworks against ISO 19650, IDS v1.0, and SANS 10400, and delivers FM-ready asset registers and compliance dashboards for healthcare, infrastructure, and commercial development projects.

What This Means for Project Teams

The practical shift that IDS v1.0 enables can be summarised in one sentence: information requirements move from opinion to evidence.

Before IDS, a BIM Manager could state in an EIR that all assets required an Asset_Tag and a Maintenance_Frequency — but verifying delivery required opening the model, running manual checks, and relying on the design team's own assurance. After IDS, the same requirement is encoded in a machine-readable specification file. The check runs automatically against any IFC export. The result is a pass or fail against a specific requirement, linked to a specific model element, with a specific rule reference — evidence that a project auditor, a facilities manager, or a CIDB assessor can review.

For each role in the project team, the change is meaningful:

Developers and Asset Owners receive compliance evidence at each information exchange milestone — not just at handover. The compliance score is visible in real time, not discovered after practical completion when it is too late to fix without variation orders.

BIM Managers replace ambiguous EIR narratives with IDS specifications that the design team can load into any compatible tool and check against before submission. The back-and-forth on "what do you mean by FM-ready?" is replaced by a file that answers the question unambiguously.

Design Teams (Architects, Engineers, Contractors) know exactly what is required and exactly whether they have met it, at every stage. The compliance bar is defined before the project starts, not negotiated at handover.

Facility Managers receive an asset register that has been validated against the IDS before it was handed over. The gap between what the BIM model promised and what the FM system can actually use is closed before the keys are handed over.

Infrastructure Authorities, Building Owners — Roads, Rail, Water utilities, Universities and Commercial Developments — gain contractible compliance evidence aligned to the ISO 19650 procurement framework they are moving toward. The situation, where firms can not deliver compliant models because no enforceable standard exists, becomes preventable.

The Road Ahead: SA's BIM Mandate Trajectory

The Global BIM Network tracks South Africa's implementation of ISO 19650, noting that SANS 19650-1 was adopted in 2022 with the National Annex under development. The BIM Community Africa's ongoing SANS 19650 workshops reflect active engagement with what the National Annex will require — and how it will be enforced.

The direction is clear. Research recommendations for South Africa include amending the Public–Private Partnership Manual to require ISO 19650-compliant, IFC-based federated models at each project gateway, and integrating BIM competence criteria into CIDB grading — potentially linking a percentage of progress payments to COBie delivery (Frontiers in Built Environment, 2025). When that happens, IDS v1.0 is the standard that makes the compliance requirement verifiable.

Firms and project owners that build IDS-aligned information delivery capability now are not just preparing for a mandate. They are building the practice that eliminates the variation orders, the coordination cost overruns, and the FM handover failures that currently define too many South African infrastructure projects.

Conclusion

IDS v1.0 does not replace the EIR, the BEP, or ISO 19650. It makes them enforceable. It converts the information requirements that project teams have always wanted to specify — but could never reliably verify — into machine-readable, automatically checkable, auditable evidence of compliance.

For South Africa, where BIM adoption is accelerating but compliance is still largely voluntary, IDS v1.0 arrives at exactly the right moment. The CIDB roadmap is published. SANS 19650-1 is live. The SANS 10400-aligned IDS framework exists. What remains is the decision — at project team level, at authority level, and at industry level — to treat information compliance as a deliverable, not an afterthought.

Request a BIM Compliance Readiness Assessment

Dabisa Consulting has developed a SANS 10400-compliant IDS, aligned to ISO 19650 and IDS v1.0, as part of our BIM Compliance & Asset Readiness framework. If you want to understand what IDS v1.0 means for your current project, or how a BIM Compliance Audit against the standard applies to your models, contact us at loyiso@dabisa.co.za or visit dabisa.co.za.