Energy demand management South Dakota

Stop points and approvals work when they are written down, simple to interpret, and backed by site leadership. The goal is to remove ambiguity during a tight window.

A practical model usually includes:

• Always-allowed actions that carry low operational risk

• Approval-required actions with a named approver and backup

• Off-limits actions that the site will not take

Stop points should reflect the site’s real limits. They may be tied to safety alarms, process stability concerns, quality thresholds, staffing gaps, or equipment constraints. When a stop point is reached, the routine stops and the site returns to normal operation.

Shift coverage matters as much as the document. A site should have:

• One decision owner per shift

• Backup coverage for weekends and holidays

• A simple log of actions taken and any stop points triggered

A short post-window review helps keep rules relevant. If a step causes operational friction, it gets refined. If an approval step slows response too much, the checklist is adjusted so the site has enough low-risk actions it can execute without delays.

Rodan helps by facilitating the boundary-setting discussion, capturing stop points in plain language, and keeping the routine workable across shifts.

PeakIQ™ supports demand management by giving operations notice ahead of peak-risk windows so the site can execute approved steps without last-minute coordination.

Consistency is the value. Without a reliable trigger, sites either react too late or react too often. A good alert-driven routine 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 and defend. Operations benefits because the team has time to coordinate and stay within safe limits. Finance benefits because actions are tied to defined windows that can be reviewed against interval data and invoices.

PeakIQ™ works best when it activates an approved checklist. If the checklist is unclear, alerting becomes noise. If the checklist is clear, alerting supports repeatable execution.

Rodan helps teams set up the routine so alerts lead to consistent action, clear documentation, and a review habit that keeps the program steady.

Demand management is the broader routine your team runs to control peak exposure. Demand response is a paid participation path where eligible sites reduce load during defined event windows and performance is measured.

Demand management can start with internal goals: reduce peaks, reduce variance, and make peak days predictable. Demand response adds program requirements, event timing, and settlement follow-through. A demand response program tends to run better when demand management basics already exist.

A clean way to separate them inside a business:

• Demand management: the site checklist, approvals, stop points, and review cadence

• Demand response: the program participation path, event execution, and performance verification

Demand response becomes a better fit when:

• The site can reduce load within its approved boundaries

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

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

• The site can log actions so review is based on a record, not memory

Even when demand response is not a fit for a specific site, demand management can still reduce peak-driven variance and help with forecasting. That value often shows up as fewer billing surprises and fewer internal escalations.

Rodan supports both paths by keeping the routine grounded in site limits and by keeping performance review tied to the same windows finance will ask about later.

A peak day routine is a short checklist of approved actions that can be executed quickly, with clear ownership and clear stop points. It is built to work during busy operations, with staffing coverage that matches reality.

A site-level routine usually includes:

• A short list of low-risk actions that can be executed without extra approvals

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

• An off-limits list that protects safety, quality, comfort limits, and uptime

• Stop points that end participation immediately

• Recovery steps that bring the site back to normal operation after the window

• A simple action log that records what happened

The routine should not depend on the “energy person” being present. It needs owners by shift, plus backup contacts for nights, weekends, and holidays. That is what keeps performance consistent.

Review is part of the routine. A short post-window check, using interval data for the same window, confirms whether the actions moved demand. If a step does not move demand, it gets revised or removed. If a step creates operational friction, it gets adjusted before the next peak window.

Rodan helps teams build these checklists with site leaders, document stop points, and set a review cadence that makes results easy to defend in finance reviews.

FacilityIQ™ adds window-based visibility across sites, helping portfolio teams 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:

• A consistent 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 shortens troubleshooting. When a site underperforms, the team can focus on practical causes: staffing coverage, constraints on that day, controls behavior, or data gaps. That keeps conversations short and 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 window when actions were taken.

For South Dakota portfolios, this helps leadership get a consistent story across sites, even when operations differ from location to location.

Rodan needs enough information to confirm scope, document site boundaries, and identify realistic actions. The goal is a decision package that procurement, operations, and finance can use.

A useful starter set includes:

• Recent utility bills and supplier invoices for each site under review

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

• Names of the operations approver and finance reviewer

Meter mapping is often the first win. It prevents wasted effort and keeps reporting clean. Interval data supports two tasks: identifying peak drivers and verifying what happened during the window when actions were taken.

Rodan uses this intake to deliver:

• A scoped list of participating meters and sites

• A draft checklist per site with owners, stop points, and recovery steps

• A screening view of demand response fit where eligibility exists

• A window-based review routine tied to billing checks

That approach keeps the work practical for site teams and reviewable for finance.

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

This works best when it is treated like an operating program, not a one-off effort. Most large sites have a small set of hours that create the biggest swings in cost and attention. Demand management targets those hours with approved actions that stay inside site limits.

A program that holds up in procurement and finance reviews usually has:

• A clear list of participating meters and sites

• A protected-load list owned by site leadership

• A short checklist of approved actions, with owners assigned

• Stop points written in plain language, so the site knows when to stop

• Recovery steps, so the facility returns to steady operation safely

• A simple review habit that ties the action window to interval performance and invoice review

Demand response can sit inside the same routine where a site is eligible and can deliver verified performance within those limits. When demand response is added, documentation and follow-through become more important, since finance will want a clear record of what happened and how it reconciles.

Rodan helps South Dakota teams set boundaries early, keep the checklist workable on any shift, and keep the reporting clear enough that the program survives budget cycles.

Procurement should expect clear scope, realistic actions by site, and a review routine that finance can use. Rollout usually starts with the sites that have clear exposure and workable flexibility, then expands once execution is steady.

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, stop points, and recovery steps

• A screening view of demand response fit where eligibility exists

• A window-based review cadence tied to billing checks

Success is repeatable execution and clean reporting. That is what keeps demand management funded, adopted, and useful across seasons.

A good fit is any large site with controllable load that can be adjusted for short windows without putting safety, quality, comfort limits, or uptime at risk. Industry matters less than operating flexibility.

Fit often comes down to three practical questions:

• Can the site reduce demand for a defined window without disrupting critical operations?

• Can the site repeat the same actions across shifts and staffing changes?

• Can the organization verify results with interval data and a consistent billing review?

Sites with large motors, pumps, ventilation systems, refrigeration, compressed air, or process-driven ramps often have levers to pull, provided the site team is comfortable with the boundaries. Multi-site portfolios can also improve fit by spreading actions across several facilities rather than leaning on one site.

A staged rollout usually works best. Start with the sites that have clear peak exposure, stable operations, and leadership buy-in. Once the routine is steady, add sites one at a time.

Rodan supports this by starting with a meter and bill review, confirming what is realistic at each site, and producing a short checklist with stop points and owners. That keeps the rollout focused and keeps reporting clean.

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

Billing friction often shows up as month-end variance, disputes that take time, and difficulty tying outcomes to a specific window. A finance-ready routine flags anomalies early, keeps documentation consistent, and reduces manual spreadsheet work. That supports confidence and makes it easier to expand beyond a pilot.

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

For portfolios, this also helps standardize review across accounts that may have different invoice formats. Finance gets a consistent process, and operations gets fewer repeated questions after the fact.

Rodan’s role is to keep the review cadence steady and to keep the reporting aligned to the same windows your team acted on.