A new project being set up requires consistency across all floor plans. However, because of variations in floor-to-floor heights, the project team needs a different View Range for each level.
What is the most efficient way to accommodate this?

• A. Duplicate the View Template for each view to control its View Range.
• B. Remove the View Template and control View Range through Visibility/Graphics.
• C. Keep one View Range for all plans and add Plan Regions as needed.
• D. Deselect the Include box for View Range in the View Template.

The BIM manager is launching a civic center project with strict sustainability and lifecycle data goals. During early planning, each discipline proposes different modelling approaches, and there is concern that downstream data handoff may be inconsistent.
To establish BIM goals and uses that ensure alignment from design through operations, what should the BIM manager do first?
Note: In the context of this exam, the term Level of Development (LOD) is used interchangeably with level of information need.

• A. Begin developing the internal BIM templates and content, assuming they will be applicable to this project.
• B. Finalize the LOD matrix and data drops based on similar past projects, updating it during the design process as needed.
• C. Host a stakeholder session to review the project-specific requirements and BIM uses, and establish mobilization needs and modelling requirements.
• D. Ask each team to submit its standard BEPs for review and consolidate them into one reference document.

The BIM manager oversees both design coordination and post-handover data requirements and is asked to ensure the digital deliverables align with the owner's long-term asset-management system.
To minimize information gaps, inconsistencies in file formats, and unclear responsibilities throughout delivery, which tool should the BIM manager rely on to define who provides what information, when, and in what format, from design through facilities handover?
Note: In the context of this exam, the term Level of Development (LOD) is used interchangeably with level of information need.

• A. The Model Element Table and Level of Development (LOD) matrix.
• B. The Master Information Delivery Plan (MIDP) and/or the BIM Execution Plan.
• C. The Quantity Takeoff Checklist and/or the BIM Execution Plan.
• D. The file-naming protocol and model-authoring standards.

A BIM manager is reviewing a consultant's architectural model before the next coordination milestone. The project requires each model to conform to a defined naming convention, include COBie parameters, and populate shared parameters according to the Model Element Table. The BIM manager notices that several elements are missing metadata and that some naming is inconsistent.
Which step best supports a systematic evaluation of completeness and compliance with project standards?

• A. Ask the design team to re-export the model with updated information based on verbal clarification and metadata from the BIM Execution Plan.
• B. Use a model checker or data-validation tool to compare parameter presence, naming conventions, and required values against the established project standard.
• C. Filter out incomplete elements in a 3D view and hide them to avoid confusion during coordination.
• D. Manually review each element in the Model Browser to confirm naming and parameter completeness.

The BIM manager received a subcontractor's 3D model containing specialty equipment to be integrated into the federated model. Upon review, they observe that:
Many elements lack consistent object styles and category assignments.
Some components are modelled with excessive detail, affecting performance.
Embedded data does not follow the project's naming conventions outlined in the BEP.
What is the most appropriate next step when evaluating this geometry and content?

• A. Review the model against content standards, document noncompliance, and request revisions aligned with agreed deliverable requirements.
• B. Instruct the subcontractor to simplify geometry and reduce file size, even if some metadata and classifications are lost.
• C. Approve the model as-is to avoid delaying coordination and document the issues for review at the next quality-control milestone.
• D. Import the model into the coordination environment and apply view filters to hide excessive detail and inconsistencies.