OCE - Service Level Management

OCE (Objective Calculation Engine) is an optional itmSUITE® module that allows you to check Ticket processing time.

It allows to define Metrics and notifications for different Workflow.

The main parameters for each Objective are: a Metric , a target(expected time interval for a Ticket to reach Objective final Status) and a scope.

Action can be configured on each Objective to manage events (for example, notification messages to solicit the progress of a Ticket).

Finally SM - Service Managment module can be configured to visualize the elapsed time or missing time for Ticket related to Objective (through columns that can be placed in the Ticket View).

Objective management is available under General\Company\Objectives by default.

Objective logical structure

OCE logical structure

1. Objectives related to Agreements are automatically calculated based objectives scope (services and dates)
2. Each objective has 1 target only
3. Service Calendar, if applicable, wins over Objective Calendar
4. For aggregated objectives, when overlapping, the one with highest priority is used

Standard Objective definition

Field	Meaning	Comments
Type	Standard vs. Aggregate
Metric	Lead time for workflow (status A -> status B) Group lead time for workflow (status A -> status B) Difference between date fields Difference between numeric fields ||
Target	The target agreement for the objective
Calculation frequency	Delay in seconds between each calculation
Scope Filter	Attributes to define the set of tickets for which the objective is calculated
Scope Parameters	Selection of values for the metric
Scope Flow Properties	Definition of behaviour for workflow statuses (e.g. calculation suspension)	Frozen: when Ticket is in a Frozen status, the objective calculation is stopped. When Ticket exit from a Frozen status and enter in a not Frozen or Suspended: all the time passed on Frozen status is added. Suspended: when Ticket is in a Suspended status, the objective calculation is stopped. When Ticket exit from a Suspended status and enter in a not Frozen or Suspended: all the time passed on Suspended status is NOT added.
Events	Definition of events triggered in time (to be used for actions)
Colours	Definition of RAG colours for objective fields
Recording	Settings used to create snapshots of objective data to be used in trend analysis

Metric

Lead Time for workflow tickets

An Objective based on this Metric will store data about time required for a Ticket to pass from a Status T1 to Status T2 and it is compared with Target value.

Example:

To monitor the resolution time of an incident is possible to configure an Objective as follows:

1. T1: Opened state
2. T2: Complete state (note that T2 status is considered equivalent to a Frozen state)
3. Target (maximum time identified to bring the ticket to Completed state (T2)): 4 days
4. Calendar: defined at Company or Service level and includes 8 business hours per day (Monday to Friday)
5. Scope: All Incident Ticket opened on technical service "Database Management" with Medium Priority
6. Frozen States: Closed, Canceled (see below for a detailed definition of Frozen)
7. Suspended States: Suspend (see below for a detailed definition of Suspended)

Group lead time for workflow tickets

1. This metric allows to select one Group and, optionally, its subgroups.
2. This means that the metric is calculated as the Leadtime for workflow metric but in this case OCE will store data for each group / subgroup worked on Ticket and selected for an Obejctive with this Metric.

Working Calendars

TBC

Objective Scope

TBC

Events

TBC

Colors

TBC

Recording

TBC

Add an Objective column to a Forced View

TBC