Tom's Hardware learned that candidates would oversee machines running 166 MHz processors with 8 MB of RAM, which are used to display important technical train data to...
Used to work at an airport that had a similar issue, turning some of these systems off simply isn’t possible. So you end up having to run the replacement system simultaneously with the old system for a few days. Can’t simply take it off line for a day.
It’s an expensive problem, especially if it’s a system that’s being used all across the airport by regular staff.
You need to train thousands of employees to use the new software, you need to have one person using the old software as a backup, while the other uses the new software, often while surrounded by hundreds of often angry customers.
And if something goes wrong, which it invaribly does (even if it’s user error or someone snagging a cable), shit can get very expensive. Small delays, add up to larger delays, and cascade through the entire system. Delayed flights, tens of thousands of euros in costs, hotels for thousands of passengers, missed flights, missed meetings, damages, lawsuits, penalties for missed landing/take-off slots, missed time windows for certain cities which don’t allow flights after a certain time, etc. And often you discover legacy stuff while you’re upgrading that needs fixing, stuff that no one knows how to replace anymore or is physically hard to access.
Sometimes it is genuinely better to leave it. COBOL is 60 years old. There’s still plenty of stuff running on it, exactly because it’s often too expensive and too risky to replace.
Is it broke if no one is able to fix it?
The reason for it to run on such an ancient device is because nobody wants to touch the scripts running on these devices.
A lot of these systems are also always on.
Used to work at an airport that had a similar issue, turning some of these systems off simply isn’t possible. So you end up having to run the replacement system simultaneously with the old system for a few days. Can’t simply take it off line for a day.
Running two systems simultaneously for a couple of days, that’s a huge problem, not solvable
It’s an expensive problem, especially if it’s a system that’s being used all across the airport by regular staff.
You need to train thousands of employees to use the new software, you need to have one person using the old software as a backup, while the other uses the new software, often while surrounded by hundreds of often angry customers.
And if something goes wrong, which it invaribly does (even if it’s user error or someone snagging a cable), shit can get very expensive. Small delays, add up to larger delays, and cascade through the entire system. Delayed flights, tens of thousands of euros in costs, hotels for thousands of passengers, missed flights, missed meetings, damages, lawsuits, penalties for missed landing/take-off slots, missed time windows for certain cities which don’t allow flights after a certain time, etc. And often you discover legacy stuff while you’re upgrading that needs fixing, stuff that no one knows how to replace anymore or is physically hard to access.
Sometimes it is genuinely better to leave it. COBOL is 60 years old. There’s still plenty of stuff running on it, exactly because it’s often too expensive and too risky to replace.