Use Cases
Three flexibility scenarios

The programme addresses three concrete situations in which home devices can respond intelligently to the energy system.

โšก

Peak Demand Limiting

The HEMS sends power envelope constraints to connected devices, limiting their consumption during congestion events. Devices must interpret and execute these limits within defined response times, with fallback behaviour when communication is lost.

๐Ÿ’ถ

Dynamic Tariff Response

The HEMS translates dynamic price signals into device-level control instructions: shifting or shaping load profiles in response to time-of-use tariffs. Requires reliable telemetry and schedule-based control.

โ˜€๏ธ

Self-Consumption Optimisation

The HEMS monitors local generation and steers flexible loads to absorb surplus. Requires real-time production telemetry and responsive device control.

System Architecture
How it fits together

Five protocols bridge the HEMS and flexible devices. Click a protocol to jump to its work package.

Home Energy Management System
HEMS
โ†•
Interoperability Protocols
WP1S2
WP2Matter
WP3EEBUS
WP4Modbus Converter
WP5OCPP
โ†•
Flexible Energy-Intensive Devices (FEID)
โšก EV Charger
๐Ÿ”‹ Battery
โ™จ๏ธ Heat Pump
โ˜€๏ธ Solar / Inverter
Implementation
From protocols to practice
Implementation scenario overview โ€” HEMS as central hub
Overview
Detail EV charging protocols โ€” OCPP, S2, EEBus, Matter and ISO 15118
Detail ยท WP1
Work Packages
What's being built

Click any card to explore details.

WP1

S2 Protocol

EN 50631-1 ยท SPINE / SHIP
Full control loop between HEMS and devices

Implements the S2 protocol (EN 50631-1) for bidirectional HEMS-device communication. Covers PEBC (Power Envelope Based Control) and CEM resource management messages over SPINE/SHIP transport layer.

Standard
EN 50631-1
Transport
SPINE/SHIP
Control
PEBC
Language
Go / Python
Why join the test events
S2 is the backbone of the interoperability stack. Testing against a reference implementation early prevents integration surprises and validates your device's flexibility control loop in a neutral environment.
HEMS VendorsDevice ManufacturersDSOsAggregators
WP2

Matter

Matter 1.x ยท Thread / Wi-Fi
Future-proof smart home protocol for energy

Implements Matter energy clusters (EVSE, Energy Management) enabling HEMS control of Matter-certified devices. Covers commissioning, fabric management, and real-time telemetry over Thread and Wi-Fi transports.

Standard
Matter 1.x
Transport
Thread/Wi-Fi
Cluster
EVSE / Energy
SDK
connectedhomeip
Why join the test events
Matter is rapidly becoming the default smart home standard. Validating energy management interoperability now โ€” before mass market adoption โ€” positions your product for seamless certification and reduces future integration costs.
Device ManufacturersHEMS VendorsSmart Home Platforms
WP3

EEBUS

SPINE / SHIP ยท LPC Use Case
Standardized power limitation for local grids

Implements the EEBUS Limitation of Power Consumption (LPC) use case over SPINE/SHIP. Covers device discovery, certificate-based security, heartbeat, and congestion management signalling between CEM and energy-intensive devices.

Standard
EEBUS / SPINE
Transport
SHIP (TLS)
Use Case
LPC / LPP
Library
eebus-go
Why join the test events
EEBUS LPC is increasingly required by grid operators and heat pump OEMs across Europe. Testing your implementation against a reference CEM provides early compliance evidence and reduces certification risk.
Heat Pump ManufacturersDSOsHEMS VendorsGrid Operators
WP4

Modbus Converter

Modbus TCP/RTU โ†’ S2
Bring existing hardware into the modern stack

A protocol bridge translating Modbus TCP/RTU register maps to S2 resource descriptions and control messages. Supports configurable device profiles (inverters, batteries, meters) and exposes a standardised S2 interface to the HEMS.

Input
Modbus TCP/RTU
Output
S2 / SPINE
Config
YAML profiles
Runtime
Python
Why join the test events
Brownfield assets represent the majority of installed flexible devices today. Testing your Modbus device or bridge implementation against real HEMS endpoints validates the translation layer and device register maps before field deployment.
Inverter ManufacturersBattery OEMsInstallersAggregators
WP5

OCPP Local HEMS

OCPP 2.0.1 ยท Local Backend
HEMS as local OCPP backend for EV charging

Implements a local OCPP 2.0.1 CSMS (Central System) within the HEMS, enabling direct charging profile management, smart charging via ISO 15118, and local fallback operation when cloud connectivity is unavailable.

Standard
OCPP 2.0.1
Feature
Smart Charging
ISO
15118
Runtime
Go
Why join the test events
Local OCPP operation is increasingly required for grid-aware smart charging without cloud dependency. Testing your charge point or HEMS OCPP implementation in a lab environment validates local fallback, charging profiles, and smart charging interoperability.
Charge Point OperatorsHEMS VendorsFleet Managers

Join the test events

These are not paper concepts. They are concrete implementations โ€” built in open source, with a direct pathway into live interoperability testing at the ElaadNL Test Lab. Organizations not involved in the software build phase are also welcome.

Register for the test events โ†’
1 / 10
ElaadNL ยท Residential Flexibility Programme

Interoperability
Build Overview

Practical, open-source connectors enabling HEMS and flexible devices to communicate consistently across vendors โ€” tested end-to-end in a real lab environment.

5Work Packages
5Protocols
3Flexibility Use Cases
Apache 2.0Open Source License
What we're solving

Three residential
flexibility use cases

โšก

Peak Demand Limiting

Coordinate devices like charge points and heat pumps to prevent grid overload โ€” automatically, without the user noticing.

๐Ÿ’ถ

Dynamic Tariff Response

Shift flexible loads to hours when electricity is cheaper and greener, reducing costs and relieving the grid.

โ˜€๏ธ

Self-Consumption Optimisation

Direct solar surpluses to batteries or charge points, increasing renewable self-consumption and reducing grid export.

System design

One stack, five protocols

Home Energy Management System (HEMS)
โ†•
WP1S2
WP2Matter
WP3EEBUS
WP4Modbus Converter
WP5OCPP
โ†•
โšก EV Charger
๐Ÿ”‹ Battery
โ™จ๏ธ Heat Pump
โ˜€๏ธ Solar / Inverter
Implementation

Scenario in practice

Implementation scenario overview
Overview
EV charging protocol detail
Detail ยท WP1
WP1

S2 Protocol

EN 50631-1 ยท SPINE / SHIP

Implements the S2 protocol (EN 50631-1) for bidirectional HEMS-device communication. Covers PEBC (Power Envelope Based Control) and CEM resource management messages over SPINE/SHIP.

Why join
S2 is the backbone of the interoperability stack. Testing against a reference implementation early prevents integration surprises and validates your device's flexibility control loop in a neutral environment.
Implementation
Standard
EN 50631-1
Transport
SPINE/SHIP
Control
PEBC
Language
Go / Python
WP2

Matter

Matter 1.x ยท Thread / Wi-Fi

Implements Matter energy clusters (EVSE, Energy Management) enabling HEMS control of Matter-certified devices. Covers commissioning, fabric management, and real-time telemetry over Thread and Wi-Fi transports.

Why join
Matter is rapidly becoming the default smart home standard. Validating energy management interoperability now โ€” before mass market adoption โ€” positions your product for seamless certification and reduces future integration costs.
Implementation
Standard
Matter 1.x
Transport
Thread/Wi-Fi
Cluster
EVSE / Energy
SDK
connectedhomeip
WP3

EEBUS

SPINE / SHIP ยท LPC Use Case

Implements the EEBUS Limitation of Power Consumption (LPC) use case over SPINE/SHIP. Covers device discovery, certificate-based security, heartbeat, and congestion management signalling.

Why join
EEBUS LPC is increasingly required by grid operators and heat pump OEMs across Europe. Testing your implementation against a reference CEM provides early compliance evidence and reduces certification risk.
Implementation
Standard
EEBUS/SPINE
Transport
SHIP (TLS)
Use Case
LPC / LPP
Library
eebus-go
WP4

Modbus Converter

Modbus TCP/RTU โ†’ S2

A protocol bridge translating Modbus TCP/RTU register maps to S2 resource descriptions and control messages. Supports configurable device profiles and exposes a standardised S2 interface to the HEMS.

Why join
Brownfield assets represent the majority of installed flexible devices today. Testing your Modbus device or bridge implementation against real HEMS endpoints validates the translation layer and device register maps before field deployment.
Implementation
Input
Modbus TCP/RTU
Output
S2 / SPINE
Config
YAML profiles
Runtime
Python
WP5

OCPP Local HEMS

OCPP 2.0.1 ยท Local Backend

Implements a local OCPP 2.0.1 CSMS within the HEMS, enabling direct charging profile management, smart charging via ISO 15118, and local fallback operation when cloud connectivity is unavailable.

Why join
Local OCPP operation is increasingly required for grid-aware smart charging without cloud dependency. Testing your charge point or HEMS OCPP implementation in a lab environment validates local fallback, charging profiles, and smart charging interoperability.
Implementation
Standard
OCPP 2.0.1
Feature
Smart Charging
ISO
15118
Runtime
Go
Next step

Join the
test events

These are not paper concepts. Concrete implementations, built in open source, with a direct pathway into live interoperability testing at the ElaadNL Test Lab.

โœ“
Validate your product against reference implementations
โœ“
Influence practical test scenarios from the start
โœ“
Reduce integration risk before commercial roll-out
โœ“
Demonstrate readiness in a neutral multi-party environment
Register for the test events โ†’
โ†โ†’ navigate  ยท  Esc exit