Get Over It Already
Member
- Aug 20, 2002
- 83
- 1
if it is the same website used to CS for someone in ORD or JFK then how can the policy be different? aa is too cheap to have different software
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Actually that is what is happening....Overspeed said:What do people want? To work more than 16 hours two days in a row and work on aircraft?
.............. a lot.MetalMover said:Actually that is what is happening....
Yes.Overspeed said:So the TWU stood up for leaving the interpretation of 121.377 the way it is and people threw rocks saying it prevented more hiring of AMTs. Now the arguments I see here are that restricting CS'ing would prevent people from commuting. What do people want? To work more than 16 hours two days in a row and work on aircraft?
When we were designing rules for StaffAdmin, we discussed flagging and even inhibit CS's where a max number of hours worked within a 24 hour period would be exceeded. I was for it, since someone who has worked three days of back to back's is not only worthless by the third day, but they start to become a safety hazard.Overspeed said:So the TWU stood up for leaving the interpretation of 121.377 the way it is and people threw rocks saying it prevented more hiring of AMTs. Now the arguments I see here are that restricting CS'ing would prevent people from commuting. What do people want? To work more than 16 hours two days in a row and work on aircraft?
That was changed in 2011 when a system wide CS policy was written for Fleet and Agents. The original committe was made up of TWU reps, management, AAB, agents, clerks, CC's, and HDQ people under Delvalle. At the second meeting Tim Guilespie got his panties in a wad and after throwing a temper tantrum ordered all the TWU people to leave the meeting. It continued anyway and the current systemwide CS policy went into affect in June of that year. It may have it's flaws, but it is at least consistent with minor flexibility allowed for stations to be more or less restrictive to a small degree regarding overlaps and advance notice.eolesen said:It never got implemented, partly because as we dug into the weeds, we couldn't guarantee the accuracy since CSW's and CSO's weren't always logged at the same time unless it was a straight swap. But both the TWU guys and field management were adamant that we not touch it.
Bob Owens said:What does the US/IAM CS language say that you object to?
In negotiations we were using the CO/IBT language but we didn't get far with it. Don only let it in as a delaying tactic.
The problem is as has been pointed out that if you don't have it in the contract the company can change it. You may have a good CS policy in ORD but NY may not. Same company, different station, different rules depending on management. Ours is a carry over from Cobbett (R.I.P) who was about as vindictive as they come. Yes there have been improvements since his departure but its still better to have minimums in the contract, putting in the contract does not limit improvements as long as they are applied equally.
Fleet ServiceAre you speaking on behalf of fleet service or A/C Maint?