Home  Administration > Application Administration > Dashboard Administration > Configuring KPIs > KPIs for User Modes > Setting Up User Mode Functionality



Setting Up User Mode Functionality

You set up user mode functionality in Mercury Business Availability Center by defining the mode for users, defining the KPI versions for each mode, and attaching the KPI versions to the CIs.

Assigning a User Mode

There are two ways to assign a user mode to a user:

Defining KPI Versions for the User Modes

The following steps describe how to define different versions of a KPI to use with each user mode.

To define KPI versions for user modes:

  1. Access the Admin > Dashboard > Repositories > KPIs page.
  2. Define the business user version of the KPI:
    • Clone the KPI.
    • Open the copy for editing.
    • In the KPI Details window, rename the copy by adding the suffix "_biz" (for example, Availability_biz).
    • Select Business in the Applicable for User Mode list.
  3. Define the operations user version of the KPI:
    • Override the KPI.
    • Open the new version for editing.
    • In the KPI Details window, rename the new KPI by adding the suffix "_ops" (for example, Availability_ops).
    • Select Operations in the Applicable for User Mode list.
    • Note: The overridden version of the KPI replaces the original KPI throughout Dashboard, so all CIs that are assigned the original CI (for example, Availability) are automatically updated to the new version (for example, Availability_ops).

      For more information on cloning and overriding KPIs, see KPIs Repository.

  4. Edit the details for each KPI version, according to your requirements. For example, you may want different business rules to apply to each version. For more information, see Specifying the KPI Details.
  5. If you want to use a different version of a business rule with each KPI version, then you must define the rule versions in the Business Rules Repository. For example, for two versions of the Availability KPI, you may require two versions of the Transaction Availability Rule, each with different default objective values.
  6. For details on defining business rules, see Business Rules Repository.

Attach KPI Versions to CIs

You manually attach the KPI versions to the CIs to which you want them to apply. If the original KPI was already attached to CIs (for example, the Availability KPI is automatically attached to transaction CIs), then the KPI version that overrode the original (for example, Availability_ops) is automatically attached to the CIs instead. You then manually attach the second KPI version (for example, Availability_biz).

To attach the KPI versions to CIs:

  1. In the Admin > Dashboard > KPIs page, add the KPI versions to each CI where they are required, so that the CIs have both versions of the KPI. You can add the KPI to multiple CIs in one operation. For more information, see Attaching New KPIs to CIs.
  2. Edit the KPI properties as required in the New KPI/Add KPI to Multiple CIs window. For example, you may want to define different objective values for the KPI.
  3. For KPIs that require selectors: Do not define anything in the Selector area, leave the selector expressions empty. After you click OK to add the KPI to the CI(s), Mercury Business Availability Center automatically replaces each blank selector with the default selector defined for the other KPIs attached to each CI.
  4. Click OK to save the KPI details. The KPI version is added to each selected CI, and propagates up the hierarchy to the parent CIs.

Result in Dashboard

Each user type sees in Dashboard the appropriate KPI version for their assigned user mode (operations or business user), for all KPIs that are defined as specific to a user mode. Users who are not assigned a user mode (undefined) see KPIs for both modes, as do system administrators:

Example of entering new values for transaction CIs

In the Geographical Map and Custom Map tabs, status at a location is based on whichever KPI versions the user sees in Dashboard:

Example of entering new values for transaction CIs

Notes and Limitations




Copyright 2006 Mercury Interactive Corporation