IDS Standard and bSDD Service as Tools for Automating Information Exchange and Verification in Projects Implemented in the BIM Methodology

Abstract

The era of openBIM is ongoing, and the open standards IDS (Information Delivery Specification) and bSDD (BuildingSMART Data Dictionary) are significantly impacting the automation of information exchange and verification in projects, using predefined data, enabling quick updates and combining it with other data. IDS and bSDD complement the widely used open IFC (Industry Foundation Classes) format, which solves the issue of purchasing both the appropriate hardware and software to work with native files from different sources. As a result, external assignments or internal tasks have the potential to precisely define the desired product, speeding up the entire process carried out according to the BIM (Building Information Modeling) methodology, reducing the number of questions about ambiguous requirements, and eliminating the need for continuous feedback on the model. Both files can be used on the developer’s side as an attachment to BIM documents, as well as on the construction site or during the bidding process. Digital IDS and bSDD files can be interpreted not only by humans but also by machines, bringing added value and usability. An identified research gap is the lack of a clear procedure for applying the mentioned standards, and thus, the common problem of purchasing software to check the quality of the model for information content. This article demonstrates the possibility of creating IDS and bSDD files in tools based on filling in specific fields and their interrelation, as well as their practical use in the process of verifying the information content of BIM models. By adopting open standards, teams can improve communication, increase productivity, and ensure continuity in data exchanges.

1. Introduction

Information Delivery Specification (IDS) is a recently introduced standard designed to define information requirements. On 6 June 2024, it was approved in version 1.0. An IDS is designed for both human-readable and computer-interpretable purposes, unlike traditional requirements distributed in formats such as PDF documents or spreadsheets. It does not have usage constraints associated with specific software vendors owing to its specification based on the Extensible Markup Language (XML). Its schema is defined in the XSD (XML Schema Definition). Informational requirements can be defined for classification, properties, quantities, attributes, materials, unit types, permissible property value lists, value ranges, IFC classes (Industry Foundation Classes), and their interrelationships [1]. The IDS structure allows the inclusion of descriptions and explanations to enhance the understanding of other users. Generated files have the extension “.ids”. This standard ensures transparency in data exchange, particularly when integrated with other standards and services, among stakeholders in the construction industry at every phase of the investment process. It can be treated as part of contractual requirements or as an annex. Digital construction product information allows contractors, architects, constructors, asset users, asset owners, construction product manufacturers, and clients to connect IDS specifications with this contract and other multiple sources of documents [2].

The same applies to the service for collecting and sharing data dictionaries, BuildingSMART Data Dictionary (bSDD), which is not a standard but has been widely adopted recently, despite the origins of both tools dating back to several years. The BuildingSMART Data Dictionary is an online platform for storing data dictionaries. It allows free publication and access to dictionaries by extending the global IFC schema with its own industry (architecture, engineering, construction, and operations—AECO) classifications and locally required parameters. In the construction industry, there is a demand for the identification of construction products and systems that are parts of buildings and are references for compliance assertions. We can look for information about construction products from the Product Data Template (PDT), the data structure of which is defined in ISO 23387 [2]. Different products may have the same properties, and defining them each time introduces disharmony. The solution to this problem is to use a single source of truth (SSOT), which is a data dictionary [3]. BSDD is an implementation of ISO 23386 [4] and ISO 12006-3 [5], which ensures data security. The former provides guidelines for defining and maintaining properties in data dictionaries for exchanging information in construction between applications and digital formats, and the second specifies their form—it is responsible for standardizing data exchange dictionaries [6]. There is a need for both open and transparent data dictionaries based on ISO 12006-3, in where all properties have a globally unique identifier (GUID) that can be interpreted by a machine. The BuildingSMART Data Dictionary is an example of such a dictionary [3]. Dictionaries are semantic databases of properties and their meaningful and clear definitions that aim to guarantee the correct interpretation of the information contained in the model, making the information high quality, consistent, and interoperable. Definitions can specify parameter units, allowed parameter ranges (in the form of a list) and materials, size range in which values should fit, maximum or minimum value, and other information. However, they did not define specific field values (e.g., width equal to 25 cm, fire resistance class REI30), data of specific products, and standards. Published data are verified before they are made available on the site. In addition, they may be translated into other languages.

Both IDS and bSDD were developed by buildingSMART International and represent a milestone in the use of openBIM in workflow [7]. Such an approach focuses on utilizing open standards in the BIM (Building Information Modelling) process, which are free of charge for access to their specifications, devoid of distribution restrictions by specific manufacturers, including publicly accessible comprehensive documentation, are developed openly, and can be freely utilized by any interested party. IDS and bSDD are fully integrated into the openBIM process, which is collaborative and comprises all participants, promoting interoperability to benefit projects and assets throughout their lifecycle. OpenBIM requires involvement from the industry [8]. Without this process, the exchange of information between different software would not be possible because each manufacturer providing modeling tools introduces its own file extensions, interface, and solutions without providing the possibility of correctly reading the data created in another program. This possibility is provided by IFC, which is a standard commonly used in BIM. BIM is treated in two ways: as an evolution of the CAD system or as a revolution in construction; therefore, it is a tool and philosophy. BIM theory defines the way tools are used, which in turn is limited by the access and development of existing applications. BIM refers to both buildings and structures that are being designed and built, and to existing facilities. At the building management stage, an AIM (Asset Information Model) model can be created to include all relevant information from an asset administration point of view, e.g., inspection date, condition, and manufacturer [9]. Among the most important issues that need to be defined in the AIM model are the appropriate and reasonable Level of Detail (LOD) and Level of Information (LOI) [10]. Such a model can also be used to plan the modernization of a building and visualize the work in progress. The correct geometry of the model, together with classified properties, is key to achieving many benefits, such as the ability to make accurate cost calculations, material estimates, and schedule work [11]. The openBIM approach was created as a milestone in 2012, and thanks to the implementation of this idea, users remain independent of software tools, and their attention is focused on the compliance of the workflow. In this way, the importance of competence in managing the construction process increases, not the ability to use specific software [12].

The BIM process itself is defined by the BIM methodology, comprising a set of instructions, norms, and standards specifying how the investment process should proceed, from conception through construction to operation and potential demolition, which is the end of a building’s life cycle. Information requirements should be defined at the conceptual stage, specifying, among other things, the information to be included in the ordered digital model. The most common reasons that reduce trust in digital data are inaccuracies between data, missing data, or, on the other hand, an unreasonable excess of data. One barrier is the formalization of information requirements. According to ISO 19650, information requirements are specifications that answer the questions of what information should be produced, and when, how, and for whom. The series of standards groups information requirements into documents depending on the context and side of the construction process [13].

The data that produces this information should be accessible, searchable, interoperable, and useful. The content of the information is verified against the established requirements. Based on a review of the current literature, it appears that the process of verifying the information content of BIM models using open digital standards has not been sufficiently explored. The objective of this article is to demonstrate how IDS and bSDD impact the automation of information exchange and verification in projects implemented within the BIM methodology. Automating this procedure brings numerous benefits and enhances the quality of the delivered data.

2. Materials and Methods

To demonstrate the possibilities of connecting bSDD and IDS and the automation they provide, it is necessary to create such files. However, before creating the files, it was crucial to familiarize oneself with their repository and documentation to understand the structure, how the models work, and the process of creation, management, sharing, and updating. The operation of the described tools can start in two ways. In the adopted process, the starting point is to define the data dictionary.

Creating a custom data dictionary initially requires gathering existing information requirements. These requirements may originate from detailed instructions, technical documentation, or AIM requirements. Next, it is necessary to define and standardize the parameters, which involves specifying property data types, creating property value lists with allowed input values, and aligning them with the IFC standard. The bSDD platform hosts a dictionary created by buildingSMART International for the IFC standard version 4.3. Inside the dictionary, there are 1418 classes corresponding to the IFC schema. For example, we can find a class for stairs that is IfcStair with a definition, and child classes that are types of stairs such as Curved Run Stair, Double Return Stair, and Half Turn Stair also with definitions. Each of these classes contains the properties assigned to it. When creating our own dictionary, in which we want to include a class already defined in the IFC standard and, moreover, corresponding definition to our needs, it is necessary to give as a source this buildingSMART International dictionary instead of redefining terms and hence duplicating them or specifying the related IFC entities. Finally, one should familiarize oneself with the data structure in the bSDD service. The bSDD platform comprises a list of organizations with their own dictionaries, followed by a list of these dictionaries, each containing classes, properties, and property sets, with all entries having detailed definitions. Relations are specified between properties and classes, and allowed values are defined for individual properties. The platform’s content is accessible via a web interface, although greater benefits can be derived from utilizing the API (Application Programming Interface). The implementation of bSDD (Figure 1) introduces numerous functionalities; however, it is a new service that requires experimentation and familiarization with an incompletely documented subject. Dictionary functionalities have been continuously refined and updated. In March 2024 was added the ability to include diacritical marks in code names, such as Polish letters: ą, ć, ż, This allows for the reflection of commonly used names in BIM datasets according to the IFC identifiers. Previously, only digits, letters from a to z (both lowercase and uppercase), and three special characters: “_”, “.”, and “-” were available. Other HTML characters are intentionally omitted, even though some software permits their use in BIM model names [14]. Data dictionaries are based on the JavaScript Object Notation (JSON) text format. However, programming skills are not required to create a file. On platforms such as ACCA, using the usBIM service, it is possible to create a new bSDD file by filling in values in a ready-made form (Figure 2). The first step is to name the organization’s dictionary, specify its version (the dictionary can be updated), the language in which it will be created, optionally the date of publication and license of use, and add other relevant information in this area. The following sections refer to classes and properties. Relations are created between them. For each class, its name, language, and definition are specified. Optionally, a precise description, status, version, revision, and references can be included. For a better search, the synonyms of a class can be specified. In the property addition section, we also specify its name, language, and definition, and the optional data are as in the classes, description, status, version, revision, and references. For each parameter, we specify the data type (string, date, character, etc.) and allowed values. Each record entered in the dictionary has its own individual URI code, which we can leave default or change to our own code. A helpful functionality is the generation of patterns with AI support, which involves entering instructions as to what to record, e.g., start with the letter L or U and then include 2 digits from 0 to 9. Such an instruction applies to the coding of the “floor” property, where we consider underground floors—“U” and above-ground floors—“L”. The artificial intelligence in this example will generate the following pattern: ‘[UL]\d{2}’. A single dictionary can contain multiple classes and parameters. The completed dictionary can subsequently be imported into an IFC model or native BIM software (Figure 1).

People who have mastered the basics of programming will probably become familiar with the data structure more quickly; however, as noted above, this is not necessary. The authors of this article do not have any programming skills. To understand the operation of data dictionaries, IDS, and other openBIM standards, it is necessary to become familiar with their structure. There is a BuildingSMART Data Dictionary repository on GitHub, where you can find published documentation with examples. The ACCA-published e-book “IDS for everyone” can also be a helpful document, as it explicitly describes usBIM functionality. Regardless of the level of sophistication, difficulties and errors in the dictionaries may arise, depending on your knowledge and experience, as well as the development of the platform and functionality of the dictionaries. The challenge can be understanding the nature of bSDD activity. A common misunderstanding is identifying data dictionaries with the source of products from specific suppliers or specific property values.

Best practices and principles have been established to create and add dictionaries. One file corresponds to one dictionary; therefore, it is not possible to upload classes in parts. Dictionaries should be concise; otherwise, they should be divided. Class names should be unique and conflict-free from existing ones. Instead of duplicating information, references such as the IFC standard are used to enhance the dictionary’s usability (Figure 3) [15]. Currently, providers implementing bSDD in their products include BIM Base B.V., IfcOpenShell Contributors, Cobuilder, Plannerly, Digibase (VolkerWessels), ACCA Software S.p.A., Autodesk, and BIMQ [16]. The first Polish dictionary published in the bSDD service was the dictionary from Mostostal Warszawa S.A. [17]. Uploading the first dictionary requires registering the organization in the BuildingSMART Data Dictionary and logging in. When adding a new dictionary to the platform (Figure 4), it gains “Preview” status, which allows you to modify it and upload a fixed version, activate the current version, or permanently delete the dictionary. The activated dictionary is given a unique URL, and its content is permanently embedded on the platform even after the status is changed to inactive. This is to prevent failure to comply with the contractual clauses of the bSDD [18].

An organization can have multiple dictionaries. The generated and published dictionary has the following structure: at the top, there is the name of the dictionary and its version; the same information is on the left, whereas below, there is information about the dictionary status. In the upper-right corner, there is information about the dictionary coding language; here, you can translate the dictionary into other languages. Underneath, classes and properties are presented. When selecting each class and property, the data assigned to it appear, such as class code, definition, synonyms, related IFC entities, or parameter type (Figure 5).

The example (Figure 6) shows the allowed values for the “Hazard Type” property, which are Fall, Electric shock, Hazardous substances, Excavation, and Crane. Each value contains a code, description, and its own identifier URI. BuildingSMART Data dictionaries have the function of making them private. This functionality is also constantly being developed so that private dictionaries can be searched and used just as effectively as public dictionaries. This is a useful option when creating a classification for a specific project by a private developer.

An important concept of dictionaries is the ability to introduce their translation into various languages. Such a dictionary becomes useful in international projects, where despite language barriers, every participant in the construction process has a clear definition of the classification. It is also an opportunity to implement an existing dictionary in domestic projects after it has been translated. On the bSDD platform, we can switch between existing language versions (Figure 7).

To further enhance the description of a given property, we can provide a reference to a graphical definition. For example, in the case of a walled property, we determine the length in the set. The length property provides a visual representation explaining how to calculate this value in the form of a link to a graph (Figure 8). By clicking on the link below, we will be taken to a new page that displays the graphic (Figure 9). It is not possible to display an image directly in the same window and add it to the attributes of the dictionary term. The only possibility that bSDD offers is to post a public link to the visualization. Such visualization may be unnecessary, but it makes an important addition to geometric properties. For example, a strip foundation will have the property ‘height’, but a slab will have ‘thickness’ instead of height.

Once the dictionary was created with digital classification, the process of creating the IDS began (Figure 10). In each project, there is a step of verifying the validity of the contracted BIM model regarding geometry and information. IDS is concerned with this second check.

There are many ways to define information requirements, such as PDT (Product Data Template), EIR (Exchange Information Requirements), BEP (BIM Execution Plan), and IDM (Information Delivery Manual). Depending on the requirements, any of these may be a good choice, although the recommended solution for using openBIM is the IDS standard [19]. However, text documents compiled into PDF files are currently the most popular form due to their versatility, the widespread familiarity with editing tools for such documents, and the easy mirroring of paper contracts. A slightly better way to record the requirements is to place them in a spreadsheet. Nevertheless, the traditional method of defining information requirements is inefficient and time consuming to implement. Rules must be created for each project to check the content of the parameters in the model and the values of these parameters. DOC and XLS document templates are created and managed by file authors; therefore, they are not universal. In addition, they are not standardized, which may impact their interoperability with individual software and reliability [13]. It is, therefore, more efficient to transfer such requirements stored in text files to an IDS file. During the transition from traditional forms of storing information requirements to digitizing them using the IDS standard (Figure 11), users may struggle with the challenge of writing such requirements according to the syntax of the specification, aligning them with Facets ranges, specifying exactly all elements to meet the requirements, separating information requirements from geometric requirements, or appropriately converting geometric requirements to information requirements with reference to existing properties that store numerical values. This process is not easy and requires a one-time consideration of the requirements relative to their usability; however, once an IDS is created, such a file is already automatically recognized by many programs and does not require additional comments or explanations.

IDS is a specification. Each specification consists of three main parts: description, applicability, and requirements (Figure 12). The composition of IDS includes specification names, verified scope, verification rules, and usage explanations. It is possible to create a message that appears when there are inconsistencies in the requirements to be verified and further enrich it with suggestions of the values expected to be entered. An example specification might be that all external walls should be load-bearing walls, in which case IDS will check the elements in the wall class, with an external position assigned, and in them, the value of the structural function. The IDS standard does not include checks for geometric inconsistencies in a model by using this standard [13]. At this point, there are also errors or impossibilities in checking numerical values, i.e., whether the width of the wall is less than the specified value, whether the volume is greater than the specified value, whether the height is within the specified range, and so on.

The usage for the selected ‘Applicability’ groups and the information requirement rules ‘Requirements’ formulated are described by a set of ‘Facets’ types. We identify the following types of ‘Facets’:

• Entity—an IFC object;
• Attribute—properties of an IFC class;
• Classification—class;
• Property;
• Material;
• Parts—part of a specific set of properties.

The Facet used in ‘Applicability’ describes the information used to identify the selected parts of the model. The Facet used in ‘Requirements’ describes the information constraints that the selected parts of the model must meet [20]. Owing to the IDS, the client can precisely specify their needs, and other participants in the process know what they need to provide. Specifications are linked to requirements, simplifying the verification during requirement modifications. This approach reduces the likelihood of oversights and ensures consistency in the introduced changes. Instead of manually creating validation rules for each model, contractors upload a predefined IDS file. The standard operates most efficiently in the IFC format. Such a process enhances workflow automation, reduces model validation time, and limits the transfer of excess data (Figure 13). Consequently, IDS is applied to define the Level of Information content in models.

IDS and BIM, in general, can also be helpful in implementing a circular economy model. This issue is important because the construction sector is responsible for almost a quarter of the CO₂ emissions from all sources of economic activities. The need to ensure a closed cycle includes an examination of the content, quality, and origin of the material, the environmental impact of the facility, and aspects related to the removal of components. An IDS automatically verifies material associations, checks the validity of data types and units, can, for example, verify the strength class or lead content (if there is a parameter storing such a value), and can identify the coded origin of the material. This shows that, in most cases, it is necessary to define additional custom properties. The IDS standard does not use inheritance; therefore, all the subclasses of the larger IFC group must be enumerated. However, IDS does not allow the material properties assigned to individual elements or universal solutions, such as multifunctional partitions, to be checked. Relatively difficult to express in BIM is the information related to disassembly instructions and connections between components for building adaptations [16].

It is possible to include a link to the bSDD in the IDS so that the information contained in the dictionary can be supplemented by reference to the next investment phase. Each of the established milestones in a project can have its own separate IDS. Terms from the bSDD can be used in IDS to work out an unambiguous definition of different types of names. Using a prepared dictionary, we do not create duplicate regulations. Although an IDS is an XML-based file, programming skills are not required to create its own specifications. Currently, more than 20 software tools have self-declared the ability to author an IDS file; their list can be found on the Building SMART International website: Software Implementations. These tools provide an opportunity to create IDS files in a simple manner. Specifications are created by filling the available templates. We fill in basic information about the IFC version to which a given file applies; we define what elements we want to check and what requirements they should meet. One such tool is usBIM.IDSeditor (Figure 14). As an example requirement that states that each reinforced concrete column must have a valid ‘Sector’ property, the existing dictionary ‘Rektorat Politechniki Poznańskiej’ was first searched. The dictionary has been prepared in Polish. In the dictionary, we search for the class ‘Słupy żelbetowe’, and from the available properties, we select the property ‘Branża’ from the property set ‘01 KLASYFIKACJA’. The specification thus created contains a URI identifier for the bSDD. We do not need to know the names of the classes and properties, and we should be careful to spell them correctly. The risk of error is eliminated by being able to add the source of the classification from the bSDD, as we only select the elements of interest.

In a tool such as usBIM, in addition to the individual specifications, we have a preview of the XML code and a report that we can download in Word Document, Rich Text Format, or Plain Text. The downloaded IDS file has a version of 1.0.

3. Results

3.1. Automatical Model Verification Process

The scheme of automated model verification starts with the creation of information requirements in IDS. Then, in the native software, a model is created according to the provided requirements and exported to IFC. During both the modeling and creation of specifications, the published bSDD dictionary can be used on an online platform to assign appropriately described classes, properties, or materials. The BIM model is automatically checked with the IDS file in the software dedicated to analyzing the quality of the models. Any discrepancies that arise should be forwarded by BCF files to designers for correction or supplementation. The model, IDS file, and comments should be shared using the CDE platform so that all information is available in one place, easily accessible, and archived. This workflow is based on openBIM, i.e., open standards, independent of software and suppliers (Figure 15). The use, availability, management, and durability of digital data have improved [7]. To create an IDS standard and data dictionary, it is necessary to standardize the naming of parameters, definitions, ranges, and classification of elements so that the specification records can be universal for each project. Another important step is to export the file from the native program to IFC—elements must be correctly classified into IFC classes and types, at least one classification system should be established in the project specification, and the file exporter to IFC should be configured in detail.

3.1.1. Creating IDS with bSDD

The usBIM.IDSeditor tool provided by the ACCA software was used to create specifications to verify the information contained in the model. The following six specifications were created.

• All elements must have the correct property ‘Industry’;
• All elements at the foundation level must have the correct property ‘Category’;
• All slabs of a type ‘Pre-stressed plate’ must have the correct value of property ‘System’;
• All elements must have the correct value of the property ‘Working plot’;
• All Foundation walls must have the correct value of property ‘Location’;
• All elements must have the property ‘Concrete class’.

They utilized a connection to the bSDD created for the project implemented using the BIM methodology. The ‘Rektorat Politechniki Poznańskiej’ dictionary (Figure 16) consists of 58 classes, which represent construction elements and 35 associated properties. These properties are further organized into six property sets that are differentiated based on the specific characteristics of the object.

While creating subsequent specifications, the function for creating property requirements using bSDD was selected (Figure 17). Then, in the dictionary, the appropriate element class was searched for, and from its properties, the one was chosen based on which elements were being searched for that either had to meet a condition or the one that had to fulfill specific requirements—depending on whether the property was searched for in Filters (applicability) or in Requirements (Figure 18).

The specifications created in this way can be downloaded in IDS version 1.0 format after the file has been validated.

The described possibilities for creating information requirements rules are provided by some BIM model verification programs such as Solibri or Bexel Manager, while with the IDS format, we are able to upload these requirements into any of these programs without any need to rewrite the rules inside the software because of the different native file format. This approach has a direct impact on increasing the productivity of employees by reducing the time needed to adapt these rules to the software and, at the same time, decreasing the cost of labor, as the time saved allows employees to take care of other tasks.

3.1.2. IFC Model

The created classification was developed for the purpose of the construction project of the administration building, where the contracting party is Poznań University of Technology and the General Contractor is Mostostal Warszawa S.A. The project is being carried out according to the BIM methodology, and the building will be in Poland, in the Poznań city on J. Rychlewski Street. BIM-related goals include reducing the risk associated with the project’s execution, improving the management of the facility’s equipment, enhancing communication between all parties involved in the project, ensuring high-quality project documentation, and increasing the efficiency of construction work through quick access to up-to-date information contained in the BIM model. The scope covered by the created classification includes the building structure (Figure 19). The building consists of five floors, with the lowest floor being an underground garage. The reinforced concrete monolithic structure is designed in the shape of a square. A BIM model has been created to represent the realistic features and dimensions of the building under construction. Frakon Construction & Engineering Consulting was responsible for the construction model.

The work on automating the verification of the information content in the model was based on an IFC file exported from native software, which is an open data standard independent of the software used. The IFC format is one of the OpenBIM standards, as is IDS. OpenBIM extends the benefits of BIM by improving the accessibility, usability, management, and sustainability of digital data in the construction industry. The fact that a standard is open is evidenced by access to its documentation, exemption from usage fees, and a lack of association with a specific software vendor. To be considered an open standard, it must be based on the ISO norms.

3.1.3. bSDD Assigning in Blender

With the bSDD platform, we can connect not only during the creation of IDS files for automated model checking but also while creating the model and assigning it the appropriate properties. Native software is increasingly incorporating this functionality, one example being Autodesk Revit. An interesting solution for implementing bSDD and IDS is the Blender program combined with the available Bonsai plugin. This software is completely free and continuously introduces improvements to its functionality. It allows users to search for a dictionary from the database, activate it, and then add classifications based on it (Figure 20).

In the active dictionary, you need to search for the appropriate class—you can filter them by the corresponding IFC type and specify whether to search for properties only from IFC or custom ones. Then, you can open the edit for the selected class—this will display the properties defined in the dictionary, grouped into property sets, along with specific lists of valid values (Figure 21). After filling in the empty values, such classification references can be saved for the selected objects from the model. This application can also be useful for the reclassification of models received from external companies or from the contracting authority during the development process.

3.1.4. Quality Control of BIM Model

A key moment demonstrating the result of automating the exchange and verification of information in projects based on BIM methodology is the process of IFC model quality control. Various programs are available to enable this process. This is also possible with the previously described Blender software v.4.2, along with the Bonsai plugin. In the program, we specify the source for the IFC model, select the option to generate a report, and enable the ability to flag faulty elements that do not meet the set requirements and upload the previously created IDS file with information exchange requirements. We initiate the testing of the IFC model, and as a result, we receive a list of specifications with a pass or fail status in the program, as well as reports, in this case, in the HTML and ODS formats. In the HTML report, the fulfillment status of the requirements is presented both numerically and as a percentage—summarized for all specifications and for each one individually. We can expand the list of elements that are being verified in the model in relation to the set requirements (Figure 22).

If an item does not meet the requirements, it can be marked in the model, which makes it easier to locate (Figure 23). In addition, we can see its ID, so there is no possibility of misinterpretation, and we can easily edit an incorrect object to meet the requirements. Failed entities can be exported as BCF files.

The same process can be conducted in BIM Vision using the IDS Checker plugin, BIM Collab Zoom, or Solibri Office (Figure 24). Once the IFC model has been uploaded to the software, we also upload the IDS file. We proceed through the model-checking process, in which we obtain the status of the requirements. An element with incorrectly entered information is highlighted in red in the model. Comments can also be created here in the BCF file and assigned to specific people responsible for this scope.

In both cases presented, the same IDS file was used. There was no need to create separate requirements for each program, and the verification process required only a few seconds. The IDS automatically searched the model for information content and provided details on the errors found in the model. This file can be shared with any participant in the investment process. The recipient is not required to interpret the classification requirements, but simply uploads the provided file into the appropriate software and corrects the identified errors. In addition, if the receiver of the IDS does not have paid the software that allows the implementation of this file, he/she can download the Blender software free of charge, in which he/she will open the IFC model and automatically verify its information scope.

4. Discussion

IDS and bSDD significantly impact the automation of information exchange and verification in projects by utilizing predefined data, enabling quick updates, and linking them with other data [21]. Both elements are based on OpenBIM and have the potential for rapid development, especially when combined with the IFC standard. As a result, external orders or internal tasks have the potential to precisely define the requested product, which accelerates the entire process carried out according to the BIM methodology by reducing the number of questions regarding ambiguous requirements and eliminating the need to constantly send feedback on the model. However, it is important to note that the IDS standard will not be suitable for model verification in the native format, which can also be considered a disadvantage. Nevertheless, an increasing number of contracts require a file to be submitted in addition to the native format and also in the open IFC format. Thus, the bigger barrier seems to be learning and knowing how to correctly export the model correctly [22]. Both files can be used on the developer’s side as an attachment to BIM documents, as well as on the construction site or during the tender process.

Currently, most requirements are delivered in paper or digital formats, such as PDF or Excel files. With such requirements, there is not much that can be done beyond reading them. Human interpretation is required, and humans are prone to errors. Unlike traditional formats, digital IDS and bSDD files are interpreted by computers, resulting in added value and usefulness. The long standardization process may be considered an obstacle, but with an approved final version of the IDS available, the problem seems to be solved. In the case of geometry verification, dedicated software is still required, as the IDS only verifies informational specifications.

Metrics to measure the effectiveness of introducing the IDS standard in conjunction with the bSDD service for automating information exchange include the following:

• acceleration of individual designing and construction works—once the classification has been transferred to the bSDD form, parameters in the model can be quickly added and completed, and through the use of BIM models, staff can propose optimized ways of making a component. Making changes and optimizations to the BIM model is faster than with CAD drawings, and with the use of IDS it is possible to find specific elements in the model that do not meet the information requirements set,
• construction meeting time—we find incorrect data in the model with the help of the IDS standard and export it as BCF files. The number of errors can be counted and reported directly in the meeting and easily shared on the CDE platform, where collaboration takes place,
• as-built documentation preparation time—based on the BIM models received from the specialist contractors created on the basis of the provided requirements, the general contractor can prepare as-built documentation by completing the individual parameters with the help of bSDD,
• number of requests for information—the generation of unambiguous definitions and rules to check the information content of the BIM model reduces the number of requests related to the interpretation of the requirements clauses. Traditionally, information requirements have been communicated through non-computer-interpretable formats,
• software cost—the platforms shown in the article, such as usBIM from ACCA or the Blender software, are free solutions,
• international development of BIM—the introduction of structured standards helps to develop the implementation of the BIM methodology in the country and brings lonely BIM to a higher level of collaboration and communication,
• office waste volume—the creation of digital classification and digital information requirements reduces the amount of paper used, which contributes to reducing the carbon footprint.

Even though IDS has been an official standard for a relatively short time, many companies have already been successfully using it [23]. Although these are still tests that have not yet been implemented in real-world projects, we are close to practically utilizing the entire information flow within the openBIM framework. This article demonstrates the possibility of creating IDS and bSDD files in tools that are based on filling out specific fields and their interconnections, as well as their practical use in the process of verifying the informational content of BIM models. A significant advantage is that programming and expert skills are not required. These tools, based on filled-out fields, automatically generate code in JSON (for bSDD) or XML (for IDS). No specialized software is required to create both files; they can even be created in a text editor, although in that case, the user needs to know the respective coding languages.

5. Conclusions

What certainly needs development is the ability to import IDS and bSDD into native software to allow their implementation during the modeling process. In the future, both IDS and bSDD could become the primary source of classification for designers—once a bSDD file is uploaded into the software, it will prevent the selection of incorrect parameters for modeled components. The importance of data dictionaries stems from the fact that local industry-specific parameters are always required despite the ongoing development of the IFC standard. For example, in construction—the net surface area of a wall can be interpreted in different ways: by multiplying the length by height, subtracting the openings for doors and windows, or additionally considering the openings for installations. The same applies to the chosen units for accurate quantity takeoff, accounting for information relevant to cost estimation. It is impossible to describe all cases globally. Time demands quick action, and for cost reasons alone, companies cannot afford to wait for new IFC classes inefficiently, while bSDD refers to this standard wherever possible. By design, dictionaries are free and publicly available to enrich the models. This ensures that users always have access to the latest standards compiled in a single database. The same applies to the importance of IDS—a format readable by both humans and computers, leaving no room for misunderstandings. By adopting open standards, teams can improve communication, increase work efficiency, and ensure continuity in data exchange. IDS and bSDD complement the widely used open IFC format, which addresses the issue of purchasing both the right hardware and software to work with native files from various sources. It also resolves the problem of purchasing software to control model quality in terms of informational content.