Optimize 10.3.0 | webMethods Optimize Documentation | Using webMethods Optimize | Monitoring System Component and Business Process Performance | Viewing the Overall Status of Process Instances | Obtaining EDA Event Information about Process Stages
 
Obtaining EDA Event Information about Process Stages
A process stage is a logical grouping of one or more process steps accompanied by a rule of some sort, such as a threshold for execution duration. Usually, the stage represents an important role from a business perspective, and it is an object of interest for business process analysts. A stage can be defined in any process model using the Process Development perspective for Software AG Designer. After the process model is uploaded for analysis, the webMethods Process Tracker component picks up the process model and its stage definitions from the Process Audit database.
Whenever an event for process or step execution that marks the beginning of a stage is received, Process Tracker produces an ProcessStageInstanceChange event for the given stage, reporting that the stage status is “running”, and begins to evaluate the rule associated with this stage. If the rule is violated, Process Tracker produces another ProcessStageInstanceChange event, reporting the current stage status and the time when the rule was breached. When a process stage is completed, Process Tracker produces another ProcessStageInstanceChange event, reporting that the stage status is now “complete”. It also produces the ProcessStageInstanceDuration event which contains the actual stage execution duration.
When a process instance containing stages is completed or canceled, Process Tracker changes the status for all running stage instances to “incomplete”, then evaluates the rules associated with those stage instances. If the rules are violated, Process Tracker sends ProcessStageInstanceChange events reporting that the stage instance status is “incomplete” and the time when the rule was breached.
The following table describes the EDA event types that Process Tracker produces.
Event Type
Description
Process Stage Instance Change
Events of this type are produced by Process Tracker every time it detects that the process execution passes through a point that has been defined as the beginning or the end of a stage, and reports the change in state for the respective process stage. It also contains the breach time in case the rule associated with a stage instance has been breached.
Process Stage Instance Duration
Events of this type are produced by Process Tracker every time it detects that a stage has completed. The events contain the actual stage duration.
For event schema definitions and other information about working with EDA event types and processes, see the webMethods BPM Process Development Help.
The following table lists the process stage intrinsic KPIs.
Process Stage KPI
Description
Breach Count by Stage
Counts the number of stages for which an associated rule has been breached. The KPI instance names conform to this template: "Breach Count by Process $Process.ProcessName Stage $Stage.StageName". For example: "Breach Count by Process PricingProcess Stage ValidatePricing". The aggregation interval is one minute, and if there are no breached stage instances during the aggregation interval, a zero value is added.
Instance Count by Stage
Counts the stage instances generated by Process Tracker. The KPI instance name conforms to this template: “Instance Count by Process $Process.ProcessName Stage $Stage.StageName”. For example: “Instance Count by Stage PricingProcess Stage ValidatePricing”. The aggregation interval is one minute.
Complete Count by Stage
Counts the completed stage instances generated by Process Tracker. The KPI instance name conforms to this template: “Complete Count by Process $Process.ProcessName Stage $Stage.StageName”. For example: “Complete Count by Process PricingProcess Stage ValidatePricing”. These KPI instances are populated only when the stage ending milestone is processed by the Process Tracker. The aggregation interval is one minute, and no zero values are added if there are no stage instances finished during the aggregation interval.
Incomplete Count by Stage
Counts the incompleted stage instances generated by Process Tracker. The KPI instance name conforms to this template: “Incomplete Count by Process $Process.ProcessName Stage $Stage.StageName”. For example: “Incomplete Count by Process PricingProcess Stage ValidatePricing”. These KPI instances are populated when the process instance is complete before a stage ending milestone is processed by Process Tracker. The aggregation interval is one minute, and no zero values are added if there are no stage instances finished during the aggregation interval.
Process Time by Stage
Measures the average execution time of the stage instances generated by Process Tracker. The KPI instance names conform to this template: "Processing Time by Process $Process.ProcessName Stage $Stage.StageName". These KPI instances are populated only when the stage ending milestone is processed by the Process Tracker. Process Tracker contains an early stage breach detection mechanism that keeps track of the actual time passed from the beginning of the stage instance and sets the state to Breached if the actual time exceeds the time specified as a stage breach condition. Stage instances marked as Breached by the early stage breach detection mechanism will not be a part of this measurement, because their actual execution time is still unknown (the ending milestone has not been received yet). The aggregation interval is one minute, and no zero values are added if there are no stage instances finished during the aggregation interval.