The project is complete. The asset is built, tested, and commissioned. And somewhere between the Common Data Environment and the asset management system, several thousand documents are about to become someone’s problem. O&M manuals without asset tags. As-built drawings with no link to the equipment they describe. A commissioning record that nobody can find when the first maintenance call comes in six months later.

This is not an inevitable outcome. The Aconex–Maximo integration exists precisely to close this gap — connecting the document of record in the CDE to the asset of record in the EAM, so that the information produced during construction flows into the system that will govern the asset for the next thirty years.

This guide covers how that integration works in practice: the architecture, the key data flows, the design decisions that matter most, and the mistakes that are worth avoiding. It is written for the people who will actually build or commission this integration — solutions architects, information managers, and digital leads on asset-intensive infrastructure programmes.

The gap between construction and operations

On most capital programmes, the information produced during construction lives in the CDE. The asset management system — where maintenance teams, operations staff, and asset managers work every day — is a separate system, populated separately, often manually, often late, and often incompletely. The two systems are rarely designed to talk to each other. They are left to be reconciled at handover, which is precisely the worst moment to attempt it.

The consequences of this disconnect are familiar to anyone who has worked on a major infrastructure handover:

• Maintenance teams searching the EAM for a document that exists only in the CDE, often not knowing the CDE exists at all

• O&M packs assembled manually at handover — time-consuming, error-prone, and frequently incomplete

• Asset tags in Maximo that do not correspond to document references in Aconex, breaking the traceability chain

• Engineering changes made during construction that never propagate to the as-built record in the EAM

• An information debt that compounds over the asset lifecycle — the longer the two systems are disconnected, the harder reconciliation becomes

Manual reconciliation at handover is not a sustainable solution at scale. A programme with five assets can manage it. A portfolio with five hundred cannot. Integration creates a persistent, automated link between the document of record and the asset of record — one that does not depend on a handover coordinator remembering to export a spreadsheet.

What each system owns

Before designing an integration, it is worth being precise about what each system is authoritative for. Unclear ownership is the most common cause of integration design errors, and the source of most post-implementation data quality problems.

Oracle Aconex owns the formal document register: all project documents in their approved, Published state, with their complete metadata (revision, discipline, document type, status, suitability code, originator), approval workflow history, transmittal records, and model coordination data. When a document is published in Aconex, that is the authoritative version. Nothing else is.

IBM Maximo owns the asset register: every physical asset, its location, classification, and attributes; maintenance records including planned and reactive work orders; spare parts and inventory; warranty and contract information; and the operational procedures that govern how each asset is operated and maintained. Maximo is the system of record for the asset. Aconex is the system of record for the information about it.

The join between these two systems is the Asset ID — the unique identifier for a physical asset in Maximo, stored as a metadata field on the corresponding documents in Aconex. Everything else in the integration flows from this relationship.

Establishing the Asset ID mapping correctly, early, and consistently is the single most important design decision in the integration. Get it right before construction starts, and the rest of the integration is straightforward. Leave it until handover, and the result is a manual matching exercise that can take months.

The integration architecture

The reference architecture for an Aconex–Maximo integration has three components: Oracle Aconex as the source of document records and metadata, an Azure API Management (APIM) gateway as the integration layer, and IBM Maximo as the target system for document links and O&M pack delivery.

The APIM gateway — in VE3’s implementation, this is the VE3-XIL integration layer — provides a stable, governed, versioned façade between the two systems. It handles OAuth2 authentication to both APIs, request throttling, routing, error handling, retry logic, and audit logging. Neither Aconex nor Maximo communicates directly with the other. All traffic passes through the gateway, which makes the integration observable, controllable, and resilient.

There are four key data flows between the systems:

Flow 1: Document linking (Aconex to Maximo, ongoing)

This is the primary integration pattern. When a document reaches Published state in Aconex, the integration pushes a link — not a copy of the file, but a deep link to the current Published revision — into the corresponding asset record in Maximo. Maximo users can see, from within their EAM, which Aconex documents are associated with each asset, and click through to the latest approved revision without leaving Maximo or requiring an Aconex licence.

The trigger for this flow uses Aconex Saved Searches filtered by document status and asset metadata, rather than polling the full register. On a large programme with tens of thousands of documents, this approach is significantly more efficient and avoids the performance issues that come with full-register polling.

Flow 2: Asset metadata (Maximo to Aconex, project phase)

During the construction phase, asset IDs are created in Maximo as assets are defined, procured, or registered. The integration pushes these IDs to Aconex so they can be applied as metadata on relevant documents from the point of first production — not retrospectively at handover. This is what enables document-to-asset traceability throughout the project, not just at its end.

Flow 3: O&M pack delivery (Aconex to Maximo, at handover)

At practical completion, a defined set of document types — O&M manuals, as-built drawings, commissioning records, test certificates, and spares schedules — is assembled in Aconex by asset and delivered to Maximo as a structured package. The integration handles the assembly, delivery, and confirmation of receipt automatically, replacing the manual handover pack process. The document types that constitute the O&M pack for each asset class should be defined in the Employer’s Information Requirements before the project starts. Defining them at practical completion means the integration cannot assemble them automatically.

Flow 4: Work order linking (Maximo to Aconex, operational phase)

Once the asset is operational, maintenance work orders in Maximo can reference the Aconex documents that govern the procedure or describe the component. This flow is less commonly included in the initial integration scope but increasingly requested as operational teams experience the value of being able to navigate from a work order directly to the relevant technical document.

Giving Maximo users access without additional CDE licences

One of the most practical commercial questions in this integration is how to give Maximo users access to Aconex documents without requiring them to hold CDE licences. Operations staff, maintenance technicians, and asset managers need to find and read documents regularly. They do not need to produce, approve, or transmit them.

The solution is a read-only portal — a lightweight application that indexes Aconex document metadata via the API and presents it to Maximo users in a simplified, searchable interface. Users search by asset ID, document type, discipline, or revision status, and view the latest published document without an Aconex licence. All write operations — uploading, submitting, approving, or transmitting documents — continue to happen exclusively in Aconex by licensed users.

On large infrastructure programmes where the number of operational staff who need occasional document access is much larger than the number of project users who produce and manage documents, this pattern produces a significant reduction in licence cost while improving access for the teams who need it most.

Five decisions that determine whether the integration works

The architecture for this integration is well-understood. The API patterns are mature. What determines whether the integration delivers its promised value is a set of design and configuration decisions that are made — or not made — early in the programme.

1. Establish the Asset ID mapping before construction starts, not at handover.  

The single most common cause of a painful handover is asset IDs defined in Maximo after construction, and documents in Aconex produced without them. The fix is to require Asset ID as a mandatory metadata field on relevant document types from first issue, enforced by the CDE configuration, not requested at the end.

2. Link documents — do not copy them.  

Copying documents from Aconex into Maximo creates two records that immediately begin to diverge. When a document is revised in Aconex, the copy in Maximo is already stale. The integration should always push deep links to the current Published revision, not file copies. Maximo becomes a navigation layer to the authoritative record, not a secondary archive.

3. Use Saved Searches for delta sync, not full register polling.  

The Aconex register on a large programme may contain tens of thousands of documents. Polling the full register to identify changes is slow and inefficient. Saved Searches allow the integration to query only documents matching specific criteria, making delta syncs fast, targeted, and scalable.

4. Define the O&M pack scope in the EIR, not at practical completion.  

The document types that constitute the O&M pack for each asset class must be defined before the project starts. This allows the integration to be configured to assemble them automatically. Defining the scope at handover means the automation cannot be applied and the process reverts to a manual chase.

5. Design for the operational phase, not just handover.  

Most integrations are designed with handover as the end state. The highest long-term value comes from a live, ongoing link that keeps Maximo current as documents are revised in Aconex post-handover. Design the integration with that ongoing state in mind from the outset, even if some flows are delivered in a later phase.

What success looks like

A well-implemented Aconex–Maximo integration produces measurable outcomes that are visible from day one of operations:

• Handover pack assembly time reduced from weeks or months to hours, driven by automated O&M pack delivery rather than manual document chasing

• Maximo users able to find and access the documents they need in seconds, via the read-only portal, without cross-system searches or phone calls

• One hundred per cent of Maximo asset records linked to at least one Aconex document at practical completion for all defined asset classes

• Document links in Maximo always pointing to the current Published revision, maintained automatically by the integration without manual intervention

• Significant reduction in CDE licence cost through the read-only portal pattern, with broader operational access as a result

For asset-intensive organisations — water utilities, energy operators, highways authorities, rail operators — these outcomes are not marginal improvements. They represent the difference between an asset management system that is genuinely useful from day one of operations and one that takes years of manual effort to bring to a reliable state.

The bottom line

The Aconex–Maximo integration is not a technical nicety. The gap between construction information and operational information is a real, ongoing, and costly problem for every asset-intensive organisation that manages it manually. Every maintenance team that cannot find the document they need, every handover that takes months to assemble, every engineering change that never reaches the as-built record represents a compounding cost that a well-designed integration eliminates.

The architecture is proven. The API patterns are mature. Done well, the implementation is achievable in phases over three to six months, with measurable value delivered at each phase. The outcome is an asset management system that is current, connected, and genuinely useful — not just at handover, but for the full operational life of the asset.

To discuss how VE3 approaches the Aconex–Maximo integration for your programme, contact us .

‍