Demand response programs get framed as a straightforward revenue opportunity for EV fleet operators: your fleet has interruptible load, utilities will pay for that flexibility, therefore you should participate. The logic is sound in broad outline. The practical execution involves enough operational constraints and program-specific requirements that fleet operators who enter demand response programs without understanding the details often find the experience either less lucrative or more operationally disruptive than expected.
This article gives an honest account of what demand response participation looks like for commercial EV fleets — the value case, the operational tensions, and the program structures that tend to work best for fleets with tight morning dispatch requirements.
What Demand Response Programs Actually Pay For
Utility demand response programs compensate commercial customers for curtailing or shifting electrical load during periods when the grid is under stress — high-demand events, transmission constraints, or situations where wholesale market prices spike sharply. The programs vary by utility and by mechanism, but commercial fleet charging programs typically fall into two categories:
Interruptible Load Programs
In an interruptible load program, the enrolled customer commits to reduce load by a specified amount (a curtailment commitment, measured in kW) when the utility dispatches an event. The customer receives a capacity payment for enrolling — compensation for having the load available to be curtailed — and may also receive an event payment per kWh of actual load reduction delivered during events.
The key operational parameter is the curtailment notification lead time. Programs with 24-hour advance notice are operationally comfortable for fleet operators — the charging schedule can be adjusted with full knowledge of the event window before vehicles return to depot. Programs with same-day or 2-hour notice are more challenging: vehicles may have already begun charging based on that evening's optimized schedule, and the system must interrupt active sessions and re-queue vehicles to deliver the curtailment while still meeting morning dispatch requirements.
Automated Demand Response (AutoDR)
AutoDR programs, deployed by several California utilities and piloted by some Pacific Northwest utilities through OpenADR 2.0 protocol, use machine-to-machine event signaling. Rather than relying on manual operator response to a curtailment notification, the building or charging management system receives an OpenADR event signal directly and triggers an automated response.
OpenADR 2.0 defines a standard XML and REST-based signaling protocol for utility-to-customer demand response communication. For fleet charging systems that implement an OpenADR VEN (Virtual End Node) client, curtailment event handling can be automated: when an OpenADR event signal arrives indicating a curtailment period, the scheduling system reduces active charging loads automatically within the response window, without requiring dispatcher action.
PGE has participation in demand response programs with automated signaling capability for commercial customers. The specific program structure and automation requirements evolve through PUC proceedings. For fleet operators interested in AutoDR participation, PGE's key accounts team and the Oregon PUC docket system are the relevant sources for current program terms.
The Fleet Dispatch Conflict
The core tension in demand response for commercial EV fleets is between the grid's need for curtailment and the fleet's need for operational readiness. A curtailment event that reduces charging load from 8 PM to 11 PM on a Tuesday means vehicles that would have been charging during that window are now behind on their overnight charge plan. If the off-peak window is 10 PM to 6 AM, and the curtailment runs from 8 PM to 11 PM, the lost charging time represents a meaningful portion of the available overnight window.
Whether this creates an operational problem depends on how much energy headroom the fleet has. A fleet where most vehicles return with moderate SOC (40–60%) and have 8 hours of available charging time to reach 90% target SOC on L2 chargers has significant headroom — a 2-3 hour curtailment can be absorbed by compressing the charging into the post-event window. A fleet where vehicles routinely return with low SOC (15–25%) due to long routes, or a fleet with tight dwell times that leaves little margin in the overnight window, is much more vulnerable to curtailment conflicts.
The scheduling implication is that demand response participation should be evaluated on a vehicle-by-vehicle basis, not just at the fleet aggregate level. A fleet of 30 vehicles might have 20 that consistently have adequate SOC margin to tolerate curtailment events without dispatch risk, and 10 that are routinely marginal. A demand response control strategy that excludes the marginal vehicles from curtailment scope — allowing them to continue charging during events — while curtailing the others can often deliver the committed curtailment while protecting operational readiness for the vulnerable vehicles.
This requires that the charging management system be capable of applying selective curtailment: reducing power on specific connectors while leaving others at full charge rate, based on per-vehicle feasibility horizon calculations. Systems that can only implement fleet-wide power limits — treating all vehicles identically during a curtailment event — are less suited to demand response participation for operationally constrained fleets.
Demand Response vs. Demand Charge Management
Fleet charging managers sometimes conflate demand response participation with demand charge management. They address different things and should be evaluated separately.
Demand charge management (the subject of our earlier article on demand charges) is about controlling your own facility's peak demand to reduce your monthly utility bill. It is entirely within the fleet operator's control and produces savings on every billing cycle.
Demand response participation is about volunteering to curtail load when the utility asks, in exchange for program payments. It produces revenue or bill credits when events occur, but events may be infrequent — in some programs, only a handful of events per year — and the payments are contingent on actually delivering the committed curtailment. Non-performance during a called event can result in program penalties under some program structures.
Both are worthwhile, but demand charge management has a clearer and more predictable ROI. Demand response participation stacks on top of demand charge management and should be evaluated separately rather than as a substitute.
Calculating Whether Participation Is Worth It
The economics of demand response participation for a commercial EV fleet depend on three factors: the program's capacity payment, the expected number of events per year, and the operational cost of executing curtailment.
Capacity payments in commercial DR programs typically range from low single-digit to mid-double-digit dollars per enrolled kW per year, depending on program structure, region, and market conditions. The value of that payment against the enrolled curtailable load needs to be weighed against the operational complexity of participating — the staff time to manage enrollment, the software integration required for automated response (if applicable), and the risk cost of dispatch impacts if curtailment events interact poorly with fleet operations.
We're not saying demand response isn't worth pursuing — for fleets with adequate SOC margin, stable overnight dwell windows, and charging management software capable of selective curtailment, the participation economics are often positive. What we're saying is that the "easy revenue from your flexible load" framing glosses over operational details that determine whether the experience is actually smooth or disruptive. Working through those details before enrollment rather than after is how fleet operators end up with demand response programs that function as intended.
Program Enrollment Process
For Oregon fleet operators interested in PGE's demand response programs, the starting point is PGE's business rates team. Program enrollment typically involves: confirming eligibility under the applicable program tariff, establishing a measurement and verification (M&V) baseline period (against which curtailment is measured), configuring notification or signaling protocols, and in some cases installing interval metering equipment if the existing meter doesn't provide sufficient granularity.
The M&V baseline methodology is worth understanding before enrolling. Your curtailment is measured against a baseline — typically an average of recent non-event days under similar conditions. If your fleet's baseline charging profile is already optimized (shifted heavily to off-peak windows, with low on-peak load), your potential curtailment during on-peak events may be limited, because you're not running much load to curtail during on-peak hours anyway. This is the somewhat counterintuitive situation where aggressive TOU optimization actually reduces demand response opportunity during on-peak windows — a feature, not a problem, from a cost management perspective, but worth understanding when calculating DR program value.
Pacific Power also operates demand response programs for commercial customers in its Oregon and Washington service territories. Program terms differ from PGE's and should be evaluated separately for depots in Pacific Power territory.