Skip to main content

The Evolution of a Definition

The definition of an IT service has certainly evolved:

IT Service (ITILv1):    A set of related functions provided by IT systems in support of one or more business areas, which in turn may be made up of software, hardware and communications facilities, perceived by the customer as a coherent and self-contained entity. An IT service may range from access to a single application, such as a general ledger system, to a complex set of facilities including many applications, as well as office automation, which might be spread across a number of hardware and software platforms.

IT Service (ITILv2):    A set of related components provided in support of one or more business processes. The service will comprise a range of Configuration Item (CI) types but will be perceived by Customers and Users as a self-contained, single, coherent entity.

IT Service (ITILv3):  A Service provided to one or more Customers, by an IT Service Provider. An IT Service is based on the use of Information Technology and supports the Customer's Business Process. An IT Service is made up from a combination of people, processes and technology and should be defined in a Service Level Agreement.

Service: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks.  The term service is sometimes used as a synonym for core service, IT service, or service package.

In ITIL v3 an outcome based definition of services moves the IT organization beyond just alignment to the business but to actual integration.  In today’s world there are few business strategies, activities or tasks that do not include some underlying IT component in the form of a service. These services should enable desired outcomes by enhancing the performance of associated tasks and reducing the effects of constraints.  While some services enhance performance of tasks, some may actually perform the task itself reducing the need for expensive human intervention. 


Over the years the definition has changed to incorporate a more business/customer focus in defining what an IT service is.   Ultimately we must deliver services that always have at least three underlying factors, Utility (fit for purpose) does it do what the user needs, Warranty (fit for use) is it available when demanded with enough capacity, security and continuity to insure agreed levels of performance and without which our services could not deliver Value to our customers.

Comments

Rob La said…
Great thoughts on the evolution of the definition Professor. I know that this topic generates a lot of passion on my team and I might borrow these concepts to shed light on the topic.

The concept of Value in Services intrigues me. I know about gathering requirements for Utility and Warranty, but how do you suggest we approach measuring value?

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…