Book Appointment

ITOps Glossary for Beginners, Told Through a Clinic Admin’s Notes

Healthcare Software

Mira spent her first week in the admin office of a clinic group surrounded by unfamiliar words. People talked about tickets, change windows and something called a CMDB. Nobody had time to explain, so she started a notebook. This primer is that notebook, tidied up for anyone new to ITOps, the team responsible for everyday technology working as expected. Every term below is explained for non-engineers, and there is nothing clinical in it.

First, the big idea

ITOps is a team and a set of roles. Its job, as the Ops Atlas describes it on the ITOps page of that reference, is to keep everyday IT services available: respond to requests and incidents, fix repeat causes, manage changes and know what equipment exists. Mira liked the framing because it matched what she saw. When the booking system stalled, a specific group of people was responsible, and they had routines.

The mini-glossary

Service desk

The front door. Every problem and every request goes here first. Mira’s clinic used a shared inbox that created a numbered record for each message, which was enough to start with.

Incident

Something that should work and does not. A frozen screen, a dead scanner, a login that fails. The aim is to restore service quickly, even if the true cause is still unknown.

Service request

A routine ask, such as access for a new colleague or a replacement keyboard. Nothing is broken; someone just wants something provided.

Problem

The cause behind repeat incidents. If the same scanner dies every month, the incidents are symptoms and the problem is whatever keeps killing it. The Atlas lists problem management among the eight core practices of the main framework.

Change

Any alteration to a live service. Three kinds exist. Standard changes carry little risk and are cleared in advance. Normal ones are assessed before scheduling. Emergency ones are applied at once, for instance to close a hole that attackers are exploiting, and is reviewed afterwards. Mira was relieved to learn that not every change needs a committee.

Change enablement

The newer name for what used to be called change control. The shift in wording reflects an idea in the Atlas: the point is to let safe change happen quickly, not to slow everything down.

CMDB

A configuration management database: a register of equipment, software and the connections between them. Mira discovered that hers listed a decommissioned workstation as still active. Registers drift unless someone owns them. The Atlas advice is to hold what decisions need, not every object in the building.

SLA, OLA and UC

Three abbreviations for three promises. A service level agreement is made with users. An operational level agreement is an internal promise between teams. An underpinning contract is the promise from an outside supplier. A customer promise is built from the other two kinds, plus a little slack.

CAB

A change advisory board, the group that looks at higher-risk changes. In modern thinking, according to the Atlas, its role moves from gatekeeper to a designer of good process and a source of shared information.

Event

A signal from a monitoring tool, such as a disk filling up. Many events can be grouped into one incident. The Atlas treats the event layer as a production dependency, because when it fails silently, outages hide.

ITSM and ITOM

Three labels get tangled: ITSM means the written practices, ITOM means the technical monitoring and operations tools, and ITOps means the people doing the work. Vendors do not always agree on these boundaries, so read job descriptions and product pages with care.

How Mira used the notebook

Within a month, her glossary turned into a small laminated card beside the office phone. It held the clinic’s four priority levels, a line explaining which changes were pre-approved, and the name of whoever owned the equipment register. She did not buy new software. The only tool she added was a free open-source service desk product on a spare server, which the Atlas lists among current options for smaller teams.

She also learned that ITIL, the widely used framework, is optional, while a standard called ISO/IEC 20000-1 is the one a company can earn a certificate for. The Atlas notes a free European alternative named FitSM as well. Choosing between them was something for later; first came vocabulary.

One more word: the clock

Service targets run on clocks, and clocks have rules. Some tick around the clock; others only during office hours and stop for weekends and public holidays. Mira’s card carries a reminder to ask which clock applies before judging any report. A ticket can look slow or quick depending entirely on that setting, which is why the Atlas lists misunderstood clock rules among the common traps. It is a small detail that new staff rarely hear about until a monthly report surprises them.

Where to read next

If the glossary left you curious about the wider family of operations disciplines, our overview of the unified architecture behind these operations disciplines gives a map. For a practical angle on service and cloud tasks, there is also our note on smoothing software and cloud operations.

Three habits for beginners

  1. Keep your own notebook. Writing a definition in your own words proves you understood it.
  2. Ask what a word covers and what it leaves out. The Atlas spends real effort on scope for exactly this reason.
  3. Look at one real ticket from start to finish. It teaches more than a week of slides.

By her second month Mira was the person colleagues asked about the jargon. That is how most people grow into this field: slowly, one clear definition at a time.