Autodesk BIM_MGT_101 - Autodesk Certified Professional in BIM Management for Building Design

Exhibit 1 correctly assigns a red dashed line pattern to the Demolished phase status for both Projection/Surface Lines and Cut Lines. This is required because demolished elements may appear either in projection or in section, depending on the view orientation and whether the element is intersected by the view’s cut plane.

Configuring only Projection/Surface Lines would leave demolished elements displayed differently when cut. Conversely, changing only Cut Lines would not produce the required standard in elevations, plans, or other views where the elements are viewed in projection. The phase graphic override must therefore consistently define the colour and line pattern in both graphical conditions.

This setting belongs in the firm’s Revit project template so that future projects inherit the standard. The corresponding phase filters must also be configured to apply the Demolished override in relevant demolition and construction views. A graphic override does not operate independently; the active phase and phase filter determine whether an element is classified and displayed as existing, demolished, new, or temporary.

Reference topics: Revit phasing; Phase Graphic Overrides; demolished-element standards; phase filters; projection and cut graphics; corporate project templates.

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

Copy/Monitor is designed to support both the initial creation and continuing coordination of critical datum elements between linked Revit models. Participating disciplines can copy the approved Levels and Grids from the authoritative architectural or structural model into their own models and establish monitored relationships to the source elements.

If the structural framing decision later changes floor-to-floor elevations or grid positions, Revit generates coordination-review notifications when the linked source model is reloaded. The receiving teams can then assess each change, postpone it where necessary, reject it, or update their corresponding datum elements through a controlled coordination process.

Shared Coordinates ensure that models occupy the correct common spatial position, but they do not monitor changes to individual Levels or Grids. Establishing a primary model in a collaboration platform supports information exchange but does not create element-level coordination relationships. Exporting reports and property information provides only a static record and would require manual comparison after every design revision.

The project must also establish which discipline owns the master datum elements and define how proposed changes are reviewed and approved before dependent teams modify their models.

Reference topics: Copy/Monitor; coordination review; Levels and Grids; datum ownership; linked-model change management; multidisciplinary Revit coordination.

The BIM manager should generate an access or permissions report directly from the Autodesk cloud platform. The platform is the authoritative source for project members, folder access levels, assigned roles, and permission configurations. Exporting the report preserves the relationship between the reported information and the actual project configuration while providing the project manager with a format that can be reviewed without navigating the cloud administration interface.

A manually created Word document or spreadsheet would only be a secondary transcription of the permissions. Such records can become inaccurate when users are added, removed, or reassigned, and they provide weaker traceability than a system-generated report. A Revit Show History report records model synchronization activity and user interactions with a workshared model; it does not report cloud-folder permissions.

The exported report should be reviewed for unnecessary access, inconsistent folder inheritance, external-user permissions, and whether each team member has only the level of access required by their role. The BIM manager should also retain the report as part of the project’s information-governance and audit records.

Reference topics: Common Data Environment permissions; cloud-user administration; access reporting; information security; role-based access; project audits.

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

The training programme should focus on the technologies directly supporting iterative option generation, environmental evaluation, and cloud-based stakeholder review. Generative-design methods allow the team to systematically explore multiple façade or planning alternatives using defined goals, constraints, and measurable outcomes. This is more appropriate than manually producing disconnected options under a compressed schedule.

Autodesk Forma and its site-design capabilities support early-stage design development, option comparison, contextual review, and environmental analysis. These workflows are particularly valuable for a geographically distributed team because design alternatives and analysis results can be prepared consistently for recurring client meetings. Training should include option creation, analysis interpretation, naming and version conventions, presentation workflows, and the method for documenting decisions against the client’s sustainability criteria.

AutoCAD and Civil 3D are not the principal tools required for the stated façade-option and energy-analysis workflow. Sustainability certification training may be beneficial at an organizational level, but it does not replace practical project-specific instruction in the applications and computational methods the team must operate each week.

Reference topics: Project technology assessment; Autodesk Forma; Forma Site Design; generative design; environmental analysis; distributed-team training; design-option evaluation.

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

A structured performance audit is the correct starting point because it evaluates the model comprehensively rather than assuming a single cause. The review should examine warning quantity and severity, file size, imported or linked CAD data, excessive views, unused content, model groups, in-place families, highly detailed components, workset configuration, and other authoring practices that can increase regeneration time and memory consumption.

In-place families are particularly relevant because numerous or geometrically complex instances can make the model difficult to maintain and may increase computational overhead. Warning trends also matter: some warnings create repeated relationship checking or indicate poor modelling practices, although warning count alone does not determine performance.

Deleting sheets or exporting only 3D views damages the project’s documentation structure and does not constitute a controlled health-improvement strategy. Clash reports evaluate multidisciplinary spatial conflicts; they do not diagnose the internal efficiency of the submitted Revit model. Loading linked files individually can be useful later when evidence specifically implicates a link, but it is too narrow as the primary health assessment.

The audit should produce documented findings, prioritized recommendations, and measurable actions that the consultant can implement without compromising required project deliverables.

Reference topics: Revit model-health audits; performance management; warnings; in-place families; file-size analysis; consultant model review; coordination readiness.

Training should be targeted to the personnel responsible for executing, checking, or approving the specialized data-formatting and export workflow. The BIM manager should develop task-specific tutorials that cover tool installation, approved configuration, source-data prerequisites, export settings, file naming, validation procedures, exception handling, and the method for confirming compliance with the government and global data-management requirements.

Role-based assignment is more effective than training the entire project team. Only users who perform or supervise the workflow require operational proficiency, while other participants may need only general awareness of submission dependencies. This reduces training time, limits unnecessary software access, and creates clear accountability.

Waiting for software crashes or quality-control failures is reactive and exposes the project to preventable delivery risk. Revit Journal files may help diagnose technical failures, but they do not identify whether users understand the required data workflow. Similarly, milestone reviews occur too late to serve as the primary training trigger.

The BIM manager should also test the add-on in a controlled environment, document approved versions, provide sample datasets, and verify user competency before production exports begin.

Reference topics: Role-based training; project-specific technology deployment; add-on validation; data-export standards; competency assessment; quality assurance.

Because the host model itself has not changed, the first investigation should focus on how the external references are being resolved. Relative paths depend on the relationship between the host file and the linked files within the project folder structure. If a folder was renamed, relocated, synchronized differently, or omitted from a distributed package, Revit may no longer locate the linked models even though the links remain correctly configured in the host.

The BIM manager should review the link status and saved paths in Manage Links , confirm that the referenced files still exist, and compare the current folder structure with the approved project structure. Access permissions, cloud synchronization status, and network availability should also be checked where applicable.

Converting all references to absolute paths would make the links dependent on a specific drive or network location and commonly causes failures for other users. Removing and reinserting links risks losing positioning, pinning, display overrides, workset assignments, and coordination history. Rebuilding the host from backup is disproportionate and does not address an external path or access failure.

Reference topics: Manage Links; relative file paths; federated-model folder structures; reference resolution; link-status troubleshooting; Common Data Environment access.

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

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.

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

A country-specific Mechanical Equipment family template should use the measurement system and unit formatting expected in the target market. This includes the appropriate conventions for dimensions, flow, pressure, power, temperature, electrical values, and other discipline-specific quantities. Establishing units in the template ensures that family authors enter, interpret, test, and document parameter values consistently from the beginning of content development.

Object Styles govern the graphical representation of family categories and subcategories; they do not translate the family into a country’s official language. Parameter classification as Type or Instance must be determined according to the intended behavior of each value. For example, manufacturer and nominal-capacity information may be type-based, while asset identifiers or installation-specific values may be instance-based. Setting every parameter to Instance would therefore produce poorly structured content.

Project Location concerns geographical and environmental project settings and is not the principal country-standard setting for a reusable equipment family. A family template is intended to be loaded into many projects, so its numerical conventions must align with the regional standards under which the content will be authored and used.

Reference topics: Revit family-template standards; regional content development; project and family units; mechanical equipment parameters; corporate content libraries.

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