— Articles —
Real-world insights for making sense of AI, Data, Systems, and Digital delivery.
We stand at the edge of digital possibility,
capturing advances in AI and smart
technology, transforming research into
real-world impact, and unlocking new
potential across the infrastructure world.
12. The Cost of Disconnected Project Data
The cost of disconnected project data sits in labour, rework, delay and dispute exposure. See the four layers and a worked model you can take to a project board.
11. Automated CDE Data Flows: Replacing the Manual Transfer Cycle
Automate file transfer between CDEs and retire the manual cycle. What an automated data flow replaces, what it does not, and how event and scheduled flows differ.
10. Connected CDEs and ISO 19650: Compliance Across Multiple Platforms
An ISO 19650 connected CDE has to carry container state across platforms. See what the standard requires, what breaks at the boundary and what to put in the EIR.
09. How Many CDEs Does One Project Have?
Multiple CDEs on one project is the norm rather than a failure. See where the environments come from, what the count costs, and what to do about it.
08. CDE Archive: Keeping the Project Record After the Project Closes
A CDE archive moves a finished project out of a live licence into long term storage you own. See what an archive must preserve and how to keep it searchable.
07. CDE Backup: Holding an Independent Copy of Your Project Record
A CDE backup is a second copy of the live project record held in storage you control. See the failure modes, what the copy must contain and where it should live.
06. Open and Closed CDEs: What the Difference Means for Your Data
An open CDE and a closed CDE hold your project record on different terms. Compare the security, cost and exit trade-offs, and test how easily you could leave.
05. CDE Connectors and Connected CDEs: What the Difference Means at Scale
CDE connectors link two platforms at a time, so the link count grows faster than the platform count. See what breaks them and what a hub arrangement changes.
04. CDE Integration: Integrating CDEs Without Rebuilding Your Data
CDE integration connects platforms without restructuring anyone's data. Compare native connectors, iPaaS, custom builds and purpose-built AECO platforms.
03. Enterprise Connection Services for CDEs: What Enterprise-Grade Connectivity Requires.
Enterprise connection services link CDEs under central governance. The residency, audit, cost allocation and exit tests an enterprise buyer should apply first.
02. How to Connect CDEs: A Practical Guide to CDE Connect Workflows
How to connect CDEs step by step: scope, service accounts, folder and metadata mapping, direction, triggers, pilot and go live. A practical CDE connect guide.
01. Connected Common Data Environments: What They Are and What They Actually Solve.
A connected common data environment keeps two or more CDEs aligned automatically. See what has to cross a platform boundary and what a connection cannot fix.
Migration or Sync? Knowing Which One Your Project Actually Needs
"Move data between CDEs" sounds like one problem. It is actually two. Migration is a one-time move when you are leaving a platform. Sync is an ongoing connection when platforms stay live. Picking the wrong one either wastes money or leaves your data drifting. Here is how to tell them apart.
How to Validate a CDE Migration (and Prove the Record Came Across)
Files appearing in the new platform is not a migration completion. It is the starting point for validation. Real validation proves the record arrived whole, with version history, metadata, file integrity, and the audit trail intact. Here is what that actually looks like.
Data Sovereignty and Residency: Moving Your CDE Data Where Compliance Requires
Data residency, sovereignty, and localisation are not the same thing, and assuming an "in-region" setting satisfies compliance is one of the most common mistakes on infrastructure projects. If the data is in the wrong place, here is what it takes to move it without breaking the record.
Autodesk CDE Migration: Moving To and Within Autodesk Forma (formerly ACC)
BIM 360 is being phased out, ACC is now Autodesk Forma, and native tools like Bridge and the Replication Tool leave version history behind. Whether you are moving between hubs, off BIM 360, or into the right data region, here is what a proper Autodesk migration actually involves.
Why CDE Migration Matters: The Platform Is Temporary, The Record Isn't
A CDE migration is not a copy-paste job. Version history, metadata, audit trails, and document relationships are the record that protects your position in a dispute or handover. Most tools quietly leave that behind. Here is why it matters more than it looks.
ISO 19650 Metadata Compliance Across Multiple CDEs: What the Tools Actually Support
ISO 19650 requires consistent metadata across every platform your project uses. Most integration tools can move files, but they cannot translate metadata between vendor schemas or validate against your naming convention. Here is what full compliance actually requires.
CDE Integration Comparison: The Complete Guide for AECO Project Teams
Not all CDE integration tools are built the same. This guide compares CDE Sync, Bentley BECS, IMAGINiT Clarity, Workato, the Autodesk Replication Tool, and custom development across platform coverage, deployment complexity, security certifications, and AECO domain logic, so you can make the right call for your project.
Why Custom CDE Integration Development Costs More Than You Think
Custom CDE integration typically costs $500,000 to $2,000,000 USD to build, takes up to 18 months to deploy, and carries ongoing maintenance costs every time a CDE platform updates its API. Before committing to a bespoke build, here is what to factor in.