Demand side management North Carolina

PeakIQ™ turns peak risk into lead time by sending verified alerts through multiple channels, with a response window chosen to match operations capability.

PeakIQ™ monitors grid conditions and delivers peak risk alerts a week ahead, a day ahead, and day-of, with in-day adjustments. When a peak window is near, alerts go out via email, SMS, and automated phone call, and every alert is verified by Rodan’s 24/7 real-time operations center. The operations team does not need to interpret market signals. They need a clear trigger and a clear window to act.

The response window matters. Rodan notes that customers choose a 2-hour, 4-hour, or 6-hour response window based on what operations can execute. A longer window gives more time for staffing coordination and process sequencing. A shorter window can fit sites with simpler, faster actions. Procurement should treat that as an operating design decision, not a marketing choice.

PeakIQ™ does not replace a playbook. It activates it. A North Carolina DSM plan should define: which actions are triggered by an alert, who owns each action, and what stops the action. FacilityIQ™ can support the confirmation step by showing what happened during the window across sites, and SettlementIQ™ can support finance by validating whether billing drivers moved as expected.

For procurement, PeakIQ™ supports budget stability because it reduces missed windows and creates a consistent record of when the organization acted.

Demand response is a revenue pathway that can sit inside a broader DSM plan when a site is eligible and can deliver verified load reduction within operational limits.

Demand side management is the umbrella. It focuses on peak-driven cost exposure and operational control during high-impact windows. Demand response adds payments for verified reductions during event windows under program rules. In PJM, Rodan positions the Emergency Load Response Program as one example of a demand response path, with a program year and lead-time requirements that can be material for operations planning.

Procurement should evaluate demand response with the same discipline used for any operational program tied to revenue: what is the commitment, what are the allowed actions, and what is the measurement method. A site plan should include protected loads, a short action list, timing requirements, and stop points that protect safety, comfort, product quality, and uptime. It should also include clear authority. Who approves a curtailment action under time pressure, and who confirms performance?

Rodan supports the execution side with tools and services that reduce internal lift. FacilityIQ™ overlays demand response activation windows onto real-time performance, which helps multi-site teams spot underperformance before settlement. SettlementIQ™ supports finance by simulating bills daily with interval data, flagging discrepancies before they become disputes, and protecting revenue as DR participation grows.

A North Carolina DSM page should present demand response as a controlled option with clear guardrails, not as a blanket promise.

FacilityIQ™ reduces underperformance risk by making site performance visible during activation windows across the portfolio.

FacilityIQ™ aggregates consumption data across sites and overlays demand response activation windows onto facility performance data. That means the energy team does not need to reconstruct what happened from a post-event report. They can see performance at each site in real time, and underperformance surfaces early, not at settlement.

That matters in North Carolina because “partial PJM” portfolios can create uneven execution. A site in scope may have a new supervisor, a different shift routine, or a changed process schedule that reduces flexibility. FacilityIQ™ helps locate that issue quickly. It also supports governance by providing a consistent reporting view across sites and markets. Rodan also notes that FacilityIQ™ includes alerts via email, SMS, and phone when problems emerge.

Procurement leaders care about underperformance because it creates settlement disputes, delays revenue, and erodes internal support for the program. FacilityIQ™ helps keep the program stable by supporting three routines: pre-event readiness checks, in-window confirmation, and post-window review tied to settlement outcomes. SettlementIQ™ then supports finance by simulating the bill daily and flagging discrepancies early, which reduces the chance that a billing issue is discovered long after the event window.

FacilityIQ™ is also positioned as included with Rodan DR enrollment, which makes it a practical part of a demand response rollout when a site is eligible.

Demand side management North Carolina is an operating plan that reduces peak-driven cost exposure and supports grid program participation for sites that have PJM exposure based on utility territory and account structure.

North Carolina is not a single market story. Large portfolios can have sites under different utilities, different supply terms, and different pass-through components. That is why demand side management begins with a territory screen and a bill review. Procurement needs a clear view of which accounts carry PJM-driven components, which accounts do not, and which sites have the operational flexibility to act during peak windows.

A procurement-ready DSM plan has three parts. First, a trigger that tells operations when a peak-risk window is approaching. Second, a written site action list that names owners, timing, and stop points. Third, a measurement and reconciliation loop that finance can use for reporting. Rodan supports that loop with PeakIQ™ alerts, FacilityIQ™ performance visibility across sites, and SettlementIQ™ billing validation. PeakIQ™ sends multi-channel alerts, including email, SMS, and automated phone call, and every alert is verified by Rodan’s 24/7 ROC. FacilityIQ™ overlays demand response activation windows onto performance data across sites, which reduces the “post-event rebuild” burden. SettlementIQ™ simulates the bill daily using interval data, flags discrepancies, and supports repeatable reconciliation for finance.

The output procurement should expect is simple: which sites have PJM exposure, what actions are allowed, and how results will be verified.

SettlementIQ™ gives finance early visibility into billing drivers and flags discrepancies before month-end close, which supports repeatable reconciliation.

SettlementIQ™ simulates the utility bill every day using interval meter data. Finance sees cost drivers before month-end, instead of discovering surprises at close. When discrepancies appear, the system flags them early, which reduces disputes and speeds resolution. Rodan also positions settlement accuracy as a revenue protection issue when demand response participation grows.

North Carolina portfolios often have repeated friction points for finance: different bill formats across accounts, pass-through components tied to peaks, and program revenue that must be reconciled against performance. SettlementIQ™ supports a repeatable process. It also supports audit readiness, because daily shadow invoicing creates a consistent record of expected versus actual drivers.

Procurement benefits from this because program value becomes easier to defend internally. Operations benefits because finance questions can be answered with data tied to the same event windows that FacilityIQ™ tracks. PeakIQ™ supports the front end by creating a consistent trigger record for when the organization acted.

In a “partial PJM” state, the finance story can get messy fast. SettlementIQ™ helps keep it clean by standardizing validation across sites.

The best DSM actions are repeatable, reversible, and tied to clear stop points set by site leadership.

DSM actions vary by facility type, staffing model, and controls maturity. The common thread is operational discipline. A site should not rely on complex actions that require a long approval chain during a peak window. A better approach is to build a tiered action list, starting with low-risk steps that can be executed across shifts, then adding steps that require deeper coordination.

Common action categories include load scheduling changes for discretionary processes, staged HVAC adjustments within approved ranges, control changes on supporting systems like pumps, fans, and compressed air, and sequencing changes that avoid simultaneous large equipment starts. The details should come from the site team, because protected load differs by process, tenant requirements, comfort constraints, and uptime commitments.

PeakIQ™ supports DSM by providing advance warning of peak risk windows and delivering alerts via email, SMS, and automated phone call, with verification by Rodan’s 24/7 NOC. FacilityIQ™ supports execution by showing performance at each site during activation windows, reducing the need for manual post-event reconstruction. SettlementIQ™ supports finance by validating billing drivers daily and flagging discrepancies early, which helps confirm whether the targeted actions moved the cost drivers that matter.

A DSM plan does not need heroic actions. It needs actions that operators can repeat and management can approve.

A procurement-ready DSM plan has clear scope, clear operating limits, and clear reporting that finance can reconcile.

A DSM plan fails internally when it creates uncertainty. Procurement signs off on a program, operations feels exposed to disruption, and finance cannot see the result in the billing data. Procurement-ready DSM avoids that by documenting three items early.

• Scope: which accounts and sites have PJM exposure and are in the program.

• Operating limits: protected loads, allowable actions, and stop points.

• Reporting: how performance and billing outcomes will be tracked and reviewed.

Rodan’s IQ products are built for that loop. PeakIQ™ monitors grid conditions and sends peak risk alerts a week ahead, a day ahead, and day-of, with in-day adjustments, and alerts go out via email, SMS, and automated phone call. FacilityIQ™ aggregates consumption data across sites and overlays demand response activation windows onto performance data, which creates a shared view for energy teams and operations. SettlementIQ™ simulates the utility bill daily using interval data and flags discrepancies early, which supports a repeatable close process for finance.

Procurement should also stage the rollout. Start with one or two sites with clear exposure and clear flexibility. Prove execution and reporting. Expand after the playbook is stable across shifts and staffing changes. That pacing reduces risk, builds internal confidence, and keeps the DSM program funded through the next budget cycle.

Treat the portfolio as a governance problem first, then standardize the playbook and reporting, and adjust the action list by site.

Multi-utility portfolios create three procurement risks. Scope risk, because the sites do not share the same cost drivers. Performance risk, because one site’s operational habits can differ from another’s. Reporting risk, because finance may receive bills with different formats and drivers across accounts. A portfolio operator needs one operating rhythm that works across sites, then a site-specific action list that reflects each facility’s limits.

FacilityIQ™ is designed for multi-site visibility across markets. It aggregates consumption data, maps demand response activation windows onto performance data, and highlights underperformance early, not at settlement. That supports portfolio governance because the energy team and operations team can see the same picture during an event window. SettlementIQ™ supports finance governance by simulating the bill daily with interval data and flagging discrepancies early, which reduces month-end surprises and reconciliation backlog. PeakIQ™ supports operational governance by providing the same alert cadence across sites, with a selected response window that matches how the operations team works.

Procurement can then stage the rollout. Start with the sites with the clearest PJM exposure and the best operational flexibility. Expand after the program has stable execution and reporting. That path keeps the portfolio aligned and reduces time spent debating results after the fact.

The assessment should confirm PJM exposure by account, quantify peak exposure by site, and produce a short site playbook plus a reporting plan.

A useful assessment starts with basic inputs: a recent utility bill, interval data access or a path to obtain it, and a short summary of operating limits. Rodan’s PeakIQ™ intake begins with sharing a recent utility bill, and Rodan assesses peak exposure by market and facility profile. That aligns with what procurement needs in North Carolina, since the first decision is scope.

The assessment should then move to site feasibility. What loads are protected, what loads can move for short windows, who owns approvals, and what stop points apply. That produces a site action list that operations can follow across shifts. The assessment should also include a reporting plan, because procurement decisions live and die on finance reconciliation and leadership reporting cadence.

Rodan’s IQ tools map to that loop. PeakIQ™ provides verified alerts with a chosen response window. FacilityIQ™ supports multi-site visibility and overlays demand response activation windows onto performance data. SettlementIQ™ supports daily bill simulation, discrepancy detection, and revenue protection tied to settlement accuracy.

The deliverable set should be short and usable: a PJM exposure map by account, a prioritized site list, a draft playbook per site, and a simple plan for PeakIQ™, FacilityIQ™, and SettlementIQ™ deployment. That is what a procurement leader can take into a budget review without hand-waving.

“Partial” means PJM exposure is not uniform across the state, so procurement should screen eligibility and cost exposure by account before building a DSM or demand response plan.

For large energy users, the risk is rolling out a one-size plan and discovering later that some sites were never in scope for PJM-related participation or cost drivers. That can waste internal time and erode confidence with finance and operations. A cleaner approach is to treat “partial” as a procurement control step: map sites, confirm exposure, and prioritize where the financial drivers and operational flexibility line up.

A practical screening process uses two inputs: recent utility bills and interval data access. Bills show how charges appear and how pass-throughs are applied. Interval data shows when the site peaks, how often, and which operations drive the highest intervals. Once the sites are mapped, DSM becomes an operations program, not a spreadsheet idea.

Rodan’s tools support that sequencing. PeakIQ™ starts with a bill review and then delivers peak risk alerts tied to a response window your operations team can execute. FacilityIQ™ supports multi-site rollouts because it aggregates consumption data and maps demand response activation windows onto performance in real time. SettlementIQ™ supports finance by simulating bills daily and flagging discrepancies early, which helps prevent month-end surprises from derailing the program.

Procurement does not need to guess where PJM matters in North Carolina. It can be verified account by account, then managed site by site.