FDX-Reserve on VTO
#11
Banned
Joined APC: Mar 2009
Position: 757 Capt
Posts: 798
Raptor nailed it. I did notice that they answered that question in the TA Q and A section, and said that it remains the same as now, trips until they run out of them, so respecting seniority. But I'm still suspicious, though I feel better than I did about the issue before I read their answer.
Pipe
#12
Gets Weekends Off
Joined APC: Nov 2013
Posts: 2,756
I tend to jump to the worst possible scenario, but that may be on the extreme side.
#13
Stockholm syndrome. Our NC spends an inordinate amount of time with the Company NC and probably has grown to respect the guys on the other side of the table. After a while, they start believing these guys have integrity and can be taken for their word.
Trust, but verify.
Trust, but verify.
#14
Gets Weekends Off
Joined APC: Nov 2006
Position: 767 FO
Posts: 8,047
We asked for more control over our VTOs. We get more control over our VTOs. But the NC has stockholm syndrome? Read the SLR workgroup letter, I am not sure what else we could have asked for. In the end if we dont like it we can say no keep what we got.
#15
Banned
Joined APC: Mar 2009
Position: 757 Capt
Posts: 798
We have been arguing for weeks about what the TA really says. What does that say about the work done in the authorship of the document?
If you reach an understanding about intent during the negotiation, write an intent paragraph into the contract adjacent to contract clause. History shows that to be the only path to success with FDX. I am no longer interested in voting for what people "think" they agreed to. Those are nothing more than opinions. Trust is a thing of the past here.
Pipe
#16
How is it that the SLR programming with its language, preferences, penalties, was not developed during the last 4 years??? Why do we have to sign up for software, that seriously affects our QOL, when we have no idea on how it will be implemented? That's insane. Why does our MEC not have a say in the IMPLEMENTATION of the SLR? You should know the answer. This is PBS by another name. After 4 years of distraction with PBS across the board, this is what we got, the opening door to PBS with 20% of R-days system wide, added to it.
If the company's negotiators had instead used the 4 years to source a vendor for a replacement of the VTO (PBS 1.0) system, and had developed language, software, metrics, penalties, etc... during that time, instead of stalling and distracting, while CRS continued to creatively re-interpret un-optimized sections of our current CBA, we would be in a different position. And if the company had then began implementing a modern, working PBS 2.0 on the VTO lines, and we had a 4 year contract duration to further explore how it affects VTO lines, this would be a non-issue.
But, that's not the case. Instead, the company used PBS as a stalling tactic. They did not source PBS vendors for VTO lines, nor wrote language, nor limitations. Instead, they asked for 20% of R days added to VTO's, with zero language to date, and they are asking for YOUR TRUST, that the implementation of said PBS, I mean SLR, with zero MEC input in the implementation phase, will be a good thing for us as they use it to enhance productivity. Unfortunately, due to CRS efficiencies in the last few years, trust is lacking.
If the company's negotiators had instead used the 4 years to source a vendor for a replacement of the VTO (PBS 1.0) system, and had developed language, software, metrics, penalties, etc... during that time, instead of stalling and distracting, while CRS continued to creatively re-interpret un-optimized sections of our current CBA, we would be in a different position. And if the company had then began implementing a modern, working PBS 2.0 on the VTO lines, and we had a 4 year contract duration to further explore how it affects VTO lines, this would be a non-issue.
But, that's not the case. Instead, the company used PBS as a stalling tactic. They did not source PBS vendors for VTO lines, nor wrote language, nor limitations. Instead, they asked for 20% of R days added to VTO's, with zero language to date, and they are asking for YOUR TRUST, that the implementation of said PBS, I mean SLR, with zero MEC input in the implementation phase, will be a good thing for us as they use it to enhance productivity. Unfortunately, due to CRS efficiencies in the last few years, trust is lacking.
Last edited by CloudSailor; 10-01-2015 at 07:11 AM.
#17
I think it's worse than that ... during one of our previous contract negotiations (FPA maybe?), the union Negotiating Committee and the Management negotiators actually met at a church so that they could pray for a mutually agreeable agreement!*?
Are you ef-ing kidding me?
#18
Gets Weekends Off
Joined APC: Nov 2013
Posts: 2,756
I think it's worse than that ... during one of our previous contract negotiations (FPA maybe?), the union Negotiating Committee and the Management negotiators actually met at a church so that they could pray for a mutually agreeable agreement!*?
Are you ef-ing kidding me?
Are you ef-ing kidding me?
Thread
Thread Starter
Forum
Replies
Last Post