An indicator is a rule of a time counter activation that is specified by proper conditions for starting, pausing, resetting and , and stopping this counter. It also determines a the time limit for declaring SLA as breached and contains and contains time conditions of a Commitment commitment type implementation.
For example, based on your SLA agreement,you can create separate SLA separate SLA indicators for incidents that are having an impact from "Low" to " to Very High" and set a separate "separate Breach Time" value for them, based on your SLA agreement.
When an indicator starts, the system automatically generates an Indication, which is a time 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:
- standard – indicator creates indications that start or complete when specified conditions are met, or the duration ends.
For example, the start time is when the task state changes to Assigned. - retrospective – indicator creates indications that count time based on the Date/Time column defined manually. Indications are created for records meeting specified conditions. To use this type of indicator, select the Defined by field option in the Indication start time and specify the field you need.
For example, the start time is the value of the Opened at field, and the indication is created when the task state changes to Assigned.
| Tip |
|---|
Role required: service_level_manager. |
Creating Indicator
To add a new Indicatornew indicator, please complete the following steps below:
- Navigate to the to Service Level Management → Indicator menu.
- Click New Click New and fill in the form.
- Click Save or Click Save or Save and Exit to to apply changes.
The Indicator form fields
Field | Required | Description |
|---|
| Name | Y |
An Specify the indicator name. |
Please do similar same name to indicators when creating them |
|
against for the same table; otherwise, they will not work |
|
incorrectly correctly if edited or deleted later. |
|
| Agreement | N | Specify |
an related | related to this indicator containing tracking metrics. |
| Commitment |
Type a the commitment type for this indicator. Available options: |
- - – the time it takes to resolve the issue (generally,
|
this is the is created - creation to its state changed to Completed).
- Response Time
|
- the - – the time it takes to process the issue in a non-automated
|
- this is is created - creation to its state changed
|
to dictionary to table to apply the Indicator conditions. | Note |
|---|
After saving the form, the Table field becomes read-only. This is done: - to ensure the performance of
|
|
the Indicator.- indications for which start or breach time is specified by the appropriate field.
- to keep the logical consistency and the correct indicator's work.
|
|
| Inheritance | N | Select this checkbox if you are creating an indicator |
on for a parent table, and it is necessary to use it |
against of the The table considered thought of as a parent table, and |
|
every extending it is a single service request. |
|
Turning By enabling this attribute |
|
on a single on for a parent table which will affect every child table created. |
|
| Active | N | Select this checkbox |
on | to make the indicator active or inactive. |
Indication start time | Anchor |
|---|
| indication start time |
|---|
| indication start time |
|---|
|
| N | Select one of two options: - Defined by condition – for standard indications. The standard indication start time is when a record meets the conditions defined in the Start Conditions tab.
- Defined by field – for retrospective indications. Retrospective indication start time is based on the value retrieved from the Date/Time column specified in the Start time field. The record must also meet the conditions defined in the Start Conditions tab. Unlike the standard indication, the time when the conditions were met is ignored.
|
| 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. | Info |
|---|
The field appears if the Defined by field option is selected in the Indication start time field. |
| Note |
|---|
| Note that a retrospective indication counts the value relevant at the time of indicator creation. If the value changes, indications will not be recalculated. |
|
| Indication breach time | N | Select one of two options: - Defined by duration – the indication breach time is based on the Duration value. The timing of the SLA breach also takes into account pause durations.
- Defined by field – the breach time indication is based on the value retrieved from the Date/Time column specified in the Breach time field.
| Note |
|---|
After saving the form, the Indication breach time field becomes read-only. |
|
| 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. | Info |
|---|
The field appears if the Defined by field option is selected in the Indication breach time field. |
| Note |
|---|
- If the value of the referenced field is less than Start Time or Minimum duration, no indication will be created.
- If the value of the referenced field changes, the value in the related Indication record will be changed, and related fields will be recalculated.
- If the value of the referenced field changes, and it is less than Start Time or less than Minimum duration, the indication will be canceled.
|
|
| Business duration | Y | Set up a business time measure for the SLA |
runs marked as Breached.| Note |
|---|
marked as Breached. | Info |
|---|
The field changes to Minimum duration if the Defined by field option is selected in the Indication breach time field. |
| Note |
|---|
Note that all day duration (not just business hours) according to the chosen schedule is taken into account. See the calculation samples below this table. |
|
| 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. | Info |
|---|
The Minimum duration field appears if the Defined by field option is selected in the Indication breach time field. |
| Note |
|---|
Please note that all day duration (not |
|
only according according to the chosen schedule is taken into account. See the calculation samples below this table. |
|
| Schedule | Y |
A Select a working schedule |
selected from the list. It determines the working hours that the system uses when calculating |
an the implementation implementation under certain conditions. To configure this timeline, use |
the featuresDetermines indicator timezone timezones are available to choose from. |
|
| Timezone |
Source| 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 |
's timezone. Available options: |
Caller's CI 's IndicatorTask 's
| Note |
|---|
| title | Indicator inheritance |
|---|
|
Please keep in mind that if you create an inherited indicator on for a parent table, and after that a separate usual indicator on for a child table, the indications are to will be created only for a child table. |
Also, when creating an inherited indicator against for a parent table, please keep in mind 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:
- The parent table, attribute set is XX
- The child table 1, attribute set is XXYYY
- The child table 2, attribute set is XXYYYZZ
Considering the fact that the Because attribute inheritance is going top-down, the table attributes (such as fields) that extend parent table 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.
Duration calculations
Example 1.
Company A uses schedule "24x7", which means 24 working hours, 7 days a week, and around-the-clock shift-working, as an example. In this case, if 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 schedule "8x5" schedule , which means 8 working hours, 5 days a week, one of the most common working schedules. In this case, if 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.
Specifying indicator conditions
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 make get the Indicator startstarted. 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 setting allows to establish a condition for to start cancellation by one of the options below: - Start conditions are not met
- – the system ignores the start conditions if it
- Do not cancel– start conditions are always verified.
|
| Cancel Conditions | Y | This option appears when the Cancel conditions are met option is selected in the When to cancel field. It allows defining Define additional conditions to meet before the indicator cancels. In other words, if 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 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 setting allows to set a condition for pause resumption by using one of the options below: - Pause conditions are not met
- – the system ignores the pause conditions if it
|
| Resume Conditions | Y | This option appears when the Resume conditions are met is selected in the When to resume field. It 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. | Info |
|---|
This option appears when the Resume conditions are met option is selected in the When to resume field. |
|
| 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. | Info |
|---|
This field is unavailable for retrospective indications (the Defined by field option selected in the Indication start time field). |
|
| Note |
|---|
If an indication was is not on pause when the reset condition has conditions have been met: - Pause time and its duration are reset.
- Start time is set to the reset condition trigger timetime reset conditions are triggered.
- The breach time and original breach time is are recalculated.
- All specifications are recalculated against according to the values defined.
If an indication was is on pause when the reset condition has conditions have been met: - Pause time are reset.
- Start time and pause time is are set to the reset condition trigger timetime the reset conditions are triggered.
- The breach time and original breach time is are recalculated.
- All specifications are recalculated against according to the values defined.
|