WEBVTT

00:00.000 --> 00:01.840
Say you’re modeling a hamburger stand,

00:01.860 --> 00:07.070
and you need to show the product moving through it, from the freezer to the customer.

00:07.620 --> 00:12.160
If you’ve taken a simulation course, you probably learned to make every burger an entity,

00:12.180 --> 00:16.070
and the model keeps track of where each one is through time.

00:16.580 --> 00:18.070
Discrete rate works differently.

00:18.620 --> 00:20.970
It doesn't track where each burger is.

00:21.260 --> 00:23.790
It tracks how fast each node is running.

00:24.080 --> 00:31.370
Here's a small line with three steps, defrost, cooker and seasoning, and each one has a rate.

00:31.730 --> 00:36.860
The cooker could handle a quarter of a burger a minute, but it's only running at 0.20.

00:37.280 --> 00:40.060
It can't cook faster than defrost feeds it.

00:40.310 --> 00:45.250
So in a rate model, how fast a node runs depends on the nodes around it.

00:45.810 --> 00:49.090
Between the cooker and seasoning there's room for five burgers.

00:49.590 --> 00:54.920
They come in at 0.20 and go out at 0.18, so that space slowly fills.

00:55.450 --> 00:59.540
The model works out when it'll be full, at minute 250, directly,

00:59.560 --> 01:02.890
instead of stepping through every event to get there.

01:03.280 --> 01:08.360
At 250 it fills up, and the cooker has to slow down to match seasoning.

01:08.840 --> 01:13.860
At 1,000, the next buffer fills, and defrost slows down too.

01:14.270 --> 01:21.020
So the slowest step ends up setting the pace for the whole line, all the way back upstream.

01:21.410 --> 01:24.310
And that's really all a rate model is.

01:24.700 --> 01:30.380
You've got nodes with rates, buffers that fill or drain at the difference between them,

01:30.400 --> 01:35.590
and interrupts, like a breakdown, which is just a rate dropping to zero.

01:36.270 --> 01:37.700
There's a side effect, too.

01:38.080 --> 01:41.650
The discrete-event version followed every one of the 300 burgers,

01:41.670 --> 01:45.190
and that took 2,993 events.

01:45.700 --> 01:48.950
The rate version ran the whole thing on six events.

01:49.520 --> 01:54.370
Andy Siprelle published the first discrete rate simulation engine back in 1995,

01:54.390 --> 01:57.890
and most simulation courses still don't cover it.

01:58.170 --> 02:02.080
Everything you just saw runs free in your browser, if you want to try it.

02:02.270 --> 02:06.220
And if the line you want to model is a high-speed,

02:06.240 --> 02:09.460
high-volume manufacturing line, that’s what ReliaSim is built for.

02:09.480 --> 02:14.760
It uses the same method, with the ways machines fail worked out in detail.
