1. Home
  2. AutoDesk
  3. BIM_MGT_101 Exam Syllabus

AutoDesk BIM_MGT_101 Exam Syllabus

Start Free BIM_MGT_101 Exam Practice After Reviewing the Topics

Before starting your BIM_MGT_101 exam preparation, it is recommended to review the complete AutoDesk Certified Professional in BIM Management for Building Design exam syllabus and carefully go through the exam objectives listed below. Once you understand the exam structure and objectives, you should practice using our free BIM_MGT_101 questions. We also provide premium BIM_MGT_101 practice test, fully updated according to the latest exam objectives, to help you accurately assess your preparedness for the actual exam.

AutoDesk
Vendor
BIM_MGT_101
Exam Code
57
Total Questions
4
Total Exam Domains

START FREE BIM_MGT_101 EXAM PRACTICE

NO SIGNUP REQUIRED  •  100% FREE TO START

BIM_MGT_101 EXAM QUESTIONS

AutoDesk BIM_MGT_101 Exam Objectives

Section 1: Corporate standards and documentation
Weight:
16%
1.1. Establish BIM standards to align with organizational requirements
  • 1.1.a Create model health thresholds
  • 1.1.b Research, interpret, and apply industry data standards
1.2. Create project and content templates
  • 1.2.a Create Autodesk Forma project template
  • 1.2.b Create multidisciplinary model templates
  • 1.2.c Customize content creation template
  • 1.2.d Support graphic standards via authoring tools (e.g., create view templates, customize annotations)
1.3. Develop BIM Execution Plan (BEP) templates
  • 1.3.a Establish risk management system template
  • 1.3.b Define mobilization plan templates
  • 1.3.c Establish information delivery plan templates (e.g., TIDP, MIDP, AIA, or ConsensusDocs)
  • 1.3.d Define project team roles and responsibilities
1.4. Evaluate digital tools that improve the consistency and efficiency of deliverables
  • 1.4.a Establish a standard process for evaluating tools
  • 1.4.b Evaluate and build a business case
1.5. Document best practices at the corporate level
  • 1.5.a Define the QA/QC process for milestone review
  • 1.5.b Review BIM standards
  • 1.5.c Perform post-project evaluation
1.6. Develop training and learning paths
  • 1.6.a Aggregate and evaluate current staff competencies against requirements
  • 1.6.b Create training and provide resources to support career pathways
Section 2: Project needs assessment
Weight:
28%
2.1. Analyze project requirements
2.1.a Determine clients’ BIM requirements
  • i. May include identifying expectations, milestones, and deliverables, and assessing BIM goals and uses.
2.1.b Strategize ecosystem of tools for project execution
2.1.c Assess each task team capability and capacity and determine training
requirements
2.2. Develop and implement project-specific BIM Execution Plan (BEP)
2.2.a Establish BIM goals and uses (e.g., define and support project-specific
templates and content, establish the mobilization plan, etc.)
2.2.b Establish the delivery team’s risk management system (e.g., quality control
procedures, access control, model use limitations, communication breakdown)
2.2.c Establish information delivery plans
2.2.d Distribute BIM Execution Plan (BEP)
  • i. May include confirming the delivery team’s BEP and implementing custom project conditions to include in the BEP.
2.2.e Establish level of development (LOD) or Level of Information Need
2.3 Initialize project setup
2.3.a Establish project datums (e.g., Shared Coordinates, Levels, Grids)
2.3.b Assemble interdependent models
2.3.c Implement project-specific BIM processes
  • i. May include Shared Parameters, Worksets, Phases, Autodesk Forma folders and permissions, and model coordination workflow
2.3.d Initialize or participate in internal and external project kickoff meetings
2.4 Implement quality control procedures
2.4.a Analyze project models for performance and model health and identify
areas of improvement
2.4.b Check model information for completeness and compliance with specified
requirements according to project standards
Section 3: Collaboration process
Weight:
36%
3.1. Manage Common Data Environment (CDE) process
  • 3.1.a Share BIM data files and models with third parties
  • 3.1.b Manage data security
  • 3.1.c Implement issue tracking
3.2. Coordinate and maintain geolocation
  • 3.2.a Extend coordinates across multidisciplinary project models
  • 3.2.b Implement a building location change using shared coordinates
  • 3.2.c Reconcile geolocation issues (e.g., resolving differences in project units, addressing unintentional changes, etc.)
3.3.Manage 3D coordination
  • 3.3.a Manage clash detection processes using model coordination tools
  • 3.3.b Set up focused clash-detection reports and analytics in line with the clash matrix
  • 3.3.c Allocate resolution responsibilities
3.4.Manage 3D models
  • 3.4.a Assemble multi-building and/or multidisciplinary model scenarios
  • 3.4.b Map phases of multi-disciplinary linked models
  • 3.4.c Implement stakeholders' shared parameters (e.g., Parameter Service)
3.5.Review consultant and/or subcontractor BIM deliverables
  • 3.5.a Validate QA standards and LOD/Level of Information Need requirements
  • 3.5.b Evaluate received geometry and content
  • 3.5.c Mandate standards compliance
Section 4: Data management
Weight:
20%
4.1. Manage model creation according to project standards
4.1.a Ensure naming and numbering compliance (e.g., ISO 19650, client/company
standards)
4.1.b Control output visibility (e.g., templates, filters, overrides)
4.2. Audit and resolve model issues
4.2.a Educate the team in response to model issues (e.g., warnings, journal files,
and subdivision strategy)
4.2.b Troubleshoot project files
  • i. May include Revit journal file, review warnings, rollback file versions, fix corrupt families, manage supporting files, visibility graphics, and external references and links management
4.2.c Periodically review internal models for compliance with project data
structure and overall health
  • i. May include workset strategy, browser organization, and layer management
4.2.d Check and validate compliance with project or industry standards
4.3.Conduct project closeout
4.3.a Archive project data
4.3.b Facilitate data handover as per project requirements
Info