{"id":1181,"date":"2026-11-16T05:40:00","date_gmt":"2026-11-16T05:40:00","guid":{"rendered":"https:\/\/flyaiaa.com\/blog\/?p=1181"},"modified":"2026-11-18T14:40:00","modified_gmt":"2026-11-18T14:40:00","slug":"itops-plain-english-ground-crew","status":"publish","type":"post","link":"https:\/\/flyaiaa.com\/blog\/itops-plain-english-ground-crew\/","title":{"rendered":"ITOps in Plain English: The Ground Crew Behind Smooth Flights"},"content":{"rendered":"<p>When a flight leaves on time, nobody claps for the fuel truck, the baggage belt or the person who checked the gate display. Yet if any one of them slips, everybody notices. Technology has its own ground crew, and the name for that crew is ITOps. Here is the idea in everyday words: what the work involves, how it is organised, and what it has to do with you even if servers are a mystery. If you can follow how a turnaround at an airport gate works, you can follow this.<\/p>\n<p>The explanations here lean on <a href=\"https:\/\/www.xopsschool.com\/itops\/\">the Ops Atlas page that describes ITOps<\/a>, which sets out the discipline in a clear structure. Think of the page as a reference manual and this post as the friendly briefing before the flight.<\/p>\n<h2>So what is ITOps, really?<\/h2>\n<p>ITOps is the group of people who keep a company&#8217;s technology working day in and day out. If a login fails, they help. If a system breaks, they restore it. If the same thing breaks again and again, they dig for the reason. If someone wants to alter how something works, they check it will not cause damage, and they keep an up-to-date list of what the company owns. That is the whole job, in one breath.<\/p>\n<p>Compare the ramp team at an airport. They do not design aircraft or sell tickets. They make sure that what exists works today and keeps working tomorrow.<\/p>\n<h2>Three words people mix up<\/h2>\n<p>You will hear ITOps, ITSM and ITOM used as if they were synonyms. The Atlas suggests a tidy way to separate them:<\/p>\n<ul>\n<li><strong>ITOps<\/strong> is the crew itself, the humans and the roles they hold.<\/li>\n<li><strong>ITSM<\/strong> is the playbook the crew follows, the agreed way of handling work.<\/li>\n<li><strong>ITOM<\/strong> is the equipment, meaning monitoring and similar technical tools.<\/li>\n<\/ul>\n<p>The Atlas admits that even large software firms do not agree about the boundaries. One puts the equipment under the crew; another treats the words as interchangeable in one place and nests one inside the other elsewhere. So if two articles define them differently, that is normal and not your mistake.<\/p>\n<h2>The eight everyday jobs<\/h2>\n<p>The Atlas lists eight core activities from the widely used ITIL guidance. Here they are, with airport comparisons:<\/p>\n<ol>\n<li><strong>Service desk:<\/strong> the information counter. Everyone starts here.<\/li>\n<li><strong>Incident management:<\/strong> a baggage belt jams; get it moving again, fast.<\/li>\n<li><strong>Service requests:<\/strong> a passenger asks for wheelchair assistance. Expected, routine, planned.<\/li>\n<li><strong>Problem management:<\/strong> the belt has jammed six times this month; find out why.<\/li>\n<li><strong>Change enablement:<\/strong> repainting gate numbers without sending travellers to the wrong place.<\/li>\n<li><strong>Monitoring and events:<\/strong> the signs and sensors that tell you something is wrong.<\/li>\n<li><strong>Configuration management:<\/strong> the master list of every gate, belt and screen.<\/li>\n<li><strong>Service level management:<\/strong> the promises, such as how long a fix should take.<\/li>\n<\/ol>\n<p>Notice the difference between items two and four. Fixing a broken thing is an incident. Finding out why it keeps breaking is a problem. Teams that only do the first end up busy forever.<\/p>\n<h2>How changes are sorted<\/h2>\n<p>Not every change deserves a meeting. The Atlas describes three kinds. A standard change is low risk and already approved, like swapping a standard display cable. A normal change gets a proper look first. An emergency change must happen right now, for example closing a security hole that attackers are already using, and gets reviewed afterwards.<\/p>\n<p>It is a common myth that guidance like ITIL demands a committee for every tweak. It does not. In fact, research on software delivery found no evidence that outside approval reduces failed changes, and recommends peers reviewing each other&#8217;s work instead. If you want a practical airline-style checklist mindset for safety around flights, have a look at <a href=\"https:\/\/flyaiaa.com\/blog\/common-charter-safety-mistakes-travelers-should-avoid\/\">the usual safety slips charter passengers make<\/a>, which shows how simple written checks prevent trouble.<\/p>\n<h2>What a service promise looks like<\/h2>\n<p>Here is a neat example from the Atlas. Suppose a customer is promised that a medium-urgency fault will be fixed within eight hours. Behind the scenes that promise is sliced up: half an hour for the desk to sort it out, two hours for the network team to find the cause, four hours for an outside carrier to do their part, and ninety minutes kept spare. Each slice has an owner. If the promise is missed, you know whose slice ran over.<\/p>\n<p>The airport version is a turnaround target for a plane: fuelling, cleaning, boarding, each with its own team and its own time. When the plane is late, the slices show where the minutes went.<\/p>\n<h2>Keeping the master list honest<\/h2>\n<p>The list of everything the company owns is called a configuration database. Plain advice from the Atlas: keep what helps decisions, not everything imaginable. In a sample check of ten entries, most were complete, but a couple were out of date, one had no owner and one repeated another&#8217;s serial number. It is the same story as an airport asset list where a screen is recorded twice and another is missing; decisions based on it go wrong quietly.<\/p>\n<h2>The quiet failure to watch for<\/h2>\n<p>A warning system that fails silently is worse than none, because it makes everyone feel safe. The Atlas lists this as a classic mistake: treating the alert layer as unimportant. A good habit is a regular test message that proves a human would really be told if something broke. The ground transport side of a trip works similarly; the <a href=\"https:\/\/flyaiaa.com\/blog\/private-ground-transport-checklist-for-charter-travelers\/\">checklist for arranging private ground transport on a charter trip<\/a> is built around confirming each handover rather than assuming it happened.<\/p>\n<h2>A day in the life, told simply<\/h2>\n<p>It helps to picture one ordinary morning. At 07:45 the monitoring screen shows a booking system slowing down. A sensor picks it up before any customer complains, which is the whole point of having sensors. The person on shift opens an incident, checks the priority rule, and sees that many users are affected, so it goes to the top of the pile. Meanwhile, three routine requests sit waiting in a separate queue: a new starter needs an account, someone wants a shared mailbox, another person needs a password reset.<\/p>\n<p>By 09:00 the slowdown is fixed by restarting a stuck service. But the story does not end there. The same fault happened twice last month, so a problem record is opened to find the real cause. A fortnight later, the team discovers a scheduled job that clashed with a busy period, and they move it. A change like that is small and well understood, so it goes through the quick lane. Nobody wrote a speech about it. That is ITOps working properly: mostly invisible, mostly dull, and extremely valuable.<\/p>\n<h2>Common mistakes in plain words<\/h2>\n<ul>\n<li>Using a big, heavy system for a tiny team with a single service.<\/li>\n<li>Treating a coffee-machine change and a payment-system change the same way.<\/li>\n<li>Adding more rules every time something fails instead of fixing the cause.<\/li>\n<li>Counting service time without knowing the pause rules for weekends and holidays.<\/li>\n<li>Keeping secret spreadsheets because the official tool is awkward.<\/li>\n<\/ul>\n<h2>Do I need a certificate to start?<\/h2>\n<p>No. The Atlas notes that the main guidance is optional, that one international standard can be certified if customers require it, that a governance framework exists for risk and audit people, and that a no-cost framework born in a European project works well for small teams. Learn the ideas first. A certificate later is a bonus, not a gate.<\/p>\n<h2>Your first week, in plain steps<\/h2>\n<ol>\n<li>Write a list of the five services people would miss most if they stopped.<\/li>\n<li>Next to each, write who looks after it.<\/li>\n<li>Decide how you would find out if one failed in the night.<\/li>\n<li>Keep a notebook of every repeat problem, with dates.<\/li>\n<\/ol>\n<p>That is enough to make a real difference. Smooth flights are built from small, boring, repeatable habits, and so is reliable technology. Once you notice the ground crew, you will start spotting them everywhere.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>No jargon: what ITOps is, how it differs from ITSM and ITOM, and the eight everyday jobs, explained with airport ground-crew comparisons.<\/p>\n","protected":false},"author":6,"featured_media":1182,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[634],"tags":[],"class_list":["post-1181","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-flight-training-tech"],"_links":{"self":[{"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/posts\/1181","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/comments?post=1181"}],"version-history":[{"count":1,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/posts\/1181\/revisions"}],"predecessor-version":[{"id":1291,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/posts\/1181\/revisions\/1291"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/media\/1182"}],"wp:attachment":[{"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/media?parent=1181"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/categories?post=1181"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/tags?post=1181"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}