By AGILE Consulting Engineers, Solar PV and Battery Energy Storage Systems (BESS) specialists.
A battery doesn’t just export power to the grid, it also imports it, often at short notice and in the opposite direction to what a distribution network service provider (DNSP) is used to seeing from a solar array. That bi-directional behaviour is the reason BESS connection applications get more scrutiny than a comparably sized solar-only system, and why a design that looks straightforward on a single line diagram can still stall at the connection assessment stage if the protection and control philosophy hasn’t been thought through for both flow directions.
Table of Contents
- Why Batteries Are Assessed Differently to Solar-Only Systems
- The Standards Underpinning a BESS Connection
- Connection Pathways and Capacity Thresholds
- Protection Settings and Anti-Islanding for Batteries
- Export and Import Limits, and Dynamic Connections
- Metering, Visibility and Communications Requirements
- What DNSPs Want to See in a Connection Application
- What to Do Next
- FAQ
Why Batteries Are Assessed Differently to Solar-Only Systems
A DNSP’s core concern in any connection assessment is network security: voltage rise, fault level contribution, protection coordination and the risk of unintended islanding, where part of the network keeps operating on local generation after it’s been disconnected from the main grid. Solar-only systems present a fairly predictable profile, generation follows daylight and inverter output ramps in a known pattern. A BESS can charge and discharge on a schedule set by a site’s tariff arrangement, a virtual power plant (VPP) dispatch signal, or a frequency control ancillary services (FCAS) response, which means the network sees load and generation behaviour that can change direction within minutes. DNSPs need confidence that the system’s protection and control philosophy accounts for both directions of flow, not just export.
The Standards Underpinning a BESS Connection
Every DNSP connection in the National Electricity Market (NEM) sits on a common standards base: AS/NZS 3000 for the electrical installation itself, and AS/NZS 4777.1 and AS/NZS 4777.2 for grid connection of inverter energy systems. AS/NZS 4777.1 covers installation requirements while AS/NZS 4777.2 covers inverter performance requirements, and from 23 February 2025 compliance with AS/NZS 4777.1:2024 and AS/NZS 4777.2:2020 became mandatory for inverters connecting at low voltage. Interface protection, the equipment that detects an abnormal network condition and disconnects the system, is a mandatory requirement once the aggregated inverter capacity at a site exceeds 30 kVA. Individual DNSPs can depart from the default settings in AS/NZS 4777.1 where local network conditions require it, so a design based purely on the standard’s default values without checking the relevant DNSP’s technical requirements is a common source of delay.
Connection Pathways and Capacity Thresholds
Smaller systems typically proceed through a DNSP’s standard or basic connection process, largely governed by the inverter standards above and the DNSP’s own technical guidelines. Larger systems, and standalone BESS in particular, move into a more involved negotiated connection process. Under the National Electricity Rules (NER), anyone operating a generating system is generally required to register with the Australian Energy Market Operator (AEMO) once nameplate capacity reaches 5 MW, with systems between 5 MW and 30 MW sometimes eligible for exemption depending on how the output is contracted or dispatched. Standalone BESS connections are addressed specifically under NER clause 5.3.4A and schedule 5.2, which set out how access standards are negotiated between the connection applicant, the DNSP or transmission network service provider, and AEMO. AEMO has also been working to streamline technical connection requirements for solar, wind and BESS projects, with reforms aimed at reducing the time and cost of the connection process for new applications from mid-2025 onward.
Protection Settings and Anti-Islanding for Batteries
Because a BESS can supply load locally even when disconnected from the grid, anti-islanding protection needs particular attention in the design. The control philosophy has to clearly define how the system detects loss of mains, how quickly it disconnects, and how it behaves during reconnection, including any requirements around soft-start or ramp rates to avoid destabilising the local network. This is closely tied to the wider control and monitoring architecture of the site, which is why protection philosophy is usually developed alongside the broader design work covered in AGILE’s article on control philosophy and SCADA design for solar and BESS systems, where supervisory control and data acquisition (SCADA) architecture and protection logic are treated as a single coordinated design task rather than separate workstreams.
Export and Import Limits, and Dynamic Connections
Many DNSPs now offer, or require, some form of export limitation for connections in constrained parts of the network, and a growing number are moving toward dynamic connection arrangements where the allowable export or import limit varies in near real time based on network conditions rather than being fixed at a single static value. For a BESS, this has direct implications for the energy management system (EMS) and control logic, which need to respond to a DNSP-issued limit signal without compromising the site’s own operational objectives, whether that’s peak demand management, FCAS participation or VPP dispatch. Designing for a static limit when the local DNSP is moving toward dynamic connections is a common gap that surfaces late in the connection application process.
Metering, Visibility and Communications Requirements
DNSPs increasingly expect visibility of a BESS’s operating state, not just its net import or export at the connection point. This can include separate metering of charge and discharge, remote monitoring access, and in some cases a requirement for the DNSP to be able to curtail or disconnect the system remotely under defined conditions. These requirements need to be reflected accurately on the electrical design documentation submitted with the connection application, and inconsistencies between what’s shown on the single line diagram and what’s described in the supporting technical documents are a frequent cause of requests for information from the DNSP, adding weeks to an otherwise straightforward application.
What DNSPs Want to See in a Connection Application
A complete application typically includes an accurate single line diagram, protection settings and coordination study where required, inverter and battery datasheets confirming standards compliance, and a clear description of the control and communications architecture. AGILE’s guide to single line diagrams for solar and BESS projects covers what a DNSP actually expects to see on this document, which is often the first thing a network engineer reviews and the fastest way to either build or lose confidence in the rest of the application. Applications that are internally consistent across all documents, and that reference the correct DNSP-specific technical requirements rather than generic standard defaults, tend to move through assessment noticeably faster.
What to Do Next
DNSP connection requirements for battery storage sit at the intersection of network engineering, protection design and control system architecture, and they differ enough between distribution areas that a generic approach rarely survives first contact with a real application. Working through these requirements as part of the design process, rather than after a connection application has already been lodged and queried, is a core part of AGILE’s BESS engineering service.
FAQ
Why does a battery system face more scrutiny than a solar-only system at connection?
Because a BESS can both import and export power, sometimes changing direction within minutes depending on dispatch signals or tariff arrangements, DNSPs need confidence that protection, anti-islanding and control settings are designed for both directions of flow, not just export, which is the primary behaviour a solar-only system exhibits.
What standards apply to a BESS connection in Australia?
AS/NZS 3000 covers the electrical installation, while AS/NZS 4777.1 and AS/NZS 4777.2 cover installation and performance requirements for inverter energy systems connecting to the grid. From 23 February 2025, compliance with AS/NZS 4777.1:2024 and AS/NZS 4777.2:2020 became mandatory for low voltage connected inverters, alongside each DNSP’s own technical connection requirements.
Does every BESS need to register as a generator with AEMO?
Generally, registration obligations under the National Electricity Rules apply once a generating system’s nameplate capacity reaches 5 MW, with some exemptions available between 5 MW and 30 MW depending on how the output is contracted or dispatched. Standalone BESS connections are addressed specifically under NER clause 5.3.4A and schedule 5.2.
What is a dynamic connection and why does it matter for a BESS?
A dynamic connection allows the export or import limit at a site to vary in near real time based on actual network conditions, rather than being fixed at a single static value. For a BESS, this means the energy management system needs to be able to respond to a variable DNSP-issued limit signal, which is a different design requirement to a fixed static export cap.
How long does a DNSP connection application typically take for a BESS?
Timeframes vary significantly by DNSP, system size and connection pathway, and depend heavily on whether the application is complete and internally consistent on first submission. Standard connections for smaller systems are generally faster than negotiated connections for larger or standalone BESS, which involve more parties and a more detailed technical assessment.
What’s the most common reason a BESS connection application gets delayed?
Inconsistencies between the single line diagram, protection settings and supporting technical documentation are a frequent cause of requests for further information, along with designs based on generic standard defaults rather than the specific DNSP’s published technical requirements for the area.
