DoIT Operational Framework - Section 2.0 - Glossary of Significant Terms
Section 2.0 of the Operational Framework for viewing and printing.
This portion of the Operational Framework aims to familiarize the
reader with definitions of key terms used throughout all the sections
of the Operational Framework. These definitions are influenced heavily
by the Information Technology Infrastructure Library Glossary version
- Change Management
- Configuration Item
- Configuration Management Database
- Emergency Change
- End User
- Event Management
- Expedited Change
- Incident Management
- IT Service
- Problem Management
- Root Cause
- Root Cause Analysis
- Service Catalog
- Service Outage
- Service Request
The of an is the person or group who defines and agrees to the .
A person who uses the on a day-to-day basis. are distinct from , as some do not use the directly.
A change of state that has significance for the management of an IT service or other configuration item. The term is also used to mean an alert or notification created by any IT service, configuration item or monitoring tool. Events typically require IT operations personnel to take actions, and often lead to incidents being logged.
The process responsible for managing events throughout their lifecycle. Event management is one of the main activities of IT operations.
Expedited changes are categorized as non‐emergency changes that must be
implemented in a time frame that does not allow them to go through the
normal approval cycle/timeframe (e.g., customer request, change directed
by management, vendors availability). For instance, a change may
require that an external vendor also be available when the change is
- Failure of one disk in a redundant array
- Failure of the only server supporting a service
The process responsible for managing the lifecycle of all incidents. Incident management ensures that normal service operation is restored as quickly as possible and the business impact is minimized.
Examples of IT Services supported by the UW-Madison Division of Information Technology (DoIT) include: the campus email service, the campus calendaring service, the DoIT Help Desk Walk-in service and the campus network.
A cause of one or more incidents. The cause is not usually known at the time a problem record is created, and the problem management process is responsible for further investigation.
The process responsible for managing the lifecycle of all problems. Problem management proactively prevents incidents from happening and minimizes the impact of incidents that cannot be prevented.
The underlying or original cause of a problem.
An activity that identifies the root cause of a problem. Root cause analysis typically concentrates on IT infrastructure failures.
A database or structured document with information about all live IT services, including those available for deployment. The service catalogue is part of the service portfolio and contains information about two types of IT service: customer-facing services that are visible to the business; and supporting services required by the service provider to deliver customer-facing services.
Any event in which any of the following criteria are or will be met will constitute an IT Service Outage for a DoIT managed/monitored IT Service:
- The IT Service is unavailable to its customers or a subset of its customers.
- The IT Service is unable to function as designed and installed.
- IT Service performance has degraded to a degree to render the resource unusable.
- Multiple users' work may be lost.
A formal request from a user for something to be provided – for example, a request for information or advice; to reset a password; or to install a workstation for a new user. Service requests are managed by the request fulfilment process, usually in conjunction with the service desk. Service requests may be linked to a request for change as part of fulfilling the request.
Time periods used to track non-IT impacts or activities on IT Services. Examples include Housing Move In/Out, Campus Events (Enrollment Periods, Breaks, Final Exam Periods, etc).
- DoIT Operational Framework - Section 1.0 - Overview
- DoIT Operational Framework - Section 3.0 - Change Management
- DoIT Operational Framework - Section 4.0 - Incident Management
- DoIT Operational Framework - Section 5.0 - Configuration Management
- DoIT Operational Framework – Section 6.0 - Event Management
- Working with the Operational Framework (Policy)
- The DoIT Operational Framework, ITIL & Service Management Contacts at DoIT