Accountable and Responsible

I was recently asked about the accountabilities and responsibilities of the Service Level Manager and Service Owner.

Let’s start with Service Level Manager.

Responsible for gathering Service Level Requirements from the customer.
Responsible for negotiating and maintaining SLAs with the customer.
Responsible for developing and maintaining OLAs.
Responsible for understanding underpinning contracts as they relate to OLAs and SLAs.
Responsible for producing, reviewing and evaluating reports on service performance and achievements on a regular basis. Also for conducting meeting with the customer to discuss service performance and improvements.
Responsible for initiating appropriate actions to improve service levels (SIP).
Conducting yearly reviews of SLAs, OLAs and underpinning contracts.

The success of SLM is very dependent on the quality of the Service Portfolio and the Service Catalogue and their contents. They provide the necessary information on the services to be managed within the SLM process.

Service owner:

Accountable for a specific service within an organization regardless of where the underpinning technology, components or processes reside.
Provide input for service attributes such as performance, availability, etc.
Represents the service to the entire organization.
Point of escalation for major incidents.
Represents service in Change Advisory Board meetings
Works with CSI Manager to identify and prioritize service improvements
Responsible for ensuring that the service entry in the Service Catalogue is accurate and maintained.

The ITIL Continual Service Improvement book pg 135/136 Table 6.8 shows the primary and secondary responsibilities for both the Service Level Manager and the Service Owner. This might be a good place for you start defining work flow for each role. In the same book on page 138 is a sample process flow for change management. You might apply this model to the two roles you have added to your organization. Additionally on page 139 Table 6.10 is a sample RACI Matrix.

Comments

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group . As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. Note: Goods may not always be provided for every Service Offe

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the

Search