IDS file: understanding Information Delivery Specification

An IDS file describes information requirements for BIM models. buildingSMART presents IDS as a computer-interpretable XML format, mainly used to define specifications for IFC (the buildingSMART IDS repository).

It is useful when a project team needs to make its information expectations explicit. This guide explains what an IDS covers, gives a simple example, and outlines what to check before using one.

What does an IDS file do?

IDS stands for Information Delivery Specification. It provides a way to express information requirements for BIM. The buildingSMART repository describes the standard as a way to define specifications related to IFC (repository overview).

The goal is to turn a request written in general terms into structured requirements. The repository also provides a user manual, examples, and documentation for software implementers (IDS documentation).

A simple example

Take a common request: "every door must state its fire rating". Before drafting an IDS, split it into two parts:

• what it applies to: objects of type IfcDoor;
• what is required: the FireRating property of the Pset_DoorCommon property set, filled in.

An IDS follows exactly that split: an "applicability" part that selects the objects, and a "requirements" part that describes the expected information. A request that cannot be split this way is not ready to be checked yet. For the full XML syntax, the examples in the buildingSMART documentation are the right place to start.

Create or import requirements in SeveUp App

SeveUp App lets users create and import BIM requirement sets. It can also generate IDS from requirements documents with AI: AI extraction is followed by manual validation and bSI compilation.

This can help turn source documents into an IDS without treating generation as validation. Review the result against the project’s actual requirements before relying on it.

Limitations and checks

An IDS expresses requirements; it does not replace the project team’s decisions about what information is needed. If the source document is ambiguous, clarify the request first rather than assuming generation will resolve it.

Check that the wording matches the information you intend to request from the model. For format details, refer to the manual and examples in the buildingSMART documentation.

Sources and useful links

• buildingSMART IDS repository: an overview of the standard and links to its resources.
• IDS documentation: user manual, examples, and technical documentation.