5 Factory Decisions You Should Simulate Before You Commit
Five factory decisions are worth simulating before you commit: a layout change, a fix for a bottleneck, a robot or automation investment, a capacity change for new demand, and a change to shifts. They have three things in common. They are expensive to reverse, several options look plausible, and the result depends on how machines, people, forklifts and buffers interact over time. A spreadsheet of averages cannot show that interaction. A simulation can.
Why averages fail on exactly these decisions
Most factory decisions are prepared in a spreadsheet: average cycle time, average demand, average transport time. Averages work for simple, independent steps. They fail when steps depend on each other.
Say, for illustration, that two stations in a row each have an average cycle time of 55 seconds against a takt of 60 seconds. On paper, the line has spare capacity. On the floor, both stations also serve a second product, the order sequence puts two long jobs back to back, and a forklift brings pallets in batches. A queue forms that the spreadsheet never showed. Output at the end of the shift is below plan, even though no single station is "too slow".
A simulation runs the same line over a whole week of orders, with fixed cycle times and with transport, buffers and shifts included (see Averages vs simulation over time). It shows where queues form, how long parts wait and what the line delivers, which is what each of the five decisions below depends on.
1. A layout change or a new hall
A drawing tells you whether a new layout fits. Whether it runs well is a different question. Routes that look short can cross in a busy aisle. A buffer that was removed to save space can leave semi-finished parts waiting for a forklift between processes.
Compare each layout variant with today's layout on output per day, material flow time, waiting time between processes and forklift or cart load. Every variant needs the same order mix and the same shift rules, or the comparison is unfair. We show how to set this up in How to Compare Layout Variants Without Guesswork.
2. Fixing a bottleneck
When a bottleneck gets fixed, the constraint usually moves somewhere else. A faster machine can flood the next buffer, starve a station downstream, or push more pallets onto a shared forklift. The improvement then delivers less output than the business case promised.
In the model, look at where work queues before and after the fix and how utilization changes at the neighboring stations. Judge the result by the output of the whole line. Then run the model again after each fix to see where the constraint moves next. The method is described in How to Find Production Bottlenecks Before They Happen.
3. Buying a robot or automating a station
A robot is usually justified by its cycle time. Whether it delivers that output depends on what happens around it: material supply, the buffer in front, the station after it, and who loads and unloads it.
A plastic injection molding company in central Poland, working three shifts, analyzed automating several stations on one line. The simulation found the bottleneck at a manual step by the first operator: 90 seconds of activity and 98 seconds of waiting. Replacing that operator with an autonomous cart increased efficiency by over 100%, which created the conditions for the investment to be economically viable. The problem was waiting, not working time, and no cycle time sheet showed it.
Here the model should run the line with and without the robot and report output, waiting time and working time for each, along with alternative automation variants such as automated transport. More detail is in Before You Buy a Robot, Simulate It First.
See these decisions in real plants
Several of the cases behind this list, from relocating machines into a new hall to automating a molding line, are written up with the numbers DBR77 Digital Twin produced.
4. Adding capacity for a demand change
When demand rises or the product mix shifts, the usual answers are a new machine, a new line, an extra shift or a bigger hall. Each option also changes transport routes, buffer needs and the load on shared resources.
A car lamp manufacturer in southern Poland added a new production hall and had to relocate machines without interrupting production. The simulation showed that extended transport routes were the main source of production losses, that the final machine layout differed from the initial assumption, and that the right relocation sequence allowed some processes to run in parallel. None of this was visible in a capacity table.
Test output under several demand scenarios beyond the expected one, and track buffer levels, transport load and the order of the changes. See How to Test Capacity Before the Next Demand Shift.
5. Changing shifts
Moving from two shifts to three, or changing when a shift starts, looks like simple arithmetic. In practice, output depends on what is waiting at each station when work arrives and which shared resources the extra shift loads. A station shared by two products can become the bottleneck at peak times, while the capacity on paper looks sufficient.
For each shift variant, the model should show output, waiting time and the utilization of each station. Run with your real order mix, it tells you whether the extra shift adds output or only adds cost. See How to Use a Digital Twin to Test Shift and People Decisions.
How to choose your first scenario
You do not need to simulate everything. Start with the decision that is closest, most expensive and hardest to reverse. The table below summarizes what averages miss in each case.
| Decision | What averages miss | What to compare in the model |
|---|---|---|
| Layout change or new hall | Waiting for transport, crossing routes | Output per day, flow time, waiting, forklift load |
| Fixing a bottleneck | Where the constraint moves next | Queues and utilization before and after the fix |
| Robot or automation | Waiting around the new station | Output and waiting with and without automation |
| Capacity for new demand | Buffers, routes, order of changes | Output under several demand scenarios |
| Shifts | What is waiting when work arrives | Output, waiting and station utilization |
Small, reversible changes do not need a model. If you can move a rack on Saturday and move it back on Monday, try it on the floor. Simulate when a wrong choice costs a rebuild, a lost ramp-up or a machine that sits idle.
FAQ
Which decision should we simulate first?
The one that is coming up soonest and is hardest to reverse. For most plants, that is a layout change, a capacity investment or an automation project already on the agenda.
Do we need a model of the whole plant for these decisions?
No. Model the area where the change happens, plus anything that shares forklifts, buffers or people with it. You can extend the model for the next decision.
Can one model answer several of these questions?
Yes. Once the material flow of an area is modeled, the same model can test a layout variant, a robot, an extra shift or a new demand scenario. That reuse is what makes a model a digital twin.
What do we need to start simulating a decision?
Nominal times are enough to start. Enter routings, stations and times by hand, or bring them in by import (import scope to be confirmed). The scope is set by the decision and the options on the table.
Conclusion
Look at the investment and change plans for the next twelve months and mark which of them fall into the five types above. For the one that is closest and hardest to undo, write down the options already on the table and the measure that should decide between them. That is the brief for a first model.
Have one of these decisions on the table?
Whether it is a robot cell, a third shift or a new hall, the demo shows how DBR77 Digital Twin lays out options like these side by side. Then we can discuss how your decision would be modeled.
Sources
- DBR77, Case study: Development of an automation concept (summary on this site)
- DBR77, Case study: Plant expansion plan (summary on this site)
- DBR77, Case study: Production line design (summary on this site)
- DBR77 Digital Twin, Averages vs simulation over time
Want to test a decision from your plant?
Describe the decision to a DBR77 expert and we will show how DBR77 Digital Twin compares the options on output, waiting time and transport load.
Questions
Have a question about this topic?
Tell us what it is about. We will reply within one business day.
Digital Twin newsletter
Short notes on testing layout and flow decisions on a model, and news from DBR77 Digital Twin. You can unsubscribe at any time.