Iowa runs on more wind power than any other state, with overnight prices that swing low when wind is high and tighten fast when it isn’t. If you operate an Iowa facility and have, or are evaluating, an energy storage system, the hard part is operating it against that volatility. Rodan integrates storage into MISO programs, manages dispatch, and forecasts peak risk so the asset captures value across the swings.
Iowa’s grid is not a flat duck curve. It is a wind-driven system with deep overnight price drops, tight afternoon peaks, and seasonal load that follows harvest, hogs, and corn processing. Rodan operates storage and demand response assets across five North American markets, including MISO. For Iowa facilities, that means a single team for integration, dispatch, and performance reporting, with operating logic tuned to a wind-heavy grid.
We model the actual MISO price shape that an Iowa facility sees, including overnight wind events, afternoon ramp periods, and the occasional negative pricing window. The dispatch logic captures arbitrage where it exists and protects against peak charges when it doesn't.
Iowa's load profile shifts with the calendar. Ethanol plants, grain dryers, hog operations, and food processing each have their own peak weeks. We tune dispatch to those cycles, not to a generic MISO baseline.
Demand response, peak forecasting, and facility performance are operated by a single team in a single Real-time Operations Center. No handoffs between integration, dispatch, and reporting.
In one session, we map how an existing or planned storage asset can be operated for MISO program value, peak demand reduction, and value capture against Iowa’s wind-driven price profile, with operational guardrails for your facility.
using interval data and operational context.
including peak shaving, arbitrage during wind events, and resilience layering.
across LMR, ancillary services, and economic demand response.
your team can use for internal approval and implementation.
We’ll confirm which programs you qualify for and handle all registration.
Storage discharged during MISO peak hours reduces metered demand at the moments that drive the capacity charge component of your MidAmerican or Alliant bill.
Iowa's high wind penetration creates real arbitrage windows. Charge during low-price wind events, discharge during peak. Where the asset duration supports it, this pathway adds revenue beyond capacity participation.
Forecast peak risk windows in advance, including the late-summer and early-fall dynamic where corn drying, ethanol production, and MISO-wide system stress can converge.
Reserve capacity for backup priorities, especially for processes where an unplanned shutdown spoils product or breaks a continuous batch.
Define no-go boundaries inside the dispatch logic. Critical process loads stay covered. Participation does not compromise throughput during harvest peaks or shoulder-season production runs.
Iowa agricultural processors and manufacturers often run multiple plants. FacilityIQ compares site performance against shared baselines and identifies underperformance early.
For Iowa facilities, Rodan’s MISO product set is 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 on a wind-driven grid.
Continuous operational performance monitoring across sites. See site behavior in context, spot underperformance early, and compare across the portfolio.
Advance notification of MISO peak risk windows, calibrated to Iowa conditions including wind ramp events and seasonal agricultural load. Dispatch the asset at the right hour rather than reacting after the peak forms.
Enrollment, dispatch, and execution for MISO Load Modifying Resource and ancillary services in MidAmerican and Alliant territories. Built for industrial and agricultural duty cycles.
Prefer email? Send us a message and we’ll respond within one business day.
FacilityIQ helps multi-site programs by showing performance during the time window that matters, site by site, with a consistent view across the portfolio.
Multi-site demand management often breaks down for one reason: inconsistency. One site executes, another site misses a step, and leadership sees mixed results. A portfolio view helps teams catch issues quickly and keeps the program focused on correction and repeatability.
FacilityIQ supports that operating rhythm by:
Aggregating consumption data across sites.
Mapping key windows to performance, so the team sees what happened when it happened.
Supporting a consistent reporting view for procurement, operations, and finance.
This is also useful for coaching. If a site underperforms, the team can look at concrete questions: Was the action executed, did the site have a constraint that day, did staffing change, or did the data feed have gaps. That is a faster path to improvement than debating summaries after the fact.
For procurement leaders, FacilityIQ supports governance. It creates a shared performance record that can be used in leadership updates and budget reviews. For operations leaders, it reduces friction because the focus stays on actions and boundaries that were agreed up front.
PeakIQ supports demand management by giving operations lead time and a consistent trigger before peak-risk windows. That makes the playbook usable, which is the point.
Most facilities are not set up to watch grid conditions all day. Operations teams are focused on production, staffing, and safety. When a peak window shows up with little notice, teams improvise, and results vary. PeakIQ helps reduce that variability by creating a predictable alert-and-action routine.
A good PeakIQ setup includes:
Primary and backup recipients for each site, including off-hours coverage.
A response window that matches how quickly the site can act.
A short action checklist tied to the alert.
A simple log of what actions were taken.
PeakIQ works best when it activates a playbook that has already been approved. It is not a replacement for operating boundaries. It supports execution inside those boundaries.
Procurement benefits because actions become consistent and easier to report. Finance benefits because actions can be tied to specific windows that can be reviewed against interval data. Operations benefits because the team has time to coordinate and stay within safe limits.
If your organization runs multiple sites, PeakIQ also helps standardize the cadence across locations, which reduces the “each site does its own thing” problem that can undermine portfolio results.
A demand management playbook is a short, written checklist of approved actions that the site can execute during peak-risk windows, with clear owners, timing, stop points, and recovery steps.
A playbook that works in the real world has a few traits:
It is short enough that a supervisor can run it without debate.
It is built around site constraints, not a target number.
It has stop points written in plain language.
It has a recovery plan so operations can stabilize after the window.
A practical structure looks like this:
Tier 1 actions: always allowed, low-risk steps.
Tier 2 actions: steps that require approval, with the approver named.
Off-limits list: actions the site will not take.
Stop points: conditions that end participation immediately.
Recovery steps: how the site returns to normal.
The playbook also needs roles:
Who receives alerts and who is backup for nights and weekends.
Who can authorize actions.
Who confirms execution and logs what happened.
A playbook that depends on a single person being on shift will not scale. The goal is repeatable execution. That is what protects operations and supports reporting that procurement and finance can rely on.
Start with a scoped assessment that identifies peak exposure, site limits, and measurement readiness. The first step should not feel heavy. It should produce a clear decision package that procurement, operations, and finance can act on.
A practical start includes:
Sharing a recent utility bill for each site in scope.
Confirming interval data access, or the path to obtain it.
Documenting key constraints and protected loads.
Identifying the right site contacts for approvals and execution.
Agreeing on how results will be reviewed and reconciled.
Procurement should expect these outputs:
A prioritized site list based on exposure and operational feasibility.
A draft playbook per site with owners, timing, stop points, and recovery steps.
A recommendation on demand response fit where eligibility exists.
A reporting approach that keeps window-based performance and billing validation connected.
Rodan’s role is to reduce internal lift and keep the program operationally safe. That starts with boundaries, then builds execution, then builds reporting finance can trust. When those pieces are in place, scaling across more Iowa sites becomes a business decision, not an operational gamble.
A good fit is any large facility with controllable load that can be adjusted for limited windows without putting safety, quality, comfort, or uptime at risk. Industry matters less than how the site operates.
Fit usually comes down to three questions:
Can the site reduce or shift a meaningful amount of load for a defined window?
Can the site do it consistently across shifts and staffing changes?
Can the organization measure performance and reconcile outcomes without manual rebuilds?
Facilities often have more flexibility than they expect, but it sits in the supporting systems and scheduling levers, not the core process. Strong programs start conservative, prove repeatability, then expand the action list only after site leaders are comfortable.
A portfolio view can also improve fit. A single site may have limited flexibility on its own. A group of sites can spread the response across different operating profiles, which reduces strain on any one facility. That approach also helps procurement and finance because it creates a more stable, repeatable result set.
Rodan starts with a scoped assessment: review bills, confirm interval data access, document operating limits, and identify realistic actions. The output is a prioritized site list, a draft playbook per site, and a clear path for demand response participation where it makes sense.