Context tool
Plain-language dossiers connect confirmed ERP design, limitations, open questions, version history, and the documents that support each statement.
2 linked sources
The IESO program that develops participation models for resources that do not fit cleanly within existing market rules.
Why it matters: It is the umbrella for the Storage and Co-located Hybrid and DER integration workstreams.
1 linked sources
A reading rule that separates controlling IESO design, supporting IESO material, superseded versions, responses, stakeholder positions, historical context, and recordings.
Why it matters: ERP materials can appear to conflict when their authority, date, and role are not kept visible.
2 linked sources
The sequence from design material, stakeholder engagement, IESO response, and rule or system implementation.
Why it matters: A proposal, a response to feedback, and an implemented requirement are different evidence states.
2 linked sources
The market participation design for electricity storage resources, including single- and distributed-market models.
Why it matters: It frames how storage is registered, optimized, dispatched, settled, and mitigated.
2 linked sources
A storage participation model represented through a single market schedule.
Why it matters: It determines how the resource's operating state and market activity are represented.
2 linked sources
A storage participation model whose market representation uses distributed schedules.
Why it matters: It affects registration, dispatch inputs, optimization, and settlement treatment.
2 linked sources
The stored-energy state used to assess what an electricity storage resource can feasibly do.
Why it matters: State of charge constrains dispatch feasibility and connects offers, optimization, and operations.
2 linked sources
The market-engine treatment used to evaluate feasible storage and hybrid schedules.
Why it matters: Optimization connects bids and offers to state of charge, dispatch outcomes, and settlement results.
1 linked sources
The requirements that establish how a storage or hybrid facility is connected and represented as market resources.
Why it matters: Registration structure is the foundation for dispatch, settlement, and accountability.
1 linked sources
The operational data used to communicate, assess, and issue market dispatch for storage and hybrid resources.
Why it matters: Reliable inputs are essential to feasible dispatch and meaningful settlement.
2 linked sources
Standby market capability that can be activated to support system reliability.
Why it matters: Storage operating constraints and state of charge affect the feasibility of reserve offers and dispatch.
3 linked sources
The financial calculation and adjustment of market outcomes for participating resources.
Why it matters: Settlement design determines how dispatch and price outcomes become credits and charges.
1 linked sources
A settlement structure that distinguishes day-ahead commitments from real-time outcomes.
Why it matters: Storage schedules can differ across day-ahead and real-time horizons, creating balancing credits or charges.
1 linked sources
A settlement mechanism associated with differences between day-ahead and real-time market outcomes.
Why it matters: It is part of understanding how storage schedules and dispatch changes are financially reconciled.
3 linked sources
Settlement adjustments intended to address eligible cost or revenue outcomes under defined market rules.
Why it matters: Storage operating modes and commitments can create settlement circumstances that need explicit treatment.
2 linked sources
Operating points associated with economically evaluated resource schedules and dispatch.
Why it matters: They connect storage capability, optimization, dispatch, and settlement outcomes.
1 linked sources
Rules and processes intended to limit the exercise of market power in relevant market circumstances.
Why it matters: Storage and hybrid participation introduces resource characteristics that must fit the mitigation framework.
2 linked sources
A facility arrangement in which different technologies share a connection while retaining relevant market representations.
Why it matters: Shared facilities create registration, dispatch, optimization, and settlement interactions.
4 linked sources
The ERP workstream for integrating distributed energy resources into wholesale-market participation and operations.
Why it matters: DER participation connects aggregators, distributors, the IESO, and distribution-connected facilities.
4 linked sources
The coordinated representation of multiple distributed resources for wholesale-market participation.
Why it matters: Aggregation can make smaller resources market-relevant while creating coordination and visibility needs.
3 linked sources
Participation by eligible resources in IESO-administered wholesale markets.
Why it matters: DER and storage models must translate physical capability into market registration, offers, dispatch, and settlement.
4 linked sources
Operational and information coordination between the IESO, distributors, aggregators, and distribution-connected resources.
Why it matters: Wholesale instructions must remain compatible with distribution-system reliability and constraints.
4 linked sources
The exchange of registration, operational, availability, constraint, and performance information among relevant parties.
Why it matters: DER participation requires the IESO and distributors to have timely, reliable information at the right level of detail.
3 linked sources
The ability for relevant parties to see information flowing in both directions about resource status, constraints, and instructions.
Why it matters: Coordinated DER operation depends on visibility into both wholesale needs and distribution conditions.
4 linked sources
The operating coordination needed where wholesale-market actions and distribution-system conditions interact.
Why it matters: DER dispatch and aggregation can affect both transmission-level objectives and local distribution reliability.