Skip to main content

Constructs of a “Service Relationship” – ITIL 4

Generally, when we think of “relationships” we immediately think of the people aspect. In ITSM we are referring to the relationships between third-party vendors, suppliers, customers, and many other stakeholders necessary to deliver the optimum service. It is mandatory to be able to manage those relationships at the appropriate level. One way to understand the “organization and people” involved in those relationships is to understand the constructs of a “Service Relationship”

ITIL provides us this model. 
Starting from the bottom of the diagram and moving up, let's discuss the critical elements of a Service Relationship: 

Resources – All resources including people, process, and technology. In ITIL terms that includes resources from all Four Dimensions:
  • People and Organizations 
  • Information and Technology
  • Partners and Suppliers 
  • Value Streams and Processes 
Products – A configuration of resources provided by the service provider that are potentially valuable to their customers. 

Service Offerings - Simply put, service offerings are a way that providers can offer options to consumers. 

An example that we can relate to is a banking service offering. Products might include checking and savings accounts that come with a debit card and access to ATMS and online banking service. A consumer typically can avoid fees by using their bank’s ATMs, or by also having a savings account or using direct deposit. These offerings are designed to address the cost and risk profiles of their various target consumer groups. Products are typically complex and are not fully visible to the consumer. The portion of a product that the consumer sees does not always represent all of the components that comprise the product and support its delivery. Organizations define which product components their consumers see and tailor them to suit their target consumer groups.

Learn more about how to accelerate and optimize your services and receive your ITIL 4 certifications.

Comments

Popular posts from this blog

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

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service". I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize: SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle. ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with