Connecting Primavera, Aconex and Oracle Fusion ERP
Most capital project organizations run four systems that each hold part of the truth. The schedule is in P6. The cost and contracts are in Unifier. The documents and correspondence are in Aconex. The ledger is in Fusion. Every month someone reconciles them by hand, and when two of them disagree nobody can say which is wrong.
That's an integration problem, and it's a solved one. Oracle publishes supported paths for it. Most of the work isn't the middleware — it's deciding what should flow, in which direction, and who owns each field.
The integrations we build
Primavera Unifier to Oracle Fusion ERP
The cost chain, end to end: projects and structures, suppliers, contracts and commitments, change orders, invoices and actuals, budget and forecast.
Oracle publishes a supported, documented path for syncing the Unifier project shell with Fusion Cloud ERP — so this is a documented integration rather than a bespoke build, which matters if you've been burned by custom middleware before.
Primavera P6 to Oracle Fusion ERP
The other half of the picture. Project and task structures stay aligned between the schedule and finance, progress and resource actuals flow to where costing happens.
This is what closes the gap between "the schedule says we're on track" and "the ledger says we've spent 70%" — the two most common numbers in a project review that nobody can reconcile in the room.
Aconex with the project and cost systems
Connected to Unifier and P6, the record attaches to the commitment and the activity it actually relates to. This matters most when something goes wrong: a change order with the correspondence behind it is a defensible position. The same facts scattered across three systems and an inbox is a dispute.
We integrate Aconex. We don't implement it — that's a specialism in its own right, and our implementation partners do it.
Primavera to Primavera
P6, Unifier and Primavera Cloud sharing structures and data rather than diverging — so portfolio reporting is a rollup of real data rather than a monthly rebuild.
Two ways to build it — and we deliver on both
This matters more than it sounds. Most integrators recommend the platform they happen to build on. We work in both, so the recommendation is driven by what suits you rather than by what we can deliver.
Project Integration Framework (PIF)
Oracle Construction and Engineering's own lightweight framework, purpose-built for this family of products — Unifier, P6, Aconex and Primavera Cloud, plus external systems. Usually the proportionate answer when the integration sits within that estate plus finance and you'd rather not own general-purpose middleware.
Oracle Integration Cloud (OIC)
Oracle's full enterprise integration platform. More connectors, and a proper home for orchestration, error handling and monitoring. The right choice when this is one of several integrations, or when other parts of the business already run on OIC — if you already own it, use it.
What we do
Decide what should flow, and which way
Which system owns each field, what happens when both change, and what must never be overwritten. This is where integrations are won or lost.
Align the structures first
Cost codes, project identifiers, supplier records and calendars have to mean the same thing on both sides. In practice this is most of the work.
Build and configure
Transformation, scheduling, and the error handling that decides whether a failed transaction is noticed the same day or at month-end.
Reconcile and cut over
Proving the systems agree before you depend on them, and running in parallel long enough to trust the result.
Support, handover and change
We document what we build and hand it over properly, because an integration your team can't troubleshoot at 7am is a liability rather than an asset.