Demand side management Washington DC: Turn peaks into budget control

Demand response payments depend on verified performance against program rules, and settlement often arrives after the operating period. Finance teams care because timing, accuracy, and documentation determine whether the revenue is trusted, forecastable, and easy to reconcile at close. If reporting is late or disputed, the value of the program can get discounted internally, even if operations did the work.

For large organizations in Washington, D.C., the common friction points are:

• Missing or inconsistent interval data

• Disagreement about baseline or event window interpretation

• Difficulty tying operational actions to measured results

• Billing errors or settlement discrepancies that take months to resolve

• Lack of a repeatable audit trail for internal controls

SettlementIQ™ is built to reduce that friction by simulating the utility bill every day using interval meter data, surfacing cost drivers before month-end, and catching discrepancies before they become disputes. That matters more as DR revenue grows, because settlement accuracy protects the revenue stream and reduces time spent on reconciliation.

From a governance standpoint, pairing SettlementIQ™ with FacilityIQ™ can also help. FacilityIQ™ maps activation windows onto consumption data, so finance and operations can align on what happened, site by site, before settlement is final. That alignment is often the difference between “DR is interesting” and “DR is a finance-approved program.”

PJM demand response programs generally pay participating facilities to reduce electricity use when the grid needs relief. Your facility commits to a level of curtailment capability, then performs during dispatched events, with payments tied to program rules and verified performance.

For D.C. energy decision-makers, the key is aligning program participation with operational reality. Office portfolios, universities, hospitals, and public-sector buildings often have flexibility, but it must be structured so it does not create mission risk. A strong demand response plan starts with what you can curtail safely for 1 to 4 hours, who will execute it, and how you will verify results.

A typical participation path looks like this:

• Eligibility review: interval data, load shape, and operational constraints

• Enrollment and program setup: registrations, reporting requirements, and site mapping

• Curtailment plan: step-by-step actions with clear “do” and “do not” boundaries

• Dispatch execution: perform during events with an accountable escalation path

• Settlement follow-through: validate results and track payments

Rodan’s Demand Response service is designed to remove the administrative workload while keeping your team in control of operational decisions. Rodan manages eligibility, enrollment, curtailment plan development, event dispatch coordination, performance tracking, and settlement reconciliation, while your team executes the agreed site actions.

PeakIQ™ helps by giving your team actionable notice when peak risk is rising, so you can execute a planned reduction window instead of reacting after the cost is already locked in. It is designed for facilities where a missed peak can create material charges and budget volatility.

PeakIQ™ monitors grid conditions and delivers peak risk alerts week-ahead, day-ahead, and day-of, with in-day updates. Alerts go out by email, SMS, and automated phone call, and they are human-verified by Rodan’s 24/7 ROC. You also choose a response window, which matters for D.C. sites that need time to coordinate building operations, tenant communications, or staffing coverage.

Where PeakIQ™ fits in a D.C. demand side management plan:

• Procurement: supports budgeting by reducing peak-driven volatility

• Operations: creates a repeatable “peak day” runbook with clear triggers

• Leadership: adds a defensible narrative for why actions were taken

• Portfolio teams: standardizes response across multiple properties

PeakIQ™ is not a replacement for good controls or a curtailment plan. It is the early warning and coordination layer that helps teams execute consistently, which is often where peak strategies succeed or fail.

Enrollment timelines vary by program, utility, and site readiness, but the onboarding work typically follows a consistent sequence: data access, eligibility review, curtailment planning, communications setup, and reporting configuration. The goal is to remove surprises by locking down operational boundaries and measurement requirements before the first high-risk season.

A practical onboarding sequence for D.C. facilities:

• Share interval data and a recent bill: confirm load shape and exposure

• Confirm eligible sites: align on which meters and buildings participate

• Build the curtailment plan: step-by-step actions, boundaries, and approvers

• Set communications: who receives alerts, who executes, who confirms

• Set reporting: performance visibility during events and settlement documentation

Rodan’s Demand Response service is structured to manage the full program lifecycle, including eligibility assessment, enrollment, curtailment plan development, event dispatch, and settlement follow-through. If your organization also needs stronger internal reporting, FacilityIQ™ and SettlementIQ™ can be layered in so you have real-time performance visibility and finance-grade validation, not just a post-season summary.

In PJM, event lead time depends on the specific program and signal, and it can be relatively short. Rodan’s PJM materials cite lead times in the 30 to 120 minute range for certain demand response participation paths.

From an operations and procurement standpoint, lead time is not the only issue. The bigger issue is whether your site can execute the same actions consistently with the people on shift, the equipment available, and the right approvals. For many D.C. facilities, the most reliable actions are the ones that are simple, reversible, and documented.

What strong sites do to make short lead times workable:

• Pre-approve actions: setpoints, staging rules, and noncritical loads with guardrails

• Assign roles: who gets the call, who approves, who executes, and who confirms

• Build a short checklist: 5 to 10 actions that can be executed in minutes

• Practice once: a tabletop drill with facilities, security, and operations

• Validate data: interval meters are mapped correctly for measurement

PeakIQ™ can support readiness by delivering peak risk alerts and escalation via email, SMS, and automated phone call, with human verification by Rodan’s 24/7 ROC.That structure helps teams treat peak windows like planned operating periods, not surprises.

You manage it by standardizing what “good” looks like, and by using portfolio-level visibility so underperformance is caught early, not discovered at settlement. Multi-site organizations often have the same problem: a few sites perform well, a few sites struggle, and leadership gets an inconsistent picture that makes the program harder to defend.

A workable portfolio operating model has three parts:

• Standard playbooks: a common set of curtailment actions and boundaries, adapted per site

• Clear roles: one owner for program operations, plus site-level executors

• A single reporting view: performance across all facilities, with a way to spot issues fast

FacilityIQ™ is designed for that portfolio problem. It aggregates consumption data across sites and overlays demand response activation windows onto facility performance, so teams can see event performance at every site in real time and surface underperformance before settlement. That is what reduces admin burden: you are not chasing spreadsheets, and you are not waiting for a post-event report to learn that a site missed the target.

For finance teams, SettlementIQ™ adds a second layer by validating billing and settlement using daily shadow invoicing from interval data, which reduces reconciliation drag when you manage many meters and multiple sites.

Demand side management in Washington, D.C., is the umbrella term for reducing, shifting, or shaping electricity use to lower costs and support grid reliability. Demand response is one demand side management approach where you get paid to reduce load during specific PJM or utility event windows.

For procurement and finance leaders in D.C., the practical difference is how value shows up and how performance is measured. Demand side management can target everyday cost drivers like peak demand charges, while demand response adds a structured revenue opportunity tied to event performance. Many organizations do both at once: they treat peak days like planned operational windows, and they enroll the right facilities in demand response programs when the operational risk is acceptable.

What this usually includes for large D.C. portfolios:

• Peak planning: operating procedures for the few hours that set a large share of annual charges

• Load shaping: pre-cooling, setpoint adjustments, staging equipment, and deferring noncritical loads

• Demand response participation: committed curtailment capability during PJM event calls

• Measurement and validation: interval meter data, event baselines, and settlement documentation

Rodan’s approach is built for teams that need repeatable execution and clean reporting. Rodan manages demand response participation end to end, and supports decision-making with PeakIQ™ for alerts, FacilityIQ™ for event performance visibility, and SettlementIQ™ for billing and settlement validation.

For many Washington, D.C., office buildings, the best demand side management opportunities are HVAC-driven, because cooling and ventilation are often the largest controllable loads during peak conditions. The goal is to identify actions that reduce demand for a short window without creating comfort complaints, indoor air quality issues, or equipment risk.

Common categories of workable load levers in commercial buildings:

• HVAC optimization: staged chillers, chilled water resets, fan speed adjustments, and controlled temperature setpoint changes within approved ranges

• Pre-conditioning: pre-cooling earlier in the day so the peak window requires less compressor work

• Scheduling: shifting cleaning equipment, pumps, and other time-flexible loads outside peak periods

• Lighting: selective reductions in noncritical areas where safety requirements are still met

• Controls tuning: lockouts that prevent avoidable simultaneous heating and cooling

For procurement leaders, the key question is repeatability. A demand side management plan should not depend on one “hero” operator. It should be a documented playbook with clear boundaries, equipment prerequisites, and a simple confirmation step.

Rodan supports this by pairing program operations with visibility and verification. FacilityIQ™ overlays activation windows on facility performance so your team sees what happened during events at each site, in real time, and can spot underperformance early. That feedback loop is often what turns a one-time curtailment into a dependable operating practice.

At a minimum, you need reliable interval usage data that can be tied to the facility, the program, and the event window. Interval data is what enables performance measurement, baseline calculations, and settlement validation. If data is incomplete or mismapped, you can end up arguing about results after the fact, which is exactly what procurement and finance teams want to avoid.

For most large D.C. facilities, the checklist looks like this:

• Interval meter data access: utility interval data, meter IDs, and consistent timestamping

• Site mapping: which meter corresponds to which building or load pocket

• Event window alignment: the ability to tag the exact dispatch window for reporting

• Data quality checks: missing intervals, obvious spikes, and meter changes documented

• Reporting cadence: who reviews performance during the season and at settlement

FacilityIQ™ is designed to aggregate consumption data across sites and overlay demand response activation windows on facility performance, so teams can see event performance in real time rather than reconstructing it later. For finance teams, SettlementIQ™ can add another layer by simulating billing daily using interval data and flagging discrepancies early, before they become month-end surprises or disputes. That pairing is often what makes demand side management “procurement-ready” because results are measurable, explainable, and auditable.

It does not have to. The safest demand side management programs are designed around operational boundaries first, and they prioritize actions that are reversible and approved in advance by stakeholders who own comfort, safety, and mission requirements.

In D.C., that governance layer matters. Many facilities have high-visibility occupancy, critical services, or security requirements. Procurement and facilities leaders typically need a plan that can be executed without improvisation, and with a clear record of what was done and why.

How teams reduce disruption risk:

• Set boundaries upfront: temperatures, ventilation minimums, and restricted equipment

• Separate critical from flexible loads: identify what never changes during an event

• Use staged actions: start with low-impact steps, then add deeper steps only if needed

• Create an escalation path: who can stop curtailment if comfort or safety thresholds are approached

• Document post-event results: capture performance, exceptions, and lessons for next time

Rodan’s Demand Response service is built around site-specific curtailment plans and consistent event operations, so performance is repeatable and aligned to constraints, not shift-by-shift improvisation. If your organization wants tighter internal alignment, FacilityIQ™ and SettlementIQ™ can support performance visibility and finance-grade documentation, so operational decisions and billing outcomes stay connected.