SOW_attachment_1March_23.pdf

PDF 186 KB Posted

Attached to
WORLDWIDE FLIGHT DATA Federal contract opportunity
Solicitation number
HSTS02-15-Q-OIA095A
Issued by
Department of Homeland Security Transportation Security Administration

About this file

ATTACHMENT_1 SOW

View the file

Other files for this federal contract opportunity

Other files attached to WORLDWIDE FLIGHT DATA, newest first.
File Type Posted
HSTS02-15-Q-OIA095A_Questions_-RESPONSE.pdf PDF
Combined_Solicitation_Synopsis_HSTS02-15-Q-OIA095A.pdf PDF
Technical_Requirement_Attachment_2_March_23.pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

HSTS02-15-Q-OIA095A

Statement of Work (SOW)

Transportation Vetting System

Lot 8:

Technology Refresh

STATEMENT OF WORK (SOW)

1. INTRODUCTION

The Office of Intelligence and Analysis (OIA) 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. The

Transportation Vetting System (TVS) is a mission-critical, National Security system which operates 24 hours per day, 7 days per week.

2. SCOPE AND PERIOD OF PERFORMANCE

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 File Transfer Protocol (SFTP) site, where they will be retrieved by TVS.

Flight data shall identify code sharing flights using IATA code standards where applicable.

Help Desk support shall be provided for flight data questions and will be available on a 24x7x365 basis.

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.

TVS’ data subscription expired on March 17, 2015. The period of performance for this task order is based on the expiration of the existing subscription, as follows:

Base Period 2015 -2016 subscription year April 13, 2015-April 14, 2016

Option Period 1 2016 -2017 subscription year April 13, 2016-April 14, 2017

Option Period 2 2017 -2018 subscription year April 13, 2017-April 14, 2018

Option Period 3 2018 -2019 subscription year April 13, 2018-April 14, 2018

Option Period 4 2019 -2020 subscription year April 13, 2019-April 14, 2020

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

The Government reserves the right to evaluate and add/change/modify/delete any services under this contract, at any time, based on changing requirements in support of the TSA mission.

3. TECHNICAL REQUIREMENTS

The Contractor shall deliver the data in a format equivalent to that specified in this SOW. The solicitation requires each bidder to provide a sample set of formatted files which are representative of the files to be provided in the subscription. These sample files will be evaluated as part of the technical evaluation prior to award.

3.1 Worldwide Scheduled Flight Data

Provide projected Worldwide Scheduled Flights, delivered in a pipe-delimited text format on a weekly basis.

Data file shall contain, at a minimum:

Carrier Code

Flight Number

Duplicate Carriers

Duplicate Flight Numbers

Departure Airport Code

Departure City Code

Departure Country Code (ISO-2 format)

Arrival Airport Code

Arrival City Code

Arrival Country Code (ISO-2 format)

Departure Time

Arrival Time

Arrival day

Days of Operation

Stops

Intermediate Airports

Aircraft Change

Aircraft Type

Aircraft Model

Service Type

Available Seats

Freight Class

Domestic / International

Schedule Start date

Schedule End date

Full Route (aggregation of IATA codes in sequence)

Shared Airline Designation

Multi Carrier Designation

Aircraft Owner

Operating / Non operation carrier identifier

Departure Terminal

Arrival Terminal

3.2 Aircraft Data

Provide aircraft data, via pipe-delimited text format at the same time and frequency of delivery as the

Worldwide Scheduled Flights data. Data file shall include, at a minimum:

Aircraft Name

Aircraft Type

Aircraft Body Type

Cargo Service Types

Max Speed

Max Range

Specific Aircraft Code

PAX Service Types

General Aircraft Code

3.3 Location Data

Provide location data (including airports, bus stations, metropolitan areas, et al), via pipe-delimited text format at the same time and frequency of delivery as the Worldwide Scheduled Flights data. Data file shall include, at a minimum:

Country (ISO-2)

Location Code

Location Type

GMT Offset

DST Start Date

DST End Date

Location Name

Location Coordinates (latitude/longitude)

3.4 Carrier Data

Provide carrier data, via pipe-delimited text format at the same time and frequency of delivery as the Worldwide

Scheduled Flights data. Data file shall include, at a minimum:

Carrier Code

Carrier Name

Country (ISO-2)

State

3.5 Delivery

Delivery of data is not required. TSA will retrieve the data files from the vendor's Secure File Transfer Protocol

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

4.0 508 COMPLIANCE

Section 508 of the Rehabilitation Act, as amended by the Workforce Investment Act of 1998 (P.L. 105-220) requires that when Federal agencies develop, procure, maintain, or use electronic and information technology, they must ensure that it is accessible to people with disabilities. Federal employees and members of the public who have disabilities must have equal access to and use of information and data that is comparable to that enjoyed by non-disabled Federal employees and members of the public.

All EIT deliverables within this work statement shall comply with the applicable technical and functional performance criteria of Section 508 unless exempt. Specifically, the following applicable standards have been identified:

36 CFR 1194.22 – Web-based Intranet and Internet Information and Applications, applies to all Web-based deliverables, including documentation and reports procured or developed under this work statement. When any

Web application uses a dynamic (non-static) interface, embeds custom user control(s), embeds video or multimedia, uses proprietary or technical approaches such as, but not limited to, Flash or Asynchronous

Javascript and XML (AJAX) then “1194.21 Software” standards also apply to fulfill functional performance criteria.

36 CFR 1194.31 – Functional Performance Criteria, applies to all EIT deliverables regardless of delivery method. All EIT deliverable shall use technical standards, regardless of technology, to fulfill the functional performance criteria.

36 CFR 1194.41 – Information Documentation and Support, applies to all documents, reports, as well as help and support services. To ensure that documents and reports fulfill the required “1194.31 Functional

Performance Criteria”, they shall comply with the technical standard associated with Web-based Intranet and

Internet Information and Applications at a minimum. In addition, any help or support provided in this work statement that offer telephone support, such as, but not limited to, a help desk shall have the ability to transmit and receive messages using TTY.

Exceptions for this work statement have been determined by DHS and only the exceptions described herein may be applied. Any request for additional exceptions shall be sent to the COTR and determination will be made in accordance with DHS MD 4010.2. DHS has identified the following exceptions that may apply:

36 CFR 1194.2(b) – (COTS/GOTS products), When procuring a product, each agency shall procure products which comply with the provisions in this part when such products are available in the commercial marketplace or when such products are developed in response to a Government solicitation. Agencies cannot claim a product as a whole is not commercially available because no product in the marketplace meets all the standards. If products are commercially available that meets some but not all of the standards, the agency must procure the product that best meets the standards.

When applying this standard, all procurements of EIT shall have documentation of market research that identify a list of products or services that first meet the agency business needs, and from that list of products or services, an analysis that the selected product met more of the accessibility requirements than the non-selected products as required by FAR 39.2. Any selection of a product or service that meets less accessibility standards due to a significant difficulty or expense shall only be permitted under an undue burden claim and requires approval from the DHS Office on Accessible Systems and Technology (OAST) in accordance with DHS MD 4010.2.

36 CFR 1194.3(b) – Incidental to Contract, all EIT that is exclusively owned and used by the contractor to fulfill this work statement does not require compliance with Section 508. This exception does not apply to any

EIT deliverable, service or item that will be used by any Federal employee(s) or member(s) of the public. This exception only applies to those contractors assigned to fulfill the obligations of this work statement and for the purposes of this requirement, are not considered members of the public.

36 CFR 1194.3(f) – Back Office, applies to any EIT item that will be located in spaces frequented only by service personnel for maintenance, repair, or occasional monitoring of equipment. This exception does not include remote user interfaces that are accessible outside the enclosed “space”.

File details come from the government source that posted it. Updated .