Body
Overview
The Information Technology Infrastructure Library (ITIL) provides definitions for the different classifications of events. This article discusses how we leverage the standard ITIL and classifications work within the TeamDynamix system at RPI.
The most common classification is Service Request. Service Requests are tied to our shared Service Catalog and should be represented there with clear information about who the service is for, how it is requested, and what the customer or user can expect.
The second most common classification is Incident.
Classification Definitions
Incident – An unplanned interruption to a service or a reduction in the quality of a service.
Examples include: Unexpected inability to login/authenticate. Error message when attempting to use standard application or service. Website inaccessible or unresponsive.
Major Incident – An event which significantly affects a business or organization, and which demands a response beyond the routine incident management process. A major incident is an incident that is either defined in the major incident procedure or which:
- Affects, or has the potential to affect services or systems that are critical to the business
- Has a significant effect on the reputation, legal compliance, regulation or security of the business/organization.
Examples include: Banner is down. OSCAR is down. Campus network or Internet access are down.
Problem – The cause of one or more incidents. The cause is not usually known when a problem record is created, and the problem management process is responsible for further investigation.
Examples include: Server or network crashes unexpectedly. Restarting service resolves immediate incidents but root cause analysis is necessary to mitigate future issues.
Change – the addition, modification or removal of anything that could affect services. This includes all services, configuration items, processes, documentation, etc.
Examples include: Security patching that may impact expected availability or functionality of a service. Customization request that may impact functionality of service. Change to a business process that may impact expectations.
Release – A collection of hardware or software documentation, processes or other components required to implement one or more approved changes to services. The contents of each release are managed, tested, and deployed as a single entity.
Examples include: Documentation and notification to support a timed change to a service.
Service Request – A request from a user for information, advice, a standard change or access to a service. For example, to reset a password, or to provide standard services for a new user. Service requests are usually handled by a service desk or other service area.
Examples include: Requests for access or software. Requests for approval. Request for a new laptop. Request for consultation on a topic. Request for help with a website.
Use Cases
Let’s look at a hypothetical use case that covers most of these definitions:
There are fifty reports (incidents) of WiFi being interrupted. Those incidents are then rolled up into a single problem ticket that concluded the root cause is lack of suitable WiFi infrastructure. A change ticket could then be opened and the WiFi infrastructure can be changed or upgraded to be more resilient and reliable. A release ticket could then be created, and the institution could release new documentation and justification for the upgrade in WiFi infrastructure. The institution could release the news that the new WiFi infrastructure should be more consistent, and that there is no cause for concern.
A Note on Projects
As of this time, we have not yet implemented the TeamDynamix PPM or Project Portfolio Management, tool. When this is available, it is also possible to convert an incident to a project, project task or project request. This may be relevant when/if it is determined that the scope of the resolution is large enough to be managed as a project.