It’s 4 p.m. on the hottest day of the year. The demand flexibility team is getting ready for its own event. Thousands of smart thermostats, batteries and EV chargers are enrolled and waiting. The event will go out system-wide at 5 p.m., because that’s when the program calendar says it should.
Meanwhile, in the control room, an operator watches a feeder on the east side of the service territory creep toward its limit. The options on the screen are familiar: switch load, call on utility-owned assets, or hope the temperature breaks.
Will demand flexibility programs like demand response, EV charging, BYOD programs, or virtual power plants (VPPs) work? Both teams are working hard to protect the same grid on the same afternoon. Often, neither knows that a few hundred of those enrolled devices sit on the exact feeder the operator is worried about. That gap isn’t a technology problem anymore. It’s a conversation that hasn’t happened yet.
In This Article
- For Grid Operators
- For Program Managers
- What Each Team Needs From the Other
- Start the Conversation With These Questions
- Make the First Move
- FAQ
- Glossary of Terms
- Conclusion: Your Control Room & Your Demand Flexibility Program Teams Want the Same Thing.
For Grid Operators
You have a network model, SCADA, and a clear view of every feeder and its constraints. What you don’t have is a reliable way to use the devices your customers own.
Those devices are already on your feeders. They show up as load, not as a resource. When you need relief on one circuit, a system-wide demand flexibility event is too blunt: it costs program goodwill everywhere to help one place. And if you can’t verify how much load actually dropped, you can’t plan around it.
What you need is simple to say and hard to get on your own: dispatchable, verified capacity, placed on the feeder where you need it, that never gets in the way of a reliability call.
For Program Managers
You’ve done the hard part. You’ve engaged with and enrolled customers, integrated thermostats, batteries and EV chargers from multiple manufacturers, and built programs people stay in. You run events, measure the results and settle incentives.
But your program is often judged on peak reduction alone, and it’s usually dispatched on a calendar rather than on what the grid needs that hour. Every event asks something of your customers. When the event doesn’t relieve a real constraint, that’s a cost with less to show for it.
What you need is a bigger job for the capacity you’ve already built: a role in grid reliability that justifies the program budget, while customers only get called when it counts.
What Each Team Needs From the Other
Each team holds something the other one is missing. Put side by side, the trade is clear.
| Grid Operations Needs | Customer Programs Needs | |
|---|---|---|
| Visibility | Device capacity by feeder, not just a system total | Feeder topology, so events land where they help |
| Dispatch | A firm MW block for a set window. Topline Demand Control delivers a flat, predictable block instead of a spike and a rebound | Dispatch requests with a MW target, a time window and a feeder |
| Trust | Telemetry that verifies the response, device by device | |
| Value | Fewer devices called for the same relief | Reliability value to justify program budgets and grow enrollment |
| Effort | No new screens or manual reconciliation in the control room | No spreadsheets or phone calls to find out what operations needs |
Topline Demand Control matters most to operators because it changes what they can plan around. Instead of a demand flexibility event that drops sharply and then rebounds, they get a flat block of load reduction held across the window they asked for, shaped like any other resource they dispatch.
Start the Conversation With These Questions
You don’t need to know the full scope of your demand flexibility goals to begin. You need one meeting and a few good questions. Need some tips to get started? Bring these to your counterpart.
If you’re in grid operations, ask the programs team:
- How many devices are enrolled today, and what types?
- Can you tell me which feeders those devices sit on?
- How quickly can you call an event, and how do you confirm it worked?
- Can you hold a steady MW reduction for a set window, or does load rebound?
If you’re in customer programs, ask the control room:
- Which feeders give you the most trouble on peak days?
- How much relief would make a difference on those feeders, and for how long?
- What would you need to see to trust a DR event as a grid resource?
- How would you want to send us a request, and how fast?
Then answer one together:
- If our programs start supporting reliability, who owns the outcome and the budget?
Make the First Move
The next peak day is already on the calendar. The devices are enrolled, and the control room knows where the constraints are. The only thing missing is the two teams in the same room.
Forward this post to your counterpart. Whichever side of the hall you’re on, send it to the person on the other side with one line: “Can we talk about this before summer?”
Then bring both teams to us. Virtual Peaker will host a 30-minute working session with your grid operations and customer programs teams. We’ll map your enrolled devices to the feeders that matter, show how dispatch requests and telemetry flow between the systems, and leave you with a plan both teams agree on.
FAQs
Can demand flexibility really be treated as a grid resource? Yes, but it has to be dispatched for a set window, and the response has to be verified with device-level telemetry. When those are in place, operators can plan around demand flexibility the same way they plan around other dispatchable resources.
Won’t targeting specific feeders mean fewer events for most customers? Usually that’s the point. Feeder-targeted events call only the devices that relieve a real constraint. That means fewer devices called for the same relief, and less fatigue across the wider customer base.
What happens if a program event conflicts with a reliability need? Both teams should agree on a simple rule ahead of time: grid needs come first. Program events are scheduled around reliability calls, never the other way around.
What’s the difference between a typical DR event and Topline Demand Control? A typical demand flexibility event often drops load sharply and then rebounds as devices recover. Topline Demand Control holds a flat, predictable reduction across the full window requested, so operators get a block of capacity they can count on.
Does the control room need new tools to make this work? It shouldn’t. The goal is for dispatch requests and telemetry to flow between existing systems (like distributed energy resource management systems [DERMS]), without new screens or manual reconciliation for operators.
Who should own the budget once programs support reliability? There’s no single right answer, and that’s why it belongs on the agenda for the first joint meeting. What matters is that both teams agree on ownership before the first peak-day dispatch.
Glossary of Terms
- Demand response (DR): Programs that pay or reward customers for reducing or shifting electricity use during periods of high demand or grid stress.
- Demand snapback: The spike in load that can follow a DR event as devices return to normal operation, such as thermostats cooling homes back down.
- Feeder: A distribution circuit that carries power from a substation to a group of customers. Feeders have capacity limits that can be stressed on peak days.
- Feeder topology: The map of which customers and devices are connected to which feeders.
- Network model: The utility’s digital representation of its grid, including feeders, equipment and their connections.
- Peak reduction: The amount of demand a program removes during the highest-load hours, often used as a program’s main performance metric.
- Reliability call: An action the control room takes to keep the grid stable and within its operating limits.
- Supervisory Control and Data Acquisition( SCADA): The system grid operators use to monitor and control equipment across the network in real time.
- Telemetry: Data reported back from devices that shows what they actually did, used to verify how much load dropped.
- Topline Demand Control: Virtual Peaker’s approach to delivering a flat, sustained block of load reduction across a dispatch window, rather than a sharp drop followed by a rebound.
Conclusion: Your Control Room & Your Demand Flexibility Program Teams Want the Same Thing
Go back to that 4 p.m. scene. The operator is watching the east-side feeder climb. The programs team is preparing a system-wide event for 5 p.m. A few hundred enrolled devices sit on exactly the circuit that needs relief. Every piece of the solution is already in place except the connection between the two teams.
That connection is what turns a demand flexibility program from a calendar exercise into a grid resource. Operators get verified, feeder-level capacity they can plan around. Program managers get a reliability role that justifies their budget, and customers get called only when it counts. Neither team has to give anything up. Each just needs what the other already has.
The work doesn’t start with a new platform or a long project. It starts with one conversation, a few honest questions, and an agreement on who owns the outcome. Summer peak days will arrive whether or not that conversation has happened.