Production Scheduling
Place production work into specific finite resource slots, sequence jobs, protect due dates, manage changeovers and respond to disruptions while keeping schedule changes explainable.
Each block is planned for 60 minutes: about 35 minutes to learn, 15 minutes for the worked case and 10 minutes for notes or review. Take breaks between blocks. You can complete the lesson over several days.
The idea in simple words
Production scheduling answers which order runs next, on which resource and at what time. It translates a feasible manufacturing plan into a sequence that people can execute. A strong schedule respects precedence, materials, calendars, changeovers and due dates—and remains stable enough to communicate.
Start here: Use released or approved manufacturing orders with validated routes, quantities, material status and due dates. Do not schedule a quantity that is not feasible or approved.
1. Distinguish scheduling from planning and dispatch
Planning sets quantities and time buckets; scheduling assigns orders to finite resources and times; dispatching tells the floor which ready task to start next. These layers are related but not interchangeable. A schedule should respect firm commitments and identify what is still tentative. Define the time horizon and frozen zone, where changes are restricted because material, labor or customer commitments are already in motion.
Worked example
A weekly plan calls for 80 bottles. The schedule places 30 on Monday morning and 50 on Tuesday afternoon. Dispatching then selects the next released, material-ready operation at the start of a shift.
Try it · 10 minutes
Write one example of a plan, a schedule and a dispatch instruction for the same product.
Watch for: A schedule is useful only when the shop floor can understand and execute its sequence.
2. Build operation sequence and setup logic
Orders may contain several operations with precedence relationships. A later step cannot start before required earlier work is complete, unless the process explicitly allows overlap. Setup time may depend on the sequence of products: moving from a light color to a dark color can differ from moving dark to light. Grouping similar work can reduce setup but may delay urgent orders. Use a setup matrix or approved family logic instead of assuming every changeover costs the same.
Worked example
Three jobs require color changes: white, blue and black. If setup is 20 minutes from white to blue and 45 minutes from blue to white, the reverse order changes the plan. A 45-minute saving may be outweighed by a missed customer due date.
Try it · 10 minutes
Draw a precedence chain for three operations and compare two sequences with different setup times.
Watch for: Sequence-dependent setups mean “same total units” can require different total schedule time.
3. Use finite capacity and sequencing rules wisely
Finite scheduling places work only where a resource has available time. Common priority rules include earliest due date (EDD), shortest processing time (SPT) and critical ratio (time remaining until due ÷ processing time remaining). Each rule optimizes a different concern and can produce poor outcomes when used alone. Include setup, run duration, release readiness and due-date meaning. Use the rule as a decision aid; planners still need to respect commitments and exceptions.
Worked example
Job A needs 2 hours and is due in 6 hours: critical ratio 3. Job B needs 4 hours and is due in 8 hours: ratio 2. B is more urgent by this rule, but setup, material readiness and customer priority may change the final sequence.
Try it · 10 minutes
Calculate critical ratios for two sample orders and choose one to schedule first. State one reason the rule could mislead.
Watch for: Priority rules help organize work; no single rule captures every business objective.
4. Check material, labor, tools and calendars
A machine may be open while the job is not ready. Confirm the right material, revision, labor skill, tooling, quality status and maintenance window. Check shift calendars, breaks, planned downtime and overlapping resource requirements. Some operations need more than one resource at once, such as a machine and a certified operator. If a component is expected but not confirmed, show it as a readiness risk rather than treating it as available.
Worked example
A line has a free 2-hour slot, but the label roll is not due until the afternoon and the operator with required training is on the morning shift. The job is not ready for that slot even if machine capacity exists.
Try it · 10 minutes
Build a readiness checklist for one work order with material, labor, tools, quality release and calendar. Mark each item confirmed or at risk.
Watch for: A free machine slot does not prove that a job can start.
5. Manage batches, campaigns and changeovers
Batch size can affect throughput, quality and inventory. A large batch may reduce setup per unit but delay other jobs and increase work in process. A campaign groups similar products to reduce changeovers, but it can postpone an urgent order. Consider shelf life, downstream capacity, container or tooling limits and partial-lot rules. Show the reason for a sequence choice so operators and customer teams can anticipate the consequences.
Worked example
Running 100 blue bottles together saves 40 minutes of setup, but a 20-unit urgent white order due first would be late. Running the white order first may be better even if the total setup time is higher.
Try it · 10 minutes
Compare a large-batch sequence with an urgent-small-batch-first sequence. Record total setup time, completion times and WIP.
Watch for: Reducing changeovers is not automatically the same as improving customer service.
6. Replan disruptions without creating avoidable churn
When a machine fails, a supplier is late or demand changes, identify affected orders and the latest feasible recovery time. Consider alternate qualified resources, overtime, split lots, sequence swaps and revised promises. Preserve a baseline schedule and record what changed, why, and who approved it. Avoid re-optimizing every order for a small improvement; schedule churn makes plans difficult to trust and execute. Compare service, cost, stability, safety and material impacts.
Worked example
A machine stops for 2 hours. Job A due in 3 hours needs 90 minutes; Job B due tomorrow needs 2 hours. Moving B to a qualified alternate line may protect A without creating a larger downstream setup or material issue.
Try it · 10 minutes
Simulate a two-hour outage. List the affected orders and compare three responses with their remaining risks.
Watch for: Replanning should focus on the smallest set of changes that restores a feasible and understandable plan.
7. Measure schedule adherence and learn from execution
Schedule adherence compares actual execution with the agreed schedule using a clearly defined measure. It might compare start dates, completion dates or quantities; define the window and tolerance. Pair adherence with throughput, WIP, setup loss, downtime, scrap and on-time delivery. A poor score may reflect an unrealistic schedule, weak material readiness, disruptions or execution constraints. Avoid blaming operators for plan conditions outside their control. Feed actual times and reason codes back into routing and planning data only after review.
Worked example
The schedule calls for 80 units by Friday; 72 good units are complete, 4 are in rework and 4 never started due to missing caps. A single “90% complete” figure hides quality and material causes.
Try it · 10 minutes
Define one schedule-adherence formula and specify how you treat early starts, partial quantities, approved changes and rework.
Watch for: Metrics need stable definitions before teams compare sites or periods.
8. Create a practical schedule and handoff
For each order, collect quantity, route, due date, release status, setup family, run time, material readiness and required skills. Place work in calendar slots, include setup and planned downtime, check precedence and resource overlap, then review the resulting completion promises. Publish the schedule with a version and cutoff time. Communicate priority, changes and escalation path. At shift handoff, record completed work, WIP location, shortages and the next ready job.
Worked example
Northstar has 30 bottles due Monday and 50 due Wednesday. Line A runs 20 units/hour with a 30-minute setup; the first order needs 2 hours plus setup. The second follows only after the setup and first run, subject to cap availability and the shift calendar.
Try it · 10 minutes
Create a two-day schedule using three jobs, one machine, a setup family and a due date. Check total load against shift hours and mark uncertain material.
Watch for: A schedule is a communication agreement backed by feasible resource and material checks.
Further reading and scope
These sources provide background for the planning concepts. The explanations, diagrams and Northstar examples on this page are written for this site. Official software manuals describe the named product and configuration; they do not define a universal process. No source text or figures are reproduced here.
- Oracle, “Manage a Production Schedule.” Official product documentation; publication date not displayed; accessed 30 October 2026.
Describes production-schedule refresh, finite-capacity solve or repair, release, resequencing and alternate-resource actions in Oracle SCM. - Oracle NetSuite, “Finite Scheduling.” Official product documentation; publication date not displayed; accessed 30 October 2026.
Explains finite scheduling in a named product and its dependency on routings and available capacity.
Quick knowledge check
Choose an answer before opening the explanation. These questions review the key ideas from all eight blocks.
1. What does production scheduling add to a weekly build plan?
- Specific resource sequence and time slots
- A new product forecast
- A supplier contract
- A balance sheet
Reveal answer and explanation
Answer: A. Specific resource sequence and time slots Scheduling assigns work to finite resources and times.
2. What is dispatching?
- Choosing the next ready task to start
- Creating a forecast baseline
- Approving a supplier
- Calculating annual revenue
Reveal answer and explanation
Answer: A. Choosing the next ready task to start Dispatching communicates which ready operation should run next.
3. What does earliest due date prioritize?
- Jobs with the soonest due date
- The shortest setup only
- The largest quantity
- The newest SKU
Reveal answer and explanation
Answer: A. Jobs with the soonest due date EDD sorts work by due date.
4. Critical ratio is calculated as?
- Due-date time remaining ÷ processing time remaining
- Inventory ÷ sales
- Capacity × forecast
- Setup time + yield
Reveal answer and explanation
Answer: A. Due-date time remaining ÷ processing time remaining The ratio compares time remaining with work remaining.
5. Why can grouping products by setup family be harmful?
- It may delay an urgent order
- It eliminates setup
- It always reduces capacity
- It removes the due date
Reveal answer and explanation
Answer: A. It may delay an urgent order A setup-saving campaign can delay priority work.
6. A machine slot is open but material is missing. Is the job ready?
- Yes, machine availability is enough
- No, material readiness is also required
- Yes, if forecast is high
- Only when schedule is monthly
Reveal answer and explanation
Answer: B. No, material readiness is also required A job needs all required inputs, not merely an open machine.
7. Why preserve a schedule baseline after replanning?
- To understand what changed and why
- To hide disruptions
- To increase setup
- To prevent execution
Reveal answer and explanation
Answer: A. To understand what changed and why The baseline makes revisions traceable and supports learning.
8. What is schedule churn?
- Repeated changes that destabilize the working sequence
- A fixed setup time
- A demand pattern
- A product unit
Reveal answer and explanation
Answer: A. Repeated changes that destabilize the working sequence Excessive changes make plans harder to execute and trust.
9. Why define schedule-adherence rules?
- So all teams measure starts, completions and tolerances consistently
- To make all jobs identical
- To eliminate materials
- To remove customer dates
Reveal answer and explanation
Answer: A. So all teams measure starts, completions and tolerances consistently Metrics are comparable only when their definitions are clear.
10. What should a shift handoff include?
- Completed work, WIP, shortages and the next ready job
- Only the yearly forecast
- Only a logo
- No information
Reveal answer and explanation
Answer: A. Completed work, WIP, shortages and the next ready job A useful handoff gives the next shift a clear, executable starting point.
Educational content only. All quantities, products, scenarios and costs are illustrative. Real methods depend on data quality, local policy, system design, contracts and operating constraints.