enen
Ongoing project

General acceptance criteria EEbus

All components must implement:  

  • TLS 1.2+ with mutual authentication (mTLS) 
  • PIN-based certificate pairing process 
  • mDNS-based device discovery and announcement 
  • Lifecycle and key management (pairing, removal, rekeying) RFP Residential Flexibility 17 / 42 
  • Encrypted WebSocket framing as transport 

SPINE (Semantic Communication)  

  • Only implement SPINE messages defined in selected Use Cases 
  • Follow all role-specific message flows and cardinality rules 
  • Implementrequiredstate machines per actor  
  • Use dynamic feature binding and subscription mechanisms 
  • Reject or ignore messages outside defined Use Cases

Work is focused on the implementation and validation of interoperable communication using the EEBUS protocol stack, specifically targeting the SPINE semantic layer and the SHIP secure transport protocol. The implementation must adhere to EEBUS Use Case specifications and follow the defined actor structures, scenario flows, and state machine logic to ensure interoperability across multiple vendors and device types. 

Acceptance criteria EEbus -HEMS side

  1. Demonstrate complete EMS behaviour for at least 3 controllable device types. 
  2. Show plan negotiation, power limit enforcement, and fallback handling.
  3. Run scenario-based tests aligned with Use Case specs.
  4. Correct state machine transitions and SPINE interaction logic must bevalidated.

Acceptance criteria EEbus - device side

  1. Device responds to EMS instructions with correct timing and logic.
  2. Supports all required Use Case message sequences.
  3. Handles failsafebehaviourand reverts under communication loss