Demand response programs Ontario

They often can be part of a strategy, depending on your site configuration and the program pathway you are pursuing. The key is governance: what assets are permitted, how they are dispatched, and how performance is measured and documented.

Where onsite assets can help

• Batteries: can reduce grid import during an event, support smoother execution, and reduce manual intervention.

• Onsite generation: can contribute to load reduction plans when it is permitted, maintained, and operated within your site rules.

• Microgrids: can support resilience goals while also supporting planned load management actions.

What must be clarified up front

• Program eligibility rules for specific asset types

• Metering boundaries and how reductions are measured

• Controls, safety requirements, and operating approvals

• How the strategy interacts with your resilience plan

Rodan’s role
Rodan supports DER optimization, including value stacking across programs and tariffs, plus demand response strategy and operations support. Rodan also provides metering and telemetry services that underpin reliable participation.

A readiness review is the cleanest way to determine whether onsite assets make the plan more reliable, or whether they introduce complexity that is not worth it for your site.

Payments are generally tied to the capability you commit and the performance you deliver when events occur. Programs also typically include performance requirements, and underperformance can reduce earnings or create charges, depending on the program rules.

Typical payment structure

• Capacity-style earnings: compensation for being available to reduce load, based on your committed capability.

• Event performance settlement: confirmation of delivered reduction using an accepted baseline approach.

• Timing and administrative cycle: payments often arrive on a schedule tied to program settlement timelines.

Typical performance expectations

• Deliver the committed reduction within the required timeframe

• Maintain performance for the event duration

• Provide data that supports verification and settlement

Risk controls that matter

• Commit what you can deliver repeatedly. Overcommitting is the fastest way to create headaches.

• Use layered options. A mix of smaller actions is often more reliable than a single big lever.

• Build “no-go” rules. Document when you will not respond, tied to safety, quality, or mission-critical constraints.

• Validate telemetry early. Poor data can create disputes and delays.

What Rodan does
Rodan’s role includes measurement and verification support and operational execution support, designed to reduce surprises during events and settlement. For exact rates, timelines, and penalty mechanics, the right approach is to confirm current IESO program documentation during enrollment.

Performance risk is managed through conservative commitments, clear operating guardrails, and a playbook that has been tested before the grid calls a real event. That approach protects operations and reduces the chance of unpleasant surprises during settlement.

Risk controls that work in practice

• Right-sized commitments: the capability should match what you can deliver consistently, not what you can deliver once.

• Layered response options: a blend of smaller actions is often more stable than a single point of failure.

• Defined “no-go” boundaries: documented conditions where the site will not respond, tied to safety and operational integrity.

• Season-specific planning: hot and cold weather can change what is feasible, so the playbook should reflect real seasonal constraints.

• Testing and drills: validate communications, roles, and steps before peak conditions.

What Rodan brings
Rodan supports event strategy and operational execution, with measurement and verification that documents performance. Rodan also supports metering and telemetry work where needed, which reduces data disputes.

What you should expect internally
Operations leadership should sign off on what actions are permitted. Procurement and finance should understand how commitments translate to earnings and what performance obligations come with participation. That alignment keeps the program steady over time.

Demand response can support peak cost management by giving your organization a structured way to reduce load during the hours that tend to drive peak-related charges. For many large sites, a small number of peak intervals can have an outsized impact on annual cost outcomes.

Why this matters to procurement
Energy procurement decisions are not only about commodity price. They also involve cost volatility tied to peak conditions, capacity-related charges, and operational exposure during system stress.

How demand response can support peak cost strategy

• Adds a disciplined operating plan for peak hours

• Creates a repeatable process for aligning operations and finance

• Supports better internal forecasting and budgeting

• Provides a path to monetize flexibility while you manage exposure

What varies by customer
Global Adjustment impacts and peak-related drivers depend on customer class, tariff structure, and site load profile. That is why generic promises are not helpful.

What Rodan does
Rodan’s demand response and peak management services include assessment, operating support, and measurement and verification. Rodan also provides energy intelligence tools that support forecasting and facility-level visibility, which helps teams manage peak risk with fewer surprises. For exact cost mechanics, the right approach is to validate your current rate structure and IESO program details during the readiness review.

Enrollment timelines vary by program, site complexity, and metering readiness. What stays consistent is the workstream: assess fit, confirm technical requirements, complete enrollment steps, and validate the operating plan before the first real event.

What Rodan typically handles

• Facility assessment and fit review

• Enrollment support, including coordination and documentation

• Event strategy and playbook design with your operations team

• Performance reporting and verification support

What your team typically owns

• Approving operational boundaries, safety rules, and “no-go” conditions

• Assigning internal roles for event approval and execution

• Providing access to interval data, metering information, and site contacts

• Aligning procurement, finance, and operations on the decision

Practical timeline drivers

• Metering and telemetry readiness

• Complexity of operating constraints and approvals

• Number of sites, vendors, and internal stakeholders

If your site is already metered and you have a clear operating plan, enrollment is more straightforward. If metering or controls work is needed, the right move is to start with a readiness review so you can set an internal timeline that makes sense.

Demand response programs in Ontario pay large electricity users for the ability to reduce load when the IESO needs system support. Your facility commits to a defined capability, then follows an agreed operating plan during called events.

How it usually works

• You define a reliable reduction. The goal is a realistic amount you can deliver without compromising safety or production.

• You enroll through a provider. Enrollment typically involves eligibility review, documentation, and technical checks.

• You perform during events. When the grid calls an event, you follow a pre-approved sequence to reduce load for a set period.

• You get measured and reported. Performance is compared to a baseline method, and results are documented for settlement.

What makes Ontario different
Ontario participation often ties back to capacity procurement and peak conditions. That means the value is strongly linked to preparation, governance, and repeatable performance during hot and cold weather peaks.

Where Rodan fits
Rodan supports assessment, enrollment, event strategy, operations support, and measurement and verification. Results vary by site, operating limits, and current IESO rules, so a short readiness review is the cleanest starting point.

You typically need interval data that can verify load reductions, plus a communication path that supports timely event response and performance reporting. The exact setup varies by program pathway and facility configuration.

Common technical requirements

• Interval metering: data that reflects site load at a resolution suitable for program verification.

• Telemetry or data transfer: a secure method to share data for monitoring and settlement.

• Event communications: a reliable way to receive event notifications and confirm response.

• Controls integration (optional): some sites automate part of the response through building controls or SCADA.

Why this matters
Demand response becomes hard to defend when the data trail is weak. Good metering and telemetry reduce the risk of disputes, speed up reporting, and make it easier to run events with confidence.

How Rodan supports
Rodan provides metering, telemetry, SCADA integration, and engineering services that support accurate data and reliable participation in grid programs. That can include identifying gaps, recommending practical upgrades, and supporting integration work so your facility can participate without relying on manual workarounds.

What your team should prepare

• Identify who owns metering data access and permissions

• Confirm where interval data is stored and how it can be shared

• Confirm any cybersecurity, IT, or vendor requirements for connectivity

• Confirm who can approve changes to controls or operating sequences

A readiness review is usually the fastest way to identify what is already in place and what needs to change.

A procurement leader should focus on operational fit, performance governance, data credibility, and transparency in reporting. Demand response is an operational commitment, so the provider must work well with plant leadership, facilities teams, and finance.

Key questions that separate strong providers

• What does participation look like at my site? Ask for a site-specific operating concept, not generic claims.

• How do you set commitments? Look for conservative sizing, clear assumptions, and documented guardrails.

• What data and reporting will I receive? Expect baseline approach, event results, and settlement-ready documentation.

• What support is available during events? Confirm who is on point, how escalation works, and how communications are handled.

• What is your approach to metering and telemetry gaps? Weak data can undermine outcomes.

• How do you protect operations? Demand response should have defined “no-go” rules and clear safety boundaries.

Rodan’s fit in Ontario
Rodan is Ontario’s largest demand response provider, with more than 300 MW under management and the largest virtual capacity position in the IESO capacity auction. Rodan supports assessment, enrollment, event strategy, operations support, and measurement and verification, with metering and telemetry services available to close technical gaps.

Eligibility depends on your facility’s load profile, metering, and ability to deliver a consistent reduction when called. In practice, the best candidates are large sites with controllable equipment, clear operating guardrails, and reliable interval data.

Good fit characteristics

• Meaningful, steady load with identifiable drivers (HVAC, compressed air, pumping, process loads, refrigeration, or batch operations)

• Operational flexibility in one- to four-hour windows

• Clear “can do” and “will not do” limits approved by operations leadership

• Strong data quality from revenue-grade metering or equivalent telemetry

Load strategies that commonly work

• Shifting noncritical processes to off-peak hours

• Staging equipment start-ups to avoid stacking demand

• Temporarily reducing discretionary loads (fans, pumps, compressors) within defined boundaries

• Using onsite assets where available, including storage or generation, if permitted and appropriate

What tends to struggle
Sites with highly variable load, tight process constraints without flexibility, or limited metering and controls often need a readiness phase before they can participate confidently.

Rodan’s role
Rodan’s demand response work includes assessment, enrollment, event strategy, operational support, and measurement and verification. The goal is a plan your team can execute the same way every time, with performance reporting that stands up to review.

In most cases, it does not have to. Well-run demand response focuses on planned, low-risk actions that protect safety, product quality, and uptime, rather than improvising in the moment.

What a low-disruption program looks like

• A short playbook, approved in advance. Operators are not asked to invent actions during an event.

• Only noncritical load is used. Production-critical systems remain protected by clear boundaries.

• Roles are assigned. One person approves the response, one executes, and one confirms completion and documentation.

• Testing happens before peak season. Communications and control steps are validated during normal conditions.

How different sites tend to approach events

• Manufacturing: use maintenance windows, batch timing, compressed air optimization, and staged equipment control.

• Campuses: adjust HVAC setpoints, rotate equipment schedules, and manage large building loads with facilities oversight.

• Data centers: focus on noncritical mechanical strategies and carefully governed changes, given uptime priorities.

What Rodan manages
Rodan supports event strategy, operations support, and measurement and verification, with a focus on minimizing operational disruption while supporting performance. Participation still requires internal alignment, especially on what actions are permitted, who approves them, and what conditions trigger a “no-go.”