Context

An integrated national oil and gas corporation operating across the full value chain — exploration and production, gas gathering and processing, pipelines and storage, refining, and distribution and retail — alongside a wider role in developing national gas infrastructure.

Organisations of this shape carry decades of accumulated systems across operationally distinct segments, each with its own technology history. The corporation had no established enterprise architecture function: no single view of the estate, no agreed principles or standards, and no mechanism to align technology investment to strategy across the segments.

The challenge

The requirement was not a one-off architecture document. It was to establish enterprise architecture as a permanent internal capability — one the organisation could run itself after the engagement ended.

That is a materially harder brief than producing blueprints. It meant designing the function alongside the architecture: deciding how architecture decisions would be made and by whom, what standards would apply, how conformance would be assured, and how the function would keep its artefacts current once the consultants left. Architecture content without a function to sustain it becomes shelfware within a year.

The scope also had to cover six architecture domains rather than the usual four, adding security and integration to the standard business, data, application and technology set — reflecting an estate where integration between operational segments was itself a primary constraint.

Approach

1. Strategy and assess. Establish governance for the engagement, capture the business vision, drivers and priorities, and set up the benefits management framework. Plan the EA capability itself as a deliverable from the outset, rather than treating it as an afterthought.
2. Design. Develop architecture principles and reference architecture. Capture the as-is architecture and existing technology portfolio, align the portfolio to the reference model, and produce an initial gap analysis and target operating model.
3. Construct. Build the architecture artefacts across all six domains — business, information, application, technology, information security and integration. Refine the target models, complete the gap analysis, and develop the transition architecture and roadmap.
4. Implement. Stand up the architecture function: structure, processes, service catalogue, tooling and repository. Migrate architecture activity from a project footing onto the permanent function.
5. Operate and review. Benefits management, service and risk monitoring, and continuous improvement — with training and skills transfer running throughout so the capability stayed in-house.

What was established

• An enterprise architecture operating model — vision, governance approach, structure, processes and service catalogue
• An architecture principles set and reference models to govern subsequent decisions
• Current-state architecture across six domains, with the technology portfolio mapped to the reference model
• Target-state architecture across the same six domains
• A gap analysis and transition architecture, sequenced into a roadmap of enabling initiatives
• Architecture tooling and repository selection
• A benefits realisation framework to measure whether the function delivered value
• Training and skills transfer to sustain the capability internally

Describes engagement scope and what was established; measured post-implementation outcomes are not published. Client, country, year and delivering firm withheld; described at sector level only.