PJM market operations
Indiana

Short event notice changes the operating model. A program that requires quick action will not work with approval chains that rely on meetings, or with playbooks that exist only in a spreadsheet no one can find. Indiana facilities with shift work, maintenance windows, and production schedules need a response model that is simple, repeatable, and staffed.

Operational planning should assume a defined notification path that reaches the right people on every shift, with redundancy. It should assume a written set of response steps that do not require technical judgment in the moment. It should assume defined authority to act, with clear limits. It should also assume performance verification, because a response that cannot be verified becomes hard to defend financially. Facilities often discover that communications and approvals are the weakest link, not equipment capability.

Rodan supports the execution side through Demand Response program operations, including event coordination and settlement follow-through. FacilityIQ supports real-time performance visibility by mapping event windows to interval load data across sites, which helps operators confirm delivery during the window. SettlementIQ supports finance by validating billing and reducing reconciliation friction. Indiana procurement leaders should evaluate readiness through practical questions: Who receives the call, who approves, who executes, and who confirms performance. A program that answers those questions clearly will hold up during the season.

Demand response revenue comes from reducing load during PJM called events or program-defined periods, based on the participation terms, the committed reduction, and verified performance. Procurement teams often like the revenue story, while plant teams focus on operational risk. A strong program balances both. The goal is not maximum reduction on paper. The goal is a reduction amount the site can deliver reliably during real conditions, including peak season staffing constraints, production variability, and equipment limitations.

Indiana facilities that succeed treat demand response like a controlled operating procedure. The program starts with interval data review and a realistic curtailment sizing exercise. Curtailment actions are documented, approved, and tested. Roles are assigned so night shifts and weekend coverage are not left to chance. Response steps are written at the level that a supervisor can execute without debate. The plan also includes stop points that protect safety, quality, and uptime. Those stop points protect procurement credibility as much as they protect the plant.

Rodan helps by managing the lifecycle work that consumes internal bandwidth. Demand Response support covers eligibility review, enrollment steps, curtailment planning, and event coordination. FacilityIQ provides a portfolio view that helps operators verify performance during event windows. SettlementIQ supports the finance side by validating billing and flagging discrepancies early. Revenue becomes procurement-friendly when it is predictable, documented, and reconcilable. That is the standard Indiana energy leaders should hold for PJM demand response participation.

PeakIQ supports peak cost control by giving operations a trigger before peak-sensitive hours. Procurement often knows peak exposure is a risk, but operations needs time and clarity to act. PeakIQ provides peak-risk notifications with a response window that can match the facility’s operating reality. That turns peak management into a planned routine rather than a reactive scramble.

Indiana sites often run multiple shifts, and they often have production constraints that limit what can move. PeakIQ supports planning by giving teams a consistent signal, so actions can be scheduled, staffed, and approved. The signal is only useful when it is paired with a playbook. That playbook defines what actions are allowed, the order they occur, and what conditions stop participation. Procurement benefits because peak management becomes auditable and repeatable. Finance benefits because avoided cost drivers are easier to explain.

PeakIQ also supports multi-site portfolios. One site might have flexible HVAC and utility loads. Another site might rely on process sequencing. A portfolio plan can assign different actions to different sites while using the same alert trigger. FacilityIQ complements this by showing performance by site during key windows. SettlementIQ complements it by validating the billing outcomes tied to the activity. Indiana procurement leaders should view PeakIQ as a risk-control tool that improves budget predictability while creating operational discipline that supports demand response participation.

Both matter, and they solve different problems. “PJM market operations” support is about program participation, event readiness, and verified performance under PJM rules. “Peak load management” work is about controlling peak-sensitive costs by planning load moves during the hours that drive exposure. Indiana procurement leaders usually need both, because cost risk and reliability readiness show up in different ways across the year.

A practical way to choose the starting point is to look at internal readiness. If the organization already has strong operational controls and clear authority to act, demand response participation can start sooner. If the organization has unclear approvals, or no routine for responding to peak-sensitive windows, PeakIQ and a peak playbook can build operational discipline that later supports demand response. Multi-site organizations often start with a portfolio view, then tighten playbooks site by site. FacilityIQ supports that by showing performance during key windows across sites.

The procurement outcome should be one operating motion that leadership can understand. Peak risk alerts trigger approved actions. Demand response events use the same governance model, with additional documentation tied to participation. SettlementIQ supports billing validation so finance can reconcile results. Indiana buyers should look for a vendor that supports the full operating loop: identify the trigger, execute safely, measure performance, and validate the dollars.

The most useful inputs are interval meter data, a recent utility bill, and a short description of operating constraints. Interval data supports curtailment sizing and performance planning. The utility bill supports rate and account review, and it helps identify peak-sensitive cost drivers. Operating constraints define what actions are off-limits, what staffing coverage exists, and what time windows are realistic.

A readiness review also benefits from a basic site inventory of controllable systems, plus any known policies that govern load changes. The goal is a practical plan that plant leaders approve. Procurement should expect the output to include a conservative curtailment estimate, a draft playbook outline, and a short list of readiness gaps that could affect performance or reporting. Multi-site organizations should expect a portfolio-level view that identifies which sites are best for a first rollout and which sites need more preparation.

Rodan can use FacilityIQ to support performance visibility once participation begins, and SettlementIQ to support billing validation. PeakIQ can support peak planning routines that make response more repeatable. The data request should feel reasonable. A demand response program that depends on perfect data rarely survives operational reality. The goal is a plan grounded in what the site can deliver reliably.

PJM market operations affects Indiana energy budgets in two ways: it influences how reliability is managed, and it influences the cost components that show up in supply pricing and pass-through charges. Procurement leaders feel the impact when a small number of high-load hours creates outsized cost exposure, and when leadership asks why forecasts missed the mark. Many Indiana organizations have multiple sites, multiple meters, and production schedules that do not pause for grid stress. That combination creates operational friction when energy costs spike and a response is needed quickly.

A procurement-ready approach connects three elements: participation, performance, and proof. Participation means choosing a demand response path that fits the site’s risk tolerance and operating limits. Performance means having a written playbook that defines what actions are allowed, who approves them, and what conditions stop participation. Proof means having reporting that finance can reconcile, and leadership can understand, without a long manual process. Rodan supports this as an operating program rather than a one-off initiative. Demand Response covers enrollment support, curtailment planning, event coordination, and settlement follow-through. FacilityIQ supports portfolio visibility so results are visible by site during event windows, not after the fact. SettlementIQ supports billing confidence so earned value is reflected accurately in financial reporting. That combination is what turns PJM market operations from a cost risk into a managed lever.

Success in year one is not measured by maximum curtailment. It is measured by repeatability, operational acceptance, and clean financial reporting. Indiana plants build confidence when response actions are safe, simple, and executed the same way across shifts. Procurement builds confidence when participation produces value that finance can reconcile without extended disputes. Leadership builds confidence when reporting is consistent across sites.

A strong first year usually starts with a conservative commitment and a clear playbook. Participation expands after the organization proves delivery during real conditions. FacilityIQ supports this by giving visibility into event-window performance by site, which helps refine playbooks and reduce drift. PeakIQ supports peak routines that improve operational readiness and help reduce exposure during high-impact hours. SettlementIQ supports billing validation so the dollars align with expectations.

Procurement leaders should expect a clear governance model: who approves actions, who executes steps, who verifies performance, and who reviews results. That governance should be documented and reinforced. A first year that delivers consistent performance and clean reporting gives the organization permission to scale. Scaling then becomes a business decision, not an operational gamble.

FacilityIQ provides a portfolio view that matters most when results vary by site. Indiana organizations often have multiple plants, warehouses, or campuses, each with different operations teams and different constraints. Performance tends to drift when playbooks are not monitored. A site may miss a step, or a staffing change may break the routine. FacilityIQ reduces drift by mapping event windows to interval consumption data at each site and surfacing underperformance quickly.

Procurement and finance gain a single source of truth for performance reporting. Plant leadership gains clarity on what happened during the event window without relying on anecdotal reports. Energy teams gain the ability to compare sites and improve playbooks based on actual data. That portfolio view is also valuable during leadership reviews. It supports straightforward reporting: participation status by site, delivery performance by window, and follow-up actions for sites that missed targets.

FacilityIQ also supports operational coaching. When a site underperforms, the question becomes actionable. Was the action not executed, was the action too small, was the load different that day, or was the meter data incomplete. That level of visibility helps fix the root cause instead of debating assumptions. For Indiana organizations that want predictable PJM participation and consistent peak management, FacilityIQ helps keep the program stable across shifts, sites, and seasons.

A curtailment boundary is a written definition of what loads are available, what loads are protected, and what conditions stop an action. Indiana manufacturing sites benefit from clear boundaries because production risk is not theoretical. A poor curtailment choice can create scrap, downtime, or safety issues, and it can damage support for energy programs across the organization.

A useful boundary process starts with operations, maintenance, and EHS at the table. Identify critical loads that must never be touched. Identify flexible loads that can be adjusted for a limited window with minimal impact. Define time limits, ramp rates, and recovery steps. Define triggers that stop the plan, including safety concerns, process instability, customer commitments, and staffing limitations. Tie the plan to shift schedules, because an action that works on day shift may not work on night shift. Build a short checklist that a supervisor can follow. The checklist should include who approves participation, who executes the steps, and who confirms the load drop.

Procurement teams should require this boundary work before committing to a reduction size. A conservative commitment that is delivered consistently produces better long-term value than an aggressive commitment that fails under real conditions. FacilityIQ supports this discipline by showing what happened during event windows at each site, which helps refine boundaries over time. A boundary process that is written, tested, and measured is what keeps demand response aligned with Indiana manufacturing uptime.

PeakIQ supports DSM by giving operations lead time to act during peak-risk windows, using a response window your organization agrees to in advance.

Alerting is not the strategy, but it makes the strategy usable. Without a reliable trigger, sites either react too late, or they overreact too often. PeakIQ is positioned as an early-warning layer that supports disciplined execution, not guesswork.

A practical PeakIQ routine includes:

• Recipient design: primary and backup contacts by site, including off-hours coverage.

• Response window selection: aligned to approvals, staffing, and operational reality.

• Alert-to-action mapping: each alert triggers a defined subset of playbook actions.

• Action logging: a simple record of what was done and when.

• Post-window review: confirm performance using interval data and update the playbook.

For procurement, PeakIQ improves predictability because peak response becomes consistent and measurable. For operations, it reduces disruption because actions are planned and pre-approved. For finance, it improves reconciliation because actions are tied to clear windows that can be reviewed and validated.

PeakIQ works best when it is paired with a playbook that is short, approved, and executable on any shift.

FacilityIQ helps multi-site DSM by making performance visible during the window across all sites, using a consistent view that supports governance and fast issue detection.

Multi-site programs often fail due to inconsistency. One site executes well, another site misses a step, and the portfolio outcome becomes difficult to explain. FacilityIQ is positioned to reduce that gap by keeping performance tied to the same time window across sites, rather than relying on post-event spreadsheets.

What portfolio leaders typically need:

• A single view of performance across sites during key windows.

• Early detection of underperformance while corrective action is still possible.

• A consistent reporting format for procurement and finance.

• An operating record that supports playbook updates.

FacilityIQ also supports practical troubleshooting. When a site underperforms, the team can focus on the real causes: staffing coverage, controls behavior, process constraints, or data issues. That reduces internal debate and improves the playbook over time.

For Indiana portfolios, the value is not just visibility. It is standardization. Standardization is what makes DSM repeatable and scalable without increasing administrative burden.

DSM is the broader strategy. Demand response is one way to monetize part of that strategy, when a site is eligible and can deliver verified performance.

Think of DSM as the operating system: you identify peak risk, define allowed actions, assign owners, and build a routine the site can run safely. Demand response is an application: you enroll in a program and get paid to reduce load during specific event windows, under defined rules.

For Indiana decision-makers, the difference matters because:

• DSM can start immediately as an internal operating discipline, even before any program enrollment.

• Demand response adds obligations including measurement, verification, and settlement processes.

• DSM reduces risk by making execution repeatable, which improves confidence if demand response is added later.

A clean way to manage both is to standardize the operating fundamentals:

• A protected-load list, approved by operations and safety.

• A short action list that works across shifts.

• A clear go or no-go decision owner, with backups.

• A post-window review routine that improves the playbook over time.

Then, if demand response participation is a fit, the organization is not starting from zero. It already has the governance, documentation, and execution habit that keeps performance stable and reporting credible.

A DSM playbook is a short, written set of approved actions that your site can execute during peak-risk windows without compromising safety, quality, or uptime.

The best playbooks read like an SOP, not a brainstorm. Each action includes an owner, timing, a recovery step, and a stop point. Stop points are the guardrails that keep the program safe and credible. They should be specific, easy to interpret, and authorized by the right stakeholders.

A practical playbook structure includes:

• Tier 1 actions: always allowed, low-risk actions that can be executed quickly.

• Tier 2 actions: actions that require explicit approval, with a named approver.

• Off-limits list: actions the site will not take due to operational risk.

• Stop points: conditions that end participation immediately.

• Recovery steps: how the site returns to normal operation safely.

To make this shift-ready, the playbook should also include:

• Primary and backup contacts by shift.

• A single decision owner for the event window.

• A simple method to log actions taken.

A playbook that depends on one expert being on shift is not scalable. The goal is reliable execution that can withstand staffing changes and production variability.

Demand side management in Indiana is a planned approach to reducing or shifting electricity use during peak periods to manage peak-related costs and support grid reliability.

For a large facility, DSM is not a one-time project. It is an operating discipline that answers three practical questions: Which hours matter most, what actions are allowed on-site, and how will the organization prove the result to finance. The “prove it” part matters because DSM only survives budget cycles when the reporting is clean and repeatable.

A procurement-ready DSM program typically includes:

• Scope: which meters and sites are in scope, and which are not.

• A playbook: a short list of approved actions that are safe, reversible, and shift-ready.

• Stop points: conditions that end participation immediately, written in plain language.

• Measurement: interval data review tied to the actual time window when actions were taken.

• Finance validation: a routine to reconcile outcomes without spreadsheet rebuilding.

DSM often overlaps with demand response, where eligible. In that case, DSM becomes the operating backbone that supports performance during event windows. The key is staying realistic. A smaller action set that the site can execute consistently is more valuable than an aggressive target that breaks down on nights, weekends, or high-production days.

Rodan’s role is to help you put structure around this so the plan works across procurement, operations, and finance, without introducing operational risk.

The strongest DSM 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 site type, equipment, and constraints, so the best practice is to start with operating boundaries and interval patterns, then select actions that fit. In many large facilities, teams evaluate a mix of supporting systems and scheduling levers.

Common categories organizations often review include:

• HVAC and ventilation adjustments: within approved temperature and air quality limits.

• Compressed air optimization: pressure bands and staged operation within equipment limits.

• Pumps, fans, and supporting systems: sequencing and scheduling changes that do not destabilize processes.

• Process scheduling moves: shifting discretionary steps away from peak-risk windows.

• Deferrable loads: timing changes for loads that can move without operational risk.

Procurement leaders should focus less on the category and more on the controls:

• Is there a protected-load list?

• Are stop points written and enforceable?

• Is there a recovery step to avoid downstream issues?

• Can the site execute the same actions on any shift?

DSM works when the action list is small, approved, and repeatable. That is what protects operations and creates results that finance can reconcile.

They should expect a consistent, auditable link between three things: the window when actions were taken, the interval data that shows performance, and the billing outcome that finance reconciles.

If reporting is vague, DSM becomes hard to defend. If reporting is structured, DSM becomes a controllable lever that procurement can include in planning and that finance can trust during close.

A finance-ready DSM reporting package typically includes:

• Window-based reporting: performance tied to specific time windows, not weekly averages.

• Site-level visibility: results by meter and by site, especially for multi-site portfolios.

• Exception handling: a way to flag anomalies early and document root cause.

• Attribution discipline: a consistent approach for explaining outcomes without hand-waving.

Procurement should also look for governance signals:

• Was the playbook followed?

• Were stop points triggered?

• Was the decision owner available?

• Were actions logged, and were recovery steps completed?

These details matter because they explain performance variance in a way leadership understands. They also prevent the “we think it worked” problem that often kills programs after one season.

The most important reporting rule is simple: if finance cannot reconcile it, it will not scale.