Finite Scheduling & Short-Term Capacity Workbook

Welcome — What this workbook helps you do

This worksheet helps you produce a realistic short-term schedule that respects true, finite capacity and protects bottlenecks. Use it to capture the capacity inputs you need, choose a simple sequencing approach, lock in constraint-protection rules, document your short-term change protocol, and track a few KPIs that quickly reveal why orders run late.

How to use this workbook

Work through the sections in order. Keep the schedule horizon short (1–7 days) for finite scheduling: the shorter the horizon, the easier it is to keep constraints protected. Use the templates below to gather the data operations staff already have (order list, machine capacities, run times, setup types). If you later want to save responses, consider converting this workbook to an interactive form that stores submissions.

Section A — Finite capacity inputs (capture the facts)

Collect these baseline inputs for each resource/machine/line you plan to schedule over the planning horizon.

• Resource name (machine/line/operator)
• Available hours per shift (e.g., 8)
• Shifts / day (e.g., 2)
• Planned uptime / shift (account for breaks, meetings, known downtime)
• Effective capacity (units/hr or cycle time per part)
• Routine maintenance windows (planned PMs during the horizon)

Template (paste or copy to a spreadsheet):

Resource | Shifts/day | Hours/shift | Planned uptime (hrs) | Capacity (units/hr) | PM windows
Press A | 2 | 8 | 7.5 | 100 | 14:00-15:00 day 3
  

Section B — Orders and routing (what you must schedule)

For each order include at least: Order ID, Quantity, Due date/time, Routing steps (resource sequence), Estimated run time per step, Setup type (standard, family, full changeover).

OrderID | Qty | Due | Routing (A->B->C) | Run time step A (hrs) | Setup type
O-1223 | 500 | 2026-08-15 | Press A -> Oven B | 4.5 | family
  

Section C — Identify bottlenecks (quick methods)

Use one or more of these quick checks to find constraint resources:

1. Historical throughput: which resource most often runs at or near 100% utilization?
2. Cycle-time vs demand: whose required processing-hours exceed available hours?
3. Shop-floor observation: where does finished WIP queue up?

Document identified bottlenecks and why you believe they are constrained:

Bottleneck resource: Press A — high utilization in last 7 days; WIP pile before press; frequent overtime
  

Section D — Choose simple sequencing heuristics (practical examples)

Pick a heuristic appropriate to your primary risk (due-date failures, minimizing average lead time, minimizing setups):

• Earliest Due Date (EDD) — sort orders by due date. Best when meeting due dates is the top priority.
• Shortest Processing Time (SPT) — run the shortest jobs first to reduce average completion time and clear WIP quickly.
• Critical Ratio (CR) — (time until due) / (processing time). Lower ratios get priority; helps balance urgency and work remaining.
• Family batching / setup minimization — group orders that share tooling or setups to reduce changeovers at the cost of some lateness risk.

Example guidance: For a bottleneck press with many small orders, SPT or family batching (if setups are heavy) often reduces overall lateness. If a few large customer orders drive penalties, use EDD or CR.

Record chosen heuristic and any tie-break rules:

Sequencing heuristic: CR with tie-break to family grouping
Tie-break: prefer same setup family when CR within 0.1
  

Section E — Constraint protection rules (must-follow safeguards)

These rules prevent optimistic schedules from being violated. Use as-is or adapt to your context.

• Protect bottleneck capacity: never schedule > available effective hours on the bottleneck for the horizon.
• Reserve capacity for planned PMs and changeovers (treat as non-available time).
• Limit WIP entering a constrained buffer (max WIP queue length or hours of work-in-process).
• Apply a finite freeze window: do not accept schedule changes inside X hours of execution on constrained resources.
• Use capacity buffers for high-variability products (e.g., hold 10–20% spare time on a bottleneck when demand is volatile).

Fill your rules here:

Protect bottleneck: Press A max 48 hrs booking over next 3 days; Freeze window: 6 hrs; Buffer: 10% of daily bottleneck time
  

Section F — Short-term change protocol (who can change the plan and how)

A short, clear change protocol reduces firefighting and miscommunication. Use this template and adapt names/SLAs.

• Change requester notes request to planner.
• Planner review evaluates impact on bottlenecks within 15 minutes for urgent requests.
• Change approval — who may approve (Planner, Shift Lead, Production Manager) depending on impact level.
• Communication — update board, dispatch log, and notify downstream ops via radio/text.
• Escalation — if change will cause late delivery or >X% bottleneck utilization, escalate to Plant Manager before implementation.

Change approval matrix:
Minor (<30 min impact) — Planner
Moderate (30–120 min or causes <5% increase bottleneck load) — Shift Lead
Major (>120 min or causes >5% bottleneck increase) — Production Manager
  

Section G — KPI sheet: what to track daily

Track a small set of indicators to see whether the finite schedule is being respected and why orders are late.

Suggested daily checklist for the shift planner:

1. Confirm bottleneck available capacity for the shift.
2. Verify first X scheduled jobs are fully ready (materials, tooling, operator).
3. Run a 5-minute pre-shift huddle to review critical orders and constraints.
4. Record any deviations and root causes in the dispatch log.

Section H — Quick decision rules when things go wrong

Use simple, pre-agreed actions to reduce firefighting:

• If bottleneck overruns by >30 minutes: trigger cross-functional huddle and hold non-critical setups.
• If a material shortage prevents start: push affected orders past freeze window and notify customer if due date affected.
• If unplanned breakdown reduces bottleneck capacity by >20%: move non-critical work to later shifts or outsource short runs where economical.

Section I — Practical examples

Example 1: A press is the bottleneck. You have three orders due next day: a small urgent order (2 hrs), a large run (12 hrs), and a medium run (6 hrs). SPT clears the small order fast and reduces average lateness; CR would prioritize urgent if due time is tight. If setups are long, consider running the medium and large together if they share tooling.

Section J — Reflection & next steps

After creating and operating the finite schedule for 3–7 days, review these questions in a short improvement huddle:

• Which late reasons appeared most often?
• Did the freeze window prevent chaos or cause unacceptable delays?
• Is the bottleneck utilization steady within your buffer target?
• Which sequencing heuristic performed best for our goals?

Document changes and update the rule set. If you regularly need to collect and compare plan inputs and outcomes, consider making this workbook an interactive form that stores each plan and lets you track KPI trends over time.

Appendix — Ready-to-copy templates

Order table, resource table, KPI tracker and the change-approval matrix above are intentionally simple so they can be copied into a spreadsheet or digital board. Keep one canonical schedule for the horizon and distribute it to operators and supervisors.