AA enters LAX -ATL
- Thread starter lpbrian
- Start date
eolesen
Veteran
- Joined
- Jul 23, 2003
- Messages
- 15,959
- Reaction score
- 9,374
DL's previous attempts failed largely because of control issues, not the underlying technology.
That's what Todd Spaude told us earlier this year without actually saying it verbatim. But, I'm sure you know better than Todd would...
Worldspan and Deltamatic are about as different as a Cadillac Escalade and a Chevy Tahoe. Branded differently, and some different features for the different markets they serve, but the really important stuff is identical.
I don't know where you learned about data mapping and migrations, but clearly, you weren't very good at it if you can't look past naming and/or ownership.
That's what Todd Spaude told us earlier this year without actually saying it verbatim. But, I'm sure you know better than Todd would...
Worldspan and Deltamatic are about as different as a Cadillac Escalade and a Chevy Tahoe. Branded differently, and some different features for the different markets they serve, but the really important stuff is identical.
I don't know where you learned about data mapping and migrations, but clearly, you weren't very good at it if you can't look past naming and/or ownership.
eolesen
Veteran
- Joined
- Jul 23, 2003
- Messages
- 15,959
- Reaction score
- 9,374
Yep, and I'm not sure why WT decided to start a "DL did a migration in 10 months... why can't AA?" pissing contest, which he's lost thoroughly and now has to start nitpicking semantics.jcw said:
I'm done. I've done data migrations and worked directly with every platformed used in North America with the exception of Navitaire, while he's only watched it from his kitchen table in his boxers...
WorldTraveler
Corn Field
- Joined
- Dec 5, 2003
- Messages
- 21,709
- Reaction score
- 10,662
yes, you are.
and why DL didn't have someone as smart as you to tell them that they could have kept NW's WSPN system and just slapped DL's software on it is beyond not only me but all of those people who actually run DL's IT systems.
and with all your experience, why has AA not bothered to merge the AA/US res systems? it's been 11 months already.
should have been done the day after the merger if we are to believe you.
eolesen
Veteran
- Joined
- Jul 23, 2003
- Messages
- 15,959
- Reaction score
- 9,374
You obviously didn't read the part where I said SHARES doesn't have the same IT DNA.WorldTraveler said:
Average PNR migration between disparate systems is 30 months. Between similar systems, it can be as short as a month.
Rather than cycle thru this a second (or third) time due to your lack of experience, maybe you should just go back four pages and start re-reading.
WorldTraveler
Corn Field
- Joined
- Dec 5, 2003
- Messages
- 21,709
- Reaction score
- 10,662
Oh, I read it fine alright.
You also missed the part about DL merging with a company that was compatible with it and gave it something of value instead of US which provided only a bunch of domestic presence and a lot of int'l presence which largely overlapped what AA already had.
net/net, AA gained very little strategically - in all kinds of regards.
DL/NW was a far better fit on far more levels.
including their nearly similar but not close enough to be called the same res systems.
You also missed the part about DL merging with a company that was compatible with it and gave it something of value instead of US which provided only a bunch of domestic presence and a lot of int'l presence which largely overlapped what AA already had.
net/net, AA gained very little strategically - in all kinds of regards.
DL/NW was a far better fit on far more levels.
including their nearly similar but not close enough to be called the same res systems.
WorldTraveler
Corn Field
- Joined
- Dec 5, 2003
- Messages
- 21,709
- Reaction score
- 10,662
the topic left LAX to ATL a long time ago.
funny you want a lock now.
if you are correct that DL and NW were the only two legacies that were merger partners that had legacy mainframe systems and that mainframe systems inherently provide greater compatibility, then DL had an advantage by choosing a merger partner with whom it could obtain revenue benefits far faster.
while you and I might get it, the vast majority of people on here likely don't realize that harmonizing the network, pricing, and O&D systems are all driven by commonality in the res system.
If AA has to wait 2 or 3 times what DL waited to get those revenue benefits, not only will the value of the merger be less but also the cost increases that came from AA's merger came much faster than the revenue benefits.
that is exactly what happened to UA.
the only reason why WN didn't see much of the same thing is because WN"s fares were so much higher than FL's so WN offset much of the cost of delaying integration by fare increases.
when you talk about adding routes like ATL-LAX, there will be no integration of the networks that AA and US operate on either end of that route. there may not need to be but when you look at routes like CLT-MIA or PHL-DFW, the inability to gain revenue benefits because of a joint res system is very significant.
