MHHS

MHHS and the UK Grid (Part 2) - From Transparency to Deterministic Coordination

Inkwelldata

13 Feb 2026 • 5 min read

In Part 1, we examined how Market-wide Half-Hourly Settlement (MHHS) replaces statistical profiling with explicit half-hourly allocation. Demand, imbalance exposure and flexibility value are now determined by measured interval performance rather than inferred portfolio averages.

That reform introduces clarity.

But clarity does not, in itself, ensure control.

The structural consequence of MHHS is not simply improved measurement. It is the requirement to translate interval transparency into deterministic coordination across retail portfolios, distribution networks and emerging flexibility markets.

Visibility is necessary. But it is not sufficient.

When Precision Increases, Tolerance Decreases

Under the profiling regime, variability was absorbed within statistical smoothing. Communication gaps, timestamp inconsistencies and behavioural clustering were diluted across aggregate curves and corrected retrospectively.

Half-hourly settlement reduces that margin for abstraction.

Each migrated meter now produces 48 discrete settlement intervals per day. Behaviour that was once averaged becomes explicit. Portfolio exposure tightens around measured performance.

As precision increases, tolerance decreases.

Where allocation is interval-specific, coordination must also operate at interval resolution.

        This is about tighter coupling between economic accountability and physical behaviour.
    

Correlation at Feeder Level — What Has Changed

Electrification is altering the statistical character of domestic demand.

Historically, the distribution grid was engineered around diversity. If a transformer served 200 homes, engineers assumed that only a proportion would draw high load simultaneously. Cooking, lighting and appliance usage varied naturally from household to household.

Electrification weakens that diversity.

If 40 or 50 households on the same street return home between 5.30pm and 6.30pm and connect 7kW EV chargers, their behaviour is no longer independent. It becomes synchronised.

When demand is described as "correlated at feeder level", this is what it means: multiple connected properties within the same local circuit begin behaving in the same way, at the same time.

Under MHHS, these synchronised patterns are economically visible within half-hour intervals. Under distribution reform, they become operationally material.

        Measurement reveals the clustering. The local network must manage the consequence.
    

Settlement Timing Versus Physical Limits

Settlement operates through defined reconciliation stages.

Under MHHS, initial allocation typically occurs on a D+1 basis — meaning consumption for a given day (D) is first allocated on the following day (+1). Subsequent reconciliation runs refine that allocation over time.

This framework is appropriate for financial settlement.

Physical infrastructure operates differently.

A transformer has a thermal rating. Sustained loading above that rating reduces asset life or causes failure. Voltage must remain within statutory limits. Protection thresholds trigger immediately when exceeded.

These limits do not wait for reconciliation cycles.

A transformer cannot be "corrected tomorrow".

As flexibility participation increases and feeder-level constraints become more dynamic, interval telemetry must serve more than settlement.

It must be

Temporally aligned, ensuring devices report against consistent half-hour windows without drift.

Sequenced correctly, so intervals arrive in order and gaps are detected early.

Aggregated at meaningful scale, combining hundreds of meters to understand feeder loading.

Routed consistently, so settlement engines, flexibility platforms and DSO systems operate from coherent datasets.

Secure transport ensures delivery. Settlement systems allocate cost.

Neither performs feeder-level aggregation, cross-estate validation or staged dispatch coordination.

That responsibility belongs to a distinct architectural layer.

From Centralised Reconciliation to a Digital Spine

Historically, reconciliation was centralised. Profiles were applied centrally. Settlement was resolved retrospectively. Physical constraints were managed largely through planning and reinforcement.

Millions of meters now generate billions of interval records. Flexibility markets introduce event-driven dispatch. Distribution networks require feeder-scale insight.

A single central coordination point would introduce bottlenecks and concentrate risk.

A federated model distributes responsibility.

In a federated coordination architecture

Each participant operates its own coordination environment.

Telemetry is validated and aggregated before crossing domain boundaries.

Settlement, distribution and flexibility systems receive structured inputs.

Fault domains remain contained within participant estates.

        The coordination layer becomes connective infrastructure — ensuring coherence between transport, settlement and operational domains without replacing any of them.
    

What Deterministic Coordination Requires

Deterministic coordination is not merely faster data processing.

It requires infrastructure designed for:

Infrastructure Requirements

Parallel device execution, with each device operating as an isolated, supervised digital twin process, allowing large estates to be processed concurrently without blocking or cross-interference.

Horizontal scalability, enabling capacity to expand through distributed cluster growth rather than vertical concentration in a single processing engine.

Fault isolation at process level, containing local anomalies within defined execution domains and preventing cascading impact across portfolios or estates.

Structured validation before propagation, ensuring interval alignment, sequencing checks and routing logic are applied before telemetry flows into settlement, DSO or flexibility systems.

End-to-end telemetry traceability, maintaining clear lineage from device-level input through validation and aggregation to downstream distribution, preserving audit integrity.

Traditional batch integration or ETL pipelines are not designed for this operating model.

Deterministic coordination requires carrier-grade, distributed infrastructure.

Altior: Federated Coordination in Practice

Altior is architected to provide this coordination layer in practice.

Each device is represented as a supervised digital twin executing as an isolated concurrent process within a distributed cluster architecture. This model enables parallel processing across large device populations while maintaining strict fault containment.

Scaling occurs horizontally. Additional capacity is introduced by replicating nodes within the cluster rather than expanding a single processing engine.

Validation logic is applied before telemetry propagates into downstream systems. Interval alignment, sequencing integrity and cohort-level anomaly detection occur within the coordination layer itself.

This ensures

Settlement engines receive coherent interval allocations.

DSO interfaces receive feeder-scale aggregated insight.

Flexibility platforms operate against deterministic, auditable baselines.

Coordination occurs without central bottlenecks.

Deterministic Trust in a Distributed System

As coordination extends closer to feeder-level aggregation and community-scale flexibility, the operational surface expands.

Distributed intelligence must be matched by distributed trust.

Altior enforces identity at device, service and process level. Digital twins authenticate before interaction. Access controls operate within the execution environment rather than relying solely on perimeter security. Encryption and key management are embedded into the platform's design.

Security controls remain effective under degraded connectivity. Process-level isolation prevents faults or compromise in one domain from propagating across estates.

If coordination becomes distributed, trust must be equally structured.

Community Assets as Structured Resources

As flexibility capacity grows towards Clean Power 2030 targets, community-scale assets become increasingly significant: shared batteries, aggregated EV fleets, rooftop solar clusters, and domestic flexibility portfolios.

MHHS makes their contribution interval-legible.

But legibility does not ensure stability.

Without structured coordination, correlated dispatch can amplify local volatility. With staged aggregation, validation and controlled execution, community assets become stabilising components of a distributed system.

        Interval transparency enables valuation. Federated coordination enables reliability.
    

The Structural Requirement

MHHS introduces interval transparency into the UK energy market. Consumption is now measured and allocated with far greater precision.

That precision reshapes accountability.

But it also reshapes responsibility.

Interval measurement must be matched by structured coordination across settlement, distribution and flexibility domains. As electrification increases correlation at feeder level, reconciliation alone is no longer enough.

Federated, concurrency-native coordination is not an enhancement to the existing model. It is the logical consequence of it.

        Architecture will determine whether interval precision strengthens resilience — or simply reveals where coordination is missing.
    