








Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
PROCESS INTERACTION APPROACH and SIMAN ARENA SOFTWAREPROCESS INTERACTION APPROACH and SIMAN ARENA SOFTWAREPROCESS INTERACTION APPROACH and SIMAN ARENA SOFTWAREPROCESS INTERACTION APPROACH and SIMAN ARENA SOFTWARE
Typology: Exams
1 / 14
This page cannot be seen from the preview
Don't miss anything!









PROCESS INTERACTION APPROACH and SIMAN/ARENA SOFTWARE Process-Interaction approach is based on; i- giving descriptions of all ‘processes’ that all entities undergo in the system, ii- simulating the system by focusing on ‘interactions’ between different processes. Modeling and simulation using process-interaction thus requires firstly providing descriptions of all processes that different entities undergo. Simulation programming using process-interaction approach requires special-purpose simulation software. Such software (like SIMAN/ARENA) are high-level packeges that provide a ‘descriptive’ programming platform (instead of traditional ‘procedural’ programming). Simulation using event-scheduling is easily done by any procedural programming language (such as C++, Java, True Basic, Fortran, R, Python). But programming for process-interaction simulation using such general-purpose procedural languages would be very difficult. Special-purpose simulation software packages such as SIMAN/ARENA offer the users the necessary built-in structures, functions and macros to facilitate process-interaction modeling and simulation. We will use SIMAN/ARENA as an example. Like all processinteraction software, ‘ entity’ is the most essential concept. They enter the system and travel from ‘process to process’, until they complete their lifecycle, at which point they leave the system. Entities have attributes , which are either built-in or user-defined, which determine the processing rules for different entities.
Certain processes require some limited resources (such as servers). Defining and using such resources is critical in SIMAN/ARENA (or any other process-interaction software). When all resources needed for a particular process are full, a Queue is formed in front of that process. Thus, defining Queues is another critically important concept in SIMAN/ARENA. Entities are ‘alive’; they constantly try to push forward through the system and complete their lifecycles. They try to move from process to process until the end. The processes are represented by ‘ process blocks ’ in SIMAN/ARENA. (So programming is mostly done graphically/visually, by connecting different process blocks in the logical order that exist in real system). By default, the movement of entities is sequential (from one block, to the next connected block). But branching (non-sequential flow) is also provided of course. Execution of the program: A block (corresponding programming statement) is executed, when an entity enters it. This execution logic and order is absolutely critical to understand. (This why SIMAN is called a ‘ descriptive’ programming’ software -unlike procedural ). If different entities enter different block simultaneously, then different blocks are executed simultaneously, in parallel. A SIMAN model is a collection of logically ordered, connected and defined Blocks. A SIMAN model provides a complete description of all processes that all entities undergo. In addition to this model file, a SIMAN program also requires an Experiment file , in which all parameters, variables, simulation and initial conditions are defined. A SIMAN simulation run is obtained by linking and running the model and experiment files.