WebSphere Lombardi Edition 7.2 >


Configure KPIs and SLAs

The data that Lombardi tracks and stores for key performance Indicators (KPIs) enable you to analyze process performance as well as create service level agreements (SLAs)


Use KPIs

Key performance indicators (KPIs) are measurements that Lombardi tracks at process run time, storing results that you can use to analyze process and task performance in the Optimizer. Lombardi includes the following types of KPIs:

KPIs Description
Standard KPIs Reside in the System Data Toolkit. By default, most of the standard KPIs are associated with each activity that you add to a BPD diagram. Click the KPIs option in the properties for an activity to see the associated KPIs. Each of these KPIs has default settings that you can change.
Custom KPIs You can define custom KPIs and associate them with one or more activities in your BPDs.

When you run instances of a BPD, Lombardi tracks and stores data for configured KPIs in the Performance Data Warehouse. Lombardi uses stored KPI data when you run certain types of historical analyses in the Optimizer. (Not all historical analyses available in the Optimizer rely on data generated and stored due to KPIs. See Simulating and optimizing processes for more information.)


  1. Create custom KPIs
  2. Associating KPIs with activities

The standard KPI, Total Time (Clock), is associated with each BPD by default. To view the settings for this KPI, click the Process KPIs tab in the Designer. (You cannot alter the settings for this KPI.)


Use SLAs

You can create service level agreements (SLAs) based on standard and custom KPIs. SLAs enable you to establish a condition for one or more activities that triggers a consequence. For example, you can create an SLA that causes Lombardi to send an email notification when a particular activity takes longer than expected to execute.

When you run instances of your processes, SLA consequences do not trigger until the associated activity starts or completes. For example, if you configure an SLA to send an email notification when a particular activity takes longer than two days to execute, Lombardi does not send the notification at the time that the violation occurs. Lombardi sends the notification at the time that the activity is complete. So, if the activity takes three days to complete, Lombardi sends the notification at that time, informing users of the violation. SLAs enable you to easily report on violations and, for example, understand the trend in violations over time.

To enable end users to immediately react to time-based conditions for a single activity, use a timer event to capture the violation. The consequence of the violation can be any type of implementation that you want to develop as

If an SLA is based on something other than time, consider using exposed process values (EPVs) to model the SLA. See Create exposed process values (EPVs) for more information. To provide immediate notification of violations, develop the appropriate implementation for your needs (such as a timer event for an escalation), and then also create an SLA so that you can track and report on historical trends.

See Create SLAs to learn how to configure SLAs. SLAs enable in-depth performance analysis over time

Analysis Description
SLA Overview Scoreboard View this report in Lombardi Process Portal to see the name, description, and current status of each configured SLA, as well as a trend chart of violations for all SLAs or a chosen SLA. See Use out of the box scoreboards for more information.
Custom SLA reports Leverage SLA data stored in the Performance Data Warehouse to create custom reports using Lombardi or a third-party tool. To learn more about the data that is tracked and stored for SLAs, read about the SLASTATUS and the SLATHRESHOLDTRAVERSALS views in Performance Data Warehouse database architecture. See Reporting options for more information about the types of custom reports you can create.
Historical analysis in Optimizer view When running scenarios, choose the SLA visualization mode to display results based on SLA violations. See Run simulations, historical analyses, and comparisons for more information.

+

Search Tips   |   Advanced Search