Object Realization or Object Runspace
Once a simulation run is started, Object Instances are represented with object realizations. Object realizations hold the state
values for that object instance. Each realization of an object instance is unique because of its unique combination of state and
function values.
All objects have a fixed runspace. A fixed runspace is the physical X,Y,Z location where an object instance is created once a run is
started and is located where the object instance was placed in the Facility window. Dynamic Objects are created at this location
and then are transferred to another location. Below, Vehicle1’s fixed runspace is located at the bottom left hand corner of the
screen, the stationary vehicle labeled Vehicle1.
In the case of dynamic objects, there is also a dynamic runspace created to represent the number in system for a particular object
instance. Each dynamic runspace has independent values for states and functions. You can see the three dynamic runspace
instances of Vehicle1 moving throughout the system. Each of these three vehicles have different X,Y,Z locations, they are doing
different tasks – one of them is going to pick up an entity while another is carrying an entity to its destination – and therefore have
different values for their Destination, RideC apacityRemaining function, etc.