Any "Latest & Greatest" about Delta?
06-26-2010, 12:44 PM
Gets Weekends Off
Joined APC: Feb 2008
Position: Urban chicken rancher.
Posts: 6,070
Originally Posted by Carl Spackler
So much wrong in your post it's hard to know where to begin. First of all it's not "this is got to stop" it's "this has got to stop." But what is it you want to stop? The thread's resident published author goes off on a name calling intemperate rant, and you respond to Schwanker who posts a thoughtful response that has just one shot of opinion in the last sentence? But no response from you to the intemperate rant?
I'll take up the rest of your post in pieces.
Carl
I'll take up the rest of your post in pieces.
Carl
06-26-2010, 12:45 PM
Back on TDY
Joined APC: Apr 2008
Position: 747-400 Captain
Posts: 12,487
Originally Posted by DAL330drvr
Excellent Post! Give it up Carl, NWA is history now, I've let go, my paycheck says Delta on it! 
Or does it?
Carl
06-26-2010, 12:51 PM
Back on TDY
Joined APC: Apr 2008
Position: 747-400 Captain
Posts: 12,487
Originally Posted by acl65pilot
DAL330, it is not meant as a slap in the face. It is just the truth. If you want to change it, get involved and work on slow change.
Originally Posted by acl65pilot
As with all corporations the small and often unnoticeable change takes place over the next five years.
Carl
06-26-2010, 12:58 PM
Back on TDY
Joined APC: Apr 2008
Position: 747-400 Captain
Posts: 12,487
Originally Posted by alfaromeo
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.
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.
I do understand the concept of adopt and go. I'm now convinced that the error was in adopting and going with the fDAL IT stuff. But that ship has sailed. Now it's time for band aids.
Carl
06-26-2010, 01:01 PM
Back on TDY
Joined APC: Apr 2008
Position: 747-400 Captain
Posts: 12,487
Originally Posted by Schwanker
No Problem....shoot the messenger--same strategy as the White House. Concerns from those with a "fresh look" are being brushed aside. Mid level managers who also have these concerns are being replaced. It has nothing to do with avoiding change, it's about changing things for the better for the company and the pilots! If you prefer to needlessly **** away fuel and revenue because you are the survivor, have at it. I'd rather see additional profit margins and better compensation!
Very evolved thinking...isn't it.
Carl
06-26-2010, 01:03 PM
Gets Weekends Off
Joined APC: Sep 2005
Position: Retired 767 Captain
Posts: 548
Is there anything this guy doesn`t gripe about? He got a pay raise, he got to keep his pension, he still flies the 747. We need to introduce him to "Sky High" on the "other" forum. He must be a real pleasure to aviate with.
06-26-2010, 01:04 PM
ATL A320 B
Joined APC: Oct 2009
Position: No longer MEM or 9, but still a guy.
Posts: 238
This whole thing has degenerated into a useless thread that ought to be shut down. At least for me, I've had enough... goodbye.
06-26-2010, 01:05 PM
Back on TDY
Joined APC: Apr 2008
Position: 747-400 Captain
Posts: 12,487
Originally Posted by Carl Spackler
Really? NW was always last? You sure 'bout dat?
Carl
Carl
Originally Posted by firstmob
Give it a break Carl
Pleaseeeeeeeeee
Pleaseeeeeeeeee
Carl
06-26-2010, 01:06 PM
Back on TDY
Joined APC: Apr 2008
Position: 747-400 Captain
Posts: 12,487
Originally Posted by Schwanker
Not if you can't operate them profitably due to an inefficient/outdated operation. Some savy newcomer will come in and clean our pockets if we can't adapt.
Carl
06-26-2010, 01:11 PM
Back on TDY
Joined APC: Apr 2008
Position: 747-400 Captain
Posts: 12,487
Originally Posted by 1234
I am talking about the actual database structure and set-up. It isn't as simple as adding a few more subsets and datafields.
IT had to be an adopt and go strategy because you can't just make the two systems talk to each other (it would take nearly as long to do this as to just develop a new customized it backbone and reporting structure). I don't really like SAP, (very limited experience) and would prefer a customized wholly owned solution but this is very expensive to develop and maintain.
I agree that it is about usability and productivity and flight ops is not the only user of the system.
IT had to be an adopt and go strategy because you can't just make the two systems talk to each other (it would take nearly as long to do this as to just develop a new customized it backbone and reporting structure). I don't really like SAP, (very limited experience) and would prefer a customized wholly owned solution but this is very expensive to develop and maintain.
I agree that it is about usability and productivity and flight ops is not the only user of the system.
Carl
Thread
Thread Starter
Forum
Replies
Last Post
