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

with the procurement team to create a purchase order. This coordination between<br />

various parties requires a good amount of effort. Instead, I automate the process; I don’t<br />

skip any steps, but I remove the coordination efforts using the power of automation. I<br />

would design the tool to seek the manager’s approval when the request is raised. After the<br />

manager’s approval, I route the ticket directly to the procurement team. In this example,<br />

I have taken out the mid<strong>dl</strong>eman. This translates to more efficient and cost-effective<br />

service.)<br />

5.7.1.8 SLM vs. BRM<br />

The SLM works with ears to the ground and is tasked with dealing with all issues<br />

pertaining to service quality. The BRM, on the other hand, works closely with the<br />

business and is aligned to the customer’s current and future requirements. BRM also acts<br />

as a conduit for the customer to share their feedback.<br />

The BRM and the SLM processes are similar in principle, but they differ in the<br />

out<strong>com</strong>es they are trying to achieve. The BRM works at a strategic level (as discussed in<br />

Chapter 4). It works with customers to understand the pains, requirements, and desires<br />

to formulate and tailor IT services to their needs. On the other hand, the SLM process<br />

works with the customer during and after the IT service delivery stage. It works with the<br />

customer in ensuring that the service levels are met and making sure pain points and<br />

other runway-level issues are han<strong>dl</strong>ed.<br />

The BRM process works at the strategic level and at times at the tactical level. The<br />

SLM process works at the operational level and at times at the tactical level. Although<br />

at a tactical level, both BRM and SLM are involved, there is no overlap between their<br />

responsibilities as laid out in the process.<br />

The BRM is required to act as the big brother as strategy feeds into tactics and operations.<br />

The SLM must work within the ambit of the services and can take support from the BRM to<br />

align with the strategy. Likewise, BRM needs to interface with the SLM quite stably as the<br />

operations on the ground are the basis for all discussions with existing customers.<br />

5.7.1.9 SLM Interfaces<br />

As the SLM process deals with measuring and reporting service levels, in principle it must<br />

interface with every ITIL process. This is in fact true for all processes. None of them can<br />

work in isolation. They require at least one or multiple process to provide triggers, inputs,<br />

and feedback on output. In the case of SLM, the following sections discuss some of the<br />

critical interfaces.<br />

5.7.1.9.1 Business Relationship Management<br />

As discussed earlier, there are differences in interfacing between the SLM and the BRM.<br />

5.7.1.9.2 Service Catalog Management<br />

The SLM interfaces with the service catalog management for obtaining service<br />

information and associated service levels from the service catalog.<br />

80

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

Saved successfully!

Ooh no, something went wrong!