Setup, Sequencing, and Why Order Matters
Synopsis
Manufacturing scheduling often gets buried under terminology long before the underlying ideas are understood.
This is Part 1 of a three-part series that steps away from abstract language and explains core scheduling concepts using something most people already understand: a pizza kitchen. Setup time, sequencing, setup keys, and sequence-dependent changeovers sound complex in SAP conversations, yet they show up every day in kitchens, workshops, and factory floors.
This first article focuses on why order matters. The same set of jobs can produce very different outcomes depending on sequence alone. By introducing setup keys, setup groups, and setup matrices through a simple analogy, it shows how scheduling decisions directly affect time, utilisation, and delivery performance.
The goal is not to simplify manufacturing realities, but to make them tangible. Before optimisation algorithms or advanced tools come into play, teams must decide what they are optimising for, whether that is reduced setup loss, higher throughput at a bottleneck, or improved delivery reliability.
Part 2 will examine sequencing rules and the trade-offs they introduce. Part 3 will address what happens when reality disrupts the schedule.
If scheduling discussions in your organisation feel technical yet disconnected from shop-floor behaviour, this series is designed to reset that conversation.
Main Article
Manufacturing scheduling has a reputation for sounding far more complicated than it needs to be. Words like setup key, setup matrix, and sequence-dependent setup time tend to make people either nod politely or quietly disengage.
So let us put SAP language aside for a moment and talk about pizza.
Because if you have ever run a kitchen during a busy hour, you already understand most of manufacturing scheduling. You just may not know the vocabulary yet.
Let us start with setup time.
Setup time is the fixed time required to prepare a workstation before starting the next job. In a pizza kitchen, this is the time it takes to clean the counter, adjust the oven temperature, change toppings, or reset trays before making the next pizza. During this time, nothing is produced. No value is added. It is preparation.
Importantly, setup time by itself does not decide how long your day will run. That depends on the sequence in which you execute orders.
This brings us to the setup key.
The setup key defines what actually causes a changeover. In pizza terms, the setup key could be pizza type, oven temperature, or ingredient category. The key answers a simple question. What is it that changes when I move from one order to the next?
Next is the setup group.
A setup group is the specific value of the setup key. For example, vegetarian pizzas could be one setup group, meat-based pizzas another, and seafood pizzas a third. If chicken and seafood require no meaningful cleaning or temperature change, they may belong to the same setup group. This grouping requires thought. Poor grouping decisions create unnecessary changeovers and wasted time.
Then comes the setup matrix.
This is where things become interesting. The setup matrix is a table that defines how much time it takes to move from one setup group to another. Moving from vegetarian to meat might take five minutes. Moving from seafood back to vegetarian might take eight minutes, for reasons that are cultural as much as operational.
The key point is this. Not all changeovers are equal. The direction of the change matters.
Finally, we arrive at sequence-dependent setup time.
This is the dynamic part of scheduling. During scheduling, the system looks at the actual sequence of orders and calculates the real setup time based on the setup matrix. Change the sequence, and the total setup time changes.
For example, consider three orders.
- Vegetarian, then meat, then seafood.
- Vegetarian to meat takes five minutes.
- Meat to seafood takes ten minutes.
Total setup time is fifteen minutes.
Now change the sequence.
- Seafood, then vegetarian, then meat.
- Seafood to vegetarian takes eight minutes.
- Vegetarian to meat takes five minutes.
Total setup time is thirteen minutes.
Nothing about the orders changed. Only the sequence did.
Is the customer willing to wait two minutes longer or shorter? Sometimes yes. Sometimes no. That judgement is where scheduling stops being mathematical and starts becoming managerial.
So what is the point of all this?
When implementing manufacturing scheduling using tools like SAP ePPDS, the real work is not in clicking buttons. It is in deciding what you are optimising for.
- Are you trying to minimise total setup time because setup is economic waste?
- Are you trying to maximise utilisation of a bottleneck resource, like an oven during Friday lunch hours?
- Are you trying to reduce lateness, meaning the scheduled finish time must not exceed the planned finish time?
These goals are often in conflict. Optimising one can damage another.
This is why analogies matter. Everyday systems like a home kitchen or a pizza shop make abstract concepts tangible. Your kitchen already teaches you forecasting, material planning, sequencing, and inventory control. How much rice to keep at home. When to reorder milk. In what order to make tea when the stove is the bottleneck.
In Part 2, we will look at how different sequencing rules, called heuristics in SAP language, make different trade-offs. We will explore what it really means to decide which order goes first, and why that decision changes everything in assembly line and job shop manufacturing.
In Part 3, we will deal with reality. What happens when the schedule collapses because a machine fails, quality rejects spike, or a critical resource disappears. Because that is where good scheduling systems are tested.
If these concepts sound familiar but rarely get discussed this clearly during implementation conversations, that is not an accident.
At Lydian, this is exactly the kind of thinking we bring into manufacturing planning and scheduling programmes. Before tools, before configurations, before algorithms.
If you want to have a practical conversation about scheduling that starts with how your factory actually works, you can reach us at lydian.nishantfadnavis.com/.