Case study: network constraint response

Curtailment periods, export disclosure to lenders, and coordination with market registration updates.

Operations desk with grid monitoring displays
Wind turbines on ridge under variable cloud cover

Owner context

South Australian system strength and congestion patterns can limit export when wind is available. Investors modelling nameplate capacity without constraint history misprice risk. HORNSDALE ASSET CO PTY LTD documented constraint experience for board and lender packs rather than treating curtailment as an operator-only topic.

Problems encountered

Protection setting changes after system disturbances required re-study of fault levels at the connection point. Registration updates lagged operational reality during storage augmentation, creating compliance grey zones. Internal revenue forecasts sometimes used pre-constraint assumptions inherited from development models.

Measures taken

The owner aligned public grid brief language with internal constraint logs shared under confidentiality. Curtailment episodes were classified by cause—network, unit, or market instruction—for lender reporting. Dispatch was curtailed when registration identifiers were misaligned, accepting short-term revenue loss over regulatory exposure.

Outcomes

Board packs include constraint themes alongside availability statistics. Refinancing advisers could reconcile market data with owner narratives without ad hoc explanations. Grid connection and NEM participation materials cross-link from this case for continued reading.

Case study FAQ

Does this case provide a curtailment forecast?
No. It describes governance and disclosure. Forecasts belong in finance models supplied under entitlement.
Where are connection studies summarised?
See the grid and market connection project brief for institutional correspondence and connection compliance themes.