By AGILE Consulting Engineers, Solar PV and Battery Energy Storage Systems (BESS) specialists.
Most project delays at the connection stage are not caused by a difficult Distribution Network Service Provider (DNSP). They are caused by an application that was not designed to be approved in the first place. A connection application built on assumptions, rather than on modelled fault levels, protection coordination and clear single line documentation, tends to bounce back with information requests that cost weeks, sometimes months.
Table of Contents
- What a DNSP Actually Assesses
- Connection Pathways and Why They Matter for Design
- The Technical Documentation a Connection Application Needs
- Protection Settings and Why They Are Central
- Export Limits and Generation Management
- How Detailed Design Supports the Application
- Common Pitfalls That Slow Connection Approval
- What to Do Next
- FAQ
What a DNSP Actually Assesses
A Distribution Network Service Provider (DNSP) owns and operates the poles, wires, substations and transformers that make up the local electricity distribution network. When a solar PV or Battery Energy Storage System (BESS) project connects to that network as embedded generation, meaning generation connected at distribution voltage rather than directly to the transmission grid, the DNSP has to satisfy itself that the new connection will not degrade power quality, safety or reliability for other customers on the same feeder. That assessment covers fault level contribution, voltage rise, protection coordination, harmonic injection and, for larger projects, dynamic performance during network disturbances.
It helps to remember that the DNSP is not assessing your project in isolation. It is assessing what your project does to a shared, finite piece of network infrastructure that other customers also depend on. Every technical requirement in a connection agreement traces back to that shared-asset reality, which is why generic answers rarely satisfy a reviewer and project-specific modelling usually does.
Connection Pathways and Why They Matter for Design
Australian DNSPs generally sort embedded generation connections into tiers based on capacity, ranging from small inverter-connected systems assessed against a standard technical guideline through to larger generators that require individual negotiation and detailed studies. Energy Networks Australia’s National Distributed Energy Resources (DER) Grid Connection Guidelines set out a nationally consistent framework that individual DNSPs then apply with their own network-specific variations, and AEMO has separately been consulting on technical requirements for sub 5 MW DER connections, with a final consultation report published in 2025. Because the exact capacity thresholds, application timeframes and required studies vary between DNSPs and change periodically, a design team needs to confirm the current pathway with the relevant network at the start of a project rather than assuming last year’s rules still apply.
The pathway a project falls into shapes almost everything downstream. A basic connection under a standard technical guideline is largely a compliance exercise against published inverter and protection standards. A negotiated connection for a larger solar or BESS asset typically requires load flow studies, fault level studies and sometimes dynamic modelling, all of which need to be reflected in the detailed design well before the application is lodged.
The Technical Documentation a Connection Application Needs
A connection application is, at its core, a technical submission. DNSPs typically expect a Single Line Diagram (SLD) showing the point of connection, protection devices and metering arrangement, a protection schedule with proposed relay settings and coordination logic, equipment datasheets and type test certificates for inverters and Power Conversion Systems (PCS), and a description of how the system will behave under normal operation, fault conditions and network disturbances. For BESS specifically, DNSPs also want to understand charge and discharge behaviour, how the system responds to network signals, and how protection distinguishes between the battery, the inverter and the grid interface.
None of this documentation is generated cheaply after the fact. It is a natural output of a properly sequenced detailed design process, which is one reason connection applications assembled from a preliminary or concept-stage design so often come back with requests for further information.
Protection Settings and Why They Are Central
Protection is where a lot of connection reviews slow down, and for good reason. The DNSP needs confidence that a fault on the network will be isolated quickly and selectively, without the embedded generator either failing to disconnect when it should, or nuisance-tripping when it should not. Protection requirements for inverter-connected systems in Australia are set out in AS/NZS 4777.2, and since 23 February 2025 all new low-voltage connected inverters have been required to comply with AS/NZS 4777.1:2024, so a design team needs to keep current on which edition and transitional arrangements apply to a given project.
Coordinating protection is not a matter of copying settings from a similar project. Fault levels, feeder impedance, existing protection on the network and the specific inverter or PCS behaviour all differ from site to site. Detailed design is where these variables get modelled and reconciled into a settings proposal the DNSP can actually approve, rather than query.
Export Limits and Generation Management
Many embedded generation connections, particularly at lower voltage or on constrained feeders, are approved subject to an export limit, a cap on how much power the system can push back into the network at any given time. The specific limit is always network and site specific, driven by feeder capacity, transformer headroom and what else is already connected nearby, so it is not something a design team should assume or quote generically. What detailed design does is translate a DNSP-imposed export limit into a workable generation management scheme, whether that is a fixed inverter setting, a dynamic export limiting system responding to real-time measurements, or a BESS dispatch strategy that manages the site’s net export profile.
Getting this translation wrong has real consequences. An export limiting scheme that is poorly specified can either leave value on the table by curtailing more generation than necessary, or fail to hold the agreed limit reliably, which risks a compliance breach after the system is commissioned.
How Detailed Design Supports the Application
Detailed design and the connection application are not two separate workstreams that happen to run in parallel. They inform each other continuously. Fault level and load flow modelling done during detailed design feeds directly into the protection schedule submitted to the DNSP. The SLD produced for construction is the same document, refined, that supports the application. Equipment selection, particularly inverter or PCS models and their certified compliance with AS/NZS 4777.2 or equivalent standards, needs to be locked in early enough that datasheets and certificates are ready when the application is lodged.
Sequencing detailed design ahead of, or genuinely alongside, the connection application, rather than treating the application as a formality to be handled after design is finished, is one of the more reliable ways to keep a project’s connection timeline predictable.
Common Pitfalls That Slow Connection Approval
A handful of recurring issues show up across projects that experience connection delays. Preliminary single line diagrams get submitted before equipment selection is finalised, which means the DNSP is reviewing a document that will change. Protection settings are proposed without site-specific fault level studies behind them. Export limiting schemes are described conceptually without enough detail on how they will be implemented and tested. And in some cases, a project team engages with the DNSP too late, after design decisions that affect connection feasibility have already been locked in with a builder or supplier.
Each of these is avoidable with a design process that treats the connection application as a core deliverable rather than an administrative afterthought.
What to Do Next
If your project is heading toward a DNSP connection application and the technical documentation is still light on protection modelling, export limit strategy or a finalised SLD, it is worth resolving that before the application is lodged rather than after it is queried. AGILE’s solar and BESS system design service covers the electrical design work, including protection coordination and connection documentation, that underpins a connection application built to be approved on its first pass rather than its third.
FAQ
What is embedded generation?
Embedded generation refers to generating plant, such as solar PV or BESS, connected directly to the distribution network rather than the transmission grid, which is why DNSPs rather than AEMO typically manage the connection approval process for these projects.
How long does a DNSP connection application take?
Timeframes vary significantly by DNSP, connection tier and project complexity, and are published in each DNSP’s own connection guidelines, so it is best confirmed directly with the relevant network rather than assumed from another project.
Do export limits apply to every solar or BESS connection?
Not every connection is limited, but many are, particularly on feeders with limited spare capacity, and the specific limit is set by the DNSP based on network conditions at the connection point rather than a fixed national figure.
What standard governs inverter protection settings in Australia?
AS/NZS 4777.2 covers inverter protection requirements for grid connection, and as of 23 February 2025 new low-voltage connected inverters must also comply with AS/NZS 4777.1:2024, so current editions should be confirmed for each project.
Why does a BESS need different connection documentation to solar PV alone?
A BESS can both import and export power and its behaviour depends on dispatch strategy, so DNSPs typically want additional detail on charge and discharge operation, protection between the battery and the grid interface, and how the system responds to network conditions, beyond what a solar-only system requires.
Can detailed design start before the DNSP application is lodged?
Yes, and in practice it generally should, since the protection modelling, single line diagram and equipment selection produced during detailed design are the same technical basis the connection application relies on.
