Scribd
Upload
17 views12 pages

Discrete-Event Simulation Framework

The document discusses concepts in discrete-event simulation, focusing on tracking activities and managing events in dynamic systems. It explains the creation of event notices for activities and the distinction between primary and secondary events. The example of a call center illustrates the components of a discrete-event model, including system states, entities, and events.

Uploaded by

homeimran0335
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
17 views12 pages

Discrete-Event Simulation Framework

The document discusses concepts in discrete-event simulation, focusing on tracking activities and managing events in dynamic systems. It explains the creation of event notices for activities and the distinction between primary and secondary events. The example of a call center illustrates the components of a discrete-event model, including system states, entities, and events.

Uploaded by

homeimran0335
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

Modeling and Simulation

Framework For
Discrete-event
Simulation-III

1
Concepts In Discrete-event Simulation

• This section discusses


keeping track of
activities

2
To Keep Track Of Activities

• For example, if the


current simulated time
is CLOCK = 100
minutes and an
inspection time of
exactly 5 minutes is
just beginning, then
an event notice is
created that spec­ifies
the type of event (an
end-of-inspection
event), and the event
time (100 + 5 = 1 0 5
minutes)
3
Conditional Wait

• A delay is sometimes
called a conditional
wait, an activity an
unconditional wait.
• The completion of an
activity is an event,
often called a primary
event, that is
managed by placing
an event notice on the
FEL.

4
Conditional Or Secondary Event

• The completion of a
delay is sometimes
called a conditional or
secondary event, but
such events are not
represented by event
notices, nor do they
appear on the FEL.

5
Systems Considered Here Are Dynamic

• The systems
considered here are
dynamic, that is,
changing over time.
Therefore, system
state, entity attributes
and the number of
active entities

6
Systems Considered Here Are Dynamic

• The contents of sets,


and the activities and
delays currently in
progress are all
functions of time and
are constantly
changing over time.
Time itself is
represented by a
variable called CLOCK

7
Example 3.1: Call Center, Revisited

• Consider the Able-


Baker call center
system of Example 2.2.
A discrete-event model
has the following
components:
• System state
– Lq (t): the number of
callers waiting to be
served at time t;

8
System State

– La (t): 0 or 1 to
indicate Able as
being idle or busy
at time t;
– Lg (t): 0 or 1 to
indicate Baker as
being idle or busy
at time t.

9
Entities

• Entities:
– Neither the callers
nor the servers
need to be explicitly
represented, except
in terms of the state
variables, unless
certain caller
averages are
desired

10
Events

• Events:
– Arrival event;
– Service
completion by
Able;
– Service
completion by
Baker.

11
Summary

• This Module deals


exclusively with
dynamic, stochastic
systems (i.e.,
involving time and
containing random
elements) that
change in a discrete
manner

12

You might also like