DFO Segment 2 TO2 Draft 2.pdf

Task Order 2 STATEMENT of WORK (Draft 2) Screening Information Request (SIR) 693KA8-21-R-00001

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

WIDE AREA AUGMENTATION SYSTEM

Dual Frequency Operations (DFO) 2 [DFO-2]

Task Order 02 Technical Refresh and Enhancement FY 2022 to 2026

Statement of Work

1 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the

1. Task Order Scope This Task Order 2 defines the efforts for the achievement of Wide Area Augmentation System (WAAS) Dual Frequency Operations (DFO) 2 Technical Refresh, transition from point-to-point telecommunications infrastructure to the FAA’s cloud-based infrastructure, the transition from a closed to open network security posture, and development and implementation of WAAS Dual Frequency (DF) compliant L5 Signal-In-Space (SIS).

Unless otherwise noted, all baseline documentation, including the WAAS code baseline, will be provided as Government Furnished Information (GFI) at the initiation of the contract. The WAAS code baseline includes all fielded and development/test/monitoring code. Unless otherwise noted, WAAS development, integration, and test hardware sets will be provided to the Contractor as Government Furnished Equipment (GFE) at the initiation of the Contract.

Definitions of key WAAS terminology are included in Indefinite Delivery Indefinite Quantity (IDIQ) Contract, Section C, Appendix A. Background information on WAAS is available at https://gps.faa.gov.

2. Supplies or Services & Cost/Price The PRISM task order document will reflect the obligated funding and applicable lines of accounting. For informational purposes, a RECAP of FUNDS is provided for administrative purposes as an attachment to this Task Order.

2.1. Contract Line Item Numbers (CLINs)

This Task Order utilizes the following contract types: Cost-Plus-Fixed-Fee (CPFF) and Cost Reimbursable (CR) as included in the following CLINS:

CLIN

CLIN

DESCRIPTION

TYPE

FUNDS

CONTRACT

TYPE

SOW Reference ESTIMATED

COST

FIXED

FEE

TOTAL

0002 System Engineering

F&E CPFF 3 $ TBD $ TBD $ TBD

0003 Software Engineering

F&E CPFF 3 $ TBD $ TBD $ TBD

Hardware/Elec trical Engineering

F&E CPFF

3.2.1, 3.2.2, 3.3.2, 3.4, 3.4,

3.5. 3.6.1, 3.6.2, 3.6.3, 3.7.2, 3.7.3, 3.7.5, 3.7.6, 3.7.8, 3.7.9, 3.7.11

$ TBD $ TBD $ TBD

https://gps.faa.gov/

2 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the

0006 Program/

Laboratory Support

F&E CPFF 3.1, 3.2.2, 3.3.2,

3.4, 3.5, 3.6.2.1, 3.6.3, 3.7.3.5, 3.7.3.7

$ TBD $ TBD $ TBD

0009 Travel/ODCs F&E Cost 3.6.2.1, 3.6.3 Not To Exceed

$ TBD

0500 Hardware & Hardware Kits

F&E Cost 3.1, 3.2.2, 3.3.2, 3.4, 3.5, 3.6.2.1, 3.6.3, 3.7.3, 3.7.6, 3.7.8.10, 3.7.9, 3.7.11

$ TBD $ TBD

3. Tasks The Contractor must implement the functionality addressed in the subsequent sections in accordance with the WAAS Performance Specification, FAA-E-2892e, as tailored by this Task Order. The Contractor must update requirement tracing between the WAAS System Specification (A121) and the WAAS Performance Specification FAA-E-2892e, as tailored by this Task Order. The requirement tracing update must be performed as part of the Contractor’s first WAAS Release in accordance with Section 3.1 of this Task Order.

The Contractor is responsible for the design, development, and testing of all hardware and software that comprise a Release in accordance with Section 3.7 of this Task Order. As required in Section 3.7, the Contractor provides the final hardware and software to the FAA for final validation and fielding. The Contractor must support the FAA with remote support during Release fielding.

The Contractor must implement the requirements of this Task Order in a manner such that risks to the operational WAAS as part of design, development, and fielding efforts are eliminated or mitigated to the maximum extent practical. Except for the initial Release work efforts specified in Section 3.1, the Contractor must plan work performed under this Task Order such that Release development and fielding efficiencies are maximized.

The term ‘operational’ refers to hardware, software, tools and processes that contribute to the fielded WAAS capability and are incorporated into the operational baseline; ‘non-operational’ implies that the hardware, software, tool or process is not a component of the operational WAAS baseline.

3 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

3.1. Ground Uplink Subsystem Receiver Upgrade

The Contractor must integrate the new Ground Uplink Subsystem (GUS) Receiver into the WAAS Baseline. The Contractor must include the GUS Receiver upgrade as a component of the Contractor’s first development and implementation effort under this Contract.

The FAA will provide GFE/GFI G-III based GUS Receivers, product drawings and DO-178B Software Level (SL) D certified firmware to the Contractor. The FAA will provide GFI prototype code and redlined software and hardware requirements documents and hardware configuration drawings. This GFI supports the integration of the G-III GUS Receiver with the Signal Generation Subsystem (SGS) within the GUS.

The Contractor must design changes to the SGS to support either the receipt and broadcast of a separate test L5 WAAS User Message processing from the current, repeated L1 WAAS User Message. This change will support the introduction of the test L5 message in support of DF Limited Operational Capability (LOC)/Initial Operational Capability (IOC) efforts under Section

3.6 of this Task Order. The proposed design must include support for current and future satisfaction of security requirements per Section 3.5 of this Task Order.

The Contractor must generate the GUS Receiver Upgrade Design Document (Contracts Data Requirement List (CDRL) A201) based on the GFI material, describing the implementation approach with rationale for proposed differences from the GFI FAA materials. The Contractor must follow the requirements for design, development and test included in Section 3.7 of this Task Order.

CDRL A201 GUS Receiver Upgrade Design Document

Upon FAA acceptance of the GUS Receiver Upgrade design document, the Contractor must develop hardware and software upgrade kits for the fielded SGSs for all GUS sites, all impacted FAA environments, and all impacted GFE Environments. The Contractor must update all affected drawings that result from the integration of the new GUS Receiver, including GUS sites and GFE Environments.

Due to the nature of the GUS design and the impact of changing the GUS receiver, the GFE test environments do not provide the ability to completely verify this upgrade. The FAA will conduct a field test of the G-III GUS receivers at the FAA specified Geosynchronous Earth Orbit (GEO) Uplink Station pair before the completion of the Development Test (DT) for this release. To conduct this field test, the FAA will load Contractor formal DT GP test software, install Contractor provided GUS receiver kit at those GUS locations, and perform other modifications required at the GUS locations. The FAA will set the GEO to test mode at the

4 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

operator console for this test period. The G-III-GUS field tests (nominal 2 weeks) will allow the FAA to collect SIS verification (Code Minus Carrier corrected for Iono, Code-Carrier Coherence (CCC)), SGS restarts for fielded configuration Site-Specific Parameter (SSP)/Operational System Parameter confirmation, and GEO Orbit Determination performance analysis. The FAA will provide the results of this analysis to the Contractor as GFI. The data will verify that the new receiver does not degrade the ranging performance of the WAAS GEOs. If collected data indicates that the new receiver does impact GEO ranging performance, the FAA will confer with the Contractor to determine appropriate modifications.

The FAA will update and field all Wide-area Reference Station (WRS) changes required to accommodate a single G-III receiver baseline prior to Contractor completion of Release 1. The G-III and G-III GUS are the same G-III receivers in different configurations determined by the controlling computers.

3.2. WAAS Level D Processor Upgrade and Transition to Linux

The processor upgrade involves replacing all of the IBM p720 processors currently used in WAAS and WAAS support laboratories with x86 compatible processors running a Linux Operating System. The WAAS application will be migrated from the current Advanced Interactive Executive (AIX) operating system to Linux and from the current XL C/C++ compiler to a Linux-based compiler for x86 hardware. The current p720 processors host the DO-178B SL D processes of the WAAS application. WAAS Level D code must be compiled for 64-bit operation. Compliance with DO-178B SL D must be maintained as part of this upgrade. WAAS SL B code must be compiled for 32-bit operation as required by SC design. The processor upgrade must support WAAS security upgrades per Section 3.5.

3.2.1. WAAS Level D Processor Upgrade Trade Study

The Contractor must conduct a trade study, considering at a minimum of 3 options, to determine candidate upgrade options and a final recommendation for replacement of the WAAS p720 processors, Operating System, and associated compiler. The Contractor must document the results of the trade study and deliver in the Processor Upgrade Trade Study Report (CDRL A202). The trade study must evaluate and determine recommendations for the following areas, at a minimum:

• Hardware manufacturer

• Processor and workstation/server specifications

• Peripheral specifications (Universal Serial Bus storage, Ethernet and serial adapters, monitor and keyboard including keyboard, video, mouse (KVM) capabilities)

• Linux distribution and licensing

• C/C++ Compiler options

• Integrated Development Environment including source code editor and debugger

• Build generation environment

5 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

• Support for existing WAAS Commercial-Off-The-Shelf (COTS) components (e.g., BRASS, GLG, PKZIP, BX Pro, Curses, X/Motif) or, preferable, similar open-source replacement for the existing COTS components.

The following criteria must be included in the trade study (along with any Contractor-identified criteria):

• Reliability, Maintainability, Supportability (For hardware upgrade areas)

• Hardware and software driver support for peripherals (For hardware and Operating

System upgrade areas)

• Software development tool support (For Operating System, compiler, and environment upgrade areas)

• Support for maintaining 178B certification objectives (For all upgrade areas)

• Operating System Maintainability

• Security that includes support for WAAS security requirements and maintenance of security updates (for Operating System upgrade areas)

• Commercial Rack-mountable hardware

Additional Requirements:

• The Contractor must include candidate upgrade options for the development and build environments with support for an automated build process based on continuous integration.

• The Contractor must include candidate upgrade options for automated provisioning and configuration management of the operating system and workstation application baseline (i.e., replacement of the WAAS configurator toolset).

• All candidate upgrade options for processor and workstation/server specifications must include Error-Correcting Code (ECC), Random Access Memory (RAM) ECC RAM.

• All candidate upgrade options for processor and workstation/server specifications must include support for a 4k digital display interface.

• If the current WAAS WRS/GUS KVM units are not compatible with candidate upgrade options, then the Contractor must perform an analysis of potential replacements and include a recommendation in the trade study.

• All candidate upgrade options for the processor and workstation/server specifications must provide the same or better performance than current p720 hardware with respect to the WAAS application and network communications. The Contractor must include candidate upgrade options for replacing the current SNMP management software -

BRASS.

• All candidate upgrade options for the processor and workstation/server specifications must include enough storage to meet Operations and Maintenance (O&M) data retention requirements of FAA-E-2892e and derived requirements without the use of an external device and must include the capability to extract data if needed.

• The Contractor must coordinate with the FAA and provide a regular status of progress and updates on technical decisions during the performance of the trade study.

• For the processor, operating system, or compiler upgrades, the Contractor must assess any potential impacts to failure modes identified in the WAAS fault trees (provided as

6 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

GFI). If any potential threats are identified, the Contractor must coordinate with the FAA WAAS safety team to determine whether mitigations are necessary.

• The study must detail any risks associated with the Contractor’s recommendations as well as potential mitigations for those risks.

Based on the results and recommendations of this study, the FAA will select the upgrade options that will be incorporated into the WAAS 2 system and associated environments.

CDRL A202 Processor Upgrade Trade Study Report

3.2.2. WAAS Level D Processor Upgrade Implementation

Following the FAA’s selection of upgrade options, the Contractor must perform a detailed impact analysis to assess the required changes to the WAAS operational baseline and the baseline for WAAS support tools and environments (non-operational baseline). The impact analysis must address changes from the current 32-bit compiler to a 64-bit compiler. The results of this analysis must be documented in a Processor Upgrade Implementation Approach Report (CDRL A203). The report must include an operational and non-operational cutover strategy and must be submitted to the FAA for approval. The report must cover impacts on the GFE environments as well as the FAA environments in Oklahoma City. The Contractor must coordinate with FAA personnel to perform the analysis for Oklahoma City tools and environments.

The implementation approach report must include the Contractor’s planned approach for verification of high-level software requirements to ensure associated RTCA/DO-178B SL D objectives (or equivalent) are fully met.

CDRL A203 Processor Upgrade Implementation Approach Report

Concurrent with the delivery of CDRL A203, the Contractor must schedule a Design Review (DR) for this upgrade activity per Section 3.7.

Upon FAA acceptance of the Processor Upgrade Implementation Approach Report, the Contractor must complete the efforts necessary to implement the design and update the WAAS baseline, in accordance with Section 3.7 of this Task Order.

The Contractor must qualify all Commercial off-the-shelf (COTS) products including the Linux Operating System for use with RTCA/DO-178B SL D WAAS Operational code. The COTS qualification approach must include COTS requirements based verification and the COTS Safety Assessment Process. The Safety Assessment of all COTS function calls, identified by the COTS Safety Assessment Process documented in PNB W106-4-2-16, supplied with the Technical Data

7 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

Package in Section J, must address functional failures, their potential safety impact on the WAAS Operational code, and, where necessary, proposed software mitigation action. The COTS requirements based verification must provide sufficient evidence for the qualification of COTS products for use with the WAAS SL D Operational Code; this includes updates to COTS requirements, test procedures, COTS traceability (PNB 5-6-2-4), supplied with the Technical Data Package in Section J, and generation of test results for all COTS call used by the WAAS SL D Operational Code.

The Contractor must develop hardware and software upgrade kits for the deployment of the new processor at all WAAS sites, all impacted FAA environments, and all impacted GFE Environments. Hardware upgrade kits must include appropriate numbers of site spares.

Contractor must also provide an additional supply of depot spares for each new Contractor-supplied hardware item, commensurate in each case with Contractor’s reliability estimates for that item. The Contractor must develop the hardware and software upgrades required to update both GFE and FAA build generation, software development, software integration, system test, and performance monitoring environments. The Contractor must also update GFE environment documentation that is impacted by this change.

Additional Requirements:

• As part of the process to update the O&M software, Graphical User Interface (GUI) displays and screen output must be re-scaled for a 4k resolution wide-screen monitor.

• WAAS O&M software must be modified to use native Operating System support, when available, for application interfaces to peripherals. Legacy software design that addressed AIX interface limitations must be replaced by a native solution where available.

3.3. WAAS Automated Testing Improvements

In order to improve the efficiency of lifecycle maintenance for WAAS, the Contractor will evaluate improvements to software and system test capabilities. This activity must include a study to assess the current WAAS test capabilities and evaluate ways to improve processes, automate testing, and improve the generation of test documentation. Once the FAA has approved the study and agreed to a list of recommendations, the Contractor must proceed with the implementation of the test improvements.

3.3.1. WAAS Automated Architecture Development

The FAA would like to maximize the potential benefits of automated testing improvements during the performance of the processor upgrade implementation. The Contractor must conduct a study to investigate improvements to system and software test capabilities for WAAS. The Contractor must assess the existing capabilities as provided by the GFE environments, GFE tools, and current FAA processes. The Contractor must evaluate test coverage of system and software requirements and assess how existing tests can be automated and improved either

8 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

through modification or replacement. The study must include an evaluation of commercial and open source products for testing and test automation. The study must also include an evaluation of existing GFI tools and the potential for expanded capabilities of these tools.

The Contractor must generate and deliver to the FAA an Automated Testing Architecture Report (A204). The report must detail the results of the assessment of WAAS test capabilities and any recommendations for improvement.

Additional requirements for this study:

• Recommended improvements must support continued adherence to the verification objectives detailed in DO-178B Section 6. Additionally, the study must identify any tools requiring qualification as detailed in DO-178B Section 12.2.

• The Contractor must evaluate software tools that support collaboration and automation for the review of source code and software test documentation.

• In order to maximize the potential benefits of automated testing improvements during the performance of the processor upgrade implementation, the Contractor must evaluate software and system test automation improvements that can be used in the WAAS Level D Processor Upgrade. The evaluation must consider the time of the implementation of the improvements: Before, during, and after the efforts identified in Section 3.2, WAAS Level D Processor Upgrade and Transition to Linux. The evaluation must consider the scope of the implementation of the improvements. The Contractor must provide a recommendation based on the evaluation.

• The study must evaluate impacts upon software and system requirements that may result from the implementation of study recommendations.

• The Contractor must coordinate with the FAA and provide the regular status of progress and updates on technical decisions during the performance of the trade study.

The following criteria must be included in the evaluation of test capabilities (along with any Contractor-identified criteria) and included in Automated Testing Architecture Report:

• Usability of automatic report generation

• Flexibility of test case development

• Configurability of test scope and grouping of test cases

• Level of detail provided for troubleshooting test failure

• The ability to configure automatic notifications of test completion

• Requirements traceability for Level D code, and COTS baseline products

CDRL A204 Automated Testing Architecture Report

3.3.2. WAAS Automated Testing Implementation

Upon FAA approval of the Automated Testing Architecture Report, the Contractor must complete the efforts necessary to implement the recommended changes. As part of the

9 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

implementation, the Contractor must first perform a detailed change impact (Section 3.7.3.2.1) analysis that fully assesses changes to the WAAS operational baseline and changes to WAAS support tools and environments. The change impact analysis must also detail updates required for existing Contractor and FAA processes, plans, and procedures. During the performance of the change impact analysis, the Contractor must coordinate with the FAA on any commercial or open-source licensing requirements so that the FAA can ensure licenses are procurable by the government.

After completion of the change impact analysis, the Contractor must conduct a Design Review for the Automated Test capability per Section 3.7.2. At the Design Review, the Contractor must also provide a proposed schedule for deploying the capability at both the Contractor and the government facilities and a plan for implementation of upgrades at both sites.

Upon successful approval of the Automated Testing Design Review, the Contractor must proceed with the development, verification and qualification of the Automated Testing architecture. Tool qualification must be in accordance with RTCA/DO-178B Section 12.2.

During implementation, the Contractor must support the FAA with any updates required for FAA environments, processes, plans, or procedures. As necessary, the Contractor must develop hardware upgrade kits for the impacted GFE and FAA environments. The FAA will procure necessary software and licenses separately. The Contractor must support the FAA with installation, configuration and validation of completed hardware and software integration.

3.4. FAA Telecommunications Network Transition Solution Design, Development and

Implementation

Commercial telecommunications carriers have notified the Federal Communications Commission (FCC) and their customers that they will no longer provide services based on Time Division Multiplexing (TDM) technology. The availability of TDM-based technologies will decrease over time. The FAA intends to transition all voice and data communications from TDM-based communications to Ethernet-based communications interfaces and standardize on the use of the Internet Protocol (IP). The WAAS Terrestrial Communications Network (TCN) currently uses TDM links for wide-area connectivity. WAAS needs to be updated to transition away from TDM communications and into one of the more modern service offerings available through the FAA's telecommunications program. The Contractor must assess the available service offerings, develop a transition approach, and then design and implement a new communications architecture for WAAS.

Available FAA service offerings will be provided to the Contractor after Task Order Award. For purposes of costing this Task Order, the Contractor can assume two potential service offerings:

1) Operational IP (OPIP) network and 2) Private Ethernet Virtual Local Area Network (VLAN)

10 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

(PEV). The OPIP network is the FAA's primary network for operational IP traffic and is currently used to provide layer-3 communications for multiple systems with the NAS. PEV service consists of logical Ethernet VLANs provided over the OPIP network in a private enclave using Virtual Private LAN Service (VPLS) and MultiProtocol Label Switching (MPLS). Section J includes current WAAS Prime Contractor OPIP and PEV analysis results and FAA analysis and test results for OPIP. The Contractor must conduct a study to investigate the transition of the WAAS TCN from its existing TDM-based architecture to a new architecture developed using the FAA telecommunications service offerings that are available at the time of contract award. The study must determine candidate architectures and provide a recommended architecture for the WAAS TDM-to-IP transition. The FAA will provide prior study work for Contractor’s reference and information at contract award. The Contractor must document the results of this study with the proposed recommendation in a TCN Architecture Study Report (CDRL A205).

CDRL A205 TCN Architecture Study Report

Additional study requirements:

• The Contractor must ensure the recommended architecture includes external one-way interfaces that can support real-time data collection of live network traffic and low-latency forwarding of the traffic to external test systems. Note: Currently, this capability is provided by the WAAS Operations & Maintenance (O&M) External Interfaces (OEI) at the National Operations Control Center (NOCC) and Pacific Operations Control Center (POCC), by the WAAS External Interfaces (WEI) at the WMS Correction and Verification (C&V) sites, and the GUS External Interfaces (GEI) at the GUS sites.

• The Contractor must evaluate the impacts of architecture changes on the current system test environments and must ensure that system test capabilities are not adversely impacted by the recommended architecture.

• The Contractor must ensure candidate architectures meet the requirements of FAA-E- 2892E.

• The Contractor must ensure the recommended architecture maintains current subsystem-to-subsystem latencies.

• The Contractor must identify any new LRUs required for candidate architectures.

• The Contractor must evaluate potential cutover methods for each of the candidate architectures and develop a high level cutover plan. The cutover methods must ensure that all operational performance requirements continue to be met during the cutover time period.

• The study must focus on support for IPV4 but allow for potential future migration to

IPV6.

Upon FAA review and approval of the TCN Architecture Study Report, the Contractor must develop and deliver the TCN Architecture Design Approach (CDRL A206). The TCN

11 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

Architecture Design Approach must address adherence to FAA-E-2892e requirements. The Contractor must perform a detailed change impact analysis (Section 3.7.3.2.1) to assess the required changes to both the WAAS operational baseline and the baseline for WAAS support tools and environments. The results of this change impact analysis must be documented in the TCN Architecture Design Approach document.

CDRL A206 TCN Architecture Design Approach

The Contractor must also develop a TCN Detailed Cutover and Deployment Plan (CDRL A207).

This plan must provide a detailed approach for implementing the new TCN architecture, including a proposed schedule, site-by-site activities, and responsibilities for O&M operators as well as field personnel involved with the deployment of upgrades. The Contractor must include a listing of performance and operational risks associated with the upgrade including recommended mitigations. The Contractor must address adherence to all security requirements within FAA-E-2892e as part of the cutover process. The Contractor must consider service availability dates for the selected telecommunications services at individual WAAS sites. The Contractor must include the transition of WAAS development and test environments in the overall TCN transition planning.

CDRL A207 TCN Detailed Cutover and Deployment Plan

Upon FAA receipt and approval of the TCN Architecture Design Approach and TCN Detailed Cutover and Deployment Plan, the Contractor must conduct a Design Review.

Upon successful conduct of the Design Review and FAA acceptance of the design, the Contractor must complete the efforts necessary to implement the design and update the WAAS baseline, in accordance with Section 3.7 of this Task Order.

The Contractor must develop hardware and software upgrade kits for deployment of the modification at all WAAS sites, all impacted FAA environments, and all impacted GFE Environments. Upgrade kits must include appropriate numbers of site spares. Contractor must also provide an additional supply of depot spares for each new Contractor-supplied hardware item, commensurate in each case with Contractor’s reliability estimates for that item. The Contractor must develop the hardware and software upgrades required to update both GFE and FAA software integration, system test (including TCS testbed), and performance monitoring environments. The Contractor must also update GFE environment documentation that is impacted by this change.

12 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

3.5. WAAS Security Upgrades

The Contractor must conduct a study to document the feasibility, approach, and scope of implementing the security requirements of FAA-E-2892e, Section 3.5.7, into WAAS. If any of the requirements cannot be implemented due to potential impacts to WAAS operations, the Contractor must recommend a compensating approach to the WAAS Program Office for coordination with the FAA Security Office. The Contractor must also address process and/or procedures changes by the WAAS Operators or second-level support function to address satisfaction of security requirements and/or improve the WAAS security profile. The Contractor must document the results of the study in the WAAS Security Requirement Study Report (CDRL A208).

CDRL A208 WAAS Security Requirement Study Report

The Contractor must develop and deliver a WAAS Security Architecture Design report detailing the satisfaction of the security requirements of FAA-E-2892e (CDRL A209) as analyzed in the WAAS Security Requirement Study Report. The WAAS Security Architecture Design must include derived requirements and detail on how the proposed architecture meets or exceeds the WAAS security requirements while minimizing impacts to WAAS operational performance, maintenance frequency, and development and lifecycle costs. The Security Architecture design must include industry-standard commercial products and must provide a rationale as part of the WAAS Security Architecture Design report where commercial products are not recommended for meeting security requirements. The Security Architecture design must also address the implementation of security updates as part of other defined Release activities under this Task Order.

Commercial security solution products must be selected based on functional performance, ease of integration into WAAS, scalability, and maintainability. Wherever possible, products must be selected that can perform multiple security functions and hence meet multiple security requirements by implementing a single solution.

CDRL A209 WAAS Security Architecture Design

Upon FAA approval of the WAAS Security Architecture Design report, the Contractor must implement the security requirements identified.

The Contractor must implement the security requirements contained in FAA-E-2892e Sections 3.5.7.1, 3.5.7.2, 3.5.7.5, and 3.5.7.6, either as part of the GUS Receiver upgrade or before AIX- Linux transition.

13 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

The Contractor must implement the security requirements identified in FAA-E-2892e Sections

3.5.7.3 and 3.5.7.4 as part of the AIX to Linux transition and before the TCN transition solution.

The Contractor must address the security upgrade aspects within the Release documentation associated with the selected Release(s). If a stand-alone security Release is necessary, the Contractor must follow requirements in Section 3.7 of this Task Order.

For each set of security upgrades introduced into the WAAS, whether as part of other development activities or as a stand-alone Release, the Contractor must develop security implementation kits for the Government-provided test systems and the FAA tests systems.

3.6. WAAS Dual Frequency Service

Dual Frequency (DF) WAAS services will be designed, developed, tested, and deployed by WAAS DFO-2 Contactor as part of DFO 2. The DF service introduction is separated into three phases: DF LOC, DF IOC and DF Final Operational Capability (FOC). The DF LOC capability must generate WAAS user messages compliant with the Dual-Frequency Multi-Constellation (DFMC) Satellite Based Augmentation System (SBAS) Standards and Recommended Practices (SARPs) and the DFMC SBAS Minimum Operational Performance Standards (MOPS) -compliant L5 Signal in Space (SIS). The DF LOC capability must provide the L5 messages to an operational GUS for over-the-air broadcast for non-safety-of-life use only. The DF IOC efforts will transition the DF LOC non-aviation use L5 SIS to aviation use on the Linux platform.

This Task Order is limited in scope to DF LOC and DF IOC design, development, and deployment. DF FOC design, development, test and deployment will be covered under a separate, to be developed, Task Order. The FAA is planning for the DF LOC and IOC capabilities to be completed by the Contractor no later than the date referenced in Attachment 2.

The Contractor must design the DF LOC and IOC capabilities using a Split C&V configuration:

the DF L5 message generation and integrity processing must be conducted on Correction and Verification (C&V) equipment separate from the C&Vs supporting the current operational Single Frequency (SF) service WAAS. The DF LOC and IOC design must use existing WRS sites without modification.

The Contractor can assume that the Covariance User Differential Range Error algorithm will be in the operational WAAS baseline prior to the start of this Task Order. Also, FAA has provided new and updated DF Algorithm Description Documents (for which the FAA is solely responsible) and the DF Fault Tree in the Technical Data Package made available to vendors prior to the release of the Final SIR. The FAA will perform algorithm performance analysis, 14 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

evaluate integrity performance, and conduct Hazardously Misleading Information (HMI) analysis.

The Contractor must modify processes as needed and in coordination with the FAA described in Section 3.7 to support specification and software changes that are common to both the existing WAAS Single Frequency baseline and the new DF LOC/IOC baseline. The Contractor must recommend and support changes to Section 3.7 processes as agreed upon by the Contractor and the FAA.

It is anticipated that the DF LOC and IOC capabilities will be developed from the existing WAAS AIX corrections processor baseline. The remainder of this section assumes that the Contractor DF LOC efforts start with the existing WAAS AIX baseline. However, the Contractor may elect to satisfy the DF LOC and IOC required work efforts and performance requirements via an alternative solution.

If such a methodology is proposed in the Contractor’s response to the SIR, the Contractor must articulate proposed modifications to impacted sections of this TO 2 Statement of Work as appropriate and must provide this modified TO 2 SOW with the proposed solution in its response to the SIR. The Contractor must identify how the proposed solution will support existing WRS hardware and software, without modification. The Contractor must also identify impacts to sparing and logistic functions, impacts to system certification and HMI analysis, impacts to operator workstations, impacts to operator and maintainer workflows, and impacts to maintenance functions. The Contractor must also address DF LOC/IOC/FOC system capability transfer to the FAA’s Operations and Maintenance organization for system maintenance efforts by the FAA after capability delivery by the Contractor.

Note: The DFMC SBAS MOPS (DFMC MOPS) will be a final draft version at the time of DFO 2 SIR release. It is anticipated that the DFMC MOPS will be finalized prior to start of the Contract or shortly thereafter. No substantive changes are anticipated in the approved DFMC MOPS. Any substantive changes will be negotiated between the FAA and the Contractor after final approval of the DF MOPS.

3.6.1. DF LOC/IOC Architecture

The Contractor must generate a DF LOC/IOC Architecture Design Document (CDLR A210) that meets the requirements outlined below. The Contractor must hold monthly meetings with the FAA during the development of the DF LOC/IOC architecture.

CDRL A210 DF LOC/IOC Architecture Design Document

15 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

Unless otherwise proposed and accepted by the FAA, the DF LOC design and build must use existing IBM processing platforms and AIX operating system for the corrections processor and existing safety computer platforms for the safety processor. The use of existing IBM processing platforms allows for development with a stable platform and known performance baseline and decouples DF LOC development from AIX-Linux transition efforts. The existing IBM processors and Safety Computers will be provided as GFE. The DF LOC design must ensure that the SF WAAS performance is not impacted nor degraded during all phases of DF LOC and IOC implementation.

The Contractor must design the capability to correct the L1/L5 ionosphere free pseudorange, develop associated messages for the SBAS L5 SIS, and transmit the messages through the GEO satellite payloads. The DF LOC system must support L5 SIS transmission from at least two WAAS GEO satellites. The Contractor must implement appropriate loop control and logic to support use of the L5 WAAS SIS in combination with the L1 WAAS SIS to generate an ionosphere-free pseudorange by DF-capable WAAS receivers.

The DF LOC C&V(s) must maintain information security separation between operational and DF LOC equipment The Contractor must modify the C&V Computer Software Configuration Item (CSCI) to process the GPS L5 pseudorange in place of the existing L2PY processing, generate the L5 messages per FAA-E-2892e requirements and the GFI-provided L5 message scheduler, update SL B monitors for DF operation (including DF Ranging), and remove any unneeded monitors. DF specific algorithm design documents are provided in the Technical Data Package (Section J) of the Contract.

The Contractor must document all proposed monitor additions, deletions, and modifications to support DF L5 message generation and monitoring as part of the DF LOC/IOC Architecture Design Document. The Contractor must remove or modify integrity monitors, including but not necessarily limited to:

• Grid Ionospheric Vertical Error, Range Domain Monitor, L1/L2 Bias (Removed)

• Ionospheric related functions (Removed)

• DF Range Error (DF equivalent to the User Differential Range Error)

• Code-Carrier Coherency (CCC) Monitor (Modified)

• DF Signal Quality Monitor (SQM) (DF equivalent to the Signal Quality Monitor)

• User Position Monitor (UPM) (Modified)

• Code Noise and MultiPath (CNMP) Monitor (Modified)

When provided to the GUS, the L5 message generated by the DF C&Vs must be transmitted via the operational GUSs in place of the default L5 message generated by the local SGS. The

16 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

Contractor must include the capability to receive, validate, and broadcast the L5 message at the GUS without interference to the L1 WAAS capability. The DF LOC SGS-specific changes must maintain information security separation between operational and DF LOC processing.

The Contractor must develop an O&M capability for DF system operation. The Contractor must coordinate with the FAA regarding specific O&M display configurations and operational changes. DF O&M design must consider future capability integration with operational WAAS O&M sites and FAA Operator operations.

The Contractor must investigate potential failures and errors (hardware, software, safety monitors, etc.) across each WAAS subsystem and provide recommendations for appropriate responses for DF capability. The Contractor must formulate this aspect of the study to consider not only the DF LOC capability where SF service must not be impacted but also the hierarchy of SF and DF service impacts with the operational introduction of DF IOC.

The DF LOC/IOC Architecture Design Document must identify the implementation approach.

The implementation approach must enable early over-the-air broadcast of L5 messages. The implementation approach must introduce capability into the L5 broadcast, provide for periods of monitoring and assessment, and provide for algorithm updates during HMI data collection and analysis. The implementation plan must address the cutover from the DF LOC system to the DF IOC system.

The DF LOC architecture must incorporate necessary security enhancements as defined under Section 3.5 of this Task Order that are necessary to support initial non-operational service introduction.

The Contractor must coordinate with the FAA regarding specific C&V cabinet configurations.

The Contractor must provide for at least two sets of DF LOC specific C&V equipment complements. The Contractor must provide, if and as required by design, two complements of DF LOC specific O&M equipment.

The Contractor must provide DF LOC modification kits to support L5 SIS transmission from two WAAS GUS site pairs (four total GUS sites).

The DF LOC L5 C&V and O&M equipment will be hosted at the Contractor’s facility and the FAA WAAS Engineering site in Oklahoma City.

The Contractor must present the DF LOC Architecture Design to the FAA after delivery of the initial DF LOC/IOC Architecture Design Document (CDRL A210).

17 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the

3.6.1.1. DF LOC Design and Implementation

The Contractor must complete the detailed design of the DF LOC system. The Contractor must follow the requirements for design, development, and test included in Section 3.7 of this Task Order with the exception that the DO-178B SL B and D software do not require software certification as a test capability. The Contractor must identify new hardware and software configurations to be generated.

The Contractor must work with the FAA to support WAAS Operator human factors and other considerations for DF IOC O&M display design and integration with existing Single Frequency O&M design, functionality, and operations.

The Contractor must support the FAA in data collection and processing to assess DF LOC operational performance for the duration of the DF LOC period. The Contractor must support FAA analysis efforts to modify DF algorithms and monitors to increase performance. Contractor rework may be required for acceptable DF LOC operation.

The Contractor must deliver new WAAS development, integration, and test assets for DFO LOC development, maintenance and operation period. The Contractor must document and deliver all updated or developed tools under DFO LOC. The Contractor must deliver updated and new DFO LOC documentation to the FAA.

The Contractor must operate and maintain the DF WAAS LOC capability.

The FAA will be the lead for both the DF Fault Tree generation and DF Integrity Analysis. The Contractor must support the FAA in data collection for the WAAS Dual Frequency L5 signal integrity analysis and with fault tree node computations and supporting documentation. The Contractor must provide support in the conduct of HMI data reduction and analysis.

DF LOC capability is considered complete when system integrity requirements have been validated by the WAAS Integrity Performance Panel and DF IOC performance requirements (per Table 1) below are met.

The Contractor must monitor the completed DF LOC system for a period of a least 30 days for stable operation before implementing any changes in support of DF IOC capability build-out.

3.6.2. DF Initial Operational Capability

The DF IOC efforts transition the DF LOC non-aviation use capability to a certifiable service for aviation use broadcast from all WAAS GEOs. The Contractor must update the DF IOC specific aspects of the DF LOC/IOC Architecture Design Document (CDRL A0209), updating changes between the DF LOC and IOC systems to support processor and operating system updates, 18 | P a g e “This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

security, IP-cloud implementation and other relevant changes, and re-deliver to the FAA for review and approval.

The Contractor must update impacted WAAS CSCI and ICD CDRLs as separate revisions for those that are different for SF versus DF hardware/software baselines.

The Contractor must migrate the DF LOC SL D software and toolsets to Linux based solutions implemented under Section 3.2 and 3.3 of this Task Order. The Contractor must also migrate and incorporate all security and FAA cloud-based communications network solutions implemented under Section 3.5 of this Task Order into the DF IOC equipment configuration.

The Contractor must modify fielded SGS hardware and software to support operational integration of the DF IOC capability.

The Contractor must deliver in place all GFE environment upgrades to support DF IOC to the FAA as part of GFE environment updates and must generate kits for FAA DF environment updates. The Contractor must satisfy all release development and test requirements per Section

3.7 of this Task Order. The Contractor must update, document, and deliver all tools impacted by the transition from DFO LOC to DFO IOC capabilities. The Contractor must deliver updated and new DFO IOC documentation to the FAA.

The DF codebase must demonstrate compliance with DO-178B Objectives for SLs B and D.

The Contractor must construct and deliver three DF IOC C&V…