become-itil-foundation-certified-abhinav-kaiser(www.ebook-dl.com)
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 5 ■ Service Design<br />
To state a few examples of SLRs, the customer might ask for critical incidents to be<br />
resolved within the hour, might ask for changes to the systems be implemented within a<br />
day, and might ask for 100% availability of Internet service. Not all SLRs are feasible, even<br />
by the top service providers. In fact, the cost of services tends to go up exponentially as<br />
the service-level requirements hit the high percentage. So, the art of negotiation is to find<br />
the balance between the service levels and the cost of providing services.<br />
Then there are some SLRs which are impossible to match, even by the best of service<br />
providers, perhaps implementing system changes within a day. Not all changes may be<br />
feasible given the timeline, as changes need to be developed, tested, and then deployed.<br />
It takes a lot of planning, coordinating, risk measures, and countermeasures. If the service<br />
provider signs off on an SLR stating that all changes would be implemented within a day,<br />
he would be setting himself up for a grand failure.<br />
Ideally SLRs are captured in the service strategy phase by the service portfolio and<br />
business relationship management processes. But, this is at a high level. Specifics are<br />
not discussed until the agreements are charted. When the contracts are set in stone, the<br />
ball passes to the service-level management to obtain specific requirements from the<br />
customer, who then translates them into workable SLAs.<br />
When SLRs have been determined, the next activity is to <strong>com</strong>e up with servicelevel<br />
targets (SLT). SLTs are hard to <strong>com</strong>e up with in the first instance. Generally, initial<br />
SLTs are defined, and over a period of time, they are refined and finalized. SLTs are a<br />
<strong>com</strong>mitment made by the service provider against an aspect of a service. Examples of<br />
SLTs might be:<br />
• More than 95% of the incidents will be resolved within 8 hours<br />
• Configuration management database (CMDB) will be greater<br />
than 99.5% accurate<br />
When SLTs are agreed to, they go into the SLA document. SLAs are finalized, signed<br />
off on, and then make their way into an addendum to the business contract. I will explain<br />
this process in detail in the next section.<br />
5.7.1.3 SLA Frameworks<br />
SLAs can be drafted in a number of ways. The two most popular types in vogue are<br />
service-based and customer-based SLAs. Figure 5-4 illustrates the service- and<br />
customer-based SLAs.<br />
74