2.3.1 MEASUREMENT ACCURACY
All measurements shall have measurement accuracies as described in Table 1. These accuracies are independent of the accuracy of the DER internal measurements.
Table 1 – Measurement accuracies
Measurement parameter (Symbol) | Measurement accuracy |
Apparent power (S) | Lower of 4% of rated apparent power or 100VA |
Active power (P) | Lower of 4% of rated active power or 100W |
Note: These measurement accuracies are as defined in AS/NZS 4777.2.
2.3.2 PROTOCOL REQUIREMENTS
The test utility server, in addition to the requirements of IEEE 2030.5, supports the following communications parameters in order to conduct conformances tests for all feasible communications clients:
a) Payloads communicated via HTTPS, in any of XML, EXI or GZip;
b) Resources contain links to their subordinate resources;
c) Aggregator clients support REST paging techniques to process lists from the Server that may be incomplete; and
d) Resources use the standard IEEE 2030.5 namespace of urn:ieee:std:2030.5:ns
a. CSIP-AUS extensions use namespace of https://csipaus.org/ns
It is expected that any commissioning between the utility server, communications client and DER is done prior to commencing tests.
2.3.3 SUPPORTED FUNCTIONS
2.3.3.1 General
To conform with CSIP-AUS the communications client shall specify the functions it supports, including both core and optional components.
2.3.3.2 Core Functions
To conform with CSIP-AUS a communications client shall meet at least one of the following sets of CSIP- AUS DER Management controls, as determined by the type of DER the client is intended to support:
a) All clients –
o opModEnergize
b) DER capable of generation –
o opModExpLimW
o opModGenLimW
o opModMaxLimW
c) DER capable of load –
o opModImpLimW
o opModLoadLimW
2.3.3.3 Optional Components
A communications client may choose to comply with the following:
a) ConnectionPoint; and
b) Demand Response operations.
2.3.3.4 Aggregator-only Components
The following components are specific to aggregator use-cases only.
a) Subscription/Notification.
Gateways and DER end-devices are not expected to support these components directly, although they may form part of an aggregator solution that supports these commands.
2.3.4 DEFAULT CONFIGURATION
On initial discovery the test utility server shall configure the communications client with the following poll- and post-rates for the listed Resources in Table 2.
Table 2 – Default communication configurations
Resource | Value (secs) |
DeviceCapability | 300 |
EndDeviceList | 300 |
FunctionSetAssignmentsList | 300 |
DERProgramList | 60 |
DERList (including DERStatus, DERSettings and DERCapability) | 60 |
MirrorUsagePoint | 60 |
Note: These values differ from the default values defined in CSIP-AUS and are changed for testing in order to expedite the tests.
2.3.5 SUPPORT FOR SETS OF DER
Communications clients that intent to support management of multiple DER simultaneously shall be tested controlling at least two DER, and that the DER that are included will cover the range of generation and load the client wishes to claim conformance with. For the purposes of this requirement a battery energy storage system can be considered as either a generator or a load but not both. That is:
a) For clients only able to manage multiple generation-type DER (i.e. a client that supports opModExpLimW, opModGenLimW and opModMaxLimW) shall be tested controlling two or more DER capable of generating energy (which may include battery energy storage systems);
b) For clients only able to manage multiple load-type DER (i.e. a client that supports opModImpLimW and opModLoadLimW) shall be tested controlling two or more DER capable of consuming energy (which may include battery energy storage systems).
c) For clients able to manage multiple DER capable of both generation and load (i.e. a client that supports all functions listed in Section 2.3.3.2) shall be tested controlling two or more DER that collectively are capable of both generating and consuming energy.
2.3.6 COMMUNICATION INTERACTIONS
Figure 3 and Figure 4 below show the primary communications interactions to provide the functionality required to conform with tests described in this document. Figure 3 relates to the discovery process (tested in Section 3.2.1) while Figure 4 describes the commands involved in ongoing communication. Additional examples detailing XML payloads can be found in CSIP Sections 6 and 7, and in CSIP-AUS Annexes B and E.
Figure 3 – Client-server interactions – Discovery
Figure 4 – Client-server interactions – Ongoing