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

‌ Resources and Function Sets‌

Line 410 – Table 7

‌ Commissioning and Identification of DER Requirements

Lines 555-565

In the Aggregator scenario, the DERs under the management of the Aggregator may not be IEEE 2030.5 devices – that is, they may not have a device certificate. In this case, the Aggregator will produce the LFDI (see section 5.2.1.2). In all cases, this identity and the associated LFDI are returned to the Aggregator for their uses in ensuring communications are routed correctly.

In the rare event that an LFDI collision is detected (i.e. two unique certificates or IDs hash to the same LFDI value), the certificates or IDs of the offending DERs will need to be replaced or re-generated. This may require returning the DERs to the manufacturer for certificate replacement. Note that the probability of a LFDI collision is infinitesimally small. It is much more likely the collision was caused by an accidental duplication of the certificate or ID.

‌ DER Controls and DER Default Control Requirements

Line 601 – Table 9

Refer to Annex B for further specification of the four DER management envelope extensions.

Lines 602-604

The Ramp Rate Setting function is used to control the ramp rate of the DefaultDERControl controls and is used to manage the rate of application of the failsafe controls.

The DER Client will need to store the DefaultDERControl settings between communication and electrical network interruptions.

5.2.4.1 Scheduling of Controls

Lines 606-607

DERControls are IEEE 2030.5 events and SHALL conform to all the event rules in Section 10.2.3 of IEEE 2030.5-2018.

5.2.5.1 Monitor Data

Lines 651-652 Tables 10 – 11

Refer to Annex A for details on expected monitoring data, attributes and data qualifiers.

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