A BIM Execution Plan establishes the operational framework by which BIM will be implemented on a project. Two core components are the modeling standards that govern how information is authored and the technology ecosystem that enables production, exchange, review, coordination, and delivery. Modeling standards typically address file structure, naming conventions, model segmentation, coordinates, units, worksharing, content requirements, quality-control procedures, and information expectations. The technology ecosystem identifies approved authoring applications, software versions, cloud platforms, coordination tools, interoperability formats, add-ins, and supporting hardware or infrastructure.

An LOD or level-of-information matrix may be attached to or referenced by the BIM Execution Plan, but general project specifications are contract or technical-design documents rather than defining components of the BEP itself. Likewise, collaboration protocols are normally covered by a BEP, but “project playbook” is not the precise paired component represented by the Autodesk curriculum. A conventional project schedule may influence BIM deliverables, yet it is not equivalent to the BIM production and information-delivery plan.

Therefore, option B contains two elements that directly belong to BIM implementation planning and govern consistent execution across disciplines. These provisions prevent incompatible software, inconsistent modeling practices, and uncontrolled information exchanges.

Reference topics: Corporate BIM standards; BIM Execution Plan development; model-authoring requirements; software and technology planning; interoperability; quality-control standards.

===============