Predictive Scheduling Rule¶
Scheduling rule — instantiates Predictive Precommitment Correction
Sets the timing and sequence of a planned action from a forecast, so its effect lands inside the target envelope when the disturbance arrives — the schedule is pre-shaped, not reacted into.
A Predictive Scheduling Rule takes a known, planned action and uses a forecast to decide when and in what order to execute it, so that its effect lands on target at the moment the disturbance hits rather than lagging behind it. Its defining move is treating timing itself as the adjustable control variable: the action is not changed in kind, only shifted earlier, later, or resequenced, so a slow-acting effect is set in motion in time to be ready. Unlike a rule that waits for a signal to trip, this one is a standing, forecast-driven timetable — computed ahead and committed as a plan, then revised as the forecast updates. It pre-shapes the schedule so the system is never caught reacting at the moment of peak load, when reaction is too slow to keep the outcome inside its tolerance.
Example¶
A facilities manager runs a large office tower whose comfort target is a temperature band occupants won't notice. Tomorrow's forecast is unambiguous: 35 °C, full occupancy, and an electricity price that peaks 2–6 p.m. A purely reactive air-conditioning loop would fight the heat at 3 p.m., at the worst price, and still overshoot the comfort band because the building's thermal mass responds slowly. So the manager applies a predictive scheduling rule: pre-cool the building's thermal mass overnight and through the early morning — shifting the cooling earlier in the sequence — so the structure enters the afternoon already cold and coasts through the peak within the comfort band on stored coolth.
Nothing about the action changed — it is still "run the chillers" — only its timing. The forecast of heat, occupancy, and price sets when the cooling happens; the comfort band defines what "landing on target" means; and if tomorrow's forecast softens overnight, the schedule is revised down rather than committed blindly. The building stays comfortable through the peak without the reactive overshoot, and off the most expensive hours.
How it works¶
What distinguishes it from reacting-when-the-signal-trips is that it computes and commits a timetable ahead of time:
- Read the forecast. Take the predicted disturbance — heat, demand, load — and its timing as the driver of the schedule.
- Fix the target envelope. Define the tolerance band the action's effect must stay inside, which sets how much pre-shaping is needed.
- Solve for timing and sequence. Choose when and in what order to run the planned action so its (possibly slow) effect is in place when the disturbance arrives.
- Commit ahead, revise on update. Lay the schedule down as a plan, and re-shape it as the forecast refreshes rather than freezing the first version.
Tuning parameters¶
- Look-ahead horizon — how far ahead the schedule is planned. Longer anticipates slow effects but leans on a forecast that degrades with distance.
- Pre-shaping aggressiveness — how far the action is shifted (how deep the pre-cool, how early the start). More aggressive guarantees the target is met but spends more when the forecast is wrong.
- Re-schedule cadence — how often the plan is revised as the forecast updates. Frequent revision tracks change but can churn the schedule.
- Sequence granularity — how finely the action's order and timing can be tuned; finer control lands the effect more precisely at more planning cost.
- Envelope width — how tight the target band is. A tight band demands more pre-shaping and precision; a loose one tolerates cruder scheduling.
When it helps, and when it misleads¶
Its strength is defeating the lag of a slow-acting effect: by starting the action early enough, the system is ready when the disturbance lands instead of chasing it, avoiding the overshoot and oscillation a reactive loop suffers against a known incoming load. This is the logic behind pre-cooling and other anticipatory demand-shaping — spend ahead, on a schedule, to avoid a worse reactive cost later.[n1]
Its failure mode is the wrong forecast: pre-shape hard for a heat wave that doesn't come and the pre-cooling is wasted energy; pre-shape for demand that arrives differently and the schedule is mistimed. A schedule committed and never revised is the classic misuse — the forecast moves, the plan doesn't, and the pre-correction lands in the wrong place. And too-aggressive pre-shaping can create the very problem it aims to avoid, over-cooling or over-provisioning against a disturbance that under-delivers. The guarding discipline is to re-shape the schedule as the forecast refreshes, to size the pre-shaping to the forecast's confidence, and to keep a reactive loop underneath as a backstop for when the schedule is wrong.
How it implements the components¶
Predictive Scheduling Rule fills the archetype's forecast-driven-timing slot — the parts that pre-shape when a planned action happens:
intended_action_specification— the planned action is specified in kind; scheduling changes only its timing, not its nature.target_state_or_tolerance_envelope— the tolerance band the effect must stay inside sets how much and how early the action must be shifted.adjustable_control_variable_set— timing and sequence are the dials this rule turns; the when and the order are the control variables.
It fires no correction on a live threshold crossing — the event-driven precorrection_rule is its nearest twin Leading-Indicator Trigger Rule, which waits for a signal rather than committing a timetable ahead. And it relocates no physical resources sized to a forecast_uncertainty_band — that spatial pre-placement is Forecast-Based Resource Prepositioning; this rule changes *when an action runs, not where the resources are.*
Related¶
- Instantiates: Predictive Precommitment Correction — pre-shapes an action's timing from a forecast so its effect lands on target.
- Consumes: Forecast-Error Backtest certifies the forecast the schedule is planned against.
- Sibling mechanisms: Digital-Twin Preview · Precommitment What-If Simulation · Feedforward Adjustment Dashboard · Leading-Indicator Trigger Rule · Forecast-Based Resource Prepositioning · Forecast-Error Backtest · Preflight Consequence Checklist · Model Predictive Control · Staged Commitment Gate
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: The mechanism reads a forecast and solves for the timing and order whose delayed effects will land within a future target envelope.
Nearest alternative: Control, Automation & Runtime — The timetable may later be revised, but the defining operation is ahead-of-time schedule optimization rather than reactive runtime actuation.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Operations Research
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Using forecasts to set action timing and sequence is a scheduling and anticipatory-control problem in operations research.
Related originating lineages:
- Engineering & Design — Engineering control contributes feedforward timing against expected disturbances.
Review resolution: Both blind reviewers agree that operations research is the primary origin. Reconciliation resolves encyclopedia synthesis disagreement. Formative alternate lineages are retained as engineering_design; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Pre-cooling / anticipatory demand shaping — lowering a building's temperature ahead of a forecast heat or price peak so its thermal mass carries it through the peak, a well-established demand-response technique. The general idea generalizes beyond HVAC: run a slow-acting action early, on a forecast-driven schedule, so its effect is in place before the disturbance arrives. ↩