Exchange Information Requirements: What is EIR in BIM?

The EIR, acronym for Exchange Information Requirements, is the document through which the client defines the information requirements to be produced, exchanged, and verified within a BIM process.

The BIM methodology presupposes a collaborative workflow and the creation of information models rich in graphic and textual data that characterize all the elements belonging to the model, for its entire lifecycle.

The information package that characterizes each model is outlined by the client’s needs, who has the responsibility and capability to define, upstream of a project’s design, what information is useful, how it should be exchanged, and when this should occur. There are innovative BIM IDS tools that allow, through the IDS standard, to properly set the EIR and to manage the entire process of creating, compiling, and validating the information request.

But first, let’s discover what the EIR (Exchange Information Requirements) is, what it consists of, and how it can be made even more effective through the IDS standard. We will also see a practical example of validation of an IFC model, in which an informational requirement of the EIR is transformed into an IDS specification to automatically check the correct nomenclature of the project.

Finally, we will analyze in detail a case study called Recycle BIM, an important multinational and multi-stakeholder initiative aimed at developing an integrated framework for the circularity of construction materials. This project has been led by the University of Minho and has seen several international collaborations, such as that of ACCA software.

EIR BIM model checking

What is an EIR (Exchange Information Requirements) document?

In a competition carried out according to BIM methodology, the EIR is a pre-tender document that defines standards, information, and requirements of a BIM process and constitutes the input to start the tender itself, to which technicians and contractors respond with appropriate offers.

If the PAS 1192-2 defined the EIR as “Employer Information Requirements”, today the acronym EIR refers to “Exchange Information Requirements,” as changed by ISO 19650.

The difference between the definitions underscores a clear change. While the informational requirements produced and delivered in both cases play a predominant role, the new meaning helps us understand that the focus is now rather on the method of exchanging this information.

The EIR therefore focuses on the methods to be performed for data sharing and the generation of documents, concentrating on the management of informational content among various stakeholders and on the methods of verifying, archiving, and delivering models. It constitutes a true textual document in which the following are identified:

• regulatory reference aspects, priorities, and objectives;
• models to be implemented for each design phase with levels of information appropriate to the reference step.

The objectives must be achieved through a collaborative effort from the various proposing teams, which includes contractors, technicians, suppliers, and any subcontractors and sub-suppliers, attainable with optimized data exchange and the use of a BIM management system.

Even today, it is still common to encounter proposing parties who have difficulty drafting such a document, sometimes because they have not fully embraced the methodology, and other times because it is often difficult to frame the project objectives, data exchange, and management.

What are the information requirements of the client?

We have seen that through the EIR, the client defines the management characteristics of the assignment, outlining the production and delivery process. But what are the specific information requirements that must be defined?

The information requirements to be defined are related to aspects such as:

• management methods (for example, the use of collaborative platforms);
• production methods;
• coordination methods between models and the team (use of BIM tools, coordinated model analysis, etc.);
• verification and control methods;
• level of detail related to the elements and in general to the specific model to be realized in each phase;
• exchange methods (for example, interoperable formats);
• timelines, deadlines, and delivery phases;
• delivery methods (output formats, file naming, etc.).

Information flow for drafting an EIR exchange information requirement

Why do we need an EIR document?

The Exchange Information Requirements (EIR) is a key document in the BIM methodology, because its purposes refer to the basic idea of BIM itself: “Begin with the end in mind”, according to which one must start any design with clear objectives in mind.

To effectively achieve the final objectives, the EIR is certainly functional as it identifies in detail the entire workflow to be followed, managing the entire construction process in advance.

An EIR is also advantageous for:

• the client as the creation of Digital Twin models that are realistic and rich in information gives the proposer a real view of the projects and allows them to evaluate a number of factors (construction phases, resources, costs and timelines, management and maintenance processes);
• designers and all collaborators as, through clear guidelines and workflows defined by the EIR, they become more productive, reduce errors, and avoid delays.

These advantages reach their maximum expression through the use of the BuildingSMART IDS standard. With an IDS BIM tool, the client can create the IDS document with the required information specifications, and the designer can edit them in a guided manner. When the designer completes the work, the computer automatically reads the designer’s model, and the client can validate the delivered datasets.

To better understand how these advantages can translate into tangible control of BIM models, it is useful to explore the role of the IDS: the standard allows transforming the information requirements defined in the EIR into structured specifications that can be automatically verified on IFC models.

How to transform EIR requirements into verifiable IDS controls on the IFC model

The IDS – Information Delivery Specification takes a further step beyond simple definition of information requirements: it allows transforming them into control rules applicable to IFC models. In practice, a request contained in the EIR, such as compliance with a certain nomenclature or the presence of specific properties, can become a structured rule to apply to an IFC model to verify its compliance.

The operational flow is simple: first, the information requirement to be checked is identified, then it is defined which elements of the IFC model the verification will apply to through applicability, finally, the actual requirement is set, i.e., the condition that the selected elements must meet to be considered compliant.

In this way, the EIR establishes what needs to be verified, while the IDS defines where to apply the control and which condition must be met. The final validation on the IFC model returns a result of compliance or non-compliance, allowing the client to verify whether the requested information is indeed present, correct, and consistent in the delivered BIM model.

Operational example: verifying the project name in an IFC model

To understand how the IDS works, let’s imagine we need to validate an architectural information model of a school building designated as a nursery, exported in IFC 4×3 format.

The client requests that the project name is uniform across all delivered IFC models. This requirement, expressed in the EIR, has a practical purpose: to ensure consistency in file nomenclature and make the data more easily consultable, aggregable, and usable by stakeholders and IT tools during the various phases of the life cycle of the building.

In the case study, the requested name for the project is “Rainbow Kindergarten”. The information requirement can therefore be expressed as follows: all delivered IFC models must have a project name consistent with this value.
At this point, the requirement must be transformed into an IDS specification. The specification should not generically check the entire model, but should identify the correct IFC entity on which to apply the check. Since the control pertains to the project as a whole, the applicability is set on the IfcProject entity.
The requirement, on the other hand, consists of verifying that the Name attribute of the IfcProject entity is populated with the expected name, which is “Rainbow Kindergarten”.

In this way, a request that in the EIR could be described in a discursive manner is transformed into a technically controllable rule.

How to set the IDS specification for name control

In the IDS file, a specification is created dedicated to verifying the project name. The description of the specification clarifies that the IFC model must present a nomenclature consistent with what is required by the client, in order to ensure uniformity among the various files produced and facilitate data analysis.

In the general section of the specification, the reference IFC version can be indicated, for example, IFC 4×3, along with any operational instructions for the designer. For instance, it can be specified that those exporting the IFC model must ensure that the project name is correctly filled in before delivery.

The decisive part is the applicability configuration and requirements. Applicability filters the entity IfcProject, while the requirement checks the value of the Name attribute. In our example, if the found value corresponds to “Rainbow Kindergarten,” the check is passed; if the value is absent or different, the model is non-compliant with that specification.

This setup clearly illustrates how the IDS allows transforming an information requirement from the EIR into a precise verification on the IFC model.

Validation of the IFC model: how to read the outcome of the check

Once the IDS file is created, the specification can be applied to the IFC model through a validator. The validator compares the contents of the model with the rules defined in the IDS file and returns an outcome. In the case of the example, the check concerns a single requirement: to verify that the project name associated with IfcProject matches the required value.

If the Name attribute contains the value “Rainbow Kindergarten,” the model is compliant with the specification. If, however, the value is absent, wrong, or different from the expected one, the validator indicates a non-compliance. The operational value of the IDS validation lies not only in indicating whether the model is correct or not but also in making traceable the reason for any error.

The validator can indeed show:

• the specification that has not been respected;
• the involved IFC element;
• the expected requirement;
• the value actually found in the model;
• the non-compliance report.

This enables the designer, BIM specialist, or validator to quickly identify the problem and intervene in a targeted way, without having to manually check the entire model.

From error to correction: why the IDS simplifies quality control

In a traditional process, verifying the data contained in a BIM model can require lengthy manual checks that are subject to different interpretations. With the IDS, however, the control is formalized upstream and applied consistently to the IFC model.

If the model does not comply with the specification, non-compliance becomes immediately identifiable. This allows for more effective management of the problem: the team can correct the value in the model, re-export the IFC file, and repeat the validation until the required compliance is achieved.

In an openBIM flow, reports can also be shared through standard formats such as the BCF – BIM Collaboration Format, facilitating communication between the parties involved in the model review.

Why use the IDS alongside the EIR?

The IDS does not replace the EIR but makes it more effective from an operational standpoint. The EIR establishes which information is necessary, in which phase it must be produced, and what criteria it must meet. The IDS allows translating these criteria into automatic checks applicable to IFC models.

The result is a clearer and verifiable process: the EIR defines the information requirement, while the IDS transforms it into a structured, machine-readable specification suitable for automated validation.

In this sense, the IDS represents a fundamental tool for making the informational quality of BIM models more controllable. It allows checking not only the presence of the requested data but also their correctness, consistency, and usability in subsequent design, construction, management, and maintenance processes of the work.

What should an EIR contain?

There are several documents that contribute to the Exchange Information Requirements and assist in its drafting:

• OIR (Organizational Information Requirements) – includes the information necessary to define the objectives of the proposing entity;
• AIR (Asset Information Requirements) – includes the management aspects and technical procedures of the property;
• PIR (Project Information Requirements) – includes the information necessary to implement the objectives related to the specific project.

To fully frame the EIR within a BIM project, simply refer to ISO 19650-1, which defines the flow and hierarchy of information requirements that develop in a BIM process.

The project is completed with the drafting of:

• PIM (Project Information Model) – includes information related to the design and construction of the building;
• AIM (Asset Information Model) – includes information related to the use, management, and maintenance of the property.

Here we have listed a series of acronyms that may seem difficult to you. For this reason, I recommend reading the article “IFC, PAS, COBie, BEP, EIR: all the BIM acronyms” to learn more about these and other acronyms you will encounter along your journey in the BIM world.

Hierarchy information requirements

To correctly draft the EIR, it is necessary to follow a template that is divided into three parts:

1. Technical;
2. Management;
3. Commercial.

Each part consists of a series of typical contents, outlined in the table below:

Technical Part

In this part, the technical requirements of the project are framed:

• exchange formats – the file formats (possibly including versions) to be used for data exchange, so that everything occurs in a format usable by the proposing party itself;
• level of detail – for each model and each technical element of each model, the minimum geometric and informational level of detail to be achieved must be defined based on project requirements;
• software platforms – the software infrastructure and collaborative platform of the project must be clarified;
• coordinates – identify a common coordinate system for everyone, because project models must have the same coordination point;
• level of training – the client must define the necessary BIM training to participate in the drafting of the offer and in the signing of the possible assignment.

Management Part

In this part, the management requirements for project processes are outlined:

• standards – procedures to follow to ensure the correct flow of information, data exchange, delivery, and process security;
• roles and responsibilities of stakeholders – it is advisable to prompt bidders to indicate all roles and responsibilities of the participants in the design;
• data security – security measures to protect sensitive data;
• coordination process – methods of control and resolution of interferences, tolerances, etc.;
• collaboration process – the collaborative methods that the team must follow should be clarified;
• scheduling model review meetings – control and support program for the design team during the execution of the assignment;
• management of design health and safety – design requirements related to safety on site to be ensured;
• constraints – to communicate any constraints or limitations present in the assignment;
• compliance plan – related to defining methods to ensure the quality of the information and data produced;
• method of delivering information on assets – to define a minimum standard and the data schema through which to manage the information in the asset.

Commercial Part

In this part, the requirements related to the purposes and project objectives are listed:

• strategic objectives – purposes of the informational requirements;
• BIM results to achieve – must define in detail the results to be attained, in terms of modeling, computerization, and coordination;
• skills assessment – through which the capabilities and skills of the bidders in information management and exchange are analyzed.

How is an EIR different from a BEP?

EIR and BEP are both necessary documents during a BIM assignment but differ in purpose:

• the EIR serves to identify the information needs and requirements requested by the client;
• the BEP serves to indicate how to respond to the needs expressed in the EIR.

Thus, in the realization of a BIM design, the production and exchange of information defined by the EIR enables bidders to draft the BEP (BIM Execution Plan).

The BEP (BIM Execution Plan) highlights the methods and tools aimed at reaching the objectives required by the EIR. Based on the phase in which one is located, two BEPs are drafted: the pre-contractual one (preBEP) and the post-contractual one (BEP).

Diagram illustrating a BIM development order workflow

The BEP pre-contract is drafted during the offer phase (pre-tender phase) by each participant.

For this reason, it outlines how the needs of the client will be addressed, planning the main “steps” of the design to be carried out (in the form of PIM – Project Information Model) and focusing on their level of expertise, operational capacity, resources, and technologies available.

At the conclusion of the tender, the winning entity, following the signing of the contract with the proposing entity, must present another plan, the BEP post-contractual.

If the preBEP was somewhat an offer, the BEP post-contractual frames the actual methods of execution, control, exchange, and sharing of the final documents and models to be produced. It is enriched with documents such as the responsibility matrix, the MIDP, the TIDP, detailing the management of procedures, processes to follow, delivery strategies, and standards.

In conclusion, it can be stated that it is precisely with the BEP that all actors in the process understand the purposes and uses of the BIM model, defining an efficient, functional, and compliant proposal to the standards.

Case study: the drafting of the EIR in the RecycleBIM project

The construction sector faces significant challenges in terms of productivity and predictability, often stemming from fragmented planning and reactive information management.

To overcome these difficulties, it is essential to adopt a proactive approach to information management, in line with ISO standards.

In this context, the Exchange Information Requirements (EIR) emerge as crucial tools for efficient information management throughout the entire lifecycle of a project, from its conception to demolition.

In this paragraph, we will detail a case study in which ACCA software is actively involved. This is the RecycleBIM project, an important initiative to promote sustainability and the circularity of construction materials through the advanced use of BIM.

If you want more information, I recommend reading the in-depth article “RecycleBIM: a step forward towards the circularity of construction materials.”

Thanks to this project, it has been possible to investigate procedures aimed at improving the management of building materials, reducing environmental impact, and promoting more efficient and sustainable building practices.

Regarding the drafting of the EIR, the case study included the creation of two templates, one related to the demolition of an existing asset, the other to be used in the case of a new construction.

The two templates are indicated as follows:

• track: to-be-demolished;
• track: new construction.

Let’s examine them in detail.

EIR for demolition: “track: to-be-demolished”

Although BIM is not yet widely used in demolition projects, the compilation of an EIR remains crucial to ensure a structured approach and minimize resource waste. A well-defined EIR helps streamline processes, reduce redundancies, and ensure that all relevant data is accurately captured and shared among stakeholders.

The EIR for demolition focuses on a series of specific objectives, including:

• planning a lean demolition to promote the circularity of materials;
• increasing sales of recovered materials, creating new business opportunities;
• optimizing work planning, reducing project time and costs;
• facilitating data exchange with the market, creating an efficient flow of information between supply and demand, to avoid “information waste” and to provide a justified application of BIM;
• clarifying objectives, outlining the necessary information and specifying information standards, production methods, and applicable procedures during the pre-demolition phase and dismantling planning;
• using templates aimed at systematically capturing and exchanging critical information regarding materials, structural elements, and site conditions during the demolition process;

A key element in the EIR for demolition is the Deconstruction Information Model (DIM), a data model specific to the planning and execution of demolition projects.

EIR model for demolition and dismantling projects

Let’s see how an EIR is structured to manage demolition processes.

1. Introduction

1.1. Purpose of the Exchange Information Requirements (EIR) – explains that the Exchange Information Requirements (EIR) have been formulated by the contracting authority for the project in question.

1.2. Information management objectives – illustrates the client’s objectives regarding project information management and their commitment to using BIM to improve demolition procedures, with the intent of achieving economic and time benefits and adopting a dismantling strategy oriented towards the circularity of materials.

1.3. Project information

1.3.1. General project information – provides basic details about the project (project title, description, project start date, etc.).

1.3.2. Contact details of the contracting authority – lists the contact information of the organization that commissioned the project (company name, website, address, etc.).

1.3.3. Details of the constructed asset – describes the building or existing structure that will be demolished (asset description, asset owner, etc.).

1.3.4. Purpose of the project – defines in detail what is intended to be achieved with the project (project justification, deliverables, etc.).

1.3.5. Project constraints – identifies all limits and restrictions that affect the planning, design, and execution of a construction project (budget, personnel, etc.).

1.3.6. Milestones for information delivery – defines the crucial moments during the project when specific information needs to be delivered.

1.3.7. Reference information – lists the information about the asset that is made available to the tender participants. The location of this information is indicated, specifying that it will be accessible via links to the shared data environment (CDE) (as-built drawings, project drawings, cadastral data, etc.).

1.3.8. Shared resources – similarly to the previous section, this lists other resources that are made available to participants via links to the CDE (process maps, specifications of the level of information need, etc.).

2. Information requirements

This section defines the information requirements necessary for the delivery of the demolition information model. These requirements are the result of broader business strategies and the specific needs of the project, and they are communicated to the work team through the EIR (Exchange Information Requirements). The Figure 1 illustrates the hierarchy of information requirements, which starts from the OIR (Organizational Information Requirements), passes to the PIR (Project Information Requirements), and culminates in the definition of the EIR, culminating in the definition of specifications for the PIM (Project Information Model).

Figure 1 – Hierarchy of information requirements, adopted by ISO 19650

2.1. Organizational Information Requirements (OIR)

The OIR (Organisational Information Requirements) represent the high-level information needs of the commissioning organization and are aligned with its ESG (Environmental, Social and Governance) policies. They define the guiding principles for information management at the corporate level, influencing all projects. In this context, the OIR highlight the importance of:

• decommissioning and demolition of assets with minimal environmental impact – this implies the need to plan interventions that minimize waste production, promote the recovery and recycling of materials, and consider the safety and health of the surrounding community. For example, an OIR could establish the goal of achieving a certain percentage of recycled materials from the demolition process;
• compliance with national regulations and promotion of circularity – the organization must operate in accordance with existing laws and regulations regarding demolition and waste management, while also integrating practices that promote the circular economy, such as reuse and valorization of materials. An example could be the obligation to identify reusable materials present in the building before demolition;
• adoption of a comprehensive strategy for project planning and execution – it is essential to define a structured approach for information management throughout the entire project lifecycle, from the planning phase to its conclusion. This may include the use of collaborative platforms and the definition of clear workflows.
• selection of demolition and decommissioning techniques based on optimized models – the use of informational models (BIM) allows for the simulation and analysis of different demolition techniques, choosing the most efficient, safe, and sustainable ones. For example, the BIM model can be used to plan the sequence of disassembly of structural elements.

2.2. Project Information Requirements (PIR)

The PIR (Project Information Requirement) specify the high-level informational content required specifically for the project in question, in order to support the strategic objectives of the commissioning organization. These requirements are a derivation of the OIR, adapted to the peculiarities of the individual project and its key decision points.

Four distinct key points are identified (Table 1) within the process of creating the Project Information Model (PIM) for demolition planning:

• Delivery of a spatial representation of the asset (M1): for example, the point cloud obtained from laser scanning;
• Delivery of the materials inventory resulting from the pre-demolition audit (M2): the detailed list of materials present in the building;
• Delivery of the BIM model, representing the asset (M3): the informative 3D model of the building;
• Delivery of the asset specifications in an interoperable data format for marketplaces (M4): the data on materials structured in a format usable for online sales.

Table 1 – Project Information Requirements (PIR) – (Source: University of Minho)

2.3. Exchange Information Requirements (EIR)

The EIR (Exchange Information Requirements) is a crucial document that ensures alignment among all project stakeholders and facilitates effective information management throughout the entire lifecycle. It establishes a common understanding among the parties involved, promoting collaboration, clarity, and efficiency in data exchange.

The Table 2 details the information requirements for delivery. For each information requirement (corresponding to the milestones), the table specifies a series of information (the necessary supporting information, the required file format, etc.).

Table 2 – EIR decomposition – (Source: University of Minho)

The Table 3 defines the milestones for the delivery of information and the key dates associated with each deliverable.

Table 3 – Information delivery milestones and key dates – (Source: University of Minho)

The document also specifies that by a deadline all stakeholders can submit questions regarding the EIR. In response to the EIR, each participant in the tender must produce a pre-BEP (pre-BIM Execution Plan), which outlines their approach and information management capabilities to meet the requirements. The pre-BEP must be signed by the established date and will be subject to review before acceptance.

The appointed parties are required to develop a detailed pre-BEP that includes a range of information (the information delivery strategy, collaboration strategy, etc.).

After the appointment, the delivery team’s BEP will be validated in collaboration with the entire team, taking into account feedback from the contracting authority. The final BEP must be signed by the established date and will contain information similar to the pre-BEP but with more details such as the MIDP (Master Information Delivery Plan) and TIDPs (Task Information Delivery Plan), in addition to any deviations from the EIR.

2.4. Level of Information Need

The specifications of the LOIN (Level of Information Need), compliant with standard EN 17412-1:2020, are fundamental elements of the information requirements defined by the contracting authority and must be adhered to during information delivery. These specifications must be included in the BEP (BIM Execution Plan) as a reference to define the informational content related to the constructed asset and its components, such as construction products.

3. Information Standards

Projects must follow specific information standards to ensure effective information exchange with other technologies, favoring open data formats:

• adhere to ISO 19650, CEN/EN 17412-1 / ISO 7817, and ISO 16739-1 standards;
• use EWC codes for waste classification;
• use Uniclass and ISO 16739-1 classes for structuring and classifying information;
• units of measurement refer to the International System if not indicated;
• it is essential to adopt standardized conventions for file identification (naming convention with Project Name, Originator, Break-down, etc.);
• files must include a metadata field, managed through the common data environment (CDE).

Information Production

• the delivery team must specify in the BEP (BIM Execution Plan) the authoring software and its version;
• data must be provided in both proprietary/editable format and open data format (e.g., IFC for BIM models);
• the maximum size for individual files is 300 megabytes;
• the platforms used by the client are indicated, and the delivery team must specify how it intends to exchange information with them if it uses alternative software;
• information management functions are a shared responsibility among all team members;
• the document defines the responsibilities of the various parties at the different stages of the information production process;
• the phases of survey of the asset, BIM modeling, and data parsing for the marketplace are described;
• an authorization and information publishing process is defined, which includes initial and technical review, authorization, etc.;
• a spatial coordination strategy and an information breakdown structure are required, to be detailed in the BEP.

Acceptance Procedures

• published files are subject to validation and acceptance procedures at each significant milestone;
• acceptance depends on the compliance of each individual deliverable with the defined criteria, which may relate to geometric aspects, alphanumeric data, and documentation;
• the client aims to automate the acceptance of work results through machine-readable checks and data specifications;
• specific acceptance criteria (AC) for each deliverable identified in the EIR breakdown tables are listed.

EIR for new construction: “track: new construction”

The EIR for new construction aims to integrate sustainability and circularity considerations from the early design stages. The most important aspects are outlined below:

• optimization of material selection, operational efficiency, and a low-cost end-of-life phase for the project;
• the characteristic differences compared to the EIR for the “to-be-demolished” track, as the EIR is a document compiled from the EIR for specific deliverables;
• a conceptual BIM model to allow iterative analysis of the energy efficiency of the building envelope, material composition, and other aspects;
• specific information needs for the as-built model, which will then be used to plan demolition work for the asset. This model must include the information necessary for the DIM;
• additional requirements for a BIM model that reflects the changes made to the constructed asset during its use and maintenance period;

1. THE SCOPE OF THE EIR

In a construction project (“track: new construction”), there are many phases and potential uses of BIM throughout the project lifecycle, including planning, construction, operational management, and maintenance, and finally demolition.

Considering this, the scope of this EIR includes only the characteristic differences compared to the EIR for the “track: to-be-demolished” and therefore the information requirements established in this document can be integrated into the EIR when executing a project using BIM methodology.

2. KEY PROVISIONS OF THE EIR

2.1. Purpose of the information requirements exchange The EIR – establishes the information needs to be met in the design and construction phases;

2.2. Objectives and purposes of information management – the client commits to using Building Information Modeling (BIM) for this project;

2.3. Milestones for information delivery – are established considering various factors and the key distinguishing points adopted are:

• M0 – Project start;
• M1 – Start of preparation;
• M2 – Start of conceptual design;
• M3 – Start of detailed project development;
• M4 – Start of detailed technical design, construction, and fabrication;
• M5 – Start of on-site work;
• M6 – Start of asset delivery;
• M7 – Delivery of the asset and start of operation and maintenance;
• M8 – Start of end-of-life phase.

2.4. Project Information Requirements (PIR) – specify the informational content needed to support the contracting authority’s strategic objectives and derive from the organization’s strategic objectives and the project’s key decision points.

Table 4 identifies the high-level project-specific information requirements for each key delivery point.

Table 4 – Project Information Requirements (PIR) new construction – (Source: University of Minho)

Table 5 represents the information requirements for the delivery parties.

Table 5 – EIR new construction – (Source: University of Minho)

2.5. Level of Information Need (LoI) – these are essential components of the information requirements, formulated by the client and binding for the delivery of information.

2.6. Project Information Standards – information must be produced in accordance with the project information standards to ensure effective exchange with other technologies, using open data formats as much as possible.

2.7. Software and Information Authoring – the delivery team must specify in the BEP the authoring software and its version for all information containers.

2.8. Information Creation and Collaboration Process – the native model and interoperability guidelines should facilitate the creation of models in the IFC schema.

2.9. Acceptance Criteria and Quality Control Procedures – after each phase of information generation, an acceptance/rejection process for each individual deliverable and compliance with specifications is expected.

2.10. Supporting Information and References – it is advisable to consult the supporting material made available to the client.

FAQ on EIR in BIM

What is the EIR in BIM?

The EIR, which stands for Exchange Information Requirements, is the document by which the client defines the requirements related to information exchange in a BIM process. It serves to clarify what information must be produced, how it should be shared, in what formats, and with what verification and delivery methods.

What is the purpose of an EIR document?

The EIR serves to correctly set up the BIM workflow from the early phases of the construction process. It allows the client to define goals, requirements, data exchange methods, control criteria, and delivery timelines, helping designers and collaborators to work with clearer rules and reducing errors, delays, and informational inconsistencies.

What informational requirements must the client define?

The client must define requirements related to the management, production, coordination, and verification of models. These include the use of collaborative platforms, interoperable formats, levels of detail, delivery methods, file nomenclature, deadlines, and control procedures.

How can the IDS support the EIR?

The IDS allows transforming the informational requirements defined in the EIR into structured specifications, readable by both people and software. In this way, a request from the client can become an automatically verifiable rule on an IFC model, making information control more objective and traceable.

How do you transition from an EIR requirement to IDS control?

The transition involves first identifying the informational requirement to be controlled, then the elements of the IFC model to which the verification will be applied, and finally the condition that must be met. The EIR then establishes what needs to be verified, while the IDS defines where to apply the control and which requirement must be satisfied.

What happens if an IFC model does not comply with a specific IDS?

If the model does not comply with the specification, the validator reports a non-conformity. This way, the team can identify the unmet requirement, the involved IFC element, and the found value in the model, then intervene to correct the data, re-export the IFC file, and repeat the validation.

What should an EIR contain?

An EIR contains technical, managerial, and commercial requirements. The technical part concerns aspects such as exchange formats, levels of detail, software platforms, and coordinates. The managerial part includes standards, roles, data security, collaboration processes, and compliance plans. The commercial part defines strategic goals, BIM outcomes to achieve, and skills evaluation.

What is the difference between EIR and BEP?

The EIR defines the needs and informational requirements requested by the client. The BEP, which stands for BIM Execution Plan, instead describes how the team intends to respond to these requests. In summary, the EIR establishes what the client needs, while the BEP indicates how to fulfill those requirements.