ERP Reference Desk

Why it matters

ERP materials can appear to conflict when their authority, date, and role are not kept visible.

Confirmed design

The current design memos supersede named earlier versions for their modules.
Sources: Storage and Co-located Hybrid Integration - Connection and Registration · Storage and Co-located Hybrid Integration - Dispatch Data and Other Inputs · Storage and Co-located Hybrid Integration - Market Power Mitigation · Storage and Co-located Hybrid Integration Project - Settlements

Implementation status and limitations

Applied as metadata and ranking rules throughout this reference.

A cataloged recording is not treated as reviewed evidence until it has been transcribed or content-reviewed.
Sources: Recorded Presentation

Open questions

Which future IESO publications will formally replace current authorities?

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
- [2024-11-20-design-memo-enabling-resources-program-framework-and-modules-6a283195] Enabling Resources Program - Framework and Modules — IESO; 2024-11-20; authority: primary-supporting; review: reviewed; https://www.ieso.ca/-/media/Files/IESO/Document-Library/engage/erp/erp-20241120-design-memo.pdf

Selected concept dossiers:
- [evidence-and-authority] Evidence and Authority: A reading rule that separates controlling IESO design, supporting IESO material, superseded versions, responses, stakeholder positions, historical context, and recordings.

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