Shopfloor Dispatching & Priority Rules Matrix

Purpose

This dispatching and priority rules matrix explains a small set of clear, testable heuristics operators and MES logic can use to sequence work. It turns schedule intent into consistent decisions that protect constraints, reduce firefighting, and make sequencing explainable and auditable.

How to use this matrix

1. Agree with planners and production control on the primary objective (protect constraint throughput, minimize lateness, minimize changeovers, or balance multiple objectives).
2. Choose a primary dispatch rule and one or two secondary rules (tie-breakers) from the definitions below.
3. Configure simple side constraints (maximum WIP at bottleneck, no unscheduled rushes on hourly cadence, setup window protections).
4. Train operators on escalation: when to follow the rule, when to call a supervisor, and how to document exceptions.
5. Run short experiments, measure outcomes (OTD, throughput, changeovers, WIP), and iterate.

Core rule definitions (pick the few you will actually enforce)

• Due Date / Earliest Due Date (EDD) — sequence by nearest promised delivery date. Good when the overriding goal is on‑time delivery to customers.
• Shortest Processing Time (SPT) — run shortest jobs first to reduce average flow time and WIP.
• Longest Processing Time (LPT) — run long jobs first when setup or throughput favors blocking long runs on constrained resources.
• First In, First Out (FIFO) — sequence by arrival time to keep process fairness and simplicity.
• Critical Ratio (CR) — ratio of time remaining to work remaining (due date horizon / remaining processing). Values <1 are urgent.
• Slack Time — time until due date minus remaining processing time; smaller slack = higher priority.
• Setup Minimization — group runs to minimize changeovers (e.g., sequence by tooling family or color).
• Constraint Protection — protect the bottleneck by sequencing to keep it fed with ready work; may prioritize jobs that keep the constraint busy.
• Expedite — explicitly flagged orders that override normal rule(s) but must be limited and documented.
• Kanban / Pull — replenish only when downstream consumption triggers; use for repetitive, stable flows.

Tie‑breakers (secondary rules to resolve equal priority)

1. Customer priority (premium or critical customers first).
2. Smaller remaining processing time (SPT).
3. Lower setup cost if changeover will be required.
4. Earlier release date (FIFO).
5. Random within same priority bucket (to avoid bias when nothing else differentiates).

Sample Priority Matrix (example you can copy)

Escalation path and rules

Document a simple, short escalation path to keep decisions fast and auditable:

1. Operator follows matrix and documents chosen rule & reason in the board or MES.
2. If a rule conflict or unexpected event arises (e.g., machine break, missing parts, customer expedite), operator notifies Supervisor within X minutes and continues with next valid job as defined by the matrix.
3. Supervisor resolves issues that can be fixed locally (swap resources, authorize limited expedite within daily quotas).
4. Planner/Production Control handles broader schedule changes, large expedites, or repeated exceptions.

Sample scenarios with expected outcomes

Implementation checklist

• Agree objective and matrix with planners, supervisors, and operators.
• Configure MES rules or create a simple visual board that implements the matrix.
• Limit the number of exceptions and require documented escalation for any expedite.
• Define 2–4 clear KPIs to measure impact (OTD, throughput at constraint, average changeover time, WIP levels).
• Run a 2‑week pilot on a cell, collect data, then iterate the matrix rules.

Common pitfalls and how to avoid them

• Too many rules: keep the matrix simple—operators should be able to remember and apply it.
• Unlimited expedites: put quotas or approval steps in place.
• No measurement: track KPIs to see if the matrix actually improves outcomes.
• Ignoring constraint protection: sequencing that dries up the bottleneck damages throughput even if it helps individual orders.

Notes for MES or automation

This matrix is intentionally compact so it can be translated into simple MES logic or a rule engine: primary rule, tie‑breakers, and hard side constraints. When automating, capture which rule produced the decision for later analysis and keep operator override gated and auditable.

Next steps & experiment ideas

1. Run A/B pilot comparing current ad‑hoc sequencing vs. the matrix for two weeks on comparable lines.
2. Log every exception and reason; review weekly with the CI team to refine the matrix.
3. When stable, convert the matrix into MES rules with an operator confirmation step and use the Content Data Submission capability to record exceptions.

Copy this matrix into your plant toolkit and adapt the sample priority table to reflect your local constraint, customer mix, and changeover economics.