AISS Draft Statement of Work (SOW) December 2022.pdf

Federal Aviation Administration

AJW Integrated Support Services

Statement of Work

(SOW)

DRAFT

December 5, 2022

AJW Integrated Support Services (AISS) Statement of Work i

Table of Contents

1 Introduction

1.1 Background

1.2 Scope of Work

1.3 Inherently Governmental Functions

2 References

3 Programmatic Support Requirements

3.1 Transformation of the FAA’s Telecommunications Enterprise

3.2 Zero Trust Architecture (ZTA) Security

3.3 Evolution of Air Traffic Control (ATC) Voice Communications

3.4 Evolution and Operation of Air Traffic Control Information Display Systems ... 6

3.5 Resiliency of Time and Frequency Sources

3.6 Integration and Operation of Wireless Communications Technologies

3.7 Integrated Security Architecture and Operations

3.8 Evolution and Operation of Enterprise Infrastructure, Messaging, and Security

Systems

3.9 NAS Infrastructure and System Modernization

3.10 Supply Chain Management and Supply Chain Risk Management

3.11 Maintenance Optimization

3.12 Integration of Unmanned Aircraft Systems (UAS) and Other Emerging

Technologies and Capabilities into the NAS

4 Functional Support Requirements

4.1 Engineering and Technical Services

4.2 Test and Evaluation Support

4.3 Integration and Implementation Support

4.4 Operations and In-Service Management Support

4.5 Software, Tools, and Technology Support

4.6 Business Intelligence and Data Analytics Support

4.7 Strategic and Operational Planning, Governance, and Policy Support

4.8 Acquisition Planning and Procurement Support

4.9 Program and Project Management Support

4.10 Contract Program Management

5 End Results/Deliverables

6 Place of Performance

7 Hours of Operation

8 Security Clearances, Certifications, and Accreditations

9 Government Portals and Information Management Tools

10 Travel and Other Direct Costs (ODCs)

Appendix A Acronyms and Abbreviations ........................................................................................... A-1

1 Introduction This Statement of Work (SOW) describes the Federal Aviation Administration’s (FAA) requirements for the AJW Integrated Support Services (AISS) acquisition that will provide technical and management support services required to fulfill the mission of the FAA’s Technical Operations (AJW) organization through an integrated, enterprise-level approach to performing the required work efforts.

The required services will support AJW in completing its roles and responsibilities relative to new initiatives and strategic initiatives specific to the evolution of the National Airspace System (NAS).

Each Task Order (TO) issued will have an associated TO SOW that identifies project-specific requirements such as programs to be supported, the place of performance, deliverables, and other pertinent information. Each TO will address specific initiatives, objectives, and functional areas within this contract-level SOW, with an emphasis on integration across AJW directorates, NAS programs/systems, and the functional areas identified in this contract-level SOW.

1.1 Background

AJW is part of the FAA’s Air Traffic Organization (ATO). AJW’s mission is to ensure a safe and efficient NAS through the effective management of air navigation services and infrastructure. The scope of AJW’s mission includes the integration, management, operation, maintenance, and modernization of the systems and services that comprise the NAS.

AJW is responsible for the operational management of critical NAS infrastructure. The NAS operating environment continually evolves as the result of the implementation of new technologies, new systems and services, and new cybersecurity capabilities to respond to a changing cyber threat environment. Addressing these challenges requires an enterprise-level and integrated approach.

AJW continuously evolves to provide the flexibility and resiliency to align with its ever-changing internal and external environment. AISS is structured to be a flexible and adaptable vehicle for obtaining technical and programmatic support services to meet the magnitude, diversity, complexity, and scale of AJW’s operational and programmatic challenges.

1.2 Scope of Work

There are three facets of the AISS scope of work: (1) the programmatic support required, (2) the functional support required; and (3) the organizations that require the support. These three different facets of the AISS scope of work are described in the subsections below.

Programmatic Scope The programmatic support required under AISS is defined based on the following set of FAA initiatives and AJW strategic objectives:

• Transformation of the FAA’s Telecommunications Enterprise;

• Migration to and Operation of a Zero Trust Architecture (ZTA) Security Model;

• Evolution and Operation of Air Traffic Control (ATC) Voice Communications;

• Evolution and Operation of Air Traffic Control Information Display Systems;

AJW Integrated Support Services Statement of Work

• Resiliency of Time and Frequency Sources;

• Evolution to and Integration of commercially-available wireless communications technologies and services;

• Establishment and Operation of an Integrated Security Architecture;

• Evolution and Operation of Enterprise Infrastructure, Messaging, and Security systems;

• NAS Infrastructure and System Modernization;

• Supply Chain Management and Supply Chain Risk Management;

• Maintenance Optimization; and

• Integration of Unmanned Aircraft Systems (UAS) and other emerging technologies and capabilities into the NAS.

Section 3 of this SOW identifies the high-level support programmatic support requirements associated with each of these initiatives and strategic objectives. Specific requirements within the scope of these programmatic work areas will be identified, defined, and issued under individually funded TOs and the associated TO SOWs.

The programmatic support required under this contract may address any systems, products, and services affected by or needed to accomplish the identified initiatives and objectives. This may include, but is not necessarily limited to systems, products, and services that are: (1) currently in operation within the NAS, (2) implemented in simulated environments; or (3) planned for implementation in the NAS. Programmatic support required under AISS may also include newly defined initiatives and strategic objectives that are related to the specific set of initiatives list above.

Functional Scope The next facet of the AISS scope of work is the types of functional support required. Any of the following categories of functional support may be required relative to any of the initiatives and strategic objectives defined in Section 3 of this SOW:

• Engineering and Technical Services;

• Test and Evaluation;

• Integration and Implementation;

• Operations / In-service Management;

• Software, Tools, and Technology Support;

• Business Intelligence and Data Analytics Support;

• Strategic and Operational Planning;

• Acquisition Planning and Procurement Support; and

• Program and Project Management.

Section 4 of this SOW identifies the high-level support requirements associated with each of these functional areas. Specific requirements within the scope of these functional work areas will be identified, defined, and issued under individually funded task orders.

The SOW functional areas represent a diverse set of work activities, which require a broad range of labor categories and skill levels within each labor category. Contractor personnel must apply broad experience and technical knowledge of assigned disciplines and specialties for each functional area.

The Contractor must furnish the necessary personnel, materials, equipment, and facilities required to satisfy the requirements of the individual task orders.

Organizational Scope The following three AJW directorates are anticipated to be the primary users of services provided under AISS:

• Operations Support, AJW-1 – responsible for providing the support structure, methodology, tools, procedures, performance monitoring and assurance necessary for the proper operation and maintenance of the NAS;

• ATC Facilities / Engineering Support, AJW-2 – responsible for the safe and effective lifecycle management of the facilities infrastructure of the NAS; and

• NAS Security and Enterprise Operations (NASEO), AJW-B – responsible for providing operational and cybersecurity management of NAS services.

Other FAA organizations may obtain support through the AISS when necessary to support their collaboration with AJW on specific initiatives or strategic objectives.

Definition of Terms and Limitations on Scope Unless otherwise indicated, the term “prime contractor” is used in this SOW to refer to the contractors engaged by the Government to provide NAS systems and services. The AISS Contractor(s) will be required to interact with FAA prime contractors at the direction of the COR, subject to the limitations described in the next section.

1.3 Inherently Governmental Functions

In its performance of this contract, the Contractor must not perform any inherently governmental functions, as identified in Acquisition Management System (AMS) Guidance T3.8.2(3)(a). Inherently governmental functions are so intimately related to the public interest as to require performance by Federal Government employees. The term includes functions that require either the exercise of discretion in applying Federal Government authority or the making of value judgments in making decisions for the Government. This would include, among other things, binding the Government to take or not to take some action by contract, policy, regulation, authorization, order, or otherwise, and exerting ultimate control over the acquisition, use, or disposition of the property of the United States, including the collection, control, or disbursement of appropriations and other Federal funds.

2 References The Contractor must adhere to all applicable FAA Orders. The Contractor must research and employ appropriate FAA Orders, where necessary, under the guidance of the Contracting Officer’s Representative (COR) regarding existing materials and specifications for Government systems.

The Contractor must ensure all work is in full compliance with:

• FAA orders, standards and guidelines

• ATO orders, standards and guidelines

The specific standards and orders applicable to particular work efforts will be identified in each TO

SOW.

Websites where additional supporting information is available are listed below:

• Orders and Notices:

http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parentTo picID/184

• Forms:

http://www.faa.gov/library/forms/

• Acronyms and Abbreviations:

https://www.faa.gov/jobs/abbreviations/

• Contractor & Industrial Security Program:

http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/ documentid/15573

3 Programmatic Support Requirements This section identifies the range of programmatic support that must be provided by the Contractor when identified within a task order issued under this contract. Task orders may encompass one or more of the programmatic areas defined within this section. In addition, the task orders will identify the specific types of functional support required in each programmatic area.

3.1 Transformation of the FAA’s Telecommunications Enterprise

This section identifies requirements pertaining to the transformation of the FAA’s telecommunications enterprise with respect to: (1) the migration from Time Division Multiplexing (TDM) technologies to Internet Protocol (IP)/Ethernet technologies; and (2) the migration from the FAA Telecommunications Infrastructure (FTI) network to FAA Enterprise Network Services (FENS). The Contractor must support this initiative including, but not limited to:

• Assist with the planning and execution of the implementation of FENS and the transition of legacy services to the FENS network infrastructure in accordance with the program’s schedule baseline while minimizing impacts to FAA operations and maximizing efficient use of available field resources;

http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parentTopicID/184 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parentTopicID/184 http://www.faa.gov/library/forms/ http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentid/15573 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentid/15573

• Assist with the planning and execution of the FAA’s migration from TDM- to IP/Ethernet-based technologies in a manner that minimizes disruptions to NAS operations;

• Achieve and sustain interoperability between FENS and its legacy network environments so that user traffic can flow bi-directionally between sites not yet transitioned to FENS and sites that have been transitioned to FENS;

• Develop, implement, and execute new operational management procedures to support the dual operation of FENS and the FAA’s legacy network environments;

• Implement and operate the FAA’s new security operations environment model within FENS;

• Engage stakeholders in the transformation of the FAA’s telecommunications enterprise to minimize impacts to their respective organizations;

• Proactively identify and mitigate technical and operational risks to minimize potential impacts to NAS safety, reliability, and efficiency; and

• Support the FAA in responding to external inquiries resulting from increased political and oversight interest (Congressional, GAO/IG, Inter-agency, etc.).

3.2 Zero Trust Architecture (ZTA) Security

This section identifies requirements pertaining to the FAA’s migration to and operation of a Zero Trust Architecture (ZTA) security model for NAS systems and networks. The Contractor must support this initiative including, but not limited to:

• Migrate the NAS from static, network-based information security perimeters to a ZTA security model for the segmentation, authentication, and monitoring of NAS systems, assets, resources, and users;

• Achieve an effective level of coordination and collaboration between NAS systems and users to facilitate the implementation and operation of a ZTA security model to protect NAS operations from external threats and cyberattacks that could propagate between interconnected NAS systems;

• Establish and implement system-specific and enterprise-wide Concepts of Operation based on a ZTA security model;

• Integrate, test, deploy, and operate functions for patch management, log management, enterprise enhanced monitoring, asset inventory, and NAS-wide authentication/authorization within a ZTA security model; and

• Establish and operate monitoring and control capabilities based on the ZTA security model inclusive of the personnel, tools, and training required for 24 x 7 x 365 operations.

3.3 Evolution of Air Traffic Control (ATC) Voice Communications

This section identifies requirements pertaining to the evolution of Air Traffic Control (ATC) Voice Communications capabilities within the NAS operating environment. The Contractor must support this initiative including, but not limited to:

• Migrate ATC voice connections to pilots and between controllers from dedicated, point-to-point, static connections to a dynamic and flexible NAS-wide enterprise capability;

• Evolve ATC voice communications through the effective integration of the telecommunications enterprise with air/ground radios and ATC voice systems that provide the interface to air traffic controllers;

• Support concurrent operation and ATC voice communications between legacy networks and voice systems and modernized networks and voice systems;

• Develop and implement a new CONOPs to ensure the effective operational management, monitoring, and control of the FAA’s modernized ATC Voice Enterprise; and

• Develop and implement a comprehensive, enterprise-wide security management CONOPS for the configuration ATC Voice Enterprise, including updates as it evolves over time.

3.4 Evolution and Operation of Air Traffic Control Information Display Systems

This section identifies requirements pertaining to the evolution of Air Traffic Information Display capabilities within the NAS operating environment. The Contractor must support this initiative including, but not limited to:

• Assist with planning and execution of the implementation of Enterprise Information Display capabilities and the transition of legacy systems to the enterprise system in accordance with the program's schedule baseline while minimizing impacts to FAA operations and maximizing efficient use of available field resources.

3.5 Resiliency of Time and Frequency Sources

This section identifies requirements supporting the FAA in enhancing the resiliency of Time and Frequency information sources used by NAS systems and networks. The Contractor must assist the FAA with compliance with Executive Order 13905, Strengthening National Resilience Through Responsible Use of Positioning, Navigation, and Timing Services. In addition, the Contractor must assist the FAA with ensuring that NAS systems and networks: (1) comply with FAA Order 1770.68, Selection and Use of Time and Frequency Sources for all Systems, Services, and Applications Supporting NAS Operations; and (2) align with the resilience and reliability constructs described in the Department of Homeland Security’s (DHS’s) Best Practices, Improving the Operation and Development of Global Positioning System (GPS) Equipment Used by Critical Infrastructure; and the Cybersecurity and Infrastructure Security Agency (CISA) publication, Time Guidance for Network Operators, Chief Information Officers, and Chief Information Security Officers. The Contractor must support this initiative including, but not limited to:

• Identify and evaluate alternatives to Global Navigation Satellite System (GNSS) receivers as the primary source of precision time and frequency;

• Support the acquisition of non-GNSS sources of precision time and frequency; and

• Assist with the planning and implementation of non-GNSS sources as the primary sources of precision time and frequency for NAS systems.

3.6 Integration and Operation of Wireless Communications Technologies

This section identifies requirements supporting the integration and operation of commercially-available wireless technologies and services including 4th generation LTE (Long-Term Evolution) cellular, 5th Generation (5G) cellular, and Low-Earth orbit (LEO) and Medium Earth Order (MEO) satellites. This initiative also includes Spectrum Engineering and Spectrum Certification associated with changes in the allocation and use of aviation radio spectrum driven by the emergence of new technologies such as Unmanned Aerial Systems (UAS), Counter-UAS (C-UAS), novel military radio spectrum capabilities, and experimental radio systems. The Contractor must support this initiative including, but not limited to:

• Assess the telecommunications service performance requirements of existing and planned NAS systems to identify viable candidates for using 5G and other commercial wireless services as primary and/or diverse telecommunications media;

• Assess the cost and performance of 5G and other commercial wireless services with respect to the requirement of candidate NAS systems;

• Assess the operational compatibility of integrating 5G and other commercial wireless services into the NAS operating environment;

• Assess the impact of dynamic radio spectrum sharing technologies and techniques on incumbent radio frequency users;

• Develop and/or assess alternative strategies for protecting aviation radio spectrum through Radio Frequency Interference (RFI) resolution methods and other techniques; and

• Assist with the planning and implementation of 5G and other commercial wireless services within the NAS operating environment.

3.7 Integrated Security Architecture and Operations

This section identifies requirements pertaining to the FAA’s evolution to and operation of an Integrated Security Architecture for NAS systems and networks. The FAA’s objective of establishing an Integrated Security Architecture is to ensure consistent control and management of security capabilities across the NAS, particularly when individual systems are dependent on a disparate set of security solutions. The Contractor must support this initiative including, but not limited to:

• Establish standardized Security Policy management processes;

• Develop and support the execution of effective security risk management practices;

• Assess trade-offs between information, physical, and environment security to identify security solutions conducive to the establishment of an Integrated Security Architecture;

• Define a comprehensive approach to managing and monitoring security policy compliance;

• Ensure efficient information system authorization and account management for NAS systems;

• Apply an enterprise-level approach to security incident management;

• Support the FAA in the identification and implementation of an Integrated Security Architecture that enhances operational resiliency and business continuity;

• Define conceptual architecture for governance, policy and domain architecture, certificate management, access control, incident response architecture, application security, web services, and communications networking;

• Map the conceptual architecture to the physical architecture for hardware/platform security, network security, operating system security, file security, and database security;

• Identify and tailor the required security controls;

• Optimize application of Procedural controls, Operational controls, Access controls, Application controls, Endpoint controls, and Infrastructure controls;

• Document approaches and guides for implementation of security controls, system administration, configuration/patch management, monitoring, logging, penetration testing, access management, change management, and forensics; and

• Develop IT disaster recovery plans to minimize impacts to NAS operations.

3.8 Evolution and Operation of Enterprise Infrastructure, Messaging, and Security Systems

This section identifies requirements pertaining to the evolution and maintenance of enterprise systems within the NAS operational and support environments. These systems include infrastructure systems which provide hardware and software services to other systems and services, messaging systems which support the transmission and exchange of Air Traffic Services (ATS) messaging between NAS systems and other FAA and non-FAA users, and security systems which provide enterprise level authentication and authorization services to NAS systems and external users. The Contractor must support this initiative including, but not limited to:

• Assist with the analysis of new NextGen, Program Management Organization (PMO), or ATO Cybersecurity Group (ACG) program requirements and identify potential impacts to existing system baselines;

• Provide engineering, development, documentation, and test support to deploy hardware and software modifications to operational systems in accordance with applicable FAA configuration management policies and orders;

• Integrate and install hardware and COTS software and services required to provide microservices support as a platform service to systems and users;

• Integrate and install hardware and COTS software and services required to implement Development, Security, and Operations (DevSecOps) capabilities for the automation of system deployment between development, system test, and operational environments;

• Engage system stakeholders with regard to requirements analysis, enhancement requests, troubleshooting system issues, and restoration of system services; and

• Support technical and informational meetings with internal and external stakeholders including but not limited to NextGen, PMO, ACG, foreign Air Navigation Service Providers (ANSPs), and other aviation and commercial organizations.

3.9 NAS Infrastructure and System Modernization

This section identifies requirements pertaining to the modernization of existing NAS infrastructure and systems. The Contractor must support NAS modernization initiatives including, but not limited to:

• Capitalize on opportunities within NAS modernization programs to improve NAS safety, reliability, and efficiency;

• Develop strategies to establish requirements for new systems that align with the new maintenance philosophy;

• Incorporate new technologies to manage risk through use of data and algorithms to assist in mitigating disruptions to NAS services;

• Support development of a corporate strategy on NAS infrastructure maintainability;

• Improve logistics support and ensure infrastructure sustainability;

• Ensure NAS program requirements align with the NAS enterprise-level maintenance philosophy and strategy;

• Complete the planning and execution of programs to modernize NAS infrastructure and systems in accordance with the baseline schedule while minimizing impacts to FAA operations and maximizing efficient use of available field resources;

• Address the planning, scheduling, resource management, and overall operational risk management required to manage and operate modernized NAS systems and infrastructure;

• Develop comprehensive strategies to support the development of the workforce, plans, training, and other elements required to effectively manage the operation of modernized NAS systems and infrastructure; and

• Incorporate modernized NAS systems and infrastructure into the ZTA model.

3.10 Supply Chain Management and Supply Chain Risk Management

This section identifies requirements pertaining to Supply Chain Management and Supply Chain Risk Management. The Contractor must support FAA Supply Chain Management and Supply Chain Risk Management initiatives with the objective of ensuring compliance with associated Executive Orders, Office of Management and Budget (OMB) guidance and mandates, AMS policies, and FAA orders.

The Contractor must support the following aspects of FAA Supply Chain Management and Supply Chain Risk Management initiatives at a minimum:

• Support Supply Chain Management planning to ensure that all services, equipment, components, and other supplies required for the maintenance and operation of the NAS are available as needed;

• Monitor and track changes to the Information and Communications Technology (ICT) industrial base to ensure the integrity of the NAS supply chain;

• Identify, assess, and provide recommended Supply Chain risk management and mitigating controls to manage risks to the ICT supply chain;

• Address and manage evolving threats and disruptions to the supply chain for components use to provide NAS systems and services; and

• Identify alternative sources for components use to provide NAS systems and services.

3.11 Maintenance Optimization

This section identifies requirements pertaining to Maintenance Optimization and encompasses NAS infrastructure and systems that are currently in operation as well as those that are planned for deployment. The Contractor must support Maintenance Optimization initiatives including, but not limited to:

• Expand current Preventive and Reactive maintenance activities to include Condition–Based, Predictive, and Prescriptive maintenance;

• Implement Service Management Models and Reliability Centered Maintenance (as part of Predictive Maintenance);

• Leverage technology and data science to enhance the NAS maintenance program through the integration of system data and development of algorithms;

• Identify historical failure patterns;

• Implement the processes and systems to support machine learning capabilities to rapidly process large amounts of data to provide accurate system predictions and status;

• Compile and analyze data to support lifecycle decisions on infrastructure management based on observed conditions;

• Develop and implement algorithms based on key variables internal and external to Technical Operations;

• Evolve maintenance services to meet demands as technology changes, stakeholder engagement increases, and requirements exceed resources;

• Develop new strategies to meet this ever-changing environment with service/enterprise management, leveraging new technologies, and transforming data into useful information to reduce loss of NAS services;

• Optimize Technical Operations maintenance through use of new and existing technology, enterprise service management, and development of new integrated data management tools;

• Reinforce distinction between service and enterprise services at the control centers;

• Establish collaborative maintenance strategies considering service impacts versus equipment impacts;

• Leverage technology to provide more timely support to the technical workforce; and

• Retrofit existing and design new facilities with increased sensor capabilities.

3.12 Integration of Unmanned Aircraft Systems (UAS) and Other Emerging Technologies and Capabilities into the NAS

This section identifies requirements pertaining to the integration of Unmanned Aircraft Systems (UAS) and other emerging technologies and capabilities into the NAS. The FAA’s objective for this initiative is to promote access of UAS and other New Entrants into the NAS through policy and automation. In the context of the requirements within this section, a “New Entrant” is defined as a new user of the NAS that requires Air Traffic Control services and/or potentially impacts Air Traffic Control operations and a “non-FAA technology” is defined as a system or service that the FAA does not intend to procure, but has the responsibility to approve and oversee if it will be operated by non-federal sponsors. Contractor work efforts supporting this initiative must adhere to the FAA’s integration roadmap with the objective of establishing a safe and secure environment for all New Entrants, including manned and unmanned airborne vehicles. The Contractor must support these initiatives including, but not limited to:

• Assess the potential impact New Entrants will have on the NAS and how their operation will integrate into the NAS;

• Assess the potential impact of non-FAA technologies on the NAS and support the development of processes, procedures, and requirements to ensure their efficient and safe integration into the NAS;

• Collaborate with agency partners and applicable standards bodies to support the development of technical requirements for non-FAA systems and services, UAS services, and other New Entrants into the NAS;

• Collaborate with FAA Cybersecurity to define minimum cybersecurity standards for UAS, non-FAA systems/services, and other New Entrants into the NAS;

• Work collaboratively with agency stakeholders to secure the wireless connections used by UAS vehicles as well as the UAS vehicles themselves from malicious actors;

• Safeguard new UAS communications and connections and support the planning and implementation of the additional bandwidth necessary to support them;

• Identify and evaluate opportunities to enhance maintenance, restoration, and emergency response activities through new tools and technology being introduced into the NAS;

• Engage with ATO Security Operations and other agency partners to define requirements for Command and Control (C2) links for UAS and other New Entrants into the NAS;

• Provide technical expertise in managing UAS data set captures and other New Entrants to include secure transmission and visualization using geospatial data products;

• Support the development of a standardized concept of operations for UAS and other New Entrants with National Security Stakeholders;

• Support the development of requirements for Beyond Visual Line of Sight Operations (BVLOS) for UAS and other New Entrants into the NAS;

• Engage with applicants and industry stakeholders to facilitate system/service approvals;

• Provide technical expertise for non-FAA system/service approvals in areas including: safety assurance, software & hardware design assurance, and system/service verifications; and

• Support the development of UAS operational policy and technical requirements for types of missions and types and minimum requirements of photogrammetry.

4 Functional Support Requirements This section identifies the range of support that must be provided by the Contractor when identified within a task order issued under this contract. Task orders may encompass one or more of the functional areas defined within this section. The Contractor must consider and address enterprise needs and goals of AJW and stakeholder organizations; integration across NAS programs and systems; and the magnitude, diversity, complexity, and scale of the operational and programmatic challenges of affected NAS systems. Additional requirements and details, including but not limited to written deliverables and/or place and period of performance, will be specified in individual task orders, as applicable. The Contractor must provide the full range of support capabilities defined in the task orders issued under this contract. The Contractor must provide program management, technical analysis and planning, administrative, and managerial expertise to perform the work described below.

In the performance of task orders issued under this contract, Contractor personnel may be required to possess in-depth knowledge of the FAA operating environment including, but not necessarily limited to: Air Traffic Control (ATC) operations, AJW, NAS systems and subsystems, and FAA/ATO orders, policies, and standard operating procedures. In providing the required functional support described in the following subsections, the Contractor also must provide written and graphical work products as requested by the FAA TO Lead to convey the outputs of the work efforts, including but not limited to: reports, technical documentation, briefings, presentations, issue papers, graphics, and reports.

4.1 Engineering and Technical Services

This section identifies the required engineering and technical services to be provided under this contract. In providing the required Engineering and Technical Services, the Contractor must consider and address:

• enterprise needs and goals of AJW and stakeholder organizations;

• integration across NAS programs and systems;

• the magnitude, diversity, complexity, and scale of the operational and programmatic challenges of affected NAS systems; and

• cybersecurity implications across all system functions relative to their NAS-wide operational implementation.

Engineering Support

The Contractor must provide engineering and other technical support to assist AJW with systems, products, and services that are: (1) implemented in simulated environments, (2) currently in operation within the NAS, or (3) are planned for implementation in the NAS. As specified in individual task orders, the Contractor may provide a range of technical engineering expertise and assistance associated with the implementation, integration, and transition of NAS systems, products, and services. A variety of engineering disciplines may be required to include civil, electrical, electronics, environmental, mechanical, systems, telecommunications, and others.

The Contractor must support activities associated with planning, managing, supporting, executing, and maintaining system engineering processes, programs, and work. The Contractor must support all aspects of engineering task activities involving concept definition, requirements development, design and development, testing, installation, implementation, integration and transition of systems, services, components, and equipment, as required by the FAA.

The Contractor must support Capital Improvement Program (CIP) projects, Corporate Work Plan (CWP) projects, and AJW’s sustainment of NAS facilities. As part of these efforts, the Contractor must analyze NAS Facility evaluations and site surveys and provide recommendations based on the needs identified by the facility. The Contractor must utilize the CWP project management system to track project flow, including project initiation, validation, planning, design, construction, installation, and commissioning. The Contractor must track projects and support ongoing project work to include Baseline Scope, the CWP’s 3D Work Plan process, and Joint Acceptance Inspections (JAIs). The Contractor must coordinate with FAA Service Areas and on-site personnel to obtain facility access, schedule meetings, visit requests, badge activation, and conference room scheduling.

Cybersecurity Engineering

The Contractor must provide cybersecurity engineering support to assist AJW with systems, products, and services that are planned for implementation in the NAS or are currently in operation within the NAS. In providing the required Engineering and Technical Services, the Contractor must consider and address:

• Cybersecurity implications across all functions including the application of Cybersecurity within NAS systems and services relative to their NAS-wide operational implementation; and

• the changing cyber threat environment, the FAA’s migration to IP infrastructure, and integration of Cloud services.

The Contractor must provide system development lifecycle support for NAS enterprise-level Cybersecurity services and solutions including the development, management, and operation of Cybersecurity tools. The Contractor must support all aspects of the Cybersecurity Engineering including the design, development, testing, installation, and operations of security solutions to prevent NAS and other FAA systems from unauthorized access and cyberattacks. In addition, the Contractor must support the development of Cybersecurity standards and policies, integration of NAS systems into the enterprise architecture at the strategic and tactical levels, security authorization activities including internal FAA security authorizations and Government-wide authorizations such as FedRAMP, and the conduct of cybersecurity exercises.

Spectrum Engineering

The Contractor must provide spectrum engineering and analysis support for NAS programs, systems, and services involving the radiation or reception of radio frequency signals. The Contractor must process and review frequency assignment requests; prepare and conduct radio frequency interference investigations and analyses; review, assess, and provide comments on technical documentation pertaining to spectrum usage in ATC/aviation environments; and apply Spectrum Engineering principles in the performance of work efforts in this functional area.

4.2 Test and Evaluation Support

The Contractor must support test and evaluation activities conducted by the Government and prime contractors for systems, products, and services that are planned for implementation in the NAS or are currently in operation within the NAS. In providing the required Test and Evaluation Support, the Contractor must consider and address:

• the needs of AJW and stakeholder organizations;

• integration and interoperability with other NAS systems;

• potential synergies in testing activities involving multiple NAS systems; and

• Enterprise-level strategies for resolving Problem Tracking Reports (PTRs).

Support may be required throughout the life cycle including test activities related to prototyping;

development laboratory testing; factory acceptance testing; COTS/NDI Testing; Development Testing (DT), including hardware and software testing; Regression Testing; Operational Test and Evaluation (OT&E); Key Site Testing; Site Acceptance Testing; Service Acceptance Testing;

Information System Security Penetration Testing; Aircraft Cyber Vulnerability and Penetration Testing; and Operational Site Assessment Testing.

4.3 Integration and Implementation Support

The Contractor must support integration and implementation activities conducted by the Government and prime contractors for systems, products, and services being deployed within the NAS as well as the implementation of modifications/upgrades to systems, products, and services that are currently in operation within the NAS. In providing the required Integration and Implementation Support, the Contractor must consider and address:

• Resource availability and impacts to AJW and stakeholder organizations;

• Impacts to other NAS systems already in operation; and

• Potential synergies in the implementation planning associated with dependent and/or collocated systems.

The scope of required support may include the integration of both FAA systems and “non-FAA technologies” into the NAS. A “non-FAA technology” is defined as a system or service that the FAA does not intend to procure, but the FAA has the responsibility to approve and oversee if it will be operated by non-federal sponsors. The Contractor must provide integration support including, but not limited to:

• Assess the potential impact of introducing new technologies into the NAS and define requirements to ensure they can be integrated into the NAS;

• Collaborate with agency partners and applicable standards bodies to support the development of technical requirements for new technologies, systems, and services;

• Collaborate with FAA Cybersecurity to define minimum cybersecurity standards for new technologies, systems, and services;

• Create and maintain project schedules for the approval process for new technologies, systems, and services

• Provide technical expertise for new technology, system, and service approvals in areas including: safety assurance, hardware and software design assurance, and system/service verifications; and

• Support the preparation of updated approval and oversight policies for non-FAA systems/services.

The Contractor must support all aspects of implementation activities involving site implementation, system installation, service transition, and checkout and integration, removal of existing equipment and disposal/disposition, facility modernization, briefing diverse air traffic communities and equipment manufacturers, airport personnel, various FAA originations, labor organizations, and other government agencies foreign and domestic.

The Contractor may also be called upon to support various FAA organizations involving services such as reviewing issues relating to various engineering disciplines for technical content and procedural adherence; coordinating issues with the submitter, presenting issues to various FAA organizations and the coordination and tracking of plan of action and resolution process; status and database management support and providing assistance in the tracking, resolution, and elevation of various implementation and integration issues as necessary.

4.4 Operations and In-Service Management Support

The Contractor must provide operations and in-service management support to enhance the safety and efficiency of the NAS. In providing this support, the Contractor must: (1) facilitate coordination between AJW In-service Managers and their stakeholders, such as the Program Management Organization (AJM); and (2) maintain awareness of where programs reside in the AMS lifecycle and which duties identified in the In-Service Management Standard Operating Procedure should be performed during the respective AMS lifecycle phase.

In providing the required Operations and In-Service Management Support, the Contractor must consider and address the integration of in-service management capabilities across AJW directorates, NAS programs/systems, and all of its AISS TOs. In addition, the Contractor must support the development and implementation of enterprise solutions that provide a situational awareness perspective that spans multiple systems and programs to include logistics and maintenance support, acquisition planning and procurement support, network operations support, training support, system safety and operational risk management, helpdesk operations, workstation support, and service desks.

Logistics and Maintenance Support

The Contractor must provide logistics and maintenance support for systems, products, and services that are planned for implementation in the NAS or are currently in operation within the NAS. The Contractor must support all aspects of integrated logistic activities. The contractor must support the planning, establishment, implementation, and integration of maintenance concepts for the lifecycles of FAA systems, products, and services as designated by the Government.

The Contractor must provide logistics and lifecycle management support and expertise to planned acquisitions and throughout the procurement and operations support (OS) lifecycle to include providing inputs to support the preparation of documentation and briefings required to obtain program/project approval, including those items associated with FAA Acquisition Management System and milestones.

Network Operations

The Contractor must provide network operations support to FAA communications networks, inclusive of leased operational and administrative telecommunications services as well as FAA-owned and operated networks for new and legacy systems and services. In performing the required work efforts in this functional area, the Contractor must apply its telecommunications experience, which includes voice, and data communications standards as well as a technical understanding of Internet Protocol (IP) network performance, routing protocols, routing configuration, and IP network management.

The Contractor must perform troubleshooting and analysis of telecommunications systems and components. The Contractor must support service restoration activities to mitigate impacts to NAS operations. The Contractor must perform analyses of system and service operations (e.g., trends, tools, planned investments) and provide recommendations for improvements to enhance network efficiencies, reliability, availability, and responsiveness. The Contractor must support service provider Maintenance Request (MR) coordination activities to include collaboration with customer, control center(s), and service provider as necessary.

Training Support

The Contractor must provide training support for systems, products, and services that are planned for implementation in the NAS or are currently in operation within the NAS. The Contractor must support all facets training requirements analysis; development and maintenance of training aids; and training delivery.

For Contractor-conducted training, the Contractor must provide classroom training, hands-on training, and distance learning (i.e., remote/virtual) training, as required. The Contractor must provide all training materials and training instructors who are subject matter experts. Training will not commence without approval by the FAA of all submitted materials. The size of the training classes, location of the training classes, and the number of training classes to be held will be identified in each task order. The FAA reserves the right to record the training provided to satisfy its future training requirements. The training program and materials, in hard and soft copy, must become the property of the FAA, with reproduction rights, for future training requirements of the FAA.

Cybersecurity Operations

The Contractor must assist NAS Cyber Operations (NCO) in its mission to minimize the impact of cyber security events and incidents in support of availability and restoration requirements for NAS critical and essential services. Due to the critical nature of these activities, the Contractor may be required to provide support on up to a 24x7x365 basis. Specific hours of operation/performance will be identified in the Task Order SOWs.

The Contractor may be required to travel to NCO facilities to obtain training on and familiarization with NCO processes and functions. NCO facilities include the FAA Command Center in Warrenton, VA, the WJHTC in Atlantic City, NJ, and Security Operations Control Centers operated by leased service providers.

System Safety and Operational Risk Management

The Contractor must support Safety Management System activities for systems, products, and services that are planned for implementation in the NAS or are currently in operation within the NAS. The Contractor must support the implementation of system safety measures to mitigate hazards or reduce risk to an acceptable level.

The Contractor must support Operational Risk Management activities for systems, products, and services that are planned for implementation in the NAS or are currently in operation within the

NAS.

Helpdesks, Workstation Support, and Service Desks

This section identifies requirements for helpdesks, workstation support, and service desk support. For each instance of helpdesk, workstation support, and service desk support that the Contractor is required to support, the Government-issued task order will identify:

• Required programmatic, system, and subject matter expertise;

• Responsiveness/performance requirements;

• Required user/customer contact methods that must be supported (e.g., telephone, e-mail, web portal, etc.);

• Required days and hours of operation;

• Required user/customer contact volume level that must be supported; and

• Reporting requirements on user/customer contact volume level and responsiveness/performance.

The following subsections identify additional requirements specific to each support function.

4.4.6.1 Helpdesk Support

The Contractor must operate helpdesk functions for systems, products, and services that are currently in operation within the NAS. Helpdesk support is focused on providing information to users and answering questions. The Contractor must staff each helpdesk function (up to 24x7x365 coverage as required) with personnel who are appropriately trained and possess the subject matter expertise needed to provide the required support.

4.4.6.2 Workstation Support

The Contractor must install, configure, and maintain computer/system workstations. For each set of workstations the Contractor is required to support, the Government-issued task order will identify:

• The types of workstations;

• Any software applications running on the workstations that must be supported by the Contractor;

• The number of workstations and their locations;

• The days of the week and the hours of day for which support is required; and

• Reporting requirements associated with the support provided, e.g.,…