| Term | Expansion | Definition | Example |
|---|---|---|---|
| OIR | Organisational Information Requirements | What the asset OWNER's business needs to know — the top of the requirements pyramid. Drives everything below. | Energy consumption per m² for ESG reporting; preventive-maintenance trigger frequencies. |
| AIR | Asset Information Requirements | What information is needed to OPERATE and maintain the asset day-to-day. Derived from OIR. | Equipment make/model, warranty dates, spare-part numbers, preventive maintenance schedule. |
| PIR | Project Information Requirements | What information is needed to DELIVER the project. Time-bound to construction milestones. | Cost forecast, programme dates, RFI status, design approval status at each gateway. |
| EIR | Exchange Information Requirements | What each appointed party must HAND OVER at each delivery milestone — the contractual deliverable list. Derived from PIR. | Architect issues IFC + DWG + room schedule at Concept Stage; structural engineer issues IFC + analytical model at Tech Design. |
| Hierarchy | OIR → AIR → PIR → EIR | Each layer is derived from the one above. EIR is what an appointed party actually contracts to deliver. | On a hospital project: OIR (lifecycle cost) → AIR (HVAC efficiency) → PIR (HVAC layout by Stage 4) → EIR (IFC at LOIN level X by Apr 2026). |
| Term | Expansion | Definition | Example |
|---|---|---|---|
| Appointing Party | — | The CLIENT — the party that issues the appointment. Was 'Employer' in old PAS 1192 vocabulary. | DDA, NHAI, MMRDA, the building owner, the developer. |
| Lead Appointed Party | — | The principal contractor / lead consultant — directly contracted to the appointing party. Owns the project's BIM execution overall. | Main contractor, lead architect, design-build consortium. |
| Appointed Party | — | Any party contracted (directly or via the lead) to deliver work — designers, contractors, subcontractors, manufacturers. | Structural consultant, MEP consultant, façade subcontractor. |
| Information Manager | — | Person in each appointed party responsible for BIM information management. Sometimes the same person as BIM Coordinator. | Manages CDE access, runs clash detection, validates IFC exports. |
| Term | Expansion | Definition | Example |
|---|---|---|---|
| BEP | BIM Execution Plan | The contract document that says HOW BIM will be done on this project. Two versions: pre-appointment (in tender response) and post-appointment (signed after award). | Lists CDE platform, file naming convention, LOIN per discipline, model federation strategy, software versions, clash protocol. |
| MIDP | Master Information Delivery Plan | The MASTER schedule of all information deliverables across all appointed parties. Owned by the lead appointed party. Aggregates all TIDPs. | Spreadsheet listing every deliverable with due date, format, owner, recipient, reviewer. |
| TIDP | Task Information Delivery Plan | The schedule of deliverables for ONE appointed party / ONE task. Multiple TIDPs roll up into the MIDP. | Structural engineer's schedule of model issues, drawing issues, schedule of materials. |
| BIMForum LOD Spec | Level of Development Specification | The most-cited LOD reference document, published annually by BIMForum (USA). Defines geometric and information requirements per object type per LOD level. | Concrete column LOD 300 = nominal size + position + concrete grade. |
| Term | Expansion | Definition | Example |
|---|---|---|---|
| CDE | Common Data Environment | The single trusted repository for all project information. Hosts every information container. | Autodesk BIM 360 / Construction Cloud, Aconex, ProjectWise, Asite, Dalux, Trimble Connect. |
| Information Container | — | A discrete chunk of information with a unique ID — a model file, drawing, issue, schedule, anything. Each has a state, revision, classification. | An IFC file, a Revit model, a PDF drawing, a clash report, a meeting minute. |
| WIP | Work In Progress | First state of an information container — being authored, NOT yet shared with others. Author has full control. | Architect's working Revit model — not yet pushed to the federated CDE. |
| Shared | — | Container has been checked, suitability assigned, and pushed for collaboration. Other parties can reference but not edit. | Architect's IFC export pushed to CDE for structural and MEP coordination. |
| Published | — | Container has been authorised by the appointing party as a contractual deliverable. Read-only. | Stage 3 Concept Design report — signed off and issued for client approval. |
| Archived | — | Container is preserved as a record (audit trail, project history). Read-only forever. | All published containers are archived at project close-out. |
| Term | Expansion | Definition | Example |
|---|---|---|---|
| LOD | Level of Development (AIA) | AIA-defined scale 100/200/300/350/400/500. Bundles geometric detail and information into one number. Most-cited globally. | LOD 100 = symbolic; 300 = accurate dimensions + grade; 400 = fabrication-ready; 500 = as-built verified. |
| LOIN | Level of Information Need | ISO 7817-1 / ISO 19650-1 concept that REPLACES single-number LOD with three independent dimensions: Geometric (G), Alphanumerical (A), Documentation (D). | A door might need rough geometry (G2) but rich properties (A4) and full warranty PDFs (D3). |
| AIM | Asset Information Model | The information model maintained during the OPERATIONAL phase of an asset. Built from the PIM at handover. | Facility manager's BIM with live equipment, sensor data, maintenance history. |
| PIM | Project Information Model | The information model produced during the DELIVERY (project) phase. Becomes the AIM at handover. | Federated model used by designers + contractors during design and construction. |