BIM Management & Level of Development (LOD)

BIM protocols, permitted uses, and level of development

BIM coordination needs agreement on authorship, model content, intended uses, delivery dates, and reliance. A visually detailed model is not necessarily a reliable fabrication or field-verification record. Establish the project protocol before transmitting files and evaluate individual elements rather than assigning one blanket reliability label to every item in the model.

Current and historical AIA digital documents

AIA retired E203–2013, G201–2013, G202–2013, and C106–2013 on July 31, 2024. Earlier agreements and study resources may reference them, so recognize their historic roles, but do not prescribe them as the currently available forms. The 2022 family distinguishes E201, where model versions may be enumerated as Contract Documents, from E202, where they may not. E401 and E402 address sharing within design and construction teams respectively. G203 records a BIM execution plan; G204 and G205 provide model element tables; C106–2022 addresses digital licensing.

Select the exhibit that matches the intended sharing and contractual reliance. Record participating parties, identified model versions, uses, author assignments, and development expectations. A protocol does not automatically grant a warranty of error-free fabrication, transfer every copyright, or make every model a Contract Document. Review those choices in the actual agreements. If an exam resource expressly supplies a historical protocol, apply that resource rather than silently substituting current clauses.

The Level of Development (LOD) Framework

A common misconception on the ARE is confusing Level of Detail with Level of Development:

• Level of Detail (Input): Refers to how visually detailed an element appears in the 3D model (e.g., whether a pump is rendered with cosmetic bolts and a brand logo).
• Level of Development (Output / Reliance): Refers to the degree to which team members and downstream contractors can rely on the accuracy, geometry, and data content of that element for decision-making, estimating, and construction.

The LOD framework, originally created by the AIA and comprehensively expanded by BIMForum, standardizes model progression across common designations:

LOD 100 — Conceptual Representation

• Description: Model elements are represented as generic massing volumes, geometric placeholders, or conceptual spatial shapes.
• Information Content: Approximate gross floor areas, overall building volume, building height, conceptual building orientation, and spatial programmatic footprints.
• Possible use, subject to agreed reliance: High-level feasibility studies, zoning massing envelopes, conceptual cost benchmarking based on historical area and volume metrics ($/sq ft or $/cu ft), and preliminary solar/energy orientation studies. Do not rely on a quantity or geometry beyond the agreed accuracy and intended use.

LOD 200 — Approximate Representation

• Description: Model elements are represented as generalized systems or assemblies with approximate quantities, sizes, shapes, locations, and orientations.
• Information Content: Generic wall thicknesses (e.g., "generic 6-inch partition" rather than specific stud gauges and drywall layers), rough structural column grids, and conceptual spatial routing for primary mechanical shafts and duct chases.
• Possible use, subject to agreed reliance: Schematic design deliverables, spatial coordination of major building zones, preliminary energy modeling, and assembly-level cost estimating based on UniFormat classifications. LOD 200 elements provide spatial placeholders but lack precise engineering dimensions.

LOD 300 — Specific Representation

• Description: Model elements are graphically represented as specific systems, objects, or assemblies with accurate quantity, size, shape, location, and orientation.
• Information Content: Specific material assemblies (e.g., 3-5/8" 20-gauge metal stud with 5/8" Type X gypsum board each side, deflection track, and acoustic batt insulation), precise structural beam sizes (W18x35), and engineered ductwork dimensions.
• Possible use, subject to agreed reliance: Generating traditional 2D Construction Documents (drawings and schedules), regulatory code compliance reviews, permitting submissions, detailed CSI MasterFormat unit-price cost estimating, and competitive bidding. While LOD 300 defines exact dimensions and locations of isolated components, it does not detail cross-discipline interface connections or fabrication clearances.

LOD 350 — Interdisciplinary Coordination & Clearances

• Description: Model elements are graphically represented with specific cross-discipline interfaces, connection points, support brackets, and critical clearances necessary to coordinate with other building systems.
• Information Content: Structural baseplates, connection gussets, bracing stiffeners, duct flange connections, pipe hanger zones, wall backing plates for wall-mounted equipment, maintenance access buffers, and fireproofing clearance envelopes.
• Possible use, subject to agreed reliance: Comprehensive automated clash detection, constructability reviews, and interdisciplinary coordination between architectural, structural, and MEP trades. LOD 350 supports interface coordination: it provides the spatial interface data used to evaluate whether systems fit within congested plenums and vertical risers without physical collisions during construction.

LOD 400 — Fabrication & Assembly

• Description: Model elements are detailed with sufficient geometric and fabrication specificity to enable direct manufacturing, shop assembly, and field erection.
• Information Content: Precise shop fabrication details, exact weld profiles, bolt patterns and bolt hole diameters, rebar bends and lap splices, custom sheet metal transitions, and manufacturer-specific equipment models.
• Possible use, subject to agreed reliance: Generating trade shop drawings, computer-numerical-control (CNC) direct machine cutting, off-site prefabrication, and field erection. In standard practice, LOD 400 models are authored by trade specialty subcontractors and fabricators (steel detailers, sheet metal contractors, precast concrete manufacturers), not the prime design architect or consulting engineers.

LOD 500 — As-Built Field Verified / Facility Operations

• Description: Model elements are field-verified representations of actual installed assemblies in terms of precise size, shape, location, quantity, and orientation post-construction.
• Information Content: Verified as-constructed field dimensions, manufacturer serial numbers, equipment model numbers, maintenance service manuals, commissioning warranty dates, and maintenance scheduling links.
• Possible use, subject to agreed reliance: Ongoing facility management, preventative maintenance operations, and lifecycle building management by the owner. LOD 500 identifies field-verification status and requires the agreed verification method, which may include survey or scanning; a design model cannot simply be relabeled as LOD 500 without rigorous field verification.

---

The BIM Execution Plan (BEP / BxP)

While the selected exhibit and model element table provide the legal and protocol structure, the BIM Execution Plan (BEP) is the living operational roadmap that governs day-to-day modeling operations across the design and construction team. The BEP is typically drafted during Schematic Design by the Project Manager or BIM Manager and reviewed by all participating consultants.

Essential Components of a Professional BEP

1. Project Information & BIM Objectives: Core project data, delivery method (DBB, CMc, DB), and primary BIM goals (energy analysis, automated clash detection, 4D schedule simulation, facility management handover).
2. Organizational Roles & Staffing: Identification of the Project BIM Manager, Discipline BIM Coordinators (architectural, structural, mechanical, electrical, plumbing), and designated Model Element Authors (MEAs).
3. Collaborative Processes & File Exchange Cadence: Establishing when models are published, synchronized, and exchanged (e.g., weekly model updates every Friday by 5:00 PM; federated clash runs conducted every Tuesday morning). It defines the Common Data Environment (CDE), such as Autodesk Construction Cloud (ACC) / BIM 360, Trimble Connect, or Revizto.
4. Technological Infrastructure & Interoperability: Specifying software platforms, exact software release versions (preventing corruption from mixed version years), file export formats, and adherence to open BIM standards (Industry Foundation Classes - IFC).
5. Model Structure & Shared Spatial Coordinates: A failure to calibrate spatial coordinates can cause coordination breakdowns. The BEP mandates:
   • Project Base Point: Defines the origin (0,0,0) of the local project coordinate system.
   • Survey Point: Aligns the virtual model with real-world georeferenced benchmarks (state plane coordinates, latitude, longitude, and USGS mean sea level elevation).
   • True North vs. Project North: Establishing standard rotation angles across all discipline models.
6. Model Quality Control & Audit Protocols: Establishing file health audit cadences (compacting central files, purging unused families, checking unplaced rooms, and resolving internal software warnings).

---

Managing Legal Reliance and Model Disclaimers

One of the most heavily tested legal considerations on the ARE 5.0 Project Management exam is the boundary of legal reliance on digital models. When an architecture firm issues a BIM model, what can the contractor legally rely upon?

Are BIM Models "Contract Documents"?

Under standard AIA General Conditions (AIA Document A201–2017 Section 1.1.1), the Contract Documents consist of the Agreement, Conditions of the Contract, Drawings, Specifications, Addenda, and Modifications. Historically, electronic BIM model files are NOT Contract Documents by default unless expressly designated as such in the Owner-Contractor agreement or through the selected exhibit.

If the contract states that 2D printed, stamped drawings govern, then the digital model is legally classified as an informational reference aid. If a general contractor relies on unverified 3D model geometry to order steel or excavate foundations, and that geometry conflicts with the dimensioned 2D contract drawings, the contractor’s unauthorized reliance is a relevant responsibility issue; actual damages allocation also depends on the agreements, information, and each party’s own conduct.

Reliance is a project agreement

Define whether identified model versions are Contract Documents, the authorized uses for each element, and how conflicts with sheets are resolved. Do not impose automatic paper-over-model precedence where the agreement identifies model versions as contractual. Warranties and insurance coverage require review of the actual terms; sharing a model does not automatically void coverage. Match proposed fabrication uses with adequate developed information and the required review process.

LOD is specified per element, not automatically per project phase. The phase and author examples above illustrate possible allocations and uses; the execution plan controls. A project can contain different LODs simultaneously, and LOD 500 field verification is not simply a higher-design-detail stage beyond LOD 400. Information and permitted uses must be explicit.

Reference: AIA retirement and current digital forms.

Reference: BIMForum 2025 LOD specification.