Ohio runs one of the broadest industrial bases in PJM, from Cleveland-Cliffs steel mills to Honda assembly to GE Aviation jet engines to Intel’s emerging Columbus semiconductor cluster. All operate under the same five-hour PLC mechanic that drives capacity charges for the year ahead. Peak load management is the most direct way to reduce that exposure across diverse operations.
Ohio carries one of PJM’s deepest industrial concentrations and one of its fastest-growing data center markets. Steel mills run continuous casting. Auto assembly runs takt-driven shift cycles. Chemical and aerospace operations run continuous hot processes. Semiconductor fabs are coming online. Data center clusters are scaling fast. All face the same PLC mechanics. Rodan operates demand response and peak management across that complexity with operating logic built around what Ohio industries actually require.
We model the actual load profile of an Ohio facility, whether it is a Cleveland-Cliffs integrated steel mill, a Honda or Ford assembly plant, a GE Aviation jet engine production line, a Procter & Gamble manufacturing operation, or a hyperscale data center. The dispatch logic respects what each operation requires.
PJM capacity charges are driven by Peak Load Contribution, set on the five highest PJM RTO-wide peak hours of the prior delivery year. The 2027/2028 Base Residual Auction cleared materially above prior years. For Ohio operators across AEP, FirstEnergy, Duke, and DP&L territories, those five hours represent the single biggest opportunity to reduce capacity exposure.
Demand response, peak forecasting, and facility performance run through a single team in a single Real-time Operations Center. No handoffs between integration, dispatch, and reporting.
In one working session, we map how PLC management, demand response participation, and operational performance can be operated as a single program across your Ohio facilities, with operating logic tuned to PJM market dynamics and Ohio’s broad industrial profile.
using interval data and operational context.
that respect production schedules, shift patterns, and process integrity requirements across diverse industries.
across Capacity Performance, Synchronized Reserves, and Economic Load Response.
your team can use for internal approval and implementation.
Thank you for your interest in an Ohio peak load assessment. Our PJM team will follow up to schedule a 30-minute working session. Please complete the form below.
Reduce metered demand during PJM's coincident peak hours. PLC drops on the bill the following delivery year, lowering capacity charges across the entire portfolio.
Forecast the days where PLC risk concentrates, primarily July and August afternoons across Ohio. Document the action taken. Reduce the share of operating cost that surprises finance.
Use PJM Capacity Performance demand response where eligible, aligned to site limits and the realities of continuous-process or shift-driven operations.
Define no-go boundaries inside the dispatch logic. Steel furnaces hold. Paint shop temperatures stay constant. Engine assembly continuity stays uninterrupted. Semiconductor clean rooms stay protected. Data center IT loads stay covered. Program participation does not compromise process integrity.
Ohio industrial portfolios often span AEP, FirstEnergy, Duke, and DP&L territories. FacilityIQ compares site performance under shared baselines and identifies underperformance early, even across utility boundaries.
The Intel build and broader data center expansion in central Ohio are reshaping Ohio's load profile. Performance data and operating documentation that meet semiconductor and hyperscale governance standards position your facility for the operating environment ahead, not just today's bill.
For Ohio facilities in PJM, Rodan’s product set runs as a bundle. Demand response is the participation layer. PeakIQ is the forecasting layer. FacilityIQ is the operational performance layer. Each piece can stand alone, but the bundle is how the value compounds across diverse industrial operations.
Continuous operational performance monitoring across sites. See site behavior in context, spot underperformance early, and compare across the portfolio with shared baselines and audit-grade reporting.
Advance notification of PJM peak risk windows, calibrated to PLC management for Ohio facilities. Act at the right hour to influence the five highest peak hours of the year.
Capacity Performance enrollment, dispatch, and operating routines for PJM Load Modifying Resource and ancillary services across AEP Ohio, FirstEnergy operating companies, Duke Energy Ohio, and DP&L zones. Built for steel, auto, aerospace, chemicals, and continuous-process duty cycles.
Prefer email? Send us a message and we’ll respond within one business day.
Strong candidates are loads that can be reduced, shifted, or sequenced for short windows without creating safety risk, product quality issues, or major restart problems. In Ohio, this often includes HVAC strategies, compressed air optimization, chilled water adjustments, process scheduling moves, and noncritical pumping or conveying, depending on site type.
Common fit patterns by facility type
Manufacturing: Sequencing noncritical motors, rescheduling batch steps, adjusting compressed air setpoints, and shifting maintenance timing.
Warehousing and logistics: HVAC and ventilation strategies, battery charging schedules for equipment fleets, and staggered process loads.
Data centers: Noncritical support loads, staged cooling optimization, and coordination of backup assets where permitted and appropriate.
How Rodan supports
PeakIQ: Provides early warning so operations can schedule changes, rather than react.
Demand Response: Rodan helps translate flexible load into a curtailment plan with clear steps and owners.
FacilityIQ: Gives multi-site visibility and flags underperformance early, which is critical for portfolio operators.
What to avoid
Do not build a plan that depends on a single person, a single shift, or a last-minute work-around. Peak management should feel like a standard operating procedure, with documented steps, clear limits, and measurable outcomes that finance can validate.
Yes, storage can support peak load management by reducing peak demand, smoothing load shapes, and supporting demand response participation when program rules and site constraints align. The strategy must protect the primary purpose of the asset, including resilience requirements, and it must match how the facility operates.
What storage can do in a peak strategy
Peak shaving: Discharge during the highest-risk hours to reduce peak demand.
Load shaping: Smooth ramps to avoid operational and electrical stress.
Program participation support: In some cases, storage can support demand response performance by providing controlled, repeatable reductions.
What leaders should decide early
Resilience boundaries: Minimum state of charge requirements and outage-readiness rules.
Dispatch governance: Who controls discharge decisions during peak windows.
Measurement and validation: How performance will be reported and verified.
How Rodan supports
Rodan’s approach connects peak management, demand response program execution, and measurement workflows, then aligns the operational plan to your constraints.
PeakIQ provides early warning to plan charge and discharge windows.
FacilityIQ supports visibility during event windows for portfolio operators.
SettlementIQ supports billing and revenue validation when savings and program payments matter to finance.
Storage economics vary widely by site and tariff, so the right starting point is a site-specific review, tied to operational priorities and financial goals.
Peak strategies typically create value in two ways: reduced peak-driven charges over time and demand response payments tied to program participation and performance. The exact mix depends on your tariff, load profile, and program eligibility, so the right starting point is a sizing assessment, not a generic promise.
Where finance teams see value
Budget stability: Fewer surprise cost spikes tied to peak hours.
Revenue potential: Demand response can turn flexible load into a new revenue line, with variability by site and program.
Reduced reconciliation effort: Better measurement and settlement processes reduce time spent on disputes and corrections.
How Rodan supports finance-grade outcomes
Demand Response program management: Rodan handles the lifecycle work that protects performance and settlement.
SettlementIQ: Simulates bills using interval data and flags discrepancies earlier, supporting audit-ready workflows.
FacilityIQ: Supports site-level visibility during event windows, which helps explain results internally.
How to socialize the business case
Build it around drivers your CFO cares about: predictable budgeting, controllable risk, and measurable outcomes. Tie every action to a cost driver, a revenue driver, or a risk driver, then document how results will be verified. That is how peak load management becomes a procurement decision that stands up in the boardroom.
PJM demand response events are called when the grid needs load relief. A participating Ohio facility reduces consumption according to an agreed plan, and earns program payments tied to availability and performance, subject to the program’s rules and measurement approach.
What to expect operationally
Compressed timelines: In PJM emergency programs, lead time can be short, often in the 30 to 120 minute range.
Clear roles: Someone must own the “go/no-go” call, and the curtailment steps must be safe and repeatable.
Proof requirements: Performance must be measured against a baseline and validated through settlement.
How Rodan supports
Program lifecycle management: Rodan runs eligibility review, enrollment, curtailment plan development, event dispatch coordination, and settlement reconciliation.
Event readiness: The best outcomes come from testing curtailment steps during normal operations, then documenting what works.
FacilityIQ and SettlementIQ: FacilityIQ shows event window performance against actual consumption, and SettlementIQ strengthens billing and revenue validation.
What your procurement team should ask
What is the realistic curtailment range during peak hours, without affecting core production?
Who approves curtailment, and what are the safety and quality boundaries?
How will settlement and billing validation be handled so finance can trust the results?
PeakIQ supports peak load management by monitoring grid conditions and sending peak risk alerts with lead time, so your team can take planned actions before the highest-cost window hits. It relies on interval data and site information to align alerts with how your facility actually operates.
What PeakIQ delivers
Multi-stage alerting: Week-ahead, day-ahead, and day-of alerts, with in-day adjustments.
Multiple channels: Email, text, and automated phone calls.
Operational fit: You choose a response window that matches your operational reality.
What data is typically needed
Interval meter data or utility interval access.
Basic facility information, including operating schedule and major load drivers.
Key contacts and escalation paths for alert delivery and response.
How PeakIQ fits with other Rodan offerings
Pair PeakIQ with Demand Response to align peak actions with program participation when appropriate.
Use FacilityIQ if you manage multiple Ohio sites, so performance can be tracked consistently.
Add SettlementIQ if billing validation and finance reporting are pain points, or if DR revenue is growing and needs stronger controls.
PeakIQ is most valuable when alerts feed a documented curtailment checklist owned by operations, supported by measurement, and validated by finance workflows.
The first 30 days are focused on sizing value, defining safe operational actions, and setting up the measurement path that finance can trust. The goal is to move from “we think we can” to “we have a documented plan and a clear path to execute.”
Typical first-30-day flow
Data intake: Utility bills, interval data access, and basic facility operating details.
Peak exposure review: Identify which hours and conditions are driving peak risk, and what controllable levers exist.
Curtailment plan draft: Document actions, owners, timing, and no-go boundaries.
Program fit review: Assess demand response eligibility and readiness, aligned to PJM and utility requirements.
Measurement and validation setup: Align reporting expectations across operations and finance, and define how results will be verified.
How Rodan products support onboarding
PeakIQ: Can be staged early to support near-term peak readiness.
Demand Response: Enrollment and program management steps begin once fit is confirmed.
FacilityIQ: Added when multi-site visibility is a priority.
SettlementIQ: Added when billing validation, reconciliation backlog, or revenue verification is a material pain point.
The deliverable your procurement team should expect is a clear, defensible plan: what actions will happen, who owns them, how performance will be measured, and how financial results will be validated.
Peak load management in Ohio is the discipline of reducing or reshaping electricity use during the specific hours that drive the biggest cost outcomes, including demand-related charges, capacity-related costs, and peak price exposure. In PJM territory, those critical hours can also overlap with demand response events, where curtailment can generate revenue.
What leaders in Ohio should focus on
The “few hours” problem: Most facilities do not lose money on average kWh usage. They lose money when peak demand spikes during the wrong hours.
Operational control: The value comes from repeatable actions that protect safety and uptime, not heroic last-minute calls.
Verification: Savings and revenue only count when performance and settlement stand up to scrutiny.
How Rodan supports
PeakIQ: Delivers week-ahead, day-ahead, and day-of peak risk alerts, so operations can act with lead time.
Demand Response: Rodan manages the program lifecycle, including eligibility review, enrollment, event operations, and settlement follow-through, while your team executes the agreed actions.
SettlementIQ: Adds daily invoice validation, so billing surprises surface earlier, not at close.
What you can do now
Bring a recent utility bill and interval data, and map the top drivers of peak demand. Then align operations and finance on what you will do, what you will never do, and who owns the call when the peak window arrives.
FacilityIQ is designed for portfolio visibility. It aggregates consumption across sites and maps demand response activation windows to actual performance, so you can see what happened at each facility during each event window, without manual reporting.
Why portfolio operators choose it
One view across sites: Compare performance across Ohio locations and beyond.
Event window clarity: Event windows are mapped to consumption, so you can see performance during the window, not only after.
Early underperformance detection: Underperforming sites can be identified earlier, reducing settlement surprises.
How it supports better outcomes
Operational coaching: When a site underperforms, you can identify whether it was a process issue, a staffing issue, or a controls issue.
Standardization: Portfolio-wide playbooks work best when performance data is consistent.
Internal reporting: Finance, operations, and sustainability teams can align on one version of performance.
How it fits with PeakIQ and SettlementIQ
Use PeakIQ to trigger planned actions with lead time.
Use FacilityIQ to verify what happened during the window.
Use SettlementIQ to validate bills and program payments so results hold up at close.
For Ohio organizations with multiple facilities, FacilityIQ turns peak and DR performance into a repeatable management process, not a site-by-site guessing exercise.