Production Planning vs Scheduling: Shopping List vs Cooking Timer

The weekly plan for the coating line looks comfortable: 38 hours of work against 40 hours of capacity. Everyone signs off on Friday. By Tuesday afternoon, a customer order is running late, the supervisor is asking for overtime, and nobody can say what went wrong. The plan was right. The week was still impossible.

Production planning decides what to make, how much, and by when, and checks that the totals fit your materials and capacity. Production scheduling decides the exact order, machine and start time of each operation, so the work fits hour by hour. In production planning vs scheduling, the question is not which is better, but which one answers what.

The shopping list and the cooking timer

Think about cooking a holiday dinner for twelve. The shopping list is your plan: a turkey, potatoes, two pies, enough of everything, bought by Wednesday. If the list is right, nothing is missing.

The cooking timer is your schedule. The turkey needs the oven from 11 a.m. to 4 p.m. The pies need the oven too, at a different temperature, for an hour each. You have one oven. The list never told you that, because a list has no clock in it.

Factories work the same way. A plan works in buckets, a week or a month, and asks "is there enough?" A schedule works on a timeline and asks "what happens first, on which machine, and when does it finish?"

A worked week: 38 of 40 hours, and Tuesday still fails

The coating line runs one 8-hour shift, five days a week: 40 hours. Five orders are planned for the week:

• Order A: 10 hours, due Tuesday evening
• Order B: 8 hours, due Tuesday evening
• Order C: 6 hours, due Thursday
• Order D: 8 hours, due Friday
• Order E: 6 hours, due Friday

Total: 10 + 8 + 6 + 8 + 6 = 38 hours. The weekly capacity check passes with 2 hours to spare.

Now put the orders on a timeline. Orders A and B must both be finished by Tuesday evening. That is 10 + 8 = 18 hours of work. Monday and Tuesday together hold 2 × 8 = 16 hours. Whatever the sequence, one of them finishes 2 hours into Wednesday.

The 2 spare hours do exist, but they sit at the end of Friday: Wednesday to Friday holds 24 hours, and the 2-hour spillover plus C, D and E need 2 + 6 + 8 + 6 = 22. Spare hours at the end of the week cannot be spent at the start of it. Capacity is perishable: an idle hour on Friday does nothing for a customer waiting on Tuesday.

Add a 30-minute color change between orders, four in total, and the week needs 38 + 4 × 0.5 = 40 hours. Zero slack.

The planner now has real choices, and they are business choices:

• Run 2 hours of overtime on Monday or Tuesday.
• Move the first hours of Order A to a second line, if that line can coat the product.
• Ask the customer of Order B to accept delivery Wednesday morning.
• Split Order B: ship three quarters on Tuesday and the rest on Wednesday.

None of them appeared in the weekly plan. All of them appear once the week is on a timeline.

The ladder: what each planning tool checks

Each rung between "what do customers want" and "what did the machine do" checks something the rung above it could not.

1. MPS, the master production schedule. Which finished products you will make, how many, and in which week. It is the promise a factory makes to itself. It checks demand and priorities.
2. RCCP, rough-cut capacity planning. Converts the MPS into hours on a few key resources per week or month. Rough-cut capacity planning is the check that said "38 of 40, fine".
3. MRP, material requirements planning. Explodes the bill of materials and tells you which components are missing and when to order them. MRP assumes infinite capacity: it will happily plan A and B for the same Tuesday.
4. APS, or finite scheduling. Places each operation on a real resource with a real calendar, one job at a time, including changeovers and material arrival dates. This is where Tuesday fails, and where it gets fixed.
5. MES, or shop-floor feedback. Records what actually started, finished and got scrapped, so tomorrow's schedule starts from reality.

Most ERP systems cover rungs 1 and 3 well and rung 4 barely, which is why so many plants fill the gap between ERP and the shop floor with a spreadsheet.

Myth: "A schedule is just a more detailed plan"

Cut the week into days and you have a schedule, right? Not quite. Daily buckets would still say Monday has 8 hours and Tuesday has 8 hours and let you pour A and B into them. A schedule knows three things a plan cannot:

• One machine does one job at a time. Order matters, and a queue forms.
• Changeovers depend on sequence. Dark after light may cost 30 minutes; light after dark may cost two hours.
• Time only runs forward. Material that arrives Tuesday noon cannot feed a job that had to start Monday.

That is also why sorting jobs by due date rarely gives a good sequence. The rules for that are a topic of their own, covered in production scheduling.

The reverse myth is just as costly: a great scheduler cannot rescue a bad plan. If the week really needs 46 hours on a 40-hour line, resequencing only chooses which customer is late. Adding overtime, using a second line or moving a date is a planning decision, and it belongs to whoever owns the customer promise.

When to replan and when to resequence

• Local and temporary (a short breakdown, one late pallet): resequence. The plan stays.
• Repeated or large (the same work center overloaded every week, a supplier two weeks late): replan. A new sequence only moves the pain around.

The urgent order is the classic trap. Inserting it does not create a single hour of capacity. It pushes other jobs to the right, and an honest schedule shows which ones.

FAQ

Is production scheduling the same as APS? APS (advanced planning and scheduling) is software that builds finite-capacity schedules, usually with some planning functions on top. Scheduling is the job; APS is one way to do it.

Who owns the plan, and who owns the schedule? Usually the plan comes out of S&OP with sales at the table, and the schedule belongs to the scheduler. Write down which changes the scheduler may make alone and which go back to planning.

How the example looks in factory.online

In factory.online, RCCP shows the coating line at 38 of 40 hours for the week. On the Gantt chart of the finite schedule, Order B's bar runs past Tuesday evening, with the sales order and customer behind it. The planner copies the plan into a scenario, adds two overtime hours on Tuesday, and compares both versions before calling anyone. Output confirmed at the line becomes the starting point for the next schedule.

If your week looks fine on Friday and falls apart by Tuesday, see how it looks on your own orders in a demo.