ERP Reference Desk

Why it matters

Storage operating constraints and state of charge affect the feasibility of reserve offers and dispatch.

Confirmed design

Operating-reserve considerations intersect with current optimization and dispatch-data design.
Sources: Storage and Co-located Hybrid Integration - Optimization · Storage and Co-located Hybrid Integration - Dispatch Data and Other Inputs

Implementation status and limitations

Treat as a cross-module Phase 1 topic.

This dossier is an orientation aid and not a substitute for applicable market rules.
Sources: Enabling Resources Program - Framework and Modules

Open questions

Which reserve-specific implementation details remain outside the available design memos?

Build a handoff from this dossier

Build a source-bounded prompt locally. Nothing is sent until you choose what to do with it.

Question or outcomeAnalysis depth

Selected evidenceStorage and Co-located Hybrid Integration - OptimizationStorage and Co-located Hybrid Integration - Dispatch Data and Other Inputs

Generated handoff

# ERP Phase 1 evidence handoff

## Outcome
Explain the selected ERP material and identify the implications for Phase 1 work.

## Selected evidence
- [2026-05-06-design-memo-storage-and-co-located-hybrid-integration-optimi-41a5324f] Storage and Co-located Hybrid Integration - Optimization — IESO; 2026-05-06; authority: controlling; review: reviewed; https://www.ieso.ca/-/media/Files/IESO/Document-Library/engage/erp/SHIP1-20260420-Optimization.pdf
- [2026-05-06-design-memo-storage-and-co-located-hybrid-integration-dispat-1aa9a2df] Storage and Co-located Hybrid Integration - Dispatch Data and Other Inputs — IESO; 2026-05-06; authority: controlling; review: reviewed; https://www.ieso.ca/-/media/Files/IESO/Document-Library/engage/erp/SHIP1-20260420-Dispatch_Data_and_Other_Inputs.pdf

Selected concept dossiers:
- [operating-reserve] Operating Reserve: Standby market capability that can be activated to support system reliability.

## Authority rules
- Treat current IESO-authored design memos as controlling program design unless a later Market Rule, Market Manual, or IESO publication supersedes them.
- Do not claim implementation unless a Market Rule, Market Manual, or other official implementation source proves it.
- Keep stakeholder submissions attributed to their authors; attribute stakeholder positions and do not present them as IESO decisions.
- Use superseded and historical sources only for lineage. Label what changed.
- Treat recordings as catalog-only unless a reviewed transcript is explicitly supplied.
- If two sources conflict, prefer the later higher-authority source and describe the conflict.

## Citations
Cite every substantive claim with document title, publication date, page when available, document ID, and canonical URL. Never invent a page number.

## Known gaps
- No review-status gaps are identified in the selected evidence.

## Requested depth
Give a practical, structured analysis suitable for daily program work. Distinguish confirmed design, history, stakeholder feedback, and open questions.

## Answer format
1. Direct answer
2. Confirmed ERP design
3. Historical or stakeholder context
4. Phase 1 implications
5. Open questions and evidence gaps
6. Source list

Work only from the selected evidence. If the evidence is insufficient, say exactly what is missing.

Open ChatGPT Open Codex