BEP & EIR — BIM Execution Plan / Exchange Information Requirements
EIR = client requirements (in tender). BEP = how the contractor will deliver them. MIDP/TIDP = the schedule.
BIM Execution Plan (BEP) and Employer's Information Requirements (EIR) are key documents in ISO 19650-aligned BIM management. EIR (Employer's Information Requirements) — set by the client/employer at project commencement; specifies what BIM information is needed throughout the project lifecycle. BEP (BIM Execution Plan) — prepared by the contractor/lead designer in response to EIR; describes how the BIM will be executed (tools, processes, deliverables, schedules).
EIR contents (set by client): (1) Project information requirements — what models, drawings, data needed. (2) Asset information requirements (AIR) — for facility management. (3) Software preferences and exchange formats (IFC, Navisworks). (4) LOD requirements at each project milestone. (5) Naming conventions and quality standards. (6) Submission schedules and review procedures. (7) Hand-over deliverables.
BEP contents (in response to EIR): (1) Team structure — designers, sub-contractors, BIM lead. (2) Software stack — authoring (Revit, Tekla), coordination (Navisworks, Solibri), CDE. (3) Modelling standards — naming, layering, parameters. (4) LOD progression schedule by discipline. (5) Coordination workflow — federation frequency, clash detection process. (6) Quality control procedures. (7) Information delivery schedule. (8) Risk register. The BEP is updated at major milestones; the EIR is typically static through the project. Indian best practice: EIR + BEP at project commencement for any project >₹50 cr; informal residential rarely formalises this. Major Indian government projects increasingly mandate ISO 19650-compliant EIR + BEP.
- Major commercial and infrastructure BIM projects
- Government and PSU projects with formal information management
- Pre-engineered industrial buildings
- Hospital and airport construction with complex MEP
- Major renovation projects