The CDE now controls actions, not just files
Edition: 4 October 2026 · Category: BIM News
This archive article preserves the English content of the original dated Daily BIM Tech Brief. Product availability, deadlines, research status and recommendations describe that edition—not a fresh assessment today. Underlying source dates differ from the edition date; supplier claims and research results remain attributed, not independent product tests.
Today’s main Daily BIM Tech Brief signal is that the common data environment is becoming much more than a passive file store. The latest Autodesk Forma and Procore changes show the CDE turning into a control layer for migration, permissions, approval exceptions, coordination filters and links to physical site conditions. For a BIM manager, the key question is not how many features exist. It is whether the team can prove which information was authoritative, who had the right to change a process state, and whether migrated or automated results were actually verified.
Visual archive note: no original per-topic video artwork was recovered for this edition. The original thumbnail and source video are retained; no substitute illustrations have been invented.
Forma Data Transitions and historical records
Autodesk Forma Data Transitions is now generally available for eligible BIM 360 Next Gen and BIM 360 Field projects. Hub administrators can import supported historical project information for preservation and, when necessary, transition the imported copy into Forma Data Management. Access still depends on eligibility. This lowers a technical barrier to moving away from older cloud products, but the word supported does not mean that every semantic relationship, audit record or permission state will survive. An imported copy is not automatically the active, authoritative CDE. Before migration, teams should inventory files, revisions, requests for information, issues, forms, attachments, users, permissions and dates. After migration, they should compare not only object counts but also links, statuses, timestamps, responsible people and access rights.
Sources retained from the original edition: - https://www.autodesk.com/blogs/construction/september-autodesk-forma-construction-releases-built-for-whats-next/
Project templates and administrator rights
Forma is strengthening control over project templates and administrator privileges. An organization can require every new project to start from an account template. A Hub administrator can restrict the granting of new Project Admin rights to Hub administrators only. Teams can also export a folder permission report from a project template, organized by user, role and company. Existing Project Admin assignments are not removed automatically. These tools support more consistent project setup, but they do not guarantee that the template is correct. A flawed permissions model can now be reproduced very efficiently across many projects. Templates therefore need an owner, a version and a formal permission-matrix review before release. A platform role is not the same as contractual responsibility, so technical access should be reconciled with real obligations and the information-management process.
Sources retained from the original edition: - https://www.autodesk.com/blogs/construction/september-autodesk-forma-construction-releases-built-for-whats-next/
Coordination search sets and reality context
model coordination has gained search sets, point clouds and a more connected two-dimensional and three-dimensional context. Forma Model Coordination can use Search Sets in clash checks so that coordination focuses on specific object groups. Search Sets can be arranged in folders, transferred between projects and updated while remaining connected to clash and view filters. Viewing RCS point clouds with design models is explicitly marked as beta. Hypermodeling connects three-dimensional models, drawings and documents in one navigation experience. The link between Revit issues and related two-dimensional and three-dimensional views is also described as beta.
This means coordination logic is becoming a reusable CDE object rather than a local filter hidden inside one model. Every Search Set should have an owner, purpose, discipline, selection logic and version. Beta capabilities should stay inside a controlled pilot. For a point cloud, record the coordinate system, registration report, density and tolerance. Being able to view a cloud does not prove geometric accuracy, and seeing one issue in two and three dimensions does not prove that the correct model or sheet revision is being used.
Sources retained from the original edition: - https://www.autodesk.com/blogs/construction/september-autodesk-forma-construction-releases-built-for-whats-next/
Handover attachments and evidence
Forma is expanding the evidence chain inside handover packages. As-built and handover exports can now include attachments from requests for information, forms and issues, in addition to supported submittal attachments. When references and attachments are included, photos, PDFs and other files are added to the export package and report links point to the packaged files. Packages on mobile are now generally available on iOS and Android.
This improves the ability to transfer decision context, not only final documents. However, the presence of an attachment does not prove that it is final, approved or linked to the correct asset. Before handover, verify the manifest, checksums, link integrity, statuses and duplicate content. Teams should also distinguish between an informative photo, contractual evidence and an authorized asset record.
Sources retained from the original edition: - https://www.autodesk.com/blogs/construction/september-autodesk-forma-construction-releases-built-for-whats-next/
Procore approval overrides
Procore is preparing an auditable way to override a stalled approval step. Workflow updates announced on September twenty-ninth are scheduled for general availability on October thirteenth. Mobile Step Override is planned to roll out between October sixth and thirteenth. An authorized user will be able to advance a stalled workflow while providing a required reason. The action will be attributed to a named person and recorded in the history. Separate permissions will allow a workflow to return to an earlier step or restart without granting the full Workflow Manager role.
The availability status matters. This is an announced near-term release, not a feature that is active everywhere today. A controlled exception may reduce delay, but it also creates a new route around the intended approval sequence. Before activation, define who can use an override, which reasons are acceptable, when a second approval is required, and how exceptions will be reviewed.
Sources retained from the original edition: - https://www.procore.com/whats-new/workflows-keep-every-approval-moving
DroneDeploy Ground Pro in Procore
DroneDeploy Ground Pro turns a three-dimensional site record into measurable information within the Procore context. Ground Pro is generally available. Mobile three-dimensional scanning, optional real-time kinematic positioning, reconstruction of three-hundred-and-sixty-degree walks, three-dimensional measurement and navigation can capture trenches, cast-in components, façades, above-ceiling zones and other conditions that may later be concealed. Procore customers can overlay drawings on floor or ceiling maps. DroneDeploy also became part of Procore in September.
Reality capture is moving from visual progress reporting toward a measurable project-evidence layer. But a mesh created from a phone or a three-hundred-and-sixty-degree camera is not automatically a survey-grade as-built model. Each use case needs a tolerance, an independent control method and a clear decision threshold. Critical dimensions should be checked independently. The record should preserve the device, positioning status, time, coordinates, processing version and the drawing revision used for comparison.
Sources retained from the original edition: - https://www.procore.com/press/dronedeploy-launches-ground-pro-bringing-measurable-3d-records-into-procore
Bentley MCP experiments
Bentley has publicly shown Model Context Protocol experiments, not a production product. Its engineers described trials using MCP servers for MicroStation, STAAD, PLS and other applications. In the examples, a language model generated CAD geometry from an image and helped create three-dimensional volumes for protected views in London. Bentley itself presents these as experiments and a glimpse of possible future workflows. The public article does not provide general product availability, certification or an engineering-accuracy service level.
This reflects a broader industry direction: a probabilistic model chooses an action and a deterministic engineering application executes it. The risk appears when an impressive demonstration is treated as an approved engineering result. Organizations should classify this work as experimental and require reference files, dimension and topology comparisons, a tool-permission inventory, human approval and a rollback mechanism before any future pilot.
Sources retained from the original edition: - https://www.bentley.com/en/blog/navier-stokes-ai-engineering-workflows/
The openBIM Awards Yearbook
buildingSMART has published the openBIM Awards Yearbook twenty twenty-five. The publication appeared on September thirtieth. It is not a new version of IFC, BCF or IDS. It is a collection of practical award projects and a useful teaching resource. Its value is empirical: readers can compare how organizations defined information exchange, coordination and asset-data use. But an award-winning case does not prove that the same method will work in another market or project. For education, one case can be used to separate the standard, the software implementation, the process and the measured outcome.
Sources retained from the original edition: - https://www.buildingsmart.org/resources/publications/
Analysis and practical actions
Today’s deeper analysis is that the CDE is becoming an action-control plane. The traditional CDE discussion often started with files, revisions, status and access. The platform now does much more. It migrates information from legacy systems, creates projects from mandatory templates, controls administrator privileges, runs filtered clash checks, brings in point clouds, advances approvals through exceptions and connects captured site reality to drawings.
Decision logic increasingly lives inside the platform. A Search Set determines what the clash process checks. A permission template determines who can see or change information. A workflow override determines who may alter the approval sequence. A migration engine determines which history survives. A reality-capture link determines which drawing revision is associated with evidence of physical conditions.
The technical consequence is that configuration becomes project data. Templates, permissions, filters, automation rules and exception policies need version control as seriously as the model itself. The business consequence is that changing platforms affects more than storage. It affects the organization’s process memory. Migration budgets therefore need to include quality assurance, reconstruction of permissions, comparison of audit histories and staff training.
The opportunities are substantial: more consistent project mobilization, less manual access setup, more focused clash checks, stronger links between two-dimensional, three-dimensional and physical conditions, richer handover and shorter approval delays. The risks are equally systemic. A bad template can be reproduced at scale. A migration can preserve a file while losing a relationship or status. A beta capability can enter a contractual workflow. A changed Search Set can silently change clash results. An exceptional approval can become a routine shortcut. A mobile three-dimensional record can be mistaken for a survey-grade as-built, and an AI demonstration can be mistaken for production engineering.
Five practical actions follow. First, create a CDE configuration register covering templates, the permission matrix, Search Sets, workflow rules, the migration map and named owners. Second, test every important change in a reference project with known files, permissions, clashes and audit records. Third, keep beta, announced and generally available as distinct maturity states. Fourth, apply least privilege, a required reason, an expiry date and periodic review to approval exceptions and administrator rights. Fifth, in education, assess whether a student can reconstruct the evidence chain: who changed a state, when, in which version, with what authority and according to which source.
The conclusion is simple. A modern CDE is becoming the operating system for project actions. Its reliability depends not only on data being in the cloud, but on versioned rules, limited privileges, traceable exceptions, verified migrations and a clear separation between experiments and production capabilities.
Watch the edition: https://www.youtube.com/watch?v=wvQn9U9uORQ
Watch the original BIMETI Daily BIM Tech Brief — 4 October 2026. Archived edition; review the cited sources for details and later updates.
