Record outage schedules, mitigating measures, and saved changes. Review the available tools and proposed coordination features below.
Current capabilities and the next product priorities, clearly separated.
Enter shared details once. Select a date range, preview the daily logs, and save the batch. Explicit time zones, overnight intervals, and schedule revision history keep operating time separate from entry time.
Outage outlook connects outage windows, recorded alternatives, named dependencies, and overlap checks with a copyable shift handoff. Next: prioritize missing mitigating measures and approaching restoration times.
A dedicated section in the Outages Log keeps operating options with each outage. Operators can add, edit, or delete measures. Every change records who did it, when, the previous text, and an optional reason. Next: ranked priorities and reusable measures.
Saved reference values and log history already reduce repeat work. Proposed additions include reusable mitigating measures and exactly three recent contacts per counterparty. Preserve who changed each field, its previous value, and when the change was saved.
Proposed: participating utilities would share selected outage facts. A path diagram and shared timeline would show relevant overlaps for review and coordination.
Ranked presentation · proposed refinement
Record availability, delivery arrangements, and applicable operating limits.
Keep purchase arrangements and delivery points with the outage.
Record the delivery split and its operating conditions with this measure.
Illustrative measures based on the supplied outage. Ranked priorities and structured delivery-path fields are proposed refinements.
CHANGE HISTORY
Example: Mit. Measure #1 was deleted by Alex at Sep 14, 2026, 12:10 PDT. Reason: Replaced by an updated delivery plan. If no reason is entered, the reason is omitted. Additions and edits are recorded in the same history.
Measure number · Measure text · Added, edited, or deleted by · Timestamp · Previous and updated text · Optional reason
The example below pairs a path diagram with a shared timeline. Keep the selected outage, alternate paths, delivery points, and relevant neighboring outages in view. Expand to a utility-approved BES one-line when validated topology is available.
Sep 14, 2026 · PDT
Illustrative coordination scenario. Schematic connections only; no live utility data, verified topology, or available transfer capability.
Tracy–Westley #1 / #2 08:00–18:00
Neighbor A restriction Not added to scenario
Sharing utility · Asset / affected path · Start / expected end · Reported impact · Source and revision · Updated at / fresh or stale · Coordination owner / acknowledgment
Only explicitly shared outage facts. Private trade details and contact histories remain inside the originating workspace. Missing or stale information never becomes an “available” path.
This proposal would make saved field values reusable and suggest the three most recent contacts for each counterparty. Try the example below; its entries are temporary.
A name leaving the dropdown never leaves its historical log. A prefilled contact is a suggestion, not confirmation of a conversation.
CONTACT MEMORY DEMO
Fictional names. Temporary state on this page; resets on reload.
Select a recent name or enter a fourth name, then save to see the ordering change.
Add, edit, and delete mitigating measures with a complete change history. Next: priority ordering, reuse, and shift handoff.
Start with selected outage facts from participating utilities and explicit sharing agreements. Keep private trade details and personal contact history inside the originating workspace.
Add approved topology and authorized feeds. Match both time overlap and a mapped dependency. Stale or missing data stays visible; an overlap requests review and never certifies feasibility or outage approval.
Design context: RC West describes outage communication and conflict coordination. CAISO treats transmission outage information as confidential. These sources inform the proposed sharing model; they do not validate this illustrative operating plan. RC West outage coordination process. CAISO outage management.