Energy demand management Pennsylvania

Demand response events are called during grid stress, and participating facilities reduce load according to an agreed plan, with performance measured against a baseline and settled later.

For Pennsylvania facilities in PJM pathways, the operational reality is lead time and readiness. Rodan’s PJM sell sheet lists ELRP program timing as June 1 to May 31, with 30 to 120 minutes lead time. That means a facility cannot rely on a last-minute email chain and hope. It needs a written plan, named owners, and a short list of safe actions that can be executed on any shift.

A procurement-ready preparation cycle includes:

• Eligibility and fit screening: confirm the site can reduce load within required windows without violating constraints.

• Curtailment plan development: define actions, owners, sequencing, and stop points tied to safety, quality, and uptime.

• Communication paths: confirm who receives event notifications, who makes the go or no-go call, and who confirms execution.

• Measurement discipline: confirm interval data access, and how performance will be reviewed post-event.

• Settlement follow-through: confirm who tracks payments, credits, and exceptions.

Rodan supports the lifecycle with service and tools. FacilityIQ™ overlays activation windows onto performance, which helps teams see what happened during the event window without reconstructing later. SettlementIQ™ simulates the bill daily and flags discrepancies early, which protects revenue as participation grows. PeakIQ™ provides verified alerts via email, SMS, and automated phone call, with a chosen response window based on what operations can execute.

Set limits by defining protected load, approved actions, and explicit stop points in writing, with sign-off from operations, maintenance, and EHS.

Curtailment fails when the plan is vague. “Reduce load if you can” turns into inconsistent behavior and internal conflict. Procurement needs a plan that can be defended. Operations needs a plan that protects safety and uptime. A good plan is specific and short.

Key steps:

• Protected load inventory: list loads that cannot be touched due to safety, product quality, environmental limits, or contractual uptime commitments.

• Approved action tiers: build a small set of “always allowed” actions, then a second tier that requires explicit approval.

• Stop points: define the exact conditions that stop participation, including safety signals, process instability, quality risk, staffing gaps, or equipment alarms.

• Owner by step: each action needs a role owner, and the event window needs one accountable decision-maker.

• Practice: run a tabletop drill, then a controlled live test during a low-risk window.

PeakIQ™ supports this by giving operations lead time to execute approved steps, rather than improvising. PeakIQ™ delivers multi-channel alerts, verified by Rodan’s 24/7 ROC, and supports 2-hour, 4-hour, or 6-hour response windows chosen by the customer. FacilityIQ™ supports follow-through by showing site performance during activation windows and surfacing underperformance early. SettlementIQ™ supports finance by validating the billing side daily, so the internal story matches the invoice story.

It reduces risk by lowering demand during the specific intervals that drive peak-sensitive charges or pass-through exposure, then validating outcomes with interval data and billing review.

Pennsylvania procurement teams often focus on supply price, then discover a second layer of exposure tied to demand, peak contribution methods, and pass-through terms. Demand management targets that layer by reducing demand when it matters most. The goal is not to reduce load every day. The goal is to reduce load during the high-impact windows that move the annual cost outcome.

A practical approach procurement can defend includes:

• Billing and contract review: identify which line items scale with demand and peak timing, and how costs are allocated.

• Peak window mapping: use interval data to pinpoint when your sites typically peak, and why.

• Action design: prioritize reversible actions that operators can execute across shifts.

• Performance verification: confirm what happened during the window at each site.

• Financial validation: confirm whether cost drivers changed as expected, and flag anomalies early.

Rodan’s IQ stack supports the operational and financial sides. PeakIQ™ monitors grid conditions and sends alerts a week ahead, a day ahead, and day-of, with in-day adjustments, via email, SMS, and automated phone call, verified by Rodan’s 24/7 ROC. FacilityIQ™ overlays demand response activation windows onto performance data, so portfolio managers can see underperformance early. SettlementIQ™ simulates the bill daily using interval data and flags discrepancies before they become disputes, which reduces month-end churn.

FacilityIQ™ aggregates consumption data across sites and overlays demand response activation windows onto facility performance data, showing real-time performance and surfacing underperformance early.

Portfolio programs fail when leaders cannot see what is happening until after settlement. FacilityIQ™ is built to eliminate that delay. It provides a single view across facilities, then maps activation windows onto consumption so teams see what happened at each site during each window. It also supports early problem detection, with alerts via email, SMS, and phone, before underperformance becomes a dispute.

In Pennsylvania, this matters because portfolios often include:

• Sites with different staffing coverage

• Sites with different operating rhythms

• Sites with different curtailment options

• Sites with different tolerance for interruption

FacilityIQ™ supports a consistent operating model:

• Pre-event: confirm readiness, contact paths, and expected actions by site.

• During the window: monitor performance, identify gaps, and coordinate corrective steps within stop-point limits.

• After the window: produce a clear record tied to the activation window, then feed learnings back into the playbook.

FacilityIQ™ is included with Rodan DR enrollment, which helps reduce internal lift for portfolio operators. It pairs naturally with SettlementIQ™, which handles the fin

PeakIQ™ monitors grid conditions and sends peak-risk alerts through email, SMS, and automated phone call, with every alert verified by Rodan’s 24/7 ROC, and a response window selected by the customer.

Operations teams do not need market jargon. They need a credible trigger, enough lead time, and a clear checklist. PeakIQ™ is designed to provide that trigger across week-ahead, day-ahead, and day-of horizons, with in-day adjustments. The response window is a key operating decision. Rodan notes that customers select 2-hour, 4-hour, or 6-hour response windows based on what operations can execute.

A clean on-site routine includes:

• Recipient design: primary and backup contacts for each shift, plus a single accountable decision-maker.

• Alert-to-action mapping: each alert level triggers a specific set of approved actions.

• Action logging: record which actions were taken, when, and by whom.

• Post-window review: confirm what happened in interval data and what it meant financially.

PeakIQ™ is strongest when paired with performance and validation tools. FacilityIQ™ overlays activation windows onto site performance, which keeps the focus on what happened during the window, not weekly averages. SettlementIQ™ simulates the bill daily and flags discrepancies early, helping finance confirm that actions affected the intended drivers.

You need a recent utility bill and interval meter data, plus basic operating constraints, to size opportunity and build a safe action plan.

The fastest way to waste time is to start with assumptions. Procurement should start with the bill because it shows how costs are calculated, what charges are demand-related, and which accounts are in scope. Interval data is the second input because it shows when peaks occur, how long they last, and what drives them.

A practical data package includes:

• Recent utility bills and supplier invoices: at least one full billing period, more if available.

• Interval data access: 15-minute, 30-minute, or hourly interval data, depending on what the utility provides.

• Site operating profile: operating hours, shift patterns, batch schedules, maintenance windows, and constraints.

• Major load list: chillers, compressors, pumps, process lines, material handling, and other large drivers.

• Contacts and escalation paths: who receives alerts, who authorizes actions, and who validates outcomes.

PeakIQ™’s “how to get started” guidance is to share a recent utility bill so Rodan can assess peak exposure by market and facility profile. FacilityIQ™ requires interval data to aggregate consumption across sites and map activation windows to performance. SettlementIQ™ uses interval meter data to simulate the bill daily and show cost drivers before month-end.

If interval data access is slow, the procurement path still works: start with bills and site constraints, then add interval feeds as the operating motion is built.

A good first 30 days focuses on scope, site limits, and measurement, not big promises.

Pennsylvania procurement leaders usually want three things early: clear scope, clear operating limits, and clear reporting. The rollout should start with a bill-based review and a data intake that identifies which accounts are peak-sensitive and which sites offer safe flexibility. PeakIQ™’s starting point is sharing a recent utility bill so Rodan can assess peak exposure by market and facility profile.

A typical first-month sequence:

• Week 1: collect bills, interval data access details, and site constraints, then confirm program fit paths at a high level.

• Week 2: draft site action plans with owners, sequencing, and stop points, then confirm alert recipients and escalation paths.

• Week 3: configure PeakIQ™ alerting, and set a response window aligned to operations capability.

• Week 4: set up performance visibility and finance validation, then run a tabletop drill and a controlled test.

FacilityIQ™ supports the performance side by aggregating site data and overlaying activation windows onto performance, which keeps execution visible. SettlementIQ™ supports finance by simulating bills daily and flagging discrepancies early, reducing month-end churn.

SettlementIQ™ simulates the utility bill every day using interval meter data, shows cost drivers before month-end, and catches discrepancies before they become disputes.

Demand management and demand response create value, then value can leak through billing confusion. Finance teams often see the leak in three ways: unexpected demand drivers, unclear credits, and time-consuming reconciliation. SettlementIQ™ is designed to replace manual reconciliation with a repeatable, auditable process.

What finance gets:

• Daily shadow invoice: cost drivers visible before month-end close, reducing late surprises.

• Discrepancy detection: automated exception flags that catch billing errors and metering gaps early.

• Revenue protection: as DR and market participation revenue grows, settlement accuracy becomes a control requirement, not a nice-to-have.

What procurement gains from that:

• A cleaner internal story that ties actions to dollars

• Fewer disputes that slow adoption across sites

• Faster root-cause work when bills shift unexpectedly

SettlementIQ™ also supports governance for multi-site programs. When one site’s bill behaves differently, finance can flag it quickly, and the energy team can investigate with FacilityIQ™’s event-window performance view. PeakIQ™ strengthens the front end with verified alerting and a chosen response window that aligns to operations capability.

Energy demand management Pennsylvania teams use is the practice of controlling load during the hours that carry the most financial weight, then proving results with metered data and clear reporting.

Energy demand management is not an equipment project by default. It is an operating discipline that targets timing, peak demand, and controllable load. Procurement leaders care because a small number of intervals can influence costs and create budget variance. Operations leaders care because any load change has to fit safety, quality, comfort, and uptime commitments. Finance leaders care because the outcome has to show up in bills, settlements, and internal reporting.

A procurement-ready program usually includes:

• A scope screen: which meters, sites, and contracts have peak-sensitive drivers.

• A site action plan: a short list of approved actions, each with an owner, expected impact, and a clear stop point.

• A trigger and cadence: who gets notified, when actions occur, and how often results are reviewed.

• A proof loop: performance visibility during the window, then validation against billing and settlement outcomes.

Rodan supports that proof loop with PeakIQ™, FacilityIQ™, and SettlementIQ™. PeakIQ™ delivers peak-risk alerts through email, SMS, and automated phone call, and alerts are verified by Rodan’s 24/7 ROC. FacilityIQ™ aggregates site data and overlays activation windows onto performance, which helps portfolio teams see results without manual rebuilds. SettlementIQ™ simulates the utility bill daily using interval data and flags discrepancies early, which supports finance and close.

The difficulty is not the concept, it is the execution: different sites, different operators, different constraints, and inconsistent follow-through during the hours that matter.

Multi-site Pennsylvania organizations often manage a mix of plants, campuses, warehouses, and office loads. Each site has different operating schedules, different staffing coverage, and different tolerance for interruption. Without a standard operating motion, demand management becomes informal, and results vary by site. Procurement sees that as unreliable savings. Finance sees it as hard-to-explain variance. Operations sees it as unclear expectations.

A multi-site program needs:

• One definition of success: what counts as participation, what counts as non-participation, and what is considered a stop condition.

• One playbook format: consistent action lists, owners, and stop points, even when actions differ by site.

• One performance view: the same time windows, the same measurement lens, and a clear record of what happened.

• One finance process: validation steps that do not depend on manual spreadsheets or individual heroics.

FacilityIQ™ is built for this problem. It aggregates consumption data across sites and overlays demand response activation windows onto facility performance data, so teams see results in real time and underperformance surfaces early. SettlementIQ™ supports the finance side by simulating the utility bill every day using interval meter data, showing cost drivers before month-end, and catching discrepancies before they become disputes. PeakIQ™ supports execution by providing verified alerts with a response window aligned to what operations can execute.