Energy demand management North Dakota

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 late or when the decision owner is unavailable. A consistent alert-and-action cadence reduces that variability. A practical setup includes:

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

• A response window that matches staffing and approval needs

• A short checklist tied to alert timing

• A simple action log for post-window review

Procurement benefits because peak response becomes easier to report. Operations benefits because the team has time to coordinate and stay inside safe limits. Finance benefits because actions are tied to defined windows that can be reviewed against interval data.

PeakIQ works best when it activates a routine that has already been approved and tested against site constraints. Rodan helps teams set that routine so alerts lead to consistent action, not noise.

This page is intended for North Dakota sites with MISO exposure. Portfolios can vary by service territory and account structure, so the safest approach is to confirm exposure by meter and bill, not by state name.

Mixed exposure creates two common problems inside large organizations. Rollouts get messy when sites are treated the same even though their participation paths differ. Reporting gets noisy when in-scope and out-of-scope sites are blended in the same dashboard or budget narrative. Both issues can be avoided with a quick scoping step.

A clean start uses:

• Utility bills and supplier invoices for each site

• Meter identifiers tied to the physical location

• Interval data access details, or the path to obtain it

• Site schedules and constraints that affect flexibility

From there, sites can be grouped into: those with a realistic participation path, those where an internal peak routine still helps, and those that should stay out of scope for now due to process limits.

Rodan supports this by starting with a meter-level review and producing a clear scope map, a site checklist, and a reporting routine that keeps operations and finance aligned. That keeps the program focused and makes results easier to defend.

Energy demand management helps control peak-driven cost exposure, where a small set of high-demand intervals can create outsized swings in monthly bills and annual budgeting. It also reduces variance, which is often what procurement and finance care about most.

Peak exposure tends to show up when load ramps quickly or multiple systems stack demand at once. That can be driven by operating schedules, equipment staging, and weather-related load. Demand management treats those windows as planned operating periods rather than surprises.

A practical cost-control routine includes:

• Mapping when the site peaks and what triggers it

• Selecting safe actions that can be repeated across shifts

• Writing stop points that protect operations

• Reviewing interval data for the same time window when actions were taken

• Tying that record to billing review

Finance confidence depends on verification. If reporting relies on assumptions or informal notes, the program becomes harder to defend. A clean record of the window, the action, and the measured change makes reviews faster and reduces rework.

Rodan supports this by keeping the routine site-specific, keeping roles clear, and keeping performance review tied to the same windows finance will ask about later.

A site checklist is a short, written list of approved actions the facility can take during peak-risk windows, with owners, timing, stop points, and recovery steps. It should work on any shift.

A practical structure uses three layers:

• Always-allowed actions that carry low operational risk

• Approval-required actions with a named approver and backup

• Off-limits actions the site will not take

Stop points are the guardrails. They are written in operational terms and tied to the site’s limits. They may include safety alarms, process stability concerns, quality thresholds, staffing gaps, or equipment constraints. When a stop point is met, participation ends, and the site returns to normal operation.

A checklist is also a governance tool:

• Operations uses it to keep actions safe and consistent

• Procurement uses it to show leadership that actions are controlled

• Finance uses it to connect actions to measurable outcomes in interval data

A short post-window review keeps the checklist honest. If a step does not move demand, it gets revised. If a step causes operational friction, it gets adjusted before the next window.

Rodan helps North Dakota teams build these checklists around real constraints and keep them usable across shifts and staffing changes.

FacilityIQ adds window-based visibility across sites, so portfolio teams can see performance during the window and address issues quickly. Multi-site programs lose momentum when a few sites drift and reporting becomes inconsistent.

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

Window-based visibility also shortens troubleshooting. When a site underperforms, the team can focus on concrete causes: staffing coverage, constraints on that day, controls behavior, or data gaps. That keeps discussions action-oriented.

Sites do not need identical actions. They need the same cadence: alert, execute within limits, verify performance, and review outcomes. FacilityIQ supports that cadence by keeping performance tied to the time window when actions were taken.

At a minimum, Rodan needs a recent utility bill, interval data access details, and basic site limits for each location under review. That information supports scope, feasibility, and verification.

A practical starter set includes:

• Utility bills and supplier invoices

• Meter identifiers tied to each physical site

• 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 limits, and uptime

• Names of operations approvers and finance reviewers

Meter mapping is the early win. It prevents wasted effort and keeps reporting clean. Interval data supports two things: identifying peak drivers and verifying results in the same window when actions were taken. Finance needs that consistency to reconcile outcomes without manual rebuilding.

Rodan uses the intake to deliver a decision package: which sites are candidates, what actions are realistic, what stop points apply, and how results will be reviewed. Demand response fit is screened only where eligibility exists and site limits support verified performance.

Demand management gets harder when staffing is lean, sites are spread out, and peak conditions show up quickly. Programs that rely on manual coordination, long approval chains, or one “energy person” tend to fade.

A North Dakota-friendly approach favors simplicity:

• A short checklist that a supervisor can run without debate

• Owners and backups defined for nights, weekends, and holidays

• Stop points that protect safety, quality, comfort limits, and uptime

• Recovery steps that bring the site back to steady operation

The goal is repeatability. A smaller action set executed consistently is easier to manage and easier to explain than an aggressive routine that only works under perfect conditions. Repeatability also improves reporting. Finance reviews become faster when actions are tied to defined windows and backed by interval data.

Weather can add pressure. Winter cold snaps and summer heat can push load higher, and response windows can tighten. That is where a written routine helps. The site knows what it will do, what it will not do, and who has authority to stop participation.

Rodan supports this style of program by helping write the checklist with site leaders, setting role coverage, and keeping performance review tied to the same time windows your team acted on.