15.08.2018 Views

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 />

a day-to-day basis. Other examples include broadband Internet data usage, minutes on<br />

your mobile phone, and bandwidth usage of your web sites.<br />

This subprocesses also keeps an eye on the performance of capacities and its related<br />

SLAs as agreed to with the customer. On an agreed term, service capacities are measured<br />

and reported back to the service-level management process and to the customer. It also<br />

aids business capacity management in predicting future capacity requirements.<br />

5.7.6.2.3 Component Capacity Management<br />

The innermost layer in capacity management is the <strong>com</strong>ponent capacity management. It<br />

deals with the capacities of individual <strong>com</strong>ponents that make up the service. It deals with<br />

the management of the individual <strong>com</strong>ponents and places control mechanisms around it.<br />

Just as in services, automated thresholds are placed to ensure there is a warning<br />

before the storm. Examples could include the warning message from a storage server<br />

when it reaches 80% disk capacity. Let’s say that the storage management group ignores<br />

it, and when it reaches 90%, it sends out an exception alert. Still no response at 95%, so<br />

it triggers an incident, which will force the teams to act on it at the earliest. This is the<br />

reactive phase that I was referring to earlier. This is the reality today. Teams don’t gear up<br />

before the storm, but rather take corrective measures when the storm is about to hit.<br />

5.7.7 IT Service Continuity Management<br />

IT is the lifeline for all of us today, and living without it is unthinkable. Whether we deal<br />

with <strong>com</strong>municating with people, medical operations and scans, entertainment, or even<br />

the day-to-day work we perform, in one form or another, they are all connected somehow<br />

to IT. So it is imperative that IT services provide some kind of insurance, which does not<br />

deal with penalties and <strong>com</strong>pensation, but rather a ring of resilience outside the normal<br />

resilience discussed in the availability management process.<br />

IT services <strong>com</strong>e in all shapes and sizes, mainly from the criticality perspective.<br />

Not all IT services are equally critical. IT service continuity management (ITSCM) is<br />

expensive, so it mainly covers critical services. For example, a customer dealing with a<br />

call center leverages on telephony and Internet from a service provider. For his business,<br />

telephony would be a critical IT service considering he is in the business of making and<br />

receiving calls. For another customer who is in the business of content writing for blogs,<br />

Internet would be a critical IT service, but telephony would not be critical. So, how does<br />

the service provider decide which IT services to take into the ring of an additional layer of<br />

resilience and which ones to leave out?<br />

It’s simple really. The service provider doesn’t have to make that choice. It asks the<br />

customer to pick out critical services, and the customer would be firmed up with the IT<br />

service continuity process. I will discuss the entire process in the next section.<br />

So what exactly is this resilience that I am talking about, you might ask?<br />

Suppose a customer obtains e-mail service from a service provider. The servers<br />

hosting the e-mail IT infrastructure, database, and applications are in a single data center<br />

in one part of the city. Let’s say that this part of the city gets flooded, or gets hit by a riot<br />

or earthquake, and the data center as a result <strong>be<strong>com</strong>e</strong>s inaccessible or powered down.<br />

The business still has to continue. And without e-mails, as the critical service for this<br />

103

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!