Site infrastructure conditions don't wait for someone to be watching a dashboard. Whether it's PSI dropping on a gas line, temperature climbing past a safe threshold, or any other Modbus-readable metric moving outside its normal range, your site often needs to respond immediately — before conditions escalate into equipment damage, unplanned shutdowns, safety issues, or consuming more energy than planned. Managing this manually means someone has to monitor the right data at the right moment, every hour of every day, and then adjust setpoints across the fleet fast enough — which isn't realistic at remote or unstaffed sites, where a delayed response can turn a minor fluctuation into a costly one.

Infrastructure-Initiated Dispatches solve this by letting you connect any Modbus device to Foreman and creating setpoint dispatches — single-step or multi-step — that will automatically occur based on data from the device. As your monitored metric moves, Foreman adjusts your fleet's setpoint accordingly, in real time and without anyone needing to intervene. For example, as site PSI drops or your site is approaching your peak consumptions, you can define what setpoint your site should drop to in response — automatically.

How It Works

1. Foreman monitors your chosen infrastructure condition through a connected Modbus device.
2. You configure the setpoint dispatch — either a single-step change or a multi-step sequence — that should occur as the monitored value crosses your defined threshold(s), using ladder logic: one or more threshold/setpoint pairs (rungs) evaluated in order from top to bottom. This lets you define multiple response levels as conditions change — for example, a moderate response at the first threshold, and a more aggressive one if conditions continue to worsen.
3. To prevent false triggers from momentary fluctuations, you set a debounce — the number of consecutive telemetry windows (typically ~1 minute each) that must meet or fall below the threshold before Foreman makes a change. Debounce applies not just to the initial trigger, but to every adjustment step along the way.
4. When the debounce condition is met, Foreman automatically dispatches the configured setpoint change to your fleet.
5. If none of the rung conditions are met, the dispatch automatically ends — no manual step required to turn it off.

How To Initiate

1. Navigate to Power from the left-hand menu, then select Command Center.

2. Click Add Event, then Add Dispatch to open the dispatch form.

   

3. Fill in the following:
   • Name (required)
   • Reason (optional)
   • Power Target — select Setpoint (required)
   • Schedule — select Infrastructure Initiated (this option appears once Setpoint is selected as the Power Target)
4. Once Infrastructure Initiated is selected, the Infrastructure Trigger section expands, where you'll configure:
   • Trigger Device — the Modbus device you want to monitor. 
   • Metric — the specific value to track, shown with its live current reading
   • Condition — whether the dispatch should trigger as the metric rises (Ascending ≥) or falls (Descending ≤)
   • Unit — W, kW, or MW
   • Debounce — how many consecutive telemetry windows must meet the condition before Foreman acts

   • Setpoint Ladder — your threshold/setpoint rungs, evaluated top to bottom

     

5. Click Save to activate the dispatch. Note: There is a new table for Infrastructure Initiated Dispatches that will appear when one is created. These dispatches will appear in Standby while they are waiting for the condition to occur. If there is an active dispatch, one will appear in the Events table with the status of active. The dispatch in the Infrastructure table will also show status as active.

   

Manage Dispatches

Similar to other events created, you have the ability to edit and delete Infrastructure Initiated Dispatches, but it MUST be done via the template in the Infrastructure Initiated table. Click into the ellipses menu to select either Edit or Delete.

Key Benefits & Things to Know

• Responds to infrastructure conditions in real time, without manual monitoring.
• Supports single-step and multi-step setpoint dispatches, with multi-rung ladders for escalating (or de-escalating) responses.
• Debounce logic prevents unnecessary setpoint changes from brief, momentary fluctuations.
• Works with any Modbus-compatible device — not limited to a specific sensor type.
• Dispatches automatically terminate when conditions no longer meet any rung's trigger — no manual cleanup needed.
• Infrastructure-initiated dispatches appear in their own Infrastructure Initiated table on the Command Center, separate from your standard Events table, so you can track them independently.
• Works 24/7 for remote and unstaffed sites, with no manual intervention required once configured — it runs continuously in an always-on/listening mode after setup. Should not be combined with Buffered Dispatches, but can be used alongside PRP depending on the situation.

For questions about configuring your Modbus device or connecting infrastructure data, contact your CSM or leave a comment below. For technical issues connecting your device, reach out to Foreman support.