Attachment 02 - SOW.pdf

STATEMENT OF WORK

1. INTRODUCTION AND OVERVIEW

This task related statement of work (SOW) is for aviation sector information technology (IT) data services for use in the FAA.gov Internet/Intranet Web operations environment.

1.1. BACKGROUND

The Office of Accident Investigation and Prevention (AVP) has a requirement for data and metrics on the global civil aviation fleet characteristics, history, and activities. This data is used to understand the aviation environment, for accident and event analysis, and to support the maintenance of safety metrics. This task will provide for this data to be through a data feed from a commercial Vendor to AVP via the FAA Enterprise Information Management (EIM) environment.

1.2. SCOPE OF WORK

The FAA requires data on the global civil aircraft fleet to inform safety work. This data is part of analytical systems that utilize and combine information from a variety of sources to provide visualizations and metrics. It is also used as part of system and safety research and analysis, including incident and accident investigations. The task is for the Vendor to provide predetermined data elements to the FAA via the FAA’s EIM Platform for use with FAA analytical tools and systems including, but not limited to, the Aviation Safety Information Analysis and Sharing (ASIAS) and Analyze Safety Performance Insight Results Environment (ASPIRE) tool sets. FAA personnel must also have access to Vendor applications such as web apps that allow for the FAA to make direct queries and conduct research on its own outside of the delivery of the required data. The required data must be provided on at least a daily basis via a direct API (Application Programming Interface) connection to the Enterprise Information Management Platform (EIM) or through a data exchange technology such as FTP (File Transfer Protocol). The data must be in a structure and format that allows for direct connection and import to analytical tools used by the FAA. Data must be provided with primary key fields associated with each table and record to allow for complex data fusion and integration between the Vendors data and FAA data. The data structure and sources must be documented and validated by the Vendor and the FAA periodically. The data feed must be reliably available to the FAA outside of occasional periods for maintenance and other factors that are conveyed to the FAA in advance of any such interruption.

1.3. OBJECTIVES

The following are the specific objectives of this requirement:

1. To provide required data elements to the FAA.

2. To provide access to data through either an API or Secure File Transfer Protocol (to include SFTP, FTP or FTPS) for the EIM team and enable data accessibility for users.

3. To serve the data needs of several aviation safety organizations.

4. To ensure validity of data sources.

5. To define and document all data definitions.

6. To deliver data daily to end users.

7. To ensure the FAA can quickly research and deliver information via Vendor portal and/or web apps in support of short turn actions.

8. To enable the FAA to fuse and integrate data provided by the Vendor with other FAA data sets.

2. REFERENCES

2.1. REGULATORY AND STATUTORY REQUIREMENTS

Regulatory and Statutory Requirements relative to the FAA’s Internet and Intranet include but are not limited to:

1. The Clinger-Cohen Act, February 10, 1996

2. The Computer Security Act of 1987

3. The Privacy Act as Amended (PL 93-5795 latest amendment), January 5, 1999

4. The Paperwork Reduction Act of 1995

5. Government Paperwork Elimination Act (GPEA)

6. The Electronic Freedom of Information Act (e-FOIA) Amendments of 1996

7. The E Government Act of 2002

8. Applicable Federal Information Processing Standards (FIPS)

9. Section 508 of the Rehabilitation Act (29 U.S.C. 794d), as amended by the Workforce Investment Act of 1998 (P.L. 105-220), August 7, 1998

10. OMB Section 515 of the Treasury and General Government Appropriations Act for Fiscal Year 2001 (Public Law 106-554; H.R. 5658), Information Quality Guidelines

11. OMB Circular A-123

12. OMB Circular A-130

13. OMB Privacy Policies for Federal Web Sites (OMB Memo 99-18), June 2, 1999

14. Instructions for complying with President's Memo "Privacy and Personal Information in Federal Records" (OMB Memo 99-05), January 7, 1999

15. Guidance on Inter-Agency Sharing of Personal Data-Protecting Personal Privacy (OMB Memo 01-05), December 20, 2000

16. Children's On-Line Privacy Protection Act (COPPA) of 1998

2.2. DOT AND FAA POLICIES AND ORDERS

DOT and FAA polices and orders relative to the Agency’s Internet and Intranet include, but are not limited to:

1. DOT Internet Policy (DOT H 1350.2)

2. FAA Internet and Intranet policies and orders (e.g., Password Administration Notice (1370.38)

3. Internet Access Points Policy (1370.83)

4. Internet Services Policy (1370.84))

5. FAA Information Systems Security policies and orders (e.g., ISS Program Policy (1370.82))

6. FAA Web Management Order (1370.93), August 17, 2004 https://employees.faa.gov/library/web/web_guide/order/media/ND1370-93.doc

3. REQUIRED ELEMENTS FOR ALL DATA AND DELIVERABLES

3.1. METADATA

The Vendor must provide the FAA with information on the structure, origin, and quality of data provided to the FAA. The Vendor must document the sources of the data provided to the FAA. The Vendor must explain the process by which the quality of the data is maintained. This Meta Data must be delivered upon award and at the commencement of any options exercised.

3.2. DATA FIELDS

The Vendor must provide the required data through the FAA’s EIM platform for use by the ASPIRE and ASIAS tool sets and FAA’s AVP and Aircraft Certification Services

(AIR). The data must be accessed via Application Programming Interface (API) to allow for direct daily updates. The EIM platform will directly access the Vendor’s data though the API and serve this data to authorized FAA applications.

3.3. COMPOSITION AND DELIVERY OF DATA

For each set of data identified in the Deliverables Table in Section 3.6 below, the following elements must be satisfied:

# Title Requirement 1 Territory Must cover the global fleet, world-wide, NOT only the U.S.

2 Aircraft Covered Must cover all fixed wing aircraft and turbine helicopters, excluding purpose built Military types.

3 Status

Definitions The Vendor must describe status definitions such as: ‘Current’:

Current refers to the ‘situation’ as of the date of data extraction, commonly referred to as ‘today’ as opposed to the ‘situation’ at an event date. ‘New’: The ‘next’ aircraft history event which occurs subsequent to the ‘today’ event. ‘Old’: The ‘previous’ aircraft history event which occurs prior to the ‘today’ Event.

4 API Delivery The Vendor must provide data through an Application Programming Interface (API).

5 EIM Connection The Vendor must provide all contracted data/info to the FAA Enterprise Information Management Platform (EIM) for use by enterprise via the API.

6 ASIAS Portal The Vendor must grant access to data via a dedicated launch page on the FAA's ASIAS portal, using a secured hyperlink imbedded on the launch page. Access to this page will be restricted to authorized FAA employees, ASIAS users, and approved contractors acting solely on the FAA’s behalf, solely for the purposes of FAA related research and analysis.

7 WAAS Portal The Vendor must provide accident data to FAA's EIM portal for use in the World Aircraft Accident Summary (WAAS) - Subset and be made available for public search and export.

8 Vendor Portal Access

The Vendor must provide authorized FAA users with access to the Vendor’s portal for accessing and query of data directly from the Vendor’s software or web application.

9 Availability The Vendor must provide reliable Services to Subscribers and Authorized Users excluding downtime for regular or emergency maintenance which shall be kept to a minimum. The Vendor must notify the FAA within 1 business day of any current outages. The Vendor must provide the FAA with a minimum of 1 business day notification of any planned outages.

10 Data Format The Vendor must provide data in a format suitable for large file size bulk data purposes (e.g. csv. format).

11 Key level Data The Vendor must provide data with associated primary key identifiers to allow for complex data fusion and integration.

12 Field Definitions The Vendor must provide a directory of all available fields (including, but not limited to, the required fields) and the definition of those fields.

3.4. NEW DATA SETS

The Vendor may work with the FAA to review new data needs when the FAA or the Vendor identifies that new capabilities are required or available.

3.5. FREQUENCY OF DATA DELIVERY

The data in the Deliverables table in Section 3.6 must be delivered on a DAILY basis.

3.6. DELIVERABLES

# Title Requirement 1 Flight Data The Vendor must provide flight hour and cycle information on a daily basis by type, aggregated and including but not limited to:

aircraft type code/name, year/quarter of data, operator, fleet size and value, years/age, service years, flight hours, landings, accident /loss info by date, passenger and others onboard/fatalities/injuries by type of event, loss value. Data must go back as far as possible, but at a minimum from 1960 to the present.

2 Loss Data The Vendor must provide Loss/accident data on a daily basis including but not limited to: date, environmental/light/weather conditions, manufacturer/nationality, type/variant, class/type, registration/tail number, serial numbers, engine make/model/series, type, operator category/name/nationality, service type, owner/operator, accident location/country/associated airport, phase of flight, fatalities/injuries onboard and on ground.

cumulative hours/cycles at accident, detailed event information. This data must be provided at the per aircraft level and not aggregated. Data must go back as far as possible, but at a minimum from 1960 to the present.

3 Track Data The Vendor must provide daily track data on a daily basis including but not limited to: unique flight ID, date, designator, aircraft ID, aircraft and engine family/type/serial number, departure/arrival airport name/IATA and ICAO codes/ terminal/gate scheduled and actual, date and UTC departure and arrival, runway departure and arrival, tracked flight time, nautical miles, number of seats. This data must be provided at the per aircraft level and not aggregated. Data must go back as far as possible, but at a minimum from 2020 to the present.

4 Fleet Histories The Vendor must provide daily data on Fleet Histories. All published aircraft status will be included, including but not limited to: ‘Cancelled’, ‘Type Swap’, ‘Retired’, ‘Written Off’, ‘In Service’, ‘Storage’, as well as Orders and options including letters of Intent (LOIs). This data must be provided at the per aircraft level and not aggregated. Data must go back as far as possible, but at a minimum from 1950 to the present.

5 Fleet Data The Vendor must provide daily data on current fleets including, but not limited to: cargo door configuration, class and type, dimensions, manufactures, usage and category codes, market values, accidents data by event/phase of flight/type of service, companies with contact details, airports, countries, engine manufactures/variants/types/specifications, status, generation, weights/capacities/seating, individual aircraft histories, hush kits, historical utilization, build/delivery/order dates, operators, airline info, events and event types, registration info, block/fleet/line number, type certificate holders, Make/model/series/variant, hours/cycles, average flight time, current and past regions/countries/states of operations and operators, storage and conversion locations, APU manufacturer/Type/Series, age, status, owners, age at retirement, build location/ICAO/IATA codes, owner and lessor info, market sector and class, Fuel capacity, payload mass and volume, noise class. This data must be provided at the per aircraft level and not aggregated. Data must go back as far as possible, but at a minimum from 1950 to the present.

Upon award of the contract, the Vendor will work with the FAA EIM Team to coordinate the initiation of required data feeds to the FAA's Enterprise Information Management platform. The FAA’s Information Technology organization will provide necessary instructions to the Vendor to connect to the EIM platform. The primary source for FAA authorized FAA users will be through this EIM platform. Within 30 days of the contract initiation the Vendor must provide information on data sources, validity definitions and directories.

3.7. ACCESS

Access to the data in Section 3.6 will be granted to authorized FAA employees and approved contractors acting on the FAA’s behalf. Vendor must allow the FAA to change authorized users when requested. In addition, authorized users must have access to the Vendor’s application or web application to allow for direct access of the Vendor’s data through such application or web application. The FAA will ensure that only authorized users have access to the Vendor’s data.

The Vendor and the FAA will communicate as necessary to discuss any issues with data products.

4. PERIOD OF PERFORMANCE

Base year: April 1, 2024, to March 31, 2025.

Option Year 1: April 1, 2025, to March 31, 2026 Option Year 2: April 1, 2026, to March 31, 2027 Option Year 3: April 1, 2027, to March 31, 2028 Option Year 4: April 1, 2028, to March 31, 2029

5. PLACE OF PERFORMANCE

Place of Performance will be at the Contractor’s facility. No physical access to FAA facilities is required.