Interactive System Architecture for smart Charging

Implementation of Field Trials in Harmon-E


The interactive display presents the system architecture developed in the unIT-e² project and applied in the field. The architecture describes the conceptual structure and organization of a system, including its components and their interactions. Users can examine various use cases either in isolation or in combination by selecting individual or multiple use cases, in order to gain a comprehensive understanding of the architecture and its functionality in different scenarios.

In the Harmon-E cluster of the unIT-e² research project, the focus is on market-optimized, system- and grid-friendly charging of electric vehicles. Various use cases are developed, tested, and demonstrated in three field trials. These trials take place at different locations and involve various flexibilities as well as implementation prioritizations of the use cases.


Use Case am Eigenheim

Use Case am MFH/Arbeitsplatz


 TSO










TSO...
 Workplace 















Workplace...
 Connectee workplace















Connectee workplace...
 HEMS Manufacturer



HEMS Manufacturer...

 Plattform Operator


Plattform Operator...
Crowd-Balancing Plattform
Crowd-Balancing Plat...
 DSO





DSO...
 Energy Provider


Energy Provider...
 Aggregator
 (technical)





Aggregator...
 MPO



MPO...
pEMP-System
pEMP-System
 Connectee single-family home

















Connectee...
 Vehicle User 
 (SFH)







Vehicle USer...


SMGW
SMGW...
HEMS
App
HEMS...
(inflexible)
Load
(inflexible...
PV
PV
HP
HP
HSS
HSS
EVSE
EVSE
mME
mME
EV
EV
Backend
Backend

Vehicle Manufacturer
(OEM)



Vehicle Manufacturer...
Backend
Backend
 Vehicle User 
 (single-family home)





Vehicle User...
 Vehicle User 
 (SFH)





Vehicle User...
 Vehicle user 
 workplace








Vehicle user...
EV
EV
EV
EV
EV
EV

Meter
(mME, RLM, Transformer Meter)

Zähler...
EVSE
EVSE
DSO/TSO-Redispatch-System
DSO/TSO-Redispatch-System

EV

App

EV...

Currently Control Box, later HKE

Aktuell S...
SMGW
SMGW
Legende














Legende...

Actor
Actor
Technical Component
Technical Component
Data / Information
Data / Information
Data / Information
(Implementation Debatable)
Data / Information...
Measurement Data According to TAF
Measurement Data According to TAF
Communication of Prices / Pricesignals (not implemented)
Communication of Prices ...
HKE
(CLS-GW)
HKE...
Grid Controller
Grid Controller
App1
App1
(inflexible)
Load
(inflexi...
aEMP-System
aEMP-System
...
...
Measurement Data According to TAF
(not implemented)
Measurement Data According to TAF...
Communication of
Communication of Prices / P...
EVSE
EVSE
Measured Energy Flow
Measured Energy Flow
HEMS
HEMS
Charging-management
Charging-management
Backend
Backend
Text is not SVG - cannot display
Communications API
Communications API
Market Access
Market Access
Exchange for
Flex use
Exchange for...
Redispatch Signal
Redispatch Signal
Plim via
Ad-hoc-Command
(proprietary)
Plim via...
EEBUS
EEBUS
ISO
15118-2
ISO...
EEBUS
EEBUS
EEBUS
EEBUS
Charging Requirements
(Vehicle- & User Data)
Charging Requirements...
Vehicle Data
Vehicle Data
Text is not SVG - cannot display
Charging Requirements
Charging Requirements
(Flex-)Timetables
(Flex-)Timetables
Charging Requirements
Charging Requirements
EEBUS
EEBUS
Flex
Information
Flex...
OCPP dependent
from EVSE 1.6/2.X
OCPP dependent...
ISO 
15118-2
ISO...
1
1
16
16
15
15
9
9
3b
3b
11
11
Flex
Timetables
Flex...
7a
7a
23
23
User Data
User Data
Vehicle Data
Vehicle Data
24
24
7b
7b
onmouseenter="tooltip('')" onmouseleave='resetTooltip()'
25
25
22
22
26
26
2b
2b
I
I
alternate
Communications
(WAN 2)
alternate...
currently
Relais-Contacts,
later EEBUS
currently...
13b
13b
H
H
F
F
LPC
LPC...
A
A
B
B
3b
3b
27
27
2b
2b
4b
4b
LPC/LPP via
CLS.EEDI
LPC/LPP via...
LPC via
CLS.EEDI
LPC via...
TOUT
via CLS.EEDI
TOUT...
Charging Requirements
(Vehicle- & User Data)
Charging Requirements...
25
25
Charging Requirements
Charging Requirements
23
23
3a
3a
9
9
2a
2a
4a
4a
13
13
3a
3a
TAF 10 via universal
Ordering Process (MAKO)
universal Ordering Process...
C
C
12
12
E
E
F
F
D
D
4a
4a
13a
13a
23
23
20
20
EEBUS
EEBUS
5
5
14
14
19
19
8
8
18
18
10
10
17
17
Communications API
Communications API
21
21
G1
G1
TAF7
via Proprietary
TOUT...
G2
G2
12
12
Text is not SVG - cannot display
Icon Description
1
1
If necessary, the DSO transmits a power limitation (Plim) from the grid controller to the MPO as aEMP (GWA) as an ad-hoc signal via a proprietary interface.
2a
2a
As aEMP, the MPO sends the Plim signal (LPC via CLS.EEDI) through the transparent CLS proxy channel of the SMGW to the HCU (CLS gateway) of the home. The HCU transmits Plim to the HEMS.
2b
2b
As a GWA, the MPO sends the Plim signal to the SMGW in the home via an encrypted TLS channel using DIN VDE V 0418-63-8. The SMGW stores the transmitted Plim signal locally and transmits the Plim signal to the HEMS via the EEBUS protocol.
3a
3a
As aEMP, the MPO sends the Plim signal (LPC via CLS.EEDI) through the transparent CLS proxy channel of the SMGW to the HCU (CLS gateway) of the workstation. The HCU transfers Plim to the load management system.
3b
3b
As the GWA, the MPO sends the Plim signal to the SMGW at the workstation via an encrypted TLS channel using DIN VDE V 0418-63-8. The SMGW stores the transmitted Plim signal locally and transmits the Plim signal to the charging management system via the EEBUS protocol.
4a
4a
The aggregator transmits the redispatch signal to the aEMP, which opens a transparent CLS channel through the SMGW to the HCU. The HCU transmits the signal to the HEMS.
4b
4b
Alternative to 4a: The aggregator transmits the redispatch signal to the home's HEMS via the supplementary communication channel (WAN 2).
5
5
The HEMS optimizes the connected components and transmits any control commands in the system-specific protocol to maintain the power limit (Plim).
7a
7a
The aggregator transmits specific (flex) schedules to the charging management system at the workplace.
7b
7b
Alternative to 7a: The aggregator transmits (flex) schedules directly to the vehicle (EV) via the OEM.
8
8
The HEMS orchestrates the flexibilities with the aim of optimizing self-consumption (zero-point control at the grid connection) and forwards the schedules to the corresponding flexibility.
9
9
DThe EVSE communicates (via ISO 15118-2 or -20) with the EV, transmits information and negotiates charging plans according to the specification.
10
10
The charging management system optimizes the connected components and transmits any control commands in the system-specific protocol to comply with the Plim signal.
11
11
Text is not SVG - cannot display
The charging management system transmits information to the aggregator to create the (flex) schedules.
12
12
Text is not SVG - cannot display
The energy supplier transmits electricity market prices to the aggregator or the MPO.
13
13
Text is not SVG - cannot display
The aEMP transmits price tables (based on electricity market prices) via the SMGW to the HCU of the home (TouT via CLS.EEDI). The HCU transfers the price tables to the HEMS.
13a
13a
Text is not SVG - cannot display
The aggregator submits a request to the aEMP, which initiates the establishment of a transparent CLS proxy channel to the HCU, via which price information is transmitted to the property.
13b
13b
Text is not SVG - cannot display
Alternative to 13 a) The energy supplier submits a request to the aEMP, which initiates the establishment of a transparent CLS channel to the HCU, via which price information is transmitted to the property.
14
14
Text is not SVG - cannot display
The HEMS optimizes the schedules of the flexibilities based on the price table received and forwards the calculated schedules to the corresponding flexibility.
15
15
Text is not SVG - cannot display
The aggregator uses vehicle data, user charging requirements and market prices to calculate optimized (flex) schedules for EVs at the workplace.
16
16
Text is not SVG - cannot display
The aggregator exchanges information on the availability and use of flexibilities with the energy supplier.
17
17
Text is not SVG - cannot display
The charging management takes other loads into account and controls the charging of the flexibilities (EVs) with the aim of equalizing the power consumption and/or reducing the power peak (peak shaving).
18
18
Text is not SVG - cannot display
The charging management system translates the (flex) schedules of the aggregator into control commands for charging the vehicles and transmits these to the EVSE.
19
19
Text is not SVG - cannot display
The HEMS optimizes the schedules of the flexibilities with the aim of peak load capping (forecast-based) and forwards the calculated schedules to the corresponding flexibility.
20
20
Text is not SVG - cannot display
Information on the use of redispatch is shared between the crowd-balancing platform and the TSO/DSO redispatch system via a communication interface (API).
21
21
Text is not SVG - cannot display
Information on flex availability and signals for the use of redispatch are exchanged between the aggregator and the crowd-balancing platform via a communication interface (API). /span>
22
22
Text is not SVG - cannot display
Relevant vehicle status data is transmitted from the EV to the OEM's backend.
23
23
Text is not SVG - cannot display
The charging requirements set by the user in the app are transmitted to the aggregator's backend. Relevant vehicle status data is displayed to the user in the app.
24
24
24
24
Text is not SVG - cannot display
Relevant vehicle status data is transmitted from the EV to the aggregator via the OEM's backend.
25
25
Text is not SVG - cannot display
Charging requests based on vehicle and user data are transmitted (if necessary) to the backend of the HEMS or the backend of the aggregator.
26
26
Text is not SVG - cannot display
The requirements for the home set by the user in the HEMS app are transmitted to the HEMS backend. Status data is transmitted to the app and visualized
27
27
Text is not SVG - cannot display
Measurement, vehicle and user data/requirements are being exchanged between the HEMS-backend and the HEMS (if required).
A
A
Text is not SVG - cannot display
Relevant measurement data (TAF 7/ 9/ 10/ 14) is transmitted to the MPO as pEMP via SMGW at the home.
B
B
Text is not SVG - cannot display
Relevant measurement data (TAF 7/ 9/ 10/ 14) is transmitted to the MPO as pEMP via SMGW at the workstation.
C
C
Text is not SVG - cannot display
Relevant metering data (TAF 7) is transmitted by the MPO as pEMP to the energy supplier.
D
D
Text is not SVG - cannot display
Relevant metering data (TAF 7/ 14) is transmitted by the MPO to the aggregator as pEMP.
E
E
Text is not SVG - cannot display
Relevant metering data (TAF 9/10) is transmitted by the MPO to the DSO as pEMP via MAKO processes.
F
F
Text is not SVG - cannot display
Measured value recording of flexibilities via one or more MMEs and provision of the data to the SMGW.
G1
G1
Text is not SVG - cannot display
Relevant metering data (15min feed-in/feed-out power, TAF 7) is transmitted by the aggregator to the crowd balancing platform.
G2
G2
Text is not SVG - cannot display
Relevant metering data (15min feed-in/feed-out power, TAF 7) is transmitted by the MPO as pEMP to the crowd balancing platform.
H
H
Text is not SVG - cannot display
Relevant measurement data is transmitted from the charging management system to the aggregator's backend.
H
I
Text is not SVG - cannot display
The HEMS receives relevant measurement data (TAF7, TAF10) of the property from the Smart Meter Gateway (SMGW).
Abbreviation Descritpion
aEMp active external market participant
CLS controllable-local-system
CBP crowd balancing plattform
DSO distribution system operator
EV electric vehicle
EVSE electric vehicle supply equipment
GWA gateway administrator
HAN home area network
HCU HAN communication adapter unit
HEMS home energy management system
HP heatpump
HSS home storage system
MFH multi-family home
mME modern metering equipment
MPO metering-point operator
pEMP passive external market participant
PV photovoltaic
SFH single-family home
SMGW smart meter gateway
TAF tariff application cases
TCP transmission control protocol
TSO transmission system operator

The main goals of the Harmon-E cluster are:

  • Addressing the conflict of objectives between economic efficiency and network and system utility, and development of proposed solutions.
  • Testing various use cases with technically mature solutions in pilot operation and bidirectional charging in the lab.
  • Establishing a standardized and secure process chain to optimally use flexibility potential and achieve maximum customer satisfaction.
  • Analysis of the differences in the process chains of private homes and workplaces/commercial/multi-family houses.
  • The field trials include:

  • A trial with 19 private customers in the Oldenburg/Rastede area, aimed at testing market and network access to the electric vehicle.
  • A workplace trial in cooperation with Wernsing Feinkost, investigating the benefits of peak shaving as well as network- and market-friendly charging.
  • A trial in a new building with a heat pump near Bremen, equipped with various components for energy management and electromobility.
  • The illustration shown here demonstrates the architecture implemented in the field trial. The original planning version is still available for your review.

    If you have any questions, please feel free to contact our representative Jeremias Hawran.




    1 current state of work. May be subject to change without notice.