##  [Discrete Event Simulation](/discrete-event-simulation-0) 

 Definition

A computational modeling technique in which a system’s state changes only at discrete time instants triggered by instantaneous events; the model is represented by state variables and an event list, and the simulator processes events in nondecreasing time order to update state and produce performance measures.

 

 

 

 

 

 





## Principle

Principle

The system trajectory and performance metrics are fully determined by the event set, each event’s precondition and state‑update function, and the rule that events execute in chronological order; between events the state is assumed unchanged.

 

 

 

 

 





## Demonstration

Demonstration

Illustrative scenario — Manufacturing line: Situation — parts arrive stochastically and machines complete processing at discrete completion times. Recognition — modeler encodes arrivals, service-completion events, a queue state, and an event calendar. Action — simulator pops the earliest event, updates queue lengths and resource status, schedules any consequent events (next completion, next arrival) and records delays. Consequence — collected statistics (average wait, resource utilization) converge with repeated runs and identify bottlenecks for design changes.

 

 

 

 

## Misapplication

Misapplication

Treating DES as appropriate for systems whose relevant dynamics are continuous in time (e.g., heat diffusion) or replacing event scheduling by a fixed small time step without justification; the error is assuming state changes are negligible between events or that arbitrary discretization preserves event ordering and efficiency.

 

 

 

 

 





## Consequence

Consequence

When correctly applied, DES yields computationally efficient, exact (within model assumptions) simulation of systems whose changes are event-driven, enabling accurate performance estimates and capacity planning; misapplication produces biased metrics, excessive computation, or missed fast dynamics.

 

 

 

 

## Reversal

Reversal

If state changes occur continuously or events occur at such high frequency that per‑event overhead dominates, or when time‑dependent partial differential dynamics are primary, a continuous, time‑step, or hybrid simulation formalism (e.g., co-simulation with differential equations or timed/hybrid DES) becomes necessary.

 

 

 

 

 





## Boundary

Boundary

Clearly within — single- or multi‑server queueing networks, job-shop scheduling, communication packet switching where state changes occur on arrivals/completions. Boundary case — production with periodic batching plus small continuous adjustments (may require hybrid model). Clearly outside — pure continuous dynamical systems described by ODEs/PDEs without discrete instantaneous events.

 

 

 

 

 





## Semantic Tension

Semantic Tension

Discrete-event efficiency and clarity versus the need for temporal resolution and continuous dynamics: choosing DES trades modeling simplicity and speed against potential loss of fidelity when continuous phenomena matter.

 

 

 

 

 





## Synthesis

Synthesis

Select DES when system behavior is dominated by sparse, instantaneous state transitions and event ordering governs outcomes; otherwise prefer continuous or hybrid models or augment DES with timing extensions (timed/stochastic events) to capture needed fidelity.