Rule ID: SOL/244/1.1
This article describes how the IDS Validation rule works and how you can configure the rule. The article also describes what IDS is, why it’s used and how you can create your own IDS file.
In v24.9.0, an update to this rule template was published. The rule now supports all common IDS versions: v0.9.6, v0.9.7 and the official version v1.0. The previos, pre-release version was based on IDS v0.9.6.
The article covers the following topics:
The Information Delivery Specification (IDS) is a standard developed by buildingSMART for defining information requirements in a way that can be easily read by humans and interpreted by computers. IDS helps standardize the format and content of information exchanged, ensuring consistency and clarity in communications. It facilitates interoperability between different software and systems used in the construction industry by defining common data formats.
IDS is a structured framework that defines the type, format, and detail of information that needs to be exchanged between parties involved in a construction or infrastructure project. It specifies how information is created, managed, and shared throughout the project lifecycle. IDS defines the level of detail (LOD) and level of information (LOI) required at different stages of the project.
An IDS is a file format ending in .ids and it contains a list of information specifications. For example, a single specification might say that "all doors must have a fire rating property". The IDS file can be shared with other stakeholders in the project (and reused in other projects following the same requirements). Model authors can use the IDS file to ensure all required information is provided for each specification. The IDS file can also be used to check whether the IFC model meets all of the specifications. Reports may also be generated to list the results of specification compliance checks.
For further information on IDS, have a look at the buildingSMART website and the IDS documentation.
The IDS file itself is an XML file. To create the file, we recommend using the Solibri IDS Editor, which is available for Solibri customers. For more information on the product, see here.
With this rule, you can ensure that the model includes all information according to the requirements of the IDS file you’ve specified.
In the rule parameters, you can select the IDS file used in the rule:
IDS Definition: To select the .ids file, click Select IDS file or drag and drop the IDS file to the Parameters view. When the file has been loaded, you can see a preview of it in the rule parameters:
In Solibri v9.13.8 and newer, there are several improvements in the IDS rule:
-
You can open multiple IDS files at the same time. In earlier versions, you can only open one IDS file at a time.
-
XML file formats are supported
-
When you import an IDS file, rulesets, which contain a separate rule for each applicability, are automatically generated. In earlier versions, you need to manually create the rules.
-
You can see the specified IFC version, so you'll know which components are checked based on the IFC version.
Notice
If there’s an error in the IDS file structure, an error message is shown when you upload the file.
Tip
You can download the IDS file used in the rule by clicking Save IDS File.
The rule creates an issue for each checked component which doesn’t meet the specifications in the IDS file:
Severity Parameters:
By default, all components not matching the requirements return a medium () issue. To specify the critical and low severities for specific components, open the Severity Parameters view and set the conditions in the filter table: