3f PWS_FPAMS_20180716 v5.docx

PERFORMANCE WORK STATEMENT (PWS)

Flight Program Aircraft Management System (FPAMS)

July 16, 2018

Douglas Vaz, COR

Angel Taylor, CO

Table of Contents

Performance Work Statement July 16, 2018 , 2018 I

1 Introduction

1.1 Introduction

Flight Program Operations, Aircraft Maintenance and Engineering (AME) supports maintenance and engineering for Federal Aviation Administration (FAA) flight operations and other governmental agencies that operate aircraft across the U.S. and abroad. Aircraft based in Oklahoma City, OK; Atlantic City, N.J; Washington D.C.; Ft. Worth, TX; Atlanta, GA and Sacramento, CA. The fleet consists of 46 aircraft .Aircraft types include C-90 GTi; BE-200; BE-300; Challenger 600 Series; Lear 60; S-76a Helo; PA-31-350; BD-700. The flight hour consumption is expected to be approximately 18,000 flight hours annually.

The current Inventory Logistics & Maintenance (ILM) system currently used to track aircraft maintenance requirements (i.e. scheduled maintenance, unscheduled maintenance, labor usage and tracking, sign-off history, cost tracking, and document retention). In addition, the inventory, both in stock and installed on aircraft are tracked for base and field locations; purchases and overhauls for aircraft components and interface with operational systems are a part of the logistics support required. The solution must comply with applicable Federal Aviation Regulations listed in section 1.4 and have complete solutions for all aspects of providing maintenance support for a fleet of aircraft. The replacement system will be called the “Flight Program Aircraft Management Systems (FPAMS)”.

This award contains detailed requirements based on the operating methods in use with the current custom system. The FAA understands some of the current methods or procedures may change or vary depending on the solution. Each requirement s will be evaluated to determine of an alternate solution is compatible with our organization. Compatibility with current maintenance requirement intervals, work card management, and parts management is required. This project has a direct effect on FAA’s ability to provide aircraft operations services that support the National Airspace System (NAS) safety and the flying public.

1.2 Background

The current ILM system being used to track maintenance and logistic requirements is a legacy system and is becoming unsupportable. The legacy ILM system tracks maintenance and logistic requirements. The AME organization is dependent on this software for scheduling maintenance and tracking inventory needs. There is an urgent requirement to replace the legacy ILM system in order to continue operations without interruptions to services.

1.3 Objectives

The objective of this PWS is to outline the requirements for the Commercial Off The Self (COTS) application. The solution must meet the business and operational requirements associated with managing a fleet of aircraft in accordance with references in Section 1.4 and operational directives for the management of aircraft maintenance labor and associated inventory, parts and cost management.

1.4 Scope of Work

This PWS describes the scope of work required by the Contract. In summary, the Contractor must:

· Provide software licenses for Aircraft Management.

The Contractor shall provide user licenses for the application. AME estimates up to 300 licenses for the application. The application must provide the capability to manage a complex fleet of multiple aircraft types, in multiple locations. Software must provide the capability to track maintenance requirements, parts management, labor usage, software configuration and revision control, inventory and logistics management of parts and test equipment, aircraft modifications and routine and non-routine maintenance actions. The system must handle custom maintenance inspection programs.

· Provide maintenance of software.

The Contractor shall provide the correct updates to new versions, service packs, and patches to AME. In addition to maintenance of the COTS application, the contractor shall provide software maintenance for the current and future system modifications. Contractor shall provide technical support via phone, email, and on-site, depending on the requirements of the issue(s). The Contractor shall provide access to operational support 24 hours a day and 7 days a week. Most interaction with the FAA will be on Central Standard Time (CST).

· Provide customer within defined response times when technical problems arise. If modification is required, contractor shall negotiate a delivery time within five (5) business days of request. Deliveries should not exceed twenty (20) business days unless the complexity of the change required a longer delivery time and is agreed upon by AME.

· Provide consulting services (technical and functional) When requested, the Contractor shall provide the appropriate support personnel for consulting on system capabilities and AMEG requirements. The Contractor’s support personnel shall be knowledgeable in the area of the support application and able to answer technical questions and provide technical and functional support.

· Provide user and system administration training. Methods of training may be online or class-room environment. Provide training for up to twenty (20) users and five (5) system administrators.

· Complete tasks detailed in Section 2

· Provide deliverables listed in Section 3

· Meet all other requirements of this PWS and contract

· Target date for deployment of the system is October 1, 2019

· FedRAMP certification is desirable. Must be able to interface with Agency Personal Identity Verification (PIV) authentication system; (see https://www.fedramp.gov)

· Provide a system that handles unique maintenance interval requirements, work card processing and parts management.

· Provide electronic documentation options vs. hardcopy documentation

· Applicable Regulations and Guidance include:

· CFR14 FAR part 91

· CFR14 PAR Part 65

· CFR14 FAR Part 135

· CFR14 FAR Part 145

· 40 CFR Code of Federal Regulations: Protection of Environment

· 49 CFR Code of Federal Regulations: Hazardous Material Regulations as required by US Department of Transportation (DOT)

· HAZMAT (Transportation by ground) FAA Order 3900.21

· IATA International Air Transport Association – Dangerous Goods Regulation (HAZMAT Transportation by Air)

· JO 1050.1 Flight Program Environmental Program document

· JO 3900.1 Flight Program Occupational Safety and Health Program

· AC1600.78 Personal Identity Verification (PIV)

· AC43-216 Software Management During Aircraft Maintenance

· Airworthiness Directives

· Engineering Orders

· Advisory Circulars

· Manufacturer Requirements

· TI 4100.24 General Maintenance Manual (GMM)

1.5 Communication

The Contractor shall communicate technical exchanges with the FAA Contracting Officer (CO), Contracting Officer Representative (COR), or Subject Matter Expert (SME). Authorization for SMEs must come from CO or COR.

Technical Exchange report shall include (CDRL A003):

· Date Range of reporting period

· List open issues being worked with description and options for resolution

· Tasks accomplished and hours/cost expended or estimated to be expended on each issue Contractor shall provide a monthly help-desk usage report if costs are incurred. (CDRL A004):

· Date Range of reporting period

· List of help desk calls received with description and resolution or status if costs are incurred

· Tasks accomplished and hours/cost expended

2 Task Requirements The Contractor shall perform the activities outlined in this PWS. Unless otherwise specified, the activities under this contract shall be performed during normal business hours as defined by the Professional Services Order Form (6:00 a.m. – 6:00 p.m. U.S. Central Time). Any work requested outside normal business hours or on weekends and federal holidays will be subject to special rates/charges outlined in the contract. Contractor personnel travel requirements shall be determined on an as needed basis, approved in advance by the CO, in accordance with the contract.

2.1 Task 1 – Program Management Support

The Contractor shall conduct the tasks described in the following sections. The Contractor shall provide personnel to complete the tasks assigned. The Contractor shall assure that persons employed on this contract possess the required skills consistent with the job classifications for which they are employed.

2.1.1 Subtask 1.1 – Task Order Management

The Contractor shall provide program management support to ensure that identified tasks are performed within established target dates and in compliance with the requirements. The Contractor must participate as a member of a government-led team, as requested by the COR.

2.1.2 Subtask 1.2 – Monthly Financial Reports (CDRL A001)

When services are performed and/or delivered during a monthly billing period, the Contractor shall provide a Monthly Financial Report. Work description shall be aligned with the Contract Line Item Number (CLIN) structure. The reports shall be delivered to the COR.

2.1.3 Subtask 1.3– Monthly Operational Activity Report (CDRL A002) To ensure proper documentation of operational activity, a monthly report is required for the life of the service that reflects the aircraft maintenance activity in the reporting period. Report is due within the first ten (10) business days of the following month. The report shall be submitted in PDF format. (See example report attachment 1); Exact report formatting is negotiable, provided it contains the data needed to monitor workload activity. The COR. will approve report.

· Date Range of reporting period

· Aircraft Tail #/ Serial # and Model

· Date when work was performed

· Aircraft actual hours/landings/cycles as of a specific date

· Workload Description

· Labor category for each event/item

· Resource name for each event/item

2.2 Task 2 – Software Licenses

The Contractor shall provide user licenses for the application.

2.2.1 Subtask 2.1 – Annual Licenses

AME shall be able to add or delete licenses, as needed. The Contractor shall provide perpetual software licenses in the quantities requested by AME; estimated purchase is 300 licenses. AME shall have the option to purchase licenses for the entire product suite or only specific modules. AME shall retain the option to purchase additional product suites and modules.

2.3 Task 3 – Software Maintenance

The Contractor shall provide software maintenance for the software licenses specified by AMEG, including COTS software and any customization that may be required to meet FAA’s requirements. Software maintenance shall include, but is not limited to, the following:

2.3.1 Subtask 3.1 – Technical Support

The Contractor shall provide a technical support telephone number. The contractor shall be able to perform technical and operational support onsite or remotely. The Contractor shall maintain technical support personnel knowledgeable and experienced in commercial aviation that have a strong background in aircraft maintenance and logistics support. The support personnel shall be identified to AMEG and available for support via telephone and email.

2.3.2 Subtask 3.2 – Maintenance

The Contractor shall provide the correct updates to new versions, service packs, and patches to AME. In addition to maintenance of the COTS application, the contractor shall provide software maintenance for the current and future system modifications. All updates will be evaluated in a test environment before acceptance for production use.

2.3.3 Subtask 3.3 – Help Desk

The Contractor shall provide rights and access to the support center 24 hours a day and 7 days a week for AME to report new application software faults. The COR will report software faults. Cases will be tracked via reporting requirement CDRL 004. Upon case generation, the Contractor shall:

· Assist with case registration, where needed

· Assist the customer to determine the route to case acceptance for production use

· Search the knowledge database

· Start analysis of cases within 24 hours of reported issue

· Provide assistance to resolve the cases reported

· Provide a test environment for solution review before updates and patches are placed in production

· Provide the user link, direction or instructions for the individual user to accomplish it immediately.

2.3.4 Subtask 3.4 – Implementation Support

The Contractor shall provide a telephone number to assist in the installation and use of the software. The contractor shall supply a combination of onsite and remote support. Contractor shall:

· Provide technical support and assistance in the data migration process

· Provide technical support with any hosting and interface requirements

· Provide technical support with security, managing user roles and access methods

· Provide a test/training environment in addition to a production environment

2.3.5 Subtask 3.5 - Interfaces

The System shall interface with operational infrastructure for the management of dispatching aircraft and flight tracking of aircraft. This includes:

· Passing actual and Not Exceed flight hour, calendar and landing/cycle data

· Updating of flight hours as flights are dispatched and arrived in real time

· Handling cancelled and deleted flights

· Updating of airport identifier of base location and last known location

· Interface with FAA infrastructure for user authentication; Personal Identity Verification (PIV)

· Mechanism to audit and insert/delete/update records

· Mechanism to identify user entries including time stamps for all transactions

2.3.6 Subtask 3.6 – Hosting and Solution Configuration Management (CM)

The solution system replacing the legacy ILS must be a lasting system that is compatible with required agency interfaces and security requirements. User authentication must be compatible with agency PIV system.

User authentication must be compatible with Agency Personal Identification Verification (PIV) system.

2.4 Task 4 – Over and Above

2.4.1 Subtask 4.1 – Software Modifications

Future software modifications may be identified due to a change in requirements or lack of existing functionality in the application. The specific tasks, determined by AME, shall be assigned to the Contractor by the Contracting Officer (CO) using written descriptions. The contractor shall provide support personnel to assist with development of the requirements for the modification to ensure the result meets the AME requirements. Contractor shall provide training and technical support for the testing and use of the software modifications. The delivered system modifications shall be tested and meet the specifications outlined in the modification request in a test environment before being placed in production environment.

2.4.2 Subtask 4.3 – Consulting Services

When requested, the contractor shall provide the support personnel for consulting on system capabilities and AMEG requirements. The Contractor’s support personnel shall be knowledgeable in the subject matter.

The contractor shall provide any applicable training on the software modules purchased by AME. The contractor shall provide remote technical support for technical issues not covered under the maintenance agreement.

2.4.3 Subtask 4.4 – Migration Support

When requested, the contractor shall provide the support personnel for technical support of the AMEG migration of legacy data. The contractor shall provide support merging legacy databases into the new database. The minimum contractor personnel qualifications include:

· Understanding and experience with Structured Query Language (SQL)

· Software table structures

· Mapping of data from an external system

3 End Results/Deliverables The contractor must provide a software system and support services that successfully manage all aspects of an aircraft maintenance and engineering program and meets applicable Federal Aviation regulations. This section describes the products and tangible results expected from tasks contained in the previous section, the date each deliverable is due, and the government acceptance criteria. All days are business days, unless otherwise specified.

The Contractor shall provide deliverables that meet the requirements of the specific task. Contractor shall meet the task completion schedules and deliverable due dates required by AME. The Contractor shall submit deliverables to the COR and/or POC(s) designated by the COR.

For Contract Data Requirements List (CDRL) documentation deliverables, the Contractor shall submit documents by email in MS Word, Excel or PDF format.

A001 Program Management Support: Monthly Financial Reports

10th business day of the following month The Monthly Financial Reports (invoicing) are accurate, complete, submitted on time, in the FAA approved format, and is prepared in accordance with subtask 2.1.2 and AMS Clause 3.11-28 Contractor’s Invoices. Deliver reports to COR for acceptance and approval/disapproval.

4 Period of Performance

The Period of Performance will consist of one base year and four one-year option periods, for a total of five years.

5 Place of Performance Performance of contractor services are typically at the contractor’s facility; however, some services will require performance at the Mike Monroney Aeronautical Center (MMAC), in Oklahoma City, Oklahoma. Contractors will be escorted while on FAA facilities.

6 Transition/Close Out Plan All FAA security badges, if issued, shall be turned in to the COR by closeout of the Contract. Approximately four weeks prior to the Contract end date, the FAA will require the Contractor to provide the following:

· All documentation as of the most recent version

· A final status report that includes a projection of activities for the remainder of the Contract

· A closeout meeting with the FAA (details and participants to be determined by the FAA)

7 Other Direct Costs (ODCs) Contractor personnel may be required to travel away from the contractor’s facility, as requested by the FAA CO or COR. The CO shall approve in writing and in advance of each occurrence, all ODCs, including travel.

8 Government Furnished Property (GFP) If GFP is provided, all GFP must be returned to the FAA in accordance with this PWS, the Contract, or as requested by the FAA.

A-8 Performance Work Statement July 16 2018 , 2018 image1.png image2.jpeg