| Section | Purpose | Must Contain | Tip |
|---|---|---|---|
| 1. Project Information | Context | Project name, location, scope, programme, key dates, value | Brief — 1 page |
| 2. Information Standards | Which standards apply | ISO 19650 parts referenced, classification system (Uniclass/OmniClass), file formats, software versions | Cite by year |
| 3. Information Production Methods & Procedures | How information is to be produced | CDE platform, naming convention, model authoring rules, federation protocol, clash protocol | Allowed to defer 'how' to BEP — but state the platform |
| 4. Information Containers Required | What deliverables are expected | List of model files, drawings, schedules, reports per discipline per stage | Specific — not 'all design info' |
| 5. Information Acceptance Criteria | How will containers be checked | What checks, by whom, against what criteria | SMART criteria — measurable |
| 6. Information Delivery Milestones | When must containers be delivered | Milestone dates tied to project programme stages | Match RIBA / IPA / Indian project stages |
| 7. Level of Information Need (LOIN / LOD) | How much detail per object per milestone | Table: object types × milestones × LOIN/LOD requirement | Cite framework (BIMForum / AIA / ISO 7817-1) |
| 8. Strategic / Asset Information Requirements | Link to OIR / AIR | Property data needed for operations (manufacturer, warranty, maintenance frequency) | Connect to FM system data structure |
| 9. Security | If ISO 19650-5 applies | Sensitivity assessment, security strategy, vetting requirements | Defence/critical infra/government MUST address |
| 10. Pre-appointment BEP Requirements | What you want in tender response | Required sections of pre-appointment BEP, page limit, evidence required | Helps bidders write a focused response |
| Section | Purpose | Must Contain | Tip |
|---|---|---|---|
| 1. Project Information & Acknowledgement | Confirm understanding | Acknowledge EIR; restate key parameters | 1 paragraph |
| 2. Proposed Approach to EIR | How bidder will meet each EIR clause | Section-by-section response to EIR Information Standards, Production Methods | Show familiarity, don't over-promise |
| 3. Project Team | Personnel | Named BIM Manager, Information Manager, key authoring leads — with CV references | Real people — not 'TBD' |
| 4. BIM Capability Evidence | Proof of capability | Past projects (similar scale + complexity), case studies, client references | 1-2 strong projects beats 10 weak ones |
| 5. Tools & Software | Technical stack | Authoring tools, CDE platform, coordination tools — with versions | Match what's in the EIR if specified |
| 6. Mobilisation Plan | What you'll do in Activity 5 | How CDE will be tested, when training will happen, milestones | Shows you understand mobilisation matters |
| 7. Risks & Assumptions | Honest exceptions | Anything you cannot commit to without clarification, dependencies on appointing party | Better to flag now than dispute later |
| Section | Purpose | Must Contain | Tip |
|---|---|---|---|
| 1. Project Definition | Project info, parties, contacts | All appointed parties, RACI, contact directory | Update when team changes |
| 2. Information Production Methods | Detailed how-to | CDE setup, file naming, model templates, coordinate system, units, classification | Most disputes trace to this section being vague |
| 3. Common Data Environment (CDE) | Platform & workflow | Platform name, login process, folder structure, suitability codes, access matrix | Include screenshots |
| 4. Federation Strategy | How models combine | Federation tool, frequency, ownership, naming, who federates | Clear ownership prevents 'we thought you were federating' |
| 5. Clash Detection Protocol | How clashes are managed | Hard vs soft clash, severity, owner assignment, re-test cycle, exit criteria per milestone | Define 'acceptable clash count = 0' or define a tolerance |
| 6. MIDP | Master deliverable schedule | Aggregated TIDPs, dates, owners, recipients, format, review cycle | Live spreadsheet — not a snapshot |
| 7. TIDPs | Per-task schedules | One TIDP per appointed party / task | Append as annexes |
| 8. Information Authoring Standards | Modelling rules | Element naming, parameter list, classification mapping, view templates, sheet templates | Templates uploaded to CDE |
| 9. Software Versions & File Formats | Technical specs | Authoring versions (e.g., Revit 2025), IFC version (IFC 4 Reference View), exchange formats | Lock versions — upgrade only by amendment |
| 10. Roles & Responsibilities (RACI) | Who does what | RACI matrix for every key activity | Sign off in kick-off meeting |
| 11. Security | ISO 19650-5 if applicable | Built Asset Security Strategy + Security Management Plan | Sensitive projects only |
| 12. Archival & Project Close-Out | End of project | Archival policy, AIM handover, lessons-learned process | Activity 8 — don't skip this |
| Annexes | Supporting documents | TIDPs, model templates, naming convention quick-ref, classification mapping, clash matrix | Keep in CDE; reference by container ID |