At least one terminating result should be present at the end of the process in the context diagram. Terminating results can be added at any level of decomposition and are used to calculate the efficiency of the process based on the attributes associated to the objects when they were introduced into the process. An End event has an end event type that defines the cause for the event.

Enables you to pass objects from a Child diagram to the Parent diagram.

A terminating result is designated as either a Goal, Reject, or Neither. Goals represent a desired outcome that usually generates revenue while Rejects normally incur a cost.

Scaler is provided to vary the revenue or costs associated to an object when it terminates, for example a Goal that is achieved early in the process might generate more revenue than one at the end of the process.

Minimum and Maximum times can be specified which are used to determine whether the time an object has taken to arrive at a 'Goal' result is in agreed service level standards.

Select Hour, Minute, Second, Day or Week.