Attachment J005 - Sample Problem Scenario.pdf

Enterprise Financial Services (EFS)

DTFAWA-17-R-00017

Attachment J005 – Sample Problem Scenario

FAA’s aircraft hygiene technicians are critical to meeting FAA’s mission of keeping the United States’ aerospace system safe and efficient. They use specialized equipment and possess skills that are difficult to attain. Federal safety regulations require that a certain number of aircraft hygiene technicians be on duty at a given time at every facility in order to ensure that aircraft are clean. The regulations further require that aircraft hygiene technicians be certified to operate various pieces of equipment and perform certain functions. The aircraft hygiene technicians are represented by a union whose objective is to advocate for the technicians. The FAA and the union are currently operating under a collective bargaining agreement (CBA) signed in 2012, which has a five-year term. The CBA covers a wide variety of topics. Importantly for this scenario, the CBA specifies:

• How many hours the technicians are expected to work in a shift;

• How may breaks technicians are entitled to in a shift;

• What on the job training technicians are entitled and/or required to participate in;

• The amount and types of leave technicians are entitled to;

• When and whether technicians need to be available “on call” to work;

• Overtime – premium pay rates, who is permitted to work it, who has right of first refusal; to turn down hours, when it can be required.

Since 2003, FAA management has used a system called CLN MCHN for shift management. This system allows FAA mangers to develop monthly work schedules, develop “on call” schedules, assign technicians to various functions within a shift, and ensure coverage of all functions and all equipment by an adequate number of technicians within a given shift. CLN MCHN interfaces with a number of FAA systems, including its financial system, and its learning management system.

CLN MCHN is housed on servers that are going end of life in February of 2019. After that point, the original equipment manufacturer will not provide any support for the equipment. Moreover, the system was programmed using Microsoft’s Visual Basic in a Windows XP environment, which is no longer supported on FAA’s Windows platform. Because Microsoft no longer supports Windows XP, FAA can no longer make any changes to the CLN MCHN source code.

FAA is trying to develop a prototype a system to replace CLN MCHN. If the prototype works well, the plan is to roll it out nationwide (in 270 facilities) prior to January of 2019. Beyond replacing current functionality, FAA management wants to make the system better. Notably, FAA management wants the successor system to interface with the FAA’s timekeeping system and allow system users to access it remotely from a variety of devices.

Because work schedules and timekeeping are closely related to the CBA, FAA leadership signed a memorandum of understanding (MOU) with the union. Under the MOU, management is the system owner, but the union has the right approve/disapprove system requirements. If the system does not provide for all of the rights specified by the CBA, the technicians will not be obligated to use the system.

Your company has been issued a hypothetical task order under EFS to:

• Support the development of requirements for the prototype system.

• Develop the prototype system.

• Support the transition of development, enhancement, and sustainment efforts to a successor contractor

(full lifecycle support is not in scope of EFS).

Enterprise Financial Services (EFS)

DTFAWA-17-R-00017

• Support the nation-wide roll-out of the actual production system. Support includes the development and delivery of training for end users as well as general program management support.

The period of performance for the hypothetical task order is September 27, 2017 through March 30, 2019. By the end of the period of performance, the objective is to have a production system deployed and fully operational nationwide.