TFDM Section C.docx

Table of Contents

C.3.6.4.2 Engineering Change Proposal………………………………...………………………………...34

C.4.2.2.1 RESERVED………………………………………………………………………………………47

C.4.4.1.1 Security Characterization Document………………………………………………………….. 52 C.4.4.1.2 System Security Plan…………………………………………………………………………...52 C.4.4.1.3 NAS Contingency Plan…………………………………………………………………………53 C.4.4.1.4 Security Standard Operating Procedures……………………………………………………….53 C.4.4.1.5 Privacy Threshold Assessment (PTA)………………………………………………………….54 C.4.4.1.6 Plan of Action and Milestone (POAM) Status Report………………………………………….54 C.4.4.2 Security Engineering Support ……………………………………………………………………..54 C.4.4.3 Security Measures ………………55 C.4.4.4 Software Vulnerability Assessment and Patching……………………………………… .………51 C.4.4.4.1 Software Security Patch Program………………………………………………………………...51

C.4.5.3.1.2 Software Design Description……………………………………………………………...58

C.4.5.3.1.5 Software Configuration Management Plan………………………………………………..59 C.4.4.3.1.6 Software Quality Assurance Plan………………………………………………………….59 C.4.5.3.1.7 Software Standards………………………………………………………………………...60

C.6.1.1.2 Program Dcoumentation……………………………………...…………………………………72 C.6.1.1.3 Site Surveys……………………………………………………………………………………..72 C.6.1.1.4 Environmental Compliance……………………………………………………………………..72 C.6.1.1.5 Site Preparation and Installation………………………………………………………………...72 C.6.1.1.6 Hazardous Materials……………………………………………………………………….……74 C.6.1.1.7 System Test and Evaluation………………………………………………………………...… 75 C.6.1.1.8 Implementation…………………………………………………………………...……………..75 C.6.1.1.9 Legacy Hardware Disposition………………………………………………………….……….75 C.6.1.1.10 Maintenance……………………………………………………………………………………..76

C.8.8.1 Post DT Test and Evaluation Management…………………………………………………..…… C.8.8.2 Post DT Test Procedures……………………………………………………………..………...…….97 C.8.8.3 Formal Test Conduct………………………………………………………………………………....98 C.8.8.4 Test Readines Review………………………………………………………………………….……….99 C.8.8.5 Regression Tetsing……………………………………………………………………………..… .100

C.8.8.6 Program Trouble Reporting………………………………………………………………….......…100 C.8.8.6.1 PTR Verification (PTR-V)…………………………………………………………………… C.8.8.7 Test Report…………………………………………………………………………..………..…….100 C.8.8.8 Maintenance of Temporary Build 1.x/2.x Test Labs………………………………………………101 C.8.8.9 Maintain the XL Gen10 Mimic lab for SIG50 RedHat Enterprise Linux 8.2 and associated new COTS integration and test for Build 2.X………………………………………….………… …...101

C.9.5.2.1 Barcode Symbology Standard………………………………………………………………….109 C.9.5.2.2 System Level Data……………………………………………………………………….…….110 C.9.5.2.3 Examples of Equipment Types…………………………………………………………...……110 C.9.5.2.4 Asset Management Systems……………………………………………………….…………..110 C.9.5.2.5 Barcoded Asset Listing……………………………………………………………….………..110 C.9.5.2.6 Asset Identification Report…………………………………………………………………….110

C.5.9.5 Quick Reference Guides and Cards..…………………………………………………...…….. 117

C.9.5.9.10 Contractor Requesst for Government Property……………...…………………………… . …118

C.11.6.6 Training Course Reformatting Requirements…………………………………………………….129

C.11.12.13 Site Training Scenario…………………………………………………………………………... 132 C.11.12.14 Web-Based Training……………………………………………………………………………..132 C.11.12.15 Build 1.4 to Build 1.5 Training “Delta Pack”……………………………………………………132 C.11.12.16 TTS-1 Site Specific Scenarios Maintenance …………………………………………………….132 C.11.13 Training Course Maintenance Support…………………………………………………………………132 C.11.13.1 Training Course Re-baselining……………………………………………………………………132 C.11.13.2 Training Course Validation………………………………………………………...…………….132 C.11.14 Air Traffic Training and First Level System Maintenance and Technical Operations Course Printing Suppport………………………………………………………………...…………………….127 C.11.15 Technical Operations Training Delta Packs………………………………………………………… 127

Appendix 1: Terms of Reference & Acronyms List 134

TABLES

Section C

Terminal Flight Data Manager (TFDM) DTFAWA-16-C-00021 Mod 155 i i Terminal Flight Data Manager (TFDM) DTFAWA-16-C-00021 Mod 155 C.1 Flight Data Manager (TFDM) Overview

C.1.1 Introduction As demand for our National Air Space System (NAS) grows, smarter Next Generation (NextGen) technologies are making air travel more efficient, safer, and environmentally friendly. The Federal Aviation Administration (FAA) is committed to update terminal automation systems and implement NextGen Air Traffic Control (ATC) capabilities that will improve air traffic operations in the National Airspace System (NAS). The implementation of NextGen technologies is a continuous effort to align airplanes’, airlines’, and airports’ technical capabilities. This alignment affects pilots, controllers, airport operators, airlines operators, and the flying public. One such system that the Federal Aviation Administration (FAA) is developing is called Terminal Flight Data Manager (TFDM). Terminal Flight Data Manager (TFDM) is an FAA NextGen program based on airport surface management concepts developed under NextGen direction. The TFDM concepts have been validated with operational users through FAA funded concept engineering and prototype development activities. TFDM will help save time and fuel, reduce emissions, and improve the experience for the flying public.

The FAA Air Traffic Organization (ATO), Decision Support Systems Organization with the Program Management Office (PMO) is the agency sponsor for this acquisition. TFDM capabilities will be incrementally deployed to provide efficiencies in the airport surface and terminal airspace by providing new integrated surface traffic control and management capabilities. TFDM functions include: Surface Collaborative Decision Making (S-CDM), including departure scheduler and other airport decision tools; Electronic Flight Data (EFD); Enhanced Air Traffic Control Tower (ATCT) Traffic Flow Management System (TFMS); and Replacement or integration of multiple systems in the National Airspace System (NAS). TFDM will share data among controllers, aircraft operators, and airports so they can better stage arrivals and departures and manage traffic flow within terminal airspace for greater efficiency. Stakeholders will have a shared awareness of flights on the ground and in the air; the ability to exchange

C.1.2 Background Currently, at most airports, paper flight strips are being used to monitor and share flight plans, requiring controllers to handle and communicate safety-critical data manually. Traffic predictions and decisions are tied to flight plan data that is often untimely and unable to be shared between stakeholders. Flight plans are used to estimate arrivals, gate push-backs, routings, and departures. Their use in the tactical decisions made in handling the more than 40,000 flights daily can lead to inefficiencies across the national airspace system. In addition, aircraft operators currently board passengers and push back from the gates before flights are given slots in line for departure. This can lead to tarmac congestion and wasted fuel with aircraft idling as they wait to join the departure queue.

The imbalance between capacity and demand causes significant growth of delays and severely disrupts the movement of passengers and goods. The implementation of TFDM will result in improved collaboration with users, enhanced accuracy of demand and capacity predictions, and improvements in system modeling and measurement will lead to a better understanding of alternative strategies, enabling more informed decisions.

C.1.3 Purpose

The purpose of this Statement of Work (SOW) is to define the effort required to design, develop, test, implement and support the TFDM System that meets all requirements in the FAA TFDM System Specification Document (SSD), provided in Section J (Attachment J-6) of this contract. This SOW also includes provisions for Program Management (PM), System Engineering (SE), System Design, System Development, System Test and Evaluation, Training, Implementation, Integrated Logistic Support, Engineering Services, and General Engineering/Technical Services. The Contract Data Requirements List (CDRL) contained in Section J of this contract defines the products to be delivered to the Government resulting from the effort defined in this SOW.

C.1.4 Scope

The scope of this contract includes the following major components:

1. Establish and maintain a Program Management Office and perform Program Management to support and coordinate the work performed under this contract to ensure compliance with all terms and conditions

2. Design, development and test of TFDM requirements in accordance with the FAA TFDM System Specification Document (SSD) (Attachment J-6).

3. Development of training for FAA TFDM operators and maintainers

4. Implementation including replacement or integration of multiple systems in the National Airspace System (NAS) and Logistical Support

5. Engineering Services and System/Site Support C.1.5 Benefits TFDM will provide automated data available to stakeholders in real-time to facilitate faster and higher quality decision-making and reduce errors. It will accomplish this through providing the following benefits:

· Real-time Accuracy. Accurate data from surface and terminal surveillance in continuously updated capacity-and-demand predictions will decrease time aircraft spend waiting to taxi, improve the traffic flow, and help prevent missed connections.

· Collaborative Decisions. By connecting aircraft operators, controllers, and airports with digital flight plans, shared surveillance data, and collaborative decision-support tools, TFDM will help stakeholders work together to optimize flights. This will save time and fuel, reduce emissions, and improve the experience for passengers.

· Connected Stakeholders. TFDM lets stakeholders exchange data electronically to make more informed tactical decisions and better handle changing traffic volume, weather, and other evolving situations.

· Better Predictive Tools. TFDM uses surface and terminal surveillance and flow-management capabilities in its predictive modeling for improved departure management, ground movement, and flight coordination.

· Taxpayer Savings. Multiple costly legacy systems will be replaced with a single, easily maintained state-of-the-art TFDM platform.

· Environmentally Friendly. Reduced taxi times, fewer delays and missed connections, and greater predictability with TFDM will save fuel and reduce emissions.

C.2 Applicable Documents The following specifications, handbooks, orders, standards, and drawings form a part of this contract and are applicable to the extent specified herein Tables 1: Military Standards and Specifications, Table 2: FAA/Department of Transportation (DOT) Specifications, Standards, and Orders, and Table 3: Other Publications and Specifications. In the event of conflict between this contract and any of the applicable documents cited below, the provisions of this SOW must apply.

a. Copies of Federal Aviation Administration (FAA) specifications and interface documents may be obtained from the Federal Aviation Administration, Headquarters Public Inquiry Center APA-230, 800 Independence Avenue SW, Washington, DC 20591, 202-267-3484. Requests should fully identify material desired and cite the solicitation or contract number.

The FAA Test and Evaluation Handbook, VVSPT-A2-PDD-013_TnE_Handbook_v3.0, may be obtained at the following website: http://www.faa.gov/about/office_org/headquarters_offices/ang/offices/tc/initiatives/vnv/documents/publications/VVSPT-A2-PDD-013_TnE_Handbook_v3.0.pdf

The FAA Work Breakdown Structure (WBS) Version 5.1 may be obtained at the following website: http://fast.faa.gov/docs/wbs.doc

b. Requests for copies of documents not covered in the preceding paragraph should be addressed to the Contracting Officer (CO). Requests should fully identify material desired and cite the solicitation or contract number.

c. Military Standards and Specifications can be ordered from the Department of Defense Single Stock Point (DODSSP), Building 4/Section D, 700 Robbins Avenue, Philadelphia, PA 19111-5098. Information is available at their website, http://dodssp.daps.dla.mil.

d. Copies of ANSI/ASQC-Q9001-2008 and ISO 9000-3:2004 can be obtained from the following source: American Society for Quality Control P.O. Box 3005, Milwaukee, WI 53201-3005 or 600 North Plankinton Avenue, Milwaukee, WI 53203 Phones: (414) 272-8575 or (800) 248-1946. The Fax is: (414) 272- 1247.

e. Copies of RTCA Documents can be ordered from the RTCA website: http://www.rtca.org C.2.1 Military Standards and Specifications Table 1: Military Standards and Specifications

Products And Systems Volume I

C.2.2 FAA/DOT Specifications, Standards, and Orders Table 2: FAA/DOT Specifications, Standards, and Orders

C.2.3 Other Publications and Specifications Table 3: Other Publications and Specifications

Volume II: Appendices to Guide for Mapping Types of Information and Information Systems to Security Categories

C.3 Program Management The Contractor must establish and maintain a Program Management Office (PMO) and perform Program Management to support and coordinate the work performed under this contract to ensure compliance with all terms and conditions set forth in this contract. The Contractor must establish clear and effective lines of authority, coordination, communication, and accountability between the Contractor’s PMO and the Government to ensure sufficient and timely resources are given to the resolution of any problems that may arise.

The Contractor must assign a Program Manager (PM) who will ensure performance under this contract and will be the primary point of contact for the work to be performed under this contract. The PM must keep the FAA informed of any potential problems and make recommendations for resolution. The PM must ensure that all necessary management, business, contracts, engineering, implementation, and maintenance resources are available and sufficient, both in terms of the quantity of resources and their qualifications to successfully perform all the tasks required in this contract. The Contractor is responsible for management and control of all subcontractors/team members to ensure compliance with all requirements of this contract.

The Contractor must include, but not be limited to, program management activities such as contract administration, finance, obtaining and retaining qualified personnel, as well as technical support across all phases of the program. The PM must have sufficient corporate resources and authority to direct, execute, and control all elements of the program to ensure efficient and timely program execution. The PM must be the focal point within the Contractor's activities for all required program tasks. The PM must be prepared at all times to present and discuss the current program status as well as forecasts related to contract activities with the Government Contracting Officer (CO), the Contracting Officer's Representative (COR), and/or the Government PM. The Contractor must support the Contract/Finance Working Group, Working Group and TIMs Listing (Attachment J-7), to address relevant contract activities including, but not be limited to, resource loading, work breakdown structure, schedules, deliverables, Earned Value (EV) analysis, program tracking, contract modifications, and funds expenditure tracking and status.

The Contractor must provide management oversight of all contract activities to ensure high quality of work effort and deliverables that demonstrate traceability to all program requirements. The Contractor must identify and remedy potential technical cost and schedule risks and issues. The tasks described herein must be fully integrated to ensure their efficient and timely execution.

The Contractor must develop and implement and update every 24 months an integrated Program Management Plan (PMP) in accordance with (CDRL M01). The PMP must integrate all functional areas and must articulate the specific objectives to be accomplished at an overview level. The PMP must also identify the staffing and other resources required to meet contract requirements.

M01 Program Management Plan (PMP)

C.3.1 Meetings, Reviews, Conferences, and Evaluations The Contractor must support recurring meetings such as status meetings, Technical Interchange Meetings (TIMs), Program Management Reviews (PMRs), Formal Design Reviews (i.e. System Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), and evaluations with the Government to discuss program progress, and identify potential problems and resolve identified issues.

The Contractor must prepare Agendas, Meeting Minutes, Action Item Lists, and Presentation Materials for each meeting, conference review and/or evaluation. The Contractor must provide an agenda and notify the CO of its readiness five business days prior to the start of each meeting, conference, review or evaluation. All CDRL items required for a meeting, conference, review or evaluation, are to be delivered in accordance with the (CDRL M03) requirements.

The following instructions are applicable to all meetings, reviews, conferences, and/or evaluations:

1. All Program Management Reviews will be held at a Contractor provided facility within the fifty (50) mile radius local commuting area of Washington, DC unless otherwise directed by or approved by the government. All other meetings, conferences and/or evaluations will be held at the Contractor’s facility unless otherwise directed by or approved by the Government. The Contractor must provide teleconferencing capability, internet access, and facility location(s) to accommodate necessary participation as requested by the Government. The Contractor must propose a date for the meeting, review, conference, and/or evaluation for the COR's approval.

2. For all presentations and agendas, the Government reserves the right to revise the agenda and/or presentation material. The Contractor must provide appropriate Contractor personnel to respond to Government questions. The Contractor must prepare and deliver a summary of open, pending, and closed action items and presentation materials prior to the start of each scheduled meeting, conference, review or evaluation. The Government will revise the delivery times when necessary.

3. The Contractor must record and submit minutes. The Contractor must track action items. Each assigned action item must have a due date and responsible person(s) assigned, who must provide the status of the action at agreed upon intervals until the action is closed. Unless otherwise specified by the Government, the Contractor must respond to all action items with a written closure statement. In the event that an action item cannot be closed promptly a plan of action must be developed for closure.

M03 Agenda, Presentation Materials, Action Item List and Meeting Minutes

C.3.1.1 Post Award Conference The Contractor must plan for, host, support, and participate in a Post Award Conference (PAC) to be held at the Contractor's site within twenty-one (21) calendar days after contract award and document the conference in accordance with (CDRL M03). At this conference, the Contractor must address the plans and schedules for the TFDM work efforts. The Contractor must demonstrate adequacy of proposed efforts to meet all contractual requirements.

The conference is intended to:

1. Establish a liaison between the Contractor, FAA Contracting Officer, FAA Contracting Officer Representative (COR), FAA Technical Training Advisor (TTA), and other FAA personnel specified in the contract and charged with the responsibility for contract administration.

2. Permit inspection of the Contractor’s facility and establish a working relationship with contractor personnel.

M03 Agenda, Presentation Materials, Action Item List and Meeting Minutes

C.3.1.2 Program Management Reviews The Contractor must conduct and support Program Management Reviews (PMRs) in accordance with (CDRL M03) to provide a status and review of work and efforts being conducted under this contract. The Contractor must be prepared to support monthly PMRs but the Government reserves the right to decrease the frequency in accordance with the program needs. For all PMRs, the Government PM may modify the meeting schedule and/or PMR agenda topics to accommodate special program needs. At PMRs, the Contractor must provide, at a minimum, program's management, technical, cost and schedule status. The age of financial data presented at the PMR will be clearly indicated to support the goal that it should be as current as possible. The PMR must be accomplished nominally within one working day.

The Government reserves the right to conduct Executive PMR(s) as part of the PMR agenda(s).

The Contractor must use PMRs to provide program insight to Government representatives on the topics including, but not limited to:

1. Major accomplishments since the last PMR and expected major accomplishments prior to the next PMR;

2. Anticipated differences between contract milestones, schedules, technical performance, cost, Estimate at Completion (EAC) and performance status including identification of major drivers behind cost/schedule variances and the action plans to resolve these variances;

3. Changes in organizational chart and planned versus actual staffing by functional discipline;

4. Review of actions from previous PMR, future required actions, and continual funding status;

5. Integrated Master Schedule (IMS) identifying schedule changes from previous PMR, completed and upcoming milestones, critical path status, all critical path changes, critical path issues and impacts, and a preview of all activities for the next ninety (90) calendar days;

6. Contractor deliverables to be delivered within the following ninety (90) calendar days, the status of CDRL reviews from the Government and status of changes from the previous PMR;

7. Status of open program trouble reports (PTRs), and/or discrepancy reports (DRs) and change requests (CRs) since the last PMR;

8. Status of testing including testing metrics;

9. Status of program risks and their mitigation plan;

10. Program management action item status;

11. Notification of any deviations/waivers from the requirements and the associated justification;

12. Commercial product obsolescence and supportability issues and recommended actions;

13. (Reserved as of BCD RFO) Status of Engineering Change Proposals (ECPs);

14. Implementation and site activation/deployment status; and

15. Status of production readiness to include:

a. Procurement/integration and production schedules for system components; and

b. System integration schedules that demonstrate compatibility with the site deployment schedule.

16. Reporting of metrics specified in SOW Section C.3.3.1.

M03 Agenda, Presentation Materials, Action Item List and Meeting Minutes

C.3.1.3 Integrated Baseline Review The Government will conduct an Integrated Baseline Review (IBR) no later than 120 days after contract award. The contractor will host the event and is to play an active role in planning and providing all requested data in preparation for the event. The purpose of the IBR is to:

· Evaluate the Contractor’s implementation of the performance measurement baseline;

· Ensure that the Government and Contractor mutually understand program scope, schedule, resources, inherent risk, and management approach;

· Review contractor’s planning and execution efforts to meet contractual requirements in areas including but not limited to complete coverage of the SOW, logical scheduling of work activities and adequate allocation of resources;

· Ensure early and adequate planning;

· Identify risks to be tracked; and

· Ensure appropriate reporting levels have been identified and variance thresholds are agreed to by the Government and Contractor.

The Contractor must provide the Government with requested information to include, but not be limited to, data and documents in accordance with IPMR Material (CDRL M08). The contractor must refer to Section H and the National Defense Industrial Association (NDIA) IBR Guide dated September 2010 as guidance for the IBR. The Government may conduct additional IBRs within six months after major modifications to the contract, through mutual agreement between the Government and the Contractor. The Contractor must submit meeting minutes in accordance with (CDRL M03) following each IBR.

C.3.1.4 System Requirements Review The Contractor must plan for, participate in, and conduct a System Requirements Review (SRR) in accordance with (CDRL E07 and M03). The objective of this review is to ascertain the adequacy of the Contractor’s efforts in defining the complete set of system requirements specified in the TFDM System Specification Document (SSD) (Attachment J-6), and TFDM Deployment Build Release Plan (Attachment J-10) as specified in this contract. A single, comprehensive SRR must be conducted to address the requirements outlined above. Incremental or “delta” SRRs may be conducted, subject to Government approval, to address those TFDM functional requirements addressed in the SRR which have been impacted from the development and implementation of segregated TFDM Software Builds.

The SRR must be conducted when the Government determines through the Requirements Identification and Development Working Group (RIDWG) that a significant portion of the system functional requirements have been established.

C.3.1.4.1 System Requirements Review Acceptance Criteria To successfully complete the SRR, the Contractor must meet the following acceptance criteria:

· Obtain Government acceptance of all SRR-associated CDRLs;

· Analyze requirements in the FAA TFDM System Specification Document (SSD) (Attachment J-6) and demonstrate a thorough understanding of these requirements;

· Identify any derived requirements; and

· Establish a requirements baseline consisting of the requirements in, FAA TFDM System Specification Document (SSD) (Attachment J-6), and any derived requirements.

C.3.1.5 Preliminary Design Review The Contractor must conduct a Preliminary Design Review (PDR) in accordance with (CDRLs E04 andM03). Subject to Government approval the Contractor may conduct incremental, or “delta” PDRs. All PDRs must address:

1. Allocation of TFDM functional requirements to individual TFDM Software Builds, specified in Deployment Build Release Plan (Attachment J-10) of the contract, and/or

2. PDR topics that have been impacted from the development and implementation of segregated TFDM Software Builds, specified in Deployment Build Release Plan (Attachment J-10) This review must be conducted for each configuration item or aggregate of configuration items to:

1. Evaluate the progress, technical adequacy, and risk resolution (on a technical, cost, and schedule basis) of the selected design approach.

2. Evaluate the degree of definition and assess the technical risk associated with the selected manufacturing methods/processes.

3. Establish the existence and compatibility of the physical and functional interfaces among the configuration items and other items of equipment, facilities, computer software, and personnel.

For Computer Software Configuration Items (CSCIs), this review must focus on:

1. The evaluation of the progress, consistency, and technical adequacy of the selected top-level design and test approach.

2. Compatibility between software requirements and preliminary design.

3. The preliminary version of the operation and support approach.

The SRR must be approved by the Government before a PDR may be conducted, and all SRR action items must be closed prior to conducting the PDR, unless the Government has given permission to proceed. The PDR must cover the preliminary design of all Contractor-developed hardware and software configuration items. For items that are not Contractor-developed, the Contractor must provide a functional/physical description of the item, the results of the analysis that verifies the item will meet the associated technical requirements, and a description of the interfaces with other configuration items.

At the PDR, the Contractor must describe the products, processes, methodologies, milestones, and measurements to be used in conducting software development activities. The Contractor must describe its plans for acquiring and developing the required hardware and software to meet contract requirements. The Contractor must describe a process and products similar to those in IEEE/EIA 12207-2008. Overall technical program risks must be reviewed on a technical, cost, and schedule basis.

C.3.1.5.1 Preliminary Design Review Acceptance Criteria To successfully complete the PDR, the Contractor must meet the following acceptance criteria:

· Allocate all the requirements in the requirements baseline to Hardware Configuration Items (HWCIs) and Computer Software Configuration Item (CSCIs);

· Provide a traceability of the requirements baseline to the HWCIs and CSCIs;

· For each HWCI and CSCI, identify which requirements are satisfied by Commercial Off The Shelf (COTS), which requirements are already implemented, but require modification, and which requirements require development; and

· Present a preliminary design in accordance with (CDRL E04) that shows how COTS, modified COTS, and new…