< 上一个 | 内容 | 下一个 >

6. LV DERMS Communication Models

image

Introduction

This section outlines the available communication models that are in scope for our LV DERMS.

Note that our interoperability test procedures referenced in this document will target testing and certifying communications to software clients only. Any gateway to inverter or aggregator to inverter communications are out of scope for this testing program, and any physical response testing behind the inverter will be covered off in the interconnection handbook.

Four communication models are possible between the Utility Server and the DER End Device as illustrated below. In all cases communications between the Utility Server and the Software Communications Client shall be via the internet and shall comply with standard IEEE 2030.5.


image

Direct to Inverter Communications Model

For a small DER installation such as residential rooftop solar with a single inverter one method to be CSIP-AUS compliant is to incorporate the Software Communications Client in the inverter enabling direct communications between the Utility Server and the DER. Fail-safe operating modes shall be implemented at each site at the end device.


image

image

image

IEEE 2030.5

communications


Utility Server Direct Device (e.g. inverter)


Figure 2: Direct to inverter Communications Model


image

Gateway/GFEMS Communications Model

Rather than having direct communications between the Utility Server and the inverter, it is possible to communicate to a Gateway which in turn communicates with the inverter. This option may be used if the inverter is not capable of acting as the Software Communications Client. The Gateway can be used for larger or more complex installations with multiple End Devices such as solar inverters, battery energy storage, and electric vehicle charging or V2G technology. When used this way the Gateway is referred to as the Generating Facility Energy Management System (GFEMS). The Gateway acts to collect data from and control the various End Devices and may be seen as a single DER device to the Utility Server. In this configuration fail-safe operating modes shall be implemented at each site (either in the End Device or within the local Gateway/GFEMS).


image

image

IEEE 2030.5

communications

local communications


image

image

image

Utility Server

Gateway/GFEMS

End Device(s) (e.g. inverters)


Figure 3: Gateway/GFEMS Communications Model


image

Aggregator Communications Model

The Utility Server can communicate with an Aggregator Platform which acts as the Software Communications Client. The Aggregator Platform then communicates with the various End Devices via a range of other communications technologies. The End Devices need not be located within one electrical installation and can be distributed across a large geographic area but aggregated together by a single entity. It remains necessary for the Utility Server to be able to identify each individual DER as an IEEE 2030.5 End Device so that each End Device can be monitored and controlled individually.


Furthermore, fail-safe operating modes shall be implemented at each site (such as in the End Device), so that fail-safe export limits will operate correctly if there is a failure of the Aggregator Platform.


image

image

image

image

IEEE 2030.5 Aggregator to device

image

communications communications


Utility Server Aggregator Platform End Device(s) (e.g. inverters)


Figure 4: Aggregator Communications Model


image

Aggregator Gateway Communications Model

The Utility server can communicate to end devices through a combination of the Gateway and Aggregator Communication Models. In this model, the Utility Server communicates to an Aggregator Platform as the Software Communications Client. The Aggregator Platform can then communicate with a combination of End Devices and/or Gateway devices. As with the previously described Aggregator Communications Model, the End Devices and Gateways need not be located within one electrical installation and can be distributed across a large geographic area but aggregated together by a single entity. It remains necessary for the Utility Server to be able to identify each individual site as an IEEE 2030.5 End Device so that each End Device can be monitored and controlled individually. Furthermore, fail- safe operating modes shall be implemented at each site (either in the End Device or within a local Gateway/GFEMS) so that fail-safe export limits will operate correctly if there is a failure of the Aggregator Platform.



Utility Server

IEEE 2030.5

image

communications


image


Aggregator Platform Aggregator to device

communications


image

image

image


Gateway to device

communications


Gateway to device

communications


Gateway to device

communications

Gateway/GFEMS


End Device(s) (e.g. inverters)


Figure 5: Aggregator Gateway Communications Model