CSIP-AUS is a communication protocol used in Australia for communications between a utility and remote CER on customer’s premises. One use case of CSIP-AUS is the communication of dynamic operating envelopes that consist of upper bounds for both flexible export limits and flexible import limits.

CSIP-AUS is currently primarily being used to manage embedded generators under flexible export and emergency backstop schemes; however, the protocol also supports other use cases, including control of loads as part of network load control arrangements.

A detailed description of the technical requirements for CSIP-AUS including current and planned features are set out in the section CER technical and interoperability standards.

Key points

• CSIP-AUS allows electricity networks to communicate flexible import limits and load limits to customer energy resources.
• CSIP-AUS supports both targeted and variable controls.
• Two-way communication allows devices to report their status and confirm whether they are responding to network limits.
• CER manufacturers and integrators may need to support CSIP-AUS directly or allow their equipment to be controlled through an external energy management system.

What load control features does CSIP-AUS support?

CSIP-AUS enables the communication of dynamic import and load limits:

• Flexible Import Limits: A site import limit can be applied (opModImpLimW) to cap total power draw from the grid. This requires flexible loads like EVSE or BESS, etc. to be managed or curtailed if the total site import exceeds the specified level.
• Load Limits: CSIP-AUS also defines a load limit control (opModLoadLimW) that relates to the net load of the CER system under management.

CSIP-AUS presents several benefits over other load control mechanisms:

• Ripple Control technologies: CSIP-AUS allows for controls to be targeted at a set of devices, rather than applying to all devices in a network area.
• Load Control Circuits: CSIP-AUS allows for more granular specification of limit values than those available through AS/NZS 4755, or through opening/closing a circuit in a meter.

CSIP-AUS also enables two-way communication for telemetry and acknowledgment. Devices must report status (e.g. current power) back to the utility server, confirming conformance with limits. This two-way communication ensures the network has visibility of CER behaviour which improves the network operator’s ability to develop more targeted controls and generally manage the network efficiently within network limits.

How are multiple CER devices coordinated onsite?

Flexible import limits are applied at the site-level and are relevant to all controllable CER (uncontrolled generation and load) at a customer’s premises. For example, if a network tightens an import limit, the customer can respond by reducing load from any flexible device or increasing generation from a BESS. This provides flexibility to decide how available load capacity is utilised and prioritise between loads.

Importantly, as network operators generally only allow for one CSIP-AUS EndDevice per site, all load and generation resources that form part of the system must be coordinated by a single EMS. This ensures that all controllable assets can collectively meet the import limits while optimising device usage within them.

More information on interoperability and product design considerations for DOEs is provided in the section CER Technical and Interoperability Standards.

How is CSIP-AUS currently being used for load control?

Energy Queensland (Energex/ Ergon Energy) provides an option for assets to be connected to their CSIP-AUS Utility Server to enable Dynamic EVSE management. This is explored further in the article on Load control requirements for EVSE in Queensland. A key advantage of this option is that it allows the EVSE to be connected to the customer’s main circuit where it can self-consume any local solar production. Coupled with Flexible Exports, this can provide greater utilisation of existing customer and network assets, reducing network costs and maximising value for the customer.

While the current priority for DNSPs remains enabling emergency backstop capability, CSIP-AUS provides the foundational technology capabilities to enable a range of other use cases. Outside Queensland the use of CSIP-AUS for network load control is currently limited to trials, however there is interest from parties in leveraging this existing technology for load-based use cases.

What should CER product developers consider?

The need for manufacturers and integrators of CER equipment to ensure compatibility with CSIP-AUS load control schemas is becoming increasingly important.

Key considerations for CER product developers include:

• Implementing CSIP-AUS: Product developers should consider either building native support or partner with hardware or software solution provider to provide the required capabilities.
• BTM ecosystem integration: Most CSIP-AUS deployments require compliance with site-level limits. Where there are multiple assets installed on site they must be coordinated to comply with these site level limits. OEMs can facilitate this by providing an interface for an external controller to override device set-points through a standard communications protocol.

For instance, an EVSE might support control through OCPP or Modbus, allowing for a site controller to receive site level CSIP-AUS signals and determine and set power values or limits for the EVSE. Product developers should consider designing their solutions to support this interoperability, maximising the ability for their products to be installed on sites with equipment and products from other OEMs.

• Product testing and certification: Where developers are operating a CSIP-AUS client solution they should consider achieving certification through the national CSIP-AUS testing and certification service (more details are available via csip-aus.org) to ensure their implementation is interoperable with a reference implementation.
• Tracking DNSP load control requirements: Some networks already require certain CER devices to be “communication-ready” as a condition of connection. Developers should track communication and capability requirements and ensure their products meet the requirements for listing in each region.

Related articles

• Network load control schemes
• CER Technical and Interoperability Standards
• Load control requirements for EVSE in Queensland
• Utility Interconnection (CSIP-AUS)
• Dynamic network export and generation control schemes