• Enterprise Technology
  • ET Staff Intranet
  • IT@UT
  • Alerts and Outages Page
  • Critical Service Availability
  • IT Maintenance Calendar
  • IT Updates
  • Information Security Office
  • ServiceNow
  • Contact Us
  • Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
UT Shield
Information Technology Services at the University of Texas at Austin
  • About Us
  • ITSM Processes
    • IT Service Catalog Management
    • Incident Management
    • Change Management
    • Knowledge Management
    • Glossary
  • Training
  • Newsletter
  • Contact Us

Glossary

Terms & Definitions

AccountableThe group or individual that is personally answerable for an activity. Accountability cannot be delegated, unlike responsibility.
Blackout WindowA scheduled period of time in which changes that may affect critical academic or IT services should be avoided. Only pre-approved, standard, or emergency changes required to resolve production issues should be made during this period.
Business CriticalityThe importance of this service to the business.
Business ServiceA service that is delivered to business customers by business units. For example, the Business Service of Email can have multiple Service Offerings, including Office 365, UT Mail, and UT Lists.
Catalog ItemA form used to submit information, a request, or to create a task.
CategoryA logical group of services that benefit from being managed together.
ChangeThe addition, modification, or removal of anything that could affect an IT service.
Change ApproverThe role that 1) reviews and authorizes RFCs submitted by their team and 2) ensures that Post Implementation Review (PIR) reports, action items, and lessons learned are reviewed and approved at the appropriate level following an unsuccessful change and 3) is typically fulfilled by the Service Owner.
Change CalendarThe official schedule of all authorized ET changes, Maintenance Windows, Reserved Maintenance Windows, and Blackout Windows.
Change RequesterThe role that submits an RFC.
Change ReviewerThe role that reviews an RFC to verify that it is complete and technically sound.
Composite Customer ExperienceA metric based on a questionnaire designed to capture customers’ thoughts and feelings about ET services.
Configuration ItemAny component or other service asset that needs to be managed in order to deliver an IT service.
ConsultedThe group or individual that is given the opportunity to contribute to and make recommendations on an action or document.
Critical Infrastructure ServiceA service that other services are dependent on in order to support the business and academic efforts of the university. Only these services may be granted a Reserved Maintenance Window for their changes when appropriate.
CustomerThe consumer or end-user of an IT service.
ImpactThe scope of an incident, problem, or change on business processes. Impact is often based on how service levels will be affected.
IncidentAn unplanned interruption to an IT service or reduction in the quality of an IT service. Failure of a configuration item that has not yet affected service is also an incident.
InformedThe group or individual that is advised of a change or a decision.
Key Performance IndicatorA metric that is used to help manage an IT service, process, plan, project, or other activity. Key performance indicators are used to measure the achievement of critical success factors and should be selected to ensure that efficiency, effectiveness, and cost-effectiveness are all managed.
Maintenance WindowA scheduled period, preferably recurring, in which changes can be implemented.
Major IncidentThe highest category of impact for an incident. A major incident results in significant disruption to the business.
Post Implementation ReviewA review that takes place after a unsuccessful change that identifies, in a written report, the root cause, contributing factors, and opportunities for improvement.
Post Incident ReviewA review that takes place after a major incident to identify, in a written report, the root cause, contributing factors, and opportunities for improvement.
PriorityA category used to identify the relative importance of an incident, problem, or change. Priority is based on impact and urgency and is used to identify minimum required times for actions to be taken.
ProblemA 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.
Process OwnerThe role that has end-to-end responsibility for process definition, documentation, and performance.
RequesterThe role that submits a service request. Requestors may be anyone in the organization. Requesters may submit service requests on behalf of others. 
Reserved Maintenance WindowA Maintenance Window for a Critical Infrastructure Service that should be prioritized over other Maintenance Windows.
ResponsibleThe group or individual who has the authority and is expected to deliver a task or activity; responsibility can be delegated.
Risk Assessment ValueA value that represents the expected risk and impact a proposed change may have on the IT service. 
ServiceAn end-to-end IT service that delivers value to customers, typically not identified by specific product or application names. The service combines people, processes, and technology to provide outputs or results that enable business capabilities or a customer’s work activities and desired outcomes.
Service Level AgreementAn agreement between an IT service provider and a customer. A service level agreement describes the IT service, documents service level targets, and specifies the responsibilities of the IT service provider and the customer. A single agreement may cover multiple IT services or multiple customers.
Service Level ObjectiveThe SLO is a key element between a service provider and a customer. SLOs are agreed as a means of measuring the performance of the service provider and are outlined as a way of communicating mutual understanding between the service provider and customer.
Service OfferingThe specific technology-focused activity or product used to deliver a service. These can be software bundles, custom application solutions, or other technology that enables a service offering. Multiple service offerings might exist for a single service.
Service OwnerThe functional manager of an IT service or suite of IT services who is empowered to make Incident Management decisions for the services for which they are responsible. 
Service RequestA formal request from a customer for something to be provided.
StakeholderA person who has a technical, business, or institutionally-related interest in an organization, project, or IT service.
Unsuccessful ChangeA change that either significantly deviated from the implementation plan, caused an incident, or did not achieve the desired outcome. For example, change backed out, change not made when scheduled, human error, exceeded maintenance window, or change incomplete.
UrgencyThe actual or potential degree to which a user’s ability to do their work has been affected by an incident.
UserA person who uses the IT service on a day-to-day basis.

Acronyms

CCEComposite Customer Experience
CABChange Advisory Board
CIConfiguration Item
CMDBConfiguration Management Database
CSIContinual Service Improvement
ITILInformation Technology Infrastructure Library
ITSMIT Service Management
KBKnowledgebase
KPIKey Performance Indicator
MIMajor Incident
SLAService Level Agreement
SLOService Level Objective
RAVRisk Assessment Value
RFCRequest for Change
VTBVisual Task Board

Primary Sidebar

IT Resources

  • Enterprise Technology
  • ET Staff Intranet
  • IT@UT
  • Alerts and Outages Page
  • Critical Service Availability
  • IT Maintenance Calendar
  • IT Updates
  • Information Security Office
  • ServiceNow
  • Contact Us

Footer

  • IT@UT
  • Information Security Office (ISO)
  • Enterprise Technology
  • ET Staff Intranet

UT Home | Emergency Information | Site Policies | Web Accessibility | Web Privacy | Adobe Reader

© The University of Texas at Austin 2025