Light sport aircraft owners are comfortable with written procedures: a pre-flight card, a maintenance log, a squawk list. That makes them better prepared than they think for the technology side of running a flying club, a small rental operation or a flight school. The language is the obstacle. This primer introduces ITOps, the discipline of keeping technology services running, and finishes with a short glossary worth bookmarking. Our reference point is the Ops Atlas entry covering ITOps, summarised here for beginners.
ITOps in one paragraph
ITOps is the function that looks after live technology so people can rely on it. Practically, it means somebody receives requests, somebody restores things that fail, somebody investigates why they failed, somebody controls how alterations are made, somebody watches for early warning signs, somebody maintains a list of what exists and somebody keeps the promises about how fast things get fixed. In a large company those are separate teams. In a small club they may all be the same volunteer.
The three layers: people, practice, tools
The Atlas offers a clean way to prevent confusion. The function is the group of people and their roles. The practices are the agreed ways of working, usually described in service-management guidance. The tools are the technical systems used for monitoring and the like. A hangar offers a close match: the engineers are the function, the approved maintenance schedule is the practice, and the torque wrench and test gear are the tools.
What lives inside and outside the boundary
Inside the fence, the Atlas puts the help desk, break-fix handling, routine asks, cause analysis, change enablement, event watching, asset records, response-time promises and the help articles stored inside the ticketing system. Outside, assigned to neighbouring disciplines: commanding a live major incident, designing a service catalogue, release pipelines, alert correlation, external customer support, and patching or endpoint management. For a small operation, the useful lesson is that you do not have to do everything. Pick the core and leave specialist topics for later.
The eight core practices, explained for newcomers
- Service desk. One known place to ask for help.
- Incident management. Restore normal service quickly when something breaks.
- Service request management. Handle routine asks, such as a new account, in a predictable way.
- Problem management. Find and remove the cause of repeat incidents.
- Change enablement. Make alterations safely, at a speed matched to their risk. The Atlas notes that ITIL 4 first used the name change control before renaming it.
- Monitoring and event management. Detect trouble early and filter signals into useful alerts.
- Service configuration management. Maintain a dependable register of the estate and its relationships.
- Service level management. Agree, measure and report on promises.
Three change types every beginner should know
A standard change is low risk and pre-authorised: no meeting, just follow the recipe. A normal change gets assessed first. An emergency change is urgent, such as closing a flaw attackers are exploiting, and is reviewed afterwards. The Atlas says a common myth is that the guidance demands a committee for every single change. It does not.
An aircraft owner will see the match immediately: replacing a lamp is a task you do from a manual, adding a new avionics unit needs planning and sign-off, and a grounding defect needs action before the paperwork. For the mechanical side of owner checklists, see the landing gear checks every light sport owner should run as an illustration of how written routines keep people safe.
How a request becomes finished work
A short walk-through makes the vocabulary stick. Imagine a club member emails to say the online booking page will not load. That arrives at the front desk and is recorded. It is classified as an incident, because something that should work does not. Its priority is chosen from how many people are affected and how soon it matters, and it is assigned to whoever is on duty. While it is being fixed, the person updates the record so others can see progress. Once service returns, the record is closed with a note on what was done.
If the same page failed three times in a month, a separate problem record would be opened, because three identical incidents suggest an unremoved cause. If the cure involves changing a setting, it passes through the change routine at the speed its risk deserves. Finally, the knowledge article describing the fix is saved so the next volunteer does not start from nothing. One event, five of the eight practices, and no special software required.
Why records and clocks matter
Two beginner traps deserve attention. First, the records of what exists must be accurate but not bloated. The Atlas gives a small sample of ten records where several were out of date, an orphan had no keeper and a twin carried a serial number already in use, which is a fair reminder that registers decay without care. Second, service clocks follow rules. In one lab a ticket stayed open across 92.5 real hours but was only charged four and a half, since weekends and holidays stopped the timer. Learn the rule before you judge a number.
Beginner mistakes to avoid
- Buying a ticketing product and assuming the practice has been installed; the tool only records it.
- Giving every change identical scrutiny.
- Adding new rules after every failure without examining the cause.
- Letting monitoring fail silently, which the Atlas warns can hide outages.
- Keeping private spreadsheets alongside the shared record.
- Importing heavyweight process into a team that runs one service.
Fuel systems are a good analogy for the silent-failure item: a gauge that sticks looks like a healthy tank. If that comparison appeals, you may appreciate the fuel-system slips that catch LSA pilots out.
Mini-glossary
- Alert: an automatic message saying something may be wrong.
- CAB (change advisory board): a group that reviews higher-risk changes.
- CI (configuration item): one recorded component in the inventory.
- CMDB: the database that stores those items and the links between them.
- Emergency change: a change done at once, reviewed later.
- Incident: anything unplanned that interrupts or weakens a service.
- ITIL: a widely used library of service-management guidance, first published in 1989.
- ITOM: the technical tools for monitoring and operations.
- ITSM: the practices used to manage services.
- OLA: an internal agreement between teams that supports a customer promise.
- Problem: the root reason behind a run of incidents.
- SLA: a promise to a customer about service levels.
- Standard change: low-risk, pre-approved change.
Where the frameworks fit
You will hear about several frameworks. The Atlas groups them roughly as follows: ITIL 4 is voluntary guidance describing 34 practices, while ISO/IEC 20000-1:2018 is the standard you can be certified against; COBIT 2019 focuses on governance with forty objectives; FitSM is free, created through a European project, and handy for small organisations. A beginner can safely ignore certification at first and borrow vocabulary from whichever suits the community around them.
Questions beginners often ask
Do I need a ticketing product? Not at the start. The Atlas observes that the tool records the practice rather than being the practice, and it lists both commercial and open-source options for later. A shared spreadsheet with disciplined columns will teach you the habits.
Is this only for IT specialists? No. Anyone who coordinates a shared service can use the same ideas, from a club website to a maintenance booking calendar.
Your first-month reading plan
- Week one: learn the three layers and the eight practices.
- Week two: sort recent club or school tasks into requests, incidents, changes.
- Week three: list your key services and who looks after each.
- Week four: test your alerting path, then book a monthly review.
Another gentle starting point is the cheerful explainer on the friendly digital helper that gets computers fixed quickly, which approaches the same territory from the user’s side. Terms feel strange for a week and then become ordinary. That is how every discipline, from airmanship to operations, is learned.

