Skip to content

Production scheduling and inventory

This playbook covers the digital work around two jobs: keeping the production schedule, and keeping inventory records right through cycle counts. It describes the work today, what our forward-deployed engineers build and who does what at each level of the autonomy ladder.

The physical work in both jobs stays with people. Agents do not run machines and do not count parts.

The ERP holds the work orders, their due dates and their routings. The schedule people really run to is somewhere else: a spreadsheet, a whiteboard by the supervisor’s office, the scheduler’s head. The ERP’s version assumes run times and capacity that the floor knows are wrong.

Each morning the scheduler gathers what changed. Which purchase orders are late. Which jobs fell behind. Which machine is down and who is out. Which order customer service has promised for Friday. Then the scheduler re-sequences the work, walks the floor and spends the rest of the day answering one question: when will it ship.

  • A job reaches the machine and the material is not there, because the ERP still showed the date that was requested.
  • Job status runs a shift behind, because operators report at the end of the shift or on paper.
  • The sequencing knowledge is in one person’s head: which jobs share a setup, which material runs before which.
  • Customer service promises dates without seeing the schedule.

The quantities in the ERP drift from what is on the shelf. Scrap goes unreported. A pick comes from the wrong bin. A receipt is entered in the wrong unit of measure. Cycle counts are meant to catch the drift: someone prints count sheets, counters count, someone keys the counts, variances are recounted and adjustments are posted.

  • Counts are skipped in a busy week.
  • A count taken while picks or production are still unreported shows a variance that is not real.
  • Adjustments are posted without anyone finding the cause, so the same variance comes back.

The work touches the scheduler, production supervisors, buyers, customer service, counters and the controller. The workflow owner is typically the plant manager or the scheduler for the schedule, and the inventory lead for counts.

  • Screens: a schedule screen fed from the ERP’s work orders, routings, material availability and job status, where the scheduler sequences the work and every move is recorded with its reason. A count screen where counters enter what they counted.
  • Queues: jobs at risk, meaning jobs that start soon with material not on hand or a supplier date that has slipped. Counts due today. Schedule changes, recounts and adjustments waiting for a person.
  • Rules: the scheduler’s sequencing rules, written down: setup families, preferred machines and the frozen window inside which nothing moves without the supervisor. For counts: how often each class of item is counted, the variance tolerance, when a recount is required and who approves an adjustment above a set amount.
  • Integrations: reads of work orders, routings, purchase order dates, on-hand quantities and open transactions. Write-backs: schedule dates on work orders, where the ERP supports it, and inventory adjustments through the ERP’s own count transaction.
Level What the agent does What people do
Level 0 (Recorded) Nothing yet. The scheduler builds the schedule on a screen that records every move and its reason. Counters enter counts on a screen that records the count, the recount and the cause of each variance.
Level 1 (Assisted) Drafts the morning list of jobs at risk and a summary of what changed overnight. Answers “when will this order ship” from the current schedule. Drafts the day’s count list and summarizes the variances. The scheduler decides the sequence. The inventory lead decides what to count and what to adjust.
Level 2 (Prepared) Prepares a schedule change in full when a material date slips or a job falls behind, showing what moves and why. Prepares each inventory adjustment with the count, the recount, the open transactions and the likely cause. The scheduler approves every schedule change. The inventory lead or the controller approves every adjustment.
Level 3 (Supervised) Issues the daily count list. Posts adjustments that a recount confirmed, under a quantity and amount limit, for the item classes on its list. Sends the jobs-at-risk list and current order dates to customer service without an approval. People count. The inventory lead handles larger variances and spot-checks. The scheduler still approves every schedule change.
Level 4 (Autonomous) Not a goal for this work. People keep setting the schedule and approving the larger adjustments.

This is the work where the ladder stops earliest, for two reasons. The schedule decides what machines and people do, so a wrong action costs scrap, overtime or a missed shipment. And not every input is digital: the supervisor knows a machine is running rough or a crew is short before any system does.

  • Schedule changes stay at Level 2 for good. The agent prepares and the scheduler decides.
  • Information around the schedule, the jobs-at-risk list and the dates customer service sees, can run at Level 3.
  • Counts can reach Level 3. The agent issues count lists and posts small adjustments that a recount confirmed. Larger adjustments always go to a person, because an adjustment changes the value of inventory on your books and can bury a problem that needs finding.
Exception Who it usually goes to
Material is short for a job inside the frozen window Scheduler and supervisor
A rush order that would bump other jobs Scheduler, with customer service
A machine down or an operator out that nobody has recorded Supervisor
A job reported complete with less than the ordered quantity Scheduler
A variance still over tolerance after a recount Inventory lead
A negative on-hand quantity Inventory lead
A variance on a lot-controlled or serialized item Quality or the inventory lead
  • Schedule changes per day, and the reason for each.
  • Jobs that started late for lack of material, and whether the shortage was seen in advance or found at the machine.
  • Dates promised to customers against dates shipped.
  • Time the scheduler spends gathering information against time spent deciding.
  • Counts planned against counts done.
  • Variances by item, location and cause, and what the recounts found.
  • Adjustments posted: how many, in which direction and who approved them.

These are things to measure, not targets. The threshold for each level is set with the workflow owner and written down before that level starts.