Exchange Information Requirements – planBIM

Amazing! Exchange Information Requirements – planBIM

Information about Exchange Information Requirements – planBIM

Phil Puccio

Most customers would likely have a clear idea of ​​what information they would like their respective project teams to receive during the deployment phase when quotations are being designed and calculated. They also likely know what information they will need upon handover to operate their newly completed building and get the most of it. Information exchange requirements or EIRs are the documents that set out these requirements.

In the recently published ISO document on BIM (ISO 19650), the term Employers Information Requirement is replaced by Exchange Information Requirement (commonly abbreviated as EIR). At the same time, the term “data” is replaced by the term “information” with various important sub-terms to define roles, tasks and responsibilities in relation to different types of information requirements in the AEC industry.

EIR is a document that gives clear instructions on the project to be carried out. It helps give bidders and construction teams a clear picture of the models required and defines the purpose of each model for the entire project. It also contains data that will help in clearly defining the information of the model to be created, the process for information development, the details of project management and delivery deadlines during the design phase of the project. Therefore, the EIR provides both parties, ie the construction team and its client, with enough information to answer a request for an offer or how the client intends to meet the project deadlines. The EIR also has a regulatory role as it ensures that information is provided and made available to all parties involved upon request.

There are various information requirements that help in creating and informing an EIR. The Organizational Information Requirements (OIR) help define what information is required to achieve an organization’s strategic goals in terms of business operations, asset management, etc. It describes the needs of an owner organization to manage its building portfolio and related services. Project Information Requirements (PIR) defines what information the client of a project needs from the delivery team. It describes the owner’s requirements for the management of a particular facility. It can refer to the details of the facility’s premises (the rooms that are functional within the building), the services (the operational and maintenance activities that take place in these rooms) and the equipment characteristics: type, location, maintenance needs, replacement time and Costs). Asset Information Requirements (AIR) Specifies the information to be provided by the project team in the project handover phase, mainly for the operation and facility management of the project. To summarize the various information requirements:

1. OIR (Organizational Information Requirement): To define the goals, needs and necessities of the organization.

2. AIR (Asset Information Requirements): Understand all required assets, their management and maintenance procedures.

3. PIR (Project Information Requirement): To agree which asset information should be delivered for the individual project milestones.

4. EIR (Exchange Information Requirement): Agreement on how the information is to be transmitted, in which format, at which level of information and definition of an agreement between the parties involved on how and with which functions they exchange their digital information have to.

An EIR is basically divided into three parts: Technology, Management and Commercial.

In the technical part, the software platforms section should communicate about the software versions. It clearly defines which software platforms the employer uses, e.g. B. Its Common Data Environment (CDE), BIM / CAD systems, etc. Data Exchange Formats defines the formats that are used to provide and exchange data throughout the project. The purpose of the coordinate section is to ensure the implementation of a unified coordinate system for all BIM data for consistency. The Level of Information Need (LOIN) section contains information about which LOIN is to be followed in general or for an individual component within the project.

In the management part, the Standards section defines the processes and procedures to be used for the management of the information flow, delivery and security of the project. The Stakeholder Roles and Responsibilities section provides clarity on the roles, responsibilities, and authorities of the various people working on the project. The coordination and collision detection process needs to be defined as it is carried out. The security part is intended to convey the customer-specific security measures that are required to secure the data.

In the management, the section data drops (information exchange) and project services are determined according to the work plan of the employer and via an identified gateway. The main purpose of this section is to communicate the content of these data drops. The Customer Strategic Purposes section defines the details of the expected purposes of the information provided in models. The Defined BIM / Project Services section contains details on specific BIM services, e.g. fully rendered animated model representations, 4D program models, fly / walk-through visualizations, solar impact analysis models. The specific requirements, phases and the level of detail / definition are also clearly indicated.

Hence, we can see that a customer’s commitment to the BIM process is undoubtedly important, but we have to take into account that not every customer is regularly and also technically involved in the construction process. Not every customer in the world is going to request BIM in the right way and with the right documentation, and if we expect that, we will get nowhere. Therefore, it remains important to educate customers about these issues so that they can get the most out of their projects.

An excellent solution to this could be to use some of the Plain Language Questions (PLQs) to help and interpret what information the customer expects or needs from BIM, which can then be worked out to create or develop an EIR .

To sum up, teams working without EIR will struggle to ensure that the right information is provided to the client and other contractors at the right time to aid their decision making, which would ensure a smoother workflow. Worse, they could create an inordinate amount of information just for their own sake rather than efficiently directing their focus to what is needed. planBIM is a great way to create EIRs and much more. Start exploring today and contact us to learn how!

Breaking Story – Exchange Information Requirements – planBIM

The Latest News on Exchange Information Requirements – planBIM

Original Source:
Category – BIM

© 2022 - WordPress Theme by WPEnjoy