All expertise
DIGITAL TRANSFORMATION

Digital consulting.

Let business value define the digital agenda.

OUR PERSPECTIVE

Start with the business problem. Build digital capabilities that can keep evolving.

Energy businesses often face two pressures at once: existing production systems must remain stable while the way the business operates needs to change faster. The difficult task is not adding another system. It is enabling assets, trading, finance and field operations to use consistent information and work toward the same business outcome. ZHICE starts with the value stream, connecting business capabilities, data products, application architecture and delivery teams. We distinguish the shared capabilities a group should standardize from the differences its business units need to retain. Every digital investment should explain which decision it changes, who will use it, how it will be accepted and who remains accountable after launch. Whether a project creates a lasting capability is central to our assessment of a digital proposal.

THE DECISION CONTEXT

Understand the relationships.
Then choose the tools.

Digital planning for an energy business must answer two sets of questions: can the group understand its assets and cash flows, and can operating sites maintain safe, continuous production? Business definitions, organizational responsibilities and system boundaries sit between the two. ZHICE selects an important value stream and traces how information is created, decisions are made and results feed back. We then distinguish management, data and technology barriers. This creates an evidence-based order of investment rather than a project list assembled from departmental software requests.

Digital capabilities can sustain value only when they become part of stable working practices. ZHICE connects target processes through a business capability map, specifies information sources and conditions of use through data products, and uses phased architecture to address legacy systems. Business owners participate in prioritization and acceptance; technology teams are accountable for operability and maintainability; finance helps agree benefit definitions. Planning, delivery and operations use the same questions and evidence, allowing each stage to decide whether to continue, adjust scope or stop low-value investment.

THE ZHICE APPROACH

The ZHICE Digital Capability Method

Five stages—value definition, capability design, connected data, phased delivery and value management—bring planning, delivery and operations onto one roadmap. Business and technology teams make decisions together. The approach draws on MIT CISR research on digital business transformation, DORA findings on organizational and technical collaboration, and public specifications for data interoperability and OT security. ZHICE translates these perspectives into work designs for energy businesses; the business’s actual constraints determine implementation priorities.

ZHICE / VALUE TO EXECUTIONFive stages. Evidence to move forward.
01

Define value

Which business outcome deserves attention first?

02

Design capabilities

What should be standardized, and where should differences remain?

03

Connect data

Can the data behind decisions be trusted and traced?

04

Deliver in stages

How can change proceed without compromising business continuity?

05

Manage value

Does value continue to materialize after launch?

Across every stageBusiness valueAccountabilityData and evidenceRisk boundaries
Operating results revisit the original judgement and inform the next allocation of resources and actions.
See how each stage worksCore questions, methods, deliverables and stage decisions
ANALYTICAL FRAMEWORK

Exhibit 1 | Connect cross-functional work with reusable capabilities

Business integration and shared capabilities should reinforce one another. Quadrants guide the next discussion; they are not company ratings.

Swipe to explore the complete figure

Exhibit 1 | Connect cross-functional work with reusable capabilities01Temporary integration02Sustainable coordination03Fragmented development04Local standardizationCapability standardization and reuseDepth of cross-functional coordinationLowHighHighLowPositions reflect decision conditions, not quantified scores
01

Temporary integrationCoordination has expanded but relies on bespoke interfaces and manual intervention. Establish common meanings, stable services and enduring ownership so every new request does not require another connection effort.

02

Sustainable coordinationShared capabilities are reusable and business flows work end to end. Focus on service quality, negotiated change and value review, while checking suitability for new uses.

03

Fragmented developmentApplications develop within departments, with people bridging cross-system tasks. Start with a critical value stream and a shared problem, then decide which capabilities and data to standardize.

04

Local standardizationFoundational services share common elements but are not yet embedded in complete business flows. Clarify users and outcome ownership, then test whether reuse improves coordination.

A ZHICE methodological illustration. Reuse increases from left to right; coordination deepens from bottom to top. There is no quantitative scale, and the framework does not establish returns or rankings.
OUR PRACTICE

Explore the critical questions.

Each practice examines diagnosis, solution design, implementation and delivery requirements in detail.

EVIDENCE & ACCEPTANCE

Make deliverables useful to decisions.

Go beyond document names to define purpose, evidence and verification. Agree the work scope against actual conditions at project initiation.

DECISION TOOL

Digital capability development: from stage outputs to leadership decisions

Swipe to explore the complete table

Stage and scopeCore outputsEvidence for validationLeadership decision
Define value: Follow an important business value stream to establish the main problems affecting outcomes and the conditions in which they arise.Connect problems, responsibilities, baselines and benefit hypotheses, producing initial diagnostic and investment recommendations.Provide business documents, process records and role confirmations, identifying the facts behind key judgments and remaining uncertainties.Confirm the priority business problem and whether to fund further architecture design and data verification.
Design capabilities: Define shared group capabilities and business differences, comparing paths to retain, integrate and evolve legacy systems.Produce the target capability map, option comparisons and transition architecture, with stage dependencies, responsibilities and exit conditions.Provide application assessments, business differences and decision records explaining constraints, costs and continuity effects.Select the delivery path and stage scope, assigning shared capability ownership and necessary exceptions.
Connect data: Start with specific uses to define the meaning, provenance, quality and applicability of critical objects.Produce data product specifications and accountability arrangements, connecting definitions, interfaces, permissions and issue handling.Provide end-to-end lineage samples, quality checks and trial feedback demonstrating that data issues can be detected and handled.Determine whether data supports the target use and choose further governance, restricted use or business validation.
Deliver in stages: Organize the first implementation around complete business outcomes, preserving production and business continuity.Deliver usable business capabilities, joint acceptance materials and plans for migration, recovery, training and handover.Provide normal and exceptional task records, reconciliation results and recovery tests, explaining how unresolved issues will be handled.Decide whether to launch, defer or narrow scope, and specify regional and asset differences requiring validation before rollout.
Manage value: Continue checking actual use, business outcomes and full costs against the original investment assumptions.Produce value reviews and recommendations for product improvement or retirement, with a reviewable basis for the next allocation of resources.Provide use and issue records, business outcomes and cost details, separating confirmed improvements, untested items and external effects.Decide whether to invest further, adjust ownership or scope, or consolidate and retire low-value capabilities with continuity arrangements.
Deliverables are tailored to the problem and decision. These outputs describe ZHICE’s working approach, not results already achieved by a client, and do not replace the company’s own investment or safety approvals.
WHAT THE WORK LEAVES BEHIND

Leave behind mechanisms that work.

01

Target capability map, application disposition plan and phased architecture blueprint.

Every capability has an accountable owner and a use case, with explicit reasons for architecture choices.

02

Critical data product specifications, responsibility matrix, data quality rules and interface requirements.

Source owners and consumers agree their responsibilities and conditions of use, and critical data flows can be traced.

03

Delivery roadmap, acceptance cases, migration plan and rollback arrangements.

Business acceptance, technical operations and security boundaries meet the conditions agreed in advance.

04

Digital product operating practices, value reviews and a register of improvement and retirement decisions.

Benefits have accountable owners, full costs are recorded, and low-value investment can be stopped promptly.

RESEARCH FOUNDATIONS

Research brought into
consulting practice.

We translate management research and technological advances into working methods for energy businesses. The frameworks below are ZHICE's synthesis of the research and industry questions.

MIT CISR · Peter Weill / Stephanie WoernerFuture Ready? Pick Your Pathway for Digital Business Transformation · 2017-09-21

Application in the ZHICE approachUse operating efficiency and customer experience as two lenses on transformation pathways, moving the discussion from system inventories to business capabilities and organizational change.

Scope and limitationsUse the analytical perspective of the published research; do not treat its cross-industry profitability differences as expected returns for energy businesses or ZHICE projects.

Read the original research
Google Cloud · DORAState of AI-assisted Software Development 2025 · 2025

Application in the ZHICE approachAssess technical tools within their organizational, process and delivery context, emphasizing continuous feedback and complete operating accountability.

Scope and limitationsThe research primarily concerns software delivery. Release and change requirements in energy production need a separate assessment and cannot be inferred directly.

Read the original research
W3CData Catalog Vocabulary (DCAT) — Version 3 · 2024-08-22

Application in the ZHICE approachDraw on ways to describe datasets, data services, versions and catalog interoperability to improve data discovery and conditions for reuse.

Scope and limitationsDCAT is a metadata interoperability specification. It does not replace data quality management, ownership decisions or internal authorization policies.

Read the original research
NISTGuide to Operational Technology (OT) Security · SP 800-82 Rev.3 · 2023-09-28

Application in the ZHICE approachConsider performance, reliability and security together in IT/OT collaboration, defining boundaries for interfaces, changes and recovery.

Scope and limitationsThis reference uses the final Rev. 3. The official site also identifies an initial public draft of Rev. 4; a draft is not treated as a final requirement. Projects in China must consider applicable local requirements.

Read the original research