CENG 7106 SYSTEM ANALYSIS AND MANAGEMENT TECHNIQUES II

LECTURE NOTE
CYCLONE – A SIMULATION MODELING METHODOLOGY

1
 INTRODUCTION TO CYCLONE
— CYCLONE is an acronym that stands for CYCLic Operations Network.

— It is a simulation modeling language that enables graphical representation and

simulation of discrete systems characterized by deterministic or stochastic
variables.
— CYCLONE can be used to model cyclic interacting processes with ease.

— Modeling Environments that provide for a CYCLONE approach include:

→ MicroCYCLONE

→ CYCLONE Special PurposeTemplate in Simphony

→ STROBOSCOPE

— The CYCLONE Special Purpose Template in Simphony will be used for

modeling in this part of the course.
2
 Dynamic systems & Simulation
— Have you ever waited in a bank
teller or coffee shop line and
tried to figure at why it was
taking so long? The wait gets
longer and you start analyzing in
your mind what is going on:
— What if there were more servers?
— What if the server was more
efficient?
Server Customer Queue — Why don’t they have a separate
line for those with picky orders
that take forever? My order is
straight forward!
— How long is the average customer
waiting and at what point to they
decide it is not worth it and go
somewhere else?

3
 CYCLONE

Server Customer Queue

Server Service Customer Queue

Served Customers Arrival

Customer Pool

4
 Modeling elements we need
— CYCLONE exists in Simphony as a special purpose template
with seven modeling elements namely:
→ Queue Node (Queue)
→ Combination Activity (Combi)
→ Normal Activity (Normal)
→ Counter
→ Function (Consolidate and Generate)
→ Probabilistic branch
→ Composite element

— It also has entities (abstract elements) and arrows

5
INTRODUCTION TO CYCLONE TEMPLATE IN SIMPHONY
— These entities (units) flow through the different modeling elements during
execution of simulation. They don’t have any attributes.

— On the other hand, the arrows link up the modeling elements and facilitate
the routing of entities through the elements in the model. Arrows aid in
representation of the logic of the system being modeled.

— Simulation is terminated in CYCLONE models built in Simphony when one

or all of the following conditions are met:
→ Maximum limit for entities are registered by counter

→ Pre-set simulation time is reached

→ The model exhausts all entities

6
 Example

Table 1 - Coffee Shop Customer Data

Customer No. Arrival Time (min) Service Time (min)

1 3.34 3.01
2 5.54 2.78
3 8.05 4.57
4 18.55 4.21
5 21.66 3.99

7
 Simulating customer service

Figure 4 - State of Coffee Shop at Time 0.00

Figure 3 - State of Coffee Shop at Time 0.00

Figure 6 - State of Coffee Shop at Time 3.34

Figure 5 - State of Coffee Shop at Time 3.34

8
 Results of the simulation

Customer Arrival Time Service Time Time in System

No. (min) (min) (min)

1 3.34 3.01 3.01

2 5.54 2.78 3.59

3 8.05 4.57 5.65

4 18.55 4.21 4.21

5 21.66 3.99 5.09

9
 Modeling concepts
— Models are composed of modeling elements and virtual entities that
flow from one element to the other until simulation is terminated (a
certain condition is met to end the simulation).
— We try to create a model by describing the real-world systems they
represent by following the journey of the virtual entities between the
modeling elements.
— The modeling elements process the virtual entities as they arrive and
release them to subsequent elements upon completion.
— The modeling elements in CYCLONE are:
— Queue element (Queue),
— Combination task (Combi),
— Normal task (Normal),
— Production counter,
— Function (Consolidate and Generate), and
— Probabilistic branch (not a CYCLONE element).

10
 THE QUEUE ELEMENT IN THE CYCLONE TEMPLATE
— Queue Node
A queue node is an element that can only be followed by a combination activity
(combi) in this template.
Inputs: Icon for Queue Node
Initial Length – The number of entities created & thus present within
this element at the start of simulation.
Outputs:
Current Length – The number of entities in this element at the Property Grid for Queue Node
current time.
Statistics:
File Length - A statistic for the number of entities waiting in
this element.
PercentNonEmpty – A statistic indicating the % time this element
has an entity within it.
Waiting Time - A statistic describing the length of time that an
entity takes waiting in this element.
11
 SIMULATION BEHAVIOR OF THE QUEUE ELEMENT IN
THE CYCLONE TEMPLATE
— Queue Node
Simulation Behavior:
→ Serves as an element that creates entities. All entities are created at once at
the start of simulation.
→ Provides queuing services to entities.

→ Does not necessarily have to be connected to another element at it’s input

point.

N.B:
The design and layout properties of any modeling element don’t affect the
simulation at run time.

12
 THE COMBI ELEMENT IN THE CYCLONE TEMPLATE
— “Combination Activity” Element (Combi)
This element can only be connected to a queue node at its input point.
However, the output point can be connected to any other element. Icon for Combi Element

Inputs:
Duration – Specifies the time length for which the entities will be
held by this element measured from their time of entry. It
can be deterministic (constant), stochastic (distribution) Property Grid for Combi

or a formula.
Priority – Combis with higher priority get preference in receiving
entities from queue nodes over those with a lower
priority.
Outputs: No outputs
Statistics:
Inter-Arrival-Time – This is a statistic of the time span between the
arrival of two sequential entities at this element.
13
 SIMULATION BEHAVIOR OF THE COMBI ELEMENT IN
THE CYCLONE TEMPLATE
— “Combination Activity” Element (Combi)
Simulation Behavior:
→ A combi can be connected to one or multiple queue nodes.

→ When connected to a single queue node, entities flow into a combi without
restriction and are processed simultaneously i.e. held for the same
duration.
→ On the other hand, when connected to multiple queue nodes, the combi
will not commence processing until there is at least one entity available in
each of the queue nodes it is connected to. Once this condition is fulfilled,
only one entity is drawn from each queue node, held in the combi for the
specified duration and then just one entity is released.
→ Combis have the capacity to process multiple entity combinations
simultaneously because it behaves as though it has infinite servers.
14
 NORMAL ELEMENT IN THE CYCLONE TEMPLATE
— “Normal Activity” Element (Normal)
This element can be connected at its input point to any element except a queue node.
However, the output point can be connected to any other element except a combi.
Inputs:
Icon for Normal Element
Duration – Specifies the time length for which the entities will
be held by this element measured from their time of
entry. It can be deterministic (constant), stochastic
Property Grid for Normal
(distribution) or a formula.

Outputs: No outputs
Statistics:
Inter-Arrival-Time – This is a statistic of the time span between
the arrival of two sequential entities at this
15
element.
 SIMULATION BEHAVIOR OF THE NORMAL ELEMENT IN
CYCLONE TEMPLATE

— “Normal Activity” Element (Normal)

Simulation Behavior:
→ Entities are routed into this element without the need to fulfill any
constraint.

→ The entities are held for a duration that was pre-defined by the user; after
which the same number of entities that entered the element are routed out.

→ A Normal can process as many entities as are available simultaneously

because it has no restrictions on the number of available servers.

16
 FUNCTION ELEMENT IN THE CYCLONE TEMPLATE
— Function Element (Generate & Consolidate)
This element can be connected at its input point to any element except a queue node.
However, the output point can be connected to any other element except a combi. It
can switch functions between entity generation or consolidation depending on the
Icon for Consolidate (Function
users preference. Element)

Inputs:
Number – Specifies the number of entities to generate or Icon for Generate (Function
Element)

consolidate.
Type - A value indicating whether the element generates or Property Grid for Function

consolidates entities.
Outputs: No outputs
Statistics: No statistics
17
 SIMULATION BEHAVIOR OF THE FUNCTION ELEMENT
IN THE CYCLONE TEMPLATE
— Function Element
Simulation Behavior - Generation:
→ The element will generate (clone) and release the number of entities
specified by the user for each entity that is routed into it.
→ Entities routed into this element are released without delay.

Simulation Behavior - Consolidation:

→ The element will consolidate (clone) entities routed into it that are equal in
quantity the number specified by the user and release only one entity.
→ The release of a consolidated entity from this element is delayed until the
user defined number of entities are routed into it.

18
 COUNTER ELEMENT IN THE CYCLONE TEMPLATE
— Counter Element
This element can be connected at its input point to any element except a queue node. The output point can be
connected to any other element except a combi.
Icon for counter in CYCLONE
Inputs:
Initial – The starting value of the count property.
Limit - A parameter that will cause the simulation run to terminate if its value (with the exception of zero) is equal
to the value of the count. A value of zero indicates that the counter does not determine termination.
Step - The amount by which the count is increased (or decreased) each time an entity flows through this element.
A value may be entered direct or a formula. Properties for counter element
Outputs:
Count – The final count when the last entity when through this element. It is a function of the total number of
entities that have flowed through it and the step.
Time – The time at which the last entity flowed through this element.

Statistics:
Inter-Arrival-Time – A statistic representing the time entities arriving at this element.
FirstTime – Statistics summarizing time values for all runs with each observation in each run representing the time
when the first entity arrived at this element.
LastTime– Statistics summarizing time values for all runs with each observation in each run representing the time
when the last entity arrived at this element.
LastCount – Statistics summarizing count values for all runs with each observation in each run representing the count
when the last entity arrived at this element.
Production – The cumulative count of the entities that arrived at this element.
ProductionRate – It is a statistic representing the ratio of the value of the count property to the simulation time. A
value for this ratio is collected each time an entity flow through it.
19
 COUNTER ELEMENT CONTINUED
Statistics (continued):
Last Count – Is a statistic of the count value registered by this element at the end of each simulation run
Last Time – Is a statistic of the time value registered by this element at the end of each simulation run

— Counter Element
Simulation Behavior:

→ Entities are also routed into this element without the need to fulfill any constraint.

→ These entities flow through the element without any delay and trigger some
calculations causing the count, time, inter-arrival-time and productivity properties to
be updated.
→ In this Simphony template, a model can have as many counter as the modeler requires
which is not the case in MicroCYCLONE because it accepts only one counter per
model.
→ It is useful for determining the termination of simulation and also for monitoring
things taking place in a simulation during execution.
20
 THE BRANCH ELEMENTS IN THE CYCLONE TEMPLATE

— PROBABILISTIC BRANCH ELEMENT:

Inputs: Icon for Probabilistic Element

Probability - Accepts any real number between 0 and 1 as a
probability. The value entered is assigned to and reflected at the
top branch of the element. The implication is that the entity gets
routed out through that branch by that specified probability
Property grid for probabilistic Element
multiplied by100 percent of the time (or of the entities flowing
through this element).

Outputs: No outputs
Statistics: No statistics

21
 THE COMPOSITE ELEMENT IN THE CYCLONE TEMPLATE
— COMPOSITE ELEMENT:
This element serves as a container in which parts of a model are
Icon for Composite Element
placed. This allows for a hierarchical approach to modeling which
makes it easy to read large models

Inputs:
Inputs – Is a provision for the modeller to specify the number of Property grid for Composite Element

input points that the composite element should have

Outputs – Is a provision for the modeller to specify the number of
output points that the composite element should have

Outputs: No outputs
Statistics: No statistics

22
 CYCLONE TEMPLATE - SUMMARY
— Important things to note about each of the modeling elements, are:
→ Their names & Icons (appearance);

→ The properties associated with each;

→ Their simulation behavior and

→ How they are linked when building models – to accurately represent the logic of
the system being analyzed.
— Properties common to all elements (except the branch and composite
element)
Incoming trace – Associated with input points and allows modeler to enter information
they would want to display within the Simphony trace window
Outgoing trace - Associated with output points and allows modeler to enter information
they would want to display within the Simphony trace window

Color – Allows the modeler to pick a fill color for the respective element. Useful for
purposes of making large models more readable
23
 Adding the CYCLONE Template to Simphony
— Install Simphony software on your computer
→ Install the latest build provided

— Follow the steps below to add the CYCLONE template

→ Start Simphony (Start, programs, Simphony.Net 4.0, Simphony
Modeling environment);
→ Select “Add Template” tab; Browse for template in program files
(Simphony folder, Templates folder, Cyclone Template and click okay)

24
 Graphical Illustration of Steps for
Installing CYCLONE Template in Simphony
Launch Simphony & click “add template”
Browse for the template to be
added and add it

“Add template”
tab

Location of added
cyclone template

25
 AN EARTH-MOVING OPERATION EXAMPLE MODELED WITH THE
SIMPHONY-CYCLONE TEMPLATE
— Model a typical earth-moving operation using cyclone template in
simphony. Run the model to simulate the dumping of the specified volume.
The objectives of this exercise are to:
→ Demonstrate how to use CYCLONE to built models
→ Illustrate how to run a built cyclone model
→ Obtain useful output; in this case – system production rate, equipment balance
numbers e.t.c.
— A schematic layout of a simplified earth moving operation is shown below:

26
 AN EARTH-MOVING OPERATION EXAMPLE MODELED WITH
THE SIMPHONY-CYCLONE TEMPLATE
— A detailed description of processes involved is presented below
(Includes excavation & spreading, not shown in the figure):
→ A back hoe excavates a finite volume of dirt and places it in a dirt pile;
→ A front-end loader picks dirt from this pile and places it onto waiting
trucks;
→ Loaded trucks travel to dumpsite;
→ Trucks are spotted one-at-a-time for dumping;
→ A dozer then spreads each dumped pile of dirt;
→ Empty trucks return for re-loading.
→ Ignore the effects of traffic, road profiles (grade) and road roughness

— Input data for modeling this operation is summarized in a table

on the following slides.

27
 INPUT PARAMETERS FOR THE EARTH-MOVING PROBLEM
Serial Parameter for the Value of the

No. Operation Parameter

1. Initial quantity of dirt to be excavated (cubic 8,900

yards)

2. Track capacity (cubic yards) 8.9

3. Trucks available 5

4. Excavators available at the loading area 1

5. Loaders available at the loading area 1

6. Spotters available at the dumpsite 1

7. Dozers available at the dumpsite 1

8. Excavation duration (minutes) 1.2

9. Loading duration (minutes) 2.8

10. Haul duration for each truck (minutes) 19.1

11. Return duration for each truck(minutes) 15.6

12. Dumping duration (minutes) 2.8

13. Spreading duration by dozer at the placement 8.5

site (minutes)

28
 INFORMATION ON RESOURCES AND REQUIREMENTS

— Assume that the capacity of the excavator, loader, truck(s)

and dozer are each 10CY.
— Develop a CYCLONE model for the described operation
and find the following:
i. The optimal number of trucks to use on this operation

ii. The time required to dump all the dirt

29
 SOLUTION - CYCLONE MODEL LAYOUT OF THE PROBLEM

30
 SIMULATION RESULTS
Production rate table for the different scenarios

Max production

31
 A RIPRAP OPERATION EXAMPLE MODELED WITH THE
SIMPHONY-CYCLONE TEMPLATE
— Model a Riprap installation using cyclone template in simphony. The
objectives of this exercise are to:
→ Demonstrate hand simulation of construction operations
→ Introduce the concepts of cyclic processes and their interaction
→ Introduce the use of modeling elements (particularly the function - consolidate and
generate)
→ Introduce the probabilistic branch element
— A schematic layout of a riprap installation operation is shown below:

32
 A RIPRAP OPERATION EXAMPLE MODELED WITH THE
SIMPHONY-CYCLONE TEMPLATE
— A detailed description of processes involved is presented below
→ Space available to stock pile only 3 skid loads (60 stones)
→ A skid loader delivers 20 stones each trip
→ 3 Labourers available that are working independently
→ Labourer can only lift one stone at a time

— Input data for modeling this operation is summarized on the

following slide.

33
 INPUT PARAMETERS FOR THE RIPRAP PROBLEM

Activity Duration (Minutes)

Skid Loader resupply time 7.5
Labourer travel (loaded) 3.0
Pick one stone 1.2
Labourer travel (empty handed) 1.0
Placement of a stone 2.7

34
 A RIPRAP OPERATION EXAMPLE MODELED WITH THE
SIMPHONY-CYCLONE TEMPLATE
— Modeling Requirements
→ Time to place 4 truck loads
→ Production rate of the skid loader and that of the entire operation
→ Identify bottleneck(s) in the system
→ Report system production (Stones placed per hour)
→ Examine stone stock replenishment policies – Replenish all stock has run out
verse replenish when there is space for a load
→ Examine the possibility of sorting out poor quality stones and discarding those

35
 CYCLONE MODEL FOR THE RIPRAP PROBLEM

36
 CYCLONE MODEL FOR THE RIPRAP PROBLEM - RESULTS

37
 A RIPRAP OPERATION EXAMPLE MODELED WITH THE
SIMPHONY-CYCLONE TEMPLATE
— Embellishment 1
→ Resupply only if space for 3 skid loads is available

38
 A RIPRAP OPERATION EXAMPLE MODELED WITH THE
SIMPHONY-CYCLONE TEMPLATE
— Embellishment 1 - Result

39
 A RIPRAP OPERATION EXAMPLE MODELED WITH THE
SIMPHONY-CYCLONE TEMPLATE
— Embellishment 2
→ 10% chance of bad stones which are then discarded

40
 A RIPRAP OPERATION EXAMPLE MODELED WITH THE
SIMPHONY-CYCLONE TEMPLATE
— Embellishment 2 - Result

41
 A RIPRAP OPERATION EXAMPLE – HAND SIMULATION

— Input parameters

42
 A RIPRAP OPERATION EXAMPLE – HAND SIMULATION

../Lecture 2. Cyclone/2.1 Hand Simulation Examples

(Earthmoving and Riprap Operations)/Hand Simulation - Riprap
Example/Riprap Hand Simulation.xlsx

43
 A LRT CONSTRUCTION OPERATION EXAMPLE MODELED WITH
THE SIMPHONY-CYCLONE TEMPLATE

44
 A LRT CONSTRUCTION OPERATION EXAMPLE MODELED WITH
THE SIMPHONY-CYCLONE TEMPLATE
Tunnel Alignment:

SB1

SB2

NB1

NB2

45
 A LRT CONSTRUCTION OPERATION EXAMPLE MODELED WITH
THE SIMPHONY-CYCLONE TEMPLATE

Section along the Alignment:

46
 PROJECT DETAILS FOR THE LRT CONSTRUCTION
OPERATION PROBLEM
Tunnel Lengths
Tunnel Label Length (m)
1 NB1 (North Bound 1) 184
2 SB1 (South Bound 1) 184
3 NB2 (North Bound 2) 265
4 SB2 (South Bound 2) 241
Excavation Tools:
Equipment Soil Type
Backhoe Soft soil
Rock Grinder Hard soil

Excavation Sequence:
→ 1m of heading
→ Next 1m of heading
→ 2m of invert

47
 INPUT PARAMETERS FOR THE LRT CONSTRUCTION
OPERATION PROBLEM

48
 PROCESS LOGIC FOR CONSTRUCTION ACTIVITIES

49
 SEM BASE MODEL (HEADING PART A1)

50
 SEM BASE MODEL (HEADING PART A1) RESULTS -
CONSTANT DURATIONS

51
 SEM CYCLONE MODEL (HEADING PART A1)
Embellishment 1 – VARIABLE ACTIVITY DURATIONS
— Transforms the provided times into triangular distributions.
This is done by using the original value as the mode, subtracting
15% to obtain the low value and adding 20% to obtain the high
value.
Activity Duration (Minutes)
Probe/Drainage Holes Triangular(9.95,11.70,14.04)
Excavation Triangular(34.43,40.50,48.6)
Mucking Triangular(24.28,28.56,34.27)
Survey/Map Triangular(29.75,35.00,42.00)
1st Layer Shotcrete Triangular(22.98,27.03,32.44)
1st Layer WWF Triangular(38.25,45.00,54.00)
Lattice Girders Triangular(38.25,45.00,54.00)
2nd Layer Shotcrete Triangular(27.47,32.32,38.78)
2nd Layer WWF Triangular(38.25,45.00,54.00)
52 3rd Layer Shotcrete Triangular(16.50,19.41,23.29)
 SEM EMBELLISHED MODEL (HEADING PART A1) RESULTS -
TRIANGULAR DURATIONS

53
 SEM CYCLONE MODEL (HEADING PART A1)
Embellishment 2 – BACK HOE BREAKDOWNS

— A breakdown of the backhoe should be incorporated in the

original model. The interval between breakdowns is modeled
using an exponential distribution with a mean of 56 hours
(3360 minutes) and the repair duration is modeled using a
triangular distribution with a low value of 408 minutes, a high
value of 576 minutes, and a mode of 480 minutes.

54
 SEM EMBELLISHED CYCLONE MODEL (HEADING PART
A1) - BACK HOE BREAKDOWNS

55
 SEM EMBELLISHED MODEL (HEADING PART A1) RESULTS
- BACK HOE BREAKDOWNS

56
 SEM CYCLONE MODEL
Embellishment 3 – MODEL FOR PART A1, A2 AND B3
USING COMPOSITE ELEMENTS

57