TBFM Section C.pdf

PART I - SECTION C

STATEMENT OF WORK

DTFAWA-10-C-00052 Conformed Contract

C.1 INTRODUCTION

The Government, specifically the Federal Aviation Administration (FAA), is transforming the current aviation system to a Next Generation (NextGen) modernized Air Traffic Management (ATM) system using modern technologies and redesigning the National Airspace System (NAS) Enterprise Architecture to fully exploit these new technologies. This Statement of Work (SOW) defines the programmatic and technical requirements for the management and execution of the Time Based Flow Management (TBFM) Program.

C.1.1. Background The FAA expects significant growth in air traffic in the foreseeable future. This growth is placing increased demand on the existing NAS and has led FAA programs to evaluate new methods that could safely and efficiently improve the capacity of the existing system in order to accommodate future air traffic expectations.

C.1.2. Purpose The purpose of this SOW is to define the project-specific management requirements, activities, deliverables and timelines supporting the design, development, testing, implementation and sustainment (including Technology Refreshment) of the TBFM System. The TBFM system functional and performance requirements are identified in the TBFM System Specification Document (SSD), located in Section J. This SOW also includes requirements for Program Management, System Engineering, System Design, System Development, System Test and Evaluation, Implementation, Training, and Integrated Logistic Support.

This SOW allows, on a Task Order basis, requirements for Engineering Services and Second Level Engineering (SLE) Site Support as defined in Sections C.11 and G.13.

The Contract Data Requirements List (CDRL) and associated Data Item Descriptions (DIDs) contained in Section J define the documentation deliverables.

C.1.3. Scope The scope of this contract includes the following major components:

Sustainment of existing TBFM baseline system to include maintaining current software, adaptation, documentation and addressing newly identified problems Perform Technology Refreshment of system components that are obsolete or reaching end-of-life NextGen enhancements to the system to include design, development, test and implementation of requirement as defined in the TBFM SSD and Interface Requirements and Control Documents

Geographically expand the TBFM System Engineering Services and Site Support as defined per Sections C.11 and G.13

C.1.4 Period of Performance

The period of performance is for a five (5)-year base with twelve one (1)-year option periods and one 6-month extension period.

C.1.5 Place of Performance

The primary place of performance is facilities. The geographical scope of this contract covers the United States (US) and its territories as deployment of system will require equipment facility, places of performance, as approved by the Government, for execution of this contract are indicated in Section F.8.

DTFAWA-10-C-00052 Conformed Contract

C.1.6 Definitions

Development is defined as the systematic use of scientific and technical knowledge to meet specific requirements. Development represents the design, building, modification, or improvement of the product as determined by the basic idea or concept.

Enhancement is defined as a new requirement or additional capability that changes a performance envelope.

Sustainment is defined as those activities necessary to maintain or restore an item to a specified operational condition. These can be corrective, event, preventative, scheduled or unscheduled.

Product Improvement is defined as a capability that improves a product within the current performance envelope.

Technology Refreshment is defined as the periodic replacement of equipment to ensure continuing reliability and availability of systems.

C.2 APPLICABLE DOCUMENTS

The following specifications, handbooks, orders, standards, and drawings form a part of this SOW and are applicable to the extent specified herein. In the event of a conflict between this SOW and any of the applicable documents cited below, the requirements of this SOW take precedence. In the event of a revision to an applicable document that necessitates an adjustment to programmatic, technical requirements and/or design after contract award, an Engineering Change Proposal (ECP) is required.

Section J provides additional document references.

C.2.1 FAA Instructions, Orders, Specifications and Standards

C.2.1.A Document References Pertaining to work completed prior to TBFM Contract Extension Definitization. Section C.2.1.A reflects those Instructions, Orders, Specifications and Standards which have been superseded, cancelled or revoked but were applicable to efforts accomplished prior to TBFM Contract Extension Definitization. Reference to these documents are retained here to maintain a record of their applicability to those requirements.

Document ID # Title 41 CFR 102 (Parts 35 through 39) (Captured in AMS Clause)

Disposition of Personal Property

ANSI/NFPA 70E (Not in RFP) National Electrical Code DD Form 1586 (Captured in CDRL M05) Contract Funds Status Report DoD 5200.28-STD (Superseded by DoDD 8500.1) Department of Defense Trusted Computer System

Evaluation Criteria EO 12902 (Revoked by EO 13123) Energy Efficiency and Water Conservation at Federal

Facilities EO 13123 (Revoked by EO 13423) Greening the Government through Energy Efficient

Management EO 13423 (Revoked by EO 13693) Strengthening Federal Environmental, Energy, and

Transportation Management FAA Order 1320.32B (Cancelled 05.01.1992) DOT Directives Clearance and Implementation FAA Order 1350.15C (Cancelled by 1350.14B) Records, Organization, Transfer, and Destruction

Standards FAA Order 1370.92A (Cancelled by 1370.121A) Password and PIN Management FAA Order 1370.100 (Cancelled by 1370.121A) Media Sanitizing and Destruction Policy FAA Order 1370.105 (Cancelled by 1370.121A) Logical Access Control Policy FAA Order 1370.107 (Cancelled by 1370.121A) Rules of Behavior/System Use Policy

DTFAWA-10-C-00052 Conformed Contract

Document ID # Title FAA Order 1370.82A (Cancelled by 1370.121A) Federal Aviation Administration Information Systems

Security Program FAA Order 1370.83 (Cancelled by 1370.121A) Internet Access Point FAA Order 1370.89 (Cancelled by 1370.121A) Information Operations Condition FAA Order 1370.91 (Cancelled by 1370.121A) Information System Security Patch Management FAA Order 1370.95 (Cancelled by 1370.121A) Wide Area Network Connectivity Security FAA Order 1370.102 (Cancelled by 1370.121A) System Use Notification and Disclaimer Statement

Policy FAA Order 1370.116 (Cancelled by 1370.121A) Boundary Protection Policy FAA Order 1375.1E (Not in RFP) Information/Data Management FAA Order 1280.1B (Cancelled by 1370.121A) Protecting Personally Identifiable Information (PII) 36 CFR Part 1194 (Not in RFP) Electronic and Information Technology Accessibility

Standards FAA Order 4420.4 (Cancelled 02.26.2007) Space Acquisition FAA Order JO 6000.22B (Cancelled 06.15.2012) Maintenance of Analog Lines FAA Order JO 6000.47A (Cancelled by JO 6000.204) Maintenance of Digital Transmission Channels FAA Order 7032.9 (Cancelled 10.21.2016) Traffic Management System (TMS) Air Traffic

Operational Requirements FAA-STD-005E (Superseded by FAA-STD-067 &

FAA-STD-068)

Preparation of Specifications, Standards and Handbooks

MIL-HDBK-454B (Not in RFP) Department of Defense Handbook, General Guidelines for Electronic Equipment

C.2.1.B Document References Pertaining to work efforts delivered for TBFM Contract Extension Definitization. These FAA Orders, Instructions, Specifications and Standards are applicable to work efforts performed and delivered for TBFM Contract Extension Definitization.

Document ID # Title

FAA AIR TRAFFIC CONTROL

FAA Order JO 7110.65Y Change 1 Air Traffic Control FAA NAS EA AV-1 Overview and Summary Information FAA Order JO 1900.47C Air Traffic Organization Operational Contingency Plans FAA Order 8260.3B Change 21 United States Standards for Terminal Instrument

Procedures (TERPS) FAA Order 8260.44A Change 2 Civil Utilization of Area Navigation (RNAV) Departure

Procedures

SAFETY & HEALTH

29 CFR 1910 Occupational Safety and Health Standards 29 CFR 1926 Safety and Health Regulations for Construction EO 12196 Occupational safety and health programs for Federal employees FAA Order 3900.19C Federal Aviation Administration (FAA) Occupational

Health and Safety (OSH) Program FAA Order JO 1000.37B Air Traffic Organization Safety Management System FAA Order 8040.4B Safety Risk Management Policy 41 CFR 101 (Parts 42 through 48) Utilization and Disposal of Hazardous Materials ANSI/TUT IEC 60068-1:2013 Environmental Testing - General and Guidance FAA Order 1053.1C Energy and Water Management Program for FAA

Buildings and Facilities MIL-HDBK-470A Designing and Developing Maintainable Products and

Systems

PROGRAM MANAGEMENT

DTFAWA-10-C-00052 Conformed Contract

Document ID # Title FAA-STD-028C Standard Contract Training Programs ANSI/EIA-748-B Earned Value Management Systems (EVMS) FAA Order 1350.14B Records Management

CONFIGURATION CONTROL

ANSI/EIA-649-2004 National Consensus Standards for Configuration

Management FAA Order 1800.66 Changes 1, 2, & 3 Configuration Management Policy FAA-STD-021A Configuration Management (Contract Requirements) MIL-HDBK-61A Configuration Management Guidance

QUALITY ASSURANCE

ANSI/ISO/ASQ Q9001-2008 Quality Management Systems Requirements Standard FAA Order JO 7210.6 Air Traffic Quality Assurance Program FAA Order 4630.5B Quality and Reliability Assurance of General Operating

Material Managed by the FAA Logistics Center ISO 9001:2008E Quality Management Requirements ISO-10007 Quality Management for Configuration Management ANSI/Q9002-1994 American Society for Quality Control (ASQC) Q- 900-

2-1994 FAA-STD-013D Quality Control Program Requirements FAA-STD-016A Quality Control System Requirements

SECURITY

FAA Order 1200.22E External Requests for National Airspace Systems (NAS)

Data FAA Order JO 1370.101 ATO Information Security Incident Reporting and

Response Policy FAA Order JO 1370.96 ATO System Access Control FAA Order 1370.121A FAA Information Security and Privacy Program &

Policy FAA Order 1600.1E Personnel Security Program FAA Order 1600.2F Safeguarding Classified National Security Information FAA Order 1600.72A Contractor and Industrial Security Program FAA Order 1600.75 Protecting Sensitive Unclassified Information (SUI), FAA-Order 1600.69C Facilities Security Management Program Federal Information Processing Standards (FIPS) Publication (PUB) 199

Standards for Security Categorization of Federal Information and Information Systems

Federal Information Processing Standards (FIPS)Publication (PUB) 200

Minimum Security Requirements for Federal Information and Information Systems

National Institute of Standards and Technology (NIST) Special Publication (SP) 800-64

Security Considerations in the System Development Life Cycle, October 2008

NIST SP 800-18 Rev 1 Guide for Developing Security Plans for Federal Information Systems

NIST SP 800-30 Rev 1 Guide for Conducting Risk Assessments NIST SP 800-34 Rev 1 Contingency Planning Guide for Information

Technology Systems NIST SP 800-37 Rev 1 Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach

NIST SP 800-53 Recommended Security Controls for Federal Information Systems

NIST SP 800-60 Guide for Mapping Types of Information and Information Systems to Security Categories

SYSTEMS & SOFTWARE ENGINEERING

FAA RMA-HDBK-006C V1.1 Reliability, Maintainability, and Availability

(RMA) Handbook

DTFAWA-10-C-00052 Conformed Contract

Document ID # Title MIL-HDBK-46855A Human Engineering Program Process and Procedures DOT/FAA/HF-STD-001 (HFDS001) FAA Human Factors Design Standard for Acquisition of

Commercial-of-the-Shelf Subsystems, Non- Developmental Items, and Developmental Systems

FAA Order 9550.8 Human Factors Policy HF-STD-004 Requirements for a Human Factors Program FAA-CT-96-1 w/Rev to Ch. 8 Human Factors Design Standard ASME Y14.100-2004 Engineering Drawing Practices FAA-STD-067 & FAA-STD-068 Preparation of Specifications, Standards and Handbooks FAA-STD-025F Preparation of Interface Documentation FAA-STD-026A Software Development for National Airspace (NAS) FAA-STD-039C NAS Open System and Protocols FAA-STD-045A Open System Interconnection Security Architecture FAA-STD-060B Data Standard for National Airspace System FAA-STD-063 XML Namespaces FAA-STD-064 Web Service Registration FAA-STD-065 Preparation of Web Service Description Documents FAA-STD-066 Web Service Taxonomies WSDL 2.0 Web Services Description Language XML 1.0 Extensible Markup Language ISEE/EIA 12207.0 Standard for Information Technology Software Life

Cycle Process Description MIL-STD-498 Software Development and Documentation MIL-STD-31000A Systems Engineering Standards and Specifications NAS Systems Engineering Manual Version 3.1, dated (6 June 2006)

TEST & EVALUATION

MIL-HDBK-781A Handbook for Reliability Test Methods, Plans and

Environments for Engineering, Development, Qualification, and Production

FAA GS-2152 FAA Certification and Authorization Handbook: Air Traffic Control Series

FAA Order CT 1810.8A FAA William J. Hughes Technical Test and Evaluation Policy

FACILITY CONSTRUCTION

FAA-C-1217H Electrical Work, Interior FAA Order JO 6950.2D Change 1 Electrical Power Policy Implementation NAS Facilities FAA Order 6950.27A Power System Analyses: Load Flow Calculations, Short Circuit Analysis, Protective Device Coordination Studies and ARC Flash Hazard Assessment

FAA Order JO 6470.33B Control of Power, Space and Environmental Interfaces at EnRoute Air Traffic Control Facilities

FAA-STD-019E

Lightning and Surge Protection, Grounding Bonding and Shielding Requirements for Facilities and Electronic Equipment

FAA-STD-020B

Transient Protection, Grounding, Bonding and Shielding Requirements for Electronic Equipment

FAA-G-2100H Electronic Equipment and General Requirements FAA-STD-001B Color and Texture of Finishes for National Airspace

Equipment 47 CFR Part 15 Federal Communications Commission Regulations for

Radio Frequency Devices

MIL-STD-461E

Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment

DTFAWA-10-C-00052 Conformed Contract

Document ID # Title IEC 61000 Electromagnetic Compatibility (EMC) FAA Order 4441.16 Acquisition of Telecommunications Systems, Equipment, and Services FAA Order 6650.8A Airport Fiber Optic Design Guidelines FAA Order 6000.36A Communication Diversity

LOGISTICS

FAA Order JO 7210.3BB Facility Operation and Maintenance ASTM-D-3951 Standard Practice for Commercial Packaging MIL-STD-129 Marking for Shipping and Storage, Quality and Format

Specification ISO 15416 Barcode Print Quality Guideline - Overview FAA Process and Procedure Guide FAA Asset Identification Specification V2.4 OMB Circular A-130 Revised Memo #4 Management of Federal Information Resources FAA Order 4600.27C Personal Property Management FAA Order JO 1320.58C Instructions for Writing Notices, Maintenance

Technical Handbooks, and System Support Directives FAA Order 1370.120 Section 508 Accessibility Policy FAA Order FAA 4250.9B Field Material Management and Control FAA Order FAA-D-2494 Technical Instruction Book Manuscript: Electronic, Electrical and Mechanical Equipment, Requirements for Preparation of Manuscript and Production of Books

MIL-T-31000 Technical Data Package Specifications FAA Order 4650.20A Reporting and Replacement of Items Falling Under

Warranty FAA Order 6000.15H General Maintenance Handbook for National Airspace

System (NAS) Facilities FAA Order 6000.30F National Airspace System Maintenance Policy FAA Order 6000.41 Policy Governing Contractor Assisted Maintenance for the National Air Space System FAA Order JO 6000.53D Remote Maintenance Monitoring Interfaces FAA Order JO 6480.24A Maintenance of Time Based Flow Management System

(TBFM Maintenance Technical Handbook) FAA Order JO 6980.25C Maintenance of Batteries for Standby Power (If applicable) FAA Order JO 6950.22A CHG 1 Maintenance of Electrical Power and Control Cables

C.3 PROGRAM MANAGEMENT

The TBFM Contract enables the enhancement of capability through a modular approach to provide incremental software releases within a constrained schedule to achieve requirement satisfaction as funds become available and technology matures over time.

Each TBFM software release will undergo a twenty four to thirty six (24 36) month cycle consisting of requirements definition, development, and T&E activities, followed by up to six (6) months of stakeholder review of documentation/reports in support of a software release fielding decision.

The Contractor must be responsible for program management, system and software engineering, product design, development, integration, testing, and implementation to include software maintenance, configuration management, risk management, and quality assurance. The Contractor is also responsible for developing and delivering documentation in accordance with the CDRLs associated with this SOW.

a. General Certifications and Qualifications

DTFAWA-10-C-00052 Conformed Contract

The Contractor must execute structured software engineering and program management processes that facilitate effective and high-quality software development in accordance with ISO/IEC/IEEE 12207.0, Systems and Software Engineering Software Life Cycle and ISO/IEC/IEEE 15289:2017, Standard for Information Technology Software life cycle processes Life Cycle Data.

The Contractor must use standard development procedures equivalent to those articulated by the Capability Maturity Model Integration for Systems Engineering and Software Engineering (CMMI SE/SW) maturity level 3 or equivalent.

The Contractor must ensure that all software development, enhancements, maintenance and product improvements are to the most current baseline versions of the TBFM application and adhere to the applicable Application Programming Interfaces (APIs), NSA Information Assurance Security Requirement Directive (IASRD), and TBFM SSD.

The Contractor must accomplish the following TBFM specific tasks.

b. Enhancements

The Contractor must enhance the TBFM software to incorporate new functional and performance requirements as identified in the TBFM SSD (see Section J) and develop associated System/Subsystem Specifications (SSS) and Software Requirements Specifications (SRS). The integration of new technologies should be aimed at moving toward more distributed operations while preserving data integrity, improving data access, and increasing interoperability. The Contractor must evaluate any interoperability or other impacts to the current baseline and provide design and implementation information, to include modeling and simulation. The enhancement effort includes analyzing the requirements, developing the capability, integrating the capability into the TBFM application, testing of the new capability, implementation of the capability at designated sites, and maintenance support requirements.

c. Geographical Expansion

The Contractor must install TBFM enhanced capability at new sites. Installation includes the integration of new technologies and hardware, ensuring the fielded system availability requirement (99.9%) is maintained during peak air traffic periods. Selection of hardware should balance reducing the Size, Weight, and Power (SWaP) footprint with projected peak software processing demands/workload at each site.

IDAC. Integrated Departure/Arrival Capability (IDAC) automates the Call for Release (CFR) process for departure scheduling and EnRoute Departure Capability (EDC). IDAC enables Tower (or in some cases terminal) controllers to use automation to assign departure times to flights that correspond to available slots in the overhead flow (see SSD in Section J for IDAC functional requirements).

The Contractor must expand the deployment of IDAC to the remaining ARTCCs and additional associated airports within each respective ARTCC.

Deploy IDAC to thirty-four (34) new site locations (IAH, MCI, MDW, COS, HOU, BOI, TPA, OMA, PDX, ASE, OKC, AUS, SGF, TWF, PBI, GFK, GEG, MNS, EGE, SHV, SAT, TUL, SUN, RSW, DSM, BFI, GJT, LBB, MSY, XNA, BZN, SRQ, FSD, and PDT)

[Deferred] TSAS. Terminal Sequencing and Spacing (TSAS) enables the extension of time-based scheduling into the terminal environment, all the way to the runway, and provides terminal controllers information and decision support tools to manage time-based scheduling. TSAS decision support tools include Speed Advisories, Slot Markers (graphical

DTFAWA-10-C-00052 Conformed Contract depictions of where the aircraft should be positioned along the path to meet a scheduled time), and indicators on the data block, and a scheduling timeline (see SSD in Section J for TSAS functional requirements).

The Contractor must expand the deployment of TSAS to terminal sites.

Deploy TSAS to three (3) sites (DEN, LAX, ATL)

Deploy 30 TBFM in a Box. Further detail: 12 for TRACONs (4 each at D01, SCT, A80); 3 for OSFs (D01, SCT, A80); 3 for TLSE (One each for TSLE Deployment, OT&E, and Integration); 2 for SLE; 6 for Raytheon (3 labs with 2 TIABs each); 1 for Leidos; 3 for Hot Spares.

d. Transition

The Contractor must assist the Government during transition of services (e.g., weather data, etc.) as described in the TBFM SSD (see Section J).

e. Decision Support Tool Integration and Data Exchange

Increased data sharing between TBFM and Terminal Flight Data Manager (TFDM) and Traffic Flow Management System (TFMS) systems (3T) is required to enhance demand capacity prediction.

The Contractor must coordinate, plan, and implement TBFM integration and data exchange with TFDM and TFMS decision support tool programs (TBFM-TFDM-TFMS (3T)) as described in the TBFM SSD and in accordance with the NAS ICD (see Section J).

The Contractor must conduct 3T integration engineering activities aligned toward advancing trajectory-based operations over clearance-based operations.

f. RESERVED

g. Technology Refreshment

The Contractor must replace TBFM hardware nearing end of life. Technology Refreshment includes the integration of new technologies and hardware, ensuring the fielded system availability requirement (99.9%) is maintained during peak air traffic periods. Selection of hardware should balance reducing the forward footprint with future software processing demands and costs.

Technology Refreshment must also incorporate product improvement - that is, improving TBFM hardware architecture and product index list to resolve software problems caused by underperforming hardware and ensure full software capability is consistently available during peak demand periods. The Contractor must evaluate hardware/software configuration or other impacts to the current baseline and provide implementation information for all improvements.

Software changes shall be limited to essential modifications to maintain compatibility with the new OS and middleware APIs, modifications to facilitate transition to the new tech refresh baseline, M&C updates associated with Tech Refresh, CHI changes in support of new monitors, TSIM usability enhancements, software tools updates, new, critical compiler warnings that did not exist prior to the compiler upgrade, and modifications to support identified system security issues.

Applicable software changes will be proposed by Leidos and approved by the FAA via standing engineering meetings/reviews.

h. Sustainment/Maintenance/Training

DTFAWA-10-C-00052 Conformed Contract

The Contractor must provide Supply Chain Risk Management (SCRM), which addresses Supply Chain Security Controls as described in Committee on National Security Systems Instruction (CNSSI) 1253 (companion publication to NIST SP 800-53) for protection of Mission Critical Functions to Achieve Trusted Systems and Networks.

The Contractor must perform maintenance on the TBFM system to resolve sustainment software needs to meet the needs of the FAA.

Upon Government request, the Contractor must provide operator and maintainer training courses.

C.3.1 Program Management The Contractor must establish and maintain a program management organization with the resources and infrastructure necessary to meet all contract requirements within the period of performance. The FAA has designated the Program Manager (PM) position as a key position. The Contractor must assign a fully qualified PM at contract award. The PM must be fully empowered to manage resources and make program decisions that are within the scope of the contract. The PM must be the primary point of contact for all program related matters and must maintain collaborative communications with the Government PM and Contracting Officer Representative (COR) on a continual basis. The PM is the focal point for all required program tasks and activities.

Relevant program activities include resource loading, work breakdown structure, schedules, deliverables, Earned Value (EV) analysis, and funds expenditure tracking and status. The PM must be prepared at all times to present and discuss the current program status as well as forecasts related to activities with the Government

The PM is responsible for all aspects of the program, to include staffing, organizing, managing, budgeting, scheduling, and reporting. This includes, but is not limited to, subcontractor management and allocating small business workshare activities, as well as, program management activities such as risk management, cost control, problem solving, quality control, and recruiting and retaining the most qualified personnel throughout the period of performance.

The PM must have sufficient corporate authority to direct, execute, and control all elements of the program. The PM must have ready access to the resources necessary to ensure efficient and timely program execution (facilities, funding, manpower, and infrastructure).

C.3.2 Program Management Plan

The Contractor must provide management oversight of all program activities, inclusive of the processes, procedures, reports, checks, audits and systems put in place to ensure the quality of work effort and deliverables. The Contractor must establish a continual improvement process that identifies, reduces, or eliminates suboptimal processes. The execution of tasks described in this SOW must be fully integrated to ensure efficient and timely coordination of interdependent program activities.

The Contractor must provide Government access to records and data that support the cost data reported throughout the period of performance.

The Contractor must develop and implement a TBFM Program Management Plan (PMP). At a minimum, the Contractor must perform the following tasks in managing the TBFM contract:

Produce the schedules of work that reflect and track the delivery of products as specified by this SOW Use methods and metrics for assessing the schedule, technical performance of the work, and risks to this program Use procedures for relating risks and costs to schedule and technical performance to assess the impact of risks and costs on successful completion of the TBFM work effort

DTFAWA-10-C-00052 Conformed Contract

Designate a Program Manager (PM) who is responsible for integrating and maintaining the total Contractor effort as described in this SOW.

The Contractor must specify how the PM will manage and control communications. The plan must ensure that all interaction is managed and conducted to provide maximum benefit toward successful completion of the TBFM contract. The Contractor must demonstrate subcontractor(s) integration within the overall program management plans and procedures. The Contractor must integrate all functional areas (e.g., systems engineering, software engineering, testing, configuration management, risk management, quality assurance, security, safety, integrated logistics support) and define the organizational structure and business processes that will be utilized for the successful execution of the program. The Contractor must specify the work tasks, at an overview level, necessary to meet SOW requirements. The Contractor must also discuss staffing and other resources required to meet contract requirements. The Contractor must also address risk management and quality control activities that will be ongoing throughout the contract period. The Contractor must submit the PMP, documenting its management program, for Government approval.

C.3.2.1 Contract Work Breakdown Schedule

The Contractor must prepare a Contract Work Breakdown Structure (CWBS) based on a logical and efficient sequence of tasks designed to accomplish the effort described in this SOW and the TBFM specification (see attachment in Section J). The CWBS must align with the FAA approved best facilitate program management. The Contractor must maintain and update the CWBS to a minimum level 3 unless otherwise specified in the preliminary WBS. The CWBS must describe the work that will be accomplished and must facilitate data collection and reporting. The CWBS must include a WBS Dictionary and WBS Index. The Contractor must use the CWBS as the primary framework for planning, budgeting, executing, and reporting of program cost, schedule, and performance status to the Government. The Contractor must deliver the CWBS as part of Program Management Plan (Appendix A) in accordance with CDRL M01.

The Contractor must not modify the WBS or associated definitions for any reporting elements identified in the WBS without prior Government PM Concurrence and CO Approval.

C.3.2.2 Risk Management

The Contractor must describe the procedures to be used for managing areas of risk to successful project completion in a Risk Management Plan. The Risk Management activities must be documented and delivered as Appendix B to the PMP in accordance with CDRL M01. TBFM Risk Management approach must accomplish the following objectives:

Identify potential sources and drivers of risks.

Quantify risks, including risk levels, and their impacts on cost (including life cycle costs), schedule and performance. Include performance, cost, and schedule uncertainties and sensitivity to program, product, and process assumptions.

Determine the sensitivity of interrelated risks.

Determine potential alternative approaches to mitigate moderate and high-level risks Develop mitigation plans that minimize impact of each risk assessed as high and/or moderate pertaining to the program.

Develop and maintain risk-reporting matrix (risk register).

Apply resources and take actions necessary to avoid, mitigate, control, or accept each risk assessed as high and/or moderate. Proactively monitor implementation of mitigation plan on each risk to determine if plan is having intended effect. Adjust mitigation plan as necessary to ensure implementation has intended effect. Update

DTFAWA-10-C-00052 Conformed Contract program document(s) as necessary and communicate with Government status of risk and impacts if risk realized.

Ensure that risk is factored into all subsequent actions or decisions on implementation of requirements, design, and solutions.

The Contractor must also identify program personnel assigned specific risk management roles.

The Contractor must provide a summary of prioritized risks and proposed risk mitigation plans with estimate costs and any secondary or tertiary impacts at each PMR.

The Contractor must quantify risks with respect to their impact on all phases of the program. In assessing the life cycle risks, any interdependencies with other programs must be considered.

Interdependencies must be documented in the risk assessment submission as a statement of dependencies.

The Contractor must identify risks and assign a priority for developing a recommended course of action per the NAS System Engineering Manual. The Contractor must develop risk mitigation plans for all high priority risks and moderate risks involving interdependencies. The Contractor must track the effectiveness of risk mitigation plans and strategies.

The Contractor may submit to the Government risk mitigation strategies involving prototyping.

The Contractor must submit a recommendation describing cases where prototyping would reduce risk associated with design decisions. Prototypes may be developed and tested at the facility or, with prior Government approval, at William J. Hughes Technical Center (WJHTC) or other specified Government site.

Prototype activities must not impact NAS operations.

Contractor must update the status and risk mitigation plans on a monthly basis and summarize risk management progress during scheduled PMRs. The Contractor must request Government concurrence for each program risk disposition, and must continuously identify, assess, and add new risks as bilaterally determined during the PMRs. Electronic access to risk management information must be provided to Government designated personnel.

C.3.2.3 Integrated Master Schedule

The Contractor must develop and maintain an Integrated Master Schedule (IMS). The IMS must identify critical milestones (including all applicable support activities) for meeting program activities as defined in this SOW and Section F for the period of performance for this contract.

The Contractor must ensure that the IMS:

Includes all contractually specified milestones and Contractor activities to meet the milestones Includes appropriate predecessors, successors, and all relationships between activities Identifies the critical path Identifies all GFE/GFI required to meet these milestones, along with the need dates Organized according to the WBS Consistent with the Government approved EVMS Includes all site activities Includes sufficient detail to allow tracking of progress throughout the life cycle Includes all CDRLs and other contract deliverables Includes the details for software releases per Section C.6.12.2.2

DTFAWA-10-C-00052 Conformed Contract

C.3.2.4 Quality Assurance Program

The Contractor must establish a Quality Assurance (QA) program and document the processes and procedures in a TBFM Quality System Plan (QSP). The Contractor must establish a baseline metric for each process output being monitored with an acceptable tolerance level from the baseline that still allows for consistent outputs meeting Government requirements, which are located in Section J. For example, a key indicator in the software development process may be software defect rates. If defect rate increases above the established tolerance level then QA team reports the trend to the PM for corrective action and to the corporate QA

Verification that processes and procedures put in-place to support the TBFM program are under control. i.e., ensuring TBFM deliverables (documentation, reports, training, etc.) and products (hardware and software) consistently comply with requirements of this SOW, CDRLs, DIDs, and the TBFM Specification, as applicable.

A quality assurance organization that has sufficient independence and authority to evaluate TBFM processes and procedures at key points providing performance negative trends and/or quality problems identified, and report finding(s) to action to the PM for getting process within established tolerance levels, but it is the responsibility to ensure processes and procedures are under control and reliably delivering consistent outputs.

Emphasis placed on Configuration Management (CM) processes and procedures to ensure they are under control and CM is maintaining consistency of TBFM's performance, functional, and physical attributes with its requirements, design, and operational information.

Controls to ensure that all inspections, audits, and testing are performed in compliance with contract requirements and that all test data is complete, correct, traceable, repeatable, and acceptable.

Maintenance of a proper record keeping function to provide objective evidence and traceability of inspections, audits, and testing performed.

Procedures and controls for assuring that all products or services procured from subcontractors or vendors, including pre-packaged Commercial-of-the-Shelf (COTS) products, conform to contract requirements.

Procedures and controls to ensure that deliverables are adequately reviewed, and meet contract requirements. The Contractor must place emphasis on monitoring:

a. Procedures and controls for the prevention of software and adaptation defects and/or deficiencies.

b. Detection and analysis of software and adaptation defects and/or deficiencies and procedures for determining and implementing corrective action.

The inspection requirements specifically set forth in this SOW must become a part of the Contractor's overall QA program. The Contractor must perform a series of periodic internal quality audits to verify whether quality activities and results are in compliance with the Contractor quality assurance program. The Contractor must deliver the Quality System Control Plan in accordance with CDRL M07.

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 the requirements of this contract.

The Contractor must provide and maintain a quality assurance program in accordance with ISO- 9001:2008, FAA-STD- -approved Quality System Plan

DTFAWA-10-C-00052 Conformed Contract

(QSP). The Quality System Plan must describe the procedures and controls to be utilized by the Contractor and/or subcontractor(s), if applicable, for assuring that all requirements of the contract are met. At a minimum, this program must provide for:

(a) A QA organization that has sufficient responsibility and authority to identify and evaluate quality problems, and to initiate, recommend or provide solutions;

(b) Procedures and controls to assure adequate configuration management during all operations through final acceptance;

(c) Controls to assure that all inspection and testing is performed in compliance with contract requirements and that all test data is complete, correct, traceable, repeatable, and acceptable;

(d) Maintenance of a proper record keeping function to provide objective evidence and traceability of operations performed;

(e) If applicable, procedures and controls for assuring that all software products or services procured from subcontractors conform to contract requirements;

(f) Procedures and controls to assure that all documentation is adequately reviewed and meets contract requirements;

(g) Procedures and controls for the prevention of deficiencies, detection and analysis of deficiencies when they do occur, as well as procedures for corrective action;

(h) A system of periodic internal quality audits or reviews to verify whether quality activities and related results are in compliance with planned arrangements, and to verify that the QA program is performing effectively.

C.3.2.4.1 Quality Assurance Management Responsibility

Due to the safety and secure nature of air traffic management services, failure of the Contractor to correct deficiencies to the satisfaction of the Government may be cause for suspension of acceptance by the Government until corrective action has been taken, or until conformance of the product to prescribed criteria has been demonstrated. The Contractor must document the results and recommendations for each quality inspection performed including newly developed or integrated software and adaptation. These inspections must span the entire period of performance. The Quality Assurance inspection reports must be maintained by the Contractor's QA organization, and must be made available to the Government upon request.

C.3.2.4.2 Quality Assurance Verification

All QA operations performed by the Contractor must be subject to Government verification at any time.

Government verification will consist of, but not be limited to:

Government surveillance of the operations to determine that practices, methods and procedures of the written quality program are being properly applied.

Government product inspection to measure quality of the product to be offered for acceptance.

C.3.2.5 Meetings, Reviews, Conferences and Evaluations

The Contractor must support recurring status meetings, Technical Interchange Meetings (TIMs), Program Management Reviews (PMRs), Formal Design Reviews, and evaluations with the Government to discuss program progress, identify potential obstacles or risks to continued progress, and proactively apply resources to mitigate risk or resolve identified problems (realized risks).

DTFAWA-10-C-00052 Conformed Contract

The Contractor must prepare Agendas, Meeting Minutes, Action Item Lists, and Presentation Materials for each meeting, conference review and/or evaluation. The Contractor must notify the Government of its readiness prior to the start of any meeting, review, conference, and/or evaluation.

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

All meetings, reviews, conferences and/or evaluations will be held in the Washington, DC metro area or at WJHTC unless otherwise directed by the Government. The Contractor must provide teleconferencing capability, internet access, and facility location (within 25 miles of FAA Headquarters) 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.

For all presentations, the Government reserves the right to revise the agenda and/or presentation. The Contractor must provide Contractor personnel who are knowledgeable of the topic when responding 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 conference, meeting, review or evaluation in accordance with CDRL M02. The COR will revise the lead time between delivery of presentation materials and the subject conference, meeting, review or evaluation to balance adequate Government review time and currency of the subject material.

The Contractor must record and submit minutes in accordance with CDRL M02 following the event for Government review and concurrence. 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. The Contractor must update presentation material, action items, and meeting minutes based on Government comments and feedback on draft minutes. The Contractor must submit final documents to the Government in accordance with CDRL M02 after receiving Government comments and feedback. If Government has no comments or feedback, then the initial draft will become the final and no further submissions are required.

C.3.2.5.1 Post Award Conference

The Contractor must plan, support, and participate in a Post Award Conference (PAC) within seven (7) calendar days after contract award. 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/update of the following, as appropriate, at each PAC (coordinate with COR on which documents are appropriate):

1. Evolution Plan

2. Transition Plan

3. Program Management Plan

4. System Engineering Management Plan

5. Quality System Plan

6. Configuration Management Plan

7. Software Development Plan

8. Integrated Master Schedule

9. Draft PMP, QSP, and CMP must be delivered at the PAC

DTFAWA-10-C-00052 Conformed Contract

C.3.2.5.2 Program Management Reviews

The Contractor must conduct and support Program Management Reviews (PMRs) to provide a status of work being conducted under this contract. The Contractor must be prepared to support monthly PMRs but the Government reserves the right to increase or decrease the frequency per the program needs. For all PMRs, the Government PM may modify the meeting schedule to accommodate special program needs. At PMRs, the Contractor must provide, at a minimum, provide program insight to Government representatives.

C.3.2.5.3 Integrated Baseline Review

The Contractor must conduct an Integrated Baseline Review (IBR) no later than 120 business days after contract award. The Government will approve the date and location. Purpose of IBR is for the Government and the Contractor to jointly assess areas, such as the Contractor's planning, to ensure complete coverage of the SOW/Specification, logical scheduling of the work activities, adequacy of resources, and identification of inherent risks.

The Contractor must propose entrance and exit criteria for the IBR. IBR updates must be scheduled, as required, to address the exercise of significant contract options, or the incorporation of major modifications.

The Contractor must refer to Section H and the National Defense Industrial Association (NDIA) IBR Guide as guidance in preparing for and conducting the IBR. The Contractor will schedule the IBR to occur.

C.3.2.5.4 Technical Interchange Meetings

Technical Interchange Meetings (TIMs) must be held to discuss issues that require mutual resolution or further clarification. The Government COR must approve all ad hoc TIMs prior to the meeting. Scheduled TIMs identified in the SOW do not require further COR approval. The Contractor must prepare TIM material in accordance with CDRL M02.

C.3.2.6 Data Deliverables

The Contractor must provide a matrix, which states the delivery method for each CDRL deliverable (e.g. Compact Disk, flash drive, Webpage, email, etc.).

All data delivered and data made available during this contract must be furnished electronically in accordance with DD Form 1423-1. Specific deliverables required and schedules are stated in the SOW and described in Section J.

All data must be delivered in accordance with DD Form 1423-1 and included a Letter of Transmittal (LT) to the Government CO. The LT must indicate the contract number, Contract Line Item Number, Sub-Line Item Number, Data Item Number, Title and Subtitle (when applicable) of the data, SOW paragraph number reference which required the data to be prepared, and the date of transmittal.

C.3.2.6.1 Management Performance Indicators

The Contractor must identify key indicators and metrics for tracking Contractor progress and performance throughout the period of performance. In addition, the Contractor must collect data related to the user satisfaction, cost of ownership, and operational benefits over the life of the program (return on investment).

DTFAWA-10-C-00052 Conformed Contract

The Contractor must provide status, resolution and trend analysis of high severity PRs as well as CRs. This data will support Government investment analyses, benefits quantification, and related activities. Data from the Performance Measurement System will serve as input to the Management Indicators Report (MIR).

The Contractor must provide monthly MIRs. The MIR must include at a minimum:

Progress/status reporting against contract deliverables.

A running history of progress in meeting schedules, including a brief description of activities and accomplishments during each reporting period.

A Risk Matrix maintained by the Contractor that identifies design, schedule, technical, resources, and other program element risks. The Risk Matrix must be updated with each monthly MIR.

Software metrics must include at a minimum: (1) Software Size e.g. Source Lines of Code (SLOC) to include at a minimum: New SLOC, Reused SLOC, Modified SLOC, and Total SLOC, (2) Organization Staffing, (3) Cost/Schedule Percent Complete, (4) Defects.

The Contractor must use the MIR to propose updates and changes, and document slippages to the deliverables schedule. Government Acceptance of the MIR does not indicate concurrence with the MIR content or proposed changes to schedule(s). The Contractor must deliver the MIR in accordance with CDRL M06.

C.3.2.6.2 Earned Value Management System

The Contractor must include TBFM in its Earned Value Management System (EVMS) in order to plan, control costs, measure performance, and identify cost and schedule variances. The Contractors EVMS must comply with provisions provided in Section I. The Contractor must use the same EVMS for all work performed, including subcontractors.

The EVMS must support identification and reporting of the status of the program as well as any program variances from established baseline. When a variance of 10% or more from baseline is identified, or a trend of increasing variance over a 90-day period where the cumulative variance is 10% or more, the Contractor must develop corrective action plans that identify root cause of variance and take immediate corrective measures to stop variance from growing.

Additionally, corrective action plan must include realistic courses of action to recover all or some of the variance identified.

The Contractor must prepare and submit a monthly IPMR starting within 30 days of successful IBR. The IPMR must utilize the most current EVMS data and include a monthly written analysis that examines the actual prime and subcontractor(s) expenditures measured against the planned expenditures. The Contractor must deliver the IPMR in accordance with CDRL M04.

The Contractor must ensure that the assumptions and content of the Estimate at Completion (EAC) and Budget at Completion (BAC) contained in the IPMR are consistent for each monthly submittal. The Contractor must provide the Government with written explanations for EAC changes as a result of comprehensive EAC updates within the management system.

The Contractor must track EAC changes from the baseline BAC during the period of performance of the program. Significant EAC changes must be incorporated into PMR presentations or sidebar discussions for management review.

The data used to generate performance…