IBM Certification Test 992.6 - Modeling Business Measures
How to define business metrics for business processes
Metrics
A metric is a holder for information, usually a business performance measurement. A metric can be used to define the calculation for a key performance indicator (KPI), which measures performance against a business objective. Examples of metrics are: the working duration of a process, the name of the user assigned to a task, a supplier’s average response time, and the average cost of the risk assessment step in an insurance process.
There are two types of metrics:
- Instance metrics
which return the result from one run of the process. For example, if each run of the process is a customer order, you might want to capture information (such as the customer name or the amount) each time. - Aggregate metrics
which are calculated across multiple runs of the process so that you can find the average, maximum, minimum, sum, or number of occurrences. For example, you might want to capture the total number of orders, or the average amount across all orders.
An aggregate metric can combine an instance metric with an aggregation function (average, maximum, minimum, sum, or count).
When to create instance metrics versus aggregate metrics
The custom metrics that you create in WebSphere® Business Modeler can be either instance or aggregate metrics. They contain implementation information and hints to the developer using the Monitor Model editor in the WebSphere Business Monitor development toolkit. If you want to create an aggregate metric and know what the underlying instance metric is, you can create the instance metric and then specify an aggregation function. Alternatively, you can choose to create only the aggregate metric and have the developer in the Monitor Model editor add the underlying instance metric.
If the monitor model is to be exported to WebSphere Integration Developer and used to monitor a WebSphere Process Server application based on a model created in WebSphere Business Modeler, the monitor model can be exported at the same time as the process. The business measures are then directly tied to the implementation of the process, and the events and other elements for monitoring the process are created automatically. To completely specify the business measures in this way, you must create instance metrics using predefined business measure templates, and any aggregate metrics or KPIs must be based on those instance metrics.
If the monitor model is to be exported to WebSphere Integration Developer and used to monitor a WebSphere Process Server application based on a model created in WebSphere Business Modeler, the monitor model can be exported at the same time as the process. The business measures are then directly tied to the implementation of the process, and the events and other elements for monitoring the process are created automatically. To completely specify the business measures in this way, you must create instance metrics using predefined business measure templates, and any aggregate metrics or KPIs must be based on those instance metrics.
- Instance metrics
Instance metrics return the result from one run (or instance) of the process. Examples of instance metrics are the working duration of a process, the name of the assigned user, a supplier’s response time, and the cost of the risk assessment step in an insurance process. - Aggregate metrics
Aggregate metrics are calculated across multiple runs (or instances) of the process. You use aggregate metrics to find the average, maximum, minimum, sum, or number of occurrences of a situation or event. Examples of aggregate metrics are the average working duration of a process, the minimum response time for a supplier, and the maximum cost of the risk assessment step in an insurance process.
Parent topic: Monitor models
No comments:
Post a Comment