(We won’t include a graphic display since you’re now familiar with the drag-and-drop sequence.) 3. Arena will connect it to the primary (True) exit point of the Decide module. Drag a Dispose module to the right of the Decide module. Select the Decide shape so that our first Dispose will be connected automatically. Then, we’ll complete the flowchart with another Dispose for returned applications. Incomplete applications (False result to the Decide test) will leave via the bottom connection.ĩ Dispose the Applications and Terminate the Processĭispose the applications to terminate the process Next we’ll place the Dispose module that represents accepted applications, connecting to the True (right) output from the Decide shape. If the mortgage application has a complete set of information, it will leave the Decide module from the right side of the diamond shape, representing the True condition.
Drag a Decide module to the right of the Process module. If you’re using the Auto-Connect feature (i.e., it’s checked on the Object > Auto- Connect menu), be sure that the Process module is selected so that the Decide module will be connected to it. If it’s not, select it to turn on this option.Ĩ Decide if the Applications are CompleteĪfter the Process, we have a Decide module which determines whether the mortgage application is complete. If your Create and Process weren’t connected automatically when you placed the Process, check the Object > Auto-Connect menu to verify that it’s checked. As with the Create, the Process module has a default name that we’ll replace later. Arena will automatically connect the two modules. Drag a Process module from the Basic Process panel into the model window, placing it to the right of the Create. Be sure that the Create module is selected so that Arena will automatically connect the Process to the Create module.
Next in our flowchart is a Process module that represents the Review Application step. After it’s created, each entity moves from the Create module to the next shape in the process flow. When you simulate the flowchart, individual entities will be created according to timing information you supply in the Create module properties. Navigate panel: Allows you to display different views of your model, including navigating through hierarchical submodels and displaying a model thumbnail.Įvery process flow starts with a Create module. Reports panel: Contains the reports that are available for displaying results of simulation runs. The Project Bar hosts panels with the primary types of objects that you will work with: Basic Process panel: Contain the modelling shapes, called modules, that you’ll use to define your process.
To model your process in Arena, you’ll work in three main regions of the application window.
To begin, we’ll look at the process of receiving and reviewing a home mortgage application. Analyze how your system will perform in its “as-is” configuration and under a myriad of possible “to-be” alternatives so that you can confidently choose the best way to run your business.Ĥ Task We will examine a simple mortgage application process (with modules) to illustrate how you can model, simulate, visualize, and analyze with Arena. Visualize your operations with dynamic animation graphics. Simulate the future performance of your system to understand complex relationships and identify opportunities for improvement. Model your processes to define, document, and communicate. Analyze a Home Mortgage Application Process in Arena By Terence James HaydockĢ Overview Introduction Task Arena’s Modelling EnvironmentĬreate Application Entities Process the Applications Decide if the Applications are Complete Dispose the Applications and Terminate the Process Results Summary