Concepts
system: collection of entities interacting together to
Discrete Event
accomplish a goal
model: an abstract representation of a system
structural / logical / mathematical relationships
Simulation Concepts
describe system in terms of state, entities, attributes,
processes, events, activities
Discrete Event Simulation system state: collection of variables to describe a system
at any time
2005-2006 Fall Term
entity: object or component in the system
attributes: properties of entities
Prof. Dr. Nadir Yücel, Asst. Prof. Dr. A. Şima Uyar
list: collection of entities ordered by first come first
serve
Example: The Able – Baker Call
Concepts
Center Problem - Definition
events: instantaneous occurrence changing the state of a system In a computer technical support center where personnel
event notices: record of events to occur take calls and provide service, the time between calls
event lists: list of event notices ranges between 1 to 4 minutes with distribution shown
ordered by time of occurrence in Table x. There are two support people: Able and
FEL: Future Events List Baker. Able is more experienced and can provide faster
activity: duration of time of specific length service than Baker. The distribution of their service
e.g. interarrival / service times times are given. Able gets a call if both are idle. The
duration may be deterministic, statistical, a function of system variables
and / or entity attributes problem is to determine how well the current
delay: activity: duration of time of unspecific length arrangement is working. To estimate system
waiting customer in a line performance, a simulation of the first 100 callers is
clock: variable representing simulated time made.
Example: The Able – Baker Call Example: The Able – Baker Call
Center Problem - Components Center Problem - Components
system state events
arrival of a call
LQ(t): no of caller waiting for service at time t
service completion by Able
LA(t): Able is idle/busy at time t (0/1) service completion by Baker
LB(t): Baker is idle/busy at time t (0/1) activities
entities interarrival time of calls (as defined in table)
service time by Able (as defined in table)
callers and servers not needed to be represented service time by Baker (as defined in table)
explicitly
delays
represent in terms of state variables a caller waits in queue until Able or Baker is free
1
Definition Event Scheduling
discrete event simulation mechanism for advancing simulation depends on FEL
modeling over time of a system whose state changes scheduling a future event: at start of activity
occur at discrete points in time duration determined
produces sequence of snapshots of system evolving end-activity event and its time determined
over time all placed on FEL
includes: sequence of actions a simulator / program performs to
system state at time t advance the clock and to build a new system snapshot:
FEL event-scheduling / time-advance algorithm
values of cumulative statistics and counters
Event-Scheduling / Time-Advance
Discrete Event Simulation
Algorithm
step 1: remove event notice for imminent event from world views: orientation to develop model
future events list (FEL) event-scheduling world view
step 2: advance CLOCK to imminent event time process-interaction world view
step 3: execute imminent event: update system state, activity-scanning world view
change entity attributes
step 4: generte future events (if necessary) and place the
event notices on FEL, ranked by event time
step 5: update cummulative statisics and counters
Event-Scheduling World View Process-Interaction World View
concentrate on concentrate on processes
proces: life cycle of one entity
events
process: time sequenced list of events, activities and
effect of events on system delays, including demands for resources, that define the
life cycle of one entity as it moves thorugh the system
has variable time advance
define simulation model in terms of
entities / objects
their life cycle as they flow through system
demand resources
wait in queues
...
has variable time advance
2
Process-Interaction World View Activity-Scanning World View
delay activity concentrate on
time
arrival event begin service event end service event activities of a model
conditions that allow an activity to begin
interaction
at each clock advance conditions for all activites
activity
checked
delay
time arrival event begin service event end service event if conditions true, activities started
slow runtime
mixed approach
Two interacting customer processes in a single-server queue
A Simulation Example – Simulation
of a Barber Shop
ta probability die
assume data on interarrival rates
and service times have been 5 1/6 1
collected: 10 2/6 2, 3
ta: interrarival time
ts: service time 20 3/6 4, 5, 6
roll a die to get random numbers
barber shop opens and starts ts probability die
serving customers at 8:00am 30 1/6 1
only 1 barber, infinite waiting space
assume no breaks 20 1/6 2
do a hand-simulation of the barber 15 4/6 3, 4, 5, 6
shop and give a simulation table to
show the progress of simulation
simulate for 10 customers also look at:
simulate for 4 hours • max / average queue length
• max / average waiting time for customers
• max / average idle time for barber
