Skip to main content
Key dates & deadlines

Michigan key dates and deadlines for 2026

PJM program calendars and enrollment windows vary by program and utility. These planning windows keep procurement and operations aligned early enough to act.

Next: June 2026 BRA
Adjust capacity positions from prior BRA

2026/27 Third Incremental Auction

Cold snaps can create sharp load ramps and fuel-driven volatility that push system stress events.

Enroll before February 2026

Action Required
BRA for delivery year starting June 2028

2028/29 Base Residual Auction

Hot and humid stretches can drive peak system conditions and higher exposure to peak-driven charges.

Enroll before June 2026

Always Open
Year-round readiness

Year-Round Enrollment and Operations

Demand response enrollment, baseline validation, telemetry readiness, and ongoing peak risk monitoring operate year round.

Enroll anytime

We’ll confirm which programs you qualify for and handle all registration.

Platform solutions

Products available in this market

Explore the intelligence and operations products available here.

FacilityIQ™ ->

Monitor multisite performance during events, then spot issues early, before settlement becomes a dispute.

Available in
  • IESO
  • PJM
  • NYISO
  • AESO
  • MISO
PeakIQ™ ->

Get peak risk alerts across week-ahead, day-ahead, and day-of horizons for action windows your team can meet.

Available in
  • IESO
  • PJM
  • NYISO
  • AESO
  • MISO
SettlementIQ™ ->

Track expected outcomes and settlement drivers, then validate results with clean, defensible data.

Available in
  • IESO
  • PJM
  • NYISO
  • AESO
  • MISO
FlexOps™ ->

Use batteries and onsite assets for peak shaving and program participation, without sacrificing resilience priorities.

Available in
  • IESO
  • NYISO
  • AESO
Demand Response ->

Earn revenue by reducing load during PJM events, with Rodan managing enrollment and operations.

Available in
  • IESO
  • PJM
  • NYISO
  • AESO
  • MISO
GridOps™ ->

Close data and connectivity gaps that block participation, measurement, and settlement confidence.

Available in
  • IESO
  • AESO
Free strategy session

Michigan demand side management assessment

A fast, structured review that shows where your sites can reduce peak-driven costs and participate in PJM programs with low operational risk.
  • Identify flexible load, controls, and site constraints across your Michigan footprint.

  • Screen PJM program fit and operational requirements at a high level.

  • Quantify peak exposure and estimate value drivers using your interval data.

  • Deliver an execution plan your operations team can run without guesswork.

Prefer email? Send us a message and we’ll respond within one business day.


150+
PJM Participants
$25M+
Annual Revenue
1.5 GW
Managed Capacity
20+
Years Experience
FAQ

Michigan PJM energy market FAQ's

PeakIQ™ is designed to turn peak risk into operational lead time. Many peak-driven charges and risk moments are not caused by average usage. They are caused by a small number of hours when grid conditions, weather, and system demand align. Michigan facilities that face PJM exposure can benefit when they know peak windows early enough to plan and execute a safe response.

PeakIQ™ provides alerting across week-ahead, day-ahead, and day-of horizons, with in-day updates, and the alerts are supported by Rodan’s monitoring capability. The value for procurement is straightforward: fewer surprises and fewer missed opportunities to reduce peak exposure. The value for operations is equally important: time to coordinate actions within defined guardrails. A two-hour response requirement is very different from a six-hour response option. A plan that fits the plant’s operating rhythm is more likely to be executed consistently. PeakIQ™ also supports better internal alignment. When alerts are consistent and credible, teams can standardize who gets notified, what actions are triggered, and how confirmation is tracked. That reduces friction between energy managers and site leaders.

PeakIQ™ works best when paired with a playbook that defines actions by severity level and season. It also pairs well with FacilityIQ™ and SettlementIQ™ because alerts are only the start. Performance needs to be measured, validated, and tied to financial outcomes. Program rules and peak definitions vary by utility and market structure, so PeakIQ™ should be treated as a decision-support layer that feeds your internal process and program participation strategy.

Demand response in PJM is a market mechanism that pays qualified customers to reduce electricity use when the grid needs help, often during high-demand periods or emergency conditions.

For Michigan facilities in PJM, the practical sequence is consistent even though the specific program details can vary by utility or offering. A site is assessed for fit, enrolled into the appropriate program pathway, and prepared to perform with clear response actions. During an event window, the facility reduces load relative to an established baseline using pre-approved actions.

Performance is measured using interval data and settlement rules, then payments and outcomes are calculated after the fact. Procurement leaders should focus on four realities. First, results depend on the site’s load profile and operational flexibility. Second, telemetry and data quality are not optional. They are core to proving performance. Third, response expectations need to match what operations can execute, which is why playbooks and response windows matter. Fourth, internal coordination is often the biggest blocker. A program can look good on paper, then fail in execution if roles are unclear.

Rodan’s approach is to treat demand response as an operating capability. We help define what the site will do, what it will not do, and how it will respond across different event types. We also support monitoring, event communication, and post-event validation using tools that map event windows to facility performance and surface issues early. Program names, lead times, and payment structures can shift, so the right posture is a durable process that stays valuable even as program details evolve.

FacilityIQ™ is built for multisite visibility and execution discipline. Michigan organizations often have multiple facilities, and procurement leaders want consistent performance without building a reporting process from scratch after every event.

FacilityIQ™ aggregates consumption data across sites and maps event windows onto facility performance so teams can see what happened during an activation. The operational value is early detection. If one site underperforms, it is better to see it quickly, address root causes, and reduce the likelihood of a settlement dispute later. That matters for procurement because settlement issues create uncertainty, delay payments, and reduce confidence in the program. FacilityIQ™ also supports internal accountability. Sites can be compared against expected behavior, and leadership can see which facilities execute playbooks consistently. That creates the conditions for scaling DSM and demand response Michigan efforts across the portfolio.

FacilityIQ™ is especially helpful when sites sit under different local utility relationships or have different operating profiles. A single dashboard view lets energy teams spot anomalies and focus support where it is needed. FacilityIQ™ is commonly paired with Demand Response services because Rodan can manage enrollment and operations, then use FacilityIQ™ to validate execution and performance. It also pairs with SettlementIQ™ because performance data becomes more valuable when it is tied to expected financial outcomes and settlement drivers. Programs and market rules vary, so the tool’s role is not to replace program documentation. Its role is to make execution and performance visible in a way operations and finance can trust.

Procurement leaders should evaluate a DSM plan the same way they evaluate any operational strategy tied to financial outcomes: controllability, measurability, and governance. Start with controllability. Which loads can be adjusted within a defined window without compromising safety, quality, or throughput? A DSM plan that requires heroic action will not scale. Move to measurability. Does the site have reliable interval data, and is the telemetry path ready to support program participation and settlement validation? Data gaps create disputes and uncertainty, which reduce confidence at the executive level. Governance matters just as much. Who owns the playbook? Who has authority during an event window? Who communicates to operations, finance, and leadership, and who signs off on what actions are allowed?

A strong plan includes a clear RACI-like structure even if it is written in plain language. It also includes a repeatable calendar and readiness routine tied to summer and winter peak periods. Procurement should also look at portfolio complexity. Many Michigan organizations have sites in multiple states or market footprints. The plan should be consistent enough to scale, with local adjustments at the site level.

Rodan supports this evaluation with an assessment that maps flexibility, screens program fit at a high level, and produces an execution plan with clear limits. The output should be something procurement can defend internally because it ties actions to measurable outcomes, not aspirational claims.

DER optimization becomes important when a site has onsite assets that can change the economics of DSM and demand response participation. Batteries, backup generation, and flexible controls can support peak shaving, event response, and operational resilience.

In Michigan, the value comes from aligning the asset’s operating priorities with the market and tariff realities the facility faces. A battery installed for resilience can also reduce peak exposure if dispatch rules are set correctly. It can support demand response events when program fit is confirmed and when dispatch does not conflict with critical load coverage. DER optimization requires discipline. The facility needs clear priorities, clear limits, and a dispatch plan that respects maintenance, warranty terms, and reliability requirements. Procurement leaders should focus on value stacking only after execution basics are stable. A site that cannot reliably execute a simple DSM playbook will struggle to capture additional value from a more complex asset strategy.

Rodan supports DER optimization by assessing the asset, reviewing constraints, screening program fit, and designing a dispatch approach that supports peak reduction and program participation without undermining resilience. The approach should also connect back to measurement and settlement. If a battery discharges during an event window, the team needs to know what effect that had on the baseline, the measured load reduction, and the settled outcome. That is where Energy Intelligence tools and settlement validation matter. Market and utility rules vary, so DER optimization should be framed as a site-specific plan that is built around your data, your risk tolerance, and your operating priorities.

Demand side management in Michigan is the set of actions a large energy user takes to actively shape when and how the facility uses electricity, with a focus on peak hours that drive a disproportionate share of total cost. In a PJM context, demand side management Michigan teams care about two linked outcomes: reducing peak-driven charges and creating optionality to earn revenue through demand response participation when a site is a fit. The work is practical, not theoretical. It starts with understanding the site’s interval data and identifying which loads can move, pause, or ramp within defined limits.

Many sites find flexibility in HVAC strategies, compressed air, pumps, process staging, battery dispatch, or noncritical loads that can be sequenced. Procurement leaders usually want one thing: predictability. Demand side management supports that by turning peak exposure into a plan with clear triggers, roles, and response windows. PJM program participation is one pathway within that plan.

Program rules, baselines, lead times, and event structures vary, so the right approach is to treat demand response as a controlled operating capability rather than a one-time signup. Rodan’s role is to translate the market requirements into an execution plan, manage enrollment and telemetry needs, support event operations, and tie results back to settlement outcomes using tools that make performance visible and defensible.

SettlementIQ™ is designed to connect operational performance to financial outcomes. Demand response and DSM efforts create value only when the organization can validate results, explain drivers, and reconcile settlement outcomes without a long back-and-forth. Michigan demand response participation tied to PJM exposure can involve multiple parties, baselines, event windows, and settlement steps. That complexity creates room for confusion.

SettlementIQ™ helps teams track expected outcomes and compare them to settled results, then identify gaps that can signal data issues, execution issues, or interpretation mismatches. Procurement leaders benefit because they get a clearer audit trail that supports budgeting and internal reporting. Finance teams benefit because the story is measurable and repeatable, not a one-time analysis.

Operations teams benefit because issues can be traced back to a specific site action or constraint rather than becoming a vague “program problem.” SettlementIQ™ also improves scale. When an organization adds more sites, the settlement workload grows quickly if everything is manual. A structured approach makes it possible to expand participation without expanding headcount at the same rate.

SettlementIQ™ fits best as part of a stack: Demand Response services to manage participation and operations, PeakIQ™ to anticipate risk windows, FacilityIQ™ to validate site execution, and SettlementIQ™ to reconcile outcomes. Exact settlement mechanics vary by program. The point is to build a reliable way to explain what happened and what it meant financially, using consistent data and reporting that can stand up to internal review.

Demand side management is the umbrella. Peak load management is one high-value use case within it.

Demand side management Michigan programs and strategies cover a wide set of actions that shape load, improve control, and reduce cost and risk over time.

Peak load management focuses on a narrower objective: reducing demand during the specific hours that drive peak-related charges or system stress exposure. In practice, many organizations start with peak load management because it is easier to explain internally and easier to measure. You find the peaks, identify controllable drivers, build a playbook, and execute during the windows that matter.

Demand side management expands beyond that by adding program participation options, longer-term operational improvements, and asset optimization. A battery can be dispatched for peak shaving. A controls upgrade can smooth ramp rates. A multisite organization can standardize playbooks and performance reporting across plants and campuses. Procurement leaders benefit because peak load management addresses budget volatility directly, and demand side management adds additional value streams and resilience benefits over time.

Rodan supports both. PeakIQ™ helps teams anticipate peak risk with actionable alert windows. FacilityIQ™ helps validate that sites executed as intended during an event. SettlementIQ™ helps connect actions to financial outcomes and settlement drivers. Demand response adds a revenue component when program fit is confirmed. The right approach is a staged plan: start with a peak-focused playbook, then expand scope when execution discipline is proven and the organization wants more value from flexibility and assets.

Telemetry and metering readiness determine whether demand response participation is smooth or painful. Most disputes and missed value come from gaps in data, timing, or measurement alignment. In Michigan demand response and DSM programs tied to PJM participation, interval data is central because performance is typically evaluated relative to a baseline and event window requirements. A site needs reliable interval metering, consistent data delivery, and a clean mapping between the facility’s load, the event window, and the measurement logic used for settlement.

Telemetry can also include real-time or near-real-time signals depending on the program path. Even when the technical requirements are manageable, the operational requirement is the same: the site must be able to prove what happened during an event and reconcile it with settlement outcomes later. Procurement leaders should treat telemetry as part of the business case, not a technical afterthought. If the site cannot prove performance, finance will not trust the results, and operations will lose interest.

Rodan supports metering and telemetry work as a foundational service that enables demand response, Energy Intelligence tools, and settlement validation. The right approach is to assess current infrastructure, identify gaps, and close them with the minimum scope needed for reliable participation. Program details and equipment needs vary by situation, so the safest promise is that Rodan will map the requirements to your facility and define a path that supports participation and measurement without forcing a full controls overhaul.

Michigan has a high concentration of energy-intensive operations, and many facilities run processes where uptime, quality, and throughput drive margin. Demand side management matters because it targets cost drivers that procurement cannot solve with a single supply contract. Even with a good energy price, peak-driven charges can create budget volatility that shows up months later, long after the operating decision was made. Demand side management gives manufacturers a way to reduce that volatility with operational moves that are planned and tested.

The goal is not to disrupt production. The goal is to create a short list of actions that protect safety and quality, then deliver measurable impact during the few hours that matter most.

Common approaches include pre-cooling strategies, shifting batch timing, sequencing motors, using onsite generation within environmental and reliability limits, and dispatching storage for peak shaving when available. A strong program also clarifies internal ownership. Procurement sets the financial objective, operations defines what is allowed, and the site executes a playbook with clear decision rights.

Demand response Michigan opportunities can layer on top when program fit is confirmed, turning flexibility into revenue and making the effort easier to justify internally. Rodan supports this by mapping the site’s load shape, defining operational guardrails, confirming telemetry readiness, and running event operations so plant teams do not have to become market specialists to capture value.

Still have questions? Contact our team

Offer

Michigan demand side management assessment

Share a recent utility bill, and Rodan will size your demand response fit, peak exposure, and readiness steps for a low-disruption start.

  • Interval load review, plus preliminary curtailment sizing
  • Program fit screening, plus an operations readiness checklist
  • Measurement and settlement validation approach for finance
  • Practical next steps with a simple timeline