How Do I Connect Asite and InEight?

You connect Asite and InEight with a CDE integration that moves documents, models, revisions and metadata between the two platforms in the direction each party needs. CDE Syncâ„¢ links Asite and InEight through dedicated accounts, maps attributes between their schemas and logs every transfer, so each organisation keeps its own platform while the record stays consistent.

Why Asite and InEight meet

Asite is used by many owners, contractors and public bodies to run controlled document workspaces, particularly in the UK and internationally. InEight is common on major capital programmes, where owners and principal contractors manage document control alongside cost, schedule and construction. Joint ventures, international contractors and large programmes regularly bring the two together.

Without a connection, documents are exported from one platform, renumbered, re-attributed and uploaded to the other, and responses come back the same way. Two controlled records that should agree slowly diverge, and reconciling them becomes a recurring task at every milestone.

What carries across between Asite and InEight

CDE Syncâ„¢ synchronises documents and models with their version history and translates metadata between Asite attributes and InEight fields. Document number, revision, status and discipline are mapped so each platform receives values it accepts, and status codes are translated rule by rule. Every transfer is logged for audit.

The Asite and InEight integration pages describe each connector, and CDE Sync for InEight covers InEight in more depth.

How to connect Asite and InEight, step by step

  • Agree which party submits, which receives and which document types flow in each direction.

  • Collect the Asite workspace configuration and InEight's numbering and mandatory fields.

  • Request service accounts from each platform's administrator.

  • Connect both platforms in the CDE Syncâ„¢ wizard and select folders and destinations.

  • Map attributes and status codes between Asite and InEight.

  • Run a test exchange on a handful of documents and compare both records.

  • Switch on the schedule and agree who monitors failed transfers.

Joint ventures and international programmes

Joint ventures often combine partners with different platform standards. One partner may run Asite across its business while the JV or the owner uses InEight. A connection lets each partner keep its familiar environment while the JV record stays complete. When the JV closes, each partner can keep evidence of what was delivered, and the record can be captured with CDE Archiveâ„¢.

International programmes add data residency to the picture. Asite and InEight may each be hosted in different regions, and the owner may have rules about where data is processed. CDE Syncâ„¢ processes data in the Azure region you choose. Our article on joint venture CDEs covers this pattern in more detail.

Running the connection is mostly about exceptions. A document that fails a mandatory field rule on the receiving side is reported rather than dropped, and the fix is made in the source platform so the next run succeeds. Because both platforms draw on one mapping table, a change to status codes or picklists is made once and applies to every later transfer, which keeps the two records in agreement over a long programme.

It is also worth agreeing early how transmittals and review outcomes are represented on each side. Asite and InEight each have their own way of recording a formal issue and a response. Deciding which outcomes should travel, and how they should appear on arrival, keeps both records meaningful and avoids confusion when a reviewer in one platform sees a status that was set in the other.

Security for major projects

CDE Syncâ„¢ streams files directly between Asite and InEight without storing them and encrypts data in transit. That suits SOCI-regulated transport, energy, water and aviation work. Utopia Digital holds SOC 2 Type II and Cyber Essentials. See the Security Trust Portal and the global data region map.

Asite, InEight and the Utopiaverseâ„¢

An Asite to InEight connection is part of the Utopiaverseâ„¢, the connected record Utopia Digital builds across your platforms. CDE Syncâ„¢ keeps both aligned during delivery, CDE Backupâ„¢ keeps an independent copy in your own Azure, CDE Migrateâ„¢ handles moves onto or off either platform, and CDE Archiveâ„¢ captures the record at completion. AI Insights searches both platforms together, with answers that cite the source documents. See also How Do I Connect Oracle Aconex and Asite? and How Do I Connect InEight to My Other CDEs?

See Asite and InEight connected in the monthly live demo, or talk to the team about your programme.

Previous
Previous

How to Choose a CDE Connector or Enterprise Connection Service

Next
Next

How Many CDEs Does One Project Have?