1

An Electronic Assembly and Test

System

 Produce two different sealed elect. units (A, B)

 Arriving parts: cast metal cases machined to accept the electronic
parts
 Part A, Part B – separate preparation areas
 Both go to Sealer for assembly, testing – then to Shipping (out) if OK, or
else to Rework
 Rework – Salvaged (and Shipped), or Scrapped 2
Part A
• Interarrivals: expo (5) min.
• From arrival point, go immediately to Part A Prep
• Process = (machine + deburr + clean) ~ tria (1,4,8)
min.

• Go immediately to Sealer
• Process = (assemble + test) ~ tria (1,3,4) min.
• 91% pass, go to Shipped; Else go to Rework
• Rework: (re-process + testing) ~ expo (45) min.
• 80% pass, go to Salvaged; Else go to Scrapped

3
• Part B
• Interarrivals: batches of 4, expo (30) min.
• Upon arrival, batch breaks into 4 individual parts
• Proceed immediately to Part B Prep area
• Process = (machine + deburr +clean) ~ tria (3,5,10)
• Go to Sealer
• Process = (assemble + test) ~ weib (2.5,
5.3) min. ,
different from Part A, though at same station
• 91% pass, go to Shipped; Else go to Rework
• Rework: (re-process + test) = expo (45) min.
• 80% pass, go to Salvaged; Else go to Scrapped 4
 Run Conditions, Output
 Start empty & idle, run for 32 hours

 Collect statistics for each work area on

 Resource utilization

 Number in queue

 Time in queue

 For each exit point (Shipped, Salvaged, Scrapped), collect

total time in system (cycle time)

5
 Building the Model
 Entities are the individual parts (two types)
 Separate Create modules for two part types
 Separate Process modules for each Preparation area
 Process modules for Sealer followed by a Decide module
(2- way by Chance)
 Rework, each followed by a Decide module (2-
way by Chance)
 Dispose modules for Shipped, Salvaged, Scrapped
 Attribute Sealer Time assigned after Creates in Assign
modules (parts have different times at the Sealer)
 Record modules just before Departs for time in system
6
 Building the Model (Cont.)
 New model window
 Attach Basic Process panel (if needed)
 Place modules
 Create (× 2)
 Assign (× 2)
 Process (× 4) Alternate strategy –
place one module at a
 Decide (× 2) time, fill it out completely

 Record (× 3)
 Dispose (× 3)
 Right click — repeat last action (place module)
 Auto-Connect, or manually connect via

7
8
 Name: Part A Arrive
 Entity Type: Part A
 Time Between Arrivals
 Type: Random (Expo)
 Pull-down list with options
 Value: 5
 Units: Minutes
 Pull-down list with options
 Default what’s not mentioned
above
9
 Name: Part B Arrive
 Entity Type: Part B
 Time Between Arrivals
 Type: Random (Expo)
 Pull-down list with options
 Value: 30
 Units: Minutes
 Pull-down list with options
 Entities per Arrival: 4

10
  Name: Assign Part A
Sealer and Arrive Time
 Add button:
 Type: Attribute
 Attribute Name: Sealer Time
 New Value: TRIA(1, 3, 4)

 Add button:
 Type: Attribute
 Attribute Name: Arrive Time
 New Value: TNOW (to compute
time in system on exit)

TNOW is the internal Arena variable name for

the simulation clock; see
Help > Arena Help > Contents >
Variables, Functions, and Distributions > Variables >
Right Click to build Date and Time Variables 11
this expression
 Name: Assign Part B
Sealer and Arrive Time
 Add button:
 Type: Attribute
 Attribute Name: Sealer Time
 New Value: WEIB(2.5, 5.3)

 Add button:
 Type: Attribute
 Attribute Name: Arrive Time
 New Value: TNOW

Although four entities are

created in the previous
module for each arrival, they’ll
each be assigned a different
(independent) value from the
sealer time distribution in this
Assign Module
12
 If several Resources
were named (Add
button), entity would
have to Seize them
all before the Delay
could start.

 Name: Prep A Process

 Action: Seize Delay
Release
 Resources
subdialog
(Add button):
 Type: Resource (a
pull- down option)
 Resource Name: Prep
A
 Quantity: 1 (default)
 Delay Type:
Triangular
 Units: Minutes 13


 Name: Prep B Process
 Action: Seize Delay
Release
 Resources subdialog
(Add button):
 Type: Resource (a
pull-
down option)
 Resource Name: Prep
B
 Quantity: 1 (default)
 Delay Type:
Triangular
 Units: Minutes
 Minimum: 3
 Value (Most Likely):
5 14
 Maximum: 10
  Name: Sealer Process
 Action: Seize Delay
Release
 Resources subdialog
(Add button):
 Type: Resource (a
pull- down option)
Recall – Sealer Time attribute  Resource Name:
was defined upstream for both Sealer
Parts A and B … now its value is
 Quantity: 1 (default)
being used … allows for different
distributions for A and B.  Delay Type:
Expression
 Units: Minutes
 Expression: Sealer
  Decide module
provides branch points
 By Condition (entity
Attributes,
global Variables)
 By Chance (multi-sided,
possibly-biased
hypercoin flip)
 Name: Failed Sealer
Inspection
 Type: 2-way by Chance
(default)
 Percent True: 9
– Note it’s percent true, so “9” means  Different exit points
probability of 0.09
– We arbitrarily decided “true” meant part failed
for True, False results
inspection … could have reversed (but would – connect
change numerical results ... why? ... does appropriately
this upset you? ... why?) downstream

16
 Name: Rework Process
 Action: Seize Delay Release
 Resources subdialog
(Add button):
 Type: Resource (a pull-down
option)
 Resource Name: Rework
 Quantity: 1 (default)
 Delay Type: Expression
 Units: Minutes
 Expression: EXPO(45)

17
 Name: Failed Rework
Inspection
 Type: 2-way by
We arbitrarily decided “true”
Chance
meant part failed inspection
(default)
 Percent True: 20

18
Record Modules
 Arena collects and reports many output statistics
by default, but sometimes not all you want
 Remember that as part of the simulation output,
we wanted to collect statistics on
1. resource utilization,
2. number in queue, and
3. time in queue at each of the operations.
 These three statistics are automatically collected
whenever you use a Process module with an
Action option that requires a resource assuming
that
1. the Report Statistics box for the module is checked and
2. that the Processes box is checked in Run > Setup > Project
Parameters

19
 Record Modules (cont…)
 Arena may not collects and reports many output
statistics that you want
 Want time in system (avg, max) of parts sorted by their
exit point (Shipped, Salvaged, Scrapped)
 It’s this sorting that Arena doesn’t do by default ... it would
automatically sort by Entity Type if we had Entities checked in
Run > Setup > Project Parameters (which we don’t)
 Record module can be placed in flowchart to collect and
report various kinds of statistics from within model run as
entities pass through it
 For Tally-type output performance measures

20
 Name: Record Shipped Parts
 Type: Time Interval
 Records time elapsed up to now (TNOW) from when an entity attribute
was marked with a time “stamp” upstream ... Attribute Name is
below
...
 There are several other options for Type … explore via Record
module’s Help button!
 Attribute Name: Arrive Time
 Was defined upstream as the clock value in the Assign modules
instantly after each entity was Created
 Tally Name: Record Shipped Parts
 Determines the label in the reports

Other two Record

modules –
just like this except
for Name and Tally
Name.

21
 Dispose Modules
 Three separate exit points for three
separate part disposition (Shipped,
Salvaged, Scrapped)
 Could have directed all three exit types to
a single Dispose module
 Separate ones gets animation counts of three
dispositions

22
 Without this, model would
run forever – no defaults for
termination rule
 That’s part of modeling, and
generally affects
results!
 Project Parameters tab:
 Fill in Project Title, Analyst
Name
 Defaults for Statistics Collection,
but we cleared the check
box for Entities
 Not needed for what we want (we
installed our own Record modules),
and would slow execution

23
  Replication Parameters tab:
 Replication length: 32, accept
Hours default for Time Units
 Base Time Units: Minutes for
inputs without Time Units option,
internal arithmetic, and units on
output reports

24
25
26
 Some Modification

 In the previous model, cycle time was collected and

differentiated by exited type (scraped, salvaged or
shipped)

 Now, let us assume we want to get the cycle time

further differentiated by part type (scraped Part A,
scraped Part B, salvaged Part A, savaged Part B,
shipped Part A, shipped Part B)

27
Detailed in the Next Slide

28
29
30
Th
eE
nd