I'm a Beta tester. There are some issues outstanding. The developer and CS are actively working on resolving the problems. I'd say we're pretty much where a medium scale realtime IT system implementation should be at this point in its lifecycle. It won't be long.
/PL

^^^^^^this. It also wouldn’t be that hard to have a dedicated scheduler for each base during an IROP so that a pilot with an MSP question doesn’t have to wait 5 hours to get an answer for an OT pickup when NYC is crapping itself for the 12th time of the month.

Not trying to be snarky....but why tell somebody to go to a hotel when the reservation isn't even made yet? There were eight rooms in this hotel left in a market with dozens of flights cancelliing. The crew had 11 hours left until report for the flight the following morning. Seems like you may want to be sure of what you're telling them to do before you have to start wrecking the next days schedule before the ink is wet on it. Thankfully they held the rooms for us knowing I was on hold waiting to get it fixed.

Indeed. It seems negligent to allow your operation to implode because you will not spend a trivial amount of money on extra schedulers when they are needed. This sort of carelessness should not continue for months and years, and when it does, it undermines the culture, the leadership, and everything the leadership says. You have to acknowledge your weakness and address it; thats exactly what we do with FOQA, for example.

The biggest issue I see is that many things require multiple calls. 5 calls yesterday over 7 hours to get a hotel. And this was on a non-irop day.

So frustrating. I am the only one that gave no effs. Delayed deadhead, which caused a misconnect so I just booked it home and took my chances. To now, I still have no notifications or schedule modifications and that trip ended yesterday. All I care is that rainmaker is accurate and it is.

Agreed...nothing but a big arse damn failure. It’s pathetic that we continue down this path. How can you keep your employees on the phone for two damn hours? Managament /ALPA needs to address this yesteryear

thanks again for previous answers. its not an easy decision to give up earned seniority and start over at another airline. I don't think it will be all sunshine and roses at 9E but the following questions might give some more insight...

when does pay start at 9E ? door closed or wheel movement ?

do you need to carefully audit your paycheck every pay period ?

do you need to submit pay claims for overtime, holiday, etc etc ?

if you find an error in pay beyond XX days time are you forever screwed out of that pay ?

never used PBS how is it overall for bottom middle and top 1/3 ? is it like I've heard top 1/3 gets 18 days off a month and 90 credit and bottom 2/3 gets 11 days off and 80 hours credit ?

trips commutable? avg day credit ? ya'll have min day or trip/duty rigs ?

what mechanisms are in place if you want to trade out of a trip or just plain drop a trip? (we have schedule adjustment, seniority based and first come first serve...) how often are you able to actually trade (need green days I assume?)?

reading through the last few pages doesn't seem hotels/schedulers are much better

appreciate any feed back, like said its not an easy decision to give up earned seniority...

see above in the quote

Here ya go...