Autodesk Updated BIM_MGT_101 Exam Questions and Answers by eryn

The existing project levels should be retained because the preset floor plans, reflected ceiling plans, and other level-associated views already placed on sheets depend on them. The BIM manager should align those levels with the authoritative as-built levels and then establish monitoring where appropriate. The linked grids can be created in the host through Copy/Monitor , providing native project grids that correspond to the resource model.

Deleting the template levels would also delete or disrupt dependent views, resulting in precisely the extensive sheet and view reconstruction the question requires the BIM manager to avoid. A Scope Box controls datum extents and view cropping; it does not reconcile level elevations or create coordinated grid elements. Hiding the host levels and displaying only linked datums would leave the host project without properly coordinated native reference elements and would not support reliable modelling or documentation.

After alignment and copying, the team should review Copy/Monitor warnings whenever the linked as-built model changes. This preserves the firm’s established documentation infrastructure while integrating authoritative project-specific datum information.

Reference topics: Copy/Monitor; level-associated views; linked as-built models; grid coordination; Revit template reuse; datum management.

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

Scheduled, filtered reports provide the most efficient and controlled method of communicating coordination status to a project manager who does not routinely operate the coordination platform. The BIM manager can configure the report to include relevant issue attributes such as discipline, status, assignee, due date, location, priority, and creation date. A weekly schedule then delivers a consistent snapshot without requiring repetitive manual extraction.

Saving the reports within the project environment also maintains a traceable project record. The project manager can compare reporting periods, identify overdue items, review issue closure rates, and escalate unresolved coordination risks without maintaining a separate unofficial dataset.

Manual Excel exports introduce unnecessary administrative effort and create a risk that the spreadsheet becomes outdated immediately after issue statuses change. Using Excel as the principal tracker would fragment the project’s source of truth and could result in conflicting issue records. AutoCAD’s interference functions are not the appropriate mechanism for managing multidisciplinary Revit coordination issues and would not preserve the associated cloud-based issue workflow, assignments, comments, and status history.

The correct strategy is to retain issue management in the approved coordination platform while tailoring automated reporting to the stakeholder’s information needs.

Reference topics: Model Coordination; issue management; scheduled reporting; discipline-based filtering; coordination dashboards; Common Data Environment reporting.

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