One Control Plane

Operate sites, portfolios and market workflows together.

Give operators a connected view of live energy data, controlled automation, VPP portfolios and market participation.

Energy OS Architecture

From the edge to VPPs and energy markets.

A connected platform for asset control, energy data, forecasting, portfolio orchestration and country-specific market integration.

Operating layers

One operational model from device configuration to delivery records.

Electron Edge, the Energy Data Fabric, Atmosphere Intelligence, Atmosphere VPP, Market Connect and Trust & Operations connect through one Energy OS architecture.

Layer 01Field interface
Electron Edge

Connect, commission and configure solar, storage, EV charging, meters and flexible loads.

Layer 02

Energy Data Fabric

Normalise device telemetry, site relationships and operational status into one energy model.

Layer 03

Atmosphere Intelligence

Forecast demand, solar generation and available flexibility to support better decisions.

Layer 04

Atmosphere VPP

Enrol eligible assets, preview operations and coordinate flexibility across portfolios.

Layer 05

Market Connect

Link forecasts, bids, grid-service events and accepted results to operational workflows.

Layer 06

Trust & Operations

Apply identity, roles, audit records and operator oversight across every platform layer.

Integration model

Work with the estate that exists.

A deployment begins by documenting the existing control boundary, available protocols, required data and the owner of every intervention pathway.

Interface

Asset Connectivity

Connect inverters, batteries, meters, chargers and flexible loads through an extensible control layer.

Model

Energy Data & APIs

Normalise operational telemetry and make approved site, tariff and device data available to partners.

Control

Site & Device Operations

Commission controllers, organise site architectures and manage device configuration from one platform.

Deployment choices

Place responsibilities where the programme requires them.

Architecture can be reviewed across cloud, hybrid, and site-resident responsibilities. The final model depends on control ownership, connectivity, recovery needs, and data-residency requirements.

01
Cloud-coordinated portfolio services
02
Hybrid site and portfolio responsibilities
03
Defined degraded-mode and recovery pathways
Review security and deployment topics