Skip to main content

ITIL Practitioner - Components of a Service

At the core of ITSM is the idea of delivering services to customers, how these services will be engaged to deliver some form of value to the customer and the customer’s organization, and the value captured by the service provider.  For this to be accomplished we must first understand the key elements of an IT service and how, as a service provider, we deliver the correct set of services effectively and efficiently. 

 “A service is a means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks”.  This allows the customer to create the desired business outcome without having to invest in specialized tools or skills.  By linking activities performed by the service provider to the desired business outcomes the provider can be seen as contributing value, not just as a cost to the business.

The value of a service is derived from what it enables someone to accomplish or what outcomes it enables them to realize.  The service provider must have a clear understanding of the types and levels of service that will make its customers successful and then be able to organize themselves in a way which allow the optimal delivery and support of those services by defining a consistent and repeatable approach to developing, delivering and supporting services throughout their entire lifecycle.

Cost is the amount of money spent on a specific activity, IT service or business unit.  Costs consist of real costs (money) and notional cost (time) and depreciation.  Risk is uncertainty of outcome.  It may be an event that could possibly cause harm, loss or impact negatively the ability to deliver desired outcomes.  Customers will be concerned with costs and the reliability of the services delivered to them.  However they will not need to know in detail every expenditure item or risk mitigation measure engaged by the service provider.

A successful relationship between the customer and the service provider ensures that the customer receives a service that delivers the correct levels of utility and warranty for the right price and that the service provider is able to achieve this balance and communicate it in a way that would allow the customer to make changes to this balance in a way that will meet their changing requirements.

For more information please see https://www.itsmacademy.com/itil-practitioner/
 



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