Interruption schedules
Versioned schedules used by storage and outage modelling.
Reviewed
What this is for
Who supplies a site, which group it is interrupted with, and when. Curated and effective-dated, exactly like a tariff: a proposal that promised a number of hours of cover has to reproduce that figure next year against the schedule that applied when it was issued. Editing a schedule in place would destroy that silently.
The page is named for this market's own word for planned supply interruptions. The pack is a representative rota, not a published block table for every suburb. Hours a day step by a fixed increment per stage, printed on the row. Group count is this pack's. Do not treat the calendar as a named street. That is why most rows read Never reviewed.
A market that publishes no such schedule models every site with the grid available in every hour. That is a real answer rather than a missing feature.
Hours of cover a storage model reports live on Outages and autonomy. This article is the library.
Steps
- Open Schedules.
- Choose a supplier. The list is this market's distributors. The facts card gives its group and schedule counts, its export terms, when it was last reviewed, and any filing portal.
- Choose a supply group.
- Published versions lists stages. Each stage has an effective date, hours per cycle, hours a day, last reviewed, and Show. Hours a day steps by a fixed increment per stage, printed on the row.
- Show draws that stage's month of interruptions below the table. Last reviewed is recorded by whoever runs this deployment, because the schedule is shared by every team on it. "Never reviewed" means nobody has checked these figures against a published source.
- Attach a supplier and a group to a project on its Grid connection card. Storage and outage modelling read that pairing. This library does not assign a suburb for you.
Tips and common mistakes
- Do not treat the calendar as a published rota for a named street. It is a representative pattern with the right hours. Say so on a proposal.
- The increment between stages is the structure the pack is built to reproduce, not a set of unrelated numbers.
- Review dates are deployment-wide, not per team. You cannot "review" a row from this screen.