user guide

Disclaimer Copyright Information

The information in this guide is provided by Pro- © 10/08 ProModel Corporation
Model Corporation to document ProModel. The
All rights reserved
contents of this manual are subject to change
without notice and does not represent a commit- Printed in the United States of America
ment on the part of ProModel Corporation. The
software described in this guide is applied under
a license agreement and may be copied only
under the terms of the license agreement. No part
ProModel and SimRunner are registered trade-
of this guide may be reproduced, transmitted, or
marks of ProModel Corporation.
distributed by any means, electronic or mechani-
cal, for purposes other than the owner’s personal Text indicator graphics Copyright New Vision
use without express written permission from Pro- Technologies Inc.
Model Corporation.
Microsoft is a registered trademark and Win-
dows, Excel, and ActiveX are trademarks of
Microsoft Corporation.
Stat::Fit is a trademark of Geer Mountain Corpo-
ration.
IBM is a registered trademark of International
Business Machines Corporation.
Netware and Novell are a registered trademarks
of Novell, Inc.
AutoCAD is a registered trademark of Autodesk,
Inc.

10/08
 ProModel iii
User Guide

Table of Contents

Table of Contents ......................................................................... iii

Introduction ....................................................................................1

About the User Guide ........................................................... 1

Symbols and Notation .......................................................... 3
Keyboard ........................................................................ 3
Text ................................................................................ 3
Logic .............................................................................. 3
Product Support .................................................................... 4
Modeling Services ................................................................ 5
Reporting Suggestions .......................................................... 5

Chapter 1: Getting Started ..................................................................................7

Welcome to ProModel .......................................................... 7

Where to Go from here .................................................. 7
Using ProModel .................................................................... 9
Building Models ............................................................. 9
Running Models ........................................................... 11
Creating Run-Time Models ......................................... 11
Trace Window .............................................................. 11
Location Information Windows ................................... 12
Viewing Output ............................................................ 12
iv

Chapter 2: Installation and Registration ...........................................................15

General Setup Information ................................................. 15

Hardware Requirements ............................................... 15
Installation Procedure for a Stand-alone PC ...................... 15
Installation Procedure for Network Version ....................... 17
Overview ...................................................................... 17
Install Program Files .................................................... 17
Set Up License Server .................................................. 19
Registering ProModel ......................................................... 22
Checking for ProModel Updates .................................. 24
Software License Key FAQ ......................................... 24

Chapter 3: Planning the Model .........................................................................25

Steps for Doing Simulation ................................................ 25

Introduction .................................................................. 25
General Procedure ........................................................ 25
Step 1: Planning the Study ........................................... 26
Step 2: Defining the System ......................................... 30
Step 3: Building the Model .......................................... 35
Step 4: Conducting Experiments .................................. 37
Step 5: Analyzing the Output ....................................... 45
Step 6: Reporting the Results ....................................... 45
Pitfalls in Simulation .................................................... 46
Summary ...................................................................... 46
Building a Model ................................................................ 47
Modeling Scenario ....................................................... 47
Phased Modeling Approach ......................................... 48
Phase 1: Basic Model Elements ................................... 48
Phase 2: Adding Resources & Variability ................... 52
Phase 3: Additional Operations .................................... 55
Running a Model ................................................................ 56
Simulation Options ...................................................... 57
Animation Screen ......................................................... 57
Options Menu ............................................................... 58
Information Menu ........................................................ 58
 ProModel v
User Guide

Viewing Model Statistics & Reports .................................. 59

Chapter 4: Modeling Environment ...................................................................61

Menu Bar ............................................................................ 61

File Menu ............................................................................ 62
File Management .......................................................... 62
Model Merging ............................................................ 64
View/Print Model Text ................................................ 66
Model Packaging/Data Protection ............................... 68
Edit Menu ........................................................................... 70
Editing Tables .............................................................. 70
Editing Process Records ............................................... 71
Editing Notes Windows ............................................... 72
Editing Logic Windows ............................................... 72
Editing Background Graphics ...................................... 73
Editing & Moving Graphics ........................................ 74
View Menu ......................................................................... 76
Switches ....................................................................... 76
Toolbars ....................................................................... 77
Settings ......................................................................... 77
Views ........................................................................... 77
Zoom Feature ............................................................... 79
Layout Settings ............................................................ 80
Edit Tables ................................................................... 83
Commands ................................................................... 83
Window Menu .................................................................... 84
Help Menu .......................................................................... 85
Toolbars .............................................................................. 85
Right-Click Menu ............................................................... 87

Chapter 5: Building the Model: General Elements ...........................................89

Build Menu .................................................................. 89

Locations ............................................................................ 90
vi

Locations Editor ........................................................... 90

Location Edit Table ...................................................... 91
Location Graphics Window ......................................... 92
Location Graphics ........................................................ 94
Capacities and Units ................................................... 100
Location Downtimes .................................................. 101
Rules Dialog Box ....................................................... 109
Entities .............................................................................. 112
Entities Editor ............................................................ 112
Defining Entities ........................................................ 113
Entity Graphic Dimensions ........................................ 113
Defining Multiple Entity Graphics ............................ 114
Preemptive Entities .................................................... 115
Path Networks .................................................................. 117
Path Networks Editor ................................................. 117
A Typical Path Network ............................................ 119
Path Segment Edit Table ............................................ 120
Automatic Time and Distance Calculation ................ 121
Interfaces Edit Table .................................................. 121
Mapping Edit Table ................................................... 122
Nodes Edit Table ........................................................ 124
Pre-translation check for Path Networks ................... 125
Resources .......................................................................... 126
Typical Use of Resources .......................................... 126
Resources Editor ........................................................ 126
Static Resources ......................................................... 129
Dynamic Resources .................................................... 129
Multiple Resource Graphics ....................................... 130
Multi-Unit Resources vs.
Multiple Single-Unit Resources ................................. 131
Resource Downtimes ................................................. 131
Resource Priorities and Preemption ........................... 134
Resource Shift Downtime Priorities .......................... 134
Resource Preemption Matrix ..................................... 135
Resource Specifications Dialog Box .......................... 136
Resource Search Routines .......................................... 138
Node Logic Editor ...................................................... 140
Resource Points .......................................................... 141
Processing ......................................................................... 143
 ProModel vii
User Guide

Using the Processing Editor ....................................... 143

Defining Entity Processing ........................................ 144
Processing Editor ....................................................... 145
Process Edit Table ...................................................... 145
Routing Edit Table ..................................................... 149
Processing Tools ........................................................ 153
Arrivals ............................................................................. 156
Arrivals Editor ............................................................ 156
Arrivals Edit Table ..................................................... 156
Defining Arrivals ....................................................... 157
Independent Arrivals .................................................. 158
Arrival Logic .............................................................. 160
Shifts & Breaks ................................................................. 161
Shift Editor ................................................................. 161
Adding, Editing Work and Break Time ..................... 162
Shift Assignments ...................................................... 163
Shift Downtime Principles ......................................... 167
General Information ......................................................... 171
General Information Dialog Box ............................... 171
Cost ................................................................................... 175
Cost Dialog Box ......................................................... 175
Building a Model with Costing .................................. 176
Preemption/Downtime ............................................... 177
Join/Load .................................................................... 177
Combine/Group .......................................................... 177
Special Cost Handling ................................................ 178
Costing Output Statistics ............................................ 178
Enable or Disable Costing .......................................... 179
Tanks ................................................................................ 180
Basic Concepts ........................................................... 181
Tank Logic Builder .................................................... 183
Pre-defined Tank Subroutines .......................................... 185
Tank_Fill .................................................................... 185
Tank_Empty ............................................................... 186
Tank_Transfer ............................................................ 187
Tank_TransferUpTo ................................................... 187
Tank_TransferDownTo .............................................. 188
Tank_SetLevel ........................................................... 189
viii

Tank_Inc .................................................................... 190

Tank_Dec ................................................................... 190
Tank_RiseTrigger ...................................................... 191
Tank_FallTrigger ....................................................... 191
Tank_Cap ................................................................... 192
Tank_FreeCap ............................................................ 192
Tank_DoOperation ..................................................... 193
Tank_GoDown ........................................................... 193
Tank_GoDownSched ................................................. 194
Tank_DoPrep ............................................................. 195
Tank_SetState ............................................................ 196
Tank_SelectOutput ..................................................... 196
Tank_SelectInput ....................................................... 198
Tank_UpdateStats ...................................................... 198
Tank_Rate .................................................................. 199
Pre-defined Data Elements ......................................... 199
Defining Tank Control Subroutines ........................... 201
Examples of Tank Control Logic ............................... 201
Background Graphics ....................................................... 210
Background Graphics Editor Modes .......................... 210
Background Graphics Editor ...................................... 211

Chapter 6: Building the Model: Advanced Elements .....................................217

Attributes .......................................................................... 217

Attribute Types .......................................................... 217
Memory Allocation for Attributes ............................. 218
Attributes vs. Local Variables .................................... 218
Cloning Attributes ...................................................... 218
Attribute Edit Table ................................................... 219
Example of Attributes in Logic .................................. 219
Attributes and the JOIN or LOAD PERM Statement 220
Attributes and the GROUP/UNGROUP Statements . 220
Attributes and the LOAD/UNLOAD Statements ...... 221
Attributes and the COMBINE Statement ................... 222
Variables ........................................................................... 223
Variable Edit Table .................................................... 223
Variable Layout .......................................................... 224
 ProModel ix
User Guide

Editing a Variable’s Icon ........................................... 225

Local Variables .......................................................... 225
Arrays ............................................................................... 227
Arrays Edit Table ....................................................... 228
Initializing Arrays ...................................................... 229
Import Data into Arrays ............................................. 229
Export Arrays to Spreadsheets ................................... 231
Using Arrays .............................................................. 232
Notes on Arrays ......................................................... 232
Macros .............................................................................. 233
Macro Editor .............................................................. 233
Run-Time Interface .................................................... 234
Resource Grouping .................................................... 236
Subroutines ....................................................................... 238
Subroutine Editor ....................................................... 238
Subroutine Format ...................................................... 239
Subroutine Example ................................................... 240
Interactive Subroutines .............................................. 241
External Subroutines .................................................. 242
Subroutines vs. Macros .............................................. 242
Arrival Cycles ................................................................... 244
Arrival Cycles Edit Table .......................................... 244
Arrival Cycles Example ............................................. 244
Cumulative Cycle Tables ........................................... 246
Arrival Cycles by Quantity ........................................ 246
Table Functions ................................................................ 248
Table Functions Editor ............................................... 248
Table Function Edit Table .......................................... 249
User Defined Distributions ............................................... 251
User Distribution Edit Table ...................................... 251
Discrete Distributions ................................................ 251
Continuous Distributions ........................................... 253
External Files .................................................................... 254
External Files Editor .................................................. 254
File Types ................................................................... 254
Streams ............................................................................. 258
Streams Edit Table ..................................................... 258
x

Using Random Number Streams ................................ 258

Stream Example ......................................................... 259
Material Handling Systems .............................................. 261
Crane Systems ............................................................ 261
Conveyors .................................................................. 269
Automated Guided Vehicle Systems ......................... 273
Manual Material Handling Systems ........................... 274
Industrial Vehicles ..................................................... 274
Automated Storage/Retrieval Systems ....................... 275
Modeling Tips .................................................................. 276
Using Entity Attributes .............................................. 276
Customizing Graphics ................................................ 277
Batching & Unbatching Entities ................................ 278
Modeling Priorities .................................................... 280
Displaying Statistics On Screen ................................. 281
Creating Pull Systems ................................................ 282
Making Assemblies .................................................... 283

Chapter 7: Building the Logic ........................................................................285

Logic Builder .................................................................... 285

Using the Logic Builder ............................................. 285
Operation Logic ................................................................ 291
Preemption Process Logic ................................................ 292
Routing Move Logic ......................................................... 294
Move-Related Statements .......................................... 295
Related Logic Statements ........................................... 296
Statement Processing ................................................. 296
Shift & Break Logic ......................................................... 297

Chapter 8: Using Auxiliary Tools ...................................................................299

Tools Menu ................................................................ 299

Expression Search ............................................................ 300
Expression Search Sub-Menu Choices ...................... 300
 ProModel xi
User Guide

Find Expression .......................................................... 301

Replace Expression .................................................... 301
Important Notes Regarding Expression Searches ...... 302
Local Find and Replace .............................................. 303
Graphic Editor .................................................................. 304
Overview .................................................................... 304
File Menu ................................................................... 305
Edit Menu ................................................................... 306
Graphics Menu ........................................................... 308
Options Menu ............................................................. 311
Window Menu ............................................................ 312
Library Edit Buttons ................................................... 313
Manipulating Graphics ............................................... 313
Create New Graphics and Libraries ........................... 314
Naming a Graphic ...................................................... 314
Graphic Tools Button Bar .......................................... 315
Editing a Library Graphic .......................................... 323
Options ............................................................................. 325
Customize ......................................................................... 327
Power Tools ...................................................................... 328
ProClare ..................................................................... 329
ProSetter ..................................................................... 330
Shift Library ............................................................... 331
ProActiveX ................................................................. 331
ProModel Player ........................................................ 334

Chapter 9: Running the Model ........................................................................337

Simulation Menu ........................................................ 337

Simulation Options ........................................................... 338
General Options & Settings ....................................... 338
Output Reporting Options .......................................... 340
Running a Specific Replication .................................. 341
Customized Reporting ................................................ 342
Model Parameters & Scenarios ........................................ 342
Model Parameters ...................................................... 342
Scenarios .................................................................... 343
xii

Running the Simulation .................................................... 345

Run-Time Menus & Controls ........................................... 345
Run-Time File Menu .................................................. 345
Run-Time Simulation Menu ...................................... 346
Run-Time Options Menu ........................................... 346
Debug Option ............................................................. 347
Trace Options ............................................................. 351
Animation Options ..................................................... 353
Run-Time Information Menu ..................................... 353
Dynamic Plots ............................................................ 354
Run-Time Window Menu .......................................... 358
Run-Time Interact Menu ............................................ 358
Run-Time Help Menu ................................................ 358
Run-Time Controls .................................................... 359
Run-Time Right-Click Menu ..................................... 360
SimRunner ................................................................. 360

Chapter 10: Reports and Graphs .....................................................................363

Output Viewer 3DR .......................................................... 364

Menu Bar .................................................................... 364
Toolbar ....................................................................... 369
Right-click Menu ....................................................... 369
Creating Reports ............................................................... 372
Creating Charts ................................................................. 379
Chart Window ............................................................ 379
Category Chart ........................................................... 381
State Chart .................................................................. 382
Histogram ................................................................... 384
Time Plot .................................................................... 387

Chapter 11: Language Elements and Expressions ..........................................393

Language Elements .................................................... 393

Names ............................................................................... 394
Keywords .......................................................................... 395
 ProModel xiii
User Guide

Numbers ........................................................................... 396

Character Strings .............................................................. 397
Operators .......................................................................... 398
Mathematical Operators ............................................. 398
Relational Operators .................................................. 398
Comparison Operators ............................................... 398
Operator Precedence .................................................. 398
Expressions ................................................................ 398
Numeric Expressions ....................................................... 399
Boolean Expressions ........................................................ 400
Time Expressions ............................................................. 401
String Expressions ............................................................ 402
Operator Precedence ......................................................... 403

Chapter 12: Routing Rules ..............................................................................405

Routing Rules ............................................................. 405

Alternate ........................................................................... 406
Backup .............................................................................. 407
Continue ........................................................................... 408
Dependent ......................................................................... 410
Empty ............................................................................... 411
First Available .................................................................. 412
Join ................................................................................... 413
Load .................................................................................. 414
Longest Unoccupied ......................................................... 415
Most Available ................................................................. 416
Probability ........................................................................ 417
Random ............................................................................. 418
Send .................................................................................. 419
Turn .................................................................................. 420
Until Full .......................................................................... 421
User Condition .................................................................. 422
xiv

Chapter 13: Logic Elements ...........................................................................425

Functions .......................................................................... 425

System Functions ....................................................... 425
General Functions ...................................................... 425
Statements ......................................................................... 426
Distribution Functions ...................................................... 427
Priorities ........................................................................... 428

Chapter 14: Statements and Functions ............................................................429

Accum ............................................................................... 429

Activate ............................................................................. 431
Animate ............................................................................ 432
ArrayDims() ..................................................................... 433
ArrayDimSize() ................................................................ 434
Assignment Statement ...................................................... 435
Begin ................................................................................. 436
Break ................................................................................. 437
BreakBlk ........................................................................... 438
CalDay() ........................................................................... 439
CalDOM() ......................................................................... 440
CalHour() .......................................................................... 441
CalMin() ........................................................................... 442
CalMonth() ....................................................................... 443
CalYear() .......................................................................... 444
Cap() ................................................................................. 445
Char() ................................................................................ 446
Clock() .............................................................................. 447
Close ................................................................................. 448
Combine ........................................................................... 449
Comments ......................................................................... 451
Contents() ......................................................................... 452
Create ................................................................................ 453
 ProModel xv
User Guide

Debug ............................................................................... 455

Dec .................................................................................... 456
Display .............................................................................. 457
Do...Until .......................................................................... 458
Do...While ........................................................................ 459
Down ................................................................................ 460
DownQty() ........................................................................ 461
DTDelay() ......................................................................... 462
DTLeft() ........................................................................... 463
DynPlot() .......................................................................... 464
End .................................................................................... 465
Ent() .................................................................................. 466
Entity() .............................................................................. 467
Entries() ............................................................................ 468
Exp() ................................................................................. 469
ForLocation() .................................................................... 470
Format() ............................................................................ 471
ForResource() ................................................................... 472
Free ................................................................................... 473
FreeCap() .......................................................................... 474
FreeUnits() ........................................................................ 475
Get .................................................................................... 476
GetCost() .......................................................................... 478
GetReplicationNum() ....................................................... 479
GetResRate() .................................................................... 480
Goto .................................................................................. 481
Graphic ............................................................................. 482
Group ................................................................................ 483
GroupQty() ....................................................................... 485
If...Then...Else .................................................................. 486
Inc ..................................................................................... 488
IncEntCost ........................................................................ 489
IncLocCost ....................................................................... 490
IncResCost ........................................................................ 491
Int ...................................................................................... 492
xvi

Join ................................................................................... 494

Jointly Get ........................................................................ 496
Last() ................................................................................. 497
Ln() ................................................................................... 498
Load .................................................................................. 499
Loc() ................................................................................. 501
LocState() ......................................................................... 502
Location() ......................................................................... 503
Log .................................................................................... 504
MapArr ............................................................................. 506
Match ................................................................................ 508
Move ................................................................................. 510
Move For .......................................................................... 512
Move On ........................................................................... 513
Move With ........................................................................ 514
Next() ................................................................................ 516
Order ................................................................................. 517
OwnedResource() ............................................................. 518
Pause ................................................................................. 519
PercentOp() ....................................................................... 520
PercentUtil() ..................................................................... 521
Preemptor() ....................................................................... 522
Priority .............................................................................. 523
Prompt .............................................................................. 524
Rand() ............................................................................... 526
Read .................................................................................. 527
Real ................................................................................... 529
Real() ................................................................................ 530
Rename ............................................................................. 531
Report ............................................................................... 532
Res() ................................................................................. 533
Reset ................................................................................. 534
Reset Stats ........................................................................ 535
Resource() ......................................................................... 536
ResourceUnit() ................................................................. 537
 ProModel xvii
User Guide

ResQty() ........................................................................... 538

Return ............................................................................... 539
Round() ............................................................................. 541
Route ................................................................................. 542
Send .................................................................................. 544
SetRate .............................................................................. 546
Sound ................................................................................ 548
Split As ............................................................................. 549
Sqrt() ................................................................................. 551
Stop ................................................................................... 552
ThreadNum() .................................................................... 553
TimeLeft() ........................................................................ 554
TimesUsed() ..................................................................... 555
Trace ................................................................................. 556
Trunc() .............................................................................. 557
Ungroup ............................................................................ 558
Units() ............................................................................... 560
Unload .............................................................................. 561
Use .................................................................................... 563
Variable() .......................................................................... 565
View ................................................................................. 566
Wait .................................................................................. 567
Wait Until ......................................................................... 568
Warmup ............................................................................ 569
While...Do ........................................................................ 570
Write ................................................................................. 571
WriteLine .......................................................................... 572
Xsub() ............................................................................... 573
Xwrite ............................................................................... 575

Appendix A ................................................................................577

Glossary ......................................................................................591
xviii

Bibliography ...............................................................................596

Index ...........................................................................................597
 ProModel 1
User Guide

Introduction

This chapter will introduce you to the user guide, and provide information regarding assumptions this
guide makes. You may also find information on support and consulting services in this chapter.

About the User Guide model. It then provides an example scenario,

which designs a model from start to finish.
The ProModel User Guide is designed as a refer-
ence to guide you through the process of build- Chapter 4
ing, running, and viewing the results of
Modeling Environment
simulation models. The guide contains detailed
information on the use of features and capabili- Familiarizes your with the ProModel modeling
ties found within ProModel and serves as a com- environment. You will learn how to use many of
pliment to the product training. the menus and windows found in ProModel.

Chapter 1 Chapter 5
Getting Started Building the Model: general elements
Welcomes you to ProModel and provides infor- Brings you face to face with basic modeling com-
mation on getting started with the model building ponents. Discussion revolves around the nuances
process. of creating and working with locations, entities,
path networks, resources, processing records,
Chapter 2 arrivals, shifts, costs, background graphics, and
more.
Installation and Registration
Provides step-by-step instructions on how to Chapter 6
install ProModel.
Building the Model: advanced ele-
ments
Chapter 3
Planning the Model Advanced elements ensure that the models you
create reflect the exact behavior of your system.
Introduces you to the theory behind simulation Contributing elements include attributes, vari-
modeling and gives an overview of model build- ables, arrays, spreadsheets, macros, run-time
ing procedure. This chapter outlines six steps to interfaces, subroutines, arrival cycles, table func-
help you plan and create a successful, valid
2
About the User Guide

tions, user-defined distributions, external files, Discussion focuses on names, reserved words,
and streams. numbers, strings, operators, and basic syntactical
structure, as well as operator precedence and
Chapter 7 numeric, Boolean, time, and string expressions.
Building the Logic
Chapter 12
Applying intelligence and decision-making capa-
bilities to your models makes them true to life.
Routing Rules
The logic builder helps you create and implement Provides syntax and examples for the rules you
logic for operations, routings, shifts, breaks, and will use to route between locations in the model.
more.
Chapter 13
Chapter 8 Logic Elements
Using Auxiliary Tools Introduces the different types of functions and
Auxiliary tools allow you to work with many statements available to use in building logic for
aspects of your model. You may create and mod- your model and identifies where you may use
ify graphics, search for expressions, or examine them.
which statistical distributions best suit your mod-
eling needs. Chapter 14
Statements and Functions
Chapter 9
Provides syntax and examples for the statements
Running the Model and functions you will use to apply intelligence
Running the model is the most exciting part of and decision-making capabilities to your model.
the modeling process. This chapter discusses the
various conditions under which you may run a Appendix A
model and how to ensure that the model contains
no logical errors. Presents a categorized list of all expressions,
statements, and functions with a table identifying
which fields evaluate at translation and which
Chapter 10 evaluate continuously.
Reports and Graphs
With the simulation complete, you are ready to Appendix B
examine the results from the model. Options
Gives instructions for the Classic Output Viewer
available include reports, graphs, spreadsheets,
and customized output templates.
Glossary
Chapter 11 Contains definitions and descriptions for many of
Language Elements and Expressions the terms and concepts common to simulation
and modeling.
Describes the basics of the language used to
define model objects and logic, as well as expres-
sions and the role they play in creating models.
 ProModel 3
User Guide

Bibliography Symbols and Notation

Referenced materials and suggested readings. To better help you navigate this text, please
review the following symbols and conventions.

Keyboard
The names of keys are displayed in capital letters.
For example, ESC refers to the Escape key and
CTRL refers to the Control key.
Keys are frequently specified in combinations or
in a sequence of keystrokes. For example,
CTRL + L means to hold down the CTRL key
while pressing L. When key commands are set
off by commas (e.g., ALT + N, R), press and
release each of these keys (or key combinations)
in the order listed. The term “arrow keys” refers
collectively to the ×, Ø, Õ, and Ö cursor keys.

Text
Specific text you are asked to type is shown in
bold type. For example, if you are directed to
type cd pmod, you would type the lowercase let-
ters “cd” followed by a space and the letters
“pmod.”
Place holders for things such as file names and
directories are shown in italics. For example, if
you are directed to type filename.mod, enter the
name of the file you wish to use (e.g.,
model_1.mod).

Logic
All ProModel reserved keywords are in upper-
case.

Syntax example:

IF Start_Time = 10 THEN INC Var1

4
Product Support

Product Support Telephone (888) PROMODEL

Speak to a technical support engineer and resolve
Technical support is available to all licensed Pro- the problem over the phone. Our support lines are
Model users with current maintenance and sup- open Monday through Friday from 6:00 AM to
port agreements. Support representatives are glad 6:00 PM MST. The technical support number is
to answer specific questions you may have and
(888) PROMODEL.
offer direction in solving specific modeling chal-
lenges you encounter.
After Hours Support (801) 362-8324
In our ongoing effort to serve you better, techni-
Technical support
cal support is also available after hours. Please
have ready your user profile and a description of
Technical support is available via: telephone, fax, the problem you encountered.
ftp, and email. When you contact technical sup-
port, please be prepared to provide your user pro- Fax (801) 226-6046
file and a description of any problems you
experience. Send a fax of the listing created when you select
Print Text from the File menu along with your
User Profile user profile and a description of the problem you
encountered.
• Your name and company.
• The license # or serial # found on your secu- FTP
rity key or ProModel CD.
• Hardware make and configuration. For file transfers to and from ProModel Corpora-
• Network information (if applicable).
tion via file transfer protocol, contact technical
support
• Version number of Windows and ProModel.

Email [email protected]
Problem Description
When you contact technical support via email,
• Brief description of the problem you are
send your user profile and a description of the
experiencing.
problem you encountered.
• What you were doing when the problem
occurred.
• The exact wording of any messages that
appeared on your screen.
 ProModel 5
User Guide

Modeling Services Reporting Suggestions

If you find yourself in need of extra help or spe- It is our goal to make ProModel the ultimate
cific expertise to complete your simulation manufacturing simulation tool. To do this, we
project, let us help you. ProModel Corporation rely on your input. Please feel free to submit
Modeling Services will meet all of your needs comments and ideas on how we may improve the
with fast, accurate results at competitive rates. ProModel software and documentation.
Whether simple or complex, partial or complete,
ProModel Corporation Modeling Services can Send us your comments
create any model you require. With our vast
experience in producing simulation models for ProModel Product Team
many diverse applications, we are in a unique ProModel Corporation
position to evaluate your system and isolate spe- 556 E. Technology Way
cific improvements. We work closely with you Orem, UT 84097
during the development process to ensure that the
model we create is complete and precise. Phone (801) 223-4600
Fax (801) 226-6046
With each simulation ProModel Corporation pro- Email [email protected]
vides a complete, comprehensive analysis of your
system. We document conclusions and results
derived from the project and present you with sta-
tistics suitable for company presentations and
briefings. You may even present a limited version
of the model which allows repeated executions
and minor revision capabilities.

For more information on modeling

services, please contact:

Phone (801) 223-4600

Fax (801) 226-6046
6
Reporting Suggestions
 ProModel 7
User Guide

Chapter 1: Getting Started

Welcome to ProModel • Transfer lines• JIT and KANBAN systems

• Flexible Manufacturing systems• Supply
ProModel is a powerful, Windows-based simula- chains & logistics
tion tool for simulating and analyzing production
systems of all types and sizes. ProModel provides
the perfect combination of ease-of-use and com- Use of ProModel requires only a brief orientation
plete flexibility and power for modeling nearly and virtually no programming skills. With Pro-
any situation, and its realistic animation capabili- Model's convenient modeling constructs and
ties makes simulation come to life. graphical user interface, model building is quick
and easy. All you do is define how your particular
ProModel provides engineers and managers the
system operates, mostly through part flow and
opportunity to test new ideas for system design or
operation logic. Automatic error and consistency
improvement before committing the time and
checking help ensure that each model is complete
resources necessary to build or alter the actual
prior to simulation. During simulation, an ani-
system. ProModel focuses on issues such as
mated representation of the system appears on the
resource utilization, production capacity, produc-
screen. After the simulation, performance mea-
tivity, and inventory levels. By modeling the
sures such as resource utilization, productivity
important elements of a production system such
and inventory levels are tabulated and may be
as resource utilization, system capacity, and pro-
graphed for evaluation
duction schedules, you can experiment with dif-
ferent operating strategies and designs to achieve
the best results. Where to Go from Here
As a discrete event simulator, ProModel is 1. In order to use ProModel effectively, you
intended primarily for modeling discrete part must understand the basics of the Microsoft
manufacturing systems, although process indus- Windows operating environment. If you are
tries can be modeled by converting bulk material unfamiliar with Windows you should begin
into discrete units such as gallons or barrels. In by reviewing the help information. To do
addition, ProModel is designed to model systems this, select Help from the Start menu. If you
where system events occur mainly at definite are an accomplished Windows user, you can
points in time. Time resolution is controllable and proceed to the next step.
ranges from .01 hours to .00001 seconds. 2. To begin using ProModel you must install
• Typical applications for using ProModel the software. This is described in Chapter 2:
include: Installation and Registration.
• Assembly lines• Job Shops 3. You will want to become familiar with the
basic theory of model building, and review
8 Chapter 1:
Welcome to ProModel

the model building scenario, which is cov- office at (801) 223-4600 and ask for the Pro-
ered in chapter 3: Planning the Model. If you Model Product Team.
are already familiar with modeling theory, or
just want to jump into model building, skip
to the next step.
4. ProModel incorporates an easy-to-use as
well as intuitive user interface. Chapter 4:
Modeling Environment will introduce you to
the menus and options you will use to build
your model.
5. Build your model. Chapters 5 and 6: Build-
ing the Model propel you into model build-
ing by describing the Build menu, which
gives you access to most of the tools needed
to build your model.
6. Refer to Chapter 7: Building the Logic dur-
ing the model building process to learn the
logical elements that will control your model
during simulation.
7. Run your model. See you model come to life
as its animation runs. Chapter 9: Running the
Model outlines the process of running a
model.
8. View, analyze, and display the data your
model collected during simulation. With this
information in hand you are ready to make
real-world decisions to achieve your model-
ing goals. Chapter 10: Reports and Graphs
describes the Output Viewer, which presents
you with your simulation’s data.

Training
Although the tutorial and documentation are both
self contained, first-time users are strongly
encouraged to seek formal training at some point
before embarking on a complex modeling
project. PROMODEL Corporation holds training
courses on a regular basis for beginning and
advanced users of PROMODEL simulation prod-
ucts. For details on course dates and times, or to
register for the course nearest you, call our main
 ProModel 9
User Guide

Using ProModel graphical tools for placing locations, path net-

works and other modeling elements.
ProModel views a production system as an
arrangement of processing locations, such as
machines or work stations, through which parts
(or entities) are processed according to some pro-
cessing logic. A system may also include paths,
such as aisle-ways for movement, as well as sup-
porting resources, such as operators and material
handling equipment used in the processing and
movement of parts.
The example below depicts a typical manufactur-
ing workcell with six processing locations
(Receiving, NC_301L, NC_302L, Degrease,
Inspect, Rework), two entity types (Pallets and
Blanks), two operators, and one transporting
device (forklift). Models such as this are devel-
oped rapidly and easily using ProModel's graphi-
cal user interface and point-and-click approach to
modeling. Modules may be completed in any order and with
any amount of switching back and forth between
modules. However, with certain exceptions, it is
recommended that modules be completed in the
general order in which they appear in the menu.
For example, it is usually best to identify and
place locations in a model, and define the entities
to be processed at those locations, before actually
defining processing logic. This is generally
accepted since processing logic describes the
flow of entities from location to location and the
operations performed on, for, or in behalf entities
at each location.
Building Models
Edit Tables
Models are created by completing the necessary
modules selected from the Build menu shown Edit tables, such as the Locations edit table, are
below. Each module consists of various edit used extensively throughout ProModel for defin-
tables and dialog boxes used to supply model ing model elements. Edit tables provide direct
information. A layout window also appears with access to model data without wading though sev-
eral levels of dialog boxes. Each table consists of
records, which consist of fields describing some
aspect of the element. Many of these fields have
heading buttons you can click (or select and press
10 Chapter 1:
Using ProModel

F2) to open a dialog box for further definition of every statement and function, allowing you to
the particular element. define logic by simply filling in the blanks.

Dialog Boxes
Dialog boxes are used throughout ProModel for
selecting options. The Decision Rules dialog
shown below contains additional information
regarding a location.

To access the Logic Builder, click the right

mouse button in any edit box which accepts an
expression or anywhere inside an open logic win-
dow. You may also click the Build button on the
logic window's toolbar.

Model Merging and Submodels

Logic Builder Another extremely useful feature in ProModel is
The Logic Builder in ProModel provides a quick the ability to merge two or more models into one
and powerful way to create and insert valid state- larger model. This supports the concept of modu-
ments and expressions in logic windows or fields. lar model building, where models are created and
It takes you through the process of creating state- tested in modules, and then joined together to
ments or expressions, as well as providing point- produce a final model.
and-click access to every element defined in your The use of sub-models further allows you to build
model. The Logic Builder handles the syntax for common model elements such as work cells and
place them repeatedly in a model. The elements
of each sub-model (i.e., locations, entities,
resources, etc.) may all be given a common prefix
 ProModel 11
User Guide

or suffix to differentiate them from the same ele- more information on running models, see “Run-
ments of another sub-model. ning the Model” on page 337.

For more information on merging models, see

“Model Merging” on page 64.
Creating Run-Time Models
On-Line Help
One of the most powerful features in ProModel is
Regardless of where you are in the model build- the ability to create models that may be run by
ing process, the on-line help system is available others who do not own the full software. PRO-
to provide context specific definitions and MODEL allows you to install the software on any
instructions. The help system can even run in the machine to run a model. However, without the
background, allowing instant access to help security key, the user has limited ability to build
whenever you need it. or make changes to a model.
Like all Windows applications, you can locate the You may wish to develop run-time models to
help you need quickly using the standard help allow the user to perform "what-if" analyses with
tools. the models. PROMODEL encourages you to
develop demonstration models, and allows you to
Running Models distribute them freely. These models can be run
by installing ProModel from the CD-Rom onto a
Completed models are run using the Simulation computer without a security key.
menu. Model data is automatically checked for
consistency and completeness before each simu-
lation begins. Trace Window
As shown in the dialog below, ProModel allows Several tools are available to help you verify and
you to specify a run length, warm-up period, validate your models. During model execution
number of replications, and other special options you may trace the activity of the simulation
before running a simulation. In addition, you may events to see exactly what is happening in the
run the models with or without animation. For
12 Chapter 1:
Using ProModel

model. The example below shows a brief portion simulation, see “Reports and Graphs” on
of a trace window. page 363.
Simulation results may be presented in either tab-
ular or graphic format, including histograms, pie
charts, plots and bar graphs. Multiple output
results can even be compared on the same chart.
The example below shows a portion of a general
report for a model.

Location Information Windows

In addition to trace files, you may track the activ-
ity at any location through a Location Informa-
tion window. This feature gives up-to-the-minute
information about a selected location, such as Graphical Analysis
current contents, total entries, and operational
In addition to the general report shown above,
state (i.e., idle, blocked, or in operation).
almost all report elements of a model may be dis-
played graphically. Below is an example of a Cat-
egory Chart.

Viewing Output
The output generator gathers statistics on each
location, entity, resource, path network, and vari-
able in the system. You may, however, turn off
reporting capability for any element you do not
wish to include. The default level of statistics is
at the summary level (i.e., average values, % val-
ues, and final values), although detailed history
plots can be gathered on such things as utiliza-
tion, queue fluctuations, and variable values. For
more information about viewing the results of a
 ProModel 13
User Guide

Utilization Graphs
Quickly generate utilization graphs of various
types such as the State Chart shown below.

Timeplots
In addition to Category and State Charts, Time-
plot Charts, which show variable values as they
change over time, can be created.
14 Chapter 1:
Using ProModel
 ProModel 15
User Guide

Chapter 2: Installation and Reg-

istration

General Setup Information Installation Procedure for a

This section describes how to install and register Stand-alone PC
ProModel.
The installation program will decompress and
copy files from the CD-ROM into user specific
Hardware Requirements directories.

Minimum Technical Support

Pentium 3 - 800 MHz or better
512 MB RAM If you encounter problems during installation,
200 MB Free Disk Space please call the Product Team at (888) PRO-
32 MB Video Card (1024 x 768 x 16 bit color) MODEL between 6:00 AM and 6:00 PM MST,
CD ROM Monday through Friday. We will be glad to help
Mouse you get up and running.
Windows 2000 or higher

Recommended
How to install ProModel:
Core 2 Duo or better
2 GB RAM
1. Start Windows.
256 MB Video Card (1280 x 1024 x 32 bit color)
SVGA Monitor (1280 x 1024 x 32 bit color) 2. Insert the CD-ROM.
1 GB free disk space, CD ROM 3. Select the language that you would like to use dur-
Speakers ing the installation. By choosing a specific language,
Internet access you are also choosing to install language-specific demo
Mouse models and other files.
Windows Vista, XP
16 Chapter 2:
Installation Procedure for a Stand-alone PC

4. The ProModel Setup program will open automati- drive space permits, it is recommended that you allow
cally, and display the following window. the Setup program to backup previous files. When you
are ready to continue with the installation, click Next.
10. The Setup program is now ready to install Pro-
Model on your computer. If you wish to make changes
to the options you have previously selected, click the
Back button to return to any point in the installation
you wish. Otherwise, click Next to allow the Setup
program to install ProModel.

The Setup program may require you to reboot

your computer during the setup. If you do so, the
Setup program will automatically launch after the
reboot, and the installation will continue.
Please note When you have completed the installation, you
can run ProModel from the Windows Start menu.
If the Setup Program did not open automatically,
Upon running ProModel for the first time, you
select Run... from the Windows Start menu. Type
will be prompted to register ProModel. For
x:\install.exe (where x is the CD-ROM drive let-
instruction on doing so, see the section at the end
ter) and press ENTER. The proper dialog will the
of this chapter on registering ProModel.
appear

5. Click Next to proceed with the installation

6. Review the License Agreement. If you wish to
accept the agreement and continue with the installa-
tion, select the button to accept the agreement, and then
click Next.
7. Select Standard Package and click Next.
8. From the dialog that appears, choose the compo-
nents that you would like the Setup program to install.
It is recommended that you allow the Setup program to
install all components, hard drive space permitting.
When you have finished selecting your components,
click Next.
9. The next dialog allows you to have the Setup pro-
gram create backups of any files that might be replaced
during the installation. This is helpful if you are install-
ing this version of the ProModel software on a com-
puter that already has ProModel installed on it. If hard
 ProModel 17
User Guide

Installation Procedure for nets, see “Find a License Key Server on a Routed
Network” on page 21.
Network Version
In a multi-user environment, license tracking
with multiple keys is difficult. To combat this,
Set Up Network License Server
PROMODEL Corporation offers a network ver-
sion of ProModel that allows a single machine to The license server consists of the security key
control license usage (via a network connection) that plugs into the license server’s USB port, and
for several users. To use this method of license the license manager software. When installed, the
tracking, you must install a network version of license server responds to ProModel license
ProModel. The network version of ProModel requests and allows workstations to run either a
includes a hardware security key and the license full version (if sufficient licenses are available) or
manager software you will use to control license a limited run-time version.
usage at your site.
Install Program Files
Overview
When you install and run the network version of How to install program files:
ProModel, the workstation searches your net-
work for a license key server rather than check its 1. Start Windows.
own USB port for a security key. Once it locates 2. Insert the CD-ROM.
the license key server, the workstation asks the
3. The ProModel Setup program will open automati-
license manager software (running on the key
cally, and display the following window.
server) if a license is available. If a license is
available, the license manager software will
assign a license to the workstation. When you
exit ProModel, the license you used becomes
available to another user.
Check the support web page for periodic updates
to the installation information, software configu-
ration, and the license server software for Pro-
Model.

http://www.promodel.com/support

Please note
Please note
If you are running a network version of ProModel
on a routed network and your license key server
and workstations are located on different sub- If the Setup Program did not open automatically,
select Run... from the Windows Start menu. Type
x:\install.exe (where x is the CD-ROM drive let-
18 Chapter 2:
Installation Procedure for Network Version

ter) and press ENTER. The proper dialog will the 9. From the dialog that appears, choose the compo-
appear nents that you would like the Setup program to install.
It is recommended that you allow the Setup program to
install all components, hard drive space permitting.
When you have finished selecting your components,
4. Click Next to proceed with the installation click Next.

5. Review the License Agreement. If you wish to 10. Choose the destination directory for the install. If
accept the agreement and continue with the installa- you wish to change the destination from the default,
tion, , select the button to accept the agreement, and select the Browse button and choose a new directory.
then click Next. When you have chosen the destination directory, click
Next.
6. From the dialog that appears, select Network Pack-
age. The dialog will then appear as below: 11. The next dialog allows you to have the Setup pro-
gram create backups of any files that might be replaced
during the installation. This is helpful if you are install-
ing this version of the ProModel software on a com-
puter that already has ProModel installed on it. Later, if
you choose, you can have the installation rolled back
and the original files restored. If hard drive space per-
mits, it is recommended that you allow the Setup pro-
gram to backup previous files. When you are ready to
continue with the installation, click Next.
12. The Setup program will add a new Windows Pro-
gram group containing ProModel program icons to the
Program Manager. When you have selected where you
want the Program icons to appear, click Next.
13. The Setup program is now ready to install Pro-
7. Select Install program files, and click Next. Model on your computer. If you wish to make changes
8. Select the type of hardware key you are using on the to the options you have previously selected, click the
network server. If your license server is on a different Back button to return to any point in the installation
subnet, enter the IP address of the server. Click Next. you wish. Otherwise, click Next to allow the Setup
program to install ProModel.

The Setup program may require you to reboot

your computer during the setup. If you do so, the
Setup program will automatically launch after the
reboot, and the installation will continue.
When you have completed the installation, you
must set up a license server. See “Set Up License
Server” on page 19, for information on how to do
so.
 ProModel 19
User Guide

Please note 3. The ProModel Setup program will open automati-

cally, and display the following window.
If you are running a network version of ProModel
on a routed network and your license key server
and workstations are located on different sub-
nets, see “Find a License Key Server on a Routed
Network” on page 21.

Set Up License Server

PROMODEL software monitors licensed user
activity through a security key attached to the
parallel port (for the network version of Pro-
Model, you must have the red key supplied by
PROMODEL Corporation). The machine to Please note
which you attach the key becomes the license
manager—whether it is a dedicated file server or If the Setup Program did not open automatically,
a workstation. The security server can run on select Run... from the Windows Start menu. Type
Windows 95, 98, 2000, or NT 4.0 and listen for x:\install.exe (where x is the CD-ROM drive let-
incoming license requests over any of the follow- ter) and press ENTER. The proper dialog will the
ing network protocols: IPX, TCP/IP, and Net- appear
BEUI. If the security server is not functioning,
ProModel will start as a limited run-time version.

4. Click Next to proceed with the installation

Please note
5. Review the License Agreement. If you wish to
accept the agreement and continue with the installa-
If you are running a network version of ProModel
tion, click Next.
on a routed network and your license key server
and workstations are located on different sub-
nets, see “Find a License Key Server on a Routed
Network” on page 21.

Set Up License Server:

1. Start Windows.
2. Insert the CD-ROM.
20 Chapter 2:
Installation Procedure for Network Version

6. From the dialog that appears, select Network Pack- You need to install the device driver only once.
age. The dialog will then appear as below: However, you must launch the license manager
program each time you reboot the key server
machine. To automatically start the license man-
ager each time you reboot the system, create and
place an icon for NHSRVW32.EXE in the work-
station’s startup folder.
When you have completed installing either you
local machine or server setup, and finished
installing the License Server, you are ready to run
ProModel.

Set Up License Server Manually

After successfully running the setup for the
7. Select Set up a network license server, and click
license server, if you chose to manually install the
Next.
device driver for the security key and launch the
8. Select the type of hardware key you are using on the license manager software, follow the steps below.
network server, and click Next.

Install the Device Driver:

1. Open a DOS box and run HINSTALL -i from the

directory to which you installed the license server.
2. After you receive a confirmation that the driver
installed successfully, reboot the workstation

Start the License Manager Software:

1. From the directory to which you installed the

9. The Install Wizard for the NetHASP License Man- license server, run NHSRVW32.EXE. A window will
ager will appear. Click Yes, and follow the on-screen appear and show the network protocols to which the
directions to install the manager. If you click No, you license manager will listen for license requests.
will have to set up the license server manually, which
is described in the next section.

The Setup program may require you to reboot You need to install the device driver only once.
your computer during the setup. If you do so, the However, you must launch the license manager
Setup program will automatically launch after the program each time you reboot the key server. To
reboot, and the installation will continue. automatically start the license manager each
 ProModel 21
User Guide

time you reboot the system, create and place an NH_SERVER_ADDR=<Enter the license
icon for NHSRVW32.EXE in the workstation’s server’s IP address here>
startup folder.

Find a License Key Server on a

Routed Network
In order for a workstation to run the network ver-
sion of ProModel properly, the workstation must
check out a license from a license server. To
make a license request, the workstation sends a
broadcast message out on the network and awaits
a response from the license server. If the license
server and the workstation running ProModel are
on the same sub net of a routed network (or on
the same network of a non-routed network), the
license server receives the request and responds.
Due to the nature of routed networks, if the
license server and workstation running ProModel
are not on the same sub net of a routed network,
the key server will not receive the license request
broadcast.
To resolve this problem, the workstation must
send a license request directly to the computer on
the network set up as the license server. To iden-
tify which computer on the network is the license
server, you must create and store a text file called
NETHASP.INI in the directory to which you
installed ProModel on the workstation or file
server.
For TCPIP-based network the NETHASP.INI file
must contain the following lines
[NH_COMMON]
NH_TCPIP=Enabled;

[NH_TCPIP]
NH_TCPIP_METHOD=TCP
22 Chapter 2:
Registering ProModel

Registering ProModel When you have entered your information and

clicked next, you will be prompted to enter your
Your ProModel product must be registered. If Serial Number.
you do not register ProModel, you will only have
access to a limited, evaluation version of Pro-
Model. This version will not allow expansive
model building.
The registration process for ProModel depends
on the type of installation you chose.

Registration for a Stand-alone PC

Installation
When you run ProModel for the first time after
installing it on a Stand-alone PC, you will be
prompted to register ProModel. The following
screen will appear.

Depending on your organization’s software

licensing arrangement, a Serial Number may be
included with your CD or possibly obtained by
contacting the ProModel Corporation licensing
representative for your organization.
If you do not have a Serial Number, you may still
register using the instructions “How to Register
without a Serial Number” on page 23.

How to Register with a Serial Number

1. When you have obtained a valid Serial Number,

enter it into the registration dialog, and then click the
Next button.
2. If a connection cannot be made to the ProModel
Corporation server, an Internet connectivity issue (fire-
wall, etc.) may exist. If this is the case, you will be
prompted that the registration was not successful, in
which case you may still register without a serial num-
ber. See “How to Register without a Serial Number” on
page 23.
 ProModel 23
User Guide

3. When the serial number has been successfully sent While waiting for a response from ProModel Support,
to the ProModel Corporation server, you will be given you may leave the Registration dialog open, or close it
a ProModel username and password. Record this infor- until you receive your response.
mation, since you will use it to obtain updates to Pro-
The reply you receive from ProModel Support will
Model in the future.
contain a License Key code. If you have closed Pro-
4. Check the “I have recorded this information for Model, relaunch it, and return to the Phone or Email
future use” box, and then click Exit to finish the regis- Registration window. In the “Step 2: Enter License
tration. Key” area, enter the License Key code that is in the
email reply from ProModel Support.
You may then click “Register” to complete the registra-
tion process.
How to Register without a Serial Num-
3. If you would like to register over the phone, call
ber ProModel Support at (888) PROMODEL. A ProModel
Support representative will guide you through the rest
1. If you do not have a serial number, or your serial of registration process.
number cannot be used due to Internet connectivity
issues, choose the “I do not have a Serial Number (or
registering with the serial number failed)” option, and
click Next. You will now have access to the full version of
ProModel.
If you choose not to register ProModel at this
time, click Cancel without entering registration
information. You will then have access to the lim-
ited, evaluation version of ProModel.

Registration for a Network

Installation
If you purchased a network version of ProModel,
you will have received a hardware key with your
ProModel software. To register your network ver-
sion of ProModel, simply attach the hardware
key to your computer’s LPT1 port.

2. You may choose to email (this step) or phone (next Transferring/Terminating Your
step) ProModel Support to register your product. If you Software Key
would like to email ProModel Support, follow the
“Click to send registration request” link that is next to As you use ProModel it may become necessary to
the Email option. transfer your software key from one PC to
An email message will be composed using your com- another. Please contact ProModel Corporation
puter’s default email application, and you can then technical support if you would like to move or
choose to send it. terminate your software key.
24 Chapter 2:
Registering ProModel

Checking for ProModel Updates puter’s configuration, please contact Pro-

Model Corporation technical support for
The Check for ProModel Update feature checks options to preserve your license key.
the ProModel Web server for an update to Pro- 3. My software license key no longer appears
Model, downloads any available update, and then to be functioning. What should I do?
installs the update. In order to have access to Your software license key may have been
updates, you will need a ProModel Solutions disturbed by changes to your computer’s
Cafe username and password, and a current configuration. Reboot your computer in an
Maintenance and Support agreement. If you have attempt to reset the configuration to a point
questions regarding your M&S agreement, or that is recognizable by the license key. If the
username and password, please contact Pro- problem persists, please contact ProModel
Model Technical Support at support@pro- Corporation support (1-888-PROMODEL).
model.com.
There are two ways to obtain ProModel Updates:
• Quickly check to see if an update exists by
selecting "Check for ProModel Update"
from the Help menu in the ProModel appli-
cation.
• Go to the ProModel Corporation solutions
cafe on the ProModel Website (www.pro-
model.com). You can obtain updates for any
of your ProModel products for which you
have a current support agreement.
It is recommend that you check regularly for
updates to ProModel.

Software License Key FAQ

1. I need to move my software license key to
another computer, can I do this?
Yes. Please contact ProModel Corporation
technical support if you would like to move
or terminate your software key.
2. I want to upgrade my computer’s operat-
ing system, or make a major change to my
computer’s configuration, should I be
concerned?
The software license key is sensitive to
changes to your computer’s configuration.
This is to prevent the key’s unauthorized
duplication to multiple computers. If you
plan on making major changes to your com-
 ProModel 25
User Guide

Chapter 3: Planning the Model

Steps for Doing Simulation General Procedure

A decision to do a simulation usually results from
Introduction a perception that simulation can help resolve one
or more issues associated with the design of a
Doing simulation requires more than just know- new system or the modification of an existing
ing how to use a simulation product. A simula- system. Before launching into a simulation
tion study is, by its very nature, a project. Like project, one or more individuals should have
any project, there are tasks to be completed and been assigned to the study who have at least a
resources required to complete them. To be suc- basic knowledge of the system to be studied and
cessful, a simulation project should be planned the issues of concern. Enough background infor-
with an understanding of the requirements of mation should have been obtained about the
each of the tasks involved. Many failures result nature of the problem to determine whether simu-
from hastily jumping into a simulation without lation is a suitable solution. If the simulation is
first taking time to consider the steps involved being conducted by individuals inside the com-
and developing a plan for proceeding. pany, there may already be a basic knowledge of
the operation. For outsiders or those unfamiliar
Simulation modeling requires good analytical,
with the operation, a brief description of the sys-
statistical, communication, organizational, and
tem and explanation of key issues should be pro-
engineering skills. The modeler must understand
vided. For an existing system, a facility walk-
the system being investigated and be able to sort
through is an excellent way of getting familiar
through complex cause-and-effect relationships
with the operation.
that determine system performance. At least a
basic foundation in statistics is needed to prop- Once a suitable application or project has been
erly design experiments and correctly analyze identified as a candidate for simulation, decisions
and interpret input and output data. Ongoing must be made about how to conduct the study.
communication with owners, stakeholders, and There are no strict rules on how to perform a sim-
customers during a simulation study is also vital ulation study, however, the following steps are
to ensure that a purposeful model is built and that generally recommended as a guideline (Shannon,
everyone understands the objectives, assump- 1975; Gordon, 1978; Law, 1991):
tions, and results of the study.
1. Plan the study
2. Define the system
3. Build the model
4. Run experiments
5. Analyze the output
26 Chapter 3:
Steps for Doing Simulation

6. Report results ensure that the project is conducted in an orga-

nized, timely fashion with minimal waste of time
Each step need not be completed in its entirety
and resources and maximum effectiveness in
before moving on to the next step. The procedure
achieving the objectives.
for doing a simulation is an iterative one in which
activities are refined and sometimes redefined
with each iteration. Describing this iterative pro- Step 1: Planning the Study
cess, Pritsker and Pegden (1979) observe the fol-
lowing. Many simulation projects are doomed to failure
from the outset due to poor planning. Undefined
The iterative nature of this process is shown next: objectives, unrealistic expectations and a general
lack of understanding of requirements frequently
result in frustration and disappointment. If a sim-
ulation project is to be successful, a plan must be
developed which is realistic, clearly communi-
cated and closely followed. Planning a simulation
study involves the following sub tasks:
• Defining Objectives
• Identifying Constraints
• Preparing a Simulation Specification
• Developing a Budget and Schedule
Each of these tasks is discussed in the following.

Defining Objectives
With a basic understanding of the system opera-
tion and an awareness of the issues of concern or
interest, one or more objectives can be defined
for the study. Simulation should only be used if
an objective can be clearly stated and it is deter-
mined that simulation is the most suitable tool for
achieving the objective. Defining an objective
does not necessarily mean that there needs to be a
problem to solve. A perfectly valid objective may
be to see if there are, in fact, any unforeseen
problems. Common types of objectives for a sim-
ulation study include the following:
Procedure for Conducting a Simulation Study • Performance Analysis How well does the
While the requirements for each step vary from system perform under a given set of circum-
simulation to simulation, the basic procedure is stances in all measures of significance (utili-
essentially the same. The primary value of adopt- zation, throughput, waiting times, etc.)?
ing this systematic procedure, or one like it, is to
 ProModel 27
User Guide

• Capacity Analysis What is the maximum intended for use by managers with little simula-
processing or production capacity of the sys- tion background and must be easy to use. Some
tem? models are used to make decisions of minor con-
• Capability Analysis Is the system capable of sequence. Other models are relied upon to make
meeting specific performance requirements major financial decisions.
(throughput, waiting times, etc.), and, if not,
Realizing the objectives of a simulation should
what changes (added resources or improved
consider both the purpose as well as the intended
methods) are recommended for making it
use of the model, the following questions should
capable?
be asked when defining the objectives of the
• Comparison Study How well does one sys- study:
tem configuration or design variation per-
form compared to another? • Why is the simulation being performed?
• Sensitivity Analysis Which decision vari- • Who will be using the model?
ables are the most influential on one or more • To whom will the results of the simulation be
performance measures, and how influential presented?
are they? • What information is expected from the
• Optimization Study What combination of model?
feasible values for a given set of decision • Is this a “throw-away” model?
variables best achieves desired performance • How important is the decision being made?
objectives?
• Decision/Response Analysis What are the Identifying Constraints
relationships between the values of one or
more decision variables and the system Equally as important as defining objectives is
response to those changes? identifying the constraints under which the study
• Constraint Analysis Where are the con- must be conducted. It does little good if simula-
straints or bottlenecks in the system and tion solves a problem if the time to do the simula-
what are workable solutions for either reduc- tion extends beyond the deadline for applying the
ing or eliminating those constraints? solution, or if the cost to find the solution exceeds
the benefit derived. Objectives need to be tem-
• Communication Effectiveness What vari-
ables and graphic representations can be pered by the constraints under which the project
must be performed such as the budget, deadlines,
used to most effectively depict the dynamic
resource availability, etc. It is not uncommon to
behavior or operation of the system?
begin a simulation project with aspirations of
Defining the objective should take into account developing an impressively detailed model or of
what the ultimate intended use of the model will creating a stunningly realistic animation only to
be. Some models are built as “throw-away” mod- scramble at the last minute, throwing together a
els to be used only once and then discarded. crude model that barely meets the deadline.
Other models are built to be used on an ongoing
basis for continued “what-if” analyses. Some Constraints should not always be viewed as an
models need only provide a quantitative answer. impediment. If no deadlines or other constraints
Others require realistic animation to convince a are established, there is a danger of getting too
skeptical customer. Some models are intended for involved and detailed in the simulation study and
use by only the analyst. Other models are run the risk of “paralysis from analysis.” The
28 Chapter 3:
Steps for Doing Simulation

scope of any project has a tendency to shrink or a particular activity has on achieving the objec-
expand to fill the time allotted. tives of the simulation. A common tendency is to
model the entire system, even when the problem
In identifying constraints, anything that could
area and all relevant variables are actually iso-
have a limiting effect on achieving the desired
lated within a smaller subsystem. If, for example,
objectives should be considered. Specific ques-
the objective is to find the number of operators
tions to ask when identifying constraints for a
required to meet a required production level for a
simulation study include the following:
machining cell, it is probably not necessary to
• What is the budget for doing the study? model what happens to parts after leaving the
• What is the deadline for making the deci- cell.
sion? The following figure illustrates how the scope of
• What are the skills of those doing the study? the model should be confined to only those activ-
• How accessible is the input data? ities whose interactions have a direct bearing on
• What computer(s) will be used for the study? the problem being studied. Upstream and down-
stream activities that do not impact the perfor-
Preparing a Simulation Specification mance measure of interest should be omitted
from the model. In the following figure, since the
With clearly defined objectives and constraints, output rate from activity A is predictable, it can
the simulation requirements can be specified. be modeled as simply an arrival rate to activity B.
Defining a specification for the simulation is Since activity E never constrains output from
essential to projecting the time and cost needed to activity D, it can also be ignored.
complete the study. It also guides the study and
helps set expectations by clarifying to others
exactly what the simulation will include or
exclude. A specification is especially important if
the simulation is being performed by an outside
consultant so that you will know exactly what
you are getting for your money. Aspects of the Confining the Scope to Impacting Activities
simulation project to be contained in the specifi-
cation include the following:
Level of Detail Project the level of detail defines
• Scope the depth or resolution of the model. At one
• Level of detail extreme, an entire factory can be modeled as a
• Degree of accuracy single “black box” operation with a random
• Type of experimentation activity time. At the other extreme, every detailed
• Form of results motion of a machine could be modeled with a
one-to-one correspondence depicting the entire
Each of these specification criteria will be dis-
machine operation.
cussed in the following pages.
Unlike the model scope which affects only the
Scope The scope refers to the breadth of the
size of the model, the level of detail affects model
model or how much of the system the model will
complexity as well as model size. Determining
encompass. Determining the scope of the model
the appropriate level of detail is an important
should be based on how much bearing or impact
decision. Too much detail makes it difficult and
 ProModel 29
User Guide

time consuming to develop a valid model. Too gather data. It often has little impact, however, on
little detail may make the model too unrealistic the model building time since a model can be
by excluding critical variables. The following built with estimated values that can later be
figure illustrates how the time to develop a model replaced with more accurate values. Output pre-
is affected by the level of detail. It also highlights cision is often governed by the degree of accu-
the importance of including only enough detail to racy of the model.
meet the objectives of the study.
Type of Experimentation The number and nature
One to One
Correspondence
of the alternative solutions to be evaluated should
be planned from the outset in order to ensure that
adequate time is allotted. This decision is often
Minimum
Required influenced by the deadline constraints of the
study. Where alternatives with only slight differ-
Level of
Detail ences are to be evaluated, a base model can be
developed requiring only minor modifications to
model each alternative. If alternative configura-
Model Development Time tions are significantly different, it may require
nearly as much effort modeling each configura-
Effect of Level of Detail on Model Development tion as it does developing the initial model.
Time
For studies in which improvements to an existing
system are being considered, it is often helpful
and effective to model the current system as well
The level of detail is determined largely by the as the proposed system. The basic premise is that
degree of precision required in the output. If only you are not ready to make improvements to a sys-
a rough estimate is being sought, it may be suffi- tem until you understand how the current system
cient to model each activity by its time, rather operates. Information on the current system is
than specific details making up the activity. If, on easier to obtain than information on areas of
the other hand, details such as downtimes or change. Once a model of the current system is
move times have an appreciable effect on the out- built, it is often easier to visualize what changes
come of the model, they should be included. need to be made for the modified system. Both
Degree of Accuracy The degree of accuracy per- systems may even be modeled together in the
tains to the correctness of the data being used. same simulation and made to run side by side.
For some models or activities, the information During the final presentation of the results, being
need not be as accurate or exact as it does for oth- able to show both “as is” and “to be” versions of
ers. The required degree of accuracy is deter- the system effectively demonstrates the impact
mined by the objectives of the study. If the changes can have on system performance.
decision is important or a comparison is close, Form of Results The form in which the results
greater accuracy may be required. Accuracy are to be presented can significantly affect the
sometimes has to be sacrificed if reliable infor- time and effort involved in the simulation study.
mation is simply unavailable such as when mod- If detailed animation or an extensive report is
eling a completely new system. expected, the project can easily stretch on for
The required degree of accuracy can have a sig- several weeks after the experimental phase has
nificant impact on the time and effort required to been completed. Many times the only result
30 Chapter 3:
Steps for Doing Simulation

required is a simple verification of whether a sys- Step 2: Defining the System

tem is capable of meeting a production require-
ment. In such cases, a simple answer will suffice. With clearly defined objectives and a well orga-
nized plan for the study, the system that will be
simulated can begin to be defined in detail. This
Developing a Budget and Schedule
can be viewed as the development of a concep-
With objectives and constraints clearly defined tual model on which the simulation model will be
and a specification prepared identifying the work based. The process of gathering and validating
to be performed, a budget and schedule should be system information can be overwhelming when
developed projecting the expected cost and time faced with the stacks of uncorrelated data to sort
for completing the simulation project. Obviously, through. Data is seldom available in a form that
the time to perform a simulation project will vary defines exactly how the system works. Many data
depending on the size and difficulty of the gathering efforts end up with lots of data but very
project. If data is not readily available, it may be little useful information.
necessary to add several additional weeks to the
project. A small project can take two to four Data gathering should never be performed with-
weeks while large projects can take two to four out a purpose. Rather than being haphazard, data
months. A simulation schedule should be based gathering should be goal oriented with a focus on
on realistic projections of the time requirements information that will achieve the objectives of the
keeping in mind the following: study. There are several guidelines to keep in
mind when gathering data.
• Defining the system to be modeled can take
• Identify cause-and-effect relationships It is
up to 50% of the project time.
important to correctly identify the causes or
• Model building usually takes the least
conditions under which activities are per-
amount of time (10 to 20%).
formed. In gathering downtime data, for
• Once a base model is built, it can take sev-
example, it is helpful to distinguish between
eral weeks to conduct all of the desired
downtimes due to equipment failure or per-
experiments, especially if alternative designs
sonal emergencies and planned downtimes
are being compared.
for break. Once the causes have been estab-
While it may have initially been determined that lished and analyzed, activities can be prop-
simulation is a suitable tool for achieving the erly categorized.
objective, the decision to use simulation may
need to be reconsidered in light of projected cost • Look for key impact factors Discrimination
and time estimates. Simulation may be a good should be used when gathering data to avoid
solution to the problem at hand, but if the time or wasting time examining factors that have lit-
the cost of doing the project outweighs the antici- tle or no impact on system performance. If,
pated benefits, either an alternative solution may for example, an operator is dedicated to a
need to be explored or the objectives may need to particular task and, therefore, is never a
be modified to cut down on the level of effort cause of delays in service, there is no need to
required. include the operator in the model. Likewise,
extremely rare downtimes, negligible move
times and other insignificant or irrelevant
activities that have no appreciable effect on
 ProModel 31
User Guide

routine system performance may be safely important for the modeler to be constantly
ignored. thinking abstractly about the system opera-
tion in order to avoid getting too caught up in
• Distinguish between time and condition depen- the incidental details.
dent activities Time-dependent activities are
those that take a predictable amount of time • Separate input variables from response vari-
to complete, such as customer service. Con- ables Input variables in a model define how
dition-dependent activities can only be com- the system works (e.g., activity times, rout-
pleted when certain defined conditions ing sequences, etc.). Response variables
within the system are satisfied. Because con- describe how the system responds to a given
dition-dependent activities are uncontrolla- set of input variables (e.g., work-in-process,
ble, they are unpredictable. An example of a idle times, resource utilization, etc.). Input
condition-dependent activity might be the variables should be the focus of data gather-
approval of a loan application contingent ing since they are used to define the model.
upon a favorable credit check. Response variables, on the other hand, are
the output of a simulation. Consequently,
Many activities are partially time-dependent response variables should only be gathered
and partially condition-dependent. When later to help validate the model once it is
gathering data on these activities, it is impor- built and run.
tant to distinguish between the time actually
These guidelines should help ensure that the sys-
required to perform the activity and the time
tem is thought of in the proper light for simula-
spent waiting for resources to become avail-
tion purposes.
able or other conditions to be met before the
activity can be performed. If, for example, To help organize the process of gathering data for
historical data is used to determine repair defining the system, the following steps are rec-
times, the time spent doing the actual repair ommended:
work should be used without including the
• Determine data requirements.
time spent waiting for a repair person to
• Use appropriate data sources.
become available.
• Make assumptions where necessary.
• Convert data into a useful form.
• Focus on essence rather than substance A
system definition for modeling purposes • Document and approve the data.
should capture the key cause-and-effect rela- Each of these steps is explained on the following
tionships and ignore incidental details. Using pages.
this “black box” approach to system defini-
tion, we are not concerned about the nature Determining Data Requirements
of the activity being performed, but only the
impact that the activity has on the use of The first step in gathering system data is to deter-
resources and the delay of entity flow. For mine what data is required for building the
example, the actual operation performed on a model. This should be dictated primarily by the
machine is not important, but only how long scope and level of detail required to achieve the
the operation takes and what resources, if model objectives as described earlier. It is best to
any, are tied up during the operation. It is go from general to specific in gathering system
32 Chapter 3:
Steps for Doing Simulation

data. The initial focus should be on defining the 3. Besides route locations, what types of
overall process flow to provide a skeletal frame- resources (personnel, vehicles, equipment)
work for attaching more detailed information. are used in the system and how many units
Detailed information can then be added gradually are there of each type (resources used inter-
as it becomes available (e.g., resource require- changeably may be considered the same
ments, processing times, etc.). Starting with the type)?
overall process flow not only provides an orderly 4. What is the routing sequence for each entity
approach to data gathering, but also enables the type in the system?
model building process to get started which 5. What activity, if any, takes place for each
reduces the amount of time to build and debug entity at each route location (define in terms
the model later. Often, missing data becomes of time required, resources used, number of
more apparent as the model is being built. entities involved and any other decision
logic that takes place)?
In defining the basic flow of entities through the
6. Where, when and in what quantities do enti-
system, a flow diagram can be useful as a way of
ties enter the system (define the schedule,
documenting and visualizing the physical flow of
interarrival time, cyclic arrival pattern, or
entities from location to location. Once a flow
condition which initiates each arrival)?
diagram is made, a structured walk-through can
7. In what order do multiple entities depart
be conducted with those familiar with the opera-
from each location (First in, First out; Last
tion to ensure that the flow is correct and that
in, First out)?
nothing has been overlooked. The next step
8. In situations where an output entity could be
might be to define the detail of how entities move
routed to one of several alternative locations,
between locations and what resources are used
how is the routing decision made (e.g., most
for performing operations at each location. At
available capacity, first available location,
this point it is appropriate to identify location
probabilistic selection)?
capacities, move times, processing times, etc.
9. How do entities move from one location to
To direct data gathering efforts and ensure that the next (define in terms of time and
meetings with others, on whom you depend for resources required)?
model information, are productive, it may be use- 10. What triggers the movement of entities from
ful to prepare a specific list of questions that one location to another (i.e., available capac-
identify the data needed. A list of pertinent ques- ity at the next location, a request from the
tions to be answered might include the following: downstream location, an external condition)?
11. How do resources move from location to
1. What types of entities are processed in the
location to perform tasks (define either in
system and what attributes, if any, distin-
terms of speed and distance, or time)?
guish the way in which entities of the same
12. What do resources do when they finish per-
type are processed or routed?
forming a task and there are no other tasks
2. What are the route locations in the system
waiting (e.g., stay put, move somewhere
(include all places where processing or queu-
else)?
ing occurs, or where routing decisions are
13. In situations where multiple entities could be
made) and what are their capacities (i.e., how
waiting for the same location or resource
many entities can each location accommo-
when it becomes available, what method is
date or hold at one time)?
used for making an entity selection (e.g.,
 ProModel 33
User Guide

longest waiting entity, closest entity, highest • Equipment Manufacturers

priority, preemption)? • Managers
14. What is the schedule of availability for • Engineers
resources and locations (define in terms of • Facility Walk-throughs
shift and break schedules)? • Comparisons with Similar Operations
15. What planned interruptions do resources and
locations have (scheduled maintenance, In deciding whether to use a particular source of
setup, changeover)? data, it is important to consider the relevancy,
16. What random failures do resources and loca- reliability and accessibility of the source. If the
tions experience (define in terms of distribu- information that a particular source can provide is
tions describing time to failure and time to irrelevant for the model being defined, then that
repair)? source should not be consulted. What good is a
maintenance report if it has already been decided
Depending on the purpose of the simulation and that downtimes are not going to be included in
level of detail needed, some of these questions the model? Reliability of the source will deter-
may not be applicable. For very detailed models mine the validity of the model. A managers per-
additional questions may need to be asked. ception, for example, may not be as reliable as
Answers to these questions should provide nearly actual production logs. Finally, if the source is
all of the information necessary to build a model. difficult to access, such as a visit to a similar
facility in a remote site, it may have to be omit-
Using Appropriate Data Sources ted.
Having a specific set of questions for defining the
system, we are now ready to search for the Making Assumptions
answers. Information seldom comes from a sin- Not long after data gathering has started, you
gle source. It is usually the result of reviewing may realize certain information is unavailable or
reports, conducting personal interviews, personal perhaps unreliable. Complete, accurate, and up-
observation and making lots of assumptions. “It to-date data for all the information needed is
has been my experience,” notes Carson (1986), rarely obtainable, especially when modeling a
“that for large-scale real systems, there is seldom new system about which very little is known. For
any one individual who understands how the sys- system elements about which little is known,
tem works in sufficient detail to build an accurate assumptions must be made. There is nothing
simulation model. The modeler must be willing wrong with assumptions as long as they can be
to be a bit of a detective to ferret out the neces- agreed upon, and it is recognized that they are
sary knowledge.” Good sources of system data only assumptions. Any design effort must utilize
includes the following: assumptions where complete or accurate infor-
• Time Studies mation is lacking.
• Predetermined Time Standards Many assumptions are only temporary until cor-
• Flow Charts rect information can be obtained or it is deter-
• Facility Layouts mined that more accurate information is
• Market Forecasts necessary. Often, sensitivity analysis, in which a
• Maintenance Reports range of values is tested for potential impact, can
• On-line tracking systems give an indication of just how accurate the data
34 Chapter 3:
Steps for Doing Simulation

really needs to be. A decision can then be made tion table. Defining a frequency distribution is
to firm up the assumptions or to leave them done by grouping the data into intervals and stat-
alone. If, for example, the degree of variation in a ing the frequency of occurrence for each particu-
particular activity time has little or no impact on lar interval. To illustrate how this is done, the
system performance, then a constant activity time following frequency table tabulates the number
may be used. Otherwise, it may be important to and frequency of observations for a particular
define the exact distribution for the activity time. activity requiring a certain range of time to per-
form.
Another approach in dealing with assumptions is
to run three different scenarios showing a “best-
Frequency Distributions of Delivery Times
case” using the most optimistic value, a “worst-
case” using the most pessimistic value, and a Delivery Number of Cumulative
Time (days) Observations Percentage Percentage
“most-likely-case” using a best-estimate value.
This will help determine the amount of risk you 0-1 25 16.5 16.5
want to take in assuming a particular value. 1-2 33 21.7 38.2
2-3 30 19.7 57.9
Converting Data to a Useful Form 3-4 22 14.5 72.4
Data is seldom in a form ready for use in a simu- 4-5 14 9.2 81.6
lation model. Usually, some analysis and conver- 5-6 10 6.6 88.2
sion needs to be performed for data to be useful 6-7 7 4.6 92.8
as an input parameter to the simulation. Random 7-8 5 3.3 96.1
phenomena must be fitted to some standard, theo- 8-9 4 2.6 98.7
retical distribution such as a normal or exponen-
9 - 10 2 1.3 100.0
tial distribution (Law and Kelton, 1991), or be
input as a frequency distribution. Activities may
need to be grouped together to simplify the Total Number of Observations = 152
description of the system operation. While there are rules that have been proposed for
determining the interval or cell size, the best
Distribution Fitting To define a distribution using
approach is to make sure that enough cells are
a theoretical distribution requires that the data, if
defined to show a gradual transition in values, yet
available, be fit to an appropriate distribution that
not so many cells that groupings become
best describes the variable. ProModel includes
obscured.
the Stat::Fit distribution fitting package which
assists in fitting sample data to a suitable theoret- Note in the last column of the frequency table
ical distribution. An alternative to using a stan- that the percentage for each interval may be
dard theoretical distribution is to summarize the expressed optionally as a cumulative percentage.
data in the form of a frequency distribution that This helps verify that all 100% of the possibilities
can be used directly in the model. A frequency are included.
distribution is sometimes referred to as an empir-
ical or user-defined distribution. When gathering samples from a static population,
one can apply descriptive statistics and draw rea-
Whether fitting data to a theoretical distribution, sonable inferences about the population. When
or using an empirical distribution, it is often use- gathering data from a dynamic and possibly time
ful to organize the data into a frequency distribu- varying system, however, one must be sensitive
 ProModel 35
User Guide

to trends, patterns, and cycles that may occur times are not identified in the system description,
with time. The samples drawn may not actually a statement of explanation should be made
be homogenous samples and, therefore, unsuit- explaining why. Stating why certain factors are
able for applying simple descriptive techniques. being excluded from the system description will
help resolve later concerns that may question
Activity Grouping Another consideration in con-
why the factors were omitted.
verting data to a useful form is the way in which
activities are grouped for modeling purposes. Validating system data can be a time-consuming
Often it is helpful to group activities together so and difficult task, especially when many assump-
long as important detail is not sacrificed. This tions are made. In practice, data validation ends
makes models easier to define and more manage- up being more of a consensus or agreement that is
able to analyze. In grouping multiple activities obtained confirming that the information is good
into a single activity time for simplification, con- enough for the purposes of the model. While this
sideration needs to be given as to whether activi- approved data document provides the basis for
ties are performed in parallel or in series. If building the model, it often changes as model
activities are done in parallel or with any overlap, building and experimentation get under way.
the time during which overlapping occurs should
not be additive.
Step 3: Building the Model
Serial activities are always additive. For example,
if a series of activities is performed on an entity at Once sufficient information has been compiled to
a location, rather than specifying the time for define the basic system operation, the model
each activity, it may be possible to sum activity building activity can begin. While starting to
times and enter a single time or time distribution. build a model too early can be a wasted exercise,
waiting until all of the information is completely
gathered and validated may unnecessarily post-
Documenting and Approving the Data pone the building of the model. Getting the
When it is felt that all relevant information has model started before the data is completely gath-
been gathered and organized into a usable form, it ered may even help identify missing information
is advisable to document the information in the needed to proceed.
form of data tables, relational diagrams and
The goal of model building is to provide a valid
assumption lists. Sources of data should also be
representation of the defined system operation.
noted. This document should then be reviewed by
Additionally, the model must be able to provide
others who are in a position to evaluate the valid-
any other statistical or graphical representation
ity of the data and approve the assumptions
needed to satisfy the objectives of the study. A
made. This document will be helpful later if you
model is neither true nor false, but rather useful
need to make modifications to the model or look
or not useful. Once validated, a model is useful
at why the actual system ends up working differ-
when it provides the needed information to meet
ently than what was modeled.
the objectives of the simulation.
In addition to including those factors to be used
in the model, the data document should also Progressive Refinement
include those factors deliberately excluded from
the model because they are deemed to be either One nice feature of simulation is that models do
insignificant or irrelevant. If, for example, break not have to include all of the final detail before
36 Chapter 3:
Steps for Doing Simulation

they will run. This allows a progressive refine- tested and debugged before adding new sections
ment strategy to be used in which detail is added and makes a large task more manageable.
to the model in stages rather than all at once. Not
For unusually large models, it may be useful to
only do models get built and running quicker this
identify definable boundaries within a model to
way, but it also makes models easier to debug. In
permit model partitioning. Model partitioning is
the initial stages of a model, for example, attrac-
the process of subdividing a model into two or
tive graphics are not very useful and, since they
more modules that represent physically separate
are likely to be changed anyway, should not be
sections within the system. The purpose of model
added until later when preparing for the final
partitioning is to allow model sections to be built
model presentation.
and debugged, possibly even by separate individ-
The complexity of model building should never uals, independently of each other. Once sections
be underestimated and it is always better to begin are finished, they can be merged together to cre-
simple and add complexity rather than create an ate the overall model. This “divide-and-conquer”
entire complex model at once. It is also easier to method of model building can greatly reduce the
add detail to a model than it is to remove it from a time and difficulty in building and debugging
model. Building a model in stages enables bugs large models.
to be more readily identified and corrected.
Emphasizing the importance of applying progres- Model Verification
sive refinement to model building, Law and Kel-
ton (1991) have advised: Once a model is defined using a selected software
tool, the model must generally be debugged to
Although there are few firm rules on how one ensure that it works correctly. The process of
should go about the modeling process, one point demonstrating that a model works as intended is
on which most authors agree is that it is always a referred to in simulation literature as model veri-
good idea to start with a simple model which can fication. It is much easier to debug a model built
later be made more sophisticated if necessary. A in stages and with minimal detail than to debug a
model should contain only enough detail to cap- large and complex model. Eliminating bugs in a
ture the essence of the system for the purposes for program model can take a considerable amount
which the model is intended: it is not necessary to of time, especially if a general purpose program-
have a one-to-one correspondence between ele- ming language (e.g., C++) in which frequent cod-
ments of the model and elements of the system. A ing errors occur is used. Most simulation
model with excessive detail may be too expensive languages provide a trace capability in the form
to program and to execute. of audit trails, screen messages, graphic anima-
tion, or a combination of all three. A trace
Incremental Expansion enables the user to look inside of the simulation
to see if the simulation is performing the way it
In addition to adding complexity to a model in
should. Good simulation products provide inter-
stages, models that have a broad scope are some-
active debugging capability which further facili-
times easier to build in phases where additional
tates the debugging process. A thorough “walk-
sections are added incrementally to the model.
through” of the model input is always advisable.
This method of "eating the elephant one bite at a
time" allows a portion of the model to be built,
 ProModel 37
User Guide

Model Validation Step 4: Conducting Experiments

During the process of model building, the mod- The fourth step in a simulation study is to con-
eler must be constantly concerned with how duct simulation experiments with the model.
closely the model reflects the system definition. Simulation is basically an application of the sci-
The process of determining the degree to which entific method. In simulation, one begins with a
the model corresponds to the real system, or at theory of why certain design rules or manage-
least accurately represents the model specifica- ment strategies are better than others. Based on
tion document, is referred to as model validation. these theories the designer develops a hypothesis
Proving absolute validity is a non attainable goal. which he tests through simulation. Based on the
As Neelamkavil (1987) explains, “True valida- results of the simulation the designer draws con-
tion is a philosophical impossibility and all we clusions about the validity of his hypothesis. In a
can do is either invalidate or fail to invalidate.” simulation experiment there are input variables
For this reason, what we actually seek to estab- defining the model which are independent and
lish is a high degree of face validity. Face validity may be manipulated or varied. The effects of this
means that, from all outward indications, the manipulation on other dependent or response
model appears to be an accurate representation of variables are measured and correlated.
the system. From this standpoint, validating a
model is the process of substantiating that the In some simulation experiments we are interested
model, within its domain of applicability, is suffi- in the steady-state behavior of the model. Steady-
ciently accurate for the intended application state behavior does not mean that the simulation
(Schlesinger, 1979). produces a steady outcome, but rather the distri-
bution or statistical variation in outcome does not
There is no simple test to establish the validity of change over time. For example, a distribution
a model. Validation is an inductive process warehouse may ship between 200 and 220 parts
through which the modeler draws conclusions per hour under normal operating conditions. For
about the accuracy of the model based on the evi- many simulations we may only be interested in a
dence available. Gathering evidence to determine particular time period, such as a specific day of
model validity is largely accomplished by exam- the week. For these studies, the simulation may
ining the model structure (i.e., the algorithms and never reach a steady state.
relationships) to see how closely it corresponds to
the actual system definition. For models having As with any experiment involving a system with
complex control logic, graphic animation can be random characteristics, the results of the simula-
used effectively as a validation tool. Finally, the tion will also be random in nature. The results of
output results should be analyzed to see if the a single simulation run represent only one of sev-
results appear reasonable. If circumstances per- eral possible outcomes. This requires that multi-
mit, the model may even be compared to that ple replications be run to test the reproducibility
actual system to see how they correspond. If of the results. Otherwise, a decision might be
these procedures are performed without encoun- made based on a fluke outcome, or at least an
tering a discrepancy between the real system and outcome not representative of what would nor-
the model, the model is said to have face validity. mally be expected. Since simulation utilizes a
pseudo-random number generator for generating
random numbers, running the simulation multiple
times simply reproduces the same sample. In
38 Chapter 3:
Steps for Doing Simulation

order to get an independent sample, the starting Answers to these questions will be determined
seed value for each random stream must be dif- largely by the following three factors:
ferent for each replication, ensuring that the ran-
1. The nature of the simulation (terminating or
dom numbers generated from replication to
nonterminating).
replication are independent.
2. The objective of the simulation (capacity
Depending on the degree of precision required in analysis, alternative comparisons, etc.).
the output, it may be desirable to determine a 3. The precision required (rough estimate ver-
confidence interval for the output. A confidence sus confidence interval estimates).
interval is a range within which we can have a
certain level of confidence that the true mean Terminating Versus
falls. For a given confidence level or probability,
Non-terminating Simulations
say .90 or 90%, a confidence interval for the
average utilization of a resource might be deter- As part of setting up the simulation experiment,
mined to be between 75.5 and 80.8%. We would one must decide what type of simulation to run.
then be able to say that there is a .90 probability Simulations are usually distinguished as being
that the true mean utilization of the modeled one of two types: terminating or non-terminating.
resource (not of the actual resource) lies between The difference between the two has to do with
75.5 and 80.8%. whether we are interested in the behavior of the
system over a particular period of time or in the
Fortunately, ProModel provides convenient facil- steady-state behavior of the system. It has noth-
ities for conducting experiments, running multi-
ing to do, necessarily, with whether the system
ple replications and automatically calculating itself terminates or is ongoing. The decision to
confidence intervals. The modeler must still perform a terminating or non-terminating simula-
decide, however, what types of experimentation
tion has less to do with the nature of the system
are appropriate. When conducting simulation
than it does with the behavior of interest.
experiments, the following questions should be
asked: A terminating simulation is one in which the sim-
ulation starts at a defined state or time and ends
• Am I interested in the steady state behavior
when it reaches some other defined state or time.
of the system or a specific period of opera-
An initial state might be the number of parts in
tion?
the system at the beginning of a work day. A ter-
• How can I eliminate start-up bias or getting minating state or event might be when a particu-
the right initial condition for the model? lar number of jobs have been completed.
• What is the best method for obtaining sam- Consider, for example, an aerospace manufac-
ple observations that may be used to estimate turer that receives an order to manufacture 200
the true expected behavior of the model? airplanes of a particular model. The company
• What is an appropriate run length for the might be interested in knowing how long it will
simulation? take to produce the aircraft along with existing
• How many replications should be made? workloads. The simulation run starts with the
• How many different random streams should system empty and is terminated when the 200th
be used? plane is completed since that covers the period of
• How should initial seed values be controlled interest. A point in time which would bring a ter-
from replication to replication? minating simulation to an end might be the clos-
 ProModel 39
User Guide

ing of shop at the end of a business day, or the Running Terminating Simulations
completion of a weekly or monthly production
period. It may be known, for example, that a pro- Experiments involving terminating simulations
are usually conducted by making several simula-
duction schedule for a particular item changes
weekly. At the end of each 40 hour cycle, the sys- tion runs, or replications, of the period of interest
using a different random seed for each run. This
tem is “emptied” and a new production cycle
procedure enables statistically independent and
begins. In this situation, a terminating simulation
unbiased observations to be made on the system
would be run in which the simulation run length
response over the period simulated. Statistics are
would be 40 hours.
often gathered on performance measures for suc-
Terminating simulations are not intended to mea- cessive intervals of time during the period.
sure the steady-state behavior of a system. In a
terminating simulation, average measures are of For terminating simulations, we are usually inter-
little meaning. Since a terminating simulation ested in final production counts and changing
always contains transient periods that are part of patterns of behavior over time rather than the
the analysis, utilization figures have the most overall average behavior. It would be absurd, for
meaning if reported for successive time intervals example, to conclude that because two techni-
during the simulation. cians are busy only an average of 40% during the
day that only one technician is needed. This aver-
A non-terminating or steady-state simulation is age measure reveals nothing about the utilization
one in which the steady-state behavior of the sys- of the technicians during peak periods of the day.
tem is being analyzed. A non-terminating simula- A more detailed report of waiting times during
tion does not mean that the simulation never the entire work day may reveal that three techni-
ends, nor does it mean that the system being sim- cians are needed to handle peak periods, whereas
ulated has no eventual termination. It only means only one technician is necessary during off-peak
that the simulation could theoretically go on hours. In this regard, Hoover and Perry (1990)
indefinitely with no statistical change in behav- note:
ior. For non-terminating simulations, the modeler
must determine a suitable length of time to run It is often suggested in the simulation literature
the model. An example of a non-terminating sim- that an overall performance be accumulated over
the course of each replication of the simulation,
ulation is a model of a manufacturing operation
ignoring the behavior of the systems at intermedi-
in which oil filters are produced on a continual
basis at the same pace. The operation runs two ate points in the simulation. We believe this is too
shifts with an hour break during each shift in simple an approach to collecting statistics when
which everything momentarily stops. Break and simulating a terminating system. It reminds us of
third shift times are excluded from the model the statistician who had his head in the refrigera-
since work always continues exactly as it left off tor and feet in the oven, commenting that on the
before the break or end of shift. The length of the average he was quite comfortable.
simulation is determined by how long it takes to For terminating simulations, the three important
get a representative steady-state reading of the questions to answer in running the experiment
model behavior. are:
1. What should be the initial state of the model?
2. What is the terminating event or time?
3. How many replications will you make?
40 Chapter 3:
Steps for Doing Simulation

Many systems operate on a daily cycle, or, if a simulation progresses through N periods of a
pattern occurs over a weeks time, the cycle is simulation.
weekly. Some cycles may vary monthly or even
annually. Cycles need not be repeating to be con- Period Y
sidered a cycle. Airlines, for example, may be 1
interested in the start-up period of production
during the introduction of a new airport which is 2 Transient State
a one-time occurrence.
3
The number of replications should be determined
4
by the precision required for the output. If only a
rough estimate of performance is being sought, 5
three to five replications are sufficient. For Steady State
6
greater precision, more replications should be
made until a confidence interval with which you 7
feel comfortable is achieved.
8

Running Non-terminating Simulations Behavior of Response Variable Y for Successive

Periods During Simulation
The issues associated with generating meaningful
output statistics for terminating simulations are
somewhat different that those associated with The time that it takes to reach steady-state is a
generating statistics for non-terminating sys- function of the activity times and the amount of
tems. In steady-state simulations, we must deal activity taking place. For some models, steady-
with the following issues: state might be reached in a matter of a few hours
of simulation time. For other models it may take
1. Determining the initial warm-up period. several hundred hours to reach steady-state. In
2. Selecting among several alternative ways for modeling steady-state behavior we have the prob-
obtaining sample observations.
lem of determining when a model reaches steady-
3. Determining run length.
state. This start-up period is usually referred to as
Determining the Warm-up Period In a steady- the warm-up period. We want to wait until after
state simulation, we are interested in the steady- the warm-up period before we start gathering any
state behavior of the model. Since a model starts statistics. This way we eliminate any bias due to
out empty, it usually takes some time before it observations taken during the transient state of
reaches steady-state. In a steady-state condition, the model.
the response variables in the system (e.g., pro-
While several methods have been presented for
cessing rates, utilization, etc.) exhibit statistical
determining warm-up time (Law and Kelton,
regularity (i.e., the distribution of these variables
1991), the easiest and most straightforward
are approximately the same from one time period
approach, although not necessarily the most reli-
to the next). The following figure illustrates the
able, is to run a preliminary simulation of the sys-
typical behavior of a response variable, Y, as the
tem, preferably with several (3 to 5) replications,
and observe at what time the system reaches sta-
tistical stability. The length of each replication
should be relatively long and allow even rarely
 ProModel 41
User Guide

occurring events, such as infrequent downtimes, Obtaining Sample Observations In a terminating

to occur at least two or three times. To determine simulation, sample observations are made by
a satisfactory warm-up period using this method, simply running multiple replications. For steady-
one or more key response variables should be state simulations, we have several options for
monitored by period over time, like the average obtaining sample observations. Two widely used
number of entities in a queue or the average utili- approaches are running multiple replications and
zation of a resource. This approach assumes that interval batching. The method supported in Pro-
the mean value of the monitored response vari- Model is running multiple replications.
able is the primary indicator of convergence
Running multiple replications for non-terminat-
rather than the variance, which often appears to
ing simulations is very similar to running termi-
be the case. If possible, it is preferable to reset the
nating simulations. The only difference is that (1)
response variable after each period rather than
the initial warm-up period must be determined,
track the cumulative value of the variable, since
and (2) an appropriate run length must be deter-
cumulative plots tend to average out instability in
mined. Once the replications are made, confi-
data. Once these variables begin to exhibit
dence intervals can be computed as described
steady-state, we can add a 20% to 30% safety
earlier in this chapter. One advantage of running
factor and be reasonably safe in using that period
independent replications is that samples are inde-
as the warm-up period. This approach is simple,
pendent. On the negative side, running through
conservative and usually satisfactory. Remember,
the warm-up phase for each replication slightly
the danger is in underestimating the warm-up
extends the length of time to perform the replica-
period, not overestimating it. Relatively little
tions. Furthermore, there is a possibility that the
time and expense is needed to run the warm-up
length of the warm-up period is underestimated,
period longer than actually required. The follow-
causing biased results.
ing figure illustrates the average number of enti-
ties processed each hour for several replications. Interval batching (also referred to as the batch
Since statistical stability is reached at about 10 means technique) is a method in which a single,
hours, 12 to 15 hours is probably a safe warm-up long run is made with statistics being reset at
period to use for the simulation. specified time intervals. This allows statistics to
End of Warm-up Period
be gathered for each time interval with a mean
calculated for each interval batch. Since each
100
90
interval is correlated to both the previous and the
80 next intervals (called serial correlation or auto-
70 correlation), the batches are not completely inde-
Output
(per hr)
60
pendent. The way to gain greater independence is
50
40
to use large batch sizes and to use the mean val-
30 ues for each batch. When using interval batching,
20 confidence interval calculations can be per-
10
formed. The number of batch intervals to create
2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 should be at least 5 to 10 and possibly more
Simulation Time (hrs)
depending on the desired confidence interval.
Plot of Hourly Entity Output to Identify Start of Determining Run Length Determining run length
Steady-State
for terminating simulations is quite simple since
there is a natural event or time point that defines
42 Chapter 3:
Steps for Doing Simulation

it for us. Determining the run length for a steady- tional replications actually lead the opposite con-
state simulation is more difficult since the simu- clusion?
lation can be run indefinitely. The benefit of this,
Evaluating alternative configurations or operat-
however, is that we can produce good representa-
ing policies can sometimes be performed by com-
tive samples. Obviously, running extremely long
paring the average result of several replications.
simulations is impractical, so the issue is to deter-
Where outcomes are close or where the decision
mine an appropriate run length that ensures a suf-
requires greater precision, a method referred to as
ficiently representative sample of the steady-state
hypothesis testing should be used. In hypothesis
response of the system is taken.
testing, first a hypothesis is formulated (e.g., that
The recommended length of the simulation run methods A and B both result in the same through-
for a steady-state simulation is dependent upon put) and then a test is made to see whether the
(1) the interval between the least frequently results of the simulation lead us to reject the
occurring event and (2) the type of sampling hypothesis. The outcome of the simulation runs
method (replication or interval batching) used. If may cause us to reject the hypothesis that meth-
running independent replications, it is usually a ods A and B both result in equal throughput capa-
good idea to run the simulation enough times to bilities and conclude that the throughput does
let every type of event (including rare ones) hap- indeed depend on which method is used.
pen at least a few times if not several hundred.
Sometimes there may be insufficient evidence to
Remember, the longer the model is run, the more
reject the stated hypothesis and thus the analysis
confident you can become that the results repre-
proves to be inconclusive. This failure to obtain
sent a steady-state behavior. If collecting batch
sufficient evidence to reject the hypothesis may
mean observations, it is recommended that run
be due to the fact that there really is no difference
times be as large as possible to include at least
in performance, or it may be a result of the vari-
1000 occurrences of each type of event (Thesen
ance in the observed outcomes being too high
and Travis, 1992).
given the number of replications to be conclu-
sive. At this point, either additional (perhaps time
Comparing Alternative Systems consuming) replications may be run or one of
Simulations are often performed to compare two several variance reduction techniques might be
or more alternative designs. This comparison employed (see Law and Kelton, 1991).
may be based on one or more decision variables
such as buffer capacity, work schedule, resource Factorial Design
availability, etc. Comparing alternative designs
In simulation experiments we are often interested
requires careful analysis to ensure that differ-
in finding out how different input variable set-
ences being observed are attributable to actual
tings impact the response of the system. Rather
differences in performance and not to statistical
than run hundreds of experiments for every possi-
variation. This is where running multiple replica-
ble variable setting, experimental design tech-
tions may again be helpful. Suppose, for exam-
niques can be used as a “short-cut” to finding
ple, that method A for deploying resources yields
those input variables of greatest significance.
a throughput of 100 entities for a given time
Using experimental-design terminology, input
period while method B results in 110 entities for
variables are referred to as factors, and the output
the same time period. Is it valid to conclude that
measures are referred to as responses. Once the
method B is better than method A, or might addi-
 ProModel 43
User Guide

response of interest has been identified and the number of combinations to test. In this type of
factors that are suspected of having an influence situation, a fractional-factorial design is used to
on this response defined, we can use a factorial strategically select a subset of combinations to
design method which prescribes how many runs test in order to “screen out” factors with little or
to make and what level or value to be used for no impact on system performance. With the
each factor. As in all simulation experiments, it is remaining reduced number of factors, more
still desirable to run multiple replications for each detailed experimentation such as a full-factorial
factor level and use confidence intervals to assess experiment can be conducted in a more manage-
the statistical significance of the results. able fashion.
One's natural inclination when experimenting After fractional-factorial experiments and even
with multiple factors is to test the impact that two-level full-factorial experiments have been
each individual factor has on system response. performed to identify the most significant factor
This is a simple and straightforward approach, level combinations, it is often desirable to con-
but it gives the experimenter no knowledge of duct more detailed experiments, perhaps over the
how factors interact with each other. It should be entire range of values, for those factors that have
obvious that experimenting with two or more fac- been identified as being the most significant. This
tors together can affect system response differ- provides more precise information for making
ently than experimenting with only one factor at a decisions regarding the best factor values or vari-
time and keeping all other factors the same. able settings for the system. For a more concise
explanation of the use of factorial design in simu-
One type of experiment that looks at the com-
lation experimentation see Law and Kelton
bined effect of multiple factors on system
(1991).
response is referred to as a two-level, full-facto-
rial design. In this type of experiment, we simply
define a high and low level setting for each factor Use of Random Streams
and, since it is a full-factorial experiment, we try One of the most valuable characteristics of simu-
every combination of factor settings. This means lation is the ability to reproduce and randomize
that if there are five factors and we are testing replications of a particular model. Simulation
two different levels for each factor, we would test allows probabilistic phenomena within a system
each of the 25 = 32 possible combinations of high to be controlled or randomized as desired for con-
and low factor levels. For factors that have no ducting controlled experiments. This control is
range of values from which a high and low can be made available through the use of random
chosen, the high and low levels are arbitrarily streams.
selected. For example, if one of the factors being
A stream is a sequence of independently cycling,
investigated is an operating policy for doing work
unique random numbers uniformly distributed
(e.g., first come, first served; or last come, last
between 0 and 1 (see the figure on next page).
served), we arbitrarily select one of the alterna-
Random number streams are used to generate
tive policies as the high level setting and a differ-
additional random numbers from other probabil-
ent one as the low level setting.
ity distributions (Normal, Beta, Gamma). After
For experiments in which a large number of fac- sequencing through all of the random numbers in
tors are being considered, a two-level full-facto- the cycle, the cycle starts over again with the
rial design would result in an extremely large same sequence. The length of the cycle before it
44 Chapter 3:
Steps for Doing Simulation

repeats is called the cycle period and is usually example, arrival distributions should generally
very long. have a random number stream used nowhere else
in the entire model. That way, activities added to
.52 a model that sample from a random number
stream will not inadvertently alter the arrival pat-
.80 .31 tern because they do not affect the sample values
generated from the arrival distribution.
To show an example of how multiple streams can
.07 .95 be useful, consider two copy machines, Copy1
and Copy2, which go down approximately every
4 hours for servicing. To model this, the fre-
.60
quency or time between failures is defined by a
.25 normal distribution with a mean value of 240
minutes and a standard deviation of 15 minutes,
.66 N(240,15). The time to repair is 10 minutes. If no
stream is specified in the normal distribution, the
Example of a Random Stream Cycle with a Very
same stream will be used to generate sample val-
Short Period
ues for both machines. So, if the next two num-
bers in the stream number are .21837 and .86469,
A random stream is generated using a random Copy1 will get a sample value from the normal
number generator or equation. The random num- distribution that is different from Copy2. There-
ber generator begins with an initial seed value fore, the two machines will go down at different
after which, each successive value uses the previ- times.
ous value as input to the generator. Each stream
used in a simulation has its own independent seed Suppose, however, that the resource servicing the
and tracks its own values for subsequent input to machines must service them both at the same
the generator. Where the sequence begins in the time, so we would like to have the machines go
cycle depends on the initial seed value used by down at the same time. Using the same stream to
determine both downtimes will not bring them
the generator.
down at the same time, because a different ran-
Any time a particular number seeds a stream, the dom number will be returned from the stream
same sequence of values will be repeated every with each call to generate a random normal vari-
time the same seed is used to initialize the stream. ate. Using two different streams, each dedicated
This means that various elements within a model to a machine's downtime and each having the
can be held constant with respect to their perfor- same initial seed, will ensure that both machines
mance while other elements vary freely. Simply go down at the same time every time. The two
specify one random number stream for one set of streams have the same starting seed value so they
activities and another random number stream for will produce exactly the same sequence of ran-
all other activities. dom numbers.
Because the same seed produces the same
sequence of values every time it is used, com-
pletely independent functions within a model
must have their own streams from the start. For
 ProModel 45
User Guide

Step 5: Analyzing the Output only reports the symptomatic behavior of prob-
lems. Bottleneck activities, for example, are usu-
Output analysis deals with drawing inferences ally identified by looking for locations or queues
about the actual system based on the simulation that are nearly always full which feed into one or
output. When conducting simulation experi- more locations that are sometimes empty. Detect-
ments, extreme caution should be used when ing the source of the bottleneck is sometimes a
interpreting the simulation results. Since the bit trickier than identifying the bottleneck itself.
results of a simulation experiment are random Bottlenecks may be caused by excessive opera-
(given the probabilistic nature of the inputs), an tion times, prolonged delays due to the unavail-
accurate measurement of the statistical signifi- ability of resources, or an inordinate amount of
cance of the output is necessary. downtime. The ability to draw correct inferences
People doing simulation in academia are often from the results is essential to making system
accused of working with contrived and often improvements.
oversimplified assumptions, yet are extremely
careful about ensuring the statistical significance Step 6: Reporting the Results
of the model results. Simulation practitioners in
industry, on the other hand, are usually careful to The last step in the simulation procedure is to
obtain valid model data, only to ignore the statis- make recommendations for improvement in the
tical issues associated with simulation output. actual system based on the results of the simu-
Maintaining a proper balance between establish- lated model. These recommendations should be
ing model validation and establishing the statisti- supported and clearly presented so that an
cal significance of simulation output is an informed decision can be made. Documentation
important part of achieving useful results. of the data used, the model(s) developed and the
experiments performed should all be included as
The most valuable benefit from simulation is to part of a final simulation report.
gain insight, not necessarily to find absolute
answers. With this in mind, one should be careful A simulation has failed if it produces evidence to
about getting too pedantic about the precision of support a particular change which is not imple-
simulation output. With more than 60 combined mented; especially if it is economically justified.
years of experience in doing simulation model- The process of selling simulation results is
ing, Conway, Maxwell and Worona (1986) cau- largely a process of establishing the credibility of
tion that attaching a statistical significance to the model. It is not enough for the model to be
simulation output can create a delusion that the valid, the client or management must also be con-
output results are either more or less significant vinced of its validity if it is to be used as an aid in
than they really are. They emphasize the practi- decision making. Finally, the results must be pre-
cal, intuitive reading of simulation results. Their sented in terms that are easy to understand and
guideline is "If you can't see it with the naked evaluate. Reducing the results to economic fac-
eye, forget it." tors always produces a compelling case for mak-
ing changes to a system.
The goal of conducting experiments is not just to
find out how well a particular system operates, In presenting results it is important to be sensitive
but hopefully to gain enough insight to be able to to the way in which recommendations are made.
improve the system. Unfortunately, simulation It helps to find out whether recommendations are
output rarely identifies causes of problems, but being sought or whether a simple summary of the
46 Chapter 3:
Steps for Doing Simulation

results is wanted. It is generally wise to present • Overrunning budget and time constraints.
alternative solutions and their implications for • Failure to document and get a consensus on
system performance without suggesting one input data.
alternative over another, particularly when per- • Including more detail than is needed.
sonnel changes or cuts are involved. In fact, • Including variables that have little or no
where there may be careers on the line, it is best impact on system behavior.
to caution the decision maker that your simula- • Failure to verify and validate the model.
tion study looks only at the logistical aspects of
• Basing decisions on a single run observation.
the system and that it does not take into account
• Basing decisions on average statistics when
the potential reactions or potential difficulties
the output is actually cyclical.
employees may have in accepting a particular
• Being too technical and detailed in present-
solution.
ing the results to management.
Animation and output charts have become an
extremely useful aid in communicating the
results of a simulation study. This usually Summary
requires that some touch-up work be done to cre- A simulation project has distinct phases that must
ate the right effect in visualizing the model being be understood and followed in order to be suc-
simulated. In preparing the results, it is often nec- cessful. Simulation requires careful planning
essary to add a few touch-ups to the model (like a with realistic goals and expectations. Steps to
full dress-rehearsal) so the presentation effec- performing a simulation study include planning
tively and convincingly presents the results of the the study, defining the system, building the
simulation study. model, conducting experiments, analyzing the
After the presentation is finished and there is no output, and presenting the results. Systematically
further analysis to be conducted (the final presen- following these steps will help avoid the pitfalls
tation always seems to elicit further suggestions that frequently occur when conducting a simula-
for trying this or that with the model), the model tion study.
recommendations, if approved, are ready to be
implemented. If the simulation has been ade-
quately documented, it should provide a good
functional specification for the implementation
team.

Pitfalls in Simulation
If the steps that have been outlined are followed,
the chances of performing a successful simula-
tion project are very good. Typical reasons why
simulation projects fail include the following:
• Failure to state clear objectives at the outset.
• Failure to involve individuals affected by
outcome.
 ProModel 47
User Guide

Building a Model Locations

We need some type of receiving location to hold
ProModel gives you the flexibility to create a incoming entities. We also need processing loca-
model in several ways—the easiest is to use the
tions where entities have value added to them.
graphical point-and-click approach. To build a
For the given production rate, Cogswell's engi-
model, you should first define any locations in
neers have determined that the workcell will
the system. With locations defined, you are ready
require two NC_300 series numerically con-
to create entities (parts, customers, calls, etc.) and
trolled mills, a degreasing machine, and an
schedule their arrivals to the locations you cre-
inspection/assembly station.
ated. Next, specify the process logic for entities at
each location (this will establish the entity flow
Entities (Parts)
throughout the model). Finally, define any
optional model elements such as attributes, vari- The entity types in this system include Pallets,
ables, or arrays that you will use in processing each carrying six cast Blanks. Blanks become
entities. Cogs after processing, and Bearings are loaded at
the Inspect station. If a Cog fails the inspection it
will be called a Reject.
Modeling Scenario
Before we actually begin building a model, let's Arrivals
look at a fictitious scenario for our model build- Cogswell's engineers have determined that Pal-
ing session. lets should arrive at the rate of 1 Pallet every 45
minutes.
Cogswell Cogs has just secured a contract to pro-
duce a new cog for production of the X-95C
Processing
Family Space Cruiser. The current capacity of the
Cogswell facility is not adequate to handle any The operation at each mill requires an operator to
additional work load while continuing to fill load the Blank, which takes a normally distrib-
existing orders. Therefore, Mr. Cogswell has uted amount of time with a mean of 3 minutes
ordered the I.E. department to simulate the design and standard deviation of .2 minutes (i.e.,
of a new workcell dedicated to the production of N(3,.2)). After a blank has been loaded, the
the new cog. machining time is a constant 5.7 minutes.
The process consists of loading a cast blank onto Cogs are then removed from the mill and placed
an NC mill for milling of the outside splines. in the degreasing machine. The degreasing
Once the splines have been cut, the cog must be machine has capacity for 2 Cogs, and has a cycle
degreased, inspected and loaded with an inner time of 5 minutes.
bearing. All operations, including inspection, are
Once the Cogs have been degreased, they are
to be performed by a single operator.
inspected for proper spline depth, and a bearing is
installed in the center hole. This process requires
Model Elements the cell operator, and takes U(3.2,.3) minutes for
In building this model we must define all of the the inspection and U(1.5,.2) minutes for the Bear-
basic modeling elements and a few of the ing to be installed. If the Cog fails inspection, no
optional elements. Bearing is installed.
48 Chapter 3:
Building a Model

Resources tions in the layout window. Upon completion of

this phase you have a fully working model, ready
A single operator, CellOp, performs all manual
to animate and collect output.
operations.
Phase 2: Adding Resources & Variability
Path Networks
The second phase normally consists of expanding
In order to make CellOp a mobile resource, we
the model by adding resources and the corre-
must define a path network. We'll call it CellNet.
sponding path network needed to move entities,
using resources, from location to location.
Attributes
An attribute is simply a “numeric tag” attached to Phase 3: Additional Operations
either an entity (entity attribute) or a location
(location attribute). Since each Cog is inspected The final phase usually consists of adding addi-
for proper spline depth, we attach an attribute tional reality to the model—that is, adding those
called Test to each Cog, specifying the Pass/Fail nuances that make the model an accurate repre-
status of the Cog. sentation of a real system. These include:
• Adding Quantity and Time_in_system
User Distributions attributes.
We will sample from a user defined distribution • Changing operational times from simple
and set the Test attribute to either 1 (for pass) or 0 time constants to distributions.
(for fail). Ninety six percent of the Cogs pass • Adding features that ensure accurate entity
inspection and have their Test attribute set to one. processing.
Four percent fail the inspection and have their • Adding variables for on-screen display.
Test attribute set to zero. • Defining appropriate downtimes.

Phased Modeling Approach Phase 1: Basic Model Elements

Instead of trying to build a model all at once, you The first step in building the model is to define
may want to implement a phased modeling the model's basic elements.
approach where you build the model in stages.
This will help you understand the basic modeling General Information
elements before moving on to more complex
ones like attributes and IF-THEN logic. The fol- The General Information dialog box, accessed
lowing elements are those components normally through the Build menu, allows you to name your
entered during each phase of the model building model and specify default information such as
process. time and distance units. You also specify the

Phase 1: Basic Model Elements

In the first phase you input all of the basic model
elements: General Information, Locations, Enti-
ties, Arrivals, and Processing. You also import a
background graphic to help in placing the loca-
 ProModel 49
User Guide

name of the graphics library to use. By default it Defining Locations

will be PROMOD5.GLB.
Locations are defined easily by selecting the
desired icon and placing it in the layout window.
Each time a location is placed in the layout win-
dow, a corresponding record is entered in the
Location edit table. This table lists each location
along with location parameters such as the capac-
ity, number of units, and downtime information.
For more information on how to define a loca-
tion, see “Locations” on page 90.

Layout Window (maximized)

Importing a Background Graphic

Simple background graphics are imported easily
through the Background Graphics Editor. Pro-
Model also allows you to import complex graph-
ics files such as AutoCAD drawings to use as the
background for your simulations. For more infor-
mation on how to import a background graphic,
see “Graphic Editor” on page 304.

Location Edit Table

Defining Entities
Once all locations have been defined, we define
Often, importing a background graphic makes the entities in a similar way by selecting an icon for
process of placing locations easier, or altogether each entity type. As we do this, a record is cre-
eliminates the need to create graphic icons for ated in the Entity edit table for each entity type.
locations.
50 Chapter 3:
Building a Model

For more information on how to define entities, information on defining process logic, see “Pro-
see “Entities” on page 112. cessing” on page 143, and “Operation Logic” on
page 291.
Once the basic entity flow has been defined using
the point and click method, operation statements
are added to the processing logic. The processing
logic can be as simple as a constant operation
In this model the Speed (fpm) column is irrele- time or as complex as a nested IF...THEN...ELSE
vant since all entities move according to the defi- statement.
nition of the mobile resource CellOp. Also, the
Stats column shows that we desire detailed statis- Process editing actually involves two edit tables
tics for all entity types. “Time series” statistics that normally appear side by side. The Process
include throughput history of the entity. “Basic” edit table specifies what happens to an entity
statistics include only the total exits of each entity when it arrives at a location, and the Routing edit
type from the system and the final quantity of table specifies where an entity is to be sent once
each entity type in the system. processing is complete.

Process Edit Table

Defining Arrivals
Of the four entity types, only one needs to be
scheduled to arrive in the system. Every 45 min-
utes one Pallet arrives at the Receiving location.
The word “INFINITE” in the Occurrences col-
umn means that one pallet continues to arrive
every 30 minutes as long as the simulation runs.
For more information on defining arrivals, see
“Arrivals” on page 156.
Routing Edit Table

Defining Process Logic

The last step in defining Phase 1 of our model is
Process and Routing Logic
to define the processing of entities at each loca-
tion. ProModel simplifies this task by allowing The entire process and routing tables for the
you to select an entity type and then use the Phase 1 model are shown next. The table reads as
mouse to click on the locations in the order in follows:
which they will process the entity. Each time you 1.When an entity called Pallet arrives at location
click on a location, a new processing record is Receive there is no operation time or processing
added to the Process edit table, defining the pro- logic (it's just a storage location). The resulting
cess for that entity type at that location. For more output is six entities called Blank that are routed
 ProModel 51
User Guide

to the FIRST available destination of either 3.Two Cogs are accumulated at Degrease and
NC_301L or NC_302L. processed for 5 minutes. When the degrease
cycle is complete, Cogs are routed to location
2.When Blanks arrive at NC_301L or NC_302L,
Inspect.
the processing time is a normal distribution with
a mean of 3 and a standard deviation of .2 min- 4.The inspection time is a uniform distribution
utes. The name of the entity is now changed to with a mean of 3.2 and a half range of .3 minutes.
Cog, and the Cog is sent to the Degrease location Ninety six percent of the Cogs pass inspection
(FIRST is the default routing rule). and exit the system, while four percent of the
Cogs fail inspection and become Rejects.

 Process Table Routing Table

Entity Location Operation (min) Blk Output Destination Rule Move Logic
Pallet Receive 1 Blank NC_301L FIRST 6 MOVE FOR .5
Blank NC_302L FIRST MOVE FOR .5
Blank NC_301L WAIT N(3,.2) 1 Cog Degrease FIRST 1 MOVE FOR .5
Blank NC_302L WAIT N(3,.2) 1 Cog Degrease FIRST 1 MOVE FOR .5
Cog Degrease ACCUM 2 1 Cog Inspect FIRST 1 MOVE FOR .5
WAIT 5
Cog Inspect WAIT U(3.2,.3) 1 Cog EXIT 0.960 1
Reject EXIT 0.040
52 Chapter 3:
Building a Model

Phase 2: Adding Resources & Path Segment Edit Table

Variability
In this phase we wish to add the operator, CellOp,
to move entities from location to location, and to
perform the loading, unloading, and inspection
operations. ProModel requires that all dynamic
resources travel on a path network. Therefore, for
Phase 2, we need to define resources and path
networks.

Defining Path Networks

Path Networks consist of nodes and path seg- Defining Resources
ments which connect nodes to other nodes. Each Resources are defined in much the same way as
location where a resource may stop to pick up, entities. When in the Resource module we simply
drop off, or process entities must interface with a select an icon to represent the resource and then
path node. specify the characteristics of the resource in the
We define path networks through the Path Net- Resource edit table. For more information about
work edit table similar to the previous edit tables. defining resources, see “Resources” on page 126.
For each network we specify the nodes and path
segments connecting the nodes. Some of the
heading buttons, such as Paths and Interfaces,
bring up other edit tables such as the Path Seg-
ment Edit table shown below. For more informa-
tion on defining path networks, see “Path
Networks” on page 117.

Path Network Edit Table

 ProModel 53
User Guide

The Resource edit table shown below contains Process Edit Table and corresponding opera-
fields for specifying the name and number of tion logic
units of a resource. It also has fields for specify-
ing resource downtimes (DTs...), the level of sta-
tistics to collect (Stats...), which path network
used for travel (Specs...), and any work and park
search routines (Search...). Clicking the mouse on
any of these buttons brings up separate edit tables
for specifying this data.

Process Editing
Now that we have defined a resource, we must
specify how and when that resource is used in the
processing logic.
In the Phase 1 model we used only constant pro-
cessing times. Now, due to variability associated
with the operator, we must represent the loading
and inspection times as distributions.
Routing Edit Table
In the example below, CellOp loads the blank at
mill NC_302L and is then FREEd to perform
other operations. When the Blank has finished
processing, the entity is moved with the CellOp
to the degreasing machine.

Process and Routing Logic

The complete process and routing logic is shown
below, with CellOp used to perform the loading
operations at each mill and inspect the Cogs at
the Inspect location. CellOp is also used to trans-
port entities from location to location. All addi-
tions or changes to the Phase 1 model are shown
in bold type.
54 Chapter 3:
Building a Model

 Process Table Routing Table

Entity Location Operation (min) Blk Output Destination Rule Move Logic
Pallet Receive 1 Blank NC_301L FIRST 6 MOVE WITH CellOp
Blank NC_302L FIRST MOVE WITH CellOp
Blank NC_301L WAIT N(3,.2) 1 Cog Degrease FIRST 1 MOVE WITH CellOp
FREE CellOp
WAIT 5.7
Blank NC_302L WAIT N(3,.2) 1 Cog Degrease FIRST 1 MOVE WITH CellOp
FREE CellOp THEN FREE
WAIT 5.7
Cog Degrease ACCUM 2 1 Cog Inspect FIRST 1 MOVE WITH CellOp
WAIT 5
Cog Inspect WAIT U(3.2,.3) 1 Cog EXIT 0.960 1
FREE CellOp Reject EXIT 0.040
With the new processing now defined, we have
specified all of the necessary modeling elements.
We are now ready for the model execution phase.
Once again, we shall defer discussion of model
execution until we have finished the final phase
of the model.
 ProModel 55
User Guide

Phase 3: Additional Operations case, 96% of the entities pass inspection and 4%
fail.
In the final phase of our modeling session we
want to demonstrate an assembly operation by
using the operator to install a Bearing into the
center hole of the Cog if (and only if) the Cog
passes inspection.
Once we have defined the attribute and distribu-
tion table, we must return to the Locations, Enti-
ties and Arrivals modules to define a new
location called Bearing_Que, a new entity called
Bearing, and an arrival schedule for the Bearings.
In addition, we also need to specify a usage based
downtime for mills NC_301L and NC_302L New Location, Entity, and Arrival
from the Location module.
Before we can assemble the Cog at the Inspect
The final step in completing this phase of the location we must first define the new entity type
model is to edit the processing logic to include called Bearing in the Entities module. We must
the assembly. We will use the built-in JOIN con- also define a new location, Bearing_Que, to hold
struct to accomplish the assembly. the Bearings, and an arrival schedule for the
Bearings. To do this we simply open the appro-
Defining Attributes priate module as in Phase 1 and supply the infor-
mation. For simplicity we'll skip the details and
The Attribute module allows you to enter the
move on to downtime specification.
Attribute edit table to define an Entity Attribute
called Test that holds integer values. We set this
attribute to one if the Cog passes the inspection, Defining Location Downtimes
or zero if it fails the inspection. For more infor- In order to represent machine failure times for the
mation about defining attributes, see “Attributes” two mills, NC_301L and NC_302L, we click on
on page 217. the DT... button in the Location edit table shown
below. This brings up another edit table for speci-
fying a downtime based on machine usage. For
more information about defining location down-
times, see “Location Downtimes” on page 101.

Defining a Distribution
In order to determine if an entity passes or fails
the inspection, you sample from a user-defined
distribution called Dist1 (alternately, you could
use the RAND() function). To define the distribu-
tion, simply click the mouse on the Table... but-
ton and fill in the distribution parameters. In this
56 Chapter 3:
Running a Model

In the example above, we have defined failures to Process and Routing Logic
occur according to an exponential distribution
with a mean of 30 minutes. When a machine The process and routing table below shows all of
fails, resource CellOp is required to service the the changes and additions to the Phase 2 model in
machine. bold text.

 Process Table Routing Table

Entity Location Operation (min) Blk Output Destination Rule Move Logic
Pallet Receive 1 Blank NC_301L FIRST 6 MOVE WITH CellOp
Blank NC_302L FIRST MOVE WITH CellOp
Blank NC_301L WAIT N(3,.2) 1 Cog Degrease FIRST 1 MOVE WITH CellOp
FREE CellOp
WAIT 5.7
Blank NC_302L WAIT N(3,.2) 1 Cog Degrease FIRST 1 MOVE WITH CellOp
FREE CellOp THEN FREE
WAIT 5.7
Cog Degrease ACCUM 2 1 Cog Inspect FIRST 1 MOVE WITH CellOp
WAIT 5 THEN FREE
Cog Inspect WAIT U(3.2,.3) 1 Cog EXIT FIRST 1
Test = Dist1() 2 Reject EXIT FIRST 1
IF Test = 1 THEN
BEGIN
JOIN 1 Bearing
WAIT U(1.2,.2)
FREE CellOp
ROUTE 1
END
ELSE
BEGIN
FREE CellOp
ROUTE 2
END
Bearing Bearing_Que 1 Bearing Inspect JOIN 1 MOVE FOR .05
This concludes the final phase of our model Running a Model
building session. We now turn our focus to run-
ning the model. Running a model is a fun and easy process. Mod-
els are compiled automatically at runtime, keep-
ing you apart from any complex compilation
process. If your model contains any errors, a
detailed message explains the nature of the error
and points to the module and line number where
the error occurred. In most cases you are permit-
ted to make changes on the fly.
ProModel uses concurrent animation, which
means that the animation occurs while the simu-
 ProModel 57
User Guide

lation is running. Concurrent animation has many

advantages over post-simulation animation. By
CLOCK PRECISION
eliminating the two-step process of running the Time Unit .01 .001 .0001 .00001
simulation and then animating it, you save valu- Seconds 11,930 hrs 1,193 hrs 119 hrs 11 hrs
able time. Concurrent animation immediately (sec)
allows you to see if a model is working properly. Minutes 715,827 hrs 71,582 hrs 7,158 hrs 715 hrs
(min)
Hours (hr) 42,949,672 4, 294,967 429,496 42,949
Simulation Options hrs hrs hrs hrs
Days (day) 1,030,792,1 103,079,2 10,307,90 1,030,77
When you select Options from the Simulation 28 hrs 08 hrs 4 hrs 6 hrs
menu, ProModel displays the Simulation Options
dialog. This dialog contains several options for also control the animation through panning,
controlling the simulation, such as the run length, zooming, and pausing.
warm-up period, clock precision, and the name of
the output file. You can also set the number of
replications and the level of detail to be collected
for the statistics. For more information about
Simulation options, see “Simulation Menu” on
page 337.

Speed Control Bar

Clock Selection Button

The screen above shows the speed control bar,

along with the clock selection button for control-
ling the format of the clock readout.
The File menu includes an option for viewing a
The maximum run length depends on the clock text file of the model as the model is running.
precision and the time unit selected as shown in This is an excellent way of checking to make sure
the model is doing what it is supposed to do!
the following table.
Next we'll take a look at two of the other menu
items: Options and Information.
Animation Screen
The ProModel animation screen has a menu of its
own, with selections for controlling many simu-
lation parameters (such as run speed). You can
58 Chapter 3:
Running a Model

Options Menu Other options include: Animation Off, which

makes the simulation run considerably faster;
The Options menu contains several options that Zoom, which allows you to zoom in or out to any
allow you to track events in the system as they degree on the animation; Views, which allows
occur. The Debugger is a convenient and efficient you to quickly and easily access specific areas of
way to test or follow the processing of any logic the model Layout window (see “Layout Settings”
defined in your model. The debugger is used to on page 80); and User Pause, which allows you to
step through logic one statement at a time and specify the time of the next simulation pause.
examine variables and attributes while a model is
running. A Step Trace allows you to step through
the system events one at a time by clicking on the Information Menu
left mouse button. A Continuous Trace allows
The Information menu contains selections for
you to step through system events continuously
obtaining system information during the run. For
without clicking the mouse.
up-to-the-minute location information, such as
current location contents and total number of
entries, select Locations from the Information
menu.

The following Trace window shows system

events as they occur in the animation. The num-
ber in the left hand column represents the simula-
tion time when the event occurred, while the text
describes the event. Stepping through the events
is an excellent way to verify and debug a model.
 ProModel 59
User Guide

Viewing Model Statistics & Graphs” on page 363 for detailed examples of the

Reports output generated by the Output Viewer 3DR.

The purpose of any simulation model is to gain a
deeper understanding of the system under study.
ProModel's Output Viewer 3DR helps you to see
the interactions between various system elements
through tabular and graphical representation of
system parameters such as resource utilization,
throughput history, cycle time, and work-in-pro-
cess levels.
After each simulation run, you are prompted to
view the model output. You can select yes to
view the results immediately, or select no to con-
tinue with some other task. Selecting yes opens
the Output Viewer 3DR and automatically loads
the output of the most recent model run.

The Output Viewer 3DR can be run directly from

within ProModel, or as an independent applica-
tion separate from ProModel. You can load a sin-
gle results file or several results files from
different models for comparison of selected sta-
tistics.
Model output is written to several output files
according to the type of data being collected. The
main output file contains information of a sum-
mary nature such as overall location utilization
and number of entries at each location. Other
files keep track of information such as location
contents over time and the duration of each entity
at each location.
In order to see the power and flexibility of the
ProModel output generator, see “Reports and
60 Chapter 3:
Viewing Model Statistics & Reports
 ProModel 61
User Guide

Chapter 4: Modeling Environ-

ment

The Modeling Environment is everything con- Menu Bar

tained within the ProModel window.
All of the tools necessary to build and run a
When you open a model or select New from the
model and view the corresponding output are
File menu, your screen appears with a menu bar
accessed through the menu bar. The menu bar is
across the top of the screen and a layout window.
located just beneath the ProModel caption bar
You will also be given access to the ProModel
and contains the selections listed on the following
Shortcut Panel. For now, let's look briefly at the
page. These selections access other menus with
Shortcut Panel and then the menus accessible
selections related to the menu heading.
from the menu bar.
• File The File menu allows you to open new
From the ProModel shortcut panel seen above,
models, save current models, and merge two
you may quickly access some of ProModel’s
or more models into one. It also allows you
commonly used features:
to view a text version of the model and print
• Open a model Opens an existing model. either the model text file or the graphic lay-
• Install model package Loads an existing out of the model. For more information, see
model package. “File Menu” on page 62.
• Run demo model Allows you to run a dem- • Edit The Edit menu contains selections for
onstration model. editing the contents of edit tables and logic
• www.promodel.com Immediately connects windows. The selections available from this
you with the ProModel support page on the menu will change according to the module
PROMODEL Web site. from which the Edit menu is selected. They
• SimRunner Launches SimRunner. also vary according to the currently selected
• Stat::Fit Launches Stat::Fit. window. For more information, see “Edit
Menu” on page 70.
To simply begin working on a new model, close • View The View menu lets you control Pro-
the Shortcut Panel and select New from the File Model’s appearance. From this menu you
menu. The Shortcut Panel can be opened again can control layout settings, hide or view hid-
from the View menu. den paths, operate the zoom controls, and
more. For more information, see “View
Menu” on page 76.
• Build The Build menu contains all of the
modules for creating and editing a model.
62 Chapter 4:
File Menu

This includes the basic modules such as

Locations, Entities, Arrivals and Processing,
File Menu
and the optional modeling elements such as The File menu is the first selection on the menu
Variables, Attributes, Arrays, and Subrou- bar and consists of five major sections divided by
tines. For more information, see “Build horizontal lines. The file management section
Menu” on page 89. contains functions related to model files such as
• Simulation The Simulation menu controls saving and retrieving. The view/print section
the execution of a simulation and contains allows the user to view a text listing of the current
options for running a model, defining model model and print that listing or model layout. The
parameters, and defining and running scenar- model packaging section allows the user to create
ios. For more information, see “Simulation and install model packages consisting of models
Menu” on page 337. with associated files. Exit quits ProModel, and
• Output The Output selection starts the Pro- the model history section lists the five most
Model Output Viewer 3DR for viewing recently opened models for quick retrieval.
model output. It also allows you to view the Choosing any model in the model history will
trace generated during run-time. For more open and retrieve that model.
information, see “Reports and Graphs” on
page 363.
• Tools The Tools menu contains various util-
File management
ities including the Graphics Editor for creat-
ing and modifying graphic icons and a
search and replace feature for finding or View/Print
replacing expressions throughout a model.
For more information, see “Tools Menu” on
Model packaging
page 299.
• Window The Window menu allows you to
arrange the windows (or iconized windows)
that are currently displayed on the screen
such that all windows are visible at once. It
also allows you to bring any individual win-
dow to the forefront of the display. For more
information, see “Window Menu” on
page 84. File Management
• Help The Help menu accesses the ProModel
The File menu provides five functions related to
Online Help system. For more information,
model files such as saving and retrieving. Files
see “Help Menu” on page 85.
in the ProModel format use the MOD extension.
The following table defines each of the selections
 ProModel 63
User Guide

available from the file management section • version 5.0 to run with versions 5.0, 5.1, 5.2
shown previously. or 5.3.
• version 4.5 to run with version 4.5.
• version 4.0 to run with versions 4.0 or 4.2.

Please note

New Closes any currently opened model so a There is also an Autosave feature that saves the
new model can be built. This command is unnec- model file every n minutes as specified in the .INI
essary if no other model is open. If the currently file. This feature can be disabled. See the discus-
opened model has changed, ProModel will ask if sion later in this section.
you want to save the model before closing it.
Open Opens a user-specified model and clears
previous model data.
File Management Procedures
Merge Merges a selected ProModel model or
submodel into the current model. The same sub-
How to create a new model:
model can be merged multiple times into the
same model. See “Merge Model” on page 64.
1. Select New from the File menu.
Save Saves an open model under the current file
2. Define model elements using their corresponding
name. If no file name has been given, the user is modules.
prompted for a file name.
Save As Saves an open model under a new file
name specified by the user. The old file name still
exists. How to open an existing model:
Models saved in current versions of ProModel 1. Select Open from the File menu.
are not always compatible with previous versions
of ProModel. 2. Enter the necessary information in the Load Model
dialog box.

However, models may be saved as previous ver-

sions in order to allow those models created in
recent versions of ProModel to be shared with
others who may be running a previous version of
ProModel.
Models created in version 5.4 or higher must be
saved as:
64 Chapter 4:
File Menu

How to save a model: The Merge feature consists of two options:

Merge Model and Merge Submodel.
• Select Save from the File menu. If the model does
not already have a name, the Save As dialog box will
appear.

How to save a model with a new name:

Merge Model
1. Select Save As from the File menu. The Merge Model option allows two or more
independent (complete or incomplete) models to
2. Enter the new file name in the Save As dialog box
as shown in the following dialog box.
be merged into a single model. Duplicate ele-
ments found in the base model and the merging
3. Select OK. model are treated differently according to the ele-
ment type.
1. Entity and attribute names common to both
models are considered common elements in
the merged model. For example, if both
models contain the entity type In-Box, the
merged model will contain only the record
from the base model in the Entities table for
In-Box.
2. Duplicate locations, resources or path net-
works must first be renamed or deleted from
the merging model. Otherwise, an error
message occurs and the merge will termi-
nate.
Backup File 3. If the two models use different graphic
ProModel also creates a backup file every time a libraries, ProModel will give the user the
model is saved. The backup file is named the choice to append the merging model's
same as the model file, only with a .BAK exten- graphic library to the base model's graphic
sion. library.
4. All other duplicate model elements cause a
prompt to appear with the choice to delete
Model Merging the duplicate element from the merging
Model merging is a powerful feature that allows model or cancel the merge process.
large or complex models to be built in smaller
segments. A model segment may be as small as a Merge Submodel
single workstation or as large as an entire depart-
The Merge Submodel option allows commonly
ment. After all segments are ready, they can be
used submodels to be merged into an existing
merged together to form a single model.
model in one or more places. Submodels are cre-
 ProModel 65
User Guide

ated just like any other model and may be com- How to merge a model or submodel
plete or incomplete models. into an existing model:
When specifying a submodel, you are prompted
for a “tag” to be attached to each element of the 1. Open the initial (base) model.
submodel as either a prefix or suffix. For exam- 2. From the File menu select Merge.
ple, you may be developing a model with four
3. Select Model or Submodel from the submenu.
workstations. Instead of creating workstations
individually, you could create a submodel with 4. Specify the name of the model to be merged in the
only the common elements (e.g., in-box, out-box, following dialog box.
telephone, variables, arrays, etc.) and merge the
submodel into the main model four times. In the
resulting model, you would then fill in the unique
portions of each workstation. Entity and attribute
names will not be tagged.
In the following example, the tag “A_” is
attached as a prefix to every element of the sub-
model. A location called Queue1 in the submodel
becomes A_Queue1 in the main model and so on.
Likewise, a variable called Rejects becomes
A_Rejects in the merged model.
5. If you select Submodel, specify a prefix or suffix to
be attached to each element of the submodel.
6. Click on the layout where you want the model or
submodel to appear. A bracket appears on the screen,
representing the upper left corner of the merging
model’s layout. This bracket moves as you move the
mouse, allowing you to correctly position the layout to
be merged.
7. Next, you will be asked if you would like to append
the graphic library file from the model or submodel to
the current graphic library file. Select yes or no
depending on your preference.

Please note 8. When the model is merged in, the graphical ele-
ments remain selected so that you can position the
merged model exactly where you want it.
Tags used as prefixes must begin with a letter, A
through Z, or an underscore. For example, the
tag “3C_” is invalid and would produce an error
message. Please note

When merging models, if the zoom factors and

grid scales are not the same, ProModel will
66 Chapter 4:
File Menu

adjust the sizes of graphical elements in the How to view the text of a model:
merging model to the scale of the original model.
• Select View Text from the File menu. The model's
text is displayed in a window as shown in the following
example.
View/Print Model Text
The modular nature of ProModel makes it easy to
focus on the individual elements of a model.
However, it can still be useful to see an entire
model with all of the model elements in view at
one time. ProModel provides two ways to accom-
plish this. The first is through the View Text
option and the second is through the Print Text
and Print Layout Options.
The second major division of the File menu con-
tains the following options.

Only the first 30 characters of names will appear

in the names column.
Each menu selection is covered in detail in the
following pages.
Please note
• View Text Displays the text of the current
model data in a window. You may leave the View Text window open for ref-
• Print Text Prints the text of the current erence while editing the model. However, any
model to either a file or the printer. updates will not appear until you close the win-
• Print Layout Prints the model layout to a dow and select View Text again.
printer.
• Printer Setup Opens a dialog box to allow
printers to be selected and controlled.
Print Text
View Text The Print and Print Layout options allow you to
The View Text option displays the text of the cur- print a model to any printer configured for use
rent model data in a window. This window may with Windows. You may also save a text copy of
be sized or shrunk to an icon for later viewing. the file to disk.
 ProModel 67
User Guide

How to save a text copy of the current Print Layout

model: You may print the layout of any model including
all locations, path networks, resources, variables
1. Select Print Text... from the File menu. and background graphics to any printer config-
2. Select To Text File from the submenu. ured for use with Windows. Regardless of the
size of the model layout, the layout will be pro-
3. Supply a name for the file in the Print to Text File
portioned automatically to print on one standard
dialog box. The default file extension is TXT.
size sheet of paper.

How to print a model layout:

How to print the current text to a
printer: 1. Select Print Layout from the File menu.
2. Select the desired options from the Print dialog box
1. Select Print Text... from the File menu. and click OK.
2. Select To Printer from the submenu.
3. Select the desired options from the Print dialog box
and click OK.

3. Choose the elements to be included in the layout.

Please note

The entire layout may also be copied to the clip-

board for editing and printing in another appli-
cation.
68 Chapter 4:
File Menu

Printer Setup tion, you can prevent others from viewing or

altering logic contained in your model.
ProModel allows you to print to any printer con-
figured for use with Windows. At times you may
need to switch from the default printer to another
printer or plotter. This can be done easily
through the Setup option on the print dialog box. Create Model Package Copies the current model
and its associated files to a specific directory or
How to change the printer settings: disk as <model name>.pkg.
Install Model Package Copies the files in a *.pkg
1. Select Printer Setup... from the File menu to
file to the destination directory you wish to use.
access the Print Setup dialog box.
2. Select the desired options and click OK.
Creating a Model Package
The Create Model Package option allows you to
copy the current model and its associated files to
a specific directory as a single file entitled
<model name>.PKG. This file includes the model
file (*.MOD), the graphic library (unless you
check the Exclude Graphic Library option), and
any external files you defined (e.g., read files,
arrivals files, and shift files)—the model package
automatically includes bitmaps imported into the
background graphics.
When you create a model package, two options
are available:
• Exclude Graphic Library Excludes the
Model Packaging/Data Protec- graphics library file from the model pack-
age—if not required—and creates a smaller
tion package file.
Model packaging and Data Protection are power- • Protect Model Data Prevents those who
ful tools that allow you to distribute copies of install the model package from viewing or
your model for others to examine and review, yet editing the model data. When you load a
maintain the integrity of the model. When you model package, ProModel disables the View
create a model package, ProModel builds an Text, Print Text, and Expression Search fea-
archive of files necessary to run the model and tures, plus the Build menu and portions of
allows you to distribute a copy of the model’s the run-time Options and Information
graphics library. When you apply Data Protec- menus.
 ProModel 69
User Guide

Please note How to install a model package:

You may NOT use dynamic plots with protected 1. Select Install Model Package... from the File
models. Menu.

How to create a model package:

1. Select Create Model Package from the File menu.

2. Select the model package (*.pkg) from the Install

Model Package dialog.
3. In the Destination field, type the name of the direc-
tory to which you want to copy the model package.
4. Select OK. After you install the model package, a
dialog will appear and allow you to load the model.

2. Enter the name you wish to use for the model pack-
age (by default, ProModel uses the name of the current
model with a *.pkg extension). You may also use the
Browse... button to select the model name and direc-
tory.
3. Check the Exclude Graphics Library box if you
want to package the model without the graphics library.
4. Check the Protect Model Data box if you want to
protect your model data and prevent other users from
changing or viewing the model data.
5. Click OK.

Installing a Model Package

Install Model Package copies all files in a model
package to a specified destination directory and
gives you the option to load the model.
70 Chapter 4:
Edit Menu

Edit Menu multiple edit tables and windows may appear on

the screen at the same time, the Edit menu com-
The Edit menu is the second selection on the mands pertain only to the currently active win-
menu bar. It changes forms depending on which dow. (To activate a window, click anywhere inside
window is currently active when choosing Edit. it.)
• If the active window is an edit table such as
the Locations edit table, the Edit menu con-
tains options for inserting, deleting and mov-
ing records. Editing Tables
• If the active window is the Processing edit When creating or modifying records in an edit
table, the Edit menu contains two additional table such as a Locations or Entities table, the
options for copying and pasting completed Edit menu appears as follows.
process and routing records.
• If the active window is a Notes window, the
Edit menu contains selections for cutting,
copying, and pasting text within the current
window or transferring it to another window.
• If the active window is a logic window, such
as the one for the operation column of the
processing module, the Edit menu contains The following table briefly lists the function of
an additional selection, Compile, which each selection of the Table Edit menu.
checks the syntax of the logic in the logic
Delete Deletes a record from the table.
window. This option is additional to the cut
and paste functions normally available in a Insert Inserts a record in the table above the cur-
notes window. rent record.
• Finally, if the active window is either the
Append Appends a record to the end of the table.
Graphic or Background Editor, the Edit
menu contains three sections. The first sec- Move Marks a record for moving to a new posi-
tion has choices for cutting, copying, and tion in the table. Only one record may be marked
pasting graphic objects to and from Pro- at a time.
Model's internal clipboard. The second has
Move to Moves the previously marked record in
options to cut and paste items to and from
the table above the current record.
the Windows Clipboard. The third has
options to import and export graphics from
other applications. How to delete a record from a table:

Please note 1. Select the desired record by clicking in any field of

the record.

The Edit menu is accessible only while working 2. Select Delete from the Table Edit menu.
inside a module such as a processing edit table or
a Notes edit window. If no module is currently
open, the Edit selection is not available. Because
 ProModel 71
User Guide

How to insert a record in a table: pasting entire process and routing records appear
in the Edit menu.
1. Position the cursor in the record below where you
wish the new record to be inserted.
2. Select Insert from the Table Edit menu.

How to append a record to the end of a

table:
The Processing Edit menu's first five selections
1. Position the cursor in any record of the table. are identical to the Table Edit menu. The two
2. Select Append from the Table Edit menu. A new additional menu items are as follows:
record will appear below the last record of the table. Copy Record Copies all fields of the current
record for subsequent pasting.
Paste Record Places a copy of the most recently
How to move a record to a new posi- copied record above the current record.
tion in a table:
Please note
1. Select the record to be moved by placing the cursor
in any field of the desired record. Notes on editing process records:
2. Select Move from the Table Edit menu.
1. A process record consists of all fields in the
3. Position the cursor in the record that is below the Process edit table, as well as all corresponding
final destination of the selected record and select Move routing records defined in the Routing edit table
to from the Table Edit menu. for the given process.
2. From a Routing edit table, you may only use
the Copy Record and Paste Record options to
Editing Process Records copy routing information to another routing
record.
When editing the records in the Processing edit
table, two additional options for copying and 3. These options cannot be used to copy process-
ing or routing records from one model to another.

How to copy information from another

record:

1. Select the information to copy from field of the

desired record.
72 Chapter 4:
Edit Menu

2. From the Edit menu, select Copy Record (or press Cut Removes the selected text and places it in
CTRL + C) to copy the information. the clipboard.
3. In the field you want to place the information, select Copy Copies the current text and places it in the
Paste Record from the Edit menu (or press CTRL +
clipboard.
V).
Paste Inserts the contents of the clipboard at the
cursor.
Clear Deletes the selected text without placing a
Please note
copy in the clipboard.
Alternately, you may copy information between In addition to the options in the edit menu, the
records using the right-click menu. notes window itself contains four buttons. There
are three edit buttons, Cut, Copy, and Paste which
work exactly the same as the corresponding
options in the Edit menu, and a Print button. The
Editing Notes Windows print button prints the text in the notes window. A
status bar appearing at the bottom of the Notes
You may annotate individual records of the loca- edit window shows the current line position of
tions, resources and entities tables through Notes the cursor (e.g., Line: 2).
windows. When editing the text of a notes win-
dow, the Edit menu changes to the following
form. Editing Logic Windows
All multi-line logic windows, such as the opera-
How to annotate a record: tion logic window of the Process edit table,
include the editing function buttons shown in the
1. Click inside the record to be annotated. following example. These buttons include cut,
2. Click on the Notes button at the right of the table. copy, paste, undo, local find and replace, build,
compile, print, and help. Using the Cut, Copy, or
Paste button works exactly the same as using the
corresponding option from the Edit menu.

The selections available from the Notes Edit

menu are defined as follows.
 ProModel 73
User Guide

Build The Logic Builder, which may also be Please note

accessed by clicking the right mouse in the logic
window button, is a tool that allows you to build A status bar is displayed at the bottom of a Logic
logic without typing a single keystroke. Primarily edit window, and shows the current line position
for building logic in the logic windows, it may of the cursor (e.g., Line: 2).
also be used for building expressions in expres-
sion fields.
Compile The Compile menu item checks the
logic in the edit window to see if it is complete Editing Background Graphics
and syntactically correct. If an error is found, an
information box with details regarding the When working with graphic objects in the Back-
error(s) appears. For example, the following error ground Graphics module, the Edit menu appears
is a result of the incorrectly spelled statement as follows.
“Acum 2.”

Cut Removes the selected object(s) and makes a

temporary copy that may be pasted back into the
layout window.
Print Prints text, such as the operation logic for
a single location, in a logic window and is helpful Copy Makes a temporary copy of the selected
when you are trying to debug a model and need to object(s) for pasting later.
work with particularly complex logic at certain Paste Adds the most recently cut or copied
locations. object(s) to the layout window.
Help Provides context-sensitive help. ProModel
will provide help with select words or any word Please note
with the cursor next to it.
While in the Background Graphics module, CUT,
COPY, and PASTE all use ProModel's internal
clipboard. Any objects copied to this clipboard
cannot be pasted into other Windows applica-
tions. To copy objects to other applications, use
COPY TO CLIPBOARD.
74 Chapter 4:
Edit Menu

Delete Deletes the selected objects from the lay- 2. Select Edit Background Graphic from the right-
out window. click menu.

Select All Selects all of the objects in the layout

window.
Copy to Clipboard Copies the entire contents of
the workspace to the Windows clipboard. Objects
cannot be copied individually to the clipboard.
ProModel copies the workspace as a bitmap or
windows metafile for easy transfer to other
graphics packages that use the Windows clip-
board.
Paste WMF Pastes a Windows metafile (WMF)
from the Windows clipboard into the Edit win-
dow. You must have previously copied a Win- 3. Edit the graphic as desired.
dows metafile to the Windows clipboard.
Paste BMP Pastes a bitmap file (BMP) from the
Windows clipboard into the Edit window. You Editing & Moving Graphics
must have previously copied a bitmap to the Win-
dows clipboard. ProModel allows easy adjustment and fine tuning
of the graphics in one window rather than open-
Import Graphic Imports a WMF, BMP, PCX or
ing individual modules to move each object. This
GIF file into the layout window.
makes it possible to move or rearrange a whole
Export Graphic Exports the graphic in the layout submodel or model after it has been merged. To
window to a WMF or BMP file. move any or all graphics in a model, ProModel
must be in common mode (all modules must be
How to edit background graphics: closed, leaving only the layout window open).
While in common mode, graphics that can be
1. Right click on the background graphic you wish to moved and arranged in the layout window
edit. include locations, path networks, static and
dynamic resources, variables, and background
graphics. Multiple graphics can be selected and
moved simultaneously. When graphics are
selected, the layout can be scrolled and the graph-
ics will remain selected.

How to move graphics:

1. Close all build modules leaving only the layout win-

dow open.
 ProModel 75
User Guide

2. Left click and drag the selected graphic to the but will move when a location to which they are
desired position. connected is moved. If a routing path has multi-
3. To move multiple graphics, hold down the Shift key ple segments, only the segment connected to the
while left clicking the desired graphics to select them location being moved gets readjusted. However,
and then drag them to the desired position. Using the when both locations on the routing path are
shift key with a left click deselects a selected graphic. moved simultaneously, the whole routing path is
4. Fine tune the position of the selected graphic(s) by moved.
using the arrow keys on the keyboard to move one
pixel at a time.

When a submodel or model is merged into

another model, all graphics associated with it are
selected. This allows for immediate movement
by left clicking on the graphics and dragging
them to the desired position in the Layout win-
dow. You may also scroll the layout first and then
move the selected graphics.

Please note

Multiple graphics can also be selected by drag-

ging a bounding box around the graphics. Hold-
ing the left mouse button down, drag the mouse
from one corner of the graphics to the opposite
corner. The bounding box must completely
enclose the graphics you wish to select.

Special Considerations for Moving

Graphics
Locations When you click on a location with In the examples above, the machine on the right
multiple graphics defined for it (i.e., counter, sta- is moved. The routing paths remain connected to
tus light, label) in common mode, it is selected as each graphic while the path segment connected to
one graphic. Multiple units of a location can be the moved graphic is adjusted accordingly.
moved individually. Adjusting the position of an
Path Networks Path networks are not resized
individual graphic in a multiple graphic location
when moved. Any resource points defined for a
must be done in the locations module.
dynamic resource are moved when the path net-
Routing Paths Routing paths defined in the Pro- work is moved. The resource points remain rela-
cessing module cannot be selected for movement tive to the node for which they were defined.
76 Chapter 4:
View Menu

Resources When a dynamic resource is moved,

the resource point associated with it moves but
View Menu
not the entire path network. The View menu provides options for modifying
the model editing environment. These options are
Sizing Graphics cannot be sized in common
defaults, used each time the program is started
mode.
and are not specific to any particular model. The
Snap-to-Grid Graphics will not snap to the grid View menu consists of three categories:
in common mode, but their position can be fine- Switches, Settings, and Commands. Each of
tuned using the arrow keys on the keyboard to these categories is explained in the following sec-
move the selected graphic(s) one pixel at a time. tions.
Labels To view the label or edit a location, path
network, resource, or variable graphic, right click
on the item. If you double left click on an item,
ProModel opens the build module and highlights
the record where you defined the element.

How to access the View menu:

• Select View from the menu bar.

Switches
The following selections are available from the
switches section of the View menu. Switches are
 ProModel 77
User Guide

options you can check or uncheck to turn on or menu. These selections and their submenus are
off. discussed in more detail on the following pages.

Snap to Grid Check this switch to cause any

object subsequently drawn or placed on the lay- Views Allows you to define, then quickly and
out to be positioned on the nearest grid line. Snap easily access specific areas of the model layout.
to grid snaps the upper left corner of a graphic. Once the view is defined, you can select it while
Show Grid Check this switch to show the grid in editing or running the simulation.
the layout window. Zoom to Fit Layout Shrinks or enlarges the lay-
Show Layout Coordinates Displays cursor’s the out to include the entire model.
coordinates in the upper-left-hand side of the lay- Zoom Allows you to shrink or enlarge the layout
out window. by the percentage selected.
Show Hidden Networks Check this switch to
show the invisible path networks during editing.
A path network can be made to be invisible by
Views
selecting the “invisible” option for the particular The Views feature allows you to define, then
network while in the Path Networks editor. quickly and easily access specific areas of the
Show Routing Paths Causes routing paths to be model layout. Selecting a view scrolls the layout
visible during run time as well as edit time. If the window and adjusts the zoom so you see a spe-
option is not checked, the routing paths are visi- cific region of the layout regardless of the layout
ble only while in the processing editor. window’s size. Once a view is defined, you can
select it while editing or running the simulation
by selecting the view from the View menu or by
Toolbars using the keyboard shortcut.
Allows you to toggle the various ProModel tool-
bars on and off. See “Toolbars” on page 85 for Defining & Selecting Views
more infomation on each toolbar.
How to define a view:
Settings 1. At edit time, select the View menu.
The following table defines each of the selections
available from the settings section of the View
78 Chapter 4:
View Menu

2. Select the Views item. If no defined views exist, the How to select a view from the menu:
Views dialog is displayed and not the submenu shown
here. If the Views dialog appears, skip step 3.
1. At edit time or run time, select the View menu.
2. Select the Views menu item to display the submenu
list.

3. Click Define from the extended menu and the

Views dialog appears.

3. Click on the desired view from the submenu.

How to select a view with shortcut key

CTRL + n:

• Press CTRL + n to select the desired view where n is

the number (1-9) of its position in the view list (e.g.,
pressing CTRL + 1 would access Single Screen Zoom
from the view list above and CTRL + 3 would access
the Waiting Time Zoom view). Views beyond nine will
not have a CTRL + n shortcut key.

4. With the Views dialog open, select the area in the

layout window you want to define as a view using the
scroll bars and zoom feature in the View menu. Or size Managing Your Views
the layout window to the desired view.
When you click on Define from the Views menu,
5. With the layout window set, type a name for your the Views dialog is displayed. It lists the defined
view in the View Name field at the bottom of the views in the Views List and provides buttons for
Views dialog, and then click the Add button to define
adding views, removing views, and managing the
the view you have selected in the current layout win-
list. The function of each button is described
dow.
next.
6. The name you have entered will appear in your list
of views. Add Adds the view, which you have named in
the View Name field, to the list of views.
Remove Deletes the currently highlighted view
from the View List.
Please note
Move Up Moves the currently highlighted view
Views cannot be defined at run time. up one position in the list creating a correspond-
ing change to the menu and CTRL+ n order.
 ProModel 79
User Guide

Move Down Moves the currently highlighted The Views Panel may be moved or resized, and
view down one position in the list creating a cor- will remain on top of the simulation window until
responding change to the menu and CTRL+ n the Panel is closed.
order.
Simply click on the name of a view in the Panel
Rename Renames the currently selected view to to switch to that view.
the name you have typed into the View Name
field. Referencing a View in Model Logic
Set View Sets the highlighted name in the View Once a view has been defined, it may be refer-
list to the portion of the model currently visible in enced in the model using the VIEW statement
the Layout window. (e.g., VIEW “Service Office”). This is useful for
View Name This is the field where you type the illustrating certain parts of the model at specific
name of the view you wish to add. times during run-time. For syntax and examples,
see “View” on page 566.
Show View Checking this box will cause your
views to be displayed in the Layout window as
you select them in the list. Zoom Feature
The Zoom feature allows you to shrink or enlarge
Using Views at Run-time the layout by the percentage selected.
When the simulation is running, you may choose
the active view by picking its name from the How to zoom in or out on the layout:
Views menu or the Views Panel.
The Views menu is accessible during run-time 1. Select Zoom from the View menu.
from either the Menu Bar’s Option menu or the 2. Choose any preset zoom level, or the Custom
Right-Click menu. Zoom option.

The Views menu will display a list of your Preset Zoom Levels
defined views. There is also an option to open the
Views Panel.
The Views Panel is a dialog window with a list of
your defined views.
80 Chapter 4:
View Menu

Please note Please note

The minimum and maximum zoom levels are cal- Changes to these settings are saved as the default
culated automatically depending on the total size settings.
of the layout at 100% zoom.

Grid Size
Layout Settings By using the grid dialog box, you may set the res-
The following selections are available from the olution of the grid lines to your preference.
Settings section of the View menu.
Please note

You may save the grid settings for the model by

checking the Save as default grid settings check
The Layout Settings submenu contains selections box.
for changing the grid characteristics, color of the
layout window background, and the routing
arrow colors. These, as well as default setting
changes, apply to any currently loaded model. To
change any of these items for the current model
only, use the options provided in the General
Information dialog. The routing path color can be
changed for the current model only by selecting
the Path Options button in the Processing mod-
ule.
The following table defines each of the selections
available from the Layout Settings submenu.

Grid Settings Provides options to control the

amount of space between grid lines. It also pro-
vides the option to define the grid units in terms
of distance and time per grid unit.
Background Color Allows the user to change the
background color in the layout window.
Routing Path Color Provides the option to
change the routing color used in processing logic.
 ProModel 81
User Guide

How to change the colors and resolu- How to set the default time and dis-
tion of the grid lines: tance per grid unit:

1. Select Layout Settings from the View menu. 1. Select Layout Settings from the View menu.
2. Select Grid Settings from the Layout Settings sub- 2. Select Grid Settings from the Layout Settings sub-
menu. menu.
3. Select the Ones or Tens option button. 3. Select the Scale button from the Grid Dialog.
4. Select the desired color. 4. Enter the desired time and distance per grid unit.
5. Use the scroll bar to adjust the resolution.

Please note
Please note
The “Recalculate path lengths when adjusted”
To change the color of the grid lines, select the option applies to path networks, conveyors, and
Ones button and choose a color. To change the queues. For details regarding recalculation of
color of every tenth grid line, select the Tens but- times and distances when editing path segments,
ton and choose a color. see “Path Networks” on page 117.

Grid Scale Background Color

In addition to setting the resolution of the grid The Background Color option allows the user to
lines, you may also associate a time and distance change the background color in the layout win-
value to each grid unit. This is extremely useful dow.
when you are creating conveyors, queues, or path
networks to scale and you want the time or dis- How to set the background color of the
tance between nodes to be based on the number layout:
of grid units between the nodes.
1. Select Layout Settings from the View menu.
2. Select Background Color from the Layout Set-
tings submenu.
3. Select the desired color.
82 Chapter 4:
View Menu

4. Click OK. 5. Select Add to Custom Colors. The color now

appears in one of the 16 custom color boxes.

Routing Path Color

ProModel allows you to select which colors to
use when showing selected, unselected and
related routings in the Processing module. This
helps in visually identifying the origin and desti-
nation of a process routing.

How to specify the routing colors:

Custom Colors 1. Select Routing Path Color from the View menu.

ProModel allows you to create up to 16 custom

colors for use anywhere a color selection is avail-
able. Entity, location, and resource icons, as well
as background graphics, can use any custom
color defined in the colors menu.
When creating a custom color, the nearest solid
color is shown next to the dithered color for refer-
ence.
2. Click on the desired routing type, Unselected,
How to create a custom color and add Selected, or Related from the menu.
it to the color menu: 3. Select the desired color.

1. Select Layout Settings from the View menu.

2. Select Background Color... from the Layout Set-
tings submenu.
3. Move the cursor to the area on the multi-color chart
closest to the custom color you desire and click the left
mouse button.
4. Adjust the color by moving the custom color adjust-
4. Click OK.
ment slider up or down until the desired shade is
obtained. Alternately, you can manually adjust any of
the color definition fields (Hue, Sat, Lum, Red, Green,
Blue).
Routing Path Types
Unselected All routing lines not for currently
highlighted process record.
 ProModel 83
User Guide

Selected Routing line for currently highlighted Edit Table Color

routing record.
ProModel allows you to specify the table color
Related Routing lines for highlighted process used in edit tables.
record, except highlighted routing record.
How to change the edit table back-
Edit Tables ground color:

1. Select Edit Tables from the View menu.

Edit Table Fonts
2. Select Color from the Edit Tables submenu.
Edit tables are used extensively in ProModel for
data entry. ProModel allows you to specify the 3. Choose the desired color.
font used in these tables. 4. Click OK.

How to change the edit table font:

1. Select Edit Tables from the View menu.

2. Select Font from the Edit Tables submenu.

Please note

For information on creating custom colors, see

“Background Color” on page 81.

3. Choose the desired font by scrolling through the

Font selection list box. Commands
4. Choose the Font Style. The Commands section of the View menu con-
5. Choose the Font Size. tains various selections for controlling the model-
ing environment.
6. Click OK.

Refresh Layout Clears and redraws the graphics

in the layout window.
84 Chapter 4:
Window Menu

Reset Window Positions Causes all edit tables to

return to their original positions and sizes.
Window Menu
The Window menu allows you to rearrange win-
dows and icons and select the active window.
These functions are standard to all Windows‰
applications.

Tile Causes all open windows to fit in the avail-

able screen space. Windows that may be hidden
behind other windows become visible.
Cascade Causes all open windows to overlap
such that the title bar of each window is visible.
Arrange Icons Causes all icons representing
iconized applications to be arranged neatly along
the bottom of the screen.

Please note

Below Arrange Icons is a list of the open win-

dows. The window with the check next to it is the
active window.

How to reset the windows to their

default positions:

• Choose Reset Window Positions from the View

menu.
 ProModel 85
User Guide

Help Menu Toolbars

The ProModel Help menu is a convenient, quick The ProModel toolbars provides quick access to
way to look up information about a task you are many of the options found in the menu bar.
performing, a feature you would like to know
The toolbar space may contain up to nine tool-
more about, or a command you want to use. Pro-
bars, which can be be toggled on or off in the
Model Help is available whenever you see a Help
View menu. These toolbars are described below.
command button, or Help as an item on a menu
bar.
File

New Closes any currently opened model so a

new model can be built. This command is unnec-
essary if no other model is open. If the currently
opened model has changed, ProModel will ask if
The selections from the Help Menu are as fol- you want to save the model before closing it.
lows:
Open Opens a user-specified model and clears
Index Brings up the Main Help Index. previous model data.
Context Opens the help system to the topic Save Saves an open model under the current file
related to the currently active window. name. If no file name has been given, you will be
ProModel Support on the Web When you prompted for a file name.
select this option from the help menu, ProModel Create Package Bundles all files used for a
automatically connects you with the ProModel model into one package. See “Creating a Model
customer service page on the PROMODEL web Package” on page 68 for more information.
site.
Install Package Copies all files in a model pack-
About ProModel Displays a message containing age to a specified destination directory and gives
information about the product. you the option to load the model. See “Installing
a Model Package” on page 69 for more informa-
tion.

Layout

Show Grid Check this switch to show the grid in

the layout window.
Show Hidden Networks Check this switch to
show the invisible path networks during editing.
A path network can be made to be invisible by
86 Chapter 4:
Toolbars

selecting the “invisible” option for the particular Simulation

network while in the Path Networks editor.
Show Routing Paths Causes routing paths to be
visible during run time as well as edit time. If the Simulation Options Opens the simulation
option is not checked, the routing paths are visi- options dialog. See “Simulation Options” on
ble only while in the processing editor. page 338 for more information.
Scenarios Opens the scenarios dialog. See “Sce-
View
narios” on page 343 for more information.
Play Begins the simulation

Views Allows you to define, then quickly and Pause Pauses and unpauses the simulation when
easily access specific areas of the model layout. it is running.
Once the view is defined, you can select it while Stop Ends the simulation and prompts you
editing or running the simulation. See “Views” whether to collect and view statistics up to the
on page 77 for more information. point where the simulation was stopped.
Zoom to Fit Shrinks or enlarges the layout to Animation On/Off Toggles the animation on and
include the entire model. off
Zoom Allows you to shrink or enlarge the layout View Statistics Opens Output Viewer 3DR.
by the percentage selected.
Simulation Information
Build Basic

Location Information Select this option and

The options in this toolbar open the respective choose a location to view an information box
build modules. Mouse over a toolbar button to with real time information about the location.
see its function and then refer to Chapter 5 for Information for all locations may also be dis-
information of that build module. played.
Variable Information Select this option to show
Build Advanced
the current state of all real and integer global
variables.
Array Information Select this option to show the
The options in this toolbar open the respective current value of all cells for arrays of up to three
build modules. Mouse over a toolbar button to dimensions.
see its function and then refer to Chapter 6 for
information of that build module. Define Dynamic Plots Allows you to define
Dynamic Plots. See “Dynamic Plots” on
page 354 for more information.
 ProModel 87
User Guide

View Dynamic Plots Allows you to view previ-

ously defined Dynamic Plots. See “Dynamic
Right-Click Menu
Plots” on page 354 for more information. To simplify many of the steps required to perform
common modeling operations, ProModel
Debug includes a variety of right-click menus. From
these menus, you can access context-sensitive
options and settings for variables, locations, pro-
cessing, path networks, resources, and other com-
User Pause by Time Allows you to specify by ponents. The following menu appears when you
clock time when the simulation should pause right-click on the layout.
next.
User Pause by Date Allows you to specify by
calander date when the simulation should pause
next. This option is not available when you are
not running the simulation by calandar date.
Trace Step Select this option to step through the
trace listing one event at a time. Each time you
click the left mouse button, the trace will advance
one event. Clicking and holding the right mouse
button while in this mode generates a continuous
trace.
Filtered TraceOpens the Filtered Trace dialog. The right-click layout menu includes the follow-
See “Trace Mode” on page 351 for more infor- ing options:
mation. Edit Background Graphic Only when you have a
Debug Opens the Debug dialog. See “Debug background graphic defined, this option appears
Option” on page 347 for more information. and lets you edit the graphic.
Snap to Grid Selecting this option snaps all
Tools graphics to the grid.
Show Grid When you select this option, Pro-
Model displays the background grid.
Graphic Editor Opens the Graphic Editor. See
Show Layout Coordinates Displays cursor’s the
“Graphic Editor” on page 304 for more informa-
coordinates in the upper-left-hand side of the lay-
tion.
out window.
Simrunner Opens Simrunner.
Show Hidden Networks Displays all hidden net-
Stat::Fit Opens Stat::Fit. works.
3D Animator Opens 3D Animator. Show Routing Paths Displays all routing paths
used in the model.
88 Chapter 4:
Right-Click Menu

Views From this option, you may select from the

views defined in the model.
Zoom to Fit Layout This option resizes the model
to fit the entire image in the layout window.
Zoom Allows you to select the zoom percentage.

Layout Settings From here, you may select and

define the grid settings, background color, and
routing color.
Refresh Layout This option refreshes the image
to reflect recent changes.

Please note

For information about the right-click menus for

model elements (e.g., locations, variables, rout-
ings, resources, path networks, queues, and con-
veyors), see “Building the Model: Advanced

Elements” on page 217.

 ProModel 89
User Guide

Chapter 5: Building the Model:

General Elements

Build Menu How to access the Build menu:

The Build Menu is the gateway to all modeling
• Select Build from the menu options bar.
elements used to define a model. Through this
menu you specify the locations, entity types,
arrival rates, resources, path networks, down-
times, processing logic, variables, attributes, Each selection from the Build Menu is covered in
arrays, macros, and subroutines that provide the detail in the following sections of this chapter.
flexibility needed to model your system.

Any element represented by a graphic in the lay-

out window can be edited by holding the CTRL
key while clicking on the graphic representing
that element.
90 Chapter 5:
Locations

Locations or...

Locations represent places in the system where

entities are routed for processing, storage, or • Right click on the existing location and select Edit.
some other activity or decision making. Loca-
tions should be used to model elements such as
delivery locations, warehouse locations, network
servers, and transaction processing centers. Locations Editor
Every location has a name and a name-index The Locations Editor consists of three windows:
number. The name-index number is the location’s the Location Graphics window in the lower left
numerical position in the list of locations. Logic portion of the screen, the Location edit table
which refers to a location, such as routing logic, along the top of the screen, and the Layout win-
can use either the location's name, or the LOC() dow in the lower-right portion of the screen.
function to refer to the location. The LOC() func- These windows can be moved and resized using
tion allows a location whose index number has the mouse.
been stored in an attribute or variable to be refer-
enced. See “Loc()” on page 501.
Locations are defined in the Locations Editor,
which is accessed through the Build menu.

Layout Window

Location Graphics Location Edit Table

Window

The Location edit table contains information

about every location in the model, including
characteristics such as capacity and number of
units. The Location Graphics window is a tool
box used for creating, editing, and deleting loca-
How to create and edit locations tions graphically. Locations are positioned in the
Layout window.
• Select Locations from the Build menu. The Loca-
tions Editor appears.
 ProModel 91
User Guide

Location Edit Table Please note

A location's characteristics can be modified with
Individual units of a multi-unit location may dif-
the Location edit table. The Location edit table
fer in capacity only if every unit's capacity is
contains fields for displaying the graphic icon,
greater than 1. For example, in a location with
specifying the location name, and defining other
two units, one may have a capacity of 5 and the
characteristics of each location. Each of these
other a capacity of 10. However, one unit may not
fields is explained below. You can edit the
have a capacity of one and the other a capacity of
desired field directly in some cases, or by select-
five. (See “Multi-Capacity, Multi-Unit, and Mul-
ing a record and clicking the column heading but-
tiple Locations” on page 100.)
ton of the desired field.

Units The number of units of a location, up to

999. A multi-unit location works like several
locations with common characteristics. (See
“Multi-Capacity, Multi-Unit, and Multiple Loca-
Icon The graphic icon used to represent the loca- tions” on page 100.)
tion. Changing location graphics is done using
DTs Click on this heading button to define loca-
the tools in the Location Graphics window. If
tion downtimes, including any setup times. (See
multiple graphics have been used to define a
“Location Downtimes” on page 101.)
location, the first graphic used is shown here.
Clicking on the Icon button brings the graphic for Stats Click on this heading button to specify the
the current location into view if it is not currently level of statistical detail to be gathered for the
showing in the layout window. location. (To view a location's statistics after a
simulation run, choose View statistics from the
Name The name of each location. Names can be
Output menu.) Three levels of data collection are
up to 80 characters in length and must begin with
available:
a letter (for more information on naming items,
see “Names” on page 394). A location's name can • None No statistics will be collected.
be changed by editing this field. The Search and • Basic Only utilization and average time in
Replace is automatically called when the name is location will be collected.
changed. • Time Series Collects basic statistics and
Cap. The capacity of the location refers to the time series tracking the contents of the
number of entities the location can hold or pro- location over time.
cess at any one time. A location's maximum Rules This field defines (1) how a location
capacity is 999999. Entering INF or INFINITE selects the next incoming entity from several that
will set the capacity to the maximum allowable are waiting to enter this location, (2) how multi-
value. If this field contains an expression, it will ple entities at a location queue for output, and (3)
be evaluated at the start of the simulation before which unit of a multi-unit location is selected by
any initialization logic. Accordingly, a location's an incoming entity. (See “Rules Dialog Box” on
capacity will not vary during the simulation run. page 109.) To edit any of this information at a
92 Chapter 5:
Locations

location, click on the heading button to open the Edit Button Displays the Library Graphic Dialog
Location Rules dialog box. Box used to change the color, dimensions, and
orientation of the location graphic.
Notes Enter any optional notes about a location
in this field or click on the heading button to open Erase Button Erases the selected location
a larger Notes window. graphic in the Layout window without deleting
the corresponding record in the Location edit
table.
Location Graphics Window
View Button Brings the selected location in the
The Location Graphics window provides a graph- edit table into view on the Layout window.
ical means for creating locations and changing
their icons.
How to define a new location graphi-
cally:
New Box
1. Check the New Box in the Location Graphics win-
Counter
dow.
Gauge/Tank
2. Select a location symbol or icon from the Location
Conveyor/Queue
Graphics window.
Text Label
Status Light 3. Click on the Layout window where you want the
location to appear.
Entity Spot
Region 4. A new record is added automatically to the Location
edit table. You may now change the default name to the
desired location name.

How to define multiple locations, each

Icons added to the layout will either represent a having the same graphic:
new location or be added to an existing location's
icon depending on whether the New box at the 1. Check the New box inside the Location Graphic
top left of the window is checked or unchecked. window.
2. Select the desired graphic.
New Mode 3. While holding down the SHIFT key, click on the
Layout window where each location should appear.
Allows you to create a new location record each
time you place any location graphic on the lay-
out. The new location is given a default name
which may be changed if desired. New mode is
selected by checking the New box [X] at the top
of the Graphic Tools window.
 ProModel 93
User Guide

How to move a location graphic on the How to erase a location graphic:

layout:
1. Select the location graphic to erase.
• Drag the graphic to the desired spot on the layout. 2. Select the Erase button in the Location Graphics
window or press the <Delete> key. The location
graphic disappears, but the location record still exists
in the Location edit table.
How to move all graphics defined for a or...
single location:
1. Right-click on the location graphic in the layout
window.
• Drag inside the dashed box surrounding the graphic
(do not drag on an individual graphic inside the box).

How to move multiple graphics for 2. Select Delete Graphic. The location graphic disap-
two or more locations at once: pears, but the location record still exists in the Location
edit table.
1. Click outside of any graphic and drag to create a
rectangle encompassing all of the graphics to be
moved.
2. Drag the rectangle to the desired position on the lay- How to bring a location graphic into
out. view that is off the layout:

1. Highlight the record of the desired location in the

Location edit table.
How to delete a location: 2. Select the View button in the Location Graphics
window or click on the icon heading button.
1. Select the location record to be deleted in the Loca-
tion edit table.
2. Select Delete from the Edit menu.
or...
1. Right-click on the location graphic in the layout
window.

2. Select Delete [location name].

94 Chapter 5:
Locations

Add Mode exchange between continuous material and dis-

crete entities such as when a liquid is placed in
Allows you to add additional graphics to an exist- containers.
ing location, such as a text label, an entity spot, or
a status light. A location with multiple graphics Conveyor/Queue A symbol representing a con-
will be enclosed by a dashed box. Add mode is veyor or a queue. To create joints in a conveyor
selected by unchecking the New box [] at the top or queue, click on the conveyor or queue with the
of the Graphic Tools window. right mouse button. Drag the joints to achieve the
desired shape. Right click on a joint to delete it.
How to add an icon or symbol to an The options available with conveyors and queues
are described next.
existing location:
Label Any text used to describe a location. The
1. Uncheck the New Box in the Location Graphics label is initially synchronized with the name of
window. the location and changes whenever the location
name is changed. The name, size, and color of the
2. Select a location symbol or icon from the Location
Graphics window. text may be edited by double clicking on the label
or selecting it and clicking on the edit button (see
3. Click on the Layout window where you want the “Text Tool” on page 315). Once the name on a
additional icon to appear.
label is edited, it will no longer be automatically
4. The graphic or symbol is added to the location. changed when the location name is changed.
Status Light A circle that changes color during
the simulation to show the location’s status. For a
Location Graphics single capacity location, the states displayed are
idle/empty, in operation, blocked, down, waiting,
A location may have any one or more of the fol- and in setup. For multi-capacity locations, the
lowing graphics selected from the Location displayed states are up (operational) and down
Graphics window. (off-shift, on break, disabled).
Counter A counter representing the current num- Entity Spot An assignable spot on the layout
ber of entities at a location. The options available where the entity or entities will appear while at
with counters are explained next. the location. While an entity is at a location, the
entity’s alignment spot (defined in the Graphic
Gauge A vertical or horizontal sliding bar show-
editor) will appear exactly on top of the location's
ing the location's current contents during the sim-
entity spot, allowing the two graphics to align
ulation (shown as a percentage of the capacity).
exactly as desired. A multi-capacity location will
This graph will be updated constantly as a simu-
use as many entity spots as defined (in the order
lation runs. The options available with gauges are
defined) up to the capacity of the location. Enti-
explained below.
ties in excess of entity spots will continue to pile
Tank A vertical or horizontal sliding bar show- up on the last entity spot defined.
ing the continuous flow of liquids and other sub-
Region A boundary used to represent a location's
stances into and out of tanks or similar vessels.
area. A region may be placed in the layout over
This continuous modeling capability can be com-
an imported background such as an AutoCAD
bined with discrete-event simulation to model the
drawing to represent a machine or other location.
 ProModel 95
User Guide

This technique allows elements in the imported 2. A location may include any of the above
background to work as locations. graphics and symbols. However, a location can
have no more than one counter, one gauge, one
Library graphic Any of the graphics appearing
tank, one queue, one status light, or one region.
in the library graphic menu. Use the scroll bar to
view all available graphics. Library graphics may
3. Clicking on a layout graphic with no edit
be created or modified through the Graphic Edi-
table on the screen displays the name of the ele-
tor. The name for the graphic, the default name of
ment (location, etc.) represented by the graphic.
any location created with that graphic, can be
With any edit table showing, hold down the CTRL
saved in the Graphic Editor (see “Naming a
key while clicking on the graphic to display the
Graphic” on page 314).
location name.

How to edit a graphic already on the

layout:
Counter Dialog Box
• Double click on the graphic.
To edit the appearance of a counter, double click
on the counter on the layout, select the counter
or... and click on the Edit button, or right click on the
counter and select edit. The counter dialog box
allows you to choose the appearance of a graphic
1. Select the graphic.
counter that is used to display the contents of a
location. To change the digit color of the counter,
2. Click on the Edit button inside the Location Graph- click on the Digit Color button. To change the
ics window. counter's background and border, click on the
Frame button. The digit's font size and style may
or... be changed by clicking on the Font button.

1. Right-click on the graphic in the layout.

2. Select Edit Graphic from the menu.

Please note

Location graphics notes:

1. Location graphics are painted on the layout Gauge/Tank Dialog Box

in the order of the location list and, for any given When you create a gauge or tank, ProModel will
location having multiple graphics, in the order prompt you to specify which type you wish to use
that the graphic was added to the layout. before you paste it in the layout. To edit a gauge
or tank on the layout, double click on the gauge
96 Chapter 5:
Locations

or tank to display the gauge/tank dialog box, currently chosen options is shown in the lower-
select the gauge/tank and click on the Edit button, left corner.
or right click on the gauge or tank and select edit
graphic. From the gauge/tank dialog, you may
change a gauge to a tank and define its appear-
ance, orientation, and fill direction. You may also
access this dialog by selecting the gauge or tank
and clicking on the Edit button.

Library Graphic Dialog Box

To change or edit a library graphic that represents
a location, you may double click on the library
graphic on the layout, select the graphic and click
on the Edit button, or right click on the graphic
and select edit.

Text Dialog Box

To edit the appearance of a location label, you
may double-click on the text once it is on the lay-
out, select the text and click on the Edit button, or
right click on the text and select edit. The text is
typed in an edit window with several edit features
available via buttons above the window. The font,
color, alignment, rotation and frame may be
changed from this dialog box. A sample of the

This gives the option to change the icon, orienta-

tion, color, or graphic dimensions of the graphic.
The default dimensions for the graphic, which are
 ProModel 97
User Guide

created in the Graphic Editor, are displayed Queues

above the graphic. To change the dimensions of
the graphic, click on the Dimensions button. This A queue is a location that imitates the progressive
gives you the ability to specify horizontal or ver- movement and queuing of waiting lines. When an
entity enters a queue, ProModel executes any
tical and feet or meters to change the graphic
operation logic for the entity and then moves it to
dimensions.
the end of the queue. To have processing logic
execute after an entity arrives at the end of a
Queue/Conveyor Dialog Box queue, use a MOVE statement in the operation
To control the look and operation of a conveyor logic. A MOVE statement causes the entity to
or a queue, you may double click on the con- move to the end of the queue where any addi-
veyor/queue in the Layout window, select the tional operation logic defined will be processed.
graphic and click on the Edit button, or right click Operation logic following a MOVE statement
on the conveyor/queue and choose edit graphic. actually gets processed after the elapsed time that
The Queue/Conveyor dialog box appears. It also the entity would have reached the very end of the
allows you to specify whether you wish to define queue if no other entities were ahead of it. Fol-
the location as a conveyor or queue. Use the lowing a MOVE statement, any operation state-
scroll bar to set the width of the queue or con- ment is valid except for CREATE, SPLIT AS,
veyor. Select the style by clicking on solid, roller UNGROUP, UNLOAD, or another MOVE state-
(i.e., roller conveyor) or line. Click on the border ment.
color or fill color to change the color of the If a MOVE statement is specified that includes a
queue. If you want the queue to be visible during move time (e.g., MOVE for 5.2 sec), the entity
edit time and invisible during run time, click on speed and length of the queue are ignored. If a
the Invisible During Simulation option. See the move time is not included with the MOVE state-
discussion on conveyors and queues later in this ment, the move time is based on the entity speed
section for more information. and length of the queue (if no queue length or
entity speed is defined, the move time is zero).
Entities in a queue may not be preempted by
other entities and, once entities begin movement
in a queue, are not allowed to pass each other.
After the specified move time, however, entities
continue processing any additional operation and
output logic. A “No Queuing” rule specified for a
queue location allows entities to depart in any
order after completing their move time.
Queues are drawn from the beginning to the end
of the center-line and are assigned a default
length based on the graphic scale. However, the
default queue length may be overridden by enter-
ing a different length. When a queue is modified
graphically, the length will automatically be
recalculated based on the graphic scale unless
98 Chapter 5:
Locations

you checked the “Recalculate path lengths when entity on a conveyor is calculated using the fol-
adjusted” option. You can access this option from lowing formula:
the Tools menu under Options.
Time = (Conveyor Length - Entity Length or Width)/
Conveyor Speed
Conveyors And the percentage utilization is calculated using
A conveyor is a location that simulates the move- this formula:
ment of entities on either an accumulating or non-
accumulating conveyor and appears with a con- ∑ tc
veyor graphic. Entities can only enter a conveyor all Cc
entities
at the beginning and leave at the end. For accu- Util % =
mulating conveyors, if the lead entity is unable to T
exit the conveyor, trailing entities queue up
Where:
behind it. For non-accumulating conveyors, if the
lead entity comes to a stop, the conveyor and all tc = the time the entity spent on the conveyor
other entities stop. Entities on a conveyor may whether moving or not
not be preempted by other entities.
Cc = the conveyor capacity for that entity
The capacity assigned to a conveyor limits the
number of entities that can access a conveyor. T= the total simulation time
However, the cumulative total length or width of
the entities on the conveyor cannot exceed the Please note
conveyor length. In fact, the utilization statistics
for a conveyor reflect the amount of space uti- Unlike queues, MOVE statements for conveyors
lized on the conveyor throughout the simulation, may not include a move time. Processing logic
not the number of entities occupying the con- executed at the end of the conveyor may contain
veyor. Unlike other locations, an entity is not any operation statement except for CREATE,
routed to the conveyor until there is room at the SPLIT AS, UNGROUP, or UNLOAD. Addition-
beginning for the entity to fit, even if the con- ally, the ACCUM, COMBINE, and GROUP
veyor has capacity to hold it. statements are not allowed at the end of non-
ProModel executes operation logic for entities accumulating conveyors.
entering a conveyor as soon as they enter unless
the logic follows a MOVE statement. If no
MOVE statement is encountered, entities begin
their move on the conveyor after processing any Due to the space limitations of a conveyor, cer-
logic. If a MOVE statement is encountered, entity tain operation statements at the beginning of a
movement is initiated. Any logic defined after a conveyor are invalid including ACCUM, COM-
MOVE statement is processed when the entity BINE, CREATE, GROUP, SPLIT AS,
reaches the very end of the conveyor. UNGROUP, and UNLOAD.

Move time on a conveyor is based on the length The default conveyor length is determined by the
and speed of the conveyor, as well as the length graphic scale, although this may be overridden by
or width of the entity. The move time for an entering a different length. When a conveyor is
modified graphically, the length will automati-
 ProModel 99
User Guide

cally be recalculated based on the graphic scale How to create bends in an existing
unless you uncheck the “Recalculate path lengths conveyor:
when adjusted” option. You can access this
option from the Tools menu under Options.
1. Click on the conveyor with the right mouse button.
From the menu that appears, select Add Joint. A small
Conveyor Graphics Display black square appears on the conveyor.
When you use conveyors and want the graphics 2. Using the left mouse button, drag the square in the
to display properly on the conveyor with no over- direction you desire to bend.
lapping and little space between entities, use the
following:

Entity Conveyor Options Dialog Box

Orientation
on Conveyor Requirements The conveyor options dialog box is used to define
Width-wise 1. Entity width on conveyor the specifications for a conveyor. To access the
should equal horizontal dimen- conveyor options dialog box, you may double
sion. click on a conveyor, select the conveyor and click
2. Entity length on conveyor on the Edit button from the Location Graphics
should equal vertical dimension. window, or right-click on the conveyor and select
Length-wise 1. Entity width on conveyor edit. This opens the Conveyor/Queue dialog box
should equal vertical dimension. from which the Conveyor Options dialog box can
2. Entity length on conveyor be opened by clicking on the Conveyor Options
should equal horizontal dimen- button. The Conveyor Options dialog box pre-
sion. sents the following options:

Conveyor Animation
The animation of entities traveling along convey-
ors is displayed according to the logical length or
width of the entity, not the scaled length or width
of the entity graphic.

How to define a conveyor graphically:

Accumulating Select or deselect this option
1. Select the conveyor/queue symbol from the Loca- depending on whether the conveyor is to be accu-
tion Graphics window. mulating or non-accumulating.
2. Click on the Layout window with the left mouse Entity Orientation Select Lengthwise or Width-
button where the conveyor should start. wise depending on whether the entity is traveling
3. Add bends to the conveyor by moving the mouse on the conveyor in the direction of the entity
and clicking the left mouse button. length or in the direction of the width.
4. Move the mouse in the desired direction and click Length The length of the conveyor expressed in
on the right mouse button to end the conveyor. either feet or meters depending on the default
specified in the General Information dialog.
100 Chapter 5:
Locations

Speed The speed of the conveyor in feet or There are three possibilities for defining the
meters per minute. The distance units can be set machines: (1) as a multi-capacity location, (2) as
in the General Information dialog box. a multi-unit location, or (3) as multiple locations.
The method you choose to define the locations
depends on your application.
Capacities and Units

Capacities
A location capacity is the maximum number of
entities it can hold at any one time. In general,
multi-capacity locations are used to model loca-
tions such as queues, waiting areas, or any other
type of location where multiple entities may be
held or processed concurrently. Consider the fol-
lowing multi-capacity location:

For many situations modeling parallel stations as

a multi-capacity location works fine. By placing
an additional graphic for each station, both the
Units logic and visual effects of having parallel stations
can be achieved. However, you should use a
A location unit is defined as an independently
multi-unit location instead of a multi-capacity
operating station. When multiple, independently
location when any of the following situations
operating stations all perform the same operation
exist:
and are interchangeable, they form a multi-unit
location. Consider the following multi-unit loca- • Individual units have independent down-
tion: times.
• It is important to collect individual statistics
on each unit.
• It is important, for visual effect, to see enti-
ties select individual units by a routing
rule other than First Available (e.g., By
Turn, Fewest Entries, Longest Empty,
Multi-Capacity, Multi-Unit, and etc.).
Multiple Locations • It is important, for visual effect, to have a
Sometimes it can be unclear whether to use status light assigned to each unit.
multi-capacity, multi-unit, or multiple locations In some situations, it may even be desirable to
when defining parallel workstations. Suppose, for model multi-unit locations as totally separate
example, we have three parallel stations, each locations. Multiple locations should be used
performing the same operation as shown below. instead of multi-unit locations when:
 ProModel 101
User Guide

• A path network is defined but each location Selecting Incoming Entities option in the Rules
must interface with a different node on the dialog box. (See the discussion regarding the
network. Rules dialog box later in this section.)
• Different units have different processing
In the output report, scheduled hours for the par-
times.
ent location will be the sum of the scheduled
• The input for each unit comes from different hours for the individual units.
sources.
• The routing is different for each unit.
Please note
Defining a Multi-Unit Location
Multi-Unit notes:
To create a multi-unit location, enter a number
greater than one as the number of units for a loca- 1. It is not possible to create a path network to
tion. A corresponding number of locations will interface with each unit of a multi-unit location.
be copied below the multi-unit location record in You must define the locations individually and
the Location edit table, each with a numeric use multiple locations as discussed above.
extension designating the unit number of that
2. It is not possible to route an entity to a spe-
location. Successive graphics, representing indi-
cific unit of a multi-unit location. For example,
vidual units will be drawn to the right of the orig-
typing Loc2.3 in the destination field of the Rout-
inal location, but may be moved normally.
ing edit table is not allowed.
The original location record becomes the proto-
type for the unit records. Each unit will have the
prototype's characteristics unless the individual
unit's characteristics are changed. In the table Location Downtimes
below, each unit of the location has a clock-based
downtime defined because the parent location, A downtime stops a location or resource from
Loc2, was assigned a clock-based downtime. operating. A down resource or location no longer
However, Loc2.1 has an additional entry-based functions and is not available for use. Downtimes
downtime and Loc2.2 has an additional usage- may represent scheduled interruptions such as
based downtime. Any other characteristic, shifts, breaks, or scheduled maintenance. Or, they
including the icon, can be changed as if the unit may represent unscheduled, random interruptions
were an independent location. such as equipment failures. Downtimes may also
be given preemptive or non-preemptive priority
and may require one or more resources for repair
times.
For single capacity locations, downtimes may be
based on clock time, usage time, number of enti-
If the number of units is changed, the individual ties processed,a change in entity type, or called
unit location records are automatically created or using the DOWN statement. Multi-capacity loca-
destroyed accordingly. tions have only clock and called downtimes. If a
downtime is occurring at a location and any other
Individual units of a multi-unit location can be
downtime starts (except a setup downtime), the
selected to process an entity according to the
102 Chapter 5:
Locations

two downtimes are processed together, not see if the specific statement or function is valid in
sequentially (i.e., downtimes overlap). a particular field.)

How to specify a location downtime:

1. Select the desired location in the edit table.

2. Click on the DTs... button. This brings up the down- Frequency The time between successive down-
time selection menu shown here for single-capactiy time occurrences. This option may be an expres-
locaitons. (Multi-capacity locations will only have the sion. This field is evaluated as the simulation
Clock and Called options.) progresses, so the time between downtimes can
vary.
First Time The time of the first downtime occur-
rence. If this field is left blank, the first clock
downtime will occur according to the frequency
field. This time is evaluated after any initializa-
3. Each selection opens an edit table for specifying the tion logic.
required elements of the downtime.
Priority The priority (0-999) of the downtime
occurrence. The default priority is 99, the highest
Please note non-preemptive priority.

An alternative and more straightforward method Scheduled... Select YES if the downtime is to be
for defining downtimes due to breaks or shifts is counted as a scheduled downtime. Select NO if
to use the Shift Editor. The Shift Editor also has the downtime is to be counted as a non-scheduled
the advantage of allowing a downtime to be downtime.
defined for an entire group of locations. All scheduled downtimes will be deducted from
the total scheduled hours reported in the output
statistics and, therefore, will not be considered in
computing utilization, percent down, and so on.
Clock Downtime Editor
Logic Enter any logic statements to be processed
Clock downtimes are used to model downtimes when the downtime occurs. When the logic has
that occur depending on the elapsed simulation completed, the location becomes available. In the
time, such as when a downtime occurs every few most simple case, the logic is simply a WAIT
hours, no matter how many entities a location has statement with a time value or expression which
processed. represents the duration of the downtime. Click on
The Clock Downtime Editor consists of the edit the heading button to open a larger edit window.
table shown below. To access the Clock Down- Disable Select YES to temporarily disable the
time Editor, select Clock from the menu that downtime without deleting it from the table.
appears after clicking the DT... heading button.
Most expressions, including distributions, can be The example above shows a simple clock-based
included in the Frequency, First Time, and Prior- downtime where the location is down for 10 min-
ity fields. (See the “Appendix A” on page 577 to utes every 2 hours (120 min). Because this time
 ProModel 103
User Guide

should not be included in the total scheduled or time expression representing the length of the
available hours, YES is selected in the “Sched- downtime. Click on the heading button to open a
uled” column. larger edit window.
Disable Select YES to temporarily disable the
Entry Downtime Editor downtime without deleting it from the table.
Entry downtimes are used to model downtimes In the example above, Robot1 will go down
when a location needs to be serviced after pro- every 100 entries, with the first downtime occur-
cessing a certain number of entities. For example, ring after only 50 entries. When the downtime
if a printer needs a new cartridge after printing occurs, it will require a resource (M1) to service
2000 shipping orders, an entity downtime should the machine for some amount of time between
be defined. The downtime occurs after the entity 3.8 and 4.2 minutes. If resource M1 is unavail-
that triggered the downtime leaves the location. able when requested, the robot will remain down
The Entry Downtime Editor consists of the edit until M1 becomes available.
table shown below. To access the Entry Down-
time editor, select Entry from the menu that Please note
appears after clicking the DT... heading button.
Entry downtimes are only available for single Entry-based downtimes do not accumulate. For
capacity locations. The Downtime Editor con- example, if a downtime cannot occur because the
tains fields for defining downtimes based on the priorities of the entities being processed are at
number of entries processed at a location. Most least 2 levels higher than the priority of the
functions, including distributions, can be downtime, only the first downtime resumes after
included in the Frequency and First Occurrence processing the entities. All others are ignored.
fields. (See the “Appendix A” on page 577 to see
if the specific statement or function is valid in a
particular field.)
Usage Downtime Editor
Usage downtimes are used to model downtimes
that occur after a location has been operating for
a certain amount of time, such as if a machine
Frequency The number of entities to be pro- fails due to wear after so many hours of opera-
cessed between downtime occurrences. This may tion. Usage downtimes are different from clock
be a constant value or a numeric expression and downtimes because usage downtimes are based
is evaluated as the simulation progresses. on location operation time, which does not
include blocked time. Clock downtimes are based
First Occurrence The number of entities to be
on total elapsed simulation time (operation time,
processed before the first downtime. This may be
blocked time, idle time). Usage downtimes are
a value or a numeric expression. If left blank, the
available only for single-capacity locations.
first downtime will be based on the frequency
entered. The Usage Downtime Editor consists of the edit
table shown below. It contains fields for defining
Logic Any logic statements to execute when the
location downtimes based on the actual time in
downtime occurs. Normally, this logic is simply a
use. Most functions, including distributions can
104 Chapter 5:
Locations

be included in the Frequency, First Time, and Pri- downtime, only the first downtime resumes after
ority fields. (See the “Appendix A” on page 577 processing the entities. All others are ignored.
to see if a specific function is valid in a particular
field.)

Setup Downtime Editor

Setup downtimes should be used to model situa-
tions where a location can process different types
Frequency The usage time between downtimes. of entities, but needs to be setup to do so. Setup
downtimes will not overlap but will preempt
First Time The time in use before the first down- other downtimes in a manner similar to that of an
time occurrence. Leave blank if the first time is to entity. Setup downtimes are only available for
be based upon the frequency entered. single capacity locations.
Priority The priority, between 0 and 999 of the Note that a setup downtime is assumed to occur
downtime. The default priority is 99, which is the only when an entity arrives at a location and is
highest non-preemptive priority. Generally, usage different from the previous entity to arrive at the
downtimes tend to be preemptive and should location. Consequently, the word ALL in the
have priority values greater than 100. prior entity field means all except the same entity
Logic Any logic statements to be processed type.
when the downtime occurs. Typically, this field The Setup Downtime Editor consists of the edit
contains a time expression representing the table shown below. It contains fields for defining
length of the downtime. Click on the heading but- location downtimes based on the arrival of a new
ton to open a larger edit window. entity type.
Disable Select YES to temporarily disable the
downtime without deleting it from the table.
In this example, Robot2 will experience break-
downs according to a Gamma distribution with
shape and scale parameters 1.7 and 2.3. Mainte-
nance resource M1 will be used to service the Entity The incoming entity for which the setup
robot. The repair time is normally distributed occurs. If the setup time for all entity types is
with a mean of 2.4 minutes and a standard devia- identical when shifting from the same prior
tion of .3 minutes. entity, the reserved word ALL may be entered.
Prior Entity The entity preceding the entity for
Please note which the setup occurs. If the setup is the same
regardless of the preceding entity, you may enter
Usage-based downtimes do not accumulate. For the reserved word ALL.
example, if a downtime cannot occur because the
priorities of the entities being processed are at Logic Enter any logic statements to be processed
least 2 levels higher than the priority of the when the downtime occurs. Click on the heading
button to open a larger edit window.
 ProModel 105
User Guide

Disable Select YES to temporarily disable the Logic Enter any logic statements to be pro-
downtime without deleting it from the table. cessed when the downtime occurs. When the
logic has completed, the location becomes avail-
This example shows that the time to setup Robot3
able. In the most simple case, the logic is simply
depends on the arriving entity and the prior
a WAIT statement with a time value or expres-
entity. If a GearB follows a GearC, the setup time
sion which represents the duration of the down-
for the machine will be based on a Lognormal
time. Click on the heading button to open a larger
distribution with a mean of 4.5 minutes and a
edit window.
standard deviation of .95 min. But if a GearC fol-
lows a GearA, the setup time will be based on a For more information on the DOWN statement,
Lognormal distribution with a mean of 2.3 min see “Down” on page 460.
and a standard deviation of .2 min.
Location Priorities and Preemption
Called Downtime Editor Priorities determine which entity or downtime
Called downtimes are used in conjunction with uses a location when more than one entity or
the DOWN statement to make a location go downtime is contending for it. Priorities may be
down. When the name of the called downtime is any value or expression between 0 and 999, with
referenced during simulation by the DOWN higher values having higher priority. For simple
statement, the called downtime will execute its prioritizing, you should use priorities from 0 to
logic. 99. Priorities greater than 99 are used for pre-
empting (bumping or displacing) entities or
downtimes currently occupying a location.
Priority values are divided into ten levels (0 to
99, 100 to 199, ..., 900 to 999), with values
beyond 99 used for preempting entities or down-
times of a lower priority level. Multiple preemp-
Name The name of the called downtime. This is
tive levels make it possible to preempt entities or
the name that will be referenced by the DOWN
downtimes that are themselves preemptive. This
statement.
means that an entity, EntA, with a priority of 99
Priority The priority (0-999) of the downtime can be preempted by another entity, EntB, with a
occurrence. The default priority is 99, the highest higher priority level of 199. In turn, another
non-preemptive priority. entity, EntC, with a priority of 299 can preempt
EntB at the same location.
Scheduled... Select YES if the downtime is to be
counted as a scheduled downtime. Select NO if To preempt an entity currently using a location, a
the downtime is to be counted as a non-scheduled preempting entity or downtime must have a prior-
downtime. ity at least ONE level higher than the entity cur-
rently at the location. To preempt a downtime in
All scheduled downtimes will be deducted from
effect at a location, a preempting entity must have
the total scheduled hours reported in the output
a priority at least TWO levels higher than the cur-
statistics and, therefore, will not be considered in
rent downtime. Since all overlapping location
computing utilization, percent down, and so on.
downtimes are processed concurrently (except
106 Chapter 5:
Locations

setup downtimes), a downtime cannot, in effect, Assigning Priorities

preempt another downtime.
An entity or downtime accesses a location based
A preempted entity will resume processing where on its priority. An entity is assigned a priority for
it left off unless the location was in the middle of accessing a location in the Destination column of
a setup downtime. If the entity initiated a setup the Routing edit table. A downtime is assigned a
downtime before being preempted, it will begin priority in the appropriate Downtime edit table.
processing the setup logic from the beginning The first of the following examples shows a pri-
when it resumes. ority of 100 assigned to EntA as it tries to claim
Loc2. This priority is high enough to preempt any
entity at the location having a priority less than
100. It is not high enough, however, to preempt
any downtimes at the location.

Process Table
Entity Location Operation (min)
EntA Loc1 USE Res1 FOR N(3,.1)

Routing Table
Blk Output Destination Rule Move Logic
1 EntA Loc2, 100 First 1 MOVE FOR 1

This example shows a priority of 200 assigned to

a usage-based downtime at Loc4. This priority
can preempt any entity at the location with a pri-
ority less than 200.

The following table shows the minimum priority

level requirements for an incoming entity or an
upcoming downtime to preempt the current entity
or downtime at the location.
 ProModel 107
User Guide

Minimum Required Priority Levels for Pre- Example 1

empting at a Location The following example demonstrates what hap-
pens when Ent 1 with a priority of 99 is pre-
To preempt the
To preempt the Current empted by Ent 2 which has a priority of 100 or
Current Entity downtime greater.
Incoming 1 priority level 2 priority levels
higher higher
Entity Preempting an Entity
Entity
Upcoming 1 priority level Downtimes over-
Downtime higher lap Ent 1

• The upper left quadrant shows that for an

entity to gain access to a location already
processing another entity, the incoming
entity must have a priority at least one Ent 2
level higher than the current entity's prior- Time
ity.
• The upper right quadrant shows that for an T2 T3 T4
T1
incoming entity to gain access to a loca-
tion where a downtime is currently in Ent 1 processing resumes upon
effect, the entity must have a priority at completion of Ent 2 processing
least two levels higher than the downtime's
priority.
• The lower left quadrant shows that a for a Example 2
downtime to preempt an entity currently This example demonstrates what happens when a
processing, the downtime must have a pri- downtime having a priority of 99 is preempted by
ority one level higher than the currently an entity having a priority of 200 or greater.
processing entity.
• The lower right quadrant shows that all loca- Entity Preempting a Downtime
tion downtimes (except setup) are concur-
rent or overlapping. Setup downtimes
DT
preempt as if they were entities.
The following examples demonstrate the expla-
nations above in greater detail.

Entity
Time

T2 T3 T4
T1

Downtime resumes immediately upon

completion of entity processing
108 Chapter 5:
Locations

Example 3 Example 5
This example demonstrates the behavior when an This example demonstrates what happens when a
entity with a priority of 99 is preempted by a setup downtime with a priority of 99 is pre-
downtime with a priority value of 100 or greater. empted by a normal downtime having a priority
of 100 or greater.
Downtime Preempting an Entity
Downtime Preempting Entity in Setup
Entity

Entity setup

DT Time

DT
Time
T2 T3 T4
T1
T1 T2 T3 T4
Remaining entity processing time
resumes upon completion of downtime
Remaining setup time resumes upon
completion of downtime
Example 4
This example illustrates how, regardless of the Example 6
downtime priority values, downtimes will over- This example demonstrates what happens when
lap. The exception is setup downtimes, which Ent 1 setup downtime with a priority of 99 is pre-
preempt downtimes exactly like entities (see empted by Ent 2 having a priority of 100 or
Example 5). greater.
Overlapped/Concurrent Downtimes Entity Preempting Entity in Setup
DT 1 Ent 1 setup Ent 1 setup

DT 2

Overlap Ent 2

Time
Time

T1 T2 T3 T4
T1 T2 T3 T4
Total Downtime Ent 1 setup must start over upon completion
of Ent 2 processing
 ProModel 109
User Guide

Special Notes Regarding Location Downtime inhibiting statements

Downtimes
1. When an entity preempts another entity WAIT UNTIL
(Example 1), or when an entity preempts a ACCUM
downtime (Example 2), or when a downtime COMBINE
preempts an entity (Example 3), any
resources owned by the preempted entity or MATCH
downtime will be freed temporarily until the GROUP
preempting entity or downtime finishes at JOIN
the location. At that time, the original entity
or downtime will seek to claim the exact LOAD
units of the resource or resources it owned
before the preemption occurred.
2. As shown in examples 5 and 6, an entity that 5. In cases where a downtime or other entity
requires a location setup will be treated dif- attempts to preempt an entity’s use of a loca-
ferently depending on the preempting activ- tion, a preemption process may be defined to
ity. If the preempting activity is another override the default way of handling the pre-
entity, the current setup in process will have
emption. See “Preemption Process Logic” on
to start over from the beginning. However, if
page 292.
the preempting activity is a downtime, the
remaining setup time will finish upon com-
pletion of the preempting downtime. Rules Dialog Box
3. Locations will not go down if they are in a
blocked state. A location is blocked if it has The Rules dialog box, selected by clicking on the
an entity that cannot be routed because of the Rules button in the Locations edit table, is used to
unavailability of the next location. This may choose the rule for ProModel to follow when
also include the time an entity waits to enter making the following decisions:
a location based on a routing condition, such • Selecting incoming entities
as LOAD. • Queuing for output
4. Locations will not go down if any of the • Selecting a unit
occupying entities are waiting for a resource
or are waiting at any downtime inhibiting
statement.
110 Chapter 5:
Locations

Selecting Incoming Entities have departed. A decision must be made to allow

the entity to leave or to wait according to some
When a location becomes available and there is queuing rule. If one of the following queuing
more than one entity waiting to enter, a decision rules is not specified, “No Queuing” will be used.
must be made regarding which one to admit. The
primary determining factor is the priority of the No Queuing Entities that have completed their
input routing. The entity with the highest routing operations at the current location are free to route
priority will be admitted regardless of the incom- to other locations independent of other entities
ing selection rule. However, if two or more enti- that have finished their operations. If this option
ties have the same priority for claiming the is selected it is not displayed in the Rules Box.
location, then the location selects an incoming
First In, First Out (FIFO) The first entity com-
entity based on the incoming selection rules listed
pleting operation must leave for its next location
below.
before the second entity completing its operation
Oldest by Priority Selects the entity waiting the can leave, and so on.
longest among those having the highest routing
Last In, First Out (LIFO) Entities that have fin-
priority.
ished operations queue for output LIFO so the
Random Selects randomly with equal probability last one finished is the first to leave.
among all waiting entities.
By Type Entities that have finished operations
Least Available Capacity Selects the entity com- queue for output FIFO by entity type so the rout-
ing from the location having the least available ing for each entity type is processed indepen-
capacity. Ties are broken by the entity waiting the dently of routings for all other types.
longest.
Highest Attribute Value Entities that have com-
Last Selected Location Selects the entity coming pleted operations queue for output according to
from the location that was selected last. Ties are the highest value of a specified attribute.
broken by the entity waiting the longest. If no
Lowest Attribute Value Entities that have com-
entities are waiting at the last selected location,
pleted operations queue for output according to
the Oldest by Priority rule takes effect.
the lowest value of a specified attribute.
Highest Attribute Value Selects the entity with
the highest attribute value for a specified Selecting a Unit
attribute. Ties are broken by the entity that has
been waiting the longest. Location attributes are If the location has multiple units, then incoming
also valid entries. entities must select which available unit to use.
One of the following rules may be selected.
Lowest Attribute Value Selects the entity which These decision rules apply to multi-unit locations
has the lowest attribute value for a specified only.
attribute. Ties are broken by the entity waiting the
longest. Location attributes are also valid entries. First Available Selects the first available unit.

By Turn Rotates the selection among the avail-

Queuing For Output able units.
When an entity finishes its operation at a loca-
tion, other entities to finish ahead of it may not
 ProModel 111
User Guide

Most Available Capacity Selects the unit having Two parts are queued for output at Loc1. The part
the most available capacity. This rule has no waiting the longest, EntA, at Loc1 has been wait-
effect with single capacity units. ing 10 minutes. The other part, EntB, which
queued for output after EntA, has been waiting 5
Fewest Entries Selects an available unit with the
minutes. At Loc2, the part queued for output,
fewest entries.
EntC, has been waiting 7 minutes. At Loc3, the
Random Selects an available unit randomly. part queued for output that has been waiting the
longest, EntD, has waited 3 minutes.
Longest Empty Selects the unit that has been
empty the longest. The part to enter Loc4 first is EntC at Loc2 which
waited 7 minutes. Even though EntA has been
When specifying the decision rules for selecting
waiting ten minutes, it must wait until EntB has
incoming entities at a location, it is important to
been routed, because EntB is ahead of it in the
remember that the routing of an entity is also
output queue according to the LIFO queuing rule.
dependent on the queuing for output decision
Once Loc4 finishes processing EntC, EntB at
rules at the previous location. The following
Loc1 enters Loc4. EntB enters before EntA
example will clarify this principle.
because entities must be output before a destina-
tion selects incoming entities. Next, EntA at Loc1
Rules Dialog Box Example enters Loc4 after which EntD at Loc3 enters
Consider a location, Loc1, which has a “Last In, Loc4.
First Out (LIFO)” as the queuing for output rule.
Suppose that two other locations, Loc2 and Loc3,
have “No Queuing” for the output rule. The three
locations, Loc1, Loc2, and Loc3 feed into Loc4
which has an “Oldest by Priority” rule for select-
ing incoming entities.
112 Chapter 5:
Entities

Entities Entities may also have user-assigned attributes to

represent such things as dimensions, weights,
Anything that a model processes is called an pass/fail status, and group identifiers.
“Entity.” Documents, people, or phone calls
should be modeled as entities. Entities may be
grouped, such as when several boxes are stacked
on a pallet (through the GROUP statement); con-
solidated into a single entity, such as when two or
more documents are joined together (through the
JOIN statement); split into two or more entities,
such as when a box is opened and the contents
removed (through the SPLIT AS statement); or
converted to one or more new entities (through
the RENAME or CREATE statement or by defin-
ing multiple outputs in the routing).
Each entity type has a name and a name index
number. In logic and expressions, an entity can be
referred to by name or by its name-index number
using the ENT() function. The ENT() function
allows a statement requiring an entity name to
use an expression that may change to reference
different entity names as a simulation progresses. How to access the entities editor:
See “Ent()” on page 466 for more information.
• Select Entities from the Build menu.

or...

• Right click on the existing entity and select Edit.

Entities Editor
Entity types are created and edited with the Enti-
ties Editor. The Entities Editor consists of (1) an
edit table to define the name and specifications of
each entity type in the system, and (2) the Entity
Graphics window for selecting one or more icons
 ProModel 113
User Guide

to represent each entity. The fields of the edit How to define entities graphically:
table are explained below.
1. Select Entities from the Build menu.
2. Check the New box in the Entity Graphics window.
3. Select an icon for the entity. (Use the Graphic Editor
to create new icons.)
Icon This is the graphic icon used to represent 4. Edit the name and other default entries for the entity
the entity during the animation. Entity graphics in the Entity edit table.
are defined or modified using the Entity Graphics
window. This icon can vary during the simula-
tion. See “Defining Multiple Entity Graphics” on
page 114.
Name The entity name. See “Names” on
page 394 for more information on naming.
Speed This entry is optional and applies to self-
moving entities such as humans. It defines the
speed in feet or meters (depending on the dis-
tance units chosen in the General Information
Dialog box) per minute to be used for any of the
entity's movement along a path network. When
creating a new entity, a default value of 150 fpm
(or 50 mpm for metric systems) is automatically
entered. This is roughly the speed of a human
walking.
Stats The level of statistical detail to collect for
each entity type: None, Basic, or Time Series.
Time series statistics must be selected if you wish
to view a time series plot in the output module.
Notes Any information you wish to enter about
the entity, such as material, supplier name.

Defining Entities Entity Graphic Dimensions

Entities are typically defined graphically by An entity has two sets of dimensions, a logical
clicking on a desired library graphic in the Entity (length and width) dimension, and a graphical
Graphics window. Alternatively, you may define (horizontal and vertical) dimension. An entity's
entities by simply entering their names and char- length and width are used to determine the num-
acteristics in the Entity edit table. Entity graphics ber of entities that can fit on a conveyor, and do
are optional. not affect the size of the graphic on the screen
during a simulation. They are changed in the
114 Chapter 5:
Entities

fields labeled Length and Width in the Entity changes automatically to maintain proportional-
Graphics window. If multiple graphics are ity.
defined for an entity, each graphic can have a dif-
ferent length and width. Which side a user
chooses to call the length or width is unimportant
as long as the proper side is referenced when Defining Multiple Entity Graph-
defining a conveyor. If no conveyors are defined
in the model, no specifications of a length and
ics
width are necessary. Entity types can be assigned more than one
An entity's horizontal and vertical dimensions are graphic to represent the entity at various stages of
used to determine the size of the graphic on the production or traveling in different directions. An
screen. These dimensions can be changed in two entity representing a loan application could be
ways. The scroll bar to the right of the graphic assigned three graphics: the first representing the
will scale the graphic. In addition, the horizontal application before a credit check has been
and vertical dimensions can be changed by click- received, the second representing the application
ing on the Edit button, then clicking on the after receiving the credit check but before the
Dimensions... button from the resulting dialog loan is approved, and the third representing the
box. The default dimensions are determined application after the loan is approved. During the
when an icon is created to scale in the Graphic simulation, the application’s status could be
Editor. If the size is changed using the scroll bar, shown by adding additional graphics to represent
the change will be reflected in the dimensions each state of the loan process using the
listed. If you change either the horizontal or verti- GRAPHIC statement (see “Graphic” on page 482
cal dimension from the dialog box, the size of the for information).
icon will change accordingly.

Please note

Since the horizontal and vertical dimensions must

remain proportional, only one of the dimensions
needs to be changed. The other dimension
 ProModel 115
User Guide

How to define multiple graphics for an ing an entity or a location that is down. An entity
entity type: with high enough priority can also take over a
resource when it is being used by another entity
or when it is off shift. When an entity takes over a
1. Uncheck the New box on the Entity Graphics win-
dow. Numbered graphic cells appear in the Entity location that was down or in use by another
Graphics window. entity, the entity has preempted the downtime or
the other entity.
In a multi-capacity location, the occupying entity
will be preempted only if there is no more capac-
ity at the location and the occupying entity is
undergoing an operation time. Further, the occu-
pying entity cannot be one that has been split,
created, grouped, combined, ungrouped, or
unloaded at the location.
An entity must have a priority one level higher
Multiple
than an occupying entity to preempt the occupy-
graphic
ing entity. An entity must have a priority that is
cells
two levels higher than a downtime to preempt the
downtime. If an entity does not have a high
enough priority to preempt another entity or
downtime at a location, it waits in line (oldest by
priority) to access the location (see “Location Pri-
2. Click on the desired cell. orities and Preemption” on page 105).
3. Select a library graphic from the graphics menu.
Note that the priority of an entity is not defined
4. Repeat steps two and three until all the desired for the entity itself. For claiming a location, it is
graphics have been assigned to the entity type. defined in the destination field of the routing. For
capturing a resource it is defined as part of the
GET, JOINTLY GET, or USE statement. A prior-
ity may, however, be assigned to an attribute of a
The graphic that represents an entity during a
referenced entity when it attempts to access a
simulation will be the first in this series until an
resource or location.
entity's graphic is changed with the GRAPHIC
statement.
Example of Preemptive Entities
Preemptive Entities In this example entity (EntA) arrives at location
Loc1. Immediately upon arrival it requests to use
Often during a simulation, it is desirable to have resource Res1 for a normally distributed amount
an entity preempt an activity at a location or of time. The priority for obtaining the resource is
resource in order to gain access to that location or 99, which means that it is a non-preemptive
resource. These situations can be modeled using request. When Res1 becomes available, EntA
preemptive priorities. An entity with a high will be first in line because it has the highest non-
enough priority can take over a location process- preemptive priority possible. When processing is
116 Chapter 5:
Entities

complete for this entity, it is routed to Loc2 with

priority 200. This means that it can preempt
another entity or a downtime that may already be
in process at Loc2. (See “Location Downtimes”
on page 101 and “Resource Downtimes” on
page 131 for more details on entity preemption.)

Process Table
Entity Location Operation (min)
EntA Loc1 Use Res1,99 For N(3,.1)

Routing Table
Blk Output Destination Rule Move Logic
1 EntA Loc2,200 First 1 MOVE FOR
2.5
 ProModel 117
User Guide

Path Networks Path Networks are defined in the Path Networks

Editor, which is accessed from the Build menu.
When resources are modeled as dynamic
resources which travel between locations, they
follow path networks. Entities moving by them-
selves between locations may also move on path
networks if referenced in the move logic of the
routing. Otherwise, they follow the routing path.
Multiple entities and resources may share a com-
mon path network. Movement along a path net-
work may be defined in terms of speed and
distance, or simply by time. See discussion on
Automatic Time and Distance Calculation, later
in this section, for more information about move-
ment according to speed and distance or by time.
There are three types of path networks: passing,
non-passing, and crane. A passing network is used
for open path movement where entities and
resources are free to overtake one another. Non-
passing networks consist of single-file tracks or
guide paths such as those used for AGVs where How to create or edit a path network:
vehicles are not able to pass. Crane path networks
are described in more detail in the section “Crane • Select Path Networks from the Build menu.
Systems” on page 261.
Passing and non-passing networks consist of or...
nodes, which are connected by path segments.
Path segments are defined by a beginning and an
ending node and may be uni-directional or bi- • Right click on the existing path network and select
directional. Multiple path segments, which may Edit.
be straight or jointed, may be connected at path
nodes. For all path networks, path nodes define
the points where the resources using the network
interface with processing locations. Path Networks Editor
The Path Networks Editor consists of an edit
table with fields for defining basic information
about each network, such as the network name,
the type of network (Non-Passing or Passing),
and the basis for movement along the network
(Speed and Distance or Time). Clicking on the
118 Chapter 5:
Path Networks

appropriate heading button will bring up a table The Path Segment edit table is covered in more
for defining nodes, path segments, and location detail later in this section.
node interfaces.
Interfaces The number of location-node inter-
faces in the path network. If an entity will be
picked up or dropped off at a particular location
by a resource, that location must connect to a
node through a location-node interface. Clicking
The following explains each field of the Path on the heading button opens the Interfaces edit
Networks edit table. table where the user may define nodes that con-
nect to processing locations. The Interfaces edit
Graphic For passing or non-passing path net-
table is covered in more detail later in this sec-
works, this button displays the Path Color dialog,
tion.
which allows you to define the color of the path
network. Click on the heading button or double Mapping The number of entries in the Mapping
click in this field to bring up the graphic dialog. edit table. Clicking on the heading button opens
Both dialogs allow you to specify whether or not the Mapping edit table where the user may map
the network will be visible at run time. destinations to particular branches of the net-
work. (The Mapping edit table is covered in more
Name A name that identifies the path network.
detail later in this section.)
For more information about valid names, see
“Names” on page 394. Nodes The number of nodes defined in the
Nodes edit table. Nodes are created automatically
Type Set this field to Non-Passing if you want
when graphically defining path segments. Click
entities and resources to queue behind one
on this heading button to open the Node edit
another on the path network. If a path is Non-
table, which may be used to define nodes manu-
Passing, entities may not pass each other, even if
ally or set Node Limits on one or more nodes.
an entity is traveling at a faster speed than the one
Nodes may also be used to control a resource's
in front of it. Set this field to Passing if you want
behavior through node logic or search routines
entities or resources to pass each other on the
such as work and park searches (see “Resources”
path network.
on page 126). The Nodes edit table is covered in
A "Crane" option is also available, which is more detail later in this section.
described in more detail in the section “Crane
Systems” on page 261. How to create a path network graphi-
T/S Set to either Time or Speed and Distance as cally:
the basis for measuring movement along the net-
work. See the discussion on Automatic Time and 1. Set the default time and distance values per grid unit
Distance Calculation later in this section for more from the Grid dialog box.
information. 2. Choose Path Networks... from the Build menu.
Paths The number of path segments in the net- 3. Enter the name of the network in the Path Networks
work. Clicking on the heading button opens the edit table.
Path Segment edit table where the user may
4. Select either Passing or Non-passing as the net-
define the network's node to node connections. work type.
 ProModel 119
User Guide

5. Select either Speed and Distance or Time as the To highlight a path on the layout and in the
travel basis. Path Segment edit table
6. Click on the Paths... heading button to open the • Left click on that path.
Path Segment edit table.
7. Lay out the network using the mouse buttons as
described below.
How to create additional nodes or
move existing nodes:

How to create path segments: 1. Click on the Nodes heading button in the Path Net-
works edit table.
1. Left click to create a node and begin a path segment. 2. Click the left mouse button to create a node both on
2. Additional left clicks produce path joints. the layout and in the Nodes edit table.

3. A right click ends the segment and creates a new 3. Drag an existing node to move that node.
node.

How to move a path network:

How to modify path segments:
1. Click on the Paths heading button in the Path Net-
works edit table.
To create a new path from an existing node 2. Left click on any path segment and drag to the
• Left click on that node. desired position. The entire network will move.

To delete a joint
• Right click on an existing joint. A Typical Path Network
The following diagram shows a path network
To add a joint consisting of seven nodes (N1 to N7) connected
1. Right-click anywhere on a path segment. by path segments. Path segments may be straight
lines from one node to another, as in the segment
2. Select Add Node from the menu.
from node N7 to node N6, or they can have any
3. Drag the joint to the desired position.

Please note

If you hold down the CTRL key and move the cur-
sor over a path segment or joint, the Add/Delete
joint cursor will appear. From here, left click to
add or delete a joint.
120 Chapter 5:
Path Networks

number of joints, such as the segment from node Time If travel along the network is to be mea-
N2 to node N5. sured in time rather than in speed and distance,
then enter the time required for a resource or
entity to traverse the path segment. This value
may be any numeric expression except for
resource and downtime system functions. When
travel along a path is measured in time, all
resources and entities traveling along the path
take the same amount of time to travel it, regard-
less of their speed. This field's title changes to
“Distance” if the T/S field in the Path Networks
edit table is set to Speed and Distance.
Distance If travel along the network is to be
measured in terms of speed and distance, enter
the length of the segment which determines the
travel time along the path in conjunction with the
Path Segment Edit Table speed of the resource or entity.
This table is used to define the Path Segments The value entered may be any numeric expres-
that make up a path network. When specifying sion except for attributes, arrays, and system
travel according to time between nodes, the head- functions. This expression is evaluated only
ing “Distance” changes automatically to “Time.” when the simulation begins.
The distance may be followed by a comma and a
speed factor between .01 and 99. This speed fac-
tor may be used to model any circumstance
affecting the speed of items traveling the path.
For example, a resource may normally travel at
150 fpm, but may slow down as it goes around a
corner to 80% of the original speed, 120 fpm.
This would be entered as 100, .8 for a path seg-
ment 100 feet long which traversed the corner.
This field's title changes to “Time” if the T/S
field in the Path Networks edit table is set to
Time.
The following defines the fields of the Path Seg-
ment edit table.
Please note
From The beginning node of the path segment.

To The ending node of the path segment. Path segment editing notes:
BI Set to Uni-directional or Bi-directional 1. If no path segments have been defined for a
depending on whether traffic can travel in only network, resources and entities will move from
one or either direction. node to node in zero time. See “Processing” on
 ProModel 121
User Guide

page 143 for more information about the Routing 4. Enter the time and distance values as shown below.
Move dialog box.
2. To move nodes already defined on the layout,
click on the Nodes button and move the desired
nodes.
3. To insure that all nodes can be seen by the user,
two nodes cannot be located at the same point.

Automatic Time and Distance

Calculation
The distance between two successive nodes or
the time required to traverse a segment between Please note
two successive nodes is calculated according to
the number of grid units between the nodes and To set these values as defaults, you must check
the default time and distance values per grid unit. the Save as Default Grid Settings option on the
ProModel automatically enters this time or dis- grid dialog box.
tance in the Time/Distance column of the Path
Segments edit table. Although the calculated time
or distance may be edited later, relying on the
automatic time and distance calculation feature Interfaces Edit Table
allows path networks to be built to scale and
saves time when defining path networks graphi- If an entity will be picked up or dropped off at a
cally. The time or distance for a path is automati- particular location by a resource, that location
cally recalculated whenever the path is edited must connect to a node through a location-node
(lengthened or shortened) unless you unchecked interface. The Interfaces edit table is used to
the “Recalculate path lengths when adjusted” box define location-node interfaces. The graphic
under Options in the Tools menu. below shows how to set node N1 to interface with
location Loc1, node N3 to interface with Loca-
How to set the default time and dis-
tance values per grid unit:

1. Select Layout Settings from the View menu.

2. Select the Grid Settings button.
3. Click on the Scale... button in the Grid dialog box.
122 Chapter 5:
Path Networks

tion Loc2, and so on, as in the example at the Mapping Edit Table
beginning of this section.
If there are multiple paths emanating from one
node to another node, the default path selection
will be based on the shortest distance for speed &
distance networks, and the least number of nodes
for time based networks. These defaults can be
overridden by explicitly mapping some destina-
tion nodes to specific branches that entities and
resources will take when traveling out of a
“from” node.

The fields of the Interfaces edit table are

described as follows.
Node The node name.

Location The name of any locations which inter-

face with the node. Nodes can interface with sev-
eral locations, but a location may interface with
only one node on the same path network.

How to create location-node interfaces

The fields of the Mapping edit table are described
1. Left click on the desired node to begin rubber-band- as follows.
ing a link or interface. From Entities and resources traveling out of this
2. Left click on the desired location to complete the node will use this mapping record to decide
interface. which of the alternate branches will be taken
next.
To The “from” node and the “to” node together
Please note define the branch to be taken next. This might
also be interpreted as the node which entities and
resources will go through, to reach one of the
A node on a path network may not interface with
destination nodes.
a particular unit of a multi-unit location (i.e.,
Loc1.2). A node may interface only with the Dest. Entities and resources whose ultimate des-
“parent” location (i.e., Loc1) of a multi-unit tination is one of these nodes will be forced to
location. take the branch that directly connects the “from”
node to the “to” node.
 ProModel 123
User Guide

Please note Please note

When your simulation is compiled and run, Pro- ProModel automatically calculates and uses the
Model will automatically define destinations for shortest paths on unmapped portions of networks
your network mapping, if you have not defined (if the network is time based, the path having the
them yourself. These computer-generated map- least number of nodes is used). Explicitly indicat-
pings will not appear in the Dest. column of the ing shortest paths using mapping constraints will
Mappings table, but the From and To columns speed up the translation process, especially for
will contain information on these mappings. Do models with complex networks.
not delete the information in these collumns.

An example of mapping two branches of a net-

How to create mappings using the work is given on the following pages.
mapping edit table:
Mapping Example
1. Click on the Mapping... heading button in the Path The following example uses a path network dia-
Network edit table. This will open the Mapping edit
gram to demonstrate mapping.
table.
2. Click on the From heading button and select the In this example, we wish to force resources and
node to be mapped. entities enroute from Loc1 to Loc4, Loc5, or
Loc6 to take the branch directly connecting node
3. Click on the To heading button and select the termi-
N2 and node N5 to avoid traffic congestion at the
nating node for the branch to be mapped.
intersection of the two main branches at node N3.
4. Click on the Destination heading button and select Since there are multiple ways to go from N2 to
the desired node(s). N5, a decision as to which alternative will be
used has to be made at N2.
In addition, we want resources and entities to fol-
How to create mappings graphically: low the same path in the opposite direction when
enroute from Loc4, Loc5, or Loc6 to Loc1. In
1. Click on the Mapping... heading button in the Path this case, the decision must be made at N5.
Network edit table. This will open the Mapping edit Because the combined length of segments con-
table.
necting N2 to N3 and N3 to N5 is shorter than the
2. Click on the from node in the Layout Window. This length of the single segment from N2 to N5,
places the selected node in the From field. resources and entities based on speed and dis-
3. Click on the to node in the Layout Window. Note tance will normally take the former path to travel.
that the to node must be directly connected to the from
node with a single branch.
4. Click on the destination node(s) in the Layout Win-
dow. This places the selected node(s) in the Destina-
tion field.
124 Chapter 5:
Path Networks

To force them to take the longer path, we must path network extended up to include many other
specify mapping constraints. nodes N8, N9, ..., and locations Loc7, Loc8, ...,
then we would change the Mapping edit table as
follows:
1. Delete line 1 in the Mapping edit table.
2. Make sure that line 3 is there (it is not
optional any more).
3. Include a line which reads: “From: N2, To:
N5, Dest:<BLANK>”.

This case requires two explicit mapping con-

straints to override the selection of default paths
in each direction: The first table entry forces enti-
ties and resources en-route from Loc1 to Loc4,
Loc5, or Loc6 to override the default path and
take the direct branch from N2 to N5. The second
table entry forces entities and resources traveling The empty destination column will be interpreted
from N5 (originally from Loc6, Loc5 or Loc4) to as “all other destination nodes” by ProModel.
Loc1 to take the direct branch from N5 to N2.
Entries 3 and 4 are optional, and might be useful
Please note
to speed up translation, since the restrictions they
impose allow the shortest path calculations to be
bypassed. For a “from” node (unless there is a branch map
with a blank destination column), any nodes not
explicitly listed in the destination columns of
existing mapping records will be reached via the
default path selections.

Nodes Edit Table

The Nodes edit table lists the nodes that make up
a path network and is used to limit the number of
resources and entities that may occupy a node at
any given time. In addition to controlling traffic
There is a shortcut to force the same non-default
on a path network, nodes also define where
path selection constraint to a number of destina-
resources interface with locations or where enti-
tion nodes: For instance, if the vertical arm of the
ties enter and leave the path network. Nodes may
 ProModel 125
User Guide

also be used solely to control a resource or errors. This saves compilation time on large mod-
entity's behavior through node logic or search els.
routines such as work and park searches (see
However, if you edit one or more of your path
“Resources” on page 126).
networks, ProModel will once again check the
modified path networks for errors during compi-
lation. ProModel will consider a path network to
have been modified if its name was at any time,
since the last compile, highlighted in the Path
Network dialog window.

The following defines the fields of the Nodes edit

table.
Name The node name.

Limit The maximum number of resources and

entities that may occupy a node at any given
moment. A blank entry means there is no limit.

Pre-translation check for Path

Networks
When you run your simulation, ProModel will
compile your model and check your path net-
works for errors. If your model has large, com-
plex path networks, this could cause your
model’s compilation time to run quite long.
To combat this, ProModel will perform a pre-
translation check for path networks. This means
that the first time your model compiles, it will
check your path networks for errors. It will then
save this information.
Every subsequent time your model compiles, it
will read the saved information about your path
networks and not check the path networks for
126 Chapter 5:
Resources

Resources How to create and edit resources:

A resource is a person, piece of equipment, or • Select Resources... from the Build menu.
some other device used for one or more of the
following functions: transporting entities, assist- or...
ing in performing operations on entities at loca-
tions, performing maintenance on locations, or • Right click on the existing location and select Edit.
performing maintenance on other resources.
Resources consist of one or more units with com-
mon characteristics, such as a pool of service
technicians or a fleet of lift trucks. Resources
Typical Use of Resources
may be dynamic, meaning that they move along a The diagram below shows two types of
path network, or static, in which no movement resources: forklifts and an operator. Forklifts are
occurs. Resources may also have downtimes. used as resources to transport entities from Loc1
Every resource has a name and a name-index to any of the processing locations, Loc2 through
number. Logic referring to a resource, such as the Loc6. The forklifts are dynamic resources and
GET statement, can use either the resource's travel along the path network, Net1, explained
name, or the RES() function to refer to the previously in “Path Networks” on page 117. The
resource. The RES() function allows a statement operator inspects all parts at Loc7 and never
using a resource name to refer to different moves from that location. Therefore, the operator
resources as a simulation progresses. See “Name- is a static resource and does not need a path net-
Index Numbers” on page 396 and “Res()” on work.
page 533 for more information.
Resources are defined in the Resources Editor,
accessed through the Build menu.

The remainder of this section defines the ele-

ments and the procedures necessary for specify-
ing static and dynamic resources.

Resources Editor
The Resources Editor consists of the Resources
edit table and the Resource Graphics window.
 ProModel 127
User Guide

These windows are used together to specify the Icon The icon selected for this resource. Icons
characteristics of a resource. are selected using the Resource Graphics Win-
dow. If more than one icon is selected for the
resource, the first icon is shown here.
Name The name of the resource.
Units The number of units represented by this
resource name between 0 and 999 (or a macro). If
the entry is a numeric expression, the expression
will be evaluated at the start of the simulation
run. Consequently, the number of resource units
cannot be changed during the simulation run. If
you would like to vary the number of units of a
resource during runtime, use downtimes to vary
the number of resources available at a given time.
(See also “Resource Downtimes” on page 131.)
Resources edit table Appears along the top of the
workspace with fields for specifying the name of
each resource, the number of identical units of a Please note
resource, the downtime characteristics of each
resource, and other important information, such When you use a macro with a value of zero in the
as the path network the resource uses for move- units field, you can use SimRunner to find the
ment. optimal number of resources needed for your
model.
Resource Graphics window Contains graphic
icons that may be selected to represent a resource
during simulation. A resource may have more
than one icon to represent different views of the
DTs... Select this field to define any optional
resource, or its status. This window also allows
downtimes for this resource. Only clock and
you to define multi-unit resources graphically on
usage based downtimes are permitted for
the layout. Defining a resource is as simple as
resources.
selecting an icon from the Resource Graphics
window, giving the resource a name, and specify- Stats... The desired statistics, if any, to gather for
ing the characteristics of the resource. this resource. Statistics can be collected as a sum-
mary report over all units of a resource, or indi-
Resources Edit Table vidually for each unit of a resource. The options
are as follows:
The Resources edit table defines the characteris-
tics of each resource in the system. The fields of • None: No statistics are gathered.
this table are defined below. • Summary: Average utilization and activity
times are recorded collectively for all units
of the resource.
• By Unit: Statistics are gathered for each
unit individually as well as collectively.
128 Chapter 5:
Resources

Specs... Select this field to open the Resource ing on the desired cell and selecting a library
Specifications dialog box. From here you can graphic from the graphics menu.
assign a path network, set the resource speed, and
By using the GRAPHIC statement in resource
define pickup and deposit times. For more infor-
downtime logic, or in the case of a dynamic
mation on the Specification dialog, see
resource, node logic, any of the multiple graphics
“Resource Specifications Dialog Box” on
assigned to a resource may be activated during
page 136.
simulation. For static resources, you may define a
Search... If a path network has been assigned, second or third graphic to be used automatically
select this field to access the Work Search and when the resource is busy or down, respectively.
Park Search edit tables, used to define optional
Resource graphics may be sized using the scroll
work and park searches.
bar or edited by clicking the edit button. Edit
Logic... If a path network has been assigned, options include rotating, flipping horizontally or
select this field to define any optional logic to be vertically, and changing the color of the graphic.
executed whenever a resource enters or leaves a In addition, you can specify the dimensions of the
particular path node. If you have defined a node resource graphic. For more information, see
entry and exit logic, the logic field will show the “Dimension” on page 310.
number of nodes where node entry and exit logic
has been defined.
Pts... If a path network has been assigned, select
this field to define resource points. Resource
points are auxiliary points where multiple
resources may appear graphically when parked or
in use at a multi-capacity node.
Notes... Enter any notes in this field, or click on
the heading button to open a larger Notes window
for entering notes.

Resource Graphics Window

The Resource Graphics Window appears when
the Resources module is opened and is used to
assign graphic symbols to resources. If the New
box is checked in the window, selecting a graphic
creates a new resource. Multiple graphics are
defined for a given resource by selecting the
desired resource and unchecking New. This pro-
cedure causes a scrollable row of graphic cells to
appear which are automatically and sequentially The Layout Position allows you to add or delete
numbered beginning with 1. Graphics may be resource graphics on the layout. When adding a
added or replaced for a given resource by click- resource graphic to the layout, ProModel auto-
matically adds a unit and a resource point. When
deleting a resource graphic from the layout, Pro-
 ProModel 129
User Guide

Model deletes the resource point but leaves the 1. When defining the static resource specifica-
number of units in the units field unchanged. tions, the default for Resource Search is Least
Utilized. The default for Entity Search is Longest
Waiting. You may only specify Pick-up and
Static Resources Deposit Time in the Motion box.
Static resources are resources not assigned to a 2. There is not a status light for a static resource;
path network and therefore do not visibly move. however, a second and third graphic may be
A static resource may be needed to perform an defined for use when the resource is busy or
operation at only one location, such as an inspec- down, respectively. If no second and third
tion operator, and will appear during the entire graphic are defined, the resource graphic
simulation in the same place it was defined changes color to green when in use and red when
graphically. Although a static resource is station- down.
ary and does not visibly move between locations,
it may be used at more than one location or to
move entities between locations.
Dynamic Resources
How to define a static resource:
Dynamic resources are resources that move along
1. Select Resources from the Build menu. This auto-
an assigned path network and may transport enti-
matically brings up the Resources edit table and the ties between locations as a forklift would. They
Resource Graphics window, used together to define all may also need to process entities at several loca-
resources in the model. tions, such as an operator performing tasks at
more than one location. For these reasons, it is
2. Choose a graphic icon for the resource from the
Resource Graphics window.
usually preferable to model the resource's move-
ment using a path network. Defined properly, the
3. Select the Add button in the Resource Graphics resource will travel along the path network dur-
window. ing the simulation run.
4. Click on the layout at the desired position of the
resource graphic. How to create a dynamic resource:
5. Add additional resource graphics for the same
resource if desired. Every time a resource graphic is 1. Create a path network using the Path Network Edi-
placed on the layout for the same resource in the edit tor.
table, a new resource point is created.
2. Select Resources from the Build menu. This auto-
6. Supply any optional information about the resource, matically brings up the Resources edit table and the
such as downtimes. Resource Graphics window, which are used together to
define all resources in the model.
3. Choose a graphic icon for the resource from the
Resource Graphics window.
Please note
4. Click the Specs... button to open the Specifications
Static resources notes: Dialog.
5. Assign a path network to the resource.
130 Chapter 5:
Resources

6. If desired, place units of the resource on the layout How to assign multiple graphics to a
by selecting the Add button in the Resource Graphics
resource:
window and clicking on the layout. Every time you
create and place a resource graphic on the layout for
the same resource in the edit table, ProModel creates a 1. Select Resources from the Build menu.
new resource point. See “Resource Points” on 2. Highlight the desired resource in the Resources edit
page 141 for more information. table.
7. Supply any optional information about the resource 3. Uncheck the New box in the Resource Graphics
including number of units, downtimes, work and/or window.
park searches, and node logic in the Resources edit
table. 4. Click on the next blank resource graphic cell in the
Resource Graphics window.
5. Select the desired resource icon.
6. Change the color, rotation, or other aspect of the
Please note new graphic by clicking on the Edit button.

Dynamic resources notes:

1. When defining the resource specifications, the An example of a single resource with multiple
default Resource Search for dynamic resources is graphics is given on the following page.
Closest Resource. The default for Entity Search is
Closest Entity.
Multiple Resource Graphics Example
2. More than one resource can use the same path
network. Uncheck the
New Box

Multiple Resource Graphics

Select the next
ProModel allows you to define several different blank resource
graphic icons for the same resource. For example, graphic cell
you may wish to change the color of a resource
whenever it becomes unavailable due to an
unscheduled downtime. Resource graphics for
dynamic resources may be changed during a sim-
ulation by using the GRAPHIC statement (see
“Graphic” on page 482) in either the node or
downtime logic. The GRAPHIC statement for
static resources can only be used in downtime
logic, however, any second and third graphics are Select an icon for the resource
automatically used when static resources are busy
or down, respectively. If no second and third
graphics are defined, the resource graphic turns
green when in use and red when down.
 ProModel 131
User Guide

This example shows a forklift with two different Multi-unit resources are intended for use when
orientations. You may define as many graphics as several resources are defined with the exact same
needed for each resource. specifications and any resource can be used at a
number of locations. For example, a computer
Please note can be operated by one of three technicians. If
you did not use multi-unit resources, you would
need to specify “USE Technician1 OR
When changing the graphic for a resource in
Technician2 OR Technician3,” although this can
downtime logic, or in the case of dynamic
easily be abbreviated by using a macro to repre-
resources, node logic, the number after the word
sent the resource expression. When you define
GRAPHIC refers to the cell number in the
three units for a single resource, Res1, you can
Resource Graphics window as shown above. For
simply state “USE Res1” and one resource unit
example the statement GRAPHIC 2 would
will be used based on its availability.
change the forklift to the icon in cell number 2.
The default graphic is the graphic in cell number
1 if none is specified. See “Graphic” on page 482 Multiple Single-Unit Resources
for more information. Multiple single-unit resources are useful when
resources have different specifications, follow
different path networks, or are used at specific
locations. If several resources have the same
Multi-Unit Resources vs. specifications and travel the same path network
Multiple Single-Unit Resources but can only do work or interface with specific
locations, they must be defined as multiple sin-
gle-unit resources. This is because a unit of a
Multi-Unit Resources multi-unit resource must be able to interface with
When a resource is defined as having more than all locations where it is called to work.
one unit, each resource unit is given a numeric
suffix by which it is identified in the output Resource Downtimes
report. For example, a resource (Res1) which has
five units will display output statistics for Resource downtimes refer to the times when a
resources called Res1.1, Res1.2, . . . . Individual resource is unavailable due to scheduled events
units of a resource (e.g., GET Res1.1) cannot be like breaks and shift changes, or unscheduled
requested. events like illness and random failures. For
scheduled events, it is much easier and more
Suppose you define a resource, Technician,
straightforward to define these downtimes using
which has ten units. You also have ten locations
the Shift Editor (see “Shifts & Breaks” on
and each resource unit can only interface with
page 161). Unscheduled downtimes, based on the
one location. For example, Technician.5 can only
elapsed time of the simulation clock or resource
work at Loc5. Since “USE Technician.5” is
usage time, are defined in the Resources edit
invalid, you would need to use multiple single-
table by clicking on the downtime heading but-
unit resources instead (e.g., Technician1,
ton.
Technician2, Technician3).
132 Chapter 5:
Resources

How to define resource downtimes: rence is to be determined from the frequency

field.
1. Select Resources from the Build menu. Priority The priority of the downtime (0-999).
2. Select the resource for which the downtime is to be The default priority is 99, which is the highest
defined. non-preemptive priority.
3. Click the DTs... button from the Resources edit Scheduled... Select YES if the downtime is to be
table. counted as a scheduled downtime. Select NO if
4. Select the downtime basis: Clock or Usage. the downtime is to be counted as a non-scheduled
downtime. (All scheduled downtimes are
5. Enter the required information in either the Clock
Downtime or Usage Downtime edit table. Each of deducted from the total hours scheduled in the
these tables is described in the following pages. statistical calculations.)
List A list of the individual units of the resource
to be affected by the downtime. You may list
individual units of the resource, specify ALL, or
Please note leave blank to affect all units.

Unlike location downtimes, multiple resource • 1,2 Units 1 and 2 only

downtimes occurring within the same time frame • 1-3,5 Units 1 through 3 and 5 only
are processed sequentially, not concurrently. • none You may use none to indicate that no
However, through the use of the DTDelay func- unit will adopt this downtime. This is use-
tion, concurrent downtimes can be achieved for ful in creating a run-time interface. By
resources. using a macro to represent the number of
units, the user may select none as an
option.
• Macro The name of a run-time interface
Clock-Based Downtime macro that allows the user to define the
units to be affected by the downtime.
Clock-based downtimes for resources are speci-
fied through the Clock Downtimes edit table Node This field applies only to dynamic
shown below. The fields of this table are defined resources and defines the node to which the
as follows: resource will travel to go down. If no node is
entered, the resource stays at the current node.
The actual downtime will not begin until the
resource arrives at this node. Traveling to the
downtime node is counted statistically as time
traveling to park.
Frequency The time between downtimes. This Logic... Specific logic to be performed when the
may be a constant time as shown above, a distri- downtime begins, typically a WAIT statement.
bution, or an expression. Resources may be used to service resources that
First Time The time of the first downtime occur- are down if the servicing resource is static, or if
rence. Leave this field blank if the first occur- the servicing resource is dynamic and uses the
same network. (See the “Appendix A” on
 ProModel 133
User Guide

page 577 for a list of statements valid in • none You may use none to indicate that no
Resource Downtime logic.) unit will adopt this downtime. This is use-
ful in creating a run-time interface. By
Disable Select YES to disable a downtime with-
using a macro to represent the number of
out removing it from the table.
units, the user may select none as an
option.
Usage-Based Downtime • Macro The name of a run-time interface
A usage-based downtime is a downtime based on macro that allows the user to define the
how long a resources has been used, such as how units to be affected by the downtime.
often a forklift needs to be refueled. Usage-based Node This field applies only to dynamic
downtimes for resources are specified through resources and defines the node to which the
the Usage Downtimes edit table shown below. resource will travel to go down. If no node is
Actual time in use includes any time that a entered, the resource stays at the current node.
resource is moving with an entity or is being used The actual downtime does not begin until the
by an entity at a location. It also includes any resource arrives at this node. Traveling to the
time a resource is being used in downtime logic downtime node is counted statistically as time
as a maintenance resource. The fields of this table traveling to park.
are defined as follows:
Logic... Specific logic to be performed when the
downtime begins, typically a WAIT statement.
Resources may be used to service resources that
are down if the servicing resource is static, or if
the servicing resource is dynamic and uses the
Frequency The time between downtimes, based same network. (For a list of statements valid in
on the usage time of a resource. This may be a Resource downtime logic, see the “Appendix A”
time distribution as shown above, or an expres- on page 577).
sion.
Disable Select YES to disable a downtime with-
First Time The time of the first downtime occur- out removing it from the table.
rence. Leave this field blank if the first occur-
rence is to be determined from the frequency
field. Please note
Priority The priority of the downtime (0-999). Usage-based downtimes do not accumulate. For
The default priority is 99, the highest non-pre- example, if a downtime is preempted by an entity
emptive priority. and another downtime is scheduled to occur
List A list of the individual units of the resource while processing the entity, only the first down-
to be affected by the downtime. You may list time resumes after processing the entity. All oth-
individual units of the resource, specify ALL, or ers are ignored.
leave blank to affect all units.
• 1,2 Units 1 and 2 only
• 1-3,5 Units 1 through 3 and 5 only
134 Chapter 5:
Resources

Resource Priorities and Preemp- Please note

tion
Resource priorities and preemption notes:
Priorities for resource requests may be assigned
1. If a resource is transporting an entity, it can-
through a GET, JOINTLY GET, or USE state-
not be preempted by another entity or by a down-
ment in operation logic, downtime logic, or move
time until it drops off the current entity at the
logic (or the subroutines called from these log-
destination location. Therefore, the resource will
ics). Priorities for resource downtimes are
deliver the current entity and then immediately
assigned in the Priority field of the Clock and
come under control of the preempting entity or
Usage downtime edit tables. The following
downtime.
examples illustrate these points.
2. If a resource is moving but does not possess an
Process Table entity, the resource can be preempted by a down-
time or entity. The resource will stop at the next
Entity Location Operation (min)
node in the path network and travel to the down-
EntA Loc1 Use Res 1,200 For N(3,.1)
time node after which the resource will go down.
Routing Table
Blk Output Destination Rule Move Logic
1 EntA Loc2 First 1 MOVE FOR 5 Resource Shift Downtime Priori-
ties
In ProModel, you define the shift downtime pri-
orities in the Shift Assignments module. The pri-
ority for a resource to start a shift downtime and
When an entity using a resource is preempted by the priority required for some other task to pre-
either a downtime or another entity, any process- empt the downtime must be set in the Shift
ing time for the preempted entity due to a WAIT Assignments module.
or USE statement is interrupted until the pre-
empting entity or downtime releases the resource. Although a resource may be in use during a shift
If an entity is using other resources in addition to downtime, the scheduled hours in the statistics
the one preempted, the other resources remain in will still reflect the hours scheduled to be on
possession of the entity. shift. For example, a resource goes off shift after
eight hours. Due to an emergency, the resource is
In the case of a resource downtime preempting called back two hours later to work on a machine
another resource downtime, any remaining time that has gone down. The statistics will still indi-
delay, as well as any other downtime logic cate that the scheduled hours for the resource are
remaining to be processed by the preempted eight when the resource actually spent more than
downtime, is immediately discontinued without eight hours in use, because the resource was
resuming and the preempting downtime takes scheduled to work only eight hours. The
over. resource's total usage time, however, will still
indicate the additional time spent working on the
downed machine.
 ProModel 135
User Guide

Resource Preemption Matrix • The lower-right quadrant shows that a pre-

empting downtime must have a priority at
The following Preemption Matrix shows the pos- least one level higher than the current
sibilities of entities and downtimes preempting downtime to preempt it.
each other in the use of a resource. “Current”
The following graphics demonstrate basic pre-
refers to the entity or downtime in possession of
emption concepts.
the resource when the requesting entity or down-
time attempts to capture it. Downtimes below
refer to clock and usage-based downtimes only.
Preemptive DT vs DT Total
Priority values are divided into ten levels (0 to Downtime:
99, 100 to 199,..., 900-999), with values beyond T1 to T3
DT 1
99 used for preempting entities or downtimes of a
lower priority level.
Discontinue
To Preempt To Preempt
The Current The Current
DT 2
Owner Downtime
Requesting
Entity or 1 priority level 2 priority levels
Time
Another higher higher
Resource or
Location’s T1 T2 T3 T4
Downtime
DT 2 priority at least 1 level higher
Requesting 1 priority level 1 priority level than DT 1 priority
Downtime higher higher

Non-preemptive DT vs. DT
• The upper-left quadrant shows that if an
entity tries to seize a resource currently DT 1
owned by another entity (or another
resource’s or a location’s downtime), the
entity must have a priority at least one
level higher than the current entity to pre- Scheduled DT 2
empt the resource.
• The lower-left quadrant shows that a down- Actual DT 2
time must have a priority at least one level
higher than the entity currently owning a
resource if the resource is to be preempted. Time
T1 T2 T3 T4
• The upper-right quadrant shows that an
entity must have a priority at least 2 levels DT 2 priority NOT at least 1 level higher than
higher than the current downtime priority DT 1 priority
to preempt a downed resource.
136 Chapter 5:
Resources

Non-preemptive DT vs. Entity Preemptive Entity vs. Entity

Entity
Ent 1

Scheduled DT

Actual
Ent 2
Time
Time
T1 T2 T3 T4
T1 T2 T3 T4

DT 2 priority NOT at least 1 level Ent 2 priority at least 1 level higher

higher than entity 1 priority than Ent 1 priority

Preemptive DT vs. Entity Preemptive Entity vs. DT

Entity DT

DT Entity
Time
Time

T1 T2 T3 T4 T1 T2 T3 T4

DT priority at least 1 level higher than Entity priority at least 2 levels higher
entity priority than DT priority

Resource Specifications Dialog

Box
The Specifications dialog box contains informa-
tion for defining the operating characteristics of
 ProModel 137
User Guide

each resource in the system. Many of the items Break If the resource is assigned to a path net-
pertain only to dynamic resources (i.e., resources work and shift, this is the node to which the
with path networks). If the resource is static (i.e., resource travels to go on break.
not assigned to a path network) many of the
Resource Search When an entity that needs a
options will be disabled. The Resource Specifica-
resource must select between several available
tions dialog box includes the following fields:
resource units, it follows this rule. This only
applies to multi-unit resources. The following
rules may be specified:
• Closest Resource
• Least Utilized Resource
• Longest Idle Resource

Please note

For a non-passing path network, only the Closest

Resource rule is allowed since the other rules
Path Network The name of the path network could cause the network to jam. Static resources
along which the resource travels. This should be only allow Least Utilized and Longest Idle rules
“none” for a static resource. since there is no traveling to be done.
Home If a path network has been assigned, this
is the name of the home node where the resource
is positioned at the beginning of the simulation.
Entity Search When two or more entities of
equal priority request a resource at the same time,
Please note the resource follows this rule to choose the one to
service. The resource first checks for any entities
To have resources start at other nodes in the net- waiting at locations listed in a work search before
work, define a Park Search from the home node defaulting to this rule and, if an exclusive work
which causes the resource unit or units to be search has been defined, the default entity search
positioned at the nodes identified in the park rule is not used. The following rules may be spec-
search. ified:
• Longest waiting entity (with highest priority)
• Closest entity (with highest priority)
• Entity with the minimum value of a specified
Return Home If Idle If a path network has been attribute
assigned, check this box to return the resource to • Entity with the maximum value of a specified
the home node when no other tasks are waiting to attribute
be performed and no park searches are defined.
Off Shift If the resource is assigned to a path net- Please note
work and shift, this is the node to which the
resource travels to go off shift. Entities look for resources to move them after
they capture a location. If several entities are
138 Chapter 5:
Resources

waiting to be transported to one location by a Resource Search Routines

resource and you want the entity with the mini-
mum attribute value to arrive next at the location, Search routines refer to the instructions a
you must use the Locations edit table to define the dynamic resource will follow after being freed at
rule at the location for incoming entities as mini- a path node where a search routine was defined.
mum attribute value. The Closest entity rule Two types of search routines may be specified.
applies to dynamic resources only. Work Search A list of locations where entities
may be waiting for the resource. Work searches
If the path network that the dynamic resource is may be either exclusive or non-exclusive.
using is time-based, the closest entity is the entity
with the least number of nodes from the resource. • Use exclusive work searches to limit the
If the path network is defined by speed and dis- locations a resource may search for work.
tance, the closest entity is the entity the shortest An exclusive work search will cause the
distance from the resource. resource to search only the locations in the
list. If no work is found at any of the listed
locations, the resource will either park at a
node listed in its park search, go to its
Motion If a path network has been assigned, the home node, or simply become idle until
motion fields define the speeds and times work is available at one of the locations in
required for basic resource movement and con- the exclusive work search list.
tain the following information: • Use non-exclusive work searches to have a
resource check for work at certain loca-
• Speed traveling empty/full*
• Acceleration rate*
tions first, and then move on to others. A
• Deceleration rate* non-exclusive work search will cause the
• Pickup time resource to search the listed locations first
• Deposit time and then resort to the default search rule
listed in the Resource Search section of the
Please note Specifications dialog box (e.g., oldest
waiting entity, closest waiting entity).

Resource specification notes: Park Search Park searches are typically used to
get a resource off a main path segment, or send
1. The units to the side of these fields change the resource to the next most likely place work
automatically from feet to meters (and vice- will become available. A park search is a list of
versa) depending on the default distance units nodes to which a resource may be sent to park if
selected in the General Information dialog box. no work is waiting at either the work or default
2. Pickup and deposit times for resources are search locations.
included as transit time in the output statistics.
 ProModel 139
User Guide

Please note processing location. This helps to keep the pro-

cessing locations busy at all times.
A lockup can occur in the model if you define a
park search at the home node and specify Return Park Search Edit Table
Home If Idle in the Resource Specifications.
Park searches are defined for dynamic resources
through the Park Search edit table shown next. If
several resources share the same path network,
each resource must have its own park search
Work Search Edit Table defined (i.e., resources cannot share park
Work searches are defined for dynamic resources searches).
through the Work Search edit table shown below.
If several resources share the same path network,
each resource must have its own work search
defined (i.e., resources cannot share work
searches).

The fields of the Park Search edit table are

defined as follows:
Node The node for which the park search is
defined.
Parking Node List A list of nodes to which a
resource may be sent to park. The resource will
The fields of the Work Search edit table are
look for available capacity at the first node in the
defined as follows:
list (Node capacity is defined in the Path Net-
Node The node for which the work search is works edit table in the Nodes window). If there is
defined. no capacity at that node, the resource will look to
the second node in the list and so on until a node
Type Exclusive or non-exclusive work search.
with capacity is found. If no capacity is found at
See “Resource Search Routines” on page 138 for
any node in the list, the resource will remain
an explanation of exclusive and non-exclusive
where it is until capacity becomes available at
work searches.
one of the nodes in the list.
Location List A list of locations to be searched
In the table above, a park search has been defined
for waiting entities when the resource becomes
for each of the internal path nodes where a fork-
available.
lift might deliver an entity and then be in the way
In the edit table above, work searches have been if it has nothing else to do. Specifically, if a fork-
defined at each location where the forklift deliv- lift makes a delivery and then becomes available
ers entities. The purpose of the work search in at node N3, it will park at node N4. From node
this example is to force the forklifts to give prior- N5 it will park at node N1, and from node N6 it
ity to entities waiting to be delivered to process- will park at node N7.
ing locations before taking an entity to a non-
140 Chapter 5:
Resources

Node Logic Editor Node Logic Example

The Node Logic edit table is used to define spe-
cial logic for a dynamic resource to perform upon
entering or exiting a node. Node logic may be
defined for any dynamic resource at any node.
Typical uses of node logic are:
• Changing a resource graphic using the
GRAPHIC statement
• Controlling traffic using WAIT UNTIL state-
ments
• Gathering special statistics on resource
movement
Suppose that for safety considerations we desire
to keep track of the number of times both forklifts
simultaneously enter a particular zone of the net-
work consisting of branches N2 to N3, N3 to N4,
and N3 to N5. (It is thought that this zone may be
The fields of the Node Logic edit table are particularly susceptible to accidents due to heavy
defined as follows: traffic.) We could accomplish this using node
logic at the entry and exit points of the zone.
Node The entry or departure node where the
resource will process the logic. The only way to enter or exit the zone is through
nodes N2 and N5. To track the number of fork-
Entry Logic Logic to be executed when a lifts currently in the zone, we increment and dec-
resource enters the node. rement a variable called Current. Each time a
Exit Logic Logic to be executed when a resource forklift leaves node N2 or N5 en-route to node
leaves the node. N3 we increment variable Current. Each time a
forklift enters node N2 or N5 enroute from N3 we
The table above was taken from the example con- decrement variable Current. Finally, each time
tained on the following pages. we increment the variable Current, we check to
see if Current > 1. If so, we increment a second
variable called Total to record an occurrence of
both forklifts in the zone at the same time.
The following windows show the entry and exit
logic for node N2, representing one entry to the
 ProModel 141
User Guide

zone. The node logic for node N5 is identical to it. The horizontal offset is 0 units for each point.
that for node N2. The vertical offset is 13 units both up and down
from the node position. (For resource points posi-
tive distances are up and to the right.)

Please note

This example follows the rule that allows the

LAST() function to be used only in Node Entry
Whenever a forklift arrives or parks at node N8,
Logic, while the NEXT() function may be used
it will automatically go to one of the two resource
only in Node Exit Logic. (See “Resource-Specific
points. This prevents the forklifts from graphi-
System Functions” on page 425).
cally appearing on top of each other if they are
both at node N8 simultaneously.

Resource Points How to add resource points to a node:

For a static resource, resource points are the lay- 1. Select Resources from the Build menu.
out coordinates of the resource graphics. For
2. Click on the resource points heading button, Pts....
dynamic resources, resource points are auxiliary
points where multiple resources may appear 3. Click on the node for which a resource point is to be
graphically when in use or parked at a multi- added.
capacity node. When a resource arrives at a node, 4. Click on the layout where the resource point is to
it will appear on that node unless a resource point appear.
is defined for that resource at that node. The 5. Repeat steps 3 and 4 for each resource point to be
resource will appear on the resource point when it added.
arrives to park or perform a task at a particular
node. Resource points prevent resources from
appearing on top of each other. In the case of
dynamic resources, resource points are defined in
terms of an offset from the node to which they are Please note
connected. Resource points are defined in terms
of an offset from the upper left corner of the lay- Resource points are automatically added to the
out for static resources. home node for each resource graphic placed on
The following Resource Points edit table shows the layout.
that node N8 has two resource points attached to
142 Chapter 5:
Resources

How to delete resource points:

1. Bring up the Resource Points edit table by clicking

on the Pts... heading button in the Resources edit table.
2. Select the point to be deleted by highlighting the
edit table record or clicking on the resource point in the
layout. (If you click on the point to select it, you must
then reactivate the Resource Points window by click-
ing on the title bar of the table.)
3. Select Delete from the Edit menu.

How to move resource points:

1. Bring up the Resource Points edit table by clicking

on the Pts... heading button from the Resources edit
table.
2. Drag the resource point to a new location with the
mouse.
 ProModel 143
User Guide

Processing Using the Processing Editor

Processing defines the routing of entities through This discussion covers the procedures used to
the system and the operations that take place at define operations and routings using the Process-
each location they enter. Once entities have ing Editor. As with most other procedures in Pro-
entered the system, as defined in the Arrivals Model, they may be performed graphically using
table, processing specifies everything that hap- the mouse, or manually by typing the information
pens to them until they exit the system. directly in the edit tables.

Processing is defined in the Processing Editor, Before you begin to specify the processing logic,
which is accessed through the Build menu. This define all locations and entities to be referenced
section first describes how to create simple pro- in the processing. This is done through the Loca-
cesses, then explains each feature of the Process- tion and Entity Editors. If you reference a loca-
ing Editor. tion or an entity that has not yet been defined in a
location or entity field, you will be prompted to
add that location or entity to the respective loca-
tion or entity list. However, no graphic gets auto-
matically assigned to the location or entity.
The easiest way to define the processing logic is
to define the routing or flow sequence using the
tools in the Processing Tools window, which
appears in the lower left corner of the Processing
Editor. These tools have been designed to allow
you to easily and rapidly define the flow of enti-
ties through the system. It is also a good idea to
define the routing rule for each routing as it is
created. Once you have defined the from-to rela-
tionships between locations for each entity, fill in
the details of the operation and move logic for
each location. This is typically done by typing the
logic in the operation or move logic column man-
ually or by using the Logic Builder, documented
How to create and edit process rout- at the end of this section.
ings: Defining processes graphically in ProModel
requires interaction with all four process editing
• Select Processing from the Build menu. windows.
• Process Edit Table
or... • Routing Edit Table
• Tools Window
• Right click on the existing process routing and select • Layout Window
Edit.
144 Chapter 5:
Processing

Before discussing the procedures for using these the top of the list—this entity will come into the loca-
windows interactively, let us look briefly at a pro- tion, it is not the entity that results from the process.
cess flowchart of a simple model. 2. Select the desired editing mode: New Process or
Add Routing.
Example Model 3. Click on the first location where the entity will pro-
cess. A rubber-banding routing line appears. If you
Two entity types, EntA and EntB, arrive at Loca-
select Add Routing, the rubber-banding routing arrow
tions 1A and 1B, respectively, according to some
automatically appears from the current location.
specified arrival logic. After a short preparation
time, both entities are routed to Location 2 where 4. To choose a different entity as the output entity,
1 EntB is joined to 1 EntA. At this point the select the desired output entity in the tools window.
resulting entity, EntC, is sent to Location 3 for 5. Click the destination location.
consolidation. Twelve EntC's are accumulated at
Location 3 and processed together for 3.0 min-
utes. Then they exit the system. Please note

Process Flow Chart In the example below, we first clicked on Loc1A

and then on Loc2. The records in the Process and
EntA @ Loc1A
EntA
Routing edit tables were entered automatically.
EntA 1.0 min 1

EntA @ Loc2 EntC @ Loc3

EntC
Join 1 1 Accum 12 1
N(3.4,.2) 3.0 min

EntB @ Loc1B
EntB
EntB 1.0 min 1 Exit

Arrival Processing
Logic Logic

In the flowchart above, each block represents a

process record for an entity at a location. The
lower left portion of a block specifies the opera-
tion(s) performed on the entity at the location.
The lower right portion of the block represents
the number of entities output to the next location.

Defining Entity Processing

6. Repeat this process until the flow of entities has
How to define entity processing graph- been completely defined except for exiting the system.
ically: 7. From the final processing location route an entity to
Exit by clicking on the “Route to Exit” button in the
1. Select an entity from the entity list in the Tools win- Tools window.
dow. The selected entity will appear in the edit field at
 ProModel 145
User Guide

8. Once all routings have been defined, enter the pro- shown in their default arrangement, you may
cessing logic in the operation field of the Process edit arrange them as desired.
table.

Process Edit Table Appears in the upper left cor-

ner of the workspace and defines the operations
performed for all entities at all locations.
The figure above shows the completed routings
Routing Edit Table Appears in the upper right
for the example model. Note that the operations
corner of the workspace and controls the destina-
(for example, Join 1 EntB) have been entered
tion of entities that have finished at the location.
manually in the operation column. These opera-
tions could also have been entered by way of the Tools Window Appears in the lower left corner of
Logic Builder, documented at the end of this sec- the workspace and is used for graphically defin-
tion. ing operations and routings.
Layout Window Appears in the lower right cor-
Processing Editor ner of the workspace and shows each location
with all from-to routings.
The Processing Editor consists of four windows
that appear simultaneously, as shown in the fol-
lowing diagram. Although the windows are Process Edit Table
The Process edit table is used to create operation
logic for each entity type at each location in the
system. Processes for entities at locations may be
in any order in the edit table, but for the sake of
organization you should group them by entity
type or location. The only time the order of pro-
cesses is significant is when the same entity is
routed multiple times through the same location,
in which case, later processes must appear some-
146 Chapter 5:
Processing

where after earlier processes. When searching for can also click on an entity name and select OK to
the next process, ProModel always searches for- place it in the table.
ward in the process list first, and then starts from
the beginning of the list.

Heading
Buttons

Current Entity, Location, and Operation

are highlighted. The entity list box defaults to the current field
entity, the last entity selected, or the first entity
An explanation of each field of the Process edit defined.
table is contained on the following pages. Location The location where the process occurs.
Entity The entity type for which the process is Click on the heading button to bring up the Loca-
defined. If all entities at the same location tions selection box from which you may choose a
undergo the same operation or have the same location.
routing, the reserved word ALL may be entered
in this field. (See discussion on ALL later in this
section.) If an entity not previously defined is
entered in this field, ProModel will ask if it
should create the new entity type.
Click on the heading button to bring up the Enti-
ties selection box. If this is a preemption process
record, check the box (see “Preemption Process
Logic” on page 292) and double click on an
entity to automatically place it in the table. You

The location list box defaults to the current loca-

tion, the last location selected, or the first location
defined.
Specifying ALL in the Location field and omit-
ting any routing defines a process for an entity at
all locations previously specified as routing desti-
nations for the entity. Because there is no routing,
 ProModel 147
User Guide

after the entity finishes that process, ProModel operations performed on other entities at the
will search ahead in the Process edit table for a same location.
process for the entity specific to the actual loca-
tion. The keyword ALL in the Location field is
particularly useful when entities route to different
locations having the same operations and then
route to a common destination. In most other
instances, it is recommended that a subroutine or
macro be used to define identical operations.
Operation Operation logic is optional, but typi-
cally contains at least a WAIT statement for the
amount of time the entity should spend at the
location. If the entity needs a resource to process
or to be combined in some way with other enti-
ties, that would be specified here as well. In fact, For more information see “Operation Logic” on
anything that needs to happen to the entity at the page 291.
location should be specified here, except for any
information specified in the entity's routing. Using the “ALL” Entity Type
Statements can be typed directly into the opera- The reserved word ALL may be entered as the
tion field, or inside a larger logic window after processing entity if all entity types at that location
double clicking in the field or clicking on the have the same operation. ALL may also be used
Operation button. Alternatively, the Logic in the output field of the routing if all entity types
Builder can help build logic and is accessed by at that location have the same routing. If a pro-
clicking the right mouse button inside the opera- cess record for a location using ALL as the entity
tion field or logic window. All of the statements, follows several process records for the same loca-
functions, and distributions available in the oper- tion using specific entity names, and each process
ation field are discussed in detail, including record has a defined routing, the ALL process is
examples, in “Statements and Functions” on interpreted to mean ALL of the rest of the enti-
page 429. ties. The following examples show how ALL
may be used in different situations.
Each entity performs the operation steps defined
for it at a particular location, independent of other
1.All entities have a common operation and a
common routing.
To define a common operation and routing for all
entity types at a location, simply enter ALL for
both the process entity name and the output entity
name.
In the following example three entity types,
EntA, EntB, and EntC, are all sent to a packing
station for packaging. The packing time is .5 min-
utes and the entities move on to a shipping sta-
148 Chapter 5:
Processing

tion. Though this is a simple example, it shows Process Table

how one process and routing record is used for all
Entity Location Operation (min)
entity types. In contrast, the previous operations
ALL Packaging WAIT .5
at Loc1, Loc2, and Loc3 require separate process
EntA Packaging
and routing records for EntA, EntB, and EntC.
EntB Packaging
EntC Packaging
Process Table
Entity Location Operation (min) Routing Table
EntA Loc1 WAIT N(5,.3)
Blk Output Destination Rule Move Logic
EntB Loc2 WAIT U(3,.2)
EntC Loc3 WAIT T(3,5,9)
1 EntA Ship1 FIRST 1 MOVE FOR 1
ALL Packaging WAIT .5
1 EntB Ship2 FIRST 1 MOVE FOR 1
1 EntC Ship3 FIRST 1 MOVE FOR 1
Routing Table
If only the destination is different, but move
Blk Output Destination Rule Move Logic times and output quantities are identical, an alter-
1 EntA Packaging FIRST 1 MOVE FOR 1
native method is to assign each entity an attribute
1 EntB Packaging FIRST 1 MOVE FOR 1
that corresponds to the destination's name-index
1 EntC Packaging FIRST 1 MOVE FOR 1
number and then route with the LOC() function
1 ALL Shipping FIRST 1 MOVE FOR 1
as shown in the following example.
2.All entities have common operations but
Process Table
individual routings.
To define common operations but individual Entity Location Operation (min)
routings, use ALL as the process entity and ALL Packaging WAIT .5
define the common process, but do not define any
routings. Then define individual processes for Routing Table
each entity type at the common location, with a Blk Output Destination Rule Move Logic
blank operation field and the desired routing. 1 ALL Loc(Att1) FIRST 1 MOVE FOR 1

3.All entities have a common routing but indi-

vidual operations.
To define individual operations along with a
common routing for all entity types at a location,
define operations for each entity, but do not
define any routings. Then define a process record
for ALL at this location and define the common
routing for all entity types.
 ProModel 149
User Guide

Process Table table to the Process edit table (i.e., all routings
that appear in the routing edit table apply to the
Entity Location Operation (min)
currently highlighted process), though the two
EntA Loc1 WAIT .4
tables appear side by side. Not all process records
EntB Loc1 WAIT .5
need to have a corresponding routing. If the rout-
EntC Loc1 WAIT .6
ing is omitted, ProModel will search forward in
ALL Loc1
the Process edit table for another process for that
entity at that location. So an entity's complete
Routing Table
processing at a location could be broken into sev-
Blk Output Destination Rule Move Logic eral records. In that case, only the last process
would have a routing. If no routing is defined for
at least one of the process records for a given
entity and location, an error occurs.
1 ALL Packaging FIRST 1 MOVE FOR 1
Another situation that does not require routing is
Alternatively, you can assign an attribute to each when an entity changes its name at a location
entity which represents the processing time or after a RENAME AS or SPLIT AS statement.
some other entity-specific parameter. Then use Any time during processing logic that an entity
the attribute as the processing time, or call a sub- changes its name, ProModel searches forward in
routine and pass the attribute as a parameter for the Processing edit table until it finds a process
entity-specific processing. for the new name at the same location. For exam-
ple, if the identity of an entity is changed through
In the following example, the test time for each
a RENAME AS statement in the operation logic,
entity type is different. This time is stored in an
then no routing block will apply to the old entity.
attribute, Oper_Time. The attribute is then listed
Instead, the newly named entity will be routed by
on a line in the operation logic (with a WAIT
the process for the new name. (See “Rename” on
statement) to signify an operation time. Once the
test time for each entity is completed, the entities page 531).
are all routed to a packaging location.

Process Table
Entity Location Operation (min)
ALL Test WAIT Oper_Time
The fields of the Routing edit table are as fol-
Routing Table lows:
Blk Output Destination Rule Move Logic Blk This field contains the block number for the
1 ALL Packaging FIRST 1 MOVE FOR 1 current routing block. A routing block consists of
one or more alternative routings from which one
is selected based on the block rule (e.g., a list of
Routing Edit Table routings where one is selected based on the most
The Routing edit table defines the outputs for available capacity). Since all of the routings
each process record defined in the Process edit using the same rule are part of the same block,
table. The Routing edit table is really just a sub- only the first line of each routing block contains a
150 Chapter 5:
Processing

route block number. If no routing blocks have sequentially while split entities get processed
been referenced explicitly in the operation logic concurrently.
(for example “ROUTE n”), all routing blocks
If the reserved word ALL was used as the incom-
will be executed in sequence upon completion of
ing entity type for this process, it may also be
the operation logic (See “Route” on page 542).
entered here. Otherwise, every entity entering the
Multiple routing blocks are processed sequen-
location will change to the specified output
tially with the next block being processed when
entity. (See the discussion on using ALL in the
all of the entities in the previous block have
Entities section.)
begun executing any move logic defined. To
change the routing block number or add a new
routing block, see the discussion on the Routing
Rule dialog box later in this section.
The following example shows a process record
with two separate routing blocks. Note that both
routings will execute upon completion of the
operation time because no ROUTE statement has
been specified. One EntB gets routed to Loc2 and
one EntC gets routed to Loc3.

Process Table
Entity Location Operation (min)
The entity list box defaults to the current field
EntA Loc1 WAIT N(5,.3)
entity, the last entity selected, or the first entity
defined.
Routing Table
To better anticipate the entity entry likely to be
Blk Output Destination Rule Move Logic
made, the entity highlighted in the list box
1 EntB Loc2 FIRST 1 MOVE FOR 1
2 EntC Loc3 FIRST 1 MOVE FOR 2
defaults first to the current field entity, then to the
last entity selected, and finally to the first entity
Output If a routing is defined, the name of the defined.
entity resulting from the operation must be
entered here. This name may be the same as the The example below shows how an incoming
entity that entered, or it may be another name, or entity, EntA, changes identity and becomes an
even several names, each on a different line. EntB upon exiting location Loc1. This is done by
simply specifying the new entity name as the out-
Using another name works much like a put entity.
RENAME-AS statement, except that the entity is
routed according to the routing block instead of
being processed further at the same location.
Using several names on different lines is similar
to having a SPLIT AS statement in conjunction
with a RENAME-AS statement. The difference is
that multiple routing blocks are processed
 ProModel 151
User Guide

Process Table TINUE, and IF EMPTY routings. (See “Loc()”

on page 501 for more information.)
Entity Location Operation (min)
EntA Loc1 WAIT T(2,5,8) Rule This field defines the rule for selecting the
route destination. An output quantity may also be
Routing Table specified as part of the rule. This quantity works
much like the SPLIT AS statement. (See the fol-
Blk Output Destination Rule Move Logic lowing discussion on the Routing Rule dialog
1 EntB Loc2 FIRST MOVE FOR 1 box.) To open the Routing Rule Dialog box, dou-
Destination This is the location to which entities ble click in the field or click in the field and then
are to move after the operation is complete. on the heading button.
Optionally, the destination may be followed by a Move Logic The Move Logic window allows
comma and a routing priority. If no priority is you to define the method of movement as well as
specified, the default is zero. any other logic to be executed between the time
The location name may be typed directly in the the next location is claimed for routing to the
field, or selected by either clicking in the field time the entity arrives, but not yet enters, the next
and then on the heading button, or double click- location. To open the Move Logic window, dou-
ing in the field. The resulting dialog box looks ble click in the field or click the heading button.
like this: This window allows you to manually edit the
logic or click on the Build button to use the Logic
Builder. It also provides other convenient buttons
for editing and printing the move logic. For sin-
gle move statements it is easiest to right click in
the move field to open the Logic Builder. If left
blank, it is assumed that no time, resources, or
path networks are needed to make the move. (See
“Routing Move Logic” on page 153.)

Routing Rule Dialog Box

The Routing Rule dialog box provides methods
for selecting an entity's destination after finishing
a process. The Rule heading button in the Rout-
ing edit table, brings up the Routing Rule dialog
Instead of entering a location name, you may use
the LOC() function which returns the location
name corresponding to the index designated by
an expression. For example, LOC(5) routes to the
fifth location defined or the fifth record in the
location edit table. You can also specify variable
destinations such as LOC(Att4). However, the
LOC() function may not be used in conjunction
with the BY TURN, UNTIL FULL, CON-
152 Chapter 5:
Processing

box. The fields of this dialog box are defined in AS statement, dividing the cost statistics between
the following example. the split members and resetting all time statistics
to zero.

Please note

A run-time error occurs if you fail to route one

(and only one) main entity for a process. If no
routing block executes for the main entity, a “No
routing defined for main entity” error occurs. If
more than one route block executes for the main
entity, a “Main entity already routed” error
occurs.

Quantity The number of entities resulting from

Start new block Check this box to signal the
this routing block. The default is one. Several
beginning of a new routing block. Checking this
entities of the same name can be created from a
box will place a number in the Blk field for that
single entity, much like a split AS statement, by
record.
entering a number greater than one. Each of the
New Entity Check Box In order to let you desig- new entities then processes the routing block one
nate whether a routing block applies to the main entity at a time. For example, suppose an entity
entity or if you wish to create a new entity, Pro- called mail_bag enters a location and is separated
Model includes a New Entity check box in the into 30 individual pieces of mail, called Letters.
routing rule dialog. By default, ProModel does Enter 30 as the quantity and Letter as the output
not check the first routing block for a process entity, as in the example below. Only the first line
record but does check subsequent blocks unless in a routing block can specify a quantity.
they share the same input and output name. If you
check the New Entity box, an asterisk (*) appears Process Table
after the block number in the block column of the
routing table. Entity Location Operation (min)
mail_bag Loc1 WAIT T(2,5,8)
If you check the new entity box, the entity using
the routing block will begin routing with new Routing Table
cost and time statistics. If the new entity box
remains unchecked, ProModel assumes the entity Blk Output Destination Rule Move Logic
routing from this block is a main entity (the par- 1 Letter Loc2 FIRST 10 MOVE FOR 1
ent entity), carrying with it all cost and time sta- Routing Rules Choose the rule for selecting the
tistics. next location. Only one rule may be chosen for
If the new entity field remains unchecked and each routing line. Note that the last three routing
you enter a quantity field value greater than 1, rules, alternate, backup and dependent, may not
ProModel behaves just as it does with a SPLIT be chosen as the start of a new routing block.
 ProModel 153
User Guide

Note also that no more than one of the other rules more information on “Routing Move Logic” on
can appear in a single block (e.g., you cannot mix page 153.
a First Available rule and a Most Available rule in
the same block).
Processing Tools
For exact syntax and examples of each routing
rule, see “Routing Rules” on page 405. The Tools window provides graphical aids that
may be used to define processing records and
routing records. It is also used to define the
Routing Move Logic graphical paths that entities follow when moving
The Move Logic window allows you to define without a path network between locations.
the method of movement as well as any other
The Tools window, which appears along with the
logic to be executed prior to or after the move
other Processing windows, can define processing
actually takes place.
in one of two modes, New Process or Add Rout-
Once the route condition or rule has been satis- ing. Each is explained next. Additionally, Find
fied for allowing an entity to route to a particular Process Mode is available. To select a mode,
location, the move logic is immediately executed. click on the desired button. Each of the modes is
The entity does not actually leave the current described on the next page.
location until a move related statement (MOVE
FOR, MOVE ON, MOVE WITH) is executed or
the move logic is completed, whichever happens
first. This allows the entity to get one or more Editing Mode
resources, wait additional time, or wait until a
condition is satisfied before actually leaving the
location.
Any statements encountered in the move logic Current Entity
after the move related statement are executed
after the move is complete but before the entity
actually enters the next location. This is often
useful for freeing multiple resources that may
have been used to transport the entity.
When defining exit logic, such as incrementing a Routing Options
variable used to track the number of exits from a
location, it can generally go before the move
statement unless a MOVE WITH statement is
used and the entity must capture the resource
before making the move. In this situation, a GET
statement should be specified first to get the In addition to option buttons (New Process, Add
resource. Then the exit logic may be specified Routing, or Find Process) for the process editing
followed by the MOVE WITH statement. mode, the Tools window contains a list of defined
entities as well as the reserved word ALL to rep-
Any delay occurring as a result of move logic is resent all entity types. The entity in Processing
reported as part of the entity’s move time. For Tools applies to either the process or routing
154 Chapter 5:
Processing

entity, depending on what is currently being How to delete a process or routing

defined. record:

New Process Mode 1. Click inside the desired record in the Process or
Routing edit table.
New Process Mode is used to create a new pro-
cess record. A new process is automatically cre- 2. Select Delete from the Edit menu.
ated for the selected entity each time you click on
a location.
This mode should be used if you want to create a Editing a Routing Path
process for a particular entity at a location. You
may even create multiple processes for the same Once a routing path has been defined you may
entity and location if you want to re-route an edit the path (regardless of the current mode) by
entity through the same location more than once clicking anywhere on the routing path. This
for additional operations. Once a new process is selects the path and allows you to change the
created, the mode automatically changes to Add source or destination of the routing by dragging
Routing mode to enable a routing to be defined the beginning or end of the path to a new loca-
for the process. tion. It also allows you to move any intermediate
joint in the path to change the shape. You may
also click on a path with the right mouse button to
How to define a new process using the create or delete a joint.
Tools window:
If a process is already defined and a location is
moved while in the Location module, the con-
1. Depress the New Process button.
necting leg of any routing lines will also move.
2. Select the entity for which a new process is to be
defined from the Tools window.
Add Routing Mode
3. Click on the location where the entity will be pro-
cessed in the layout window. A new process record is Add Routing Mode is used to create multiple
created in the edit table. The mode is automatically routings for a single process record. Suppose an
switched to Add Routing mode and a rubber banding entity, EntA, can travel to one of three locations
line appears that connects the mouse pointer to the depending on which is available first. Selecting
location. the New Process mode and then defining the
4. If a different entity is to be output from the process, entity process causes the entity to travel from one
select it from the Tools window. location to another location. Selecting Add Rout-
ing mode afterwards allows you to define a dif-
5. Click on the destination location. A new routing
ferent destination location within the same
record appears in the edit table and the mode switches
back to New Process mode. routing block.
 ProModel 155
User Guide

How to add additional routings to an Find Process Mode

existing routing block: To find a previously created process for an entity
type at a certain location, use Find Process mode.
1. Select the process record in the Process edit table
that needs an additional routing line (you may use the
Find Process button to locate the process record).
How to find a process for an entity at a
location:
2. If you wish to insert the routing record rather than
simply append the record to the current routing list,
highlight the routing record where the routing is to be 1. Click on the Find Process button.
inserted and choose Insert from the Edit menu. 2. Click on the desired entity type.
3. Select the Add Routing button from the Tools win- 3. Click on the desired location. The first process
dow. A rubber-banding line is created. found for that entity type at the location will be high-
4. Select the entity in the Tools window to be output in lighted in the Edit window.
this routing.
5. Click on the desired destination location. This cre-
ates a new routing record in the Routing edit table. This option always searches forward in the pro-
cess list. By clearing the entity field in the tools
window, the next process for any entity at the
location selected is found. If multiple process
Please note records exist for the same entity and location, the
edit table indexes forward to the next process
To cancel a routing once a rubber-banding line record each time you click on the location.
appears, click on the New Process button or click
on the originating location.
View Routing
The View Routing button in the Processing Tools
window causes the process record currently high-
How to route a current entity to exit: lighted in the edit table to become centered on the
layout.
1. Click the Add Routing button.
2. From the Tools window, select the entity for which Snap Lines to Border
you want to define a new process. When you check this option, ProModel snaps the
3. Click the Locations button in the process record dia- routing lines to the location’s bounding area
log and select the location from which the entity will rather than a specific position on the graphic.
exit the system. ProModel creates a new process record
in the edit table and displays a rubber-banding line
from the selected location.
Show Only Current Entity
4. Add joints as needed to define the exit path. When you highlight an entity in the list box,
checking this option will show only those rout-
5. Click the Route to Exit button in the tools dialog.
ings associated with the entity.
156 Chapter 5:
Arrivals

Arrivals edit table contains the specifications of each

arrival to the system and appears across the top of
Any time new entities are introduced into the sys- the screen. The Tools window contains tools for
tem, it is called an arrival. An arrival record is defining arrivals graphically and appears at the
defined by specifying the following information: bottom left corner of the screen. The Layout win-
dow appears in the lower right corner of the
• Number of new entities per arrival
workspace.
• Frequency of the arrivals
• Location of the arrival
• Time of the first arrival
• Total occurrences of the arrival
Any quantity of any entity type can be defined as
an arrival for a location. The frequency of arriv-
als can be defined as either a distribution or as an
arrival pattern which cyclically repeats over time.

Arrivals Edit Table

The Arrivals edit table lists all scheduled entity
arrivals to the system. The various fields are
explained next.

Entity The name of the arriving entity.

Location The name of the location where the

How to edit arrivals entity is to arrive.

• Select Arrivals from the Build menu. Qty each... The number (1 to 999999) of entities
to arrive at each arrival time interval. Any valid
expression may be entered here except for
attributes and non-general system functions. This
Arrivals Editor field is evaluated throughout the simulation run
and will change if the result of the expression
The Arrivals Editor consists of three windows changes.
that appear on the screen together. The Arrivals
 ProModel 157
User Guide

To fill a location to capacity at every arrival time, Disable Set this field to YES or NO if you want
use the keyword INFINITE, abbreviated INF. to temporarily disable this arrival without delet-
ing it. This is useful when debugging a model and
If you have previously created an arrival cycle
for verification purposes where you want to fol-
and want to use it for this arrival, enter the name
low a single entity through the system.
of the arrival cycle followed optionally by a
quantity. You may also click on the Qty each...
heading button to select from the list of defined Arrivals edit table notes:
cycles. See the section on Arrival Cycles for
more information about defining cycles. 1. When several different entity types are sched-
First Time This option allows you to dynami- uled to arrive at a location simultaneously, they
cally vary the time of the first arrival to your will arrive in the order they are listed in the
model. You may define scheduled arrivals to Arrivals table. To have them alternate their arriv-
occur at given intervals (e.g., appointments) or als, enter a 1 in the “Qty each” field and the total
use an arrival cycle to define random arrivals entry quantity in the “Occurrences” field.
over a period of time (this value is the start time 2. Arrivals defined through an external arrival
for the first cycle). ProModel evaluates this field file will be appended to the arrival list. Therefore,
only at the beginning of the simulation. if an external arrival file is the only source of
Occurrences The number of times per simulation arrivals, the Arrival edit table may be left blank.
run that ProModel will generate arrivals (1 - See the section on External Files for more infor-
999999). Entering the reserved word INFINITE mation on arrival files.
(abbreviated INF) will cause ProModel to send 3. If the capacity of the location is insufficient to
the specified number of arrivals at every arrival hold all the arriving entities, the excess entities
time without limit. This value may be any expres- are destroyed. Therefore, the arrival location
sion and is evaluated only at the beginning of the should have a capacity at least equal to the “Qty
simulation. If an arrival cycle is used, this is the each” in the Arrivals edit table. If more entities
number of times to repeat the cycle. are scheduled into the system than are exiting, the
Frequency The inter-arrival time or time arrival location may not have enough capacity to
between arrivals. Any valid expression may be handle all the arrivals.
entered here except for attributes and non-general
system functions. If an arrival cycle was entered
for the arrival quantity, this is the time between
the start of each cycle. This field is evaluated Defining Arrivals
throughout the simulation run and will change if
Arrivals may be defined graphically by using the
the result of the expression changes.
tools in the Tools window, or by manually enter-
Logic This field defines any optional arrival ing the arrival information directly in the Arrivals
logic, consisting of one or more general state- edit table.
ments, to be executed by each entity upon its
arrival (e.g., assigning attribute values to entities How to define arrivals graphically:
as they arrive). Double-click inside this field or
click the logic button at the top of the column to 1. Select Arrivals from the Build menu.
define logic for an arrival.
158 Chapter 5:
Arrivals

2. Select the desired entity from the Tools window. appointments, meeting times, or pickup and
delivery times. When defining independent arriv-
als, remember that simulation can model only
predefined appointment schedules. This means
that dynamically scheduled appointments (e.g.,
rescheduling return visits to fit into available
slots) must take place where you define the
appointment schedule.
When defining independent arrivals, you may:
• Define them by elapsed time, day and time,
3. Click in the layout window at the location where the
or calendar date.
entity is to arrive. (You may need to scroll through the • Assign them to occur at fixed intervals (e.g.,
layout to bring the desired location into view.) interviews scheduled every fifteen min-
utes).
4. Enter the specifications for the arrival record (e.g.,
arrival quantity and frequency).
Please note

When you define independent arrivals as inter-

How to define arrivals manually: vals, the next arrival time is independent of the
previous arrival. For example, applicants will
1. Select Arrivals from the Build menu. arrive for appointments based on the clock
2. Enter the Entity, Location, and Quantity through time—not the time elapsed since the last arrival.
either the keyboard or by clicking on the respective
heading buttons and choosing the proper information.
3. Enter the First Time, Occurrences, and Frequency
• Allow a positive or negative offset to adjust
using either the keyboard or the statement builder
(accessed by right clicking inside the desired field). the scheduled time of arrival (e.g., appli-
cants must arrive at least ten minutes prior
4. Enter the time of the first arrival by clicking on the to their interviews).
First Time button. (See “Independent Arrivals” on
• Define a distribution to allow variability
page 158 for more information on the First Time dia-
log.) from the adjusted arrival time.
• Allow the possibility that an entity will not
5. Click on the Logic or Notes heading button to enter
arrive at all.
desired logic or notes.
• Define specific appointment types for only
certain resources or resource types.

Independent Arrivals
An independent arrival is any arrival assigned to
occur at a specific time or at a fixed interval.
Independent arrivals include such things as
 ProModel 159
User Guide

How to define independent arrivals: and time or calendar date and click the Edit
Arrival Time button.
1. Open the Arrivals module from the Build menu.

2. Click on the Entity button and select the entity type

you want to schedule.
3. Click on the Location button and select the location
where you want the independent arrival to appear.
4. Click on the Qty Each button and enter the number
of entities to arrive at the scheduled time. To model no
shows, enter the expression “Rand(1) + <probability of
showing>”. For example, if only 90% of applicants 6. In the offset field, enter any offset you wish to apply
show up for scheduled interviews, enter “Rand(1) + .9” to the arrival time. This will direct incoming appoint-
5. Click on the First Time button to open the dialog ments to arrive earlier (or later) than scheduled. For
used to define the independent arrival time for the example, if job applicants are to arrive 10 minutes
entity. If you define a block of identical appointments prior to the time of their appointment, enter “-10”
occurring at equal intervals, this is the time of the first
Offset (-10)
appointment in the block. (You may enter the arrival
time by elapsed time—since the start of the simula-
{
tion—by a weekday and time, or by calendar date.) Arrival Appointment
Time Time
Please note 9:50 AM 10:00 AM

The arrival time must match the time units 7. In the variation and offset fields of the First time
selected for the simulation run-length. If you dialog, enter any optional distribution to define the
variation from the adjusted arrival time. Generally, to
defined the elapsed time by calendar date, you
prevent the arrival from being unrealistically late, you
must also define the simulation length by calen-
should use a doubly-bound distribution (i.e., uniform,
dar date. To edit arrival times, select either day normal, triangular, or beta). The triangular and beta
distributions provide the most realistic variation.

Variation

Arrival Appointment
Time Time
9:50 AM 10:00 AM
160 Chapter 5:
Arrivals

8. In the Occurrences field of the arrivals edit table, The arrivals logic for the entity called Test1 is as
enter the number of times to repeat this appointment follows:
definition. (Enter 1 if it will occur only once.)

9. If the number of occurrences you entered is greater

than zero, enter a time interval in the frequency field.
ProModel assumes this interval to be fixed for each
occurrence (if you enter an expression, ProModel eval-
uates it only once and applies it to each occurrence).
The distribution defined in the First Arrival dialog
applies it to each occurrence.
10. In the Logic field of the arrivals edit table, enter
any attribute assignments you will use to determine the
processing of the entity. This might include the
resource or appointment type (e.g., interview) and it
will be helpful if you define these attributes before-
hand.

Arrival Logic
Arrival Logic allows you to perform certain logic
as an entity enters the system and is used prima-
rily for assigning initial entity attribute values.
Suppose you process three different types of sam-
ples at an inspection station and each sample
takes either 8, 10, or 12 minutes to test. Fifty per-
cent of the samples take 8 minutes to test, 35%
take 10 minutes, and 15% take 12 minutes.
The samples have different processing times
depending on the test performed. To differentiate
between the different types of samples, we assign
an entity attribute called Sample_Type to the
samples. We define a discrete, non-cumulative
user distribution called Test1 with the following
information:
 ProModel 161
User Guide

Shifts & Breaks View resolution selection, and a grid representing

one week of time.
Weekly shifts and breaks for locations and
resources are defined using the Shift Editor.
Shifts and breaks are defined by selecting blocks
on a grid divided into days and hours. Once a
weekly shift and break schedule have been
defined, it may be saved in a shift file with an
SFT extension.

The remainder of this section describes the Shift

Editor interface and the following procedures:
• Adding a block of time to define Work
• Adding a block of time to define a Break
• Editing Work or Break time
• Erasing Work or Break time

Main Menu
The Main menu in the Shift Editor is accessible
from the Menu button found at the top left corner
of the application.
New Start a new shift file definition. If a shift
file is already open, it will be closed. If the shift
file was modified, you will be prompted to save
the changes before it is closed.
Open Browse to open a shift file for viewing or
How to define a shift: editing.
1. Select Shifts from the Build menu.
Save Saves any changes made to the loaded shift
2. Select Define from the submenu. file. If it is a newly defined shift file, the Save As
dialog will open.
Save As Save the currently loaded shift file as a
Shift Editor different filename.

The Shift Editor window consists of a Main menu Recent Shift Files Lists the most recently loaded
button, Quick Access toolbar, Add Work, Add shift files opened in the Shift Editor.
Break and Erase buttons, a Clear All button, the
162 Chapter 5:
Shifts & Breaks

Quick Access Toolbar Please Note

The Quick Access Toolbar is found at the top left of the
application and to the right of the Main menu button. Work can be added to multiple days simulta-
The toolbar contains Save, Undo, and Redo buttons. neously by dragging the mouse across multiple
days.
View Resolution
Work and Break time can be defined down to the
nearest 5 minute interval. Other minimum time Adding a Break
resolutions can also be used such as 15 minute,
30 minute, and hourly. These are set using the 1. Click on the Add Break button to designate the
View resolution button. drawing mode (or, with the Add Work button selected,
press the Ctrl key while dragging the mouse).
The view resolution button is a drop down button
that gives four choices for setting the minimum 2. Click within a defined Work area and begin drag-
time resolution. When a time resolution is ging the mouse from the day and time the Break should
selected, the Shift Editor grid will automatically begin. Break time cannot be added to an area in the
adjust and only allow Work or Break time to be shift where Work is not defined.
defined to that nearest resolution. 3. Release the mouse button at the day and time the
Break should end.
For example, if the View resolution was set to 30
minutes, Work or Break time could only be
drawn to the nearest 30 minute period..
Editing Work or Break Time

Adding, Editing Work and Break 1. Select the Add Work or Add Break button (or, if
adding break time, select the Add Work button and
Time then press the Ctrl key while dragging the mouse).
2. Add Work or Break time to the beginning or end of
Adding Work existing Work or Break time by clicking and dragging
the mouse on the grid.
1. Click on the Add Work button to designate the 3. Removing Work or Break time is accomplished
drawing mode. using the Erase button. (See Erasing Work or Break
2. Click and begin dragging the mouse from the day Time)
and time on the grid the work should begin.
3. Release the mouse button at the day and time the Please Note
work should end.
Break time can be added to multiple days simul-
taneously by dragging the mouse across multiple
days.
 ProModel 163
User Guide

Erasing Work or Break Time processing location, where the employee will be
requested at the appropriate priority level.
1. Select the Erase button (or, with the Add Work but- There are many ways to use shift assignments
ton selected, right-click and drag the mouse). and shift logic to solve any number of problems
2. Erase Work or Break time by clicking and dragging in creating a valid model. This chapter explores
the mouse on the day and time in the grid where Work the features and functionality of the Shift Assign-
or Break time should begin to be removed. ments module, including statements and func-
3. Release the mouse at the day and time the Work or tions for shift and break logic.
Break time should stop being erased.
Assigning Shifts
ProModel allows you to can select multiple loca-
Shift Assignments tions and resources and assign them to a shift in
one record. Plus, you can:
The Shift Assignment module allows you to
• assign a location or resource to multiple shift
model everyday, real-life situations involving
scheduling and availability issues, and you can files with a start time for each shift,
easily define logic to control the way your model • define off-shift and break priorities, and
handles these problems. • create off-shift and break logic.

If you have an employee that works a split shift, The Shift Assignments module allows you to
assign two shifts to the resource with the corre- schedule the availability of resources and loca-
sponding start times. If you have a processing tions based on shifts and work breaks defined in
location that can only be used during specifically the Shift Editor. When a location or resource goes
scheduled hours, set up a separate shift for that off shift or on break, it is off-line or off-duty and
location. is reported in the output statistics as non-sched-
uled time rather than downtime.
You may have an office or some other operation
just starting up, and you need to run a specific The off-shift and break logic are optional and
shift for the first week and another for two more allow you to control more precisely when a
weeks before going to your full capacity shift
schedule. Simply set up three shifts and assign
them all to the office in one step, indicating the
appropriate start times for each.
If you want to establish a controlled location
gateway: Among fulfilling other duties, your
employee needs to begin doing something (pro-
cessing a certain entity at a certain location) at a
certain time, so you set up a queue location, a
gate location (with a capacity of one), and a pro-
cessing location. Assign a shift to the gate loca-
tion so it will come on line at the designated time.
Now the gate location begins taking the entities
from the queue location and moving them to the
164 Chapter 5:
Shifts & Breaks

resource or location may go off shift, on break, ing on a location also selects or removes it. Click OK
and how long before it becomes available again. when finished.

3. Select Resources - Click on the Resources button to

display the Select Resources dialog (shown next).
Click on a resource and use the buttons to select or
remove it from the Shift Resources list. Double-click-
ing on a resource also selects or removes it. Click OK
when finished.
When you select Shifts from the Build menu, two
options are displayed: Define and Assign. You
must define a shift before you can assign a
resource or location to it.

How to assign locations and resources

to shifts:

1. Select Shifts from the Build menu, then click on

Assign. ProModel displays the Shift Assignments edit
window shown below.

4. Units Enter the specific units of the selected

resource to be assigned to the shift. You may assign
one, several, or all units of a resource to a shift. You
can also use a macro to specify the units. If left blank,
2. Select Locations - Click on the Locations button to ProModel assigns the default of All units to the shift.
display the Select Locations dialog (shown below).
Click on a location and use the buttons to select or 1,3 Units 1 and 3 only
remove it from the Shift Locations list. Double click-
1-3,5 Units 1 through 3 and 5 only

All All units of the resource

None You may use none to indicate that no

unit will adopt this shift. This is useful in
 ProModel 165
User Guide

creating a run-time interface. By using a resource or location back on line. You can also use
macro to represent the number of units, the macros to specify priorities.
user may select none as an option.
Macro The name of a run-time interface
macro that allows the user to define the units
to be affected by the shift.
5. Select Shift Files - Click the Shift Files button to
display the Select Shift Files dialog (shown next).
Click on the Add button to display the File Open dialog
and select the shift files you want to use in the model.

These priorities follow standard ProModel prior-

ity level and preemption rules. (See “Locations”
6. Define Start Times - Enter the start time for each of on page 90, “Entities” on page 112, and
the selected shift files. The value will be interpreted “Resources” on page 126).
according to the time units specified in the General
Priority for Ending Shift This is the priority for
Information dialog unless a unit label is entered after
the value (e.g., 10 hr). You can also use a macro to regularly ending the shift. An entity or downtime
specify the start times. If the Start time is left blank, the must have a higher priority level to prevent this
shift will begin at the start of the simulation. All shifts location or resource from going off shift at the
specified apply to the locations and resources selected preset time.
for these shifts in the Shift Assignment record.
Off Shift Priority This is the priority for the loca-
During the simulation, the shift with the earliest start tion or resource to stay off shift. In other words,
time remains in effect for the locations and resources an entity or downtime must have a higher priority
listed until the next start time encountered activates a level to bring this location or resource back on
new shift. line before the preset time.
7. Define Priorities - Click on the Priorities button. Priority for Starting Break This is the priority for
The Priorities button allows you to enter the priorities going on break. An entity or downtime must have
for going off line due to a break or end-of-shift as well a higher priority level to prevent this location or
as the priorities of the off-line state in the event that resource from going on break at the preset time.
some other activity attempts to bring a particular
Break Priority This is the priority for staying on
break during the break period. In other words, an
entity or downtime must have a higher priority
level to bring this location or resource back on
line before the end of the preset break.
166 Chapter 5:
Shifts & Breaks

Shift & Break Logic How to determine the sequence of

Shift and break logic are optional and are defined events
in four distinct logic windows, each executed in a
specific sequence throughout the simulation run. 1. When a location or resource is scheduled to go off
You can define logic to control how resources line due to a break or the end of a shift, the pre-logic
and locations go off line and what happens once for that particular location or resource is executed.
they are off-line. 2. After executing the pre-logic, which may contain
conditional (WAIT UNTIL) or time (WAIT) delays,
To define shift or break logic, click on the Logic the location or resource is taken off line, assuming it is
button to display a submenu of four events asso- either available or the priority is high enough for pre-
ciated with shifts for which logic may be defined. emption.
Selecting an event from the submenu displays a
3. At the instant the location or resource is taken off
standard logic window. You can enter separate
line, the Off-Shift or Break logic is executed.
logic for each of these four events to be executed
when the event occurs. See the following discus- 4. After executing this logic, the location or resource
sion, Sequence of Events. waits until the time defined in the shift file expires
before going back on line.

Please note

If the off-shift and break nodes are not specified

You may want to use the Logic Builder to help in the Resource Specs dialog, the resource will
you enter the logic. Just click on the Build button stay at the current node. If no resources or loca-
in the logic window. tions are assigned to a shift, the shift is ignored.
Pre-Off Shift or Pre-Break Logic Executed when-
ever the location or resource is scheduled to go
off shift or on break. This occurs before the loca-
Functions and Statements
tion or resource is checked for availability, so it is
executed regardless of availability. This logic ProModel uses several functions and statements
may be used to check certain conditions before specifically for shift and break logic: SKIP, PRI-
actually taking the resource or location off line. ORITY, DTLEFT(), FORLOCATION(), and
The logic is executed for each resource and loca- FORRESOURCE(). Following is a brief descrip-
tion listed as members for this shift assignment tion of each. For more details, see “Statements
record. This allows some members to be taken off and Functions” on page 429.
line while others may be forced to wait. (Pre-off SKIP If used in pre-logic, it causes the off-shift
shift and pre-break logic may be referred to in or break time (including any off-shift or break
this manual as pre-logic when speaking of either logic) to be skipped so a location or resource
one.) never goes off line. If used in the off-shift or
Off Shift & Break Logic Executed at the instant break logic, it causes the off-line time defined in
the location or resource actually goes off line. the Shift Editor to be skipped. This allows you to
 ProModel 167
User Guide

specify a WAIT statement for the off-line time Pre-off shift logic
and SKIP the off-line time defined in the Shift
Editor. IF FORRESOURCE() THEN
PRIORITY This statement provides an alterna- BEGIN
tive way to specify off-shift or break priorities. It
IF RESOURCE() = Loan_Officer THEN
also allows the priority to be changed after some
time being off-shift or on break. If the priority is BEGIN
changed to a value lower than the current value, WAIT UNTIL Applications = 0
the system will check to see if any preemption
END
may occur at that time. This statement is not
allowed in off-shift or break pre-start logic. END

DTLEFT() This function returns the remaining

off-shift time based on when the location or
resource is scheduled to go back on shift as In addition to these functions, DTDELAY() may
defined in the shift file. It may be used in off-shift also be called at the beginning of the off-shift or
and break logic to adjust the actual time the loca- break logic to determine how much time has
tion or resource is off-line. elapsed between the time the shift downtime was
scheduled to start and when it actually started.
FORLOCATION() This function returns TRUE
The length of the shift downtime defined in the
if the member for which the shift or break logic
shift file would be the sum of DTDELAY() and
being executed is a location. This may be fol-
DTLEFT().
lowed by a test using the LOCATION() function
to determine the precise location.
Preemptions to Off-Shift or Break
FORRESOURCE() This function returns TRUE
Logic
if the member for which the shift or break logic
being executed is a resource. The RESOURCE() If off-shift or break logic is defined using WAIT
function may then be used to determine the pre- or USE statements and happens to get preempted,
cise resource if multiple resources are listed as the logic will resume one statement after the
members. WAIT or USE statement where it was preempted.
RESOURCE() This returns the name-index num-
ber of the resource currently processing the off- Shift Downtime Principles
shift or break logic.
To illustrate how FORLOCATION() and FOR- Locations Shift Downtime Principles
RESOURCE() might be used, consider the fol-
It is important to understand that when a location
lowing example: Suppose you have locations and
or resource goes off shift, it is essentially down.
resources as members in a shift file assignment
We call this type of downtime a shift downtime
and you want to wait until variable Applications is
and it is treated slightly differently from other
equal to zero before allowing a particular
downtimes. Breaks, which are also part of the
resource called Loan_Officer to go off shift. You
shift schedule, are treated exactly like clock-
would enter the following pre-off shift logic:
based downtimes. These downtimes are dis-
168 Chapter 5:
Shifts & Breaks

cussed in “Locations” on page 90 and Example 1 (b)

“Resources” on page 126.
Entity Entity
Shift Downtimes for Locations
All location shift downtimes have a default prior- Shift DT
ity of 99, the highest non-preemptive priority
possible. This means that when a location is
scheduled to go off-shift, this downtime will take
priority over all other entities with a priority less Actual DT
Time
than 99 waiting for the location. If the location is
currently in use, shift downtimes allow the cur-
rent entity to complete its process at the location. T1 T2 T3 T4 T5
After the entity is finished, the shift downtime
proceeds as if it started at its scheduled time. This
means that the location becomes available at the Please note
start of the next shift regardless of when it actu-
ally went off shift. This procedure is demon- Since the entity was preempted, the remaining
strated in the following example. time for the entity to be processed at the location
was completed after the location shift downtime
Example 1 (a) was completed.

Entity

Preempting Off-Shift Locations

Shift DT
An off-shift location may be preempted back into
service by an entity. Following the preemption,
the shift downtime will resume for any remaining
Actual DT time before the start of the next shift. The follow-
Time ing example demonstrates this principle.

Example 2
T1 T2 T3 T4
In this example an entity with priority of 200 or
Although the downtime is scheduled to last from greater preempts an off-shift location. The loca-
time T2 to T4, the actual downtime does not tion becomes available to process the entity.
begin until time T3. This is what happens for
both locations and resources currently busy when
the shift downtime is scheduled to occur.
To preempt a location in which an entity is cur-
rently processing, set the priority for going off
shift to a number one level higher than the
entity’s priority.
 ProModel 169
User Guide

Once processing is complete, the location returns tion remains off-shift for the total duration of the
to its off-shift status. shift downtime.

Shift DT
Shift DT

DT
Entity

Time
Time

T1 T2 T3 T4
T1 T2 T3 T4

In order for an entity to preempt any location The example above could represent the situation
downtime (shift or otherwise), it must have a pri- where a recurring downtime, such as a lunch or
ority level that is at least 2 levels higher than the dinner break, has been defined for a single loca-
downtime's priority. In this example the location tion that is scheduled to be available for a two-
shift downtime has a priority level of 99 so the shift period. It would be simpler to specify a sin-
entity must have a priority level of 200 or greater gle downtime for lunch and dinner that occurs
to preempt the shift. once every 8 hours continuously than to define
separate downtimes for lunch and dinner. In this
Overlapping Downtimes case the preempting downtime would represent a
meal break occurring while the location was off-
If a preemptive clock downtime occurs during a
shift.
shift downtime, the downtimes simply overlap.

Example 3 Resource Downtime Principles

This example shows the effect of a preemptive Shift Downtimes for Resources
downtime occurring for a location already off-
shift due to a shift downtime. Because location Resource shift downtimes work exactly like loca-
downtimes always overlap, the effect is as if the tion shift downtimes with the exception that if the
preemptive downtime never occurred. The loca- off-shift downtime is preempted by some other
downtime, the original off-shift downtime never
resumes. The following examples show how a
resource that is off shift is affected by a preemp-
tive request by another entity (example 1) and by
downtime preemption (example 2).

Example 1
Suppose a resource, repairman, is off-shift. An
important machine goes down unexpectedly.
Because this machine is a bottleneck in the opera-
170 Chapter 5:
Shifts & Breaks

tion, it is vital to repair the machine as quickly as it would have been had the original shift down-
possible. The repairman is called in and takes 30 time been completed.
minutes to fix the machine. The logic for the
downtime to call him back is “USE Repairman,
Shift
600 FOR 30 min”. This will preempt the shift
downtime and use the repairman to repair the Discontinued
machine even though the repairman is off-shift.
Once the repairman has repaired the machine, he DT
returns to his shift downtime until he is scheduled
to go back on shift. The repairman's shift down- Time
time will end at the originally scheduled time
regardless of the fact it was preempted by a repair
activity. T1 T2 T3 T4

Although in practice, situations like the example

Shift DT
above are unlikely to occur, it is important to
Discontinued understand that the above condition is possible.
Typically, preemptive downtimes are due only to
Task
some type of location or resource failure, in
which case, the downtime occurrence would be
based on usage and not clock time. If a preemp-
Time
tive downtime is based on usage, the situation in
the example above could not occur because the
T1 T2 T3 T4
location or resource would not be in use, and
would not accumulate usage time.
Although the shift downtime is scheduled to last
from time T1 to T4, the actual downtime lasts
from T1 to T2 and then from T3 to T4.

Example 2
This example shows the effect of a preemptive
downtime occurring for a resource already off-
shift due to a shift downtime. Since resource
downtimes are not overlapping, as in the case of
location downtimes, the shift downtime in
progress is discontinued and the preemptive
downtime takes control of the resource because it
has a priority greater than or equal to five-hun-
dred (remember that a downtime priority needs to
be only one level higher than another downtime
priority to preempt it). The effect in this example
is that the total downtime is actually shorter than
 ProModel 171
User Guide

General Information General Information Dialog Box

The General Information dialog box allows you
to specify basic information about a model, such
as its name, default time units, default distance
units, and graphic library. You also may specify
the model's initialization and termination logic.
Finally, a notes window is available for specify-
ing particulars of a model, such as the modeler's
name, the revision date, modeling assumptions or
anything else about it.

The fields of the General Information dialog box

are as follows:
Title An optional, brief description of the model.
Information will be displayed in the caption bar
and included in the model and results files.
Time Units The unit for any time value in the
model that does not have an explicitly specified
time unit. The smallest unit of time available in
ProModel is .00001 second and the largest is 1
day.
Distance Units The units in feet or meters for all
distances specified in the model. There is no
practical limit on the size of the model.
Model Notes... Brings up a notes window for
specifying general notes about the model. Notes
are optional and are for user reference only. An
alternative way to display notes is using a DIS-
PLAY statement (see “Display” on page 457) in
the initialization logic.
How to open the General Information
Graphic Library File Opens a dialog box for
dialog box:
selecting the graphic library file to use with the
open model. Graphics library files have the
• Choose General Information from the Build menu.
extension GLB and are further explained later in
this section.
Initialization Logic Opens the Initialization
Logic window for specifying initialization logic.
An asterisk (*) next to the name of the button
means that some initialization logic has been
172 Chapter 5:
General Information

defined for the model. (See “Initialization Logic” Termination Logic

on page 172.)
Termination logic allows you to summarize data
Termination Logic Opens the Termination Logic or write special statistics to an output file at the
window for specifying termination logic. An end of a simulation run as shown below:
asterisk (*) next to the name of the button means
that some termination logic has been defined for
the model. (See “Termination Logic” on
page 172.)

Initialization Logic
Initialization logic allows you to initialize arrays,
variables, and other elements at the beginning of
a simulation run as shown below:

Other common uses of termination logic include:

• Displaying messages
• Resetting read/write files
See the following page for a discussion on the
placement of initialization and termination logic
within the sequence of run-time events.

Please note
Other common uses of initialization logic
include: Although Initialization and Termination logic
• Reading external files cannot be tested with the Compile option in the
• Displaying messages Edit menu, as with Processing or Arrival logic,
• Prompting for values
the logic can be tested by clicking on the compile
button in the logic window. ProModel checks all
• Resetting general read/write files
logic automatically upon selecting OK and, if an
• Activating independent subroutines that pro-
error in the logic is found, an error message
cess logic based on a timer. (See “Subrou-
describing the problem will appear.
tines” on page 238; also see “Activate” on
page 431).
For a discussion of each of the buttons in the Ini-
tialization Logic window, see “Editing Logic Execution Time of Initialization and
Windows” on page 72. Termination Logic
It is important to understand exactly when initial-
ization and termination logic is executed. When
 ProModel 173
User Guide

you select Run from the Simulation menu the fol- logic. The model structure cannot change after
lowing things occur in the order listed: the model has been loaded into the simulation
module. Thus, any variable or array figuring into
1. Arrays are initialized based upon the defined
a location's capacity and initialized in the initial-
Import specifications
ization logic will be initialized too late to affect
2. Variables are initialized to the values speci-
the location's capacity.
fied in the Variables Editor.
3. Macros with a run-time interface are set to Variables or arrays which do not figure into a
their user-specified value. location's capacity may be initialized in the Ini-
4. The model is loaded into the simulation tialization Logic without any problem. A variable
module. As the model is loaded, any numeric initialized in the initialization logic could be used
expressions used to define such things as as the “First Time” for an arrival or downtime
location capacities or number of resource occurrence. This is true because arrivals and
units are evaluated and assigned a numeric downtime occurrences are simulation events, and
value. all initialization logic occurs before the first sim-
5. Initialization logic is performed. ulation event.
6. Simulation begins. Initial arrivals and down-
times are scheduled and simulation pro- Graphic Library File
cesses begin.
7. Simulation ends. ProModel allows you to create and store as many
8. Termination logic is performed. graphics libraries as desired. However, only one
9. Statistics are compiled. graphic library may be used for each model. To
copy a graphic from one graphic library to
Logic elements that figure into a model's struc- another model's graphic library, see “Copying a
ture are evaluated only when the model is loaded Graphic from One Library to Another” on
into the simulation module. Those logic elements page 308.
are:
• Simulation warm-up hours How to select the desired graphics
• Simulation run hours library:
• Node capacity
• Length of path segments 1. Select Graphic Library File from the General
• Resource units Information dialog box.
• Location capacity
• Queue length
• Conveyor length
• Conveyor speed
For a complete list of when each field is evalu-
ated, see the “Appendix A” on page 577.
Any variables or arrays used in an expression that
change any of these logic elements should be ini-
tialized in the Variables Editor, Arrays Import, or
run-time interface and not in the initialization
174 Chapter 5:
General Information

2. Enter the name of the desired graphics library.

3. Select OK.

Please note

Only files with the extension GLB may be used as

graphics libraries. For more information on cre-
ating, merging and saving graphics libraries, see
“Graphic Editor” on page 304.
 ProModel 175
User Guide

Cost Model evaluates expressions in these fields only

during translation at run time. The General Statis-
With ProModel’s costing capability, you can tics Report includes statistical information auto-
make decisions about your system on a cost matically generated during run time about cost
basis. Costing dialogs allow you to monitor costs for locations, entities, and resources.
associated with Locations, Entities, and
Object Type Use this pull-down menu to define
Resources during a model run and the General
costing for the components of the selected object
Statistics Report includes Costing statistics, auto-
type. Object types include locations, resources,
matically generated at the start of the simulation.
and entities as shown in the following example.
All defined model components of the selected
type appear in the box below the object type field
and ProModel allows you to assign costs to any
of these components.

Locations

Operation Rate This field specifies the cost per

unit of time to process entities at the selected
location. Cost accrues only while an entity exe-
cutes a WAIT or USE statement in operation
logic. ProModel accepts expressions in this field
and evaluates them at translation.
How to use cost

• Choose Cost from the Build menu. The Cost Dialog

appears.

Cost Dialog Box

Use the Cost Dialog box to define costs for Loca-
tions, Entities, and Resources. Fields in the Cost
Dialog box vary between Object Types and Pro-
176 Chapter 5:
Cost

Per With this pull-down menu, you can set the cost applies to the resource only when it returns
time units for the Operation Rate. Time units may to the entity.
be in seconds, minutes, hours, or days as shown
here.

Entities

Resources

Initial Cost This field allows you to define the

initial entity cost for an entity which enters the
system through a scheduled arrival, a CREATE
statement, or an ORDER statement. ProModel
Regular Rate This field specifies the cost per unit accepts expressions in this field and evaluates
of time for a resource used in the model. You can them at translation.
use expressions in this field (evaluated at transla-
tion) to set the rate or change it using SetRate. Please note
For more information on the SetRate operation
statement, see “SetRate” on page 546. When you implicitly create new entities through a
Per This pull-down menu allows you to set the
ROUTE statement, ProModel does not add an
time units for the Regular Rate. Times may be in initial cost to the entity. To add an initial cost, use
seconds, minutes, hours, or days as shown here. the INCENTCOST statement. See “IncEntCost”
on page 489 for more information.

Building a Model with Costing

Cost Per Use This field allows you to define the
actual dollar cost accrued each time you use the When you build a model using the costing fea-
resource (i.e., the minimum usage cost). The cost ture, you must first define the locations,
per use updates when you obtain the resource and resources, and entities used in the model. Once
ProModel accepts expressions in this field (eval- you define these model components, you may
uated at translation). assign costing information to them through the
Cost option in the Build menu. To collect costing
Please note information about your model, uncheck the dis-
able costing box from the simulation options dia-
log of the simulation menu. By default, ProModel
Since ProModel counts a preemption as a use, if
you preempt a resource from an entity, the usage
 ProModel 177
User Guide

disables costing and sets all defaults to zero. See both entities. If the preempting entity
“Enable or Disable Costing” on page 179. obtains a resource, the preempted entity
will not record the resource costs during
the preemption period.
• If an entity is at a location when a preemp-
tive downtime occurs, the entity records
the downtime as part of its operational
costs. This applies to all types of location
downtimes, including shifts. The location
records the cost of the preempted entity
while it remains at the location.
• If an entity’s resource has a downtime which
requires the use of another resource, the
entity will not record the second resource’s
cost. However, the location will record the
extra resource’s cost.

Join/Load
• Joined and permanently loaded entities add
their costs to their base entities, but not
their time statistics.
• Loaded entities do not add their costs or time
Please note statistics to their base entities.
• When an UNLOAD occurs, ProModel
The following scenarios assume you defined costs divides all costs accrued by a loaded entity
for all model components. among the unloaded entities. ProModel
adds all other entity statistics calculated
during the loaded period to each of the
unloaded entities.
• Entities leaving the system that were tempo-
Preemption/Downtime rarily loaded onto other entities do NOT
• If you preempt an entity’s resource, an addi- report their individual costs, but do report
tional cost per use will apply once you re- all other statistics. To get the cost of each
acquire the resource. While waiting for the entity, you must unload the entities before
resource to return, the entity does not they exit or permanently load them when
record operation or resource costs. they are initially loaded using the LOAD
• If an entity preempts another entity, the pre- PERM statement.
empted entity continues to record opera-
tion time during the entire preemption
period. While the preempting and pre- Combine/Group
empted entities are simultaneously at a • Combined entities add their costs to the
location, the location records the cost for resultant entity, but not their time statis-
178 Chapter 5:
Cost

tics. The resultant entity begins with fresh • The SPLIT AS statement divides the cost of
time statistics. the original entity between all entities.
• Grouped entities do not add their costs or Each new entity begins with new time sta-
statistics to the group shell (a temporary tistics.
entity representing grouped entities that
starts with cost and time statistics of zero).
• When an UNGROUP occurs, ProModel
Costing Output Statistics
divides all costs accrued by a grouped ProModel collects costing statistics only if you
entity among the ungrouped entities. Pro- uncheck the Disable Cost Statistics option in the
Model copies all other entity statistics cal- Simulation Options menu (see “Enable or Dis-
culated during the grouped period to each able Costing” on page 179). Included in the Gen-
of the ungrouped entities. eral Statistics Report, ProModel calculates
• Entities leaving the system grouped with costing statistics.
other entities do NOT report their individ-
ual costs, but do report all other statistics. Locations
To get the cost of each entity, you must • Operational Cost = (Active Operation Time
ungroup the entities before they exit. * Rate) + (Any IncLocCost)
• % Operational Cost refers to the location’s
Special Cost Handling percentage of the sum of all operation
costs
• As soon as you acquire a resource, it begins • Resource Cost = (Utilization * Rate) +
to accrue cost. (Times Used * Cost per use)
• Unless obtained in the move logic, ProModel
charges the “Cost per use” for a resource
Please note
to the location that obtained it. Resources
obtained in the move logic do not charge a
“per use” cost to any location. For Resource Cost, Utilization and Times Used
refer to the utilization of a resource while at a
• ProModel does not charge any resource time
location. This applies only to resource use
used during move logic to any location.
through operation logic.
• ProModel adds initial entity costs defined in
the cost module only as entity costs, not
location costs.
• If a location uses a resource during a down- • % Resource Cost refers to the location’s per-
time, the location accrues that resource’s centage of the sum of all resource costs
cost.
• Total Cost = (Operation Cost + Resource
• The USE statement counts as operation and Cost)
resource cost.
• % Total Cost refers to location’s percentage
• When you CREATE a new entity, it begins of the sum of all location costs
with new time statistics and an initial cost.
• If you RENAME an entity, previous time Resources
statistics and costs continue with the
• NonUse Cost = (1-% Utilization) * Sched-
entity.
uled Time * Rate
 ProModel 179
User Guide

• % NonUse Cost refers to the resource’s per- • % Total Cost % Total Cost refers to the
centage of the sum of all nonuse costs entity’s percentage of sum of all entity
• Usage Cost = (% Utilization * Scheduled costs
Time * Rate) + (Times Used * Cost per In the above calculations, the rate defined (per
use) day, hour, minute, and second) converts to the
• % Usage Cost refers to the resource’s per- default time units specified in the General Infor-
centage of the sum of all resource usage mation dialog.
costs
• Total Cost = Usage Cost + NonUse Cost In the above calculations, the rate defined (per
day, hour, minute, and second) converts to the
• % Total Cost refers to the resource’s percent-
default time units specified in the General Infor-
age of the sum of all resource costs
mation dialog.
Entities
• Explicit Exits The number of entities that Please note
have explicitly exited. Whenever an entity
exits the system, it is an explicit exit ProModel does not allow you to generate a Cost-
except in the following cases: ing Graph. However, if you set a variable equal
- When an entity JOINS, permanently to GetCost (e.g., Var1=GetCost), you can gener-
LOADS, or COMBINES with another ate a time series graph to track changing entity
entity, it implicitly exits the system, and costs. See “GetCost()” on page 478 for more
is reported as an exit in the Entity Activ- information.
ity report. However, for costing pur-
poses, the entity did not explicitly exit,
but its costing information was added to
the entity it was JOINED, permanently Enable or Disable Costing
LOADS, or COMBINED with.
- When an entity temporarily LOADS or To enable the costing feature, be sure that the
GROUPS with another entity, and the Disable Cost option in the Simulation Options
entire LOADED or GROUPED entity dialog is not checked.
exits the system, the original entity
implicitly exits the system, and is
reported as an exit in the Entity Activity
report. However, for costing purposes,
the original entity did not explicitly exit,
but its costing information was added to
the entire load or group.
• Total Cost Dollars Total Cost = cumula-
tive entity cost, or the sum of costs
incurred on all locations the entity passed
through + the sum of all costs incurred by
use of resource + initial cost + any IncEnt-
Cost
180 Chapter 5:
Tanks

Tanks Please note

Tanks are simply locations to which ProModel When you create the first tank in your model,
associates a level instead of an entity routing. (As ProModel will display a dialog that allows you to
a result, the units and rules fields do not apply to automatically import various subroutines, arrays,
tanks.) Using tanks, you can model the continu- macros, and library graphics specific to tanks. If
ous flow of liquids and other substances into and you do not wish to include these new items, you
out of tanks or similar vessels. Also, when com- may cancel the action.
bined with discrete-event simulation, ProModel’s
continuous modeling capability makes it possible
to model the exchange between continuous mate-
rial and discrete entities (e.g., when you place liq- 3. Enter a capacity (1 to 999999) for the tank in the
uid into a container). Other uses include location capacity field.
modeling high-rate, discrete part manufacturing
4. Define and reference any necessary tank control
systems. subroutines.

The Tank Submodel

In order to function properly, all tank models
How to edit a tank or a gauge
should include the tank submodel (TANK-
SUB.MOD). The tank submodel contains impor-
1. Double click on the tank or gauge (or right click and
tant subroutines and data elements (arrays and
select Edit Graphic).
macros) used to simplify tank modeling. Each of
these subroutines and data elements has a 2. From the dialog that appears, make the appropriate
“Tank_” prefix to help identify it and to prevent changes.
any accidental name duplication. 3. Click OK.

Please note

All user-defined model elements should begin

with something other than “Tank_”.

How to define a tank

1. Select the gauge/tank symbol from the Location

Graphics window.
2. Click on the layout window where you wish to
place the tank and select Create Tank Location from
the menu that appears. ProModel places the tank on the
layout.
 ProModel 181
User Guide

How to change between a tank and a Subroutine module. To call these subroutines and
gauge operate them independently in the model, use the
ACTIVATE statement. For examples of how to
use these subroutines, see the discussion at the
• Double click on the tank or gauge and check or
uncheck the tank option. end of this section. To model tanks effectively,
you must understand the following concepts.

or... Tank Levels

ProModel records tank levels in a pre-defined
array called Tank_Level where each element of
• Right click on the tank or gauge and select Change
Tank to Gauge or Change Gauge to Tank. the array corresponds to each tank location in the
location list. For example, the level of TankA is
the value of Tank_Level [TankA]. If TankA were
the third location in the location list, you could
In addition to defining a tank graphic, you may also reference the level of TankA with
add labels and other figures to a tank. For exam- Tank_Level[3]. For best results, you should con-
ple, you can add a counter to digitally display the trol all tank levels using only the pre-defined tank
fill level of the tank (ProModel rounds the value filling and emptying subroutines rather than
displayed to the nearest integer). The following change the Tank_Level array values directly. This
are examples of how you can use tanks in Pro- will prevent overfilling or overdrawing and will
Model. accurately gather statistics for each tank. For
example, calling Tank_Fill (TankA, 500, 30, 0)
automatically fills TankA to 500 units at a rate of
30 units per minute. The 0 signifies that the tank
will not accept excess material and, as a result, an
error message will occur if the tank reaches
capacity before the specified amount fills into the
tank.

Basic Concepts
Since tanks do not process discrete entities, you
may not define routings to or from tanks. To con-
trol a tank level, ProModel provides predefined
subroutines that fill, empty, and transfer tank con-
tents. To monitor tank levels and initiate flows,
you must define control subroutines using the
182 Chapter 5:
Tanks

The Flow Time Step flow. The units of flow, however, may change
when you move material from one tank to
To model continuous flow, ProModel uses a another (e.g., pounds of dry material may transfer
Tank_TimeStep macro. This macro is the time into a tank containing gallons of liquid).
step used when filling/emptying tanks and is an
RTI (run-time interface) parameter. Initially, Pro- To specify a variable rate of flow that changes
Model sets this value to .2 minutes. If you wish to dynamically with each time step, pass a value of
use a different value for the time step, you may 0. This signals the subroutine to call the
change it temporarily (for a particular model) Tank_Rate subroutine with each time step. To
through the Simulation/Parameters menu option, return the desired rate value for each time step
or permanently by changing the macro itself. The when you use a variable rate, you must modify
larger the time step, the longer the interval the Tank_Rate subroutine appropriately.
between filling and emptying (which speeds up
the simulation). For example, suppose you set the Tank States
time step to .1 minutes. If a tank empties at a rate
of 60 gpm, the simulation would actually empty Like other model elements, tanks use states to
the tank by a discrete amount of 6 gallons every test and track statistics. ProModel automatically
.1 minutes. When filling or emptying a tank, if sets these states when you use the predefined tank
the remaining quantity doesn't require the full subroutines to control the tank. The following are
time step, ProModel reduces the time step using a defined states:
linear interpolation. Tank_Idle The tank is empty and not in use. Set
automatically when a tank empties and at the end
Please note of a Tank_DoPrep or Tank_GoDown subroutine.
Tank_Operation The tank is active (e.g., mixing,
The only adverse effect of using a large time step reacting, heating). Set automatically when the
is that any WAIT UNTIL statement or other test model calls the Tank_DoOperation subroutine.
based on the Tank_Level array may be off by as
much as the flow amount for the time step. For Tank_Setup The tank is cleaning or preparing for
example, if the time step is .5 minutes and the rate future use. Set automatically whenever you call
of flow is 60 gpm, the level will change in 30 gal- the Tank_Prep subroutine.
lon increments. This means that the tank will not Tank_Filling The tank is filling. Set automati-
satisfy the statement “WAIT UNTIL cally whenever you fill the tank.
Tank_Level[TankA]>=31” until the level reaches
60. Tank_Emptying The tank is emptying. Set auto-
matically whenever you empty the tank.
Tank_Blocked The tank is full and ready to
transfer. Set automatically when the tank fills to
Rate of Flow capacity.
To use flow rates properly, you must define all Tank_Down The tank is down. Set automatically
rates in terms of units (i.e., gallons, pounds) per whenever you call Tank_GoDown.
time unit defined in the General Information dia-
log. Whenever you call one of the empty, fill, or
transfer subroutines, you must specify the rate of
 ProModel 183
User Guide

Tank_ScheduledDown Similar to the SKIP example

Tank_Down state, except statistics are not col-
lected. Tank_GoDownSched (<TankID>, DTLeft())
While ProModel sets these states automatically, SKIP
you may change the state of the tank at any time
by calling the Tank_SetState subroutine. Pro-
Model records statistics for these states in the
ProModel temporarily suspends tank flow while
output report under Locations. Since a tank may
a tank is down or off shift.
fill and empty simultaneously, the output report
combines Tank_Filling with Tank_Emptying and
reports it all as waiting time. Tank Logic Builder
An expanded capability within ProModel, the
Over Filling/Emptying Tanks tank logic builder provides you with what you
When using the predefined subroutines to fill, need to model complex tank and fluid system
empty, or transfer from one tank to another, you operations. The logic builder contains all avail-
may accidentally attempt to over fill or over able tank subroutines and provides you with a
empty a tank. To prevent these situations, you description of the components required to use
have the option to terminate the fill/empty sub- each subroutine.
routine or suspend further filling/emptying until
the tank reaches a resume level. If you terminate
the subroutine, ProModel temporarily stores the
un-filled or un-emptied quantity for immediate
access in the global variable, Tank_QtyLeft.

Tank Downtimes
For Tanks, you must define downtimes and shifts
in a special way. First, you may define only clock
downtimes for tanks. Second, when defining a
clock downtime for a tank, use the
Tank_GoDown subroutine (page 193) in the
Downtime Logic field instead of just a WAIT
statement. This sets the state of the tank to
Tank_Down and gathers the appropriate statis-
tics. Third, when defining a shift for a tank, you
should call the Tank_GoDownSched subroutine
in the off-shift logic using the DTLeft() function
as the time parameter. A SKIP statement should
follow this function as shown next.
184 Chapter 5:
Tanks

Please note

The subroutine logic is not accessible until you

define your first tank location—when you define
the tank location, ProModel loads the tank sub-
model.

How to access the Logic Builder:

• Click the right mouse button in the logic window or

expression edit field. Or click the Build button on the
logic window’s toolbar.

For more information about the Logic Builder,

see “Logic Builder” on page 285.
 ProModel 185
User Guide

Pre-defined Tank Subrou- TANK_FILL (HoldingTank, 2000, 75, 1500)

tines
Tank_Cap ............................................... page 192 Description
Tank_Dec ................................................ page 190 Fills a tank using a specific quantity and rate. The
Tank_DoOperation .................................. page 193 default tank state sets to Tank_Filling, then to
Tank_Blocked if the tank becomes full.
Tank_DoPrep .......................................... page 195
Use Tank_Fill when the source of the material is
Tank_Empty ........................................... page 186 not another tank, but an arriving entity or a
Tank_FallTrigger .................................... page 191 source that is not part of the model.

Tank_Fill ................................................. page 185

Components
Tank_FreeCap......................................... page 192
<Tank ID>
Tank_GoDown ........................................ page 193
The tank name or location index number.
Tank_GoDownSched ............................... page 194
<Fill Quantity>
Tank_Inc ................................................. page 190
The number of units (gallons, pounds) to fill into the
Tank_Rate ............................................... page 199 tank. To fill the tank to capacity, enter
Tank_Cap(<Tank ID>).
Tank_RiseTrigger .................................... page 191
<Fill Rate>
Tank_SelectInput .................................... page 198
The rate in units (gallons, pounds) per time unit
Tank_SelectOutput .................................. page 196 defined in the General Information dialog. To
instantly increase the level of a tank, use the Tank_Inc
Tank_SetLevel ......................................... page 189
subroutine. To initialize the level of a tank (e.g., at the
Tank_SetState ......................................... page 196 start of the simulation), use the Tank_SetLevel subrou-
tine. To use a dynamically calculated rate in the
Tank_Transfer......................................... page 187 Tank_Rate subroutine, enter 0.
Tank_TransferDownTo ............................ page 188 <Resume level>
Tank_TransferUpTo ................................ page 187 If the tank level reaches capacity before you add the
specified quantity, the tank must drop to the resume
Tank_UpdateStats ................................... page 198 level before it can continue filling. To terminate filling
if the tank reaches capacity, enter Tank_Stop as the
resume level. A value of 0 causes an error to occur if
Tank_Fill the tank becomes full before reaching the fill quantity.

Syntax samples
Example
TANK_FILL (<Tank ID>, <Fill Quantity>, <Fill
Rate>, <Resume Level>)
186 Chapter 5:
Pre-defined Tank Subroutines

A tanker arrives and fills a storage tank by the quantity The number of units (gallons, pounds) to empty. To
stored in the tanker’s attribute, Load_Qty. The rate of empty a tank completely of its current contents, enter
fill is 80 gpm and, if the tank fills to capacity before the Tank_Level [<Tank ID>].
tanker discharges the entire quantity, the level of the
<Empty Rate>
storage tank must drop to 12,000 gallons before it
resumes filling. To represent this, enter the following The rate in units (gallons, pounds) per time unit
statement in the operation logic for the tanker at the defined in the General Information dialog. To instantly
unloading station. decrease the level of a tank, use the Tank_Dec subrou-
tine. To specify a dynamically calculated rate using the
Tank_Fill(StorageTank, Load_Qty, 80, 12000)
Tank_Rate subroutine, enter 0.
<Resume level>
If the tank level drops to 0 before you empty the speci-
See Also fied quantity, the tank must rise to the resume level
before continuing to empty. To terminate emptying if
“Filling from an Entity” on page 202 and “Initial-
the level ever drops to 0, enter Tank_Stop. A value of 0
izing and Replenishing Supply Tanks” on
causes an error to occur if the tank becomes empty
page 202. before removing the specified quantity.

Tank_Empty Example

When a chemical tank, ChemTank, is full (state is

Syntax samples
Tank_Blocked), workers pump its contents into a rail
car at a rate of 60 gpm for transportation to another
TANK_EMPTY (<Tank ID>, <Empty Quantity>, facility. Since rail cars are always available and the
<Empty Rate>, <Resume Level>) delivery activity is not of interest, it is not necessary to
TANK_EMPTY (TankB, 2000, 40, 0) model the rail cars explicitly. Instead, activate a sub-
routine in the initialization logic with the following
statement:
Tank_Loop //logic repeats continuously
Description {
Empties a tank by a specified quantity and rate. WAIT UNTIL Tank_State[ChemTank]=Tank_Blocked
The state is set to Tank_Emptying, then to
Tank_Idle if the tank becomes empty. Tank_Fill(ChemTank, Tank_Level[ChemTank], 60, 0)
}
Use Tank_Empty when the destination is not
another tank, but an arriving entity or a source
that is not part of the model.
See Also
Components “Emptying to an Entity” on page 203.

<Tank ID>
The tank name or location index number.
<Empty Quantity>
 ProModel 187
User Guide

Tank_Transfer The rate in units (gallons, pounds) per time unit

defined in the General Information dialog into the TO
tank. Use 0 if same as the FROM rate. (The TO rate is
Syntax samples automatically the same as the FROM rate if you add 0
as the FROM rate.)
TANK_TRANSFER (<FROM Tank ID>, <TO Tank <Resume level>
ID>, <Transfer Quantity>, <FROM Rate>, <TO
If the TO tank reaches capacity before the specified
Rate>, <Resume Level>)
quantity transfers, the TO tank must drop to the resume
TANK_TRANSFER (Tank1, Tank2, 2000, 100, 0, 0) level before continuing with the transfer. To terminate
transferring when the TO tank reaches capacity, enter
Tank_Stop. A value of 0 causes an error to occur if the
tank becomes empty before transferring the specified
Description quantity.

Transfers a specified quantity from one tank to

another. ProModel sets the state of the FROM Example
tank to Tank_Emptying and the TO tank to
Tank_Filling. If the FROM tank becomes empty, When a mixing tank is ready to mix a new batch of
its state becomes Tank_Idle. If the TO tank material, 10,000 gallons of water must first transfer
becomes full, its state becomes Tank_Blocked. from a water supply tank at a rate of 100 gpm. The fol-
lowing logic represents this action:
Otherwise, the states remain unchanged.
Tank_Transfer(WaterTank, MixingTank, 10000, 100,
Use Tank_Transfer when you want to transfer a 0, 0)
specific quantity from one tank to another.

Components
See Also
<FROM Tank ID> “Tank Transfers” on page 204.
The name or location index number of the FROM tank.
<TO Tank ID> Tank_TransferUpTo
The name or location index number of the TO tank.
<Transfer Quantity> Syntax samples
The number of units (gallons, pounds) to transfer. To
transfer the entire contents of a tank, enter Tank_Level TANK_TRANSFERUPTO (<FROM Tank ID>, <TO
[<FROM Tank ID>]. Tank ID>, <TO Level >, <FROM Rate>, <TO Rate>)
<FROM Rate> TANK_TRANSFERUPTO (Tank1, Tank2, 8500, 75,
0)
The rate in units (gallons, pounds) per time unit
defined out of the FROM tank. To use a dynamically
calculated rate in the Tank_Rate subroutine, enter 0.
<TO Rate>
188 Chapter 5:
Pre-defined Tank Subroutines

Description To model this, define an activated subroutine for the

supply tank using the following logic:
Similar to Tank_Transfer except that
Tank_Loop //logic repeats continuously
Tank_TransferUpTo does NOT terminate a trans-
fer based on the transferred quantity, rather when {
the TO tank level rises to a certain point. If the WAIT UNTIL Tank_Level[InProcessTank]<=5000
tank empties before reaching the TO level, Pro-
Tank_TransferUpTo(SupplyTank, InProcessTank,
Model suspends the transfer until capacity
20000, 100, 0)
becomes available.
}
Use Tank_TransferUpTo when you want to raise
the level of a tank to a certain value but are not
certain of the quantity needed to reach that level
(e.g., the tank is draining at the same time you are Tank_TransferDownTo
trying to fill it).

Components Syntax samples

TANK_TRANSFERDOWNTO (<FROM Tank ID>,

<FROM Tank ID>
<TO Tank ID>, <TO Level >, <FROM Rate>, <TO
The name or location index number of the FROM tank. Rate>)
<TO Tank ID> TANK_TRANSFERDOWNTO (Tank1, Tank2, 1000,
80, 0)
The name or location index number of the TO tank.
<TO Level>
Transfer until the TO tank reaches this level.
Description
<FROM Rate>
The rate in units (gallons, pounds) per time unit
Similar to Tank_Transfer except that
defined in the General Information dialog out of the Tank_TransferDownTo terminates the transfer
FROM tank. To use a dynamically calculated rate in when the FROM tank level lowers to a desig-
the Tank_Rate subroutine, enter 0. nated level instead of lowering by a specific
quantity. If the TO tank becomes full, ProModel
<TO Rate>
suspends the transfer until capacity becomes
The rate in units (gallons, pounds) per time unit available.
defined in the General Information dialog into the TO
tank. Use 0 if the TO rate is the same as the FROM Use Tank_TransferDownTo when you want to
rate. lower the level of a tank to a specific value but
you are not certain how much to empty in order
Example to drop to that level (e.g., the tank may fill at the
same time it empties).
An in-process tank supplies several downstream tanks
and must maintain a maximum level of 20,000 gallons. Components
Whenever the in-process tank drops below 5,000 gal-
lons, a supply tank refills the tank at a rate of 100 gpm. <FROM Tank ID>
 ProModel 189
User Guide

The name or location index number of the FROM tank. Tank_SetLevel

<TO Tank ID>
The name or location index number of the TO tank. Syntax samples
<TO Level>
TANK_SETLEVEL (<Tank ID>, <Quantity>)
Transfer until the FROM tank drops to this level.
TANK_SETLEVEL (TankA, 1500)
<FROM Rate>
The rate in units (gallons, pounds) per time unit
defined in the General Information dialog out of the
FROM tank. To use a dynamically calculated rate in Description
the Tank_Rate subroutine, enter 0.
Instantly sets the level of a tank to a specified
<TO Rate>
quantity. If the quantity is negative or larger than
The rate in units (gallons, pounds) per time unit the tank capacity, an error occurs. The tank state
defined in the General Information dialog into the TO sets to Tank_Blocked if you set the tank level to
tank. Use 0 if the TO rate is the same as the FROM the tank capacity and to Tank_Idle if you set the
rate.
tank level to 0. Otherwise, the state remains
unchanged.

Example Use Tank_SetLevel when you want to initialize a

tank to a specific level.
An in-process tank, TankA, supplies TankB at a rate of
50 gpm. TankA must maintain a minimum level of 200 Components
gallons to insure against pump cavitation. When
TankA’s level drops to 200 gallons, the tank stops <Tank ID>
pumping to TankB until the level of TankA rises above
200 gallons. To model this scenario, enter the follow- The tank name or location index number.
ing logic in the subroutine controlling the flow from <Quantity>
TankA to TankB:
The level at which to set the tank (number of gallons,
Tank_Loop //logic repeats continuously pounds). To completely fill the tank, enter
{ Tank_Cap(<Tank Name>).

WAIT UNTIL Tank_Level[TankA]>200

Tank_TransferDownTo(TankA, TankB, 200, 50, 0) Example
}
When you begin a simulation, you wish to set the ini-
tial level of a supply tank, TankX, to 10,000 gallons.
To model this, enter the following statement in the ini-
See Also tialization logic for the model.

“Split Transfers” on page 206. Tank_SetLevel(TankX, 10000)

190 Chapter 5:
Pre-defined Tank Subroutines

See Also WAIT 2.5 MIN

“Initializing and Replenishing Supply Tanks” on Tank_Inc(HoldingBin, 5000)

page 202.

Tank_Inc Tank_Dec

Syntax samples Syntax samples

TANK_INC (<Tank ID>, <Quantity>) TANK_DEC (<Tank ID>, <Quantity>)

TANK_INC (StorageTank, 5000) TANK_DEC (SupplyTankB, 1000)

Description Description
Instantly increases the level of a tank by a speci- Instantly decreases the level of a tank by a speci-
fied quantity. If the tank has insufficient capacity, fied quantity. If the tank has insufficient quantity,
the level increases as capacity becomes available. it empties as material becomes available. Pro-
ProModel sets the tank state to Tank_Blocked if Model sets the tank state to Tank_Idle if you
the level increases to the tank capacity, otherwise decrease the level to 0. Otherwise the state
the state remains unchanged. remains unchanged.
Use Tank_Inc to instantly add a specific quantity Use Tank_Dec to instantly remove a specific
to a tank. quantity from a tank.

Components Components

<Tank ID> <Tank ID>

The tank name or location index number. The tank name or location index number.
<Quantity> <Quantity>
The number of units by which to increment the con- The number of units by which to decrement the con-
tents of the tank (gallons, pounds). tents of the tank (gallons, pounds).

Example
Example
A fill tank fills one 10-gallon container every 15 sec-
Trucks deliver pellets to a holding bin twice a day. onds. After filling, each container moves to a location
When a truck arrives at the drop-off station, it dumps called FillStation. To model this activity, define the fol-
the entire 5,000 lb load in only 2.5 minutes. To model lowing activated subroutine (this subroutine creates a
this, define the following operation logic for the truck filled container every 15 seconds):
at the drop-off station:
 ProModel 191
User Guide

Tank_Loop //logic repeats continuously A tanker waits at a dispatch station until the level of a
finished goods tank rises to 2,000 gallons. Once the
{
tank level reaches this point, a signal dispatches the
WAIT 15 SEC tanker to the finished goods tank for loading. Mean-
Tank_Dec(FillTank, 10) while, the finished goods tank continues filling. To
model this situation, define the following process logic
ORDER 1 Container TO FillStation for the tanker at the dispatch station:
} Tank_RiseTrigger (FGTank, 2000)

See Also Please note

“Emptying to an Entity” on page 203.
Using the Tank_RiseTrigger subroutine instead of
a WAIT UNTIL statement prevents the next tanker
Tank_RiseTrigger from dispatching until the finished goods tank
falls back below 2,000 gallons.
Syntax samples

TANK_RISETRIGGER (<Tank ID>, <Level>)

See Also
TANK_RISETRIGGER (TankA, 3000)
“Defining Trigger Levels” on page 207.

Description Tank_FallTrigger
Waits until tank contents rises to a specific level.
Use Tank_RiseTrigger to initiate some action Syntax sample
when a tank rises to a certain level.
TANK_FALLTRIGGER (<Tank ID>, <Level>)

Components TANK_FALLTRIGGER (TankB, 500)

<Tank ID>
The tank name or location index number. Description
<Level> Waits until tank contents falls to a specified level.
When the tank level rises to this value, ProModel exe-
Use Tank_FallTrigger to initiate an action when a
cutes any subsequent logic.
tank level falls to a specific level.

Example Components

<Tank ID>
192 Chapter 5:
Pre-defined Tank Subroutines

The tank name or location index number. Description

<Level> Returns the capacity defined for the specified
When the tank level falls to this value, any subsequent tank.
logic executes.
Use Tank_Cap when you need to know the
defined capacity for a tank.
Example
Components
When an in-process tank, TankX, falls to 1000 gallons,
it triggers a mixing tank to begin producing more prod- <Tank ID>
uct. To model this, define the following activated sub- The tank name or location index number.
routine to control the mixing tank:
Tank_Loop //logic repeats continuously
{ Tank_FreeCap
Tank_FallTrigger(TankX, 1000)
[Insert logic to mix new batch here] Syntax samples
}
TANK_FREECAP (<Tank ID>)
TANK_FREECAP (TankA)

Please note

Using Tank_FallTrigger instead of a WAIT Description

UNTIL statement prevents the action from trig- Returns the available capacity of the specified
gering again until the level first rises above the tank.
fall trigger level.
Use Tank_FreeCap when you need to know the
available capacity of a tank.

See Also Components

“Defining Trigger Levels” on page 207.
<Tank ID>
The tank name or location index number.
Tank_Cap

Syntax samples

TANK_CAP (<Tank ID>)

TANK_CAP (TankA)
 ProModel 193
User Guide

Tank_DoOperation Tank_GoDown

Syntax samples Syntax samples

TANK_DOOPERATION (<Tank ID>, <Operation TANK_GODOWN (<Tank ID>, <Down time>)

time>)
TANK_GODOWN (TankA, 5)
TANK_DOOPERATION (TankA, 30)

Description
Description
Sets the state of the tank to Tank_Down, waits for
Sets the state of the tank to Tank_Operation and the specified downtime, then sets the state back
waits for the specified operation time. ProModel to the previous setting. If you defined a downtime
sets the state to Tank_Blocked after the operation. using the location downtime dialog, call the
Tank_GoDown subroutine in the downtime logic
Use Tank_DoOperation when some activity or
rather than use a WAIT statement. If the down-
treatment time is necessary for the material in a
tank. time is for cleaning, use the Tank_DoPrep sub-
routine.

Components Use Tank_GoDown to shut down a tank due to

equipment failure (e.g., pump failure). If the
<Tank ID> downtime occurs periodically, you can define a
clock downtime in the downtime logic for the
The tank name or location index number. tank location and use Tank_GoDown in place of
<Operation time> the WAIT statement.
The duration (in time units defined in the General
Information dialog) of the operation. Components

<Tank ID>
Example The tank name or location index number.
<Down time>
After technicians add all the necessary ingredients to
the mixing tank, the tank requires a 20 minute mixing The duration (in time units defined in the General
time. To define this operation, enter the following Information dialog) of the downtime.
statement in the subroutine for the mixing activity:
Tank_DoOperation(MixingTank, 20)
Example

A fill line from a dry supply bin plugs randomly

See Also according to an exponential distribution with a mean of
10 minutes. The time to unplug the line is normally
“Mixing and Reactor Tanks” on page 203.
distributed with a mean of 5 minutes and a standard
194 Chapter 5:
Pre-defined Tank Subroutines

deviation of 1 minute. To define this behavior, define a nance or end of scheduled workday). Since the
clock downtime for the bin to occur with a frequency tank uses a scheduled downtime, the time lapsed
of E(10) minutes. In the logic defined for the down- during the event does not record as a downtime.
time, enter the following logic:

Tank_GoDownSched

Syntax samples

TANK_GODOWNSCHED (<Tank ID>, <Down

time>)
TANK_GODOWNSCHED (TankA, 5)

Description
Sets the state of the tank to
Tank_ScheduledDown, waits for the specified
scheduled downtime, then sets the tank state back
to its previous setting. If you defined a scheduled
downtime using the location downtime dialog,
call the Tank_GoDownSched subroutine in the
downtime logic rather than use a WAIT state-
ment. If the downtime is for cleaning and you
will return the tank status to idle, use the
Tank_DoPrep subroutine.
Use Tank_GoDownSched to shut down a tank for
a scheduled task or event (e.g., interim mainte-
 ProModel 195
User Guide

Components Description
Sets the state of the tank to Tank_Setup, waits for
<Tank ID> the specified time, then sets the state to
The tank name or location index number. Tank_Idle. Use Tank_DoPrep for cleaning activi-
<Down time> ties after you empty a tank.

The duration (in time units defined in the General Use Tank_DoPrep to take a tank off line for
Information dialog) of the scheduled downtime. cleaning or other preparation time.

Components
Example
<Tank ID>
Every 4 hours, a technician must check the fill line The tank name or location index number.
from a dry supply bin. The time required to check the
line is normally distributed with a mean of 10 minutes <Prep time>
and a standard deviation of 3 minutes. To define this The duration (in time units defined in the General
behavior, define a clock-based, scheduled downtime Information dialog) of preparation time.
for the bin to occur with a frequency of 4 hours. In the
logic defined for the downtime, enter the following:

Example

Workers clean a mixing tank for 30 minutes after each

batch produced. To model this, enter the following
logic in the mixing subroutine defined for the mixing
tank:
Tank_Loop //logic repeats continuously
{
[Enter mixing and transfer logic here]
Tank_DoPrep(MixingTank, 30)
}

See Also
Tank_DoPrep
“Mixing and Reactor Tanks” on page 203.
Syntax samples

TANK_DOPREP (<Tank ID>, <Prep time>)

TANK_DOPREP (TankA, 5)
196 Chapter 5:
Pre-defined Tank Subroutines

Tank_SetState Description
Selects an output tank from among several tanks
Syntax samples based on a selection rule and optional product
type. To use this function, list all tanks included
TANK_SETSTATE (<Tank ID>, <State>) in the selection decision together in the Location
module.
TANK_SETSTATE (TankA, Tank_Idle)

Components

Description <First Tank>

Sets the state of the tank (e.g., Tank_State[<Tank The name or location index number of the starting tank
ID>]) to a new state and updates the statistics in the range.
since the last change of state. <Number of Tanks>
Use Tank_SetState to explicitly change the state The number of tanks in the selection range (limit 10).
of a tank. Use Tank_SetState only if the default <Selection Rule>
state changes do not adequately meet modeling
needs. The rule for making the selection may be one of
the following:
Components Tank_InOrder (selects the first idle tank encoun-
tered)
<Tank ID> Tank_LongestIdle (selects the tank idle the long-
est)
The tank name or index number.
<Maximum Level>
<State>
The maximum level of the output tank before consider-
The new state for the tank. For a list of possible tank
ing it for selection. Enter 0 if the output tank must be
states, see “Tank States” on page 182.
empty or idle before being considered.
<Product Type>
An integer specifying the required value of the Product
Tank_SelectOutput array in order to select the tank. Enter 0 if the tank
selection requires no product type match. (This applies
Syntax samples only if the maximum level specified is greater than 0.)

TANK_SELECTOUTPUT (<First Tank>, <Number

of Tanks>, <Selection Rule>, <Maximum Level>, Example
<Product Type>)
TANK_SELECTOUTPUT (TankA, 3, Tank_InOrder, A supply tank feeds one of 3 output tanks and always
5000, 0) gives preference first to Tank1, then to Tank2, and
finally to Tank3 based on availability. Furthermore, the
supply tank can select a tank only if its contents are
less than 8000 gallons. To model this selection, list
 ProModel 197
User Guide

Tank1, Tank2, and Tank3 together (and in order) in the .

location module. Then define the following statement
SelectedTank=Tank_SelectOutput(Tank1, 3,
to select the tank using a local variable, Selected_Tank:
Tank_InOrder, 8000,0)
INT Selected_Tank
.
. The diagram below shows the logic used to make
a tank selection:

No
Is the specified Max
level > 0?

Yes

Is
there a tank Is
No No Wait for first tank to
No there an idle
with level > 0 but Is the specified Max become idle.
less than Max level and tank that satisfies
level > 0?
same product selection rule?
type?

Yes Yes
Yes

Match Wait for first tank to

fall below the Max
specified product
type if required level.
No

Yes

Return Tank ID

If you base a tank selection on product type, you See Also

must be careful to assign an appropriate integer
value to the Product array element corresponding “Selecting from Multiple Input or Output Tanks”
to the tank location. on page 205.
198 Chapter 5:
Pre-defined Tank Subroutines

Tank_SelectInput An integer specifying the required value for the Prod-

uct array in order to select the tank. Enter 0 if the tank
selection requires no product type match.
Syntax samples

TANK_SELECTINPUT (<First Tank>, <Number of Example

Tanks>, <Selection Rule>, <Minimum Level>, <Prod-
uct Type>)
A tanker arrives at a pick up station to load from one of
TANK_SELECTINPUT (Tank1, 5, Tank_ByOrder, 5 tanks depending on which tank has been full the
1000, 0) longest. The tanker will fill from a partial tank if the
tank has any contents at all (at least .1 gallons). To
model the tank selection, define the following opera-
tion logic for Tanker at PickUpStation:
Description INT SelectedTank
Selects an input tank from among several tanks Selected_Tank=Tank_SelectInput(Tank1, 5,
based on a selection rule. To use this function, Tank_LongestBlocked, .1, 0)
you must list all tanks included in the selection
together in the Location module.

Components See Also

“Selecting from Multiple Input or Output Tanks”
<First Tank> on page 205.
The name or location index number of the starting tank
in the range. Tank_UpdateStats
<Number of Tanks>
The number of tanks in the selection range (limit 10). Syntax samples
<Selection Rule>
TANK_UPDATESTATS (<Tank ID>)
The rule for making the selection may be one of the
following: TANK_UPDATESTATS (TankA)
Tank_InOrder (selects the first blocked tank
encountered)
Tank_LongestBlocked (selects the tank blocked Description
the longest)
ProModel calls this subroutine automatically
<Minimum Level>
whenever you call any of the predefined subrou-
The minimum level of the input tank before consider- tines that affect the tank level. If you change the
ing it for selection. If the tank must be full before con- value of the Tank_Level directly, call the
sidering it for an input source, enter 0. Tank_UpdateStats subroutine afterward. This
<Product Type> subroutine updates the current statistics on the
tank and sets the state to Tank_Filling (if filling),
 ProModel 199
User Guide

Tank_Emptying (if emptying), Tank_Blocked (if The name or location index number of the TO tank
full), or Tank_Idle (if empty). (this value should be 0 if there is no TO tank).

You should not need to use this subroutine unless

you defined a customized Tank_Empty,
Tank_Fill, or Tank_Transfer subroutine.
Example

TankA fills with 10,000 gallons at a rate of 60 gpm

Components until it reaches a level of 9,700 gallons. Then it fills at
a rate of 30 gpm. To model this change of rate, define
<Tank ID> the following logic in the Tank_Rate subroutine:
The tank name or location index number. IF Tank_ToID=TankA
THEN IF Tank_Level[TankA]<9700
THEN RETURN 60
Tank_Rate ELSE RETURN 30
Now when you fill TankA, enter the following:
Syntax sample
Tank_Fill(TankA, 10000, 0, 0)
TANK_RATE (<FROM tank ID>, <TO tank ID>) The first 0 in the expression above causes the logic
defined in the Tank_Rate subroutine to execute and
TANK_RATE (TankA, TankB) determine the flow rate.

Description See Also

ProModel calls this subroutine automatically if “Varying the Transfer Rate” on page 206.
you pass a 0 value as the From Rate when using
the Tank_Empty or Tank_Transfer subroutine. To
return the desired rate value, enter the necessary Pre-defined Data Elements
logic in the subroutine—ProModel calls the sub-
routine with each time step. A return value of 0 The ProModel tank submodel provides the fol-
terminates the flow and returns the remaining lowing data elements for modeling tanks. Unless
amount in the Tank_QtyLeft variable. otherwise specified, all arrays are single-dimen-
sional and of type integer. Initially, these arrays
are 100 elements in size to allow for up to 100
Components locations. If you define more than 100 locations,
you will need to enlarge the array or place tanks
<FROM Tank> toward the beginning of the location list (within
The name or location index number of the FROM tank the first 100 locations).
(this value should be 0 if there is no FROM tank).
Tank_Level array Stores the level of each tank.
<TO Tank> Since the values in this array directly control the
tank gauge and tank statistics, the array MUST be
present in every tank model.
200 Chapter 5:
Pre-defined Tank Subroutines

Tank_State array Tracks the state of the tank. • Total Entries The number of units (e.g., gal-
lons, pounds) to enter the tank.
Tank_Product array An optional array used to
• Avg Minutes Per Entry Left blank since
record or test the product currently at a tank.
there is no individual entry for a tank.
Tank_Statistics array A two-dimensional array
Tank_Fills array An optional array used to track
of type real used to record tank level statistics
the number of transfers to a tank. This is espe-
whenever the level changes. Generally, you will
cially useful when you activate multiple
never need to reference this array since values
Tank_Fill or Tank_Transfer subroutines for a
automatically update when you use the pre-
tank and you wish to know when the fills are
defined Tank subroutines. All times are in time
complete. The user sets the value of Tank_Fills to
units defined in the General Information dialog.
zero before activating the subroutines, then
ProModel always gathers these statistics but
defines a WAIT UNTIL statement after the
reports them only if you check Basic or Time
ACTIVATE statement. The Tank_Fills array
Series statistics for the tank location.
increments automatically when a Tank_Fill or a
Column Description Reset After Warm-up Tank_Transfer subroutine executes. See “Mixing
1 Last level NC and Reactor Tanks” on page 203 for additional
2 Last change time Current time in time information.
units defined in the
General Information
dialog Statistics
3 Cum time-weighted 0
level
4 Entries Value of column 1
Please note
5 Max contents Value of column 1
6 Last State Change Current time in time
TS = Tank_Statistics array
units defined in the n = Location index number of tank
General Information
dialog
7 Cum time Idle 0
8 Cum time Operation 0
Calculating Location Statistics for
9 Cum time Setup 0
Tanks
10 Cum time Filling 0
11 Cum time Emptying 0
Entries = TS [n, 4]
12 Cum time Blocked 0
13 Cum time Down 0 Avg. Time per Entry = (not applicable)
14 Current downtime NC Avg. Contents = TS[n,3] / Scheduled Time
count
Max Contents = TS [n,5]
As shown in the previous table, the statistics col- Current Contents = TS [n,1]
lected in the Tank_Statistics array automatically Utilization=100 x TS[n,3] / (Capacity x Scheduled
reset after any warm-up period. ProModel reports Time)
output statistics under Location statistics and
Location States by Percentage. When reporting
Location statistics for tanks, note the following:
 ProModel 201
User Guide

Calculating Location State Statistics be capable of executing independently of each

for Tanks other. On the other hand, if the logic associated
with two tanks is interdependent, only one con-
trol subroutine is necessary. For example, if
%Operation = 100 x TS[n, 8] / Scheduled Time
TankA fills TankB while TankB waits, then
%Setup = 100 x TS[n, 9] / Scheduled Time TankB pumps out while tank A waits, you need
%Idle = 100 x TS[n, 7] / Scheduled Time only a single control subroutine since you control
both tanks by a single logic sequence. If a single
%Waiting = 100 - Sum of other percentages
tank feeds several other tanks independently, you
%Blocked = 100 x TS[n, 12] / Scheduled Time would need a separate subroutine to control each
%Down = 100 x TS[n, 13] / Scheduled Time output. In most cases, you will need at least one
control subroutine per tank and, in certain situa-
tions, you may wish to use a hierarchical control
system (i.e., a master or supervisory control sub-
To gather statistics on how much of a particular routine) to activate subordinate subroutines.
product was processed, you may define variables
to record product processing during the simula- Most tank control subroutines should be activated
tion. subroutines. In contrast to called subroutines,
activated subroutines use the ACTIVATE state-
ment and cause the logic activating the subrou-
Defining Tank Control Subrou- tine to continue independently of the activated
tines subroutine. This allows you to execute multiple
control subroutines concurrently. Multiple tanks
Unlike defining entity activity at a location with identical control logic may share the same
(defined in the Processing module), modeling control subroutine if you activate the subroutine
tank location activity requires the use of subrou- for each tank and pass the tank ID as a parameter.
tines. Many of these subroutines are user-defined
One of the keys to modeling interactive tank
and called using the ACTIVATE statement.
behavior is to effectively use WAIT UNTIL state-
Though you generally activate them from the ini-
ments. When you use WAIT UNTIL statements
tialization logic, you may also activate them from
based on the Tank_Level array, use them spar-
another tank subroutine. Tank subroutines consist
ingly since this array changes frequently and may
of logic defined to control when, where, and how
slow the simulation.
much to empty, fill, or transfer from a tank.
Often, these subroutines require the use of WAIT
UNTIL statements to monitor conditions (e.g., Examples of Tank Control Logic
the tank level or state) before making a transfer
and may include delays for mixing or cleaning. The following examples show how to model dif-
ferent tank and flow situations. For full models
At a minimum, you should define a separate con- illustrating these situations, see the reference
trol subroutine for any logic that executes inde- model in the MODELS\REFS directory within
pendently of any other logic. For example, if the ProModel directory.
TankA fills TankB at the same time TankB trans-
fers to some other tank, you should define two
separate subroutines since both sets of logic must
202 Chapter 5:
Pre-defined Tank Subroutines

Filling from an Entity tanker delivers this quantity, it is free to execute

the routing defined for it at the Delivery location.
A typical tank modeling situation is the arrival of
an entity (e.g., a tanker or other vehicle) to
deliver its contents to a tank. To model this situa- Initializing and Replenishing Supply
tion, define an arrival or routing for the entity, Tanks
causing it to enter the location where it will make A supply tank is an originating tank that is a
its delivery. In the entity processing logic at the source of raw material for one or more down-
delivery location, call the Tank_Fill subroutine. stream tanks. Often, supply tanks contain ingredi-
By calling rather than activating the subroutine, ents that feed into a mixing tank or hold
you will detain the delivering entity until chemicals that feed into a reactor. Typically, you
Tank_Fill executes. Note that the material does replenish a supply tank when it gets low and
NOT route from the delivery location to the tank. make it available for use whenever it has an ade-
Instead, the Tank_Fill subroutine simply fills the quate supply. If you always stock the supply tank
tank with a specified quantity while the entity and it is always available for use, you do NOT
waits. Unless the quantity is a constant amount, it need to model it since it poses no constraint on
is usually a good idea to use an entity attribute to the process. You may set supply tanks to an initial
store this quantity value. After filling the contents level at the start of the simulation in the initializa-
into the tank, the entity is free to continue pro- tion logic, then use them as needed by a mixing
cessing. or other downstream tank. To initialize the level
To illustrate how an entity might transfer its con- in a supply tank, enter the following statement in
tents to a tank, suppose an entity, Tanker, arrives the initialization logic:
at a location, Delivery, carrying a quantity of gal-
lons stored in an entity attribute called Initialize tank level
Tanker_Qty. The tanker discharges its contents
into a tank, ReceivingTank, at a rate of 200 gal- Tank_SetLevel (<supply tank>, <qty>)
lons per minute. Once the ReceivingTank
becomes full, the level must drop to 1000 gallons
before filling resumes. Since the entity is tied up
while it discharges into the tank, use the follow- If, for example, you wanted to begin the simula-
ing statement in the processing logic for Tanker tion with the supply tank, WaterTank, filled with
at Delivery to define the logic used to fill the 800 gallons of water, you would enter:
tank:
Start with full tank
Fill the tank
Tank_SetLevel (WaterTank, 800)
Tank_Fill (ReceivingTank, Tanker_Qty, 200, 1000)

To gradually fill or refill a supply tank whenever

The above statement causes each arriving tanker it drops below a trigger level, use the Tank_Fill
to wait until the quantity stored in its Tanker_Qty subroutine with a large fill quantity and an appro-
attribute adds to the ReceivingTank. Once the priate resume level. For example, the following
 ProModel 203
User Guide

statement will continue pumping up to 999999 Tank_DoOperation (MixingTank,15) //Mix time

units into TankA at a rate of 200 units per minute. Wait Until Tank_State [StorageTank]= Tank_Idle /*
Whenever the tank becomes full, it must drop to Waits for storage tank availability */
400 units before filling resumes.
Tank_Transfer (MixingTank, StorageTank,
Tank_Level[MixingTank],40, 0, 0)
Resume fill with trigger level Tank_Prep (MixingTank, 50) // Clean mixing tank for
50 minutes.
Tank_Fill (TankA, 999999, 200, 400)
END

Mixing and Reactor Tanks If the ingredients feed into the mixing tank at the
Mixing and reactor tanks receive material usually same time rather than sequentially, activate the
from one or more supply tanks. Once it receives Tank_Transfer subroutines for the mixing tank
the material, the tank may require a mixing or and monitor the Tank_Fills array to know which
other reaction time. To illustrate, suppose we ingredients enter into the tank. For simultaneous
have two tanks (Tank1 and Tank2) supplying fills, replace the first two transfer statements fol-
ingredients to a tank called MixingTank. First, lowing the BEGIN statement in the previous sub-
workers pump 2000 gallons of a liquid from routine with the following logic:
Tank1 at 50 gallons per minute followed by the
transfer of 300 pounds of dry mix from Tank2 at Simultaneously mix, then clean tank
20 pounds a minute (the dry mix adds .2 gallons
to the level of the MixingTank for every pound
Tank_Fills[MixingTank]=0
transferred, equating to 4 gallons per minute).
The ingredients then mix for 15 minutes before ACTIVATE Tank_Transfer(Tank1, MixingTank, 2000,
transferring to an idle storage tank. After trans- 50, 0, 0)
ferring the mix, workers must clean the Mixing- ACTIVATE Tank_Transfer(Tank2, MixingTank, 300,
Tank for 50 minutes to prepare it for the next 20, 4, 0)
mixing cycle. WAIT UNTIL Tank_Fills[MixingTank]=2
The control logic for the mixing tank should be a ...
subroutine activated from the initialization logic
which continues to loop throughout the simula-
tion. The subroutine logic might appear as fol-
lows: Emptying to an Entity
Often, tanks deliver material to discrete entities
Mix and clean the tank such as containers (or perhaps the material itself
converts to discrete entities through a solidifica-
Tank_Loop //logic repeats continuously tion or consolidation process). In either case, you
BEGIN can draw from the delivery tank using the
Tank_Empty subroutine if outflow is gradual and
Tank_Transfer (Tank1,MixingTank,2000, 50, 0, 0) defined by a flow rate, or the Tank_Dec subrou-
Tank_Transfer (Tank2,MixingTank, 300, 20, 4, 0)
204 Chapter 5:
Pre-defined Tank Subroutines

tine if the output occurs in discrete intervals Tank Transfers

based on a bottling or packaging time.
To output material from a tank without modeling
the entity to which it outputs, call the
Tank_Empty or Tank_Dec subroutine. To transfer
material from a tank to entities arriving at a fill-
ing station (remember, the filling station itself is
NOT a tank), route the entities to the filling sta-
tion using a SEND or other routing rule, then call
the Tank_Empty or Tank_Dec subroutine.
If using the Tank_Dec subroutine, the entity
should wait for the fill time before decreasing the
tank level since Tank_Dec happens instantly. For
example, if a bottling operation fills a 2 gallon When transferring from one tank to another, you
container every 6 seconds, define the following must determine whether the source tank makes
processing logic for the container at the fill sta- the decision to transfer to the destination tank (a
tion: push approach) or whether the destination tank
makes the decision to draw material from a
Wait to fill from tank, then continue source tank (a pull approach). You should define
a control subroutine from the perspective of the
Wait 6 sec tank that makes the decision. If the model
requires no tank selection, specify a WAIT
Tank_Dec (Filler, 2) UNTIL statement to wait until the FROM or TO
tank satisfies the condition required for transfer.
For example, if a source tank makes the decision
If the delivery tank has insufficient contents to to transfer to a destination tank whenever the des-
decrease the level by the specified amount, the tination tank becomes idle, enter the following
processing will automatically pause until enough statement in the subroutine:
material is available. Once the specified quantity
empties, the entity can continue processing. To Transfer contents when idle
create an entity as the result of an emptying oper-
ation, define an activated subroutine that empties Wait Until Tank_State [<destination tank ID>] =
the desired quantity, then execute an ORDER Tank_Idle
statement. This will create a new entity at the fill-
ing station.

If the destination tank makes the decision to

transfer (a pull approach), you should base the
WAIT UNTIL statement on a required condition
for the source tank as follows:
 ProModel 205
User Guide

Transfer contents based on condition Selecting from Multiple Input or

Output Tanks
Wait Until Tank_State [<source tank ID>] =
To enable one or more tanks to select from sev-
Tank_Blocked
eral input or output tanks, use the pre-defined
subroutine Tank_SelectInput or
Tank_SelectOutput (see subroutine descrip-
Following the WAIT UNTIL statement, call the tions). ProModel bases tank selection on which
Tank_Transfer, Tank_TransferUpTo, or tank is ready to transfer or receive and that has
Tank_TransferDownTo subroutine to transfer the same ProductType array value. You must list
from the source tank to the destination tank. the tank selections together in the Location mod-
ule.
To illustrate how to define a tank transfer using a
pull approach, suppose that TankB requires 1000 For example, if TankX selects from among three
gallons from TankA whenever TankB becomes input tanks (Tank1, Tank2, and Tank3) based on
empty. TankB will draw material from TankA which input tank has waited the longest to dis-
only when TankA has a minimum level of 1000 charge its contents, you would enter the follow-
gallons. The subroutine to define this logic might ing logic in the control subroutine defined for
appear as follows: TankX:

Tank transfer in a pull system Select from multiple tanks

Tank_Loop //logic repeats continuously Int SelectedTank

Begin SelectedTank = Tank_SelectInput(TankX, Tank1, 3,

Tank_LongestBlocked, 0)
Wait Until Tank_Level[TankA] >= 1000 /*Wait for
TankA to reach 1000 gallons*/
Tank_Transfer (TankA, TankB, 1000, 200,0,0) /*
Transfer 1000 gal to TankB at 200 gpm*/ The first statement defines a local variable,
[Enter TankB processing and emptying logic here] SelectedTank, used to assign which tank you
select. The second statement calls the SelectInput
End subroutine specifying that TankX is to select one
of three tanks beginning with Tank1.
Tank_LongestBlocked causes TankX to select the
tank blocked the longest (i.e., tank is full or wait-
Please note ing). Entering 0 at the end prevents selecting a
full tank. If no tank is full, the statement does not
To select from among multiple input or output execute until one of the input tanks fills. With a
tanks, activate this subroutine in the initialization tank ID assigned to SelectedTank, you can call a
logic. transfer subroutine to make the transfer.
206 Chapter 5:
Pre-defined Tank Subroutines

For output tanks, you would define similar logic The subroutines TransferToB and TransferToC
but include Tank_SelectOutput instead of would each execute a Tank_TransferDownTo
Tank_SelectInput. command followed by a statement incrementing
the value of TransferDone. For example, the
logic for TransferToB would be as follows:

Split transfers subroutines

TransferDownTo(TankA, TankB, 0, 30, 0)

INC TransferDone

Varying the Transfer Rate

The transfer or empty rate can change dynami-
Split Transfers cally during an empty, fill, or transfer. To vary the
rate of flow, pass 0 as the flow rate when calling
Sometimes it is necessary to use a tank or separa- any of the transfer, fill, or empty subroutines.
tor to split the flow to several output tanks. To This calls the Tank_Rate subroutine automati-
define the concurrent transfer of material from cally with each time step. You should modify the
one tank to multiple tanks, define an activated Tank_Rate subroutine so that it returns the appro-
subroutine for each transfer. Suppose, for exam- priate rate value.
ple, that when TankA fills it begins transferring
to TankB at a rate of 30 gpm and to TankC at a Suppose, for example, that TankA transfers to
rate of 40 gpm. To know when both transfers are TankB at a rate that decreases from 150 gpm to
complete, define a global variable (e.g., Transfer- 50 gpm when the level of TankB reaches 4000.
Done) which increments at the end of each trans- To achieve this, pass 0 as the From Rate when
fer. Defining the following logic would initiate you call the transfer subroutine, then enter the
this split transfer once TankA is full: following logic in the Tank_Rate subroutine:

Initiate split transfer Vary the transfer rate

ACTIVATE TransferToB () // initiates transfers from A IF (Tank_FromID = TankA) AND (Tank_ToID =

to B TankB)

ACTIVATE TransferToC () // initiates transfers from A THEN IF Tank_Level[TankB] >= 4000

to C THEN RETURN 50
WAIT UNTIL TransferDone = 2 // Wait until transfers ELSE RETURN 150
are complete
TransferDone = 0 // reset for next transfer
 ProModel 207
User Guide

Dynamically Suspending Flow ciated action should execute when the tank level
rises or falls to a certain level.
To momentarily interrupt flow into or out of a
tank, use the Tank_GoDown subroutine or set the
state of the tank to down (Tank_SetState =
Tank_Down). This typically happens if a pump
fails but may occur in other situations.

Dynamically Terminating a Flow

Normally, the flow into or out of a tank stops
once you reach the desired quantity or level.
However, in some situations you may wish to ter-
minate a transfer if some event or condition
occurs that you cannot predetermine (e.g., a deci-
sion to divert flow to a preferred outlet tank that To show how to define a trigger subroutine, sup-
just became available). In this case, you can turn pose that whenever TankA rises to 2000 gallons,
off the flow into or out of a tank by specifying a an entity called Truck travels to a location called
variable transfer rate instead of a fixed transfer Pickup. The logic for this trigger subroutine
rate (see previous discussion, Varying the Trans- might look as follows:
fer Rate). A variable transfer uses the Tank_Rate
subroutine to determine the rate for each time Trigger subroutine
step—to terminate a transfer, return a rate value
of 0. Tank_Loop //logic repeats continuously
Begin
Defining Trigger Levels
Tank_RiseTrigger (TankA, 2000) /* waits for TankA to
A trigger level is a level to which material in a rise to 2000 units*/
tank either falls or rises and triggers some action. Order 1 Truck to Pickup // order a Truck to Pickup
To continuously monitor when a tank reaches a
trigger level, define and activate a trigger subrou- End
tine in the initialization logic. The subroutine
should call Tank_RiseTrigger or
Tank_FallTrigger depending on whether the asso-
Once the tank reaches the trigger level, the
Tank_RiseTrigger subroutine prevents further
triggering until the level drops back below the
trigger level first.
When you use trigger subroutines, use them spar-
ingly because they are CPU intensive. Every time
the tank level changes, ProModel tests to see if
the tank reached the trigger level. Trigger subrou-
tines are often unnecessary because, unlike an
actual tank where sensors report the tank level,
208 Chapter 5:
Pre-defined Tank Subroutines

you directly control how much to pump into a Showing Pipes

tank. For instance, an alternative way to model
the previous example without using a triggering To show pipes connecting the tanks, use paths or
subroutine would be to call the background graphics. If you desire to show the
Tank_TransferToLevel subroutine to first fill the material in the pipe, use a long, skinny tank with
tank to the 2000 unit level, order the Truck entity a capacity of 1 to represent the pipe. You can set
and then transfer the rest. the level of this tank to 0 or 1 to show product
flow. For example, suppose we define a tank
location called Pipe used to represent the connec-
Processing Multiple Products tion between Tank1 and Tank2. Whenever trans-
Where you must track several different products ferring from Tank1 to Tank2, you would enter the
through one or more tanks, it may be useful to following:
define macros for naming each product type. For
example, setting ProductA equal to 1 and Pro- Define pipes
ductB equal to 2 will improve the readability of
the model. To track which product a particular Tank_SetLevel (Pipe,1)
tank is processing, ProModel uses a pre-defined
Tank_Transfer (Tank1, Tank2, ….)
integer array called Tank_Product—the user is
responsible for maintaining the array values. If, Tank_SetLevel (Pipe, 0)
for example, ProductA begins pumping into
Tank1, enter the following after you assign an
integer value to ProductA in the Macros module
to distinguish it from other products: High-Rate Entity Processing
For systems that process entities at rates higher
Tracking products than one hundred units per minute, using discrete
entities could make the simulation extremely
Tank_Product [Tank1] = ProductA slow. For this reason, ProModel uses tanks. To
use a tank to model high-rate processing, think of
the tank as a buffer where the tank level repre-
sents the number of items in the buffer. For exam-
ple, suppose that bottles feed through a filling
station at a rate of 110 per minute. The input
buffer, FillerInput, has a capacity of 1200 bottles
and the output buffer, FillerOutput, has a capacity
of 2000 bottles. If FillerOutput is full, processing
stops until the quantity in the output buffer drops
to 1500 bottles. An arriving container feeds quan-
tities of 200 bottles to the FillerInput location and
it takes 1 minute to unload the container. When
the filling station fills 50 bottles, workers put the
bottles into a box (represented by an entity) and
ship them. Since workers load the boxes as soon
 ProModel 209
User Guide

as the bottles complete the filling process, there is }

no delay time involved.
The operation logic for the container at the arriv-
ing location would be as follows: Please note
High-rate processing The Tank_Dec statement automatically removes
50 bottles from FillerOutput whenever there are
WAIT 1 min at least 50 bottles available.
Tank_Inc (FillerInput, 200)

Special Notes
To model the processing of bottles from FillerIn- • Since tank models do not stop automatically
put to FillerOutput, enter the following statement when there are no more entities or sched-
in the model initialization logic. uled arrivals, remember to define a run
length or a STOP statement.
High-rate processing • When you activate a subroutine, it doesn't
process until the current logic (the one
ACTIVATE Tank_Transfer(FillerInput, FillerOutput, activating the subroutine) finishes or
999999, 110, 0, 1500) becomes blocked. It you want the acti-
vated subroutine to process first, enter
“WAIT 0” after the ACTIVATE statement.
• Do not define a local variable inside of a
This statement causes the FillerInput tank to
Tank_Loop since the loop will create the
transfer bottles to FillerOutput at a rate of 110 per
variable multiple times.
minute whenever there are bottles in FillerInput
• Make sure all IF...THEN logic and WAIT
and capacity available in FillerOutput. The
UNTIL statements based on the
resume level is 1500. (Up to 999999 bottles will
Tank_Level array use the “>=” or “<=”
transfer.)
operator and not just an “=” operator. (This
To model the creation of a 50-bottle box each is because flow occurs in increments and
time the filling station fills 50 bottles, define and you can’t check for an exact value.)
activate the following subroutine in the model • Tanks are not legal in multi-unit locations or
initialization logic: in locations containing a conveyor or
queue.
Create new, combined unit

Tank Loop //causes logic to repeat continuously

{
Tank_Dec(FillerOutput, 50)
Order 1 Box to Shipping
210 Chapter 5:
Background Graphics

Background Graphics How to create or edit background

graphics:
Background graphics allow you to enhance a
model by adding a background to the animation.
1. Select Background Graphics from the Build
A background could show a floor-plan of a fac- menu.
tory or any item that is not part of a location,
entity, or resource. Backgrounds can be created 2. Select Front of Grid or Behind Grid depending on
the mode desired.
using the tools in the Background Graphics Edi-
tor or by importing an existing background from
another application, such as AutoCAD. Imported
graphics must have been saved in one of the fol-
lowing formats BMP, EMF, WMF, GIF, or PCX.
Background Graphics Editor
The Background Graphics Editor is accessed Modes
from the Build menu as shown below.
ProModel gives you the option of placing the
background graphic in front of or behind the grid.
This is useful when you want to view the
imported background graphic, but you also want
to see the grid for drawing and sizing objects on
the imported background graphic.

Front of Grid Mode

Creating graphics in this mode places the back-
ground graphic in front of the grid as shown
below.

There are two modes for editing in the Back-

ground Graphics Editor: Front of Grid and
Behind Grid. Generally, most graphics should be
laid out in front of the grid. Graphics placed Behind Grid Mode
behind the grid should be reserved for large
Creating graphics in this mode places the back-
objects such as walls or imported backgrounds.
ground graphic behind the grid as shown below.
 ProModel 211
User Guide

located in the lower right portion of the

workspace.

Library Graphics Window

The Library Graphics window contains the icons
of the current graphic library file, specified in the
General Information dialog. These icons may be
placed on the Layout in the same way as other
objects.

Background Graphics Editor

The Background Graphics Editor allows you to You may size the window as desired, or use the
place icons, text and other graphic shapes on the scroll bar shown above to scroll through the
layout behind locations and other system element available icons.
graphics. The arrangement of the two windows
and button bar is shown below. Tools Button Bar
The Tools button bar contains the tools necessary
to create objects various shapes. It also contains

• The Library Graphics window, containing all

the icons in the current graphic library, is
located at the top of the workspace.
• The Tools button bar, where you may select a
tool for creating and editing graphic
shapes, is located at the left of the work-
space.
• The Layout window, where all creating and
editing of graphic shapes is done, is
212 Chapter 5:
Background Graphics

tools for editing those objects including flip, The first four functions apply to the currently
rotate, and cut. selected object. To select multiple objects, hold
the shift key while selecting an object. Alterna-
Selector tively you can drag a rectangle encompassing the
objects you want selected. To deselect one of sev-
eral selected objects, click on the selected object
while holding the shift key.

Drawing Tools

Cut Removes the selected object(s) and makes a

temporary copy that may be pasted back into the
Editing Tools
edit window later.
Copy Makes a temporary copy of the selected
object(s) for later pasting.
Paste Adds the most recently cut or copied
object(s) to the Layout window.
The Background Graphics Editor Tools button Delete Deletes the selected background graphic
bar is the nearly the same Tools button bar used from the Layout window.
in the Graphic Editor. The only difference is that
Select All Selects all of the graphic objects in the
the Background Graphics Editor Tools button bar
current mode.
does not contain an entity spot or status light tool.
For more information on the Tools button bar, see Copy to Clipboard Copies all graphic objects in
“Graphic Tools Button Bar” on page 315. the current mode to the clipboard as a bitmap or
windows metafile so they can be pasted into
Edit Menu another application such as a word processor.

Use the Edit menu for selecting and duplicating Paste WMF Pastes a Windows metafile (WMF)
the graphic objects in the current Background from the Windows clipboard into the Layout win-
Graphics mode. You may also use it to exchange dow. You must have previously copied a Win-
graphics with other applications. To use the Edit dows metafile to the Windows clipboard.
menu functions, select the object you wish to edit Paste BMP Pastes a bitmap file (BMP) from the
by clicking on it in the Layout window. Windows clipboard into the Layout window. You
 ProModel 213
User Guide

must have previously copied a bitmap file to the How to move an imported background
Windows clipboard. graphic:
Import Graphic Imports a WMF, EMF, BMP,
PCX, or GIF file into the Layout window. • Place the cursor on the imported background graphic
and drag it to the desired location in the layout.
Export Graphic Exports all graphic objects in
the current mode to a WMF or BMP file.

Importing a Graphic How to size an imported background

Importing a background graphic can bring reality graphic:
into the model. For example, if a layout is created
in a graphic package, it may be desirable to 1. Place the cursor on one of the four corners of the
import the entire layout rather than create it in imported background graphic. The cursor becomes a
cross-hair at this point.
ProModel. This is done by saving the file in a
graphic package, such as AutoCAD, as a WMF, 2. Drag the cursor to size the background graphic as
EMF, BMP, PCX, or GIF file and importing the desired.
graphic into ProModel. This can save you an
extensive amount of time.

Please note
How to import a background graphic
into the layout: Once imported, the background graphic is not a
separate file from the model. It is included in the
1. In a graphics application, save the graphic in one of model. Therefore, when moving or copying a
the following formats, WMF, EMF, BMP, PCX, or
model file from one directory to another, it is not
GIF.
necessary to move or copy the imported back-
2. Select Background Graphics from the Build ground graphic file as well. On the other hand, if
menu. the external graphic file is changed, it must be re-
3. Select Front of Grid or Behind Grid. imported to update the model layout.
4. Select Import Graphic from the Edit Menu.
5. Enter the name of the graphic you would like to
import or browse to the directory where the graphic is Exporting a Graphic
located.
In some cases, it is desirable to export a graphic
6. Select OK to close the import graphic dialog box.
created in ProModel for use in another applica-
The graphic will then appear in the layout window. The
tion. ProModel will export all objects in the cur-
upper left corner of the imported graphic will align
with the upper left corner of the layout window. rent mode (In Front of Grid and Behind Grid) as
one graphic to a WMF or BMP file.

How to export a graphic:

1. Select Export Graphic from the Edit menu.

214 Chapter 5:
Background Graphics

2. Enter a valid DOS name for the graphic in the you must go to Behind Grid mode to edit the
resulting dialog box, such as forklift.bmp. graphic.
3. Click the OK button in the Export Graphic dialog Front of Grid Moves the selected object in the
box.
layout window in front of the grid. Once this is
done, you must go to Front of Grid mode to edit
the graphic.
Graphics Menu Group Combines or groups several graphic
objects into a single graphic so they may be sized
The Graphics Menu allows you to flip and rotate
and edited together.
the selected graphic object(s) in the layout win-
dow. It also allows you to specify whether you Ungroup Ungroups several grouped graphic
want the graphic to be behind or in front of the objects so they may be edited individually.
grid. Additionally, it allows you to group selected
Lock Locks a graphic in place so that it can’t be
graphic objects together into a single graphic.
moved. This is helpful for preventing accidental
Finally, it provides the option to define line
moving of a graphic that you wish to leave sta-
styles, fill patterns, line color, and fill color.
tionary.
Unlock Unlocks a locked graphic, allowing it to
be moved on the layout.
Alignment When multiple objects are selected
on the layout, they can be aligned side to side, top
to top, etc.
Line Styles Allows the user to define the line
style including transparent, dashed, line thick-
ness, and optional arrowheads on either end of
the line. If any objects are selected, the line styles
of the selected objects are changed.
Fill Patterns Allows the user to define the fill
pattern for solid objects including slant, grid,
crosshatch, backward slant, horizontal, vertical,
transparent, solid, vertical gradient, and horizon-
Flip Horizontal Horizontally flips the selected tal gradient. If any objects are selected, the fill
object(s). patterns of the selected objects are changed.
Flip Vertical Vertically flips the selected Line Color Allows the user to define the line
object(s). color and create custom colors. If any objects are
Rotate Rotates the selected object(s) 90 degrees selected, the line color of the selected objects are
clockwise. This does not apply for non-true-type changed.
fonts. Fill Color Allows the user to define the fill color
Behind Grid Moves the selected object in the and create custom colors for solid objects. If any
layout window behind the grid. Once this is done,
 ProModel 215
User Guide

objects are selected, the fill color of the selected

objects are changed.

Please note

All functions in the Graphic menu of Background

Graphics are nearly the same functions described
in the Graphic Editor Graphic menu. Differences
are noted below for moving a graphic behind the
grid and in front of the grid. See “Graphic Edi-
tor” on page 304 for more information on the
functions above.

How to move a graphic behind the

grid:

1. Select the graphic on the layout using the selector.

2. Select Behind Grid from the Graphics menu.

How to move a graphic in front of the

grid:

1. Select the graphic on the layout using the selector.

2. Select Front of Grid from the Graphics menu.
216 Chapter 5:
Background Graphics
 ProModel 217
User Guide

Chapter 6: Building the Model:

Advanced Elements

Attributes How to create and edit attributes:

Attributes are place holders similar to variables, 1. Select Attributes from the Build Menu.
but are attached to specific locations and entities
and usually contain information about that loca-
tion or entity. Attributes may contain integers or
real numbers. You may also assign model ele- Attribute Types
ment names (e.g., StationA) to an attribute, which
Attributes are classified as follows:
is stored as the element’s index number but may
be referenced by name. Attributes are defined
through the Build menu as shown below. Entity Attributes
Entity attributes are place holders assigned to an
entity and contain numerical information about
that entity. An entity attribute is identified by its
name and may be assigned a value or model ele-
ment name stored as a value. An entity attribute
may be examined and acted upon in any of the
following places:
• Arrival logic
• Operation logic
• Move logic which refers to the attribute of
the entity being routed
• Min or Max attribute rules for locations and
resources
• Routing quantity
• Routing destination priority
• Resource pick up and drop off times
• Entity speed
• Debug condition
218 Chapter 6:
Attributes

Location Attributes would be more appropriate to use a local vari-

able. Local variables act like temporary attributes
Location attributes are place holders assigned and are valid only within the logic in which they
directly to a location and contain numerical infor- are defined (see “Variables” on page 223).
mation about that location. A location attribute is
identified by its name and may be assigned a
value or model element name stored as a value. Cloning Attributes
A location attribute may be examined and acted
on in any of the following places: Whenever one entity initiates the creation of
other entities through a SPLIT AS, CREATE, or
• Arrival logic ORDER statement, or as the result of specifying
• Operation logic multiple outputs in a routing, the attributes of the
• Move logic original entity are automatically copied to each
• Min or Max attribute for selecting incoming newly created entity.
entities as a location rule
The following examples show two methods of
• Routing quantity splitting an incoming batch of material, called
• Routing destination priority BatchA, into one Tote and six EntA’s. The first
• Resource pick up and drop off times method uses a CREATE statement in the opera-
• Location down time logic tion logic to create the new entities, called EntA.
• Debug condition The original entity, BatchA, will have its name
changed to Tote in the routing table. In the sec-
ond example, both of the new entity types are
Memory Allocation for created in the routing table, so no CREATE state-
Attributes ment is needed in the operation logic. In both
cases, the attributes attached to the original entity,
Because locations always exist during a simula- BatchA, are duplicated in both Tote’s and the
tion, location attributes always use memory. EntA’s attributes.
However, attributes for entities are not created
until the first time any of the entity’s attributes
are examined or set. At that time, ProModel allo-
cates enough memory for all of the entity’s
attributes. When the entity exits the system or is
absorbed by another entity through a COMBINE
or JOIN statement, ProModel automatically frees
the memory allocated for its attributes.

Attributes vs. Local Variables

Attributes are primarily useful where the value of
the attribute is assigned in one logic section and
evaluated in another logic section or field, per-
haps at a different location. If, however, an
attribute is assigned a value and evaluated within
the same logic section (e.g., an operation logic), it
 ProModel 219
User Guide

Process Logic Notes A general notes field for describing the

attribute. Notes fields contain user comments
only and are never analyzed by ProModel. Click
on the Notes button or double click in the field to
open an edit window for entering detailed notes.

Example of Attributes in Logic

An appliance manufacturer’s model contains an
assembly location to join lids to pots. The pots
are either aluminum or steel and both types of
pots arrive at the same assembly location. If an
aluminum pot arrives at the assembly location, it
must be joined with an aluminum lid. The same
is true for a steel pot and lid. The entities,
steel_lids and alum_lids, are waiting at a queue to
be joined to the pots.
Obviously, one way to model the different pot
types is to use two different entity types. This
example shows how to achieve the same effect
Routing Table using a single entity type (pot) with an attribute
designating whether it is steel or aluminum.
An attribute called “type,” defined in the attribute
edit table, allows the location to tell what type of
pot has arrived at the assembly location. We will
use a value of 1 to represent a steel pot and a
value of 2 to represent an aluminum pot. When a
steel pot enters the system, we assign a value of 1
Attribute Edit Table to the attribute TYPE with the statement
This edit table is used to define entity and loca- TYPE=1. When an aluminum pot enters the sys-
tion attributes. tem, we set its type to 2.

ID The name of the attribute.

Type The type of the attribute, real or integer.

Classification Entity attribute or location

attribute.
220 Chapter 6:
Attributes

At the assembly location, we use the following Process Table

logic:
Entity Location Operation (min)
EntA Loc1 Att1 = 1
WAIT 2 min
EntB Loc2 Att1 = 2
JOIN 1 EntA
EntB Loc3 ...

Routing Table
Blk Output Destination Rule Move Logic
1 EntA Loc2 JOIN 1 MOVE FOR 1
1 EntB Loc3 FIRST 1 MOVE FOR 1
... ... ... ... ...

This logic checks the type of the pot and then In the above example, EntB would have an
joins a lid according to that type. attribute value, Att1, equal to 2 after EntA joined
to EntB.

Attributes and the JOIN or

Attributes and the GROUP/
LOAD PERM Statement
UNGROUP Statements
In some cases, one entity joins onto a base entity
using the JOIN or LOAD PERM statement (see Suppose several entities, EntA, EntB, and EntC,
“Join” on page 494 for more information). If both are grouped together and called Batch (see
the joining and base entities possess attributes “Group” on page 483 and “Ungroup” on
before the join occurs, the resulting joined entity page 558). Each of the original entities have
will possess the attribute values of the base entity. attributes with values assigned to them before
In other words, the entity with the IF Join (or IF they are grouped. The Batch is processed for 30
Load) routing rule is effectively destroyed when minutes, sent to Loc5 and then ungrouped into
it gets joined or permanently loaded. Consider the original entities.
the following diagram in which EntA joins to The attribute values of the individual entities are
EntB: not transferred to the grouped entity, Batch. In
other words, Att1=0 for the entity, Batch. How-
EntA
ever, once the entities are ungrouped, they retain

Join

EntB Loc2 EntB

EntA is joined to EntB.

The logic for the above diagram is as follows:

 ProModel 221
User Guide

their original attribute values. The following dia- Attributes and the LOAD/
gram graphically shows the concept of grouping.
UNLOAD Statements
EntA
Batch
EntA The LOAD statement permenantly or temporarily
Group Ungroup loads a specified quantity of entities on to a base
EntA
EntB Loc4 Loc5
entity. Temporary loaded entities retain their
EntB
EntB EntC identity for future unloading through an
UNLOAD statement (see “Load” on page 499
EntC EntC and “Unload” on page 561 for more information).
Three entities are grouped When the entities are temporarily loaded onto the
together to form a batch
which is later ungrouped. a base entity, the resulting entity retains the
attribute value of the base entity.
The logic for the diagram is as follows: For example, entities called Box are temporarily
loaded onto a base entity, Pallet. The Boxes are
Process Table assigned an attribute value, Att1=1. Pallets are
Entity Location Operation (min) also assigned an attribute value, Att1=2. Once
EntA Loc1 Att1 = 1 the Boxes are loaded onto the Pallet, the loaded
EntB Loc2 Att1 = 2 pallet is renamed Shipment. The Shipment then
EntC Loc3 Att1 = 3 has an attribute, Att1=2, because it inherits the
ALL Loc4 GROUP 3 AS Batch attribute value of the Pallet. However, we then
Batch Loc4 WAIT 30 assign an attribute value to Shipment, Att1=3.
Batch Loc5 UNGROUP After the Boxes are unloaded from the Shipment,
ALL Loc5 ... the unloaded shipment is renamed back to Pallet
and the Boxes retain their original attribute value,
Routing Table Att1=1. Now the Pallet has a different attribute
value, Att1=3, which was assigned to the
Blk Output Destination Rule Move Logic renamed entity, Shipment. Consider the follow-
1 EntA Loc4 FIRST 1 MOVE FOR 1
ing diagram and logic in which two Boxes are
1 EntB Loc4 FIRST 1 MOVE FOR 1
loaded onto a Pallet and renamed Shipment for
1 EntC Loc4 FIRST 1 MOVE FOR 1
the output entity:
1 Batch Loc5 FIRST 1 MOVE FOR 5 Box Box

... ... ... ... ...

Load Shipment Unload

Please note Pallet Loc2

Boxes
Loc4 Pallet

You can assign an attribute value to a grouped Two Boxes are loaded onto a Pallet and renamed Shipment
in the Output. The Boxes are then unloaded from
entity. However, once the entities are ungrouped, the Shipment. Shipment is renamed Pallet in the Output.
they retain the attribute values they possessed
before they were grouped. The logic for the diagram is as follows:
222 Chapter 6:
Attributes

Process Table bined entity, Box. The following diagram demon-

strates three entities combining into one entity.
Entity Location Operation (min)
Box Loc1 Att1 = 1
WAIT 2 min
EntA
Box Loc2 Att1 = 2
LOAD 2 Combine
Shipment Loc3 Att1 = 3
WAIT 20 EntB Loc4 Box
Shipment Loc4 UNLOAD 2
Box Loc4 WAIT 10
EntC
Routing Table
Blk Output Destination Rule Move Logic
Three entities are combined to
1 Box Loc2 LOAD 1 MOVE FOR 1
form a single entity called Box.
1 Shipment Loc3 FIRST 1 MOVE FOR 3
1 Shipment Loc4 FIRST 1 MOVE FOR .5
1 Pallet Loc5 FIRST 1 MOVE FOR 1 The logic for the diagram is as follows:
1 Box Loc5 FIRST 1 MOVE FOR 2
Process Table

Attributes and the COMBINE Entity Location Operation (min)

EntA Loc1 Att1 = 1
Statement WAIT 2 min
EntB Loc2 Att1 = 3
Consider the example where several entities are WAIT 3 min
combined permanently into a single entity, Box EntC Loc3 Att1 = 5
(see “Combine” on page 449 for more informa- WAIT 6
tion). The combined entity, Box, assumes the ALL Loc4 COMBINE 3
attribute values of the last entity that was com- ALL Loc5 ...
bined to the single entity. If three entities, EntA,
EntB, and EntC, are combined to form a single Routing Table
entity called Box, and EntC was the last entity
Blk Output Destination Rule Move Logic
that was combined, the Box will have the same
1 EntA Loc4 FIRST 1 MOVE FOR 1
attribute values as EntC. Therefore, if EntC had
1 EntB Loc4 FIRST 1 MOVE FOR 3
an attribute (Att1=5), then Att1=5 for the com-
1 EntC Loc4 FIRST 1 MOVE FOR .5
1 Box Loc5 FIRST 1 MOVE FOR 1
... ... ... ... ...

In the above example, EntC is the last entity to be

combined so the entity Box assumes the attribute
value of EntC, Att1=5.
 ProModel 223
User Guide

Variables Variable Edit Table

Variables are of two types: global and local. Glo- This edit table is used to define Variables used
bal variables are place holders defined by the user globally in the model. A description of each field
to represent changing numeric values. Local vari- is given below.
ables are place holders which are available only
within the logic that declared them. Variables can
contain either Real numbers or Integers, includ-
ing element index values, and are typically used
for decision making or recording information. A
Icon This field shows “Yes” if an icon for the
global variable can be referenced anywhere
variable appears on the layout. A variable’s icon
numeric expressions are allowed in a model. If a
looks like a counter and displays the variable’s
variable or attribute is needed only in a single
value.
block of logic, it is easier to define a local vari-
able right inside the logic block. Global variables ID The variable’s name.
are defined in the Variables Editor, accessed from
Type The type of variable, real or integer.
the Build menu. Local variables are defined with
the INT and REAL statements. (See “Local Vari- Initial Value The initial value of the variable to
ables” on page 225 for more information.) be assigned at the start of the simulation. By
default, initial values are 0, but can be changed in
the edit table to whatever value you want. Any
expression can be entered here (including previ-
ously defined variables) except attributes and
system functions.
Stats ProModel collects statistics for each vari-
able on three levels of detail, None, Basic, and
Time Series.
• None No statistics are collected for this
variable during simulation.
• Basic Collects basic statistics such as total
changes, average minutes per change, cur-
rent value, and average value.
• Time Series Collects all the basic statistics
plus the value history based on time or
observations. When you select Time
Series, ProModel collects either time-
How to access the variable edit table: weighted or observation-based statistics

1. Select Variables (global) from the Build menu.

224 Chapter 6:
Variables

for the variable depending upon the type Please note

selected.
In order to create plots or histograms for a vari-
able, Time Series stats must be selected in the
variables edit table.

Variable Layout
An icon to show a variable’s value during a simu-
lation may be placed anywhere on the layout. The
Variable Observation window below shows the icons for the variables
Record Value Time in Hours Current and Total at the right side of the screen.
Observation 1 6 1 Each icon has been labeled with a background
Observation 2 5 2 graphic.
Observation 3 6 3
Observation 4 5 4
Total 22 10

Time-Weighted Collects information on the per-

centage of time the variable was at a specific
value. As shown in the above table, the average
value of the variable is:
(6 x 1) + (6 x 3) + (5 x 2) + (5 x 4) = 5.4
10
Observation-Based Collects information on the
number of times the variable changed to a spe-
cific value. As shown in the above table, the
value of the variable is 6, then 5, then 6, then 5. How to place an icon for a variable on
The average would simply be: the layout:
6+5+6+5 = 5.5
1. Highlight the desired variable in the Variable edit
4 table.
Notes A general notes field for describing the 2. Click on the layout where the icon is to appear.
variable. Click on the Notes button or double
3. Size the icon by dragging an edge or corner of the
click in the field to open an edit window for
sizing box.
entering detailed notes.
 ProModel 225
User Guide

How to remove an icon for a variable Local Variables

from the layout:
Local variables function as though they were
temporary attributes defined in a specific logic
1. Double click on the icon.
section which disappear when the logic section is
2. Choose Delete from the resulting menu. The icon is finished executing. Local variables are useful for
removed from the layout, but the variable remains in test variables in loops and storing locally used,
the model. unique values for each entity at the current loca-
tion.
Local variables are used within a block of logic
Editing a Variable’s Icon (i.e., operation logic, subroutines) and are
declared with an INT or REAL statement. Local
A variable’s icon can be customized as necessary variables are only available within the logic in
by simply double clicking on the icon and choos- which they are declared and are not defined in the
ing Edit. A dialog box appears as shown below Variables edit table. A new local variable is cre-
for specifying the characteristics of the variable ated for each entity to encounter an INT or REAL
icon or counter. statement (See “Int” on page 492 and “Real” on
page 529). A local variable is specific to each
entity, in much the same way an attribute is spe-
cific to an entity, except that the local variable is
only available while the entity processes the logic
to declare the local variable. Local variables may
be passed to subroutines as parameters. Local
variables are available to macros.

Example
A plant manufactures valves of 10 different sizes,
How to edit a variable’s icon: such as 10'', 20'', .... All valves are inspected at a
common inspection station and then move to a
dock where they are loaded onto pallets. The pal-
1. Double click on the icon.
lets are designed to hold only a certain size valve.
2. Click on the Digit Color, Frame, or Font buttons to Therefore, a pallet designed to hold 10'' valves
adjust the respective setting. can only hold 10'' valves, not 20'' valves.
3. Click on OK.
Suppose a Pallet enters a multi-capacity location,
4. All other variable icons that you create from now on Dock. Each Pallet has a different entity attribute,
will retain these modifications. p_type, describing the type of valve it can hold.
Valves are loaded onto the Pallet. The 10” valves
must be loaded onto the pallet designed to hold
the 10” valves. Therefore, the attribute value of
the Valve, v_type, must match the attribute value
of the Pallet, p_type. We can use local variables
226 Chapter 6:
Variables

to accomplish this modeling task. The logic is as enced in the LOAD statement. The pallet
follows where X is a local variable: attribute cannot be directly referenced in the
LOAD statement.
Process Table
If Dock was a single capacity location, using a
Entity Location Operation (min) global variable would work the same as using a
Valve Inspect WAIT 5 local variable. However, because Dock is a
Pallet Dock INT X multi-capacity location, it can load valves onto
X = p_type multiple pallets at the same time. If a global vari-
LOAD 10 IFF able was used instead of a local variable, the glo-
X = v_type
WAIT 10 bal variable would change each time a pallet
entered Dock. If there were two different types
Routing Table of pallets at Dock, there would be only one type
of valve loaded on the pallet because the global
Blk Output Destination Rule Move Logic variable refers to both pallets.
1 Valve Dock LOAD 1 MOVE FOR 2
1 Pallet Delivery FIRST 1 MOVE FOR 8
Suppose, for example, a global variable, type,
signifies the pallet attribute, p_type. We assign
If we had not used local variables, we would need type=p_type at the beginning of the operation
to use the following operation logic for Pallet at logic for location Dock. The first pallet arrives
Dock: and type=3. Therefore, only valves with
v_type=3 are loaded onto the pallet. Another pal-
let enters Dock and type=5. Now only valves
with valve_type=5 are loaded onto both pallets.

Please note

Local variable notes:

1. You may not use the WAIT UNTIL statement
with local variables.
2. The local variable definition only needs to
appear somewhere in the logic before being ref-
erenced. The entity does not need to execute the
As can be seen from the two examples of logic, local variable definition statement (INT, REAL).
the first example is much easier and more straight
forward.
It is important to note that using “LOAD 10 IFF
p_type = v_type” in the operation logic would not
work for the intended purpose. Attributes refer-
enced in IFF conditions always refer to the entity
being loaded. Set the value of a local variable, X,
to the pallet attribute, p_type, so it can be refer-
 ProModel 227
User Guide

Arrays Arrays are defined in the Arrays editor accessed

through the Build menu.
An array is a matrix of cells that contain real or
integer values. Each cell in an array works much
like a variable, and a reference to a cell in an
array can be used anywhere a variable can be
used. A one-dimensional array may be thought of
as a single column of values. A two-dimensional
array is like having multiple columns of values
(similar to a spreadsheet).
To reference a cell in a one-dimensional array,
give the name of the array and enclose the cell
number in brackets. For example, if a one-dimen-
sional array containing ten cells is named OpnAr-
ray, to reference the fifth cell you would use
OpnArray[5]. To reference a cell in a two-dimen-
sional array, simply use the name of the array
with the row and column number in brackets. For
example, the statement OpnArray[3,4] references
a cell on the third row in the fourth column.
How to use the arrays editor:
Arrays with more than two dimensions are more
difficult to picture, but work exactly the same as
1. Select Arrays from the Build menu.
one and two dimensional arrays. For example, if
an array has a third dimension, you can reference
any cell simply by adding a comma before the
number of the desired cell in the third dimension. Example Arrays
For example, Tool[3,5,8]. Four and five-dimen- The following examples show how elements are
sional arrays work the same way. The maximum referenced in a one-dimensional array with five
number of dimensions for an array is 20. cells and in a two-dimensional array with fifteen
Array cell values are assigned in the exact same cells.
way as you would assign a value to a variable.
For example, to assign the value 18 to the cell at One-dimensional array
the fifth row and second column in an array OpnArray[5]
named Arr1 you would use the following state-
Cell[1]
ment.
Cell[2]

Assign array cell value Cell[3]

Cell[4]
Arr1[5,2]=18 Cell[5]
228 Chapter 6:
Arrays

Two-dimensional array if your .xls file is in the same directory as your

.mod file, simply enter the name of the .xls file
Tool[3,5]
into this field.
Cell[1,1] Cell[1,2] Cell[1,3] Cell[1,4] Cell[1,5]
See “Export Arrays to Spreadsheets” on page 231
Cell[2,1] Cell[2,2] Cell[2,3] Cell[2,4] Cell[2,5]
for more information on using the Export dialog.
Cell[3,1] Cell[3,2] Cell[3,3] Cell[3,4] Cell[3,5]
Disable: Use this option to have the import file,
export file, or both ignored during simulation
Arrays Edit Table without deleting the name of the import or export
files from the Array record. Choose “None” to
The Arrays edit table is used to define Arrays that use the specified import and export files.
are used in the model. The fields of the Arrays
edit table are explained on the following page. Persist: When running multiple replications you
may choose to keep the values in the array from
one replication to the next or clear (reset) the
array values every replication.
For example, if you run a simulation for three
ID: The name of the array. scenarios with an array that “Keeps” its values,
Dimensions: The size of each dimension of the the data in the array at the end of the first replica-
array in cells. For example, the dimensions of a tion will be kept and used as the second replica-
one-dimensional array of 100 cells is “100.” tion begins. If you are using an Import File, it will
Likewise, a two-dimensional array with 50 rows be used to populate the array for the first replica-
and five columns would have dimensions of tion, but ignored for subsequent replications
“50,5.” The number of rows is first, followed by when “Keep” is selected for the array.
a comma and then the number of columns. An If you choose to “Clear” the array, no array infor-
array cannot have more than 20 dimensions. mation will be kept from one replication to
Type: The type (integer, real, string, or expres- another and the array will be reset with its initial
sion) for all cells in the array. information at the beginning of each replication
(see the next heading “Initializing Arrays”). If
Import File: The name of the spreadsheet from you are using an Import File, it will be used to
which you will populate the array. You may enter populate the array at the beginning of each repli-
either a fully qualified path to your .xls file or a cation when “Clear” is selected for the array.
path relative to your .mod file. For example, if
your .xls file is in the same directory as your Notes A general notes field for entering descrip-
.mod file, simply enter the name of the .xls file tive information about the array. Click the head-
into this field. ing button or double click in this field to open a
larger window for entering notes.
See “Import Data into Arrays” on page 229 for
more information on using the Import dialog. The window pictured above shows how to define
the example arrays that appear on the previous
Export File: The name of the spreadsheet to page.
which you will save the array data. You may
enter either a fully qualified path to your .xls file
or a path relative to your .mod file. For example,
 ProModel 229
User Guide

Initializing Arrays Import Data into Arrays

By default, all cells in an array are initialized to When you import data, from either an external
zero. Initializing cells to some other value should Excel spreadsheet or SQL database, into an array,
be done in the initialization logic. A ProModel loads the data from left to right, top to
WHILE...DO loop is useful for initializing array bottom. Although there is no limit to the quantity
cell values. The logic below fills a 3 x 5 array (3 of values you may use, ProModel supports only
rows and 5 columns) with values from an exter- two-dimensional arrays.
nal, general read file.
Import from an Excel Spreadsheet

This example uses the variables Column and

Row (which may be defined as local variables)
along with two WHILE...DO loops to assign
every cell in the array Inventory_Array a value
from a general inventory file. The logic first sets
the value of the variable Column to one. It then Import File The name of the spreadsheet you will
assigns all the cells in column one a value by use. You may enter either a fully qualified path to
reading a value from the external file and incre- your .xls file or a path relative to your .mod file.
menting the variable Row. When all the cells in For example, if your .xls file is in the same direc-
column one have a value, the logic increments to tory as your .mod file, simply enter the name of
the second column and does the inside loop the .xls file into this field.
again. It repeats this loop until each cell in the
array has a value. Sheet Name The name of the sheet from which
you will import the array data.
Please note
Please note
Assigning values to a cell in an array can be done
in any expression or logic field, such as initializa- If your spreadsheet contains only a single data
tion and operation logic. See “Execution Time of set, ProModel will automatically load the data
Initialization and Termination Logic” on into the array—you do not have to define any cell
page 172 for a list of logic elements used to information unless you wish to limit the contents
define model parameters. of the array to a portion of the data set.
230 Chapter 6:
Arrays

Array import requires Microsoft Excel 97 or Import from a SQL Database

later.

Import Start Cell The first piece of data to place

into the array.
Import End Cell The last piece of data to place
into the array.

How to import Excel spreadsheet data

into array:

1. Select Arrays from the Build menu.

2. Select or create the array record (row) you wish to Connection String The connection string used to
import. connect to the SQL database including all neces-
3. Click the Import File button on the Arrays dialog. sary security parameters.

4. In the File field, enter the name of the spreadsheet Query or Stored Procedure Enter the SQL query
you wish to use (you may also browse to select a file). or the name of the stored procedure to be exe-
cuted during the model’s initialization logic to
populate the array.

How to import SQL database data into

array:

1. Select Arrays from the Build menu.

2. Select or create the array record (row) you wish to
import.
3. Click the Import File button on the Arrays dialog.

5. In the Sheet Name field, enter the name of the

worksheet that contains the data you wish to use.
6. Enter the Import Start Cell location. The value in
this cell will occupy the first position in the array.
7. Enter the Import End Cell location. The value in
this cell will occupy the last position in the array.
8. Click OK.
 ProModel 231
User Guide

4. Click on the Database radio button. with new data. If you wish to prevent your data
from being overwritten, you can make a backup
of the spreadsheet between each running of the
simulation.
If you are running multiple scenarios and/or rep-
lications, see step 5 below for a description of
how the spreadsheet handles the multiple scenar-
ios/replications.

How to export array data:

1. Select Arrays from the Build menu.

2. Click the Export File button on the Arrays dialog.
3. Enter the name of the spreadsheet file you wish to
5. In the Connection String field enter the necessary
use, or browse to select a file.
string to connect to the desired database.
6. In the Query or Stored Procedure field enter the
SQL query or stored Procedure name that will be used
to populate the array during the initialization logic.
7. Click OK.

Export Arrays to Spreadsheets

4. Click OK.
5. When the simulation is run, the array data will be
saved to the spreadsheet file. If you ran multiple sce-
narios and/or replications, data from each one will be
saved to a separate sheet in the spreadsheet file, as seen
below.

The fields in the Export Arrays dialog have simi-

lar functionality as those for the Import Arrays
dialog.
If you export multiple times to the same spread-
sheet, ProModel will overwrite the spreadsheet
232 Chapter 6:
Arrays

Using Arrays mation and then Arrays. This information

can also be printed.
Using arrays can simplify a model. Suppose you 4. Arrays can be used with the WAIT UNTIL
need to model an assembly line that attaches statement.
components to a computer motherboard. Fur- 5. Statistics are not generated for arrays. How-
thermore, you want to track the usage of compo- ever, if you would like to see the final value
nent parts over time. Without an array, hundreds of an array’s cell, you can use the array
of individual entities of various types would have export feature to export to Excel, you can
to represent hundreds of individual components. place a PAUSE statement in the termination
Keeping track of all the components would be logic and then view the array under the
very complex, not to mention all of the join oper- Information menu, or you could print an
ations and routings for performing the assembly. array’s values or write them to an external
Instead, various cells in a one-dimensional array file as part of the termination logic. If you
could track the number of each type of compo- want more statistical information on a partic-
nent used during the simulation. ular cell, assign the cell to a variable and
An array can do the job more efficiently. The ini- then choose basic or time-series statistics for
tial inventory level for each component could be the variable.
stored in an external file and read into the cells of
the array at the start of the simulation. The first
cell might contain the inventory level of transis-
tors; the second could contain the inventory level
of capacitors and so on. When a motherboard
arrives at the location adding the components,
each cell’s value is decremented according to the
number of that type of component joined to the
motherboard. If each motherboard requires
twelve transistors and five capacitors, then every
time a motherboard arrives at the location, the
array’s first cell is reduced by twelve and the sec-
ond cell is reduced by five. Thus the model
becomes much less complex because it requires
fewer entities and less logic.

Notes on Arrays
1. If a warm-up time is specified, array values
are not reset.
2. Arrays can be nested. For example, if
Arr1[2,3] is equal to three, then the state-
ment Arr2[5,Arr1[2,3]] works exactly like
the statement Arr2[5,3].
3. You can examine the value of a cell in an
array during a simulation by choosing Infor-
 ProModel 233
User Guide

Macros Text Any text to be substituted where the macro

name is called. This text may be a complete
A macro is a place holder for an often used expression, an entire logic block, or even part of a
expression, set of statements and functions, or logic block.
any text that might be used in an expression or
Options Allows you to define the macro as a
logic field. A macro can be typed once, and then
run-time interface parameter or select a resource
the macro’s name can be substituted for the text it
group.
represents anywhere in the model and as many
times as necessary. Macros are defined in the The example table above defines three macros.
Macros Editor, accessed from the Build menu. The first macro is simply a numeric constant,
with fpm representing a conversion factor from
miles per hour to feet per minute. If a number is
used in multiple places in a model, then a macro
makes it possible to change that number through-
out the model simply by changing the macro
itself. The second macro, Operation_Time, calcu-
lates the various operation times at different loca-
tions depending on the attributes at the locations.
The last macro, Number_of_AGVs, is a run-time
interface variable used to define the number of
AGVs in the simulation model (see “Run-Time
Interface” on page 234).
A macro is different from a subroutine because a
macro cannot pass or return a value. However,
because it is simply a text replacement, a macro
can reference any expression valid in the expres-
sion or logic field that called the macro. For
instance, the string “the number of entries is”
How to create and edit macros: might be a macro called mac1. This macro by
itself is not a valid expression. However, when
1. Select Macros from the Build Menu. used with the DISPLAY statement in the opera-
tion logic (i.e., DISPLAY mac1), the compiler
will recognize the macro as a string.
Macro Editor A macro may be used in any expression field, but
may only contain a numeric expression (e.g.,
The Macro edit table is used to assign recurring Entries (LOC1), U(5,1), Var1+Att2, etc.). In
text to a reference name. addition, a macro used in an expression field may
not contain multiple lines of text. When used in a
logic field, the macro may include any logic ele-
ment valid in that logic field.
Suppose five different locations use the same
ID A name to identify the macro. lines of code. Instead of entering the same logic
234 Chapter 6:
Macros

five times in five different fields, reference the Please note

following macro by typing the macro ID, Mac1,
in the operation logic of the machine:
Macro notes:
1. A macro may be used only when the elements
contained in the macro are appropriate to the
context from which it was called. This restriction
means that the macro in the previous example is
only valid in operation logic.
2. Because a macro simply substitutes some text
for its name, if a macro represents a statement
block, then it should contain a BEGIN at the
beginning of the block, and an END at the end of
the block. This technique is especially important
when using a macro immediately after a control
statement, such as IF...THEN or WHILE...DO.
For more information, see “Statement Blocks” on
page 426.
Every time the macro is referenced, the logic is
executed. Macros can also be nested within other
macros. This means that a macro can consist of
one or more other macros. Consider the follow- Run-Time Interface
ing Macro edit table:
Defining a run-time interface (RTI) for a macro
allows the user to easily change simulation/model
parameters before the simulation starts. It also
provides an experimental framework for defining
multiple scenarios to be run in a batch (see “Sce-
narios” on page 343). An RTI for a macro allows
a macro’s text to be changed by the user when-
ever a simulation run begins. Since macros are
The macro, Favorite_Quote references other
allowed in any expression, this gives the user
macros, such as Race and Finish. Note that some
flexibility to edit most model parameters every
of the other macros, such as For_Quality, are only
time a simulation starts without having to directly
portions of a complete line of code. Although the
edit the model data.
macro is valid, it will not compile as a part of
macro logic because the create statement requires The key difference between a macro with an RTI
an expression and an entity name. The line and one without is that when a simulation begins,
Favorite_Quote in a logic field would be inter- a macro defined with an RTI provides a menu
preted as the following line, Create 2 As EntB that allows users to change only the macros you
Take 1 Res1. want them to change. An RTI allows you to
request a variety of information to substitute for a
macro; from simple values (e.g., the initial value
 ProModel 235
User Guide

of a location’s capacity) to complex text (e.g., a tions to find the combination that works best with
line of logic). You may create RTI parameters your model.
using the dialog box below, accessed through the
Numeric Range This specifies the lower and
macros dialog.
upper limits for the parameter if the type is
numeric.

How to define an RTI for a macro:

1. Select Macros from the Build menu.

2. Type the macro name and click on the Options but-
ton.
3. Choose Define from the RTI submenu.
4. Define the Parameter Name and enter the prompt
(optional).
5. Select the parameter type: Unrestricted Text,
Record Range, or Numeric Range.
Parameter Name This text will identify the
parameter represented by this macro. It should 6. If the parameter is numeric, enter the lower value in
consist of text that clearly describes the parame- the From box and the upper value in the To box.
ter to be changed, for example, Operation Time. 7. Click OK.
The macro name and the parameter name can be
8. Enter the default text or numeric value in the Macro
different. This provides more flexibility and Text field.
allows you to view a more descriptive parameter
name when defining scenarios. 9. Use the macro ID in the model (e.g., in operation or
resource usage time).
Prompt This text will appear if the user decides
to change the parameter. You should use it to fur-
ther specify the information to be entered, for
example, “Please enter the amount of time the Please note
simulation should run.”
Unrestricted Text This option allows the user to When using a record range, be sure to group all
enter any text, such as the distribution U(8,2). arrival and shift records. This will allow you to
Note that any text that the user enters will be sub- select which series of records to include in the
stituted for the macro name in the model. There- macro. Note also that when you define an arrival
fore, the text the user enters must be syntactically or shift RTI, ProModel adds “ARRIVAL_” or
correct and valid anywhere the macro name “SHIFT_” to the name to help you identify the
appears. macro more easily.

Record Range Allows you to enable an arrival or

shift record from a range of records. This allows
you to test a variety of shift and arrival combina-
236 Chapter 6:
Macros

Run-Time Interface Example You are now able to change the operation time at
Lathe_1 using the Model Parameters option in
Suppose you build a factory model and determine the Simulation menu. For more information on
the first lathe, Lathe_1, is a bottleneck. The changing model parameters and defining scenar-
model results indicate the throughput is lower
ios, see “Model Parameters & Scenarios” on
than expected. You decide to perform several
page 342.
what-if scenarios with the model by changing the
operation time of Lathe_1. Instead of changing
the operation time at Lathe_1 within the Process Please note
edit table, it is easier to define a macro with an
RTI. This technique allows the model user to For more information concerning the differences
easily see the effect of installing a faster lathe between macros and subroutines, see “Macros”
without ever editing the model itself. The fol- on page 233 and “Subroutines” on page 238.
lowing example represents the dialog used to
define the RTI for the macro where the operation
time is a numeric value between 12 and 20:
Resource Grouping
Resource grouping allows you to define specific
groups of resources rather than define each unit
separately. For example, suppose you need a spe-
cific technician to perform an operation. If the
technician is not available, you may use either
another technician or one of two qualified opera-
tors to perform the operation. Rather than define
each qualified operator as a separate resource,
you may define a macro that includes them.

How to define a resource group

After defining the RTI for the macro, substitute
1. Select Macros from the more elements section of
the macro, Oper_Time, for the operation time in
Build menu.
the operation logic in the Process edit table for
Lathe_1 as shown below: 2. Define a macro ID and enter a list of all resources
you wish to include as part of the resource group.

Please note

When you create a list of resources, separate

each resource using AND or OR (e.g., Tech_1
AND Tech_2 OR Tech_3 AND Tech_4).
 ProModel 237
User Guide

3. Click on the Options button and select Resource

Group from the submenu.

At the end of the simulation, ProModel creates a

statistical report containing information collected
for each resource included in the resource group,
as well as the entire group. This will allow you to
track individual, as well as group performance.
For information on statistics and how to graph the
results, see “Reports and Graphs” on page 363.
238 Chapter 6:
Subroutines

Subroutines Subroutines are defined in the Subroutines Editor

which is accessed from the Build Menu.
A subroutine is a user-defined command that can
be called to perform a block of logic and option-
ally return a value. Subroutines may have param-
eters (local variables) which act as variables local
to the subroutine and that take on the values of
arguments (i.e., numeric expressions) passed to
the subroutine.
ProModel handles subroutines in three ways.
First, a subroutine may be processed by the call-
ing logic as though the subroutine is part of the
calling logic. This way is the most commonly
used, and is done by simply referencing the sub-
routine by name in some logic or expression.
Second, a subroutine may be processed indepen-
dently of the calling logic so the calling logic
continues without waiting for the subroutine to
finish. This method requires an ACTIVATE state-
ment followed by the name of the subroutine (see
“Activate” on page 431), or you may use the How to create and edit subroutines:
Interact Menu (see “Run-Time Interact Menu” on
page 358). Third, ProModel allows subroutines 1. Select Subroutines from the Build menu.
written in an external programming language to
be called through the XSUB() function.
Subroutine Editor
The Subroutines edit table consists of several
fields which identify the components of a subrou-
tine. Each of these fields is described below.

ID A name that identifies the subroutine.

Type The type of numeric value returned by the

subroutine can be Real, Integer, None, or Interac-
tive. Use Real and Integer if the subroutine
returns a number and None when no return value
is expected, as is often the case in initialization or
termination logic. Subroutines of type Interactive
 ProModel 239
User Guide

are identical to subroutines of type None, except fore, independent subroutines can run in parallel
that interactive subroutines are also accessible for with the logic that called them.
activation by the user through the run-time menu.
4. Independent subroutines called with the ACTI-
Interactive subroutines are displayed in the Inter-
VATE statement cannot contain entity-specific or
act menu during runtime. For more information
location-specific system functions.
on Interactive subroutines, see the discussion
later in this section.
Parameters Arguments passed to the subroutine
get assigned to local variables called parameters. Subroutine Format
Items passed to a subroutine as arguments can
have different names than the parameters that A subroutine may be named any unique, valid
receive them. Parameters can be real or integer. name. The general format for calling a subrou-
The first parameter receives the first argument, tine is as follows:
the second parameter receives the second argu- SubroutineName(arg1, arg2,....,argn)
ment, and so on.
Logic One or more statements to be executed Subroutine call
whenever the subroutine is called. Statements in
subroutines must be valid in the logic that calls GetOpTime(3,7)
the subroutine. Subroutine logic may contain a
DoInitialization()
RETURN statement with a value to be returned
from the subroutine. (See “Return” on page 539
for the correct syntax and an example of this
statement.) Please note
Please note Subroutine format notes:

Subroutine editor notes: 1. If no arguments are specified, open and closed

parentheses are still required.
1. If the subroutine is of type Integer and the
return value is a real number, the return value 2. Statements in subroutines must be valid in the
will be truncated unless the ROUND() function is logic that called the subroutine. For example, if a
used (e.g., RETURN ROUND(<numeric expres- subroutine is called from the operation logic, the
sion>)). subroutine may contain only those statements
2. If you do not want a stand-alone subroutine valid in the operation logic. Subroutines called
referenced in operation logic to be treated as an from an ACTIVATE statement or from the Inter-
implicit wait statement, define the subroutine as act Menu at run-time can have any general logic
type None. statements, including WAIT.
3. When using the ACTIVATE statement to call a 3. A subroutine may be used in any logic field. In
subroutine, the calling logic continues without addition, a subroutine may be used in any expres-
waiting for the called subroutine to finish. There- sion field, provided that the RETURN statement
is used to return a value to the expression field.
240 Chapter 6:
Subroutines

Expression fields include the Qty Each column of routing are shown below. The subroutine itself is
the Arrivals edit table and the routing rule for shown later in this section.
processing.

4. If a subroutine does not return an expression

with the RETURN statement, a value of zero will
be returned for subroutines of type Real and Inte-
ger. No value will be returned for a subroutine of
type None or Interactive.

Subroutine Example
Suppose that you build a Copy Center model and
it is necessary to define the processing time at the
operator assisted machines as a function of two
parameters: Order Quantity and Quality Level. In
addition, you would also like to write the pro-
cessing times at each copy machine to a file
called Report.Dat. Subroutines Edit Table
Because the operation logic is identical at both The Subroutine edit table lists the name of the
machines, a subroutine may be used to execute subroutine, the return type, the parameters to be
the group of statements required. Notice in the passed to the subroutine, and the logic. Notice
Process Logic pictured next that Subroutine that the subroutine ID corresponds to the subrou-
OrderTime is called, and each order's Quantity, tine name called in the processing logic above
Quality, and Ticket attributes are passed as argu- and that the subroutine has four parameters (P1,
ments. The third argument is simply a constant P2, P3 and P4) corresponding to the four argu-
value, 1 or 2, which represents the location from ments passed to the subroutine. Also note that
which the subroutine was called (i.e., 1 if called the subroutine is of type real since the return
from OpAsist1 or 2 if called from OpAsist2). The value will be a real valued processing time.
operation logic, which calls the subroutine, and

Subroutine Parameters
The subroutine parameters, M (for mean) and SD
(for standard deviation), are defined by clicking
on the Parameters heading button. These values
are unique to each inspection location, and are
 ProModel 241
User Guide

passed to the subroutine as parameters of the nor- upon the quality level desired. Operation time is
mally distributed inspection time. determined by simply multiplying the process
time by the scale factor.
Once the order time has been determined, this
value is written to the file Report.Dat. Included
with the operation time is the job number and the
location at which the job was processed.
The last line of the logic returns the order time
value to the processing logic.

Subroutine Logic Interactive Subroutines

The final step in defining the subroutine is to
Interactive subroutines are subroutines activated
specify the logic to be processed when the sub-
by the user anytime during run-time by choosing
routine is called. In this example, the logic should
the subroutine from the Interact menu. The name
include a processing time, a procedure to write
appearing in the Interact menu is either the sub-
the values of the attributes to a file, and a routing
routine name or if a string is entered as a com-
decision based on the values of the two attributes.
ment statement at the beginning of the subroutine
The logic window is accessed by clicking on the
logic, the string is used as the name (e.g., #
Logic heading button.
“Arrival Frequency”). Interactive subroutines
allow the user to interact with the simulation dur-
ing run-time. Subroutines are defined as type
Interactive in the Subroutine edit table. Normally,
subroutines are activated by entities. However,
interactive subroutines can be user-activated in
addition to being entity-activated. Interactive
subroutines can be used for:
• changing model parameters during a simula-
tion run
• changing routings
• calculating and reporting user-defined statis-
tics
Suppose you want to interactively change the
The first line of the logic calculates the order time arrival frequency for a certain entity, customers,
as a function of the Quantity and Quality during run time. Define a variable, Var1, and
attributes passed as parameters. These parame- assign it an initial value to be used for the initial
ters are used as arguments in two user defined arrival frequency. Enter Var1 in the arrival fre-
functions, ProcTime() and QualFactor(). Func- quency field for the entity customers. Create a
tion ProcTime() returns a time value based on the
number of copies in the order, while function
QualFactor() returns a scale factor depending
242 Chapter 6:
Subroutines

subroutine of type Interactive and enter the fol- knowledge of your external programming lan-
lowing logic: guage (C, C++, Pascal) to use external subrou-
tines. In addition, you must also have a good
Windows platform knowledge, specifically with
respect to creating DLLs in your language.
Because it is a 32-bit program, ProModel can
load and call only 32-bit DLLs, and requires that
you use a 32-bit Windows compiler.
For more information about this feature, you can
load, study and run XSUB.MOD in the reference
model directory (also see “Xsub()” on page 573).
This model uses XSUB.DLL, found in the MOD-
ELS directory. The source code and make files
for XSUB.DLL (XSUB.CPP, XSUB.MAK,
During run-time, you can then change the arrival XSUB.IDE) are also included in the MODELS
frequency for the customers by choosing the Cus- directory. Some general explanation is contained
tomer Arrivals from the Interact menu (see “Run- in the comments of this source code.
Time Interact Menu” on page 358).
Due to the complexities of Windows program-
ming and the variety of uses for this advanced
Please note feature, PROMODEL Corporation can only pro-
vide minimal support for this feature. Many ques-
Interactive subroutines may also be called from tions regarding Windows programming and other
any logic or expression where no return value is programming languages cannot be handled
required. See “Statements and Functions” on through our customer support department. Please
page 429 for more information. consult your language programming manuals,
language customer service centers, Microsoft,
and other resources to resolve these types of
problems.
External Subroutines
There may be some cases where you need to per- Subroutines vs. Macros
form actions ProModel is not capable of doing.
You may need extended capabilities with more Although subroutines and macros work similarly,
sophisticated commands. ProModel allows you they have subtle differences. Any logic may use
to interface with external subroutines located in both macros and subroutines. The main differ-
thirty-two bit Windows DLL files you have cre- ence is in the way they are used. Only subrou-
ated. This feature could be useful for doing tines can be used when you need to pass
sophisticated file I/O, performing statistical anal- arguments, get a return value, or activate the
ysis, making your simulation interactive, or help- independent execution of logic. Only macros can
ing with other simulation needs. be used when defining run-time interface param-
eters.
Because of the intricacies of the Windows devel-
opment environment, you must have a sound
 ProModel 243
User Guide

Macros may be used in any expression field, but

the macro may only contain an expression (i.e.,
Entries(LOC1), U(5,1)). When a macro is used in
a logic field, the macro may include any logic
element valid in that logic field.
Subroutines may also be used in an expression
field provided that the RETURN statement is
used to return a value to the expression field.
When a subroutine is used to represent one or
more logic statements, the subroutine may only
include statements valid for the particular con-
text.
244 Chapter 6:
Arrival Cycles

Arrival Cycles Arrival Cycles Edit Table

An arrival cycle is a pattern of individual arrivals Arrival cycles are defined by entering the proper
which occurs over a certain time period. Some data into the Cycle edit table. The fields of the
examples of arrival cycles that exhibit a pattern Cycle edit table are explained below.
are the arrival of customers to a store and the
arrival of delivery trucks to a truck dock. At the
beginning of the day, arrivals may be sparse; but
as the day progresses, they build up to one or
more peak periods and then taper off. While the
ID The cycle name.
total quantity that arrives during a given cycle
may vary, the pattern or distribution of arrivals Qty / % Select either Percent or Quantity as the
for each cycle is assumed to be the same. basis for the total number of arrivals per cycle
occurrence.
Arrival Cycles are defined in the Arrival Cycles
edit table, accessed through the Build Menu. Cumulative... Select Yes to specify the % or Qty
values in a cumulative format. Select No to spec-
ify these fields in a non-cumulative format.
Table... Click on this button (or double click in
this field) to open an edit table for specifying the
cycle parameters.

Arrival Cycles Example

Suppose we are modeling the operations of a
bank (or any service or manufacturing system)
and we need to specify a pattern for customer
arrivals. From past data, we know that customers
arrive throughout the day (9:00 AM to 5:00 PM)
according to the following approximate percent-
ages.
From Before Percent

How to edit arrival cycles: 9:00 AM 10:30 AM 0

10:30 AM 11:30 AM 10
1. Choose More Elements from the Build Menu. 11:30 AM 1:00 PM 25
1:00 PM 4:00 PM 55
2. Choose Arrival Cycles. 4:00 PM 5:00 PM 70

Defining the Arrival Cycle

The arrival cycle will be named Bank_Arrivals in
the Arrival Cycles edit table. Because the data is
 ProModel 245
User Guide

expressed in terms of percentages, we select Per- record for the bank example appears below. (See
cent as the basis for the cycle. Also, the percent- “Arrivals” on page 156 for more information.)
age values are not cumulative so we specify No
in the Cumulative field.

The total number of customers per day is nor-

mally distributed with a mean of 1000 and a stan-
Next, we click on the Table heading button to dard deviation of 35. The number of occurrences
open another edit table for entering the cycle of the cycle is 20, representing 20 working days
data. (1 month) of time. The frequency in this case
refers to the period of the cycle or the time
between the start of one cycle and the start of the
next cycle, which is every 24 hours. Make sure
the arrival frequency is defined with the same
time unit as the arrival cycle.
Without an arrival cycle, all the Customers for a
single day would arrive at the start of the simula-
tion. An arrival cycle will divide the quantity
specified in the Qty each... field into various
In this example, even though the percentages of sized groups arriving throughout the day.
customers that have arrived are not cumulative,
the time is always cumulative. Therefore, the To assign the arrival cycle to the arrival record,
table reads as follows: ten percent of the daily click on the Qty each... heading button to open a
customers arrive in the first 1.5 hours, fifteen per- dialog with the names of all defined cycles.
cent of the daily customers arrive between hour
1.5 and 2.5, and so on. The arrivals are randomly
distributed according to a Uniform distribution
during the time interval in which they arrive.
The arrival cycle is now defined and can be
assigned to an arrivals record in the Arrivals edit
table.

Assigning Arrivals to the Arrival

Cycle
After an arrival cycle has been defined, assign an
arrival record to the arrival cycle in the Arrivals
edit table for the arriving customers. The arrival
Click on the entry Bank_Arrivals and select OK.
The Qty each... field now includes the cycle.
246 Chapter 6:
Arrival Cycles

Cumulative Cycle Tables the number of arrivals to arrive within each time
interval.
In the previous example, percentages were
expressed non cumulatively. This same data Example 1
could have been expressed cumulatively as fol-
Suppose that in the bank example we knew that
lows:
for each cycle period, the number of customers to
Before Percent arrive during each time interval within the cycle
period is as follows:
9:00 am 0
10:30 am 10 From Before Number
11:30 am 25
9:00 AM 10:30 AM 100
1:00 pm 55
10:30 AM 11:30 AM 150
4:00 pm 70
11:30 AM 1:00 PM 300
5:00 pm 100
1:00 PM 4:00 PM 150
The data is now expressed cumulatively and 4:00 PM 5:00 PM 300
could be entered in the cycle table as follows.
With the data in this format, we specify the
Arrival cycle by choosing Qty in the “Qty/Per-
cent” field and complete the cycle table as fol-
lows:

To specify cycles in cumulative form, simply

choose Yes in the Cumulative... field of the
Arrival Cycles edit table.
This table could also be specified cumulatively
Please note by choosing Yes in the Cumulative... field and
entering the quantity values in a cumulative for-
Time values remain cumulative regardless of the mat.
form of the percentages.
Please note

When specifying Arrival cycles by quantity, the

Arrival Cycles by Quantity value entered in the “Quantity each” field of the
The previous example was based on the assump- Arrivals edit table changes meaning. Instead of
tion that a certain percentage of arrivals came the total arrivals per cycle, it represents a factor
within a specified time interval. An alternate by which all entries in the cycle table will be mul-
method of specifying an arrival cycle is to specify tiplied. This field may be any valid expression
which evaluates to a number. This allows the
 ProModel 247
User Guide

same arrival cycle to be entered for more than

one arrival record that has a different factor
applied to it. For example, you might want to
define a different factor to a customer arrival
pattern depending on the day of the week. In this
case, define an arrival record for each day with a
frequency of one week.

Example 2
Suppose we wish to see the effect on the Bank
example if the number of arrivals is increased by
50%. The relative quantities per time interval
remain the same but now 50% more customers
arrive each day. Using the data from the previous
example, we enter the same values in the Arrival
cycle quantity fields, but specify a value of 1.5 in
the quantity field of the Arrival edit table.

The result is an arrival schedule with the follow-

ing parameters.
From Before Quantity
9:00 AM 10:30 AM 150
10:30 AM 11:30 AM 225
11:30 AM 1:00 PM 450
1:00 PM 4:00 PM 225
4:00 PM 5:00 PM 450
248 Chapter 6:
Table Functions

Table Functions ear interpolation. The following two examples

show how to specify a linear function (where
Table functions provide an easy and convenient only two reference values are needed to define
way to retrieve a value based on an argument the entire function) and a nonlinear function
(i.e., some other value) that is passed to the table. (where more than two reference values need to be
Table functions specify a relationship between an specified).
independent value and a dependent value. All
table functions are defined in the Table Functions Example 1
editor which is accessed from the Build menu.
The example below shows a relationship that
exists between the time required to process an
order and the number of entities in the order. As
the number of entities increases, the time
required to process the order also increases. The
relationship in this case is linear, meaning the
processing time is directly proportional to the
number of copies in the order. Because of the lin-
ear relationship, only the two endpoints need to
be entered in the function table. (The function
table for this example is given in the discussion
on the Table Function editor.)
Function: ProcTime()
3

Processing
time (min)
How to access the function table edi- 1

tor:
0
0 100 200 300
1. Select More Elements from the Build menu.
Order size
2. Select Table Functions.
Example 2
In this example the relationship between the inde-
Table Functions Editor pendent value and the dependent value is nonlin-
ear and inversely proportional. In addition,
Table functions are defined by the user and return interpolation is required to determine the depen-
a dependent (or look-up) value based on the inde- dent value if the independent value passed to the
pendent (or reference) value passed as the func- function lies between the independent values
tion argument. Independent values must be
entered in ascending order. If the independent
value passed to a table function falls between two
independent values, a dependent value for the
unspecified reference value is calculated by lin-
 ProModel 249
User Guide

given explicitly in the table function. The tables for the two example functions are
given below.
Function: QualFactor()
3.0

2.0
Processing
Time Factor
1.4

1.1
1.0

1 2 3 4 5

Quality Level

In the example above the dependent value repre-

sents a factor which is to be multiplied by the
processing time required to complete an order.
Each order is assigned a number, 1 through 5,
according to the level of quality desired. In this The independent and dependent values allow any
case, a lower number represents higher quality. general expression such as numbers, variables,
(The function table for this example is listed in and math functions. The fields are evaluated only
the following explanation of the Function Table at translation, and cannot vary during the simula-
Editor.) tion.
When calling a user-defined table function, if the
Table Function Edit Table independent value is out of range, then the table
function will return a zero for the dependent
The Function Table Editor is where all function value. Consider the following function table,
tables are created and edited. The fields of the Operation_Time:
Function Table editor are defined below.

ID The name of the function table.

Table... Click on this heading button to open a If the function were called with the command
table for defining the independent and dependent “Operation_Time(5),” the independent value
values of the function. passed to the table function Operation_Time
would be five. But five is beyond the limits of the
table, so the dependent value returned will be
zero. Likewise, if the independent value is 1, the
dependent value returned will be zero. However,
if 2.7 is entered as the independent value, Pro-
250 Chapter 6:
Table Functions

Model will interpolate and return a value between

30 and 50.
 ProModel 251
User Guide

User Defined Distributions bution edit table. The User Distribution edit
table’s fields are described below.
Occasionally, none of ProModel’s built-in distri-
butions can adequately represent a data set. In
these cases, the user may define a User Distribu-
tion to represent the data set. User Distributions
specify the parameters of user-defined (empiri-
cal), discrete, or continuous probability distribu-
tions. ID The name of the distribution. When refer-
encing distribution tables (in the operation logic,
for example) the open and closed parentheses
after the distribution name must be used, such as
Dist1(), OpTime().
Type... Discrete or Continuous depending on the
number of possible outcomes.
Cumulative... Yes or No depending on whether
the distribution is to be specified in cumulative or
non-cumulative format.
Table... Click on this button (or double click in
the field) to open an edit table for defining the
parameters of the distribution. Once a distribu-
tion has been defined, the field changes from
“Undefined” to “Defined.”
The combination of Discrete and Continuous dis-
tributions, along with the ability to express either
How to create and edit user distribu- in cumulative or non-cumulative terms, creates
tions: four possible formats for specifying distributions.
The remainder of this section gives examples and
1. Choose More Elements from the Build menu.
procedures for specifying each of these distribu-
tion types.
2. Choose User Distributions.

Discrete Distributions
Discrete distributions are characterized by a finite
User Distribution Edit Table set of outcomes, together with the probability of
A user-defined distribution is a table of empiri- obtaining each outcome. In the following exam-
cally gathered data. User distributions may be ple, there are three possible outcomes for the
either continuous or discrete, and may be cumu- group size: 30% of the time the group size will be
lative or non-cumulative (more information con-
cerning these options is found later in this
section). The data is entered into the User Distri-
252 Chapter 6:
User Defined Distributions

10, 60% of the time the group size will be 20, and Process Table
10% of the time the group size will be 30.
Entity Location Operation (min)
Discrete Distribution EntA Loc1 GROUP Dist() AS Batch
Batch Loc1 WAIT 10 min
P 1.00
r .90
Routing Table
o .80
b .70
Blk Output Destination Rule Move Logic
a .60
b .50
i .40 1 Batch Loc2 FIRST 1 MOVE FOR 5
l .30
i .20
ProModel provides the flexibility to specify dis-
t .10 crete distributions according to a probability
y 0 mass function or a cumulative distribution func-
10 20 30
tion. Select Yes or No in the Cumulative field of
Group size the Distribution edit table and fill in the table
according to the probability mass function or the
One way to represent a discrete distribution is by cumulative distribution function. The following
its probability mass function, listing the possible tables show the discrete distribution example
outcomes together with the probability of observ- defined in both formats.
ing each outcome. A probability mass function
for the example above could be expressed as fol-
lows (with G representing the group size).
Discrete (probability mass function)
G 10 20 30
P(G) .30 .60 .10
An alternate way to represent a distribution is
through a cumulative distribution function, list-
ing each possible outcome together with the
probability that the observed outcome will be less
than or equal to the specified outcome. A cumu-
lative distribution function for the example above Discrete (cumulative distribution
could be expressed as follows. function)
G 10 20 30
P(G) .30 .90 1.0
In the next example, the number of parts are
grouped into a batch according to a user distribu-
tion.
 ProModel 253
User Guide

Continuous Distributions P(3.5 <= X < 5.0) = 0.40

P(5.0 <= X < 6.0) = 0.30
Continuous distributions are characterized by an P(6.0 <= X <= 8.0) = 0.10
infinite number of possible outcomes, together P(8.0 < X) = 0.00
with the probability of observing a range of these The following table represents the p.d.f. for this
outcomes. In the following example, there are example.
an infinite number of possible operation times
between the values 2.0 minutes and 8.0 minutes.
Twenty percent of the time the operation will take
from 2.0 to 3.5 minutes, 40% of the time the
operation will take from 3.5 to 5.0 minutes, 30%
of the time the operation will take from 5.0 to 6.0
minutes, and 10% of the time the operation will
take from 6.0 minutes to 8.0 minutes.

As with a discrete distribution, a cumulative dis-

Continuous Distribution tribution function for a continuous distribution
specifies the probability that an observed value
P 100
r 90 c.d.f. will be less than or equal to a specified value. A
o 80 c.d.f. for the example distribution is as follows
b 70 (where x represents the return value).
a 60
b 50 x 2.0 3.5 5.0 6.0 8.0
p.d.f.
i 40
P(X <= x) 0 .20 .60 .90 1.0
l 30
i 20 The following table represents this c.d.f.
t 10
y 0

1.0 2.0 3.0 4.0 5.0 6.0 7.0 8.0 9.0 10.0

Processing time (min)

As with a discrete distribution, a continuous dis-

tribution can be defined in two ways. A probabil-
ity density function lists each range of values
along with the probability that an observed value
will fall within that range. Each of the values
within the range has an equal chance of being
observed, hence the piece-wise linearity of the
c.d.f. within each range of values. A probability
density function for the example above is
expressed as follows.
P(0.0 <= X < 2.0) = 0.00
P(2.0 <= X < 3.5) = 0.20
254 Chapter 6:
External Files

External Files during the simulation. Each of these fields is

defined below.
External files may be used during the simulation
to read data into the simulation or write data as
output from the simulation. Files can also be used
to specify such things as operation times, arrival
schedules, shift schedules, and external subrou-
tines. All external files used with a model must ID An alias to be used in the model for referenc-
be listed in the External Files Editor which is ing the file. Note that this ID does not have to be
accessed from the Build menu. the same as the file name.
Type Click on this heading button to display the
following menu. The six file types are discussed
in the remainder of this section.

File Name... The actual file name, including the

path. Press the heading button or double click in
this field to browse for a specific file.
Prompt A prompt to be displayed at run time in
the event that the specified file cannot be opened.
How to define external files:
Notes... A general notes field for entering
1. Select More Elements from the Build menu. descriptive information about the file. Click the
heading button or double click in this field to
2. Select External Files. open a larger window for entering notes.

File Types
External Files Editor
External files may be defined as one of several
The External Files Editor consists of an edit table types depending upon the purpose of the file.
with fields specifying the external files to be used
General Read File
A General Read file contains numeric values read
into a model using a READ statement. Values
must be separated by a space, comma, or end of
 ProModel 255
User Guide

line. Any non-numeric data will be automatically entered in the cell where the names intersect. An
skipped when obtaining the next numeric value example of a spreadsheet file is shown next.
(See “Read” on page 527 for correct syntax and
examples). For example, if you specify a normal
distribution such as N(5,1) in the General Read
file, ProModel will not return a numeric value
following the distribution. Instead, it will read in
the first value, 5, and the next value, 1.
A General Read file must be an ASCII file. Data
created in a spreadsheet must be saved as a text
file.

To use the value stored in an Entity-Location file

General Write File
as an operation time, call out the file identifier in
A General Write file is used for writing text the operation logic as shown in the following
strings and numeric values using the WRITE and example. (In this example, “SvcTms” is the File
WRITELINE statements. Text strings are ID of the desired Entity-Location file.)
enclosed in quotes when written to the file, with
commas automatically appended to strings. This Please note
enables the files to be read into spreadsheet pro-
grams like Excel or Lotus 1-2-3 for custom view-
If the .wk1 or .xls file contains more than one
ing, editing, and graphing. Write files may also
sheet of data, only the first sheet will be read in.
be written to using the XWRITE statement which
gives the modeler full control over output and
formatting. (See “Write” on page 571, “Write-
Line” on page 572, and “Xwrite” on page 575 for
Process Table
correct syntax and examples.)
Entity Location Operation (min)
If you write to an external file during multiple
EntA Loc1 WAIT SvcTms()
replications or a single, independent run, the data
will be appended to the data from the previous
Routing Table
replication. However, if the RESET statement is
used, the data is overwritten for each replication. Blk Output Destination Rule Move Logic
1 EntA Loc2 FIRST 1 MOVE FOR 5
Entity-Location File By specifying SvcTms() with no arguments in the
An Entity-Location file (or expression file) is a parentheses, a value is returned from the Entity-
spreadsheet (.wk1 or .xls format only) file con- Location File “SvcTms” for the current entity at
taining numeric expressions listed by entity and the current location, i.e., EntA at Loc1. You may
location name. Entity names should appear also return the value stored in any other cell of an
across the top row, beginning in column 2, while Entity-Location file by explicitly specifying the
location names should be entered down the first entity and location names in the parentheses, e.g.,
column, beginning on row 2. A numeric expres- SvcTms(EntB, Loc1) or SvcTms(EntC, Loc2).
sion for each Entity-Location combination is
256 Chapter 6:
External Files

Arrivals File When defining an External Arrivals File, you do not

need to define arrivals in the Arrivals edit table. If sev-
An Arrivals file is a spreadsheet (.wk1 or .xls for- eral entities are scheduled to arrive at the same time,
mat only) file containing arrival information nor- entities arrive in the system according to the order in
mally specified in the Arrival Editor. One or which they appear in the arrival list. However, when
more arrival files may be defined and referenced there is more than one occurrence for the arrival
in the External Files Editor. Arrival files are record, the next entity will not arrive until the fre-
automatically read in following the reading of the quency has elapsed. Meanwhile, other entities listed
Arrival Editor data. The column entries must be below the record may be allowed to arrive.
as follows:
Column Data
A Entity name Please note
B Location name
If the time of the first arrival is zero and there is
C Quantity per arrival only one arrival of some quantity, you do not
need to complete additional cells. Likewise, if
D Time of first arrival
there is only one arrival at a time other than zero,
E Number of arrivals you do not need to fill in additional cells after the
Time entry.
F Frequency of arrivals
G through... Attribute assignments
Columns A through F may have any heading
Please note
desired as long as the data is of the proper type.
If attributes are to be assigned, columns G and
higher should have headings that match the If the .wk1 or .xls file contains more than one
names of the attributes being assigned. The fol- sheet of data, only the first sheet will be read in.
lowing example illustrates these points.

Example Shift File

A shift file record is automatically created in the
External Files Editor when you assign a shift to a
location or resource. If shifts have been assigned,
the name(s) of the shift file(s) will be automati-
cally created in the External Files Editor. If no
path is listed for the shift file, ProModel will
The values in the spreadsheet cells must be a numeric search in the default models directory.
expression as opposed to a formula commonly used in
spreadsheets. For example, if cell E4 in the spread-
sheet above was actually a formula generating the
value 100, the value ProModel generates is zero. Pro-
Model only recognizes expressions for the Qty, Time,
Number, and Frequency columns in a spreadsheet.
 ProModel 257
User Guide

Please note RDW Binary Output Reports &

Graphs saved for a
Creating a shift file record in the External Files model
Editor should not be done. It is done automati- SED* Binary Seed File used to store
cally through the shift assignment. seed values for each rep-
lication
SFT Binary Shift created when
DLL File defining a shift in the
Shift Editor
A DLL file is needed when using external sub-
routines through the XSUB() function. See “Sub- TRC* ASCII Trace File
routines” on page 238 for more information. GLB Binary Graphic Library Files
GBM Binary Graphic Bit Map file
Excel File created when loading a
An Excel file is automatically created in the model file.
External Files Editor when you assign a shift to
an array import file. If the external file has been Open Files
assigned, the name(s) of the Excel file(s) will be
automatically created in the External Files Editor. Depending on the model specifications, there
If no path is listed for the Excel file, ProModel may be some occasions where several files need
will search in the default models directory. to be open simultaneously to execute the model.
There is a feature which allows the user to access
up to 255 open files at any time. The [General]
Other External Files section of the promod.ini file contains the fol-
In addition to allowing the user to define external lowing statement: OpenFiles=n where n is the
files, ProModel creates other external files. Pro- number of files between 20 and 255. The default
Model automatically creates and/or opens files is 40. To change the number of available open
depending on the specifications in the model. files, simply edit thepromod.ini file such that
Below is a description of the different files Pro- OpenFiles equals the desired number and then
Model creates (* indicates files that remain open restart ProModel. There is also the option to close
while the model is running): files using the CLOSE statement (see “Close” on
page 448).
Extension Type Description
CSV ASCII Export Data (comma
delimited)
MOD* Binary Model File
RDB Binary Output Database (basic
statistics)
RDT Binary Output Time Series data
258 Chapter 6:
Streams

Streams Streams Edit Table

A stream is a sequence of independently cycling, The Streams Editor consists of an edit table with
random numbers. Streams are used in conjunc- three fields. The fields of the Streams edit table
tion with distributions. Up to 100 streams may be are explained below.
used in a model. A stream generates random
numbers between 0 and 1, which in turn are used
to sample from selected distributions. By default,
all streams use seed value #1 and are not reset
between replications if multiple replications are
run. To assign a different starting seed value to a
stream or to cause the seed value to be reset to the
initial seed value between replications, use the Stream # The stream number (1 to 100). This
Streams Editor. The Streams Editor is accessed number identifies each stream.
from the Build menu as shown below.
Seed # The seed value (1 to 100). Streams hav-
ing the same seed value generate the same
sequence of random numbers. For more informa-
tion on seed values, see “Using Random Number
Streams” on page 258.
Reset... Set this field to YES if you want the
stream to be reset to the initial seed value for each
model replication. Set this field to NO if you
want the stream to continue where it left off for
subsequent replications.
The Streams Editor pictured above shows five
defined streams. Each stream has a unique seed
value. Streams 1, 2 and 5 will be reset for each
replication, while streams 3 and 4 will continue
where they left off for subsequent replications.

Using Random Number Streams

How to access the streams editor:
One of the most valuable characteristics of simu-
1. Select More Elements from the Build menu. lation is the ability to replicate and isolate proba-
bilistic functions and activities within a system
2. Select Streams from the submenu.
for specific study. In the real world, events tend
to occur randomly, according to a certain statisti-
cal pattern or distribution. To help you model this
randomness, ProModel uses distributions.
When you include a distribution (e.g., Normal,
Beta, and Gamma) in your model, ProModel uses
 ProModel 259
User Guide

a random number generator to produce a set Please note

sequence or stream of numbers between 0 and 1
(0 <= x < 1) to use in the distribution. Before it The random number generator is a prime modu-
can select any numbers, however, ProModel lus multiplicative linear congruential generator.
requires an initial seed value to identify the point The C code implementation for most of the ran-
in the stream at which to begin. Once you specify dom variates was written by Stephen Vincent and
a seed value, ProModel “shifts” the random num- based on the algorithms described by Law and
ber selection (in increments of 100,000 numbers) Kelton (see the “Bibliography” on page 596).
by that number of positions and starts sampling
values. Since there is only one random number
stream, this will ensure that the selected values
do not overlap. ProModel includes 100 seed val-
ues, and each seed produces a unique set of ran-
Stream Example
dom numbers. If you do not specify an initial The following example shows one reason why
seed value, ProModel will use the stream number multiple streams are useful.
as the seed value (i.e., stream 3 uses seed 3).
Two machines, Mach1 and Mach2, are to go
Random Number Stream down approximately every 4 hours for servicing.
100,000 random numbers To model this, the frequency or time between
failures is defined by a normal distribution with a
}

mean value of 240 minutes and a standard devia-

tion of 15 minutes, N(240,15). (For more infor-
Seed 1 Seed 2 Seed 3 mation on distributions, see “User Defined
Distributions” on page 251). The machines will
When you use a specific seed value (e.g., 17), go down for 10 minutes. Because no stream is
ProModel produces a unique sequence of num- specified in the normal distribution, ProModel
bers to use each time you apply that seed value. uses stream number one to generate sample val-
This allows you to maintain the consistency of ues for both machines. So if the next two num-
some model elements and permit other elements bers in stream number one result in sample values
to vary. (To do this, specify one random number of 218.37 and 264.69, Mach1 will receive 218.37
stream for the set of activities you wish to main- and Mach2 will receive 264.69. Therefore, the
tain constant, and another random number stream two machines will go down at different times,
for all other sets of activities.) In fact, because Mach1 after almost four hours and Mach2 after
each seed value produces the same sequence of somewhat more than four hours.
values every time, completely independent model
functions must use their own streams. For exam- Suppose, however, that the resource to service the
ple, Arrival distributions specified in the Arrival machines must service them both at the same
Module should have a random number stream time. The machines would have to go down at
used nowhere else in the model. This will prevent the same time. Stream number one will not bring
activities that sample random stream values from them down at the same time because stream num-
inadvertently altering the arrival pattern (i.e., the ber one sends the machine’s distributions two dif-
activities will not affect the sample values gener- ferent numbers. Using two streams (in the
ated from the arrival distribution). example below numbered ten and eleven) with
the same initial seed will ensure that the
260 Chapter 6:
Streams

machines receive the same random number every down together. Mach1 would use the first value
time. The two streams have the same starting from stream ten; Mach2 would use the first value
seed value so they will produce exactly the same from stream eleven; and Mach3 would use the
sequence of random numbers. The first number second value from stream eleven. The first time
of stream ten will be exactly the same as the first Mach1 and Mach2 went down, they would go
number of stream eleven; the second numbers down at the same time because the first number
will be the same; indeed, every number will be in streams ten and eleven is the same. But there-
the same. after they would not. The second time they
would go down at different times because Mach1
The Streams window below shows streams ten
would receive the second value from stream ten,
and eleven with the same seed values.
Mach2 would receive the third value from stream
eleven, and Mach3 would receive the fourth
value from stream eleven.

Please note
By assigning stream ten to Mach1 and eleven to Stream notes:
Mach2, both machines will go down at exactly
the same time. 1. If a stream value is not specified for a distribu-
tion, the stream is assumed to be stream one.
Stream #1 does not automatically reset after each
replication.

2. The stream parameter is always the last

parameter specified in a distribution unless a
location parameter is also specified. See “Distri-
bution Functions” on page 427 for details.

This first clock downtime for each machine will

occur at the beginning of the simulation. After
that, the first downtime occurs at 218.37 minutes
for both machines. Defining different seed val-
ues for the streams would produce different
sequences and therefore different downtimes.
Using the same stream number for the clock
downtimes would also produce different values.
But two different streams with the same seed
value will bring both machines down at the same
times.
Note that if a third machine were to use one of the
streams, for example if Mach3 were to use stream
eleven, the two machines would no longer go
 ProModel 261
User Guide

Material Handling Systems close to the left end of the envelope, and bridge A
is to the left of bridge B, a run-time error will
The following section provides advanced tech- occur if the space remaining between node N and
niques to model Material Handling Systems. bridge A is less than the bridge separation dis-
tance. To avoid such problems, define the crane
envelope wide enough to allow sufficient space
Crane Systems beyond any serviceable nodes.
To implement cranes in ProModel, the Path Net-
work module allows three types of networks: Crane Priorities, Preemption &
non-passing, passing, and cranes. From this mod- Bridge Bump-Away
ule, you can lay down and orient a crane enve-
lope, define the bridge separation distance, and ProModel associates two types of priorities with
define the graphics for rails and bridges in the the operation of crane resources: (1) resource
bay. Additionally, the Resources module allows request priority, and (2) crane move priority.
you to define bridge and hoist speeds, and hoist Resource Request Priorities Used to resolve
graphics for one or more cranes operating in the any conflicts that arise between multiple tasks
same bay. requesting the same resource at the same time.
This priority scale follows the rules that regular
dynamic resource priorities do (i.e., 10 levels of
Creating Multi-Bridge Crane Systems
100). Use this priority to preempt crane resources
Modeling multiple cranes operating in the same from lower priority tasks to serve higher priority
bay has never been so easy! tasks.
User defined bridge separation distances, exten- Crane Move Priorities Used for multiple
sions to regular dynamic resource usage state- bridges operating in the same envelope, to decide
ments, and a set of new priority rules have been which crane bridge has priority over another
introduced in order to let you manage conflicting while moving. This priority scale is also in the
movements in the same envelope zone. range [0...999], but does not have any preemption
Crane Envelope The parallelogram-shaped levels. Any higher value has overriding priority
area represented by a crane type path network, over a lower value. You can assign priorities to
bounded by two rails and the lines connecting the crane resources temporarily, on a task-by-task
endpoints of those rails. The lines connecting the basis via extra parameters in the GET, JOINTLY
endpoints of rails are effectively the two extreme GET, USE, and MOVE WITH statements. There-
positions of the center-lines of any bridges oper- fore, you can only use priorities for cranes that
ating within the envelope. ProModel uses the end are either moving to respond to a resource request
of one of the rails as the envelope origin to serve or moving to deliver a part. Moving to downtime,
as a reference point for all logical distance calcu- off-shift or break nodes has the default (0) move
lations within the envelope. priority. Moving to park has the lowest move pri-
Bridge Separation The minimum distance you ority (the same as an idle crane).
want to maintain between center-lines of two You can further sub-divide crane move priorities
neighboring bridges. This distance is not related into three categories:
to how close a bridge center-line can get to one of • Task Move Priority Assigned by the mod-
the extreme endpoints of the envelope. Caution: eler via parameters passed to resource usage
if bridge B tries to move to a node N that lies very statements (GET, MOVE WITH, etc.). Used
262 Chapter 6:
Material Handling Systems

as the base move priority for travel to pick may define, edit, and size multiple graphics
up and travel to deposit. for the same hoist the same way you create
• Claim Priority If crane A’s bridge is multiple graphics for other resources.
headed towards its ultimate (task) destina- • Units & Multiple Cranes Crane resources
tion, the claim priority is equal to the task limit you to one unit. When you define mul-
move priority of crane A. Otherwise (if crane tiple cranes operating in the same envelope,
A’s bridge is moving under the influence of define them as separate resources—each
crane B), claim priority is equal to the claim assigned to the same crane network.
priority of the claim inducer bridge (bridge • Downtimes In addition to the clock and
B). usage downtimes you may define for cranes,
• Effective Claim Priority Applies only to you can assign cranes to shifts in the same
envelopes with three or more cranes. If mul- way you assign other resources. When a
tiple crane bridges are moving in the same crane goes down, it moves to the downtime
direction with overlapping claims, the effec- node specified in the DTs dialog. If you do
tive claim priority of any bridge in the over- not associate a node with the crane down-
lapping region is the maximum of all the time, the crane goes down at its current posi-
claim priorities of those bridges. tion.
• Specifications Cranes require separate val-
Crane Operations ues for bridge and hoist speed and accelera-
tion. You must enter Speed (Empty), Speed
The operation of cranes in ProModel has been
(Full), and Accelerate and Decelerate values
designed to closely resemble the real-life opera-
for bridge movement along the rails and
tion of cranes. Under most circumstances, you
hoist movement across the bridge. In each
need not be concerned with how ProModel han-
field, the format is Bridge Value, Hoist Value
dles crane movements. The following operational
(e.g., if you enter “150, 20” in the speed
specifications are intended as a reference only
field, the bridge moves at 150 and the hoist
and are not essential in order to model cranes
at 20 feet per minute). Although you must
using ProModel.
enter speed values, acceleration and deceler-
ation values are optional (if you leave them
Crane Animation blank, ProModel assumes the crane to have
During a simulation run, entities picked up by a an infinite acceleration and deceleration
crane appear graphically on the entity spot for the capability. (Hint: this provides better run-
hoist. The hoist graphic appears above the entity time computational efficiency).
graphic and the bridge of the crane appears on top • Crane Searches Define Work and Park
of the entity and hoist graphics. searches in the same way you define
searches for other resources.
Crane Specifications • Node Logic Define entry and exit logic for
cranes at nodes in the same way you define
When you define cranes for your model, consider node logic for other resources.
the following:
• Crane Graphics In the Resources module,
the selected graphic represents the hoist. You
 ProModel 263
User Guide

Handling Zone Claims In Multi-Crane Case 1

Envelopes
If a crane is in one of the following states, it will
be referred to as “immovable at a node.” No other
crane will be able to push this crane away,
regardless of its priority.
• Picking up or depositing an entity.
• Being used at a location. A B' B A'
• Having a downtime, off-shift time, or break
time. Bridge B starts moving first, from [B] to [B'] and
claims the zone [B'~B] in the ¨ direction. Bridge
Extended Movement Zone The net zone that
A wants to move from [A] to [A'] in the opposite
it needs to traverse ± bridge separation distance
direction. If the move priority of A is less than or
(± depending on the direction that it will go).
equal to the move priority of B, we let bridge A
Before starting to move, any <crane A> attempts start moving towards [B' - bridge separation]
to claim its extended movement zone (zone A) only. If A has a higher move priority, B is stopped
for the entire movement duration. immediately and sent back to [A' + bridge separa-
ProModel can reject the claim attempt of crane A tion]. In the latter case, A may queue up behind
for zone A for several reasons: B.
• If there are immovable cranes in zone A
• If there are any cranes in zone A with move Case 2
priorities greater than or equal to1 the move
priority of crane A, if they are going in the
opposite direction, or they are going in the
same direction with conflicting destina-
tions.2

Case Examples of Zone Claims

The following cases illustrate specific situations A B A' B'
with examples: Bridge B starts moving first, from [B] to [B'],
then bridge A wants to move from [A] to [A'].
Bridge B claims zone [B~B'] in the Æ direction.
Since bridge A wants to move in the same direc-
1. Special case treatment not “>=” but strictly “>” if all tion and their destinations do not conflict (assum-
of the following conditions hold: (1) if the bridge ing that B'-A' is greater than the bridge
that A is trying to oppose is stationary, (2) unless separation), bridge A moves all the way. If B has
crane A is trying to move just to park (if A has a task
or if it is trying to move out of the way of another already cleared the zone [A~(A' + bridge separa-
bridge), (3) if the one A is trying to push is idle or its tion)] by the time A wants to start moving, A
bridge was blocked before reaching its destination. moves independently. Otherwise, A may queue
2. Destination Conflict Test: If sign (B' - A' - up behind B. (If the distance B'-A' is less than the
sign(existing claim)*(bridge_separation)) = sign given bridge separation and the move priority of
(existing claim) then not conflicting. A is greater than the move priority of B, bridge A
264 Chapter 6:
Material Handling Systems

will push away bridge B, and crane B will not direction with a higher move priority than both of
respond to the request while passing over [B']). the other bridges. ProModel interrupts bridges A
and B and lays a new course for both bridge B
Case 3 [B'' = C' - bridge separation] and bridge A [A'' =
B'' - bridge separation]. In this case, B may queue
up behind A, and C behind B.

Case 5

A B A'' B' A'

Bridge B starts moving first, from [B] to [B'],

then bridge A wants to move from [A] to [A'].
A B C
Bridge B claims the zone [B~B'] in the Æ direc-
tion. Since bridge A wants to move in the same B'
direction and their destinations do conflict, prior- A'
( (
ities will be considered. If the move priority of A C'
is not greater1 than the move priority of B, bridge
A starts moving towards [A'' = B' - bridge separa- This is an extension of Case 4. Assume that the
tion] only. Otherwise, A will push B away, and B move priorities for crane bridges A, B, and C are
will not respond to the request while passing over 3, 1, and 2 respectively. When bridge C tries to
[B']. In both cases, A may queue up behind B. claim zone [C'~C] in the ¨ direction, it faces an
“effective priority” of 3 and is unsuccessful in its
Case 4 original claim, so it starts moving towards [B' +
bridge separation]. Bridge B goes outside the
effect of bridge A in the second part of its move-
ment, [(A' + bridge separation) ~ B'] at time t0.
However, bridge C does not override bridge B
and start moving towards [A' + 2 * bridge separa-
tion] until the first “reclaim trigger event2” after
time t0.
If ProModel rejects the original claim of crane A,
A B C' A' B' C
crane A claims the largest available portion of the
Bridge B starts moving first from [B] to [B'], original zone, and implements the procedure
claiming zone [B~B'] in the Æ direction. Bridge described below to move its bridge through the
A wants to move from A to A' and starts moving subset zone. The crane waits until a “reclaim trig-
behind B. Bridge C wants to move in the opposite ger event” occurs, and then repeats the claim
attempt to let its bridge traverse the remaining

1. In this special case, bridge A’s claim priority com-

petes with the task move priority of bridge B. 2. Discussed later in this section.
 ProModel 265
User Guide

distance. The hoist, on the other hand, moves are compared with the a, s, and d of the leading
directly to its relative destination on the bridge, bridge (L). If all of the following conditions are
independent of the bridge zone claim results. In true, bridge F moves independent of bridge L.
case of bridge interruption, the hoist does not
stop moving. Therefore, for any particular crane Conditions for No Queue-Up
move, the combined trajectory of hoist and 1. aF <= aL The following bridge cannot accel-
bridge may change depending on zone availabil- erate faster than the leading bridge.
ity at the time of the claim. 2. sF <= sL The following bridge’s maximum
If crane A accepts the claim attempt, all cranes speed cannot be greater than the leading
inside the claimed extended zone bump away at bridge.
the time of the claim. This claim also prevents 3. dF >= dL The following bridge can deceler-
any other cranes with move priority less than or
ate equally or faster than the leading bridge.
equal to the move priority of A from entering the
claimed zone in conflicting directions. If any one of the above conditions fail, bridge F
moves at the same speed as bridge L, maintaining
the distance that existed between them at the time
Zone Claim Notes F started moving.

Zone Claim Notes

Please note
1. A crane cannot do a pickup or deposit while
another crane pushes it away, even though
Condition 3 usually creates a deviation from the
the request might be on its way.
typical real life situation, but it is necessary to
2. When you interrupt a crane bridge and ask it
avoid time consuming computations that can
to make a new claim (or update its claim), its
adversely affect the run-time performance of
speed is reset to zero and ProModel re-evalu-
models with crane resources. To avoid unrealistic
ates its mobility characteristics. ProModel
queue-ups when modeling multiple bridges with
recalculates the move time with these new
different mobility characteristics in the same
parameters. This rule also applies to bridges
crane envelope, make either no bridge decelera-
that are moving when a bridge behind them
tion entry (infinite deceleration), or use the same
with a higher priority and a conflicting desti-
overall average deceleration rate for all crane
nation makes a new claim to go in the same
bridges in that envelope.
direction. See Case 3 (when priority of A is
greater than priority of B) for an example.

Treatment of Potential Queue-Up

Situations
For all bridge claims with the potential of having
two bridges queue up after one another (men-
tioned in the example cases above), the following
rule applies:
The acceleration rate (a), maximum speed (s) and
deceleration rate (d) of the following bridge (F)
266 Chapter 6:
Material Handling Systems

Bridge Motion after Queue-Up another). Independent of its current position and
movement direction, the crane still has the capa-
distance
traveled bility to respond to resource requests coming
by bridges from anywhere in the envelope. If allocated to a
task with high enough travel-to-pickup move pri-
B ridge
Separation ority, the crane may reverse direction or terminate
its move early, bumping other crane bridges on
B its way.
Qup
Whenever a crane bridge changes its claim, it
distance checks to see if there are any bridges behind it
A
that are going in the same direction with overlap-
tim e
B a ccel. B m a x. B decel. ping claims. If there are any, the newly claiming
A m im ics B A g o es w ith B’s crane triggers a chain queue-up re-evaluation
(fo rm er) a v era g e s p eed
towards the following cranes. The following
If bridge A is queued up behind bridge B, bridge example demonstrates this case.
A goes through up to two stages of movement.
The first stage occurs throughout the movement B''2 B''1
of bridge B. Bridge A mimics bridge B’s motion,
maintaining its original distance from bridge B.
The second stage occurs after bridge B stops.
Bridge A continues traveling with the former
average speed of bridge B until it reaches its des-
tination.
A B A' B'
If bridge B is moving to accomplish its own task
(as opposed to just moving out of A’s zone), then At time t0, crane A is called for a task and starts
bridge A might stop earlier, without going moving to [A'] with move priority mpA, pushing
through the second stage. In this case, the total idle bridge B to [B' = A' + bridge separation]. At
traveling time for bridge A is calculated as if time t1 (bridge A and B are still moving), a
bridge A were traveling with bridge B’s average request for crane B comes from [B" (1 or 2)] with
speed. move priority mpB. Bridge B is allocated to the
When a bridge arrives at its destination, it trig- task immediately since it is available at the time.
gers a chain queue-up re-evaluation that pene- If the new destination of bridge B is [B"1], the
trates the crane envelope in the opposite direction new claim of bridge B does not conflict with the
that the stopped bridge was moving. This chain existing claim of bridge A, so the move priorities
re-evaluation handles cases in which there were are not significant. ProModel re-evaluates all
multiple bridges queued up behind the stopped motion values for crane B (acceleration, deceler-
bridge. ation, empty and full speeds for both the hoist
and the bridge) and crane B starts moving to its
Moving Idle Cranes can Respond to new destination. If the bridge motion expressions
Resource Requests for crane B have changed their values between t0
and t1, the queue-up status between bridges B
A crane can be idle and moving at the same time and A (and any others behind A) may change, so
(moving to park or being pushed away by
 ProModel 267
User Guide

ProModel performs a chain queue-up re-evalua- In the first six cases, a crane changes state from
tion. “immovable” to a finite move priority. The sev-
If the new destination of bridge B is [B"2], the enth case may change the “effective move priori-
new claim of bridge B conflicts with the existing ties” of other cranes. ProModel requires the
claim of bridge A, so ProModel considers the eighth case for envelopes with three or more
move priorities: bridges with overlapping operation zones: It
• If mpB <= mpA, then B does not have ensures that two or more unsatisfied, opposing
enough priority to stop A before A gets to its claims with the same move priority will resolve
destination. Bridge B will have to go on their conflict based on earlier task assignment
moving until [B'] and wait until it can claim time instead of locking up the crane system.
the region [B"2 ~ B'] in the Æ direction. Hence, all of the above cases create a potential to
realize previously unsuccessful claims.
• If mpB > mpA, then B does have overriding
priority over A. Bridge B stops bridge A at The reclaim trigger events for each envelope
[B"2 - bridge separation], starting a chain echo in the trace together with the triggering rea-
move termination which tells bridge A to son for model debugging purposes. The results of
stop any other followers with the appropriate reclaim attempts for each crane resource and its
bridge separation distances between each. In effects on other crane resources in the same enve-
this case, bridge A (and other possible fol- lope are also displayed.
lowers) will have to wait until the next
reclaim trigger event to attempt reaching Other Crane Operation Rules
their original destinations. 1. If an entity currently possesses a crane, all
move logic for the entity must use a MOVE
Reclaim Trigger Events WITH statement (until you free the crane)—
Unsuccessful claims of all crane bridges in an the entity cannot move without the crane.
envelope are re-attempted when a reclaim trigger 2. Although an entity cannot possess more than
event occurs in that envelope. The following one crane at a time, the entity may possess a
events are considered to be triggers for claim re- crane and a resource of another type.
evaluations in the related envelope: 3. If a crane is in one of the following states,
another crane cannot push it away.
• The duration of a USE <crane> statement
a) Picking up or depositing an entity.
expires.
b) Being used at a location.
• You free a crane using the FREE statement.
• A crane completes a deposit (unless you
c) Experiencing a downtime, off-shift
time, or break time.
specify the KEEP option).
4. The hoist moves to its relative destination on
• A crane completes a pickup and the crane is
the bridge independent of the bridge zone
about to start moving to deliver.
claim attempt outcomes. The hoist does not
• A crane downtime ends.
stop for bridge interruption so, for any par-
• You preempt a crane resource.
ticular crane move, the combined trajectory
• A bridge arrives at its task destination of hoist and bridge may change depending
(before elapsing pickup/deposit time). on zone availability at the time of the claim.
• There are no moving task bridges left (for 5. When a crane pushes away an idle crane, the
envelopes with 3 or more cranes only). idle crane comes under the control of the
268 Chapter 6:
Material Handling Systems

work and park search lists defined for the minimum distance to the hoist and then the
node closest to its bridge. order of appearance in the nodes edit table.
If the hoist is still moving at the time the
Crane Operations Notes bridge stops, the registry procedure executes
by considering the destination of the hoist.
ProModel allows definition of resource points for
crane resources on envelope nodes to achieve the
three dimensional look for “lowering the hoist” Please note
upon arriving at a node. Since cranes can only
have one unit, only the first resource point for Only users can instruct cranes to park on nodes.
any crane at any node is meaningful. Also, Pro- However, as a result of bump-aways, a crane can
Model only uses the resource points if the crane end up standing still at positions that do not nec-
resource arrives at the node to perform a task. In essarily correspond to nodes. In any case, Pro-
other words, the hoist does not lower if the crane Model registers an idle stationary crane to a
arrives at a node to park or just ends up there after node and places it under the control of work and
a bump. park searches of that node.
In general, once ProModel makes a match
between a resource request and a resource of the
requested type, the resource is allocated for that
job and the simulation engine does not go on Cranes follow the same rules as regular dynamic
looking for other matches that can actually reach resources while searching for assignments
to the requester sooner. Since cranes blocking (returning to preempted jobs, exclusive & non-
other crane resources is a common phenomenon exclusive work searches, requests coming from
in multi-bridge envelopes, extra care should be nodes not included in the work search, etc.).
used while designing the active operation zones There are some additional steps to handle interac-
and resource request logic in such models. tions with other cranes operating in the same
envelope. Upon completion of its task, a crane
goes through these extra steps:
Nodes, Work, and Park Searches
1. Lets other cranes in the same envelope re-
ProModel “registers” all cranes to their home attempt their claims, possibly generating an
nodes at the beginning of a simulation run. When induced claim on its bridge.
a crane starts to move, ProModel erases registra- 2. Even though other cranes might bump away
tion, and re-establishes it when the crane stops, its bridge, the crane executes the work search
according to the following rules: defined for it at its current node. (If requests
1. Cranes assigned to a task (pick up, drop off, are waiting at different locations of the same
down) remain unregistered throughout inter- work search record, ProModel takes the
mediate stops and register to the task desti- resource request priorities into consider-
nation node upon arrival. ation.)
2. Idle cranes that are bumped away, or cranes 3. If it was not allocated to a task or bumped
that were unsuccessful in claiming the entire away, the crane executes the park search
bridge region to go parking register them- defined for it at its current node, or attempts
selves to the node closest to their bridge going home if return home is checked.
when they stop. If there are multiple nodes
closest to the bridge, ties are broken by the
 ProModel 269
User Guide

Please note time a crane would have taken to get to its desti-
nation if it were the only bridge in its envelope.
A crane bridge moving to park cannot bump
other idle bridges out of its way. In such a case, Please note
the bridge goes as far as it can towards its desti-
nation and registers itself to the closest node The first component of gross travel time (moving
upon stopping (using the rules discussed above). towards the actual destination) may be greater
than the net travel time, since it may include
going back towards the destination after another
crane bumps it away. It may also involve devia-
Crane Resource Statistics tions from the bridge’s original motion values
The statistics reported for cranes are very similar when queued-up behind slower bridges.
to regular dynamic resource statistics. The fol-
lowing definitions highlight the differences in the
interpretations.
In Use Includes the following states: Special Case—Blocked Time Accrual
• Stationary use at a location via GET, for Moving to Park
JOINTLY GET, and USE statements. Remember that an idle crane registers itself to the
• Gross move time while delivering — actu- closest node whenever its bridge stops. If the
ally carrying an entity from one location to hoist is still moving, ProModel uses the destina-
another. tion of the hoist to break any ties between nodes
• Pickup and deposit times before and after the that are equidistant to the bridge position.
move to deliver. In case of an unsuccessful claim attempt to move
Travel To Use Is the gross move time to start to park, the crane bridge needs to stop before
being used — traveling to respond to a request reaching the instructed park node, and ProModel
for either stationary use or use to pickup and ignores the hoist travel for statistics purposes.
deliver an entity to another location. The “travel to park” statistic terminates at the
Gross Move Time May include the following time the bridge stops, not when bridge or hoist
times: stop time reaches its maximum value. In this
case, the net moving time to park computes as the
• Moving towards the actual destination.
bridge move time from current position to the
• Possibly moving away from the destination,
endpoint of the claim, using original bridge
when bumped away by a higher priority
motion values for the crane resource. Blocked
bridge in the same envelope.
time can accrue if this bridge queues up after a
• Stationary blockage times during which the slower bridge that is already moving (remember
bridge is waiting for a higher move priority that a crane moving to park cannot bump another
bridge in the same envelope to lower its crane).
move priority.
Blocked Time Tally blocked time by subtract-
ing the internally computed, hypothetical net Conveyors
traveling time from the actual incurred gross A conveyor is any moving track, belt, chain, or
move time. ProModel defines the net time as the roller which transports parts from one location to
270 Chapter 6:
Material Handling Systems

another. This section will help you better under- Conveyor Types
stand conveyors and how to model them using
You may represent conveyors as one continuous
ProModel.
span of randomly spaced parts (e.g., belt con-
ProModel determines the capacity of a conveyor veyor) or as intermittent spaces or carriers
by its speed and load spacing rather than a stated located at fixed intervals (i.e., trolley conveyor).
capacity. Specifically, capacity is a function of
the minimum allowable interload spacing on a
conveyor (which is the length of a queue position
Accumulating & Non-Accumulating
in the case of accumulation conveyors) and its In addition to continuous or intermittent convey-
length. It may be desirable, however, to impose a ors, some conveyors permit loads to accumulate
limit to the number of loads permitted on the con- or queue if conditions impede forward motion
veyor at any one time. progress. ProModel refers to these conveyors as
Conveyors usually do not pick up and drop off accumulating conveyors. Other conveyors pro-
loads as in the case of lift trucks, AGVS, and vide no queuing and halt all activity if forward
cranes. You must place loads onto and remove progress of the leading part or load stops. Pro-
them from conveyors. Model refers to these types of conveyors as non-
accumulating conveyors.
Depending on the nature of the conveyor and its
operation, modeling a conveyor can be straight- The following figure illustrates how entities can
forward or complex. For single conveyor sec- continue to accumulate after the leading load
tions, modeling is very simple. Conveyor stops on an accumulating conveyor. How a non-
networks, on the other hand, give rise to several accumulating conveyor can accept one additional
complexities (recirculating, merging, etc.) that entity if the leading entity stops, however it is
become more difficult to model. unable to advance any further since the entire
conveyor stopped.
Conveyor Simulation Benefits
Simulating your conveyor system will help you
address design and operational issues, answering
the following questions:
• What is the minimum conveyor speed that
still meets rate requirements?
• What is the load rate capacity of the con-
veyor?
• What is the load delivery time for different
activity levels?
• How much queuing do accumulation con-
veyors need?
• How many carriers do trolley or power-and- The different combination of continuous or inter-
free conveyors need? mittent conveyors and transport or accumulation
• What is the optimum number of pallets to conveyors result in the following four different
maximize productivity in a recirculating kinds of conveyors that ProModel is capable of
environment? modeling.
 ProModel 271
User Guide

Single Section Conveyors

Conveyors used for simple queuing or buffering
Type Example often consist of a single stretch or section of con-
veyor. Loads enter at one end and exit at the other
Continuous, Non- Belt, chain end. Load spacing is generally random. These
Accumulating types of conveyors are generally quite easy to
model. The modeler merely defines the length
Intermittent, Non- Tray, trolley
and speed and states whether the conveyor is an
Accumulating
accumulating or non-accumulating conveyor.
Continuous, Roller
Accumulating Conveyor Networks
Intermittent, Power-and-free, A conveyor network consists of two or more sec-
Accumulating towline tions that are connected together to enable part
merging, diverting, and recirculating. In such
For best results, you should model carriers or part instances, a conveyor may have one or more
holding devices on intermittent, accumulating entry points and one or more exit points. Further-
conveyors as though the devices were entities more, part entry and exit may not always happen
waiting for you to load and unload other entities at the beginning or end of the conveyor. In Pro-
to and from them (see "Load" is ProModel User Model, loads or entities must always enter at the
Guide) as you move parts. An alternative but beginning and exit at the end of conveyor net-
similar method is to use a JOIN statement and works. To model merging or branching in the
then specify two routings when you want the part middle of the conveyor, break the conveyor into
removed (see Example E in "Modeling Conveyor smaller sections.
Systems" in the next section). Yet another way of
modeling parts with carriers on a conveyor, is to Modeling Conveyor Systems
simply set a part attribute equal to a particular
A conveyor system is a combination of one or
value if the part is on a carrier. If the part is not on
more types of conveyors which interact to move
a carrier, assign a different value to the same
parts. Such a system may include branching,
attribute. Operations may occur at either the
merging, and looping. The process of dividing
beginning or end of a conveyor as shown here.
conveyors into logical sections is fairly straight-
forward if you understand what constitutes a con-
veyor section.
For modeling purposes, a conveyor section is
defined as any independently driven segment of
conveyor of the same type. Conveyor turns are
irrelevant as long as the conveyor remains
unchanged and both are actuated or stopped
together.
In ProModel, an accumulating conveyor section
must end at the point where parts are permitted to
272 Chapter 6:
Material Handling Systems

accumulate or back up. This generally occurs at Some users prefer to display the grid and select
a transfer point or process location. the Snap to Grid option in the View menu. Others
will leave Snap to Grid off. You may find that the
Modeling Conveyors precise positioning of a conveyor is easier when
you turn Snap to Grid off and set the Zoom suffi-
While not essential, it is visually more effective ciently high. When you need to change the type
to draw conveyors to scale on the layout. You of conveyor to accumulating, double-click on the
should also size entities traveling on a conveyor conveyor icon in the layout, select the Conveyor
to scale when you create them. Setting the length Options button, and select Accumulating from
of a conveyor different from the scale length or the Conveyor Options dialog.
conveying entities that have a length or width that
The following six examples show various ways
is not to scale will result in the appearance of load
of modeling conveyors:
overlapping or excessive load spacing. The
underlying logic and simulation is still valid, Example A Routes one or more parts from one
regardless of whether the graphics are to scale. or more non-conveyor locations to any conveyor
location.
Loads may appear to jump when transferring
from the end of one conveyor to another con-
veyor. This is a result of ProModel not allowing
a load to transfer onto a conveyor until there is
room for the load. Including a transfer time in
the Move Logic column of the Routing edit table
can result in smooth movement between con-
veyor sections. Defining a variable called
Transfer_Time and using that variable rather than E l A
Example B Routes one or more parts from any
entering the actual time allows for experimenta-
conveyor location to one or more non-conveyor
tion with various conveyor speeds with minimal
locations.
modeling changes.
Clock precision is also important. Note that
movement of one foot at 40 feet per minute will
take .025 minutes. If clock precision is set at .1
minutes, truncation will result in zero time. Make
sure you check your model for the correct clock Example C Routes single parts from any con-
precision. For most conveyors, a clock precision veyor location to one or more other conveyor
of .001 is adequate. ProModel may require locations.
greater precision for high-speed conveyors where
speeds are greater than 200 fpm.
Modeling conveyors in ProModel is quite easy.
Select the conveyor icon in the Locations Graph-
ics window and place the beginning and ending
points of the conveyor using the mouse. Clicking
the right mouse button will end the conveyor.
Left-click to add or delete a joint and allow the
conveyor to bend.
 ProModel 273
User Guide

Example D Joins one or more parts from one Automated Guided Vehicle Sys-
or more non-conveyor locations to another trans-
porting entity (e.g., a pallet or carrier) at any con- tems
veyor location. An automated guided vehicle system (AGVS) is
a path network along which computer-controlled,
driverless vehicles transport loads. One of the
modeling requirements of AGVS is to accurately
describe the method for controlling traffic. You
can usually accomplish this in one of two ways:
• Zone blocking
• On-board vehicle sensing
Zone Blocking The most common method of
traffic control, it involves placing control points
along the guide path. Each point usually allows
Example E Accumulates multiple parts com-
only one vehicle to access it any one time, thus
ing from one or more non-conveyor locations
blocking any other vehicle from entering any seg-
onto a conveyor location.
ment of the path connected to that point. Once the
vehicle leaves a control point to travel to the next
point on the path, any vehicle waiting for access
to the freed control point can resume travel.
On-Board Vehicle Sensing Works by having a
sensor on-board the vehicle that detects the pres-
ence of a vehicle ahead of it and stops until it
Example F Splits parts at a conveyor location detects that the vehicle ahead of it has moved.
sending one or more parts to a non-conveyor
location and a single part (e.g., a pallet or carrier) Modeling AGVS
onto the conveyor. Modeling an AGVS is very similar to modeling
an industrial vehicle, such as a lift truck, (which it
is in a sense) except you control the operation
more and there exists less freedom of movement.
Paths are generally unidirectional and do not
allow vehicle passing.
One of the challenges in modeling an AGVS is
finding the shortest routes between any two stops
in a system. ProModel provides built-in capabil-
ity to automatically determine the shortest routes
between points in a complex network.
274 Chapter 6:
Material Handling Systems

AGVS Simulation Benefits • What is the best path layout to minimize

travel time?
Simulating your AGV system will help you
address design and operational issues, answering • Where are the potential bottleneck areas?
the following questions: • How many people do you need to meet
activity requirements?
• What is the best path layout to minimize
travel time? • What are the best shift and break schedule
strategies?
• Where are the potential bottleneck areas?
• Which task assignment rules maximize utili-
• How many vehicles do you need to meet
activity requirements? zation?
• What is the best idle person deployment that
• What are the best scheduled maintenance/
minimizes response time?
recharging strategies?
• Which task assignment rules maximize vehi-
cle utilization? Industrial Vehicles
• What is the best idle vehicle deployment to
Industrial vehicles include all push or powered
minimize response time?
carts and vehicles that generally have free move-
• Is there any possibility of deadlocks?
ment. Utilize powered vehicles such as lift trucks
• Is there any possibility of collisions? for medium distance movement of batched parts
in a container or pallet. For short moves, use
Manual Material Handling Sys- manual or semi-powered carts. Single load trans-
porters are capable of moving only one load at a
tems time from one location to another. Such devices
Manual material handling systems (MMHS) are are fairly straightforward to model because they
probably the most common systems for handling, involve only a single resource and a single desti-
moving, storing, retrieving, and managing mate- nation for each move.
rials. ProModel easily allows you to model man- Multiple load transporters, on the other hand, can
ual labor. With shifts, breaks, and downtimes move more than one load at a time from one or
(illness, training, etc.), model people as more sources to one or more destinations. Defin-
resources. ing capacity and operation for multiple load
Whether carrying parts from one station to transporters can be extremely difficult since there
another or stocking shelves in a grocery store, may be special rules defining when to retrieve
people can be modeled as resources to do just additional loads and when to deliver the loads
about anything in ProModel. Such resources are already on board.
dynamic and move along assigned path networks.
Since people can think, you can model them very Modeling Industrial Vehicles
much like automated guided vehicles with on- Modeling an industrial vehicle involves modeling
board vehicle sensing. a resource that moves along a path network.
Paths are typically open aisles in which bi-direc-
MMHS Simulation Benefits tional movement is possible and passing is per-
Simulating your manual labor material handling mitted. You may also need to define deployment
system will help you address design and opera- strategies (work searches, idle vehicle parking,
tional issues, answering the following questions: etc.).
 ProModel 275
User Guide

Since people generally operate industrial vehi- before movement along the other axis begins.
cles, they take breaks and may be available only From a modeling standpoint, it is usually only
during certain shifts. So in addition to modeling necessary to calculate and model the longest
the vehicle, you may need to model an operator move time.
that takes breaks and works on shifts or you may
In modeling AS/RS, the storage capacity is usu-
just want to assign shifts and breaks to the vehicle
ally not a consideration and the actual inventory
resource itself, in effect, modeling the vehicle
of the system is not modeled. It would require
and the operator as one resource.
lots of overhead to model the complete inventory
in a rack with 60,000 pallet locations. Since it is
Industrial Vehicle Simulation Benefits primarily only the activity that is of interest in the
Simulating your industrial vehicles will help you simulation, actual inventory is ignored. In fact, it
address design and operational issues, answering is usually not even necessary to model specific
the following questions: stock keeping units (SKUs) being stored or
• What is the required number of vehicles to retrieved, but only distinguish between load type
handle the required activity? insofar as it affects routing and subsequent opera-
• What is the best deployment of vehicles to tions.
maximize utilization?
• What is the best deployment of vehicles to Modeling an AS/RS as a Vertical
minimize response time? Bridge Crane
One way to model an AS/RS with greater accu-
Automated Storage/Retrieval racy is to use the bridge crane construct. An AS/
RS is really just a vertical crane with the same
Systems characteristics as a bridge crane.
An automated storage/retrieval system (AS/RS)
is “a combination of equipment and controls AS/RS Simulation Benefits
which handles, stores, and retrieves materials
Simulating your AS/RS will help you address
with precision, accuracy, and speed under a
design and operational issues, answering the fol-
defined degree of automation” (The Material
lowing questions:
Handling Institute 1977). The goal of an AS/RS
• How many aisles do you need to handle the
is to provide random, high density storage with
required activity?
quick load access, all under computer control.
• What is the best sequence of stores and
retrievals to maximize throughput?
Modeling AS/RSs • What is the best stationing of empty S/R
At a simple level, an AS/RS move time may be machines to minimize response time?
modeled by taking a time from a probability dis-
tribution that approximates the time to store or
retrieve a load. More precise modeling incorpo-
rates the actual crane (horizontal) and lift (verti-
cal) speeds. Each movement usually has a
different speed and distance to travel which
means that movement along one axis is complete
276 Chapter 6:
Modeling Tips

Modeling Tips cess time at Machine_1. You can assign a value

to “Proc_time” in the Operation field or, as men-
The following section provides advanced Model- tioned above, in the Logic field in the Arrivals
ing Tips. module. The latter allows you to assign a value to
the attribute for each entity as they arrive in the
system.
Using Entity Attributes When using attributes instead of operation times,
Entity attributes are a powerful construct that ProModel substitutes the value assigned to the
enable a user to “tag” entities with characteristics attribute directly into the Operation field. So, if
to distinguish them from other entities of the “Proc_time=4.5” were your attribute assignment
same name. and the default units for time were in minutes, the
Entity attributes are place holders associated with resulting operation time would be 4.5 minutes.
individual entities which usually contain infor- You may also use attributes to determine the rout-
mation about that entity. Attributes may contain ing of an entity. Note that the Routing Rule dia-
integers or real numbers. Unlike variables, log offers a “User Condition” routing rule. In this
attributes are not global. To define attributes, use field, you can enter an expression that evaluates
the Attributes module found under the More Ele- the value of an attribute for the entity currently at
ments option of the Build menu. that location. Hence, ProModel selects the rout-
One use of an entity attribute is to represent a ing destination based on the attribute.
processing time. This is especially useful when
you base processing times at a location on some
characteristic other than entity type, such as size
or condition.
Suppose several types of tires enter a machining
center that places the steel belts on the tire. The
processing time of the tire increases as the diame-
ter of the tire increases. The following example
shows that for a tire entering a machining loca-
tion, the processing time uses the value of the
attribute “Proc_time.” You can make the attribute
assignment in the “Logic” field of the Arrivals
module.

In this example, ProModel attaches the attribute

“Proc_time” (short for process time) to the entity,
In this example, an entity attribute called
tire, which contains a value representing the pro-
“Inspected” has a value of zero or one. For unin-
 ProModel 277
User Guide

spected tires, Inspected=0. For inspected tires, Customizing Graphics

Inspected=1. Set the attribute value equal to 1 in
the Operation field of the Inspection location to Background graphics can enhance the look of
indicate an inspected tire. your models and provide valuable visual infor-
mation to convey meaning and lend credibility to
At some other location in the model, ProModel
your models. Several file types can be imported
makes a routing decision based the tire’s inspec-
from various sources including CAD drawings.
tion status. The example above shows that the
entity, tire, will route to either Inspect or
Machine_2 based on the attribute value. How to Import a background graphic:
Another use for entity attributes is for assigning
entity characteristics such as number of times 1. Choose Background Graphics from the Build
reworked, color, model type, lot size, order num- menu.
ber, etc. You may do this to reduce the number of 2. Select Front of Grid or Behind Grid.
system entities defined. 3. Choose Import Graphic from the Edit menu.
In the following example, to show that you
reworked a casting, each entity that goes through
the location Rework has its “Reworked” attribute
set equal to 1. Front of Grid When the grid is on, the grid
lines will not cover or obstruct the imported
graphic.
Behind Grid The imported graphic will be
behind the grid lines when the grid is on.
You may paste any *.BMP or *.WMF image cop-
ied to the Windows clipboard on the Layout by
choosing Paste BMP or Paste WMF from the Edit
menu.
Once you select Import Graphic from the Edit
menu and select the desired file and type, Pro-
Model imports the image into the layout. Once
this procedure is complete, you may select or
activate the graphic by clicking with the left
mouse button on the graphic. You may then drag
the mouse to move the graphic to the desired
position on the layout. You may stretch or com-
press the graphic to the size you desire using any
of its four sizing handles.
You may assign values to entity attributes in the
ProModel allows you to import *.BMP, *.WMF,
Operation field in the Processing edit table, the
*.GIF, and *.PCX file types. BMPs and WMFs
Logic field in the Arrivals edit table, and the
can also be copied to the clipboard from other
Move Logic in the Routing edit table.
applications and pasted directly into the back-
ground. To import a CAD drawing, you must
save it to one of the file formats described above.
278 Chapter 6:
Modeling Tips

Batching & Unbatching Entities

Batching refers to congregating or consolidating
multiple entities of the same or different type for
processing or movement purposes. Batching
may be either temporary or permanent. For tem-
porary batching, use the GROUP statement. For
permanent batching, use the COMBINE state-
ment.

Temporary Batching Using GROUP/

UNGROUP
Once you accomplish the purpose for which you
The GROUP statement allows you to group enti- grouped the entities, such as moving them, you
ties together and ungroup them at a later time. can unbatch the entities using the UNGROUP
You may group entities by individual entity type statement as shown next. Note that after the
by defining a process record for the type to ungrouping takes place, you must define pro-
group, or group them irrespective of entity type cesses for each potential entity that could have
by defining an ALL process record. To combine been in the group (alternatively you could define
multiple entity types in which you must control an ALL process record).
the quantity of each type requires controlling the
routing which sends parts to the grouping loca-
tion. ProModel maintains all of the identities and
attributes of the grouped entities and allows them
to remain with the individual entities after an
UNGROUP command.
To illustrate how GROUP/UNGROUP works,
suppose we want to consolidate 20 incoming
entities into a group called Batch. If the current
location performs no additional operation steps
once you group the entities, you can simply use
the statement “GROUP 20” to group the 20 enti-
ties and then specify an output of 1 Batch in the
routing. If, on the other hand, the current location COMBINE Statement
performs additional operation steps after the ProModel uses the COMBINE statement to accu-
grouping occurs, use the statement “Group 20 as mulate and consolidate a specified quantity of
Batch” and define no output routing for the entities into a single entity, optionally with a dif-
grouped entities. Instead, the entities become a ferent name. The entities may be the same type of
new entity called “Batch” that needs a process entity or they may be different. Combined entities
record defined afterwards for the same location lose their identities and attributes and you cannot
where you batched them. ungroup them later. When defining the location,
the location capacity where you use the COM-
BINE statement should be at least as large as the
 ProModel 279
User Guide

combined quantity. The following shows the cor-

rect syntax for combining 5 Castings into a single
entity called Pallet (the location, Out, should
have a capacity of at least 5).

Note that the loaded entity, Gear, has “LOAD” in

the Routing Rule field as shown here. This tells
ProModel that the gear only goes to Loc2 when a
Load command requests it.

LOAD/UNLOAD Statements
Another method of batching and unbatching
involves the LOAD and UNLOAD statements.
As with the GROUP statement, ProModel main-
tains the identities and attributes of the batched
entities. Therefore, when you use the UNLOAD
statement, each entity still has its attribute assign-
ments.
The difference between LOAD and GROUP is
that LOAD requires a “base” entity on which you
temporarily load other entities that might repre- Since the example does not specify an entity type
sent a pallet or container. Also, the entities you as part of the LOAD statement, ProModel will
are going to load, travel to the loading location on load temporarily any entity type waiting for the
an “If load request” routing rule. LOAD request. To control which entity types the
In the following example, four Gears are loaded model loads, use the “IFF” option with the
onto a pallet. Pallet is the entity which issues the LOAD statement (e.g., LOAD 4 IFF
LOAD statement. In addition, the example Entity()=gear).
includes a time element (LOAD 4 in 10 min). Once the batch moves to its destination, the
This means “load 4 gears or wait 10 minutes, model uses the UNLOAD statement to break it
whichever occurs first.” If after 10 minutes only into individual components (Gear and Pallet).
3 gears arrive, the entity loaded with the 3 gears You must define a routing for the entity Gear
continues. after the UNLOAD takes place. Typical uses for
LOAD/UNLOAD are palletizing operations,
AGV systems, and AS/RS systems.
280 Chapter 6:
Modeling Tips

ACCUM Statement
The ACCUM statement is short for “accumu-
late.” Its use is slightly different than the GROUP
and LOAD statements. ACCUM does not “batch
together” entities, but rather holds entities at a
location until a certain number accumulate. It
behaves much like a gate restricting entities until
a certain number arrive at the location. After the
required number accumulate, ProModel releases
them for downstream processing. This allows
you to model a certain type of batching which
involves simply the accumulation of parts and
their subsequent release—all at a single location.
When using the ACCUM statement, make sure
the capacity of the location where you are using If you want the entity coming from Process B to
the ACCUM statement is at least as large as the have priority and go to Process C first, define a
amount accumulating. priority in the destination field for the routing of
Process B. In the following example, we entered
Modeling Priorities a priority of 10 for the routing of the entity Cast-
ing at the location Process_B.
Priorities are an important part of modeling any
system. They range from determining which
location has priority for processing parts to
choosing the appropriate resource. Priorities
allow you to determine the order in which events
occur in the simulation. The three most common
uses of priorities deal with choosing processing
destinations, selecting resources, and prioritizing How to enter a priority for a destina-
downtimes. tion:

Choosing a Processing Destination Enter a priority value directly in the destination field,
making sure there is a comma separating the destina-
When one downstream destination exists and tion and priority.
there are two or more upstream entities compet-
ing to get there, you can use priorities. In the fol- or...
lowing example, two entities at different Click the Destination... button and enter the priority in
locations are both trying to get to Process C. the appropriate field.

Selecting Resources
Similar to the previous example, this type of pri-
oritizing refers to which of two or more pro-
 ProModel 281
User Guide

cesses, requesting the same resource will have After defining a variable, you may display it any-
priority in capturing the resource. In the Opera- where on the layout screen by simply clicking
tion field, in conjunction with the USE or GET with your mouse in the desired position with the
statements, the process with the higher priority variable highlighted in the edit table.
number gets the resource first.
How to show system throughput on the
Downtimes and Preemption screen:
ProModel uses priorities in conjunction with
resource or location downtimes to determine 1. Define the variable “thruput.”
which defined downtime takes priority. Down- 2. Display the variable on the screen.
times with priorities that are 99 or less do not
interrupt or “preempt” the activity, but begin after 3. In the processing edit table, increment the variable
by one each time an entity leaves the system.
the current process completes. Downtimes with a
priority of 100 or higher preempt the current
activity. After the downtime, the activity resumes
from where it left off. Another common, on-screen statistic is work in
process (WIP). To show this statistic on the
Displaying Statistics On Screen screen, follow the first two steps above. To accu-
rately indicate the WIP in your model, increment
Effective use of statistics lends meaning and a variable as entities enter the system and use the
credibility to simulation models. This section is decrement statement as they exit the system.
designed to show ways of displaying statistics on
screen while the simulation is running. It also
provides examples you can incorporate into any
How to display the total system time
model. for entities:
Displaying on-screen statistics is valuable for
adding model clarity as well as providing a way 1. Assign the simulation clock time to an entity
attribute at the beginning of your simulation.
to keep track of what is happening in the model.
The technique used for displaying statistics is to 2. Subtract that attribute from the current clock time at
define variables within your model, perform cer- the ending location and assign it to a variable you can
tain functions on those variables (e.g., addition, display.
subtraction, etc.), and then display those vari-
ables on the screen.
ProModel defines variables as symbols (e.g., x, y, For example, to display total system time for
and var1) that hold numeric values. They are entities in the system, define a variable and an
defined in the Variables edit table. When defining attribute. The entity attribute, Input_Time,
variables, you must include the following infor- records the time an entity entered the system.
mation: The variable, Sys_Time, records the elapsed time
• Name (may be alphanumeric combination) each entity spent in the system (clock-input
• Type (real or integer) time). By displaying the variable on the layout,
• Initial value (may be any value) you will have a dynamic value showing system
time of the exiting entity.
282 Chapter 6:
Modeling Tips

Creating Pull Systems

Stores
Types of Pull Systems
A pull system is a system in which locations pro-
duce parts only on downstream demand. There
are two types of pull systems: Process 1
• those based on limited buffer or queue sizes.
• those based on more distant “downstream”
demand.
Process 2 OrderQue
The first method, that of limited buffer sizes, is
quite easily to model using ProModel. By simply
defining limited capacity locations, a preceding
location will not send parts until capacity is avail-
able. This method works fine for most pull sys-
Creating the Pull System
tems. The second method, triggering part Now let's examine the ProModel steps to build
movement, based on more distant downstream this pull system.
demand requires use of the SEND statement to 1. Define four locations: Stores, Process_1,
trigger part movement. Process_2, and OrderQue.
There are additional ways to model pull systems 2. Define two entities: Order and Unit.
using ProModel. As you review the modeling 3. Define the processing as shown previously.
requirements of your own pull system, you 4. Define the arrivals. Schedule Units to arrive
should verify that these constructs will satisfy at location Stores. Schedule Orders to arrive
your needs. at location OrderQue.
This section shows how to use the SEND state- 5. The entity Order “drives” the system by
ment to model a pull system. The diagram below sending Units to Process_1 to fulfill the
shows the pull system we will model. Orders for order. In the operation logic at OrderQue,
finished goods arrive at the OrderQue. The arriv- use the SEND statement to send a Unit to
ing order triggers the release of a unit from the Process_1 from location Stores. A corre-
location Stores. The order continues to wait at sponding SEND rule must be used as a Rout-
OrderQue until the unit goes through Processes 1 ing Rule for Unit at Stores.
and 2. At Process_1, Unit processes for two min- 6. After the SEND statement in the operation
utes. At Process_2, Unit processes for four min- logic at the OrderQue, use a JOIN statement
utes. Finally, the Unit joins to the requesting to join a Unit to an Order. A corresponding
order waiting in the OrderQue. JOIN rule must be used as a Routing Rule
for Unit at Process_2.
7. Place the processing times for the Unit at
Process_1 and Process_2.
 ProModel 283
User Guide

When you finish, the processing and routing

should appear as shown below.

 Process Table Routing Table

Entity Location Operation (min) Blk Output Destination Rule Move Logic
Unit Stores 1 Unit Process_1 SEND 1
Unit Process_1 WAIT 2 1 Unit Process_2 FIRST 1 MOVE FOR .5
Unit Process_2 WAIT 5 1 Unit OrderQue JOIN 1 MOVE FOR .5
Order OrderQue SEND 1 Unit TO Process_1 1 Order EXIT
JOIN 1 Unit

Making Assemblies
An assembly occurs when you attach specific
items or entities to another entity such as a base
part or frame. To assemble entities, use the JOIN
or LOAD PERM statement. Implementing JOIN
is a two-step process:
1. Employ the JOIN statement at the designated
assembly location.
2. Use the JOIN routing rule for all joining
entities.
It is helpful to designate one of the joining enti-
ties to be the “base” entity which issues the JOIN
statement. In the following example, “Comp” is
the base entity. All other joining entities must
Several other ProModel statements similar to
travel to the assembly location on an “If Join
JOIN exist such as GROUP/UNGROUP, COM-
Request” routing rule. Note that for “Monitor”
BINE, LOAD, and ACCUM. You generally use
traveling to the assembly location, the word
these statements for temporary or permanent
“JOIN” appears in the Rule field. This indicates
batching. To learn more about these statements,
that “Monitor” will go to the location Assembly
see the discussion on Batching and Unbatching
only if a JOIN statement requests it elsewhere in
earlier in this section.
the model.
For more information see “Join” on page 494.
284 Chapter 6:
Modeling Tips
 ProModel 285
User Guide

Chapter 7: Building the Logic

Logic Builder How to access the Logic Builder:

The Logic Builder provides a quick and powerful
Click the right mouse button in the logic window
way to create valid statements and expressions in
or expression edit field. Or click the Build button
logic windows or fields. It takes you through the
on the logic window’s toolbar.
process of creating statements or expressions, as
well as providing point-and-click access to every
element defined in your model. The Logic
Builder knows the syntax of every statement and
function, and allows you to define logic simply
by filling in the blanks.

Using the Logic Builder

When the Logic Builder is opened from a logic
window, it remains on the screen until you click
the Close button or close the logic window or
table from which it was invoked. This allows you
to enter multiple statements in a logic window
and even move around to other logic windows
without having to constantly close and re-open
the Logic Builder. The Logic Builder closes
automatically when pasting to an expression
field.
You can move to another logic window or field
while the Logic Builder is still up by right click-
ing in that field or logic window. The Logic
Builder is then reset with only valid statements
and elements for that field or window, and will
paste the logic you build into that field or win-
dow.
286 Chapter 7:
Logic Builder

How to build a statement or expres- double-click on the statement name. Other com-
sion: ponents of the Logic Builder are as follows:

logic text box

1. Right click in an expression field or logic window
to open the Logic Builder or click on the Build button parameter entry field
in a logic window.
2. Select the statement or expression you want to use
from the list box. When opened from a logic window,
you have the option to click on the Build Expression
button to create only an expression.
3. Enter the parameters for the statement or expres-
sion. These may be expressions using model elements parameter buttons
and/or functions or other statements. Parameters may
be edited or entered manually in the Parameter Entry keypad &
field. logic buttons

4. Paste the results into the logic field or window by

clicking the Paste button. Parameter buttons Below the logic text box are
one or more buttons to control which parameter
to enter for the statement or expression. Parame-
ters can be expressions, statements, or functions.
Logic Builder Components These buttons only appear when parameters may
be required by the statement, and may change
When invoking the Logic Builder from a logic
when you select a different statement. The name
window, you have the option of building either
of the currently selected button appears immedi-
statements or expressions. Different buttons and
ately below the row of buttons and indicates
lists appear in the Logic Builder as you use the
whether or not the parameter is optional.
Logic Builder’s options depending upon whether
you are selecting a statement or building an Parameter entry field This edit field allows you
expression. The Logic Builder shown at the to enter or edit the current parameter. This only
beginning of this section shows a statement being appears when parameters may be required by the
selected for building. statement. As soon as something is entered in this
field, the Logic Builder switches to build mode to
At the top of the Logic Builder is a display (logic
allow selection of functions or elements of the
text box) of the statement or expression you are
model.
building exactly as it will appear after it is pasted
into the logic window. A brief description of the
selected statement or function is displayed in the
logic text box. This description is replaced with
the statement or function syntax when you type a
parameter, click a parameter or logic button, or
 ProModel 287
User Guide

Keypad button Click on this button to display tion of numbers, model elements, and/or func-
the numeric keypad for entering numbers in the tions, but does not include statements.
parameter entry field without using the keyboard.
Statement selection list Choose which statement
you wish to use from this list. Only valid state-
ments are displayed for the logic window or field
you are using.
Paste button This button pastes the text of the
logic text box into your logic window or field. It
is only available once the minimum requirements
of the statement or expression have been com-
pleted. The Paste button closes the dialog if you
are pasting to a field.
Logic buttons These buttons can be used to insert Clear button This button clears whatever you
logical operators and other punctuation in the have done since the last paste and allows you to
parameter entry field above. When you click the start over.
button, the operator is inserted at the cursor posi-
Close button Closes the Logic Builder without
tion in the field. A button appears only when the
pasting the current logic text box.
currently selected parameter can use that particu-
lar logical operator. Help button Launches the context sensitive help
system.
• Logical & String Operators:
Logic Elements When editing an expression in
the parameter entry field, the Statement selection
list is replaced by Logic Elements. The box on
• Time Unit Operators:
the left lists logic and model element types. The
box on the right lists individual selections from
the logic or model element type selected.
Category This combo box allows you to select
which type of statements appear in the statement
selection list below it. You can select all or a spe-
cific type.

Build Expression button This button allows you Return and Cancel Buttons When editing the
to create only an expression. It displays the logic parameters of a function or nested statement, two
elements list (see below) for you to create the additional buttons appear to the right of the
expression. An expression consists of a combina- parameter edit box: Return and Cancel.
288 Chapter 7:
Logic Builder

• Return button This button (available only replaces the parameter name in the logic text box.
when required parameters have been The parameter name reappears when the entry
entered) returns to the previous parameter field is cleared. The names of optional parame-
entry field and pastes the function or state- ters are not displayed in the logic text box.
ment at the last cursor position.
An optional shortcut to begin editing the state-
ment’s first parameter is to double click on the
statement name in the statement list box.

• Cancel button Aborts editing of the function Selecting Logic Elements

or nested statement and returns to editing The Logic Elements list box, containing model
the previous statement or function. elements and functions, appears with a selection
list box to its right. A number pad element is
Selecting Statements included in the list, which can also be accessed
using the Keypad button.
The first thing to do in creating a statement with
the Logic Builder is to select the desired state- When you click on an item in the Logic Elements
ment from the statements list box. You can list, the model elements or functions related to
restrict the list of statements to choose from using that item are listed in the selection box on the
the Statement Type combo box above the state- right. For example, when you click on Entities,
ment list. If you are just starting to use Pro- the selection list is entitled Entities and it con-
Model, you may want to select the Basic tains all the entities defined in the model.
Statements type to list only the most commonly
used statements.
To select a statement, left click on the statement
name in the list box. The statement name appears
in the logic text box along with a brief descrip-
tion. The parameter buttons also appear just
below the logic text box.
Before you begin editing the parameters of the
statement, you can select a different statement.
However, once you begin defining a parameter,
you must click the Clear button to abandon that
statement and select another.

Editing Statement Parameters

Building a statement is simply a matter of filling
in the parameters. To enter a parameter, click the
appropriate parameter button below the logic text
box. The parameter name is displayed above the
parameter entry field. Whatever you type in this
field or select from the Logic Elements list
 ProModel 289
User Guide

How to place a model element in the which will also require defined parameters. This
parameter entry field: second function is called a nested function. In
addition, a function may be nested within a
nested function. Functions can be nested as many
1. Left click on the desired element type in the Logic
Elements list box. The elements for that type will be levels as you like. In this way, the logic builder
placed in the selection list box. helps you create complex expressions that would
be difficult to enter manually.
2. Left click on the desired element to paste it into the
parameter entry field at its current cursor position. Control statements such as IF...THEN and
Note that the element is highlighted in the parameter WHILE...DO contain parameters that are them-
field; clicking on another element will replace it. selves statements. These are called nested state-
ments. For example, an IF...THEN...ELSE
statement might look something like this:

How to place a function in the parame-

Nested IF, THEN, ELSE
ter entry field:
If (Variable1 > 10) Then
1. Left click on the desired function type or on All
functions in the Logic Elements list box. The functions {
for that type will be placed in the selection list box. < Statement1 >
< Statement2 >
2. Left click on the desired function to paste it into the }
parameter entry field at its current cursor position. The
Logic Builder jumps into build mode for that func- Else
tion’s parameter(s). Note that two new buttons are {
placed to the right of the parameter edit field: Return < Statement3 >
and Cancel. < Statement4 >
3. To fill in the function’s parameter(s), repeat steps }
one and two. If you do not want to use this function,
abandon it by clicking on the Cancel button.
4. Once the function’s parameters are complete, click
One or more statements may appear in the block
on the Return button. The parameters you just com-
between the curly braces. The Logic Builder
pleted will be pasted into the function’s parameter
entry field, and the completed function with its param- allows you to define the first statement of the
eters is pasted into the original statement’s parameter block. To add other statements to the block, place
entry field. the cursor in the logic edit window where you
want the next statement and use the Logic
Builder to write the statement and paste it in. For

Nested Functions & Statements

When you select a function as the parameter for
your statement, you must also define that func-
tion’s parameter(s). In defining the function’s
parameter(s), you may use another function
290 Chapter 7:
Logic Builder

example, in the following Logic Builder window, ments without worrying about syntax and place-
an IF...THEN...ELSE statement is being built. ment of nested statements and functions.

Creating Expressions or Pasting

Logic/Model Elements Only
In addition to creating statements, the Logic
Builder can also be used to create just an expres-
sion or to simply paste a particular element such
as a variable or resource name. You may not need
to create a complete statement, or the field may
not accept statements. Pressing the Build Expres-
sion button allows you to build and paste expres-
sions, including individual logic or model
element names, into your logic window or field.
The expression being built or element being
selected is displayed at the top of the window in
the logic text box. Use the parameter edit field to
The ELSE statement is built with the parameter
build the expression. You can use model elements
button labeled Else and the statement following
and/or functions in your expression. When you
THEN is built using the button labeled Statement.
are finished, click the Paste button to place the
When you click on the parameter button labeled
expression or selected logic/model element in the
Statement, the statement list box is displayed
logic window or edit field.
where you can select from the list of valid logic
statements. Click on paste in the above example
and you get:

The parameters of nested statements may be

model elements or functions, and within those
functions you may have nested functions. This
allows you to easily build complex control state-
 ProModel 291
User Guide

Operation Logic double-clicking in the field or clicking on the

Operation button. Alternatively, the Logic
Operation logic defines what happens to an entity Builder can help build logic and is accessed by
when it enters a location. Operation logic is clicking the right mouse button inside the opera-
optional, but typically contains at least a WAIT tion field or logic window. All statements, func-
statement for the amount of time the entity should tions, and distributions available in the operation
spend at the location. For modeling purposes, the field are discussed in detail, including examples,
exact nature of the operation (joining, grouping, in “Statements and Functions” on page 429.
etc.) is irrelevant. What is essential is to know
what happens in terms of the time consumed, the Example
resources used, and any other logic that impacts
system performance. For operations requiring
Each entity processes the operation statements defined
more than a time and resource designation, for it at a particular location, independent of other
detailed logic may need to be defined using operations performed on other entities at the same
IF...THEN or action statements. location. The following example presents the operation
logic for an entity joining an entity, EntB, and renam-
Special operation statements are provided to
ing the entity as EntC.
define the activities that are to occur. By using
operation logic, any of the following activities
can be defined:
• Detain an entity for a specified length of
time while an activity is performed.
• Detain an entity until one or more resources
are obtained.
• Detain an entity until one or more additional
entities are joined to it.
• Detach one or more entities from the current
entity.
• Consolidate one or more entities into a
group.
• Separate an entity into two or more entities.
• Detain an entity until a particular system
condition is reached.
• Destroy an entity.
• Create one or more new entities.
• Execute a block of logic (assignment of vari-
ables, etc.).
• Signal the start of some other action in the
system (e.g., place an order).
• Make some decision about further routing.
Statements can be typed directly into the opera-
tion field, or inside a larger logic window after
292 Chapter 7:
Preemption Process Logic

Preemption Process Logic How to create a preemption process

record:
With Preemption Process Logic, ProModel
makes it possible to control preemption rather
1. Using the same entity and location names, create a
than limit you to default preemption priority lev- process record somewhere following the process
els and values. This feature pertains only to the record where the preemption may occur.
preemption of entities using a location. It does
not include preemption of downtimes.
Normally, if an entity or downtime attempts to
preempt an entity that is using a location, the
location is immediately preempted (assuming it is
preemptable). Once the location finishes the pre-
empting activity, the original preempted entity
regains possession of the location and resumes 2. Click on the Entity button to display the Entities
processing where it left off. dialog shown here.
To override this default preemption procedure, in
the case of entities that are preempted by another
entity or a downtime, ProModel allows a Pre-
emption Process Record to be defined which
postpones the actual preemption of the location
until after the current entity explicitly releases it.
The Preemption Process Record, allows you to
control if and when the location is given up. In
the case of a preemptive request for a location,
the preemption process record allows the entity to
be routed elsewhere if desired. If a preemption
process is defined, the actual preemption does not
3. Check the Preemption Process option box and
occur until the preemption process explicitly
click OK.
frees the location.
4. Click on the Operation button to enter the preemp-
After the location is given up, the entity may (1) tion logic. You can use any valid operation logic
elect to use an alternative location to complete including delays. It is recommended that you enter a
the process, or (2) seek to regain access to the comment as the first line in the logic indicating that
same location to complete the process. this is a preemption process. This will make the record
easily identifiable as a preemption process.
While an entity is executing a preemption pro-
cess, it cannot be preempted by any other entity
or downtime.
Please note

When a preemption occurs, the entity looks for-

ward and then from the beginning of the process
 ProModel 293
User Guide

list trying to find a preemption process that WAIT or USE statement. It returns a time value
matches the same entity and location (a process in default time units (real). If multiple entities are
with ALL as the entity name will match any preempted from a location, it returns the longest
entity). If a match is found, the preemption pro- remaining time for all of the entities.
cess gets executed. Otherwise the default preemp-
tion occurs. Only the first preemption process Please note
encountered will be executed in the event that
multiple preemption processes are defined with
The values returned by these functions must be
the same entity and location names.
checked before any processing delay occurs since
they are updated whenever a preemption takes
place. If the values must be referred to later, they
should be assigned to the entity’s attribute or to a
Possible Effects of Delayed local variable.
Preemption
Several circumstances can be created through the
use of preemption process records. An entity
delaying a preemption, for example, may find at Preemption Process Example
the conclusion of the delay that the preemption is In this example, a Gear may be preempted in its
no longer required, or that it faces an even higher occupancy of the Lathe. This preemption may be
preemption priority. because of either a preempting entity or down-
In cases where an entity has multiple locations or time. Before the actual preemption takes place,
resources from which to choose, a preemptive the operation time for the Gear is interrupted and
request for any one of them is not necessarily a the Gear immediately begins processing the oper-
commitment to select that particular location. If ation logic defined in the preemption process.
any of the alternative locations becomes avail- In the preemption process, the remaining opera-
able, the entity will select it and withdraw the tion time is stored in Attr1. The Gear routes to
preemption request. Lathe_Backup where it finishes processing.
Because the backup lathe is not as efficient as the
Functions for Defining Logic in a other Lathe, it takes 50% longer to process the
Preemption Process Gear on Lathe_Backup. Therefore, we multiply
the time left to process the Gear by a factor of
The Preemption Process Logic feature includes 1.5.
the following functions for use in the preemption
logic.
PREEMPTOR() Identifies whether a downtime
or entity is making the preemptive request. It
returns a 0 if the preemptor is a downtime, other-
wise it returns the index number of the preempt-
ing entity.
TIMELEFT() Returns the amount of time
remaining if the preemption occurred during a
294 Chapter 7:
Routing Move Logic

Process Table Routing Move Logic

Entity Location Operation (min)
To accommodate the use of multiple resources
Gear Lathe WAIT 10 min
for entity movement, the Move Logic window
Gear Lathe Attr1=TIMELEFT()
allows you to define the method of movement as
Gear Lathe_Backup WAIT Attr1*1.5
well as any other logic to be executed upon
movement.
Routing Table
Once the route condition or rule has been satis-
Blk Output Destination Rule Move Logic
fied for allowing an entity to route to a particular
1 Gear Mill FIRST 1
location, the move logic is immediately executed.
1 Gear Lathe_Backup FIRST 1
The entity does not actually leave the current
1 Gear Mill FIRST 1
location until a move related statement (MOVE
FOR, MOVE ON, or MOVE WITH) is executed
or until the move logic is completed, whichever
happens first. This allows the entity to get one or
more resources, wait additional time, or wait until
a condition is satisfied before actually leaving the
location.
Any statements encountered in the move logic
after a move related statement are executed after
the move is complete, but before the entity actu-
ally enters the next location. This is often useful
for freeing multiple resources used to transport
the entity.
When you access the Processing module in the
Build menu, the Routing edit table appears with
the Move Logic button in the right hand column
as shown here.
 ProModel 295
User Guide

When you click the Move Logic the following MOVE WITH This statement is used to move an
Move Logic window appears. entity using a designated resource, such as a fork-
lift. With the OR operator, you can designate
alternative resources for making the move. In this
case, the statement captures the first available
alternative resource designated in the expression
and makes the move. If one of the resources is
already owned by the entity, that resource will be
used. Please note that you cannot use the AND
operator to capture (and move with) more than
one resource with this statement. To move an
entity with multiple resources, you must use a
GET statement to capture the additional
This window allows you to manually edit the
resources.
logic or click on the Build button to use the Logic
Builder. It also provides other convenient but- This statement also allows you to set the priority
tons for editing and printing the move logic. (p1) for accessing the designated resource. If the
resource is already owned by the entity, this pri-
ority is ignored.
Move-Related Statements
If the resource is static, a time (FOR <time>) may
Admissible statements in the Move Logic win- be specified for the move.
dow include the new move-related statements
listed here. A brief description of how each state- The resource used to make the move is only freed
ment functions in ProModel follows the list. See if the THEN FREE option is used.
“Statements and Functions” on page 429 for MOVE ON <path network> Use this statement to
complete syntax, description, and examples of move an entity along a path network.
these statements.

MOVE statements

MOVE FOR <time>

MOVE WITH<res1>{,{p1}} {FOR <time>} {THEN
FREE}
MOVE ON <path network>

MOVE FOR <time> Used to specify the amount

of time required to move the entity. If the <time>
is zero, events for other entities occurring at the
same simulation time will be processed before
any additional logic is processed for the current
entity.
296 Chapter 7:
Routing Move Logic

Please note This processing sequence allows you to GET or

JOINTLY GET one or more resources before the
Not entering no move related statement in the move and optionally FREE one or more
Move Logic window causes entities to move resources at the end of the move. Please note that
immediately to the next location when the move if a move related statement is not encountered in
logic is completed and begin executing the opera- the logic, an implied MOVE will be assumed and
tion logic for that location. executed at the end of the logic.

Related Logic Statements

In addition to these routing specific statements,
all statements and functions allowed in exit logic
may be used in the Move Logic window. Note,
however, that the LOCATION() function returns
the current location when executed before the
MOVE statement and returns the destination
location when executed after the MOVE state-
ment. Additional statements permitted before a
move-related statement include: WAIT, WAIT
UNTIL, GET, JOINTLY GET, and USE.
See “Statements and Functions” on page 429 for
full description, elements explained, and exam-
ples.

Statement Processing
Statements executed before a MOVE related
statement are processed after the entity claims the
next location but before the entity actually
departs from the current location.
Statements executed after a MOVE related state-
ment are processed after the move has been com-
pleted but before the entity enters the location. If
there is no move logic, the entity continues pro-
cessing until it encounters an implicit WAIT.
However, if “MOVE FOR 0” is placed in the
move logic, the event list is broken and other pro-
cesses scheduled to occur at the same time are
executed. Once these processes are executed, the
entity enters the destination location.
 ProModel 297
User Guide

Shift & Break Logic Off Shift & Break Logic Logic executed at the
instant the location or resource actually goes off
line.
Shift & Break Logic
Shift and break logic are optional and are defined How to determine the sequence of
in four distinct logic windows. Each logic win- events
dow is executed in a specific sequence through-
out the simulation run. You can define logic that 1. When a location or resource is scheduled to go off
controls how resources and locations go off duty line due to a break or the end of a shift, the pre-start
or off line and what happens once they are off- logic for that particular location or resource is exe-
line. cuted.
To define shift or break logic, click on the Logic 2. After executing the pre-start logic, which may con-
button in shift assignments to display a submenu tain conditional (WAIT UNTIL) or time (WAIT)
of four shift events for which logic may be delays, the location or resource is taken off line,
assuming it is either available or the priority is high
defined. Selecting an event from the submenu
enough for preemption.
displays a standard logic window. You can enter
separate logic for each of these four events to be 3. At the instant the location or resource is taken off
executed when the event occurs. See Sequence of line, the Off-Shift or Break logic is executed.
Events below. 4. After executing this logic, the location or resource
waits until the time defined in the shift file expires
before going back on line.

Please note
You may want to use the Logic Builder to help
you enter the logic. Just click on the Build button If the off-shift and break nodes are not specified
in the logic window. in the Resource Specs dialog, the resource will
Pre-Off Shift or Pre-Break Logic Executed when- stay at the current node. If no resources or loca-
ever the location or resource is scheduled to go tions are assigned to a shift, the shift is ignored.
off shift or on break. This occurs before the loca-
tion or resource is checked for availability, and is
executed regardless of availability. This logic
may be used to check certain conditions before Functions and Statements
actually taking the resource or location off line. ProModel uses several functions and statements
The logic is executed for each resource and loca- specifically for off-shift and break logic: SKIP,
tion listed as members for this shift assignment PRIORITY, DTLEFT(), FORLOCATION(),
record. This allows some members to be taken off FORRESOURCE(), and RESOURCE(). Follow-
line while others may be forced to wait. (Pre-off ing is a brief description of each. For more
shift and pre-break logic may be referred to in details, see “Statements and Functions” on
this manual as pre-start logic when speaking of page 429.
either one.)
298 Chapter 7:
Shift & Break Logic

SKIP If used in pre-start logic, it causes the off-

shift or break time (including any off-shift or
break logic) to be skipped so that the location or
resource never goes off line. If used in the off-
shift or break logic, it causes the off-line time
defined in the shift file to be skipped. This
allows you to specify a WAIT statement for the
off-line time and then SKIP the off-line time
defined in the shift file.
PRIORITY This statement provides an alterna-
tive way to specify off-shift or break priorities. It
also allows the priority to be changed after some
time being off-shift or on break. If the priority is
changed to a value lower than the current value,
the system will check if any preemption may
occur at that time. This statement is not allowed
in pre-off shift or pre-break logic.
DTLEFT() This function returns the remaining
off-shift time based on when the location or
resource is scheduled to go back on shift as
defined in the shift file. It may be used in off-shift
and break logic to adjust the actual time that the
location or resource is off-line.
FORLOCATION() This function returns TRUE
if the member for which the shift or break logic
being executed is a location. This may be
fol0lowed by a test using the LOCATION() func-
tion to determine the precise location.
FORRESOURCE() This function returns TRUE
if the member for which the shift or break logic
being executed is a resource. The RESOURCE()
function may then be used to determine the pre-
cise resource if multiple resources are listed as
members.
RESOURCE() This returns the name-index num-
ber of the resource currently processing the off-
shift or break logic.
In addition to these functions, the LOCATION()
and DTDELAY() functions are particularly use-
ful when defining off-shift and break logic.
 ProModel 299
User Guide

Chapter 8: Using Auxiliary

Tools

Tools Menu Model is running, you will be prompted to close

ProModel prior to running the License Manager.
The Tools menu gives you access to powerful
tools to help you through the model building pro- Options Allows you to set various directory and
cess. display defaults.
Customize Allows you to customize the Tools
menu.
Additional Tools Tools can be added to the Tools
menu by using the Customize option. These tools
are discussed in the latter part of this chapter.

Expression Search Allows you to perform global

search and replace functions on expressions
throughout any part of the model.
Graphic Editor Allows you to create, edit, rear-
range, or delete library graphics for use as enti-
ties, locations, resources and background
graphics.
Stat::Fit Launches Stat::Fit and allows you to fit
analytical distributions to user data.
3D Animator Launches 3D Animator if it is
installed. If 3D Animator is not installed, a dialog
will provide information about purchasing 3D
Animator or obtaining a demonstration version.
License Manager Launches the license manager.
Since license changes cannot be made while Pro-
300 Chapter 8:
Expression Search

Expression Search and some dialog boxes where text is entered for
defining the model, such as attributes or arrays.
The Expression Search feature is used to find or
Search Notes Check this box to include Notes
replace text entered into logic windows and
fields in the text search.
expression fields, such as location downtime
logic or location capacity. Name fields can be Whole Words Only Check this box to search for
found, but not replaced. Reference fields can be only whole words or groups of whole words that
found and replaced. However, when the name of match the text to find. For example, searching for
a location, resource, or entity is changed, the user “Attr” without the Whole Words Only box
will be prompted to automatically change all ref- checked will find “Attr1” and “Attr2” whereas a
erences to the new name. There are three types of search with the box checked would find neither.
searches: Find expression, Replace expression,
Text to Find Enter the text expression you want
and Search Next expression.
to find.

Replace
Choosing replace gives you these options in addi-
tion to the find options:
Prompt on Replace Check this box if each time
ProModel finds a match, you want ProModel to
ask if you want that particular match changed to
the replacement text. The prompt will give you
the option to replace that particular match, skip
that particular match, or to cancel the search alto-
How to perform an expression search: gether.
New Text Enter the text you want to replace the
• Select Expression Search from the Tools menu. search text.

Search Next
Expression Search Sub-Menu Choosing Search Next in the Expression Search
Choices submenu will resume the most recently canceled
search. For example, suppose you begin a search
and then break out of the search to adjust some-
Find thing in the model. If you want to continue the
A dialog box gives you the following options original search, you can select Search Next and
after choosing Find from the Expression Search ProModel will start the search again at the place
submenu: you stopped searching.

Modules to Search Check the modules you want

to search. “Other” includes all other edit tables
 ProModel 301
User Guide

Find Expression entire line on which the text was found, with the
search expression highlighted.
The Find Expression option allows you to find
each occurrence of an expression in a model.

How to find an expression:

1. From the Tools menu, select Expression Search.

2. Select Find... from the submenu.
3. Supply the necessary details in the Find dialog box
shown below. Clicking Select All or Deselect All but- How to find the next match of a text
ton will check or uncheck every module. expression:
4. Click OK.
• Click on Search Again

Replace Expression
The Replace Expression option allows you to
find each occurrence of an expression in a model
and replace that expression with a new expres-
sion.

How to replace an expression with

another expression:

1. Select Replace... from the Expression Search sub-

menu.

Once the Expression Search has found the first

occurrence of an expression, a dialog box will
appear giving information on exactly where the
text was found. Then ProModel will display the
following dialog, including a box displaying the
302 Chapter 8:
Expression Search

2. Supply the necessary details in the Replace dialog Important Notes Regarding
box shown below. Clicking Select All or Deselect All
button will check or uncheck every module. Expression Searches
1. Not every field of every module is included.
Fields such as statistics, text in graphics, or
yes/no fields which may not be edited cannot
be searched for or replaced. To replace
record identifiers, see number six.
2. Under “Modules to Search,” the Other
option refers to information entered in places
not listed in the dialog box, including the
Simulation Options dialog box.
3. Notes fields are not part of the actual model
data, therefore they are not automatically
included in the search. Notes also include
comments in the model. If you want to
search or replace Notes fields, check the
Search Notes option in the Find or Replace
3. Click on OK. If you have chosen “Prompt on dialog boxes.
Replace,” ProModel will then display the following 4. The Whole Words Only option interprets
dialog box if it finds the text you specified. words loosely enough to distinguish words
not separated by spaces. For example,
searching for “Attr1” in the expression
Attr1=Attr1+Attr2, would find both occur-
rences. You can search for expressions
longer than a whole word, such as
“Attr1=Attr1+Attr2,” as whole word expres-
sions. To find a portion of a name, like “Attr”
4. Choose: in “Attr1,” deselect the Whole Words Only
option.
Yes to change the text and search for the next match. 5. Once the Expression Search has found the
first occurrence of an expression, a dialog
Change All to change every match. box will appear giving information on
exactly where the text was found. This
No to skip this match and search for the next match. includes a box displaying the entire line on
which the text was found, with the search
Go to Module to edit the text directly. expression highlighted. In some cases the
box may be too small to display the entire
Cancel to leave the match intact and stop searching.
line. To see the hidden portion of the text,
left click with the left mouse button on the
text, and use the left and right arrow keys to
scroll the text horizontally.
 ProModel 303
User Guide

6. The Replace feature cannot be used to

change an element identifier. To change all
occurrences of a model element name (such
as a location name), change the name of the
element where it is defined and all other
expressions containing the name, as well as
any references to this record, will be changed
automatically.

Local Find and Replace

In the process of creating logic, you may need to
search for specific text. The local find and
replace button in the operation logic window
opens a dialog that will allow you to search the
logic for specific text.
304 Chapter 8:
Graphic Editor

Graphic Editor a set of icons representing the graphics in the

graphics library.
The Graphic Editor allows you to create, edit,
rearrange, or delete library graphics within a par-
Graphic Tools
ticular graphics library file. You can also copy Library Edit
Button Bar
graphics from one library to another. Graphics Buttons
from several libraries can even be merged into a
single graphic. Each graphics library is saved
with the grid size and scaled used to create the
graphics.

Graphic Icons

Edit Window

Each of the tools in the Graphic Tools button bar

is discussed in this section, including the proce-
dures for creating and editing a graphic’s compo-
How to access the graphic editor from nents (called “objects”) using the drawing tools.
within ProModel:
Graphic Editor Menus
• Select Graphic Editor from the Tools menu.
The Graphic Editor menu bar includes the fol-
lowing menus:
File The File menu allows you to open a graph-
How to access the graphic editor from
ics library for editing and saving a current library.
the program manager: It also allows you to print a single graphic or an
entire library.
• Double click the Graphic Editor icon in the Pro-
Model Group. This method allows you to use the Edit The Edit menu provides functions for
Graphic Editor as a separate application from Pro- selecting and duplicating one or more objects that
Model. comprise a library graphic. In addition, it pro-
vides functions to import and export graphics
from other applications.
Graphics The Graphics menu is for manipulat-
Overview ing one or more objects that comprise a library
The Graphic Editor consists of a menu bar, a graphic. With this menu, you can group several
Graphic Tools button bar, a Graphic Library objects together, flip and rotate objects, and alter
menu, Library Edit buttons, an Edit window, and the color, fill pattern and line style of objects.
 ProModel 305
User Guide

You can also adjust the dimensions of the entire Save As Brings up the Save As dialog box for
graphic. saving the current Graphics library file under a
new filename. Graphic Library files have the file
Options The Options menu controls the editing
extension GLB.
environment. With this menu you can use a grid
to help you align component objects, edit that Print Graphic Prints the graphic in the Edit win-
grid, and require objects to snap to it. Finally, the dow only.
Options menu allows you to zoom in and out on
Print Library Prints the entire current graphic
the graphic so you can edit the graphic at differ-
library.
ent sizes.
Exit Quits the Graphic Editor with an option to
Window The Window menu allows you to
save the current library if changes have been
arrange the windows (or iconized windows) cur-
made since the last save.
rently displayed on the screen such that all win-
dows are visible at once. It also allows you to Recently Opened Files Lists the five most
bring any individual window to the forefront of recently retrieved graphics libraries. Selecting
the display. This is particularly useful when you one of these options will retrieve the listed graph-
are opening multiple graphic libraries and want to ics library.
view all libraries simultaneously.
Opening a Graphics Library File
File Menu All individual library graphics are loaded from
and saved to the current graphics library, which,
by default, is the one specified for the current
model. However, other graphic libraries may be
opened for editing at any time. The name of the
current library is displayed in the title bar of the
window for each library. More than one library
can be opened and viewed on the screen at a time.
Opening more than one graphic library simulta-
neously facilitates copying graphics between
New Creates an empty graphics library. libraries.
Open Brings up the Open Library Graphics dia-
log box for specifying which graphics library file How to open another graphics library
to retrieve. Graphics library files have the file file:
extension GLB.
1. Choose Open from the File menu.
Close Closes the current graphic library. If the
graphics library has been changed since the last 2. Enter or select the name of the desired graphics
save, you will have the option to save it. library.
3. To view all open graphic libraries, choose Tile or
Save Saves an open graphics library under the
Cascade from the Window menu.
current file name or prompts you for a name if the
graphics library has not been named.
306 Chapter 8:
Graphic Editor

Please note Printing an Individual Graphic

A history list is given at the bottom of the File How to print an individual graphic:
menu so you are able to quickly retrieve the last
five libraries opened. 1. Double click the mouse on the desired graphic’s
icon, or select the graphic’s icon and click the Edit but-
ton.
2. Select Print Graphic from the File menu.
Closing a Graphics Library File
3. Choose the desired options from the resulting Print
When you are finished working with a graphics dialog box and click OK.
library, you can close it to save screen space and
memory. This option will not affect the graphic
library used with any model.
Printing an Entire Graphics Library
How to close a graphics library file:
How to print an entire graphics
• Choose Close from the File menu. library:

1. Select Print Library from the File menu.

Saving a Graphics Library File 2. Choose the desired print options from the Library
Print dialog box and select OK.
Once a graphic has been created or edited and
placed in the current library, the library file must
be saved in order to make the changes permanent.
Please note
How to save a graphics library file:
If more than one graphic library is open, Pro-
• Select Save from the File menu to save the library Model will print the active graphic library only.
with the same name.

How to save a graphics library file Edit Menu

with a new name: Use the Edit menu for selecting and duplicating
the individual objects comprising a library
• Select Save As from the File menu to save the graphic. You may also use it to exchange graph-
library with a new name. ics with other applications. To use the Edit menu
functions, load the graphic you wish to edit by
 ProModel 307
User Guide

selecting its icon from the library and clicking the Export Graphic Exports the graphic in the Edit
Edit button, or double click the icon. window to a WMF or BMP file.

Importing a Graphic

How to import a graphic into a

graphic library:

1. Select the box to which you would like to add the

graphic in the library. If you want to create a new
graphic, choose the blank box at the end.
2. Select Import Graphic from the Edit menu.
3. Enter the name of the graphic you would like to
Cut Removes the selected object(s) and makes a import.
temporary copy that may be pasted back into the 4. Select OK to close the import graphic dialog box.
edit window later. 5. Click on the Save button on the top right side of the
Copy Makes a temporary copy of the selected library window.
object(s) to be pasted later.
Paste Adds the most recently cut or copied
object(s) to the current graphic. Exporting a Graphic
Delete Deletes the selected objects from the cur-
rent graphic. How to export a graphic:
Select All Selects all of the objects comprising
the current graphic. 1. Double-click the mouse on the desired graphic’s
icon, or select the graphic’s icon and click the Edit but-
Copy to Clipboard Copies the entire graphic to ton.
the clipboard as a bitmap so it can be pasted into 2. Select Export Graphic from the Edit menu.
other applications including word processors.
3. Enter a valid DOS name for the graphic in the
Paste WMF Pastes a Windows metafile (WMF) resulting dialog box.
from the Windows clipboard into the Edit win- 4. Click the OK button in the export graphic dialog
dow. You must have previously copied a Win- box.
dows metafile to the Windows clipboard in
another application.
Paste BMP Pastes a bitmap file (BMP) from the
Windows clipboard into the Edit window. You
must first copy a bitmap file to the Windows clip-
board.
Import Graphic Imports a WMF, EMF, BMP,
PCX or GIF file into the Edit window.
308 Chapter 8:
Graphic Editor

Copying a Graphic from One Library graphic. This menu item works like the button of
to Another the same name described later in this chapter.
Flip Vertical Vertically flips the entire graphic or
How to copy an icon from one library any selected objects of the current graphic. This
to another menu item works like the button of the same
name described later in this chapter.
1. Open both libraries. Rotate Rotates the entire graphic or any selected
2. Drag the graphic’s icon from the first graphic objects of the current graphic 90 degrees clock-
library to the second graphic library (preferably left to wise. This menu item works like the button of the
right). same name described later in this chapter.
3. Save the destination library by choosing Save from Move to Front Moves the selected object in front
the File menu. of all other objects. Use this option to see an
object obscured by other objects. This menu item
works like the button of the same name described
later in this chapter (to move an object one posi-
Graphics Menu tion forward at a time, use the Graphic Tools).
The Graphics menu is for manipulating one or Move to Back Moves the selected object behind
more objects that comprise a library graphic. all other objects. Use this option to send an object
With this menu, you can group several objects obscuring other objects to the background. This
together, flip and rotate objects, and alter the menu item works like the button of the same
color, fill pattern and line style of objects. You name described later in this chapter.
can also adjust the dimensions of the entire
Group Combines or groups several objects into
graphic.
a single object for sizing and editing.
Ungroup Ungroups several grouped objects so
they may be edited individually.
Line Styles Allows the user to choose the line
style including solid, dashed, line thickness, and
optional arrowheads on either end of the line.
Fill Patterns Allows the user to choose the fill
pattern for solid objects including transparent,
slant, backward slant, grid, crosshatch, vertical,
horizontal, solid, vertical gradient, and horizontal
gradient.
Line Color Allows the user to choose the line
color and create custom colors.

Flip Horizontal Horizontally flips the entire Fill Color Allows the user to choose the fill color
graphic or any selected objects of the current and create custom colors for solid objects.
 ProModel 309
User Guide

Dimension Brings up the Dimensions dialog box 2. Choose Ungroup from the Graphics menu.
for defining the graphic dimension. The dimen-
sion can be height or width. The units can be feet
or meters.
Line Styles
Please note You may choose different styles for the lines and
borders of objects by choosing Line Styles in the
Line Styles, Fill Patterns, Line Color, and Fill Graphic Editor Graphics menu.
Color set the feature and cause the setting to be
applied to the currently selected elements.

Group
When using the graphic tools to create an icon, it
is often helpful to group several graphics into a
single graphic for editing purposes. For example,
you may create an icon using the square, line, and
circle tool and want to work with them as a single
item.

How to group objects together:

1. Use selector to select all objects you desire to group.

Hold the shift key down to select more than one object
at a time.
2. Choose Group from the Graphics menu. How to change the line style or border
3. Manipulate the group as necessary. style of an object:

1. Select the desired object(s) using the Selector.

Ungroup 2. Choose Line Styles from the Graphic Editor

Graphics menu.
The Ungroup option allows you to ungroup sev-
3. Click on the desired style.
eral grouped objects.

How to ungroup previously grouped

objects:

1. Use the selector to select the object you desire to

ungroup.
310 Chapter 8:
Graphic Editor

Please note 2. Choose Fill Patterns from the Graphic Editor

Graphics menu.
The arrowhead color is the same as the line color 3. Click on the desired fill pattern.
and is defined through the Line Color in the
Graphics menu.

Line and Fill Color

You may also select a custom color for your lines
Fill Patterns and graphics.
Various patterns may be used to fill each object
by choosing Fill Patterns from the Graphic Editor How to change line or fill color
Graphics menu.
1. Select the line or graphic you want to change.
2. Choose Line Color or Fill Color from the Graph-
ics menu.
3. From the dialog below, click on the color you wish
to use.

Dimension
You can define the height or width of an object in
feet or meters from the Dimensions Dialog box.
This will determine how large the graphic
appears when placed on a model layout. For
How to change the fill pattern of an example, to change the width of a graphic loaded
object:

1. Select the desired object(s) using the Selector.

 ProModel 311
User Guide

in the Edit window to 5.00 feet, enter the follow- know the graphic is actually 2.00 x 1.50 feet, you
ing in the Dimensions dialog box: will need to adjust the proportions of the graphic
accordingly by using various tools from the Tools
button bar.

Options Menu
The Options menu controls the editing environ-
ment. With this menu you can use a grid to help
align objects, edit that grid, and require objects to
snap to it. Finally, the Options menu allows you
to zoom in and out on the graphic so you can edit
the graphic at different sizes.
How to change the graphic’s dimen-
sions:

1. Load a graphic into the Edit window.

2. Select Dimension from the Graphics menu.
3. Enter the new graphic dimension and click OK.
Grid Settings Brings up the Grid dialog box for
choosing the size, color and visibility of the grid.
For example, a graphic of a computer is dis- Show Grid Causes the grid to appear in the back-
played in the Graphic Edit window. The size of ground for editing purposes. If the grid is on,
the graphic in the Graphic Edit window is 1.40 x choosing this option will turn it off. This is the
1.00 as shown below. same as choosing Grid On in the Grid dialog box.
Snap to Grid Positions any object subsequently
drawn or moved on the layout on the nearest grid
However, the computer is really 2 feet wide. To line. This option works whether the grid is visible
change the graphic’s dimensions, select Dimen- or not.
sion from the Options menu. Type 2 for the hori- Background Color Brings up the color dialog
zontal dimension and click OK. box for choosing a background color for the lay-
out window.
Zoom Shrinks or enlarges your view of the
Notice the vertical dimension is automatically graphic by the percentage selected.
adjusted to 1.43. You can only define either the
horizontal or vertical dimension of the graphic. If Grid Settings
you define one dimension, the software will auto-
matically calculate the other according to the pro- The grid size is changed by using the scroll bar to
portions of the graphic in the Edit window. If you the right of the grid dialog box. Move the scroll
bar up to increase the grid size and move the
312 Chapter 8:
Graphic Editor

scroll bar down to decrease the grid size. To Show Grid

change the color of the fine grid lines, select the
Ones button and then choose a color. To change
How to show the grid on the layout
the color of the coarse grid lines, select the Tens
button and choose a color. window:
Instead of viewing boxes as the grid units, you • Choose Show Grid from the Options menu.
may choose dots by selecting the dots box. You
may also choose to switch the grid, as well as the
grid snap, on in this same area.
Snap to Grid

How to have all new and edited objects

snap to the grid:

• Choose Snap to Grid from the Options menu.

Background Color

How to change the background color

of the edit window:

• Choose Background Color from the Options menu.

Zoom

How to change the distance per grid How to magnify a graphic:

unit in the Graphic Editor:
1. Choose Zoom from the Options menu.
1. Select Grid Settings from the Options menu. 2. Choose the level of magnification from the sub-
menu.
2. Click on the Scale button.
3. Define the distance per grid unit in either feet or
meters and click OK.
Window Menu
The Window menu is used to manipulate the var-
ious windows in the Graphic Editor and follows
 ProModel 313
User Guide

the Microsoft Windows standard for Window Clear Clears the contents of the edit window.
menus.
How to edit a graphic:

• Double-click on the graphic in the library. This

method clears the contents of the Edit window before
loading the new graphic.
Tile Causes all open windows to fit in the avail-
able screen space. Windows that may be hidden
behind other windows will become visible. This or...
is useful when desiring to view more than one
graphic library on the screen at a time.
Cascade Causes all open windows to overlap • Select the graphic by clicking once on the graphic
and then click the Edit button. This method clears the
such that the title bar of each window is visible.
contents of the Edit window before loading the new
Arrange Icons Takes all active iconized windows graphic.
and arranges them neatly along the bottom of the
screen.
Open Libraries Displays all graphic libraries
Manipulating Graphics
currently open in the Graphic Editor. To switch to
another open library, click on the desired name. Among other things, a graphic can be reduced,
enlarged, combined, and reordered.
Library Edit Buttons
How to change a graphic’s size:
The Graphic Editor contains four library edit but-
tons: Edit, Save, Delete, and Clear. 1. Select the graphic in the Edit window using the
selector.
2. Choose Group from the Graphics menu.
3. Select one of the small gray boxes at the graphic
edge to reduce or enlarge the graphic size. The selector
will change to a cross-hair when you are near a gray
Edit Retrieves a selected graphic from the box.
library to the edit window.
4. Drag the box to the desired size.
Save Saves a graphic from the Edit window to
the library. For a new graphic to be added to the
library, the blank box at the end of the library
must be selected. Otherwise, the graphic in the Several graphics can be combined together to
Edit window will replace whichever graphic’s create a single graphic. For example, a desk and a
icon is selected. chair are separate graphics but would be easier to
use if they were combined to form a single
Delete Deletes the selected graphic from the graphic.
library.
314 Chapter 8:
Graphic Editor

How to combine two graphics: Naming a Graphic

Graphics can be named for resources, locations,
1. Load the first graphic into the edit window.
and entities, or merely for easier identification.
2. Drag the second graphic into the edit window. When a named graphic is chosen while building a
3. Position and size the two graphics as desired. model, instead of entering a default name, such as
Loc1, ProModel will enter the graphic's name,
4. Click the blank box in the graphic library.
such as Desk. If the name already exists for a
5. Click the Save button. location or resource graphic, a number will be
appended (Desk1, Desk2, etc.). If the name
already exists for an entity graphic, a letter will
be appended (ChairA, ChairB, etc.). This will
How to change the order of graphics in make the model easier to understand and use.
a graphic library:

• Drag a graphic to the desired location in the library.

Create New Graphics and

Libraries

How to create a new graphic

1. Select Graphic Editor from the Tools menu. How to name a graphic:
2. Use the drawing tools to create the new graphic.
1. Enter the desired name at the bottom left of the
3. Click the Save button on the graphic editor.
screen where it says “Name.”
4. The image appears at the end of the existing icons. 2. Click the Save button to save the named graphic.

How to create a new graphic library Please note

1. Select Graphic Editor from the Tools menu.
Correct syntax for location, resource, and entity
2. Select New from the File menu. names should be used when entering a name in
3. Use the drawing tools to create any graphics you the Name field if the graphic is intended to repre-
wish to use in your library. You may also copy and sent locations, resources, or entities. Graphic
paste graphics from existing libraries. names are allowed to have spaces which auto-
4. After you finish preparing each new image, click
matically convert to underscores “_” when used
the Save button on the graphic editor. for locations, resources, or entities.
 ProModel 315
User Guide

Graphic Tools Button Bar Selector

The Graphic Tools Button Bar contains the tools The Selector is a pointing device that allows you
necessary to create and edit a graphic’s compo- to select one or more objects of a graphic. It also
nent objects. The drawing tools are the main tools allows you to move, size, and shape all graphic
through which graphics are created and edited in objects.
the Editing window. The drawing tools include
the following: Selector

• Selector
• Entity Spots
• Text
• Status Lights
• Lines
• Flip Horizontal How to move an object:
• Arcs
• Flip Vertical 1. Click on the Selector button.
• Triangles
2. Drag the object to the desired location.
• Rotate
• Regular Squares and Rectangles
• Cut
• Rounded Squares and Rectangles How to size or shape an object:
• Copy
• Circles and Ellipses 1. Click on the Selector button from the button bar.
• Paste 2. Select the desired object.
• Chords
3. Drag the sizing points. The arrow will turn into a
• Step Back cross-hair when it approaches the sizing points.
• Pies
• Step Front
• Polygons
• Line Color Text Tool
• Raised Squares and Rectangles Text may be placed anywhere in the graphic by
• Fill Color using the Text tool.

Text Tool
316 Chapter 8:
Graphic Editor

How to place text in a graphic: Lines

Lines may consist of several segments and are
1. Select the Text tool from the button bar. drawn using the line tool.
2. Click where the text is to appear. The Text dialog
box will open.

Line Tool

How to draw lines in the graphic edi-

tor:

1. Select the Line tool.

3. Enter the desired text in the Text dialog box below.
2. Click the left mouse button where the line is to
Set the desired options for the text. When finished,
begin.
click the OK button.
3. Move the mouse to the end of the line segment.
4. Click the left mouse button to create a joint and
begin the next segment.
How to edit text already in the
5. Double click the left mouse button or click the right
graphic: mouse button to end the line.

• Double click on the text.

Please note

Lines can be drawn at 15 degree increments by

holding the shift key while moving the end of a
line segment.
 ProModel 317
User Guide

Arcs Triangle Tool

Arcs are drawn using the Arc tool.

Arc Tool

How to draw an arc in the graphic edi-

tor:
How to draw a triangle in the graphic
1. Select the Arc tool from the Tools window.
editor:
2. Press the left mouse button at one end of the desired
arc. 1. Select the Triangle tool from the Tools button bar.
3. Drag the mouse to the other end of the arc and 2. Press the left mouse button where the center of the
release the left mouse button. base of the triangle is to be located.
3. Drag the mouse until the triangle’s base is the
desired size, but do not release the mouse button.
Please note 4. Press the shift key and move the mouse to adjust the
size of the other two sides. Release the mouse button
To have the arc bow left, start the arc from the top when done.
and drag down. To have the arc bow right, start
the arc from the bottom and drag up.

Triangles
Triangles are drawn using the Triangle tool.
318 Chapter 8:
Graphic Editor

Squares and Rectangles Circles and Ellipses

Squares and rectangles may be drawn using the Circles and ellipses may be drawn using the
regular rectangle tool, the rounded rectangle tool, ellipse tool.
or the raised rectangle tool.

Rectangle

Rounded Rectangle Circle/Ellipse Tool

Raised Rectangle

How to draw an ellipse in the graphic

How to draw a rectangle in the graphic editor:
editor:
1. Select the ellipse tool from the Tools window.
1. Select either the regular, rounded, or raised rectan- 2. Press the left mouse button at one end of the desired
gle tool from the Tools window. ellipse.
2. Press the left mouse button at the top left corner of 3. Drag the mouse to the other end of the ellipse and
the desired rectangle. release.
3. Drag the mouse to the lower right corner of the rect-
angle and release the mouse button.

How to draw a circle in the graphic

editor:
How to draw a square in the graphic
editor: • Hold the shift key while drawing or editing an
ellipse.
• Hold the shift key while drawing or editing a rectan-
gle.
 ProModel 319
User Guide

Chords and Pies 2. Press the left mouse button at the corner of the
“slice.”
Chords and pies are drawn using the Chord tool
3. Drag the mouse to the desired position of the “slice”
and Pie tool.
and release the left mouse button.

Polygons
Polygons are drawn using the Polygon tool.
Chord Tool

Pie Tool

How to draw a chord or pie in the

graphic editor: Polygon Tool

1. Select the chord tool or pie tool from the tools

menu.
2. Press the left mouse button at one end of the desired How to draw a polygon in the graphic
chord or pie.
editor:
3. Drag the mouse to the other end of the chord or pie
and release the left mouse button.
1. Select the Polygon tool from the Tools window.
2. Click the left mouse button to begin the first point
of the polygon.
How to draw a circular chord or pie in 3. Click the left mouse button at each successive point
the graphic editor: of the polygon.
4. Click the right mouse button or double-click the left
• Hold the shift key while drawing a chord or pie. mouse button to end the polygon.

How to adjust the size of the “slice” in Please note

the chord or pie after the graphic has
been drawn: The sides of a polygon may be drawn at 15
degree increments by holding down the shift key
1. Select a corner of the “slice” on the graphic. while moving the mouse to the next vertex.
320 Chapter 8:
Graphic Editor

Positioning Spot entity will use the entity spot defined second, and
so forth. If entity spots are defined for a location
A positioning spot controls the positioning of an graphic in the Locations module, they are used
entity on a location, resource, or path. It also con- ahead of any entity spots defined in the Graphic
trols the positioning of an entity or resource on a Editor. If no entity spot is defined for the location
path. There are two types of positioning spots: graphic, no entity is shown on the location.
entity spots and alignment spots.
Entity Graphics Use only alignment spots. When
Entity spots can be defined for a graphic in either an alignment spot is defined for an entity graphic,
the Graphic Editor or in the Locations module. the entity graphic will be positioned so the align-
Alignment spots can only be defined for a
ment spot of the entity graphic and the entity spot
graphic in the Graphic Editor. In the Graphic Edi-
for the location or resource graphic are aligned. If
tor, the button showing the red circle with the the entity is traveling along a path, the entity
white X represents the positioning spot. The graphic will move along the path with the align-
default type is entity spot. To change the type, the
ment spot and the path segment or node aligned.
user may double click on the spot to display the
If no alignment spot is placed on an entity
Spot Type dialog. This allows the user to define
graphic, the center of the entity graphic is used
the type of positioning spot.
for alignment.
A graphic may have any number of entity spots. Resource Graphics May use both entity spots and
A graphic may also have any number of align- alignment spots. An entity spot on a resource
ment spots. However, only the first alignment graphic may be used to locate an entity a resource
spot defined will be used. An entity or alignment is carrying. An alignment spot can be placed on a
spot is ignored if it is inapplicable for the model resource graphic so that when the resource travels
element it is used to represent. The following def- along a path, the resource graphic will move
initions explain uses of the entity and alignment along the path with the alignment spot and the
spots for locations, entities, and resources. path segment or node aligned. If no alignment
spot is placed on a resource graphic, the center of
Positioning Spot
the graphic is used for alignment.

How to place a positioning spot on an

icon:

1. Select the positioning spot tool from the button bar.

2. Click on the icon where the entity is to appear.

Location Graphics May only use entity spots.

Whenever an entity arrives at the location, the
entity graphic will be placed on the first entity
spot defined for the location. The next arriving
 ProModel 321
User Guide

Status Lights Flip and Rotate

A status light is a circle that changes color Objects may be flipped about the horizontal axis
depending on the status of a location. A status and vertical axis or rotated by 90 degrees using
light can be placed anywhere relative to a loca- the flip and rotation tools from the Tools button
tion to show the status or current state of the loca- bar.
tion. At run time, a window can be displayed
showing what status each color represents. Flip Horizontal

Flip Vertical
Status Light Rotate

How to flip or rotate an object:

How to place a status light on an icon:
1. Select the desired object(s).
1. Select the Status Light tool from the button bar.
2. Click on the Flip Horizontal, Flip Vertical, or Rotate
2. Click on the icon where the status light is to appear. buttons.

Please note Using the flip and rotate buttons is the same as
choosing flip and rotate options under the Graph-
Status lights for location graphics may also be ics menu.
defined in the Locations Editor.
The figure below shows an object that has been
flipped horizontally, vertically, and rotated
through all phases.
Original Flip Horizontal Flip Vertical

Rotate 90 Rotate 180 Rotate 270

322 Chapter 8:
Graphic Editor

Cut, Copy, and Paste Step Back and Step Front

To speed the development of complex graphics, You can move an object behind or in front of
you may cut, copy, and paste objects from one another object. The Step Back option allows you
area of the workspace to another. Each of these to move a selected object behind another object.
buttons works exactly the same as the corre- The Step Front option allows you to move a
sponding item from the Edit menu. selected object in front of another object.
Cut For example, suppose you have five graphic
objects displayed and you want to move the top
Copy object to the third object. You can use the Step
Back or Step Front option.
Paste

How to cut an object:

1. Select the desired object(s) using the Selector.

2. Click the Cut button. The object is removed from How to move an object behind or in
the Edit window but remains in the Graphic Editor’s front of another object:
internal clipboard.
1. Select the object to move using the Selector.
2. Click on the Step Back or Step Front tool from the
button bar.
How to copy an object:
3. Continue to press the Step Back or Step Front but-
ton until the selected object is behind the desired
1. Select the desired object(s) using the Selector.
object.
2. Click the Copy button. The original object remains
on the screen and a copy is placed on the Graphic Edi-
tor’s internal clipboard.
Please note

If you would like to move an object behind or in

How to paste an object:
front of all objects, use the Move to Back or Move
to Front option in the Graphics Menu. Alterna-
1. Click on the Paste button. The contents of the inter-
tively, use the Page Up or Page Down keys.
nal clipboard are pasted next to the last object cut or
copied.
2. Move the new object to the desired location using
the Selector.
 ProModel 323
User Guide

Line and Fill Color formed using the left button unless stated other-
wise).
An object’s line and fill colors can be chosen
using the Line tool and the Fill tool. You may use TO... DO THIS
one of the predefined colors or create your own Select an object. Choose the Selector tool
custom color. Each tool’s color changes accord- and click on the object.
ing to the color chosen. Select multiple Drag in an empty region
objects. until a bounding rectangle
encompasses the objects.
or
Shift+Click on each of the
objects you want selected
(Shift + Click again on a
How to define the line color or fill selected object deselects it).
color: Move one or more Drag the selected object(s).
selected objects.
1. Select the object(s) to change using the Selector. Delete selected Press the Delete key.
2. Click on the Line or Fill tool from the button bar. objects.
or
3. Choose the desired color. The tool will change to
the color specified. Select Cut from the Edit
menu (This method puts
the object on the clipboard
for subsequent pasting).

Please note Copy selected Press the Copy button to

objects. copy the selected objects to
the clipboard. Then press
The line color and fill color can also be defined the Paste button to place a
in the Graphic Editor Options menu. copy of the selected objects
into the Edit window.
or
Choose Copy from the Edit
Editing a Library Graphic menu. Then choose Paste
from the Edit menu.
Various editing functions allow you to alter the Edit text. Double click on the text to
objects that comprise a library graphic. These bring up the text editor dia-
functions may be applied to the entire graphic or log box.
to one of the objects from which the graphic is Change the shape of Drag one of the sizing
constructed. The following is a description of a selected object. points of the selected
object.
how to edit a graphic (All mouse actions are per-
Add a vertex to a Right click on the line or
selected line or poly- polygon where the vertex is
gon. to be added.
Delete a vertex of a Right click on the vertex.
selected line or poly-
gon.
324 Chapter 8:
Graphic Editor

TO... DO THIS TO... DO THIS

Change the fill pattern Choose Fill Patterns from Nudge a selected Press the Right arrow key.
for a selected object. the Graphics menu and object one pixel right.
select the desired pattern. Nudge a selected Press the Up arrow key.
Change the color of a Click on the Line or Fill object one pixel up.
selected object. Color button with one or Nudge a selected Press the Down arrow key.
more objects selected. object one pixel
Change the line style Choose Line Styles from down.
for a selected object. the Graphics menu. Then Size a background Select the graphic, group it,
choose the desired line graphic proportionally. then size using the handles.
style.
Create a perfect circle Select a graphic and, while
Flip or rotate a Click on the flip or rotate but- or square. holding down the shift key,
selected object. ton with one or more objects size the graphic.
selected.
Move a selected Click on the Step Front but-
object in front of ton until the selected object
another object. is in front of the other
objects.
Move the selected Choose Move To Front
object in front of all from the Graphic menu.
other objects.
or
Press the Page Up key.
Move a selected Click on the Step Back but-
object behind another ton until the selected object
object. is behind the other objects.
Move a selected Choose Move To Back from
object behind all other the Graphic menu.
objects.
or
Press the Page Down key.
Nudge a selected Press the Left arrow key.
object one pixel left.
 ProModel 325
User Guide

Options Show shortcut panel at start-up Check this option

to display the shortcut panel at start-up.
Long build menu Allows the user to view the
long build menu.
Recalculate path lengths when adjusted Recalcu-
lates the time or distance of a path network or
conveyor as it is graphically lengthened or short-
ened.

Directories
The Options dialog contains default folders, The Directories section of the Settings dialog
selections for displaying the long build menu, allows you to specify which drives and folders to
defaults for record deletion, and the time between use for storing models, graphic libraries, and out-
auto-saves. put results.

How to change the default folders:

1. Select Options from the Tools menu.

2. Click on the Browse button next to the Folder name
you would like to change.
3. Specify the desired folders for models, graphics
libraries, output results, and auto-save.
4. Click OK.

Default Folders These fields contain the default

Long Build Menu
folders for your model.
The Long Build Menu option reorganizes the
Default File: Graphics Library This field allows
Build menu. The long build menu takes the first
you to specify a default graphic library file for
section of the More Elements submenu and
every new model you create.
places it in the Build menu. This includes
Auto-Save time interval Allows you to select attributes, variables, arrays, macros, and subrou-
how often ProModel will automatically save your tines. Using the long build menu is especially
model. helpful when using these elements frequently.
Confirm record deletion Use this option to have
ProModel display a dialog box confirming that How to display the long menu:
the user wants to delete a record from an edit
table. 1. Choose Options from the Tools menu.
326 Chapter 8:
Options

2. Check the Long build menu option. 2. In the Auto-save field, enter the directory path you
wish to use.
3. Click OK.

Please note

To display the short menu, follow the same proce-

dure above and uncheck the Long build menu
option.

AutoSaving Files
ProModel automatically saves the open model
every few minutes, which is useful in the event of
unforeseen crashes and power outages. ProModel
uses a model file called “AUTOSAVE.MOD” for
all autosaves and only modifies the original file
when Save is chosen from the File menu.

How to specify the amount of time

between AutoSaves:

1. From the Tools menu, select Options.

2. In the Time between autosaves field, enter the
time.
3. Click OK.

Please note

Models are always autosaved at the start of a

simulation run. To deactivate the auto-save fea-
ture, set the time between auto-saves to 0.

How to specify the autosave directory:

1. From the Tools menu, select Options.

 ProModel 327
User Guide

Customize 2. In the Name text box, type the name of the item you
will be referencing, as you want it to appear on the
You can add direct links to applications and files drop menu.
right on your ProModel toolbar. Create a link to 3. Click the Browse button.
open a spreadsheet, a text document, or your
4. Use the browse window to find the file or applica-
favorite calculator–it’s your menu. tion that you wish to have launched, then double click
To create or modify you Custom Tools menu, on it or click Open.
select Customize from the Tools menu. 5. The file or application name and path will appear in
the Source window.

Delete a menu item

1. In the Menu Items list, click on the name of the item

you would like to delete.
2. Click the delete button.

This will pull up the Custom Tools dialog win-

dow. The Custom Tools dialog window allows Edit a menu item
you to add, delete, edit, or rearrange the menu
items that appear on the Tools drop down menu 1. In the menu Items list, click on the name of the item
in ProModel. you would like to edit. Its properties will appear in the
Edit Item panel, on the right.
2. Change the name that appears in the Name text box.
3. To redirect the item to another file or application,
change the path and file name in the Source text box by
either typing in a new source, or using the Browse win-
dow.

Rearrange items on the menu

Three tools come already added to the Custom
Tools menu by default: QuickBar, Models to Go, 1. You can rearrange the order in which menu items
and Model Package Association. These tools can appear on the Tools menu, or add separators to divide
be added to or deleted from the Tools menu. them into logical groups. To move an item up in the
list, select the item you wish to move.
Add a new menu item: 2. Click on the Up or Down button to move the menu
item’s position in the menu list.
1. Click on the New button.
328 Chapter 8:
Power Tools

Add a Separator Power Tools

1. Clicking on the Separator button adds a Separator Packaged with ProModel are several powerful
line to the drop down list. In the Menu Items list, this tools that can help you better use and understand
line is represented as --<Separator>--, in the Tools your ProModel software and the statistical data it
menu it appears as a single solid line. creates. These tools include:
2. The Separator line is inserted into the menu list • ProClare
above the highlighted Menu Item. Its placement can • ProSetter
then be adjusted similar to other menu items, using the
• Shift Library
Up and Down buttons
• ProActiveX
Any of these tools can be added to the custom
Tools menu using the steps outlined in the section
Please note “Add a new menu item:” on page 327.

Custom Tool settings are saved in your Windows

Registry. They are not a part of your model file or
model package. If you have multiple installations
of ProModel Corporation products (such as a
LAN version, MedModel, or ServiceModel) your
Customized Tool menu will be available to your
other ProModel Corporation products as well.
 ProModel 329
User Guide

ProClare Attributes This allows for the addition of new

attributes. The attribute name, type, and value
can also be configured.
Arrays This allows the user to add arrays, with
their corresponding name, dimensions and type.

Options
Select the Options button to customize ProClare
in these additional ways:
Always on Top This option allows ProClare to
always be on top of all other windows, which is
useful if you plan on adding a lot of new items.

ProClare is a quick way to add new variables, Auto Roll-up When enabled, ProClare is
attributes, macros and arrays into your ProModel reduced to just the title bar when the mouse cur-
Corporation product without having to leave sor is outside the window. When the cursor is
where you are in the model building process. inside the window, the window is restored to nor-
This is extremely useful if, for example, you are mal size.
into heavy logic and need to add a new variable.
With this tool you can add the new variable with-
out losing your place.

Tools
Startup Loads the default ProModel Corpora-
tion product for model building and editing. You
can choose to specify a model to be loaded.

Please note

When using the ProClare tools, if no ProModel

Corporation products is currently open, ProClare
will launch the default ProModel Corporation
product for you.

Variables This will allow the addition of new

variables into the model. The name, initial value,
type, and RTI stats can be set here.
330 Chapter 8:
Power Tools

ProSetter reflect whether it is installed, and indicate if it is

the default product.

Locations
When you click on a product, it will populate the
location box with all of the locations to which
that product is installed. The default product
location will have a “(Default)” caption next to it
to indicate that it is the default.

This tool is useful only if you have more than one

ProModel Corporation product installed. This
includes having more than one installation of
ProModel, or having every ProModel Corpora-
tion product installed.
When you start this tool, it will scan all your
hard-drives for ProModel Corporation products
(ServiceModel, ProModel, MedModel, or multi-
ple installations of any one of these). To change
the default product, click which product you want
to be your default. If you have multiple copies of
a product, select which location. Having made
your selection, you must then click the “Make
Default” button to process the change. When you
make a product the default product, it will modify
the registry, indicating to Windows that this prod-
uct is now your default product. It will also reset
your icon cache to reflect the new file associa-
tion.

Products
This tool supports ServiceModel, ProModel and
MedModel. It supports multiple installations of
these products as well.
Each product has 2 labels: Installed and Default.
Both labels say either Yes or No next to them to
 ProModel 331
User Guide

Shift Library ProActiveX

For your convenience, predefined shift files are
now included with your ProModel Corporation Overview
product. When installed they will appear in a The ProActiveX spreadsheet is designed to help
Shift subfolder under the Shift Editor installation you understand how to use ProModel’s ActiveX
folder (i.e. C:\Program Files\ProModel Corpora- components. The worksheets and macros give
tion\Tools\Shift Editor\Shifts\shift_file.sft.) clear and functional examples of how to access
These files have common nomenclature to sim- all currently enabled data elements.
plify the process of identification and implemen- The ProActiveX spreadsheet may be used “as is”
tation of the proper shifts. Each shift file is or modified to suit your specific needs. With Pro-
named in the following fashion: ActiveX and a fundamental knowledge of Visual
####x_####x_#(_###).sft. The first four num- Basic for Applications, you can create custom-
bers tell you what time the shift starts along with ized user interfaces for ProModel–or let our con-
a letter to designate am or pm. The second four sulting division do it for you!
numbers specify what time the shift ends along
with a letter designating am or pm. The third ProActiveX.xls has nineteen data worksheets
number specifies how many days of the week for corresponding to the module with the same name
which there is a shift definition. The numeral 1 in ProModel. Additionally, there is one hidden
means the shift occurs one day out of seven; sheet with data for drop-down lists used on the
seven means the shift is defined for every day of other sheets.
the week; a Monday through Friday schedule
would be represented with the number five. The Please note
last value in brackets is only used when breaks
are defined for the shift. The first of these three ProActiveX is only compatible with Excel 2000
numbers indicates the number of breaks in a day, or newer.
and the next two numbers indicate the cumulative
minutes of those breaks.

Example Worksheets

7a_330p_5_360.sft Drop-down lists, check boxes and text boxes

This file name represents a shift that starts at 7:00 a.m. Many of the worksheets in ProActiveX have
and ends at 3:30 p.m., five days a week. There are three drop-down lists which make it easier to fill in the
breaks defined, one for 15 minutes, one for 30 minutes, required data. In all cases, the value you select
and another for 15 minutes. These breaks add up to a will be inserted into the selected cell or range of
cumulative 60 minutes of break time, represented by
cells. However, the assigned macros do not pre-
360.
vent you from selecting a different column than
the one with the drop-down used.
Using a combo box with a pre-defined list is one
way to ensure consistency in the data. In most
cases, the numeric value of the list selection is
332 Chapter 8:
Power Tools

temporarily recorded on the hidden sheet (named Panes and Sections

Hidden Sheet). On the Simulation Options sheet,
In each worksheet where the data columns go
instead of filling in a cell or range, the value
beyond the right-hand border of a single screen,
shows in the drop-down box itself and the
separate panes have been created and ‘frozen’ to
numeric value is hidden in the cell behind it.
allow you to scroll through the columns without
The Simulation Options sheet also contains sev- moving the column that identifies the record.
eral check boxes and a text box. The values for The title rows have also been frozen, so that the
the check boxes are hidden in the cells behind user can scroll down the sheet without losing
them. The method used for hiding the values is sight of the titles.
simply to make the text color the same as the
In each worksheet, title labels spanning more
background color.
than one column indicate that all the columns
beneath that title pertain to that type of informa-
Not Enabled and Partially Enabled
tion. For example, on the Resources worksheet,
A few of the worksheets have data columns there are several columns for downtime data
defined for methods which have not yet been which have duplicate titles, but different section
implemented in the ProModel Data Object. These labels. In some cases, the labels are used merely
columns have been included to acknowledge that to make the titles easier to read.
these elements were not forgotten when ProAc-
tiveX was created–these data elements will be Controls Sheet
enabled in future releases of ProModel.
The first sheet of the ProActiveX file is the Con-
Shift Editor Button trols Sheet. The options available on this sheet
are described below.
The Shift Assignments worksheet has a button to
the far right labeled Shift Editor. Clicking on this Get (All)
button will show the Shift Editor, just like when
you invoke the menu call from your default Pro- The Get button copies ActiveX enabled data ele-
Model Corporation product. ments from the currently open model to the Pro-
ActiveX spreadsheet.
Browse Button ProModel must be running and a model loaded.
The General Info worksheet has a Browse... but- When all of the data has been copied to the
ton that uses the Microsoft Common Dialog to spreadsheet, a message box will appear saying,
display a file selection window. “Process Complete.”

Comments Build Model

Several worksheets have comments in the cells of The Build Model button copies all ActiveX
the title rows. These comments are included to enabled data elements from the ProActiveX
give you important information about the data spreadsheet to the currently open model.
contained in that column–like limitations or for- ProModel must be running and a model loaded.
matting requirements. When all of the data has been copied to the
model, a message box will appear saying, “Pro-
cess Complete.”
 ProModel 333
User Guide

Save Model in other modules to process each type of data.

The order in which the subroutines are called is
The Save Model button saves all updates to the
important, since many of the modules in Pro-
loaded model. ProModel must already be open
with a model loaded. Model depend on information in other modules.
For example, the Locations module must be built
before the Path Networks module, because the
Run Simulation
Path Networks module references Locations.
The Run Simulation button starts the simulation
for the loaded model. To view the simulation, All of the subroutines in ProActiveX use the con-
you will have to manually select ProModel from stants established in the PM_CONSTANTS mod-
your Windows Task Bar, to bring it forward. ule. You will also find this module recorded in
the file called PM_CONSTANTS.bas. The main
Open ProModel purpose of the constants is to provide a method
for accessing the parameters to the ProModel
The Open ProModel button starts ProModel, but properties and methods data, without having to
does not load a model. remember the numbers associated with each table
and field.
Load Model
There are some other useful subroutines that are
The Load Model button gives the user an opportu- used throughout the program to do things like
nity to specify a model and then open it in Pro- showing the right error message or replacing
Model. If ProModel is not already running, the Excel style carriage returns with ProModel style
Load Model button will start ProModel and then carriage returns.
load the selected model. This button gives you
an example of a custom dialog box. In many cases when you look at the tables in Pro-
Model, what you actually see on the screen is a
main table and one or more sub tables.
Macros
The subroutines in ProActiveX must process the
All of the processing logic for ProActiveX is con-
data for all tables simultaneously by using
tained in Excel macros. In most cases each
For...Next or Do While... loops.
macro is in a separate module. The controlling
modules are named Get_ALL_Model_Data and In many of the data tables, the first field is a
Pop_ALL_Model_Data. There are also macros in Name or ID field that identifies each record in the
some of the Excel Sheet Objects. For example, table and does not allow duplicates. In the sub-
Sheet04 (Resources) has subroutines that dynam- routines that populate these types of tables, the
ically fill in the Path Network drop-down list logic is designed to search for an existing Pro-
(using the information on the Path Networks Model record with the same name or ID. If a
sheet) every time the Resources sheet is acti- record is found, all of its fields will be updated. If
vated. This is one method for keeping the drop- no record is found, a new one will be appended.
down list in sync whenever you update the data. In tables that have no identifying field, records
are always appended.
When the user clicks on the Build All button on
the Controls Sheet, the create_model subroutine is
started (found in the POP__ALL_Model_Data
module). This subroutine then calls subroutines
334 Chapter 8:
Power Tools

ProModel Player After the model has been loaded, the layout win-
dow of the model appears in the main browser
ProModel Player is a browser plug-in for window.
Microsoft’s Internet Explorer that allows users to
view the animation and statistics of a model.

Viewing Simulation Models

To view, or “play,” a simulation model in Win-
dows Internet Explorer, you may:
• Select the model file in Windows Explorer,
then right-click on the package and select
Play from the menu that appears. Three
packages, Semiconductor.pkg, DaySur-
gery.pkg, and TollPlaza.pkg, are installed on
your computer when you install ProModel.
The are found in the following directory:
C:\Program Files\ProModel Corpora-
tion\Tools\PMPlayer.
or,
• View a model via HTML links to the desired
model package. Model links are available
from the ProModel Corporation Web site at Using ProModel Player
www.promodel.com. You cannot open Pro-
Model Player independently of selecting a Simulations in ProModel Player are controlled
model package. through the Toolbar.

When you open a package on your computer, or

click on a package link on the Internet, an Inter-
net Explorer window will open and you will see
the following image in your browser window : Runs the animation.
while the package is loaded:

: Pauses the animation.

: Stops the animation.

: Toggles the Animation on/off. Turning the

animation off increases the speed of the simula-
tion.
 ProModel 335
User Guide

To close the Output window and return to the ani-

:Allows you to zoom in or out on the mation window, click on the red "x" on the tool-
layout. bar.

Please Note
: Toggles the Auto Zoom on/off. When
selected, this option will zoom the animation to
A user who has installed this plug-in, but has not
fit within the browser window.
installed any other ProModel Corporation prod-
ucts will not have access to any of ProModel’s
: Opens an options window, which gives you model building capability, they may only view the
several options for controlling your animation. simulation animation and the statistical output
results. Users who have a valid ProModel Corpo-
ration registration key will have access to Pro-
: Opens this Help file. Model Player Gold, which is described in the
To run the model animation, click ProModel next section.
Player’s play button. If you have selected to view
the output, as soon as the simulation is complete,
the output statistics and graphs will open in the
browser window. Only predefined output graphs ProModel Player Gold
will come up, the user cannot define new graphs If you have a valid registration key on your com-
through ProModel Player. puter for a ProModel Corporation product, Pro-
Model Player will automatically launch
ProModel Player Gold.
The Gold version of ProModel Player is function-
ally similar to the regular version of ProModel
Player, but it contains the added functionality of
scenarios and macros.
ProModel Player Gold allows you to view values
for scenarios that are packaged with any .pkg file.
The scenario viewing area is accessible through
the green bar underneath the ProModel Player
toolbar.

If there are any bar graphs defined, as in the

Semicon report, the user can get a detailed pie
chart of the individual bar by left-clicking on the
bar of the desired statistic.
336 Chapter 8:
Power Tools

Clicking on the arrow on the far left of the green

bar will open the scenario and macro window.

From this window you can select the scenarios

you wish to run, and view the available macros.
 ProModel 337
User Guide

Chapter 9: Running the Model

Simulation Menu replication statistics. (See “Simulation Options”

on page 338.)
All of the run-time controls are accessed through
the Simulation menu located on the menu bar. Model Parameters Choose Model Parameters to
This menu contains options for running a model, open the Model Parameters dialog box. The dia-
specifying multiple replication statistics, defining log box allows you to modify the current settings
scenario data, and other extended run-time for the RTI (Run-Time Interface) parameters
options. defined in the Macros module. (See “Run-Time
Interface” on page 234.)
Scenarios Select Scenarios to open the Scenarios
dialog box. The dialog box allows you to define
different scenarios using defined RTI (Run-Time
Interface) parameters. (See “Scenarios” on
page 343.)
SimRunner SimRunner takes your existing Pro-
Model simulation models, evaluates them for
Each of the selections available on the Simulation you, then performs tests to find better ways to
menu is explained below. achieve the results you desire. (See “SimRunner”
on page 360.)
Run Choose Run to begin simulating the current
model using the options previously selected in
the Simulation Options dialog box. Choosing
Run does not save the models to the current
model file. However, the model data will be
saved to the file AUTOSAVE.MOD. To run sev-
eral scenarios, you must select Run Scenarios
from the Scenarios dialog mentioned below. Oth-
erwise, it will run the RTI default values.
Save & Run Saves the current model, then runs
it.
Options Select Options to bring up the Simula-
tion Options dialog box used to specify important
run-time information such as run length, warm-
up period, number of replications, and multiple
338 Chapter 9:
Simulation Options

Simulation Options General Options & Settings

The Simulations Options dialog provides you Output Path Contains the path of the output file
with a number of options to control the simula- (the name of the file is automatically created
tion, such as run length, warm-up time, clock pre- using the name of the model). ProModel records
cision, and the output. You also control the type all statistical output in this file for your analysis.
of statistics reporting you want from the simula- If this field is left blank, the default path is used,
tion, including period length and number of repli- which points to the Output directory in the Pro-
cations. Model directory.
In addition to reporting standard statistics based When you change the default path, be sure the
on one or more replications of a simulation, Pro- path you enter actually exists, or an error will
Model allows you to average statistics across occur at run time.
intervals of a single replication (batch mean) for
analyzing steady-state systems or take the aver- Define Run Length by ProModel allows you to
age of the average statistics for specific time peri- define a run length for you model based on the
ods over multiple replications (periodic) for non- duration you will test.
steady state systems. You may choose from three • Time Only The total run length in hours.
statistical reporting options.

How to open the simulation options

dialog:

1. Select the Simulation option from the menu bar.

2. Select Options to open the Simulation Options dia-
log.
• Weekly Time The total run length by week,
day, and time.

• Calendar Date The total run length by a spe-

cific calendar date and time.
 ProModel 339
User Guide

The following table shows the default precision

selections based on the time unit selected in the
General Information dialog.

DEFAULT CLOCK PRECISION

SELECTIONS
Clock
TIME UNIT Clock Unit Precision Maximum Run
Seconds (sec) Seconds .01 11,930 hrs
• Warm-up Period The amount of time to run
Minutes (min) Minutes .001 71,582 hrs
the simulation before collecting statistics.
Hours (hr) Hours .001 4,294,967 hrs
Usually this is the amount of time it takes for
Days (day) Hours .001 1,030,792,128 hrs
the model to reach steady state. The warm-
up period uses the same units as the run
length. Disable: Animation Use this option to improve
Clock Precision Select the clock precision value run-time speed by shutting down the animation.
from the drop down box. Then click the radio If you choose to disable animation, you cannot
button for the clock units you want to display at choose the Generate Animation Script option.
run time. Disable Array Exports This option disables the
exporting of data to external arrays. This is help-
ful for skipping the array exporting at the end of
simulation, which may save time if the data being
exported is large.
Disable Cost When you select this option, Pro-
Please note Model disables all cost information collection for
in the model.
The maximum run length depends on the clock
Disable: Time Series Use this option to improve
precision and time unit selected. The following
run-time speed by foregoing time series statistics.
table shows the maximum run hours for each pre-
This also saves disk space used to store the col-
cision setting. lected statistics.
CLOCK PRECISION At Start: Pause To pause the simulation at the
Time Unit .01 .001 .0001 .00001 start of the run, use this option. The simulation
Seconds 11,930 hrs 1,193 hrs 119 hrs 11 hrs will pause until you select Resume from the Sim-
(sec) ulation menu in the Simulation module.
Minutes 715,827 hrs 71,582 hrs 7,158 hrs 715 hrs
(min) At Start: Display Notes Use this option to display
42,949,672 4, 294,967 429,496 42,949 the notes from the General Information dialog at
Hours (hr) hrs hrs hrs hrs the beginning of the simulation.
1,030,792,128 103,079,208 10,307,904 1,030,776
Days (day) hrs hrs hrs hrs General: Adjust for Daylight Saving This option
is only available when you have defined Run
Length by Calendar Date. When checked, the
340 Chapter 9:
Simulation Options

simulation clock will account for the hour shift of General: Skip Resource DTs if Off-shift When
daylight saving time in April and October. checked, the simulation will ingnore resource
downtimes if the resource is off-shift.
General: Generate Animation Script When
checked, the simulation will generate a 3D ani-
mation script for use with ProModel Corpora- Output Reporting Options
tion’s 3D Animator application. The animation
script records the graphical events of the simula-
tion for later 3D rendering in 3D Animator.
General: Common Random Numbers This fea-
ture is a variance reduction technique used prima-
rily when running multiple scenarios, each with
multiple replications. It is intended to help reduce
the number of replications required to determine
the statistical significance of differences between
scenario results. When enabled, common random Standard When you select Standard output
numbers will ensure that the sequence of starting reporting, ProModel collects output statistics for
seed values for each stream in a set of replica- one or more replications. No interval length can
tions for one scenario is identical to the starting be specified when using this option. From the
seed values for corresponding replications in output program, statistics can be viewed for each
every other scenario. replication; although, by default they are dis-
played as an average over all the replications.
For example, if you have this option disabled, the
match between starting seed values for each Batch Mean The method of batch means, or
stream in corresponding replications for each sce- interval batching, is a way to collect independent
nario will not be guaranteed. The net effect of this samples when simulating steady-state systems as
is that you may have to run more replications to an alternative to running multiple replications.
get the same confidence interval that you are able The advantage over running multiple replications
to obtain by running with common random num- is that the warm-up period runs only once. When
bers. you select Batch Mean output reporting, the out-
put statistics are collected for each time interval
When common random numbers are enabled, indicated in the Interval Length field. The num-
you can theoretically establish the statistical sig- ber of intervals is determined by dividing the run
nificance of differences in output results between length by the interval length. The interval length
multiple scenarios with fewer replications than may be an expression but will only be evaluated
by not enabling common random numbers. Spe- once at model translation, so it is always a fixed
cifically, it reduces the amount of variation in dif- interval. The Number of Replications edit field is
ferences between outputs of corresponding not used when this option is selected since it
replications by ensuring that these differences are replaces the need for running multiple replica-
due to true differences in performance and not to tions.
differences due to randomness of the streams.
For more information on random number Example
streams, see “Using Random Number Streams”
on page 258.
 ProModel 341
User Guide

The Content History graph below shows that the con- The content history table below shows how the con-
tents of Lathe1 varied throughout the simulation. The tents of Lathe1 varied throughout the simulation and
interval length was set to 0.5 hours and the simulation from one replication to the other. The interval length
ran a little over 3 intervals (1 1/2 hours). The average was set to 0.5 hours and the simulation ran a little over
or mean of the intervals were 2.7, 3.09, and 3.15, so the 3 periods (11/2 hours) with two replications. The
average of the interval averages is the batch mean or results are shown below.
2.98.
Periodic Period Period Period
Output 1 2 3
Replication 1 2.70 3.09 3.15
Avg.
Replication 2 2.20 3.13 3.01
Avg.
Pooled Average 2.45 3.11 3.08

Interval Length Enter the interval length as the

number of time units for each interval or period.
Periodic Useful primarily in terminating or non- The interval length may be an expression but will
steady state simulations where you are interested only be evaluated once at model translation, so it
in the system behavior during different periods is always a fixed interval. To define unequal
(e.g., peak or lull periods) of activity. intervals, see “Customized Reporting” on
page 342. The time unit is defined in the General
When you select Periodic output reporting, the Information dialog. The interval length need only
output statistics are collected by period where the be specified when using Batch Mean or Periodic
length of a period is defined in the interval length reporting.
field. The interval length may be an expression
but will only be evaluated once at model transla- Number of Replications Enter the number of rep-
tion, so it is always a fixed interval. To define lications you want the simulation to run in this
unequal intervals, see “Customized Reporting” field. Number of replications only needs to be
on page 342. specified when using Standard or Periodic report-
ing.
You may gather statistics for a periodic report
over multiple replications. From the output pro-
gram, you can view each replication averaged Running a Specific Replication
over the periods, each period averaged over the ProModel allows you to run a specific replication
replications, or the pooled average (the average in order to produce time series graphs in the Out-
for each period averaged over all of the replica- put Program. To run a specific replication, enter
tions). the “@” symbol in the “Number of Replications”
box followed by the replication number. For
Example example, “@5” will run only the fifth replication.
342 Chapter 9:
Model Parameters & Scenarios

Customized Reporting Model Parameters & Sce-

For customized reporting, you may want to take narios
advantage of the following statements: REPORT,
RESET STATS, and WARMUP. See “Report” on
page 532, “Reset Stats” on page 535, and “War- Model Parameters
mup” on page 569 for syntax and examples.
The Model Parameters dialog box allows you to
REPORT A general statement called from any modify the current settings for the Run-Time
logic. When the statement is called, a full set of Interface (RTI) parameters defined in the macros
statistics is saved to be viewed as a snapshot module. This provides a convenient interface for
report in the output processor. Optionally, the making model changes without using the Build
statement allows you to reset the statistics after modules. To define and run multiple scenarios
the report is saved, giving you a batch or period using RTI parameters, select the Scenarios option
for any time interval you define. from the Simulation menu (see discussion on
Scenarios later in this section). Model parameter
RESET STATS A general statement called from
settings are saved with the model for future use.
any logic and generally used in connection with
the REPORT statement. When this statement is
used, all statistics are set to zero. The output data-
base is not erased (see WARMUP).
WARMUP A general statement called from any
logic. When this statement is used, all statistics
are set to zero and the output database is erased.
Use this statement in conjunction with the WAIT
UNTIL statement to wait until specific parame-
ters in the system being modeled are at a steady
state or other conditions are appropriate to Parameter The name of the macro defined in the
declare the warm-up period over. model as the RTI (Run-Time Interface) parame-
ter. The parameter name does not need to be the
same name as the macro.
Current Setting The current setting of the param-
eter.
Change Allows you to change the current setting
of the parameter.
Reset All Resets all parameters to the default
RTI setting defined in the Macros module.
Run Runs the model with the defined current
model parameter settings.
 ProModel 343
User Guide

How to define an RTI parameter: Scenarios are saved with the model for future
use.
1. Choose More Elements from the Build menu.
2. Choose Macros...
3. Type the macro name, choose the RTI button, and
select Define.
4. Define the Parameter Name.
5. Enter the Prompt (optional).
6. Select the parameter type, Unrestricted Text or
Numeric Range.
7. If defining a Numeric Range, enter the lower and
upper boundary for the range.
8. Click OK. Add Opens the Scenario Parameters dialog box
9. Use the macro ID in the model (e.g., operation time, to add a scenario.
resource usage time, etc.). Edit Opens the Scenario Parameters dialog box
to edit an existing scenario.
Duplicate Duplicates the selected scenario and
Please note opens the Scenario Parameters dialog box, allow-
ing you to give the newly created scenario a name
For more information on RTI, see “Run-Time and edit its data.
Interface” on page 234. Delete Deletes the selected scenario.

Disable/Enable Disables or enables the selected

scenario.
Scenarios Run Scenarios Runs the model with the defined
scenarios. When running several scenarios, click-
ProModel gives you the option of defining sev-
ing on the Abort button during translation will
eral scenarios for a model using RTI parameters
terminate all scenarios instead of just the current
specified for the model. A scenario is a set of run-
scenario.
time parameters with settings defined by the user.
Using scenarios allows you to alter various model
parameters to run a series of “what-if” scenarios Scenario Parameters Dialog
without changing the model directly. The Scenario Parameters dialog box is displayed
Scenarios can also be helpful for allowing other when choosing Add, Edit, or Duplicate from the
users of you model, who may not have experi-
ence using model logic, to make changes to the
model through RTI parameters.
344 Chapter 9:
Model Parameters & Scenarios

Scenarios dialog box. This allows you to control 4. Double click on the Parameter to bring up the
the specifics of a scenario. parameter dialog box or select the Parameter and click
the Change button.
5. Type the text in the box in the Parameter dialog box.
6. Select OK in the Parameter dialog box.
7. Repeat for every parameter desired.
8. Select OK in the Scenario Parameters dialog box.

Scenario Name The name of the scenario. This

name is chosen by the user and may contain any
alphanumeric characters.
Parameter The name of the parameter as defined
in the RTI (Run-Time Interface) definition dialog
box invoked from the Macro editor.
Current Setting The current setting of the param-
eter.
Change Allows you to change the current setting
of the parameter.
Reset All Resets all parameters to their default
settings.

Please note

Only macros defined as RTI parameters will be

displayed as parameters for the scenario. (See
“Macros” on page 233.)

How to define a scenario:

1. Choose Scenarios... from the Simulation menu.

2. Choose the Add button.
3. Define the scenario name by typing text in the Sce-
nario Name box.
 ProModel 345
User Guide

Running the Simulation Run-Time Menus & Con-

Choosing Run begins the simulation of the cur- trols
rent model. The model is automatically saved in a
file called autosave.mod. Therefore, if the simu- Once a simulation begins, a new menu bar
appears at the top of the screen with selections for
lation is terminated abnormally, ProModel will
controlling and interacting with the simulation.
ask you if you would like to load the latest
As shown below, these menu items appear above
autosave.mod file when you re-open ProModel.
the animation speed control bar and simulation
If you choose Save & Run, the model will be
clock.
saved in the AUTOSAVE.MOD file as well as
the <model name>.mod file.
Once you choose the Run option, a translation
status window appears, showing which data is
currently being translated. This gives you the
option to abort the simulation run at any time. As
shown below, the path networks are being
mapped.

Each of the menu selections and the tools for con-

trolling the animation are described in the
remainder of this chapter.

Abort Allows you to cancel model translation at Run-Time File Menu

any time during translation.
The Run-Time File menu contains only one
Continue Allows you to continue model transla- selection, View Text.
tion when a warning message is displayed.
Detailed Status Allows you to view more spe-
cific information about the data in translation.
View Text Choose this option to bring up a win-
dow with a text listing of the current model. This
feature is extremely useful for debugging and
verifying models.
346 Chapter 9:
Run-Time Menus & Controls

Please note Run-Time Options Menu

The run-time Options menu has several selec-
You may switch back and forth between a full size
tions that allow you to interact with the simula-
View Text window and the animation screen by
tion while the model is running. These options
choosing the desired window from the Window
are described in the following pages.
menu option.

Run-Time Simulation Menu

The Run-Time Simulation menu has two options:
End Simulation and Pause/Resume Simulation.

Animation Off/On Turns the animation on or off.

Off greatly speeds up the simulation. Animation
End Simulation Choose this option to end the speed may also be set with the ANIMATE state-
simulation. You will then be prompted to collect ment. (See “Animate” on page 432 for informa-
statistics or return to the model editor without tion).
collecting statistics. If running multiple scenar- Zoom Zooms in or out on the animation.
ios, End Simulation will terminate all scenarios.
Views Allows you to select a view, which you
Pause/Resume Simulation Choose Pause Simula- have defined while building the model. This
tion to pause the simulation for an indefinite option is only available if you have previously
amount of time. With the simulation paused, you defined a view.
may begin a trace, zoom in or out, set up the next
pause, examine different locations in the model, Trace Options Lists events as they happen dur-
or interact with the model in a number of other ing a simulation. This listing may be Step by
ways. Choose Resume Simulation when the sim- Step, Continuous, or Filtered.
ulation is paused to continue running the simula- Debug Brings up the Debugger Options Dialog
tion. box for debugging the model.
User Pause Allows the user to enter a simulation
clock time for the simulation to pause.
User Pause by Date/Time Allows the user to enter
a calendar date and simulation clock time for the
simulation to pause. This option is only available
if you chose "Calendar Date" as the Run Length
in the Simulation Options dialog.
 ProModel 347
User Guide

Debug Option Please note

Debugging ProModel Logic Even though several threads can execute the
same logic at the same time in the simulation, the
The Debugger is a convenient and efficient way simulation processor can only process them one
to test or follow the processing of any logic at a time. So there is really only one current
defined in your model. The debugger is used to thread while all other threads are suspended
step through logic one statement at a time and (either scheduled for some future simulation time,
examine variables and attributes while a model is or waiting to be executed after the current thread
running. at the same simulation instant).
Before discussing the details of the Debug
option, it is important to understand the following
terms:
Example
Statement A statement causes ProModel to take
some action or perform some operation. This To better explain the above concepts, consider the fol-
includes statements such as GET, JOIN, and lowing operation logic for a multi-capacity location.
SPLIT AS. (See “Statements and Functions” on
page 429 for more information).
Line of
Logic Logic refers to the complete set of state- execution
ments defined for a particular process record, for Thread 3
downtime event, initialization logic, or termina-
tion logic for a simulation. Line of
execution
Thread A thread is a specific execution of any for Thread 2
logic. A thread is initiated whenever a logic
Line of
needs to be executed. This can be an entity run- execution
ning through an operation logic, the initialization for Thread 1
logic, a resource running a node logic, a down-
time logic, or any other logic. Note that the same
logic may be running in several threads at the Logic
same time. For example, three entities of the
same type being processed simultaneously at the The logic includes all statements shown on previous
same multi-capacity location would constitute page. Let’s assume that there are three different entities
three threads. currently executing this operation logic. Each execut-
ing entity constitutes a thread. A possible scenario for
A thread or logic execution can be suspended by this case is the following: Thread 1 is an entity using
any statement, causing simulation time to pass two units of resource Oper_3 for N(35,5) minutes.
(e.g., GET Res1, WAIT 5, etc.). After such a Thread 2 is an entity waiting for resource Oper_1 to
statement completes its task, the thread is become available. The last thread is a different entity
resumed. During the time a thread is suspended, which has completed 10 minutes of the 15 minute wait
other threads may be initiated, suspended, executed at the beginning of the logic. Note that two
resumed, or completed. This is called thread entities arriving at a multi-capacity location at nearly
switching.
348 Chapter 9:
Run-Time Menus & Controls

the same time could both execute the same WAIT or Debugger Options Dialog Box
USE time in the logic, only in different threads.
The Debugger Options dialog box allows the user
to specify when to display the Debugger dialog
box during the simulation run.
In general, for a logic block containing state-
ments that pass simulation time, any number of
threads can wait for the required simulation time
to elapse, corresponding to each time elapsing
statement. These threads are scheduled to resume
at some future simulation time.
There can also be many threads (any number of
threads corresponding to each of the time elaps-
ing statements within the logic) which have com-
pleted their waiting time, but await their turn to
continue execution. These threads are on hold
because the simulation engine is busy with
another thread scheduled for the same simulation
time. There is only one thread executed at any
Disable debugger Disables the debugger com-
real time instant by the simulation engine.
pletely. By default the debugger is enabled. Run-
The debugger window will display a unique iden- ning the model with the debugger disabled
tification number for the current, active thread. increases the run speed. When running multiple
This thread ID number will help you differentiate replications or scenarios, or when the animation
between different instances of the same logic is disabled, the debugger will automatically be
block while you are debugging your models. disabled.
DEBUG statement Displays the Debugger dialog
box every time a DEBUG statement is encoun-
tered in an enabled process while running the
simulation. See “Debug” on page 455 for more
information.
Global Change Displays the Debugger dialog
box every time a global change occurs to a speci-
fied variable or array. The Debugger dialog box
shows the original and new value of the element.
Only one global name can be specified in this
box.
User Condition Displays the Debugger dialog
box when a defined user condition written as a
Boolean expression becomes true, for example,
when Var1=5. Only one expression can be speci-
fied in this box, although several conditions can
 ProModel 349
User Guide

be tested by using the OR operator. See “Boolean Context Box Error Dialog Box
Expressions” on page 400 for more information.
Check Condition Allows the user to define how
often to check the user condition. The options
include:
• Before each statement The condition, such as
Var1=1, will be checked before each state-
ment is executed. This option is the most
precise way to tell exactly when the user
condition becomes true, but it slows down
the simulation the most.
• At each thread switch The condition, such as
Var3>17, will be checked only if a state-
ment from a different thread follows the
current statement being executed.
• At each thread initiation The condition, such Logic Display Box Information Box
as Att1=5, will be checked only if the next
statement to be executed is the first state- Error Display Box Displays the error message or
ment in a thread (the first statement in a reason why the Debugger dialog box is dis-
thread is also the first statement of a logic). played, such as the User-Condition becoming
true.
Debug button Pressing the Debug button dis-
plays the Debugger dialog box before the next Logic Display Box Displays the statements of
statement executes. the current logic being executed.
OK Closes the Debugger Options dialog box Context Box Displays the module, operation, and
and continues to run the simulation model. line number (in which the debugger stopped) in
the Information box.
Debugger Dialog Box Information Box Displays local variables and
The Debugger can be used in two modes: Basic entity attributes with non-zero values in the Infor-
and Advanced. The Basic Debugger appears ini- mation box.
tially with the option of using the Advanced End Simulation Choose this option to terminate
Debugger. The Basic Debugger dialog box is the simulation. This will prompt you about col-
shown below: lecting statistics.
Run Continues to run the simulation, but still
checks the debugger options selected in the
Debugger Options dialog box.
Next Statement Jumps to the next statement in
the current thread. If the last statement executed
suspends the thread (e.g., the entity is waiting to
capture a resource), another thread meeting the
350 Chapter 9:
Run-Time Menus & Controls

debugger conditions may be displayed as the next tionality as the Next Thread button in the Basic
statement. debugger.
Next Thread Brings up the Debugger at the next New (Thread) Jumps to the next initiated thread.
initiated or resumed thread.
Disable (Thread) Temporarily disables the
Into Subroutine Steps to the first statement in the debugger for the current thread (see also enable).
next subroutine executed by this thread. Again, if
Exclusive (Thread) The debugger displays the
the last statement executed suspends the thread,
statements executed within the current thread
another thread meeting debugger conditions may
only. When the thread terminates, the exclusive
be displayed first. If no subroutine is found in the
setting is removed.
current thread, a message is displayed in the
Error Display box. Next (Logic) Jumps to the next initiated or
resumed thread that is not executing the same
Options Brings up the Debugger Options dialog
logic as the current thread.
box. You may also bring up this dialog box from
the Simulation menu. New (Logic) Jumps over any resumed threads to
the next initiated thread not executing the same
Advanced Changes the Debugger to Advanced
logic as the current thread.
mode, provides additional options discussed next.
Disable (Logic) Temporarily disables the debug-
Advanced Debugger Dialog Box ger for all threads executing the current logic (see
also enable).
The Advanced Debugger contains all options in
the Basic Debugger plus a few advanced features. Exclusive (Logic) The debugger displays only the
statements executed in any thread executing the
current logic.
Enable disabled threads and logics Enables the
threads and logics which were disabled previ-
ously.

Debugger Options Examples

Debug Statement Example

A simulation model demonstrates a proposed
flexible manufacturing system which produces
castings. A variable, WIP, is used to track the
work in process for the system. Suppose we want
to display the Debugger when the variable, WIP,
reaches a value of 300. We could place an
IF...THEN statement including DEBUG after the
Next (Thread) Jumps to the next initiated or
resumed thread. This button has the same func-
 ProModel 351
User Guide

statement incrementing the variable, WIP, as Debugger syntax

shown below:
Casting @ loc1: GET Oper_1
WAIT N(5,3)
INC Var1
Casting @ loc2: JOIN 1 Fixture
...
...
...

By checking the box next to the DEBUG state-

ment in the Debugger Options dialog, the Debug-
ger is displayed when the variable, WIP, reaches Trace Options
300.
A trace is a list of events occurring over the
Global Change Example course of a simulation. For example, a trace
statement might state “EntA arrives at Loc1,
Suppose we want to know when the variable,
Downtime for Res1 begins.” A trace listing also
COUNT, is incremented. We would check the
displays assignments, such as variable and array
box to the left of Global Change and type
element assignments. A trace listing of a simula-
COUNT in the Global Change field. This will
tion run may be viewed in several ways through
display the Debugger dialog box each time
the trace options provided.
COUNT changes. It will also display the previ-
ous and changed value of COUNT.
Trace Mode
User Condition Example A trace listing is generated in one of three modes,
Suppose we want to follow a casting through the Step, Continuous, or Filtered.
entire system (i.e., from when an entity enters the
system to when it exits). We would set an Trace Off
attribute equal to a unique number in the arrival Select this option to discontinue a current trace.
logic for a single casting (Att1=3). In other
words, only one casting in the system should Trace Step
have Att1=3. We would then check the User Con-
dition box and enter the condition as “Att1=3.” Select this option to step through the trace listing
We would then select At Each Thread Initiation one event at a time. Each time you click the left
as the Check Condition. The debugger is dis- mouse button, the trace will advance one event.
played each time a particular customer initiates a Clicking and holding the right mouse button
new thread. For example, the debugger may dis- while in this mode generates a continuous trace.
play the following information:
352 Chapter 9:
Run-Time Menus & Controls

Trace Continuous
Select this option to write the trace continuously
to the output device selected from the Trace Out-
put submenu. This is useful when you do not
know exactly where to begin or end the trace.
Clicking and holding the right mouse button
stops the trace until you release the button.

Filtered Trace...
When you view the Trace during simulation, you
see a list of all the events that occur as your
model is running.
Although it may be helpful to view every event in
the simulation, there are many times when you
will want to focus on just the events that affect
specific elements (locations, resources, variables,
etc.) of your model.
The Trace feature contains an optional, custom
filter, which allows you to pick the elements of
your model, or custom text string, that you wish
to view in the Trace window.

From the Custom Trace Options dialog, you may

choose which elements of your model you want
displayed in the Trace window.
The Custom Filter works by showing the speci-
fied elements in the trace according to the follow-
ing:
• Specified elements found in the main head-
ing of the Trace will be displayed along with
the entire contents of the sub-headings.
• Specified elements found in a sub-heading
will only display the main heading and the
sub-heading with the specified element. All
other sub-headings of the main heading,
which do not contain the specified elements,
will not be displayed.
 ProModel 353
User Guide

The Enable button in the Custom Trace Options window, the zoom function will automatically
dialog must be checked for the Trace Filter to pan to show at least part of the layout.
take effect.

Output to File
Select this option to send the trace listing to a text
file. Trace statements are automatically written to
a <model name>.TRC file.

Animation Options
In addition to the debug and trace options, anima-
tion options allow you to control the animation
To zoom in a specific area of the simulation lay-
screen.
out, press and hold the CTRL key, then click and
Animation Off Choose this option to temporarily drag the mouse to create a rectangle around the
suspend the animation. To resume the animation, are in which you would like to zoom. Release the
select this option again. (The selection automati- mouse, then the CTRL key. The layout will zoom
cally changes to “Animation On.”) Note that run- in on the selected area.
ning with animation off greatly increases the run
Views Click on this menu item to display the
speed, especially for models with a large amount
available views. Select the desired view.
of graphic detail. To increase the run speed to an
even faster rate, check the Disable Animation in User Pause Choose this option to enter a time for
the Simulation Options before running the model the simulation to pause. The proper format for
(see “Animation Options” on page 353). specifying a user pause is hh:mm:xx where hh
represents hours, mm represents minutes, and xx
Zoom Select this option to Zoom in or out on the
represents hundredths of a minute.
animation. When this option is selected, you may
choose a preset zoom level, enter your own zoom
level, or choose Zoom Full to fit the entire anima- Run-Time Information Menu
tion on one screen. The Zoom function zooms to
the center of the screen. If the zoom factor causes The Run-Time Information menu allows you to
the model layout to appear outside the layout see the status of locations in two different ways.
In addition, you may view the current state of all
variables and array elements. Each of these
options is defined in the following pages.
354 Chapter 9:
Run-Time Menus & Controls

Status Light Select this option to bring up the changes for those metrics dynamically as the
Status Light Legend. model runs. Configurations of one or more plot
windows can be saved and later retrieved to
Locations Select this option and choose a loca-
quickly view a customized set of graphs.
tion to view an information box with real time
information about the location. Information for Features include:
all locations may also be displayed.
• Up to six elements many be graphed on the
Variables Select this option to show the current same chart at the same time.
state of all real and integer global variables. • More than one chart may be active at a time.
Arrays Select this option to show the current • Charts can be resized.
value of all cells for arrays of up to three dimen- • Plots display a meaningful scale for both
sions. axes.
• Improved customization for graph appear-
Dynamic Plots Allows you to graphically monitor ance
the performance of model elements during run
• Chart settings may be saved to use over from
time and store statistical data in an Excel® spread-
one simulation run to the next.
sheet.
• Dynamic plots work with multiple replica-
tions and scenarios.
Location Status Legend
The Location Status Legend shows the different Basic Operation
colors of a location status light and the meaning
of each color. Single capacity locations may be in Please note
any of several states, while multi-capacity loca-
tions appear only as up or down. This window
The Dynamic Plot dialog is only accessible dur-
may remain open during the simulation.
ing simulation run-time. If you will be creating
saved chart views, you may wish to pause the
simulation, define Chart views, then resume the
simulation.

Starting Dynamic Plots

Dynamic plots are set up using the Information |
Dynamic Plots menu during simulation. Under

Dynamic Plots
Dynamic plots allow you to select certain metrics
for various model elements and observe value
 ProModel 355
User Guide

Dynamic Plots you will find two sub-items, New keyboards. When a subtree is fully expanded,
and Configurations… individual plottable items are shown, as below:

New opens a window similar to the one below.

Each plottable item displays a checkbox to its

left. When checked, the item is added to the list
of currently plotted items below the tree view and
the chart view begins to plot the value of the
item. When unchecked, the item is removed
from the list of currently plotted items, and the
item is removed from the chart view. Items can
also be added or removed from the chart view by
double-clicking the item. If the item was not
checked, this will check the box next to the item,
Setting up a Plot
add it to the current item list and the chart view,
and switch immediately to the chart display. If
Tree View
the item was checked, this will uncheck the box
The tree view represents a hierarchical list of all next to the item, remove it from the current item
plottable items in the model. Expanding and col- list and the chart view, and switch immediately to
lapsing of tree items works in a manner consis- the chart display.
tent with standard Windows tree controls,
including, but not necessarily limited to, double- The maximum number of statistics that can be
clicking on a parent item, clicking on plus or plotted on a single chart is six. When six items
minus graphic next to a parent item, and using the are being charted and you attempt to add an addi-
plus and minus keys on the number pad of most tional item by either clicking the box next to the
item or by double-clicking the item, nothing will
happen and no changes to the chart will take
place.

Statistic List
The item list below the tree view contains the
items currently being graphed, arranged into two
columns: a label and a statistic name. The label
356 Chapter 9:
Run-Time Menus & Controls

initially consists of only the text directly right of horizontal gridlines, and a chart title. An exam-
the item icon in the tree view, while the statistic ple of a chart view is shown below.
name is composed of the names of the items
ancestor nodes and the name of the item node
itself. For example, for the "Avg Min per Entry"
item under the Input location, the label would ini-
tially be set to "Avg Min per Entry" and the sta-
tistic name would be "Locations\Input\Avg Min
per Entry."

Please note

When you click on the Label portion of the item in

the list to select it and then click again, the label
becomes editable, and you can type over or edit
the existing text. This text becomes the new label The x-axis indicates time elapsed from the start
for the item, and will now be displayed in the leg- of the simulation, measured in clock precision
end in the chart view. units specified in the Simulation Options dialog.
The y-axis measures values of the items being
plotted. Both axes are re-scaled when necessary
so that all data points fit within the chart area.
The Remove button removes the selected item, if When in the chart view, the maximize button in
any, from the list, unchecks it in the tree view, the title bar expands the chart itself to completely
and removes it from the chart view. Clicking the fill the area within the dialog, removing the “Stats
Clear button does this for every item in the statis- to Plot” and “Chart” tabs and extra spacing. This
tic list. may be helpful when you want to size the chart
Clicking the dividing lines between headings and window as small as possible and still view the
dragging left or right resizes the columns in the chart update. Clicking the minimize button will
statistic list. restore the chart to its normal state. The items
being plotted are color-coded and the key is on
Chart View the right-hand side of the window. Many of the
chart options such as title and colors are customi-
The chart view is where graphical representations zable; simply click the right mouse button and
of changing model elements are displayed. It select Properties… from the context sensitive
consists of a chart area and, optionally, any com- menu options.
bination of the following: toolbar, legend, x- and
y-axis scales, x- and y-axis labels, vertical and Dynamic Plot Configurations
Information | Dynamic Plots | Configurations... is
disabled if no saved configurations exist for the
model and no dynamic plot windows are open. If
enabled, selecting it opens a dialog box like the
one below. The dialog box consists of a list box
 ProModel 357
User Guide

containing the names of any saved dynamic plot with the name specified in the edit field. If the
configurations for the model, an edit field, and name matches one of the configurations in the
Load, Rename, Delete, Save, and Exit button. configuration list, this data will replace the previ-
ous data for that name.
The Save button does not actually save data into
the model file. Rather, it creates or modifies a set
of configuration data associated with a particular
configuration name in memory and tags the
model as being modified. If you exit the pro-
gram, load a model, or execute the New com-
mand from the File menu you will be prompted to
save the model. Using the Delete or Rename but-
tons in the configuration dialog also tags the
model as modified.

Advanced Operation
If you select a configuration from the list and
To enhance your simulations and presentations
click Load, the indicated saved configuration of
you can turn your dynamic plots on and off using
chart(s) will be loaded, with all of the previous
the DynPlot “” statement in your model logic.
settings as far as selected data items, chart style,
Predefine the statistics to be graphed and a chart
colors, fonts, visible elements, screen position
name, then open your plot through subroutines or
and size, etc. If any of the previously selected
processing logic.
data items no longer exist in the model, they will
simply not be displayed. For example, if a statis-
tic had been selected for a location that was later
deleted from the model, it will no longer be
selected.
Double-clicking on a configuration in the list has
the same effect as selecting it and clicking the
Load button.

The Delete button removes the selected configu-

ration from the list and deletes the associated data
from the model.
The Rename button changes the name of the cur-
rently selected configuration to the text in the
Save/Rename As edit field.

Clicking the Save button saves all settings of any

open dynamic plot windows, including selected
data items, chart style, colors, fonts, visible ele-
ments, screen position and size to a configuration
358 Chapter 9:
Run-Time Menus & Controls

Run-Time Window Menu subroutines are defined in the Subroutines edit

table (see “Subroutine Editor” on page 238).
The Run-Time Window menu allows you to rear-
range windows and icons and select the active
window. These functions are standard to all Win-
dows applications.

Tile Causes all open windows to fit in the avail-

able screen space. Windows hidden behind other
windows become visible.
Cascade Causes all open windows to overlap
such that the title bar of each window is visible.
Arrange Icons Causes all icons representing
How to execute an interactive subrou-
iconized applications or windows to be arranged tine during run-time:
neatly along the bottom of the screen.
1. Select Interact from the run-time menu.
2. Select the identifier for the subroutine from the list
Run-Time Interact Menu box in the Interact dialog box.
The Run-Time Interact menu displays the Inter- 3. Choose the Activate button.
act dialog box. It allows you to execute interac-
tive subroutines during run-time. Interactive

Run-Time Help Menu

The Run-Time Help menu contains selections for
accessing the ProModel on-line help system. It
operates the same here as in the model editing
functions.

Index... Choose this option to bring up the Main

Help Index.
 ProModel 359
User Guide

Context Choose this option to go directly to the How to control the simulation speed:
help screen that corresponds to the active win-
dow. If no context sensitive help exists for the • Move the animation speed control bar to the left to
active window, the Main Help Index will appear. decrease the simulation speed or to the right to increase
the simulation speed.
About... Choose the option to display a message
containing software version information.
Slower Faster
Run-Time Controls
In addition to the animation options discussed in
the previous section, you may pan the animation
screen in any direction, control the speed of the
simulation, and change the format of the simula-
tion clock display. These and other procedures
are discussed in this section.

How to pan through the animation:

1. Press and hold the left mouse button anywhere on

the animation screen. This point then becomes the
“anchor point” by which the entire animation is
moved. Please note
2. Drag and release the mouse where you desire the
anchor point to be located. The following diagram The speed of the animation may be altered by
illustrates this procedure.
model logic with the use of the ANIMATE state-
ment (See “Animate” on page 432).

Desired Location
How to change the format of the simu-
lation clock display:

1. Click on the simulation clock button.

Anchor
360 Chapter 9:
Run-Time Menus & Controls

2. Select a format for the clock display. • Pause/Resume Simulation Allows you to
toggle the simulation’s pause on and off.
• Trace Options Lists events as they happen
during a simulation. This listing may be Step
by Step, Continuous, or Filtered.
• Dynamic Plots Opens the Dynamic Plots
window.

Please note

Right clicking to bring up the right-click menu

will pause the simulation as long as the right-
click menu is open.
How to identify any location on the
layout during the simulation:

• Click on a location while holding the CTRL key. (An SimRunner

identifier box appears and allows you to bring up the
location information window for that location.) SimRunner takes your existing ProModel simula-
tion models, evaluates them for you, then per-
forms tests to find better ways to achieve the
results you desire. Typically, most people use
Run-Time Right-Click Menu simulation tools to predict and improve a sys-
tem’s performance by modeling the actual loca-
Right clicking in the simulation window will tion (e.g., a plant floor, a bank lobby, or
bring up a right-click menu, which gives you emergency room) or abstract process (i.e., a logi-
easy access to several animation controls. cal process). Through testing various “what-if”
scenarios, SimRunner can help you determine the
most ideal way to conduct operations—we call
this optimization.
When you conduct an analysis using SimRunner,
you build and run projects. With each project,
SimRunner runs sophisticated optimization algo-
rithms on your model to help you optimize multi-
• Animation Off Turns off the animation, ple factors simultaneously. For each project, you
which makes the simulation run faster. will need to provide SimRunner with a model to
analyze or optimize, identify which input factors
• Zooms Allows you to choose a level of
to change, and define how to measure system
zoom.
performance using an objective function. Sim-
• Views Allows you to choose a view that
Runner can conduct two types of tests: Pre-Anal-
you have previously defined. See “Views”
ysis (Statistical Advantage) and Simulation
on page 77 for information on defining
Optimization.
views.
 ProModel 361
User Guide

SimRunner Benefits Please note

Using SimRunner will help you find accurate
solutions for your modeling needs. No longer SimRunner will optimize only single value RTI
must you sit and experiment with what you think macros.
might work, only to find that your solution actu-
ally interferes with productivity in other parts of
the model. SimRunner will help you locate true
solutions by monitoring how changes affect each How to define the objective function
part of the model. In other words, SimRunner (output variables):
will not let you improve one area of your model
at the expense of another—the results you get are 1. Click the Outputs button.
beneficial to the entire model.
2. In the Objective Function Setup dialog, select the
category of the item(s) you wish to minimize or maxi-
Starting a New Project mize.
The following describes how to start and prepare 3. Highlight an item in the list.
a project for analysis. Remember that you must 4. Select Maximize, Minimize, or Custom to select
create and validate your model prior to analyzing the type of optimization you wish to use for the vari-
or optimizing it in SimRunner. able.
5. Enter the Weighting. This number represents the
How to select a model: importance of Maximizing or Minimizing the item.
(The higher the number, the higher the importance.)
1. Click the New button on the button bar or select 6. After you set the values for the item, click the right
New Project from the File menu. arrow to place the item in the selected list. To remove
2. From the Open dialog, select the model file you an item from the selected list, select the item and click
wish to use. the left arrow. (Alternatively, you may double click on
an item to add it to or remove it from the list of
3. Click OK. selected variables.)
4. Once you select a model, the model’s name will
appear in the Project Information dialog.

Stage one: Pre-Analysis

With the model built, the input factors selected,
How to define the input factors: and an objective function defined, you are ready
to conduct a Pre-Analysis. Also known as Statis-
1. Click on the Inputs button. tical Advantage, the Pre-Analysis runs several
2. To select input variables, click next to each variable tests to identify the initial bias (warm-up period),
in the Selected column. SimRunner will mark the determine appropriate run-length to reach steady-
selected items. state, find the number of replications necessary to
ensure that each event occurs at least once, and
locate the model averages.
362 Chapter 9:
Run-Time Menus & Controls

Stage two: Simulation Optimization

Simulation Optimization is a multi-variable opti-
mization that tries different combinations of input
factors to arrive at the combination that provides
the best objective function (output) value.
Depending on the number of selected input fac-
tors and the complexity of the solution space, this
process can take a long or short time. Optimiza-
tions with many factors and complex solutions
take longer to run.

How to run an optimization:

1. Click on the Optimize! button or select Start Opti-

mization from the Project menu.
2. Click Play on the dashboard to begin.
 ProModel 363
User Guide

Chapter 10: Reports and

Graphs

Once your model has been built, and the simulation run, you are ready to begin making important deci-
sions about your real-world process based on your simulation’s data. To help you make the most of the
data collected during simulation, ProModel comes with a powerful, easy-to-use Output Viewer 3DR.
This Output Viewer 3DR allows you to view your date numerically, in spreadsheet format, or graphi-
cally in a variety of charts.
364 Chapter 10:
Output Viewer 3DR

Output Viewer 3DR Data sets can also be printed using the print
options in this menu.
Output Viewer 3DR organizes and displays the
data gathered during your model’s simulation.
View Menu
You can open Output Viewer 3DR from Pro-
Model or from the Window’s Start menu in the The View menu lets you specify how you want
ProModel program group. the data displayed.
Output Viewer 3DR’s Menu bar and Toolbar give
you the controls necessary to create the reports
and charts needed to help interpret your data.

Menu Bar
The Menu bar contains all of the tools necessary
to view your simulation’s data. The Menu bar is
located just beneath the Output Viewer 3DR cap-
tion bar, and allows access to the following
menus: Reports and Charts
The first five selections in the View menu display
File Menu the output data in different ways:
The File menu allows you to open and close data • Report Spreadsheets of the data collected
files, export data, and print data. during the simulation. see “Creating
Reports” on page 372.
• Category Charts Bar charts of your data.
see “Category Chart” on page 381.
• State Charts Stacked bar charts of state
variables such as location and resource
states. see “State Chart” on page 382.
• Histogram Displays graphically the fre-
quency of occurrences of time plot data. see
“Histogram” on page 384.
• Time Plot Shows variables, states and
events over time. see “Selection Window” on
Output Viewer 3DR opens files with the .idb page 386.
extension; however, .rdb files, which are gener-
ated by ProModel can be converted to .idb files Sheet/Chart Properties
when they are opened using Output Viewer 3DR. The title of the last option in the View menu will
Data can be exported to a .csv (comma-delim- vary between Sheet Properties and Chart Proper-
ited) file using the Export Data option. This ties, depending on whether a spreadsheet report
allows you to later import the data into other data or graphical chart is currently displayed. This
viewing programs, such as Excel selection brings up a window where you can
 ProModel 365
User Guide

choose the data you want to appear in the open and max, standard deviation, and various
report or chart. confidence interval information for the repli-
cations.
Sheet Properties - Display Items
If you choose Sheet Properties while you are Please note
working with a Report, the following window
appears. The default Display Items Tab is If you are working with a database that does not
described below. contain multiple replications, the Additional
Records field of the Sheet Properties window is
not applicable, and therefore not accessible.

Sheet Properties - Columns

The “Columns” tab for Sheet properties is
described below.

• Display gridlines with this desired

color: When this box is checked gridlines
will appear in the data sheet in the selected
color. Unchecking this box will hide all grid
lines for the data sheet.
Display header with desired settings: When this
box is checked the header will appear with the font
styles selected when you click the Font & Color but-
ton. If you uncheck this box, no heading will be dis-
played above the sheet. • Columns: You may choose to show or hide
• Caption: The text displayed in the sheet columns by checking or unchecking the
heading. The default caption uses the follow- boxes in this list. The available columns in
ing construct: [model name] ([scenario this list will vary depending on the sheet you
name] - [replication information]). have selected.
• Additional Records: The options in this • Column Headers: Choose the font styles of
area allow you to display additional replica- the column headers.
tion information, which includes: the min
366 Chapter 10:
Output Viewer 3DR

• Non-scrolling columns from the left: Use A view describes the way a report or chart
this column to lock columns in place as you appears. For instance, you may choose to create a
scroll horizontally through your sheet data. category chart as explained on page 381.
For example, entering “1” in this field will
lock the left-most column in place, so that it
will not scroll with the rest of the sheet’s col-
umns.
• Display time values in: By default, time val-
ues are shown is hours, but you may choose
to have time units shown in seconds, min-
utes, hours, days, or weeks.

Chart Properties
The Chart Properties dialog will vary depending
on what type of chart you choose to view proper-
ties for. See each chart type description (begin-
ning with “Category Chart” on page 381) for
more information on the options available from
its Chart Properties dialog.
That chart may then be customized using the
Tools Menu tools in the Chart toolbar, page 379, and the right-
click menu, page 369.
The Tools menu allows access to the View Man-
ager and Output Viewer 3DR options.

View Manager
The View Manager allows you to save custom-
In the example shown, the fonts, coloring and
ized report and chart views for quick retrieval.
window size were changed, but the data remains
The View Manager is great for creating custom
the same.
presentations. Views are associated with the
model, so the next time the model is run the same
view appears.
 ProModel 367
User Guide

This particular customized view of the chart can How to Save a Customized View
be saved using the View Manager.
1. Open a report or chart window. See “Reports and
Charts” on page 364 for a list of possible reports and
charts.
2. Customize the report or chart as desired using the
tools in the Chart toolbar, page 379, and the right-click
menu, page 369.
3. Open the Views Manager by clicking on the
tool in the Output Viewer 3DR toolbar, or selecting
View Manager from the Tools menu.
4. Click the New Icon, , in the View Manager and
give the view a name.
5. Click OK to save your new view.

The View Manager contains a field with the

names of your views and the following tools:
Next/Previous View
• : Creates and saves a new view based
on the report or chart you currently The Next/Previous View options in the Tools
have selected in the Output Viewer menu allows you to scroll through the views you
3DR. have saved in the View Manager.

• : Saves a view after you have modified Set as Default Style

it.
This option allows you to set the characteristics
• : Deletes the view you have selected in of a report or chart as your default style. This is
the View Manager. helpful, for instance, if you customize the color
scheme of a chart, and want it to apply to all the
• : Renames a selected view.
charts you open.
• , : Moves the name of a selected Setting a default style is different from saving a
view up or down within the list in the view, which will only save color and font
View Manager. This is helpful for cre- changes for just one report or graph.
ating an ordered list of customized If a report or chart is selected when you choose
views. The first view in the list is the the Set as Default Style option, all of the font and
initial view displayed after rerunning color changes you have made to the selected
the model again and opening the Out- report or chart will be applied to any new reports
put Viewer 3DR. or charts you open.
The default style settings can be restored from the
Options window described next.
368 Chapter 10:
Output Viewer 3DR

Options 3. Click OK to close the Options window. The default

styles will be reset for reports or charts.
The Options window allows you to change basic
settings for the Output Viewer 3DR.
Window Menu
The Window menu contains useful tools for mak-
ing multiple data windows easier to view and
compare with one another.

The decimal precision can be changed to increase • Tile Horizontally Sizes and places each
or decrease the number of digits that appear for open window horizontally across the screen
all real numbers that are displayed. so none of them overlap. Since most data in
You can choose to have the current database close the Output Viewer is arranged horizontally
whenever you open a new database. within a window, this option is very helpful
Selecting the check box for Enable Multi-create for comparing data from one window with
Dialogs will leave the Select Report and Select another.
Chart windows open until you close them. This • Tile Vertically Sizes and places each open
allows you to open multiple reports or charts at window vertically across the screen. This
the same time without having to reopen the cre- makes comparing data across two or more
ation window each time. windows convenient when the data in the
This option is checked by default. If you want the window is arranged vertically.
selection widow to close when you open a report • Cascade Places windows on top of each
or chart, uncheck the box. other in an overlapping manner.
If you have changed your report or chart style as • Arrange Icons If you have report or chart
described in the previous heading, you can windows minimized within the Output
restore the default styles by using the Reset Viewer 3DR window, this options will align
Defaults menu and Reset button. them in a row along the bottom of the Output
Viewer 3DR window.
How to Reset Default Styles • Close All Closes all open windows in the
Output Viewer 3DR.
1. Select Report or Chart Defaults from the pull-down • Open Windows This last field in the Win-
menu in the Options window. dow menu displays the names of all the open
windows. This is helpful for navigating
2. Click the Reset button.
 ProModel 369
User Guide

through data windows when you have many For more information on these features see “View
open at one time. Menu” on page 364.

Help Menu Option Tools

The Help menu gives you access to the Output These tools allow you to access some of the fea-
Viewer’s help file as well as information about tures in the Tools menu as well as the Sheet Prop-
the Output Viewer 3DR. erties window.
• : Displays Sheet Properties.
Toolbar • : Displays the Options window.
The Output Viewer 3DR Toolbar gives you quick
For more information of Sheet Properties, see
access to some of the options found in the Menu
“Sheet/Chart Properties” on page 364. For more
bar.
information on the Options windows, see “Tools
Menu” on page 366.

Help Tool
• : Starts the Output Viewer 3DR Online
File Tools Help.

The File tools allow you to quickly open data

files, export data, and print files. View Manager Tools
The View Manager tools are located on the far
• : Opens an .idb or .rdb data file. right of the toolbar. These tools allow you to
• : Exports data. quickly select a view.
• : Prints the data. • : Allows you to
For more information on these features see “File select a view from the pull-down menu.
Menu” on page 364. • : Scrolls through your views.

Report and Chart Tools • : Displays the View Manager window.

The Report and Chart tools gives quick access to For more information on Views and the View
options found in the View menu. Manager, see “View Manager” on page 366

• : Creates a report.
• : Creates a category chart.
Right-click Menu
The Right-click menu provides a shortcut for
• : Creates a state chart. editing the appearance and structure of your
• : Creates a histogram. reports and charts.
The Right-click menu is available in report and
• : Creates a time plot chart.
chart windows. Additionally, the options that
appear when you right-click in the Output Viewer
370 Chapter 10:
Output Viewer 3DR

3DR vary depending on which area you right- “Category Chart” on page 381 for more
click on. information.
• Create State Chart If you right-click on a
Right-click Menu in Reports column that contains percentage values, you
can choose to have that data displayed,
When you right-click anywhere in a report win-
together with all other percentage columns
dow, the following menu appears.
on the sheet, as a State Chart. The State
Chart that’s created is the same as one cre-
ated using the State Chart option. See “State
Chart” on page 382 for more information.

Right-click Menu in Charts

• Format Cells This option brings up a win-
The Right-click menu that appears for charts is
dow that allows you to edit the size and
different than the menu for reports.
alignment of the cell fonts, and the color of
the cells. There are three areas within a Chart window that
you can right-click to bring up a different menu:
• Copy Copy transfers the contents of the
highlighted cells to the clipboard. This is • On the legend area.
useful for transferring select information to a • In the Chart area.
separate spreadsheet. • On a title or label.
• Sheet Properties This option brings up the
Sheet Properties of the current report. For Right-click Menu for the Legend Area
more information on this window see The legend area is located within the Chart win-
“Sheet/Chart Properties” on page 364. dow, and gives an explanation of the chart’s color
When you right-click anywhere in a report win- codes.
dow that contains numerical values, the Right- An example of a legend area is shown below.
click menu contains two additional options
depending on whether the values are percentage
values or not.

• Create Chart If you right-click on a column

of numerical value, including percentage
value, you can choose to have that data dis-
played as a Category Chart. The Category
Chart that’s created is the same as one cre-
ated using the Category Chart option. See
 ProModel 371
User Guide

When you right-click anywhere in the legend This could be the color of the background or
area, the following menu appears. bars in the chart.
• Toolbar Toggles the toolbar for chart win-
dows on and off. This is helpful, for exam-
ple, to make the chart appear less cluttered
during a presentation of the data or on a
printout of the chart. For more information
on the chart window toolbar see “Chart Tool-
bar” on page 379.
• Chart Properties Opens the Properties win-
dow. For more information on this window
see “Sheet/Chart Properties” on page 364.
• Modify Chart Items This options opens the
chart’s data dialog, which was initial dialog
There are four areas in this menu: shown when you first created the chart. This
• Font This features lets you change the font option is only available for Histogram and
options for the legend labels. Time Plot chart types.
• AutoSize The AutoSize option resizes the For more information on the data dialog see
legend area to fit the labels in the legend. the corresponding chart descriptions, begin-
• Legend Position The position of the legend ning with “Category Chart” on page 381.
area can be moved to any one of the four
sides of the Chart window, or it can float in Right-click Menu for Titles and Labels
its own window. Titles and labels are the text within the chart area.
• Hide Selecting this option makes the leg- Right-clicking on either of these two will bring
end disappear. You can bring the legend back up a Right-click menu similar to that of a chart
by opening the Chart Properties window in area’s menu, but with two additional options.
the View menu.

Right-click Menu for the Chart Area

Right clicking anywhere in the Chart window,
except for the legend area, brings up the follow-
ing window.

• Edit Title Edits the text for the title of the

chart or axes.
• Font Allows you to change the font charac-
teristics for the titles and labels.
• Color This will allow you to change the
color of the area your mouse was positioned
over when you opened the Right-click menu.
372 Chapter 10:
Creating Reports

Creating Reports 2. If the model you ran had multiple scenarios or repli-
cations, the following window appears.
Reports contain the numerical data that is col-
lected during your simulation.

This information is presented in spreadsheet 3. From this window you may choose which scenarios
form, and grouped into the following categories: and replications to view.
• General 4. Click on the Create button. This will open a new
• Entity Activity window with the chosen report.
• Entity Costing
• Entity States Please note
• Failed Arrivals
• Location Costing If your model was run for only one replication
• Location States Multi and one scenario, the report window will open
• Location States Single/Tank immediately after selecting the Reports option.
• Locations
• Logs
• Node Entries
Report Window
• Resource Costing
• Resource States The Report window contains the categorized
information from your simulation.
• Resources
• Variables
For more information on each of these categories
see “Report Data” on page 373.

How to create a report

1. Choose the Reports option from the View menu or

The data appears in spreadsheet format, and is
the Reports icon, , from the Toolbar.
grouped by the categories listed by tabs along the
top of the Report window.
Selecting a tab will bring up a new table, and
additional tabs can be accessed using the left and
right arrows, .
 ProModel 373
User Guide

The caption of a report can be renamed by either Entity Activity

double clicking on it and then typing in the new Entity activity is reported for only those entities
name or opening the sheet properties window and that have exited the system.
typing a new name in the Caption area.
• Total Exits The number of entities that
completely exit the system either through the
Report Data EXIT routing or when they are joined,
The spreadsheet for each button contains the fol- renamed, or combined. In some cases, enti-
lowing information. ties also exit the system when you use the
SPLIT AS, UNGROUP, or ROUTE state-
ments.
Please note
• Current Quantity In System The total num-
ber of entities remaining in the system at the
The default time units shown in the report will be
time the simulation ends. These are entities
one unit longer than the unit selected in the Simu-
that have not exited.
lation Options dialog box. For example, if you
• Average Time In System The average total
select minutes in Simulation Options, the time
time the entity spends in the system.
displayed in the report will be in Hours. You may
• Average Time In Move Logic The average
also notice that Day is the last option available in
Simulation Options, in which case the time unit time the entity spent traveling between loca-
will be in weeks for the report. tions, including any delays incurred in move
logic.
• Average Time Waiting The average time the
entity spent waiting for a resource or another
General entity (to join or combine). Also includes
time waiting in queue behind a blocked
• Run Date/Time The date and time the
entity.
model was run for the displayed output.
• Average Time In Operation The average
• Model Title The name of the model.
time the entity spent processing (i.e., WAIT
• Model Path/File The path and name of the
or USE statements) at a location or traveling
model file. on a conveyor/queue.
• Warmup Time The amount of initial time
• Average Time Blocked The average time the
the simulation spent in a warmup state. No
entity spent waiting for a destination location
statistics were gathered during this time. The
to have available capacity.
time unit used is one unit longer than defined
in the Clock Precision field of the Simulation
Options dialog.
Entity Costing
• Simulation Time The total simulation time, • Explicit Exits The number of entities that
including the warmup time. The time unit have explicitly exited. Whenever an entity
used is one unit longer than defined in the exits the system, it is an explicit exit
Clock Precision field of the Simulation except in the following cases:
Options dialog. - When an entity JOINS, permanently
LOADS, or COMBINES with another
entity, it implicitly exits the system, and
is reported as an exit in the Entity Activ-
374 Chapter 10:
Creating Reports

ity report. However, for costing pur- • % In Move Logic The percentage of time
poses, the entity did not explicitly exit, the entity spent traveling between locations,
but its costing information was added to including any delay time incurred in move
the entity it was JOINED, permanently logic.
LOADED, or COMBINED with. • % Waiting The percentage of time the
- When an entity temporarily LOADS onto a entity spent waiting for a resource, a WAIT
base entity or GROUPS with another UNTIL condition, another entity to join or
entity, and the entire LOADED or combine, or behind other entities. (100% -
GROUPED entity exits the system, the Sum of %’s for all other states.)
original entity implicitly exits the sys- • % In Operation The percentage of time the
tem, and is reported as an exit in the entity spent in processing at a location or
Entity Activity report. However, for traveling on a conveyor/queue. If an entity is
costing purposes, the original entity did on a conveyor behind another entity which is
not explicitly exit, but its costing infor- blocked because the next location is unavail-
mation was added to the entire load or able, the time the entity spent behind the
group. other entity is considered % in Operation.
• Total Cost Dollars Total Cost = cumulative • % Blocked The percentage of time the
entity cost, or the sum of costs incurred on entity spent waiting for a the next location to
all locations the entity passed through + become available.
the sum of all costs incurred by use of
resource + initial cost + any IncEntCost Failed Arrivals
• % Total Cost % Total Cost refers to the
The number of entities that failed to arrive at a
entity’s percentage of sum of all entity
specific location due to insufficient capacity.
costs
In the above calculations, the rate defined (per
Location Costing
day, hour, minute, and second) converts to the
default time units specified in the General Infor- • Operation Cost Dollars Operational Cost =
mation dialog. (Active Operation Time * Rate) + (Any
IncLocCost)
• % Operation Cost Refers to the location’s
Please note percentage of the sum of all operation costs
• Resource Cost Dollars Resource Cost =
ProModel does not allow you to generate a Cost- (Utilization * Rate) + (Times Used * Cost
ing Graph. However, if you set a variable equal per use)
to GetCost (e.g., Var1=GetCost), you can gener-
ate a time series graph to track changing entity
costs. Please note

For Resource Cost, Utilization and Times Used

refer to the utilization of a resource while at a
Entity States location. This applies only to resource use
Reported by entity type for only those entities through operation logic.
that have exited the system.
 ProModel 375
User Guide

• % Resource Cost Refers to the location’s Location States (Single Capacity/Tank)

percentage of the sum of all resource costs • Scheduled Time The total amount of time
• Total Cost Dollars Total Cost = (Operation the location was scheduled to be available.
Cost + Resource Cost) This value is now in decimal format, not
• % Total Cost Refers to location’s percent- truncated. (Excludes off-shift time, break
age of the sum of all location costs time, and scheduled downtimes.)
• % Operation The percentage of time the
Location Setup location was actually processing an entity.
• Name The name of the location where the • % Setup The percentage of time the loca-
setup downtime occurred. tion spent in setup in order to process the
• Entity The name of the entity that caused entities.
the setup downtime. • % Idle The percentage of time no entities
• Total Setups The number of times this loca- were at the location, but the location was not
tion/entity combination resulted in a setup down.
downtime. • % Waiting The percentage of time the loca-
• Avg Time Per Setup (HR) The average time tion was waiting for a resource, another
in hours the location was down for each entity, or a WAIT UNTIL condition in order
setup downtime. to begin processing or move to the next loca-
tion. Any delays in processing move logic
Location States (Multiple Capacity) (even WAIT statements) are counted as wait-
ing time and include the following state-
• Scheduled Time The total amount of time
ments:
the location was scheduled to be available.
•JOIN
This value is now in decimal format, not
truncated. (Excludes off-shift time, break •LOAD
time, and scheduled downtimes.) •MATCH
• % Empty The percentage of time the loca- • % Blocked The percentage of time entities
tion had no entities. spent waiting for a freed destination.
• % Partially Occupied The percentage of • % Down The percentage of time the loca-
time the location has entities but was not tion was down due to unscheduled down-
filled to capacity (100% of time - %Full - times.
%Empty).
• % Full The percentage of time the location Locations
was full to capacity with entities. • Scheduled Time The total amount of time
• % Down The percentage of time the loca- the location was scheduled to be available.
tion was down as the result of unscheduled This value is in decimal format, not trun-
downtimes. This does not exclude the possi- cated. (Excludes off-shift time, break time,
bility of overlap with any of the previous and scheduled downtimes.)
three states. • Capacity The capacity defined in the loca-
tion’s module for this location.
• Total Entries The total number of entities
that entered the location, not including enti-
ties arriving to be joined and loaded. Entities
376 Chapter 10:
Creating Reports

split, unloaded, or ungrouped from another Please note

entity at a location do not count as additional
entries. Arriving entities that have been pre- Log statistics are set up by the user with a LOG
viously grouped or loaded to form a single statement to track the time entities spend between
entity only count as one entry. any two points in the model.
• Average Time Per Entry The average time
each entry spent at the location. This time
may include partial times from the beginning
and end of the actual run time. Node Entries
• Average Contents The average number of A node entry summary is generated for each non-
entries at the location. passing path network in the system. It contains
• Maximum Contents The maximum number the following information.
of entries which occupied the location over
• Path Name The name of the path the node
the course of the simulation.
resides on.
• Current Contents The number of entities
• Total Entries The number of times that a
remaining at the location when the simula- resource entered the path node.
tion ended.
• Blocked Entries The number of times a
• % Utilization The percentage of capacity
resource tried to claim a path node occupied
occupied, on average, during the simulation.
by another resource.
Cumulative Occupancy Time x 100
Capacity x Scheduled Time Resources Costing
Cumulative Occupancy Time refers to the
• NonUse Cost Dollars NonUse Cost = (1-%
sum of the clock time each entity spends at a
Utilization) * Scheduled Time * Rate
location for processing.
• % NonUse Cost Refers to the resource’s
percentage of the sum of all nonuse costs
Logs • Usage Cost Dollars Usage Cost = (% Utili-
• Numbers of Observations The number of zation * Scheduled Time * Rate) + (Times
log entries that occurred during the simula- Used * Cost per use)
tion for the given Log Name. • % Usage Cost Refers to the resource’s per-
• Minimum Value The minimum log entry centage of the sum of all resource usage
value during the simulation for the given costs
Log Name. • Total Cost Dollars Total Cost = Usage Cost
• Maximum Value The maximum log entry + NonUse Cost
value during the simulation for the given • % Total Cost Refers to the resource’s per-
Log Name. centage of the sum of all resource costs
• Average Value The average value of all log
entries during the simulation for the given Resource States
Log Name.
• Scheduled Time The total amount of time
the resource was scheduled to be available.
(Excludes off-shift time, break time, and
scheduled downtimes.)
 ProModel 377
User Guide

• % In Use The percentage of time the tion or other resource to transport or process
resource spent transporting or processing an an entity, or to service a location or other
entity, or servicing a location or other resource. Does not include any pickup time,
resource that was down. This also includes but does include any blocked time. (This
deposit time. information is not available if your model
• % Travel To Use The percentage of time the does not have dynamic resources.)
resource spent traveling to a location or other Average Time Travel to Use = total Time Travel
resource to transport or process an entity, or to Use / (divided by) Number of Times Used
to service a location or other resource. This • Average Time Travel To Park The average
also includes pickup time. (This information time the resource spent traveling to either a
is not available if your model does not have park node or a downtime node. (This infor-
dynamic resources.) mation is not available if your model does
• % Travel To Park The percentage of time not have dynamic resources.)
the resource spent traveling to a path node to • % Blocked In Travel The percentage of
park or traveling to its downtime node. (This time the resource was unable to move to a
information is not available if your model destination because the next path node along
does not have dynamic resources.) the route of travel was blocked (occupied by
• % Idle The percentage of time the resource another resource). (This information is not
was available but not in use. available if your model does not have
• % Down The percentage of time the dynamic resources.)
resource was unavailable due to unscheduled • % Utilization The percentage of time the
downtimes. resource spent traveling to be used, trans-
porting or processing an entity, or servicing a
Resources location or other resource.
• Units The number of units defined in the Total Travel to Use Time + Total Time In Usage x
Resources module for that resource. 100 / (divided by)
• Scheduled Time The total amount of time Total Scheduled Time
the resource was scheduled to be available.
(Excludes off-shift time, break time, and Please note
scheduled downtimes.)
• Number of Times Used The total number of ProModel reports resource groups and multi-unit
times the resource has been acquired to resources both by unit and collectively. The col-
transport or process an entity or to service lective unit (aggregate) report for a resource
locations or other downed resources. totals the first three fields and averages the last
• Average Time Per Usage The average time five fields discussed above.
the resource spent transporting or processing
an entity, or servicing a location or other
resource. Includes any pickup and drop-off
time as well as any blocked time while in Variables
use. (See note on time units.)
• Total Changes The total number of times
• Average Time Travel To Use The average the value of the given variable changed dur-
time the resource spent traveling to a loca- ing the simulation.
378 Chapter 10:
Creating Reports

• Average Time Per Change The average time

a given variable remained at any one value.
• Minimum Value The lowest value of the
variable during the simulation.
• Maximum Value The highest value of the
variable during the simulation.
• Current Value The final value of the vari-
able when the simulation ended.
• Average Value The average value of the
variable during the simulation. This value is
time weighted.

Please note

In the report, if a variable name is followed by an

asterisk (*), the variable is an observation-based
variable. Otherwise, it is a time-weighted vari-
able. This determination is made in the Variable
edit table where the variable is defined.

The initial value for observation-based variables

is not accounted for in the statistics.
 ProModel 379
User Guide

Creating Charts Chart Toolbar

The toolbar that appears in a Chart window gives
Charts provide visual representations of the data
you several options to change the way the infor-
contained in Reports.
mation is presented in your chart.
The Output Viewer 3DR can display four main
types of charts with several sub-types:
• Category Charts
• State Charts • : Toggles between a three-dimensional
• Histograms and two-dimensional bars in your
chart. Three-dimensional is the default
- Time-Weighted Values
view.
- Simple Values
• Time Plots • : Toggles between bars and cylinders in
- Time-Weighted Values the Chart area.
- Simple Values • : Expands the chart along the z-axis to
- State Values show multiple scenarios in layers. This
- Counts option will not be available if only one
scenario was run.
Chart Window • : Shows the results in a stacked bar
chart.
The chart window contains your chart and
options to modify your chart. • : When the chart is three-dimensional,
this option will allow you to rotate the
view using the cursor.
• : Use this tool to enlarge regions of your
chart. Select this tool then click and
drag to outline the chart area you want
to enlarge. You can continue to zoom
in on an area, or you can reset the view
to the default zoom level by selecting
this tool again.
• : Use this tool to change the colors in
the Chart area. Selecting this tool will
open a menu with color options.
Choosing a color will change your cur-
Regardless of the type of chart you open, all chart sor to a paint bucket. Position the
windows have options and fields in common: bucket over the area you want to
• Chart Toolbar change, and click to fill the area with
• Legend Field the new color.
• Chart Area • : Opens the chart’s properties dialog.
• Display and Alias
380 Chapter 10:
Creating Charts

• : Opens a dialog, which allows you to Legend Field

modify the items displayed in the
The Legend field shows the definition and color-
chart. This option is only available for
coding of the bars in your chart.
Histogram and Time Plot charts.
• : Allows you to change the chart’s titles
and labels.
• : Allows you to change the font charac- Chart Area
teristic of the chart’s titles and labels. The Chart area contains your chart.
• : Toggles the point labels on and off.
Point labels are the numbers that the
bars in your chart represent. These
numbers will appear at the top of the
bars when this option is selected.
• : Toggles the point makers on and off.
Point markers are small graphics that
show the data points on your graphs.
• : Toggles the Legend area on and off.
The appearance of this chart will depend on the
• : Toggles the Display and Alias field on type of chart you are viewing; i.e. category, histo-
and off. For more information on this gram, etc.
field see “Display and Alias” on
page 380. Display and Alias
The Display and Alias field, which can be tog-
• : Toggles the vertical grid lines in the
gled on and off from the toolbar, allows you to
chart on and off.
quickly select the data items you wish to display
• : Toggles the horizontal grid lines in the in the chart and optionally assign aliases to the
chart on and off. data items.
• : Copies the chart to the Windows clip-
board as a bitmap, a metafile, or as
plain text (data only).

Please note

The Bar/Cylinder, , tool is not available for

Simple Values and Time-weighted Values time
plot charts, since they do not use bars to repre-
sent data.
Select which series and items you would like dis-
played in the chart by checking the box in the
 ProModel 381
User Guide

Visible column. To show or hide all the items you Category Chart
can click check or uncheck the box in the <ALL>
row or click on any box while holding the CTRL Category Charts displays bar charts for columns
key. of data found in reports.
Double click on a series or item name to rename The Category Chart is an excellent way to visu-
it with an alias. ally compare the different items in your reports. It
is also helpful for organizing data attractively for
presentations.
To display a Category Chart, select Category
Chart from the View menu or the Category Chart
icon from the Toolbar. As a shortcut, you can also
right-click on any column of data in a report and
select Category Chart from the drop-down menu.
When you choose to view a Category Chart, the
Category Chart Selection dialog will be dis-
played.

From this menu you can select the scenarios, rep-

lications, periods (only available if Batch Mean
or Periodic Output Reporting is selected in the
Simulation Options dialog) and categories of the
data you want displayed.
For information on each category, see “Report
Data” on page 373.
382 Chapter 10:
Creating Charts

Category Chart Properties Category Chart Example

Choosing the properties option for a category An example of a Category Chart is shown below.
chart will open the Chart Properties dialog.

• Display Properties: Select the angle of the Please Note

text for the X-Axis labels.
• Axis Range - X-Axis Range (min- Positioning your cursor over a bar on the chart
max): These two boxes show the range of will display specific information about that par-
items displayed in the X-Axis. ticular bar. The appearance and structure of your
• Axis Range - Y-Axis Range (min- chart can be edited using the chart toolbar or the
max): In the first box choose the value for right-click menu. For more information see
the minimum range for the Y-Axis. The max- “Chart Toolbar” on page 379 or “Right-click
imum range is entered in the second box. Menu” on page 369.
• Axis Zoom Range - X-Axis Range (min-
max): Choose which range of X-Axis
items to zoom in on by using these two
boxes. State Chart
• Axis Zoom Range - Y-Axis Range (min- State Charts show stacked bar charts of location,
max): Choose which range of Y-Axis val- resource, and entity states. States describe the
ues to zoom in on by using these two boxes. condition of these objects.
This type of chart is useful for quickly seeing
Please Note what your locations, resources, and entities spent
their time doing. Such visualizations can help
Changes to a chart’s properties does not apply to identify problem areas in your process.
other charts or persist when the chart is closed To display a State Chart, select State Chart from
and then regenerated. the View menu or the State Chart icon from the
Toolbar. As a shortcut, you can also right-click on
any column of data in a report containing per-
 ProModel 383
User Guide

centage values and select State Chart from the State Chart Example
drop-down menu. An example of a State Chart is shown below.
When you choose to view a State Chart, the State
Chart Selection dialog will be displayed.

State Chart Selection Window

This chart shows the percentage of time by sce-

nario each location spent in the six different
states: operation, setup, idle, waiting, blocked,
and down.
Right click on any bar in the chart, and choose
Create Pie Chart to have that item’s state infor-
mation displayed as a pie chart.

From this menu you can select the scenarios, rep-

lications, periods (only available if Batch Mean
or Periodic Output Reporting is selected in the
Simulation Options dialog) and state categories
of the data you want displayed.

State Chart Properties

The State Chart Properties window is function-
ally equivalent as the Category Chart Properties Please Note
window. See “Category Chart Properties” on
page 382. Positioning your cursor over a bar on the chart
will display specific information about that par-
ticular bar. The appearance and structure of your
chart can be edited using the chart toolbar or the
right-click menu. For more information see
“Right-click Menu” on page 369.
384 Chapter 10:
Creating Charts

Histogram If you check the Manual Bar Width option, you

may choose the range value for each bar shown in
A histogram is a bar chart showing the percent- the chart. If you leave this field unchecked, 3DR
age of time or times that time plot data fell within will automatically calculate the range value for
a particular range of values. each bar, which will not necessarily be the value
There are two types of histograms that can be dis- in the Bar Width field.
played:
• Time-weighted Values Percentage of total Chart Properties
simulation time that the values fell into a Choosing the properties option for time weighted
specific range. (e.g. the Contents variable of values histogram will open a window with two
a location.) tabs: Data and Display
• Simple Values Percentage of total simula-
tion time that a variable was within a range Chart Properties: Data
of values (e.g. cycle times).

Time Weighted Values Histogram

The time weighted values histogram shows the
percentage of total simulation time the values fell
into specific ranges. The example further
explains how values are grouped.

Selection Window

• Display Series: This is a list of the series

data displayed in the histogram.
Choose the scenarios and replications you would • Min/Max Values: Choose whether to dis-
like displayed for the data item selected. Double play the minimum and/or maximum values
click on an item to move it from the Available for all replications in the histogram.
Items area to the Selected Items area or back • Mean/Median/Mode Values: Choose
again. You may also use the arrow buttons to whether to display the mean, median, and/or
move items between the two areas. mode values for all replications in the histo-
gram.
 ProModel 385
User Guide

• Percentile: Displays the maximum value Chart Example

the series could reach for the chosen percent- The example chart below shows the time-
age of total simulation time. For example, if weighted histogram contents of a queue.
you choose to display an 80 percentile for a
location’s contents, 80% of the simulation
time the location’s contents were at the dis-
played value or less.
• Data Properties: Displays the time units
used to calculate the histogram’s values, and
optionally allows you to choose your own
bar widths, which are the range of values
each bar will display. Entering a smaller bar
width results in more bars, while the greater
the bar width the fewer bars will be dis-
played.

Chart Properties: Display

The Display tab for the time-weighted histogram
properties window is functionally equivalent as Along the X-Axis is the contents of the queue
the Category Chart Properties: Display window, divided into bar units of 10. The Y-Axis shows
with the exception of the “Discrete label the X- the percentage of total simulation time the con-
Axis” option. tents of the queue were at the values along the X-
• Discrete label the X-Axis: When this Axis.
option is checked the full range of each bar is The mouse over shows that for 18.21% of the
shown in the X-Axis. total simulation time, for all replications, the con-
See “Category Chart Properties” on page 382. tents of the queue were between exactly 20 and
almost 30 (29.99).
The average minimum and maximum contents of
the queue, for all replications, were 18 and 64
respectively, while the mean contents were 39.81.
The 80% Percentile line shows that for 80% of
the total simulation time the contents of the queue
were 50 or less.
386 Chapter 10:
Creating Charts

Simple Values Histogram Chart Example

The simple values histogram shows when, by The example chart below shows the simple val-
percentage of total simulation time, a variable’s ues histogram for the variable WIP.
value was within a certain range.

Selection Window

The X-Axis shows the value of the WIP variable

Choose the scenarios and replications you would divided into bar units of 4. The Y-Axis shows the
like displayed for the data item selected. Double percentage of times the WIP variable fell into the
click on an item to move it from the Available ranges shown on the X-Axis.
Items area to the Selected Items area or back
This chart also shows the median value of the
again. You may also use the arrow buttons to
WIP value for all replications. The 80% Percen-
move items between the two areas.
tile shows that for 80% of the counts the value the
If you check the Manual Bar Width option, you WIP variable was 19 or less.
may choose the range value for each bar shown in
the chart. If you leave this field unchecked, 3DR
will automatically calculate the range value for
each bar, which will not necessarily be the value
in the Bar Width field.

Chart Properties
The chart properties for the simple values histo-
gram are the same as for the time-weighted val-
ues histogram. See “Chart Properties” on
page 384.
 ProModel 387
User Guide

Time Plot Time Weighted Values Time plot

Time plots show state and performance values as The time-weighted time plot chart shows variable
they occur over time. This allows you to see values over time.
trends and spikes in activity as the simulation The chart’s X-Axis shows time periods, while the
progressed. Y-Axis shows variable values for each time
Time plots can only be displayed if the user has period.
selected Time Plot as the statistics type for
objects as the model was being built. Selection Window
There are four types of time-plot statistics that
can be displayed:
• Time-weighted Values Variable values
weighted by time (e.g. the Contents variable
of a location.)
• Simple Values Variable values as they
change over time (e.g. cycle times).
• State Values Shows location states over
time.
• Counts The number of occurrences of
some particular event (e.g. the number of
exits from a location).
Choose the scenarios and replications you would
like displayed for the data items selected. Double
click on an item to move it from the Available
Items area to the Selected Items area or back
again. You may also use the arrow buttons to
move items between the two areas.
If you check the “Average data by period” box,
all the values in each period of selected time will
be averaged together. If left unchecked, each
value will be displayed.

Chart Properties
Choosing the properties option for time weighted
values time plot will open a window with two
tabs: Data and Display

Chart Properties: Data

The chart properties:data for the time-weighted
values time plot are the same as for the time-
weighted values histogram. See “Chart Proper-
ties” on page 384.
388 Chapter 10:
Creating Charts

Chart Properties: Display Simple Values Time plot

The Display tab for the time-weighted time plot The simple values time plot shows the change in
properties window is functionally equivalent as variable values over time.
the Category Chart Properties: Display window,
with the exception of the “Line Properties” Selection Window
option.
• Line Properties: Choose the pattern and
thickness for the lines on the chart.
See “Category Chart Properties” on page 382.

Chart Example
The example chart below compares the time-
weighted time plot contents of a queue for two
scenarios.

Choose the scenarios and replications you would

like displayed for the data items selected. Double
click on an item to move it from the Available
Items area to the Selected Items area or back
again. You may also use the arrow buttons to
move items between the two areas.
Choose the number of hours in each period that
will be displayed along the X-Axis.

Chart Properties
Choosing the properties option for simple values
The X-Axis shows the time periods for the chart. time plot will open a window with two tabs: Data
The Y-Axis shows the average content values of and Display
the queue for the time periods in the X-Axis.
Chart Properties: Data
The One Operator scenario additionally displays
the minimum and maximum contents of the
The chart properties:data for the simple values
queue for each time period for all replications, as
time plot are the same as for the time-weighted
well as the contents 99.99% confidence interval,
values histogram. See “Chart Properties” on
which means that 99.99% of all queue contents
page 384.
will be with the two confidence interval lines by
period.
Chart Properties: Display
This chart shows the impact that an additional
The Display tab for the time-weighted time plot
operator has on the contents of a queue.
properties window is functionally equivalent as
 ProModel 389
User Guide

the Category Chart Properties: Display window, State Values Time plot
with the exception of the “Line Properties”
The state values time plot shows location state
option.
statistics over time.
• Line Properties: Choose the pattern and
thickness for the lines on the chart. Selection Window
See “Category Chart Properties” on page 382.

Chart Example
The example chart below compares the value of
the variable “WIP” over time for two scenarios.

Choose the scenarios and replications you would

like displayed for the data items selected. Double
click on an item to move it from the Available
Items area to the Selected Items area or back
again. You may also use the arrow buttons to
move items between the two areas.

Chart Properties
The Y-Axis shows the value of the WIP (work in Choosing the properties option for state values
progress) variable over the time in the X-Axis. time plot will open a window with two tabs: Data
The example shows how adding two additional and Display
resources to the demo model increases WIP and
reduces the fluctuation in WIP. Chart Properties: Data
The only option available from this properties
window is to change the time units shown in the
X-Axis.

Chart Properties: Display

The Display tab for the state values time plot
properties window is functionally equivalent as
the Category Chart Properties: Display window.
See “Category Chart Properties” on page 382.
390 Chapter 10:
Creating Charts

Chart Example Counts Time Plot

The example chart below compares the location The counts time plot shows the number of occur-
states of a location for two scenarios. rences of some particular event in the simulation
(e.g. the throughput of an entity).

Selection Window

The Y-Axis shows the state of the location for the

time in the X-Axis. This example shows how Choose the scenarios and replications you would
adding two resource units can impact a location’s like displayed for the data item selected. Double
state over time. click on an item to move it from the Available
Items area to the Selected Items area or back
again. You may also use the arrow buttons to
move items between the two areas.
Choose the number of hours in each period that
will be displayed along the X-Axis.

Chart Properties
Choosing the properties option for the counts
time plot will open a window with two tabs: Data
and Display

Chart Properties: Data

The chart properties:data for the counts time plot

are the same as for the time-weighted values his-
togram. See “Chart Properties” on page 384.

Chart Properties: Display

The Display tab for the counts time plot proper-
ties window is functionally equivalent as the Cat-
 ProModel 391
User Guide

egory Chart Properties: Display window, with the

exception of the “Line Properties” option.
• Line Properties: Choose the pattern and
thickness for the lines on the chart.
See “Category Chart Properties” on page 382.

Chart Example
The example chart below compares the through-
put of a pallet entity for two scenarios.

The X-Axis show time periods. The Y-Axis

shows the throughput count for the pallet entity
for the time periods in the X-Axis.
This chart shows the improvement in pallet
throughput when an extra resource is added to the
model.
392 Chapter 10:
Creating Charts
 ProModel 393
User Guide

Chapter 11: Language Ele-

ments and Expressions

Language Elements
Language elements are the smallest units of the
language used to define a model’s objects and
logic. Language elements include:
• Names
• Keywords
• Numbers
• Character Strings
• Operators
394 Chapter 11:
Names

Names
A name or identifier is any combination (up to
eighty characters long) of letters, numbers, and
underscores (“_”), used to identify model ele-
ments such as locations, entities, variables, and
functions. Although any valid name can refer to
any object, it is best to use names which describe
the object they identify (e.g., using “ClientA” to
describe an entity that represents a client).
Names, like all words in ProModel, are case
insensitive, meaning that ProModel sees
“PARKING_A,” “Parking_A,” and
“PaRkInG_a” as identical.
Names must use the following conventions:
• Names may contain the letters A through Z
(upper or lower case), digits (0-9) and the
underscore “_”. Names may not contain
spaces. When opening an older model,
ProModel flags improper use of these
restricted characters.
• Do not use a digit as the first character of a
name. After the first character, any charac-
ter may be a digit. For example, “2Var” is
an invalid name, but “V2”, is a valid name.
• Names may not be keywords, but names may
contain keywords. For example, “For” is
an invalid name, but “Forklift” is a valid
name. Similarly, “Queue2” and “Order-
Qty” are both valid.
• No matter what they identify, every name in
a model must be unique. For example, you
cannot name both a location and an entity
“Server.” You may, however, name one
“Server1” or “Server_Location” and the
other “Server2” or “Server_Resource.”
 ProModel 395
User Guide

Keywords Please note

Keywords are words that ProModel reserves for *Reserved for future use.
special use as commands or function calls. Key-
words may not be used as names, although names For information on tank keywords, see “Tanks”
may contain keywords. Keywords, like all words on page 180.
in ProModel, are case insensitive.

accum dep hr ms* send

activate dispatch* if off* setrate
all display iff or show*
alt do ig order skip
and dosload in ownedresource snapshot*
as drop* inc p5 sound
backup dtleft incentcost p6 split as
begin else incloccost pause stop
bi empty increscost percentage* take
board* end inf pick* then
break ent infinite preemptedres* threadnum
breakblk entity int preemptor timeleft
by er join priority to
cancel* exit jointly prompt trace
calday fifo keep queue* turn
calhour first lifo random ungroup
calmin for load read unload
case* forlocation loc real until
char format location recently* up*
claim* forresource log rename use
close free lu report variable
combine full maparr res view
condition geo match reserve* wait
cont get min reset warmup
convey getcost mod reset stats while
create getresrate most resource wk
day goto move resqty write
debug graphic move for return writeline
dec group move on route xsub
default hide* move with sec xwrite
396 Chapter 11:
Numbers

Numbers Name-Index Numbers

ProModel uses two types of numbers: real num- When a simulation begins, locations, resources,
and entities are all assigned numbers according to
bers and integers. ProModel also uses a special
their position in their respective edit tables. The
category of integers, called “name-index num-
number assigned to the element is called its
bers.” This section discusses real numbers, inte-
name-index number. For example, the third entity
gers, and name-index numbers. It then discusses
in the Entity edit table will have the number three
converting between the different types.
for its name index number. The name of an ele-
ment may be used in an expression to reference
Integers its name-index number.
An integer number is a whole number ranging For example, if EntityA were the third entity in
from -2,147,483,648 to 2,147,483,647. Integer the Entity edit table, the statement, “Attr1 =
values may not include commas. Therefore, the EntityA,” would assign the number three to
number 5,380 should be entered as 5380. Name- Attr1, because attributes take numbers. Addition-
index numbers (described in this section) work ally, you may also test for an index number by
just like integer numbers. referencing the element name with a statement
like, “IF Var5 = Location3 THEN.” In fact, when
Examples of integers using a name-index number to identify a location,
resource, or entity (as in the previous examples),
-2234798 it is usually best to use the name of the element,
because inserting or deleting an element from the
0
edit table, may change the name-index number
32 assigned to other elements.
If you need to refer to a location, resource, or
entity by name but only know its name-index
Real Numbers number, use the name functions: LOC(), RES(),
and ENT(). These functions allow name-index
A real number is any number ranging from 1.7 X numbers and variables or attributes containing
10 -308 to 1.7 X 10 +308, including decimals. name-index numbers to be converted back to
Real values may not include commas. As such, their actual names for use in statements or
the number 5,380.5 should be entered as 5380.5. expressions requiring the element name.

Examples of real numbers Consider the statement, “Attr1 = PASSENGER.”

Although this statement only stores the name
index number of the element in the attribute, the
-2.875638
name-index number can then be used in conjunc-
844.2 tion with LOC(), ENT(), and RES() to get the
65.0 actual name of the location. For example, if PAS-
SENGER is the fifth entity in the Entity edit
table, the statement JOIN 1 ENT(Attr1) works
the same as JOIN 1 PASSENGER. Additionally,
 ProModel 397
User Guide

a name-index number can be used with the name

functions to output a name to the screen or a file.
Character Strings
A string is any collection of characters enclosed
Converting Between Numeric Types in quotes, such as “Now Boarding.” Unlike some
programming languages, ProModel uses charac-
When an expression expects one type of value ter strings exclusively for output either to a file or
but receives another, ProModel automatically to the screen. Strings may contain any of the 256
takes care of converting between the two, so most ASCII characters. (ASCII characters not on the
often the difference will not matter. However, keyboard can be included in string expressions
when ProModel expects an integer but receives a with the CHAR() function.) Strings may include
real value, it truncates the real value at the deci- keywords and names, but those keywords and
mal point. For example, say the variable Integer1 names will not be executed in or used by the
is assigned the value 3.9, as in the following logic.
statement: Integer1=3.9. The variable Integer1
would hold the value 3, not 4. To round 3.9 when Additionally, the symbol “\n” can be used to
assigning to an integer variable would require the divide a string into multiple lines when it is out-
statement, Integer1=Round(3.9). put, as in the example below.

Converting from name-index numbers to the The statement, DISPLAY “The simulation \nis
name of an element requires the ENT(), LOC(), half over.” displays this dialog box:
and RES() functions as ProModel does not auto-
matically convert numbers to names. For infor-
mation on how to output the name of an element
based on its name-index number, see “String
Expressions” on page 402.

Examples of character strings

“EntA exited the system.”

“Location 3 is operating at capacity.”
“ProModel”

Although ProModel does not provide string vari-

ables, it does allow the names of model elements
to be stored in variables and attributes as name-
index numbers (see “Name-Index Numbers” on
page 396). The name referenced by a name-index
number may be used in statements and output to
the screen or a file with the ENT(), LOC(), and
RES() functions. See “String Expressions” on
page 402 for more information.
398 Chapter 11:
Operators

Operators Comparison Operators

Operators are symbols used to perform opera- Operator Meaning
tions on elements in an expression. ProModel AND TRUE if both expressions are TRUE
operators include Boolean operators, mathemati- OR TRUE if one expression is TRUE
cal operators, and a string operator. Unlike
NOT Makes TRUE expressions FALSE
reserved words, you may not use operators as any and FALSE expressions TRUE
part of a name. The following sections explain
the use of these operators for different expression
types. Operator Precedence
As in conventional mathematics, ProModel eval-
Mathematical Operators uates expressions with more than one operator
according to certain rules of precedence. Expres-
Operator Meaning Example
sions with more than one operator evaluate in the
+ Addition A=B+C following order:
- Subtraction A=B-C
1. Terms inside parentheses: ( )
* Multiplication A=B*C
2. Exponentiation: **
/ Division A=B/C 3. Multiplication: *; Division: /; and Modulus:
Mod or @ Modulus A=B Mod C @
(assigns the remain- 4. Addition: +; Subtraction: -
der of B divided by C
5. Equalities and Inequalities: =, <>, >, >=, <,
to A)
<=
** Exponentia- A=B**C
6. NOT
tion (assigns the value of
B raised to the C 7. AND
power) 8. OR
9. Concatenation: $; (For string expressions
only.)
Relational Operators For more information and additional examples of
Operator Meaning operator precedence, see “Operator Precedence”
on page 403.
= Equal to
> Greater than
< Less than Expressions
>= Greater than or equal to Expressions consist of a value or combination of
<= Less than or equal to values (even of different types), variables,
<> Not equal to attributes, functions, and operators that result in a
value. Many consider an expression to be a string
expression if it evaluates to a string, a numeric
expression if it evaluates to a number, and so on.
(For information on how to handle different value
 ProModel 399
User Guide

types in the same expression, see “Converting

Between Numeric Types” on page 397.)
Numeric Expressions
A numeric expression is a combination of
The following are the different expression types
numeric elements (such as numbers, variables,
used in ProModel:
and functions) and operators that evaluates to a
• Numeric Expressions numeric value.
• Boolean Expressions
An expression can contain any of the following in
• Time Expressions any combination:
• String Expressions
Arrays Mathematical operators
Attributes Name-Index numbers
Boolean operators Numbers
Distributions Subroutines
Macros System functions
Math function table Variables
functions

The following mathematical operators are avail-

able:

Operator Meaning Example

+ Addition A=B+C
- Subtraction A=B-C
* Multiplication A=B*C
/ Division A=B/C
Mod or @ Modulus A=B Mod C (assigns
the remainder of B
divided by C to A)
** Exponentia- A=B**C (assigns the
tion value of B raised to the
C power)

You can perform additional mathematical opera-

tions using math functions. For more information
on operator precedence rules and expression nest-
ing, see “Operator Precedence” on page 403.

Please note

In each of the examples above, if A is an integer

number and B and C are both real numbers, the
400 Chapter 11:
Boolean Expressions

result will be truncated unless ROUND() is used

(e.g., A = ROUND(B+C)).
Boolean Expressions
Boolean expressions are relational comparisons
between numeric expressions resulting in a value
of either True or False. Boolean expressions are
used most often in IF...THEN and other control
statements. The following relational operators are
used in Boolean expressions:

Operator Meaning
= Equal to
> Greater than
< Less than
>= Greater than or equal to
<= Less than or equal to
<> Not equal to

Relational operator examples

A=B
A>B
A<B
A >= B
A <= B
A <> B

Spacing between the terms and operators within a

numeric expression is optional. However, for
operators with two characters (for example, >=,
<=, <>), no spaces are allowed between charac-
ters in the operator.
 ProModel 401
User Guide

Additionally, the following operators compare

two Boolean expressions.
Time Expressions
A time expression is a numeric expression fol-
Operator Meaning lowed optionally by a time unit (WK, DAY, HR,
AND TRUE if both expressions are TRUE MIN, SEC) which defines a duration. If no time
OR TRUE if one expression is TRUE unit is specified, the default time unit specified in
NOT Makes TRUE expressions FALSE and the General Information dialog box is assumed.
FALSE expressions TRUE ProModel knows whether an expression is a time
expression based on the context. Time expres-
For information on operator precedence and nest- sions are not valid within a function call. For
ing rules, see “Operator Precedence” on example, E(10 sec) is invalid, while E(10) sec is
page 403. valid. If a negative value is used for a time
expression, it is automatically converted to zero.

Syntax for time expressions

<numeric expression>{<time units>}

Examples
2 hr
E(10) min
Var1+40.25 min

Note that time units cannot be mixed (e.g., 3 min

21 sec), unless you use colon notation.
402 Chapter 11:
String Expressions

Colon Notation for Time Values String Expressions

Colon notation allows for more complex time Any text to be written to a file or displayed on the
expressions. You may use colon notation in the screen is created with a string expression. String
following manner to express time values. expressions are created from a combination of the
following:
Colon notation
• Character strings • ENT()
<hours expression>:<minutes expression>:<seconds • Concatenation operators "$" • LOC()
expression> • Numeric Expressions • RES()
• CHAR() • FORMAT()

Colon notated time expressions evaluate from A string expression must begin with a concatena-
right to left as illustrated in the following exam- tion operator ($) or with a string constant in
ples: quotes (i.e., “...”). The concatenation operator
combines components together, and must be
Example Meaning between all components of a string expression.
:05 5 seconds For example, if Attr1 is 7.83, then the expression
5:00: or 5:: 5 hours “STRING1”$ ATTR1 $ “STRING2” evaluates
5:00 or 5: 5 minutes to “String17.83String2.”
2:40: 2 hours and 40 minutes To output the name of a location, entity, or
15:02:05 15 hours, 2 minutes and 5 seconds resource, use the appropriate function inside a
3:25 3 minutes and 25 seconds string expression: LOC() for locations, ENT() for
entities, and RES() for resources. For example,
Attr1::Var2 Attr1 hours and Var2 seconds
the following logic checks the first ten locations
in a model and displays the name of any location
that is completely full.

Display name of full location

Var1 = 1
While Var1 <= 10 Do
Begin
If FreeCap(Loc(Var1)) = 0 Then
DISPLAY Loc(Var1) $ “is full.”
INC Var1
End

String expressions are valid only as part of the

following statements and functions: DISPLAY,
 ProModel 403
User Guide

PAUSE, PROMPT, STOP, WRITE, WRITE-

LINE, TRACE, XSUB(), and XWRITE.
Operator Precedence
As in conventional mathematics, ProModel eval-
String expressions uates expressions with more than one operator
according to certain rules of precedence. Expres-
sions with more than one operator are evaluated
If a model had been running for six days, the statement
in the following order:
DISPLAY “The simulation ran \n” $ CLOCK(DAY) $
“days.” 1. Terms inside parentheses: ( )
2. Exponentiation: **
would display the following dialog box.
3. Multiplication: *; Division: /; and Modulus:
@
4. Addition: +; Subtraction: -
5. Equalities and Inequalities: =, <>, >, >=, <,
<=
6. NOT
7. AND
8. OR
9. Concatenation: $; (For string expressions
only.)
When evaluating more than one operator with the
same precedence, ProModel works from left to
right.
Arithmetic and boolean expressions may include
nested expressions (expressions in parentheses)
to indicate precedence in complex expressions
such as the following examples:

Nested expressions

A+B*(C+D)
((A>B) OR (B>C)) AND (C>D)
The expression (C+D) is a nested expression which is
evaluated first. Multiple nesting is permitted, with the
innermost nesting being evaluated first.

Example 1

15 - MATRIX[4]**2 + CLOCK(MIN) / 60
404 Chapter 11:
Operator Precedence

In this expression, Matrix[4]**2 is evaluated first, with

the result being subtracted from 15. This value is then
added to the value obtained from Clock(min)/60.

Example 2

(A>B) OR (A>C) AND (A=D)

would evaluate
(A>B) OR ((A>C) AND (A=D))
 ProModel 405
User Guide

Chapter 12: Routing Rules

Routing Rules
Routing rules determine the next location for the
processing entity. They are specified in the
“Rule” field of the Routing edit table. They may
be typed manually or selected from the Routing
Rule Dialog box shown below by clicking on the
Rule button. For more information about routing,
see “Routing Edit Table” on page 149.
406 Chapter 12:
Alternate

Alternate Example

After Shaft completes a 3 minute operation at Drill, it

Syntax samples routes to either Lathe1 or Lathe2 if a SEND statement
somewhere in the model directs an EntA to be sent to
ALT one of those locations. If no SEND request is waiting,
an alternate routing will route the entity to Lathe3. If
no capacity is available at Lathe3, the entity will wait
until capacity becomes available at Lathe3 or a SEND
Description statement that matches the entity and the location in
one of the SEND routings executes somewhere in the
Causes a location to be selected as an alternate model.
destination if it has available capacity and the
condition for a preceding routing rule is not met.
If the ALTERNATE location is unavailable, the
entity waits until it becomes available or until the Process Table
preceding routing rule is satisfied.
Entity Location Operation (min)
ALTERNATE routings are common to all pri- Shaft Drill WAIT 3
mary routings, except the Probability and User
Condition rules, and should therefore be listed Routing Table
after the last primary routing but before any
backup routings. Blk Output Destination Rule Move Logic
1 Shaft Lathe1 Send 1
For example, a high-speed machine might be pre- Shaft Lathe2 Send
ferred, but alternatively, a slower machine can be Shaft Lathe3 ALT
used when the faster machine is unavailable.
See Also
Valid In
See the other routing rules for exceptions and
The rule field of the Routing edit table only. An special cases. Also see “Processing” on page 143.
ALTERNATE routing may be specified after any
other type of routing (including other ALTER-
NATE routings) except for BACKUP, CON-
TINUE and DEPENDENT routings.
 ProModel 407
User Guide

Backup Example

After an entity, Chip, completes a 3 minute operation at

Syntax samples CNC, it is routed to Stamp1 when Stamp1 becomes
available. Only if Stamp1 and the alternate location
BACKUP (Stamp2) are both down will it be routed to Stamp3. If
Stamp3 is also unavailable, Chip will wait for Stamp3
only as long as both Stamp1 and Stamp2 remain down.

Description
Locations specified by this rule are selected only
Process Table
if all of the destinations (primary or alternate)
listed in the preceding routings of the same block Entity Location Operation (min)
are unavailable due to any downtime, including a Chip CNC WAIT 3
shift. One use of BACKUP is to handle a
machine that is not functioning, and entities need Routing Table
another destination to continue.
Blk Output Destination Rule Move Logic
1 Chip Stamp1 FIRST 1
Valid In
Chip Stamp2 ALT
Inside the rule field of the Routing edit table, at Chip Stamp3 BACKU
the end of a routing block, after one or more pri- P
mary routings or even an ALTERNATE rule.
Conditions for using Backup routings with either See Also
USER CONDITION and PROBABILITY rout- ALTERNATE routing rule. Also see “Process-
ing rules are given in the notes for these rules. ing” on page 143.
408 Chapter 12:
Continue

Continue Valid In
The rule field of the Routing edit table only. A
CONTINUE rule must be the only routing in a
Syntax samples
routing block and must always take a quantity of
one.
CONT 1

Example

Description This example simulates an unlimited supply of ore at a

location. After the Extract location extracts the Iron
Leaves an entity at the current location for further
from the Ore, two routing blocks execute. The first
processing. ProModel searches the process list
routing block routes the Iron just extracted on to a
forward and then from the beginning until a pro- molding location. The second routing block routes
cess is found for the output entity at the current another unit of ore back to the location, where the pro-
location. If the entity name remains the same and cess begins again.
no additional processes for that entity type are
defined at the location, the original process will
repeat continuously unless a condition bypasses
the routing block with the CONTINUE rule. Process Table
The CONTINUE routing rule also allows Entity Location Operation (min)
dynamic priority changes. This means a low pri- Ore Extract WAIT 100
ority entity that enters a location can be dynami- Iron Mold ...
cally upgraded to a higher priority without
leaving the location. Move Logic for the routing Routing Table
block with the CONTINUE rule will not be exe-
Blk Output Destination Rule Move Logic
cuted.
1* Iron Mold FIRST 1 MOVE FOR 10
Neither a time value nor a movement rescue is 2 Ore Extract CONT 1
allowed in the Move Logic column for a route ... ... ... ... ...
block containing a CONTINUE rule. This rule is
See the next example for an illustration of
one way to route an entity from a single capacity
dynamic priority changing.
location to the same location without causing a
deadlock. The CONTINUE rule can also simu-
late an unlimited supply of a raw material at a Example
location.
Dynamic Priority Changing Suppose a gear enters
Statistics for a location using the CONTINUE a location. The gear has a low priority. If another type
rule are collected as one entry for the entity. of gear enters the system with a higher priority, the sec-
ond gear may preempt the first gear. Another worker in
the plant needs the first gear immediately or else he
will miss his deadline. Now the first gear’s priority is
higher than the second gear. Using the CONTINUE
routing rule allows you to change the priority of the
first gear. An entity that enters a location with a prior-
 ProModel 409
User Guide

ity 99 can increase its priority to 999 without ever leav-

ing that location. In addition, this functionality will
also allow you to specifically control which entities in
a multi-capacity location will be preempted by another
incoming high priority entity.

Process Table
Entity Location Operation (min)
Gear Loc1 WAIT 2
Gear Loc2 WAIT 3
IF CLOCK() > 1 THEN
BEGIN
var = 999
ROUTE 2
END
ELSE ROUTE 1
Gear Loc2

Routing Table
Blk Output Destination Rule Move Logic
1 Gear Loc2, 99 FIRST 1 MOVE FOR 1
1 Gear Loc3 FIRST 1 MOVE FOR 1
2 Gear Loc2, var CONT 1
1 Gear Loc3 FIRST 1 MOVE FOR 1

See Also
“Processing” on page 143.
410 Chapter 12:
Dependent

Dependent Example

After an entity named “Lamp” completes a 3-minute

Syntax samples preparation at Prep, the paint shop will paint it. If the
paint shop has capacity, the Base routes to the paint
DEP shop and the Shade routes to the Waiting area based on
the dependent rule. But if the paint shop does not have
capacity, the lamp stays together and routes to Storage
on an alternate routing.
Description
Selects a location if, and only if, the routing
immediately preceding it is selected. An ALTER- Process Table
NATE routing which follows a dependent routing
is an alternate to the last major routing preceding Entity Location Operation (min)
the dependent condition and not to the dependent Lamp Prep WAIT 3
routing itself.
Routing Table
A dependent routing should be used when one
process results in two different types of entities Blk Output Destination Rule Move Logic
that should go to different locations. For exam- 1 Base Painting FIRST 1
ple, a dependent routing could simulate the sepa- Shade Waiting DEP
ration of a customer and his or her order placed at Lamp Storage ALT
the drive-through window at a restaurant. While
the customer continues on to the cashier window, See Also
the order is sent on to the counter for fulfillment. “Processing” on page 143.

Valid In
The rule field of the Routing edit table only. A
DEPENDENT routing may be specified after any
other routing rule (including other DEPENDENT
routings) except for a CONTINUE routing.
 ProModel 411
User Guide

Empty Example

After EntA completes a 25 second operation at Loc1, it

Syntax samples is routed to one of three multi-capacity locations
(Loc2, Loc3 or Loc4) as soon as one becomes empty.
EMPTY {<expression>} Subsequent routings continue to the same location until
it is full, and then to the next location that is empty.
Once all locations are filled, no more routings occur
until one of the locations becomes empty.
Description
Selects a location only if it is completely empty.
This routing rule is similar to the UNTIL FULL Process Table
rule except that a location must be completely
empty before it is initially selected. Once an Entity Location Operation (min)
empty location is selected, it continues to be EntA Loc1 WAIT 25 sec
selected until it is full. If no location is empty, the
output waits until one becomes empty. Routing Table
The EMPTY condition is designed for the situa- Blk Output Destination Rule Move Logic
tion where two or more multi-capacity locations 1 EntA Loc2 EMPTY 1
are being filled from the same source and the EntA Loc3 EMPTY
modeler desires each location to completely fill EntA Loc4 EMPTY
and completely empty in an alternating fashion.
See Also
Valid In “Processing” on page 143.
The rule field of the Routing edit table only.

Components

<expression>
Total entities output from the process. This expression
is valid only for the first routing of a routing block. For
more information on this expression, see “Processing”
on page 143.
412 Chapter 12:
First Available

First Available Example

After EntA completes a 4 minute operation at

Syntax samples Loc1, it is routed to Loc2, Loc3 or Loc4 depend-
ing on which location is the first to have available
FIRST {<expression>} capacity.

Description Process Table

Selects the first location available among one or
Entity Location Operation (min)
more locations listed in a routing block. Specify-
EntA Loc1 WAIT 4
ing multiple First Available routings in a routing
block has the same effect as specifying a First
Routing Table
Available routing followed by one or more
ALTERNATE routings. An example of using the Blk Output Destination Rule Move Logic
First Available rule in a routing block is given 1 EntA Loc2 FIRST 1
below. EntA Loc3 FIRST
EntA Loc4 FIRST
The First Available rule is the default rule when
defining the initial routing in the Process Editor.
See Also
In this case, the First Available routing can be
interpreted to be the “primary” routing. “Processing” on page 143.

Valid In
The rule field of the Routing edit table only.

Components

<expression>
The total entities output from the process. This expres-
sion is valid only for the first routing of a routing
block. For more information on this expression, see the
“Processing” on page 143.
 ProModel 413
User Guide

Join Example

After EntA completes a 5.2 minute operation at Loc1,

Syntax samples it routes to Loc2, Loc3 or Loc4 to join to some other
entity that issued a JOIN request for an EntA.
JOIN {<expression>}

Process Table
Description
Entity Location Operation (min)
Selects a location whenever a JOIN request is EntA Loc1 WAIT 5.2
issued at that location. Since a joining entity does
not require capacity, there is no need to check for Routing Table
available capacity at the destination. Multiple
JOIN requests are filled according to the oldest Blk Output Destination Rule Move Logic
waiting request with the highest priority. Entities 1 EntA Loc2 JOIN 1
routed with the JOIN routing rule are not actually EntA Loc3 JOIN
sent to their destination until a JOIN statement is EntA Loc4 JOIN
encountered at the destination location.
See Also
Valid In JOIN statement. Also see “Processing” on
The rule field of the Routing edit table only. page 143.

Components

<expression>
The total entities output from the process. This expres-
sion is valid only for the first routing of a routing
block. For more information on this expression, see
“Processing” on page 143.
414 Chapter 12:
Load

Load Example

After EntA completes a 3 minute operation at Loc1, it

Syntax samples is routed to Loc2, Loc3 or Loc4 to be loaded onto some
other entity that has issued a LOAD request.
LOAD {<expression>}

Process Table
Description
Entity Location Operation (min)
Selects a location whenever a LOAD request is EntA Loc1 WAIT 3
issued at the destination location. Since a loading
entity does not fill capacity, there is no need to Routing Table
check for available capacity at the destination.
Multiple LOAD requests are filled according to Blk Output Destination Rule Move Logic
the oldest waiting request with the highest prior- 1 EntA Loc2 LOAD 1
ity. EntA Loc3 LOAD
EntA Loc4 LOAD
Valid In
See Also
The rule field of the Routing edit table only.
LOAD statement. Also see “Processing” on
page 143.
Components

<expression>
The total entities output from the process. This expres-
sion is valid only for the first routing of a routing
block. For more information on this expression, see
“Processing” on page 143.
 ProModel 415
User Guide

Longest Unoccupied Example

After EntA completes a 2.5 minute operation at

Syntax samples Loc1, it routes to Loc2, Loc3 or Loc4 depending
on the location unoccupied the longest.
LU {<expression>}

Process Table
Description
Entity Location Operation (min)
Selects one of the locations listed in a block of
EntA Loc1 WAIT 2.5
routings based on which has been unoccupied the
longest. If several multi-capacity locations all
Routing Table
have one or more current entities, the location
with the most available capacity will be selected. Blk Output Destination Rule Move Logic
If no capacity is available at any location, the first 1 Plane Gate1 LU 1 MOVE FOR 2
one that becomes available is selected. This rule Plane Gate2 LU MOVE FOR 2
is useful in situations where residual effects must Plane Gate3 LU MOVE FOR 2
diminish before further usage of a location (e.g., Plane Gate4 LU MOVE FOR 2
an oven cooling to an ambient temperature, the
vapor clearing out of a paint booth, etc.). Routing Table
Please note that this routing rule is not valid for Blk Output Destination Rule Move Logic
single-capacity locations 1 EntA Loc2 LU 1
EntA Loc3 LU
Valid In EntA Loc4 LU
The rule field of the Routing edit table only.
See Also

Components “Processing” on page 143.

<expression>
The total entities output from the process. This expres-
sion is valid only for the first routing of a routing
block. For more information on this expression, see
“Processing” on page 143.
416 Chapter 12:
Most Available

Most Available Example

After EntA completes a 4 minute operation at

Syntax samples Loc1, it is routed to Loc2, Loc3 or Loc4 depend-
ing on which location has the most available
MOST {<expression>} capacity at the current time.

Description Process Table

Selects one of the locations listed in a block of
Entity Location Operation (min)
routings based on which has the most available
EntA Loc1 WAIT 4
capacity. If no capacity is available at any of the
locations listed, the first one that becomes avail-
Routing Table
able is selected. Use the MOST routing rule to
equalize queues in front of workers. This rule is Blk Output Destination Rule Move Logic
useful in cases where inventory levels need to be 1 EntA Loc2 MOST 1
balanced among several downstream queues. EntA Loc3 MOST
EntA Loc4 MOST
Valid In
See Also
The rule field of the Routing edit table only.
“Processing” on page 143.
Components

<expression>
The total entities output from the process. This expres-
sion is valid only for the first routing of a routing
block. For more information on this expression, see
“Processing” on page 143.
 ProModel 417
User Guide

Probability Example

EntA completes an eight minute operation at Loc1, and

Syntax samples routes to Loc2 80% of the time, Loc3 15% of the time,
and to Loc4 5% of the time. If EntA selects Loc2 but
<probability> {<expression>} the location has no available capacity, EntA will select
an alternate location, Loc2A. If both Loc2 and Loc2A
are down, EntA selects a backup location (Loc2B).
Loc3 has an alternate location (Loc3A) in case it is
Description unavailable, but has no backup location. Loc4 has nei-
ther an alternate location nor a backup location.
Randomly selects a location listed in a block of
routings based on a probability. Several probabil-
ity routings should be used together and the sum
of all probabilities must equal one. The entity Process Table
will wait to be routed until the selected location
has available capacity. Unlike most primary rout- Entity Location Operation (min)
ings, an ALTERNATE and BACKUP routing EntA Loc1 WAIT8
may be specified after each PROBABILITY
routing in a single routing block. If the selected Routing Table
location has no ALTERNATE routing and has no Blk Output Destination Rule Move Logic
available capacity, the entity will wait for the 1 EntA Loc2 .800 1
location until it has available capacity. EntA Loc2A ALT
EntA Loc2B BACKUP
Valid In EntA Loc3 .150
The rule field of the Routing edit table only. EntA Loc3A ALT
Claim Loc4 .050

Components See Also

<probability> “Processing” on page 143.

The chance of the routing being taken, expressed as a
decimal less than one. All probabilities in a single rout-
ing block must add up to one. This number must be a
value and may not be an expression.
<expression>
The total entities output from the process. This expres-
sion is valid only for the first routing of a routing
block. For more information on this expression, see
“Processing” on page 143.
418 Chapter 12:
Random

Random Example

After EntA completes a 3 minute operation at Loc1, it

Syntax samples is randomly routed to Loc2, Loc3, or Loc4.

RANDOM {<expression>}

Process Table

Description Entity Location Operation (min)

EntA Loc1 WAIT 3
Randomly selects one of several available loca-
tions listed in a block of routings such that each Routing Table
location having available capacity is equally
likely to be selected. If none of the locations Blk Output Destination Rule Move Logic
listed has available capacity, the first location that 1 EntA Loc2 RANDOM 1
becomes available will be selected. EntA Loc3 RANDOM
EntA Loc4 RANDOM
Valid In
See Also
The rule field of the Routing edit table only.
PROBABILITY routing rule. Also see “Process-
ing” on page 143.
Components

<expression>
The total entities output from the process. This expres-
sion is valid only for the first routing of a routing
block. For more information on this expression, see
“Processing” on page 143.
 ProModel 419
User Guide

Send Example

Purchase Orders (PO’s) are held at a holding location

Syntax samples until final approval is received. Once a SEND request
has been generated at some other location in the sys-
SEND {<expression>} tem, the PO is sent to the appropriate vendor.

Description Process Table

Causes an entity to remain at the current location Entity Location Operation (min)
until one of the listed destinations issues a SEND. PO Holding
Once a location has been selected, capacity must
be available at that location before the routing Routing Table
actually takes place. Multiple alternative SEND
destinations may be specified in a block. Blk Output Destination Rule Move Logic
1 PO VendorA SEND 1 MOVE FOR 48
Hr
Valid In
PO VendorB SEND MOVE FOR 48
The rule field of the Routing edit table only. Hr
PO VendorC SEND MOVE FOR 48
Hr
Components
See Also
<expression>
“Processing” on page 143.
The total entities output from the process. This expres-
sion is valid only for the first routing of a routing
block. For more information on this expression, see
“Processing” on page 143.
420 Chapter 12:
Turn

Turn Example

In this example, Purchase Requests (PR’s) are entered

Syntax samples into an on-line accounting system at location Key-
punch. They are then assigned on a rotating basis to
TURN {<expression>} Buyer1, Buyer2, or Buyer3.

Description Process Table

Selects the locations listed in a block of routings Entity Location Operation (min)
in rotation by availability. If none of the locations PO Keypunch WAIT U(3,1) min
listed are available, the first one that becomes
available is selected. A particular location may be Routing Table
listed more than once in a routing block if it is to
have a greater proportion of turns than the others. Blk Output Destination Rule Move Logic
1 PR Buyer1 TURN 1
Valid In PR Buyer2 TURN
PR Buyer3 TURN
The rule field of the Routing edit table only.
See Also
Components “Processing” on page 143.

<expression>
The total entities output from the process. This expres-
sion is valid only for the first routing of a routing
block. For more information on this expression, see
“Processing” on page 143.
 ProModel 421
User Guide

Until Full Example

In this example, pallets are scanned at a barcode loca-

Syntax samples tion before being placed in storage in a warehouse.
The policy at the warehouse calls for keeping Aisle1
FULL {<expression>} completely full before storing anything in Aisle2.
Similarly, Aisle2 must be kept full before storing any-
thing in Aisle3.

Description
This rule continues to direct all output to the first
Process Table
location specified until it fills to capacity and
then to the next location until it fills and so on. If Entity Location Operation (min)
all locations are full, the first one that becomes Pallet Barcode USE Scanner FOR U(2.3,4)
available is selected.
Routing Table
Valid In
Blk Output Destination Rule Move Logic
The rule field of the Routing edit table only. 1 Pallet Aisle1 FULL 1 MOVE FOR
5
Components Pallet Aisle2 FULL MOVE FOR
6
Pallet Aisle2 FULL MOVE FOR
<expression> 7
The total entities output from the process. This expres-
sion is valid only for the first routing of a routing See Also
block. For more information on this expression, see
“Processing” on page 143.
“Processing” on page 143.
422 Chapter 12:
User Condition

User Condition Components

<Boolean expression>
Syntax samples
Any expression which evaluates to TRUE or FALSE.
<Boolean expression> {<expression>} <expression>
The total entities output from the process. This expres-
sion is valid only for the first routing of a routing
block. For more information on this expression, see
Description “Processing” on page 143.
Selects one of several locations listed in a routing
block based upon a user-defined condition. Sev-
eral User-Condition routings usually are used in Example
the same routing block. At least one of the user-
defined conditions in a block must be true or an Customers bring their cars to a local service station for
error message will appear and the simulation will emissions testing and state inspection. After each car
terminate. Capacity must be available at the loca- completes a 10-minute inspection operation at location
tion before the routing actually takes place. Inspect, they are put in the proper service bay depend-
Unlike most primary routing rules, an ALTER- ing on the car’s engine type. Late-model (post-1975)
NATE or BACKUP routing may be specified cars are tested in Bays 1 and 2, pre-1975 cars are tested
after each USER CONDITION routing in the in Bay3, and diesel engine cars are tested in Bay4. If
Bay1 is selected but not available, an alternate location
same routing block.
(Bay2) is selected. If both Bay1 and Bay2 are down, a
backup location (Bay3) is selected. Bay3 also has an
alternate location (Bay4) in case it is unavailable, but
has no backup location. Bay4 has neither an alternate
location nor a backup location.

Valid In
The rule field of the Routing edit table only.
 ProModel 423
User Guide

Process Table
Entity Location Operation (min)
CAR Inspect WAIT 10

Routing Table
Destinatio
Blk Output n Rule Move Logic
1 CAR Bay1 IF Type=1 1
CAR Bay2 ALT
CAR Bay3 BACKUP
CAR Bay3 IF Type=2
CAR Bay4 ALT
CAR Bay4 IF Type=3

See Also
“Processing” on page 143.
424 Chapter 12:
User Condition
 ProModel 425
User Guide

Chapter 13: Logic Elements

Functions Resource-Specific System Functions

Functions return information such as a location’s Resource-specific system functions may only be
capacity, the amount of time the simulation has used in resource node logic when a resource
been running, or a random number. A function is enters or leaves a node.
a keyword followed by parentheses, which may
contain data that the function needs to complete Downtime-Specific System Functions
its operation. You should be aware that if a func- ProModel permits you to use downtime-specific
tion or variable expecting an integer gets a real system functions only in downtime logic.
number, it will ignore everything to the right of
the decimal point.
Shift & Break System Functions
ProModel allows you to use these functions only
System Functions in shift and break logic.
The following list describes the function types
available in ProModel.
General Functions
General System Functions
Math Functions
General system functions return information
about the simulation, such as the length of time Math functions are built-in functions used for
that the simulation has run, and may be refer- performing mathematical operations on numeric
enced in any numeric expression. expressions.

Entity-Specific System Functions Type Conversion Functions

Entity-specific system functions return informa- When two types of numbers are used in an
tion about the processing entity, such as the num- expression, as when a real value is assigned to an
ber of entities in an entity group. For that reason, integer variable, they must all be converted to the
these functions may be used only where an entity same type before ProModel can evaluate them.
is processing some type of logic. This includes ProModel performs this conversion automatically
Arrival, Operation, and Location Exit logic. and, in most instances, this conversion will be
satisfactory. The only place where the user may
want to use a different conversion is when Pro-
Model converts from a real to an integer.
426 Chapter 13:
Statements

When converting from a real to an integer, Pro- There are two subsets of operation statements:
Model ignores everything to the right of the deci- entity-related and resource-related. Entity-
mal point. When converting from an integer to a related operation statements perform specific
real, ProModel simply adds a decimal point to the actions on entities only. Resource-related opera-
integer. ProModel handles name-index numbers tion statements involve resources alone (for
exactly like integers. Most often, these automatic example, GET and FREE) or resources and enti-
conversion will be sufficient, but occasionally it ties together (for example, USE).
will be necessary to convert between the types
differently. For these situations, use the conver- Statement Blocks
sion functions.
A statement block is a group of statements that
begin with the keyword BEGIN, or the symbol
Statements “{”, and end with the keyword END, or the sym-
bol “}”. Two examples appear below. See BEGIN
Statements cause ProModel to take some action and END for more extensive examples of state-
or perform some operation. Unlike functions,
ment blocks.
statements neither return a value nor use paren-
theses, and logic may contain comments. (See
“Comments” on page 451.) Statements can use Statement blocks
spacing (including a new line) before each word
in a statement, and are case insensitive so any let- BEGIN {
ter may be either upper or lower case. Statement 1 Statement 1
Statement 2 Statement 2
General Action and Control
Statement 3 Statement 3
Statements
... ...
General statements can be divided into two main
Statement n Statement n
categories: action and control statements. They
are called general because they can be used in END }
any logic. Action statements cause some action to
occur in the model, such as changing an entity’s
graphic or writing to a file. Control Statements
determine the next statement to be executed, such
as loops, branches, and statement blocks.

Resource- and Entity-Related

Operation Statements
Operation Statements perform specific actions on
entities and resources at locations throughout the
system whenever they are encountered by an
entity in the operation logic. They are valid only
in certain areas. See each statement for a list of
places where it is valid.
 ProModel 427
User Guide

Distribution Functions
Distribution functions are built-in functions
which, in conjunction with streams, return ran-
dom values according to a statistical distribution.
The following table is a summary of available
distribution functions. They are valid in any
numeric expression.

Distribution Syntax Individual Components

Beta B(a,b,c,d{,<s>}) a=shape value 1, b=shape value 2, c=lower boundary, d=upper
boundary
Binomial BI(a,b{,<s>}) a=batch size, b=probability of “success”
Erlang ER(a,b{,<s>}) a=mean value, b=parameter
Exponential E(a{,<s>,<ax>}) a=mean
Gamma G(a,b{,<s>,<ax>}) a=shape value, b=scale value
Geometric GEO(a{,<s>}) a=probability of “success”
Inverse Gaussian IG(a,b{,<s>,<ax>}) a=shape value, b=scale value
Lognormal L(a,b{,<s>,<ax>}) a=mean, b=standard deviation
Normal N(a,b{,<s>}) a=mean, b=standard deviation
Pearson5 P5(a,b{,<s>,<ax>}) a=shape value, b=scale value
Pearson6 P6(a,b,c{,<s>,<ax>}) a=shape value 1, b=shape value 2, c=scale value
Poisson P(a{,<s>}) a=quantity
Triangular T(a,b,c{,<s>}) a=minimum, b=mode, c=maximum
Uniform U(a,b{,<s>}) a=mean, b=half range,
User-defined <name>({<s>}) Name of a user-defined distribution as defined in the User Distri-
bution section
Weibull W(a,b{,<s>,<ax>}) a=shape value, b=scale value

General Components time shift the entire distribution. Any time an axis
shift is specified, a stream must be specified also.
<s> The optional stream to use in conjunction
with the distribution’s probabilities. If this option Any negative value returned by a distribution that
is omitted, ProModel will use stream one. For is used for a time expression will be automati-
more information on streams, see “Streams” on cally converted to zero.
page 258.
<ax> An optional axis shift. The distributions, E,
G, W, L, IG, P5, and P6 all normally have a mini-
mum value of zero. Use an axis shift to alter the
distribution’s minimum value and at the same
428 Chapter 13:
Priorities

Priorities
Many statements in this manual use <priority> as
a component. A priority determines the order in
which competing commands are fulfilled. For
example, priority determines which of two com-
peting requests to USE a resource gets fulfilled,
or which of two competing requests to SEND the
same entities to different locations gets fulfilled.
Commands or entities with high enough priority
can even bring back up locations that are down,
or force a location to stop processing one entity
and process another instead. This is called “pre-
emption.” All priorities must be an expression
that evaluates to a number between 0 and 999.
For a complete explanation of priorities and pre-
emption, see “Location Priorities and Preemp-
tion” on page 105, “Resource Shift Downtime
Priorities” on page 134, “Preemptive Entities” on
page 115, and “Preemption Process Logic” on
page 292.
 ProModel 429
User Guide

Chapter 14: Statements and

Functions

Accum that location will participate in the same accumu-

lation.
Entity-Related Operation Statement
Valid In
The operation column of process edit tables only.
Syntax samples
ACCUM must be used at a location with enough
capacity to accumulate the specified quantity.
ACCUM <expression>
ACCUM 10
ACCUM Var1 Components

<expression>
The number of entities to accumulate. If this expres-
Description
sion results in zero or one, it is ignored. If it results in a
Accumulates, without consolidating, the speci- number greater than the location’s capacity or a nega-
fied quantity of entities at a location. ACCUM tive number, the simulation will stop with an error.
works like a gate that prevents entities from pro- This expression is evaluated every time an entity to be
cessing until a certain number arrive. Once the accumulated arrives, so the quantity to be accumulated
specified number of entities have accumulated, can vary as the entities to be accumulated arrive. If an
they will go through the gate and begin process- entity arrives that changes this expression to a number
ing individually, independent of each other. lower than the number of entities already accumulated,
all of the accumulated entities begin to process.
ACCUM can be used to model situations where
several entities should be accumulated before
they get processed. For example, when a resource
processes orders at a work station, it may be more
Example
efficient to accumulate several orders before
requesting the resource. Entities named “Pallet” arrive at a location named
“Loading” and accumulate in batches of 20. Entities
If you specify an ACCUM operation in a process named “Box” also arrive at Loading and accumulate in
for an individual entity, accumulation will occur batches of 10. Only after the right number of boxes or
by individual entity type. However, if you specify pallets accumulates does ProModel request the forklift.
ALL as the processing entity, all entity types at The accumulation of Boxes and Pallets at Loading is
entirely independent because the accumulation state-
430 Chapter 14:
Accum

ments are in different records. Note that the forklift is

used for two minutes per pallet or box, because each
pallet and box process individually after accumulating
all of them. While the accumulation of entities at Load-
ing is by entity type, the accumulation at the location,
“Storage” is independent of entity type since the ALL
keyword denotes common processing for all entities at
this location.

Process Table
Entity Location Operation (min)
Pallet Loading ACCUM 20
USE ForkliftFOR 2
Box Loading ACCUM 10
USE Forklift FOR 2
ALL Storage ACCUM 30

Routing Table
Blk Output Destination Rule Move Logic
1 Pallet Storage FIRST 1 MOVE FOR 5
1 Box Storage FIRST 1 MOVE FOR 5
1 ALL Loc3 FIRST 1 MOVE FOR 5

See Also
COMBINE, JOIN, and GROUP.
 ProModel 431
User Guide

Activate Components

General Action Statement <subroutine>

The name of the subroutine to run. This name should
Syntax samples appear exactly as if the subroutine were being called
normally. Any return value for this function is ignored.
See “Subroutines” on page 238.
ACTIVATE <subrou-
tine>({parameter1>,<parameter2>...}) <parameters>
ACTIVATE Sub1() The parameters that the subroutine normally takes.

Description
Example
Starts an independent subroutine. The calling
logic then continues without waiting for the This example uses ACTIVATE in a model’s initializa-
called subroutine to finish. Therefore, indepen- tion logic to start a subroutine named Res_Log().
dent subroutines can run in parallel with the logic Res_Log() is a user-defined subroutine that logs every
that called them. Independent subroutines are not time that all units of a resource named Worker are in
entity or location dependent and run without use. After it logs the time that all units were busy, it
regard to what happens inside the logic that waits ten minutes to check again. Note that the
called them. WHILE...DO loop in the subroutine is never exited.
This technique allows the subroutine to run during the
Use ACTIVATE to process logic that has WAIT entire simulation.
or WAIT...UNTIL statements when you do not Initialization Logic:
want to use an entity to process the WAIT or Activate Res_Log()
WAIT...UNTIL statements. For example, an
Res_Log()
ACTIVATE in the initialization logic could call a
INT X = 1
subroutine that adjusts the arrival frequency for a
WHILE X = 1 DO
type of entity depending on the time of day. BEGIN
Independent subroutines called with ACTIVATE IF FREEUNITS(Worker)=0
cannot use entity-specific or location-specific THEN LOG "All workers busy at ",0
WAIT 10
system functions. If the subroutine has a return
END
value, then that value is ignored. External subrou-
tines cannot be called with ACTIVATE, although
they may be called from within an activated sub- See Also
routine. XSUB(). Also see “Subroutines” on page 238.

Valid In
Any logic.
432 Chapter 14:
Animate

Animate allows the modeler to more easily view which resource

(RES1 or RES2) is captured to service the location.

General Action Statement

Syntax samples

ANIMATE <expression>
ANIMATE 70
ANIMATE Var1

Description
Sets the simulation’s animation speed. The higher
the value, the faster the animation. ANIMATE is
used primarily to speed up or slow down a model
for cursory or detailed observation whenever a
See Also
particular condition is encountered. Another
common use is to set the animation speed to one- GRAPHIC and SOUND.
hundred in the Initialization Logic to rapidly
advance the simulation to some point in time.

Valid In
Any logic.

Components

<expression>
The new speed of the animation. This expression can
be any number from 0 to 100 and is evaluated every
time the ANIMATE statement is encountered. The
default speed is 56.

Example

This example shows the use of the ANIMATE state-

ment in the downtime logic for the location Press.
Whenever Press goes down for service, the animation
speed is slowed to 30 percent of maximum. This
 ProModel 433
User Guide

ArrayDims()
General System Function

Syntax samples

ARRAYDIMS(<arrayname>)
ARRAYDIMS(MyArray)

Description
Returns the number of dimensions in an array.

Valid In
Any Logic

Components

<arrayname>
The name of the array for which you wish to know the
number of dimensions.

See Also
ArrayDimSize().
434 Chapter 14:
ArrayDimSize()

ArrayDimSize()
General System Function

Syntax samples

ARRAYDIMSIZE(<arrayname>, <dim_num>)
ARRAYDIMSIZE(MyArray, 2)

Description
Returns the size of a dimension in an array. You
must provide the name of the array and the partic-
ular dimension of the array for which you want to
know the size.

Valid In
Any Logic

Components

<arrayname>
The name of the array.
<dim_num>
The number of the dimension for which you wish to
know the size.

See Also
ArrayDims().
 ProModel 435
User Guide

Assignment Statement
Syntax samples

<variable, array element, or attribute> = <numeric

expression>

Description
Assigns the value of a numeric expression to a
designated variable, array element, or attribute.

Valid In
Any Logic

Example

Var1 = 300
Attr2 = Clock(hr) - Attr3

Please Note

If you assign an expression that evaluates to a

real number to a variable, array, or attribute of
type integer, the number truncates unless you use
the ROUND() function.
436 Chapter 14:
Begin

Begin IF Attr1 = 1 THEN

BEGIN
General Control Statement ORDER 10 EntA
INC Var1
Syntax samples END
Just as in the logic above, if Attr1 in the following
BEGIN or {
example equals one, ten entities are ordered. However,
Var1 increments regardless of the value of Attr1. The
WHILE FREECAP(Loc1) > 5 DO IF...THEN applies only to the very next statement, no
BEGIN matter how you format the logic.
INC Var2, 5 IF Attr1 = 1 THEN
WAIT 5 sec
ORDER 10 EntA
END
INC Var1

IF Var1 > 5 THEN

{
INC Var2, 5 See Also
WAIT 5 sec
} END, IF...THEN...ELSE, DO...WHILE,
WHILE...DO, and DO...UNTIL.

Description
Defines a statement block with a corresponding
END statement. BEGIN and END are almost
always used in conjunction with other control
statements such as IF...THEN and DO...WHILE.
Every BEGIN statement must pair with an END
statement.

Valid In
Any logic.

Example

Compare the following logic examples:

The example below includes a BEGIN and END state-
ment. In this logic, if the attribute Attr1 equals one, ten
entities are ordered and the variable Var1 increments.
ProModel executes the statements within the BEGIN
and END only if Attr1 equals one.
 ProModel 437
User Guide

Break Process Table

Entity Location Operation (min)
General Control Statement Claim Station1 WHILE V1<3 DO
BEGIN
WAIT 3 min
Syntax samples IF V3<=5 THEN
BEGIN
BREAK WAIT 3 min
BREAK
END
WAIT 5 min
END
Description //Break to here
Exits the innermost WHILE...DO, DO...WHILE,
or DO...UNTIL loop. The next statement to be Routing Table
executed will be the one immediately following Blk Output Destination Rule Move Logic
the END statement associated with the innermost 1 EntA Station2 FIRST 1 MOVE FOR 5
loop. If a BREAK is encountered outside any
loop, then ProModel exits the entire logic. See Also

Valid In BREAKBLK.

Any logic.

Example

Normally, a WHILE...DO loop repeats a statement

block until a certain condition becomes false. This
example shows the use of a BREAK statement to exit
the loop based on a condition not included in the
WHILE...DO loop. As long as the variable V1 is less
than three and the variable V3 is less than or equal to
five, both the three-minute wait and the five-minute
wait will be executed for a total of eight minutes. How-
ever, if V3 becomes greater than five, the total wait
will be six minutes: three minutes in the main part of
the loop and another three minutes inside the
IF...THEN statement block. The five minute wait will
not be executed because the BREAK statement exits
the loop entirely.
The line “//Break to here” is a comment that marks the
next line of logic executed after the BREAK.
438 Chapter 14:
BreakBlk

BreakBlk Process Table

Entity Location Operation (min)
General Control Statement ALL Shipping IF ENTITY() = Letter THEN
INC No_of_Let
IF ENTITY() = Pkg THEN
Syntax samples BEGIN
INC No_of_Pkg
BREAKBLK IF Attr1 = 1 THEN
BREAKBLK
USE Wrapper FOR 8
Attr1 = 1
END
Description //Breakblk to here
USE Addresser FOR 3
Exits from the innermost statement block. The
next statement to be executed will be the one
immediately following the END statement of the Routing Table
innermost statement block. If a BREAKBLK is Blk Output Destination Rule Move Logic
executed outside any statement block, ProModel 1 ALL Post_Office FIRST 1 MOVE FOR
will exit the logic completely. 5

Valid In See Also

Any logic. BREAK.

Example

This example uses BREAKBLK in the logic for a ship-

ping department that handles two types of entities, Let-
ters and Packages. Both packages and letters need to be
addressed, but packages may need to be wrapped
before they are addressed. When a package arrives,
shipping increments the variable No_of_Pkg to keep
track of the number of packages it ships. Attr1 is then
checked to see if the package has been wrapped. If the
package has been wrapped (if Attr1 = 1), the BREAK-
BLK statement exits the statement block that wraps
packages. If the package has not been wrapped, a
resource, Wrapper, wraps the package. Finally, all enti-
ties that Shipping processes are addressed by the same
statement and routed to the location Post_Office. The
line
“// Breakblk to here” is a comment which marks the
next statement executed after the BREAKBLK.
 ProModel 439
User Guide

CalDay() Example

General System Function Suppose that shipment arrival types vary from day to
day. Since Monday’s Shipment_Type_A arrival pat-
terns are unique, you will need to use a distribution
Syntax samples specific to those patterns.
IF CALDAY()=1 THEN
CALDAY()
BEGIN
Shipment_Type_A =
Monday_Distribution_A
Description USE Forklift FOR Unload_Time
END
The CALDAY() function corresponds to the
weekday of the calendar date you defined as part
of the warm-up period or simulation begin date
under simulation options. Since CALDAY() See Also
resets with the advent of a new week, every CALDOM(), CALHOUR(), CALMIN(), CAL-
weekday will return the same value (i.e., Wednes- MONTH(), and CALYEAR().
day will always return a value of 3).

Valid In
Any logic.

Please note

CALDAY() works only when you select calendar

date in the simulation options dialog.
440 Chapter 14:
CalDOM()

CalDOM()
General System Function

Syntax samples

CALDOM()

Description
The CALDOM() function corresponds to the cal-
endar day of the month you defined as part of the
warm-up period or simulation begin date under
simulation options. Values returned by this func-
tion will be integers in the range of 1 to 31.

Valid In
Any logic.

Please note

CALDOM() works only when you select calendar

date in the simulation options dialog.

See Also
CALDAY(), CALHOUR(), CALMIN(), CAL-
MONTH(), and CALYEAR().
 ProModel 441
User Guide

CalHour() See Also

CALDAY(), CALDOM(), CALMIN(), CAL-
General System Function MONTH(), and CALYEAR().

Syntax samples

CALHOUR()

Description
The CALHOUR() function corresponds to the
hour of the calendar date you defined as part of
the warm-up period or simulation begin date
under simulation options. Since this function ties
directly to the 24-hour clock displayed on the
screen during simulation, CALHOUR() will
never return a value higher than 23.

Valid In
Any logic.

Please note

CALHOUR() works only when you select calen-

dar date in the simulation options dialog.

Example

The following example implements a change in per-

sonnel used to perform an operation. After the simula-
tion runs for 18 hours, the technician becomes
available to perform the activity.
IF CALHOUR() > 18 THEN
USE Worker FOR N(10,4)
ELSE USE Technician FOR N(8,2)
442 Chapter 14:
CalMin()

CalMin() See Also

CALDAY(), CALDOM(), CALHOUR(), CAL-
General System Function MONTH(), and CALYEAR().

Syntax samples

CALMIN()

Description
The CALMIN() function corresponds to the
minute of the calendar date you defined as part of
the warm-up period or simulation begin date
under simulation options. Since this function ties
directly to the 24-hour clock displayed during
simulation, CALMIN() will never return a value
higher than 59.

Valid In
Any logic.

Please note

CALMIN() works only when you select calendar

date in the simulation options dialog.

Example

Suppose parts have a fixed shipping time of 4:30 PM.

The following logic would order parts to the shipping
area.
IF CALHOUR() = 16 AND CALMIN() = 30 THEN
ORDER 1 Part TO Shipping_Area
 ProModel 443
User Guide

CalMonth()
General System Function

Syntax samples

CALMONTH()

Description
The CALMONTH() function corresponds to the
month of the year you defined as part of the
warm-up period or simulation begin date under
simulation options. Values returned by this func-
tion will be integers in the range of 1 to 12.

Valid In
Any logic.

Please note

CALMONTH() works only when you select calen-

dar date in the simulation options dialog.

Example

If CalMonth()=12 THEN WAIT 20

Else Wait 10

See Also
CALDAY(), CALDOM(), CALHOUR(),
CALMIN(), and CALYEAR().
444 Chapter 14:
CalYear()

CalYear()
General System Function

Syntax samples

CALYEAR()

Description
The CALYEAR() function corresponds to the
year of the calendar date you defined as part of
the warm-up period or simulation begin date
under simulation options.

Valid In
Any logic.

Please note

CALYEAR() works only when you select calendar

date in the simulation options dialog.

See Also
CALDAY(), CALDOM(), CALHOUR(),
CALMIN(), and CALMONTH().
 ProModel 445
User Guide

Cap() Example

General System Function The individual ovens of a ceramics plant have different
capacities, but otherwise they are exactly the same.
While each oven could be modeled as an individual
Syntax samples location, it would be easier to model this situation as a
multi-unit location. This example uses CAP() in the
CAP (<location>) processing logic of the parent location to accumulate
enough Sinks to fill each oven. The LOCATION()
GROUP CAP(Loc1) function returns the value of the current location.

Description Process Table

Returns the total capacity of a location. CAP()
Entity Location Operation (min)
can be used to prepare a batch of entities to fill a
Sink Oven ACCUM CAP(LOCATION())
location.
Routing Table
Valid In
Any logic and any expression evaluated after Blk Output Destination Rule Move Logic
translation. For a list of expressions evaluated 1 Sink Cool FIRST 1 MOVE FOR
5
after translation, see the “Appendix A” on
page 577.
See Also

Components FREECAP(), LOC(), and LOCATION().

<location>
The name of the location to examine. If this component
is the name of a multi-unit location, CAP() will return
the capacity of the entire location. For example, if each
unit of a five-unit location has a capacity of five,
CAP() will return twenty-five. This component can
also be the name of an individual unit in a multi-unit
location.
446 Chapter 14:
Char()

Char() Example

String Function The logic below displays the combined cost of all the
Parts ordered through a particular service center. The
simulation has kept a tally of all the parts it has ordered
Syntax samples in the variable Parts, and each part cost 25 English
pounds. The logic displays the cost of the parts with
CHAR(<expression>) the pound symbol (£), which is ASCII code 156.
CHAR(10) DISPLAY “Total cost of parts:” $ CHAR(156) $ Parts
* 25

Description
Returns the ASCII character for the number that
the expression evaluates to. This function is most
useful for outputting ASCII characters that can-
not be typed, such as accented characters. This
function is most often used in conjunction with a
string expression and the concatenation (“$”)
operator.
The number corresponding to the ASCII charac-
ter varies with each computer depending on the See Also
character set specified in the config.sys file of “String Expressions” on page 402.
your computer. To determine the number corre-
sponding to the ASCII character at your com-
puter, run the model CHAR.MOD found in the
MODELS\REFS directory. View the file this
model generates called CHAR.TXT found in the
same directory as the model.

Valid In
Any string expression.

Components

<expression>
Any expression that evaluates to a number between 0
and 255. The expression is evaluated every time the
CHAR() function is encountered.
 ProModel 447
User Guide

Clock() Components

General System Function <time unit>

The elapsed simulation time will be returned in this
Syntax samples unit. This may be HR, MIN, SEC, DAY, WK. If omit-
ted, the value returned will be in the default time units
as specified in the General Information dialog box.
CLOCK({<time unit>}) When using CLOCK() to capture a time for later use
IF CLOCK(DAY) >= 1.5 THEN PAUSE with the LOG statement, the units should be omitted.

Attr1 = CLOCK()
See Also
“General Information” on page 171 and “Time
Description Expressions” on page 401.
Returns value of the elapsed simulation time in
the units specified. Clock units should be kept
consistent when comparing values. If an attribute
has been assigned a time in minutes, any time
value compared with that attribute should also be
in minutes.
When no units are specified in the parentheses in
the clock function, ProModel returns the default
time unit specified in the General Information.

Valid In
Any logic and most fields, except those fields
evaluated at translation. For a list of fields evalu-
ated at translation, see the “Appendix A” on
page 577.
448 Chapter 14:
Close

Close
General Operation Statement

Syntax samples

CLOSE <file ID>

CLOSE Arrival_File
CLOSE ALL

Description
Closes a file that has previously been written to
with WRITE, WRITELINE, XWRITE, or read
with READ. Use CLOSE when finished with a
file to free system resources. A file will automati-
cally be re-opened to be read or written if it has
been closed. All opened files are automatically
closed at the end of a simulation. When you are
using many external files and you want to con-
serve system resources, this statement is espe-
cially helpful.

Valid In
Any logic.

Components

<file ID>
The file ID of the desired file as defined in the External
Files editor.

See Also
READ, WRITE, WRITELINE, XWRITE, and
RESET.
 ProModel 449
User Guide

Combine Valid In
Operation logic only. COMBINE may not be
Entity-Related Operation Statement used in combination with CREATE, GROUP,
UNGROUP, LOAD, UNLOAD, SPLIT AS, or
other combine statements in the same process
Syntax samples
logic.
COMBINE <expression> {AS <new entity name>}
Components
COMBINE Var1
COMBINE 3 AS EntQ <expression>
COMBINE Var1 as ENT(Attr1) The number of entities to combine. Negative values
generate an error message. If this expression evaluates
to zero, it is ignored. If it evaluates to one, then no enti-
ties are actually combined, but the entity that encoun-
Description tered the combine statement is renamed (if the AS
option has been specified).
Accumulates and consolidates a specified quan-
tity of entities into an entity, optionally with a dif- This expression is evaluated every time an entity
ferent name. Unlike the GROUP statement, encounters the COMBINE statement, so the amount of
combined entities lose their identities and entities to be combined can vary as the simulation
attributes and cannot be ungrouped later. Use progresses. If an entity arrives that changes this expres-
sion to a number lower than the number of entities
COMBINE when several entities need to be com-
already waiting to be combined, all of the entities wait-
bined, such as when eight spark plugs are com-
ing to be combined are combined, including the entity
bined in a box. Note that after several entities that just arrived.
have been combined at a location, no additional
statistics will be collected for any of the com- AS <new entity name>
bined entities at that location. The optional name of the resulting entity. If left off, the
new entity will have the same name as the last com-
When specifying COMBINE <expression> AS bined entity or the output entity name.
<new entity name> in the operation logic, there
must be another operating block at the same loca-
tion. In this case, the incoming entity at the new Explicit Entity Actions
operating block is the new entity name specified
in the COMBINE statement. COMBINE passes cost on to new entities but not
statistical information. ProModel counts com-
bined entities as exits.
450 Chapter 14:
Combine

Example

A manufacturing plant makes computer motherboards.

After manufacture and inspection, when the mother-
boards are ready for shipping, workers combine them
into sets of twenty to distribute to the company’s cus-
tomers. A COMBINE statement will work well for this
example, because workers do not inspect or use the
individual motherboards again. At the final assembly
location, workers group motherboards into totes of
twenty, and route the totes to the shipping department.

Process Table
Entity Location Operation (min)
mboard Assembly COMBINE 20

Routing Table
Blk Output Destination Rule Move Logic
1 Tote Shipping FIRST 1 MOVE FOR 5

See Also
GROUP, ENT(), ACCUM, and LOAD. Also see
the “Attributes” on page 217.
 ProModel 451
User Guide

Comments Valid In
Any logic.
Documentation Symbols
Example
Syntax samples
The logic below has several notes to explain it. Addi-
# tionally, ProModel ignores the ELSE statement and the
ELSE statement’s block.
//
IF Parts_Available > Attr2 THEN
/*...*/
//Parts needed is stored in attribute 2
BEGIN
JOIN Attr2#Join the number of parts
Components # needed only if there are
# enough parts available.
#
WAIT Attr1
The pound sign signals the start of a one-line comment.
END
ProModel will ignore any characters on the rest of the
line. /* ELSE
// BEGIN//Start operation
Two forward slashes signal the start of a one-line com- INC Var1
ment. ProModel will ignore any characters on the rest
WAIT Attr3
of the line. This symbol works exactly the same as the
# sign. END */
/*...*/
A slash followed by an asterisk signals the start of a
multi-line comment. ProModel will ignore all charac-
ters after the “/*” until it finds an asterisk followed by a
slash, “*/”. Use this type of comment for long explana-
tions and to prevent ProModel from executing long
portions of logic during debugging. Comments using //
or # may be nested inside multi-line comments.

Description
Comments are notes to the modeler inside blocks
of logic. ProModel ignores them, but they can be
particularly useful to explain logic when more
than one person will be using a model.
452 Chapter 14:
Contents()

Contents() Example

General System Function An assembly line has a location called Clean that often
gets too busy for one operator to handle and the super-
visor then comes to help. The processing logic below
Syntax samples models this situation with an IF...THEN statement and
the CONTENTS() function. As long as the location
CONTENTS(<location>{,<entity type>}) contains fewer than five entities, a worker processes
any arriving entities. However, if the location’s con-
LOAD CONTENTS(Loc1) tents are greater than five, the Supervisor processes
JOIN CONTENTS(Loc1, EntA) EntA them.

Description Process Table

Returns either the total number of entities at a Entity Location Operation (min)
location or the number of a certain type of entity ALL Clean IF CONTENTS(Clean)<5
at a location. Use CONTENTS() to make deci- THEN
sions based on how busy a location is. Using USE Worker FOR 10
ELSE
CONTENTS() to keep track of the number of USE Worker FOR 10
entities at a location requires fewer steps and OR Supervisor FOR 10
allows more flexibility than using variables to
count the number of entities that enter and exit a Routing Table
location. For example, the second syntax does in
one statement what would require several state- Blk Output Destination Rule Move Logic
ments without the CONTENTS() function. 1 ALL Mold FIRST 1 MOVE FOR
1
Valid In
See Also
Any logic and all fields except those fields evalu-
ated at translation only. For a list of the fields FREECAP(), LOC(), ENT(), and FREEUNITS().
evaluated only at translation, see the “Appendix
A” on page 577.

Components

<location>
The name of the location to examine.
<entity type>
The optional name of the type of entity to look for. If
omitted, CONTENTS() will return the total of all enti-
ties at the location.
 ProModel 453
User Guide

Create Components

Entity-Related Operation Statement <expression1>

The number of new entities to create. This expression
Syntax samples is evaluated every time the create statement is encoun-
tered.

CREATE <expression1> {AS <entity name>} AS <entity name>

{TAKE {<expression2>} <resource>,...} The name of the new entities. ProModel will search the
CREATE 10 AS EntX process list for the new entity type and begin process-
ing them before it finishes processing the entity that
CREATE 2 AS EntB TAKE 1 Res1, 2 Res2 created them. If omitted, the entities will be named the
CREATE Var1 AS Ent(Var2) TAKE Var3 Res(Var4) same as the currently processing entity.
TAKE <expression2>
The first created entity will take any resources
Description listed here from the parent entity. This compo-
nent is optional. The second syntax example
Creates a specified number of entities in addition above creates two EntB’s. The first of the two
to the original entity and copies all attributes of will own one unit of Res1 and two units of Res2.
the original entity to each new entity. The first
entity created can optionally take any of the <resource>
resources owned by the parent entity. The newly The name of the resource whose ownership should be
created entities require no additional capacity at transferred to the first new entity. Using the keyword
the location and are processed immediately. ALL here will take all resources owned by the parent
entity.
The CREATE statement can simulate the creation
of paperwork that needs to be hand-carried to
another location to be approved while the base Explicit Entity Actions
entity continues to process. Before the base entity
can exit the location, the paperwork must be The CREATE statement forms a new entity with
approved and routed back to the original location new statistical information and cost. ProModel
where it is joined to the base entity. adds an initial cost to explicitly created entities
(i.e., entities created with the CREATE state-
Valid In ment).

The operation column of process edit tables only. Implicit Entity Actions
CREATE may not be used in combination with
LOAD, UNLOAD, GROUP, UNGROUP, SPLIT ProModel allows you to use the CREATE state-
AS, or other CREATE statements in the same ment implicitly as part of the routing definition.
processing logic. To do this, define a route block and check the
New Entity option. ProModel does NOT add an
initial cost to implicitly created entities.
454 Chapter 14:
Create

Example

The following example shows how one entity, Record,

creates two new entities. Note that there is no routing
defined in this process for the new entities, Copy. The
new entities are handled according to the logic defined
in the subsequent process.

Process Table
Entity Location Operation (min)
Record Station1 WAIT N(8,.3)
CREATE 2 AS
Copy
Copy Station1 WAIT U(3,.3)

Routing Table
Blk Output Destination Rule Move Logic
1 Record Station2 FIRST 1MOVE FOR 5
1 Copy File_Cab FIRST 1MOVE FOR 5

See Also
ORDER, SPLIT AS, ENT(), and RES().
 ProModel 455
User Guide

Debug Process Table

Entity Location Operation (min)
General Action Statement Client Recep DEBUG
IF Attr1=1 THEN
GRAPHIC
Syntax samples WAIT 5 min

DEBUG Routing Table

Blk Output Destination Rule Move Logic
1 Client Waiting FIRST 1 MOVE FOR 5
Description
During run time, the ProModel debugger would
Brings up ProModel’s debugger. Use DEBUG to appear displaying the following information:
step through logic one statement at a time and
examine variable and attribute values while
developing a model. After a model is working,
DEBUG statements are generally removed.

Valid In
Any logic.

Example

If you were having trouble with a Client’s logic at a

particular location, we could start the processing logic
with a DEBUG statement, as in the following example.
This would allow you to watch each Client’s logic exe- See Also
cute, statement by statement, revealing problems with
the logic’s flow. “Debug Option” on page 347.
456 Chapter 14:
Dec

Dec Example

General Operation Statement The example below shows two variables decremented
in exit logic. The variable Num_in_system is decre-
mented by one, while variable Var3 is decremented by
Syntax samples 20.

DEC <name>{, <expression>}

DEC Var1
DEC Attr1, 5

Description
Decrements a variable, array element, or attribute
by the value of a specified numeric expression.
To decrement a variable, attribute, or array ele-
ment when the current entity actually leaves a
location, use DEC in the move logic.

Valid In See Also

Any logic. INC. Also see “Numeric Expressions” on
page 399.
Components

<name>
Any variable, array element, or attribute.
<expression>
The amount to decrement the value. If this expression
is omitted, the value will be decremented by one. This
can be a negative number.
 ProModel 457
User Guide

Display Example

General Action Statement This simple example displays the value of both Var1
and of Attr1 if Attr2 is 1. This logic will display the
dialog box below if Attr2 is 1. If Attr2 is not 1, an error
Syntax samples message will appear.
Operation (min)
DISPLAY <string expression>
IF Attr2=1 THEN
DISPLAY “Var1 =” $ Var1 $ “and Attr1 =” $ Attr1
DISPLAY “Var1 =” $ Var1 $ “\nand Attr1 =” $ Attr1
DISPLAY “Now beginning 100th process”
ELSE
DISPLAY Number_in_Queue
DISPLAY “Error”

Description
Pauses the simulation and displays a message.
The simulation will resume when the user selects
OK. The concatenation operator ($) should be
used to combine a numeric value into the string
(as in the first syntax example above). Using the
ENT(), LOC(), and RES() functions will display
the name of the entity, location, or resource.

Valid In Please note

Any logic.
The “\n” character starts new lines.
Components

<string expression>
See Also
The message to be displayed. To display a numeric
value, use the concatenation operator ($) as in the first PROMPT, PAUSE, CHAR(), and FORMAT().
syntax example.
458 Chapter 14:
Do...Until

Do...Until <Boolean expression>

As long as this expression is FALSE, the loop will con-
tinue. This expression is evaluated for each iteration of
General Control Statement
the loop.

Syntax samples
Example
DO <statement block> UNTIL <Boolean expression>
A machining station can manufacture parts of increas-
DO INC Var1 UNTIL Array1[Var1] <> 10 ing complexity from the same entity, called a Blank.
When a Blank arrives at the station, the value stored in
Attr1 determines the complexity of the part and the
DO amount of time needed to create the new part. The fol-
lowing logic models this situation with a DO...UNTIL
BEGIN loop. All blanks that arrive go through a five minute
INC Var2, 5 processing time, and then go through the operation
several more times depending on the value of Attr1.
WAIT 5 sec
END
UNTIL FreeCap(Loc1) > 5
Process Table
Entity Location Operation (min)
Blank Machining INT Count = 0
Description DO
BEGIN
Repeats a statement or statement block continu-
WAIT 5 min
ously while a condition remains false. INC Count
DO...UNTIL is an exit-condition loop, meaning END
that the loop will always be executed at least UNTIL Count = Attr1
once. Use DO...UNTIL when an operation will
always be executed at least one time and possibly Routing Table
more times.
Blk Output Destination Rule Move Logic
1 Base Painting FIRST 1
Valid In
Any logic. See Also
BEGIN, END, DO...WHILE, and WHILE...DO.
Components

<statement block>
The statement or block of statements to execute.
 ProModel 459
User Guide

Do...While Components

General Control Statement <statement block>

The statement or block of statements to execute.
Syntax samples <Boolean expression>
As long as this expression is TRUE, the loop will con-
DO <statement block> WHILE <Boolean expression> tinue. This expression is evaluated for each iteration of
the loop.
DO INC Var1 WHILE Array1[Var1] <> 10
DO
BEGIN Example
INC Var2, 5
WAIT 5 sec The logic below orders a minimum of ten cases to loca-
END tion Receiving every time it is encountered. As long as
WHILE FreeCap(Loc1) > 5 the location has a capacity greater than ten, it will send
additional sets of ten entities to the location.
DO
ORDER 10 Cases to Receiving
Description
WHILE FREECAP(Receiving) > 10
Repeats a statement or statement block continu-
ously while a condition remains true.
DO...WHILE is an exit-condition loop, meaning
that the loop will always execute at least once. See Also
Use DO...WHILE for processes that must be exe- BEGIN, END, DO...UNTIL, and WHILE...DO.
cuted one time and possibly more.

Please note

Use caution when using a DO...WHILE with a

system function (e.g., FREECAP()) to ensure that
the system does not enter an infinite loop. For
example, eliminating the “WAIT 5 sec” in the
syntax sample will cause the system to enter an
infinite loop because there is no time delay within
the loop.

Valid In
Any logic.
460 Chapter 14:
Down

Down Please Note

The DOWN statement does not need to be called
Downtime-Specific System Function from the processing logic at the location that is to
go down. It can be called from any logic in your
model, except Initialization and Termination
Syntax samples
logic, and still cause the location’s Called Down-
time to execute.
DOWN <dtname>, {<priority>}
See Also
“Called Downtime Editor” on page 105, and
Description “Location Priorities and Preemption” on
Makes a location, with the specified called down- page 105.
time, attempt to go down.
This statement is used in conjunction with the
Called Downtime dialog, where you have previ-
ously defined the called downtime’s name, prior-
ity, and logic.
When this statement is executed, the called
downtime will attempt to execute its logic. The
timing of the execution of the called downtime’s
logic will depend on the location’s state and the
called downtime’s priority.

Valid In
Any logic, except Initialization and Termination
logic.

Components

<dtname>
The name of the called downtime. This name is
defined in the Called Downtime dialog, found in the
Locations table.
<priority>
You may optionally define a priority. This will override
the priority you defined in the Called Downtime dialog
for the specified called downtime.
 ProModel 461
User Guide

DownQty() Example

General System Function Two resources, Welders, weld brackets onto steel
frames at a location, Man_Weld, in 6.5 minutes. An
automatic welding machine, Auto_Weld, can perform
Syntax samples the same task, but it takes 9.3 minutes. However, if
only one Welder is available and the other Welder is
DOWNQTY(<location> or <resource>>) down (e.g., on break), it takes one Welder 13.0 minutes
to weld the brackets to the frames. Therefore, if one
IF DOWNQTY(Loc1) > 3 THEN ROUTE 2 Welder is down, the frames should route to the auto-
DISPLAY “Total Res1 Down Now:” $ DOWN- matic welding machine, Auto_Weld.
QTY(Res1)

Process Table
Description
Entity Location Operation (min)
Returns the number of location or resource units Frame Buffer IF DOWNQTY(Welder)>0
down at the time of the call. Use this function to THEN
make decisions based on how many resource or ROUTE 1
location units are down. For example, if too many ELSE
ROUTE 2
units are down, a foreman could preempt several
Frame Auto_Weld ...
units back into service. Frame Man_Weld ...

Valid In
Routing Table
Any logic and all fields except those fields evalu-
Blk Output Destination Rule Move Logic
ated at translation only. For a list of the fields
1 Frame Auto_Weld FIRST 1 MOVE FOR 1
evaluated only at translation, see the “Appendix
2 Frame Man_Weld FIRST 1 MOVE FOR 1
A” on page 577.
... ... ... ... ...
... ... ... ... ...
Components
See Also
<location>
FREECAP, FREEUNITS(), and UNITS().
The name of the location to examine. LOC() can be
substituted for the name of a location.
<resource>
The name of the resource to examine. RES() can be
substituted for the name of a resource.
462 Chapter 14:
DTDelay()

DTDelay() Example

Downtime-Specific System Function The following statement models a situation where a

location is supposed to go down at 12:00 and always
goes back up at 1:00, even if it stays up past 12:00 to
Syntax samples finish processing an entity. If the downtime was missed
entirely (meaning that the downtime delay was greater
DTDELAY(<time unit>) than an hour), then the downtime takes no time at all. If
the downtime was not missed entirely, then it lasts one
WAIT Att1 - DTDELAY(Min) hour minus the delay.
DISPLAY “The downtime delay was”$DTDe- IF 60 - DTDelay(min) > 0 THEN WAIT (60 - DTDe-
lay(DAY)$“days.” lay(min))

Description See Also

Returns the difference between the time when DOWNQTY().
you scheduled a non-preemptive downtime to
occur and the time it actually occurred. Use
DTDelay to determine if downtimes are being
postponed because of incompleted work. You can
use DTDelay in downtime logic to ensure that a
location comes back up at a specific time.
Also returns the difference between the time
when a downtime is preempted and the time it
resumes.

Valid In
Any downtime logic including off-shift and break
logic. This function returns a real number.

Components

<time unit>
The function will return the downtime delay in any of
the following units: SEC, MIN, HR, DAY, and WK.
 ProModel 463
User Guide

DTLeft() Example

Shift & Break System Function Suppose a technician is frequently working on a job
when the end of the shift rolls around and that the pri-
ority for ending the shift is not high enough to interrupt
Syntax samples the job. To ensure that the technician gets a minimum
of 14 hours off before coming back to work, even
DTLEFT <time units> though the shift file specified 16 hours between shifts,
you could enter the following off-shift logic:
Shift_Time = DTLeft()
IF DTLEFT(hr) < 14 THEN
BEGIN

Description WAIT 14 hr
SKIP
The DTLEFT function returns the balance of the
off-shift or break time remaining for a location or END
resource before it resumes normal activities.
Unless passed as an argument (e.g., DTLeft(hr)),
the return value uses the time units defined in the
General Information Dialog (see “General Infor- Please note
mation” on page 171).
In the above example, the SKIP statement is
Valid In important to skip over the defined time in the shift
file.
This function can only be referenced in off-shift
and break logic (either the pre-start or main
logic).
See Also
Components
DTDELAY()
<time units>
The time units, if different from the default found in
the General Information dialog, in which you want the
return value expressed.
464 Chapter 14:
DynPlot()

DynPlot() Example

General Action Statement You are giving a presentation to management. Two

hours into the simulation, you want a chart to be dis-
played showing the value of a WIP variable plotted
Syntax samples against average part cost. Four hours into the simula-
tion, you want this chart to disappear.
DYNPLOT “<chart name>” To do this, define a Chart view from the Dynamic Plots
DYNPLOT “my dynamic plot name” dialog, naming your Chart view “WIP vs Cost.” Define
DYNPLOT “Chart 1” a subroutine and call it in the initialization logic using
DYNPLOT “” the ACTIVE statement. Enter the following logic in
the subroutine:
WAIT 2 HR
DYNPLOT “Wip vs Cost”
Description
Wait 2 HR
The DynPlot statement is used to automatically
turn on predefined Dynamic Plot windows. Its DYNPLOT ""
usage is similar to that of the View statement.
Dynamic Plot windows are predefined during
simulation mode. These predefined Chart views
can then be called from any logic statement, Please note
invoking the display of the designated chart dur-
ing simulation. Using the statement with a null value (no name
defined between the quotation marks) will close
Valid In all currently open Dynamic Plot windows.
Any Logic.

Components

<Chart name>
The name of the Dynamic Plot chart as defined in the
Dynamic Plots dialog. Enclose the name in quotation
marks.
 ProModel 465
User Guide

End Example

General Control Statement Compare the following examples:

The example below includes a BEGIN and END state-
Syntax samples ment in the form of the “{” and “}” symbols. In this
logic, if the attribute Attr1 equals one, ten Cases are
ordered and the variable, Var1, increments. ProModel
END or } executes the statements within the BEGIN and END
only if Attr1 equals one.
WHILE FREECAP(Loc1) > 5 DO IF Attr1 = 1 THEN

BEGIN {

INC Var2, 5 ORDER 10 Case

WAIT 5 sec INC Var1

END }
Just as in the logic above, if Attr1 in the following
example equals one, ten Cases are ordered. However,
Var1 increments no matter what the value of Attr1.
Description Without a statement block, the IF...THEN applies only
Defines a statement block along with a corre- to the very next statement, no matter how you format
the logic.
sponding BEGIN statement. BEGIN and END
are almost always used in conjunction with other IF Attr1 = 1 THEN
control statements such as IF...THEN and ORDER 10 Case
DO...WHILE. Every END must pair with a
INC Var1
BEGIN.

Valid In
Any logic. See Also
BEGIN, IF...THEN, DO...WHILE, WHILE...DO,
DO...UNTIL, and END.
466 Chapter 14:
Ent()

Ent() Example

Type Conversion Function The logic below orders three batches of five different
entity types to a location, Receiving.

Syntax samples Var1 = 1

WHILE Var1 <= 3 DO
ENT(<entity name-index number>) BEGIN
SEND 10 ENT(Var1) TO Loc1 ORDER 5 ENT(Var1) TO Receiving
DISPLAY “Ent A has been combined with” $ INC Var1
ENT(Var1)
END

Description
See Also
Converts a name-index number or integer to an
entity name. Use this function when a statement LOC(), RES(), ENTITY(), and LOCATION().
or function needs the name of an entity whose
name index number is stored in an attribute, vari-
able, or some other expression. ENT() can also be
used to vary the entity that a statement references
by using an expression for the name-index num-
ber. When used in an expression expecting a
string, such as in the second syntax example
above, ProModel will convert the name-index
number to the actual name of the entity.

Valid In
Any logic where an entity name is normally used.

Components

<entity name-index number>

The name-index number of the entity desired. This
component may be an expression which allows the ref-
erenced entity to change as the simulation progresses.
Real numbers will be treated as integers.
 ProModel 467
User Guide

Entity() Components

Entity-Specific System Function <expression>

The number of the entity in a group to inspect. For
Syntax samples example, ENTITY(3) returns the name-index number
of the third entity in the group. If this option is omitted,
the name-index number of the calling entity is
ENTITY({<expression>}) returned.
ENTITY()
ENTITY(Var1)
Example

All cars from the motor pool must be washed after use.
Description All cars except vans require ten minutes to wash, and
vans require an additional ten minutes. The logic
Returns the name-index number of the current
below models this situation.
entity or a particular entity in an entity group.
This function is especially useful in macros and
subroutines that vary depending on which entity
calls them. Use ENTITY() to determine what Process Table
type of entity is processing when an entity type of
ALL is specified at a location. For example, if a Entity Location Operation (min)
common area handles several different parts with ALL Wash1 WAIT 10 min
essentially the same process, use an IF...THEN IF ENTITY() = Van THEN
WAIT 10 min
statement in conjunction with an ENTITY() to
have individual statement blocks handle the
Routing Table
details of the operation. This function returns an
integer. Blk Output Destination Rule Move Logic
1 ALL Parking FIRST 1 MOVE FOR 30
Valid In
Speed fields, traveling time fields, conveyor See Also
speed fields, Resource fields, operation logic, ENT() and LOCATION().
routing fields, arrival logic, debug user-condition
field.
468 Chapter 14:
Entries()

Entries() Process Table

Entity Location Operation (min)
General System Function Order Stores IF ENTRIES(Loc1) = 50
THEN
Batch_Time = 0
Syntax samples
Routing Table
ENTRIES(<location>)
Blk Output Destination Rule Move Logic
DISPLAY “LocA has had” $ ENTRIES(LocA) $
1 Order Shipping FIRST 1 MOVE FOR 30
“entries.”

See Also
IF...THEN...ELSE.
Description
Returns the total entries to a location. This func-
tion returns an integer.

Valid In
Any logic and any field except those evaluated
only at translation. For a list of fields evaluated at
translation see the “Appendix A” on page 577.

Components

<location>
The location to examine.

Example

A location, Stores, sends entities, Orders, to a location,

Shipping. A variable, Batch_Time, tracks the amount
of time it takes to process 50 Orders. After Loc1 pro-
cesses 50 entities, we want to reset Batch_Time to
zero.
 ProModel 469
User Guide

Exp()
Math Function

Syntax samples

EXP(<expression>)
Real1 = EXP(Real2)

Description
Returns the exponential of an expression. This
function is equivalent to ex.

Valid In
Any expression. This function returns a real num-
ber.

Components

<expression>
EXP() returns the exponential of this expression.

See Also
LN().
470 Chapter 14:
ForLocation()

ForLocation() See Also

FORRESOURCE(). Also see “Shift & Break
Shift & Break System Function Logic” on page 297.

Syntax samples

FORLOCATION()

IF FORLOCATION() THEN Priority 100

IF FORLOCATION() THEN
INC Arr1 [1, 2]
ELSE
INC Arr1 [2, 2]

Description
This function returns TRUE if the object execut-
ing the shift or break logic is a location.

Valid In
Shift or break logic.

Example

We assign three resources (Oper1, Oper2, and Oper3)

and two locations (Mill1 and Mill2) to a shift. When
the locations go off-shift, the example uses a resource
called Maint for 10 minutes to clean up around the
machines. Because we assigned the same shift to loca-
tions and resources, we need to check if the object exe-
cuting the off-shift logic is a location. We place the
following logic in the off-shift logic:
IF FORLOCATION() THEN USE Maint FOR 10 min
 ProModel 471
User Guide

Format() digits to the right of the decimal than this number, the
excess digits will be truncated. If there are fewer digits,
ProModel will pad the number with zeros.
String Function

Syntax samples Example

FORMAT(<expression>, <total number of characters The logic below writes formatted output to a file with
in expression> {,<digits after decimal>}) XWRITE and FORMAT.
DISPLAY “The value of Var1 is” $ FORMAT(Var1, 5) XWRITE File1, “The variable Var1 is” $ FOR-
MAT(Var1,5,2)
In this example, if the value of Var1 is 378.87654, it
would be written to the file as:
Description
The variable Var1 is 378.87
Converts a number to a string in the format speci-
fied. FORMAT() should most often be used with (Two spaces)
the concatenation operator (“$”) and another
string, as in the syntax example above. Format is
often used in conjunction with the XWRITE
statement to produce formatted output. See Also
WRITE and WRITELINE.
Valid In
Any string expression.

Components

<expression>
This expression will be evaluated and converted to a
string. If the expression results in an integer, it will be
converted to a real.
<total number of characters in expression>
This expression formats the number so that it occupies
a total space equal to the number of digits before +
number of digits after the decimal + one character for
the decimal point. For example if you were to do the
following logic: XWRITE file1 Format (10.0 4 1)
XWRITE file1 Format (1.0 4 1), it will show up in
the file as 10.0 1.0 with a space before the 1.0.
<digits after decimal>
An expression that evaluates to the maximum number
of digits to the right of the decimal. If there are more
472 Chapter 14:
ForResource()

ForResource()
Shift & Break System Function

Syntax samples

FORRESOURCE()
IF FORRESOURCE() THEN GET Res1

Description
This function returns TRUE if the object execut-
ing the shift or break logic is a resource.

Valid In
All Shift or Break logic.

Example

A shift called DAYS.SFT has five resources and

eight locations assigned to it. When the resources
go off-shift, it is desired to write the resource
name and simulation time to a file called
RES_TIME. The following logic is placed in the
off-shift logic.
IF FORRESOURCE() THEN
BEGIN
XWRITE res_time, “Shift for” $ RES(Resource()) $
“ended at” $ Clock(hr) $ “.”
END

See Also
FORLOCATION(). Also see “Shift & Break
Logic” on page 297.
 ProModel 473
User Guide

Free Example

Resource-Related Operation Statement In the following example, EntA arrives at Loc1 for a
multi-step process requiring the use of resources Res1
and Res2. The first step requires the simultaneous use
Syntax samples of Res1 and Res2 for a normally distributed amount of
time. ProModel then frees Res1while Res2 performs
FREE {<quantity>} <resource>, {{quantity} the second step of the process according to a Lognor-
<resource>...} mal distribution.

FREE Res1, 2 Res2, 5 Res3A

FREE ALL
Process Table
FREE RES(Attr1)
Entity Location Operation (min)
EntA Loc1 JOINTLY GET Res1 AND
Res2
Description WAIT N(4.5,.2)
FREE Res1
Frees resources which are currently “owned” by WAIT L(3.4,.23)
the current entity. These resources must have FREE Res2
been captured through a GET or JOINTLY GET
statement. Routing Table

Valid In Blk Output Destination Rule Move Logic

1 EntA Loc2 FIRST 1 MOVE FOR 5
Location processing logic and downtime logic.
See Also
Components GET and JOINTLY GET.

<quantity>
The number of the following resource to free. A value
of zero is ignored and values less than zero result in an
error. This quantity may be any numeric expression
and is evaluated and truncated to an integer every time
the FREE statement is encountered.
<resource>
The name of the resource to free. The ALL keyword
may be used here to free all resources owned by an
entity. Any resource which is not owned by the entity
will be ignored.
474 Chapter 14:
FreeCap()

FreeCap() Example

General System Function Suppose the entities, Plates and Cams, travel through
an assembly line. The location, Assembly (capacity=1)
joins Cams with the Plates. When a Cam finishes pro-
Syntax samples cessing at Station2, it should not enter Station3 unless a
Plate is waiting to join with it further down the assem-
FREECAP(<location>) bly line at Assembly. If there is no Plate at Assembly,
another location, Buffer, sends one. The logic for Cam
SEND FREECAP(Loc1) EntA TO Loc1 at Station2 is as follows:
IF FREECAP(Assembly) = 1 THEN
SEND 1 Plate TO Assembly
Description
Returns the available capacity of a location. This
function returns an integer.
See Also
Valid In CAP().
Any logic and any field except those fields evalu-
ated only at translation time. For a list of fields
evaluated only at translation time, see the
“Appendix A” on page 577.

Components

<location>
The name of the location to examine. The LOC() func-
tion may also be used here.
 ProModel 475
User Guide

FreeUnits() Process Table

Entity Location Operation (min)
General System Function Problem Rework INT T_Size = FREUNITS(Spe-
cialist)
IF T_Size = 0 THEN T_Size = 1
Syntax samples USE T_Size Specialist FOR
Team_Time(T_Size) Hr
FREEUNITS(<location> or <resource>)
Routing Table
USE (FREEUNITS(Res1)) Res1 FOR 5 min
Blk Output Destination Rule Move Logic

Description See Also

Returns the free units of a location or resource.
UNITS(), RES(), and LOC().
Valid In
Any logic and any field except those fields evalu-
ated only at translation time. For a list of fields
evaluated only at translation time, see the
“Appendix A” on page 577.

Components

<location>
The name of the location to examine.
<resource>
The name of the resource to examine.

Example

This example uses FREEUNITS() to assign a team of

Specialists to rework a problem. The size of the team,
stored in the local variable T_Size, is determined by all
the free Specialist units. Team_Time is a table function
that varies the amount of time it takes to solve a prob-
lem (the amount of time in the USE statement) based
on the number of units on the team.
476 Chapter 14:
Get

Get continue where it left off when the resource

becomes available.
Resource-Related Operation/Move Logic Every GET must have a corresponding FREE or
Statement an error occurs when the entity exits the system.
If an entity owns one or more resources and is
Syntax samples subsequently temporarily loaded onto or grouped
with another entity, it cannot free the resource(s)
until it is unloaded or ungrouped.
GET {<quantity>} <resource> {,<priority>}
{AND or OR {quantity} <resource> {,<prior-
ity>}...} Valid In

GET Res1 Location processing, downtime, move, and shift

logic. A GET statement cannot follow a move
GET 3 Res1, 5
related statement in move logic.
GET 2 Res1OR 3 Res2
GET Res1, 3 AND (Res2 OR Res3) Components
GET Res(Skill_required)
<quantity>
The number of resources to get. A value of zero is
ignored and values less than zero return an error. This
Description numeric expression is evaluated and truncated every
Captures a specified number of resources as they time the GET statement is encountered.
become available. If the entity already possesses <resource>
one of the requested resources, the entity will still
The name of the resource to GET. You can substitute
try to capture an additional unit of that resource. RES() for the resource name.
When capturing multiple resources, each
resource will be captured as soon as it becomes <priority>
available until all resources are captured. When multiple entities are waiting for the same
resource to become available, the entity with the high-
A resource captured with the GET statement at est priority will capture the resource first. This expres-
one location and then released with a FREE state- sion should be a number between 0 and 999.
ment at another location will not be used to move
the entity between locations unless it is also spec-
ified in a MOVE WITH statement in the routing
Example
move logic. Otherwise, it is the entity that is
moving the resource from one location to the next
To start a semi-automatic welding process, we need a
and the resource will not be visible when moving
static resource named “Operator.” Midway through the
with the entity.
process, the Operator tests the weld with a resource
Resources captured by a GET statement can only named “Tester,” shared with other operators. After the
be preempted when the entity owning the test, the operator restarts the welder. The Operator
resource is undergoing a WAIT or USE time stays with the welder until he or she completes the last
part of the operation. After the welding process the
except in move logic. If the resource is pre-
empted during one of those times, the time will
 ProModel 477
User Guide

operator moves the part to the buffing area, completes

the buffing operation and then is freed.

Process Table
Entity Location Operation (min)
Assy Weld USE Operator FOR 4 min
GET Operator
USE Tester FOR U(2,.5)
WAIT 4 min
Assy Buffer WAIT T(7,10,11)
FREE Operator

Routing Table
Blk Output Destination Rule Move Logic
1 Assy Buffer FIRST 1 MOVE FOR
1.5
1 Assy Checker FIRST 1 MOVE FOR 5

See Also
JOINTLY GET and USE.
478 Chapter 14:
GetCost()

GetCost() Process Table

Entity Location Opn (min)
Cost Related Function EntA Shipping WAIT N(3,.52)
Var1=GETCOST()
Syntax samples
Routing Table
GETCOST() Blk Output Destination Rule Move Logic
1 EntA Exit FIRST 1

See Also
Description
INCENTCOST, INCLOCCOST, and SETRATE.
Returns the cost of the current entity executing
the logic. Use this function to return the entity’s
actual, accumulated dollar amount.

Valid In
Operation logic only.

Example

The following example shows how to use the GET-

COST() function to generate a Time Series plot that
tracks changing entity cost as entities exit the system.
(See table below.)
• Create a variable (e.g., Var1), select it to be of type
real, and select time series statistics.
• For any location where an entity exits the system,
place the following as the last line in operation logic:
Var1 = GETCOST()
 ProModel 479
User Guide

GetReplicationNum()
General System Function

Syntax samples

GETREPLICATIONNUM()

Description
Returns the number of the currently running rep-
lication.

Valid In
Any Logic.

Example

Based on the current replication, you may want to

make a decision regarding the exporting of array data.
In this case, you could use an IF THEN statement com-
bined with the GETREPLICATIONNUM() function to
decide what data to export based on the currently run-
ning replication.
480 Chapter 14:
GetResRate()

GetResRate() Input_Queue at the end of the day, he must stay and

finish them. Since the clerk is paid time-and-a-half for
any overtime, you must increment the cost of the
Cost Related Function resource by an additional half of the normal rate to get
the overtime rate. To do this, set a variable equal to 1 in
Syntax samples the pre-off-shift logic for the resource, indicating the
resource should go off-shift. If the variable is equal to
1, increment the cost of a resource by half the original
GETRESRATE({<resource>}) rate. (Since each unit of the clerk has a different rate,
GETRESRATE() you must obtain the cost rate for the resource owned by
the entity.)
GETRESRATE(Operator1)

Process Table
Description Entity Location Opn (min)
Returns the cost rate specified in the Cost dialog Order Order_desk GET Clerk, 399
WAIT N (4.5, .3)
or through the SETRATE() function for a
IF Off_Shift_Var=1
resource currently owned by the entity making THEN INCRESCOST
the function call. When used without the optional GETRESRATE() *.50
<resource> parameter, this function returns the FREE Clerk
cost rate of the entity’s most recently captured,
owned resource. Routing Table
If an entity owns multiple units of a resource, the Blk Output Destination Rule Move Logic
function returns the cost rate of the entity’s most 1 Order Shipping FIRST 1 MOVE FOR
recently captured resource unit. 1

Valid In See Also

Operation and move logic. GETCOST(), INCENTCOST, INCLOCCOST,
INCRESCOST, and SETRATE.
Components

<resource>
A resource currently owned by the entity making the
function call. When you use GETRESRATE without
this parameter, this function returns the cost rate of the
entity’s most recently captured, owned resource.

Example

A clerk normally works an 8-hour shift. However, if

the clerk does not finish entering all the orders in his
 ProModel 481
User Guide

Goto Process Table

Entity Location Operation (min)
General Control Statement Box Receive IF Attr1>1 THEN GOTO L1
INC V1
INC V2
Syntax samples L1:
INC V3
GOTO <label ID>
Routing Table
GOTO LabelA
Blk Output Destination Rule Move Logic
1 Box Stores FIRST 1 MOVE FOR
5
Description
Jumps to the statement identified by the desig- See Also
nated label. A label should follow the normal IF...THEN...ELSE, BREAK, and BREAKBLK.
rules for names except that it is followed by a
colon in the logic. GOTO statements may be
replaced by IF...THEN...ELSE statements.

Valid In
Any logic.

Components

<label ID>
The name of the label to switch to. Omit the colon on
the label name here.

Example

This example shows how a GOTO statement is used to

skip over the first two increment statements based on
the value of an attribute.
482 Chapter 14:
Graphic

Graphic the icon changes to Graphic 4 after the second two

minute processing time. (The difference between the
two graphics may only be color, but the two could be
General Operation Statement completely different.)

Syntax samples
Process Table
GRAPHIC <expression>
GRAPHIC 2 Entity Location Operation (min)
EntA Loc1 GRAPHIC 2
GRAPHIC Var1 WAIT 15 min
GRAPHIC 3
WAIT 25 min
GRAPHIC 4
Description
Routing Table
Changes the entity’s or resource’s current
graphic. Entities and resources are assigned Blk Output Destination Rule Move Logic
graphics from the graphics library in the Entity or 1 EntA Loc2 FIRST 1 MOVE FOR
Resource editor. Use the GRAPHIC to show the 5
result of a process. For example, when a cus-
tomer sits down, the graphic could change from a See Also
standing person to a sitting person. “Entities” on page 112 and “Resources” on
page 126.
Valid In
When used in node entry, node exit, and
resource-downtime logic, GRAPHIC changes a
resource’s graphic. When used in location pro-
cessing logic, move logic, and arrival logic,
GRAPHIC changes an entity’s graphic.

Components

<expression>
The number of the entity’s or resource’s new graphic.

Example

In the example below, EntA arrives at Loc1 for a two

step operation. Upon arrival, the graphic icon of the
entity changes to Graphic 2. After the first two minute
processing time the icon changes to Graphic 3. Finally,
 ProModel 483
User Guide

Group may follow a GROUP statement in the same pro-

cess.
Entity-Related Operation Statement
Components
Syntax samples
<expression>

GROUP <expression> {AS <entity name>} The number of entities to group. If this expression is
zero, the statement is ignored. If it is less than zero, it
GROUP (Var1+Var2) generates an error.
GROUP 10 AS EntX This expression is evaluated every time an entity
encounters the GROUP statement, so the amount of
entities to be combined can vary as the simulation
progresses. If it becomes less than or equal to the num-
Description ber of entities already waiting to be combined, the
Accumulates and temporarily consolidates a entity that encountered the GROUP statement will be
grouped with all the waiting entities.
specified quantity of entities into a single
GROUP shell entity. AS <new entity name>

The shell entity retains the same attributes as the The optional name of the resulting entity. If left off, the
first entity that was grouped into the shell. How- new entity will have the same name as the last entity to
complete the group.
ever, if the GROUP AS statement is used, the
new shell entity does not retain any attribute val-
ues, even if the same name is used for the
Explicit Entity Actions
GROUP shell entity as the entities that have been
grouped. GROUP creates a shell (a temporary entity repre-
senting grouped entities that starts with cost and
The individual entities comprising the group time statistics of zero) to which ProModel assigns
retain their identities, attributes, and resources all cost and time statistics for the group. Each
and are divided from the group when an grouped entity retains its individual cost and time
UNGROUP statement is encountered. The first statistics and, when you ungroup the entities and
entity processed from the group takes any the shell disappears, ProModel divides all statis-
resources the group owns. Entities in a group can
tics and cost (accrued by the shell) between them.
be grouped into a larger group at another loca-
tion.

Valid In
The operation column of process edit tables only.
GROUP may not be used in combination with
COMBINE, CREATE, LOAD, UNLOAD,
SPLIT AS, other GROUP statements in the same
processing logic, or with conveyors. An excep-
tion to this rule is that an UNGROUP statement
484 Chapter 14:
Group

Example

In this example, Man, Woman, and Child are grouped

together at Floor1 before getting on an elevator. The
group of entity types, called Grp_A, is then routed to
Floor2 where it will be ungrouped. (See the
UNGROUP statement example.)

Process Table
Entity Location Operation (min)
Man Floor1 WAIT E(2.0)
Woman Floor1 WAIT U(3,1)
Child Floor1 WAIT N(2.1,.2)
ALL Waiting GROUP 10 AS Grp_A
Grp_A Waiting GET Elevator

Routing Table
Blk Output Destination Rule Move Logic
1 Man Waiting FIRST 1 MOVE FOR
0.5
1 Woman Waiting FIRST 1 MOVE FOR
0.5
1 Child Waiting FIRST 1 MOVE FOR
0.5

1 Grp_A Floor2 FIRST 1 MOVE WITH

Elevator

See Also
COMBINE, ACCUM, GROUPQTY(), and
ENTITY(). Also see “Attributes” on page 217.
 ProModel 485
User Guide

GroupQty() Example

Entity-Specific System Function A group of entities called GRPA arrives at Loc1 and
process for some amount of time according to a Nor-
mal distribution. If the group contains three or more
Syntax samples entities it routes to Loc2, otherwise it routes to Loc3.
Routing requires 1.2 minutes.
GROUPQTY({<entity name>})
ORDER GROUPQTY(Part1) Part2 TO Loc1
IF GROUPQTY(Part1) > 5 THEN... Process Table
Entity Location Operation (min)
GRPA Loc1 WAIT N(3,.1)
Description IF GROUPQTY() > 2 THEN
ROUTE 1
Returns the number of entities of a specified type in a ELSE
grouped or loaded entity. If no name is specified, it ROUTE 2
returns the entire group quantity. If it is a loaded entity,
it will only return the number of temporarily loaded Routing Table
entities, not the base entity. For example, if four Cast-
ings are temporarily loaded onto a Pallet and called Blk Output Destination Rule Move Logic
Batch, the GroupQty() will return the number of Cast- 1 GRPA Loc2 FIRST 1 MOVE FOR
ings (i.e., 4), which does not include the base entity 1.2
Pallet. 2 GRPA Loc3 FIRST 1 MOVE FOR
1.2
In the case of hybrid nested groups with several mixed
and nested levels of groups and loads, GroupQty()
returns the number of entities in the uppermost level See Also
only. GROUP, UNGROUP, and ENT().

Valid In
Speed fields, traveling-time fields, conveyor-
speed fields, Resource fields, operation logic,
routing fields, arrival logic, and debug user-con-
dition fields. This function returns an integer.

Components

<entity name>
The optional specific type of entity to search for in the
group.
486 Chapter 14:
If...Then...Else

If...Then...Else Valid In
Any logic.
General Control Statement
Components
Syntax samples
<Boolean expression>
IF <Boolean expression> THEN <statement 1> {ELSE The condition to be tested.
<statement 2>}
THEN <statement 1>
The statement or block to be executed if the condition
IF Var1 = 5 THEN WAIT 2 min is true.
ELSE <statement 2>
IF (Attr2 = 5) OR (Var5 <> 0) THEN WAIT 2 min The statement or block to be executed if the condition
ELSE WAIT 3 min is false.

IF Var1 > Attr2 THEN

BEGIN Example
Var1 = Attr2
WAIT Attr1 In the following example an IF...THEN...ELSE test is
END made to see if the simulation clock is less than eight
ELSE hours. If so, the Client is routed to Office1, otherwise
BEGIN the Client is routed to Office2.
INC Var1
WAIT Attr2
END

Description
Executes a statement or statement block if the
Boolean expression is true. If an ELSE statement
is included and the Boolean expression is false,
an alternate statement or statement block is exe-
cuted. For an IF...THEN statement to be broken
into more than one line, the first item on the next
line must be THEN, AND, or OR. IF...THEN
statements only apply to the next statement or
statement block in a logic. Any statements out-
side of the BEGIN and END will execute nor-
mally. See BEGIN and END for examples.
 ProModel 487
User Guide

Process Table
Entity Location Operation (min)
Client Loc1 IF CLOCK(Hr) < 8 THEN
ROUTE 1
ELSE
ROUTE 2

Routing Table
Blk Output Destination Rule Move Logic
1 Client Office1 FIRST 1 MOVE FOR
5
2 Client Office2 FIRST 1 MOVE FOR
5

See Also
BEGIN, END, DO...WHILE, WHILE...DO, and
DO...UNTIL.
488 Chapter 14:
Inc

Inc Example

General Operation Statement The following example increments two variables in the
exit logic. Num_complete is incremented by one, and
Count is incremented by the expression Attr1*Attr2.
Syntax samples

INC <name>{, <expression>}

INC Var1
INC Attr2, 5+Var1

Description
Increments a variable, array element, or attribute
by the value of a specified numeric expression.
When counting the number of entities a location
has processed, increment a variable at the end of
the processing logic.
See Also
Valid In
DEC.
Any logic.

Components

<name>
The name of any variable, array element, or attribute.
<expression>
The amount to increment the value. If this expression
is omitted, the value will be incremented by one. This
can be a negative number.
 ProModel 489
User Guide

IncEntCost Example

Cost Related Statement The logic below allows you to add an initial cost to an
entity implicitly created through the ROUTE state-
ment. In the following example, a Pallet of entities,
Syntax samples PalletA, arrives at Unload_Loc where workers unload
entities called Box every 20 seconds until the pallet is
INCENTCOST <expression> empty. ProModel determines the number of Boxes
unloaded from PalletA by the value of PalletA’s
INCENTCOST 15 attribute, Qty_Attr. In Move Logic, the statement
INCENTCOST -15 “IncEntCost 10” adds an initial cost of 10 dollars to
each implicitly created entity, Box.

Description
Process Table
Enables you to increment the cost (positively or
negatively) of the current entity by a given Entity Location Opn (min)
amount. Use this function to add to the entity’s PalletA Unload_Loc int x = 0
actual, accumulated dollar amount. WHILE x < Qty_Attr DO
{INC x
WAIT 20 sec
Please note ROUTE 2}
ROUTE 1
When working with new entities created through
a ROUTE statement, use INCENTCOST to assign Routing Table
an initial cost to entities. Initial entity cost Blk Output Destination Rule Move Logic
defined for an entity in the cost module applies to 1 PalletA Exit FIRST 1
entities entering the system through a scheduled 2* Box Conveyor1 FIRST 1 INCENT-
arrival, the CREATE statement, or the ORDER COST 10
statement.

Valid In See Also

Operation and Move logic. GETCOST, GETRESRATE(), INCLOCCOST,

INCRESCOST, and SETRATE.
Components

<expression>
The positive or negative change to the value of cost.
490 Chapter 14:
IncLocCost

IncLocCost location through the IncLocCost statement and then to

the entity with the IncEntCost statement.

Cost Related Statement

Syntax samples Process Table

Entity Location Opn (min)
INCLOCCOST <expression> EntA Inspect WAIT N(3,.7)
INCLOCCOST 15 INCLOCCOST 3
INCENTCOST 3
INCLOCCOST -15
Routing Table
Blk Output Destination Rule Move Logic
Description 1 EntA Packaging PROBA-
BILITY .93
Enables you to increment the cost (positively or EntA Rework .07
negatively) of the current location by a given
amount. Use this function to add to the location’s See Also
actual, accumulated dollar amount.
GETCOST, GETRESRATE(), INCENTCOST,
Valid In INCRESCOST, and SETRATE.
Operation logic.

Components

<expression>
The positive or negative change to the value of cost.

Example

The logic below shows how to add a cost per entry to a

location for an entering entity. ProModel automatically
tracks operation cost per time unit specified in the cost
dialog, however, you may assign a one time cost each
time an entity enters a location.
In the following example, an entity, EntA, arrives for
inspection at location Inspect. We define no rate of
operation cost for Inspect because each inspection
accrues a one time cost regardless of how long the
entity remains at Inspect. At Inspect, workers inspect
EntA. After inspection, ProModel adds the cost to the
 ProModel 491
User Guide

IncResCost Example

Cost Related Statement A clerk normally works an 8-hour shift. However, if

the clerk does not finish entering all the orders in his
Input_Queue at the end of the day, he must stay and
Syntax samples finish them. Since the clerk is paid time-and-a-half for
any overtime, you must increment the cost of the
INCRESCOST <cost expression> {,<resource>} resource by an additional half of the normal rate to get
the overtime rate. To do this, set a variable equal to 1 in
INCRESCOST 10 the pre-off-shift logic for the resource, indicating the
INCRESCOST GETRESRATE(Operator1)*20, resource should go off-shift. If the variable is equal to
Operator1 1, increment the cost of a resource by half the original
rate.

Description
Process Table
Enables you to increment the cost (positively or
negatively) of a resource currently owned by the Entity Location Opn (min)
entity executing the statement. Use this function Order Order_desk GET Clerk, 399
to add to the resource’s actual, accumulated dol- WAIT N (4.5, .3)
lar amount. When used without the optional IF Off_Shift_Var=1
THEN INCRESCOST
<resource> parameter, this statement increments GETRESRATE() *.50
the cost rate of the entity’s most recently cap- FREE Clerk
tured, owned resource.
If an entity owns multiple units of a resource, the Routing Table
cost distributes evenly to each unit. Blk Output Destination Rule Move Logic
1 Order Shipping FIRST 1 MOVE FOR 1
Valid In
Operation and move logic.

Components
See Also
<cost expression>
The positive or negative change to the value of cost. GETCOST(), GETRESRATE(), INCENTCOST,
INCLOCCOST, INCRESCOST, and SETRATE.
<resource>
A resource currently owned by the entity executing the
statement. When used without the parameter, this state-
ment increments the cost rate of the entity’s most
recently captured, owned resource.
492 Chapter 14:
Int

Int Components

Local Variable Declaration Statement <names>

An identifier for the local variable. This identifier must
Syntax samples be a valid name.
<expressions>
INT <name1>{= <expression1>, <name2>= The variable will initially be assigned this value. This
<expression2>...) expression is evaluated every time the INT statement is
INT Count encountered.

INT Count = 1
INT Count = 1, Test = FREECAP(Loc2) Example

A plant manufactures pipes of 12 different types, such

as 2" steel, 4" aluminum, etc. All workers inspect pipes
Description
at a common inspection station after which they move
Creates a local variable of type integer. Local to a dock where other workers load them into boxes.
variables work much the same as attributes, The boxes are designed to hold only certain types of
except that they only are available within the pipes. Therefore a box designed to hold 2" steel pipes
logic that declares them. A new variable will be can only hold 2" steel pipes, not 4" aluminum pipes.
created for each entity that encounters an INT Suppose a Box, enters a multi-capacity location, Dock.
statement. Local variables are not directly avail- Each Box has a different entity attribute, b_type,
able to subroutines, which have their own local describing the type of pipe it can hold. Workers load
variables. However, a local variable may be pipes into the Box. Workers must load the 2" steel
passed to a subroutine as a parameter. Local vari- pipes into the box designed to hold the 2" steel pipes.
ables are available inside referenced macros. Therefore, the attribute value of the Pipe, p_type, must
match the attribute value of the Box, b_type. We can
Use local variables where ever possible for the use local variables to accomplish this modeling task. In
test variable in WHILE...DO, DO...WHILE, and the following example, we defined X as a local vari-
DO...UNTIL loops. able and set it equal to b_type:

Valid In
Any logic. Variables declared with INT are valid
in any expression within the logic where a normal
integer number is valid.
 ProModel 493
User Guide

Process Table
Entity Location Operation (min)
Pipe Inspect WAIT 5
Box Dock INT X= b_type
LOAD 5 IFF
X=p_type
Box Dock WAIT 10

Routing Table
Blk Output Destination Rule Move Logic
1 Pipe Dock LOAD 1 MOVE FOR 2

1 Box Delivery FIRST 1 MOVE FOR 8

See Also
REAL. Also see “Local Variables” on page 225.
494 Chapter 14:
Join

Join Valid In
Operation logic only. More than one JOIN state-
Entity-Related Operation Statement ment may be used in the same logic.

Syntax samples Components

JOIN <expression> <entity name> {,<priority>} <expression>

JOIN 4 EntA The number of entities to be joined. A zero value is

ignored and a negative value generates an error. This
JOIN Var1 EntA, 1 expression is evaluated when each entity first encoun-
ters it, but is not re-evaluated as the requested entities
are joined.

Description <entity name>

Joins a specified quantity of a designated entity The entity type to be joined to the base entity. Joining
entities must come from a JOIN routing and lose their
type to the current entity. The entities joined to
identity once joined.
the current entity lose their identities and any
resources owned by the joining entities are trans- <priority>
ferred automatically to the base entity. Use JOIN An entity with a higher priority will have arriving enti-
to simulate a component being assembled to a ties joined to it before one with a lower priority. This
main part, such as when wings are attached to the expression should be a number between 0 and 999. For
fuselage of an airplane. more information on priorities, see Priorities, at the
beginning of this section.
Entities to be joined must be routed to the current
location with a JOIN rule. The current entity
waits until enough entities to fill its request have Explicit Entity Actions
been routed to the current location with a JOIN
rule. JOIN passes cost on to the base entity but not sta-
tistical information. ProModel counts joined enti-
The resulting entity retains the attributes and ties as exits.
name of the base entity. To transfer attributes
from the joining entity to the current entity, in the
exit logic for the joining entity, copy the desired
attribute to a global variable. Then assign the glo-
bal variable to the attribute of the base entity after
the JOIN statement in the processing logic.
All resources owned by the joining entity are
transferred to the base entity.
To JOIN an entity with a specific attribute value
to another entity with the same attribute value,
use the LOAD PERM statement .
 ProModel 495
User Guide

Example

A certain location on an assembly line manufacturing

cars attaches doors built on another assembly line.
When the Body of the car arrives at the Assembly loca-
tion, we attach a left door, Ldoor, and a right door,
Rdoor, with a JOIN statement. The paint station paints
the doors and routes them to Assembly with a JOIN
rule. Note that the Body will wait until we join both
doors before routing to the next location.

Process Table
Entity Location Operation (min)
Rdoor Paint WAIT 30
Ldoor Paint WAIT 30
Body Assembly JOIN 1 Ldoor
JOIN 1 Rdoor

Routing Table
Blk Output Destination Rule Move Logic
1 Rdoor Assembly JOIN 1 MOVE FOR 30
1 Ldoor Assembly JOIN 1 MOVE FOR 30
1 EntB Cleaning FIRST 1 MOVE FOR 5

See Also
LOAD, COMBINE, and GROUP. Also see
“Attributes” on page 217.
496 Chapter 14:
Jointly Get

Jointly Get <resource >

The name of the resource to JOINTLY GET. RES() can
be substituted for the resource name.
Resource-Related Operation Statement
<priority>
Syntax samples When multiple entities request a resource, the requests
will be filled in order of priority. This expression
JOINTLY GET {<quantity>} <resource> should be a number between 0 and 999.
{,<priority>}
{AND or OR {<quantity>} <resource> {,<prior-
ity>}} Example
JOINTLY GET 3 Res1,5
In the following example (which also demonstrates the
JOINTLY GET 2 Res1 OR 3 Res2
FREE statement) EntA arrives at Loc1 for a multi-step
JOINTLY GET Res1,3 AND (Res2 OR Res3) process. Because the first step of the process uses Res1
JOINTLY GET 2 Res(Attribute1) and Res2 simultaneously, a JOINTLY GET statement
is issued to ensure that both resources are available
before the process begins. The resources are then freed
independently.
Description
Captures a specified number of resources when
that number of resources is available. When cap- Process Table
turing multiple resources, none of the resources
will be captured until all are available. If the Entity Location Operation (min)
EntA Loc1 JOINTLY GET Res1 AND Res 2
entity already possesses one or more of the
WAIT N(4.5,.2)
requested resources, the entity will still try to FREE Res1
capture additional units of the specified WAIT L(3.4,.23)
resources. FREE Res2

Valid In Routing Table

Location processing, downtime, move, and shift Blk Output Destination Rule Move Logic
logic. 1 EntA Loc2 FIRST 1 MOVE FOR 1

Components See Also

GET and USE.
<quantity>
The number of resources to get. A value of zero is
ignored and values less than zero return an error. This
numeric expression is evaluated and truncated every
time the JOINTLY GET statement is encountered.
 ProModel 497
User Guide

Last() Example

Resource-Specific System Function This Entry Logic window shows that whenever a
resource enters a particular node a check is made to see
if the name-index number of the last node equals one.
Syntax samples If so, the resource graphic is changed to Graphic 2, oth-
erwise it is changed to Graphic 3.
LAST()
Var1=LAST()
IF LAST() = 13 THEN Var3 = 0
IF LAST() = PathNet1.N1 THEN INC Var1

Description
Returns the name-index number of the node from
which a resource has just traveled. LAST() can
be useful to choose the appropriate graphic or to
reset a variable. You can also check the name-
index number of the last node by specifying
<path network name>. <name of the node>. For
example, if you wanted to know if the last node See Also
was N5 on the network Net3, you could specify NEXT() and WAIT...UNTIL.
“IF LAST() = Net3.N5 THEN...” in the node
entry logic.

Valid In
Node entry logic.
498 Chapter 14:
Ln()

Ln()
Math Function

Syntax samples

LN(<expression>)
Real1 = LN(Real2)

Description
Returns the natural logarithm of an expression.

Valid In
Any expression. This function returns a real num-
ber.

Components

<expression>
LN() returns the natural logarithm of this expression.

See Also
EXP().

Please note

To get a logarithm to a particular base, use the

following formula:

logbase<expression> = LN<expression>/
LN<base>
 ProModel 499
User Guide

Load cess with SPLIT AS, CREATE, COMBINE,

GROUP, or UNGROUP.
Entity-Related Operation Statement
Components
Syntax samples
<expression>

LOAD <expression> {PERM}{IFF <Boolean expres- The number of entities to load onto the base entity.
sion>}{IN <time>}{,<priority>} This expression is evaluated at the time the entity
encounters the LOAD request.
LOAD 5, 99
PERM
LOAD 5 IFF Attr3 > 2 IN 5 min
This option causes the LOAD to behave the same as
LOAD Pallet_Capacity LOAD 5 PERM IN 10 min the JOIN statement. It will permanently join entities to
the base entity executing the LOAD statement. Any
resources owned by the permanently loading entities
are transferred automatically to the base entity.
Description
IFF <Boolean expression>
Loads a specified quantity of entities onto a base
This option allows the LOAD command to be condi-
entity. Temporarily loaded entities retain their
tional. Any attributes, entity functions, or location
identity and may be unloaded with an UNLOAD functions apply to the entity to be loaded, not to the
statement. Permanently loaded entities, using the base entity. This technique allows only entities with
PERM option in the LOAD statement, do not certain properties to be loaded onto the base entity. To
retain their identity and cannot be unloaded later. use attributes, entity functions, and location functions
Loaded entities must be routed to the loading that apply to the base entity, assign the desired value to
location using the LOAD routing rule. Additional a local variable and use the local variable in the Bool-
entities may be added to an entity’s existing load ean expression.
with additional LOAD statements. Use LOAD to IN <time>
model parts placed into a container or pallet when
The entity will load entities up to the specified limit for
they must be removed later. If a base entity owns
this amount of time and then go on. Entities loaded
a resource when the entities are unloaded the with this option may have a load smaller than the spec-
resource stays with the base entity. Any resources ified amount.
owned by permanently loading entities are trans-
<priority>
ferred automatically to the base entity. Any
resources owned by temporary loading entities Waiting entities will load arriving entities by priority.
are kept and cannot be freed until the entities are This expression should be a number between 0 and
unloaded. 999.

Valid In
Explicit Entity Actions
Operation logic only. A process may contain
multiple load statements and no more than one LOAD does not transfer cost or statistics of the
UNLOAD statement following all LOAD state- loaded entity. However, if the PERM option is
ments. LOAD may not be used in the same pro- used, the cost of the loading entity does get trans-
ferred to the base entity.
500 Chapter 14:
Load

Example

In this example, boxes are loaded onto a semi-truck.

The quantity is determined by the value of the Truck’s
attribute, Attr1. The resulting entity retains the name
Truck and is sent on to its final destination, New York,
Chicago, or Boston.

Process Table
Entity Location Operation (min)
Box Shipping WAIT 2 min

Truck MfgSite

Truck Dock LOAD Attr1 IN 2 hr

Routing Table
Blk Output Destination Rule Move Logic
1 Box Dock LOAD 1 MOVE FOR 45
sec
1 Truck Dock FIRST 1 MOVE FOR 10
min
1 Truck NewYork FIRST 1 MOVE FOR 24
hr
Truck Chicago FIRST MOVE FOR 12
hr
Truck Boston FIRST MOVE FOR 28
hr

See Also
LOAD, GROUP, UNLOAD, ACCUM, COM-
BINE, JOIN, GROUPQTY(), and ENTITY().
Also see “Attributes” on page 217.
 ProModel 501
User Guide

Loc() Components

Name-Index-Number Conversion Function <location name-index number>

The name-index number of the desired location. This
Syntax samples component may be an expression, allowing the loca-
tion to vary as the simulation progresses. Real numbers
will be truncated to integers.
LOC(<location name-index number>)
ORDER 10 EntA TO LOC(5)
DISPLAY “EntA arrived at” $ LOC(5) Example

Suppose there are five locations which appear one after

the other in the Location edit table as follows: Dock1,
Description Dock2, Dock3, Dock4, Dock5. Shipments could be
ordered to each of the five locations in rotation with the
Converts a name-index number or integer to a
following logic. Note that Dist() is a user-defined dis-
location name. Use this function when a state-
tribution that returns an integer value for the number of
ment or function needs the name of a location but Shipments to order.
whose name-index number is stored in an
attribute, variable, or some other expression. It INT Var1 = 1
can also be used to vary a selected location based WHILE Var1 <= 5 DO
on the name-index number stored in the expres- BEGIN
sion. When used in a string expression, as in the
second syntax example above, ProModel will ORDER Dist() Shipments TO LOC(Var1)
convert the name-index number to the actual INC Var1
name of the location. If the expression points to a END
unit of a multi-unit location, then the LOC()
function will return the name of the parent loca-
tion.
See Also
Valid In
ENT(), RES(), and LOCATION().
Any statement where a location name is normally
used, including the Destination field of the Rout-
ing edit table. Also used in string expressions.
502 Chapter 14:
LocState()

LocState()
General System Function

Syntax samples

LOCSTATE (<locationname>)

Description
Returns a value indicating the current state of the
specified location. Return values will range from
1-7, which translate to the following:
1 = idle/empty
2 = setup
3 = operating
4 = blocked
5 = waiting
6 = up (multi-capacity location)
7 = down

Valid In
Any Logic.

Components

<locationname>
The name of the location.
 ProModel 503
User Guide

Location() Process Table

Entity Location Operation (min)
Location-Specific System Function Sink Oven ACCUM CAP(LOCATION())

Syntax samples Routing Table

Blk Output Destination Rule Move Logic
LOCATION() 1 Sink Cool FIRST 1 MOVE FOR
Attr1 = LOCATION() 5

IF LOCATION() = 2 THEN WAIT 4 MIN See Also

LOC() and ENTITY().

Description
Returns the current location’s name-index num-
ber. This function is especially useful in macros
and subroutines that vary depending on which
location’s logic calls them. By using a LOCA-
TION() function with an IF...THEN statement,
the macro or subroutine can act differently
depending on the location that called it. Also, the
same technique can be used to determine which
location is carrying out a process when ALL is
used as the process location.

Valid In
Any logic.

Example

The individual ovens of a ceramics plant have different

capacities, but are otherwise exactly the same. While
each oven could be modeled as an individual location,
it would be easier to model this situation as a multi-unit
location. This example uses CAP() and LOCATION()
in the processing logic of the parent location to accu-
mulate enough Sinks to fill each oven.
504 Chapter 14:
Log

Log Example

General Action Statement The example below shows a LOG statement used to
capture each Client’s total throughput time as they
travel through the system. Time starts when the Client
Syntax samples arrives at Receptionist and stops when the Client exits
through the door. The first process sets attribute CT
LOG <string>, <expression> equal to the current clock time. Next, Clients are sent
randomly to one of three offices. Finally, when a Cli-
LOG “Activity Time”, Attr1 ent leaves the system at location OutDoor, the LOG
statement records the cycle time by subtracting the
time stored in attribute CT from the current simulation
time.
Description
ProModel assumes that the time stored in the Throughput Time
expression is in the model’s default time units set
in the General Information dialog box. Use the
1 2 3 4 5
LOG statement to record the time from one state-
ment to another statement by storing the time of
the first statement in an attribute, variable, or Reception Loan OutDoor
array element with CLOCK() and using the same Auditor Service
attribute, variable, or array element as the expres-
sion in the LOG statement. Use the LOG state-
ment to determine throughput time or throughput
in a particular section of the facility.

Valid In
Downtime logic, location processing logic, node
entry and exit logic, and routing exit logic.

Components

<string>
This string will be stored in the file before the result of
the log expression and may not be a string expression.
Use this string to identify the number that follows.
<expression>
The result of this expression subtracted from the
model’s current time will be stored in the file <model
name>.LAP, after the string above.
 ProModel 505
User Guide

Process Table
Entity Location Operation (min)
Client Reception CT=CLOCK()
Client Auditor WAIT T(5,6,8)
Client Loan WAIT T(4.5,5,7)
Client Service WAIT N(6.2,1.1)
Client OutDoor LOG “Cycle Time”, CT

Routing Table
Blk Output Destination Rule Move Logic
1 Client Auditor RANDOM MOVE FOR
Loan 1 1.5
Service RANDOM
RANDOM
1 Client OutDoor FIRST 1 MOVE FOR
0.5
1 Client OutDoor FIRST 1 MOVE FOR
0.5
1 Client OutDoor FIRST 1 MOVE FOR
1.2
1 Client EXIT

See Also
WRITE, WRITELINE, and READ. Also see
“External Files” on page 254.
506 Chapter 14:
MapArr

MapArr TO <variable name>

The optional name of the variable to which you map
the first cell in the array. If you do not specify a name,
General Action Statement
ProModel will unmap the array from the variables.

Syntax samples
Example
MAPARR <array name>{TO <variable name>}
MAPARR Array1 TO Var10 Suppose you want to dynamically view an array,
MAPARR Array5 Storage_Array, during simulation. The array has a
dimension of 2x3x2 (a three-dimensional array with 2
cells in the first dimension, 3 cells in the second, and 2
cells in the third) and contains a total of 12 cells (multi-
ply all the dimensions together).
Description
Since you already used the first 8 of the 30 variables
Starting with the variable you specify, the MAP-
defined in the model, Var1 through Var30, you will
ARR statement maps each individual cell of an start mapping the array with Var9 and end with Var20
array to a unique variable (i.e., if you define 12 (the 12th variable from Var9 listed in the Variables
cells for the array, the array will map to 12 vari- module). In the initialization logic, use the following
ables). To display the cell value of a mapped statement:
array, create a variable graphic for the variable to
MAPARR Storage_Array TO Var9
which you mapped the array cell. ProModel col-
lects statistics for an array cell through the vari- The cells in Storage_Array will map to variables Var9
able to which you mapped the cell. (Choose to Var20 in the following order:
“Basic” or “Time Series” statistics for a mapped [1,1,1] ... Var9
variable, then view the variable in the Statistics [1,1,2] ... Var10
Output program.) [1,2,1] ... Var11
[1,2,2] ... Var12
If you do not specify the optional variable name [1,3,1] ... Var13
in the statement, ProModel will unmap the array [1,3,2] ... Var14
from the variables to which you originally [2,1,1] ... Var15
mapped it. You can remap arrays by using the [2,1,2] ... Var16
MAPARR statement again. [2,2,1] ... Var17
[2,2,2] ... Var18
Valid In [2,3,1] ... Var19
[2,3,2] ... Var20
Any logic.
In the Variables module, create graphics for variables
Components Var9 through Var20 and place them on the layout. This
will allow you to view them during the simulation.
<array name>
Map, unmap, or remap this array. The brackets, [ ], are
unnecessary after the array name in the statement.
 ProModel 507
User Guide

Please note

Changing the cell value of a mapped array will

change the value stored in the array cell AND the
value of the variable to which you mapped the
specific cell. Changing the value of a variable
(e.g., INC Var12), however, will change ONLY
the variable value and NOT the cell value of the
mapped array cell. Also, when you use a mapped
array in an expression, the array returns the
value of the variable mapped to it.
508 Chapter 14:
Match

Match Components

Entity-Related Operation Statement <attribute>

Any attribute associated with the processing entity.
Syntax samples

MATCH <attribute> Example

MATCH Attr1
You can use a MATCH to recombine the parts of an
entity which has been split using multiple routing
blocks. In the example below, every time an EntAB
arrives at the location, the variable Count increments.
Description
ProModel assigns Attr1 for EntAB the value of count,
Causes the current entity to wait until the value of which ensures that each EntAB will have a unique
the specified attribute matches the value of value for Attr1. Additionally, when each EntAB is split
another entity’s same attribute. Both entities must into EntA and EntB, both of the resulting entities,
have a corresponding MATCH statement speci- (EntA and EntB) will have the same value for Attr1.
fied for the same attribute name. The two entities EntA and EntB then travel independently through their
respective processing steps, denoted by the ellipses.
may be at any location in the model, including
Finally, EntA and EntB arrive at Loc10A and Loc10B
the same location and two completely unrelated
respectively, where each piece must wait for its match-
locations. Therefore, the value of the attribute to ing half to arrive before consolidating the entities with
MATCH should almost always be assigned to the the JOIN construct.
value of a global variable incremented for each
entity that will be matched, as in the following
example.
Locations using the MATCH statement usually
should be multi-capacity because otherwise they
would not be able to process any other entities
until the MATCH was made. Additionally, loca-
tions using MATCH usually should be non-queu-
ing to allow the entities to move out of sequence
when the MATCH is fulfilled.
Use the MATCH statement to pair two specific
parts before assembling them, or to match a work
order to a completed job.

Valid In
The operation column of process edit tables only.
 ProModel 509
User Guide

Process Table
Entity Location Operation (min)
EntAB Loc1 INC Count
Attr1= Count
EntA Loc2 ...
EntA Loc10A MATCH Attr1
EntB Loc3 ...
EntB Loc10B MATCH Attr1
JOIN 1 EntA

Routing Table
Blk OutputDestination Rule Move Logic
1 EntA Loc2 FIRST 1 MOVE FOR 5
2 EntB Loc3 FIRST 1 MOVE FOR 5
... ... ... ... ...
1 EntA Loc10B JOIN 1 MOVE FOR 30
sec
... ... ... ... ...
1 EntAB Loc11 FIRST 1 MOVE FOR 5

See Also
WAIT...UNTIL and LOAD.
510 Chapter 14:
Move

Move amount of time, and then resumes the processing

logic. The move-time for an entity on a conveyor
is calculated using the following formula:
Entity-Related Operation Statement
Time = (Conveyor Length - Entity Length or Width)/
Conveyor Speed
Syntax samples
For queues only, a MOVE may optionally be fol-
MOVE {FOR <time expression>} lowed by a FOR statement and then a move-time.
If a move-time is specified, the entity moves
MOVE FOR .25 min
through the queue in the specified amount of time
MOVE FOR 3.2 regardless of the entity’s speed and the queue’s
MOVE length. Entities with shorter move times will
catch up to, but will not pass, entities with longer
move times.
If a queue is not empty when an entity enters the
Description
queue, then the move-time will continue to elapse
Moves the entity to the end of a queue or con- even though the arriving entity’s graphic may
veyor location. Use the MOVE statement to have stopped moving. When an entity’s move-
explicitly control the movement of an entity time has elapsed, an entity will begin executing
through a queue or conveyor. any logic following the MOVE statement and
then will be available for routing, even if graphi-
cally the entity does not appear to be at the end of
the queue.
For a conveyor, if additional logic follows a
MOVE statement, the entity must advance to the
Please note last position on the conveyor before the remain-
ing logic is executed.
If there is no MOVE statement, when an entity
enters a queue or conveyor, it executes all the Valid In
processing logic defined for the entity at that The operation column of process edit tables only,
location and then moves to the end of the queue and only if the location is a queue or a conveyor.
or conveyor. For queues, its movement time is MOVE may only be used once per logic.
based on the entity’s speed and the queue’s
length. For conveyors, its movement time is
based on the conveyor speed and length. Components

<time expression>
The amount of time needed for the entity to travel
If an entity processing at a queue or conveyor through the queue. This expression is ignored for con-
encounters a MOVE statement, the entity stops veyors. It is evaluated every time the statement is
executing the processing logic, moves to the end encountered and should be on the same line as the
of the queue or conveyor in the appropriate MOVE command.
 ProModel 511
User Guide

Example

The example below shows the processing steps neces-

sary to mimic the behavior of a queue system using
MOVE statements. Locations Queue1, Queue2 and
Queue3 should each be represented graphically with a
queue symbol. The time value in the MOVE statement
represents the time required to traverse each queue sec-
tion from beginning to end when the queue is empty.

Process Table
Entity Location Operation (min)
ALL Queue1 MOVE FOR 2.5
ALL Queue2 MOVE FOR 3.5
ALL Queue3 ...

Routing Table
Blk Output Destination Rule Move Logic
1 ALL Queue2 FIRST 1
1 ALL Queue3 FIRST 1
... ... ... ... ...

See Also
“Locations” on page 90. Also see WAIT.
512 Chapter 14:
Move For

Move For Example

Entity-Related Move Logic Statement It takes 4 minutes for the entity, Cutter, to move from
one location, Grinder, to the next location, Profiler.

Syntax samples

MOVE FOR <time> Process Table

MOVE FOR 0 Entity Location Operation (min)
MOVE FOR 2.5 + CleanupTime Cutter Grinder GET Operator WAIT 1
Cutter Profiler WAIT Attr1
MOVE FOR N(8, .5) + 3 sec
Routing Table
Blk Output Destination Rule Move Logic
Description 1 Cutter Profiler FIRST 1 MOVE FOR 4
Used to specify the amount of time required to 1 Cutter Exit
move the entity. A move-time of zero may be
entered to cause events for other entities occur- See Also
ring at the same simulation time to be processed MOVE ON and MOVE WITH. Also see “Rout-
before any additional logic is processed for the ing Move Logic” on page 294.
current entity. If no move related statement
(MOVE FOR, MOVE ON, MOVE WITH) is
specified, the entity instantly enters the next loca-
tion and immediately begins executing the opera-
tion logic for that location.

Valid In
This statement is valid in Move Logic. MOVE
FOR may be encountered only once by an entity
in the same logic.

Components

<time>
The length of time the system takes to execute the
move. This expression is evaluated whenever the
statement is encountered. If no time unit is specified,
the default time unit specified in the General Informa-
tion dialog is applied.
 ProModel 513
User Guide

Move On Process Table

Entity Location Operation (min)
Entity-Related Move Logic Statement EntA StationA WAIT 2
EntA StationB ...
Syntax samples
Routing Table
MOVE ON <path network> Blk Output Destination Rule Move Logic
MOVE ON StatPath2 1 EntA StationB FIRST 1 MOVE ON
Net1
... ... ... ... ...

Description See Also

Use this statement to move an entity along a path MOVE FOR and MOVE WITH. Also see “Rout-
network. ing Move Logic” on page 294.

Valid In
This statement is valid only in Move Logic.
MOVE ON may only be encountered once by an
entity in the same move logic.

Components

<path network>
Any valid path network name.

Example

An entity, EntA, moves from StationA to StationB

along a network called Net1.
514 Chapter 14:
Move With

Move With The resource used to make the move is freed only
if the THEN FREE option is used.
Entity-Related Move Logic Statement Valid In
This statement is valid only in Move Logic.
Syntax samples
MOVE WITH may only be encountered once by
an entity in the same move logic.
MOVE WITH <res1> {,p1}
OR <res2> {,p1}
{FOR <time >} {THEN FREE} Components
MOVE WITH Technician, 100
<res1>
MOVE WITH Operator1, 399 FOR 3 min
Resource to be captured and used to transport the
MOVE WITH Truck1, 99 THEN FREE entity.
MOVE WITH Operator1 OR Operator2 <res2>
Alternate resource to be captured and used to transport
the entity.
Description <priority>
This statement is used to move an entity using a The priority for accessing the resource. If the resource
designated resource such as a person or forklift. is already owned by the entity, this priority is ignored.
With the OR operator, you can designate alterna- <time>
tive resources for making the move. In this case,
The length of time the system takes to execute the
the statement captures the first available resource
move. Used only if the resource is static. This expres-
designated in its expression and makes the move.
sion is evaluated whenever the statement is encoun-
As soon as the destination becomes available, the tered. If no time unit is specified, the default time unit
entity implicitly gets the resource. However, if specified in the General Information dialog is applied.
one of the resources is already owned by the
entity, it will use that resource.
It also allows you to set the priority (p1) for
accessing the designated resource. If the
resource is already owned by the entity, this pri-
ority is ignored.
If the resource is static, you may specify a time
(FOR <time expression>) for the move. If a
resource is dynamic, a time (FOR <time expres-
sion>) is not valid. If you use “FOR <time>” with
a dynamic resource, ProModel ignores the time.
The resource will travel based on either the time
or speed/distance defined in the path networks
module.
 ProModel 515
User Guide

Example

An entity moving from Station A to Station B may use

either Tech1 or Tech2 to move the entity depending on
which one is available first. The resource is freed after
the move.
MOVE WITH Tech1 OR Tech2 THEN FREE

The same thing could be accomplished in longer form:

GET Tech1 OR Tech2
MOVE WITH OwnedResource()
FREE OwnedResource()

See Also
MOVE FOR and MOVE ON. Also see “Routing
Move Logic” on page 294.
516 Chapter 14:
Next()

Next() Example

Resource-Specific System Function This Exit Logic window shows that whenever the
resource leaves a node a check is made to see if the
name-index number of the next node equals 1. If so,
Syntax samples the resource graphic is changed to Graphic 3. (Other-
wise it is changed to Graphic 2.)
NEXT()
Var1=NEXT()
IF NEXT() = PathNet5.N11 THEN Var5=3

Description
Returns the name-index number of the resource’s
destination node. Use NEXT() to determine the
direction an entity is headed and choose the
appropriate graphic. This function can be used to
control interference between multiple transport-
ers on the same path network. You can also check
the name-index number of the next node by spec-
ifying <path network name>. <name of the
node>. For example, if you wanted to know if the
next node is N5 on the network Net3, you could See Also
specify “IF NEXT() = Net3.N5 THEN...” in the LAST() and WAIT...UNTIL.
node exit logic.

Valid In
Node exit logic. This function returns a name-
index number.
 ProModel 517
User Guide

Order <location>
The destination of the new entities. LOC() may be sub-
stituted for the names of locations. If no location is
General Action Statement
specified, the entities will be ordered to the location of
the ORDER statement.
Syntax samples

ORDER <expression> <entity> {TO <location>} Example

ORDER 10 EntA TO Loc2
ORDER Order_Qty_Attr ENT(Entity_Attr) TO In this example, EntA arrives at LocA1 and trig-
LOC(Loc_Attr) gers an order for 100 EntB’s to LocB1.

Description Process Table

Causes the specified number of entities to be cre- Entity Location Operation (min)
ated and placed into the system at the designated EntA LocA1 ORDER 100 EntB TO LocB1
location. If the location does not have enough EntB LocB1 ...
capacity for all the new entities, the excess enti-
ties will be destroyed. Attributes from the creat- Routing Table
ing entity will be copied to the resulting entities.
Blk Output Destination Rule Move Logic
Use ORDER to replenish inventories when a par-
1 EntA LocA FIRST 1 MOVE WITH
ticular condition occurs. Such as when an inven- Forklift
tory reaches the minimum level.
See Also
Valid In
SEND, CREATE, and SPLIT AS.
Any logic.

Components

<expression>
The number of new entities to be ordered. This field is
evaluated every time the ORDER statement is encoun-
tered, allowing the number ordered to vary as the simu-
lation progresses.
<entity>
The name of the new entities. ENT() may be used for
an entity name.
518 Chapter 14:
OwnedResource()

OwnedResource() Components

Resource-Specific System Function <expression>

The nth resource currently owned by the entity or
Syntax samples downtime making the function call. When this param-
eter is not used, the function returns the last resource
captured that is still owned by the entity.
OWNEDRESOURCE ({<expression >})
OWNEDRESOURCE (2)
OWNEDRESOURCE (ResQty()) Example
OWNEDRESOURCE ()
Suppose an entity owns two resources. The first
resource was captured using the statement GET
Worker. The second resource was captured using the
Description statement GET Oper1 OR Oper2. We know the entity
owns the resource Worker, but we do not know if the
Returns the name-index number of the nth entity owns Oper1 or Oper2. It is time to release the
resource currently owned by the entity or down- second resource so we use the following logic:
time making the function call. The function FREE OWNEDRESOURCE()
parameter indicates the position of the resource in
the chronological list of owned resources. For
example, OwnedResource(1) returns the longest
owned resource in the list and so on. See Also
When used without a parameter, this function RES(), GET, JOINTLY GET, USE, and FREE.
returns the most recent resource that the entity Also see “Resources” on page 126.
captured and still owns. If the parameter value is
not within the range of the resource list, or if the
entity or downtime currently does not own a
resource, the function will return a 0 (zero) with-
out a warning or error message.
A preempted resource is NOT removed from the
list but marked temporarily to indicate that the
preemptee does not own the resource. After the
resource resumes the original process after being
preempted, it retains its original rank in the list.

Valid In
Entity speed fields, traveling-time fields,
resource fields, resource downtime logic, loca-
tion processing logic, location downtime logic,
routing fields, arrival logic, debug user-condition
fields, and move logic.
 ProModel 519
User Guide

Pause Example

General Action Statement The simple example below pauses the simulation after
the 100th EntA has been processed at Loc1. The pur-
pose for doing this might be to view the current state of
Syntax samples the system at this particular point in time.

PAUSE {<string expression>}

PAUSE
Process Table
PAUSE “Var1 =” $ Var1
Entity Location Operation (min)
PAUSE “Reached the midpoint of the simulation.” EntA Loc1 WAIT N(3.2,.1)
INC Total
IF Total >= 100 THEN PAUSE

Description Routing Table

Pauses the simulation and optionally displays a
Blk Output Destination Rule Move Logic
message at some point of interest. This pause 1 EntA Loc2 FIRST 1
allows the user to examine the system in detail.
An information dialog box will appear on the ani-
See Also
mation screen when the pause occurs. The simu-
lation will continue only when the user selects STOP, DISPLAY, and PROMPT.
Resume Simulation from the Simulation menu.

Valid In
Any logic.

Components

<string expression>
The optional message to display.
520 Chapter 14:
PercentOp()

PercentOp()
General System Function

Syntax samples

PERCENTOP (<locationname>)

Description
Returns the cumulative operation time percentage
for the specified, single-capacity location. The
value returned by this function represents the
cumulative percentage of time the location was
actually processing an entity up to the point
where the function was called.
If PercentOp() is called for a multiple-capacity
location, the value returned will always be zero,
since operation time percentage is not calculated
for multiple-capacity location
Note: The method used to calculate operation
percentage for this function is the same method
used in the output statistics.

Valid In
Any Logic.

Components

<locationname>
The name of the location.
 ProModel 521
User Guide

PercentUtil()
General System Function

Syntax samples

PERCENTUTIL (<locationname>)

Description
Returns the cumulative utilization percentage for
the specified location. The value returned by this
function represents the cumulative percentage of
capacity occupied at the location, on average, at
the time the function was called.
Cumulative Occupancy Time x 100
Capacity x Scheduled Time
Cumulative Occupancy Time in the above equa-
tion refers to the sum of the clock time each
entity spends at a location for processing.
PercentUtil() may be called to return percent uti-
lized for both multi- and single-capacity loca-
tions.
Note: The method used to calculate utilization
percentage for this function is the same method
used in the output statistics.

Valid In
Any Logic.

Components

<locationname>
The name of the location.
522 Chapter 14:
Preemptor()

Preemptor() Process Table

Entity Location Operation (min)
Preemption Logic System Function Bracket Punch_1 WAIT 3 min
Bracket* Punch_1 IF PREEMPTOR()>0 THEN
ROUTE 1
Syntax samples ELSE
ROUTE 2
PREEMPTOR()
* Preemptive Process Record
Var1=PREEMPTOR()
Routing Table
Blk Output Destination Rule Move Logic
Description 1 Bracket Inspect FIRST 1
1 Bracket Punch_2 FIRST 1
Identifies whether a downtime or entity is making
the preemptive request. The function returns the 2 Bracket Punch_Wait FIRST 1
name index number of the preempting entity;
however, it returns a 0 if the preemptor is a down-
time. See Also

Valid In “Preemption Process Logic” on page 292.

Operation logic defined as a preemptive process.

Example

Workers may process an entity, bracket, at one of two

locations, Punch_1 or Punch_2. You may preempt the
bracket at Punch_1 by either an entity with a preemp-
tive priority or a location shift downtime with a pre-
emptive priority. If an entity preempts the bracket,
workers send the bracket to Punch_2 to finish process-
ing. Punch_1 and Punch_2 are on the same shift, and
are scheduled to go off-shift at the same time. There-
fore, if a shift downtime preempts the bracket at
Punch_1, the bracket would not be able to go to
Punch_2. In this case, the bracket is sent to a location
called Punch_Wait where it waits for Punch_1 to come
back on-shift. The PREEMPTOR() function deter-
mines whether an entity or shift downtime preempts
the bracket.
 ProModel 523
User Guide

Priority Example

Shift & Break Logic Statement Suppose you want to insure that the resource is non-
preemptable for the first four hours it is off-shift. Sim-
ply enter a high (e.g., 999) off-shift priority value in
Syntax samples the priority dialog in the Shift Assignments module.
Enter the following off-shift logic to lower the priority
PRIORITY <expression> (to 99) four hours into the off-shift period:
PRIORITY 199 WAIT 4 hr
PRIORITY 99
WAIT 4 hr
SKIP
Description
This statement is used to change the priority of
the off-line state of the location or resource. If the See Also
priority is less than the value set previously, the
system will check if the location or resource can “Shift & Break Logic” on page 297.
be preempted.

Valid In
Shift and break main logic only. This statement
is not valid in pre-off shift or pre-break logic.

Components

<expression>
Any expression that yields a value between 0 and 999.
Standard ProModel priority levels apply.
524 Chapter 14:
Prompt

Prompt <name>
The name of the variable, array element, or attribute to
give the value. The value already in this item will be
General Operation Statement
used as the default value.
<choices>
Syntax samples
A string expression identifying the choice. Any num-
PROMPT <string expression>, <name>{, ber of choices may be specified, and all must have cor-
<choice1>:<expression1>, responding expressions.
<choice2>:<expression2>, <expressions>
<choice3:<expression3>...}
The value to assign the variable, array element or
PROMPT “Enter the number of entities to process:”, attribute if the user selects the corresponding choice
Var2 from the menu.
PROMPT “Enter the size of batches to accumu-
late:”,Var1, “Large”: 20, “Medium”: 15, “Small”:
10 Example

The logic below uses PROMPT to let the user select

any size of a batch. Attr1 represents the batch size for
Description EntA. If the batch size has not been set (if Attr1=0),
Pauses the simulation and displays either a mes- then the user is prompted to enter the batch size. The
sage and input field or a menu for selecting a SPLIT AS statement then splits the single entity into
choice. The value entered or selected is then the number of entities specified in the prompt dialog
box. The PROMPT statement in this example displays
assigned to the designated variable, array ele-
the following dialog box.
ment, or attribute. To have PROMPT present a
menu, specify one or more choices as in the sec- IF Attr1=0 THEN
ond syntax example above. The value already in PROMPT “Enter the Batch Size”, Attr1
the variable, array element, or attribute is used as
SPLIT Attr1 AS EntA
the default value in the dialog box. One use of
PROMPT is to give the user the option to change
the operation time represented by a variable dur-
ing a simulation.

Valid In
Any logic.

Components

<string expression>
The message to display. This expression should tell the
user what value to enter or choose.
 ProModel 525
User Guide

Example

This logic works similarly to the logic in example one,

except that it uses PROMPT to let the user select from
one of three different sized batches. The PROMPT
statement in this example displays the dialog box
below.
IF Attr1=0 THEN
PROMPT “Enter the Batch Size”, Attr1, “Small”:10,
“Medium”:15, “Large”:20
SPLIT Attr1 AS EntA

See Also
PAUSE; DISPLAY. Also see “Run-Time Inter-
face” on page 234.
526 Chapter 14:
Rand()

Rand() when assigned to an integer value. Therefore,

when generating integer values, make sure that
the result of the RAND() function is assigned to
Math Function an integer value, or is used in an expression
where it will be truncated to an integer.
Syntax samples
Valid In
RAND(<expression>)
Any expression.
RAND(10) min
ORDER RAND(10) EntA TO Loc1 Components
IF RAND(100) > 45 THEN ROUTE 1
<expression>
The upper limit of the random value to return. This
value will never be returned.
Description
Returns a random value n between 0 and X (0 <=
n < X) where X is the result of the expression. Example
To generate random numbers between the expres-
sion and a number other than zero use the expres- Two resources, Oper_1 and Oper_2, perform the same
sion as the range between the maximum and task at a location, Press. Oper_1 works at several other
locations. As a result, Press only uses him 30% of the
minimum values. Then add the minimum to the
time. The other 70% of the time, Oper_2 performs the
random number. For example, the statement
task.
Attr1 = 2+RAND(3) generates a random number
from two up to, but not including, five. An alter-
nate method is to use a uniform distribution. Note
that the RAND() function works very similar to a Process Table
uniform distribution. For more information on
Distributions, see “Distribution Functions” on Entity Location Operation (min)
page 427. Axle Press IF RAND(100) < 30 THEN
USE Oper_1
This function returns a real number, although the ELSE USE Oper_2
real value may be converted to an integer. To
have the RAND() function generate random inte- Routing Table
ger values between zero and some upper bound,
Blk Output Destination Rule Move Logic
use the formula, Integer_Value = RAND(X+1),
1 Axle Lather FIRST 1 MOVE FOR
where X is the greatest integer that should be 3
returned by the function. For example, to gener-
ate a random integer value between zero and six, See Also
use the formula, Integer_Value = RAND(7). The
RAND(7) part of this formula will actually gen- “Streams” on page 258.
erate a real value between 0 and 6.999, but will
be truncated to a whole number between 0 and 6
 ProModel 527
User Guide

Read If a read file should be read more than once in a

model, it may need to be reset. One way to tell
when a file needs to be reset is with an end of file
General Action Statement marker such as 9999 and the following two lines
of logic.
Syntax samples
Read File1,Value

READ <file ID>, <name> IF Value= 9999 then RESET File1

READ File1, Var1

Valid In
Any logic.

Description Components
Reads the next numeric value from a general read
file and assigns that value to a name. General <file ID>
read files are defined in the External Files Editor.
The file identifier as defined in the External Files Edi-
When reading from a file, ProModel skips all tor.
non-numeric data, such as text, and reads the next
numeric value. Thus comments and notes may be <name>
included in a read file. Multiple replications of a The variable, array element, or attribute to be assigned
model will continue reading from a file where the the value.
previous replication left off unless reset with the
RESET statement.
Example
Please note
The example below shows an outside file being read in
ProModel reads a period (.) in a General read the Arrival logic for entity type Box. In this case three
values representing the length, width and depth of each
file as a zero. To avoid this, you should use the
Box are listed on each line of a file called “Size.Dat.”
comment symbol (#) in front of notes and com-
The File ID for this file is simply Size. Length, Width,
ments that contain a period. and Depth are all entity attributes.

READ can read ASCII files. Most spreadsheet

programs can convert spreadsheets to ASCII files
(.TXT) and comma-delimited files (.CSV).
If a read statement is not assigning the right val-
ues to the proper name, there may be numeric
information in the read-file’s header information
(notes and comments). Additionally, if the values
are being read into an array, the array indices may
not be incremented properly between reads.
528 Chapter 14:
Read

See Also
“External Files” on page 254. Also see RESET
and CLOSE.
 ProModel 529
User Guide

Real <expressions>
The variable will initially be assigned this value. This
expression is evaluated every time the REAL statement
Local Variable Declaration Statement
is encountered.

Syntax samples Example

REAL <name1>{= <expression1>, <name2>=
The example below uses a local real variable to track
<expression2>...)
the total time an entity waits for another entity to be
REAL Var1 joined to it. A shipping area has an operation where
REAL Counter = 0 invoices are joined to boxes to produce packages. The
user wants to know exactly how long an invoice must
REAL Var1 = CLOCK(SEC), Random_Num = wait before a box arrives to be joined. By setting the
RAND(10) value of a local variable, Start, to the clock time just
before the JOIN statement and using a LOG statement
immediately after the JOIN, we can determine how
long each invoice had to wait before a box arrived. A
Description local variable is a better choice here than an entity
attribute because the only place the information is
Creates a local variable of type real. Local vari-
needed is inside this logic.
ables work much the same as attributes, except
that they only are available within the logic that
declares them. A local variable will be created for
each entity that encounters a REAL statement. Process Table
Local variables are not directly available to sub-
routines, which have their own local variables. Entity Location Operation (min)
However, a local variable may be passed to a sub- Box Packing WAIT N(10,3)
routine as a parameter. Local variables are avail- Invoice Shipping REAL Start = CLOCK()
JOIN 1 Box
able to macros.
LOG "Delay:", Start

Valid In
Routing Table
Any logic. Variables declared with REAL are
valid in any expression within the logic where a Blk Output Destination Rule Move Logic
1 Box Shipping JOIN 1 MOVE FOR 1
real number is valid.
1 Pack- Dock FIRST 1 MOVE FOR 3
age
Components
See Also
<names>
INT. See “Variables” on page 223.
An identifier for the first local variable. This identifier
must be a valid name.
530 Chapter 14:
Real()

Real()
Type Conversion Function

Syntax sample

REAL(<expression>)
Var2 = Var1 + REAL(Var3)
Attr3 = 1.05 * REAL(Var5)

Description
Converts an integer to a real number. ProModel
automatically converts integers to real when
needed.

Valid In
Any expression.

Components

<expression>
REAL() converts this expression to a real number.

See Also
ROUND() and TRUNC().
 ProModel 531
User Guide

Rename Implicit Entity Actions

ProModel allows you to define the RENAME
Entity-Related Operation Statement action implicitly as part of the routing definition.
To do this, define a route block with a different
input and output name and the New Entity option
Syntax samples
unchecked.
RENAME {AS} <new entity name>
Example
RENAME EntB
RENAME AS EntB The following example shows how two entities, EntA
RENAME AS ENT(Var2) and EntB, join together at Loc2. Once the join is com-
plete, ProModel renames the resulting entity EntC and
processes it according to a normal distribution
N(9.4,.3). RENAME is the last statement in the process
Description because as soon as you rename an entity, ProModel
searches the processing logic for a process for the
Renames the processing entity to the new entity entity with the new name.
name. After a RENAME statement is encoun-
tered, the entity then searches forward in the pro-
cess list and again from the beginning until a
process is found at the current location that has Process Table
been defined for the new entity type. No further
Entity Location Operation (min)
logic will be executed for the entity under its EntA Loc1 WAIT 1.5 min
original name. Use RENAME to start collecting EntB Loc2 JOIN 1 EntA
statistics for an entity under a new name. Usually, RENAME AS EntC
the easiest and most efficient way to rename an EntC Loc2 WAIT N(9.4,.3)
entity is simply by using the new name as the out-
put entity in the routing. Routing Table

Valid In Blk Output Destination Rule Move Logic

1 EntA Loc2 JOIN 1
The operation column of process edit tables only. 1 EntC Loc3 FIRST 1

Components See Also

COMBINE, SPLIT AS, and GROUP.
<new entity name>
The new name of the processing entity. ENT() may be
substituted for the entity name.

Explicit Entity Actions

With RENAME, statistics and cost continue on
with the entity.
532 Chapter 14:
Report

Report Example

General Action Statement To get a snapshot report every 40 hours, enter the fol-
lowing:

Syntax samples WHILE Clock(hr) < 10000 DO

BEGIN
REPORT {WITH RESET} {AS <string expression>} WAIT 40 hr
REPORT REPORT AS “40HOUR”
REPORT WITH RESET END
IF thruput = 50 THEN REPORT AS “RepOvr50” This results in reports named, 40HOUR, 40HOUR2,
40HOUR3....

Description
Calculates and reports the current statistics to the Please note
output database. This is useful to get a snapshot
of the model while it is running. If you use the REPORT statement even once, a
final overall report will NOT be created since the
The REPORT statement may be followed by the
report generated with your use of the statement
WITH RESET option to reset the statistics after
may be the final report desired. In this case, you
the report is made to the database When you use
must use the REPORT statement at the end of ter-
the WITH RESET option, you generally want to
mination logic in order to create a final report if
provide some looping or event creation that will
desired. If a REPORT statement is never used, a
call the report function at the appropriate time.
final overall report is created automatically.
Used with the AS option, REPORT creates a
report with the name specified in the expression
that can be accessed in the Output Program when
creating a General Stats report. See Also
RESET STATS and WARMUP.
Valid In
Any logic.

Components

<string expression>
A unique name given to the report so it can be
easily identified in the General Stats dialog in the
Output Program. If any reports have the same
name, a number is tacked on the end of the name
to make it unique.
 ProModel 533
User Guide

Res() Components

Name-Index-Number Conversion Function <resource name-index number>

The name-index number of the resource desired. This
Syntax samples component may be an expression. Real numbers will
be truncated to integers.

RES(<resource name-index number>)

USE 10 RES(Var1) for 1.5 min Example
FREE RES(Var1)
DISPLAY “Now using” $ RES(Var1) The logic below uses five different resource types for
ten minutes in rotation.
INT Var1 = 1
WHILE Var1 <= 5 DO
Description
BEGIN
Converts a name-index number or integer to a
resource name. Use this function when a state- USE RES(Var1) FOR 10 min
ment or function needs the name of a resource INC Var1
whose name index number is stored in an
END
attribute, variable, or some other expression.
When used in a string expression expecting, such
as in the third syntax example above, ProModel
will output the actual name of the resource. See Also
Use RES() to assign a properly skilled operator ENT(), LOC(), and GRAPHIC.
according to the attribute of the part or to change
the duties of resources as the simulation
progresses.

Valid In
Any statement where a resource name is nor-
mally used, except in the Move Logic field in the
Routing edit table. Also used in string expres-
sions.
534 Chapter 14:
Reset

Reset Example

General Action Statement The example below shows how a general read file,
Times, is reset in the Initialization logic. Each time a
simulation begins, whether a single replication or one
Syntax samples of several multiple replications, the Times file is reset
so that calls to the Times file start at the beginning of
RESET <file ID> the file.
RESET Times
RESET (Times)

Description
Starts a general read file over from the beginning.
RESET is used primarily in the Initialization or
Termination logic to reset a general read or write
file at the beginning or end of multiple replica-
tions and single, independent runs. RESET can
also be used to re-read cyclic data in the same
simulation run. The parentheses are optional and
are included only to insure compatibility with
older models. See Also
Valid In “External Files” on page 254. Also see READ,
WRITE, XWRITE, and RESET.
Initialization and termination logic, node entry
and exit logic, down-time logic, location process-
ing logic, routing exit, and arrival logic.

Components

<file ID>
The file identifier as defined in the External Files Edi-
tor.
 ProModel 535
User Guide

Reset Stats
General Action Statement

Syntax samples

RESET STATS
IF Total = 20 THEN RESET STATS

Description
Resets the simulation statistics. Useful in con-
nection with the REPORT statement to manually
control statistics for reporting purposes in case
specific or event logic.

Valid In
Any logic.

Example

Suppose you want to generate a new output report for

each 20-hour period of the simulation. Enter the fol-
lowing logic in an independent subroutine which is
activated at the beginning of the simulation:
WHILE Clock(hr) < 10000 DO
BEGIN
WAIT 20 hr
REPORT
RESET STATS
END

See Also
REPORT and WARMUP.
536 Chapter 14:
Resource()

Resource()
Shift & Break System Function

Syntax samples

RESOURCE ()

Description
Returns the name-index number of the resource
currently processing the off-shift or break logic.

Valid In
Off-shift and break logic.

Example

Suppose you have locations and resources as members

in a shift file assignment and you want to wait until
variable Parts_To_Process is equal to zero before
allowing a particular resource called Operator to go off
shift. You would enter the following pre-off shift logic:
IF FORRESOURCE() THEN
BEGIN
IF RESOURCE() = Operator THEN
BEGIN
WAIT UNTIL Parts_To_Process = 0
END
END

See Also
LOCATION(), FORLOCATION(), and FORRE-
SOURCE().
 ProModel 537
User Guide

ResourceUnit()
Shift & Break System Function

Syntax samples

RESOURCEUNIT()

Description
Returns the unit number of the resource being
used.

Valid In
Off-shift and break logic.

Example

When a multi-unit resource goes on shift, it is some-

times helpful to know which unit of the resource is
going off shift. Depending on the resource unit you
may want to skip the shift or update a variable that is
used elsewhere in your model.
538 Chapter 14:
ResQty()

ResQty() Example

Entity-Specific System Function The example below demonstrates the use of

RESQTY() to adjust the processing time for an entity
based on the number of resources available to process
Syntax samples it. Before EntA’s arrive at Loc1, they capture a certain
number of resources named Res1. Processing logic at
RESQTY({<resource name>}) Loc1 determines how many Res1’s each EntA captured
and processes it accordingly. The more resources an
IF RESQTY(Res1) > 5 THEN FREE 5 Res1 entity captures, the more workers available to work on
the project, and the less time it takes. ProModel then
routes EntA’s on to Loc2. The logic at Loc2 makes sure
that no EntA owns more than one Res1.
Description
Returns the number of units of the specified
resource that the current entity owns. RESQTY()
can be used to determine the amount of time nec- Process Table
essary to process an entity based on the number Entitiy Location Operation (min)
of resources an entity owns. EntA Loc1 WAIT 120/RESQTY(Res1)
EntA Loc2 IF RESQTY(Res1)>1 THEN
Valid In FREE (RESQTY(Res1)-1)
Res1
Entity speed fields, traveling-time fields,
resource fields, location processing logic, routing
Routing Table
fields, arrival logic, debug user-condition fields,
and exit logic. This function returns an integer. Blk Output Destination Rule Move Logic
1 EntA Loc2 FIRST 1
Components 1 EntA Loc3 FIRST 1

See Also
<resource name>
The name of the resource to check for. If no resource FREECAP(), FREEUNITS(), and
name is specified, the total number of units of all GROUPQTY().
resource types owned by the entity is returned. RES()
may be substituted for a resource name.
 ProModel 539
User Guide

Return Components

General Action Statement <expression>

The value to return. This expression must be on the
Syntax samples same line as the RETURN. If a subroutine was acti-
vated, then the return value is ignored.

RETURN {<expression>}
RETURN Example
RETURN Attr1**Sqrt(Attr2)
The following example uses a subroutine to check the
supply of items in a storage location. If the free capac-
ity of the location is greater than 10, the user is
Description prompted for an order quantity; otherwise no new
items will be ordered. If an order is made, the order
Sends a value from a subroutine to the logic that
time is returned; otherwise the variable OrdTm
called the subroutine. In the same way that
remains unchanged. The logic for Sub1() appears in
parameters send information from the calling the logic window.
logic to the subroutine, RETURN sends informa-
tion from the subroutine to the calling logic.
After the RETURN is executed, no more logic in Process Table
the subroutine is executed. When subroutines
return values, the RETURN statement must be Entity Location Operation (min)
followed by an expression. Item99 Stores
Item99 Shipping WAIT N(3.2,.2)
When used in logic that is not a subroutine, OrdTm = Sub1()
RETURN functions like a very powerful BREAK
or BREAKBLK statement. Whereas BREAK and Routing Table
BREAKBLK exit only the innermost loop or
statement block, RETURN exits the logic com- Blk Output Destination Rule Move Logic
pletely, no matter how deeply nested inside loops 1 Item99 Shipping SEND 1 MOVE FOR 15
and statement blocks. 1 Item99 EXIT FIRST 1

Valid In
Any logic, but used most often in user-defined
subroutines.
540 Chapter 14:
Return

See Also
“Subroutines” on page 238. Also see BREAK
and BREAKBLK.
 ProModel 541
User Guide

Round()
Math Function

Syntax samples

ROUND(<expression>)
Integer1 = ROUND(3.5)

Description
Rounds the expression to the nearest whole num-
ber. Use this function to override ProModel’s
default, truncation.

Valid In
Any expression. This function returns an integer.

Components

<expression>
The expression to be rounded.

See Also
TRUNC() and REAL().
542 Chapter 14:
Route

Route process the remaining logic after the route state-

ment. The “ghost” entity is also referred to as the
parent entity. The child entity takes the route
Entity-Related Operation Statement specified by the ROUTE statement. If the child
entity cannot go to the next location and is
Syntax samples blocked, the parent entity is also blocked and will
not continue logic execution until the child entity
ROUTE <expression> is no longer blocked. For more information, see
ROUTE 2 “Entities” on page 112.

ROUTE Attr1 Valid In

ROUTE Dist1()
The operation column of process edit tables only.

Components
Description
Executes a routing block for the processing <expression>
entity. The process does not continue until all of The integer result of this expression determines the
the entities being routed for the particular block routing block that the entity will take. The expression
have begun executing their move logic. The pro- is evaluated every time it is encountered, allowing the
cessing logic may contain several ROUTE state- chosen block to vary during the simulation.
ments. These statements may be selected
individually using IF...THEN statements, or they
may be processed sequentially, with or without Example
other process statements in between. If any
ROUTE statement appears in a process logic, This example illustrates a “nested” probability routing.
then ProModel assumes all routing for that pro- The initial entity, EntAB, enters Loc1 and ProModel
cess will be activated by the user and therefore makes a decision based on the user-defined distribution
does no automatic routing. If no ROUTE state- Dist1() whether to route the resulting entities according
ment appears in the processing logic, then all to Route 1, Route 2, or Route 3. If ProModel chooses
routing blocks will be executed automatically Route 1, it sends an EntA 60% of the time, or an EntB
40% of the time, to Loc2. If ProModel chooses Route
once processing logic has been completed.
2, it sends an EntA 20% of the time, or an EntB 80% of
The ROUTE Statement is most often used with the time, to Loc3. If ProModel chooses Route 3, it
IF...THEN statements to make routing decisions sends an EntA 30% of the time, or an EntB 70% of the
based on complex logic that is not available time, to Loc4.
through other ProModel features (such as system
functions or the User Condition routing rule).
ROUTE, if used with IF...THEN properly, will
insure that only one of the routing blocks is acti-
vated.
This statement can be used to route one or more
entities and leave behind a “ghost” entity that will
 ProModel 543
User Guide

Process Table
Entity Location Operation (min)
ENTAB Loc1 Route Dist1()

Routing Table
Blk Output Destination Rule Move Logic
1 EntA Loc2 .600 1 MOVE FOR 2
EntB Loc2 .400 MOVE FOR 2
2 EntA Loc3 .200 1 MOVE FOR 2
EntB Loc3 .800 MOVE FOR 2
3 EntA Loc4 .300 1 MOVE FOR 2
EntB Loc4 .700 MOVE FOR 2

See Also
“Routing Rules” on page 405.
544 Chapter 14:
Send

Send Components

General Action Statement <expression>

The number of entities to send to the destination. Neg-
Syntax samples ative values will generate an error message.
<entity name>
SEND <expression> <entity name> TO <destina- The type of entity to send to the destination. You may
tion>{,<priority>} substitute ENT() for an entity name.
SEND 2 EntA TO Loc2 <destination>
SEND 1 Grp_A TO Grp_A_Processing, 10 The name of the location to which the entities will be
sent. You may substitute LOC() for the location name.
<priority>
Description Multiple SEND requests for the same entity type are
filled according to the longest waiting request having
Sends the specified number of a particular entity
the highest priority. This expression should be a num-
type to the destination. The entities to be sent ber between 0 and 999. For more information on prior-
must be waiting with a SEND routing rule. The ities, see Priorities, at the beginning of this section.
entity that issued the SEND command continues
processing whether or not entities of the type
requested are waiting to be sent. If no entities are
Example
waiting to be sent, a SEND notice is automati-
cally posted so that entities will be sent when
In this example, EntA’s arrive at LocA1 and trigger the
they become available.
sending of EntB’s to LocB2. The value of EntA’s Attr2
The SEND statement can model a system based determines the number of EntB’s sent to LocB2.
on demand, rather than on entity arrival, (called a
pull system). Customer orders cause a SEND to
be issued for a main assembly. Main assembly
issues SEND commands for sub-assemblies. The
example model SEND has an excellent example
of this technique.
The SEND statement can also be used as a con-
trol device to limit the amount of work-in-
progress (WIP) in certain critical areas. Quanti-
ties are only sent to the production area when the
WIP level falls below a certain point.

Valid In
Any logic.
 ProModel 545
User Guide

Process Table
Entity Location Operation (min)
EntA LocA1 WAIT U(3,.5)
SEND Attr2 EntB TO LocB2
EntB LocB1 Wait 5 min

Routing Table
Blk Output Destination Rule Move Logic
1 EntA LocA2 FIRST 1
1 EntB LocB2 SEND 1
EntB LocB3 SEND
EntB LocB4 SEND

See Also
ORDER, JOIN, ROUTE, WAIT...UNTIL, and
LOAD.
546 Chapter 14:
SetRate

SetRate Please note

General Operation Statement SETRATE uses the time units defined for the
model. (By default, SETRATE uses hours.)
Syntax samples

SETRATE <resource name>, <expression>, <unit #>

Example
SETRATE Operator, 25, 3 The logic below displays how you can uniquely assign
the regular rate for each unit of a resource, Operator.
Operator has three units, meaning that each unit can
Description perform the same task. However, each of the three
Allows you to define the regular rate of cost for Operators has a different hourly rate. We set these rates
in the Initialization logic using the following:
resources contained in a model. If you have
already defined the regular rate in the Cost mod-
ule, this statement will override that rate. You can
use SetRate to set different rates for each unit of a
resource.

Valid In
Initialization logic.

Components

<resource name>
The name of the resource whose rate you wish to set.
<expression>
The rate assigned to the resource. See Also
<unit #> GETCOST, GETRESRATE(), INCENTCOST,
The unit number of the resource. Where multiple INCLOCCOST, and INCRESCOST.
instances of a resource exist, you must specify which
instance of the resource to use (e.g., Tech1, Tech2,
Tech3, etc.). The keyword ALL may be used to indicate
all instances of a resource.
 ProModel 547
User Guide

Skip
Shift & Break Logic Statement

Syntax samples

SKIP

Description
In pre-off-shift or pre-break logic, a SKIP state-
ment causes any off-shift or break main logic to
be skipped as well as the off-shift or break time
defined in the shift file so that the affected loca-
tion or resource stays on line.
In off-shift or break logic, a SKIP statement
causes the off-shift or break time defined in the
shift file to be ignored. This is useful if you want
to define your own off-shift or break time as part
of the logic rather than use the time defined in the
shift file.

Valid In
Shift logic only.

Example

Suppose a Worker is scheduled to go on break at 10:15

for fifteen minutes. However, if there are more than
two parts in queue, the Worker will skip his or her
break to stay on schedule. The following logic is
entered in the pre-break logic for the resource, Worker.
IF Contents(Worker_Que) > 2 THEN SKIP

See Also
“Shift & Break Logic” on page 297. Also see
FORLOCATION() and FORRESOURCE().
548 Chapter 14:
Sound

Sound Example

General Action Statement The example below shows an entity’s operation logic.
A variable called Total is used to keep track of the
number of entities passing through the location. Every
Syntax samples 100th entity to pass through the location will cause the
sound “Tada” to sound, thus notifying the user of the
SOUND <string expression> 100th entity. In addition, ProModel resets the counter.
SOUND “Chimes.wav”
SOUND “Tada.wav”

Description
Plays a wavefile. Wavefiles, which have the
extension .WAV, may be purchased commercially
or created with a sound card. A few sounds, such
as the examples here, come with Windows and
are found in the Windows directory. Use SOUND
to alert a model’s user that some event has taken
place.

Valid In See Also

Any logic. PAUSE, DISPLAY, and PROMPT.

Components

<string expression>
The DOS name of the wavefile to be played. This
expression must evaluate to a valid DOS file. It may
include a path.
 ProModel 549
User Guide

Split As Components

Entity-Related Operation Statement <expression>

Split the entity into this number of entities. ProModel
Syntax samples evaluates this expression every time it encounters the
statement.

SPLIT <expression> AS <new entity name> <new entity name>

SPLIT 10 AS Entx The name of the resulting entities. Each split entity
searches forward in the process list, and then from the
beginning of the list, until it finds a process for the new
entity type at the current location.
Description
Splits an entity into the number of entities you Explicit Entity Actions
specify, changes the entity names, and divides all
cost and time statistics accrued by the base entity When you use the SPLIT AS statement, Pro-
between the new entities. ProModel counts the Model divides the accrued cost between the new
old entity as an exit and the resulting entities entities and counts the old entity as an exit. Each
share the same attribute values as the original new entity begins with new statistical informa-
entity. tion.

Any entity you wish to split must release all Implicit Entity Actions
owned resources using the FREE statement. Use
SPLIT AS to divide pieces of raw material into ProModel allows you to use the SPLIT AS state-
components. The entities formed by the SPLIT ment implicitly as part of the routing definition.
AS statement at a location will not appear in the To do this, define a route block with a Quantity
statistics for this location. field output value greater than 1 and the New
Entity option unchecked.
Valid In
Example
The operation column of process edit tables only.
ProModel does not allow SPLIT AS on convey-
In the following example, a batch of entities, Batch A,
ors, and not at the end of a queue. You also may
arrives at Loc1 for a 2 hour processing time. Once the
not use SPLIT AS after a ROUTE statement. Do
processing completes, BatchA splits into individual
not use SPLIT AS in combination with COM- entities called EntA. ProModel determines the number
BINE, CREATE, GROUP, UNGROUP, LOAD, of EntA’s resulting from the SPLIT AS statement by
UNLOAD, or other split statements in the same the value of BatchA’s attribute, Attr3.
process logic.
550 Chapter 14:
Split As

Process Table
Entity Location Operation (min)
BatchA Loc1 WAIT 2 Hr
SPLIT Attr3 AS EntA
EntA Loc1 USE Res1 FOR U(2,.3)

Routing Table
Blk Output Destination Rule Move Logic

1 EntA Loc2 FIRST 1

See Also
JOIN, GROUP, UNGROUP, and CREATE.
 ProModel 551
User Guide

Sqrt()
Math Function

Syntax samples

SQRT(<expression>)
Real1 = SQRT(Real2)

Description
Returns the square root of an expression.

Valid In
Any expression. This function returns a real num-
ber.

Components

<expression>
SQRT() returns the square root of this expression.

See Also
ROUND().

Please note

To get a root other than the square root, use the

exponentiation operator as shown in the follow-
ing formula:

X**(1/Y)

For example, where Y is the desired root, the for-

mula 9**(1/3) returns the cube root of 9.
552 Chapter 14:
Stop

Stop Example

General Operation Statement In the example below, a STOP statement is used in

Operation Logic to end the simulation whenever the
variable Total_Complete reaches 100.
Syntax samples

STOP {<string expression>}

STOP
STOP “Normal termination”

Description
Terminates the current replication and optionally
displays a message. The simulation will then con-
tinue with the next replication. Use STOP to end
a replication when the simulation has run long
enough to provide sufficient statistical data.

Valid In See Also

Any logic. BREAK, BREAKBLK, RETURN, and PAUSE.

Components

<string expression>
An optional message to display when the replication
stops.
 ProModel 553
User Guide

ThreadNum() debugger displays the process and logic that caused the
error, as shown below.

General System Function

Syntax samples

THREADNUM()
IF THREADNUM()=215 THEN DEBUG

Description
Every time any logic is executed, it is executed
by a thread which is assigned a unique number. By adding the statement, “IF THREADNUM() = 210
THREADNUM returns the number of the thread THEN DEBUG” before the statement that causes the
that called the function. This function is most error, the simulation will run until the proper process
useful in conjunction with the IF...THEN and and then bring up the debugger. The debugger can then
DEBUG statements to bring up the debugger at a be used to step through the process to find the particu-
certain process. See below for a detailed exam- lar statement causing the error.
ple. Note that if the model does not change
between simulation runs, every thread will have
the same number from run to run, but not from
See Also
replication to replication. Also, most changes in a
model will cause threads to have different num- DEBUG.
bers on subsequent runs.

Valid In
Any logic

Example

For example, suppose that when the 50th entity of a

certain type arrives at a certain location, the model
always crashes. A DEBUG statement at the beginning
of the processing logic would be cumbersome because
the debugger would come up forty-nine times before it
was needed. However, when the error occurs, the
554 Chapter 14:
TimeLeft()

TimeLeft() total of 10 minutes, but it only processes for 8 minutes

before you preempt the Gear, Lathe1 should process it
for only 2 additional minutes when it returns to Lathe1.
Preemption Logic System Function To do this, we assign the remaining process time using
TIMELEFT() to an attribute, Att1. We also check Att1
Syntax samples at Lathe1 to determine if it is greater than 0 to know
whether the Gear was executing the process for the
first time or as a preempted entity. Processing should
TIMELEFT() be as follows:
Attr1=TIMELEFT()

Process Table

Description Entity Location Operation (min)

Gear Lathe1 IF Att1=0 THEN WAIT 10
Returns the time remaining if the preemption ELSE WAIT Att1
occurred during a WAIT statement. The value Gear * Lathe1 Att1=TIMELEFT()
returned is in default time units and must be Gear Wait_Area
checked before any processing delay occurs since
* Preemptive Process Record
the value is updated whenever a preemption takes
place. If the value is referred to later, it should be
Routing Table
assigned to the entity’s attribute or to a local vari-
able. Blk Output Destination Rule Move Logic
1 Gear Lathe2 FIRST 1
If several entities were preempted at a location,
1 Gear Wait_Area FIRST 1
the value returned by the function to each entity
1 Gear Lathe1, 99 FIRST 1
will be taken from whichever entity has the larg-
est time remaining in the WAIT statement.
See Also
When no units are specified in the parentheses in
“Preemption Process Logic” on page 292.
this function, it returns the default time unit spec-
ified in the General Information dialog.

Valid In
Operation logic defined as a preemptive process.

Example

You may preempt an entity called Gear while it pro-

cesses at a location called Lathe1. When you preempt
the Gear, it should go to a location called Wait_Area
where it waits to return to Lathe1. When it returns to
Lathe1, the lathe should continue processing the Gear
from where it left off when you preempted the Gear.
For example, if Lathe1 must process the Gear for a
 ProModel 555
User Guide

TimesUsed() Example

General System Function In the example below, when an EntA arrives at Loc1, it
will only use the resource Res1 if the resource has been
used five or fewer times. If the resource has been used
Syntax samples more than five times, EntA will use Res2 instead.

TIMESUSED(<resource>)
IF TIMESUSED(Res1) > 5 then USE Res2 for 10
Process Table
Entity Location Operation (min)
EntA Loc1 IF TIMESUSED (Res1)> 5
Description THEN USE Res2 FOR 10
ELSE USE Res1 FOR 10
Returns the number of times a resource has been
used.
Routing Table
Valid In Blk Output Destination Rule Move Logic
Any logic and any field evaluated after transla-
tion. For a list of fields evaluated after transla-
tion, see the “Appendix A” on page 577. See Also
UNITS().
Components

<resource>
The name of the resource to examine. RES() may be
used here.
556 Chapter 14:
Trace

Trace CLOSE
Turns tracing off and closes the trace listing.
General Action Statement

Syntax samples Example

In this example, a message will appear in the trace list-

TRACE {<message>}{STEP or CONT or OFF or
ing whenever Agent1 and Agent2 have been captured
CLOSE}
and the downtime for Gate1 begins. Another message
TRACE “Begin Test for Resource A” will appear in the trace listing at the end of the down-
TRACE CONT time.

TRACE CLOSE

Description
Turns tracing on and off. Trace listings will
appear in a separate window on the screen. Use
trace to follow the logical flow of a model.

Valid In
Any logic.
See Also
Components
DEBUG.
<message>
The message to appear in the trace listing when the
TRACE statement is encountered. The message can be
any string expression.
STEP
Makes ProModel wait for the user to click the left
mouse button to execute the next statement or trace
continuously while the right mouse button is held
down. TRACE statements default to step.
CONT
Steps continuously without user intervention. Clicking
the right mouse button will step through the logic.
OFF
Turns tracing off but does not close the trace listing.
 ProModel 557
User Guide

Trunc()
Type Conversion Function

Syntax samples

TRUNC(<expression>)
Integer1=TRUNC(3.9)

Description
Returns a real expression truncated to an integer.
Any digits to the right of the decimal place will
be removed. When necessary, ProModel auto-
matically converts real values to integers by trun-
cating them. For more information about
ProModel automatically converting between
reals and integers, see “Converting Between
Numeric Types” on page 397.

Valid In
Any expression. This function returns an integer.

Components

<expression>
The expression to be truncated.

See Also
ROUND().
558 Chapter 14:
Ungroup

Ungroup Please note

Entity-Related Operation Statement If you are trying to ungroup an entity that has
never been grouped, ProModel ignores the
UNGROUP statement.
Syntax samples

UNGROUP {LIFO}
UNGROUP Components
UNGROUP LIFO
LIFO
Last In, First Out. Starts the ungrouped entities pro-
cessing from last to first, rather than from first to last.
Description If this option is not specified, the ungrouped entities
Separates entities that were grouped with the will be processed FIFO, or First In, First Out.
GROUP statement. Each of the resulting entities
searches ahead in the process list and then from
the beginning of the list until a process is found Explicit Entity Actions
that has been defined for that entity type at the With an UNGROUP, ProModel dissolves the
current location. The first entity processed from temporary shell and divides costs among the
the group takes any resources the group owns. If ungrouped entities (ungrouped entities may
a grouped entity has members that are also include smaller clusters of grouped entities).
grouped entities, only the top level group is
ungrouped with an UNGROUP statement. An Example
additional UNGROUP will ungroup any member
groups.
The example below is the continuation of the GROUP
statement example where EntA, EntB and EntC were
Valid In grouped to form Grp_A. Now the entities are
The operation column of process edit tables only. ungrouped with all of their original properties. (See the
You may not use UNGROUP on conveyors nor at GROUP statement example.)
the end of a queue. UNGROUP may not be used
in combination with COMBINE, CREATE,
UNGROUP, LOAD, UNLOAD, SPLIT AS or
other UNGROUP statements in a processing
logic. It may follow a GROUP statement no more
than once in the same processing logic to allow
batch processing.
 ProModel 559
User Guide

Process Table
Entity Location Operation (min)
Grp_A Loc3 UNGROUP
EntA Loc3 USE Res1 FOR 2 min
EntB Loc3 USE Res1 FOR 2 min
EntC Loc3 USE Res1 FOR 2 min

Routing Table
Blk Output Destination Rule Move Logic

1 EntA Loc4 FIRST 1 MOVE FOR 2

1 EntB Loc5 FIRST 1 MOVE FOR 2
1 EntC Loc6 FIRST 1 MOVE FOR 2

See Also
GROUP, LOAD, JOIN, COMBINE, and SPLIT
AS. See “Attributes” on page 217 for more infor-
mation.
560 Chapter 14:
Units()

Units()
General System Function

Syntax samples

UNITS(<location> or <resource>)
PAUSE “There are” $ UNITS(Res1) $ “Res1's in the
system.”

Description
Returns the total units of a location or resource.

Valid In
Any logic and any field except those evaluated
before translation. For a list of fields evaluated
before translation, see “Appendix A” on
page 577.

Components

<location>
The name of the location to examine. You may substi-
tute LOC() for the name of a location.
<resource>
The name of the resource to examine. You may substi-
tute RES() for the name of a resource.

See Also
FREEUNITS() and RESQTY().
 ProModel 561
User Guide

Unload number of entities that have been loaded, the extra

quantity is ignored. This expression is evaluated every
time the statement is encountered.
Entity-Related Operation Statement
IFF <Boolean expression>
This option allows the UNLOAD command to be con-
Syntax samples ditional. Any attributes, entity functions, and location
functions apply to the entity to be unloaded, not to the
UNLOAD <expression> {IFF <Boolean expression>} base entity. This technique allows only entities with
UNLOAD 5 certain properties to be unloaded from the base entity.
To use attributes, entity functions, and location func-
UNLOAD 5 IFF Entity() = EntA tions that apply to the base entity, assign the desired
value to a local variable and use the local variable in
the Boolean expression.

Description
Unloads a certain quantity of entities, or a certain Explicit Entity Actions
quantity of those entities depending on a condi- UNLOAD divides up costs and copies statistical
tion. Use UNLOAD to unload entities from a car- information accrued while loaded, to each
rier entity that was previously loaded with unloading entity.
LOAD. The unloaded entities are processed
ahead of the entity which unloaded them. Each
unloaded entity searches ahead in the process list,
Example
and then from the beginning of the list, until a
process is found for that entity type at that loca- The following example is a continuation of the LOAD
statement example and shows how the loaded entity
tion.
(Truck) is unloaded, resulting in the original Truck and
the boxes that were loaded onto it. Boxes continue to
Valid In the next location while Truck is returned to its starting
The operation column of process edit tables only. location, Factory. (See the Load statement example.)
UNLOAD is not valid at conveyors, after routing,
or at the end of a queue. You may not use
UNLOAD in combination with COMBINE,
CREATE, GROUP, UNGROUP, and SPLIT AS
or other UNLOAD in the same process logic. If
the process contains LOAD statements,
UNLOAD can only appear once after all of them.

Components

<expression>
The number of entities to unload. A value of zero is
ignored and a negative value produces an error. If the
quantity specified for unloading is greater than the
562 Chapter 14:
Unload

Process Table
Entity Location Operation (min)
Box Shipping WAIT 2 min
Truck MfgSite
Truck Dock LOAD Attr1 IN 2 Hr
Truck NewYork WAIT T(20,30,60)
UNLOAD 5
Box NewYork
Truck Chicago WAIT T(20,30,60)
UNLOAD 5
Box Chicago
Truck Boston WAIT T(20,30,60)
UNLOAD 5
Box Boston

Routing Table
Blk Output Destination Rule Move Logic
1 Box Dock LOAD 1 MOVE FOR 45
sec
1 Truck Dock FIRST 1 MOVE FOR 10
min
1 Truck NewYork FIRST 1 MOVE FOR 24
Hr
Truck Chicago FIRST MOVE FOR 12
Hr
Truck Boston FIRST MOVE FOR 28
Hr
1 Truck MfgSite FIRST 1 MOVE FOR 24
Hr
1 Box NY_Recv FIRST 1 MOVE FOR 5
min
1 Truck MfgSite FIRST 1 MOVE FOR 12
Hr
1 Box Chi_Recv FIRST 1 MOVE FOR 5
min
1 Truck MfgSite FIRST 1 MOVE FOR 28
Hr
1 Box Bos_Recv FIRST 1 MOVE FOR 5
min

See Also
LOAD, COMBINE, JOIN, GROUP, and
UNGROUP. Also see “Attributes” on page 217
for more information.
 ProModel 563
User Guide

Use Valid In
Location processing logic, downtime logic, and
Resource-Related Operation Statement move logic.

Syntax samples Components

USE {<quantity>} <resource> {,<priority>} <quantity>

FOR <time> {AND or OR {<quantity>} The number of resources to get. ProModel ignores a
<resource> {,<priority>} FOR <time>... } value of zero and values less than zero return an error.
USE 2 Res2, 5 FOR 4:23:03 ProModel evaluates and truncates this numeric expres-
sion every time it encounters the USE statement.
USE 2 Res1 FOR 2.0 min OR 3 Res2 FOR 1.5 min
<resource>
USE Res1, 3 FOR 1 hr AND (Res2 FOR 5 OR Res3
FOR 5) The name of the resource to USE. You can substitute
RES() for the resource name.
USE Oper_Attr RES(Type_Attr) FOR Time_Var1 Hr
<priority>
When multiple entities request a resource, ProModel
fills the requests in order of priority. This expression
Description should be a number between 0 and 999.
Captures a resource or combination of resources <time>
as each resource becomes available. Once the
The length of time the entity will tie up the resource.
resource has been captured it is used for the spec- ProModel evaluates this expression whenever it
ified amount of time, and then freed when the encounters the statement. If you specify no time unit,
specified duration is over. If the entity already ProModel applies the default time unit specified in the
possesses one of the specified resources from a General Information dialog.
previous GET, JOINTLY GET, or MOVE WITH
statement, the entity will still try to capture an
additional unit of that resource. Example

Please note This simple example shows how Clients arriving at

location Reception must USE the Secretary for some
If an entity uses a USE statement to capture a amount of time according to the user-defined distribu-
resource, the resource must complete its opera- tion, Dist1. Clients are then sent to a waiting area until
the desired next location becomes available.
tion before you can preempt the entity. However,
if the entity uses a GET, WAIT, FREE sequence,
you may preempt the entity during the WAIT por-
tion of the logic.
564 Chapter 14:
Use

Process Table
Entity Location Operation (min)
Client Reception USE Secretary
FOR Dist1()
Client Waiting

Routing Table
Blk Output Destination Rule Move Logic
1 Client Waiting FIRST 1 MOVE FOR 30
sec
1 Client Loan .400 1 MOVE FOR 1
Client Auditor .350 1 MOVE FOR 1
Client Service .250 1 MOVE FOR 1

See Also
GET, JOINTLY GET, and MOVE WITH.
 ProModel 565
User Guide

Variable() Example

General System Function .In the example below, parts of different types arrive at
location In_Queue. Each entity type has a unique value
for Attr1 that corresponds to the name-index number of
Syntax samples a variable in the Variables module. Once parts arrive at
In_Queue, they increment the variable specific to that
VARIABLE(<numeric expression>) entity type before routing to the location Process_Loc.

VARIABLE(Attr) = 124
VARIABLE(x) = VARIABLE(y)
Process Table
N=VARIABLE(x) + VARIABLE(y) - 1
Entity Location Operation (min)
All In_Queue VARIABLE(Attr1) =
VARIABLE(Attr1) + 1
Description
Converts a name-index number or integer to a Routing Table
variable name. Use this function when a numeric
Blk Output Destination Rule Move Logic
expression uses a variable whose name-index 1 All Process_Loc FIRST1 MOVE 1
number is stored in an attribute, array, or vari-
able.
See Also
Valid In LOC(), ENT(), and RES().
Any logic.

Please note

You cannot use VARIABLE() in a PROMPT, INC,

DEC, or READ statement.

Components

<numeric expression>
The name index number for a variable. You can deter-
mine the name-index number associated with a particu-
lar variable by the position of the variable record in the
Variables module.
566 Chapter 14:
View

View Example

General Action Statement You are giving a presentation on the use of simulation
for airport design. Two hours into the model run, you
want to zoom in on the baggage area to show the activ-
Syntax samples ity there. Three hours into the simulation, you want to
zoom out to show the entire airport..You are giving a
VIEW “view name” presentation to management on the factory floor using
simulation. Two hours into the simulation, you want to
VIEW “Cell5” zoom in on a particular cell in the factory to show the
VIEW “View10” activity there. Three hours into the simulation, you
want to zoom out to show the entire factory.
To do this, define two views called Cell1 and Factory
using the Views editor on the View menu. Define an
Description independent subroutine and call it in the initialization
Use this statement to change the view in the Lay- logic using the ACTIVATE statement. Enter the fol-
out window from within your logic. Once the lowing logic in the subroutine:
view has been defined from the View menu in INT X=1
main menu, you can use it in the logic. WHILE X=1 DO
BEGIN
Valid In IF CLOCK(hr) = 2 THEN VIEW “Cell1”
IF CLOCK(hr) = 3 THEN VIEW “Factory”
All logic. WAIT 1 hr
END
Components

<view name>
See Also
The name of the view defined in the Views dialog.
Enclose the name in quotation marks. “Commands” on page 83.
 ProModel 567
User Guide

Wait Components

Entity-Related Operation Statement <time expression>

The length of the WAIT. This expression is evaluated
Syntax samples whenever the statement is encountered. If no time unit
is specified, the default time unit specified in the Gen-
eral Information Dialog is applied.
WAIT <time expression>
WAIT 3 min
WAIT 0 Example
WAIT 2.5 + CleanupTime
In the following example, customers arrive at a fast-
WAIT N(8,.5) + 3 sec food restaurant and place their orders at location
Counter. How long customers wait depends on the
type of meal ordered. If they order meal one, two, or
three, they wait only 2 minutes. Otherwise they wait 5
Description minutes.The example below shows WAIT statements
Simulates the time it takes to process an entity. used in an IF...THEN...ELSE expression. If the value
of EntA’s attribute, Attr1, is greater than zero, the time
WAIT delays further processing of the entity until
delay is 5.0 minutes. Otherwise the delay is 2.5 min-
the specified time has elapsed. The rest of the
utes.
model continues to process while an entity waits.
If the expression evaluates to zero, the current
entity will not finish processing until all other
processes scheduled for that moment in the simu- Process Table
lation have finished.
Entity Location Operation (min)
EntA Loc1 IF Attr1>0 THEN
Please note WAIT 5 min
ELSE
You may use the “^” symbol in place of a WAIT 2.5 min
“WAIT” statement.
Routing Table
Blk Output Destination Rule Move Logic
1 EntA Loc2 FIRST 1 MOVE FOR 10
Valid In
Location processing, downtime, and move logic. See Also
Independent subroutines may also use WAIT
WAIT UNTIL can stop additional processing
statements which function as timers. (For more
until a condition is true.
information about Independent subroutines, see
“Subroutines” on page 238.)
568 Chapter 14:
Wait Until

Wait Until Example

Entity And Resource-Related Operation State- The example below uses the WAIT UNTIL statement
to group a variable quantity of entities. As each EntA
ment
arrives at Loc1, a variable (Total) is incremented to
keep track of the total entities waiting at the location.
Syntax samples The WAIT UNTIL statement causes processing of all
EntA’s to halt at this point until the variable, Var1,
WAIT UNTIL <Boolean expression> reaches or exceeds 500. Then all of the waiting EntA’s
are GROUPed together as a BatchA.
WAIT UNTIL Var1 > 3
WAIT UNTIL Var1 < Attr3 AND Var2 >= 5

Process Table
Entity Location Operation (min)
Description
EntA Loc1 INC Total
Delays processing of the current logic until the WAIT UNTIL Total >= 5
Boolean expression is true. The rest of the model GROUP Total AS Batch
continues to process during the delay. Note that
if the expression is initially evaluated to be false, Routing Table
it is only reevaluated when a location attribute,
Blk Output Destination Rule Move Logic
variable, or array element in the expression
changes. Multiple entities waiting on the same
condition are released one at a time. This allows
See Also
a released entity to change a variable value that
will prevent the other waiting entities from being DO...WHILE, WHILE...DO, and DO...UNTIL.
released.

Valid In
Node entry and node exit logic delays processing
for resources, and location processing logic
delays processing for entities. Independent Sub-
routines. (See “Subroutines” on page 238.)

Components

<Boolean expression>
The condition that must be satisfied to continue pro-
cessing the entity or resource. Elements of this expres-
sion are limited to location attributes, variables, and
array elements.
 ProModel 569
User Guide

Warmup Example

General Action Statement Suppose you want to base the warmup period on 2,000
entities being processed rather than on a lapse of time.
You could increment a variable (e.g., Total_Processed)
Syntax samples whenever an entity exited the system. Enter the follow-
ing logic in an independent subroutine activated from
WARMUP the initialization logic:

WARMUP WAIT UNTIL Total_Processed = 2000

IF thruput = 50 THEN WARMUP WARMUP

Description See Also

Instructs the simulation to end the warmup period See “Simulation Options” on page 338 for more
by resetting all the statistics and erasing relevant information on warm-up periods.
time series files. Only one WARMUP statement
may be used in the simulation.

Please note

If multiple WARMUP statements are encountered

or a WARMUP statement is used in addition to
the warmup time specified in the Run Options
dialog, ProModel will generate a warning to
inform you that this has occurred. Only the first
warmup encountered (the statement or the Run
Options setting) will actually be executed. While
the statement will be encountered within the
logic, the Run Options setting will be executed at
the specific time indicated in the dialog.

Valid In
Any logic.
570 Chapter 14:
While...Do

While...Do Example

General Control Statement The example below shows the arrival logic window for
an entity that arrives every 40 hours to reset the values
of Array1 elements 1 through 100 to 0.
Syntax samples

WHILE <Boolean expression> DO <statement block>

WHILE Array1[n] <> 10 DO INC n
WHILE FREECAP(Loc1) > 5 DO
BEGIN
INC Var2, 5
WAIT 5 sec
END

Description
Repeats a statement or statement block continu-
ously while a condition remains true.
WHILE...DO is an entry-condition loop, meaning See Also
that the loop will not be executed once unless the BEGIN, END, DO...WHILE, and DO...UNTIL.
Boolean expression is true.

Valid In
Any logic.

Components

<Boolean expression>
As long as this expression is TRUE, the loop will con-
tinue. This expression is evaluated for each iteration of
the loop.
<statement block>
The statement or block of statements to execute.
 ProModel 571
User Guide

Write <maximum digits before decimal>

The maximum number of digits before the decimal.
This value is used to line up any numeric values into
General Operation Statement
columns on the decimal point. This value may be any
numeric expression.
Syntax samples <digits after decimal>

WRITE <file ID>, <string or numeric expression> The number of spaces to save after the decimal point.
{,<maximum digits before decimal>, Use this option to line up any labels appearing after
<digits after decimal>} numbers.

Example
Description
Writes information to a general write file. The The following example uses both WRITE and WRITE-
next item written to the file will appear immedi- LINE to record the time when EntA completes pro-
ately after this item. WRITE always appends to cessing at Loc1 in a general write file called Rpt.
the file unless the file is RESET. This holds true
for multiple replications as well as single, inde-
pendent runs. Any file that is written to with
Process Table
WRITE automatically becomes a text file and
will have an end of file marker attached automat- Entity Location Operation (min)
ically to the end when it is closed. For more flex- EntA Loc1 WAIT N(7.3,.4)
ible WRITE capability, use XWRITE. WRITE Rpt,”EntA Complete at:”
WRITELINE, Rpt CLOCK(min),3,2
WRITE and WRITELINE automatically separate
values by commas Routing Table

Valid In Blk Output Destination Rule Move Logic

Any logic.
See Also
Components XWRITE, WRITELINE, RESET, READ, and
FORMAT(). Also see “External Files” on
<file ID> page 254.
The name of the file as previously defined in the Exter-
nal Files Editor. Please note
<string or numeric expression>
The string or numeric expression to be written to the The sum of the maximum digits before and after
file. In the output file, quotes will automatically be the decimal must be less than 20.
added to string expressions so that most spreadsheet
programs can easily read the file.
572 Chapter 14:
WriteLine

WriteLine <digits after decimal>

When writing real numbers, the maximum number of
digits after the decimal.
General Operation Statement

Syntax samples
Example
WRITELINE <file ID>, <string or numeric expres-
The following example uses both WRITE and WRITE-
sion>{,<maximum digits before decimal>, <digits
LINE to record the time when EntA completes pro-
after decimal>}
cessing at Loc1 in a general write file called Rpt.

Description
Process Table
Writes information to a general write file and
starts a new line. WRITELINE always appends Entity Location Operation (min)
to the file unless the file is RESET. Any file that EntA Loc1 WAIT N(7.3,.4)
WRITE Rpt, "EntA Complete at:"
is written to with WRITELINE automatically WRITELINE Rpt, CLOCK(min),3,2
becomes a text file and will have an end of file
marker attached to the end when it is closed. Routing Table
WRITE and WRITELINE automatically separate
Blk Output Destination Rule Move Logic
values by commas

Valid In
See Also
Any logic.
WRITE, RESET, XWRITE, READ, and FOR-
MAT(). Also see “External Files” on page 254.
Components
Please note
<file ID>
The name of the file as previously defined in the Exter- The sum of the maximum digits before and after
nal Files Editor. the decimal must be less than 20.
<string or numeric expression>
The string or numeric expression to be written to the
file. In the output file, quotes will automatically be
added to string expressions so that most spreadsheet
programs can easily read the file.
<maximum digits before decimal>
When writing real numbers, the maximum number of
digits before the decimal. Use this value to line num-
bers on different lines up on the decimal.
 ProModel 573
User Guide

Xsub() type of structure. The parameters can then be

used through structure overlaying. Integers are
passed as four byte values and reals are passed as
External Subroutine Call eight byte IEEE values.

Syntax samples Please note

XSUB(<file ID>, <ordinal function number> or <func-
For Windows Programmers Only The handle to
tion name> {, <parameter1>, <parameter2>...})
the run-time simulation frame window will be the
XSUB(Interface,1, 5) last parameter passed. Most subroutines can
XSUB(LogDLL, “_Log_B_of_X”,10,5) completely ignore this parameter, but it will be
needed if the subroutine displays a window.

Description Valid In
Calls an external subroutine inside a DLL file. Any expression or logic.
XSUB() is perhaps the most powerful statement
in ProModel, because by using it the user can Components
access the entire functionality of any 32-bit Win-
dows programming language such as C, C++,
<file ID>
Delphi, or Visual Basic. XSUB() can be used for
sophisticated file IO and to make simulations The file ID assigned to an external DLL file as defined
interactive. In fact, subroutines called with in the External Files editor. This file should be a 32-bit
XSUB() can do anything that the language they Windows DLL file.
were written in allows. Because of its power, <ordinal function number>
however, XSUB() should be used with caution. The ordinal number of the function inside the DLL.
When called, the simulation is suspended until This function must be exportable. When DLL’s are
the external subroutine finishes execution. compiled, every exported function inside them is num-
bered. The individual functions can then be accessed
The subroutine inside the DLL must have been
by calling the program by number. This field may be
compiled as exportable by a Windows 32-bit
an expression that evaluates to an ordinal function
compiler and have a return type of IEEE format number that is valid inside the DLL. Use an ordinal
double real. XSUB() will copy the parameters function number or the function name.
following the function name to a block of mem-
<function name>
ory, then pass the function a pointer to that block
of memory. The name of the function inside the DLL. This func-
tion must be exportable. Note that when most compil-
The function can take only one parameter: a ers compile DLL’s, they adjust the name of the
pointer to void. But the function may access any functions inside them. The function name inside the
number of parameters through structure overlay- XSUB statement must be the adjusted name, not the
ing. The function should define a structure to original name.
match the type and order of the parameters, and Most C compilers add an underscore to the function
assign the pointer just passed to a pointer to that name; so a function called “Test1” would be compiled
574 Chapter 14:
Xsub()

as “_Test1.” For most C++ compilers, valid ProModel HWND hWndFrame;

external function names will be mangled to “@<func- };
tion name>$pv.” Different compilers will vary, how-
extern “C” //This makes this a C function rather than a
ever, so the user should be aware of the particular
C++ function
compiler’s quirks.
{
<parameters> /* On compile, Borland and Microsoft add a leading
underscore to a 'C' name! */
The parameters to pass to the function. These may be
double _export Log_B_of_X(void *p)
any variable, number, or expression. They are only
{
limited by the type of field or logic that uses the XSUB
function. Each parameter should be separated by a
//Parameters come in a structure pointed to by p;
comma. See above for how the external subroutine will
TEST_SUB_PARAMS * params;
access these parameters.
params = (TEST_SUB_PARAMS*) p;
MessageBox (GetTopWindow (params->hWnd-
Example Frame),
“Executing Log_B_of_X function.”, “XSUB”,
An external function written to the ProModel specifi- MB_OK);
cation, called Log_B_of_X and written in C, returns return log (params->x) / log (params->base);
the log of a value to a variable base. The function, }
reproduced below, has been compiled into the DLL, }
“XSUB.DLL.” The function itself is reproduced on the
left below, and the source code can be found in the file
“XSUB.CPP.” See Also
The ProModel logic statements assign the base five “Subroutines” on page 238 (normal subroutines
logarithm of the real variable R1 to the real variable are less powerful, but much easier to create and
R2. Each statement assumes that the file XSUB.DLL use).
has been assigned the identifier “Log” in the External
Files Editor. The first statement accesses the function
as if the DLL had been compiled in C++ by using the
mangled function name. The second statement
accesses the function as if it had been compiled in C by
using the C adjusted function name. The third state-
ment accesses the function using the ordinal function
number.
ProModel Logic
R2 = XSUB(Log, “@Log_B_X$pv”,5.0,R1)
R2 = XSUB(Log, ”_Log_B_X”,5.0,R1)
R2 = XSUB(Log, 2, 5.0, R1)
XSUB.CPP
struct TEST_SUB_PARAMS
{
double base;
double x;
 ProModel 575
User Guide

Xwrite Example

General Operation Statement The following example uses XWRITE to record the
time each Box completes processing at location Ship.

Syntax samples

XWRITE <file ID>, <string or numeric expression> Process Table

Entity Location Operation (min)
Box Ship WAIT N(7.3,.4)
XWRITE Rpt, “Box Shipped at:”
Description $ FORMAT(CLOCK(min),3,2)
Writes information to a general write file in any
text format the user chooses. XWRITE is for Routing Table
writing user-formatted files, while WRITE and
Blk Output Destination Rule Move Logic
WRITELINE are for writing special formatted
1 Dock Doc FIRST 1 MOVE FOR
text files. XWRITE always appends to a file 5
unless the file is RESET. Note that any time a
WRITE or WRITELINE writes to a file, the file
See Also
will automatically be a text file. No end of file
marker is appended to files written only with WRITE, WRITELINE, and RESET. Also see
XWRITE. In subsequent replications, additional “External Files” on page 254.
items are appended to the end of the file unless
the file is RESET. ProModel does not format the
string expression, although you can use the FOR-
MAT statement to manually format data. To add
an end of file marker to a user-formatted file, use
XWRITE CHAR(26).

Valid In
Any logic.

Components

<file ID>
The name of the file as previously defined in the Exter-
nal Files Editor.
<string or numeric expression>
The string expression to be written to the file.
576 Chapter 14:
Xwrite
 ProModel 577
User Guide

Appendix A

ProModel evaluates various fields and logic at 5. General System Functions

different times during a simulation run. Some
Cap(), CalDay(), CalDom(), CalHour(),
evaluate only once when the model prepares to
CalMin(),CalMonth(), CalYear(), Clock(), Con-
run a simulation, called the translation time. Pro-
tents(), DownQty(), Entries(), FreeCap(), Free-
Model evaluates others as necessary throughout
Units(), OwnedResource(), TimesUsed(), Units(),
the simulation. Below is a list of all expressions
and Variable().
and statements by category, and a table telling
which fields evaluate at translation and which
6. Location-Specific System Function
fields ProModel evaluates continuously during a
simulation. The table also tells where you may Location().
use an expression or statement.
7. Resource-Specific System Function
Expression and Statement Groups Resource().

1. General Expression 8. Node Logic-Specific System Functions

Numbers, Variables, Math Functions, Functions Last(), Next(). (The Last function is valid only in
Table, Distribution Functions, XSUB(), and Node Entry Logic and the Next function is valid
Name Functions (i.e., RES(), ENT(), LOC()). only in Node Exit Logic.)

2. Arrays 9. Downtime-Specific System Function

Arrays of any dimension. DTDelay().

3. Location Attributes 10. Shift-Specific System Functions

Referencing a location attribute in any expression ForLocation(), ForResource().
or assigning to a location attribute.
11. Preemption Logic-Specific System Func-
4. Entity-Specific System Functions and tions
Attributes Preemptor(), TimeLeft().
Entity(), GroupQty(), ResQty().
578

12. Off-Shift & Break Logic-Specific System 20. Graphic Statement

Functions & Statements
Graphic.
DTLeft(), Priority, and Skip.
21. Wait Until Statement
13. Cost Functions & Statements
Wait until.
GetCost(), GetResRate(), IncEntCost, IncLoc-
Cost, and IncResCost. Macros and Subroutines
14. General Statements: (Run-Time Only) A macro may be used in any expression field, but
the macro may only contain expressions which
Activate, Animate, Assignment, Begin End, return a value (e.g., Entries(LOC1), U(5,1)).
Break, BreakBLK, Close, Comment(#, When a macro is used in a logic field, the macro
//, /*...*/), Debug, Dec, Display, Do...Until, may include any logic element that is valid in that
Do...While, Goto, If...Then/If...Then...Else, Inc, logic field. A subroutine may also be used in an
Int, Local Variable, Log, MapArr, Order, Pause, expression field provided that the Return state-
Prompt, Read, Real, Reset, Reset Stats, Return, ment is used to return a value to the expression
Report, Send, SetRate, Stop, String Expressions, field. When a subroutine is used in a logic field,
Sound, Trace, View, WarmUp, While...Do, and the subroutine may include any logic element that
Write/Writeline/XWrite. (You may not use the is valid in that logic field.
Log statement in Initialization or Termination
Logic.)

15. Operation Statements (Group 1)

Accum, Combine, Create, Group, Join, Load,
Match, Move, Rename, Route, Split As,
Ungroup, and Unload.

16. Operation Statements (Group 2)

Free, Get, Jointly Get, and Use.

17. Operation Statements (Group 3)

Wait.

18. Move Logic-Specific Statements

Move For, Move On, and Move With.

19. External Spreadsheet File

Entity Location Expression File.
 ProModel 579
User Guide

Valid Expression and Statement the edit fields in this manner and shows the
Groups by Field expression and statement groups that can be used
in each field. Fields are classified as either
When running a simulation, expressions and expression fields or logic fields. Fields not listed
statements are either evaluated 1) once at transla- on this chart are either menu fields or expression
tion (before initialization logic and before any fields that accept only numbers.
events are created) or 2) continuously during the
simulation run. The following chart categorizes

Fields Evaluated Only at Translation

Field Name
(evaluated at translation) Field Type 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

Variables
Initial Value Exp • •
Function Table
Dependent Value Exp • •
Independent Value Exp • •
Simulation Options
Warm-up Hours Exp • •
Run Hours Exp • •
Replications Exp • •
Interval Length Exp • •
Path Networks
Node Capacity Exp • •
Segment Distance Exp • •
Speed Factor Exp • •
Resources
Resource Units Exp • •
Locations
Location Capacity Exp • •
Conveyor
Length Exp • •
Speed Exp • •
Queue
Queue Length Exp • •
580

Field Name
(evaluated at translation) Field Type 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

Shifts
Shift Start Time Exp • •
Entities
Entity Length Exp • •
Entity Width Exp • •
 ProModel 581
User Guide

Fields Evaluated During Simulation

Field Names
(during simulation) Field Type 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

Logic
Initialization Logic Logic • • • •
Termination Logic Logic • • • •
Entities
Speed Exp • • • • • • •
Path Networks
Traveling Time per
Path Segment Exp • • • •
Resources
Acceleration Exp • • • •
Deceleration Exp • • • •
Empty Load Speed Exp • • •
Full Load Speed Exp • • • •
Pickup Time Exp • • • • • • •
Deposit Time Exp • • • • • • •
Node Entry Logic Logic • • • • • • • •
Node Exit Logic Logic • • • • • • • •
Location Clock DT
First Occurrence Exp • • •
Frequency Exp • • •
Priority Exp • • •
Clock DT Logic Logic • • • • • • • • •
Location Entry DT
First Occurrence Exp • • •
Frequency Exp • • •
Entry DT Logic Logic • • • • • • • • •
Location Usage DT
First Occurrence Exp • • •
Frequency Exp • • •
Priority Exp • • •
Usage DT Logic Logic • • • • • • • • •
582

Field Names
(during simulation) Field Type 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

Location Setup DT
Setup DT Logic Logic • • • • • • • • • • •
Resource Clock DT
First Occurrence Exp • • •
Frequency Exp • • •
Priority Exp • • •
Clock DT Logic Logic • • • • • • • • •
Resource Usage DT
First Occurrence Exp • • •
Frequency Exp • • •
Priority Exp • • •
Usage DT Logic Logic • • • • • • • • •
Operation
Operation Logic Logic • • • • • • • • • • • • • •
Preemption
Preemption Logic Logic • • • • • • • • • • • • • •
Routing
Priority for Destination Exp • • • • • • •
Destination Exp • • • • • • •
Entity Output Quantity Exp • • • • • • •
User Condition Rule Exp • • • • • • •
Move Logic Logic • • • • • • • • • • • • • •
Arrivals
First Occurrence Exp • • •
Frequency Exp • • •
Occurrences Exp • • •
Qty of Each Arrival Exp • • •
Arrival Logic Logic • • • • • • • • •
Shift Assignments
Priorities Exp • •
Pre-Off Shift Logic Logic • • • • • • • •
Off Shift Logic Logic • • • • • • • • • •
 ProModel 583
User Guide

Field Names
(during simulation) Field Type 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Pre-Break Logic Logic • • • • • • • •
Break Logic Logic • • • • • • • • • •
Subroutines
Interactive Subroutines Logic • • • • • •
Debugger
Debug Condition Exp • • • • • •
584

Program Defaults Default Values

This section discusses and lists the default set- Build Menu
tings when you first run ProModel.
Graphic library promod.glb
As in most software packages, ProModel makes
Locations
certain assumptions regarding the most useful
settings for the program. While your models may Conveyor/queue style roller
require different settings, an effort has been made Conveyor/queue width 3
to select the most common and helpful default (feet)
settings. Conveyor speed (fpm) 60
Since ProModel can be used for a wide variety of Conveyor accumulating accum
applications, you may require different settings. Conveyor entity orientation lengthwise
As your models differ, so will the need to change Location statistics time series
these settings from their default. However, when
ProModel is first launched and no INI file exists Entities
for it, the defaults in the following table apply. Entity speed 150 fpm (50 mpm)
Some defaults involve edit field values, some are Entity statistics time series
check box settings, etc.
Path Networks
Many defaults can be changed by selecting one of Time/speed Speed
the Model Default options under the Tools menu.
Path color blue/yellow
Other defaults can only be changed in the Build
modules. Still others can only be changed by Resources
directly editing the .INI file. Speed 150 fpm (50 mpm)
After ProModel is first launched, the pro- Entity search Longest Waiting
mod.ini(initialization) file is created. To change Resource search Closest resource
the .INI file defaults, you must edit the it using an
Resource statistics By unit
ASCII text editor (e.g., Windows Notepad). DO
NOT attempt to edit the .INI file unless you are Processing
fully comfortable doing so and only after you Snap to border off
make a backup copy of the original .INI file.
Variable statistics time series
 ProModel 585
User Guide

Tools Menu INI Defaults

Long build menu on Graphic Editor
Confirm record delete on Text alignment center
Recalculate path lengths on Text frame type transparent
when adjusted
Text frame shape rectangle
Text font Arial 8 Bold
Text color black
View Menu Text frame border color black
Snap to grid off Text frame fill color white
Show grid off Variables
Grid size (VGA full layout) 90 grid units Digit font Arial 8 Bold
Scale - distance 1 ft/grid unit Digit color yellow
Scale - time .01 min/grid unit Digit frame type recessed
Background color lt. gray Digit frame shape rectangle
Edit table font Arial 8 Regular Digit frame border color black
Edit table color Gray Digit frame fill color royal blue
Conveyors/Queues
Queue border color black
Directories Queue fill color dark gray
Models c:\ProModel\models Gauges/Tanks
Glib c:\ProModel\glib Gauge/tank fill color maroon
Output c:\ProModel\output Gauge/tank border color black
Gauge/tank empty color white
Gauge/tank - no border checked
Gauge/tank - show scale checked
Other
Autosave (in minutes) 10
Print layout - print options unchecked
dialog - bkgrnd color
586

ActiveX Objects Program Operations

• Start program
ProModel’s ActiveX Automation capability
allows you to externally create, view, and edit • Quit program
model elements such as locations, entities, and • Pause simulation model
variables. Using Visual Basic (or any other • Query status of model
ActiveX-enabled language), you can add capabil- (e.g., running, paused, etc.)
ities to ProModel including: • Enter Run-time Interface parameters from
external data source
• Customized user interface with table inputs
• Access any data field provided in output
• Custom-designed parameter screens
database
• Automatic model creation from external data
sources (e.g., Excel spreadsheets, data- Location Table
bases, or ASCII text files)
• Name
• Software execution from another application
• Capacity
You can also use ProModel’s ActiveX capability • Units
to access any of the following actions and tables • Stats
(any table not mentioned in the following list is • Incoming selection rule
not currently ActiveX enabled).
• Incoming rule, max attribute
More information on ActiveX Automation can be • Incoming rule, min attribute
found in the ActiveX User Guide, which is • Queuing for Output rule
located in the documentation folder within the • Queuing rule, max attribute
ProModel directory. • Queuing rule, min attribute
• Multi-unit selection rule
• Notes
• Operation rate (cost)
• Time units (cost)
Clock Downtime Subtable
• Frequency
• First time
• Priority
• Scheduled
• Logic
• Disable
Entry Downtime Subtable
• Frequency
• First time
• Logic
• Disable
 ProModel 587
User Guide

Usage Downtime Subtable • Operation rate (cost)

• Frequency • Time units (cost)
• First time • Cost per use
• Priority Clock Downtime Subtable
• Logic • Frequency
• Disable • First time
Setup Downtime Subtable • Priority
• Entity • Scheduled
• Prior entity • List
• Logic • Node
• Disable • Logic
• Disable
Entity Table Usage Downtime Subtable
• Name • Frequency
• Speed • First time
• Stats • Priority
• Notes • List
• Initial cost • Node
• Logic
Resource Table
• Disable
• Name
• Units Processing & Routing Tables
• Stats • Entity name
• Resource search rule • Preemption process flag
• Entity search rule • Location name
• Entity search, min attribute • Operation logic
• Entity search, max attribute • Routing block number
• Speed empty • Output entity name
• Speed full • Destination name
• Acceleration • Destination priority
• Deceleration • Begin new block flag
• Pickup time • New entity check box
• Drop-off time • Output quantity
• Return home flag • Output rule
• Notes • Output probability
• Network • Output user condition
• Home node • Move logic
• Shift node
• Break node
588

Path Networks Table • Shift files

• Color • Start time
• Visible • Priorities
• Name • Logic
• Type • Disable
• Basis (time or speed)
Scenarios
Path Segments Subtable
• Name
• From
• Enabled
• To
• Bi-directional Model Parameters
• Time
Parameter Subtable
Interfaces Subtable
• Value
• Node
• Location Attribute Table
Mappings Subtable • Attribute name
• From node • Type
• To node • Classification (entity or location)
• Destinations • Notes

Nodes Subtable
Variables Table
• Coordinates • Variable name
• Name • Type
• Capacity • Initial value
• Stats
Arrivals Table • Stats basis
• Entity name • Notes
• Location name
• Quantity of each arrival Arrays Table
• Qty each (cycle table name) • Array ID
• First time • Dimensions
• Number of occurrences • Type
• Frequency of arrivals • Import File
• Arrival logic • Export File
• Disable flag • Notes

Shift Assignments Macro Table

• Locations • Identification (name)
• Resources • Text
• Units • Resource grouping
 ProModel 589
User Guide

Subroutine Table • Warm-up start (month, day, year, hour,

• Subroutine name minute)
• Operation logic • Simulation begin (month, day, year, hour,
minute)
User Distributions • Simulation end (month, day, year, hour,
• Distribution name minute)
• Type • Output report method
• Cumulative • Output report interval length
• Percentage • Number of replications
• Value • Clock precision
• Clock units
External Files Table • Disable time series flag
• Filename • Disable animation flag
• File type • Disable costing flag
• Path • Pause at start flag
• Prompt • Display notes flag
• Notes
More on ActiveX
General Information Dialog
• Model title For detailed information regarding ActiveX objects
• Default time units and methods, contact:
• Default distance units ProModel Sales and Support Team
• Graphics library file name Phone (888) PRO-MODEL
• Initialization logic
Fax (801) 226-6046
• Termination logic
• Model notes

Simulation Options Dialog

• Output path
• Run length type
• Warm-up period flag
Time Only
• Warm-up hours (time only)
• Run hours
Weekly
• Warm-up start (day, hr, min)
• Simulation begin (day, hr, min)
• Simulation end (day, hr, min)
Calendar Date
590

Suggested readings
To expand your knowledge and understanding of
simulation, its practices, and its applications,
consider the following texts.
Harrell, Charles; Ghosh, Biman; Bowden, Royce.
2003. Simulation Using ProModel. 2nd Edi-
tion; McGraw-Hill, Inc.

Law, A.M. and David W. Kelton. 1991. Simula-

tion Modeling and Analysis. 2nd Edition,
Chapter 4; McGraw-Hill, Inc.

Lewis, P. and E. Orav. 1989. Simulation Method-

ology for Statisticians, Operations Analysts,
and Engineers. Volume I; Wadsworth &
Brooks.

Harrell, Charles R. and Kerim Tumay. 1995. Sim-

ulation Made Easy. Industrial Engineering
Press.

Banks, Jerry and John S. Carson, II. 1984. Dis-

crete Event System Simulation. Prentice-Hall
Inc.

Heizer, Jay and Barry Render. 1988. Production

and Operations Management. Allyn and
Bacon.

Carrie, Allan. 1988. Simulation of Manufacturing

Systems. John Wiley & Sons.

Industrial Engineering & Management Press.

1987. Simulation: Modeling Manufacturing
& Service Systems. Institute of Industrial
Engineers.

Harrell, Charles R., Robert E. Bateman, Thomas

J. Gogg, Jack R.A. Mott. 1993. System
Improvement Using Simulation. JMI Con-
sulting Group and PROMODEL Corpora-
tion.
 ProModel 591
User Guide

Glossary

Cost Statistics Help button is shown, you may select Help from
the main menu.
Statistics collected on a cost basis (e.g., total cost
and average, non-use cost). You have control of
how ProModel collects these statistics. You may Edit Tables
collect information through statements, base An edit table is a powerful editing window used
them on the system clock, or use a combination to add, delete and edit modeling and language
of both. elements such as entities or locations. It is simi-
lar to a spread sheet editor in that it provides
Counter maximum visibility of element lists while still
allowing each field of a particular element to be
A counter is a location or variable graphic used to directly edited.
display the contents of a location or the current
value of a variable during animation. A counter
consists of a frame, a specification of the digit File Name
color, and the font. If the number being dis- A file name is any name used to identify a file.
played requires more digits than the maximum File names may include a path (e.g.,
specified, the counter simply expands to the left. C:\REPORTS\DATA) as well as a terminating
ProModel displays real values showing only 2 period with up to three additional characters as an
decimal places. For example, a variable equal to extension (e.g., DATA.TXT). File names are case
4.8936 would display 4.89 on the screen. insensitive.

Dialog Box Font

A dialog box is a pop-up window used to enter A font is a collection of characters sharing the
information or select options. Movement from same attributes such as height, width, and type-
field to field in a dialog box is accomplished by face. A font determines the appearance of text.
clicking in the field with the left mouse button or Select fonts using the font dialog which shows
by using the Tab key. To accept input made to a how the font will appear.
dialog box press Enter or click on the OK button.
To cancel any changes made to the dialog press
Frame
Esc or click on the Cancel button. For help on the
dialog, press F1 or click on the Help button. If no A frame is a graphical border or background for
placing text or displaying values. Frames have a
592

type (raised, recessed, transparent), shape, color Main Menus

and size. Frames are optional and you may use
them only to enhance the appearance of the The main menus are listed along the main menu
graphic layout. If you do not desire a frame, bar at the top of the application window and pro-
select Transparent as the type. vide access to all of the dialogs and commands
necessary to build, run, and analyze simulation
models.
Gauge
A gauge is a graphic bar that extends and retracts Name Index
to represent the current contents of a location.
You define a gauge by the fill color, the empty During simulation run time, ProModel converts
color, and the gauge border color. You also spec- the name of each location, entity, and resource to
a list index number for efficient access and flexi-
ify the fill direction (up, down, left or right).
bility in assigning names to variables, attributes,
etc. The index number corresponds to the order in
Integer Number which the elements appear in the edit table list. If
An integer number is a whole number ranging five locations were defined, they will be identi-
from -2,147,483,648 to 2,147,483,647. Integer fied by the index numbers 1 through 5 at run
values may not include commas, so enter the time. A name index may be assigned to a variable
number 5,380 as 5380. or attribute by referencing the name itself (e.g.,
Attr1 = EntityA). You may also test for a name
index by referencing the name (e.g., if Var5 =
Library Graphic
Loc3).
A library graphic is a graphic defined and edited
using the Library Graphics Editor. Use library Note
graphics to represent locations, resources or enti-
ties, or as part of the layout background with no A note is any comment or other information
association to any model entity. typed by the user that is for information only and
disregarded by ProModel.
When used to represent a processing location,
library graphics may have entity spots defined for
them so entities that enter the location will appear Numeric Type
graphically on the entity spot. A numeric type specifies whether a numeric
expression is of type real or integer. If, for exam-
You may reference a Library graphic multiple
times and each reference may have a unique size, ple, a variable is of type “real,” then the variable
horizontal or vertical inversion, rotation, and can only represent some real number.
color.
Numeric Value
Main Entity A numeric value is any real or integer number
such as 3.68 or 52.
The original or input entity used in routing logic.
You may create new entities from the main entity
using the CREATE statement or through multiple
routing blocks.
 ProModel 593
User Guide

Parameter Preemption
Parameters are variables used in a subroutine Preemption is the act of bumping or replacing an
which are local to or have scope only within the activity currently using a location with an activity
subroutine. Arguments or numeric expressions of a higher preemptive priority. ProModel han-
passed to a subroutine are assigned to the param- dles preempted activities differently depending
eters for use inside the subroutine. on the location preempted.
For locations, ProModel puts the preempted
Park Search activity (any current entity or downtime) in a pre-
A park search defines the sequence where a emption list for that particular location until it can
resource looks for nodes at which to park after resume its activity at that specific location unit.
completing a task assuming no other tasks are
waiting. Real Number
A real number is a number ranging from 1.7 X
Paths 10 -308 to 1.7 X 10 +308. Real values may not
Paths define the course of travel for entities and include commas, so enter the number 5,380.5 as
resources between locations. You may define a 5380.5.
path for a specific entity and routing, or a net- Examples: -2.87563, 844.2, 65.0
work of paths shared by several resources and
entities. Define movement along a path in units
of time, or speed and distance.
Reference
A reference is a name entry in an edit field that
Path networks consist of nodes connected by path
references a defined model element. If you
segments. Any node may have multiple input
change the name of the model element, all refer-
and output segments.
ences to the element automatically change to
reflect the change in name.
Positioning Spot
An entity spot is simply a graphic position rela- Region
tive to a location or resource and displays any
A region is a rectangular area on the graphic lay-
entities occupying the location or resource.
out that represents a location. Defining a region
For any given location you may place one or is useful when you import a layout from a CAD
more entity spots on the graphics layout. Entities drawing and you want to designate a portion of
to enter a location appear on the first available the layout to represent a particular processing
entity spot in the order they are placed. If an location. A region should have one or more
entity enters a location and all the entity spots are entity spots associated with it in order to be
filled, the entity will appear on the last entity meaningful.
spot.
For resources, place the entity spot where it Resource
appears when a resource carries the entity. A resource is a person or item used to perform an
operation or activity. Common resources include
human operators, inspectors, forklifts, and other
594

vehicles. Use resources used to perform opera- 1. Click on the scroll arrows at either end of the
tions on entities at a location, transport entities scroll bar for incremental scrolling.
between locations, or perform activities on a 2. Click on either side of the scroll box for
location during a downtime. scrolling one window at a time.
3. Drag the scroll box with the mouse to scroll
Resource Point to a specific position.

A resource point is a screen position where a

resource will appear when it arrives to park or
Scroll Box
perform a task at a particular node. When a A scroll box is a small box in a scroll bar that
resource arrives at a node, it will appear on that shows the position of what is currently in the
node unless you define a resource point for that window or list box relative to the contents of the
resource at that node. Resource points provide a entire window.
way to have several resources positioned at the
same node without all appearing on top of each Shell
other.
The temporary entity (representing grouped enti-
ties) to which ProModel assigns all costs and sta-
Routing Priority tistics until you ungroup the entities. Once
A routing priority is the priority given to a rout- ungrouped, ProModel divides all costs among the
ing for accessing a destination when capacity entities.
becomes available. ProModel defines the routing
priority as part of the Destination field in the Status Lights
Routing Edit Table. A routing priority applies
where two or more entities wait at a location for a A status light is a circle that lights up with differ-
routing destination to become available. The ent colors depending on the status of the location.
routing priority breaks a tie when deciding which You can place a status light anywhere relative to a
entity has access to the destination location first location for showing the status or current state of
when it becomes available. (See Selecting the location. At run time, you can display a win-
Incoming Entities in the Location Rules Dialog.) dow showing what status each color represents.

Scroll Arrow String

You can use the scroll arrows on either end of a A string is a series of characters enclosed in dou-
scroll bar to move the contents of a window or ble quotes (e.g., “Station A”). You may use
list box. Clicking once on a scroll arrow moves strings to write text to a file or to display a mes-
the contents one line. Holding down a scroll sage on the screen.
arrow scrolls continuously.
System Menu
Scroll Bar The system menu appears as a dash mark at the
A scroll bar is a Windows control for scrolling upper left corner of most windows. The main
the contents of a window. Scroll bars operate in function of the system menu is to close the win-
three different ways: dow. To do this, by either double-click on the
 ProModel 595
User Guide

menu button or click on the button once and

select Close from the menu options that appear.
ALT + <space bar> also pulls up the system
menu.

Text
Text refers to words that you wish to display on
the graphic layout. Each specification of text has
an associated font, color, frame, and orientation
(up, down, left or right). You can rotate only
true-type fonts.

Time Statistics
Statistics collected on a time basis (e.g., time in
system, average minutes per entry, and average
contents). You cannot control how ProModel col-
lects these statistics since ProModel bases them
solely on the system clock.

Work Search
A work search defines the sequence in which a
resource looks for work at locations where work
may wait to be performed.
596

Bibliography

Carson, J. S. “Convincing Users of Model's Law, Averill M. “Designing and Analyzing Sim-
Validity is Challenging Aspect of Modeler's ulation Experiments,” Industrial Engineer-
Job,” Industrial Engineering, June 1986, p. ing, March 1991, pp. 20-23
77.
Neelamkavil, Francis Computer Simulation and
Conway, Richard, William L. Maxwell, and Modeling, John Wiley & Sons, 1987.
Steven L. Worona, User's guide to XCELL
Factory Modeling System, The Scientific Pritsker, Alan B. and Claude Dennis Pegden,
Press, 1986, pp 65-66. Introduction to Simulation and SLAM, John
Wiley & Sons, 1979.
Gordon, Geoffrey, System Simulation, 2nd ed.,
Prentice-Hall, 1978. Schlesinger, S. “Terminology for Model Credibil-
ity,” Simulation, 32(3), 1979, pp.103-104.
Harrell, Charles; Ghosh, Biman; Bowden, Royce.
2003. Simulation Using ProModel. 2nd Edi- Shannon, Robert E., Systems Simulation: The
tion; McGraw-Hill, Inc. Art and Science, Prentice-Hall, 1975.

Harrell, Charles R. and Kerim Tumay, Simulation Thesen, Arne and Laurel E. Travis, Simulation
Made Easy, Industrial Engineering Press, For Decision Making, West Publishing Com-
1995. pany, 1992.

Hoover, Stewart V. and Ronald F. Perry, Simula- Tumay, Kerim, Business Process Reengineering
tion: A Problem Solving Approach, Addi- Using Simulation, Autofact Workshop,
son-Wesley, Reading Massachusetts, 1990.

Knepell, Peter L. and Deborah C. Arangno, Sim- 1993.

ulation Validation, IEEE Computer Society
Press, 1993.

Law, Averill M. and David W. Kelton, Simulation

Modeling and Analysis, McGraw-Hill, 1991.
 ProModel 597
User Guide

Index

Symbols time and condition dependent 31

Add
joint 119
- 398, 399, 403 mode 94
# 451 resource points 141
$ 398, 402, 403 resources & variability 48, 52
( ) 398, 403 routing mode 154
* 152, 398, 399, 403 view 78
** 398, 399, 403 Addition 398, 399, 403
+ 398, 399, 403 Additional operations 48, 55
/ 398, 399, 403 AGV 117
/*...*/ 451 AGVS
// 451 see automated, guided vehicle systems
< 398, 400, 403 Alignment
<= 398, 400, 403 graphics 214
<> 398, 400, 403 text 96
= 398, 400, 403 ALL 146, 150, 153, 293, 430, 453, 467, 473, 503, 546
> 398, 400, 403 entity type 147
>= 398, 400, 403 ALTERNATE 406, 407, 412, 417, 422
@ 341 Alternative systems 42
@ or Mod 398, 399, 403 Analysis
capability 27
capacity 27
A constraint 27
decision/response 27
Acceleration rate 138, 265 graphical 12
ACCUM 98, 109, 280, 283, 429, 578 output 45
Accumulate performance 26
see accum sensitivity 27
Accumulating AND 398, 401, 403, 486
conveyor 99 ANIMATE 359, 432, 578
Accumulating conveyor 98 Animation
Accumulating conveyors 270 charts 46
Accuracy, degree of 29 conveyor 99
ACTIVATE 181, 238, 239, 431, 566, 578 disable 353
Active operation zone 268 off 58
ActiveX objects 586 on/off during run time 346
Activity options 353
grouping 35 panning during run time 359
screen 57
598

user pause 353 first time 157

views 353 frequency 157
zoom 353 independent 158
Append location field 156
appending a record to a table 71 logic 157
record to a table 70 new 55
Arc occurrences 157
draw 317 quantity each field 156
Arrange icons 84 rates 89
Arrays 89, 227, 399, 506, 577 AS 532
accessing 227 AS/RS
assigning cell values 227 see automated storage/retrieval systems
definition 227 ASCII 446
dimensions 228 characters 397, 446
disable 228 files 527
displaying information during run time 86, 354 text editor 584
edit table 228 Assemblies
examples 227 making 283
export file 228 Assembly lines 7
import file 228 Assignment 435, 578
initializing 229 Attributes 48, 89, 217
notes 232 accessing 217
persist 228 cloning 218
referencing 227 example 219
statistics 232 combine statement with attributes 222
type (real or integer) 228 define 55, 217
usage 232 edit table 219
Arrivals 47, 156 entity attributes 217
accessing 156 example 219
cycles 244 group statement with attributes 220
accessing 244 join statement with attributes 220
assigning arrivals 245 load statement with attributes 221
cumulative 244, 246 location 577
cycle tables 246 location attributes 218
defining 244 memory allocation
edit table 244 for attributes 218
examples 244 see entity attributes
percent 244 types 217
quantity 244, 246 ungroup statement with attributes 220
table 244 unload statement with attributes 221
define 50, 157 Automated guided vehicle systems 273
graphically 157 Automated guided vehicles
manually 158 modeling 273
definition 156 on-board vehicle sensing 273
destroyed 157 simulation benefits 274
disable 157 zone blocking 273
edit table 156 Automated storage/retrieval systems 275
editor 156 modeling 275
entity field 156 simulation benefits 275
external arrival file 157 vertical bridge crane 275
files 256 AutoSave
example 256 directory 326
 ProModel 599
User Guide

files 326 object 73

time between saves 325, 326 wmf 74
AUTOSAVE.MOD file 345 removing an object 73
Axis shift 427 rotate 214
selecting all graphics 74
sizing an imported background graphic 213
B tools
button bar 211
ungroup 214
Background color 88
unlock 214
edit table 83
wmf 277
layout window 81
BACKUP 406, 407, 417, 422
Background graphics 74, 210, 277
Backup file 64
accessing 210
Basic 354
alignment 214
Basic model elements 48
behind grid 214
Batch means technique 41
mode 210
Batching 278
bmp 277
Batching, interval 41
cad 277
BEGIN 234, 436, 465, 578
copy
Behind grid 277
object 73
Behind grid mode 210
to clipboard 74
Beta distribution 427
create 210
Binomial distribution 427
deleting an object 74
Block
edit 73, 87, 210
number
menu 212
* 152
editor 211
routing block 149
modes 210
Blocked time 269
exporting a graphic 74, 213
BMP
fill
importing a background graphic 213
color 214
Boolean
patterns 214
expressions 399, 400
flip
operators 399
horizontal 214
Border
vertical 214
change line or border style 309
front of grid 214
tank 180
mode 210
Bottleneck 274
graphics menu 214
Bottlenecks, identifying 45
group 214
BREAK 437, 539, 578
importing 49, 74, 213
Break logic-specific system functions & statements 578
layout window 211
dtleft() 578
library graphics window 211
priority 578
line
skip 578
color 214
BREAKBLK 438, 539, 578
styles 214
Breaks 137
lock 214
colors
move
customize 162
behind grid 215
logic 166
imported background graphic 213
see shift & break logic
in front of grid 215
see shift definition & shift assignment
paste
Bridge
bmp 74
and hoist trajectory 267
600

following 265 Clearing text in a notes window 72

leading 265 Clock
motion after queue-up 266 clock-based downtime 132
multiple bridges 266 display during run time 359
separation 261 selection 57
separation distance 263 Clock precision 272
speed 261 CLOCK() 403, 447, 504, 577
Budget for simulation project 30 CLOSE 448, 578
Build Collisions 274
expression button Colon notation 402
logic builder 287 Color
menu 89 background 80, 81, 88
description 61 create custom 82
models 9, 35, 47 custom 82
Bump-away 268 edit table 83
BY TURN 151 fill 310, 323
grid lines 81
line 310, 323
C routing path 80, 82, 88
shift & break
customize 162
CALDAY() 439, 440, 577
text 96
CALDOM() 577
COMBINE 98, 109, 177, 278, 283, 449, 483, 499, 549, 558,
CALHOUR() 441, 577
561, 578
CALMIN() 442, 443, 444, 577
Commands 76, 83
CALMONTH() 577
Comments 451, 578
CALYEAR() 577
Common mode 74
CAP() 445, 503, 577
Communication effectiveness 27
Capability analysis 27
Comparison
Capacity
study 27
analysis 27
with similar operations 33
location 91, 100
Comparison operators
maximum location capacity 91
and, or, not 398
Capacity, load rate 270
Compiling within a logic window 73
Cascade 84
Concatenation operators 398, 402, 403
Category Chart 381
Conducting experiments 37
Cause-and-effect relationships
Confidence intervals (CI) 38
identify 30
Confirm record deletion 325
CHAR() 397, 402, 446, 575
Constraints
Character strings 393, 397, 402
analysis 27
Characters
identify 26, 27
ascii 397, 446
CONT, see CONTINUE
Charts 379
CONTENTS() 452, 577
Chord
Context 85
circular 319
CONTINUE 151, 406, 408, 410
draw 319
dynamic priority changing 408
Circle
continuous modeling 180
draw 318
Continuous trace 58
Claim
Control statements 426
attempt rejection 263
Convert
priority 262
data to useful form 34
zone 263
Convert between numeric types 397
 ProModel 601
User Guide

Conveyors 94, 97, 98, 269 per 176

accumulating 98, 99 regular rate 176
animation 99 disable costing 179
capacity 98 enable costing 179
conveyor networks 271 entities 176, 179
conveyors in promodel 272 initial cost 176
creating bends graphically 99 join/load 177
define locations 175, 178
color 97 operation rate 175
graphically 99 per 176
definition 98 output 178
display graphics 99 preemption/downtime 177
draw to scale 272 resources 176, 178
entity orientation 99 cost per use 176
examples 272, 273 per 176
intermittent 271 regular rate 176
length 98, 99 special cost handling 178
load delivery time 270 statistics 178, 591
load overlap 272 Cost-related functions & statements 578
load rate capacity 270 getcost() 478
load spacing 272 getresrate() 480
modeling conveyor systems 271 incentcost 489
networks 271 incloccost 490
non--accumulating 98 increscost 491
operational limitations 98 Counter 94, 95
options 99 see glossary 591
queuing 270 Cranes 261
run-time visibility 97 bridge and hoist speeds 261
set bridge separation 261
style 97 crane envelope 261
width 97 crane move priorities 261
simulation benefits 270 claim priority 262
single section 271 effective claim priority 262
speed 100, 270 task move priority 261
types 270 crane operations 262
accumulating 270 envelope 261
non-accumulating 270 horizontal speed 275
Copy 322 idle 266, 267, 268
graphic editor 308 immovable 267
information modeling multiple cranes 261
between records 71 move priority 261
from another record 71 multi-crane envelopes
record in a table 71 claim attempt rejection 263
text in a notes window 72 extended movement zone 263
Cost 175 queue-up situations 265
building a model with costing 176 zone claims 263
combine/group 177 node searches 268
cost dialog box 175 operation rules 267
cost per use 176 operations notes 268
initial cost 176 other rules 267
object type 175 park searches 268
operation rate 175 queue-up situations
602

bridge motion after queue-up 266 requirements

no queue-up 265 determine 31
reclaim trigger events 267 sources 33
resource request write 254
priorities 261 DAY 401, 403, 447, 462
response 266 Deadlocks 274
resource statistics 269 DEBUG 348, 350, 351, 455, 553, 578
blocked time 269 example 350
gross move time 269 Debug 346
in use 269 check condition 349
special case, blocked time 269 debug button 349
travel to use 269 debug dialog 349
searches 268 advanced 350
vertical bridge 275 context 349
vertical speed 275 end simulation 349
work searches 268 error display box 349
zone claims into subroutine 350
examples 263 logic display box 349
speed and mobility 265 next statement 349
CREATE 97, 98, 178, 218, 449, 453, 483, 489, 499, 549, 558, next thread 350
561, 578 options 350
Create run 349
model package 68 disable debugger 348
run-time models 11 examples 347, 350
Creating Charts 379 global change 348
Creating Reports 372 example 351
CSV files 257 logic 347
Cumulative distribution function 252 disable 350
Custom enable 350
colors 82 exclusive 350
reporting 342 new 350
zoom 79 next 350
Customize 299, 327 options dialog 348
Customizing graphics process
background graphics 277 disable 350
Cut 322 exclusive 350
cutting text in a notes window 72 new 350
Cycle period 44 next 350
process thread 347
statement 347
D user condition 348
example 351
DEC 456, 578
Data
Deceleration
approving 35
infinite 265
converting to a useful form 34
rate 265
documenting 35
Deceleration rate 138
gathering 32
Decision
protection
response analysis 27
model data 68
rules
model packaging 68
for locations 109
read 254
Default graphics library 325
 ProModel 603
User Guide

Defaults geometric 427

default values table 584 inverse gaussian 427
program 584 lognormal 427
Define normal 427
arrivals 50 pearson5 427
attributes 55 pearson6 427
distribution 55 poisson 427
entities 49, 113 stream, optional 427
location downtimes 55 triangular 427
locations 49 uniform 427
multiple entity graphics 114 user-defined 427
objectives 26 weibull 427
path networks 52 Distributions
processing 50 continuous 253
resources 52 define 55
system 30 discrete
Degree of accuracy 28, 29 cumulative distribution function 252
Delete probability mass function 252
deleting a record from a table 70 empirical 34
joint 119 fitting 34
location 93 frequency
graphic 93 example 34
process 154 user-defined 34
routing record 154 Division 398, 399, 403
DEPENDENT 406, 410 DO...UNTIL 437, 458, 492, 578
Deposit time 138 DO...WHILE 436, 437, 459, 465, 492, 578
Design of experiments (DOE) 42 Documentation symbols
Destination, choosing 280 #, //, /*...*/ 451
Detail of a simulation project 28 DOWN 460
Developing a budget and schedule 26 DOWNQTY() 461, 577
Dialog box 10 Downtimes 89, 91, 274, 281
see glossary 591 clock 132
Dimensions define location downtimes 55
entity graphic 113 define resource downtimes 132
graphic 310 downtime-specific system functions 425, 460, 462, 577
Directories 325 location 101
Disable costing 179 called 105
DISPLAY 171, 397, 403, 457, 578 clock 102
Display statistics on screen entry 103
see statistics setup 104
Distance 120 special notes 109
per grid unit 81 usage 103
change 312 overlapping shift downtimes 169
units 171 preemption 177
Distribution functions 399, 427 resource 131
axis shift, optional 427 clock 132
beta 427 usage 132, 133
binomial 427 Draw
erlang 427 arc 317
exponential 427 chord 319
gamma 427 circle 318
general components 427 circular chord 319
604

ellipse 318 implicit 453, 531, 549

lines 316 activity
polygon 319 general statistics report 373
rectangle 318 all as type 147
square 318 attributes 399
triangle 317 assigning values 277
DTDELAY() 167, 298, 462, 577 entity characteristics 277
DTLEFT() 167, 297, 463, 578 operation time 276
DTLENGTH() 166 processing time 276
Dynamic Plots 354, 358 user condition routing 276
Dynamic priority changing 408 using 276
Dynamic resources 129, 268 batching 278
accum 280
combine 278
E group/ungroup 278
load/unload 279
characteristics 277
Edit
cost 176, 179
arrivals 156
general statistics report 373
background graphics 73, 87
defining 49, 113
editing preferences
graphically 113
confirm record deletion 325
multiple entity graphics 114
long build menu 325
entities editor 112
recalculating adjusted paths 325
entity-related move logic statements
existing graphic 95
move for 512
graphics 74
move on 513
logic windows 72
move with 514
menu 70
entity-related operation statements 426
background graphics 212
accum 429
description 61
combine 449
notes windows 72
create 453
preferences 83
graphic 482
process 53
group 483
table 9, 70, 83
join 494
color 83
load 499
edit table font 83
match 508
see glossary 591
move 510
table font 83
rename 531
tank or gauge 180
route 542
Edit Tables 10
split as 549
Ellipse
ungroup 558
draw 318
unload 561
ELSE 290
wait 567
Empirical distribution 34
wait...until 568
EMPTY 411
entity-specific attributes 577
Enable costing 179
entity-specific system functions 425
END 436, 437, 438, 465, 578
entity() 467
Engineers 33
groupqty() 485
ENT() 112, 396, 397, 402, 457, 466, 517, 531, 544, 577
resqty() 538
Entity 47, 112
graphics 320
accessing 112
dimensions 113
actions
icon 113
 ProModel 605
User Guide

location file 255 types 29

name 113 types of 29
new 55 Exponential distribution 427
new entity check box 152 Exponentiation 398, 399, 403
notes 113 Exporting
orientation background graphics 213
on conveyor 99 graphic editor 307
preemptive 115 Expression search 299, 300
example 115 definition 300
processing find 300, 301
define 144 important notes 302
select performing 300
by turn 110 replace 300, 301
fewest entries 111 search next 300
first available 110 Expressions
highest attribute value 110 boolean 399, 400
last selected location 110 expression and statement groups 577
least available capacity 110 numeric 399
longest empty 111 string 397, 399, 402
lowest attribute value 110 char() 402
most available capacity 111 ent() 402
oldest by priority 110 format() 402
random 110, 111 loc() 402
show numeric 402
current 155 res() 402
speed 113 time 399, 401
spot 94 colon notation 402
states types of 398
by percentage 374 Extended movement zone 263
stats 113 External files 254
types 89 accessing 254
unbatching 278 define 254
ENTITY() 467, 577 editor 254
ENTRIES() 468, 577 open files 257
Envelope types 254
crane 261 arrivals file 256
multi-bridge 268 dll file 257
multi-crane 263, 265 entity-location file 255
Equal to 398, 400 excel file 257
Equalities 398 general read file 254
Equipment manufacturers 33 general write file 255
Erlang distribution 427 other 257
Errors, run-time shift file 256
already routed 152 usage 254
no routing defined 152 External spreadsheet file 578
Exclude graphic library 68 External subroutine calls
Exclusive work search 268 xsub() 573
EXIT 373
EXP() 469
Expansion, incremental 36
Experiments
conducting 37
606

F background graphics 214

change 310
Find and replace, local 303
Face validity 37 Find process mode 155
Facility 33 Finite move priority 267
layouts 33 FIRST AVAILABLE 412
walk-throughs 33 First in, first out
Factorial design 42, 43 Flexible manufacturing systems 7
fractional-factorial 43 Flip object 321
full-factorial 43 horizontal 308
two-level 43 vertical 308
Factors 42 Flow
impact 30 charts 33
Failed arrivals rate of flow 182
general statistics report 374 time step
FIFO 558 tanks 182
see locations, rules Focus of simulation 31
Figures Following bridge 265
add to gauge or tank 181 Font 96
File edit table 83
exclude graphic library file 68 see glossary 591
extensions 257 FOR 510, 514
external 254 FORLOCATION() 166, 167, 297, 470, 577
define 254 Form of results 28, 29
editor 254 FORMAT() 402, 471, 575
open 257 FORRESOURCE() 166, 167, 297, 472, 577
other 257 Fractional factorial design 43
types 254 Frame
graphic library 173 see glossary 591
management 62, 63 text 96
menu 62 FREE 267, 473, 476, 496, 578
description 61 FREECAP() 474, 577
during run time 345 FREEUNITS() 475, 577
during run-time 345 Frequency distributions
name example 34
see glossary 591 Front of grid 277
open external 257 Front of grid mode 210
types FULL 421
arrivals file 256 Full-factorial design 43
entity-location 255 Functions 425
general read 254 cost-related 478, 480
general write 255 general 425
shift file 256 math 425
Files system 577
ascii 527 type conversion 425
external spreadsheet 578 name 396
Fill nested 289
color 310 new 357
background graphics 214 system 425
define 323 downtime-specific 425
tank 180 entity-specific 425
pattern general 425
 ProModel 607
User Guide

resource-specific 425 graphic file library 171, 173

shift & break 425 selection 173
initialization logic 171, 172
logic execution time 172
G model notes 171
termination logic 172
time units 171
Gamma distribution 427
title 171
Gauge 94, 95
usage 171, 210
add labels and figures 181
General operation statements 578
change to tank 181
close 448
edit 180
dec 456
see glossary 592
graphic 482
GBM files 257
inc 488
General action statements 426
prompt 524
activate 431
setrate 546
animate 432
stop 552
debug 455
write 571
display 457
writeline 572
log 504
xwrite 575
maparr 506
General read file 254
order 517
General statistics report
pause 519
entity activity 373
read 527
entity costing 373
report 532
entity states by percentage 374
reset 534
location setup 375
reset stats 535
location states by percentage
return 539
multiple capacity 375
send 544
single capacity 375
sound 548
locations costing 374
trace 556
logs 376
view 566
node entries 374
warmup 569
resource states by percentage 376
General control statements
resources 377
begin 436
costing 376
break 437
grouped 377
breakblk 438
General system functions 425, 577
do...until 458
calday() 439, 440, 577
do...while 459
caldom() 577
end 465
calhour() 441, 577
goto 481
calmin() 442, 443, 444, 577
if...then...else 486
calmonth() 577
while...do 570
calyear() 577
General expressions 577
cap() 445, 577
General functions 425
clock() 447, 577
math 425
contents() 452, 577
type conversion 425
downqty() 461, 577
General information 171
entries() 468, 577
accessing 171
freecap() 474, 577
dialog 48
freeunits() 475, 577
dialog box 171
ownedresource() 577
distance units 171
percentop() 520
608

percentutil() 521 show 311, 312

threadnum() 553 size & scale 311
timesused() 555, 577 snap to grid 311, 312
units() 560, 577 grouping graphics 308, 309
variable() 565, 577 importing graphics 307
General write file 255 library edit buttons 313
Geometric distribution 427 line
GET 115, 134, 153, 261, 269, 295, 296, 476, 578 color 308
GETCOST() 478, 578 button 323
GETRESRATE() 480, 578 styles 308, 309
GIF tool 316
importing a background graphic 213 manipulating graphics 313
GLB files 257 move
GOTO 481, 578 to back 308
GRAPHIC 114, 128, 130, 131, 140, 482, 578 to front 308
Graphic naming a graphic 314
new 314 opening a graphics library 305
Graphic editor 299, 304, 305 options menu 305, 311
accessing 304 order of graphics in the library
arc tool 317 change 314
background color 311, 312 overview 304
changing a graphic’s size 313 paste
changing the order of the graphics in the library 314 button 322
chord tool 319 graphics 307
circle tool 318 pie tool 319
clear button 313 polygon tool 319
closing a graphics library 306 positioning spot 320
combining two graphics 314 print
copy graphic 305, 306
button 322 graphics library 305, 306
graphic 308 rectangle tool 318
cut button 322 rotate
delete button 313 button 321
dimensions 309, 310 graphic 308
edit save
button 313 button 313
library graphic 323 graphic 305
menu 304, 306 graphics library 306
ellipse tool 318 selector 315
exporting a graphic 307 size
file menu 304, 305 change 313
fill square tool 318
color 308 status light 321
color button 323 step back & front buttons 322
patterns 308, 310 text tool 315
flip triangle tool 317
buttons 321 ungrouping graphics 308, 309
horizontal 308 usage 304
vertical 308 window menu 305, 312
graphic tools button bar 315 zoom 311, 312
graphics menu 304, 308 Graphic library
grid create new 314
 ProModel 609
User Guide

Graphical analysis 12 view button 92

Graphics move 75
background 277 multiple
alignment 214 assign to resource 130
behind grid 214 resource 320
delete an object 74 multiple 130
edit 87 Graphs
export 74, 213 utilization 13
fill Greater than 398, 400
color 214 or equal to 398, 400
patterns 214 Grid
flip lines
horizontal 214 change color 81
vertical 214 change resolution 81
front of grid 214 scale 81
group 214 settings 88
import 49, 74, 213 grid scale 81
line show 77, 85, 312
color 214 size 80
styles 214 snap to 77
lock 214 unit
move default time 81
behind grid 215 distance per unit 81
imported graphic 213 change 312
in front of grid 215 GROUP 98, 109, 177, 278, 283, 449, 453, 483, 499, 549, 558,
paste 561, 578
bmp 74 Group
wmf 74 activity 35
removing an object 73 graphics 214, 309
right-click editing 74 objects 309
rotate 214 resource 233
size an imported graphic 213 GROUPQTY() 485, 577
ungroup 214
unlock 214
customizing 277 H
behind grid 277
front of grid 277
Hardware requirements 15
importing 277
Help
define multiple entity 114
index 85
dimensions 310
menu 85
editing & moving 74
description 62
entity 320
on-line 11
graphic dimensions 113
accessing 73
library 95
Hidden networks
file 171, 173
show 87
exclude 68
Hide
selection 173
conveyors and queues 97
graphic 96
networks 77, 85
location 94, 320
Histogram 384
graphics window 92
Hoist
edit button 92
and bridge trajectory 267
erase button 92
610

lower 268 incentcost 176

speed 261 order 176
Home route 176
return if idle 137 state 38
Horizontal speed 275 warm-up period 41
Hours 401, 402, 447, 462 Initial value 281
HR 401, 447, 462 Initialization logic 171, 172
Hypothesis testing 42 execution time 172
Input variables 31
Insert
I record in a table 70, 71
Install model package 68, 69
Installation
Icon
see setup and installation 15
add to location 94
INT 223, 225, 492, 578
locations 91
Integer number
Idle
see glossary 592
return home if 137
Integers 396
Idle cranes 267, 268
Interact menu 358
moving 266
Interactive subroutines 241, 358
IF EMPTY 151
Interfaces
IF...THEN 234, 289, 291, 350, 436, 437, 452, 465, 467, 486,
edit table 121
503, 542, 553, 578
location-node 122
IF...THEN...ELSE 50, 289, 481, 486, 578
Intermittent conveyor 271
Immovable cranes 267
Interval batching 41
Impact factors 30
Inverse Gaussian distribution 427
Import
background graphics 49, 213
graphic editor 307
tank submodel 180 J
Importing
background graphics 277 JIT systems 7
INC 488, 578 Job shops 7
INCENTCOST 489, 578 JOIN 55, 109, 112, 220, 282, 283, 375, 413, 494, 529, 578
INCLOCCOST 490, 578 Join 177
Incremental expansion 36 Joint
INCRESCOST 491, 578 add 119
Independent arrivals 158 delete 119
Industrial vehicles 274 JOINTLY GET 115, 134, 261, 269, 296, 496, 578
deployment strategies 274
modeling 274
multiple load transporters 274 K
simulation benefits 275
Inequalities 398
KANBAN systems 7
INF 91
KEEP 267
INFINITE 91, 157
Keyboard 3
Infinite deceleration 265
Keywords 393, 395
Information menu 58
during run time 353
Initial
cost
create 176
 ProModel 611
User Guide

L draw 316
styles 309
background graphics 214
Labels 76 LN() 498
add to gauge or tank 181 LOAD 109, 177, 221, 226, 279, 283, 375, 396, 414, 449, 453,
text 94 483, 499, 549, 558, 561, 578
Language elements Load
character strings 393, 397 delivery time 270
keywords 393, 395 jumping 272
names 393, 394 overlap 272
conventions 394 rate capacity 270
numbers 393, 396 spacing 272
converting between numeric types 397 LOC() 90, 151, 396, 397, 402, 457, 461, 474, 501, 517, 544,
integers 396 560, 577
name-index 396 Local find and replace 303
real numbers 396 Local variable 578
operators 393, 398 declaration statements
comparison 398 int 492
mathematical 398 real 529
precedence 398 Local variables 225
relational 398 Location
types of 393 attributes 577
Last in, first out location-specific system functions 577
LAST() 497, 577 location() 503
Layout LOCATION() 296, 298, 445, 503, 577
printing a layout 67 Locations 47, 90
settings 80, 88 accessing 90
background color 80, 81 add mode 94
grid settings 80, 81 adding symbol to existing location 94
routing path color 80, 82 attributes 218
window 49 capacity 91, 100
Leading bridge 265 maximum 91
Length conveyor/queue 94
conveyor 99 cost 175, 178
Less than 398, 400 costing
or equal to 398, 400 general statistics report 374
Level counter 94, 95
of detail 28 create 90
tank 181 define 49, 90
Library multiple locations 92
new 314 multi-unit locations 101
Library graphic 95 new location graphically 92
see glossary 592 delete
License key location 93
transfering 23 location graphic 93
LIFO 558 destination
see locations, rules processing 151
Line display
change line or border style 309 information during run time 86, 354
color 310 location name 95
background graphics 214 downtimes 91, 101
define 323 called 105
612

clock 102 light 94

define 55 tank 94, 95
definition 101 text 94, 96
entry 103 units 91, 100
setup 104 view 93
special notes 109 Lock
specifying 102 graphics 214
usage 103 LocState() 502
edit 90 LOG 376, 447, 504, 529, 578
edit table 49, 91 Logarithm 498
editing an existing graphic 95 Logic 3
editor 90 arrivals 160
entity spot 94 break 166
gauge 94, 95 builder 10
graphics 94, 320 accessing 73, 184, 285
window 92 build expression button 287
edit button 92 building statements or expressions 286
erase button 92 cancel button 287
view button 92 clear button 287
icon 91 components 286
identifying location name during run-time 360 editing statement parameters 288
information window 12 expressions, creating 290
label 94 keypad button 287
library graphic 95, 96 logic
loc() 90 buttons 287
move 75 elements 287
graphic 93 nested functions & statements 289
multiple graphics 93 parameter
multi-capacity vs. multi-unit 100 buttons 286
multiple graphics for a location 95 entry field 286
naming 91 paste
new 55 button 287
mode 92 logic/model elements only 290
node interface 122 return button 287
notes field 92 select
preemption 105, 107 logic elements 288
priorities 105, 106 statements 287, 288
queue 94 using 285
region 94 off-shift 166
rules 91, 109 operation 291
example 111 pre-break logic 166
queuing for output 110 preemption process 292
selecting a unit 110 example 293
selecting incoming entity 110 functions 293
setup statistics report 375 possible effects of delayed preemption 293
states by percentage pre-off-shift 166
multiple capacity process 53, 56, 89
general statistics report 375 routing 53, 56
single capacity routing move 294
general statistics report 375 get, jointly get, use 296
statistics 91 move-related statements 295
status statement processing 296
 ProModel 613
User Guide

shift & break 166, 297 table 233

break logic 297 example 233
functions & statements 297 macros vs. subroutines 233
off-shift logic 297 rti 233, 234
pre-break logic 297 see also run-time interface
pre-off shift logic 297 subroutines vs. macros 242
sequence of events 166, 297 text 233
subroutines 241 usage with begin/end 234
windows valid usage 233, 234
edit 72 Main entity 592
Logic elements errors
distribution functions 427 already routed 152
axis shift, optional 427 no routing defined 152
general components 427 Main menus
stream, optional 427 see glossary 592
functions 425 Maintenance reports 33
downtime-specific 425 Maintenance, scheduled 274
entity-specific 425 Managers 33
general 425 Manual material handling systems 274
resource-specific 425 modeling labor 274
shift & break 425 simulation benefits 274
system 425 MAPARR 506, 578
general functions 425 Mapping
math 425 create 123
type conversion 425 edit table 122
priorities 428 example 123
resource request logic 268 Market forecasts 33
statement blocks 426 MATCH 109, 375, 494, 508, 578
statements 426 Math functions 425
control 426 exp() 469
entity-related operation 426 ln() 498
general action 426 rand() 526
resource-related 426 round() 541
Lognormal distribution 427 sqrt() 551
Logs Mathematical operators 398, 399
general statistics report 376 Matrix, resource preemption 135
Long build menu 325 Maximum run length 339
view 325 Maximum speed 265
LONGEST UNOCCUPIED, (LU) 415 Memory
Lower the hoist 268 allocation
LU, see LONGEST UNOCCUPIED for attributes 218
Menu
bar 61
M Merge
models 10, 63, 64
submodel 64
Macros 89, 233, 399
MIN 401, 447, 462
accessing 233
Minutes 401, 402, 462
and subroutines 578
MMHS
create 233
see manual material handling systems
definition 233
MOD files 257
edit 233
Model
614

build 9, 35, 47 statements

create new 63 processing 296
data logic statements 578
protect 68 free 473
elements 47 get 476
basic 48 jointly get 496
example of building a model 47 move for 512
execution 337 move on 513
merge 63, 64 move with 514
new 63 use 563
notes 171 moving a record in a table 70, 71
open 63 multiple location graphics 93
package object
create 68 behind 322
data protection 68 in front 322
install 68, 69 path networks 75, 119
parameters 337, 342 resource 76
define 343 points 142
partitioning 36 routing paths 75
phased modeling approach 48 to park 269
results, reporting 45 MOVE FOR 153, 294, 295, 512, 578
run 11 MOVE ON 153, 294, 295, 512, 513, 578
run-time 11 MOVE WITH 153, 261, 267, 294, 295, 476, 512, 513, 514,
save 63 578
save as 63, 64 Moving Graphics, common mode 74
text Multi-bridge
print 66 crane systems 261, 266
view 66 envelopes 268
validation 37 Multi-crane envelopes 263, 265
verification 36 Multiple capacity location 100
Modeling Multiple load transporters
services 5 see industrial vehicles
Modeling conveyors 272 Multiple locations 92
conveyor systems 271 Multiple single-unit resources 131
Modeling priorities Multiple streams 44
see priorities Multiplication 398, 399, 403
Modulus 398, 399, 403 Multi-unit
MOST 416 locations 100
Motion, bridge 266 resources 131
MOVE 97, 98, 294, 296, 510, 578
Move
along path network 138 N
finite move priority 267
graphics 74
Name
special considerations 75
index
gross move time 269
see glossary 592
idle cranes 266
location 91
location 75
Name-index numbers 396, 399
location graphic 93
conversion functions
logic 151, 153, 294
loc() 501
get, jointly get, use 296
res() 533
move-related statements 295
 ProModel 615
User Guide

Names 281, 393, 394 running 40

conventions 394 Normal distribution 427
functions NOT 398, 401, 403
ent() 396 Not equal to 398, 400
loc() 396 Notation
res() 396 colon 402
Nested functions & statements 289 Notes
Network field 92
non-passing 117 see glossary 592
passing 117 windows
path 117 editing 72
resource path network 137 Numbers 393, 396, 399
show hidden 87 converting between numeric types 397
show networks 77, 85 integers 396
version name-index 396
installation procedure 17 numeric type
New see glossary 592
arrival 55 random
entity 55 streams 258
entity check box 152 real numbers 396
block number Numeric expressions 399
* 152 Numeric Type, glossary 592
location 55 Numeric types, converting between 397
mode 92
model 63
create 63 O
process
create 154
Objectives, defining 26
New & modified features
Observation-based statistics 224
activex objects 586
Off-shift
New & modified statements and functions 357
locations, preempting 168
New graphic
logic 166
create 314
node 137
New graphics library
Off-shift & break logic specific system functions & statements
create 314
578
NEXT() 516, 577
On-board vehicle sensing 273
No queue-up 265
One-dimensional array 227
Node
On-line tracking systems 33
add resource points to 141
Open
break 137
model 63
home 137
Operation
logic 128
crane 262, 267, 268
editor 140
statements 578
example 140
time
off shift 137
using entity attributes 276
Node logic-specific system functions 577
zone 268
Nodes 268
Operation logic 53
serviceable 261
processing 147
Non-accumulating conveyor 98
Operator precedence 398, 403
Non-accumulating conveyors 270
addition, + 403
Non-exclusive work search 268
and 403
Non-terminating simulation 38, 39
616

concatenation, $ 403 Parentheses 403

division, / 403 Park and work search 268
equalities 403 Park search 128, 138
examples 403 edit table 139
exponentiation, ** 403 see glossary 593
inequalities 403 Park, travel to 269
modulus, @ or mod 403 Partitioning, model 36
multiplication, * 403 Paste 322
not 403 record in a table 71
or 403 text in a notes window 72
parentheses, ( ) 403 Path
subtraction, - 403 networks, see path networks
Operators 393, 398 routing
comparison 398 move 75
mathematical 398 show 77, 86, 87
relational 398 types 82
Optimization see glossary 593
simrunner 360 segment
study 27 edit table 52
Options 299, 325 Path networks 48, 75, 89, 117
menu accessing 117
debug option 347 automatic time and distance calculation 121
during run time 346 default time and distance values 121
simulation 57, 337 define 52
OR 398, 401, 403, 486 color of path network 118
ORDER 218, 489, 517, 578 graphically 118
Output editor 117
analyzing 45 example 119
charts 46 interfaces edit table 121
costing statistics 178 location interface points 118
output menu 62 mapping 118
reporting options 340 edit table 122
batch mean 340 example 123
interval length 341 move 119
number of replications 341 name 118
periodic 341 nodes 118
running a specific replication 341 creating additional 119
standard 340 edit table 124
viewing 12 non-passing 117
Output Viewer 3DR 364 passing 117
Overlap paths 118
load 272 creating segments 119
OWNEDRESOURCE() 518, 577 recalculating adjusted paths 325
segment edit table 120
segments 119
P pre-translation check 125
resource 137
speed/distance measurement 118
Pan 57
time measurement 118
Parameters
types
see glossary 593
non-passing 118
subroutines 240
passing 118
 ProModel 617
User Guide

PAUSE 232, 519, 578 library 306

Pause simulation 57 layout 66
PCX model text 66
importing a background graphic 213 printer setup 66, 68
Pearson5 distribution 427 change the printer settings 68
Pearson6 distribution 427 text 66
People as resources 274 Printing text within a logic window 73
PercentOp() 520 Priorities 428
PercentUtil() 521 assign 106
Performance analysis 26 claim 262
Pickup time 138 crane move 261, 262
Pitfalls in simulation 46 dynamic priority changing 408
Planning the study 26 effective 264
Points finite move 267
resource 141, 142 for a destination 280
Poisson distribution 427 locations 105, 106
Polygon modeling 280
draw 319 downtimes 281
Positioning spot preemption 281
place on an icon 320 processing destination 280
see glossary 593 selecting resources 280
Power Tools 328 resource request 261, 268
Pre-analysis 361 resources 134
Pre-break logic 166 shift 165
Precedence, see Operator precedence task move 261
Predetermined time standards 33 PRIORITY 166, 167, 297, 523, 578
Preemption ProActiveX 331
creating a preemption process record 292 PROBABILITY 407, 417
downtime 177 Probability mass function 252
entities 115 Processing 47, 143
locations 105 add routing mode 154
off-shift locations 168 create and edit process routings 143
process define 50, 143
example 293 graphically 144
logic 292 deleting a process or routing record 154
possible effects of delayed preemption 293 destination location 151
new functions 293 editing 53
resources 134, 135 editor 145
examples 135 accessing 143
see glossary 593 using 143
shift & break logic 167 entity 144, 146
Preemption logic 281 example 144
and downtimes 281 find process mode 155
system functions 577 layout window 145
preemptor() 522 location 146
timeleft() 554 logic 50, 53, 56, 89
PREEMPTOR() 293, 522, 577 move logic 151, 153
Pre-off-shift logic 166 new process mode 154
Preparing a simulation specification 26 operation logic 147
Pre-translation check 125 output part 150
Print process edit table 50, 53, 145
graphic 306 processing tools 153
618

records Queue-up
edit 71 bridge 266
routing conditions 265
adding additional blocks 155 situations 265
block number 149 unrealistic 265
edit table 145, 149 Queuing 270
entity to exit 155
path editing 154
rules 151 R
view routing button 155
tools window 145
RAND() 55, 526
using all entity type 147
RANDOM 418
Processing time
Random
using entity attributes 276
numbers 258
ProClare 329
streams 43
Product support 4
Rate of flow 182
Program defaults 584
Rate, tank flow 182, 193, 195
default values table 584
RDB files 257
Progressive refinement 35
RDT files 257
Promodel Player
RDW files 257
promodel player 334
READ 448, 527, 578
promodel player gold 335
Read data 254
PROMPT 524, 578
REAL 223, 225, 529, 578
ProSetter 330
Real number
Protect model data 68
see glossary 593
Pull systems
Real numbers 396
creating 282
REAL() 530
send statement
Recharging strategies 274
pull systems 282
Reclaim trigger events 264, 267
steps to build 282
Record
types of 282
append
to table 71
copy 71
Q information 71
between records 71
Quantity 152 delete
Queue 94, 97 from a table 70
by type 110 insert in a table 71
define 97 move in a table 71
color 97 paste 71
drawing 97 Rectangle
entity preemption 97 draw 318
first in, first out (fifo) Reference
highest attribute value 110 see glossary 593
last in, last out (lifo) view 79
lowest attribute value 110 Refinement, progressive 35
move 97 Refresh layout 83, 88
no queuing 110 Region
run-time visibility 97 see glossary 593
style 97 Registration
width 97 network installation 23
 ProModel 619
User Guide

stand-alone pc 22 edit 126

Rejection, claim attempt 263 table 127
Relational operators 398 entity search rules 137
Relationships example 126
cause-and-effect 30 general statistics report 377
Remove view 78 graphic 128
RENAME 112, 178, 531, 578 graphics 320
Rename window 127, 128
views 79 group 233
RENAME AS 149, 150 home node 137
Replace, find and 303 icon 127
Replications 37, 39 least utilized 137
running a specific replication 341 logic 128
REPORT 342, 532, 535, 578 longest idle 137
Reports 372 motion 138
view 59 move 76
Requirements multiple resource graphics 130
hardware 15 example 130
RES() 126, 396, 397, 402, 457, 461, 496, 533, 555, 560, 577 multiple, single-unit resources 131
RESET 527, 534, 571, 572, 575, 578 multi-unit 131
RESET STATS 342, 535, 578 vs. multiple single-unit 131
Reset window positions 84 name 127
Resolution node logic
grid lines 81 editor 140
Resource request 266 example 140
logic 268 notes 128
priorities 261 park search 128, 138
priority 261, 268 edit table 139
Resource statistics 269 path network 137
RESOURCE() 167, 297, 536, 537, 577 people as 274
Resource-related operation statements 426 point
free 473 see glossary 594
get 476 preemption 134
graphic 482 examples 135
jointly get 496 matrix 135
use 563 priorities 134
wait...until 568 shift downtime 134
Resources 48, 89, 126 res() 126
accessing 126 resource points 128, 141
closest 137 adding 141
cost 176, 178 deleting 142
general statistics report 376 moving 142
create 126 search
new resource 128 routines 138
define 52 rules 137
definition 126 see glossary 593
downtimes 127, 131 selecting 280
clock 132 shift & break nodes 137
define 132 specifications 128, 136
usage 133 states by percentage
dynamic 268 general statistics report 376
dynamic resources 129 static resources 129
620

statistics 127 related 82

units 127 selected 82
variability unselected 82
adding 48, 52 Routing rules 405
work search 128, 138 alternate 406
edit table 139 backup 407
Resource-specific system functions 425, 577 continue 408
last() 497 dynamic priority changing 408
next() 516 dependent 410
ownedresource() 518 dialog box 405
resource() 536, 537 empty 411
ResourceUnit() 537 first available 412
Response 42 full 421
variables 31 join 413
Response time 275 load 414
minimize 274 longest unoccupied, (lu) 415
RESQTY() 538, 577 probability 417
RETURN 239, 539, 578 random 418
Return home 268 send 419
Return home if idle 137 turn 420
Right-click user condition 422
editing 74 Routing, user condition 276
menus 87 Rule field, routing edit table 405
simulation menu 360 Rules
Rotate dialog box 109
object 321 location 91
text 96 Run
ROUND() 239, 400, 541 length 41
ROUTE 150, 373, 489, 542, 549, 578 calendar date 338
Routing time only 338
block 149 weekly time 338
color 88 model 11, 56, 337
edit table 50, 53 non-terminating simulations 40
logic 50, 53, 56 simulation 345
move logic 153 terminating simulations 39
path Run-time
color 80, 82 controls 345, 359
edit 154 animation panning 359
move 75 clock display 359
show 77, 86, 87 identifying location name 360
types 82 simulation speed 359
priority end simulation 346
see glossary 594 errors
process already routed 152
create 143 no routing defined 152
edit 143 file menu 345
quantity 152 help menu 358
start new routing block 152 information menu 353
table arrays 86, 354
* 152 locations 86, 354
block number 152 status light 354
type variables 86, 354
 ProModel 621
User Guide

interact menu 358 resource search rules

subroutines 358 closest 137
interface 234 least utilized 137
advantages 234 longest idle 137
creating 235 routines 138
defining 235, 343 work 138
example 236 Search, find and replace 303
model parameters 342, 343 SEC 401, 447, 462
numeric range 235 Seconds 401, 402, 462
parameter name 235 SED files 257
prompt 235 Segments 119
record range 235 SEND 282, 406, 419, 428, 544, 578
text 235 Sensitivity analysis 27
menus 345 Separation distance, bridge 263
models, creating 11 Serviceable nodes 261
options menu 346 SETRATE 546, 578
animation off/on 346 Settings 76, 77
debug option 346, 347 layout 80
trace output 346 printer 68
user pause 346 Setup and installation 15
zoom 346 hardware requirements 15
pause/resume simulation 346 network version 17
simulation menu 346 stand-alone pc 15
window menu 358 SFT files 257
Shell 178, 594
Shift
S assignments 163
locations 164
overlapping downtimes 169
Save
priorities 165
and run 337
resources 164
model 63
units 164
model as 63
selecting shift files 165
Scale
shift & break
grid 81
logic 166
Scenarios 337, 343
functions & statements 166
defining 344
preemption 167
parameters 343
sequence of events 166
Scheduled maintenance 274
start times 165
Scheduling a simulation project 30
usage 163
Scope 28
colors
Scroll
customize 162
arrow, see glossary 594
copy a shift 163
bar, see glossary 594
definition 161
box, see glossary 594
accessing 161
Search
adding work to a shift or break block 162
entity search rules
advantage of shifts 161
closest 137
editing work or break time 162
longest waiting 137
editor 161
maximum value 137
menus 161
with minimum value 137
erasing work or break time 163
park 138
downtime
622

principles 167 description 62

examples 168 during run time 346
locations 167 model parameters 337
overlapping downtimes 169 options 337
preemption 168 running a model 337
resources 169 run-time
priorities 134 end simulation 346
editor 161 pause/resume 346
menus 161 save & run 337
file 256 scenarios 337
priorities non-terminating 38, 39
break 165 running 40
end shift 165 options 57, 338
off-shift 165 clock precision 339
start break 165 common random numbers 340
shift & break logic 297 customized reporting 342
break logic 297 disable
functions & statements 297 animation 339
off-shift logic 297 cost 339
pre-break logic 297 time series 339
pre-off-shift logic 297 display notes 339
sequence of events 297 maximum run length 339
Shift Library 331 output
Shifts & breaks 274 path 338
logic statements reporting options 340
priority 523 batch mean 340
skip 547 interval length 341
system functions 425 number of replications 341
dtleft() 463 periodic 341
forlocation() 470 running a specific replication 341
forresource() 472 standard 340
resource() 536, 537 pause at start 339
Shift-specific system functions 577 run length
forlocation() 577 calendar date 338
forresource() 577 time only 338
Show weekly time 338
conveyors and queues 97 pitfalls 46
grid 77, 85, 87, 312 planning
hidden networks 87 data gathering 32
networks 77, 85 steady-state 39, 40, 42
routing paths 77, 86, 87 steps 25
SimRunner 360 analyzing the output 45
benefits 361 building the model 35
define conducting experiments 37
input factors 361 defining the system 30
objective function 361 planning the study 26
stage three simulation optimization 362 reporting the results 45
starting a new project 361 terminating 38, 39, 41
Simulation running 39
animation off 58 Single-section conveyors 271
focus 31 Sizing 76
menu 337 SKIP 166, 297, 547, 578
 ProModel 623
User Guide

Snap basic 91
lines to border 155 cost 591
to grid 76, 77, 87 displaying on screen 281
Snap to grid system throughput 281
off 272 total system time for entities 281
on 272 none 91
SOUND 548, 578 observation-based 224
Spacing resource 269
load 272 time 595
Speed time series 91
and distance 118 time-weighted 224
bridge 261 view 59
control bar 57 Status
conveyor 100, 270 light 94, 354
crane bridge 265 place on icon 321
factor 120 see glossary 594
hoist 261 Steady-state 37, 40, 41
horizontal 275 simulation 39, 40, 42
simulation Step
run-time control 359 back 322
traveling empty/full 138 front 322
vertical 275 trace 58
SPLIT AS 97, 98, 112, 149, 150, 151, 178, 218, 373, 449, 453, STOP 552, 578
483, 499, 549, 561, 578 Stream, distributions 427
Spreadsheet Streams 258
external file 578 accessing 258
SQRT() 551 definition 258
Square edit table 258
draw 318 example 259
Square root 551 multiple 44
Stage one random number 43, 258
pre-analysis 361 usage 258
Stand-alone PC String
setup and installation 15 see glossary 594
Start new block 152 Strings
Stat::Fit 299 character 393
State expressions 399, 402, 578
initial 38 char() 402
terminating 38 character strings 402
State Chart 382 concatenation operators 402
Statements 426 ent() 402
and expression groups 577 format() 402
blocks 426 loc() 402
control 426 numeric expressions 402
cost related 489, 490, 491 res() 402
entity-related operation 426 functions
general action 426 char() 446
nested 289 format() 471
new 357 Submodel
resource-related 426 merge 64
Static resources 129 tank 180
Statistics 91 import 180
624

uses 10 menu, see glossary 594

Submodels System functions 399, 425
tank break logic-specific 577
tank_dec 190 downtime-specific 577
tank_inc 190 entity-specific 577
tank_risetrigger 191 location-specific 577
Subroutines 89, 238, 399 node logic-specific 577
accessing 238 preemption logic specific 577
and macros 578 resource-specific 577
create 238 shift-specific 577
definition 238 System throughput 281
edit 238
table 238, 240
example 240 T
executing interactive subroutines during run time 358
external 242
Table
format 239
editing 70
interactive 241
functions 248
logic 239, 241
accessing 248
parameters 239, 240
defining 248
return statement 239
edit table 249
subroutines vs. macros 242
editor 248
tank
examples 248, 249
tank_cap 192
Table functions 399
tank_dooperation 193
TAKE 453
tank_doprep 195
TANK_CAP 192
tank_empty 186
TANK_DEC 190
tank_falltrigger 191
TANK_DOOPERATION 193
tank_fill 185
TANK_DOPREP 195
tank_freecap 192
TANK_EMPTY 186
tank_godown 193
TANK_FALLTRIGGER 191
tank_godownsched 194
TANK_FILL 185
tank_rate 199
TANK_FREECAP 192
tank_selectinput 198
TANK_GODOWN 193
tank_selectoutput 196
TANK_GODOWNSCHED 194
tank_setlevel 189
TANK_INC 190
tank_setstate 196
TANK_RATE 199
tank_transfer 187
TANK_RISETRIGGER 191
tank_transferdownto 188
TANK_SELECTINPUT 198
tank_transferupto 187
TANK_SELECTOUTPUT 196
tank_updatestats 198
TANK_SETLEVEL 189
type (none, real, integer or interactive) 238
TANK_SETSTATE 196
valid usage 239
TANK_TRANSFER 187
Subtraction 398, 399, 403
TANK_TRANSFERDOWNTO 188
Supply chains & logistics 7
TANK_TRANSFERUPTO 187
Switches 76
TANK_UPDATESTATS 198
Symbols and notation
Tanks 94, 95, 180
keyboard 3
add labels and figures 181
logic 3
basic concepts 181
text 3
border color 180
System
capacity
definition 30, 31
 ProModel 625
User Guide

maximum 91 TIMESUSED() 555, 577

change between a tank and a gauge 181 Title of model 171
define 180 Toolbar 85
edit 180 Tools
fill color 180 button bar 211
flow time step 182 menu
levels 181 description 62
rate of flow 182 options
submodel 180 confirm record deletion 325
import 180 long build menu 325
Tanks, time units 182, 193, 195 recalculating adjusted paths 325
Task move priority 261 settings
Technical support 4 directories 325
Terminating processing 153
simulation 38, 39, 41 TRACE 556, 578
running 39 Trace 346
state 38 continuous 58, 352
Termination logic 172 filtered 352
execution time 172 off 351
Testing options 351
hypothesis 42 output to file 353
Text 3 step 58, 351
clear 72 window 11
copy 72 Training 8
cut 72 Trajectory, hoist and bridge 267
dialog box 96 Transfer lines 7
file Transfering a license key 23
view 57 Translation status window 345
label 94 Travel to park 269
paste 72 TRC files 257
see glossary 595 Triangle
THEN 290, 486 draw 317
THEN FREE 295, 514 Triangular distribution 427
THREADNUM() 553 Trigger events, reclaim 267
Throughput 281 TRUNC() 557
Tile 84 TURN 420
Time 118, 120 Two-dimensional array 228
between autosaves 326 Two-level design 43
blocked 269 Type 281
default grid time 81 conversion functions 425
expressions 399, 401 ent() 466
colon notation 402 real() 530
load delivery 270 trunc() 557
move 269 numeric 397
statistics 595 Type of experimentation 28, 29
studies 33
time and condition dependent activities 31
time-weighted statistics 224 U
units 171
Time units, tank 182, 193, 195
Unbatching 278
TIMELEFT() 293, 554, 577
UNGROUP 97, 98, 178, 278, 283, 373, 449, 453, 483, 499,
Timeplot 386
626

549, 558, 561, 578 icon 223

Ungroup editing 225
graphics 214, 309 placement 224
objects 309 removal 225
Uniform distribution 427 initial value 223
Units 91 input 31
location 100 layout 224
UNITS() 560, 577 local
UNLOAD 97, 98, 221, 279, 449, 453, 483, 499, 549, 558, 561, example 225
578 variables 225
Unlock response 31
graphics 214 statistics 223
UNTIL FULL 151, 411 type (real or integer) 223
Usage-based downtime 133 Vehicles, industrial 274
USE 115, 134, 175, 178, 261, 267, 269, 293, 296, 348, 428, Verification, model 36
475, 476, 563, 578 Vertical bridge crane 275
User Vertical speed 275
distributions 34, 48, 251 VIEW 566, 578
accessing 251 View 58, 77, 86, 88
continuous 253 add 78
cumulative 251 define 77
definition 251 location 93
discrete 251 managing 78
edit table 251 menu 217
table 251 accessing 76
type (discrete or continuous) 251 commands 83
pause 58 description 61
USER CONDITION 407, 422 edit table 83
User-defined distribution 427 color 83
Utilization edit table font 83
graphs 13 layout settings 80
background color 80, 81
grid settings 80, 81
V routing path color 80, 82
refresh layout 83
reset window positions 84
Valid expressions & statements 577, 579
settings 77
fields evaluated during simulation 581
switches 76
fields evaluated only at translation 579
views 77, 86
groups by field 579
managing 78
Validation, model 37
reference
Variability
in model logic 79
resources
zoom 77, 79, 86
adding 48, 52
to fit layout 77, 86
VARIABLE() 565, 577
model
Variables 89, 223, 399
reports 59
accessing 223
statistics 59
displaying information during run time 86, 354
text 66
edit
move
icon 225
down 79
table 223
up 78
global variable definition 223
output 12
 ProModel 627
User Guide

reference
in model logic 79
X
remove 78
rename 79 XSUB() 238, 573, 577
routing 155 external subroutine calls 573
select 77 XWRITE 255, 448, 471, 571, 575, 578
view 78
with shortcut key 78
set view 79 Z
text 66
file 57 Zero units 127
Views Zone
defining 77 active operation 268
selecting 78 blocking 273
claim examples 263
claims 263
W extended movement 263
Zoom 57, 58, 77, 79, 86, 88
WAIT 134, 149, 166, 167, 175, 291, 293, 296, 297, 348, 375, animation 353
431, 476, 554, 567, 578 custom 79
WAIT UNTIL 109, 140, 166, 182, 226, 232, 296, 297, 342, to fit layout 77, 86, 88
374, 375
WAIT...UNTIL 431, 568, 578
WARMUP 342, 569, 578
Warm-up period 40
determine 40
initial 41
Weeks 401, 447, 462
Weibull distribution 427
What’s new
features
activex objects 586
statements and functions 357
WHILE...DO 229, 234, 289, 431, 437, 492, 570, 578
Window menu 84
description 62
during run-time 358
WIP 281, 350, 544
WK 401, 447, 462
WMF
importing a background graphic 213
Work search 128, 138
and park search 268
edit table 139
exclusive 268
non-exclusive 268
see glossary 595
WRITE 255, 448, 571, 575, 578
Write data 254
WRITELINE 255, 448, 572, 575, 578
WWW.PROMODEL.COM 61
628