
5 Designing Paths for Entities
5-2
Role of Paths in SimEvents Models
In this section...
“Definition of Entity Paths” on page 5-2
“Implications of Entity Paths” on page 5-2
“Overview of Routing Library for Designing Paths” on page 5-3
Definition of Entity Paths
An entity path is a connection from an entity output port to an entity input port, depicted
as a line connecting the entity ports of two SimEvents blocks. An entity path represents
the equivalence between an entity's departure from the first block and arrival at the
second block. For example, in the model shown below, any entity that departs from the
FIFO Queue block's OUT port equivalently arrives at the Single Server block's IN port.
The existence of the entity path does not guarantee that any entity actually uses the
path; for example, the simulation could be so short that no entities are ever generated.
Even when an entity path is used, it is used only at a discrete set of times during the
simulation.
Implications of Entity Paths
In some models, you can use the entity connection lines to infer the full sequence of
blocks that a given entity arrives at, throughout the simulation.
In many discrete-event models, however, the set of entity connection lines does not
completely determine the sequence of blocks that each entity arrives at. For example, the
Comentarios a estos manuales