The objective of this test program is to ensure that CPPALUE can meet its new minimum demand requirements to remotely turn down or switch off all new, upgraded and replacement rooftop solar systems that connect to our distribution system after 1 July 2024.
Testing will be conducted on CPPALUE’s Non-Production environments against OEM devices over the public internet. To participate in testing, OEMs will need to provide their own test device and ancillary equipment to support testing.
There are three primary objectives of the interoperability test program:
1. To test and verify the process and capability required to connect the CPPALUE IEEE2030.5 server to an OEM software communications client and end device.
2. To test and verify the CSIP-AUS functional capabilities of the CPPALUE LV-DERMS and IEEE2030.5 server once a software communications client and/or end device has been connected.
3. To identify if any implementation changes are required, either CPPALUE or by the OEM.
An outline of the test program is attached below in Figure 6.
1. Application
1. Application
1. Application
2. Approval
2. Approval
2. Approval
3. Registration
3. Registration
3. Registration
4. Testing
4. Testing
4. Testing
5. Verification
5. Verification
5. Verification
Figure 6: Test Program Outline
OEMs submit a test application form and Certificate Signing Request (CSR) to OEM_onboarding@powercor.com.au
- For full CSR generation details refer to Appendix C.
• Mandatory test application details include applicant contact details, type of applicant, and target clients and/or devices. Refer to Appendix A: for example test application form.
• Once an application has been received and approved, CPPALUE will provision and share test certificates, test LFDIs (if required), test NMIs, and test program details to OEMs via email for the OEM to set up for registration and testing.
• The registration process for interoperability testing will be either in-band or out-of-band tested dependent on the supported method by the OEM. Note that CPPALUE systems are currently undergoing in-band registration functionality confirmation and initial testing may need to occur via out-of-band with in-band verification testing to occur later.
• The OEM will generate and share the LFDIs for the test devices, which will then be loaded into the Utility Server
- Refer LFDI generation logic detailed below in Section 11.3.
• Testing will be planned one week in advance and is expected to take a couple of hours if noted implementation changes have been completed.
• CPPALUE Utility Server tester will run through the pre-approved tests manually whilst in a Microsoft Teams session with an OEM test representative.
• Pre-testing will be completed one day prior to the testing window, such as verifying initial communications, device polling and aggregator systems are communicating with CPPALUE systems.
• Our systems telemetry and alarm requirements are described in Section 8. Required test setup and full test details are in Sections 9 and 10.
• Both CPPALUE and OEMs will observe the test outcomes and identify any issues or changes required.
• CPPALUE can share logs from the utility server to assist in troubleshooting and rectification.
• The Testing and Verification cycle can be repeated as needed.
• Once the test program is completed and both CPPALUE and the OEM is satisfied with the outcome, the test process can conclude.
We will issue the OEM with a test report with the test results. For an example test report refer to Appendix B.