4.04.15b – (LAA/LUS) JNC Implementation Update

   

April 4, 2015

LAA / LUS
JCBA Implementation Update – [email protected]
As we draw closer to the conclusion of the first 120 days from Date of Signing (DOS), the Joint Negotiating Committee (JNC) Implementation Team would like to provide the membership with an update on where we are with the implementation of the provisions of the Joint Collective Bargaining Agreement (JCBA).
 
The implementation schedule was divided into two broad time periods—the first 120 days from DOS, and beyond the first 120 days—with certain provisions to be treated as priority items both by the Joint Scheduling Implemention Committee (JSIC), Sec.10.D.2., and the JNC implementation team.
 
Furthermore, in order to achieve the best possible value for our contract over the next five years and beyond, we staggered the implementation of economic items over the first few months following DOS. And we placed high priority on the implementation of compensation items (a subset of economic items) to deliver more money in Flight Attendants’ pockets as soon as possible.
 
Let’s take a look at the provisions that have been implemented or will be implemented by May 2^nd, 2015. In the following lists, you will notice that several provisions were already in effect at either LAA or LUS before DOS due to the “adopt-and-go” process used during negotiations. Still, the below lists show how LAA and LUS Flight Attendants are moving closer to being covered by the same provisions as they are implemented.
 
Sections implemented in their entirety:

• Seventeen (17) sections, including Crew Accommodations (Section 6) and Crew Rest (Section 38)

Some provisions implemented on DOS include:

• Red flagging (Critical Coverage) paid at 150% (Section 10.H.);
• Voluntary duty day waiver (Section 11.O.1. and Section 14.D.1.);
• Location delay incentive (Section 14.M.7.);
• Seniority accrual on leaves of absences (Section 25.N.); and,
• Duration and extension of medical leave (Section 25.E.)

Some provisions implemented following DOS:

• Wages (Section 3.);
• Holiday Pay (Section 3.E.);
• ATC Hold and Diversion Pay (Section 3.L.,M.);
• Per Diem (Section 4.A.);
• Sick bank increase from 1,000 to 1,500 hours (Section 9.C.2.);
• Elimination of 420-hour annual threshold to maintain Company-subsidized health benefits (Section 26);
• Minimum of six (6) months of salary pay continuance for injury on duty (Section 27.D.2.)
• Defined Contribution Plan (Section 26.G.);
• Crew Rest (Section 38); and,
• Training Pay for CQ classes (Section 29.E.)

Some provisions to be implemented on May 2, 2015:

• Purser/ Lead / Galley premium pay (Section 3)
• Elimination of purser requirement on certain flights (Section 14.L.)
• Holding Time (Section 3.D.)
• Understaffing (Section 3.E.)
• International Pay for all Mexico destinations (Section 2.X.)
• Per Diem, including for in-base training (Section 4.A.4.)
• JCBA vacation accrual rates (Section 8.A.1.)
• Sick Leave Cap removed and all trips eligible for sick pay, except Sick Make-Up (Section 9.A.)
• Training Pay (Section 29.E. )
• Sick and vacation accrual on a VLOA (Bid Leave) regardless of duration (Section 25.N.)

All remaining JCBA items will be implemented concurrently with PBS at LAA, or at *Flight Attendant Operational Integration (FOI), or as soon as practicable. Click here to view the most recent implementation schedule.
 
Implementation requires coordination with multiple departments such as Payroll, Crew Schedule, IT, Legal and Marketing—to name a few. Once each relevant department has established its role in the administration of a given provision and determined the procedures and resources necessary to fulfill its role, the implementation of that provision can move forward. Moreover, certain contractual provisions (such as work rules) require significant programming where one change may lead to multiple changes in multiple systems within a given crew management system. What may seem as a quick and simple programming change on the surface may not necessarily be the case.
 
Currently, LAA Flight Attendants work under FOS, while LUS Flight Attendants work under CAT CREW. Both legacy crew management systems require specialized resources; and, they have been competing for these limited resources with existing high priority IT projects, such as the combining of the domestic and international operations at LAA, the integration of the Passenger Service System as well as previous contract changes.
 
Even though the Company has established an IT team to focus on the programming of our JCBA provisions, APFA has expressed its frustration over management’s lack of resources, particularly the shortage of software engineers who are skilled in programming FOS. We will continue to stay on top of management to ensure all steps are being taken to increase AA’s programming resources. In fact, the JSIC will be part of the developmental process of all scheduling-related computer programs from beginning to end. In the meantime, the Company has engaged a third party – IBM – to plan and scope out the work for JCBA programming.
 
Our goal not only involves the quick implementation of a provision, but also the proper implementation of that provision. We want to make sure Flight Attendants reap the full intended benefits of a provision once it has been implemented.
 
Moving forward, we will continue to focus on the remaining as-soon-as-practicable items (e.g., 30/35/7, last live leg, double ups, 1 for 2 duty rigs, etc.). And simultaneously, the JSIC will be working on its own list of priority items, such as pay protections, implementation of the new Reserve system, Trip Trade System (TTS) as well as other provisions.
 
We encourage you to read the JCBA Hotlines for the latest information on implementation as well as explanations of the new provisions.
 
In Unity,
The JNC Implementation Team
 
*FOI is defined as the date on which LUS Flight Attendants migrate to the crew management system under a common scheduling platform covering all Flight Attendants of the JCBA.