Quote:
Originally Posted by Shazam
The codeshare wouldn't even start until late 2009. That's probably not enough time for the massively incompetent WJA IT folks to get it working.
Also, lost among all this hubub is that WJA's load factor went down. Smiles and jokes can't protect a company from macroeconomic factors.
|
I heard that particular job was outsourced. And if thats the case then good on WJ for getting out when costs started to skyrocket. Reminded me of an SAP article on CP a while ago about costs related to Waste Managements implementation.
Market wise WJA has very little to worry about compared to AC.
I am just surprised they partnered with the ugly sister when they were perfectly poised to exploit AA's union issues with 5th freedom flying. I will likely divest myself of 1/2 my current holdings. Keep the rest until I hear more of what this SWA arrangement is - my initial thinking is that it wont bring in the type of revenue the OW partnership would have.
If anyone has ever flown on an extended 3+ hour SWA flight and a WJA flight, they know there is a severe degrade in comfort from WJA to SWA.
The only thing that would save this deal for me would be if SWA used WJA as their ATA and had WJA fly 5th freedom flights via us ports.
Also, from someone who works in IT...
IT = hardware, backend (servers, email, networking etc), IS is programming so in fact it was the IS group who screwed up, not IT.