All articles

Batteries in practice · Historical case study

When lightning tripped a power line, the battery responded

Published:

Case period: 2018–2020

An electricity disturbance can develop faster than a person can read an alert. When assessing a battery, the useful question is therefore not only how much energy it holds, but what the complete system can do in the first moments of a fault. Dalrymple in South Australia provides a practical example of that distinction.

A disturbance that needed a rapid response

In December 2019, lightning tripped a nearby power line and the ESCRI battery maintained Dalrymple’s electricity supply. ARENA’s review also records 29 system events between December 2018 and 2020, and a separate disturbance after which the network became stable within 2.5 seconds.

These numbers describe different observations. The event count covers experience over a period; the time describes the outcome of one particular response. They do not document 29 outages of the same duration. Keeping the measures separate helps a reader understand what operating experience demonstrates, without turning an impressive result into a broader claim.

Source: ARENA

A system designed for the task

ARENA describes ESCRI as a 30 MW / 8 MWh battery designed for network support and market services, working alongside local wind and solar generation. It is an engineering solution for a particular location, rather than simply a box of batteries connected to a power line.

An islanded network is a section that temporarily operates without its normal connection to the larger system. Stored energy alone is insufficient for that task: controls, protection, connections and local equipment must work together. Two batteries with the same stated energy capacity therefore need not have the same ability to support an isolated network.

Source: ARENA

Three questions instead of one

First, how quickly does the system respond? Second, what condition does it help maintain: does it contain a brief disturbance, or keep customers supplied? Third, for how long can it provide that support under the circumstances? Compressing those answers into one prominent number loses much of the information needed to evaluate a project.

Consider two different customer needs. One customer may be concerned about a short interruption stopping an industrial process. Another may need energy over a longer period. Both may be interested in storage, but their specifications will differ. This comparison implies no universal battery model: define the problem first, then assess the solution against that problem.

What the case helps us understand

Dalrymple is useful to remember when the battery market appears to be only a chart of electricity prices. A customer may value continuity, an operator may focus on system behaviour during a fault, and an asset owner may need a clearly defined service. These are connected but different perspectives. Technical usefulness alone does not tell us how that service will be paid for.

Our companion ESCRI article examines revenue separately. The lesson here is that a dependable response comes from a complete engineering solution. For a proposed project, ask which function is intended and how it will be verified. A historical result at another site provides a valuable question to investigate; it does not automatically become a capability of whichever battery is selected.

Sources and dates