Anyone working with safety management systems knows the value of precise vocabulary. A hazard is not a risk, a report is not an investigation, and a procedure is not a culture. Information technology has an equivalent problem. Three terms are used almost interchangeably in conversation and documentation: ITOps, ITSM and ITOM. A fourth set of names, the frameworks, adds to the fog. This comparison separates them so that an aviation organisation can specify, buy and audit IT support without talking past its suppliers.
Comparison one: function, practices and tools
The Ops Atlas gives each term a separate job, as the entry for ITOps shows. Under that reading, ITOps is the standing team and its roles, responsible for service availability. ITSM is the body of practices that function follows. ITOM is the technical operations tooling, covering areas such as monitoring and event handling.
An aviation parallel makes the split concrete. The function is the maintenance control centre and its engineers. The practices are the maintenance programme and its procedures. The tooling is the test equipment and monitoring instruments. Organisations get into trouble when they buy tooling and assume the function and the practices have arrived with it.
Boundaries are contested, and the Atlas says so. IBM files ITOM under ITOps, whereas Atlassian has written that ITOM is a subset of IT Service Management, and elsewhere treats the terms as interchangeable. For procurement, the implication is straightforward: define the terms in your own requirements document, and do not assume a supplier’s brochure uses them the same way.
Comparison two: scope, inside and outside the line
Scope boundaries matter as much as definitions. Per the Atlas, the territory includes the help desk, incident and request handling, problem work, change enablement, event monitoring, configuration records, service-level targets and the knowledge base held inside the service-management tool. It deliberately excludes several adjacent areas: live command of major incidents, the design of service catalogues, delivery pipelines, alert correlation, external customer support, the knowledge-management method and endpoint patching, each of which belongs to a neighbouring discipline.
For a flight training organisation, that exclusion list is useful. If an outage disrupts a simulator booking system, ITOps handles restoration and root-cause work. If a student-facing helpdesk handles questions about syllabus content, that is customer support and sits outside this scope. Clear scope prevents the gap where each team assumes another one owns the issue.
Comparison three: the frameworks
The next comparison concerns the reference frameworks. The Atlas lists several, and they differ in character.
ITIL
ITIL began in 1989 and, as the Atlas notes, is optional guidance rather than a certifiable standard for organisations. ITIL 4, from 2019, organises the material as practices; its owner unveiled plans for a fifth edition in January 2026, rolled out phase by phase, and ITIL 4 remains available in the interim. Strengths: widely understood vocabulary and a large training market. Limitation: guidance, not an audit scheme.
ISO/IEC 20000-1
This international standard dates from 2005, with the 2018 edition amended in 2024 for climate-action changes. It is certifiable, so an organisation can be audited against it. That makes it the natural choice when a customer or regulator wants independent assurance. Limitation: certification takes effort that a very small organisation may find disproportionate.
FitSM
A free framework that grew out of an EU-funded project between 2012 and 2015. It is lightweight and aimed at federated or smaller teams. Strength: low cost of entry. Limitation: smaller ecosystem of training and tooling.
COBIT 2019
Published by ISACA, with forty objectives, it addresses governance and management of enterprise IT. It sits a level above day-to-day operations, so it complements rather than replaces the others.
For a regulated aviation business, the practical shortlist is often ISO/IEC 20000 for assurance, ITIL vocabulary for daily practice and COBIT where board-level governance of IT is required.
Comparison four: regulation versus guidance
The Atlas also places two legal instruments beside the frameworks. The EU’s digital operational resilience regulation applies to financial entities from 17 January 2025, and it retains requirements such as independence of the approval function and post-implementation approval of emergency changes. The NIS2 directive sets a notification clock: the first early warning at 24 hours, a fuller notification at 72 hours and the closing report a month later. Neither is aviation-specific, and an aviation organisation should take advice on whether it falls within them. The comparison to draw is that frameworks are choices, while legislation, where it applies, is not.
One further trap: the Atlas warns against confusing the two similarly named items called DORA. The first is a body of research on how software gets delivered, bought by Google in 2018. The other is the EU regulation. They share an acronym and nothing else.
Comparison five: practices on a continuum
Even within the eight practices, maturity varies. A rough ordering for a small organisation might be:
- Foundational: service desk, incidents and requests. Without these, nothing else is measurable.
- Stabilising: problems and monitoring. These reduce incident volume and detect failures sooner.
- Controlling: change enablement and configuration records. These prevent self-inflicted outages.
- Contractual: service levels, which depend on the previous three being reliable enough to measure.
This ordering is a practical suggestion, not a quotation from the Atlas. It reflects the logic that measurement presupposes records, and records presuppose a front door.
Comparison six: tooling choices
As of late 2026, the Atlas lists commercial platforms alongside open-source options, several of them actively maintained, with one releasing a new minor version in mid-September 2026. The deciding factors are the usual ones: licensing cost, hosting control, integration needs and the effort to maintain. It repeats one principle that applies regardless of choice: the tool records the practice, and it cannot substitute for it. Also check default permissions; the Atlas advises restricting automation accounts to the ITIL role on at least one major platform’s change interface rather than granting wider rights.
A selection summary
- Need independent assurance: favour a certifiable standard.
- Need shared vocabulary and training: use ITIL terms.
- Small team, low budget: start with FitSM-style lightness.
- Board-level governance: add COBIT objectives.
- Regulated environment: confirm legal obligations first, with qualified advice.
The common thread is precision. Define the function, choose the practices, then pick tooling that supports them, in that order. Reversing the sequence is the most common and most expensive mistake in the field.
