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.