Welcome to
Module 2
Handa kana ba?
Module 2:
The Simulation
The Role of Simulation in
System Analysis and
Improvement
1. Understanding the Operation of Complex Systems
Some systems are so intricate that gaining a clear understanding of their
behavior and internal interactions is nearly impossible without a dynamic
model. In such cases:
Static observation is insufficient. Stopping the system or analyzing
components individually does not reveal how the system functions as a
whole.
Dynamic modeling becomes essential. Simulation provides a
comprehensive, interactive representation of how components interact in
real-time, allowing deeper insight into system behavior.
2. Improving System Performance through Policy Development
Simulation is a powerful tool for improving the efficiency and
effectiveness of existing systems through strategic policy adjustments. These
improvements typically focus on:
Operating Policies: Modifying scheduling priorities, job routing, or task
sequencing to enhance performance.
Resource Policies: Adjusting staffing levels, shift patterns, or break
schedules to optimize resource use.
By simulating these changes, organizations can assess the potential
impact before implementing them in the real system.
3. Testing New Concepts or Systems Before Implementation
Before investing in new systems or technologies, simulation can be used to:
Evaluate performance of proposed systems. Simulation helps determine how new
equipment, processes, or workflows will function under different conditions.
Reduce financial risk. The cost of developing a simulation model is often minimal compared
to the capital required for full system implementation.
Refine system design. Simulation helps in fine-tuning configurations and layouts to ensure
maximum efficiency.
Industry Practice: Many companies now require vendors to provide simulation models of
proposed equipment or systems.
4. Experimenting Without Disrupting the Real System
Certain systems are too critical or sensitive to allow for direct
experimentation. In these cases, simulation offers a safe and effective
alternative:
Non-intrusive experimentation: Simulation enables testing of new
policies or resource changes without affecting real-world operations.
Critical system application: For example, security checkpoints at
airports cannot be disrupted for experimentation due to safety and
operational concerns. Simulation allows for safe testing and analysis in such
scenarios.
Kinds of Systems
1. Discrete vs. Continuous Systems
Discrete Systems
● Change state at specific points in time.
● Events occur only at predefined times (e.g., arrival of a customer,
completion of a task).
● Example: A bank queue where customer arrivals and service
completions happen at distinct times.
Continuous Systems
● Change continuously over time.
● The state of the system evolves smoothly without distinct event
2. Stochastic vs. Deterministic Systems
Stochastic Systems
● Contain elements of randomness or uncertainty.
● Output can vary even with the same initial conditions.
● Example: Imagine a vending machine. If you put ₱20 and press the
button for bottled water, you’ll always get the same bottled water. No
surprises.
Deterministic Systems
● Operate without randomness.
● Given the same initial conditions, the outcome will always be the same.
3. Static vs. Dynamic Systems
Static Systems
● Do not change over time.
● Often represent a system at a single point in time.
● Example: A photograph or a balance sheet.
Dynamic Systems
● Evolve and change over time.
● Their current state depends on previous states and possibly future
actions.
● Example: A weather system or traffic network.
4. Physical vs. Abstract Systems
Physical Systems
● Tangible and made of material components.
● Can be seen, touched, and measured.
● Example: A car, a computer, or a building.
Abstract Systems
● Conceptual or theoretical models.
● Consist of ideas, formulas, or logical relationships.
● Example: Mathematical models, algorithms, or economic theories.
5. Causal vs. Non-Causal Systems
Causal Systems
● Output depends on present and past inputs only.
● Behavior is time-ordered and realistic in practical systems.
● Example: A heater that responds to current and past temperature readings.
Non-Causal Systems
● Output depends on future inputs.
● Often used in theoretical studies, not physically realizable in real-time systems.
● Example: A system that reacts to tomorrow's temperature today.
6. Linear vs. Non-Linear Systems
Linear Systems
● Follow the principles of superposition and homogeneity.
● Responses are directly proportional to inputs.
● Example: Electrical circuits with resistors, capacitors, and inductors.
Non-Linear Systems
● Do not follow superposition.
● Responses can vary greatly with input; may have multiple operating points.
● Example: Population growth models or chaotic weather systems.
Basic Simulation Model
Concepts
1. Basic Simulation Model Components
a. Entities
● Definition: Entities are the items or objects that move through the system and cause
changes to its state.
● In service systems, an entity is often a person, such as a customer, patient, or passenger.
● However, entities can also be non-human objects, such as parts in a factory, documents in
an office, or packets in a network.
Example:
In a customer service center, the customers are the entities. Their arrival, waiting, and service
affect the system’s performance.
1. Basic Simulation Model Components
b. Queues
● A queue is the simulation term for a line or waiting area.
● Entities wait in a queue when all resources are busy and cannot process them immediately.
● Most systems use a First-In, First-Out (FIFO) rule, meaning the first entity to arrive is the first to be served.
Key Points:
● Once an entity enters a queue, it usually cannot leave until it has been processed.
● Queue behavior is critical in service systems and impacts customer satisfaction and system efficiency.
Example:
In a hospital emergency room, patients (entities) may wait in a queue to see a doctor (resource).
1. Basic Simulation Model Components
c. Resources
● Resources are the servers or workers in the system that process entities.
● A resource can be in one of two basic states:
○ Idle: The resource is available, but no entity is waiting.
○ Busy: The resource is actively serving an entity.
In more complex models:
● Resources can be temporarily inactive (e.g., on a break) or failed (e.g., broken machinery needing repair).
Example:
A cashier at a grocery store is a resource. When serving a customer, the cashier is busy; when no customer is present, the cashier
2. Simulation Event Lists
● The simulation event list keeps track of all events during a simulation run.
● An event is anything that affects the state of the system.
● Common events:
○ Entity arrival to the queue.
○ Start of service for an entity.
○ End of service and entity exit from the system.
● Events change:
○ The number of entities in the system.
○ The status of resources (idle ↔ busy).
3. Measures of Performance Statistics
a. System Time
● Total time an entity spends in the system.
● Starts: When the entity enters the queue.
● Ends: When the entity exits the system after service.
b. Queue Time
● Time an entity waits in the queue only.
● Preferred in customer service systems because it reflects waiting time, often seen as the most critical factor for
customer satisfaction.
3. Measures of Performance Statistics
c. Time-Average Number in Queue
● A time-dependent statistic.
● Measures the average number of entities in the queue over a time period.
● Although the queue has a whole number of entities at any moment, the average over time may be a fraction.
d. Utilization
● Also a time-dependent statistic.
● Indicates how much time a resource is:
● Idle = utilization level 0
● Busy = utilization level 1
● The duration of each state is affected by the arrival and service rates of entities.
