Rogallo said:
And I see your point. Nothing wrong with wanting to protect what you've got.
But here's my argument. I get laid off in Tulsa after working 20 years as a mechanic. There are currently 150 vacancies in DFW for full time FSC's. I put in for a 12m transfer for a FSC position in DFW. If I were to get it why should I be considered a "new hire" and put at the bottom of the seniority list? Because I've never done that job before? My 20 years of seniority is all but null and void except for vacation. Why should someones seniority be discriminated against for changing jobs? Sorry, I don't buy into the "new hire" mentality.
That, in my opinion, is not right, and anti-union.
You just brought up what I think is the biggest sticking point between our two groups.
First, it's not "anti-union". Neither way of combining either occupational or classification seniority really is.
Second, I totally disagree with your argument. I guess because our side "has never done it that way".
In my example, I get laid off in PIT with 20 years as a Mechanic. There are 150 full time Fleet opening in PHL. I put in for a 12m (?) transfer for My Fleet Service position in PHL. When i get there I start out with 1 day of seniority. In fact, I start my 90 day probationary period again. Just like a new hire.
BUT........... I never lost any seniority in my former position as Mechanic. In fact, it continues to accrue. Now I have 2 different classification dates with one seniority date. And in my position as Fleet, my seniority won me the right to choose vacation over the guy next to me with only 19 years.
And...... (another touchy subject) .....until American Airlines came along, I could have used my 20 years as a Mechanic, and now 1 day as a Fleet Agent, to commute, and to get on the flight back home to PIT from PHL.... AHEAD.... of the guy with 19 years in Fleet sitting next to me.
How do combine these issues going forward?