Operation:
Think of an Oven as a processor of discrete batches of stuff.
The Oven opens its doors; fills (either to capacity or until it is time to close the door); bakes its contents for a time (as defined by its outflow logic); then unloads them in an instant.
Operation of the Oven can be arrested.
Only a single Uniflow can flow into an Oven.
The inflow to an Oven can come from a cloud, a Reservoir or a Queue.
Modeling Dialog Operations: The Oven's Modeling Dialog takes one
of two forms, depending on the nature of the inflow to the Oven.
If the inflow comes from a Reservoir or cloud, the dialog will look like Figure 4-36.
|
Figure 4-36 |
If the inflow comes from a Queue, the dialog will look like Figure 4-37.
|
Figure 4-37 |
|
|
Notes:
Use long fill times, "One at a time," and small capacities to represent capacity constrained situations.
Check the "DT" check box, select "One at a time," and use a large Capacity to represent a processor that takes only the "next" item from the upstream Queue.
Outflows from Queues can be designated as "overflow." When gridlock has occurred in one Oven, the overflow can direct the contents of the Queue to a larger-capacity Oven.
Outflow Dialog Operations: A single, Uniflow
outflow is allowed. Cook time is an attribute of the Oven outflow. Cook
time is sampled each time the Oven closes its door. When Cook time has
expired, the Oven will spit out its entire contents in an instant. At
all other times the Oven's outflow will be zero.
Basic operations in the Oven outflow dialog are shown in Figure 4-38. Figure 4-39 shows the Oven outflow dialog, when Arrest is in effect.
|
Figure 4-38 |
|
|
|
Figure 4-39 |