Operations teams needed to surface approved O&M packs and reference asset-related documents from within Maximo, but the CDE and EAM had no connection, forcing manual searches across disconnected systems and creating risk at asset handover.
.png){kind=small}
Large infrastructure programmes rarely operate with a single system. Our client's technology landscape spanned enterprise asset management (Maximo/IBM AIM), geographic information systems (Esri/GIS), project scheduling (Oracle Primavera P6/Unifier), records management (Microsoft SharePoint), and business intelligence (Power BI and Azure Data Lake). The challenge was not building individual systems, it was making them work seamlessly together around a central CDE. VE3 designed and implemented an open, API-first integration architecture enabling bi-directional data flows between Oracle Aconex and the wider enterprise ecosystem, delivered through the VE3-XIL integration layer.
Operations teams needed to surface approved O&M packs and reference asset-related documents from within Maximo, but the CDE and EAM had no connection, forcing manual searches across disconnected systems and creating risk at asset handover.
The programme required 4D scheduling by linking Primavera P6 programme schedules to NWD/MP4 model outputs, but there was no governed mechanism to store, surface, or play back 4D evidence from within the CDE.
Documents and models in the CDE carried no geospatial reference, making it impossible for GIS and Esri users to locate assets on a map and navigate to the relevant technical documentation from a spatial context.
The client’s Microsoft 365 estate - including SharePoint, Teams, and Outlook, was used for internal collaboration but had no structured connection to the CDE, creating a parallel, ungoverned information environment alongside the formal project register.
Programme leadership had no consolidated visibility of document approval progress, MIDP compliance, or portfolio KPIs derived from CDE data, reporting relied on manual spreadsheet aggregation across multiple project teams.
VE3-XIL uses Azure API Management as a stable, governed façade for all integrations, providing OAuth2 security, versioned endpoints, throttling, and a developer portal with sandbox mock payloads, enabling supply-chain partners to integrate without direct CDE write access.
Asset-centric document linking was implemented via APIM using Asset ID as the join key. A VE3 read-only portal gives Maximo users access to the latest approved CDE documents directly from their EAM workflow, without requiring transacting CDE licences.
Oracle Integration Cloud recipes connect Aconex to Primavera P6/Unifier. 4D evidence outputs are stored in the CDE and surfaced through the VE3 gateway for web-based playback, with schedule snapshots loaded to the Lakehouse to correlate submissions and clashes against milestones.
Feature and scene layers were published from CDE documents and models. Geospatial IDs are stored on Aconex records and exposed via the VE3 portal, with point-cloud data served as Esri 3D Scene Layers or Cesium 3D Tiles linked back to CDE records.
Delta exports from Aconex flow into ADLS Gen2, are processed by Azure Databricks, and are published as Power BI semantic models for Portfolio→Programme→Project KPI dashboards, delivering live reporting with no manual aggregation.
.png)
VE3-XIL decouples analytics, AI, and portals from the core CDE, so clients can adapt and extend their platform without disrupting ISO 19650 governance.
.png)
