ERAM Section C.docx

Section C

En Route Automation Modernization (ERAM) Enhancement, Sustainment, and Operational Support Statement of Work (SOW)

April 27, 2024

44 | Page Acquisition Sensitive ERAM SOW

Table of Contents

ERAM SOW

Acquisition Sensitive

C.1 Introduction

C.1.1 Background

The original ERAM contract was awarded to Lockheed Martin Corporation in 2002 to replace the HCS at all CONUS En Route facilities with ERAM. The contract was novated to Leidos Corporation in 2017. Since the FAA plans to continue to use ERAM at current locations for several more years, a follow-on ERAM contract is needed to support the ERAM and the planned NextGen capabilities in the En Route Automation environment.

All en route air traffic controllers in Federal Aviation Administration (FAA) Air Route Traffic Control Centers (ARTCC) located in the Continental United States (CONUS) use ERAM to provide Air Traffic Control (ATC) of aircraft flying in U.S. Airspace. ERAM interfaces to ATC towers, Terminal Radar Approach Control (TRACON) Facilities, the Air Traffic Control System Command Center, Flight Service Stations, and other agencies such as the Department of Homeland Security and the Department of Defense. ERAM and its associated hardware and software are the backbone of en route operations and flight-data processing for NAS operations; and is designed to support the evolution to the Next Generation Air Transportation System (NextGen).

The ERAM system provides the infrastructure necessary to transition the NAS to NextGen capabilities and the FAA continues to plan for future En Route automation capabilities and the evolution of En Route ATC automation to adapt and support Next Generation air traffic systems using ERAM as the foundation for the development and integration of these new functions into the NAS. The smooth transition of the operations and associated procedures for using the new capabilities are essential to providing a seamless incorporation of new NextGen enhancements.

The continuing ERAM acquisition strategy is aligned in phases to allow for time sensitive tech refresh, deployment of future applications, necessary enhancements, system sustainment, and continued operational service. Continuous improvements and efficiency will be achieved through planned future acquisitions. This Statement of Work (SOW) addresses requirements for a new ERAM follow-on contract that will fulfill future ERAM Enhancements programs, new NextGen capabilities, and Operational/Sustainment Support at all current and future operational ERAM sites.

Responding to requirements to reduce the number and type of displays present in the operational environment while continuing to present a variety of static and dynamic information from multiple sources to controllers and supervisors, ERIDS utilizes proven Commercial Off-the-Shelf (COTS), non-proprietary technology to rapidly and dependably channel administrative and operational information practically instantaneously to operational positions. Utilizing digital technology, ERIDS captures and displays constantly changing and evolving National Airspace System (NAS) data like Notices to Airmen (NOTAMS), Approach and En Route Charts, and other data to significantly reduce the amount of paper required on the control room floor.

C.1.2 Purpose

This Statement of Work (SOW) delineates the Contractor's work tasks required to enhance and maintain the En Route Automation and Modernization (ERAM), including En Route Information Display System (ERIDS), and to produce, implement, and provide support for a limited number of ERAM/ERIDS systems to be used for operational testing; and operational support. The work performed under this contract will be in support of the Operational ERAM system at all current and future operational ERAM sites within the FAA's National Airspace System (NAS).

C.1.3 Scope

The ERAM system is in use at all Air Route Traffic Control Centers (ARTCCs) in the contiguous United States (CONUS), the William J. Hughes Technical Center (WJHTC), and the FAA Academy (FAAAC). There are options in this contract to provide additional ERAM systems/capabilities at locations supporting any United States-controlled airspace if the FAA desires additional standardization of en route automation or capabilities. En route ATC services must be continuously provided 24 hours per day, seven days per week, using ERAM.

ERIDS is a system designed to provide information from a variety of diverse sources, static and dynamic, to Air Traffic Controllers in the En Route environment through utilization of a single, standardized display device. ERIDS has been deployed and operational at all planned sites since December 11, 2007.

This SOW is applicable to the ERAM, ERAM Enhancement and ERAM Sustainment programs and requires the Contractor to provide for the development, enhancement, production, deployment, and sustainment of ERAM, including ERIDS, in the NAS. The Government requirements are provided in Section J Attachments. Specifically, the ERAM System Specification Document (SSD), FAA-ER-2979 (Revision: I) contained as a J-1 Attachment and the ERAM Program/Product Requirement Assumptions needed for the development of Contract Change Proposals (CCPs) will be contained within individual J-6 Attachments.

The SOW identifies the scope of activities of which the Contractor may be asked to perform on this contract. The applicability of the SOW paragraphs is based on the individual Contract Line Item Numbers (CLINs) and/or Contract Change Proposals (CCPs) negotiated between the Contractor and Government. The Contractor will not be required to perform to any SOW paragraphs not authorized through a CCP.

This SOW structure is similar to the FAA Work Breakdown Structure (WBS) 5.2 at the program level. As a result, In-Service Management (ERAM Sustainment and Operational Support) is contained in section C.4 In-Service Management. Additionally, Section C.4 In-Service Management will form the base of the new ERAM contract for the initial period of performance and options to cover the entire period. Section C.3 Enhancements and Sustainment tasks cover En route enhancements covered by F&E funding as approved by the FAA Joint Resources Council (JRC). Section C.3 Enhancements and Sustainment efforts will be bid separately as needed and will be negotiated and awarded using the CCP process. Section C.4 In-Service Management efforts will be covered by Operations Funding and will also use the CCP process.

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. The latest version of these documents as of the contract date must apply. In the event of conflict between this SOW and any of the applicable documents cited below, the provisions of this SOW must apply.

C.2.1 FAA Specifications

C.2.2 FAA Standards

FAA-G-2100G FAA Electronic Equipment Specification

FAA-STD-025D Preparation of Interface Control Documentation

FAA-STD-028B Contract Training Programs [This standard has been canceled without replacement]

HF-STD-001B FAA Human Factors Design Standard (HFDS)

HF-STD-010A FAA Color Use In Air Traffic Control System Displays

C.2.3 Military Standards

MIL-STD-129N Marking for Shipment and Storage

MIL-HDBK-470A Designing and Developing Maintainable Products and Systems

MIL-HDBK-781A Reliability Testing for Engineering Development, Qualification, and Production

MIL-HDBK-881 Work Breakdown Structures for Defense Material Items

MIL-STD-973 Configuration Management

MIL-STD-1390D Level of Repair Analysis

MIL-PRF-28000A Digital Representation for Communication of Product Definition Data Initial Graphic Exchange Specification (IGES) Application and IGES Application Protocols

MIL-DTL-31000 Technical Data Packages, General Specification for

MIL-PRF-49506 Logistics Management Information

C.2.4 Federal Standards

DOD-STD-1686 Electrostatic Discharge Control Program for Protection of Electrical and electronic Parts, Assemblies and Equipment

DOD-STD-1700 Data Management Program

C.2.5 Other FAA Documents

FAA Order 1600.54 FAA Automated Information Systems Security Handbook

FAA Order 3900.19 Occupational Safety and Health

FAA Order 6000.30 Policy for Maintenance of the NAAMS T&E Acquisition Management System Test and Guidelines Evaluation Process Guidelines

FAA Order 9550.8 Human Factors Policy

C.2.6 Non-Government Documents

ISO 9001:2015 International Organization for Standardization to the development, supply, installation, and maintenance of software

AS9100: 2016 Quality Management Systems - Requirements for Aviation, Space, and Defense Organizations

UCC/EAN-128 Bar Code Symbol

IEEE/EIA 12207.1 Guide for IAO/IEC 12207, Standard for Information Technology-Software Life Cycle Processes-Life Cycle Data

RTCA DO-278A Software Integrity Assurance Considerations for Communication, Navigation, Surveillance and Air Traffic Management (CNS/ATM) Systems

RTCA DO-330 Software Too Qualification Considerations

RTCA DO-331 Model-Based Development and Verification Supplement to DO-178C and DO-278A

RTCA DO-332 Object-Oriented Technology and Related Techniques Supplement to DO-178C and DO-278A

RTCA DO-333 Formal Methods Supplement to DO-178C and DO-278A

C.2.7 Obtaining Copies of Documents

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

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

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

· Copies of ANSI/ASQC-Q-9001-2015 and ISO 9000-3 can be obtained from the following source: American Society for Quality Control 611 East Wisconsin Avenue P.O. Box 3005; Milwaukee, Wisconsin 53201-3005. Phones: (414) 272-8575 or (800) 248-1946. The Fax is: (414) 272-1734.

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

C.3 Enhancements and Sustainment

Enhancement of the existing ERAM system is achieved via the development of new functional enhancements into future ERAM software releases and system modifications. Sustainment efforts include replacement of aged hardware and CAS in addition to any software modifications needed to support these equipment replacement activities. For the purposes of this SOW, Sustainment activities (including Tech Refresh efforts) are considered to be system enhancements. All SOW requirements applicable to Enhancements work activities are also applicable to Sustainment work activities. The required major development milestones and schedule information for future ERAM software releases are contained in the ERAM Release Plan in Section J-2. Typically, there are two major ERAM software releases planned for delivery each year but release planning will be adapted based on operational needs and new program requirements.

The Government is solely responsible for determining the operational priorities and packaging of the new functionality enhancements into future ERAM releases based on assessment information provided by the Contractor. Since each ERAM software release is a unique collection of functionality and software defect fixes, the Contractor must assess the feasibility of completing the development activities to satisfy the ERAM Release Plan criteria for each individual functional item requested by the Government for packaging in each software release. As more content is packaged in a software release and the further into the software development cycle before a new content item is identified for packaging, the more critical the assessment becomes to ensure the availability of Contractor resources to meet the release milestone/schedule requirements for all of the packaged content. The Government and Contractor will coordinate and work collaboratively together to assess and determine the appropriate future ERAM software release packaging for new functional enhancements.

After the Contractor positively assesses that the content will fit into the software release, the Contractor is responsible for developing and delivering the new functionality enhancements into the ERAM software release as packaged by the Government. The Contractor requires Government authorization to proceed with the engineering analysis activities for functionality/content packaged in an ERAM software release. The Contractor must also receive Government authorization to proceed with software implementation after approval of the engineering analysis activities.

C.3.1 System Engineering

The Contractor must execute systems engineering (SE) activities necessary for the definition, design, development, manufacture, verification, performance measurement, integration, and testing of the system in accordance with the ERAM System Engineering Management Plan (SEMP). SE activities include analysis, design, component selection, development, and integration to modify the system and must consider all aspects of performance, quality, life cycle cost, compatibility, maintainability, reliability, sustainability, schedule, data processing reserves, and future growth requirements.

The Contractor must maintain effective control over the SE process, including subcontract items and services, to ensure that cost, performance, and schedule are met, provide early detection and correction of problems, and to reduce risk. The Contractor must specify a senior system engineer with the authority to serve as Point of Contact (POC) for SE tasks.

All ERAM system SE activities must account for the differences in design, configuration, and use between the operational sites, the WJHTC, and the FAAAC.

The Contractor shall conduct Systems Engineering Risk Reduction activities to reduce the risks associated with requirements interpretation, system design development, and operational suitability of ERAM enhancements. These activities shall also serve as a basis for identifying critical focus areas for test and evaluation of hardware and software. In conducting these activities, the Contractor shall utilize the processes, procedures, and tools previously developed for ERAM.

C.3.1.1 System Design

There are two system design approaches for incorporating new enhancements in the ERAM; Nominal Change Request (CR) and Major Capability.

The nominal CR approach is that most future ERAM software releases are a collection of new unrelated enhancements within a single software release. ERAM software release total size is typically between 15,000 and 25,000 source lines of code (SLOC) with multiple CR changes in the 50 - 2000 SLOC range. The collective group of enhancements are typically funded by multiple sources including one or more ERAM programs (ERAM Enhancements, ERAM Sustainment) or by external program(s) with NEXTGEN capabilities or an external program that requires changes in ERAM to support their new functional capabilities. For the nominal CR design approach, the SIG/PRED review/approval activities are intended to satisfy the system design review activities for the functions contained in the SIGs and PREDs.

The Major Capability design approach accommodates significantly large and/or complex capability or set of capabilities that will be added to ERAM (e.g., Data Communications). In this case, the new capability is typically developed as a separate development baseline. For a major capability design approach, the system design changes for the full major capability will likely be subdivided into multiple SIG/PRED documents. The complete collection of SIGs and PREDs is needed to fully represent all of the engineering updates needed to implement the new major capability. Additionally, due to the size and capability of the new capability, formal system design review process activities will likely be required to augment the information in the SIG/PRED documentation, with emphasis on the new capability functions that cross multiple SIGs and PREDs. If so, the formal system design review requirements will be identified in the Contractor Change Proposal (CCP).

C.3.1.2 Design Reviews

For the nominal CR design approach, the SIG/PRED review/approval activities is intended to satisfy the system design review activities for the functions contained in the SIGs and PREDs. Before the submission of a SIG or PRED for review, the Contractor must provide charts describing the high level functionality that will be provided in the implementation of the SIG/PRED. These charts must be presented to the Government and approved prior to beginning work on the SIG or PRED document.

For the Major Capability design approach the Contractor must conduct the following technical reviews:

· System Requirements Review (SRR)

· System Design Review (SDR)

Review presentations must be based upon the Contractor’s system and subsystem engineering efforts and related documentation. At each review, the Contractor must provide back-up data on assumptions made and methodologies used in arriving at specific recommendations and conclusions for the design approach. The Contractor must make available for reference and inspection at the reviews: applicable engineering data, specifications, drawings, schematics, design and test documentation, software development files, schedules, working papers, and results of studies and analyses.

There must be a free exchange of ideas between the Contractor and the Government at the formal reviews to establish program progress, identify technical problems, and resolve problems in a timely manner. Key Contractor personnel must be available to respond to Government questions.

The Contractor must notify the Government of readiness for a review at least 14 calendar days in advance of the planned start of each review.

The Contractor must submit an agenda for all technical reviews at the time of notification of readiness. The Contractor must provide the documentation for review at least seven (7) calendar days prior to the scheduled meeting in order to facilitate understanding of the design and discussion points for the meeting. The minutes must include documentation of any conclusions and/or agreements between the Government and the Contractor, and action items resulting from the review with planned closure dates, responsible person(s), planned action(s) to resolve and any Government action(s) required. The status of each open action item must be reviewed at appropriate technical working meetings until the Government concurs with closure.

C.3.1.2.1 System Requirements Review

C.3.1.2.1.1 System Requirements Review Entrance Criteria

The Contractor must conduct an SRR on significant system enhancements/modifications as directed by the Government. The objective of this review is to ascertain the adequacy of the Contractor’s efforts in defining system requirements.

C.3.1.2.1.2 System Requirements Review Presentation

The Contractor must present and review the following items with the Government, as they relate to system design:

· Analysis of the relevant portions of FAA-ER-2979, including crosswalk of System/Subsystem Specification (SSS) to FAA-ER-2979 that demonstrates mapping of requirements between the two specifications

· Identification of all new/modified SSS requirements traceable to the new/modified FAA-ER-2979 requirements directed for implementation for the Government

· Reviewed the High Level Test Approach for which requirements will be tested in CRV vs. Regression and which requirements are tested in full lab vs. Virtual Test Lab (VTL)

· Preliminary functional flow analysis and mapping of new/modified FAA-ER-2979 requirements to Hardware Configuration Item/Computer Software Configuration Item (HWCI/CSCI) including indication of which requirements are new developmental requirements

· Identification of Technical Risks, Issues, Opportunities (RIO), including assumptions, assessments, trade-offs, mitigation plans and alternative approaches

· Identification of design-driving/cost-driving requirements and potential cost saving alternatives

· Security requirement analysis

· Configuration Management overview, with emphasis on maintenance of requirements and design baselines

· Transition strategy to the new capability, including fallback The Government reserves the right to tailor the above components of the SRR presentation to delete items not required for a specific SRR and/or to add new items as deemed relevant. Such discussion will be held with the Contractor at the time the requirement for an SRR is established by the Government.

C.3.1.2.1.3 System Requirements Review Acceptance Criteria

The Contractor must meet the following acceptance criteria, to successfully complete the SRR:

· Allocation of new and modified FAA-ER-2979 requirements HWCI/CSCIs and indication of new developmental requirements and their allocated HWCI/CSCIs

· Gain concurrence on test methodology including tests that will be performed in the lab vs. VTL

· Demonstrate mapping of new and modified FAA-ER-2979 requirements to the Contractor’s SSS requirements C.3.1.2.2 System Design Review

C.3.1.2.2.1 System Design Review Entrance Criteria

The Contractor must conduct an SDR on significant system enhancements/modifications as directed by the Government. The Government may direct the Contractor to conduct an SDR even if an SRR was not required. If an SRR was required, the SRR must be approved by the Government before an SDR may be conducted. Additionally, all SRR action items must be closed prior to conducting the SDR, unless the Government has given permission to proceed. The purpose of this review will be to:

· Determine that the design including all configuration items, satisfies the performance and engineering specialty requirements of the configuration item development specifications

· Establish the design compatibility among the configuration items and other items of equipment, facilities, computer software and personnel

· Assess configuration item design and development risk areas on a technical, cost, and schedule basis

C.3.1.2.2.2 System Design Review Presentation

The SDR must cover all ERAM changes. For items that are not Contractor-developed, the Contractor must provide a functional/physical description of the item, the results of the analysis that verifies the item will meet the associated technical requirements, and a description of the interfaces with other CIs. At the SDR, the Contractor must describe the products, processes, methodologies, milestones, and measurements to be used in conducting system development activities. The Contractor must describe its plans for acquiring and developing the required software to meet contract requirements. The Contractor must describe their process for providing a system compliant with AS9100 D, Quality Management Systems - Requirements for Aviation, Space, and Defense Organizations.

As part of the SDR, the Contractor must present and review the following items with the Government:

· System overview and basic design approach for each HWCI and CSCI that shows use of an open architecture to promote modularity and scalability

· Architecture diagrams that provide data flow and control flow diagrams, and a design overview of each CSCI/HWCI

· Description of system interfaces and data flow diagrams

· Functional flow analysis and requirements allocation

· Operator controls and displays, and maintenance features overview, including examples of control and display screens

· Physical description including lists of materials and parts

· Commercial off the Shelf (COTS) and non-COTS items identification including:

· Results of any contractor make/buy decisions and/or tradeoffs

· Justification for any use of proprietary and/or non-COTs components

· Commercial software documentation, licensing agreements, and usage limitations

· Information, analysis and predictions of the reliability and maintainability of components

· Security considerations and design (see Section C.3.1.6 Security Program) including how interfaces will be protected, how system access will be controlled, availability and integrity of data

· Safety considerations

· Environmental Health and Occupational Safety (EHOS) considerations

· Environmental design concerns such as thermal control, electromagnetic compatibility/interoperability, technical risks, etc. in accordance with (IAW) FAA-G-2100G

· Power consumption goals for each component of the system

· Discussion of design tradeoffs

· Documentation status and availability, such as manuals for Contractor equipment and commercially available equipment, and notification on any proprietary or restricted design/process/components and information

· Quality Assurance overview

· Updates to Technical RIOs, including assumptions, assessments, trade-offs, mitigation plans and alternative approaches and any newly identified RIOs

· Identification of production long-lead items The Government reserves the right to tailor the above components of the SDR presentation to delete items not required for a specific SDR and/or to add new items as deemed relevant. Such discussion will be held with the Contractor at the time the requirement for an SDR is established by the Government.

Additionally, the Contractor must submit the following Contractor Data Requirements Lists (3) prior to the SDR:

· Updates to or Final System/Subsystem Specification IAW CDRL SE02

CDRL SE02 System/Subsystem Specifications (SSS)

C.3.1.2.2.3 System Design Review Acceptance Criteria

To successfully complete the SDR, the Contractor must meet the following acceptance criteria:

· Allocate all new/modified requirements in the requirements baseline to HWCIs and CSCIs

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

· Identify which requirements are satisfied by Non-Developmental Item (NDI) or COTS, which requirements are already implemented, but require modification, and which requirements require development for each HWCI and CSCI

· Present a preliminary design that shows how COTS/NDI, modified COTS/NDI, and new development will work together to satisfy the requirements baseline

C.3.1.3 Interface Documentation

The Contractor must participate in reviews of existing FAA Interface Requirement Documents (IRD, CDRL SE03) and Interface Control Documents (ICD, CDRL SE05) when technology…