Draft Section C.docx

PART I: Section C

Statement of Work (SOW)

TFM-2 DRAFT SIR Section C

TABLE OF CONTENTS

i

PROGRAM SCOPE

Background The Federal Aviation Administration (FAA) works in cooperation with flight operators and other National Airspace System (NAS) users/stakeholders to predict demand, monitor capacity, and implement Traffic Management Initiatives (TMI) as necessary to ensure the number of active flights does not exceed system capacity while striving to minimize constraint impacts to users. The Next Generation Air Transportation System (NextGen), http://www.faa.gov/nextgen/, Implementation Plan provides the vision and roadmap for modernizing the NAS to meet future air traffic demands safely and efficiently. The execution of this plan involves research, development and deployment of new Air Traffic Management (ATM) systems, technologies, and decision support tools. The FAA’s Air Traffic Systems Decision Support Programs office is responsible for the development and implementation of TFM enhancements and new capabilities to support the safe and efficient movement of aircraft through the NAS.

The Traffic Flow Management System (TFMS) assists Traffic Management personnel with predicting demand, identifying constraints, facilitating information sharing, modeling and collaboration of impact mitigation strategies. The Air Traffic Control System Command Center (ATCSCC) in Warrenton Virginia, provides centralized management of NAS-wide TFM capabilities in coordination with Traffic Management Units (TMU) at all major Air Traffic Control (ATC) facilities (approximately 900 workstations across 90 sites), e.g., Air Route Traffic Control Center (ARTCC), Terminal Radar Approach Control (TRACON), and Airport Traffic Control Tower (ATCT).

Near real-time information is shared to maximize the efficient use of available capacity across the entire NAS. The system has a centralized architecture supporting various products and tools, including over 30 user/data interfaces, comprised of custom applications running on COTS hardware. The TFMS supports Air Traffic operations 24/7/365 and is classified by the FAA as efficiency-critical.

The TFM Production Center (TPC) at the FAA’s William J. Hughes Technical Center (WJHTC) in New Jersey is comprised of a data center with on-site system management and helpdesk operations, along with labs supporting test and evaluations. The Disaster Recovery Center (DRC) serves as a backup. On-site technical support is provided at the ATCSCC.

Collaborative Air Traffic Management Technologies (CATMT) investment Work Packages provide the basis and resource allocation for the bulk of TFM enhancements. As future work is approved and funded, tasking will be added within the scope of this contract through the ordering procedures described in Section G. Two major TFMS releases are nominally planned for deployment in the spring and fall of each year – avoiding severe weather season and holiday moratoriums. The detailed design, development, test and deploy cycle is typically 18 months following several months of system engineering to baseline changes to system-level requirements and design material. Concurrent work on some phase of four to five major releases is typical.

C.1.2 Purpose This Statement of Work (SOW) defines the activities and deliverables required for solution implementation and in-service management of TFMS capabilities under this contract. To minimize duplication of information and configuration management complexity, detailed requirements for delivered products and services are left to Contract Data Requirements Lists (CDRL) and corresponding Data Item Descriptions (DID).

APPLICABLE DOCUMENTS

Refer to Section J-2 for current system-level requirements.

Refer to Section J-3 for other applicable Govt. Furnished Information (GFI).

Refer to Section J-4 for Govt. Furnished Equipment/Property (GFE/GFP)

Refer to Section J-5 for Contract Data Requirements Lists (CDRL) and Data Item Descriptions (DID)

Refer to Section J-6 for future requirements.

The following specifications, standards, instructions, orders, guidelines, handbooks, etc. are applicable. The versions of these documents as of the contract award date apply unless changed via subsequent modification. In the event of a conflict between this SOW and a referenced document, the SOW takes precedence:

FAA Orders, Standards and Guidance

FAA Orders and Standards

C.2.2 Other Documents

DOT Departmental Cybersecurity Compendium, Supplement to DOT Order 1351.37 Departmental Cybersecurity Policy, Version 1.0, June 14, 2011 06/21/2011

· Copies of FAA specifications and interface documents may be obtained from the Federal Aviation Administration, Headquarters Public Inquiry Center APA-230, 800 Independence Avenue, SW, Washington, D.C. 20591, 202-267-3484. Requests should fully identify material desired and cite the solicitation or contract number. A number of these documents may be downloaded from the FAA at http://www.faa.gov/regulations_policies/

· Copies of the Acquisition Management System Test and Evaluation Process Guidelines are available in the FAA Acquisition System Toolset (FAST). The Internet address of FAST is: http://FAST.faa.gov.

· 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 or online at http://assist.daps.dla.mil/quicksearch.

· National Institute of Standards and Technology (NIST) standards may be obtained from the Systems and Software Technology Division, Computer Systems Laboratory, National Institute of Standards and Technology, Gaithersburg, MD 20899 or ordered from the NIST website at http://www.nist.gov/.

· Institute of Electrical and Electronics Engineers (IEEE) documents may be obtained from Institute of Electrical and Electronics Engineers-USA, 1828 L Street, NW, Suite 1202 Washington, D.C. 20036-5104 or ordered from the IEEE website at http://www.ieee.org.

· American Society of Mechanical Engineers (ASME) documents may be obtained via the ASME website at http://asme.org/.

· Integrated Baseline Review (IBR) guidance is provided in the National Defense Industrial Association (NDIA) IBR Guide.

· Copies of federal publications may be obtained from the U. S. Government Printing Office, 710 North Capitol Street, Washington, DC 20401, by calling (202) 512-0132, or through the website http://bookstore.gpo.gov/.

· Requests for copies of documents not covered in the preceding paragraphs should be addressed to the Contracting Officer. Requests should fully identify material desired and cite the solicitation or contract number.

PROGRAM MANAGEMENT

The Contractor must establish and maintain an organization and infrastructure necessary to successfully implement all contract requirements efficiently and effectively for the entire duration of the contract period of performance. This must include planning, coordination, conduct and integration of all aspects of program management, e.g., contract administration, finance, technical management and support, across multiple overlapping development and maintenance tasks within the scope of this SOW. The Contractor must accurately track and report to the Contracting Officer (CO): current status of all work compared to baseline plans; cost/schedule forecasts; and issue/risk identification/mitigation. The Contractor is solely responsible for the quality and timeliness of all sub-contractor work.

Program Management Organization The Contractor must assign a dedicated Program Manager (PM) with overall responsibility to organize, plan, schedule, implement, control, analyze and report all elements of the contract. The PM must have sufficient corporate authority to direct, execute, and control all elements of the work under this contract. The PM, as focal point within the Contractor’s organization, must be capable of effectively presenting and discussing contract activities with the primary Government representatives: Contracting Officer (CO), Contracting Officer’s Representative (COR), and TFMS Program Manager.

Contract Transition The Contractor must provide and comply with a Government approved Contract Transition Plan in accordance with the Contract Data Requirements List (CDRL) and Document Item Description (DID) which covers roles, process and procedure details.

CDRL X-XX: Contract Transition Plan

Program Management Plan (PMP) The Contractor must provide, maintain and comply with a Program Management Plan (PMP) in accordance with the Contract Data Requirements List (CDRL) and Document Item Description (DID) which covers roles, process and procedure details.

The Contractor must develop and maintain a Contract Work Breakdown Structure (CWBS) to include a dictionary and index for this contract. The CWBS must align to the FAA WBS provided in Attachment J-8. The CWBS must describe the work that will be accomplished and must facilitate management data collection and reporting. The Contractor must use the CWBS as the primary framework for contract planning, budgeting, and reporting program cost and schedule status to the Government. The Contractor must submit the CWBS for approval as an Appendix of the PMP.

The Contractor must not change the CWBS or associated definitions for any reporting elements identified at level ______ or above in the CWBS without the approval of the CO. Changes at lower levels may be made by the Contractor as deemed necessary without Government approval; however, control account numbering and titles must be consistent in cost reports and the Network Logic Schedule (NLS) and reported to the CO within ten (10) days of implementation.

The Contractor must document its risk management process and procedures in the PMP for timely and continuous identification, assessment, tracking and systematic reduction of risks that could impact the Contractor’s ability to meet its technical, cost and schedule objectives. The risk management approach must accomplish the following:

a. Identify potential risks – solicit input from all team members;

b. Quantify risk probability and impacts on cost, schedule and performance;

c. Determine the sensitivity of interrelated risks;

d. Determine potential alternative approaches to mitigate moderate and high risks;

e. Develop mitigation action plans which include an owner by name;

f. Develop, maintain and report risk metrics; and

g. Ensure risks are factored into all subsequent actions/decisions related to solution implementation details – maintain team member awareness.

CDRL M01: Program Management Plan (PMP) Meetings, Reviews, Conferences, and Evaluations Meeting Logistics and Action Tracking The Contractor must provide the Government quiet working space at its primary work location with access to the internet for four government representatives in support of meetings, reviews, evaluations, etc.

The Contractor must support recurring status reviews and planning meetings, Technical Interchange Meetings (TIMs), Program Management Reviews (PMR), requirements/design reviews, and evaluations with the Government to discuss program progress, identify potential problems, and resolve issues and concerns. The Contractor must provide appropriate qualified personnel to respond to most of the Government questions during the meeting.

In addition, the Contractor must support the following specific meetings:

a. Daily Service Reviews Unless cancelled by the Government, the contractor must conduct a brief telcon (approximately 15 minutes) every morning to brief the Government on the operational status of the TFMS. By noon of each day the Contractor must provide a written summary of all significant system events within the last 24 hours and summarize service desk reports, planned outages, service changes or requests and status of root cause analysis (RCA).

b. Weekly Operations Reviews Unless cancelled by the Government, the contractor must conduct a telecon (date/time per mutual agreement) to recap significant events, outages and open issues including open RCAs, severity 1 & 2 problem tickets/reports, and watch-list items.

c. Weekly Deployment Readiness Reviews (DRR) Unless cancelled by the Government, the contractor must conduct a telecon every Tuesday at 1000 eastern to provide a summary of recent system changes and present proposed changes to any TFMS component supporting operations for the Government’s review and disposition. The information must include operational impact, safety risk assessment, test reports, and the proposed start date, time, and duration to implement the changes. The contractor must deliver an agenda by COB on the preceding Friday, and meeting minutes by COB same day of DRR conduct.

The Contractor must provide teleconferencing and on-line meeting capabilities for all meetings with the Government unless otherwise directed. The Contractor must provide adequate facilities to meet attendance requirements for all conferences, meetings, reviews, and evaluations. Government facilities will only be used at Government's direction or approval of the Contractor’s request.

The Contractor must provide draft agendas, presentation material, meeting minutes and action items in accordance with the CDRL and DID.

CDRL M02: Agenda, Presentation Materials, Action Item List and Meeting Minutes The Contractor must track action items assigned during meetings until the disposition of the action is agreed to by the Government. At a minimum, the action tracking method must have:

a. Unique tracking number;

b. Short summary title;

c. Dates for opened, due, and closed;

d. Organization and person responsible by name;

e. An adequate description to understand context without having to look back at meeting minutes to understand what needs to be done and why; and

f. Ability to share, sort and filter with ease Once the disposition of an action has been completed and validated by the Government, the action may be closed, however the Contractor must maintain a history of all items for life of the contract.

Program Management Reviews (PMR) The Contractor must conduct reviews for all active work under contract at least monthly. The first PMR must be held per the date in Section F. For all PMRs, the COR may modify the meeting schedule and location to accommodate special program needs. At PMRs, the Contractor must provide, at a minimum, the program’s management, technical, cost and schedule status. The Contractor must provide a Government approved agenda, presentation materials, action item list and meeting minutes for all PMRs.

The PMR must be accomplished nominally during one working day and must include the following (in no particular order):

a. Major accomplishments since last PMR and expected major activity/events in next 90 days;

b. Risk analysis, concerns and issues;

c. Cost, schedule and performance status including reasons for any variances and action plans to resolve these variances;

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

e. Review of actions from previous PMR and ensure new action items accurately recorded;

f. Schedule status, critical path analysis, risks, changes;

g. Status of required CDRLs;

h. Program Trouble Report (PTR) status and metrics;

i. System performance and support metrics;

j. Software development status and metrics;

k. Review any open deviation/waiver requests;

l. Commercial product supportability issues and recommended actions;

m. Status of Government Furnished Property (GFP)/Government Furnished Information (GFI);

n. Status of Engineering Change Proposals (ECPs); and

o. Implementation and site activation/deployment status.

Post-Award Conference (PAC) The Contractor must arrange and host a Post-Award Conference (PAC) per the date in Section F. The Contractor must demonstrate adequacy of proposed planning efforts to meet contractual requirements in areas such as, but not limited to, complete coverage of this SOW, logical scheduling of the work activities, and risk management. The Contractor must provide an overview of the following CDRLs at the PAC:

CDRL X-XX: Contract Transition Plan CDRL M01: Program Management Plan (PMP) CDRL C01: Configuration Management Plan (CMP) CDRL E17: Quality System Plan (QSP) CDRL M03: Network Logic Schedule (NLS) CDRL E01: Systems Engineering Management Plan (SEMP) CDRL E13: Software Development Plan (SDP) CDRL T01: Contractor Master Test Plan (CMTP) Program Control Network Logic Schedule The Contractor must develop, maintain and deliver an integrated TFM Program Network Logic Schedule (NLS) in accordance with the CDRL and DID.

CDRL M03: Network Logic Schedule (NLS) Earned Value Management System (EVMS) The Contractor must establish, maintain, and use an EVMS in compliance with ANSI/EIS-748C capable of accurately accommodating the data for all work performed under the contract including subcontractors. The EVMS must be used to plan/measure performance and identify cost/schedule variances. The Contractor must prepare and deliver a Cost Performance Report (CPR) in accordance with the CDRL/DID that examines the actual expenditures measured against the planned expenditures. The data used to generate performance information must also be used to develop and deliver a Contract Funds Status Report (CFSR) in accordance with the CDRL and DID providing funding status and requirements.

The Contractor must submit all proposed changes to EVMS to the Contracting Officer for approval prior to implementation.

The Contractor agrees to provide access to all pertinent records and data requested by the Contracting Officer, or authorized representatives, needed by the FAA to verify the Contractor's EVMS compliance during performance of this contract.

CDRL M04: Cost Performance Report (CPR) CDRL M05: Contract Funds Status Report (CFSR)

Integrated Baseline Reviews (IBR) The Contractor must support the Government’s conduct of an IBR to review its processes and procedures for scheduling work, allocating resources, and managing risk.

The contractor must refer to the NDIA IBR Guide Rev. 1 dated September 1, 2010 as guidance in preparing for and conducting the IBR. The Contractor must hold an IBR within 60 days of the start of each new Contract CLIN or subCLIN unless the Contracting Officer grants a waiver in writing.

Upon completion of the review, the Government will provide a letter of findings. The Contractor must respond to the letter within 30 days and remedy all shortfalls to ensure confidence in their ability to successfully complete work within the allocated resources.

Performance Measurement The Contractor must implement and maintain a performance measurement methodology which includes measurement indicators and metrics for tracking and forecasting performance for all work under this contract for the duration of the contract. The Contractor must prepare and deliver a Management Indicators Report in accordance with CDRL and DID.

CDRL M07: Management Indicators Report Quality Assurance (QA) The Contractor must establish, maintain, deliver and comply with a quality assurance program in accordance with ANSI/ASQC ISO-9001-2008. QA roles, process and procedure details must be documented in the Quality System Plan (QSP) in accordance with the CDRL and DID.

The inspection requirements specifically set forth in Section E must be part of the Contractor's overall QA program. The absence of Government inspection does not relieve the Contractor of the responsibility of ensuring that all products or supplies submitted to the Government for acceptance comply with all requirements of the contract.

All QA operations performed by the Contractor must be subject to Government verification at any time which will consist of, but not be limited to:

a. Government surveillance of the operations to determine if practices, methods and procedures of the quality program are being properly applied;

b. Government inspection of QA evaluations, audits and reports; and

c. Government product inspection to verify acceptability.

CDRL E17: Quality System Plan (QSP) Configuration Management (CM) The Contractor must provide, maintain and comply with a Configuration Management Plan (CMP) in accordance with the CDRL and DID which covers roles, process and procedure details.

The Contractor must minimize duplication of information across CDRLs to minimize CM complexity by referencing other documents for details best maintained elsewhere. All subcontractors must comply with the CM policy and procedures.

The Contractor must retain detailed change history for all CDRLs and provide to the Government upon COR request. Draft updates to CDRLs must be delivered with revision marks unless the COR approves a wavier in advance.

CDRL C01: Configuration Management Plan (CMP)

The Contractor must prepare and deliver a Configuration Status Accounting Report (CSAR) in accordance with the CDRL and DID.

CDRL C02: Configuration Status Accounting Report (CSAR)

For every significant TFMS software release, the Government expects to issue Task Order requests for performing the system-level engineering needed to conduct a System Design Review and prepare an Engineering Change Proposal (ECP) in accordance with the CDRL and DID for detailed design, development, test and implementation upon CO request.

The Contractor must not prepare unsolicited ECPs and will not be compensated for doing so.

CDRL C03 Engineering Change Proposal

If a temporary waiver to, or relaxation of, a requirement is desired, the Contractor must submit an RFD in accordance with the CDRL and DID for Government approval. The Contractor is strongly encouraged to coordinate the concern informally with appropriate Government representative prior to formal submission.

CDRL C04: Request for Deviation (RFD) CDRL C05: Notice of Revision (NOR)

The Contractor must prepare, deliver and comply with a Configuration Audit Plan (CAP) and related reports in accordance with the CDRL and DID which covers roles, process and procedure details.

CDRL C06: Configuration Audit Plan (CAP) Unless otherwise stated, all proposed changes to CDRLs must be reviewed and approved by the designated Government representative prior to applying change.

SECURITY

The Contractor must designate an individual responsible for compliance with all security-related requirements of the contract.

The Contractor must comply with the following personnel, physical, and information security requirements for all work performed under this contract, including development, operations and maintenance:

a. FAA Order 1370.82A, Information Systems Security Program

b. FAA-STD-045, Open Systems Interconnection Security Architecture and Mechanisms.

c. FIPS 199, Standards for Security Categorization of Federal Information and Information Systems.

d. FIPS 200, Minimum Security Requirements for Federal Information and Information Systems.

e. NIST SP 800-37, Rev. 1, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach.

f. NIST SP 800-39, Managing Information Security Risk: Organization, Mission, and Information System View;

g. NIST SP 800-30 Rev 1, Guide for Conducting Risk Assessments;

h. NIST SP 800-18 Rev 1, Guide for Developing Security Plans for Federal Information Systems;

i. NIST SP 800-53 Rev 4, Security Controls for Federal Information Systems and Organizations;

j. NIST SP 800-53A Rev 1, Guide for Assessing the Security Controls in Federal Information Systems;

k. NIST SP 800-137, Information Security Continuous Monitoring for Federal Information Systems and Organizations.

l. FAA ORDER 1370.101A, Information Security Incident Reporting and Response Policy.

m. FAA ORDER 1600.1E, Personnel Security Program.

n. FAA ORDER 1600.75, Protecting Sensitive Unclassified Information.

o. FAA Information Systems Security Authorization Handbook, current version.

p. FAA Information Systems Security Templates, current versions.

The Contractor must provide, maintain, and comply with the following in accordance with the CDRL and DID:

CDRL S01: System Characterization Document (SCD) Report CDRL S02: Systems Security Plan (SSP) CDRL S03: Information System Contingency Plan (ISCP) CDRL S04: ISCP Test Plan and Report CDRL S05: Security Standard Operating Procedures (SSOPs)

The contractor must support the Information Security Continuous Monitoring (ISCM) Process, to include:

· Conduct and support vulnerability scanning activities, including regular credentialed vulnerability scans on all operating systems and devices; web applications; and database servers (when enterprise-wide FAA tool is available) and comply with FAA remediation timeframe requirements.

· Support meetings of the ISSO’s Security Authorization Team to facilitate development of the Security Authorization Package and related activities.

· Support ongoing mitigation activities for security weaknesses identified in the information system’s Plan of Action and Milestones (POAM).

The Contractor must ensure all employees and subcontractors complete the government’s annual security awareness training.

SYSTEMS ENGINEERING

System Engineering Program The Contractor must perform systems engineering for all disciplines needed to ensure successful accomplishment of tasking under this contract. The Contractor must deliver, maintain and comply with a Systems Engineering Management Plan (SEMP) in accordance with the CDRL and DID.

CDRL E01: Systems Engineering Management Plan (SEMP) For work not covered by other CDRLs, the Contractor must deliver results of engineering analysis in a Technical Report with an appropriately specific sub-title.

CDRL E29: Technical Report Engineering Services The Contractor must perform engineering tasks that support analyses, estimates, design, development, implementation, maintenance and training as directed by the CO via Task Orders. Each Task Order Request will contain: description of the work/services to be performed; desired milestone/performance schedule; and relative priority of the task.

The Contractor’s Task Order proposal must provide a technical approach, proposed schedule and an estimate of labor hours and all other costs required to complete the Task. The Task Order proposal must identify any impact to on-going work and if there is any potential increase in recurring maintenance costs.

Engineering Services performed for TFM related work sponsored by other FAA organizations external to the AJM office will be managed under separate Task Orders.

CDRL E30: Task Work Plan

System-level Requirements and Design The Contractor must update, maintain, deliver and comply with the TFMS System/Subsystem Specification (SSS) and Interface Requirements Specification (IRS) in accordance with the CDRL and DID. These are the requirements basis for formal Government acceptance testing. The Contractor must use Concept of Operations, requirements documentation, and other GFI as the basis for proposing changes to the SSS/IRS.

The Contractor must derive, allocate and validate requirements subject to FAA approval. All changes, including editorial, must be approved by the Government’s designated Requirements Work Group Lead or alternate. The Contractor must maintain change history throughout duration of the contract.

The Contractor must notify the Government if any approved IRS changes require an update to the Government maintained Interface Requirements Document (IRD).

The Contractor must host Requirements Reviews as needed to ensure timely progress to completing baseline changes for each development task.

CDRL E03: System/Subsystem Specification (SSS) CDRL E28: Interface Requirements Specification (IRS)

The Contractor must update, maintain, deliver and comply with the TFMS System/Subsystem Design Document (SSDD) in accordance with the CDRL and DID. The Contractor must update the SSDD to reflect FAA approved changes to system requirements and design documents.

CDRL E04: System/Subsystem Design Document (SSDD)

The Contractor must update, maintain, deliver and comply with the TFMS Hardware Architecture Document (HAD) in accordance with the CDRL and DID. The Contractor must update the HAD to reflect FAA approved changes to system requirements and design documents.

CDRL E26: Hardware Architecture Document (HAD)

System Design Reviews (SDR) The Contractor must plan and host System Design Reviews, to be scheduled in accordance with Section F. The objective of the System Design Review is to gain Government acceptance of proposed changes to system-level requirements and design. This technical exchange must cover the following topics at a minimum if applicable:

a. Draft SSS and IRS changes;

b. Draft SSDD changes;

c. Draft HAD changes;

d. Security and performance impact assessments;

e. Implementation and transition strategy;

f. Operations and maintenance impact assessment; and

g. Issues/concerns/risks and action plans.

Detailed Design & Development The Contractor must provide, maintain and comply with a Software Development Plan (SDP) in accordance with the CDRL and DID that includes processes, methodologies, and measurements used in conducting software development and test activities leading to formal Government acceptance tests.

CDRL E13: Software Development Plan (SDP)

The Contractor must update, maintain, deliver and comply with the Software Requirements Specifications (SRS) in accordance with the CDRL and DID which covers roles, process and procedure details.

CDRL E02 Software Requirements Specification (SRS)

The Contractor must update, maintain, deliver and comply with the Software Design Documents (SDD) in accordance with the CDRL and DID.

CDRL E15: Software Design Document (SDD)

The Contractor must update, maintain, deliver and comply with the DataBase Design Documents (DBDD) in accordance with the CDRL and DID.

CDRL E16: Database Design Document (DBDD)

The Contractor must update, maintain, deliver and comply with Interface Control Documents (ICD) in accordance with the CDRL and DID.

CDRL E05: Interface Control Document (ICD)

Detailed Design Reviews (DDR) The Contractor must plan and host Detailed Design Reviews, to be scheduled in accordance with Section F. The objective of the design review is to gain Government acceptance of proposed changes to system-level requirements and design. This technical exchange must cover the following topics at a minimum if applicable:

a. Review any changes to SSS, IRS, VRTM and SSDD since SDR;

b. Draft Software Requirements Specifications;

c. Draft Software Design Document (SDD);

d. Draft Database Design Document (DBDD);

e. Draft Interface Control Documents (ICD);

f. Revised draft Hardware Architecture Document (HAD);

g. Security and performance impact assessments;

h. Implementation and transition strategy;

i. Operations and maintenance impact assessment; and

j. Issues/concerns/risks and action plans.

The Contractor must obtain Government approval prior to making any modification to any COTS/NDI product that is an integral part of the architecture, Upon satisfactory resolution of Government comments, the Contractor will be authorized to begin full-scale development activities.

Secondary Development Services For small-scale and short-term development activities, e.g., product/service modifications developed, tested and implemented apart from the major TFMS releases, the Contractor must perform engineering tasks that support analyses, estimates, design, development, implementation, maintenance and training as directed by the CO via Task Orders. Each Task Order Request will contain: description of the work/services to be performed; desired milestone/performance schedule; and relative priority of the task.

The Contractor’s Task Order proposal must provide a technical approach, proposed schedule and an estimate of labor hours and all other costs required to complete the Task. The Task Order proposal must identify any impact to on-going work and if there is any potential increase in recurring maintenance costs.

Human Factors The FAA Human Factors organization at WJHTC is responsible for leading TFM Human Factors engineering. Computer-Human Interface (CHI) design mockups will be coordinated with user representatives and provided as a GFI to the Contractor to assist detailed design and development. Upon CO request, the Contractor must perform CHI demonstrations on work in progress.

TEST & EVALUATION

Master Test Plan The Contractor must provide, maintain and comply with a Contractor Master Test Plan (CMTP) in accordance with the CDRL and DID.

CDRL T01: Volume I, Contractor Master Test Plan (CMTP)

Test Tools The Contractor must maintain and use the GFI/GFE TFM Test Tool (TTT) in support of test conduct as appropriate (refer to Attachment J-4 for information).

The Contractor must provide and obtain the Government’s concurrence on Contractor proposed test tools, test documentation, and test hardware and software necessary to conduct testing, capture test data, perform data reduction, and accomplish test data analysis.

For new proposed hardware configurations, the Contractor must provide samples to the Government for power requirements verification prior to issuing purchase requests.

Test Activities WJHTC System Acceptance Test (WSAT) The Contractor must conduct first round of formal Government acceptance test for every software release at the WJHTC and deliver the following in accordance with the CDRLs and DIDs:

CDRL T01: CMTP Volume II, Test Plan- WJHTC SAT CDRL T01: CMTP Volume III, Test Procedures- WJHTC SAT CDRL T01: CMTP Volume IV, Test Report- WJHTC SAT Support Government Test Activities The Contractor must support Government conduct of Operational Testing with system users. The Contractor must ensure test labs are under CM control and ready at least two working days in advance of test start date. The Contractor must have knowledgeable staff readily available to respond to questions and address any test lab configuration issues. The Contractor must provide timely analysis and response to new PTRs.

Key Site Acceptance Test (KSAT) The Contractor must conduct KSAT in accordance with the CDRL and DID at an operational site designated by the Government (usually the ATCSCC and an ARTCC) and deliver the following in accordance with the CDRLs and DIDs:

CDRL T01: CMTP Volume II, Test Plan- KSAT CDRL T01: CMTP Volume III, Test Procedures- KSAT CDRL T01: CMTP Volume IV, Test Report- KSAT

Site System Acceptance Test (SAT) The Contractor must conduct a SAT at every site which undergoes hardware configuration changes and deliver the following in accordance with the CDRLs and DIDs:

CDRL T01: Volume II, Test Plan- SAT CDRL T01: Volume III, Test Procedures- SAT CDRL T01: Volume IV, Test Report- SAT

Problem Trouble Report The Contractor must support a Development Problem Trouble Report (PTR) working group to review, validate, classify, prioritize, and approve work. The working group must meet at least weekly during execution of formal acceptance tests. The Contractor must update, maintain and deliver a Development PTR report in accordance with CDRL and DID.

CDRL E25: Development Program Trouble Report (PTR) Summary

IMPLEMENTATION

The Contractor must plan, coordinate and manage the transition to new operations hardware and/or software in accordance with the CDRL and DID for a Transition Plan. As directed by the CO, the Contractor must conduct site surveys and submit reports in accordance with the CDRL and DID. As directed by the CO, the Contractor must plan, coordinate and manage pre-installation preparation, e.g., facility power, HVAC, and communications in accordance with the CDRL and DID for a Site Installation and Integration Plan (SIIP) unless responsibility for accomplishing tasks is explicitly assigned in a Government approved plan. The Contractor must update, maintain and deliver the following in accordance with the CDRLs and DIDs:

CDRL E10: Transition Plan CDRL I01: Site Survey Report CDRL I02: Site Installation & Integration Plan The Contractor must obtain Government approval before taking components out of service. The Contractor must ensure minimal disruption to Air Traffic operations by planning on working on site only during mid-shifts as directed by the Government and minimize down time by performing configuration and checkout activities in advance to greatest extent practical extent. The Contractor’s field installation personnel must be adequately prepared, equipped and empowered to minimize time on site and avoid multiple trips.

The Contractor must install all equipment in accordance with manufacturer specifications. The Contractor must remove packaging material and dispose of replaced equipment as directed by the Government. The Contractor must perform software-only updates remotely to greatest extent practical.

The Contractor must transfer ownership of system hardware to the Government using FAA Form 6030, Contractor Acceptance Inspection Report Exceptions List and Clearance Record.

TRAINING

The Contractor must develop, deliver and maintain training on products and services delivered under this contract to Government designated personnel including users, maintainers and other stakeholders. The Contractor must provide, maintain and comply with the CDRLs and DIDs for a Training Development Plan; Training Design Guides tailored to target audience; and Familiarization Training Materials specific to system product/service changes.

CDRL R01: Training Development Plan CDRL R02: Training Design Guides CDRL R03: Familiarization Training Materials Upon Government direction, the Contractor must provide instructor led hands-on training at various facilities.

OPERATIONS AND MAINTENANCE

System Maintenance The Contractor must monitor, operate, maintain, and repair all TFMS products and services specified in Appendix A, at all locations specified in Section F and support all users, in accordance with the requirements of the SOW, CDRLs and DIDs and applicable documents. All system changes and planned service reductions (including loss of redundancy) must be approved in advance by the Government.

The Contractor must ensure awareness of COTS software updates and request Government approval to apply.

The Contractor must ensure awareness of COTS hardware and software support risks and concerns. The Contractor must provide the Government timely notification of concerns and action requests.

The Contractor must apply all 56-day Chart Cycle Update (CCU) adaptation changes every 8th Thursday, and weekly updates to a subset of files every Thursday, on time – no exceptions.

Help Desk The Contractor must maintain a 24/7/365 help desk for customer service support for all TFMS products and services. The Contractor must open “tickets” for trouble reports and help requests and assign a priority/severity level based on the impact to the TFMS mission capability, criticality of a specific site and the number of users affected. The Contractor must provide the Government remote read-only access to the contractor’s ticket tracking information. The Contractor must ensure open tickets are automatically escalated for management review after a configurable amount of time as approved by the Government.

For technical help requests from clients of TFMS data interfaces requiring significant operator time (e.g., to answer detailed design questions, assist with trouble shooting client application software, etc.), the Contractor must track and report these tickets as a separate category.

Operational System Support (OSS) The Contractor must provide the Air Traffic Control System Command Center (ATCSCC) daily onsite support from 0700 to 2300 Eastern Time. The Contractor must monitor performance of local products and services, track all issues impacting ATCSCC operations, assist with troubleshooting and service restoration, record and provide a daily log of significant system events and OSS assistance actions to the Government.

Daily checks of ATCSCC capabilities must be conducted at the start of each OSS shift and near end of last shift. In addition to prerequisite technical knowledge and skills, the OSS personnel must have adequate knowledge and communication skills to effectively answer most user questions related to all TFMS products, tools, and services.

The OSS personnel must have access to the Help Desk’s ticket tracking tools and information.

The Contractor must update, maintain, deliver and comply with the following CDRL/DIDs CDRL E21: Software Product Specification (SPS) CDRL E22: Software Version Description (SVD) CDRL E23: System/Subsystem Installation & Configuration Manual (SICM) CDRL E27: System Computer Operator Manual (SCOM) CDRL L01: Integrated Support Plan CDRL L02: Contractor Maintenance Logistics Support Activity Report CDRL L03: Technical Manual Master List CDRL L04: Commercial Manuals, Drawings, and Data CDRL L05: Contractor Developed Supplemental Technical Manuals CDRL L06: System Maintenance Manual CDRL L07: System Administraion Manual CDRL L10: Assest Identification Report

Problem Trouble Report (PTR) The Contractor must support a Development and Operations Problem Trouble Report (PTR) working group to review, validate, classify, prioritize, and approve work. The working group must meet –at a minimum bi-weekly for operations unless waived by the Government. The Contractor must update, maintain and deliver an Operations PTR report in accordance with CDRL and DID.

CDRL E25: Operations Program Trouble Report (PTR) Summary

The contractor must support the Government with Problem Trouble Reporting (PTR) tracking/administration. All PTRs must be coordinated through the PTR Working Group (PTRWG). As directed by the Government, the Contractor must design, develop, and test resolutions to TFMS problems.

All failures categorized as Severity-1 (see section H for definitions) must have the highest priority for resolution. Coordination of these time-critical PTRs must be escalated to the FAA TFMS Sustainment Manager. The Contractor must prepare and provide a Root Cause Analysis (RCA) for every Severity 1 PTR within five (5) business days of the failure to the FAA Sustainment Manager.

CDRL E-XX: Root Cause Analysis Report (RCAR)

Disaster Recovery Center (DRC) Special Provisions The FAA must know when any contractor is on site at the DRC. The Contractor must comply with the following notification process in addition to completing current Department of Homeland Security (DHS) application forms and required training.

The Contractor must provide the visitor’s full name, company, mobile phone number, date of visit, purpose, and expected entry/exit times to the FAA Contracting Officer Representative (COR), Alternate Contracting Officer Representative (ACOR), and other Government employees as directed by the COR, as follows:

· For planned scheduled weekly maintenance visits: An email one day in advance of visit must be provided to the FAA DRC POC. If the schedule or individuals change, an email must be provided at least two days prior to the visit.

· For unplanned visits in direct support of transitioning OPS to DRC or to address a critical equipment outage: A phone call in advance of visit must be made to the FAA DRC POC followed by an email which must be received by COB the day of the visit.

· For all other visits: An email must be provided at least two days prior to the visit to the FAA DRC POC explaining the purpose and contact information (including FAA sponsor if different from FAA DRC POC).

Any violation of the above process will result in contractor removal from the DRC access list.

- 1 -

Appendix A TFMS Products and Services

The following TFMS products and services are provided to FAA users and NAS stakeholders in accordance with access privileges – refer to Section J for more information. This list doesn’t identify required components and interfaces, nor products and tools used to manage, maintain and support the system.

Advisory messages Airport Arrival Demand Chart (AADC) Aircraft Situation Data to Industry (ASDI) Collaborative Decision Making (CDM) Computerized Voice Reservation System (CVRS) Current Reroutes Current Restrictions Departure Spacing Program (DSP) Diverted Flight List DTO…