Building Governed Capital Programme Controls with Oracle Primavera Unifier, OEBS and Copperleaf for Uisce Éireann (Irish Water)

Uisce Éireann (Irish Water) is Ireland's national water utility, treating 1.7 billion litres of drinking water and 1.26 billion litres of wastewater every day across more than 1,750 treatment plants, over 90,000 km of pipe network and 8,000 public infrastructure assets. Under its i2OD Digital & Data Programme, Irish Water replaced its end-of-life Primavera Contract Manager system with Oracle Primavera Unifier as the Project Management Information System for the whole capital programme, fully integrated with Oracle E-Business Suite, Copperleaf, IBM Maximo and Primavera P6. After a 125-project trial, all 4,500 active capital projects were migrated and Contract Manager was decommissioned.

 

The Opportunity

Turning a Forced Migration into a Step Change in Capital Programme Control

Every one of Irish Water's 4,500 active capital projects lived in Primavera Contract Manager, and that system had reached end of life. Around it, project governance had grown fragmented: Estimate at Completion EAC reviews ran on physical gate papers disconnected from live cost data; Monthly Progress Reports, contractor claims and monthly accruals lived in separate Excel workbooks; and budget changes keyed directly into Oracle E-Business Suite (OEBS) broke audit trails and pulled forward commitments out of line with the general ledger. Field progress and corporate finance were never in step, so cost positions were always weeks behind and expensive to reconcile.

The forced migration was treated as a strategic opportunity. Rather than re-platform the old processes, Irish Water set out to rebuild project controls on an integrated digital framework: standard lifecycle governance from request to close, financial controls enforced by the system rather than by policy documents, live schedule integration with Primavera P6, and full auditability across the portfolio. Unifier would become the master source of truth for project execution, with OEBS holding the general ledger, actuals and purchase orders, and Copperleaf handling portfolio optimisation, investment scenarios and long-term capital allocation.

The scale of the estate set the bar. A platform that could not hold thousands of projects, enforce tax and inflation rules at source, and close the month on a single rhythm would simply have moved the fragmentation into new software.

Rather than simply re-platform old processes, Irish Water used the forced migration to rebuild project controls from the ground up. The i2OD programme set four objectives: one standard gated lifecycle for every project from request to close; financial controls enforced by the system rather than by policy documents; forecasts driven each month by live Primavera P6 schedule dates; and full auditability, with every figure traceable to an approved transaction.

 

The Solution

Integrated Project Controls PMIS Implementation with Unifier, OEBS and Copperleaf

Unifier was configured as the governed centre of a three-system architecture, each neighbouring system given one defined job. Data moves between OEBS, IBM Maximo, Primavera P6, Copperleaf and Unifier through Azure API Gateway (OAuth 2.0, TLS 1.3), Oracle Integration Cloud for orchestration and fault handling, and an Oracle ATP database that logs every payload for audit.

  • Governance built into the platform. Edit permissions for project budgets were locked in OEBS, so budget setup, scope amendments, contingency releases and expenditure approvals all originate in Unifier and flow to the ERP through middleware. Paper processes were rebuilt as auditable business processes: the Project/Programme Request BP (032) for intake, Programme (343) and Project (003) Shells for hierarchy and roll-up, and digital EAC gate papers tied to cost sheet baselines. A VAT CBS Mapping process of around 700 reference records sets the permitted VAT code from the task / CBS cost code at the moment of entry.

  • Uninflated in, inflated derived. Project managers forecast in the UEE Forecast Uninflated (Editable) structure, uninflated and ex-VAT. An Inflation Rates master data business process then calculates the inflated forecast by year and length of project, so Unifier holds both views and inflation is never keyed by hand. Uninflated profiles feed Copperleaf's scenario models.

  • One monthly rhythm. Each month Unifier pulls activity dates and progress from Primavera P6 to profile cash flow by cost code, with a schedule-less path Change Request 129 for projects without a P6 network. At workday 5 an integration pre-populates accruals with actuals and Maximo uncertified spend on two streams kept apart by cost code. Project managers add assessments with mandatory justification, purchase order link and vendor tag, route the record back to themselves so drafts are visible portfolio-wide, then programme managers validate deltas and finance approves in bulk through User-Defined Reports, 20 to 30 projects at a time, posting to OEBS by workday +5.

  • Engineered around platform limits. Scale testing exposed Unifier's 120-column report cap, which truncates horizontal monthly cash flow reports at 9 years and 2 months. Three architectures were evaluated: time-bucket condensation to 43 columns, a vertical one-row-per-period layout, and scheduled OIC snapshots into ATP and an Azure data mart. Delayed baseline approvals re-merge actuals to the closed period while preserving the submitted forward trajectory, and an OIC Global Fault Handler isolates failed payloads without stopping batch processing.

  • Delivered in stages, proven before scaling. Drop 2A established secure integrations, OEBS budget sync, digital EAC workflows and the cost sheet; Drop 2B added the 6 Dials framework, Delta OPEX tracking, Outputs & Outcomes and automated forecast and baseline pipelines. Oracle Consulting Services configured the solution, IBM acted as master system integrator and Copperleaf built the portfolio integration, under a steering committee led by Irish Water.

Engineering Through Platform Constraints

Scale testing exposed hard limits, each treated as a design problem. Unifier user-defined reports cap at 120 columns, leaving 9 years and 2 months of monthly cash flow against assets that run 10 to 15 years; the team set out three governed options (time-bucket condensation, a vertical row-per-period architecture, or scheduled OIC snapshots to an Azure data mart). An OIC Global Fault Handler isolates and logs failed transactions while batches keep running, and defensive form logic stops workflows breaking on missing inputs.

 

The Impact

One Audited Source of Truth for 4,500 Capital Projects

Irish Water now runs its entire capital portfolio on a single governed PMIS. All 4,500+ active water and wastewater projects were migrated from Contract Manager (after the 125 project trial), and the legacy system was decommissioned. Every figure in the general ledger traces back to an approved, audited Unifier transaction, because direct budget edits in OEBS are no longer possible.

Forecast integrity improved at source: uninflated forecasts are entered once, inflated forecasts are calculated from them by a single governed rate table, and VAT is set by cost code at the moment of entry rather than corrected afterwards. Month-end moved from offline workbooks and one-by-one review to automated intake, audited PM assessments and bulk approval across 20 to 30 projects at a time, with the period closing between workday -5 and workday +5. Five enterprise systems are connected through a secured, logged integration layer with central fault handling.

 

Lessons for other capital programmes

  • Enforce the source of truth technically. Locking ERP budget edits did more for data lineage than any policy could.

  • Derive figures, don't re-key them. Inflated forecasts are calculated, never entered by hand.

  • Encode rarely-changing rules as reference data. A maintained VAT matrix beat an integration for rules that change once a decade.

  • Design around audit concerns, not against them. The PM self-review loop turned resistance into earlier, wider visibility.

  • Plan for platform limits early. Constraints like the 120-column report cap are cheaper to solve before go-live.

  • Prove it small, then scale. A 125-project trial validated the controls before 4,500 projects depended on them.

 

Related Case Studies

Planning a PMIS migration on your capital programme? Talk to us.

Next
Next

Building Scalable Project Controls with EcoSys, Oracle Primavera Cloud & Aconex for Commonwealth LNG