You connect two InEight environments with a CDE integration that moves documents, drawings and their fields from one organisation's InEight into another's, and returns responses on the reverse path. CDE Sync™ links both environments through dedicated accounts, maps fields between them and logs every transfer.
Why two InEight environments need to share
InEight is used by owners and contractors on large infrastructure, energy and resources projects. It often holds the formal document record alongside cost, schedule and contract information. Because both owners and contractors use it, a project can easily involve two separate InEight environments, each configured for its own organisation. An owner runs one for the programme, and the delivery contractor runs another for its own document control.
Moving documents between them is usually manual. A document controller exports a package from one environment, renames it, completes a different set of fields and uploads it to the other. Responses come back the same way. On a programme with tens of thousands of documents, that work ties up skilled people and makes it harder to prove what each party held at a given date.
What carries across between InEight environments
CDE Sync™ moves documents with their version history and maps fields between the two environments. Document number, revision, status, discipline and contract references arrive in the form the receiving environment expects, even where configuration differs. Reviewed documents and responses can travel back. Every transfer is logged, giving both organisations a defensible record.
The InEight integration page describes the connector in more detail.
How to connect two InEight environments, step by step
Agree between both organisations what moves each way and what triggers a transfer.
Compare the two field configurations and agree how each field maps.
Request an InEight service account in each environment from its administrator.
Connect both environments in the CDE Sync™ wizard and choose locations on each side.
Map fields and statuses, then set the schedule.
Run a test package, review it with both document controllers, then switch on the full flow.
Owners, contractors and alliance partners
The most common case is an owner and a contractor on the same programme. The owner wants submissions to arrive in its own environment, with its own numbering and status codes. The contractor wants to keep working in the environment it has set up for its teams. A connection lets each organisation keep its own configuration while documents and responses move between them automatically.
Alliances and joint ventures are another case. Several partners may each bring an InEight environment, and the alliance needs a consistent record across all of them. Syncing agreed areas keeps everyone aligned without forcing a single environment on every partner. Our article on joint venture CDEs covers how to keep the record clear when several organisations contribute.
It pays to agree status translation early. An owner's acceptance codes rarely match a contractor's internal statuses one for one. Writing the translation into the mapping means each side sees status in its own terms, and nobody has to interpret codes they did not create. The same applies to contract and package references, which usually follow each organisation's own structure.
Once running, the connection is mostly about exceptions. A document that fails a mandatory field rule is reported to a nominated person and fixed at source, so the next run picks it up. Because CDE Sync™ is configured through a wizard, mappings can be adjusted as contracts are added, without developer time.
Security and data residency
CDE Sync™ streams files directly between the two environments without storing them, encrypts data in transit and processes it in the Azure region you choose, which suits Australian, North American and European residency requirements. Each organisation controls its own service account. Utopia Digital holds SOC 2 Type II and Cyber Essentials. See the Security Trust Portal and the global data region map.
InEight to InEight and the Utopiaverse™
An InEight to InEight connection is part of the Utopiaverse™, the connected record Utopia Digital builds across your platforms. CDE Sync™ keeps both environments aligned, CDE Backup™ keeps an independent copy in your own Azure, CDE Migrate™ handles consolidation at contract close, and CDE Archive™ captures the record at completion. AI Insights searches content across both environments, with cited answers. See also How Do I Connect InEight to My Other CDEs? and How Do I Connect Two Oracle Aconex Projects or Instances?
See two InEight environments connected in the monthly live demo, or talk to the team about your project.