ACC (Autodesk Construction Cloud)
Autodesk's CDE platform; modules include Docs, Build, Takeoff, Estimate, and BIM Collaborate Pro. The most common CDE choice on Autodesk-stack projects.
Reference · BIM · ISO 19650 · Digital Delivery
The terms working consultants actually use — defined plainly. ISO 19650, LOD, CDE, BEP, IFC, COBie, and 35+ more, written by ConstruBIM's team.
Autodesk's CDE platform; modules include Docs, Build, Takeoff, Estimate, and BIM Collaborate Pro. The most common CDE choice on Autodesk-stack projects.
The information model maintained for the operation phase of a built asset. Populated from the PIM at handover and updated through the asset's life.
Information the operator needs to manage the asset over its lifecycle. Drives the AIM.
The model updated to reflect what was actually constructed — field changes, substitutions, and verified geometry. Becomes the foundation of the AIM at handover.
Open file format for exchanging issues, comments, and viewpoints between BIM tools. Lets disciplines using different software still share coordination findings.
The project's BIM playbook — roles, software stack, naming, LOD, modeling rules, coordination cadence, validation. ISO 19650 distinguishes pre-appointment and post-appointment versions.
A process for creating and managing project information across the lifecycle, using a coordinated 3D model and structured data. Not a tool — a discipline.
BSI publishes UK national standards (e.g. BS EN ISO 19650-2). ISO publishes international standards. ISO 19650 originated as the UK's PAS 1192 series and was internationalized via ISO.
The single, governed source of project information with controlled workflow states (WIP, Shared, Published, Archived). Examples: Autodesk Construction Cloud, Bentley ProjectWise, Trimble Connect, Aconex, Asite. A CDE is a workflow control system, not just file storage.
A discrete file or dataset within the CDE — the smallest unit ISO 19650 tracks through workflow states.
Identifying geometric conflicts between systems. Hard clashes are physical intersections; soft clashes are clearance/access violations; workflow clashes are scheduling conflicts (4D). Done in Navisworks, BIM Collaborate, or Solibri.
Construction Operations Building Information Exchange — a spreadsheet-based data format for handing over asset information to facility managers.
A live, data-connected model of a physical asset — kept synchronized with sensors and operational data after handover. The frontier beyond as-built.
Visual programming environment for Revit and Civil 3D, used to automate modeling tasks, data extraction, and quality checks.
What the appointing party (client) requires from the appointed party (supply chain) at each information exchange. The EIR drives the BEP.
A composite model assembled from individual discipline models without merging their authoring data — preserves source ownership while enabling coordination. Typically created in Navisworks or BIM Collaborate.
Adding the time dimension — linking model elements to construction schedules to visualize sequencing and identify temporal conflicts.
Adding cost — linking model elements to estimating data for model-based quantity takeoff and cost forecasting.
Optional dimensions for sustainability (6D) and facilities management (7D). Less standardized than 4D and 5D; usage varies by market.
Open, vendor-neutral data format for BIM (ISO 16739). Critical for interoperability between Revit, ArchiCAD, Tekla, Civil 3D, and other authoring tools.
A delivery method where owner, designer, and builder share risk and reward under a single multi-party contract — often paired with BIM and lean methods.
International standard (parts 1–5) for managing information through the lifecycle of a built asset using BIM. Defines roles, processes, information requirements (OIR/AIR/PIR/EIR), and CDE workflow states. Part 1 covers concepts; Part 2 the delivery phase; Part 3 the operational phase; Part 4 information exchange; Part 5 the security-minded approach.
Structured record of coordination problems, RFIs, or quality issues with status, owner, due date, and resolution. Typically managed inside the CDE.
How reliable model elements are at each project stage:
LOD 100 conceptual / massing
LOD 200 approximate, generic geometry
LOD 300 accurate, specific geometry
LOD 350 coordinated geometry with interfaces
LOD 400 fabrication-ready detail
LOD 500 verified as-built
Non-graphical data requirements at each stage — parameters, attributes, properties attached to model elements.
Mechanical, Electrical, and Plumbing systems. MEPF adds Fire protection — the typical full set of building services coordinated together.
Schedule of all information deliverables across the project, aggregated from individual TIDPs.
NWC is a per-discipline cache file exported from authoring tools; NWD is the federated, read-only Navisworks deliverable for review and clash detection.
High-level information needs of an organization. Used to derive AIR for assets and PIR for individual projects.
North American classification system for the construction industry — analogous to Uniclass in the UK.
The information model produced during the delivery phase of a project. Becomes the AIM at handover.
Information needed to deliver a specific project. Drives the PIM.
A 3D dataset captured by laser scanning. Used to verify existing conditions, generate as-built models, and support renovation projects. See also Scan-to-BIM.
A formal question from contractor to designer, often used to resolve ambiguity or coordination issues during construction.
The workflow of converting a point-cloud capture of an existing building into an accurate BIM model — usually for renovation, retrofit, or as-built verification.
The second ISO 19650 information state — passed internal review and shared with other appointed parties for coordination.
Schedule of information deliverables for a single task team. Multiple TIDPs roll up into the MIDP.
Unified classification system for the construction industry. Common in UK ISO 19650 implementations.
Broader umbrella term encompassing BIM plus simulation, project planning, and performance management.
The first ISO 19650 information state — internal team work that has not been issued for collaborative review.
Published: information formally authorized by the appointing party — the contractually accepted set. Archived: superseded or completed information held for reference and audit.
ConstruBIM turns these terms into working systems — BEPs, EIRs, CDE configurations, and audit-ready governance.