What Is a Work Center Dispatch List?

A work center dispatch list is the ordered run queue for a single station: the operations that station should run, in sequence, for a given date range. It is the clipboard at the machine that says run this job next, then that one. The list turns a shop-wide finite-capacity schedule into a station-level instruction, and EDGEBIC generates it directly from the plan the engine built, so the floor runs the sequence the scheduler actually chose.

This entry is part of the EDGEBIC by User Solutions glossary series; for the broader vocabulary of planning, see the manufacturing glossary.

How a Dispatch List Works

A schedule spans the whole shop: every job, every operation, every work center, laid out in time. That is the right view for a planner, but it is too much for the person standing at one machine. What the operator needs is a filtered slice, just this station's operations, in the order to run them.

A dispatch list is that slice. It takes the finite-capacity schedule, isolates one work center, and lists the operations assigned to it within a date range, sorted into the sequence the engine placed them. The order is not arbitrary and is not chosen at print time; it is the scheduler's own decision, arrived at by respecting available capacity, operation dependencies, and setup considerations. The dispatch list simply reports that decision at the level a supervisor can act on.

Because the list reflects the engine's plan, it stays consistent with everything else the schedule promises. If the plan says an operation runs Tuesday morning on Mill-1, that operation appears in Mill-1's Tuesday dispatch, in its scheduled position. The floor and the plan speak the same language.

A Concrete Example

Take Mill-1 at the start of a shift. The planner runs the dispatch report for Mill-1 for today. The report returns the station's ordered queue: run Job 42 Step 3 first, then Job 57 Step 1. The supervisor prints it and hangs it at the machine.

The operator now has an unambiguous instruction. Job 42 Step 3 goes on first, and when it finishes, Job 57 Step 1 follows. No scanning the whole schedule, no guessing which job is most urgent, no memory of yesterday's priorities. The sequence came from the finite-capacity engine, which already weighed capacity and dependencies, so following the list means running the plan as designed.

Widen the report to the whole shop and you get every station's queue for the day, which is what a planner uses to walk the floor's plan station by station. Narrow it back to one machine and one week and you get a focused clipboard for that station's supervisor.

How EDGEBIC Uses It

EDGEBIC produces the work center dispatch as a dedicated report. You give it a date range and, optionally, a specific work center, and it returns the ordered list of operations each station should run, in the columns a supervisor prints for the shift. Set a work center and you get that one station's queue; leave it open and you get the shop-wide dispatch across all stations.

This report is the execution face of the schedule. The scheduling engine decides the sequence when it builds the finite-capacity plan, and the dispatch report exposes that sequence per station so the floor can follow it. It is one half of turning a plan into executed work, the instruction side, paired with the actuals the floor records as jobs run. Together they keep the plan and the shop aligned, which is the whole point of a live dispatch rather than a stale printout. See how the recorded actuals close the loop in the actuals tracking guide, and how execution fits the planning hierarchy in production activity control.

Related Reading

The dispatch list is the execution front of production activity control, and the sequence it reports comes from the ordering rules in the priority rules glossary. For the generic version of this term, see the dispatch list glossary.