J-9 Task Order TFDM SE Amendment-1.pdf

TFM2 SIR DTFAWA-16-R-00010 Amendment 1 Section J-9

Task Order Statement of Work (SOW)

Task Order Title: TFDM Requirements for TFMS System Engineering Contract CLIN No. (CLIN 08) Task Order No. Alternate Task Order Number: 8.A.1 Modification No. N/A SOW Revision No.: (Original) Contracting Officer’s Representative (COR):

1.0 Purpose and Scope

1.1 The purpose of this tasking is to accomplish a successful and efficient System Design

Review (SDR) leading to further system and software design, development, test, and deployment of Release 1 under CLIN 11A TFMS-TFDM integration. The contractor must provide all necessary engineering, design and development support in accordance with Section C.5 of the TFM2 contract, and specific requirements identified in paragraph 2.1.

2.0 Requirements

2.1 The contractor will develop system requirements and design documentation for TFDM, Build 1 integration into the TFMS system. All requirements and documentation developed under this tasking must conform to the requirements identified in Section Attachment J- 6.A, Future Requirements, Terminal Flight Data Manager (TFDM) Requirements Allocated to Traffic Flow Management System (TFMS), dated July 29, 2015 August 19, 2016.

3.0 Tasks

3.1 Task Work Plan

The Contractor must prepare a Task Work Plan (TWP) to accomplish the necessary system engineering and integration work identified in paragraph 2.1. The Contractor must perform the system engineering and integration functions as specified in the approved Task Work Plan (TWP). No work is authorized under for this effort until the government provides written acceptance of the TWP. In addition to addressing the specific tasks identified in the SOW, the contractor must identify any impact to on-going work and if there is any potential increase in recurring maintenance costs.

3.2 System-Level Requirements and Design Development

The Contractor shall utilize the prior work performed under TFMM contract and the TFMS system GFI and GFE to the greatest practical extent possible to complete this work.

The Contractor must perform requirements analysis and propose system-level requirements and design documentation for FAA review and approval based on the TFDM, Build 1 requirements, the TFMS baseline and the government approved TWP.

3.3 Program Management and Administration

3.3.1 Monthly Status Reporting

The Contractor must provide a monthly status report at the Program Management Reviews (PMRs). The monthly status report must describe the work accomplished during the reporting period and work planned for the next 90 day period, discuss problems encountered and corrective actions taken, and identify pending issues. In particular, the report must address the extent to which any problems or circumstances could cause conflicts in the program schedule(s).

Task status reporting shall be provided monthly as part of the technical portion of the

TFMS PMR.

Activities performed as part of this task shall be tracked as Level of Effort (LOE) activities. The Contractor shall provide a report of actual expenditures for this task on a monthly basis.

Activities and milestones for this task will be added to the TFMS Integrated Master Schedule (Format 6 of the IPMR)

3.3.2 Technical Interchange Meetings (TIMs)

Contractor shall support TIMs with the Government, and /or its appointed representatives, as necessary to collaborate, foster mutual understanding and build consensus on recommendations. TIMS may be requested either by the Contractor or the Government as required and may be conducted at the Contractor’s facility or a place designated by the Government. All TIMs must have government approval.

3.4 Other Related Tasks

The contractor must also provide miscellaneous engineering assessments and support as required by the COR, within the scope of the task order.

4.0 Level of Experience and Skill Required

Approved labor categories are limited to those listed in Section J-7 of the contract. The Contractor must provide qualified personnel with the necessary experience in all disciplines needed to successfully complete all work required under this task order and conduct any necessary Requirements Reviews and System Design Review (SDR) for Release 1.

5.0 Government Acceptance Criteria

In order for this work to be considered successful, the SDR for Release 1 must: (1) demonstrate that the proposed TFMS system requirements are properly allocated to the Configuration Items of the system design; (2) be able to be implemented in the agreed timeframe; and (3) indicate the Contractor is ready to initiate the follow-on software design efforts. Design goal is to provide the designed capabilities with no loss of functionality and no need to provide GFE software to entities outside the U.S. Government.

The FAA will consider the monthly deliverables listed below to be acceptable if they meet the requirements of their respective DIDs.

6.0 Deliverables / Milestones/ Performance Schedule

6.1 Deliverables

The Contractor must deliver the following CDRLs in accordance with Section J of the TFMS Contract. If the CDRL has multiple submission requirements, the due date for the first submission is stated below.

CDRL E13 Task Work Plan – as identified in the request for TWP proposal Request for Proposal (RFP) – As required in writing by the CO CDRL E02 System/Subsystem Specification (SSS) CDRL E03 Interface Requirements Specification (IRS) CDRL E04 System/Subsystem Design Document (SSDD) CDRL E05 Hardware Architecture Design Document (HAD) CDRL E12 Technical Report – As Required CDRL M02 Agenda, Presentation Materials, Action Item List and Meeting Minutes – As required for all TIMs, PMRs, Requirement Review and SDR CDRL I01 Implementation Strategy Paper

The Contractor must incorporate progress reporting; both technical and financial, into monthly reports as required by the contract:

CDRL M04 Integrated Program Management Report (IPMR)

As required, CDRLs, which are not part of this list but are affected by the changes in system-level requirements and design, will be updated and submitted per their respective DIDs.

6.2 Schedule/ Milestones

Requirement Review – TIMS as needed System Design Review – Contractor to propose

7.0 Other Terms and Conditions Applicable to this Work:

7.1 Restrictions on Information Release

The Contractor must not independently publish or distribute any document prepared for the FAA without prior written permission from the Contracting Officer. No documents, reports, information, data etc. may be released to the public, or provided to any party other than the FAA TFMS Program Office, without written approval of the Contracting Officer.

8.0 PERIOD OF PERFORMANCE: Award date through 6 months. (Specific dates will be entered after award of task order.)

END OF SOW

8.0 PERIOD OF PERFORMANCE: Award date through 6 months. (Specific dates will be entered after award of task order.)