An indicator is a rule of a time counter activation specified by proper conditions for starting, pausing, resetting, and stopping this counter. It also determines the time limit for declaring SLA as breached and contains time conditions of a commitment type implementation.
For example, based on your SLA agreement, you can create separate SLA indicators for incidents that are having an impact from Low to Very High and set a separate Breach Time value for them.
When an indicator starts, the system automatically generates an indication, a time counter that tracks current timings and time points of the target service level commitment.
Depending on your business needs, you may need different types of indicators:
Role required: service_level_manager. |
To add a new indicator, please complete the following steps:
Indicator form fields
Field | Required | Description | ||
---|---|---|---|---|
Name | Y | Specify the indicator name.
| ||
Agreement | N | Specify an agreement related to this indicator containing tracking metrics. | ||
Commitment type | N | Specify the commitment type for this indicator. Available options:
| ||
Table | Y | In this field, select a table to apply the Indicator conditions.
| ||
Inheritance | N | Select this checkbox if you are creating an indicator for a parent table, and it is necessary to use it for all child tables.
| ||
Active | N | Select this checkbox to make the indicator active or inactive. | ||
Indication start time | N | Select one of two options:
| ||
Start time field | Y | Define the column of the Date/Time type from which indications will be calculated, i.e., an indication retrieves the value for the start time from this column.
| ||
Indication breach time | N | Select one of two options:
| ||
Breach time field | Y | Define the column of the Date/Time type from which indications will be calculated, i.e., an indication that retrieves the value for the breach time from this column. After saving the form, the Breach time field field becomes read-only.
| ||
Business duration | Y | Set up a business time measure for the SLA to run before it is marked as Breached.
| ||
Minimum duration | Y | Set a minimum duration that restricts the creation of an indication and its existence. After saving the form, the Minimum duration field becomes read-only.
| ||
Schedule | Y | Select a working schedule from the list. It determines the working hours that the system uses when calculating the actual duration of the Commitment implementation under certain conditions. To configure this timeline, use the Schedules feature. | ||
Timezone | Y | |||
Timezone source | Y | Select one of the available records from the drop-down list if you need to specify a special timezone bond. The default value is the Indicator timezone. Available options:
|
Please keep in mind that if you create an inherited indicator for a parent table, and a usual indicator for a child table, indications will be created only for a child table. |
Also, when creating an inherited indicator for a parent table, please remember that the extended attributes from child tables will not be available there. See the brief illustration below:
On this picture, the table set is displayed:
Because attribute inheritance is going top-down, table attributes (such as fields) that extend parent tables will be inaccessible on the lower level. Please note that when configuring conditions of your indicator, make all critical attributes accessible on the top level.
Example 1
Company A uses schedule "24x7", which means 24 working hours, 7 days a week, and around-the-clock shift-work. If you enter "2" into the days field, this value is converted to 48 working hours or 2 working days. Nothing extraordinary.
Example 2
Company B uses "8x5" schedule , which means 8 working hours, 5 days a week, one of the most common working schedules. If you enter "2" into the days field, this value is converted to 48 hours (because there are 24 hours in a day), which gives 6 working days.
To specify the conditions you need to fill in the following tabs:
Field | Required | Description | |
---|---|---|---|
Start Conditions | Y | Establish conditions with the Condition Builder to get the Indicator started. The system uses the Table fields as transactional data to verify the conditions. When the transactional data changes, the system checks these conditions. E.g. for incidents, it is appropriate to use Impact as a condition field with one of the possible values – Low, Medium, High, Very High. The When to cancel setting allows to establish a condition to start cancellation by one of the options below:
| |
Cancel Conditions | Y | This option appears when the Cancel conditions are met option is selected in the When to cancel field. Define additional conditions to meet before the indicator cancels. If the system meets these cancel conditions, it ignores the start conditions. | |
Pause Conditions | N | Establish conditions with the Condition Builder to make the indicator pause. The system uses the Table fields as transactional data to verify the conditions. When the transactional data changes, the system checks these conditions. E.g., for incidents, it is appropriate to use Impact as a condition field with one of the possible values – Low, Medium, High, Very High. The When to resume setting allows to set a condition for pause resumption using one of the options below:
| |
Resume Conditions | Y | The field allows defining additional conditions to be met before the indicator has previously paused resumes. In other words, if the system meets these resume conditions, it ignores the pause conditions.
| |
Complete Conditions | Y | Establish conditions with the Condition Builder to make the Indicator stop. The system uses the Table fields as transactional data to verify the conditions. When the transactional data changes, the system checks these conditions. | |
Reset Conditions | N | Establish conditions with the Condition Builder to make the Indicator reset. The system uses the Table fields as transactional data to verify the conditions. When the transactional data changes, the system checks these conditions.
|
If an indication is not on pause when the reset conditions have been met:
If an indication is on pause when the reset conditions have been met:
|