Systemwide PPU
08-15-2018 | 02:09 PM
#43
Gets Weekends Off
Joined: Mar 2006
Posts: 5,213
Likes: 14
From: guppy CA
This thread is hilarious. For those able to cash in, make hay while the sun shines. I haven't been able to participate; my BES doesn't have undermanning issues. Glad to see some are cashing in; hopefully they're not wasting the money.
Here's a good pilot investment
(caution; crude language): https://www.youtube.com/watch?v=R7yfISlGLNU
So where are those AMR pilots now who said that Scott Kirby was going to eliminate premium pay???? I've never seen this many PP trips at United. Hopefully summer 2019 will be a repeat.
Here's a good pilot investment
(caution; crude language): https://www.youtube.com/watch?v=R7yfISlGLNUSo where are those AMR pilots now who said that Scott Kirby was going to eliminate premium pay???? I've never seen this many PP trips at United. Hopefully summer 2019 will be a repeat.
08-25-2018 | 06:39 PM
#45
Line Holder
Joined: May 2012
Posts: 317
Likes: 1
From: CAP A320
VDO pay is a mess Pilots unaware of pay error
1. The schedulers have to MANUALLY load premium pay for each flight segment and DH. The introduces all sorts of errors. The first issue is when the hours total to less than 5 hours for the day. Some schedulers do not know how to manually code for Min5D to ensure you get at least 2.5 hours of add pay for those days.
2. The system does not automatically update on it's own for VDO pay errors. I have four trips with errors with one starting on the first day of the AUG work month, and they promised it would correct on it's own in "a few days", just like the other 3. I purposely waited to see if any would correct. Nope.
3. Here is a biggie for VDO. If you have any changes to your pairing, ie. Version A, B, C, etc. the scheduler has to manually recode for the add pay. Again, errors where they don't do it. You have to tell the scheduler when the pairing change occurs, to ensure it gets recoded. This can happen for example, when you do a fake DH. So not only does the scheduler have to remember to recode, then you have to hope you have one, that knows how to ensure you get the Min5D.
4. I've talked to several Scheduling supervisors and they are frustrated with having everyone manually input. And they admit not everyone knows how to do it correctly. I"ve been getting pushback from some schedulers that say they don't know how to do the soft time for Min5D. It's beyond ridiculous.
Lastly, PDR this. I'm writing a big one up to ALPA. ALPA put out a bulletin about PPU errors with wrong pay calculations. They need to understand about the VDO situation and put out another bulletin about this.
08-26-2018 | 07:03 AM
#47
Banned
Joined: May 2017
Posts: 320
Likes: 0
From: CA
This is absolutely incorrect. The issue with VDOs are the following:
1. The schedulers have to MANUALLY load premium pay for each flight segment and DH. The introduces all sorts of errors. The first issue is when the hours total to less than 5 hours for the day. Some schedulers do not know how to manually code for Min5D to ensure you get at least 2.5 hours of add pay for those days.
2. The system does not automatically update on it's own for VDO pay errors. I have four trips with errors with one starting on the first day of the AUG work month, and they promised it would correct on it's own in "a few days", just like the other 3. I purposely waited to see if any would correct. Nope.
3. Here is a biggie for VDO. If you have any changes to your pairing, ie. Version A, B, C, etc. the scheduler has to manually recode for the add pay. Again, errors where they don't do it. You have to tell the scheduler when the pairing change occurs, to ensure it gets recoded. This can happen for example, when you do a fake DH. So not only does the scheduler have to remember to recode, then you have to hope you have one, that knows how to ensure you get the Min5D.
4. I've talked to several Scheduling supervisors and they are frustrated with having everyone manually input. And they admit not everyone knows how to do it correctly. I"ve been getting pushback from some schedulers that say they don't know how to do the soft time for Min5D. It's beyond ridiculous.
Lastly, PDR this. I'm writing a big one up to ALPA. ALPA put out a bulletin about PPU errors with wrong pay calculations. They need to understand about the VDO situation and put out another bulletin about this.
1. The schedulers have to MANUALLY load premium pay for each flight segment and DH. The introduces all sorts of errors. The first issue is when the hours total to less than 5 hours for the day. Some schedulers do not know how to manually code for Min5D to ensure you get at least 2.5 hours of add pay for those days.
2. The system does not automatically update on it's own for VDO pay errors. I have four trips with errors with one starting on the first day of the AUG work month, and they promised it would correct on it's own in "a few days", just like the other 3. I purposely waited to see if any would correct. Nope.
3. Here is a biggie for VDO. If you have any changes to your pairing, ie. Version A, B, C, etc. the scheduler has to manually recode for the add pay. Again, errors where they don't do it. You have to tell the scheduler when the pairing change occurs, to ensure it gets recoded. This can happen for example, when you do a fake DH. So not only does the scheduler have to remember to recode, then you have to hope you have one, that knows how to ensure you get the Min5D.
4. I've talked to several Scheduling supervisors and they are frustrated with having everyone manually input. And they admit not everyone knows how to do it correctly. I"ve been getting pushback from some schedulers that say they don't know how to do the soft time for Min5D. It's beyond ridiculous.
Lastly, PDR this. I'm writing a big one up to ALPA. ALPA put out a bulletin about PPU errors with wrong pay calculations. They need to understand about the VDO situation and put out another bulletin about this.
Chill, bro This is not “Absolutely Incorrect” I have in fact had schedulers code it correctly where reassignment have triggered changes in pay and it’s taken a day or two for my Master Sched or pay register to reflect it correctly. Take a breath and relax, just screen shot the old and new assignment and keep tabs on your pay. No biggie
08-26-2018 | 09:06 AM
#48
Line Holder
Joined: May 2012
Posts: 317
Likes: 1
From: CAP A320
Chill, bro This is not “Absolutely Incorrect” I have in fact had schedulers code it correctly where reassignment have triggered changes in pay and it’s taken a day or two for my Master Sched or pay register to reflect it correctly. Take a breath and relax, just screen shot the old and new assignment and keep tabs on your pay. No biggie
And no, I'm not going to relax when the company has been repeatedly failing at paying us properly for 6 years. But you go ahead and relax and play the company's game.
08-27-2018 | 05:36 AM
#50
Banned
Joined: May 2017
Posts: 320
Likes: 0
From: CA
That's where you are out to lunch. Really, you agree with the process that pilots still need to monitor their paycheck with any changes to their schedule?! We should take snapshots prior and after and keep tabs on our pay?! You are part of the problem. This is not okay. We need to PDR this and this has to stop from the company for any of our pay issues. This should be easily coded into the software. I love the fact, when one person says, "well it worked for me" should cover everyone else, when there is a known issue of pay errors. Just like the guy that says, "My PPU auto paid me correctly", so not sure why the ALPA bulletin on the PPU errors are being looked at.
And no, I'm not going to relax when the company has been repeatedly failing at paying us properly for 6 years. But you go ahead and relax and play the company's game.
And no, I'm not going to relax when the company has been repeatedly failing at paying us properly for 6 years. But you go ahead and relax and play the company's game.
Thread
Thread Starter
Forum
Replies
Last Post
