Some of the biggest cuts your workload ever took didn’t come from a computer at all. They came from redrawing the airspace. Fixed arrival tracks, one way routes, departures that climb inside a tube nobody else may enter, arrivals that fly a published line until the last turn. Your predecessors were vectoring all of that by hand, all day. Somebody worked out that if the map is drawn so two aircraft can’t reach the same place, nobody has to keep them apart. I don’t think any software has taken that much work off you in one go. That’s a guess, and a soft one. The newer equipment and the way sectors get split belong in the same sentence, and I’ve left them out because I can’t weigh them.
The software is real too, and you use every bit of it. Strips on a screen instead of paper in a bay. Alerts that fire when two tracks are going to argue. Tools that build the arrival order before the aircraft are anywhere near you. Datalink, so a routine level change doesn’t need a transmission. Coordination with the next sector that used to be a phone call and is now a keystroke. Nobody in your trade wants the paper strips back, and nobody is going to want the lot after this one back either.
All of that changes how much traffic can be in your sector. It doesn’t touch what gets done with it.
Ask a controller what the skill is and the answer comes back slightly impatiently, because it never explains well to anybody who hasn’t had it. The picture isn’t knowing where the aircraft are. The screen has that, and the screen has it better than you do. It is knowing what every one of them is about to want, which of those wants you are going to grant, in what order, and what the sector looks like once you have. It runs forward, not sideways.
Here is the evidence for it that outsiders never think about. Everything a relieving controller needs is already on the display, and nobody takes the position cold. They stand behind you, they watch, they listen to the frequency, they take the briefing, and only then do they say they have it. Your trade counts seconds and hates waste, and it still spends that time, every relief, on every position, forever. That practice is an admission written into the roster. What matters is not on the screen, and the only way to get it is to sit and build it.
The picture is for spending. Your work is deciding which of the things in front of you to do, continuously, and that is not the same problem a hospital has. You can push back on what is still coming, and controllers do. What is already on your frequency can’t be turned away, and every one of them gets a service. What varies is which service.
On a quiet sector you grant almost everything. The direct routing, the early climb, the speed somebody wants for a connection, the deviation around a build up, the descent when they ask rather than when you’d planned it. As the sector fills, you start spending. Standby. Unable. Expect it shortly. Nobody has to tell you the order in which those go, and no rule anywhere sets it.
Then there is the move you were never taught and have never had to explain. When it is getting away from you, you flatten it. You stop the climbs, you level people off, you put them on headings so nothing has to be negotiated. A whole group of aircraft is now sitting at an inefficient level, burning fuel somebody is paying for, and you accepted that. You did that to buy room in your own head. Nothing instructed you to. No procedure names it, no report records it, and the only thing it produces is a mess that then doesn’t happen.
The same instinct runs through the smaller decisions all shift. One problem gets solved first. Another gets left alone, because that aircraft will slow for its descent and solve it on its own, and touching it now would cost words on a busy frequency and buy nothing. Choosing what not to do yet is most of the trade. It is also the part that looks, to anybody watching, like doing nothing.
The biggest of those decisions is about you. Asking for the sector to be split, telling flow you need the traffic slowed down, telling the supervisor you want relief. The resource being allocated there is your own attention, and you are the only person in the building who can measure it. Everyone knows who asks early and who never asks, and that knowledge does its work quietly.
Controllers are made, not born, in a course with a failure rate that would close most training schemes. That is proof the picture can be taught, and it is exactly the sort of thing a profession says about itself right up until somebody teaches it. A machine holding the picture also has no fourth hour in it. No night shift, no head cold, no argument at home, no need for relief, no bad Tuesday. Fatigue is a well documented problem in your trade, and it is the one thing a machine simply doesn’t have.
So the honest answer is narrower than the trade would like. A system will run your sector at its real limit, it will grant more than you would, and on plenty of mornings that will look better than what you did. The arithmetic isn’t the part I’d defend. What somebody still has to supply is the order. Which want gets granted, which gets held, which gets left alone because it is about to solve itself, and which gets refused so that three others can be granted. That ordering gets remade continuously, it is never written down anywhere, and nothing on the tape shows it being made.
Where I’d be careful is the middle. I’d guess the picture is more teachable than controllers believe and less transferable than the people selling the tools believe, and I can’t tell you where between those two it sits.
Suppose a system worked your sector this morning and granted every request you would have held. Everyone gets the climb, everyone gets the direct, and the hour passes with nothing on it. Tomorrow somebody plays you the tape and asks whether it chose better than you would have. What would you need to see on it to answer?