PJM
Demand Response &
Capacity Programs

FacilityIQ is built for multi-site visibility and event performance tracking. It aggregates consumption data across sites and overlays demand response activation windows onto facility performance data. Instead of reconstructing performance from post-event reports, teams see site performance in real time. Underperformance shows up early, not at settlement. FacilityIQ also supports alerts by email, SMS, and phone tied to those performance issues.

That matters in Delaware because multi-site organizations often struggle with consistency. One site executes the playbook perfectly. Another site is short-staffed, has a different shift pattern, or faces a production constraint that was not documented. FacilityIQ gives portfolio operators a single view across facilities and markets, and it provides a factual record tied to event windows.

From a procurement viewpoint, FacilityIQ supports internal reporting. Leadership and finance want a simple answer to three questions: did we participate, did we deliver, and what was the financial result. FacilityIQ supports the delivery side of that story by showing what happened at each site during each event window. Then SettlementIQ can support the financial side by validating billing and settlement.

FacilityIQ is included with Rodan DR enrollment per the product guide, which makes it a practical add for Delaware organizations that already have DR participation, or that plan to add it across multiple sites.

PeakIQ is designed to warn teams about peak risk windows with enough time to take safe operational steps. 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 through email, SMS, and automated phone calls. Rodan’s 24/7 network operations center verifies each alert. PeakIQ also lets you choose a response window of 2, 4, or 6 hours based on what your team can execute.

For a Delaware procurement leader, PeakIQ supports two outcomes. It reduces peak-driven cost exposure by helping operations act before the hour that matters. It also supports governance, because it gives a consistent trigger for internal action. Instead of reacting to a bill after month-end, teams act when the alert arrives, then track the result.

PeakIQ is not the same as demand response. Demand response pays you to reduce load during called events, under program rules. PeakIQ helps you manage peak risk that can drive cost volatility, even when there is no event call. Some facilities use PeakIQ as the operational backbone that also supports demand response readiness. The same curtailment actions that work during peak risk windows often work during event windows, provided they are documented and tested.

A Delaware page should frame PeakIQ as a decision tool that supports budgeting, operational planning, and lower peak exposure, then connect it to a clear next step, which is a bill-based review.

Revenue depends on your committed load reduction, your ability to deliver it consistently, and the program path you enroll in. Rodan’s PJM sell sheet cites an earning potential range of $98,000 to $170,000 per MW-year, tied to Demand Response participation, and it lists a program timing window of June 1 to May 31, plus an event lead time of 30 to 120 minutes.

That range is useful for orientation, not for budgeting your site without a sizing step. Two facilities with the same peak demand can have very different curtailment capability. A continuous process load, a data center, and a cold storage site will have different options, and different risk boundaries. The right way to estimate revenue is to start with interval meter data, identify realistic curtailment actions, then size a conservative commitment that operations can deliver on busy days, not only on perfect days.

Rodan’s Demand Response lifecycle model supports this approach. Eligibility assessment starts with load profile review against program rules. Enrollment and administration covers registration and compliance. Curtailment plan development builds site-specific response plans around operational constraints. Event operations and settlement covers dispatch coordination, performance tracking, and settlement reconciliation. For procurement, this matters because revenue only counts if it is delivered and reconciled. The goal is a commitment you can keep, plus reporting your finance team can trust.

PJM market operations Delaware refers to the PJM market activities that shape reliability actions, event calls, and the charges and credits that flow through to large energy users in Delaware. Procurement teams feel this through contract language, pass-through components, and budget volatility that can concentrate in a small number of high-load hours. A facility can run smoothly all year and still see cost spikes tied to peak conditions and PJM system stress.

A procurement-ready approach starts with three questions. What portion of your cost is peak-sensitive, what actions can operations take without jeopardizing safety and production, and how will the organization document outcomes for finance and leadership. Rodan supports that end-to-end motion by running demand response program lifecycle work, then pairing it with monitoring and settlement validation. Demand Response covers eligibility assessment, enrollment, curtailment plan development, event dispatch, and settlement follow-through. FacilityIQ adds site-level visibility that maps event windows onto performance data, which helps multi-site operators avoid surprises at settlement. SettlementIQ adds daily validation, so billing gaps do not sit undiscovered until month-end close.

Program rules vary, so the page should not overpromise. The page should tell a Delaware buyer what gets managed, what the facility is responsible for during events, and what reporting they can expect internally.

A Delaware readiness brief is a working session designed to confirm program fit, operational boundaries, and the steps needed to participate with low disruption. The most useful input is a recent utility bill and, when available, interval data. Rodan’s product guide states that sharing a utility bill starts the process for both Demand Response and PeakIQ, with a load analysis as the first step.

During the session, Rodan reviews your load profile against program rules to confirm participation value, then identifies candidate curtailment actions with your operations team. Demand Response lifecycle coverage includes eligibility assessment, enrollment and administration, curtailment plan development, event operations, and settlement reconciliation. The output should be clear and usable internally: a conservative estimate of curtailment capability, a draft site playbook with roles and stop points, and a short list of data or integration gaps that might affect participation.

If you operate multiple sites, FacilityIQ is part of the discussion because it provides portfolio performance visibility and maps activation windows to consumption data, which helps avoid surprises at settlement. If finance needs earlier cost visibility or has recurring disputes, SettlementIQ fits as a follow-on because it provides daily shadow invoices and discrepancy detection.

The brief ends with practical next steps, a simple timeline, and a clear decision path.

PJM’s Emergency Load Response Program, commonly called ELRP, is designed for grid reliability during system stress. Facilities that participate reduce load during called events, then get paid based on performance and program terms. Rodan’s PJM sell sheet positions ELRP as a way to earn revenue, reduce energy spend, and support grid reliability.

For a Delaware facility, ELRP participation should be treated as an operating program, not a one-time registration. Value shows up when enrollment is completed correctly, communications and roles are tested, and curtailment steps are written down with stop points. Rodan’s Demand Response service is built around that lifecycle. Rodan runs eligibility assessment, enrollment, curtailment plan development, event dispatch coordination, and settlement reconciliation. That division of labor matters for large energy users because the internal workload can be heavier than expected. Compliance steps, event execution, and settlement follow-through each require time, and missed steps can reduce payouts or create internal distrust.

ELRP details can vary, so Delaware leaders should start with fit and readiness rather than debating a generic program description. A short review of your interval data, operating hours, and controllable loads can identify whether ELRP participation is likely to be operationally safe, and financially worthwhile. That is what the readiness brief is designed to do.

Event lead time varies by program. Rodan’s PJM sell sheet cites a lead time of 30 to 120 minutes. That is short enough that Delaware sites need a pre-approved checklist, clear roles, and reliable communications.

Preparation has three parts. First, define curtailment actions that are safe and repeatable, and write them as steps that can be executed quickly. Second, define authority and escalation. Who approves event participation, who executes steps, and who confirms performance on the meter. Third, test the process. A program that exists only in a spreadsheet will fail under real conditions.

Rodan’s approach pairs program operations with visibility tools. Demand Response covers the core lifecycle and event dispatch coordination. FacilityIQ provides real-time visibility with activation windows mapped onto consumption data, and it can alert teams when a site is underperforming. That matters in a short notice environment because corrective actions need to happen during the window, not after the fact.

Delaware procurement leaders should also decide on boundaries in advance. Some loads are never candidates. Some loads are candidates only under specific production schedules. Those limits protect safety and customer commitments, and they keep demand response as a reliable revenue line rather than a recurring internal dispute.

Loads that work best are loads that can be reduced or shifted for a limited window without affecting safety, product quality, uptime commitments, or environmental limits. The right answer is different by facility type, and it needs input from operations, maintenance, and energy management.

A practical method is to build a tiered list. Tier one is low-risk actions that are often available, and easy to execute. Tier two is moderate actions that require coordination across teams or changes in operating sequence. Tier three is advanced actions that may require controls integration, deeper engineering review, or policy approvals. This approach keeps initial participation conservative, then expands after performance is proven.

Rodan’s Demand Response service is designed to support that operational reality. Curtailment plan development is a managed step, and it is built around your operational constraints and dispatch windows. FacilityIQ supports multi-site operators by mapping event activation windows to consumption and surfacing underperformance early. That combination matters because many underperformance issues come from operational drift across shifts, sites, or staffing changes.

Procurement leaders should focus on repeatability. A plan that depends on one person, one shift, or one perfect production schedule will not last. A plan that is documented, tested, and monitored can become part of normal operations, and can support both cost control and program revenue.