The Basic Process Panel
Flowchart modules are the set of objects that are placed in the model window to describe
the simulation process.
This module is intended as the starting point for entities in a simulation model. Entities arecreated using a schedule or based on a time between arrivals. Entities then leave themodule to begin processingthrough the system. The entity type is specified in thismodule.
The start of a part’s production in a manufacturing line
A document’s arrival (e.g., order, check, application) into a business process
A customer’s arrival at a service process (e.g., retail store, restaurant, information desk)
This module is intended as the ending point forentities in a simulation model. Entity statistics may be recorded before the entity is disposed.
Parts leaving the modeled facility
The termination of a business process
Customers departing the store
This module is intended as the main processing method in the simulation. Options
For seizing and releasing resource constraints are available.Additionally, there is
the option to use a “submodel” and specify hierarchical user-defined logic. The
process time is allocated to the entity and may be considered to be value added,
non-value added, transfer, wait, or other. The associated cost will be added to the
Machining a part
Reviewing a document for completeness
This module allows for decision-making processes in the system. It includes options to make decisions based on one or more conditions (e.g., if entity type is Gold Card) or based on one or more probabilities (e.g., 75%, true; 25%, false). Conditions can be based on attribute values (e.g., Priority), variable values (e.g., Number Denied), the entity type, or anexpression (e.g., NQ(ProcessA.Queue)).
There are two exit points out of the Decide module when its specified type is either
2-way by Chance or 2-way by Condition. There is one exit point for “true” entities
and one for “false” entities. When the N-way by Chance or by Condition type is
specified, multiple exit points are shown for each condition or probability and a
single “else” exit.The number of entities that exit from each type (true/false) is
displayed for 2-way by Chance or by Condition modules only.
Dispatching a faulty part for rework
Branching accepted vs. rejected checks
Sending priority customers to a dedicated process
This module is intended as the grouping mechanism within the simulation model. Batches can bepermanently or temporarily grouped. Temporary batches must later be split using the Separate module.
Batches may be made with any specified number of entering entities or may be matched together based on an attribute. Entities arriving at the Batch module are placed in a queue until the required number of entities has accumulated. Once accumulated, a new representative entity is created.
TYPICAL USESCollect a number of parts before starting processing
Reassemble previously separated copies of a form
Bring together a patient and his record before commencing an appointment
This module can be used to either copy an incoming entity into multiple entities or to split
a previously batched entity. Rules for allocating costs and times to the duplicate are alsospecified. Rules for attribute assignment to member entities are specified as well.
When splitting existing batches, the temporary representative entity that was formed is
disposed and the original entities that formed the group are recovered. The entities proceed
sequentially from the module in the same order in which they originally were added
to the batch.
When duplicating entities,...
Ler documento completo
Por favor, assinar para o acesso.