AXE-400 Program Support Services SOW_5.15.2024.pdf

STATEMENT OF WORK

AXE Program Support Services in support of Federal Aviation Administration (FAA) Office of National Security

Programs and Incident Response

Table Of Contents

1 Introduction ______________________________________________________ 3

1.1 Background _______________________________________________________________ 3

1.2 Scope of Work _____________________________________________________________ 3

2 References ________________________________________________________ 4 3 Task Requirements ___________________________________________________ 5

4 Period of Performance _______________________________________________38 5 Place of Performance ________________________________________________38

1 Introduction

The Federal Aviation Administration's (FAA's) Command and Control Communications (C3) Division and the Recovery Communications (RCOM) Program were established to encompass all FAA emergency command and control systems and to consolidate the various FAA emergency communications development projects under one program. The RCOM program provides the FAA with the capability to manage the restoration of the National Airspace System (NAS) during local, regional, and national emergencies or unique situations. This Statement of Work (SOW) will identify the support required to accomplish this program's mission.

1.1 Background

The Command & Control Communications Division provides the FAA with emergency communications in response to local, regional, and national emergencies when normal common-carrier communications are interrupted and ensures FAA decision makers have command and control communications during times of crisis. The C3 Program Office also ensures the Primary Alternate Facility (PAF), the agency’s alternative command and control facility, is ready for immediate operations by senior FAA leadership in response to an emergency/crisis that requires relocation from Washington, DC. and direct the agency’s Aviation War Risk Program that ensures commercial carriers fly missions in support of the Defense Department within combat zones.

The C3 Program Office has been tasked to implement and manage emergency communications efforts for the FAA. Emergency and control communications systems are defined as those means of communications the FAA employs to direct the management, the operations, and the reconstitution of the National Airspace System (NAS) in support of the FAA, the Department of Transportation (DOT), the Department of Defense (DoD), and other US Agencies’ missions during national disasters or national security emergencies when normal common carrier telephone circuits become disrupted. C3 systems are also inclusive of the various buildings, vehicles, and facilities necessary to provide emergency command and control capability to the FAA. The primary importance of these efforts is to enable the ability of FAA Senior Management at Headquarters to communicate with all FAA facilities and other important Government officials in case of national emergency or crisis, whether man-made or natural, that would disrupt existing routine communication systems such as plain old telephone service (POTS). When normal common-carrier communications are interrupted, C3 provides and enhances a variety of fixed-position, portable, and transportable emergency communications systems that support crisis management; enable the FAA and other Federal agencies to exchange classified and unclassified communications to protect national security; and support and modernize the Washington Operations Center Complex (WOCC) and several FAA Continuity of Operations (COOP) sites. This verifies FAA decision makers have command and control communications during times of crisis.

1.2 Scope of Work

The C3 Program Office manages several programs designed to comply with both National Security mandates and public safety demands. These programs enable the FAA to provide communications services that meet the requirements for connectivity, redundancy, inter-agency interoperability, restorability, and hardness needed to support routine and emergency operations. The Contractor must provide technical, business, administrative and management support and be able to perform at the unclassified, Secret, and Top Secret/Sensitive Compartmented Information (TS/SCI) levels for programs, projects and systems defined under this SOW. The C3 programs, projects, systems, and facilities include:

• Emergency Response and Continuity Facilities

• Washington Operations Center Complex (WOCC)

• Emergency Operations Center (EOC)

• Primary Alternate Facility (PAF)

• Communications Support Team (CST)

Emergency Communications

• Very High Frequency/Frequency Modulation (VHF/FM) radio infrastructure

• High Frequency Single Sideband Radio System (HF/SSB)

• Fixed and portable Satellite Telephone Emergency Network (STEN), voice and data over satellite

• Digital Microwave Communications Network (P1)

Classified Systems and Communications

• Voice Over IP Secure Phone (VIPERS)

• Secure Conferencing System (SCS)

• Secure Facsimile (SECFAC)

• Secure Iridium’s/Secure Satellite Phones/Secure VHF/Secure Cell

• Classified Data Networks

• KG-175, KG-250, and KOV-26 – devices that are part of the cryptologic family

• Distributed Continuity Integrated Network - Top Secret (DCIN-TS) System GOLD

• Defense Red Switch Network (DRSN) also referred to as Integrated Services

Telephone (IST-2)

Unclassified Systems and Communications

• Information Technology Systems

• Standard Telco Phone System/Teleconferencing System

• Emergency Operations Network (EON)

• Emergency Notification System (ENS)

• Video Teleconferencing (VTC)

2 References

The Contractor must be in full compliance with regulations expressed in the following procedures, orders, and programs.

FAA Acquisition Management Policy:

http://fast.faa.gov/AMP_TOC.cfm

FAA Acquisition Toolset:

http://fast.faa.gov/

ID Badge Online Application:

https://my.faa.gov/org/linebusiness/ash/programs/id_badge/instructionsapplication

Contractor & Industrial Security Program:

https://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/ documentID/1040448 Orders and Notices:

http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parent

Finance Standard Operating Procedures (SOP):

https://my.faa.gov/org/staffoffices/afn/finance/sop

Forms: https://www.faa.gov/forms http://fast.faa.gov/AMP_TOC.cfm http://fast.faa.gov/ https://my.faa.gov/org/linebusiness/ash/programs/id_badge/instructionsapplication https://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentID/1040448 https://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentID/1040448 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parent https://my.faa.gov/org/staffoffices/afn/finance/sop https://www.faa.gov/forms

The contractor shall ensure that their operations will be compliant with the following policies and guidance. Any updates to these policies and guidance during the life of the contract, the contractor must be compliant with as well.

- Presidential Policy Directive-40 (PPD 40) National Continuity Policy

- Executive Order 13618, Assignment of National Security and Emergency

Preparedness Communications Functions (supersedes EO 12472)

- Presidential Decision Directive-63 (PDD 63), Critical Infrastructure Protection

- Office of Science and Technology/Office of Management and Budget (OSTP/OMB)

Directive 16-1 (Minimum Requirements for Executive Branch Continuity Communications)

- OMB A-130

- Intelligence Community Directive 705, Sensitive Compartmented Information

Facilities (SCIF)

- National Emergency Communications Plan

- Federal Information Security Management Act (FISMA) and FedRAMP Guidance and

Process

- National Security Policy Directive-47 (NSPD-47)/Homeland Security Policy Directive-

16 (HSPD-16) (Aviation Security Policy)

- Federal Continuity Directive -1 (FCD-1)

- Federal Continuity Directive -2 (FCD-2)

- National Strategy for Aviation Security (NSAS)

- National Institute of Standards and Technology (NIST) documentation and standards

- National Response Plan

- National Incident Management System

- DOD 5220.22M, National Industrial Security Program Operating Manual (NISPOM)

- FAA Order 1100.1B, FAA Organization – Policies and Standards (Change 1)

- FAA Order 1110.282, Office of Security and Investigations

- FAA Order 1370.82 (Information Systems Security Program)

- FAA Order 1370.121, FAA Information Security and Privacy Program and Policy

- FAA Order 1600.2E, Protection of Classified Information

- FAA Order 1600.6E, FAA Facility Security Policy

- FAA Order 1600.38F, Employee and Other Internal Investigations

- FAA Order 1600.69C, FAA Facility Security Management Program

- FAA Order 1600.75, Protection of Sensitive Unclassified Information

- FAA Order 1600.76, SCI Program

- FAA Order 1650.20A, Support for Sensitive National Defense and Law Enforcement

Operations – redacted

- FAA Order 1700.6C, FAA Branding Policy

- FAA Order 1900.1G, FAA Emergency Operations Plan

- FAA Order 1910.K, FAA Continuity Program

- FAA Order 1910.1J, Continuity of Operations Plan for Washington Headquarters

- FAA Order 1990.1, FAA National Command and Control System

- FAA Crisis Management Handbook

- ATO Notice JO 1100.326, Air Traffic Organization

- ATO Order 7610.4T, Special Operations

- C3 EON Change Control processes and procedures

- FAA Crisis Management Handbook

- DoD Information Assurance Certification and Accreditation Process (DIACAP)

- Emergency Notification System (ENS) Governance Plan

3 Task Requirements

The Contractor must conduct the tasks described in the following sections.

3.1 Task 1 – Program Management Support

3.1.1 Task Order Management

The Contractor must provide program management support. The Contractor’s Program Manager (PM) will formulate, plan, organize and execute contract-related activities that meet the goals and objectives of the Program. It is the Contractor Program Manager’s responsibility to verify that identified tasks are performed efficiently, accurately, on time, on budget, and in compliance with the requirements. The Contractor must participate as a member of a government-led team when directed by the Contracting Officer’s Representative (COR). The Contractor must conduct a Kick-Off meeting between the stakeholders as identified in the agreement and the COR and Contractor to review SOW requirements and demonstrate they understand the work scope and deliverables. The contractor shall submit an agenda for the kick-off meeting to the COR at least five (5) business days before the meeting. The Contractor must provide minutes of the meeting to the COR within five (5) business days after the kickoff meeting.

3.1.2 Project Plan

The Contractor PM must support and assist with managing the RCOM Project Plan. The Contractor must keep the Project Plan current and updated using Microsoft Project.

3.1.3 Weekly Status Reports

The Contractor PM shall interface directly with the COR, and, when requested, the Government management team, on a weekly basis to provide real-time updates on critical items being addressed. Examples include, but are not limited to:

• Status tracking to provide updates on contractor staffing and utilization issues,

• Any clearance issues,

• Information on contractor personnel working locations, and specifically those who are working at a temporary alternate work location, and

• Any special project deadlines, such as end-of-year requirements.

• Updates shall include whether the schedule is on track or not, and whether additional resources are needed. A risk assessment shall be provided.

3.1.4 Monthly Status Reports/Monthly Quality and Performance Report

3.1.4.1 Monthly Status Reports

The Contractor must provide Monthly Status Reports (MSRs). The Contractor must provide an MSR that documents the activities of the previous month and identifies all planned activities for the following month. The reports must be delivered to the COR and must include, at a minimum, the following information:

• Overview of work completed, work in progress, and work planned for each task,

• Hours expended by task, labor category, and personnel.

• Status of individual deliverables. Deliverables shall be documented in a format acceptable to the COR. Each deliverable shall be acknowledged as received and accepted, in writing, by the COR. It shall include identification of risk areas and the status of outstanding risks associated with individual deliverables or tasks, with recommended remedial actions.

• Any additional information pertinent to the Government in administering the performance of this effort or when directed by the COR.

• Approved travel during reporting period and travel planned for next period.

• Pending Staffing Status.

• Pending Security Clearance Status.

• Scheduled deliverables and planned delivery dates.

• Actual delivery dates.

• Deliverables accepted (was it delivered on time, and acknowledgment that the supplies or services conform with applicable contract quality and quantity requirements. Deliverables will be documented in a format provided by the COR.

• Deliverables rejected with reason and corrective action steps taken. Risks shall be identified along with how they were mitigated and resolved.

• Risks and Issues Review and Status.

• Detailed financial status by CLIN & Task which captures funding levels and projections.

• The contractor shall provide the monthly quality and performance reports ten (10) business days ahead of the monthly status meetings for approval.

3.1.5 Monthly Financial Reports

The Contractor must provide Monthly Financial Reports on the 10th day of each month.

Each report must include the following for each Task:

• CLINs used during month.

• Cost/hours funded or apportioned by CLIN.

• Cost/hours used by CLIN.

• Projected date when 75% of obligated funds are expended.

• Projected date when funds are exhausted.

• Travel requests (TRs), including local travel, estimated, used, and remaining by month.

• Funds/hours remaining by CLIN.

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

• Summary of expenditures by resource and labor category for the monthly reporting period, as well as cumulative year-to-date totals for the performance period.

3.1.6 Program Management Review (PMR)

The Contractor must meet Quarterly with the PMO and COR for a Program Management Review to include discussion of the following:

• Contract/Task Order Information.

• Financial Summary.

• Status of Deliverables.

• Task Order Staffing Summary.

• Performance Summary.

• Accomplishments include corrective actions taken and risks resolved.

• Risks, Issues and Opportunities (RIO).

• Action Item Summary.

• Subcontractor Status, if any.

• Task Order Quad Charts.

• Backup Information.

PMR documentation will be submitted within five (5) days of COR request.

3.1.7 Schedules

The C3/RCOM Integrated Master Schedule (IMS) is a working document. The C3 PMO will maintain the IMS throughout the life cycle of the program. The tasks are managed and planned jointly by the RCOM program and the sub-program managers of the sub-programs responsible for task implementation.

The Contractor must support the IMS for each task area, that describes the tasks to be performed, task level resource requirements and the end results/deliverables to be produced.

Include risks identified by stakeholders.

C3/RCOM must enter all projects that may have an impact to a NAS facility (e.g. VHF- FM, SATCOM, Secure Communications) into the FAA’s Corporate Work Plan (CWP) with respect to schedule.

C3 and the Contractor will work in partnership to identify risks and mitigate risks in accordance with the FAA guidance that (1) identifies and analyzes risks, (2) plans and executes risk mitigation actions, and (3) monitors and adjusts mitigation actions until risks are reduced to acceptable levels. This includes identifying emerging risks, monitoring known risks, and reducing the effects of risk factors to acceptable levels.

3.1.8 Meeting Minutes/Trip Reports

The Contractor must provide meeting minutes for every meeting and trip reports for all trips. The Contractor will upload meeting minutes and trip reports to the AXE shared drive, and provide minutes and trip reports to the Government task lead with a copy to the COR.

Meeting Minutes must include at a minimum, topics discussed, list of participants, date and time of meeting, action items, and issues resolved. Trip Reports must include at a minimum reason for trip, worked performed, FAA point of contact (POC), duration and start/end locations. Meeting minutes shall be provided five (5) days after conclusion of the meeting. Trip reports shall be provided five (5) days after completion of the trip.

3.1.9 Task Order Phase-in and Phase-Out

3.1.9.1 Phase-In Transition Plan and Period

The Contractor must submit a proposed Phase-in Plan 20 business days after the contract award that describes actions necessary for a successful transition of operational responsibilities from the incumbent contractor to the new contractor.

Within thirty (30) calendar days of contract award, the Contractor must identify the Government Furnished Equipment (GFE) needed for contractor use.

The first thirty (30) business days from date of contract award constitute the Phase-In Period. The Contractor must provide support during this Phase-In Period. In case of a vendor change, there will be an overlap of thirty (30) days to facilitate knowledge transfer. The transition period will begin thirty (30) days before commencement of the base period of the contract.

3.1.9.2 Phase-In Joint Inventory

The Contractor must collaborate with the Government to conduct a joint inventory of Government Furnished Property (GFP) within twenty (20) business days after the contract award. The Contractor will provide the government with a monthly report or when requested by the government. During the inspection/inventory, the Contractor must identify the equipment and documentation to be transferred for contractor use. The Contractor must prepare, certify, and submit a detailed Phase-In Joint Inventory Report which must be submitted to the COR and the property custodian within 30 days. This report must be submitted within 5 business days after the survey is completed.

The Contractor must maintain an inventory list as provided by the FAA throughout the life of the contract and provide quarterly updates. The asset list is maintained within the FRAMES system. FRAMES reports can be run at any time by the property custodian or contractor as needed.

This list is maintained within the FAA’s asset management system. Major changes between quarterly updates must be reported to the Government at the time of occurrence.

3.1.9.3 Phase-Out Transition Plan and Period

The Contractor must submit a Phase-Out Transition Plan sixty (60) days before the end of the Task Order, for Government approval, that addresses the plans and procedures necessary to verify continuity of operations to the successor. The Contractor must make available all the contractor’s equipment, material and services required for the continued performance of the service. The Government reserves the right to assume, by negotiation, the possession of all facilities, equipment, material, and services necessary to provide and maintain C3 operations. The negotiation of the transfer of all property to be used by the Government after contract completion will take place during the Phase-Out Period.

The last) thirty (30) calendar days of the contract will constitute the Phase-Out Period. During this period, personnel of the incoming workforce may observe operations and performance methods of the outgoing contractor. This allows for orderly turnover of facilities, equipment, and records and will help to verify continuity of operations.

The Contractor must not defer any requirements for the purpose of avoiding responsibility or transfer such responsibility to the succeeding Contractor before the end of the last performance period. The outgoing contractor must fully cooperate with the incoming Contractor and the Government so as not to interfere with their work or duties.

3.1.9.4 Phase-Out Inventory

The Contractor and the successor must conduct a joint inventory of the GFP in accordance with the FAA Contractor’s Guide for Control of Government Property.

The Contractor must prepare, certify, and submit a Phase-Out Inventory Report no more than three (3) weeks before the end of the Task Order for approval by the Government. The inventory will include the same data as required for the Phase-In inventory. All valid discrepancies arising from the inventory must be noted. A Government representative will determine the validity of the discrepancy. If the government determines that the Contractor is responsible for the discrepancy due to negligence, the Contractor must correct the discrepancy prior to performance expiration, or the cost of repair must be deducted from the final payment to the Contractor. At the completion of the last performance period, the Contractor must return the same property or property equal in type, kind, quality, and quantity of items as originally furnished by the Government and accepted by the Contractor. Property no longer required during the execution of the Task Order must be returned within ten (10) days of the end of its use and the return to the Government must be documented as part of the Contractor’s inventory management. Government property must be in the same or better condition as when originally furnished, less normal wear and tear.

3.1.9.5 Phase-Out Execution

The Contractor must provide support to execute phase-out in accordance with the Phase- Out Plan. The Contractor must not disrupt or adversely impact the provision of services and must achieve a smooth and orderly transfer of responsibility to the successor.

Approximately four (4) weeks prior to the Task Order’s end date, the Contractor must provide the following to the COR:

• All documentation as of the most recent revision.

• A final financial report.

• A final status report including a projection of activities for the remainder of the Task Order.

• A copy of the phase-out inventory.

• A closeout meeting with the FAA (details and participants to be determined by the FAA).

• All FAA security badges, if issued, must be turned in to the COR by closeout of the Task Order.

3.2 Task 2 - C3 Communications Systems Engineering and Integration Support

The C3 Division is the Program Management Office (PMO) for the FAA’s RCOM program and comprises both long-range strategic and short-range, tactical components. The PMO was established to encompass all FAA command and control communications systems and to consolidate the various FAA command and control communications development projects under one program. The C3 Division Manager, AXE-400, is responsible for determining the set of C3 mission needs and developing the set of operational requirements that address the stated mission needs. C3 is responsible for providing planning and engineering support and the communications infrastructure to support AXE functions, including WOCC operations, emergency planning, special activities and law enforcement coordination, and national security and intelligence coordination.

C3 selects and carries out the secure and redundant communications systems requirements that satisfy the identified mission needs. Due to the wide variety of systems, the maintenance procedures for each are determined separately and may include technical support within the FAA community, contractor, or manufacturer maintenance, or C3 engineering support to troubleshoot problems, replace parts, and schedule preventive and/or corrective maintenance.

To support the development and consolidation efforts the C3 Program Office requires contract support for the acquisition, deployment, implementation, and maintenance of;

• Very High Frequency/Frequency Modulation (VHF/FM),

• Satellite Communications (SATCOM),

• Microwave Communications Network,

• High Frequency/Single Sideband (HF/SSB) Radio System.

The primary purpose of these communication systems is to support emergencies and day- to-day operations. These systems are used for emergency, real-time data, voice, and video communications during events such as hijackings, natural disasters, terrorist acts, accidents investigations, and rescue operations. These programs are designed to comply with both National Security mandates and public safety demands. They enable the FAA to provide communications services that meet the requirements for connectivity, redundancy, inter-agency interoperability, restorability, and hardness needed to support routine and emergency operations. The Contractor must maintain and operate systems consistent with FAA requirements for connectivity, redundancy, agency interoperability, restorability, and hardness needed to support routine and emergency operations. This support includes the following areas:

3.2.1 Requirements Analysis Support

The C3 Division Manager, AXE-400, is responsible for determining the set of C3 mission needs and developing the set of operational requirements that address the stated mission needs. The RCOM Program selects and carries out the secure and redundant communications systems requirements that satisfy the identified mission needs.

The C3/RCOM Program monitors systems and networks for shortcomings, service issues, and operator training issues and takes action to correct deficiencies using established and proven processes. Management and technical staff remain current with the lifecycle status of each RCOM Program system and network and take action to upgrade or replace equipment in a timely manner that avoids service disruptions. Due to the wide variety of systems, the maintenance procedures for each are determined separately and may include technical support within the FAA community, contract or manufacturer maintenance, or RCOM Program engineering support to troubleshoot problems, replace parts, and schedule preventive and/or corrective maintenance. The program office will maintain the requirements traceability matrix (RTM) throughout the life cycle of the program as requirements change.

The Contractor must review and evaluate customer and/or system functional and technical requirements to assist in the development of program's plans, requirements documents, cost/benefit analysis, work breakdown schedules, performance goals, generate flowcharts of office processes, risk analysis and quality assurance measurements. The analysis support will include providing the Government with recommendations to improve processes and procedures. The Contractor must support the C3/RCOM requirements traceability matrix to provide bi-directional traceability that clearly provides traceability of performance to requirements and indicates metrics and verification methods used to validate requirements are met within FAA standards.

3.2.2 Engineering and Planning Support

The Contractor must analyze technical requirements to support solution development.

In addition, the Contractor must attend Technical Interchange Meetings (TIMS), prepare engineering diagrams, drawings, data flow diagrams, conduct propagation studies, red-line drawings, disposition plans white papers, and coordinate technical issues with the FAA. The Contractor must prepare detailed timelines and schedules for assigned tasks and provide quality assurance for work performed by third party contractors.

3.2.3 Site Surveys, Evaluations, and Preparation Support

The Contractor must conduct site surveys and generate site survey reports all systems supported by AXE-400 and the FAA. These site survey reports allow the FAA to help maintain systems or resolve issues at FAA facilities prior to the installation of hardware.

Site survey information will include information regarding all coordination with facility personnel, a preliminary installation design and identification of all systems that interfere with the planned implementation. The Contractor site survey reports must at a minimum address power requirement, HVAC requirements, floor plans, rack space, cable paths and facility design, local contact information (points of contact) and use constraints.

3.2.4 Program and Technical Documentation Support

The Contractor must assist at all levels during the development of all required technical documentation, to include but not be limited to the following: Operational Requirements Documents (ORDs), Interface Control Documents (ICDs), System Requirements Validation Matrix (SRVM), System Level Test & Integration Plans, NAS Change Proposals (NCPs), training documentation and Joint Acceptance Inspection (JAI) documentation.

This must include the resolution of all comments dealing with specific NCPs.

3.2.5 System Safety Management

The RCOM Program must conduct safety risk management activities in accordance with the current version of FAA Order 1000.37, Air Traffic Organization Safety Management System, the current version of FAA Order 8040.4, Safety Risk Management, ATO Safety Management System (SMS) Manual, and the Safety Risk Management Guide for Systems Acquisitions.

The Contractor will develop the System Safety Program Plan (SSPP) in accordance with the SRMGSA. The Contractor will collaborate with the PO by participating in all Safety Risk Management (SRM) panels as required.

In the SSPP, the Contractor must detail the systems safety program scope, safety organization, program milestones, safety requirements and criteria, hazard analyses to be conducted, safety data to be collected, safety verification approach, safety program audit process, accident/incident reporting system, and the organization’s functional interfaces.

3.2.6 Installation Support

Site installation and checkout is performed by C3/RCOM personnel with the assistance and support of local System Support Center (SSC) personnel, as needed. All functionality, operability and training are completed as a part of the installation and checkout.

Installations are performed with IAW applicable manufactures technical instructions, and all initial parameters are measured and recorded in IAW FAA JO 6600.31.

The Contractor must assist both the FAA and/or other vendors in the installation of all required communications systems except where specific certification requirements (e.g., tower installation) are necessary, such exceptions are solely determined by the FAA.

This includes the planning and installation of hardware and software and the test and cutover exercises required for system validation/acceptance to the end goal of Full Operational Capability (FOC).

The Contractor must provide at least two certified Authorized Climbers to support installation and troubleshooting on FAA towers. Training must meet OSHA CFR 1910.268

– ANSI Z359 & Z490 – NATE CTS Industry Standards as it pertains to Authorized Climber / Rescuer.

The Contractor must provide support and planning relative to the installation of the following:

a. Grounding systems

b. Power systems

c. VHF-FM radios, repeaters, and consolettes

d. VHF-FM antennas

e. Satellite Communications Systems

f. Microwave antenna towers and antennas

g. Microwave radio systems

h. Microwave waveguides

i. Dehydrators

j. High Frequency radio equipment

k. High Frequency antennas

3.2.7 Testing Support

All C3/RCOM systems and equipment are currently deployed, in-service, technical refresh projects are designed to replace aging equipment with the same form, fit, and function with commercially available COTS equipment without modification. The C3/RCOM test program comprises a combination of voluntary testing and prescribed testing to ensure C3/RCOM facilities and systems are always operational and in a state of readiness. The Contractor must assist the C3 Program Office in the testing of all installed hardware, software, and systems.

The C3/RCOM communications modalities (VHF-FM, SATCOM, P1, and HF) conduct operational testing, which varies by sub-program and system, to ensure all aspects of the system and/or equipment is functioning as intended. C3/RCOM also conducts field familiarization (FF) activities that allow the operators to gain confidence in the system and attain a higher level of hands-on familiarization. The level and type of FF support is determined through coordination with site representatives to identify specific areas that require familiarization.

The Department of Homeland Security (DHS) conducts an exercise to test the readiness and capabilities of federal departments and agencies—coordinating with the White House—to execute their Continuity of Operations (COOP) plans. The exercise, known as Eagle Horizon, is a mandatory annual exercise for all executive branch departments and agencies coordinated by DHS through the Federal Emergency Management Agency (FEMA) and its National Continuity Programs (NCP) Directorate. C3/RCOM is required to participate in the annual Eagle Horizon exercise. This typically includes a mock activation of the PAF with operational tests/checks of each communications/data system.

The Contractor must assist the C3 Program Office in the testing of all installed hardware, software, and systems. The Contractor must provide as Test Plan for each installation.

The Test Plan must include at a minimum estimated cost, schedule, resource requirements (H/W, Tools), access to facilities/equipment, FAA coordination, testing measures and standards and acceptance criteria. The test plan must include test and verification procedures to verify proper installation and operation in the installed environment with Stakeholder approval. The test plan must be approved by the COR before testing begins. Testing will validate that all installed hardware works as intended.

The Contractor must coordinate with the William J. Hughes Technical Center and/or local representatives to assist with acceptance testing. The Contractor must assist with vendor/subcontractor oversight to assure requirements from William J. Hughes Technical Center and other FAA entities are met. The Contractor must also assist, and complete documentation as needed for spectrum approval and licensing.

3.2.8 Preventive Maintenance and Repairs Support

The Contractor must provide the C3 Program Office with maintenance support for all installed systems following acceptance. When directed by the COR, the Contractor must also provide FAA or FAA contract personnel with specialized training to support installed systems.

3.2.9 VHF-FM Communications Engineering Support

National Security Presidential Directive 51 (NSPD-51) / Homeland Security Presidential Directive 20 (HSPD-20) require federal agencies to furnish and maintain intra-agency and inter-agency communications interoperability during national disasters. The FAA must comply with these requirements. The same need also exists between FAA facilities during local or regional emergencies where the Public Switched Telephone Network (PSTN) has been disrupted. Federal Continuity Directive 1 (FCD-1) provides direction for the development of continuity plans and programs for the Federal executive branch, including continuity communications.

The VHF/FM radio network [otherwise known as the National Radio Communications System (NRCS), with Facility, Service, and Equipment Profile (FSEP) Facility Type of “NRCS”], provides the FAA with the ability to support real-time command and control communications during national emergencies and natural disasters, especially when communication by regular landline and cellular networks are impossible. The VHF/FM radio network provides local handheld, mobile, and base station emergency radio communications via repeaters located throughout the CONUS and overseas. Repeaters permit extended-range communications for a minimum of 30 miles. The transmitting range varies between repeaters and depends upon the height of the antenna, power of the repeater, terrain features, and natural and man-made obstacles interfering with near line-of-site communications. The FAA presently has about 1,900 handheld and mobile radios, over 250 consolettes, and over 200 repeaters in use. These systems reside with the local SSCs throughout the United States. The RCOM Program plans to continue the current technical refresh schedule to ensure this system is ready for use in a crisis.

The VHF mission need is to provide essential command and control communications necessary to report on and coordinate activities essential to reestablish air-ground communications, radar systems, navigation aids, and air traffic control functions when common carrier communications affecting facility communication are interrupted or otherwise fail. It is also very common that VHF systems are used on a regular basis in areas where cellular phone coverage is spotty or unavailable.

The VHF assets are installed at major FAA facilities, including FAA National Headquarters, Air Route Traffic Control Centers (ARTCCs), selected Terminal Radar Approach Control Facilities (TRACONS), regional headquarters, selected air traffic control towers, U.S.

Virgin Islands, Puerto Rico, and the Hawaiian Islands. Handheld VHF radios are provided to most of the facilities and permit a grab-and-go emergency communications capability in the event a facility requires emergency evacuation. Suitcase style transportable systems are made available as a suitable alternative to the legacy vehicle mounted systems. The repeaters, consolettes, and base stations are the fixed mounted style and provide the most robust/largest radius of coverage.

3.2.10 Satellite Communications Engineering Support

There is an ongoing FAA requirement formerly referred to as the Satellite Telephone Emergency Network (STEN). It is now more commonly called the Satellite Communications (SATCOM) program. The original network was implemented in 1995, refreshed once in 2004, undergoing a second refresh in 2021-2024/5, and includes fixed site, handheld, and transportable (suitcase/pelican-case style) satellite telephone systems. The SATCOM program does not replace any National Airspace Systems but provides the emergency command and control communications means to coordinate re-establishment of the NAS and conduct other emergency response actions.

National Communications System Directive 3-10 (NCSD 3-10) and NSPD-51/ HSPD-20 require federal agencies to furnish and maintain intra-agency and inter-agency communications interoperability during national disasters. The FAA must comply with these requirements. The same need also exists between FAA facilities during local or regional emergencies where the PSTN has been disrupted. FCD-1 provides direction for the development of continuity plans and programs for the Federal executive branch, including continuity communications.

The SATCOM mission need is to provide the minimum essential satellite-based command and control communications necessary to report on and coordinate activities essential to reestablish air-ground communications, radar systems, navigation aids, and air traffic control functions when common carrier communications affecting facility communication are interrupted or otherwise fail. These systems are not for the control of air traffic.

SATCOM is intended to provide the minimum essential satellite-based command and control communications necessary to report on and coordinate essential activities to reestablish air-ground communications, radar systems, navigation aids, and air traffic control functions. This becomes necessary when common carrier communications affecting facility communications are interrupted or otherwise fail. The FAA presently has about 218 handheld SAT phones, with 111 transportable and fixed-base stations in use.

The FSEP Facility Type is “SACOM.” These systems reside with facility management personnel at key FAA locations. The RCOM Program plans to continue the current technical refresh schedule to ensure this system is ready for use in a crisis.

The SATCOM program fixed satellite telephones (more than 100) are installed at all major FAA facilities, including FAA National Headquarters, all ARTCCs, selected TRACONS, all regional headquarters, selected air traffic control towers, U.S. Virgin Islands, San Juan Center Radar Approach Control (CERAP), and selected Hawaiian Islands.

Handheld and transportable units (more than 250 overall) are provided to most of the facilities that already have fixed systems and permit a grab-and-go emergency communications capability in the event a facility requires emergency evacuation.

Handheld satellite telephones are provided to emergency responders as their needs are identified and approved by program management. Suitcase/pelican-case style transportable systems (less than a dozen in the field) are made available on an as needed basis.

The C3 Program Office purchases and deploys both transportable and fixed satellite phones. Satellite phones may be secure or clear and require initialization before being deployed in the field. The Contractor must maintain the operational suitability of all C3 Satellite telephones. The Contractor must provide the deployment support by conducting site surveys, installing Subscriber Identity Module (SIM) cards, and tracking locations, usage, and logistical concerns in the program office inventory system. The Contractor must also perform the role of POC for the maintenance and replacement of the radios in the satellite network. This may include supporting developing contract SIRs, supporting the COR, initial troubleshooting, end user support, and preparing ordering criteria for replacement equipment.

The satellite network is an integral part of the agency’s emergency communication system and must remain operational 24/7, 365 days a year. Once an issue is reported the contractor must initiate technical support and replacement parts within two (2) calendar days.

The Contractor must support bi-monthly SATCOM exercises. To verify proper operation of the SATCOM system, bi-monthly exercises will be performed in conjunction with the C3 Program Manager. All performance issues will be addressed prior to the next quarterly test. The Contractor must be capable of being an active, contributing participant to any potential future proof of concept projects, which may be designed to determine feasibility of expanding satellite telephony services to include data and teleconferencing capabilities.

3.2.11 Digital Microwave Communications Engineering Support

The RCOM Digital Microwave Communications System, known as Project One (P1), derives its requirements from Presidential Policy Directive (PPD) 40, National Continuity Policy, Federal Continuity Directive 1, Federal Executive Branch National Continuity Program and Requirements, and Office of Science and Technology Policy (OSTP) and Office of Management and Budget (OMB) Directive D-16-1 (OSTP/OMB D-16-1), Minimum Requirements for Federal Executive Branch Continuity Communications Capabilities requires that the United States have sufficient secure command and control communications capabilities at all levels of Government to meet essential defense and civilian needs during any national security emergency, including natural or technological disasters, acts of terrorism, and acts by foreign governments hostile to the United States. PPD-40, FCD-1, and OSTP/OMB D-16-1 contain specific guidance pertaining to various emergency operations areas, including secure and redundant command and control communications programs, to which Federal government departments and agencies must adhere.

Per OSTP/OMB Directive D-16-1, “Physically Diverse Data Networks: All continuity locations shall utilize physically diverse and redundant communications links or alternate telecommunications services to access the non-secure data networks. These communications links or alternate services can include utilizing redundant network service providers that are separated from primary service providers or utilizing out of band channels for data routing.”

P1 is a point-to-point, semi-mesh, microwave radio network, which provides a redundant data transmission path, and in some cases, the primary data transmission path, for mission essential operations during any circumstance that has degraded inter-operable communications via the FAA Telecommunications Infrastructure (FTI) or FAA Enterprise Network Services (FENS), in accordance with Presidential/Homeland Security Directives.

The P1 network currently consists of 13 sites and 14 microwave links. The RCOM Program plans to continue the current technical refresh schedule to ensure this system is ready for use in a crisis.

The P1 network’s primary purpose is to serve as the alternative data transport infrastructure between FAA’s crisis management / disaster recovery locations (Headquarters, Emergency Operations Center, and Primary Alternate Facility) for the COOP cadre. P1 uses microwave radios to transport non-secure/unclassified data as a physically diverse data network. P1 is part of the C3LAN security boundary, therefore has a current Authority-To-Operate (ATO).

The loss of the P1 network would limit the overall effectiveness to meet Continuity of Operations and Continuity of Government mission requirements and provide command and control communications in times of crisis.

P1 supports not only the FAA’s continuity responsibilities, but also those of U.S. Secret Service, Federal Bureau of Investigation, and Department of Defense. These are established officially via cost-based, Inter-Agency Agreements (IAAs). On a non-cost basis, P1 also supports the Virginia State Police, West Virginia Emergency Services, FEMA MERS, DOD Joint Air Defense Operations Center (JADOC), White House Communications Agency (WHCA), Department of Homeland Security AMOC, Crisis Management System (CMS), and U.S. Air Force (USAF), each with its own private network tunnel.

The Project One (P1) network is a data transmission network, designed to be independent of commercial power and communications systems, to provide a resilient, redundant data path for the FAA and various other Federal agencies in the National Capital Region.

The core requirements of the P1 program are:

• Provide data service that is available 100% of the time, to the FAA and “other” agencies

• Support secure data transfer of classified information

• Utilize equipment which is field software upgrade capable

Examples of responsibilities include, but are not limited to:

• Coordinating work with the C3 Microwave Program Manager.

• Planning, engineering, operating, and maintaining RF equipment.

• Assisting with new equipment installs.

• Responding to network outages.

• Generating daily reports to track new or existing issues.

• Troubleshooting RF equipment outages.

• Coordinating access to sites; and

• Meeting with vendors to test and evaluate new products.

3.2.12 High Frequency Communications Engineering Support

The High Frequency (HF) network is a voice transmission network, designed to be independent of commercial power and communications systems, to provide a resilient, redundant means of communication for the FAA.

The Recovery Communications (RCOM) High Frequency (HF) Program derives its requirements from Presidential Policy Directive (PPD) 40, National Continuity Policy, Federal Continuity Directive 1, Federal Executive Branch National Continuity Program and Requirements, and Office of Science and Technology Policy (OSTP) and Office of Management and Budget (OMB) Directive D-16-1 (OSTP/OMB D-16-1), Minimum Requirements for Federal Executive Branch Continuity Communications Capabilities requires that the United States have sufficient secure command and control communications capabilities at all levels of Government to meet essential defense and civilian needs during any national security emergency, including natural or technological disasters, acts of terrorism, and acts by foreign governments hostile to the United States. PPD-40, FCD-1, and OSTP/OMB D-16-1 contain specific guidance pertaining to various emergency operations areas, including secure and redundant command and control communications programs, to which Federal government departments and agencies must adhere.

Per OSTP/OMB Directive D-16-1, “Alternate Communications Capabilities: [HF] Shall be a dedicated system installed at alternate locations. [It] shall be capable of Top-Secret voice transmission using an NSA-approved encryption device. [It] shall be able to transmit CONUS-wide at all times by ensuring that the system possesses the appropriate capabilities. [It] shall be certified for compliance by the Joint Interoperability Test Center (JITC) to meet HF Automatic Link Establishment (ALE) requirements of MIL-STD-188- 141C, and compliant with National Telecommunications and Information Administration (NTIA) requirements for equipment used within the United States.”

The HF network’s primary purpose is to serve as an alternate communications capability for the FAA COOP cadre to communicate with other federal agencies in times of crisis. HF is not part of the NAS, nor is it used to transmit data to/from the PAF, where it is located.

There is only one of these systems in the FAA inventory. High Frequency (HF) communications relies on the Department and Agency Continuity Network (DACN) to provide continuous capability for senior FAA management communications with DOT and other Agencies’ alternate sites when common carrier and cellular network circuits fail.

This is a continuity communications system to be used in the event of a natural or man-made crisis which would cause the Primary Alternate Facility (PAF) to be activated and is a requirement of OMB/OSTP D-16-1. This system is comprised of an HF antenna, HF transceiver, HF amplifier, and Communications Security (COMSEC) devices.

The loss of the HF network would limit the overall effectiveness of meeting Continuity of Operations and Continuity of Government mission requirements and provide command and control communications in times of crisis.

This function is part of a team of Emergency Communications professionals supporting the FAA’s C3 Office, which is responsible for ensuring emergency operations are maintained during national…