interaktive system architectur
Partners collaborating in the Harmon-E cluster, which is part of the unIT-e² research project, developed the system
architecture for the upcoming clusters field trials1. The interactive system architecture
displayed below shows all use cases, which will be tested in the field. Shown are all relevant
stakeholders and technical components (without specification of a measurement concept). A
distinction is made between use cases concerning single family homes and multifamily
homes/workplaces and between different datatypes (e. g.
communication data, measurement data according to TAF, prices / price signals).
The interactive representation of the system architecture allows individual use cases to be viewed separately. Use cases can be activated by the respective switches. Each use case can be displayed individually or in any combination with other use cases. More detailed explanations can be found in the tables below.
If you have any questions about the system architecture, please do not hesitate to contact our experts.
Use Case am Eigenheim
Use Case am MFH/Arbeitsplatz
|If necessary, the DSO transmits Plim to the MPO as aEMP (GWA) via web interface or similar.|
|Plim is send to single-family homes by the MPO as aEMP utilizing the SMGWs transparent CLS proxy channel. Plim is forwarded to the HEMS via the HCU.|
|Plim is send to the single-family homes SMGW by die MPO via the encrypted TLS channel (DIN VDE V 0418-63-8). The SMGW stores Plim and transfers it to the HEMS via the EEBUS protocol.|
|Plim is sent to multi-family homes / workplaces by the MPO as aEMP via the SMGWs transparent CLS proxy channel. Plim is forwarded to the HCU and transferred to the charge management.|
|Plim is send to the multi-family homes / workplaces SMGW by die MPO via the encrypted TLS channel (DIN VDE V 0418-63-8). The SMGW stores Plim and transfers it to the charge management via the EEBUS protocol.|
|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.|
|Alternative to 4a: The aggregator transmits the redispatch signal to the single-family home HEMS via the supplementary communication channel (WAN 2).|
|The HEMS optimizes the tethered devices and transmits any control signals in the device-specific protocol to ensure Plim compliance.|
Use Case 1.1/1.2 and 1.3) The DSO informs the energy
supplier about a remote-control command.
Use Case 2.1/2.2 and 2.3/2.4) The DSO informs the energy supplier about a remote-control command and the energy supplier informs the DSO about the dispatch of its flexibilities.
|The aggregator transmits specific (flex) schedules to the charge management system at the multi-family home/workplace.|
|Alternative to 7a: The aggregator (backend) transmits (flex) schedules (charge control signal) to the EV via the OEM (backend).|
|The EVSE communicates (possibly via ISO 15118-X) with the EV. EV to EVSE: specific vehicle data (SOC, charging restrictions), EVSE to EV: schedules.|
|The charge management system optimizes the tethered devices and transmits any control signals in the device-specific protocol to ensure Plim compliance.|
|The charge management system optimizes the connected components and transmits any control instructions in the system-specific protocol for compliance with Plim.|
|Locally measured values are exchanged between the SMGW and the HEMS via the HAN interface of the SMGW.|
|The energy supplier transmits electricity market prices to the aggregator.|
|The aEMP transmits price tables (based on electricity market prices) through the SMGW to the HCU of the home. The HCU transfers the price tables to the HEMS.|
The aggregator makes a request to the aEMP, which initiates the establishment of a
transparent CLS channel to the HCU.
Alternative to 13a) The energy supplier makes a request to the aEMT (MPO),
which initiates the establishment of a transparent CLS channel to the HCU.
|The HEMS optimizes the schedules of the flexibilities based on the price table and passes the calculated schedules to the corresponding flexibility.|
|The aggregator uses vehicle data, user charging requirements, and market prices to develop optimized (flex) schedules of EVs at the multi-family home/workplace.|
|The aggregator exchanges information on the availability and use of flexibilities with the energy supplier.|
|The charging management takes into account other loads and controls the charging of the flexibilities (EVs) with the aim of equalizing the power consumptions and/or reducing the power peak.|
|The local charging management translates the (flex) schedules of the aggregator into control commands for charging the vehicles and transmits them to EVSE.|
|The HEMS optimizes the schedules of the flexibilities with the goal of peak shaving (forecast-based) and passes on the calculated schedules to the corresponding flexibility.|
|Information/signals on the use of redispatch are shared via the communication interface (API) between TSO and, if applicable, DSO and CBP.|
|Flex availability information and redispatch deployment signals are shared between the aggregator and CBP via the communication interface (API).|
|Relevant vehicle data is transmitted from the EV to the OEM's backend.|
|The load requests set in the app by the user are transmitted to the aggregator's backend.|
|Relevant vehicle data is transmitted from the EV to the aggregator via the OEM's backend.|
|Loading requests based on vehicle and user data are transmitted to the backend of the HEMS (if necessary).|
|Requirements set by the user in the app are transmitted to the HEMS backend.|
|EV requests and user requests are transmitted from the HEMS backend to the HEMS.|
|Relevant measurement data (TAF 7/ 9/ 10/ 14) are transmitted to the MPO as pEMP via SMGW at the home.|
|Relevant measurement data (TAF 7/ 9/ 10/ 14) are transmitted via SMGW at the MFH/ workplace to the MPO as pEMP. This is a cluster-specific variant that has no general validity.|
|Relevant measurement data (TAF 7) are transmitted by the MPO as pEMP to the energy supplier.|
|Relevant measurement data (TAF 7/ 14) are transmitted by the MPO to the aggregator as pEMP.|
|Relevant measurement data (TAF 9/ 10) are transmitted by the MPO to the DSO as pEMP.|
|Measured value acquisition of the flexibilities via an mME and provision of the data for SMGW and local control unit (HEMS/ charge control).|
|Relevant measurement data (15min input/output power, TAF 7) are transmitted by the aggregator to CBP.|
|Relevant measurement data (15min feed-in/feed-out power, TAF 7) are transmitted by the MPO as pEMP to CBP.|
|Relevant measurement data is transmitted from the charging management system to the aggregator's backend.|
|aEMp||active external market participant|
|CBP||crowd balancing plattform|
|DSO||distribution system operator|
|EVSE||electric vehicle supply equipment|
|HAN||home area network|
|HCU||HAN communication adapter unit|
|HEMS||home energy management system|
|HSS||home storage system|
|mME||modern metering equipment|
|pEMP||passive external market participant|
|SMGW||smart meter gateway|
|TAF||tariff application cases|
|TCP||transmission control protocol|
|TSO||transmission system operator|
1 current state of work. May be subject to change without notice.