Chapter 11 focuses on the contractual and procedural documents that govern BIM collaboration. The most important of these is the Employer's Information Requirements (EIR) —a document prepared by the client (or the client's advisor) that specifies exactly what information must be delivered, in what format, at what milestones, and to what standard.
The EIR typically covers three categories: technical requirements (software versions, file formats, coordinate systems, naming conventions), management requirements (CDE protocols, review cycles, approvals process), and commercial requirements (deliverable schedule, liability, intellectual property). A well-written EIR is specific and measurable.
Not "provide detailed model" but "deliver IFC4 model at RIBA Stage 4 with Level of Information Need = 300 geometry and 350 attributes for all architectural elements." The counterpart to the EIR is the BIM Execution Plan (BEP) —the contractor's response explaining how they will meet the EIR requirements. The BEP describes the supply chain's capabilities, proposed software, responsibility matrix (who models what), clash detection strategy, quality assurance procedures, and resource plan. The BEP becomes contractually binding once accepted.
The chapter also covers the Responsibility Matrix (often called the "RACI chart"), which assigns each information task a status: Responsible (does the work), Accountable (signs off), Consulted (provides input), Informed (receives updates).
The authors emphasize that unclear responsibility assignments are a leading cause of BIM project failure. Finally, the chapter discusses the Master Information Delivery Plan (MIDP) , a schedule showing when each information deliverable will be produced, and the Task Information Delivery Plan (TIDP) , the discipline-specific sub-schedule.
Comments
Post a Comment