IBM Certification Test 992.6 - Modeling Business Measures
Demonstrate knowledge of predefined business measures
Business measure templates
You can create business measures based on a set of predefined business measure templates. The templates are designed to help you create business measures that are frequently required. For example, you can add a business measure to track the working duration of a task or whether a process is delayed. You can also add a business measure to access any data carried through the process by a business item.
Business measures based on a template are always instance metrics. They track information over a single run of the process. Business measures based on a template are identified by a specific
icon overlaying the regular icon.
If you plan to use WebSphere® Integration Developer to complete the monitor model and monitor a WebSphere Process Server application, and if you want to completely specify the business measures in WebSphere Business Modeler, you must create instance metrics using predefined business measure templates and create any aggregate metrics or KPIs based on those instance metrics.
The template information ties the instance metric to the process and the element within the process. The name of the business measure is based on the element (top-level process, task, loop, or local subprocess) and the template that you select. For example, if you right-click an Order Received task and create a business measure based on the State template, the business measure is named Order Received State. If you create a business measure based on an Order business item and the Business Item Input template, the business measure is named Order Business Item Input.
If you create a business measure based on a business item input or output, you also select the business item attribute that you want to track. For example, you might have an attribute that holds the total amount of an order, the number of items in an order, or the customer rating. You might want to change the name based on the attribute that you want to track, for example Order Amount rather than Order Business Item Input.
Business measures based on a template are always instance metrics. They track information over a single run of the process. Business measures based on a template are identified by a specific
icon overlaying the regular icon.If you plan to use WebSphere® Integration Developer to complete the monitor model and monitor a WebSphere Process Server application, and if you want to completely specify the business measures in WebSphere Business Modeler, you must create instance metrics using predefined business measure templates and create any aggregate metrics or KPIs based on those instance metrics.
The template information ties the instance metric to the process and the element within the process. The name of the business measure is based on the element (top-level process, task, loop, or local subprocess) and the template that you select. For example, if you right-click an Order Received task and create a business measure based on the State template, the business measure is named Order Received State. If you create a business measure based on an Order business item and the Business Item Input template, the business measure is named Order Business Item Input.
If you create a business measure based on a business item input or output, you also select the business item attribute that you want to track. For example, you might have an attribute that holds the total amount of an order, the number of items in an order, or the customer rating. You might want to change the name based on the attribute that you want to track, for example Order Amount rather than Order Business Item Input.
Templates can be applied to business measures created on top-level processes, tasks, loops, and subprocesses, which are collectively referred to as "activities" in the table below. The following templates are provided:
| Name | Value Type | Description |
|---|---|---|
| State | Text | The current state of the activity |
| Working Duration | Duration | The length of time that the activity is actively running
Note: For subprocesses and loops, this template is not tied to an implementation in WebSphere Process Server and cannot be used to completely specify an instance metric. |
| Elapsed Duration | Duration | The difference between the start time and end time of the activity, which might include idle time as well as processing time |
| Is Delayed | Boolean | Whether the activity is delayed
Note: This template is not tied to an implementation in WebSphere Process Server and cannot be used to completely specify an instance metric. |
| Start Time | DateTime | When the current run of the activity started |
| End Time | DateTime | When the current run of the activity ended |
| Assigned User | Text | The name of the user who claims the activity at runtime (applicable only to human tasks) |
| Is Escalated | Boolean | Whether a task escalation has taken place (applicable only to human tasks) |
| Iteration Counter | Integer | The number of times a loop runs (applicable only to loops) |
| Calling Process Name | Text | The name of the process that started this top-level process (applicable only to top-level processes)
Note: This template is not tied to an implementation in WebSphere Process Server and cannot be used to completely specify an instance metric. |
| Business item input | Type of the selected business item attribute | The value of an attribute of a business item that is an input to the activity
Note: For subprocesses and loops, this template is not tied to an implementation in WebSphere Process Server and cannot be used to completely specify an instance metric. |
| Business item output | Type of the selected business item attribute | The value of an attribute of a business item that is an output from the activity
Note: For subprocesses and loops, this template is not tied to an implementation in WebSphere Process Server and cannot be used to completely specify an instance metric. |
No comments:
Post a Comment