COO130 Flight Data SOW 7.23.20.pdf

Attachment A

Statement of Work

(SOW)

Information Technology (IT) Transportation Vetting System (TVS)

Worldwide Flight Data Subscription Services

I. INTRODUCTION

The Office of Information Technology (IT), Technology Solutions Division (TSD) is the component of the Transportation Security Administration (TSA) responsible for the development, implementation, operation and maintenance of a broad range of transportation vetting programs designed to protect the U. S.

transportation system against terrorism. Transportation Vetting System (TVS) is a mission critical system which operates 24 hours per day, 7 days a week.

II. BACKGROUND

The Transportation Vetting System (TVS) is a mission critical, national security system with a NIST 199 security categorization of: “HIGH” Confidentiality, “HIGH” Integrity, and “HIGH” Availability. TVS continuously (recurrently) vets approximately 21 million individuals in 39 populations occupying a position of "insider" trust against government watch lists. The system retains all subject and watch list records to perform recurrent vetting, a mechanism which immediately alerts users when record updates or additions cause system discovery of biographic matches. The worldwide scheduled flight data subscriptions improve the effectiveness of TSA’s biographic matching system and vetting capabilities.

III. SCOPE

TVS requires data for all scheduled commercial passenger and cargo flights, worldwide. The scope of this contract is limited to the flight data itself. TVS will ingest and process the flight data; therefore, software applications that provide flight data will not meet the technical requirements.

The Contractor shall provide the flight data in pipeline-delimited text files. Files shall be named consistently, and file names shall include the date of delivery. All data shall be updated weekly and files shall be posted to a Secure Hypertext Transfer Protocol (HTTPS) site, where they will be retrieved by TVS.

Flight data shall identify code sharing flights using International Air Transport Association IATA code standards where applicable.

The Contractor shall provide a notification procedure for reporting known data errors to TVS. The Contractor shall provide a notification procedure for planned and unplanned delays in data delivery.

Upon contract award, the COR and Contractor shall determine the date for initial file delivery and the schedule for weekly updates.

IV. TECHNICAL REQUIREMENTS

The contractor shall provide a full set of data on a weekly basis to, include the all of the following fields:

• Carrier

• Flight

• General Aircraft

• Specific Aircraft

• Depart Airport Code

• Depart City

• Depart Country

• Depart Date

• Depart Time

• Arrive Airport Code

• Arrive City

• Arrive Country

• Arrive Date

• Arrive Time

• Arrival Day Marker -- 1 for next day, 2 for 2 days later, p for previous day

• Intermediate Airport Code -- 3 letter IATA airport codes. Example: If there are 3 stops on route at Manchester, Glasgow and Aberdeen it would be represented as ‘MANGLAABZ’. There can only be up to 13 intermediate airports shown in this field.

• Full Route -- 3 letter IATA codes. Full routing provided for each sector of every flight. Example: BA 009 full routing is LHR BKK SYD MEL. This full routing will be shown as ‘LHRBKKSYDMEL’. The following 6 records should be provided: LHR - BKK BKK - SYD SYD - MEL LHR - SYD BKK

- MEL LHR - MEL

• Aircraft Change Flag -- Marker to show aircraft change on route

• Duplicate Flag – Indicates duplicate flights

• Duplicate Flight Numbers -- These are flights that are flown under a different carrier and Flight Number.

• Days of Operation -- 7-character field which contain spaces or any combination of numbers from 1 to 7 where 1 is Monday, 2 is Tuesday, etc.

Example: If a given flight only flies on Tuesdays and Thursdays this field would be populated with " 2 4 ". Or, if a flight flies every day it would be populated with "1234567".

• Effective Dates – Fields work in concert with Duplicate Flight Numbers to indicate when flights are active on the schedule.

V. DELIVERABLES

All data files must be provided to TSA by Secure File Transfer Protocol (SFTP) site. The documentation shall be delivered in file format (WDF format) – and the documentation shall explain the content of each field. TSA will retrieve the data files from the vendor's Secure Hypertext Transfer Protocol (HTTPS) site.

Government must be provided access to the HTTPS site and data files must be initially available for download by the date determined between the COR and the Contractor (within 14 days of contract award).

Help Desk support shall be provided via email and phone. Help Desk support shall be available Monday through Friday 8:00 a.m. through 5:00 p.m. Mountain Time (MT).

VI. PERIOD OF PERFORMANCE

The Period of Performance is twelve (12) month base year, plus four (4) one (1) year option periods.

VII. GOVERNMENT POINTS OF CONTACTS

Contracting Officer Representative (COR) Name: Crystal Davis Phone: (240) 568-5627 E-Mail: Crystal.Davis1@tsa.dhs.gov

IT Specialist, Information Technology (IT) / Technology Solutions Division (TSD) / Transportation Vetting System Name: Nikki (Rykiel) Zavatti Phone: (719) 327-6087

E-Mail: Nikole.Rykiel@tsa.dhs.gov