03. Enterprise Connection Services for CDEs: What Enterprise-Grade Connectivity Requires.
Enterprise connection services are integration platforms that link Common Data Environment (CDE) platforms, and the enterprise systems around them, under central governance rather than as one-off project connections. A project connection and an enterprise connection both move files and map metadata. What separates them is control of where the data sits, how credentials are held, what the audit trail proves, how the cost is allocated, and what happens when the arrangement ends.
Organisations in the Architecture, Engineering, Construction and Operations (AECO) sector usually arrive at this purchase after accumulating connections one project at a time. Deloitte and Autodesk, in their 2025 State of Digital Adoption research, found that construction businesses across Asia Pacific use a median of 11 separate data environments. Governing that estate centrally is a different exercise from making any single pair of platforms talk.
This article covers:
What enterprise connection services are
The difference between enterprise and project level integration
The evaluation tests an enterprise buyer should apply
Renewal, exit and portability
Behaviour inside restricted networks
Vendor-anchored and vendor-neutral architecture
What are enterprise connection services?
An enterprise connection service is a managed layer that carries content and metadata between platforms, configured centrally and operated as shared infrastructure. It sits above individual projects, so a connection built for one delivery team runs under the same controls, logging and commercial arrangement as every other connection in the organisation.
The scope is usually wider than CDE to CDE. Enterprise buyers also connect CDEs to document management systems, enterprise resource planning platforms, geospatial systems, asset registers and reporting tools, under the same governance requirement.
How enterprise integration differs from project level integration
A project connection is judged on whether files arrive. It is set up for one delivery, funded from one budget, and it ends when the project ends. Nobody asks it to survive an audit or a change of supplier.
An enterprise connection has to remain defensible for years, across dozens of projects, several operating companies and at least one change of platform. The questions asked of it are asked by security, legal, finance and internal audit. The delivery team is rarely in the room.
Ownership moves from the project to a central function, so the configuration has to be visible and transferable, so it does not live in one person's head. Cost stops being a project line item and becomes something finance expects to allocate. The record of what moved also becomes evidence. Average construction dispute values run at US$52.6 million globally on the Arcadis Global Construction Disputes Report, and the transfer log is what an organisation produces when someone alleges a document was never issued.
The evaluation tests an enterprise buyer should apply
Five tests separate services that will hold up at enterprise scale from ones that will not.
Data residency and region selection. Ask for the named region, not the name of the cloud. Ask separately where the control plane, the logs and the backups sit, because those often run in a different region from the data path. CDE Sync™ offers region selection across Microsoft Azure, and the global data region map sets out where those regions are. The wider obligation picture is covered in data sovereignty and residency.
Whether the service stores files at all. Zero file persistence changes the risk assessment more than any other single property. A service that never writes project files to disk is not a place intellectual property can be taken from, and not a party that needs indemnifying for loss of the record. CDE Sync streams data between platforms and retains only encrypted credentials and synchronisation logs. Staging files in an intermediate store is a legitimate design, but it creates a third copy of the project record to secure, retain, dispose of and audit.
How credentials are held. Every connection holds credentials to platforms containing commercially sensitive design and contract data. Ask where those credentials live, who can read them, whether vendor support staff can retrieve a working one, and what happens to them when the subscription ends. CDE Sync holds credentials in Azure Key Vault, with role-based access control, multi-factor authentication, production behind private endpoints and annual penetration testing.
Whether the audit trail satisfies an auditor. A project manager is satisfied by a dashboard showing green. An auditor wants immutable timestamped records of every transfer, the metadata written, the identity that performed it, and the failures alongside the successes. Check that the log is extractable into the organisation's own reporting tools rather than only viewable in a vendor portal.
Whether consumption can be allocated. A group with several operating companies cannot run shared integration infrastructure it is unable to bill internally. Ask to see consumption reporting broken down by connection, project and business unit, and check that it reconciles to the invoice. CDE Sync is priced either per CDE project ID synchronised, which allocates naturally to projects, or as a fixed enterprise subscription to an agreed data cap, with unlimited users and no per-seat fees on either model.
Renewal, exit and portability
Test the exit at the point of purchase, while the commercial leverage is still there. Three questions cover most of it. Can the full configuration be exported, including every field mapping and lookup table. Do the connections leave anything behind on either platform. Does anything stop working if the subscription lapses, beyond the transfers themselves.
Software interoperability failures already cost the US capital facilities industry US$15.8 billion a year, two thirds of it borne by owners and operators during operations and maintenance, on the NIST cost analysis of inadequate interoperability. An integration layer that becomes its own dependency reproduces the problem it was bought to solve.
Behaviour inside restricted networks
Enterprise estates contain environments that cannot expose a server to the internet. Defence work, utilities and other assets regulated under the Security of Critical Infrastructure (SOCI) Act run networks where inbound firewall rules are unavailable at any price.
The workable pattern is a lightweight outbound-only agent installed inside the network, which initiates every connection outward. No inbound rules and no public endpoints are required, which is what allows a network team to approve it. CDE Sync connects on-premises network servers this way through a Sync Agent. Ask any supplier how they handle this case, and treat a general offer to work with the network team as an unanswered question.
Vendor-anchored and vendor-neutral integration
The architectural choice is between an integration service anchored to one vendor's ecosystem and a neutral layer that treats every platform as a peer.
Bentley Enterprise Connection Services is a capable platform in this space. On Bentley's published material it provides real-time bidirectional integration between Bentley products and third-party enterprise systems including ERP, document management, geospatial tools and IoT sensors, delivered through an administration portal with pre-built packages in the BECS Integration Catalogue, described as zero-coding, across on-premises, cloud and hybrid deployment. For an organisation genuinely centred on Bentley, that alignment is an advantage. The connectors are maintained by the vendor that controls the schema, and the roadmaps move together.
The different case is an estate spanning several vendors with no natural centre. A group running one platform on a joint venture, a second on another, and a third because a client mandated it is not centred on anything, and anchoring the integration layer to one of the three gives that vendor a say in how the other two are connected. A neutral layer fits that estate better, because no single vendor's roadmap governs the connection. That comparison is set out at length in Bentley BECS Alternative: Why Infrastructure Teams Are Choosing CDE Sync. Which model is right depends on the shape of the estate being connected.
A checklist for evaluating enterprise connection services
Utopia Digital publishes its own answers to these on the Security and Trust Portal, including SOC 2 Type II certification, Cyber Essentials certification and the 62 security controls the platform operates under.
What are enterprise connection services for CDEs?
They are integration platforms that connect Common Data Environments and adjacent enterprise systems under central governance across the organisation. The defining features are residency control, managed credential storage, audit evidence rather than status reporting, consumption reporting across business units, and a documented exit path that returns the configuration to the buyer.
How is enterprise CDE connectivity different from a project integration?
A project integration is judged on whether files arrive on time. Enterprise connectivity is judged on whether it is governable at scale: who approved it, where the data is processed, what it costs each operating company, what evidence it produces for an auditor, and what happens when a platform or a supplier changes.
Can enterprise CDE integration work on a restricted or SOCI regulated network?
Yes, through an outbound-only agent installed inside the network that initiates all connections outward. No inbound firewall rules and no public endpoints are needed, which is the property that allows the pattern to be approved in critical infrastructure environments regulated under the SOCI Act and in other restricted networks.
Enterprise connectivity is a governance purchase that happens to involve software, and the tests above tend to be applied late and expensively. CDE Sync is built as a vendor-neutral layer across 21 supported vendor integrations, with region selection, zero file persistence and audit logging as standard properties rather than options. Get in touch to run your own estate against the checklist or to request the full control set.