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.
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:
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.
|2.0.2||2014-12-18||Do not overwrite the value of 'coverage_oql' in the configuration file if the value was modified.|
|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)|
Coverage Windows are defined as one single time frame per day (i.e. from 8h00 to 18h15). Defining a “lunch break” is not possible in this version of the extension.
Hollidays 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.
conf/productionis NOT read-only.
Once the new module has been installed, the default configuration states that:
'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.
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 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.