Energy demand management Minnesota

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.

Demand-side management is the broader operating program. Demand response is a paid participation path that can sit inside that program when a site is eligible and can deliver verified performance.

Demand-side management covers peak routines, load shifting, and measurement discipline. Demand response adds event windows, program obligations, and settlement follow-through. Demand response tends to run better when the demand-side management basics already exist, because the site has a checklist, role clarity, and a verification routine.

A useful way to separate them internally:

• Demand-side management: the routine your team runs to control peak exposure

• Demand response: a program path that pays for verified load reduction during events

Demand response becomes a fit when:

• The site can reduce load inside approved boundaries

• The decision owner and backups are clear for off-hours coverage

• Interval data is clean enough to validate performance consistently

Even when demand response is not a fit for a specific site, demand-side management can still reduce peak-driven variance and improve predictability. That can be valuable on its own, and it can prepare the site for participation later if conditions change.

Rodan supports both paths, with a focus on safe execution, consistent reporting, and a clean handoff to finance for reconciliation.

Energy demand management in Minnesota is a structured way to reduce or shift electricity use during peak periods that drive cost exposure, backed by a routine to verify results with interval data and billing review.

For large energy users, the difference between “trying” and “getting results” is consistency. A program lasts when the business agrees on scope, site boundaries, and a short list of actions that can be repeated on any shift. Procurement gets clearer budget control. Operations gets guardrails that protect safety and uptime. Finance gets reporting that ties actions to the billing cycle.

A durable demand management program usually includes:

• A site and meter map, so scope is clear across the portfolio

• A protected-load list owned by site leadership

• A short checklist of approved actions per site, with owners and recovery steps

• Stop points written in plain language

• A review routine tied to the actual time window when actions were taken

Demand response can sit inside the same routine when a site is eligible and can deliver verified performance inside those boundaries. That adds settlement follow-through, so clean data and consistent documentation matter even more.

Rodan’s role is to help Minnesota teams set the rules up front, keep execution consistent across sites, and keep reporting aligned with what finance needs to see.

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.

Billing validation matters because demand management and demand response value gets questioned when invoices vary and the organization cannot reconcile why. SettlementIQ™ supports finance by strengthening validation and exception handling using interval data and a consistent review routine.

Billing friction often shows up as:

• Month-end variance that is hard to explain

• Disputes that take time and attention

• Difficulty tying outcomes to a specific window

• Mixed invoice formats across accounts in a portfolio

A finance-ready routine flags anomalies early, keeps documentation consistent, and reduces manual spreadsheet work. That supports confidence in the program and makes it easier to expand beyond a pilot.

SettlementIQ™ pairs well with window-based performance visibility. When the operational record and the billing record stay aligned, procurement can defend results more easily, and finance can close with fewer open questions.