When you write a corporate computer program, there are three elements, the back end database (DB1, SQL Server, Oracle, etc.) the front end user interface, and the middleware that connects the two. The back end is a given for each corporation and in this merger they had to choose one or the other, you can't really maintain two. The front end is relatively easy, there are many tools out there to put a pretty face on data and can be done with little time. The middleware is the hard part.

If you want to adapt NWA software to the DAL back end, you will have to rewrite the entire middleware package, which is the same as starting over in terms of manpower. That is why that even if NWA software front ends were better than DAL, it doesn't make much difference in terms of adapting the software. It is not like updating a Windows Vista application to run on Windows 7. It is not an upgrade, it is a complete rewrite.

In 2004-2007, Delta ran out of money and went bankrupt. Even coming out of bankruptcy, there were a lot of gaps to fill. They chose to invest more in customer centric issues like redoing the interiors and cleaning the planes. They also invested more in their people, on a relative basis. They did not invest as much in IT stuff for internal processes like scheduling, because it didn't affect the customer as much. So what if the schedulers uses pen and paper, as long as the trips get covered.

Everyone realizes there is more investment needed in IT here. I also have about 10 projects from my wife's to do list. When I get the time and money they will all eventually get done, just not tomorrow. Updates will come, just not tomorrow.