Placement becomes a business variable
As models, data and tasks change faster, a deployment location chosen once can lose its advantage. Latency, transfer, power conditions and recovery arrangements should jointly determine placement.
ARCHITECTURE FOR CHANGE
Digital strategy and enterprise architecture.
Compute decisions are also energy decisions.
A SIGNAL WORTH EXAMINING950 TWh
Central projection for global data-centre electricity demand in 20301
2026 · Global data centres · 2030 projectionTHE ZHICE INTERPRETATION
Compute decisions are also energy decisions.
Expanding compute meets shared constraints in electricity, networks and field operations. ZHICE believes an energy business must compare more than server prices: which tasks stay near their data, which can move, and who maintains service during disconnection will shape reliability and cost. Architecture must connect the business task, the compute resource and the energy context.
TWO PERSPECTIVES. ONE BUSINESS QUESTION.
Explore the choices behind the judgement.
01Energy cloud and edge infrastructureThe next infrastructure advantage is the freedom to change placement.
ExpandCollapse
The next infrastructure advantage is the freedom to change placement.
Growing global data-centre electricity demand brings compute back into a world of physical constraints. For an energy enterprise, the practical judgement is more specific: not every workload belongs at the centre, and field autonomy does not require a complete platform at every site.
The next infrastructure advantage is the freedom to change placement.
THE BUSINESS LOGIC OF TECHNOLOGY
THE REASONINGThe business conditions behind the view
Connectivity is not continuous
The stronger the cloud capability, the more important it is to explain operations during disconnection. Collection, condition assessment and safety control have different continuity requirements.
Elasticity is not unlimited expansion
Peaks, model updates and data movement can shift cost from processing to networks and operations. We expect visibility and workload portability to become valuable architectural assets.
WHAT THIS MEANS FOR THE BUSINESSConnect the view to resources, ownership and action
01Preserve room to adjustRead the choiceCollapse
For fast-changing analytical and inference tasks, favour replaceable interfaces and portable packaging. For stable critical control, respect field operating boundaries first.
02Assess cost with reliabilityRead the choiceCollapse
Compare the complete cost per useful task, including recovery, data transfer and field support. An individual resource price is not the cost of an operating solution.
03Allocate redundancy by consequenceRead the choiceCollapse
Assess recovery within the actual business chain. Different consequences of interruption justify different levels of redundancy and local autonomy.
What would make us revise this judgement?
Where workloads are stable, connectivity dependable and central capacity sufficient, central deployment may remain the better option. Distribution is a means, not the objective.
A QUESTION FOR THE NEXT BUSINESS DISCUSSION
Which activities must continue while disconnected, and which tasks can move to improve cost or flexibility?
Energy cloud and edge infrastructureFull perspective and practical approach
02Composable architecture and legacy modernisationModern architecture should reduce the cost of the next change.
ExpandCollapse
Modern architecture should reduce the cost of the next change.
More compute increases technical supply but does not remove waiting between systems. We believe architecture will increasingly earn its value by allowing local change: can one business rule evolve without reopening an entire estate of systems, contracts and teams?
Modern architecture should reduce the cost of the next change.
THE BUSINESS LOGIC OF TECHNOLOGY
THE REASONINGThe business conditions behind the view
Value flows outlast system boundaries
Asset operations, settlement and customer service span applications. Tracing these flows reveals which connections should remain stable and which functions need to be replaceable.
Legacy can retain an advantage
Established systems often contain years of business rules. Replacement that loses tacit knowledge can recreate old problems in newer technology. Modernisation must distinguish a capability from its current implementation.
AI magnifies interface quality
Agents may call business services more frequently. Without clear authority, states and error semantics, automation amplifies coordination ambiguity rather than resolving it.
WHAT THIS MEANS FOR THE BUSINESSConnect the view to resources, ownership and action
01Design around rates of changeRead the choiceCollapse
Stable settlement and control capabilities need not evolve at the same pace as analytical experiences. A common technology agenda does not require identical release cycles.
02Untie the critical dependencies firstRead the choiceCollapse
Modernise interfaces that actually constrain business change. Establish transitional accountability and exit conditions before deciding whether further decomposition is worthwhile.
03Maintain replaceabilityRead the choiceCollapse
Keep interface contracts, test assets and migration capabilities usable. Suppliers and technologies should remain evaluable choices rather than fixed conditions.
What would make us revise this judgement?
Composable does not mean maximally fragmented. Limited team capability, weak interface management or modest business scale can make excessive decomposition costly.
A QUESTION FOR THE NEXT BUSINESS DISCUSSION
When the next business change arrives, which components must change with it and which can remain stable?
Composable architecture and legacy modernisationFull perspective and practical approach
Three turning points to watch in digital transformation.
We watch where the constraint moves after a new capability enters the business. Better technical indicators are a starting point; sustained advantage depends on changes in resources, accountability and coordination.
- 01
Compute shifts from central buying to adaptable placement
What we watch
Track movable workloads, edge connectivity and whether compute and power conditions are considered together.
How it changes the judgement
If inference becomes easier to distribute, identity, versioning and operating consistency become more important. Weak field connectivity keeps autonomy and recovery at the front of the agenda.
- 02
Data is consumed against service commitments
What we watch
Watch whether business teams rely on shared data for real decisions and whether quality exceptions have an accountable owner.
How it changes the judgement
Growing reuse with less coordination supports expansion. Repeated interpretation at every use points to unresolved semantics and responsibility.
- 03
Software delivery follows the rhythm of the business
What we watch
Track time from need to use, recovery after failed changes and business waiting caused by platform upgrades.
How it changes the judgement
Shared capability merits further investment when it reduces waiting. Dependencies amplified by centralisation require a fresh boundary between sharing and autonomy.
A VIEW THAT CAN BE PUT TO WORK
The ZHICE Digital Capability MethodExplore the framework and implementationA perspective must stand up in practice.
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.
Data notes and research foundationsExpandCollapse
- 1IEA · Key Questions on Energy and AI, 2026
Central projection for all global data centres, not AI alone or a capacity plan for an individual enterprise.
IEA 2026 · Global data centres · 2030 projection - 2IBM Institute for Business Value · 2025 CDO Study
Self-reported confidence across 27 geographies and 19 industries; not an energy-sector adoption rate or observed project success rate.
IBM 2025 · 1,700 senior data and analytics leaders globally - 3DORA · 2024 Report Infographic
The study uses a broad platform definition; associations with productivity, throughput and stability are mixed.
DORA 2024 · Cross-industry software-delivery survey
THE NEXT CONVERSATIONThe question worth discussing:
Contact ZHICE