SLA considering business hours
- SLA considering business hours
- Compute SLAs taking into account service coverage window and holidays
- SLA with Coverage Windows
- SLA, Coverage Windows, Ticket, Holidays
- itop-service-mgmt or itop-service-mgmt-provider, itop-sla-computation
This extension adds the capability to define Coverage Windows and Holidays in iTop and use them to compute Service Level Agreements (SLA) deadlines depending on the service and the coverage windows used in the customer contracts.
Compared to the 2.0.x version(s) this new version adds the support of an arbitrary number of open hours intervals per day.
By default, SLA computation assumes that a given duration does not depend on the time it starts (i.e. computations are based on a 24×7 service).
If you would like to compute SLA deadlines (TTO and TTR) depending on the customer/service and the times at which your support teams are working, then you will have to implement Coverage windows.
This extension allows you to define:
Coverage windows (i.e. open hours within each day of the week), possibly as several intervals with the day (i.e. integrate a lunch break)
Holidays (complete days which are closed for business, e.g. January 1st, May 1st…)
How the Coverage Windows and Holidays are related to each Ticket.
Once the Holidays and Coverage Windows are created in the system, the TTO and TTR deadlines are computed according to the corresponding coverage windows and exclude the holidays.
The conversion from previous format(s) of Coverage Windows is automatic, during the installation of the module.
|2.1.9||2017-03-28||Bug fix: Corruption of coverage windows when edited from a browser having a timezone different from the timezone of iTop|
|2.1.7||2016-03-15||Prevent overflow of an interval to the next day when dragging/dropping this interval in the calendar.|
|2.1.6||2015-09-30||Removed the “plus” button from the link Contract/Service, to workaround a bug in the coverage windows creation form (when shown as a dialog). Will be fixed later in the core of iTop. This regression has been introduced in the version 2.1.0 of the component and is related to the management of multiple time intervals.|
|2.1.5||2015-09-24||No change but a module version that is now consistent with our records (combodo-sla-computation: 2.1.5).|
|2.1.4||2015-06-30||Protects against “empty” days (i.e. days for which no interval exists) which generated a warning.|
|2.1.3||2014-12-18||Do not overwrite the value of 'coverage_oql' in the configuration file if the value was modified.|
|2.1.2||2014-12-09||Bug fix in the computation due to internal mismatches with timezones!|
|2.1.1||2014-12-01||Bug fix in the computation (1 min skipped from the end of intervals) and some cosmetics enhancements.|
|2.1.0||2014-11-26||Support of multiple open hours intervals per day.|
|2.0.1||2014-03-11||Integration of the German translation (thanks to ITOMIG GmbH)|
|2.0.0||2014-03-04||Offical release of the 2.0.0 version which requires iTop 2.0.2 or newer, but supports nice formatting (i.e. 19:45 instead of 19,75) for the times. If you need a version compatible with iTop 2.0.1 or older, use Coverage Window Sla Computation (legacy)|
Holidays are not taken into account if no coverage window has been defined (or if none applies to the ticket).
iTop 2.0.2 or newer.
Installation & upgrade
Download the package: and expand the content of the zip folder into the “extensions” directory of iTop.
If you have already installed iTop, make sure that the configuration file
conf/productionis NOT read-only.
Finally check the module “Plug-in SLA computation with coverage windows for UserRequest and Incidents” in the list of extensions at the end of the interactive wizard. Then complete the installation.
Once the new module has been installed, the default configuration states that:
The Coverage Window applicable to a Ticket is defined, for each Service, on the Customer Contract.
There is just one global list of Holidays. Any Holiday defined is applicable to any Ticket.
'combodo-sla-computation' => array ( 'coverage_oql' => 'SELECT CoverageWindow AS cw JOIN lnkCustomerContractToService AS l1 ON l1.coveragewindow_id = cw.id JOIN CustomerContract AS cc ON l1.customercontract_id = cc.id WHERE cc.org_id= :this->org_id AND l1.service_id = :this->service_id', 'holidays_oql' => 'SELECT Holiday', ),
You can adjust the configuration parameters if you want to use different rules.
|Parameter name||Description||Default Value|
|coverage_oql||The OQL to retrieve the Coverage Window object to apply to a given ticket. If the query returns several Coverage Window objects, only the first one will be used.||
|holidays_oql||The OQL to retrieve the Holiday objects to apply to a given ticket. All the Holidays returned by the query will be taken into account for the computation.||
:this->xxxrefer to the corresponding fields of the Ticket.
config-itop.phpwith the following value:
'deadline_format' => '$date$ ($difference$)',
This will display the deadline date and the delay from now to the dealine.
Managing Coverage Windows
The menu “Coverage windows” in the module “Service management” displays all coverage windows defined in iTop. If none has been defined click on “Create a new coverage window”, otherwise click on “Create” to create a new one.
The open hours for a given “Coverage Window” object are represented as a set of intervals, for each day of the week. The area outside of the blue intervals is considered as “Off hours”.
Click and drag over an empty area to create a new interval
Drag the handle at the bottom of an interval to adjust its duration
Drag the interval around to change its starting time
Click inside an interval to open a dialog box in order to edit the interval's properties
When clicking on an interval, the following dialog is displayed:
Click on “Remove Interval” to completely remove an interval from the coverage window.
The menu “Holidays” in the module “Service management” displays all holidays defined in iTop. If none has been defined click on “Create a new holiday”, otherwise click on “Create” to create a new one.
The Holiday Calendar allows you to group holidays (for example based on the country of your customers). This is a convenient way to simplify the queries required by a complex (multi-customer / multi-country) environment.
The OQL queries configured by default when installing the module do not use Holiday Calendars but Holidays.