Sign up free

Glossary

IT service management terms, explained in plain English — no jargon, no assumed knowledge. Each definition is one or two sentences, and where a calculator, template or guide helps, it is linked.

A

Asset register

A list of the IT assets an organisation owns — hardware, software and services — with who owns each one and where it lives. It is the starting point for asset management: you cannot manage what you have not listed.

Availability

The share of time a service is working and usable, usually given as a percentage. Availability depends on two things: how often the service fails, and how fast it is fixed when it does.

Convert availability in nines →

B

Breach (SLA)

A failure to meet a target in a service level agreement — for example, an incident that took longer to resolve than the agreement allows. A breach is usually recorded, reported, and may carry a remedy agreed in advance.

Business hours

The hours a service is covered by support, as agreed in the SLA — for example, weekdays 9 to 5. Response targets usually only count inside business hours, which is why the hours themselves are part of the agreement.

C

Change

Any addition, modification or removal of something that could affect an IT service. Changes range from a security patch to a new server, and the larger the impact, the more assessment and approval the change should get.

Use the change request template →

CMDB

A configuration management database: a record of the IT assets in an organisation and how they relate to each other — which servers run which services, and what depends on what. Its value shows up during incidents, when it answers which services are affected.

Read what a CMDB is →

D

Downtime

Time when a service is unavailable to the people who rely on it. Downtime is measured in minutes and hours, and its cost — lost revenue, wages and recovery — is what makes the case for preventing the next outage.

Estimate downtime cost →

H

Help desk

The single point of contact where users report problems and request help, usually for day-to-day IT issues. A help desk is often the front door to the wider service desk: it takes the call, logs the ticket and resolves what it can.

I

Incident

An unplanned interruption to a service, or a reduction in its quality. A server down is an incident; a request for a new laptop is not — that is a service request, and mixing the two up makes incident numbers meaningless.

Read the incident management process →

ITIL

A published framework of practices for IT service management, currently in version 4. ITIL gives teams a shared vocabulary — incident, problem, change, service request — and guidance on each practice, but it is a guide to use, not a rulebook to follow word for word.

Read ITIL 4 explained →

ITSM

IT service management: the way an organisation designs, delivers and improves the IT services its people rely on. It covers the help desk, incident handling, change control, problem management and the agreements that set expectations for each service.

Read what ITSM is →

K

Knowledge base

A collection of answers, guides and known fixes that users and agents can search. A good knowledge base turns solved problems into answers the next person can find without opening a ticket.

M

MTBF

Mean time between failures: total operating time divided by the number of failures, over the same period. It measures reliability — how long something runs before it breaks — and a shrinking MTBF is the signal to replace or fix the cause.

Calculate MTBF →

MTTA

Mean time to acknowledge: the average time between an incident being detected and someone acknowledging it. It measures the first response, not the fix — and it matters because an acknowledged incident is one someone owns.

MTTD

Mean time to detect: the average time between something breaking and the team knowing about it. Long detection times usually mean the monitoring is missing, not that the team is slow.

MTTR

Mean time to resolve: total downtime divided by the number of incidents, over the same period. It measures recovery speed — when something breaks, how fast do we fix it — and it is the number most teams watch first.

Calculate MTTR →

O

Outage

A period when a service is completely unavailable. An outage is an incident, but not every incident is an outage: a service can be degraded — slow, or partly working — without being fully down.

P

Priority (P1–P5)

A ranking of how urgently an incident needs attention, usually from P1 (most urgent) to P5 (least). Priority comes from urgency and impact together: a P1 is an outage affecting many people, not simply a request from an important person.

Set priority with the matrix →

Problem

The underlying cause of one or more incidents. Ten separate incidents with one cause are one problem, and fixing the incidents without fixing the problem means the incidents keep coming back.

Use the root cause template →

R

RACI

A way of recording who does what: who is Responsible for doing the work, who is Accountable for the result, who is Consulted, and who is Informed. A RACI matrix ends the argument about who owns a service or a decision.

Root cause analysis

A structured way of finding the underlying cause of an incident, usually by asking why repeatedly and following the evidence at each step. The first answer is usually a symptom; the cause sits further down, where the fix is cheaper and lasts longer.

Use the root cause template →

S

Service desk

The team and the function that manages IT services for users: incidents, service requests, and communication while things are being fixed. A service desk is broader than a help desk — it owns the service experience, not just the individual ticket.

Service request

A request for something the user needs — a new laptop, access to a system, a software install. It is planned work, not an interruption, which is why it is handled separately from incidents.

SLA

A service level agreement: a written promise between the IT team and the people who use a service, naming the targets — availability, response times — and what is excluded. An SLA agreed before the outage is what the conversation refers back to during one.

Calculate your SLA allowance →

SLA tracker

A tool or record that tracks performance against a service level agreement — how much downtime each service has used, and whether its targets are being met. The tracker turns the agreement from a document into a number you can check.

See the SLA Tracker →

U

Uptime

Time when a service is working and available, usually given as a percentage over a period — a week, a month, a year. Uptime is the headline number in most SLAs, and it is only meaningful next to the period it was measured over.

Calculate uptime allowance →