ERP Reference Desk

Why it matters

It is the umbrella for the Storage and Co-located Hybrid and DER integration workstreams.

Confirmed design

ERP is organized into defined projects and design modules.
Sources: Enabling Resources Program - Framework and Modules

Implementation status and limitations

Phase 1 design and engagement are active; implementation details remain document-specific.

The framework document supports orientation but does not replace current module design memos.
Sources: Enabling Resources Program - Framework and Modules

Open questions

Which later-phase issues will be prioritized after Phase 1?

Decision and version timeline

2024-11-20 — ERP framework and modules published

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 evidenceEnabling Resources Program - Framework and ModulesEnabling Resources Program

Generated 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
- [webpage-program] Enabling Resources Program — IESO; undated; authority: primary-supporting; review: unreviewed; https://www.ieso.ca/Sector-Participants/Engagement-Initiatives/Engagements/Enabling-Resources-Program

Selected concept dossiers:
- [erp-program] Enabling Resources Program: The IESO program that develops participation models for resources that do not fit cleanly within existing market rules.

## 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
- webpage-program: unreviewed; primary-supporting. Verify before relying on content-specific claims.

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