Minnesota’s grid does not look like the rest of MISO. Winter peak risk is the defining stress event, taconite plants and food processors run continuous through the cold months, and a 100% carbon-free electricity mandate is reshaping how every load is operated. Demand management here means working with a winter-tilted system, not a summer one.
MISO Local Resource Zone 1 carries the system’s tightest winter conditions. Cold snaps, sustained subzero stretches, and the simultaneous spike in residential heating and continuous industrial process load create a stress profile that no other MISO state shares. Rodan operates demand response and peak management for Minnesota facilities with operating logic built for cold-weather conditions, not adapted from a summer-peak playbook.
Most MISO playbooks were written for August. Minnesota's risk concentrates in January and February. We model winter system stress, the role of natural gas constraints during cold snaps, and the operating windows where demand management actually delivers.
Iron mining on the Mesabi Range, paper and pulp in the north, and food processing across the state run continuous loads that cannot be casually interrupted. We model what is fixed, build dispatch logic around what is flexible, and respect the operating reality of each industry.
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 peak management, demand response participation, and operational performance can be operated as a single program for your Minnesota facility, with operating logic tuned to winter peak risk and Local Resource Zone 1 conditions.
using interval data and operational context, including winter cold-snap exposure.
that respect cold-weather process minimums, freeze protection, and continuous industrial duty cycles.
across LMR, ancillary services, and economic demand response in Zone 1.
your team can use for internal approval and implementation.
Thank you for your interest in a Minnesota demand management assessment. Our MISO market expert will follow up to schedule a 30-minute working session. Please complete the form below.
Target the hours that drive variance with a repeatable routine.
Reduce month-to-month surprises with measured actions and clear review.
Use demand response where eligible, aligned to site limits and risk tolerance.
Use approved actions and stop points that protect safety and uptime.
Standardize execution and reporting across sites without forcing identical actions.
Validate bills earlier, reduce disputes, and shorten month-end churn.
Explore the intelligence and operations products available here.
Continuous operational performance monitoring across sites. See site behavior in context, spot underperformance early, and compare across the portfolio, including Xcel, Minnesota Power, and Otter Tail facilities under one view.
Advance notification of MISO peak risk windows, calibrated to Minnesota winter conditions and cold-snap dynamics. Act at the right hour rather than reacting after the peak forms.
Enrollment, dispatch, and execution for MISO Load Modifying Resource and ancillary services in Local Resource Zone 1. Built for winter-peak conditions and continuous-process industrial loads.
Prefer email? Send us a message and we’ll respond within one business day.
PeakIQ supports demand management by giving operations lead time and a consistent trigger ahead of peak-risk windows, so sites can run an approved checklist without last-minute coordination.
Peak routines often break down when notice comes too late or roles are unclear. An alert-driven routine helps keep the work consistent across shifts and across sites.
A practical setup includes:
Primary and backup recipients for each site, including off-hours coverage
A response window that matches staffing and approval needs
A short checklist tied to alerts
A simple log of actions taken
Procurement benefits because peak routines are easier to defend and report. Operations benefits because the site has time to coordinate and stay inside safe limits. Finance benefits because actions can be tied to defined windows, which supports review and reconciliation.
PeakIQ works best when it activates a checklist that has already been approved and tested against site limits. That keeps peak response consistent across seasons and staffing changes.
A site checklist is a short, written list of approved actions that can be executed during peak-risk windows without compromising safety, quality, comfort, or uptime. It reads like an SOP, not a brainstorming document.
A checklist that holds up over time includes:
Owners: who executes each action, and who approves actions that need sign-off
Timing: how long each step takes and what the site expects to see on load
Stop points: conditions that end participation immediately
Recovery steps: how the site returns to steady operation after the window
Logging: a simple way to record what was done and when
Many sites start with a small set of low-risk actions, then add actions only after operators are comfortable and results are consistent. This avoids “one good day” programs that fall apart when staffing changes or schedules tighten.
For multi-site portfolios, the format should be the same across sites, even if the actions differ. That makes training easier, makes reporting easier, and reduces confusion in leadership reviews.
Rodan helps build these checklists around your operating limits, then ties performance verification to interval data during the window. That keeps the work practical for operators and reviewable for finance.
FacilityIQ adds window-based visibility across sites, so portfolio teams can see performance during the window and address issues quickly. Multi-site programs often struggle with inconsistency, where a small number of sites drift from the routine and results become harder to explain.
A portfolio view supports:
One way to compare sites during the same window
Early detection of underperformance
A shared record for procurement, operations, and finance
Better targeting of coaching and checklist updates
It also helps shorten problem-solving. When a site underperforms, the team can focus on practical causes: staffing coverage, constraints that day, controls behavior, or data gaps. That reduces internal debate and improves the checklist over time.
Sites do not need identical actions. They need the same rhythm: alert, execute within limits, verify performance, and review outcomes. FacilityIQ supports that rhythm by keeping performance tied to the actual time window.
Rodan needs enough information to confirm scope, document site boundaries, and identify realistic actions. The goal of the intake is clarity, not paperwork.
A useful starter set includes:
Recent utility bills and supplier invoices for sites in scope
Meter identifiers tied to each location
Interval data access details, or the path to obtain it
Site schedules, staffing coverage, and key constraints
Protected-load notes tied to safety, quality, comfort, and uptime
Names of the operations approver and finance reviewer
Mixed portfolios benefit from a clean meter map. Without it, teams waste time comparing sites that should not be compared, and results can look inconsistent even when the program is working.
Rodan uses the intake to produce outputs procurement can use:
A prioritized site list based on exposure and operational feasibility
A draft checklist per site with owners, timing, stop points, and recovery steps
A screening view of demand response fit where eligibility exists
A reporting and validation approach that keeps window-based performance tied to billing review
This keeps the rollout focused on sites with real potential, while keeping operations and finance aligned from the start.
Strong candidates are loads that can be reduced or shifted for short windows, are reversible, and can be executed consistently across shifts. The exact list depends on the facility, so the best approach is to start with constraints and interval patterns, then pick actions that fit.
Load categories many large facilities evaluate include:
HVAC and ventilation adjustments within approved limits
Compressed air pressure bands and staged operation within equipment constraints
Pumps, fans, and supporting systems where sequencing is available
Process scheduling moves for discretionary steps
Deferrable loads that can move without operational risk
What matters is not the category. It is the guardrail:
Is there a protected-load list?
Are stop points written and enforceable?
Is there a recovery step that avoids downstream issues?
Can the site run the same steps on any shift?
A short list executed consistently beats a long list that only works when the right person is on duty. Repeatability is what protects operations and supports reporting finance can reconcile.
Rodan helps sites focus on actions that match real operating limits, then ties verification to the window when actions were taken.
Procurement should expect a clear scope map, a realistic action set by site, and a reporting routine that finance can use. Rollout should start with the sites that have clear exposure and realistic flexibility, then expand once execution is stable.
Inputs for the assessment:
Utility bills and meter mapping
Interval data access details
Site schedules and constraints
Protected-load notes
Names of operations approvers and finance reviewers
Outputs procurement should receive:
A prioritized site list based on exposure and feasibility
A draft checklist per site with owners, timing, recovery steps, and stop points
A screening view of demand response fit where eligibility exists
A measurement and validation approach that ties window-based performance to billing review
Success looks like repeatable execution and clean reporting. Big promises are not the goal. A routine your sites can run, and your finance team can reconcile, is what makes demand management stick.