Peak load management Montana

Demand response is a paid participation path where eligible sites reduce load during defined event windows and performance is measured. Peak load management is the broader operating discipline that prepares the site to act during high-impact hours and to verify results with data.

Demand response works best when the peak routine is already stable. A stable routine means:

• Protected loads and off-limits actions are documented.

• A short checklist exists and is executed consistently.

• One decision owner is defined for event windows, with backups.

• Interval data is available and mapped correctly to the participating meter.

• Actions are logged so post-event review is based on a record, not memory.

Demand response adds settlement follow-through, which increases the need for clean documentation. Finance will ask what happened, why, and how it shows up in the billing cycle. If the routine is informal, that conversation turns into rework. If the routine is structured, it becomes a quick review.

Participation should be sized to what the site can deliver safely. Montana sites with lean staffing are usually better served by conservative commitments that are delivered consistently. Reliability is the currency that keeps internal support strong.

Rodan supports demand response where eligibility exists, while keeping the peak routine grounded in site limits and clear reporting.

PeakIQ™ helps by giving operations notice ahead of peak-risk windows so the site can execute approved steps without last-minute coordination. For spread-out portfolios, that notice helps standardize cadence across sites.

A practical setup includes:

• Primary and backup recipients per site, including off-hours coverage.

• A response window that matches staffing and approvals.

• A short checklist tied to alert timing.

• A simple action log, so the post-window review stays factual.

PeakIQ™ is most useful when it activates an approved routine. If a site has no checklist, alerting creates noise. If the checklist is clear, alerting creates consistency.

Procurement benefits because peak response becomes easier to report and easier to defend. Operations benefits because the team has time to coordinate and stay inside safe limits. Finance benefits because actions can be tied to a defined time window for review against interval data.

Montana portfolios often need that structure because sites are not always staffed the same way and because travel time makes centralized coordination hard. A consistent alert-and-action routine helps keep the program stable without putting extra burden on site teams.

Peak actions are site-specific. The safe way to approach them is to focus on reversible steps that are already familiar to operations and to write stop points that protect the business. The checklist should be short and clear.

Many large facilities review action categories that may include HVAC staging, setpoint adjustments within approved ranges, compressed air pressure bands, pump and fan sequencing, process scheduling moves for discretionary steps, and staggered starts to reduce spikes. The exact list depends on equipment, controls, and what the site considers protected.

Safety comes from governance:

• A protected-load list and an off-limits list.

• Stop points tied to safety alarms, process stability, quality limits, and staffing coverage.

• Approval rules that match the site’s real decision paths.

• Recovery steps that avoid downstream operational issues after the window.

Repeatability matters. If actions change based on who is on shift, performance will drift and reporting will lose credibility. A smaller list executed consistently usually beats a larger list executed inconsistently.

A short post-window review using interval data helps keep the checklist honest. If a step does not move demand, it should be revised or removed. If a step creates operational friction, it should be adjusted before the next window.

Rodan supports customers by helping define safe actions, document stop points, and keep the routine steady over time.

FacilityIQ™ supports portfolio management by giving a consistent view of performance across participating sites during the time window that matters. Portfolios lose momentum when one or two sites drift and the program’s results look inconsistent.

A portfolio view helps teams:

• Compare sites using the same timing and definitions.

• Spot underperformance early and address it quickly.

• Keep a shared record for procurement, operations, and finance.

• Focus coaching and checklist updates where they matter most.

FacilityIQ™ also supports practical troubleshooting. When a site underperforms, the team can look at concrete causes: staffing coverage, constraints on that day, controls behavior, or data gaps. That keeps discussions short and focused.

For Montana, where sites can be widely distributed, portfolio visibility reduces the need for constant site-by-site calls. It also makes monthly review easier for finance because the operational record is consistent across locations.

FacilityIQ™ does not replace site ownership. It supports site ownership with visibility that makes the program easier to manage and easier to improve.

A peak routine is a short checklist of approved actions that can be executed quickly, with clear ownership and clear stop points. Lean staffing changes the design. The routine has to work when the “energy person” is not on shift, and it has to work when travel time between sites is not practical.

A Montana-ready routine often includes:

• One decision owner per site, plus backups for nights and weekends.

• A short list of low-risk steps that do not require extra approvals.

• A second list of steps that require approval, with the approver named.

• Stop points tied to safety, process stability, quality limits, comfort limits, and equipment constraints.

• Recovery steps that return the site to steady operation after the window.

The point is not maximum reduction. The point is repeatability. A smaller reduction that happens every time is usually more valuable than a large target that only works under perfect conditions. It also protects trust with site leadership, which is hard to regain once lost.

A good routine also includes measurement. A short post-window check using interval data confirms whether the actions moved demand during the window. That keeps the program grounded in facts and helps update the checklist when conditions change.

Rodan helps build the routine with site teams, then supports the cadence so it stays workable across shifts and across a spread-out portfolio.

Peak load management Montana teams use is the practice of reducing demand during the limited set of hours that tend to drive the biggest cost swings, then verifying results with interval data and a consistent finance review. The work is practical: identify which meters matter, agree on what the site can do safely, and run the same steps the same way each time.

Montana also brings a portfolio reality that changes how peak programs succeed. Many organizations have sites far apart, with different operators and different utility relationships. A peak routine that depends on one person watching conditions all day does not last. A routine that depends on a complicated approval chain also does not last. A program that survives is built around clarity.

That means:

• A clear list of participating meters, owned by procurement and finance.

• A protected-load list owned by site leadership.

• A short action checklist that a supervisor can execute on any shift.

• Stop points that end participation immediately when site limits are reached.

• A simple log of actions taken, tied to the same time window used for interval review.

Demand response can be added where eligibility exists and performance can be verified, but the same discipline still applies. A program is only as good as its repeatability. Rodan’s role is to help you build a peak routine that fits real staffing, real schedules, and real constraints, then keep the reporting clear enough that leadership can trust it month after month.

Procurement should look for clarity on scope, operational feasibility, and proof. A peak program fails when any of those three are missing.

Scope means a list of participating meters and sites, with ownership. Operational feasibility means the site has approved actions and stop points. Proof means the organization has a routine to verify performance and tie it to billing review.

A procurement-ready package usually includes:

• A meter map showing which sites are participating and why.

• A protected-load list, approved by site leadership.

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

• Stop points written in plain language.

• A reporting cadence that finance agrees to, with clear exception handling.

Procurement should also look for role coverage. Who can authorize actions during off-hours? Who logs actions taken? Who reviews performance afterward? Montana portfolios can be spread out, so relying on one person to coordinate every site is not realistic.

A good program also sets expectations. It does not promise a universal result across every site. It aims for repeatable execution at participating meters, then expands only when the routine is stable.

Rodan’s approach supports this by confirming eligibility by meter, building site checklists that match constraints, and keeping performance review connected to billing review.

You should expect clarity on three items: which meters are candidates, what actions are realistic by site, and how results will be verified. The output should be usable for procurement, operations, and finance.

Inputs that help:

• Recent utility bills and supplier invoices for sites under review.

• Meter IDs 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 operations approvers and finance reviewers.

Outputs you should receive:

• A prioritized list of participating meters based on exposure and 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 routine that keeps window-based performance tied to billing review.

A staged rollout is normal. Start with the sites that have clear exposure and realistic flexibility. Expand only after the routine is stable. That approach protects operations, keeps reporting clean, and supports long-term adoption.

Billing validation matters because peak program value is often questioned when invoices vary and the organization cannot reconcile why. SettlementIQ™ supports finance with a structured way to review costs and exceptions using interval data and a consistent review habit.

Billing friction tends to show up as month-end variance, disputes that take time, difficulty tying outcomes to a specific time window, and mixed invoice formats across a portfolio. A program can be executed well and still lose internal support if finance cannot reconcile outcomes cleanly.

A finance-ready routine should:

• Tie performance review to the same time windows used for operational logs.

• Flag anomalies early in the billing cycle, not weeks later.

• Keep documentation consistent across sites and accounts.

• Reduce manual spreadsheet rebuilding.

SettlementIQ™ supports that discipline. It pairs well with window-based performance review because the operational record and the billing record stay aligned. That alignment is what keeps procurement confident and keeps finance comfortable.

For Montana portfolios, this helps keep reporting clean across sites that may have different invoices and different internal owners. It reduces noise, reduces back-and-forth, and supports a steady monthly review.

“Partial” signals that not every Montana site will follow the same participation path. Eligibility can vary by service territory and meter. Treating the whole state as one uniform program creates wasted effort and messy reporting.

This typically shows up in two places inside a large organization. One is rollout: teams build training and checklists, then learn certain sites were never candidates. The other is reporting: results get blended across sites that do not share the same rules, so the story becomes hard to defend.

A clean approach is straightforward:

• Start with bills and meter IDs for each site you want to include.

• Separate meters into groups: eligible participation paths, peak-only operating routines, and out-of-scope for now.

• Build checklists only where the site has real flexibility and a reason to act.

• Keep reporting aligned to those groups so finance is not reviewing blended noise.

Peak load management can still be useful even when a site is not eligible for a specific participation path. Some sites benefit from an internal peak routine that reduces demand spikes and improves predictability. That becomes a local operating decision, not a market decision.

Rodan supports this by confirming eligibility at the meter level, then building site routines around actual constraints. The outcome is a program that is easier to run and easier to explain, which is what “partial” footprints require.