Advanced Planning, Scheduling & APS worked example

Dispatch Priority Score with due-date urgency of 20 1-10: a worked example

Push due-date urgency up to 20 1-10 and the picture changes. This example computes every intermediate figure at that operating point. a production planner needs to rank jobs on a dispatch list during the daily scheduling meeting

The inputs for this scenario

  • Due-date urgency: 20 1-10 (raised for this scenario; the documented default is 8)
  • Constraint load pressure: 7 1-10 (unchanged)
  • Recovery visibility weakness: 5 1-10 (unchanged)

Working through the calculation

  • Applying the documented formula (Dispatch priority score = urgency score × constraint score × visibility score) to the inputs above produces each figure below.
  • At this operating point the engine returns 11.7 score for dispatch priority score, the number this scenario is built around.
  • At this operating point the engine returns 20 1-10 for due-date urgency.
  • At this operating point the engine returns 7 1-10 for constraint load pressure.
  • At this operating point the engine returns 5 1-10 for recovery visibility weakness.

How this compares with the baseline

  • Against the tool's baseline example, where due-date urgency sits at 8 1-10 and the headline result is 6.9 score, this scenario comes in 69.57% above the baseline at 11.7 score.
  • It multiplies three 1-to-10 ratings — due-date urgency, constraint load pressure, and recovery visibility weakness — into a single ranking score for triaging schedule problems. The value of this scenario is the size of the gap it exposes: that gap, priced out over a year, is the budget you can justify spending to close it.

Results at a glance

  • Dispatch priority score: 11.7 score (headline result)
  • Due-date urgency: 20 1-10
  • Constraint load pressure: 7 1-10
  • Recovery visibility weakness: 5 1-10

Run it with your numbers

  • Every input above is editable in the live Dispatch Priority Score calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.