Conceptual Information Model ^?

The potentially relevant object types are:

1. orders,
2. machines,
3. input queues,
4. workers.

Potentially relevant types of events are:

1. (order) arrivals,
2. orders being pushed to an input buffer,
3. machine activity performances (processing steps),
4. (item) departures.

Conceptual Process Model ^?

Information Design Model ^?

Since the simulation model is entirely based on the pre-defined Processing Network modeling concepts of WorkObject, EntryNode, Arrival, ProcessingNode, ExitNode and Departure, there is no need to to define any object type or event type.

The initial state definition consists of an entry node, one processing node, and an exit node, as well as an initial arrival event.

Process Design Model ^?

Since the simulation model is entirely based on the pre-defined Processing Network modeling concepts of WorkObject, EntryNode, Arrival, ProcessingNode, ExitNode and Departure, there is no need to to define any event rule.

Other OES Models for the Same System/Problem/Domain

1. ServiceDesk-1: A service queue model (one service and one queue) with two statistics: maximum queue length and service utilization. The model abstracts away from individual orders and from the composition of the queue.
2. ServiceDesk-2: A service queue model (one service and one queue) with one statistic: the Mean Response Time, which is the average length of time a order spends in the system from arrival to departure. For recording their arrival time, individual orders are represented explicitly in a waitingCustomers queue.
3. ServiceDesk-3: A service queue model where the service is modeled as an activity with the machine as its resource, for which the utilization statistics is computed automatically.
4. ConsecutiveServices: An activity-based service queue model of two consecutive service providers with order waiting lines.
5. ProcessingNetwork-1: A service queue model where service providers are modeled as processing nodes (with input queues) within a processing network that has an entry node and an exit node for arriving and departing orders. The model is based on the pre-defined Processing Network concepts: WorkObject, Arrival, EntryNode, ProcessingNode and ExitNode, such that processing objects 'flow through the system'.

Similar Models Implemented with Other Frameworks

1. Queueing_Simulation_Discrete_Event: This NetLogo simulation uses NetLogo's tick-advance primitive to advance simulation time by non-integral amounts. However, NetLogo's standard ticks display is unable to display non-integral values, so a custom ticks display has to be programmed. Copyright 2010, Nick Bennett.