AISS Draft Statement of Work (SOW)-10-21-2021.pdf

Federal Aviation Administration

AJW Integrated Support Services

Statement of Work

(SOW)

DRAFT

October 21, 2021

AJW Integrated Support Services (AISS) Statement of Work i

Table of Contents

1 Introduction

1.1 Background

1.2 Objectives

1.3 Scope of Work

1.4 Inherently Governmental Functions

2 References

3 Support Requirements

3.1 Engineering and Technical Services

3.2 Test and Evaluation Support

3.3 Integration and Implementation Support

3.4 Operations and In-Service Management Support

3.5 Software and Computer Systems-related Support

3.6 Strategic and Operational Planning, Governance, and Policy Support

3.7 Acquisition Planning and Procurement Support

3.8 Program and Project Management Support

3.9 Contract Program Management

4 End Results/Deliverables

5 Place of Performance

6 Hours of Operation

7 Security Clearances, Certifications, and Accreditations

8 Government Portals and Information Management Tools

9 Travel and Other Direct Costs (ODCs)

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

C-1

1 Introduction This Statement of Work (SOW) describes the Federal Aviation Administration’s (FAA’s) requirements for the AJW Integrated Support Services (AISS) contract. This contract will provide the 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 assist AJW with systems, products, and services that are currently in operation within the National Airspace System (NAS), implemented in simulated environments, or are planned for implementation in the NAS. Each Task Order (TO) will have an associated statement of work (SOW) and identify project-specific requirements such as programs to be supported, the place of performance, deliverables, and other pertinent information. While each TO will address specific functional areas within this SOW, the emphasis will be placed on integration across AJW directorates, NAS programs/systems, and the functional areas identified in this 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 for new and legacy services.

1.2 Objectives

The primary objective of the AISS contract is to obtain specialized technical and management services to support the fulfillment of AJW’s mission in an integrated manner that addresses enterprise-level trade-offs in alignment with AJW’s organizational objectives. With the AISS contract, AJW is seeking to integrate the support provided across multiple directorates to improve efficiency, communications, and collaboration – both across the contractor support staff and relative to their interaction with AJW. AISS is intended to provide a contract that:

• Is focused on AJW’s mission;

• Facilitates a uniform contracting approach to support AJW and the programs, systems, and services that it manages;

• Fosters cross-organizational collaboration and unified situational awareness; and

AJW Integrated Support Services Statement of Work

A-2

• Meets the changing needs of AJW across the period of performance as the NAS operating environment evolves.

1.3 Scope of Work

This SOW is comprised of functional work areas that establish the scope of the contract. Specific requirements within the scope of these functional work areas will be identified, defined, and issued under individually funded task orders. As ordered by the Government, the Contractor must provide support in the following functional areas:

• Engineering and Technical Services;

• Test and Evaluation;

• Integration and Implementation;

• Operations / In-service Management;

• Software and Computer Systems-related Support;

• Strategic and Operational Planning;

• Acquisition Planning and Procurement Support; and

• Program and Project Management.

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.

The scope of task orders issued under the AISS contract may include any program, system, or service managed by AJW. In particular, the following three AJW directorates are anticipated to be the primary users of services provided under the AISS contract:

• 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.

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

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 will be required to interact with FAA prime contractors subject to the limitations described in the next paragraph.

A-3

1.4 Inherently Governmental Functions

In its performance of the AISS contract, the Contractor must not perform any inherently governmental functions, as identified in the Office of Federal Procurement Policy Letter 11-01.

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. Other business and financial systems must be used.

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

• FAA orders, standards and guidelines

• ATO orders, standards and guidelines

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 Support Requirements This section identifies the range of support that must be provided by the Contractor when identified within a task order issued under the AISS 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 of across NAS programs and systems; and the magnitude, diversity, complexity, and scale of the operational and programmatic 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

A-4 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. 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 the AISS 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.

3.1 Engineering and Technical Services

This section identifies the required engineering and technical services to be provided under the AISS 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.

A-5

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.

3.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;

A-6

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

3.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 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.

3.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 ISM SOP 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 AISS CLIN order and task orders. 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.

A-7

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.

A-8

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 subparagraphs identify additional requirements specific to each support function.

3.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.

A-9

3.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., number of trouble tickets opened and closed, maintenance actions performed, etc.

3.4.6.3 Service Desks

The Contractor must implement and operate Service Desk functions for Government-designated systems and environments. Service Desk support is focused on resolving problems and issues reported by customers and responding to user requests for technical assistance. The specific performance requirements including the hours of operation (e.g., 24x7x365) and whether on-site support is required will be specified in the associated task orders.

3.5 Software and Computer Systems-related Support

The Contractor must design, develop, implement, and maintain computer systems and software-based tools supporting information management, operations support, situational awareness, business process automations, and other applications.

In providing the required Software and Computer Systems-related Support, the Contractor must consider and address:

• enterprise needs and goals of AJW and stakeholder organizations;

• integration of across NAS programs and systems;

• enterprise-level situational awareness;

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

• integration of Cloud-based resources.

Contractor personnel must possess and maintain proficiency with the following applications/programming languages/operating systems: MS Windows, Linux/UNIX, MS Office, Assembly, C, FORTRAN and Very High Speed Integrated Circuit Hardware Description Language (VHSIC-HDL (VHDL)), Google Application Programing Interface (APIs), ESRI APIs, .NET, Java, C#, MS Silverlight, JavaScript, and Oracle 11g.

A-10

Software Engineering

The Contractor must provide Software Engineering support for software development activities and enhancements. The Contractor must provide Software Engineering support across the full Software Development Life Cycle (SDLC) including, but not limited to:

• Requirements identification, development, and documentation;

• Design;

• Software development;

• Testing;

• Implementation;

• Configuration management; and

• Operational support.

The Contractor must perform evaluations and assessments of other contractor and vendor software plans and products, including evaluation of commercial off-the-shelf (COTS)/non-COTS integration, quality, thoroughness, responsiveness to FAA requirements, validity, feasibility, progress, trouble-report activities and trends, and cost and trend analyses.

Computer Systems Planning, Design, and Engineering

The Contractor must plan and design computer systems that integrate computer hardware, software, and communication technologies. The Contractor must provide Computer Systems Planning, Design, and Engineering support for studies and requirements definition, analysis, development and validation; concept exploration, analysis, and evaluation; design traceability; alternative hardware and software design capabilities; external interface assessments; product deployment, integration, and support including support of product implementation engineering specialties such as site implementation, system installation and checkout, operational field data analyses, removal of existing equipment, and facility modernization.

Software Design and Development

The Contractor must provide software design and software development (including computer programming) support for AJW-managed/operated systems. The scope of required support includes, but is not limited to: software development, evaluations, modifications, testing, test and validation, and field, implementation, and other technical support.

The Contractor must develop new software and modify existing software as necessary to meet the specified requirements for software applications, tools, user portals, and interfaces with other systems. All software must be developed in accordance with the product baseline provided by the FAA. The Government will retain the data rights for all software and software documentation developed under the AISS contract.

3.5.3.1 Application Development

The Contractor must develop software solutions to support AJW organizational responsibilities including, but not limited to: data analysis, process automation, situational awareness, and operational support.

A-11

3.5.3.2 KSN Site and Webpage Development and Operational Support The Contractor must provide development and operational support for Government-hosted Knowledge Services Network (KSN) sites and websites.

Software Integration, Test, and Implementation Support

The Contractor must provide software integration, test, and implementation support for systems and automated tools managed and/or operated by AJW. The required scope of support includes all phases of testing including, but not limited to: Unit Testing, Integration Testing, System Testing, Acceptance Testing, Independent Operational Test and Evaluation, and Regression Testing.

System Administration and Database Management Support

The Contractor must provide system administration and database management support for Government-designated IT systems to ensure they provide the required availability, functionality, and performance. The Contractor must perform all necessary design, analysis, development, and support to upgrade databases and operating systems to a more current software release, perform technology refreshes, and database improvements or migrations.

IT System and Software Lifecycle Support

The Contractor must perform technical, management, and administrative services to support and assist the FAA’s software development process. Software development will generally occur through the development of new web-based applications or through the modification of existing web-based applications.

3.5.6.1 System and Software Maintenance and Configuration Management The Contractor must establish, manage, and maintain the current hardware and software inventory including the administration and dispensing of appropriate licenses for, but not limited to, operating systems, third party tools, development, and test software for configuration management, testing, and software development.

3.5.6.2 Technical Support

The Contractor must provide technical support for the systems that it develops to include, but not limited to, technical advice and engineering support across IT systems. The Contractor must control, manage, and trouble-shoot IT systems, and conduct logical operating system fault monitoring. The Contractor must manage formulation of equipment security requirements, coordination of physical security, verification of access control, and documentation of audit trails. The Contractor must backup/restore the IT systems and perform reconfiguration, diagnostics/remedial action, and ensure end-to-end physical connectivity.

3.6 Strategic and Operational Planning, Governance, and Policy Support

This paragraph identifies requirements for Strategic and Operational Planning, Governance, and Policy Support including the development of System Support Directives.

A-12

Strategic and Operational Planning

The Contractor must provide strategic and operational planning support for NAS programs, systems, and services. The scope of strategic and operational planning support activities may include, but is not limited to: consolidation of major ATC facilities, establishment and incorporation of new facilities, implementation of new and emerging technologies, radio frequency spectrum usage, human resource requirements, and logistics.

In providing the required Strategic and Operational Planning, the Contractor must:

• consider and address the enterprise needs and goals of AJW and stakeholder organizations.

• engage AJW stakeholders across the FAA (e.g., PMO, NextGen, etc.); and

• consider and address the magnitude, diversity, complexity, and scale of the operational and programmatic challenges of affected NAS systems.

In support of the communication of the outcomes of strategic and operational planning activities, the Contractor may be required to:

(1) develop presentation materials for reorganization, empowerment, culture, and various other initiatives, including, but not limited to, the production of videos, newsletters, hotline voice mailboxes, and employee bulletin boards; and

(2) provide logistics support for multimedia, office administration, and telecommunications equipment.

Governance

The Contractor must support NAS governance with a focus on enabling a set of enforceable policies, procedures, processes, tools, and organizational structures that ensure consistent alignment between business objectives and technology goals. Governance provides a representation of concepts, relationships, constraints, rules, and accountability of operations for the enterprise.

Policies and Orders

The Contractor must support the development and establishment of policies and orders that define Technical Operations responsibilities relative to NAS systems, NextGen emerging systems and technologies, enterprise architectures, and roadmaps. The Contractor must assist with the documentation of engineering practices and procedures, review of current documents, and identification and documentation to implement required changes.

System Support Directives

The Contractor must support the development and issuance of System Support Directives (SSDs) Support Role) for AJW-managed/operated systems in accordance with applicable orders.

When developing SSDs, the Contractor must strive to minimize software, hardware, and firmware impacts to the affect systems and the Contractor must identify any proposed changes for approval by the designated FAA officials. The Contractor must provide the associated reliability, maintainability, operational effectiveness, and operator interface documentation to the designated FAA officials.

A-13

3.7 Acquisition Planning and Procurement Support

The Contractor must provide acquisition planning and procurement support across the lifecycle of systems, products, and services for which AJW is responsible for the management and operation. The Contractor must support the FAA's conduct of market surveys, the development of CFO packages including the preparation of Independent Government Cost Estimate (IGCEs) and Business Case Analyses (BCAs), the development of Screening Information Requests (SIRs), and the review and assessment of industry responses to FAA-issued market surveys and requests for information (RFIs).

The Contractor may also be required to participate in the source selection process including the review of management/technical proposals and the preparation of evaluation reports.

3.8 Program and Project Management Support

The Contractor must provide program and project management support to programs, systems, and services planned for implementation in the NAS as well as programs, systems, and services that are currently in operation within the NAS. The Contractor must support all aspects of Program and Project Management to ensure FAA operational policies, processes and program elements are integrated, and documented within the ATO.

In providing the required Program and Project Management Support, the Contractor must consider and address:

• the enterprise needs and goals of AJW and stakeholder organizations; and

• the integration of work efforts across AJW directorates, NAS programs/systems, and AISS

CLIN order and task orders.

The Contractor must also ensure that all work efforts performed under this contract are planned and executed in a manner that contributes to AJW achieving its integrated set of operational and organizational goals.

3.9 Contract Program Management

This section describes work efforts that must be performed by the Contractor as part of the management and administration of the AISS contract.

Contract Management

The Contractor must efficiently and accurately manage this contract to ensure compliance with all technical, business, and management (e.g., cost, schedule, and deliverable) requirements of this SOW. The Contractor must designate a Program Manager and other primary points of contact for work to be performed under this Statement of Work and individual task orders issued under the AISS contract. In support of the management of the AISS contract, the Contractor must perform the following efforts, at a minimum:

• Provide program management support to ensure that identified tasks are performed efficiently, accurately, on time, and in compliance with the requirements;

• Conduct sufficient oversight and supervision of the contract and its employees in order to ensure both are functioning within designated labor categories and performing at acceptable levels;

• Ensure all assignments are completed in a thorough and timely manner;

A-14

• Prepare detailed written documentation of accomplishments as stipulated in the monthly report submission;

• Inform the Contracting Officer (CO) and COR of any potential problems and make recommendations for solutions;

• Participate as a member of a government-led team as required by the CO or COR; and

• Provide sufficient personnel, both in number and qualification, to successfully perform work described herein.

Key Personnel

The Program Manager and [TBD] are defined as “Key Personnel” under the AISS contract. Key Personnel may only be replaced with the approval of the FAA CO, in accordance with AMS clause 3.8.2-22. Proposed Key Personnel must be available to work on the AISS contract and serve in the assigned role for at least six months from their start of performance on the contract.

The following are the required responsibilities of the roles designated as “Key Personnel.”

• Program Manager – The Contractor’s primary focal point for the AISS contract. Has overall responsibility for the execution of the contract including questions regarding any of the task orders and their sub-activities. The Program Manager interfaces with the Government management points-of-contact for the contract.

• Others – TBD

Meeting Attendance

The Contractor must attend and/or participate in meetings at locations identified in Paragraph 6 of this SOW and other locations as may be requested by the Government.

Monthly Status Reports

The Contractor must provide Monthly Status Reports (MSRs). The MSRs must document task order accomplishments and demonstrate value-added activities of the previous month and identify future planned activities. The reports must be delivered to the COR and contain three parts: a narrative of accomplishments, a cost summary, and a personnel listing by Task Order. MSRs must include the following monthly information by Task Order, at a minimum:

• Narrative overview of work completed, work in progress, and work planned for each task by personnel;

• Status of all task deliverables;

• Identification of risk areas with recommended remedial actions;

• Status of all outstanding risks identified in previous MSRs;

• Labor/CLINs used during month by cost and hours funded and expended;

• Projected date when 75% of funds will be expended by task;

• Projected date when funds will be 100% expended by task;

• Funds and hours remaining by labor/CLINs;

A-15

• Other direct costs (ODCs) estimated, used, and remaining by month;

• Summary of expenditures by task by resource and CLIN, both for the monthly reporting period as well as cumulative year-to-date totals, for the performance period;

• Personnel listing by task, start and end dates, on or off Government site status, and primary and secondary phone number; and

• Any additional information pertinent to the FAA in administering the performance of tasks or as required by the COR.

Program Management Reviews (PMRs)

The Contractor must conduct quarterly PMRs. The PMRs must be conducted on dates and locations acceptable to the government, and on a consistent schedule, and will generally be held at, or in the general vicinity of, the FAA headquarters location in Washington, DC. The PMRs must include review of documentation submitted in draft to the COR no less than two (2) business days before the PMR. The PMR and documentation must address the following information:

Schedule by Task Order and Project

• Schedule status and progress against all tasks

• Schedule variance and recommended corrective actions

• Issues requiring schedules of events and deliverables

Cost by Task Order and Project

• Current and cumulative costs traceable to the SOW tasks

• Variance from projected costs

• Cost projections for each task

Performance by Task Order and Project

• Achievements against milestones

• Performance and quality issues

• Significant risks

• Communication/Personnel issues

Task Order Management

The Contractor must designate a Project Lead to provide the appropriate program management and project control necessary to manage each task order issued under this contract, so that task order cost, schedule, and quality requirements are continually tracked, status is appropriately communicated to the FAA, and the task order is performed successfully. The Contractor must separately track the individual task orders.

A-16

Transition-In/Transition-Out Requirements

The following subsections identify required actions on the part of the Contractor upon contract start-up (i.e., Transition-In) and upon contract close-out (i.e., Transition-Out).

3.9.6.1 Transition-In Requirements

The Contractor must ensure all staff have completed their DOT personnel security requirement(s) (SF-85P) and have received all necessary approvals prior to starting work on the contract. The Contractor shall be fully staffed and operational within 60 days of the effective date of contract award, barring any delays or issues that are beyond the control of the Contractor. At a minimum, the Contractor must accomplish the following transition-in activities with the incumbent Contractor or the Government or both as applicable:

• Assume full responsibility for providing the support services required under newly issued task orders;

• Assume version control of historic data, documentation, processes, and training as applicable;

• Assume user and system administration responsibilities for all systems and tools;

• Identify and maintain inventory of all Government-furnished items (GFI);

• Obtain facility and network access (keys, cards, security codes/PINs, etc.) and required training; and

• Conduct introduction/orientation activities as required to meet the requirement of task orders issued under this contract.

During the first 120 calendar days of contract performance, the Contractor must conduct, as directed by the CO or COR, Weekly Transition Status Meetings to provide active and planned status on all Transition-In activities.

3.9.6.2 Transition-Out Requirements

No less than 30 calendar days prior to the contract end date, the Contractor must:

• Provide the most recent version of all documentation for which the contractor is responsible to manage or maintain version control;

• Provide a final financial summary report that is cumulative across the full contract period of performance;

• Provide a final status report that includes a projection of activities for the remainder of the Task Order;

• Support the return of all Government-furnished items (GFI) to the Government and/or transfer to the successor Contactor;

• Conduct a close-out meeting with the FAA (details and participants to be determined by the FAA); and

• Turn in all FAA-issued PIV cards to the COR no later than the final day of the period of performance under the last Task Order.

A-17

4 End Results/Deliverables This section describes 1) the products and tangible end results that are expected from the activities contained in 1) Section 3; 2) the date each deliverable is due; and 3) the government acceptance criteria.

All days are business days unless otherwise specified.

SOW

Para. # End Result / Deliverable Due Date Acceptance Criteria

3.8.3 Monthly Status Reports (MSRs) 10th day of

the month, reporting on the previous month

The MSRs are accurate, complete, submitted on time in conjunction with invoice submission and in accordance with (IAW) SOW Section 3

3.8.4 Program Management Reviews

(PMRs)

Quarterly The PMRs are accurate, complete, and submitted on time and prepared IAW SOW Section 3

Additional deliverable requirements may be identified in individual task orders.

5 Place of Performance The place of performance for this contract will be at both the Contractor facilities and the Government facilities at, but not limited to, FAA Headquarters in Washington, DC; FAA Air Traffic Control System Command Center (ATCSCC); William J Hughes Technical Center (WJHTC); Mike Monroney Aeronautical Center (MMAC); FAA Service Centers; Network Operations Control Centers and Security Operations Control Centers operated by FAA service providers; and NAS Operational facilities throughout the continental United States such as the NEMCs in Hampton, Georgia and Salt Lake City, Utah.

6 Hours of Operation General hours of operation this contract will be 8:00am to 5:00pm local time. The “hours of operation” correspond to the timeframe within a work week for the Contractor must provide the required support. Any task order-specific hours of operation will be identified in the task order as applicable. Alternate work schedules or telework, or both, must be approved in advance by the Contracting Officer, with agreement from the COR. Furthermore, any requests to the Contracting Officer for Contractor employee telework, either intermittent or regularly scheduled, may only be requested if the Contractor Company has a Telework policy and their employee has met the requirements and been approved thereunder.

When FAA offices close, contractor employees may work in their local offices, telework if previously approved by the Contracting Officer, or be granted access to Government buildings, if appropriate, as directed by the FAA.

A-18

7 Security Clearances, Certifications, and Accreditations Personnel engaged in some functional work areas may be required to have security clearances, including some clearances as high as Top Secret. Requirements for security clearances will be identified with the individual task orders. At a minimum, the Contractor must provide up to 25 personnel with Top Secret clearances and up to 75 personnel with Secret clearances, as requested to support work efforts required by task orders issued under this contract. Personnel with the required security clearances must be available upon contract award and throughout the contract period of performance.

For each software development life cycle (SDLC) phase, the Contractor must: (1) be Six-Sigma certified or certified at CMMI Level 3 or better; and (2) comply with FAA standards for coding, documentation, and implementation.

The Contractor must be accredited as a Third Party Assessment Organization (3PAO) by the American Association for Laboratory Accreditation (A2LA) to perform initial and periodic assessments of cloud service providers.

8 Government Portals and Information Management Tools The following is a list of Government-operated portals and information management tools that the AISS Contractor may be required to use and/or support. There may be other portals and tools in addition to those listed below.

• Morning Briefing Report – The NOCC is responsible for generating and disseminating the Morning Briefing Report which is used to brief executive management about previous day impacts to NAS operations.

• Maintenance Alerts – The Tactical Operations Program Team, in partnership with maintenance support organizations, coordinates and issues Maintenance Alerts for maintenance moratoria, seasonal maintenance information, and for maintenance issues that can systemically affect facilities and services.

• Moratorium Waivers – The Tactical Operations Program Team, in partnership with maintenance support organizations, coordinates waivers for activities that must occur during moratorium periods.

• Field Incident Response – During periods of National emergency (e.g., Hurricanes, Earthquakes, and Floods), the National Crisis Response Emergency Operations (CREO) group is responsible for collecting and disseminating real-time NAS status information.

• NAS Delays – Part of its reporting mandate requires the Tactical Operations Program Team to collect delay-related data from various sources, compile it, and produce standardized delay reporting products.

• National Modification Index – The NOG, in partnership with maintenance support organizations, publishes this report to facilitate the distribution and notification of NAS equipment modification issuances.

• Technician Network (TechNEt) Portal – TechOps information portal that publishes a wide array of Technical Operations data, tools, links and resources.

A-19

• Emergency Operations Portal – A web-based portal that supports Technical Operations as well as FAA Command, Communications & Control (C3), Regional Operations Centers, and Emergency Operations organizations.

• Mapping Portal – A decision-support support portal for text-based data normally available on…