Skip to main content

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 than 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 Offering.
Example of no goods in offering - When a consumer is using a cloud-based service using their own technology vs. technology provided by the service provider.

Access to Resources – This is very different from “Goods”.   With this element of a Service Offering the ownership is not transferred to the consumer.  Access and usage is granted or licensed under agreed terms or conditions.

Example of Access to Resources:  If we use the hotel service as an example, let’s say that a robe is provided.  It is typically provided for you to use as a part of the service offering.  You use it and leave it there when you leave. This is “Access to Resources”.  

Example of Goods: If you take that very same robe with you, you will be charged according to agreed terms or conditions and then this is considered ownership of Goods!

Service Actions –Are Performed by the provider to address a consumer need and are performed according to agreements with the customer.
Example of Service Actions in our hotel service might be the processing of your bill or customer support at the front desk.

Simply put, Service Offerings are a way for providers to offer options to consumers.  Organizations need to thoroughly understand which components, and elements of Goods, Access to Resources and Service Actions are and then be able to tailor them to suit their target consumer groups!

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 policies (r…

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 the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…