What the simulator tells you
Peak 15-minute burst pace converts the busiest block into an hourly equivalent. It is a stress-test number, not a claim that the rush lasts a full hour.
Modeled backlog carries unserved demand into the next block. This is useful when two ovens with similar full-hour output behave differently during a compressed rush.
Queue-clear time translates the largest backlog into minutes of oven work at the candidate sustained rate. A result near zero means the modeled oven keeps up with the entered blocks; a larger number tells you how much demand can stack up.
Use POS data when possible. Choose several representative busy services, count pizzas in 15-minute blocks, and test the repeated high pattern rather than only one exceptional holiday spike.
Why one pizzas/hour number can miss the problem
A generic capacity figure cannot know your six actual rush blocks or the candidate oven rate you are considering. This simulator turns those inputs into a shareable queue model you can compare across equipment options.
Important limits
This is a planning screen, not queueing-engineering software. It does not know the exact chamber layout, pizza diameter, bake-cycle timing, heat recovery, loading pattern, operator skill, downtime, utility limits, ventilation listing or code requirements of a real appliance. Use it to identify capacity risk, then verify shortlisted equipment with manufacturer data and qualified local professionals.
Turn the rush into an oven-class target
After stress-testing your 15-minute pattern, use your defensible peak-hour target in the main planner to compare oven classes.
Open the capacity planner