Monte Carlo vs discrete rate simulation: when is a spreadsheet enough?
Monte Carlo simulation is often the first tool an engineer reaches for: it fits in a spreadsheet and handles uncertainty well. It has one structural blind spot, which is that it has no clock. Here is when that matters for manufacturing questions, and when it doesn't.
What Monte Carlo simulation is
The Monte Carlo method was developed in the 1940s at Los Alamos, associated with Stanislaw Ulam, John von Neumann and Nicholas Metropolis. The idea is simple. Describe each uncertain input with a probability distribution, draw one value from each, compute the result, and repeat thousands of times. The results approximate the output's distribution.
In most manufacturing and business use, Monte Carlo is static. Each trial is a separate calculation with no simulated time inside it: no moments, only a formula.
What a dynamic simulation adds
A dynamic simulation has a clock and a state that evolves. The level in a buffer at 10:05 depends on its level at 10:04, on whether the upstream machine was running, and on whether the downstream machine was taking material. Discrete event, discrete rate and continuous simulation are all dynamic. They differ in how they move the clock, as covered in simulation methodologies.
A terminology note. Dynamic stochastic models also use random sampling: failure times and repair times are drawn from distributions as the model runs, and the model is replicated to get a range of results. So "Monte Carlo vs discrete event" is not really a contest between random and non-random. The difference is whether time and state are part of the model.
| Aspect | Static Monte Carlo | Dynamic simulation (discrete rate or discrete event) |
|---|---|---|
| Simulated clock | None | Yes: event to event |
| State carried forward | No, each trial is independent | Yes: buffer levels, machine states, queues |
| Randomness | Sampled inputs per trial | Sampled failures, repairs and arrivals during the run, plus replications |
| Buffers, blocking, starving | Cannot be represented | Represented directly |
| Build effort | Hours, in a spreadsheet | More: needs structure, logic and data |
| Typical output | Distribution of a total | Distributions over time: throughput, downtime, buffer behavior, where losses occur |
Where the static view breaks: a two-machine example
Take two machines in series, each available 90% of the time. A Monte Carlo spreadsheet samples each machine's availability and multiplies them. On average the line is available about 0.9 × 0.9 = 81% of the time. That arithmetic is correct only if every stop on either machine stops the whole line at once, and the two machines fail independently.
Now put a buffer between them. When the upstream machine stops, the downstream machine keeps running from the buffer until the buffer empties. When the downstream machine stops, the upstream machine keeps filling the buffer until it is full. Whether the buffer rescues a little output or a lot depends on how long the stops last compared with how many minutes of material the buffer holds. That is a question about timing, and the formula has no place to put it.
The independence assumption is weaker than it looks, too. A machine that is blocked or starved is not running, and many failure modes only occur while a machine runs. Stops on one machine change how often its neighbors fail. A dynamic model represents that interaction; a multiplication does not.
When Monte Carlo is enough
- Independent risks. Project cost and schedule risk, supplier delays that add up, or several risks that do not interact.
- One-period totals. Annual demand against nominal annual capacity, where the question is whether the volume fits at all, not how the line behaves hour to hour.
- Separate assets. Several independent lines where a stop on one does not affect another.
- Screening. A quick sensitivity check to find which uncertain inputs matter before investing in a detailed model.
When you need a dynamic model
- Buffers and accumulation between machines, and questions about how big they should be.
- Blocking and starving, where a stop on one machine spreads up and down the line.
- Short, frequent stops, where the length of each stop, not just the total downtime, decides what is lost.
- Changeovers, schedules and sequences, where the order of events matters.
- Moving bottlenecks, where the constraint shifts as machines fail and recover.
- Any "what if we change X" question where X interacts with timing: a faster filler, a larger accumulation table, a new maintenance plan.
Discrete rate or discrete event for the dynamic model?
Both are dynamic, and both handle the interactions above. The difference is what they count as an event. Discrete event simulation typically treats each unit as an entity, so the work grows with the number of units. Discrete rate simulation treats flow as a rate that stays constant between events, so the work grows with the number of rate changes: failures, repairs, changeovers, buffers filling or emptying. On high-speed lines that makes discrete rate a natural fit. For discrete parts with routings and attributes, discrete event is the better tool. The full comparison is at discrete rate vs discrete event simulation.
Speed matters, because every design alternative needs its own set of replications. The published example: the ExtendSim model from Fischel and Lange's WSC 2020 study of a food plant was rebuilt in ReliaSim and independently validated by Tom Lange. The ReliaSim model came within 1% of both the plant's measured OEE and the original ExtendSim model (case study).
A practical sequence. Use Monte Carlo to scope the uncertainty and find the inputs that matter. If the answer depends on timing, build the dynamic model, fit its failure and repair distributions from your own event data, validate it against history, and then run the experiments.
Frequently asked questions
Is Monte Carlo simulation the same as discrete event simulation?
No. Monte Carlo simulation is static: it samples uncertain inputs and computes a result, with no simulated clock and no state carried forward. Discrete event simulation is dynamic: it moves a clock from event to event and tracks how the state of the system changes over time. The two are often combined, because a stochastic discrete event model is run for many replications and the spread of those results is summarized in a Monte Carlo fashion.
Can Monte Carlo simulation predict manufacturing throughput?
It can give a useful first estimate when machines are effectively independent, for example separate lines, or a line with no meaningful buffers where every stop halts the whole line. Once buffers, blocking and starving, changeovers or the length of stops matter, throughput depends on timing, and a static calculation cannot represent timing. That is when a dynamic model such as discrete rate or discrete event simulation is needed.
What is the difference between static and dynamic simulation?
A static simulation represents a system at a single point, or over a period treated as one lump, so time plays no role. A dynamic simulation represents how the system evolves over time, so the state at one moment depends on the state a moment earlier. Monte Carlo spreadsheet models are static; discrete event, discrete rate and continuous models are dynamic.
Do dynamic simulations use Monte Carlo methods?
Usually, yes. A stochastic dynamic model samples failure times, repair times and other random inputs as it runs, and it is replicated with different random numbers so results can be reported with a range rather than a single figure. The difference is that each replication carries state through simulated time, which a static Monte Carlo model does not.
When is a spreadsheet model good enough?
When the result is a sum or product of uncertain quantities that do not interact through time: budget and schedule risk, annual demand against nominal capacity, or independent failure risks. If the answer depends on what happens while a buffer drains, how long a stop lasts, or the order in which things occur, a spreadsheet will give a confident answer to the wrong question.
Read more
Simulation methodologies
— the main methods compared.
Discrete rate vs discrete event simulation
— the head-to-head comparison.
Digital twin vs simulation
— what a validated model is, and what a live-connected twin adds.
The three primitives
— constraints, buffers and interrupts.
ExtendSim® is a registered trademark of Andritz Inc. It is referenced here for identification only; no affiliation or endorsement is implied.