BIM_MGT_101 Practice Questions

A BIM mobilization plan must define both the operational information environment and the people responsible for establishing and managing it. The Common Data Environment is therefore a core component. The plan should identify the selected platform, folder structure, naming system, permission model, approval states, model-sharing process, and procedures for publishing, reviewing, and archiving project information.

The plan must also define roles and responsibilities . This includes responsibility for model setup, coordination, content management, data validation, model-health reviews, issue administration, information authorization, and delivery approval. Without explicit accountability, essential mobilization tasks may be duplicated, delayed, or left incomplete.

A contract template and project specifications are broader organizational or contractual resources rather than primary BIM mobilization components. Project milestone dates influence the subsequent delivery programme, but mobilization focuses on establishing the environment, resources, access, governance, and responsibilities necessary to begin BIM production. Detailed milestone commitments are normally developed through the project programme and information-delivery plans.

A reusable firm-wide template should allow project-specific entries while enforcing a consistent minimum mobilization standard across projects.

Reference topics: BIM mobilization planning; Common Data Environment setup; roles and responsibilities; project initiation; access governance; model-startup procedures; resource planning.

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

The BIM manager should first create a controlled package containing only the models, documents, and supporting information required for the interior-partition scope. A package establishes a defined information exchange and prevents subcontractors from relying on unrelated or uncontrolled project content.

Role-based permissions and folder-level access must then be configured according to the principle of least privilege. The subcontractors should receive only the minimum viewing, downloading, uploading, or editing rights necessary to perform their contractual tasks. Structural, MEP, scheduling, commercial, and other restricted folders should remain inaccessible rather than merely hidden within a broader model set.

Watermarking does not prevent unauthorized viewing or access. Granting full project access and relying on verbal instructions provides no enforceable technical control and creates an unacceptable information-security risk. Hiding coordination issues is unrelated to controlling access to model files and may obstruct legitimate issue resolution within the subcontractors’ assigned scope.

The BIM manager should test the permissions using an equivalent user role, confirm that inherited folder permissions do not expose restricted information, and document the approved access configuration as part of the onboarding record.

Reference topics: Common Data Environment security; role-based access; folder permissions; information packages; least-privilege access; subcontractor onboarding.

Step 1: Reset the coordinates of the model.

Step 2: Link in by current coordinates.

Step 3: Acquire coordinates from the updated property boundary resource file.

Step 4: Update the Shared Site of each link copy.

The existing shared-coordinate relationship must first be cleared because the authoritative civil background now contains revised GIS positioning. Resetting the model coordinates removes the obsolete relationship and prepares the architectural model to establish a new shared-coordinate system without physically moving its authored building geometry.

The updated property-boundary or civil resource is then linked using its current positioning so that it can serve as the authoritative coordinate source. Once the updated reference is correctly positioned, the architectural model acquires coordinates from that file. Acquiring coordinates transfers the civil model’s survey-coordinate definition into the host while preserving the architectural model’s internal origin and local modelling arrangement.

The final step is to update the Shared Site assigned to each duplicated building-link instance. This is necessary because multiple copies of the same building model may occupy different campus locations or orientations. Each link instance must reference the appropriate named site position so that the copies remain correctly placed after the revised GIS coordinate system is adopted.

Changing link sites before updating the host coordinate framework would apply positions against outdated coordinate data and could displace the campus federation.

Reference topics: Shared coordinates; Acquire Coordinates; named Shared Sites; campus model assembly; GIS and civil-reference updates; duplicated Revit links.

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