Demand side management Virginia

Demand response events are called when the grid needs relief, and participating sites reduce load based on a pre-approved plan, with performance measured against program rules and settled later.

PJM demand response is not “turn things off and hope.” It is a planned response. Rodan’s Demand Response offer describes the full lifecycle work that supports consistent delivery: eligibility assessment, enrollment, curtailment plan development, event dispatch, and settlement. Rodan’s PJM sell sheet lists ELRP timing as June 1 to May 31, lead time of 30 to 120 minutes, and an earning potential range of $98,000 to $170,000 per MW-year. Sites should treat those numbers as directional and size-specific, not guaranteed.

Operational readiness typically includes:

• A protected load list approved by operations and EHS.

• A short action list that can be executed on any shift.

• A single decision owner during the window, plus backups.

• A measurement plan that confirms performance during the window and in settlement follow-through.

Rodan reduces internal workload by managing the program steps and coordinating dispatch. FacilityIQ™ helps multi-site operators see performance at each site during activation windows, and flag underperformance early. SettlementIQ™ supports finance by adding invoice verification and reconciliation before disputes arise, which helps keep program value from getting tied up in month-end questions.

PJM participation matters because it can affect peak-sensitive costs, and it creates the option to earn demand response revenue when a site can deliver verified reduction.

Procurement teams often carry contract terms, pass-through components, and budgeting expectations that depend on load shape. PJM-related drivers can amplify the impact of a few hours. A demand side management plan gives procurement a way to pair supply decisions with operational control. It does not replace supply strategy. It gives supply strategy a lever during high-impact windows.

Procurement should verify four items:

• Account scope: which Virginia accounts are settled inside PJM, or priced with PJM components.

• Cost drivers: which line items are sensitive to demand, peak timing, or capacity-related allocation.

• Operational limits: what the site will never curtail, and what conditions stop curtailment.

• Reporting cadence: what finance needs to reconcile savings, revenue, and exceptions.

Rodan supports demand response participation by managing the program lifecycle, then supporting performance tracking tied to settlement outcomes. PeakIQ™ helps teams act before peak windows with verified alerts and a chosen response window. SettlementIQ™ helps keep the procurement story clean by supporting invoice verification and reconciliation before disputes arise.

Mission-critical sites should treat DSM as a reliability-first program with conservative actions, written stop points, and strict authority controls.

Uptime and safety come first. DSM should never ask a mission-critical site to trade reliability for savings. The right approach starts with boundaries defined by the site team. That includes protected load, environmental limits, redundancy policies, and any operational conditions that block curtailment. The action list should be short and reversible, and it should avoid actions that create restart risk or cascading impacts.

Procurement should require:

• A written “do not curtail” list.

• Stop points in plain language, tied to alarms, quality limits, and staffing coverage.

• A decision owner for every event window, plus an escalation path.

• A measurement plan that finance can review, tied to meter data.

Rodan’s Demand Response offer emphasizes curtailment plans built around operational constraints, with Rodan managing enrollment, event operations, and settlement follow-through. PeakIQ™ adds lead time so the site can act in a controlled way, using a chosen response window that matches operational reality. FacilityIQ™ supports multi-site operators by showing performance during activation windows, which helps detect gaps early. SettlementIQ™ supports invoice verification and reconciliation, which helps keep the internal narrative aligned between operations actions and finance outcomes.

A good 30-day start plan sets scope, captures site limits, and sets up measurement and reporting before the first high-impact window.

A practical month-one plan focuses on control and readiness. It does not try to roll out every action at every site at once.

A typical sequence:

1. Data intake: utility bills, interval data access path, site operating schedules, and major load list.

2. Scope and sizing: identify which sites drive peak exposure, and where demand response participation is realistic.

3. Playbook draft: write the site action list with owners, timing, recovery steps, and stop points.

4. Notification setup: configure PeakIQ™ recipients, escalation paths, and the site’s selected response window.

5. Performance view: set up FacilityIQ™ for multi-site visibility, tied to activation windows.

6. Finance validation: align finance reporting needs and add SettlementIQ™ when invoice verification and reconciliation is a priority.

Demand Response can enter the plan once site fit is confirmed and the action list is stable across shifts. Rodan’s Demand Response offer states Rodan manages eligibility assessment, enrollment, curtailment plan development, event dispatch, and settlement, reducing the internal DR administrative burden.

FacilityIQ™ adds real-time portfolio visibility by mapping demand response activation windows onto site performance, which helps catch underperformance early.

Multi-site portfolios struggle with consistency. One site executes the playbook. Another site has a staffing change, a different schedule, or a controls issue, and performance drifts. FacilityIQ™ is designed to reduce that drift. It aggregates consumption data across sites and overlays demand response activation windows onto facility performance data, giving real-time visibility and early problem detection. Alerts can be delivered by email, SMS, and phone.

Procurement and finance benefits include:

• A single view of performance across sites, without manual reporting rebuilds.

• A clear record of performance during activation windows, tied to settlement outcomes.

• Faster identification of which sites need playbook updates or operational coaching.

Operations benefits include:

• Evidence of what happened during the window, which supports practical troubleshooting.

• Visibility that helps supervisors validate actions and recovery steps.

FacilityIQ™ is listed as included with Rodan DR enrollment. That pairing matters because Rodan manages the program workload, and the portfolio team gets a consistent performance view. SettlementIQ™ then supports invoice verification and reconciliation before disputes arise, which helps keep performance and dollars aligned.

SettlementIQ™ supports invoice verification and reconciliation before disputes arise, helping finance validate results with less manual effort.

Finance teams often see the effect of peaks and program participation at month-end, when the time cost of fixing issues is highest. SettlementIQ™ is positioned to support settlement validation, with invoice verification and reconciliation before disputes arise. It can be added to any Rodan service package, with onboarding configured to billing structure and program terms, and delivery within 30 days of contract.

A finance-ready DSM program needs:

• A consistent method for attributing savings and revenue to actions taken during defined windows.

• A way to flag billing anomalies early, when the underlying cause is still traceable.

• A reconciliation habit that does not depend on spreadsheet heroics.

SettlementIQ™ supports that finance posture. It also supports procurement, because a DSM or DR program loses internal support when the financial story is hard to reconcile. FacilityIQ™ helps by mapping activation windows to site performance, which provides the operational record finance needs when questions arise. Demand Response adds settlement follow-through as part of the managed lifecycle, reducing administrative burden on the customer team.

A coincident peak is a high-impact peak hour used in cost allocation methods in some markets and rate structures, and PeakIQ™ helps sites avoid missing those hours by giving actionable alerts.

Many facilities have a “few hours” problem. Missing the wrong hour can create a material charge. PeakIQ™ is designed to give operations lead time. PeakIQ™ monitors grid conditions and delivers peak risk alerts a week ahead, a day ahead, and day-of, with in-day adjustments. Alerts go out by email, SMS, and automated phone call, and every alert is human-verified by Rodan’s 24/7 ROC. PeakIQ also supports a 2-hour, 4-hour, or 6-hour response window selected by the customer.

A Virginia operating routine using PeakIQ™ typically includes:

• A recipient list by site, including nights, weekends, and a backup contact.

• A short action checklist tied to each alert level.

• A log that records which actions were taken, and when.

• A post-window review tied to interval data and billing outcomes.

PeakIQ™ works better with measurement and billing validation. FacilityIQ™ overlays activation windows onto site performance, which helps confirm that actions moved load when it mattered. SettlementIQ™ supports invoice verification and reconciliation before disputes arise, which helps finance validate that the peak response delivered the expected billing impact.

Demand side management Virginia programs use is an operating plan that changes when your facility uses power during the hours that drive the largest costs, then validates the result with meter data and billing review.

Large facilities rarely miss budgets because of average usage. Budget pressure comes from short windows when demand spikes, prices rise, or program events are called. Demand side management focuses on those windows. Procurement wants a plan that is defensible at renewal time. Operations wants a plan that protects safety, quality, and uptime. Finance wants numbers that reconcile in close.

A workable program has three parts:

• Scope: which sites and meters carry peak-sensitive drivers, and which do not.

• Actions: a short list of approved load moves, each with an owner, a time requirement, and a stop point.

• Proof: a consistent way to confirm what happened during the window, then validate the billing outcome.

Rodan’s Demand Response offering is built around managing the program workload, including eligibility assessment, enrollment, curtailment plan development, event dispatch, and settlement follow-through. PeakIQ™ supports peak window awareness with alerts delivered via email, SMS, and automated phone call, with human verification by Rodan’s 24/7 ROC. FacilityIQ™ supports multi-site performance visibility by mapping activation windows onto actual performance. SettlementIQ™ supports invoice verification and reconciliation before disputes arise.

The best candidates are loads that can be adjusted for short windows without affecting life safety, occupant requirements, or critical processes.

Buildings and campuses often have flexibility in supporting systems. The exact action list depends on equipment, controls, and tenant requirements. A conservative approach starts with actions that have clear guardrails and minimal downstream impact.

Common categories include:

• HVAC staging and setpoint adjustments within approved bands.

• Chiller, boiler, and air-handler sequencing changes with comfort limits.

• Scheduling changes for noncritical equipment and discretionary processes.

• Staggering large motor starts to reduce peak demand spikes.

A practical playbook should include:

• Owner, timing, and expected effect for each action.

• A stop point tied to comfort, safety, or equipment limits.

• A recovery step so operations know how to return to normal.

PeakIQ™ can trigger the routine by providing verified peak risk alerts through multiple channels, with a response window chosen to match operations capability. FacilityIQ™ supports performance visibility across buildings and meters, with activation windows overlaid onto actual performance data. SettlementIQ™ supports finance by helping validate invoices and reconcile outcomes before disputes arise. Demand Response can be added where the site can deliver verified reduction during program events without crossing operational limits.

Bring a recent utility bill and basic operating limits, and expect a clear scope map, a site action plan outline, and a reporting plan tied to meter data and billing review.

A Virginia assessment should be quick to start and specific enough to support internal decisions.

Inputs that help:

• A recent utility bill and supplier invoice package for each site in scope.

• Interval data access, or the process to obtain it from your utility, supplier, or meter provider.

• Site operating schedule, shift coverage, and known protected loads.

• A contact list: energy manager, facility lead, operations approver, and finance owner.

Outputs procurement should expect:

• A scope map showing which sites carry the largest peak exposure.

• A draft curtailment plan outline per site, with owners, timing, and stop points.

• A recommended product mix across Demand Response, PeakIQ, FacilityIQ, and SettlementIQ, based on how the portfolio operates.

• A rollout plan that starts with high-fit sites, then expands after the playbook is proven across shifts.

Rodan’s PJM sell sheet also provides a reference point for demand response timing, lead time, and a stated earning potential range for ELRP, which can be used as a directional input for business case conversations, with site-specific sizing done in the assessment.