ERP Reference Desk

Why it matters

Reliable inputs are essential to feasible dispatch and meaningful settlement.

Confirmed design

The May 2026 dispatch-data memo supersedes the January 2026 version.
Sources: Storage and Co-located Hybrid Integration - Dispatch Data and Other Inputs · Storage and Co-located Hybrid Integration - Dispatch Data and Other Inputs

Implementation status and limitations

Current Phase 1 design.

The memo should be read with optimization and connection requirements.
Sources: Storage and Co-located Hybrid Integration - Optimization · Storage and Co-located Hybrid Integration - Connection and Registration

Open questions

How will missing, delayed, or inconsistent operational data be handled?

Decision and version timeline

2026-05-06 — Current dispatch-data memo

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 depthGenerated 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-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:
- [dispatch-data] Dispatch Data and Other Inputs: The operational data used to communicate, assess, and issue market dispatch for storage and hybrid resources.

## 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