Time For Airlines To Get Past The Mainframe Era
from the up-to-date dept
There have been a number of high-profile snafus at airports this year, and while bad weather tends to be the most prominent cause, it’s not the only culprit. Last month, passengers traveling on US Airways faced massive delays after self-service kiosks suffered a glitch, stemming from the company’s ongoing attempt to merge its reservation system with that of America West Airlines, which it acquired two years ago. While most industries have invested heavily to upgrade their IT systems over the years, the major airlines still rely primarily on legacy mainframe systems that were developed in the 70s. For day to day operations, these systems get the job done, but they’re not very flexible. Even when weather is a major factor in an airline’s problems, the lack of a good IT setup can exacerbate the problem. In February, jetBlue suffered a major meltdown, in part because the company was not sufficiently prepared to track its assets in the event of a major crisis. Following the fiasco, the company claimed that it had upgraded many of its systems, although considering the difficulty and time it takes to upgrade enterprise systems, it’s hard to imagine that much has already changed. Part of the reason the industry may be so behind in modernizing its IT is that for many years, most of the major carriers were hemorrhaging cash and teetering on insolvency — hardly the ideal conditions for major investments. But now most of the airlines are profitable again, and with 2007 looking like another bad year for things like delays and lost luggage, it might be time for the industry to invest heavily in its own IT infrastructure.
Comments on “Time For Airlines To Get Past The Mainframe Era”
the only people who aren’t using legacy are either tech companies, or new ones.
From my time at an airline, there is nothing from these mainframe systems, besides maybe a GUI.
It knows where every plane is, where every bag is, and where every person is. It knows when a person is going to miss a connection and automatically rebooks that person on a later flight. It can predict how a delay will effect future flights and correct the problems
The only downside from the systems is a lack of a GUI, but with the efficiency that the employees use the CLI, I would hate to see it changed.
Not really any other option
The issue is that very few platforms have the reliability and scalability of a mainframe. Certainly not Windows – can you imagine your flight delayed because of a Windows Update? Or UNIX, either, for that matter. Mainframes have massive IO capacity which can be matched only by supercomputers. In short, the airlines really don’t have the option of using anything else.
Re: Not really any other option
I’m not buying your logic. There’s nothing a mainframe can do these days that a decent Linux system couldn’t do(except maybe run RPG III programs). Their “I/O capacity” is dwarfed these days in terms of gigabit pipes and regardless of how many channels a mainframe may allow, the maximum speed back then was about 1megabit/sec(and probably much lower).
Google isn’t using a warehouse full of mainframes to do their work and they handle more data per minute than any airline will have to track in a week.
Re: Re: Not really any other option
Just what i want to trust my billion dollar business to.
I was in airline IT (unscheduled/cargo) once, and I’m reluctant to blame the airlines if what we had to deal with is at all widespread.
See, the FAA has to approve everything in airline IT. No big deal; banking was the same way. Except FSLIC/FDIC regulators were a whole different breed than the FAA ones, and getting *anything* approved by the FAA was an exercise in futility. FAA regs are sufficiently badly written as to allow a great deal of latitude in individual readings, and if the guy assigned to your airline is so motivated (say, by you making work for him by asking him to approve a new system) he can choose to interpret things like crew schedules in the most inconvenient way possible. There’s very, very heavy incentive to not upset the status quo.
Must be over 40
I guess everyone posting replies to this article are over 40 because if they weren’t they would know that a clustered anything can outperform any mainframe… but anyways its more or less just about capital and that the airlines know that the money lost because of delays, lost luggage, and angry people are far less than upgrading their IT infrastructure… So why upgrade?!? What really is the incentive… except to loose more money, raise prices of airlines, and piss of more people…
Nothing wrong with using a Mainframe
Most major companies make major investments in Mainframe infrastructure and software. There is nothing wrong on keeping a mainframe for all major tasks. It’s what you do for the interfaces and upstream/downstream that really make the rubber meet the road.
I’ve seen many cases where people (management) get a grand idea on replacing the mainframe system with either a turn-key product, or custom developed on “another” platform. Many have ended in disaster for various reasons, and they just default back to the mainframe. I’ve also seen people successfully migrate from a mainframe system too. If it ain’t broke, don’t fix it.
There are plenty of ways to modernize a mainframe system for today’s age, you just have to do it properly! To bin the decision on “Mainframe == crusty old equipment” just isn’t fair.
The real story
There are five major reservation companies that run most of the airlines, rental cars, hotels, and trains in the world. Those are Amadeus, Galileo, Worldspan, Sabre & Abacus. At least three of those have recently gone private, Sabre just last week.
OK, you’ve seen a GUI at a kiosk – big deal. That is just a front-end system that still relies on the mainframe back-end. Travelocity is a HTML front end that has the Sabre mainframes on the back-end. These are in the same data center in Tulsa, OK. When you do a low-cost search on Travelocity, the mainframe’s knees buckle.
And these are not MVS systems either. Sabre can run up to seven of the hottest IBM frames as a cluster, with the TPF operating system. 4000+ real-time transactions per second. A huge DASD farm is attached (disk drives, in Frame speak.)
The inertia of changing these systems is tremendous. Look at the history of Sabre on Wikipedia, it is very good and mostly accurate.
But, don’t think you can replace seven frames with a lean OS built for transactions with Server 2003. Maybe a large Beowulf cluster could. Or perhaps Google could…
Re: The real story
This is all true but the current problems being faced by airlines are not only to do with platform and an aging backbone structure (although this is a large part of it)
Any company engaged in a lot of mergers, aquisitions and sell offs (such as almost the entire airline industry) will encounter major problems in their IT. The problems facing the Airline sector at the moment are due largely to the sheer number of technologies and applications in use, and the corresponding number of conduits, portals and methodologies required just to get them to talk to one another – all this dramatically increases the possibility of error
The other key problem I often experience is that companies expect to just merge and be able to cut costs immediately (usually by shedding staff). This becomes a problem if a company does not consolidate its IT infrastructure, then fires the guys who knew how x and y legacy systems it just inherited really work
So I think basically my point is that its not just a platform issue but the way IT tends to fall through the crack in general in mergers, often due largely to the way boards tend to think of an IT merger as just “pluging that there machine thingumy from our new company into our own interweb thingy”
Google isn’t a fair comparison. Google is a distributed system providing a service to distributed customers.
Airlines require a central data repository that requires data locking and central management.
It is possible to do that with a cluster or network solution, but those solutions do not have the history that the mainframe ones have.
Yes, a GUI will make usage easier.
I’ve used PC’s, clusters, and mainframes.
Each have their own strengths and weaknesses.
I’ve seen some real-time solutions that run great on a mainframe.
And I’ve seen some huge databases run great on a Unix cluster.
I think what matters is the System Architecture. Choosing the hardware is part of the process after deciding what the most important requires are and how they can best be addressed.
It's not the platform its the code
The major issue isn’t the capability, stability or speed of the system, rather its the fact that the core code base is so old that its probably comprised of more patchwork solutions then original code.
The world was smaller and simpler when these systems first went online. Over the years I imagine that the airlines have chosen to not start over with a solution that was architected from the ground floor to be a comprehensive solution. Instead they most likely just kept cobbling and patching on top of their original code base.
When you take this approach changes can take a tremendously long time to engineer, not because the type of code itself is “inflexible” rather because the code that was written has so many dead ends and workarounds that any changes requires numerous and extraneous changes to patch programs that run in the background.
And before any starts with the “you must be over 40” comments, I’m actually 31.
Please base arguments on fact not fiction
There is nothing in this article taken from fact except that airlines had delays this year.
Almost all stories of computer related problems have occurred on new up-to-date systems not on legacy systems. Below are two of the best.
Navy ship Yorktown when their computer system tried to divide by 0
Wall Street Melt Down
Try to even find a headline of a legacy system having a compute error that crashed a company. It’s almost impossible.
Even the article quotes the company as saying it systems were “upgraded”, but instead of putting the blame on the new system, Joe implies that it must have been the “old” system that went bad, because it works better for the story.
Look at the gaming industry that relies heavily on mainframes (as400’s). To my knowledge there has never been a computer related problem that has shut down a casino that has made a headline and this is in a business that runs 24x7x365.
I imagine that the airlines kiosks where being run by a new up-to-date computer system that with a GUI that then updated a mainframe (if a mainframe was involved at all since it hasn’t been proven).
It’s funny to see how many people on here are sticking up for old mainframes. Let’s face it, mainframes were the top of the line back in their day, but today there are better solutions. The problem is that much of the antiquated architecture is left when a company is forced to upgrade portions. Heck, some companies run green screen systems because they “work”. These same companies are also complaining about a lack of support for new technologies. Just because something works, doesn’t mean it works well or will continue working much longer. People are expecting more and more from their systems, not just data dumps and dumb terminal connectivity.
The reality is that technology is moving forward and so should any IT department that doesn’t want to be on the news. The airlines will suffer a catastrophic issue resulting from aging technology and that will prompt them to change. It has very little to do with how well the system works and everything to do with the amount of money it would cost to upgrade.
Its about cost
They say they can’t afford to upgrade because they aren’t making money. Part of the reason they aren’t making money is because people have doubts about their outdated tech. Just a viscious cycle
In the next year New York will see a new kind of airline the VLJ Limo or very light jet limo. No more lost bags. No more long unruly lines. No more being fondled by TSA strangers. no more “on the tarmac virtual lock downs. Hang in there my fellow travelers, the light jets are coming!!!
The real story continued
In fact, JetBlue does not use the traditional TPF mainframe that the older major airlines use. JetBlue is famous in the biz for having gone 100% Microsoft.
So bad example.
And for what it is worth, TPF is an awesomely powerful OS.
Can you name me one other OS where you can run multiple versions of the OS in parallel, upgrade application versions without bringing the system down (open transactions finish in the old version, new transactions open in the new version), and unplug the whole data center, and then resume in mid transaction with no data loss the minute the power is turned on again?
Issues such as the merger problems you refer to are as “that guy” says, due to coding issues. business rules and fare structures are so different from one airline to the next (in fact they are considered closely guarded secrets) that merging the two is a monumental undertaking akin to changing the tires on a car while it is still moving.
I feel certain that there would be even more interruptions that would take longer to fix if this were being ported over to a web application at the same times as the operations merging was taking place.
How many mainframes does Google have?
What critical application do they run? How much technology do they have to create just to get it to run, because the systems they use don’t cluster very well. How many server farms do they have to have maintain? What do they really do other than simple query?
When a query is finished, that customer is “out the door” so to speak, the whole life of that transaction is finished.
Airlines not only have to handle queries, but also keep up with flights, tickets, bags, payments, seats, crews, etc.
This is like saying “I wrote an excel macro I must be a progammer”.
Re: How many mainframes does Google have?
Google uses clusters of commodity x86-based PCs mounted in racks.
Re: Re: How many mainframes does Google have?
And your query will vary from location to location. What if your reservation varied from airport to airport? Two different types of business.
Yes, the major GDS systems (that is the generic names of Sabre, Worldspan, etc.) do more than reservations. They also load balance the planes, track cargo reservations, and track maintenance. If a GDS goes down, planes don’t fly. All of the major airlines use one of the big GDS systems.
The Future Is Almost Here!!!
No more two and a half hour flights to Atlanta that take seven hours to complete. No more luggage prestidigitation. No more screaming babies, with popping eardrums, proving again that there are worst things than children, specifically, other people’s children. No more first class tickets on second class airlines with third class flight crews. No more, my fellow Americans, no more. You see, the light jets are coming.
Anyone who declares one platform is absolutely better than another is a fool.
The capital investment can be High (mainframe) or low(Linux)
Maintenance can be easy( 1 mainframe) or hard (2000 Linux servers)
A server can be reliable (mainframe) or not (beige box)
You can do any number of these comparisons which is “best” for the situation.
For those of you with less experience, the mainframe is a perfectly fine File Server, Database Server and Application Server
mainframe legacy nightmare
My last job, I was handed a loans systems cobol app that had been ported to win32. It was a nightmare, really! Most of these companies dont want to spend the $$$ to do a complete re-wirte and they cut corners by using 3d party tools that say they then do the trick and it just does not work.
Ignorance and Competitive FUD
It’s amazing how ignorant some people can be about mainframes. IBM’s current official designation for mainframes is “System z”. That’s for “zero downtime”. In fact, mainframes are famous for the “five nines”, that is being up 99.999% of the time. Other people have mentioned how you can swap out software modules without having to bring down the system. You can also do this with hardware. This isn’t because their OS contains “more patchwork solutions than original code”. This is because they have a highly evolved, thoroughly tested, finely honed OS. IBM is constantly working on modernizing their mainframes to ensure that they run all the latest enterprise-level applications support the latest protocols. One poster mentioned Linux. You can run hundreds (maybe thousands?) of virtualized Linux sessions on a single mainframe. You could, in essence, have a virtual Linux farm running on a single mainframe and the administrators could remotely log onto the individual machines an not even have to be aware that they are actually connected to a mainframe. Don’t think these companies are stupid. I’m sure the first thing some newbie just out of college who comes into one of these big iron shops thinks is “Why can’t we replace this mainframe with 1000 Sun workstations?” Then, they start costing out what it takes to run 1000 Sun blade servers in terms of maintenance, administration, software licenses and configuration, electricity, floor space, etc; and they quickly realize that not only does the existing big iron do the job as well as any massively clustered system, but it does it cheaper and more reliably. Speaking of clustering, as one poster already mentioned, mainframes can be clustered too. In fact, I’m pretty sure they have supported clustering for at least 30 years. Some people lament the fact that mainframes don’t have a GUI, but the fact is that millions of people interact with mainframes every day through HTML pages and don’t even know it. The internet plays right into the mainframes strength which is transaction processing. HTML pages are just “green screens” with colors. There are definitely places where clusters of Unix-like machines are more appropriate – telecommunications, supercomputing, etc, but mainframes still have a place and will for a long time. You don’t want to be like the man whose one tool is a hammer so everything looks like a nail, or in this case your one tool is a Unix cluster so everything looks like a Google query.
Re: Ignorance and Competitive FUD
Cisco even makes an interface that offloads the IP stack for faster processing that plugs directly into a mainframe.
JetBlue not only runs Microsoft software, but they also run beta code to lower costs. JetBlue also admits this is a risk they are willing to run to be cheaper.
Cutover? Consider US Airways – they had their own tiny reservation system until 1999. They decided that it wasn’t worth implementing a four digit year, and cut over to Sabre instead. So, check your November/December 1999 news – can you find any problems with US Airways?
The issue is continuity. How long is IBM going to make a compatible mainframe? How many years have they made one? In contrast, try to load Server 2003 on a 80286.
These companies have been doing volume transactions for years. Last I knew, Sabre had a 99.95% uptime. They have to have a long-term, clustered reliable platform.
I’m not say it is perfect. DST is done by hand, and in the fall the system is shut down for an hour to prevent time duplication. They cluster up to seven frames, but they don’t all the time. The count varies with load. That way they can do hardware changes.
Some airlines still run standalone. Last I knew, Southwest was still running VMS on VAX hardware.
But, the big res companies are in trouble. Sabre outsourced the data center to EDS for “cost saving”, but still had to go private.
Mainframes are outdated. It’s cluster computing thats won the way. You can make a solid cluster for 1000$ and it’s not hard to make a control platform.
There are very few “off the shelf” vendors that support cluster environments. Becasue there are very little standards for one.
Clusters are considered “custom” installs.
What is it with assuming atinquated = mainframe??? Whoever says that hasn’t been in a DataCenter with a zSeries Mainframe and a DASD farm from EMC 2. The platform is rock solid and I’m sorry no server farm is going to be as productive and cost effective as a modern mainframe. Want a GUI front end and keep your backend? There’s CORBA. The only downside
to using mainframes is there isn’t really any z/OS for
dummies books out there that so many so called IT
pro’s rely on these days to get by.
I recently made the same assumption that mainframes were the past while doing a research paper on this specific topic for an industry exec. At the end of the project he explained a few aces he kept up his sleeve. The industry *won’t* move away from mainframes. It’s not about money, it’s about the reliability and scalability of mainframes. You just can’t beat it. I’m not at liberty to get into my findings as they were for a private company, but I’ll say that it’s not as clear cut as it looks.
stick with mainframes
the only “death march” project i’ve ever been on was a massive two and a half year (it was supposed to be done in 12 months) conversion from a mainframe system to a client/server solaris system. if the code base is there and it works, it’s worth the premium that COBOL guys charge these days to keep the system around.
The airlines are still to reliant on mainframes?
Anybody have any experience working the financial services industry? I still carve things on the wall of my cave.
18 years in the financial services industry. I’ve seen my share of applications go from mf to wintel back to mf. Cost effectiveness is just not there for most things. And why on earth port cobol to win32? Why not use CA Realia or Microfocus. Lots of people here are talking out the side of their butt and have no real world experience in the matter.
What should happen with luggage?
What do you think they should do with the insane luggage tracking system? Anyone watching the Discovery channel can see just how unsophisticated it is, and how easy it is for a piece of luggage to temporarily go missing.
Less than 1% of luggage actually remains lost for over 60 days, so even though it is not in your possession there is an excellent chance that it will be found. Your luggage will not be considered officially lost (unsalvageable) until 90 days are up, at which time the airliner must declare the piece(s) lost in order to comply with FAA regulations. Unfortunately this process may drag a little, but at least people will be looking for it for a full 90 days.
Maybe a better system would prevent that lost period.
Re: What should happen with luggage?
Don’t confuse luggage tracking with luggage handling. It’s the mechanical/human luggage handling that loses most bags.
Also, the rate of lost bags is lower than the error rate of most programmers (defects per lines of code).
Sabre is moving to C++, MySQL, and UNIX
Actually, part of Sabre already runs on commodity OSes, languages, and DBMSes. http://www.techworld.com/opsys/features/index.cfm?featureid=1995
The article gives an indication of the benefits and drawbacks of the two platforms — mainframes have the reliability built-in at a high cost, commodity cluster solutions require software to manage the inherent unreliability.
The problem wasn’t the mainframe, it was the self service kiosk interfacing with the existing mainframe data. The problem is that 1) lack of testing by the kiosk installers prior to production… 2) the technical manager of USAIRways giving a GO decision, even with existing problems.
Mainframes have evolved just like PC and UNIX systems, but too many people have their preconceptions of what mainframe computing is like.
Mainframes have UNIX(for 12+ years), JAVA(10+ years), TCPIP(12+ years), can run Linux(7+ years), are web enabled… can be used as a server and as a client.
The issues are not the technology but the money. Management doesn’t want to spend money to modernize, unless they are forced too… Period. and who can blame them… What business value will be gained by spending $100M to migrate them off mainframes.
Also please note that many of the airlines are outsourced to EDS, a major advocate of the MMA. Even they aren’t going to spend that kind of money without some financial benefit.
It would also be interesting to see what people’s comments are on the Denver Airport’s baggage handling system. a UNIX cluster ‘state of the art’ system. It damaged baggages, wrongly routed baggage… and after two months it was declared FUBAR. Now Denver doesn’t have a ‘state of the art’ system. Is this what we want? Is this what you are suggesting.
You DO realize that mainframes are clustered computing… and have been for 30+ years….
NJE mainframe computing is the equivalent of homogenous grid computing…30+ years…
sysplex mainframe computing is the equivalent of heterogenous grid computing(about 20 years)
parallel sysplex computing(10+ years) has no equivalent in the midrange world, yet(HP is working on it).
Also, unlike the midrange world… alot of the mainframe software(applications, databases) can take advantage of this clustering out of the box, and is not a custom job.
Almost all mainframe business clients do keep their equipment up to date. IBM won’t support old machines or old OS systems. Any business that doesn’t keep their production on support hardware/software, is generally one that goes out of business. The technology you cite is from the 70s/80s, ask yourself if your Trash 80 could do anything nowadays-so let’s compare apples to apples, shall we… A z9 mainframe server, can generate up to 96 GB(that’s byte(BIG B)) of i/o throughput. … This is just one machine… imagine that clustered?
You may also want to keep yourself up to date. Virtual switch technology(where the mainframe has advantages(other platforms do have them, too)) can BYPASS those gigabit pipes. Data transfers at memory speed…Try that with traditional client/server.