Yes, this glossary will help with all our terminology:
| Term | Description |
| AIDP |
Asset Information Delivery Plan MS project-specific document outlining the data requirements. |
| AIR |
Asset Information Requirements Typically, a register defining the asset and information requirements of the Employer in relation to the assets it is responsible for. The AIR may be part of an EIR or a standalone document. |
| Asset | Used to identify and element or product usually defined by the Employer. |
| BEP |
BIM Execution Plan Document defining standard methods and procedures adopted during the contract in order to meet the objectives and requirements set out in the EIR. It is utilised following the appointment of project stakeholders, and in particular the main contractor. |
| BIM |
Building Information Model A process for creating, managing and sharing structured building information throughout the lifecycle of an asset, enabling better collaboration, efficiency and decision-making. |
| CDE |
Common Data Environment A process, which is often seen as a collaborative platform, for managing information which provides a single source of truth for any given project. It can be used to collate, manage and disseminate all relevant project documents for multi-disciplinary teams. |
| COBie |
Construction Operations Building Information Exchange Structured facility management information for the commissioning, operation and maintenance of a project. It is often in a neutral spreadsheet format that will be used to supply data to the employer or operator to populate decision-making tools, facilities management and asset management systems. It may also be used for data verification. |
| EIR |
Employers Information Requirements A document that specifies the information a client requires from a project team to support the delivery, operation and management of an asset. |
| LOD |
Level of Detail Description of graphical content of model elements at each of the stages defined by the BEP and NBS toolkit and the Master Information Delivery Plan (MIDP). |
| LOI |
Level of Information Defines the amount and quality of information required at different project stages. |
| MEPH | Mechanical, Electrical, Public Health |
| MIDP |
Master Information Delivery Plan MS project-specific documents also known as Design Management Workbook. It lists all of the required LODs. |
| Platform | The Glider Nexus software platform (formerly known as EDocuments or Springboard) |
| PIM |
Project Information Model Model/s developed throughout the project. May not yet contain all data requirements. |
| AIM |
Asset Information Model A model that complies with the data and information necessary to support asset management, providing all the data and information related to, or required for, the operation of an asset. An AIM can provide graphical and non-graphical data and information, as well as documents and metadata. Generated from information in a Project Information Model (PIM) that was created for the construction of a new asset, the AIM is managed within a Common Data Environment. It may also be referred to as an AIM CDE (Asset Information Model Common Data Environment). |
| SOMM |
System Operation & Maintenance Manual A collection all Operation & Maintenance (O&M) information, relevant materials or equipment, to make the platform function. |
| System | Systems are a group of products or materials that are interconnected and function together as a whole. e.g. MEPH system |
| Validation | A review to check that the content meets the requirements of the LOI (Level of Information). |
| Verification | A review to check that the content meets the need to satisfy the intended purpose. |
| Work package | Several systems or elements packages together under a single design or sub-contractor work package. |
