Outages and autonomy
Interruptions, backup cover, and the curated schedule library.
Reviewed
What this is for
How long the bank carries the load when the grid is not there, and against which published rota. Without a bank, a grid-tied inverter disconnects for the whole interruption. Autonomy is that gap, measured.
The library is curated, effective-dated and never edited in place, exactly like a tariff. A proposal that promised eight hours of cover has to reproduce that figure next year against the schedule that applied when it was issued.
What ships is a representative rota. Hours a day per stage are exact; which suburb sits in which group is not. Every row that has not been reviewed says so. How the library is organised is Interruption schedules. This article is the hours of cover a storage model reports.
Steps
- The site's supplier and supply group are set on Grid connection, not on Storage. Storage states what it is working from. If the site names no group, a model at step zero has no rota to apply and the grid is modelled as available in every hour; a model set above zero is not ready to compute until the group is chosen.
- Where the market publishes a schedule, the severity step (zero is uninterrupted supply) and Schedule as at are set on the model's Setup tab, and the strip repeats both - the date is stored, so figures reproduce. Schedules on the sidebar, or on the Storage head, is the curated book.
- Once computed: Outage cover is typical hours from a full bank. Worst outage is the least the bank carried. Both dash when they do not exist - a year with no interruption reports a dash, not
0 h. Outages covered in full is a count of interruptions, of how many there were. Unserved load is what the site asked for and did not get. - Availability on a condition set is uptime of the plant, not a tariff outage. Do not fold one into the other.
A market that publishes no schedule models every site with the grid available in every hour, and the two interruption tiles are not drawn - a cell reading 0 would say the grid was modelled as uninterrupted for a reason nobody chose.
Tips and common mistakes
- Do not treat Never reviewed as a broken table. The hours-per-step arithmetic is exact; the suburb-to-group map is not a claim anybody has earned.
- A limiter set to zero and no limiter are different. Compliance reads the two differently; so does export during an interruption.
- Backup-only with severity at zero is a bank that never discharges for the grid. That is a real scenario, not a missing input.