5 ms·
I'm sure a lot of people are asking how this is possible. - Legacy systems: the thing is probably old and has had a lot of patchwork done to it by various peop
by lordnacho 10y ago
I'm sure a lot of people are asking how this is possible.
- Legacy systems: the thing is probably old and has had a lot of patchwork done to it by various people, many of whom are retired by now.
- The thing is also large and distributed, which makes noticing potential failures quite hard. There are loads of postmortems on the web about how some minor issue like a line going down caused some cascade of unforeseen problems. There's a lot of lessons being learned about how to solve this problem though, so I suppose there's hope.
- Always on: it's hard to change something once the business is relying on it. Loads of staff need to be shown how it works, which makes it hard to incrementally improve the thing because "how it works" would be something that people would have to be updated on.
- Never finished: large organisations will always have loads of feature requests and bug fixes. If you start responding to some of them, you might find yourself swamped. Either you work on the next item, or you spend valuable time making sure fewer items are fixed. It's a balancing act.
- planetjones 10y agoI would add Resourcing to the list. Have Delta airlines joined the mob of traditional big businesses who decide technology is expensive and send it to the cheapest possible? Alternatively it could just be an catastrophic infrastructure failure.
- brightball 10y agoNot likely. All of Delta's scheduling software is in straight assembly. Deltas generally regarded as the well oiled machine of the airline industry. You're paying for always on time and consistent quality. It's one of the reasons a story like this is surprising.
- spyrosg 10y agoInteresting! Are there any source listings anywhere? Do they have particular programming tools or methods that help them deal with the complexity? If it's all assembly, I'm surprised this is only happening now.
- brightball 10y agoBeen that way for at least 2 decades. There's a big company in Atlanta that does all of it but I forget the name. No source listings that I know of.
- ganoushoreilly 10y agoWhile I don't doubt their investment in their software stack to manage operations, Delta is hardly always on time nor consistent. I fly them 2-3 times a month and for the past two months (including today) every flight has has delayed (to and from destination) with only one being weather related.
- nradov 10y agoAnecdotes from individual travelers are interesting but not very relevant or useful. The DoT publishes statistics for airline on time performance. http://www.transtats.bts.gov/ot_delay/OT_DelayCause1.asp http://www.transtats.bts.gov/ot_delay/OT_DelayCause1.asp
- ams6110 10y agoAlso hardware. Likely older and expensive mainframes, which while generally reliable do have a finite lifespan. I'm guessing a critical hardware problem affecting some central part of their flight dispatching system.
- clueless123 10y agoBack in the 2000's Sabre purchased spare parts from the soviets to keep their ancient mainframes running.. I can't imagine how hard it must be now.
- chinathrow 10y agoNot that hard if you're willing to part with lots of cash for IBM.
- jkot 10y agoBut that is mostly not true, you simply must invest money to replace and upgrade old system. Image similar excuses if airline was running WW2 era planes.
- digler999 10y agoI saw a comment on reddit pointing out that planes cannot take off without the baggage weight/distribution calculation. And arriving flights cannot have their baggage scanned to show up properly at baggage claim. The latter seems like something that could be overridden with pen/paper, but I can understand how the weight calc is intricately tied to the scheduling system. I just can't believe they can't have a fall-back at each airport: a simple program that runs on a PC that certifies a single flight based on who physically showed up and how heavy their bags are.