Michigan’s industrial load is shaped by the auto industry, and the auto industry shuts down for retooling in July, the same month MISO peaks. If you operate a Consumers Energy or DTE facility, your demand management program has to work with that calendar, not against it. Rodan provides the operating layer that turns Michigan’s seasonal industrial rhythm into predictable energy outcomes.
Michigan industrial load follows the auto industry. Stamping plants run two-shift weekdays. Paint shops and final assembly lines run continuous through the model year. Retooling shuts most lines in July. Tier-1 and tier-2 suppliers move with the OEMs. Rodan operates demand response and peak management for Michigan facilities with operating logic built around how the auto and industrial base actually runs, not around a generic MISO baseline.
We model the actual load profile of a Michigan industrial facility, including model-year shutdown periods, shift transitions, and the difference between continuous-process operations and discrete manufacturing. The operating playbook reflects the calendar, not just the meter.
Many Michigan industrial portfolios have ten or more facilities of varying size, ownership, and load profile. We scope eligibility by site, build dispatch logic that respects each facility's operational reality, and report performance in a way that finance and procurement can defend in a quarterly review.
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 Michigan facility, with operating logic tuned to the auto-industry calendar and Lower Peninsula MISO conditions.
using interval data and operational context, including model-year shutdown patterns where applicable.
that respect shift schedules, paint and assembly continuity, and supplier-network coordination.
across LMR, ancillary services, and economic demand response in Local Resource Zone 7.
your team can use for internal approval and implementation.
Thank you for your interest in a Michigan demand management assessment. Our MISO market expert will follow up to schedule a 30-minute working session. Please complete the form below.
Reduce metered demand during MISO peak hours where it is operationally possible. The capacity charge component of your Consumers Energy or DTE bill responds accordingly.
Forecast peak risk windows in advance, including the July dynamic where MISO-wide cooling load spikes and a meaningful portion of Michigan industrial load is offline for retooling. The math is different from a typical industrial state, and the operating plan needs to reflect it.
Define no-go boundaries inside the dispatch logic. Paint shop temperatures hold. Continuous-process loads stay covered. Program participation does not interrupt a model-year build schedule.
For Michigan organizations with multiple plants, especially those running tier-1 supplier networks across Consumers Energy and DTE territory, FacilityIQ compares site performance under shared baselines and identifies underperformance early.
For Michigan organizations with multiple plants, especially those running tier-1 supplier networks across Consumers Energy and DTE territory, FacilityIQ compares site performance under shared baselines and identifies underperformance early.
For organizations with sites in both Michigan MISO and the small Indiana Michigan Power PJM territory in southwest Michigan, we keep the operating layers separate so the two market structures are not blended into one report.
For Consumers Energy and DTE-served industrial facilities, Rodan’s MISO 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 for an industrial portfolio.
Continuous operational performance monitoring across sites. See site behavior in context, spot underperformance early, and compare across the portfolio, including Consumers Energy, DTE, and Indiana Michigan Power facilities under one view.
Advance notification of MISO peak risk windows, calibrated to Michigan industrial load patterns and the auto-industry calendar. 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 MISO Local Resource Zone 7. Built for auto, metals, food processing, and chemical duty cycles.
Prefer email? Send us a message and we’ll respond within one business day.
FacilityIQ helps multi-site portfolios by providing window-based visibility across sites, so leaders can see performance during the window and address issues quickly. Consistency is the main portfolio problem. A single site that drifts from the routine can skew results and create noise in reporting.
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 prioritization of coaching and playbook updates
Window-based visibility also improves troubleshooting. When a site underperforms, the team can focus on concrete causes: staffing coverage, constraints that day, controls behavior, or data gaps. That reduces internal debate and improves the playbook over time.
FacilityIQ also helps standardize governance. Sites do not need identical actions. They need the same rhythm: alert, execute within limits, verify performance, and review outcomes. That rhythm is what keeps programs stable across multiple facilities.
PeakIQ helps by giving operations lead time and a consistent trigger before peak-risk windows, so sites can run an approved checklist without last-minute coordination.
Peak routines often fail for simple reasons: the site gets notice too late, the decision owner is unavailable, or actions vary by shift. PeakIQ supports consistency by putting alerting and response timing into a repeatable routine.
A practical PeakIQ setup includes:
Primary and backup recipients at each site
Off-hours coverage for nights and weekends
A response window that matches approvals and staffing
A short checklist tied to alerts
A quick action log
Procurement benefits because peak routines become easier to defend and report. Operations benefits because the team has time to coordinate and stay inside safe limits. Finance benefits because actions can be tied to a defined window, which supports review and reconciliation.
PeakIQ does not replace operating boundaries. It supports execution inside boundaries that were approved in advance. That is what keeps peak response consistent across seasons and staffing changes.
A curtailment playbook is a short, written checklist of approved actions a site can execute during peak or event windows, with owners, timing, recovery steps, and stop points. Ownership is shared: operations owns safety and feasibility, procurement owns scope and governance, and finance owns the reconciliation routine.
A playbook that works in the field has:
Actions that are reversible and repeatable
Roles that are assigned by function, not one person
Stop points written in plain language
Recovery steps that protect the process after the window
A simple method to record what happened
A practical structure is:
Always-allowed actions that carry low operational risk
Approval-required actions with a named approver
Off-limits actions that the site will not take
Stop points that end participation immediately
Recovery steps that return the site to stable operation
The decision owner matters. A site needs one person who can make the go or no-go call during a tight window. Backups matter just as much, since event windows do not follow office hours.
Rodan supports playbook development by working within your site limits. The goal is not a long list. The goal is a checklist that can be executed the same way on any shift.