All the diagrams and definitions applicable to simulation using the Catalyst notation are contained in the existing browser. Objects are stored in a hierarchy and can be reused by dragging from the browser into diagrams and definitions where appropriate.

The simulation must know which diagram provides the context for the simulation. This diagram does not necessarily have to be at the top of the tree and will be deemed to be the diagram open when the request is made to run the simulation.

You generally start with a relationship map (see Relationship map diagrams for Business Process Modeling), which describes the overall process of a part of the business or a system. The Process Threads on this Relationship Map diagram are decomposed with Process Chart diagrams that show further detail of the process flow.

A Relationship Map diagram is used to show relationships between definitions that occur across diagrams. When creating a Relationship Map diagram there are three symbol types that are used for Simulation. These are Event, Process Thread, and Result.

An Event Symbol represents when Process Objects are generated or existing objects from a parent diagram can be received.

A Process Thread is represented by one or more Process Chart diagrams, which graphically shows the Events, Processes, and Results of the thread (or part of the thread).

A Result Symbol represents the end result of the process or the passing of generated objects to the next process in the hierarchy.

Mandatory and Optional Sequence lines represent the flow of Logic in a process.

When creating a Process Chart diagram there are several different symbol types. These symbols are Event, Process, Result, Flow Break, and Iteration.

An Event Symbol represents when Process Objects are generated or existing objects from a parent diagram can be received.

A Process Symbol represents who and when the Objects will be generated.

A Result Symbol represents the end result of the process or the passing of generated objects to the next process in the hierarchy.

A Flow Break Symbol represents the Object being held for a specific amount of time before continuing to the next process. No Resources are required.

An Iteration Symbol represents the reprocess of information.

There are a number of generic properties that will apply to these symbols on the Sim Definition tab.

Determines the availability of resources and processes.

Allow complex flow logic at junctions and provide the user with information about objects at each stage of the simulation for debugging the model.