09/08/2026
🎓 SIMULATION SCHOOL — Lesson 1
What discrete event simulation actually is
Skip the textbook definition. Here's the working one:
A discrete event simulation models your operation as things that happen at specific moments — a part arrives, a machine finishes, a nurse becomes available — instead of as an average.
That distinction is the whole ballgame.
Spreadsheets model averages. Averages hide the thing that actually hurts you: variability. Your average cycle time is fine. Your Tuesday-after-a-long-weekend cycle time is not, and that's the one that blows the delivery date.
What a DES model lets you do:
→ Watch queues form and drain in a virtual copy of your operation
→ Find the bottleneck that moves when you fix the first one
→ Test a change 500 times before you test it once for real
→ Put a number on risk instead of a gut feel
Where teams see it pay off: greenfield layouts, brownfield debottlenecking, staffing models, capacity commitments you have to sign your name to.
Simio's own reported range across implementations: 15–30% savings on implementation cost, 10–25% operational efficiency gains.
Lesson 1 question: When did your team last test a major operational change before implementing it?
Start with the fundamentals: https://hubs.la/Q04wXmtS0
