[Translate to English:] AIR-to-EIR-to-BEP

© Alexander Gerger, Christian Schranz, Harald Urban


Development of open, modular, and automatable Employer Information Requirements (EIR) and BEPs

The authors of the bSAT BIMcert Handbook describe the Employer Information Requirements (EIR) and the BIM Execution Plan (BEP) as essential regulations for the execution of BIM projects. The EIR is the concrete description of the client´s information needs and is thus described as a requirement for the contractor. In particular, the EIR contains the BIM requirements, BIM processes, BIM deliverables, standards to be complied with, and BIM applications to achieve the client´s BIM objectives. The BEP builds on the EIR and concretises them in project-specific terms. The BEP provides the framework for the BIM services and defines the processes/workflows and the requirements for the collaboration of the individual participants (e.g., responsibilities). The BEP thus forms the basis for BIM-based collaboration in the project. 

However, synergies only arise when EIR, BEP, and the BIM model behind them are precise, free of contradictions, and, above all, machine-readable. However, this is currently rarely the case for EIR and BEP, as they are mostly text documents in natural language with individual content and structure. The aim of AIA4ALL is therefore to design EIR and BEP in such a way that the information requirements defined in them can be processed and checked largely automatically during a project. This is achieved by developing an open platform that provides the functionality to combine information requirements of specific use cases into machine-readable EIRs in a modular way.

The platform should offer the possibility to define the necessary content, processes, structures, phases, as well as roles and generate digital artefacts. The complexity lies in the translation of requirements (e.g., BIM for technical monitoring) into the digital artefacts (e.g., IFC property definitions, checking rules, and tool configurations).

A key aspiration of the platform is to create an open standard for the creation of EIRs. This includes the creation process on the one hand and the data formats provided on the other. Therefore, the project relies on the integration of buildingSMART standards and services. Interfaces to UCM (Use Case Management) and bSDD (buildingSMART DATA Dictionary) are intended to simplify the definition of the contents of EIR by allowing the integration of the information already available and tested there.  The IDS (Information Delivery Specification) data format serves as a machine-readable format for the information requirements in the EIR. IDS is intended to close the information gaps between EIR and authoring software as well as EIR and checking software.

Project partners

AIT Austrian Institute of Technology GmbH (Projekt-Lead)

Plandata GmbH

e7 GmbH

buildingSMART Austria