SMS Module 1
SMS Module 1
MODULE 1
Introduction to simulation
1. Simulation:
Simulation is the imitation of the operation of a real world process or system over time.
Simulation models help us to study the behavior of system as it evolves
models keeps the set of assumption concerning the operation of the system
Assumptions are expressed in terms of mathematical, logical and symbolic
relationship between the entities or object of interest of the system.
Simulation modeling can be used both as an analysis tools to predict the
performance of the new system and also predict the effect of changes to existing
system.
simulation can be done by hand or computer its keeps the history of system
Simulation produce the set of data is used to estimate the measures of
performance of system.
• If there is not enough time or the people are not available, simulation is not appropriate.
• If managers have unreasonable expectation say, too much soon – or the
power ofsimulation is over estimated, simulation may not be appropriate.
• If system behavior is too complex or cannot be defined, simulation is not appropriate
1. Manufacturing Applications
Analysis of electronics assembly operations
Design and evaluation of a selective assembly station for high-precision scroll
compressor shells
Comparison of dispatching rules for semiconductor manufacturing using large-
facility models
Evaluation of cluster tool throughput for thin-film head production
Determining optimal lot size for a semiconductor back-end factory
Optimization of cycle time and utilization in semiconductor test manufacturing
Analysis of storage and retrieval strategies in a warehouse
Investigation of dynamics in a service-oriented supply chain
Model for an Army chemical munitions disposal facility
2. Semiconductor Manufacturing
Comparison of dispatching rules using large-facility models
The corrupting influence of variability
A new lot-release rule for wafer fabs
Assessment of potential gains in productivity due to proactive retile management
Comparison of a 200-mm and 300-mm X-ray lithography cell
Capacity planning with time constraints between operations
300-mm logistic system risk reduction
3. Construction Engineering
Construction of a dam embankment
Trenchless renewal of underground urban infrastructures
Activity scheduling in a dynamic, multi project setting
Investigation of the structural steel erection process
Special-purpose template for utility tunnel construction
4. Military Application
Modeling leadership effects and recruit type in an Army recruiting station
Design and test of an intelligent controller for autonomous underwater vehicles
Modeling military requirements for non war fighting operations
Using adaptive agent in U.S Air Force pilot retention
5. Logistics, Transportation, and Distribution Applications
Evaluating the potential benefits of a rail-traffic planning algorithm
Evaluating strategies to improve railroad performance
Parametric modeling in rail-capacity planning
Analysis of passenger flows in an airport terminal
Proactive flight-schedule evaluation
Logistics issues in autonomous food production systems for extended-duration
space exploration
Sizing industrial rail-car fleets
Product distribution in the newspaper industry
Design of a toll plaza
System environment:
A system is often affected by changes occurring outside the system,Such changes
are said to occure in the system environment.
Continuous system:
Is one in which the state variable change only at a discrete set of points in time.
The bank is an example, since the state variable the number of customer in the
bank changes only when a customer arrives or when the service provided a
customer is completed.
7. Continuous system:
Is one in which the state variable change continuous over time.
head of water behind a dam, during and for some time after a rain storm water
flow into the lake behind the dam.
systems.
1. Problem formulation:
Every study should begin with a statement of the problem.
If the statement is provided by the policy makers or those that have the problem, The
analyst must ensure that the problem being described is clearly understood
If the problem statement is being developed by the analyst, it is important that the policy
makers understand and agree with the formulation.
3. Model Conceptualization:
The construction of a model of a system is probably as much art as science.
The art of modeling is enhanced by ability to have following:
To abstract the essential features of a problem.
To select and modify basic assumptions that characterizes the system.
To enrich and elaborate the model until a useful approximation results.
4. Data Collection:
There is a constant interplay between the construction of the model and the collection
of the needed input data.
As complexity of the model changes the required data elements may also change.
Since data collection takes such a large portion of the total time required to perform a
simulation it is necessary to begin it as early as possible.
5. Model Translation:
Since most real world system result in model that require a great deal of information
storage and computation, the model must be entered into a computer recognizable format.
we use term program even though it is possible to accomplish the desired result in many
instances with little or no actual coding.
6. Varified:
7. Validated:
validation is the determination that a model is an accurate representation of the real
system.
Is usually achieved through the calibration of the model an iterative process of comparing
the model to actual system behavior and using the discrepancy between the two and the
insights gained to improve the model.
This process is repeated until model accuracy is judges acceptable.
8. Experimental Design:
The alternatives that are to be simulated must be determined. For each system design,
decisions need to be made concerning
Based on the analysis of runs that have been completed. The analyst determines if
additional runs are needed and what design those additional experiments should follow.
12. Implementation:
Success depends on the previous steps. If the model user has been thoroughly involved and
understands the nature of the model and its outputs, likelihood of a vigorous implementation is
enhanced.
Simulation is often used in the analysis of queuing models. In a simple typical queuing
model, shown in
In the single-channel queue, the calling population is infinite; that is, if a unit leaves
the calling population and joins the waiting line or enters service, there is no
change in the arrival rate of other units that may need service.
Arrivals for service occur one at a time in a random fashion; once they join the
waiting line, they are eventually served.
The system capacity has no limit, meaning that any number of units can wait in line.
Finally, units are served in the order of their arrival (often called FIFO: first in,
first out) by a single server or channel.
Arrivals and services are defined by the distributions of the time between arrivals and
the
distribution of service times, respectively.
The state of the system: the number of units in the system and the status of the server,
busy or idle.
An event: a set of circumstances that cause an instantaneous change in the state of the system.
In a single-channel queueing system there are only two possible events that can
affect the state of the system.
The simulation clock is used to track simulated time.
The arrival event occurs when a unit enters the system. The flow diagram for the
arrival event is shown in
The unit may find the server either idle or busy; therefore, either the unit begins
service immediately, or it enters the queue for the server. The unit follows the course of
action shown in fig 2.4.
If the server is busy, the unit enters the queue. If the server is idle and the queue is
empty, the unit begins service. It is not possible for the server to be idle and the queue
to be nonempty.
After the completion of a service the service may become idle or remain busy with
the next unit. The relationship of these two outcomes to the status of the queue is
shown in fig
2.5. If the queue is not empty, another unit will enter the server and it will be busy
Problems:
Standard Formulas:
1. Average waiting time(i.e customer wait)=total time customer wait in queue / Total number of
customer
3. Probability of idle server(idle time of server)=total idle time of server / total run time of
simulation
6. Average waiting time those who wait in queue=total time customer wait in queue/total
number of customer who wait
7. Average time customer spend In the system=Total time customer spend in system/total
number of customer
General Principles
1. Discrete-event simulation
The basic building blocks of all discrete-event simulation models: entities and attributes, activities and
events.
A system is modeled in terms of
o Its state at each point in time
o The entities that pass through the system and the entities that represent system resources
o The activities and events that cause system state to change.
Discrete-event models are appropriate for those systems for which changes in system state occur
only at discrete points in time.
This chapter deals exclusively with dynamic, stochastic systems (i.e., involving time and containing
random elements) which change in a discrete manner.
1. System: A collection of entities (e.g., people and machines) that together over time to accomplish one
or more goals.
2. Model: An abstract representation of a system, usually containing structural, logical, or mathematical
relationships which describe a system in terms of state, entities and their attributes, sets, processes,
events, activities, and delays.
3. System state: A collection of variables that contain all the information necessary to describe the system
at any time.
4. Entity: Any object or component in the system which requires explicit representation in the model (e.g., a
server, a customer, amachine).
5. Attributes: The properties of a given entity (e.g., the priority of a v customer, the routing of a job
through a job shop).
6. List: A collection of (permanently or temporarily) associated entities ordered in some logical fashion
(such as all customers currently in a waiting line, ordered by first come, first served, or bypriority).
7. Event: An instantaneous occurrence that changes the state of a system as an arrival of a new customer).
8. Event notice: A record of an event to occur at the current or some future time, along with any
associated data necessary to execute the event; at a minimum, the record includes the event type and the
event time.
9. Event list: A list of event notices for future events, ordered by time of occurrence; also known as
the future event list (FEL).
10. Activity: A duration of time of specified length (e.g., a service time or arrival time), which is
Dept. of CSE, CITNC, Bengaluru Dr. Mamatha C M
SYSTEM SIMULATION AND MODELING
The Event-Scheduling/Time-AdvanceAlgorithm
The mechanism for advancing simulation time and guaranteeing that all events occur
in correct chronological order is based on the future event list (FEL).
Future Event List (FEL)
o To contain all event notices for events that have been scheduled to occur at a future time.
o To be ordered by event time, meaning that the events are arranged chronologically; that
is, the event timessatisfy.
o Scheduling a future event means that at the instant an activity begins, its duration is computed
or drawn as a sample from a statistical distribution and the end-activity event, together with
its event time, is placed on the future event list.
The sequence of actions which a simulator must perform to advance the clock system snapshot is called
the event- scheduling/time-advance algorithm.
The system snapshot at time t=0 and t=t1 (VIP VTU question)
Event-scheduling/time-advance algorithm
Step 1. Remove the event notice for the imminent event
(event 3, time t\) from FEL
Step 2. Advance CLOCK to imminent event time
(i.e., advance CLOCK from r to t1).
Step 3. Execute imminent event: update system state, change entity attributes, and set membership as needed.
Step 4. Generate future events (if necessary) and place their event notices on PEL ranked by event time.
(Example: Event 4 to occur at time t*, where t2 < t* < t3.)
Step 5. Update cumulative statistics and counters.
The system consists of those customers in the waiting line plus the one (if any) checking out. The model has
the following components:
System state (LQ (t), LS (t)), where LQ (t) is the number of customers in the waiting line, and LS (t) is
the number being served (0 or 1) at time t.
Entities: The server and customers are not explicitly modeled, except in terms of the state variables above.
Events
Arrival(A)
Departure(D)
Stopping event (E), scheduled to occur at time 60.
Event notices
(A, t). Representing an arrival event to occur at future time t
Activities
Interarrival time, Service time,
Delay Customer time spent in waiting line.
In this model, the FEL will always contain either two or three event notices.
Flow Chart for execution of arrival and departure event using time advance /Event scheduling
algorithm (vtu Question)
Question Bank