Content deleted Content added
m Remove stub template(s). Page is start class or higher. Also check for and do General Fixes + Checkwiki fixes using AWB |
m replaced: one month → one-month using AWB |
||
Line 21:
In <ref name=":0" /> the authors define the SLO as "the quality of service aspect of the agreement. Syntactically, it is an assertion over the terms of the agreement as well as such qualities as date and time".
SLOs should generally be specified in terms of an achievement value or service level, a target measurement, a measurement period, and where and how measured. As an example, "90% of calls to the helpdesk should be answered in less than 20 seconds measured over a one
The use of the term ''SLO'' is deprecated in ITIL V3 to Service Level Target, not to be confused with [[service level requirement|Service Level Requirement]] defined in the [[service design]]. However the SLO term is found in various scientific papers, for instance in the reference architecture of the SLA@SOI project,<ref>Jens Happe, Wolfgang Theilmann, Andrew Edmonds, and Keven T. Kearney "A Reference Architecture for Multi-Level SLA Management" in "Service Level Agreements for Cloud Computing", eds. Wieder, Philipp and Butler, Joe M. and Theilmann, Wolfgang and Yahyapour, Ramin, Springer New York, 2011, DOI:10.1007/978-1-4614-1614-2_2</ref> and it is used in the Open Grid Forum document on WS-Agreement.<ref name=":0">Alain Andrieux, Karl Czajkowski, Asit Dan, Kate Keahey, Heiko Ludwig, Toshiyuki Nakata, Jim Pruyne, John Rofrano, Steve Tuecke, Ming Xu "Web Services Agreement Specification (WS-Agreement)", GFD-R-P.107, March 2007, Open Grid Forum.</ref>
| |||