AXE-400 IT and Program Support SOW_2nd SOW Posted.docx

AXE-400 C3 Program and IT Support Services Federal Aviation Administration (FAA) Office of National Security Programs and Incident Response Statement of Work (SOW)

Table of Contents

Introduction The RCOM program allows the FAA to manage the restoration of the National Airspace System (NAS) during local, regional, and national emergencies or whenever needed. The Command and Control Communications Division (C3) serves as the overall Program Management Office (PMO) for RCOM and will hereafter be referred to as the PMO.

The C3 Program Office has been tasked to implement and manage emergency communications efforts for the FAA. In this context, emergency command and control communications systems are defined as those means of communication 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 or when commercial communication systems become disrupted.

This Statement of Work (SOW) will identify the support required to accomplish the RCOM program's mission.

1.1 Mission of Need

The Federal Aviation Administration's (FAA) Office of National Security Programs and Incident Response (AXE) The Office of National Security Programs and Incident Response (AXE) safeguards the FAA through agency-level emergency readiness, crisis management, intelligence threat identification and analysis, and national security support that promotes and ensures national airspace and aviation safety and security. Among its constituent Divisions are several that support elements of the Command and Control Communications (C3) Division and the Recovery Communications (RCOM) Program, which was established to consolidate various FAA emergency communications systems, projects, and initiatives.

1.2 Background

The RCOM program Command & Control Communications Division provides the FAA with emergency command and control communications when everyday standard carrier communications are interrupted. This ensures that FAA decision-makers have continuous command and control communications capability during times of crisis or interruption. The C3 Program Office also provides the Primary Alternate Facility (PAF), the agency’s alternative command and control facility, which is ready for immediate operations by senior FAA leadership in response to any emergency/crisis that requires relocation from Washington, DC. It directs the agency’s Aviation War Risk Program, which ensures that commercial carriers fly missions supporting the Defense Department within combat zones should it become necessary.

Part of the RCOM C3 system includes operating and maintaining various buildings, vehicles, and facilities near Washington, DC. The most significant is the Primary Alternate Facility (PAF), intended to serve as the alternative command and control facility for senior FAA leadership in response to any emergency/crisis that requires relocation from Washington, DC. The others are primarily communications towers linking FAA HQ with the PAF. Each location is crucial to providing the FAA with emergency command and control capability.

Other RCOM activities deploy communications equipment to the field, either fixed, portable (conveniently carried by a person), or transportable (usually best carried in a vehicle). Some RCOM sub-programs, including VHF/FM and SATCOM, procure and install fixed-position equipment at FAA key sites well before an emergency/crisis. Most sub-programs, again including VHF/FM and SATCOM, will also deploy portable or transportable assets to local personnel immediately before an emergency/crisis, as well as during and after, as circumstances change and requirements evolve with them.

All these efforts intend to ensure that FAA decision-makers and Senior Management at FAA HQ have the means to communicate effectively with all FAA personnel in all facilities and other important Government officials in case of national emergency or crisis, whether artificial or natural, that would disrupt existing routine communication systems such as Public Switched Telephone Network (PSTN) service. When everyday 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 that FAA decision-makers have command and control communications during times of crisis.

1.3 Scope of Work

The PMO C3 Program Office manages programs that comply with National Security mandates and public safety demands. These programs enable the FAA to provide communications services that meet the requirements for the connectivity, redundancy, inter-agency interoperability, storability, and hardness needed to support routine and emergency operations. The Contractor shall provide technical, business, administrative, and management support and shall perform at unclassified, Secret, and Top Secret/Sensitive levels. Compartmented Information (TS/SCI) levels for programs, projects, and systems are defined under this SOW. The Contractor shall provide planning and engineering support and the communications infrastructure to support AXE functions, including WOCC operations, emergency planning, special activities, law enforcement coordination, and national security and intelligence coordination. The RCOM C3-associated programs, projects, systems, and facilities include:

1.3.1 Emergency Backup of Networks

· Emergency Response and Continuity Facilities

· Washington Operations Center Complex (WOCC)

· Emergency Operations Center (EOC)

· Primary Alternate Facility (PAF)

· Communications Support Team (CST)

1.3.2 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)

1.3.3 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)

1.3.4 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 Federal Policies, Directives and Guidance The Contractor shall ensure its operations comply with the following policies and guidance. The Contractor shall also comply with any updates to these policies and guidance during the contract's life.

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

2. Executive Order 13618, Assignment of National Security and Emergency

3. Preparedness Communications Functions (supersedes EO 12472)

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

5. Office of Science and Technology/Office of Management and Budget (OSTP/OMB) Directive 16-1 (Minimum Requirements for Executive Branch Continuity Communications)

6. OMB A-130

7. Intelligence Community Directive 705, Sensitive Compartmented Information Facilities (SCIF)

8. National Emergency Communications Plan

9. Federal Information Security Management Act (FISMA) and FedRAMP Guidance and Process

10. National Security Policy Directive-47 (NSPD-47)/Homeland Security Policy Directive16 (HSPD-16) (Aviation Security Policy)

11. Federal Continuity Directive -1 (FCD-1)

12. Federal Continuity Directive -2 (FCD-2)

13. National Strategy for Aviation Security (NSAS)

14. National Institute of Standards and Technology (NIST) documentation and standards

15. National Response Framework of 2008. The Fourth Edition was released in 2019

16. National Incident Management System

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

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

19. FAA Order 1110.282, Office of Security and Investigations

20. FAA Order 1370.82 (Information Systems Security Program)

21. FAA Order 1370.121, FAA Information Security and Privacy Program and Policy

22. FAA Order 1600.2E, Protection of Classified Information

23. FAA Order 1600.6E, FAA Facility Security Policy

24. FAA Order 1600.38F, Employee and Other Internal Investigations

25. FAA Order 1600.69C, FAA Facility Security Management Program

26. FAA Order 1600.75, Protection of Sensitive Unclassified Information

27. FAA Order 1600.76, SCI Program

28. FAA Order 1650.20A, Support for Sensitive National Defense and Law Enforcement Operations – redacted

29. FAA Order 1700.6C, FAA Branding Policy

30. FAA Order 1900.1G, FAA Emergency Operations Plan

31. FAA Order 1910.K, FAA Continuity Program

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

33. FAA Order 1990.1, FAA National Command and Control System

34. FAA Crisis Management Handbook

35. ATO Notice JO 1100.326, Air Traffic Organization

36. ATO Order 7610.4T, Special Operations

37. C3 EON Change Control processes and procedures

38. FAA Crisis Management Handbook

39. DoD Information Assurance Certification and Accreditation Process (DIACAP)

40. Emergency Notification System (ENS) Governance Plan

41. FAA Acquisition Management Policy: http://fast.faa.gov/AMP_TOC.cfm

42. FAA Acquisition Toolset: http://fast.faa.gov/

43. ID Badge Online Application: https://my.faa.gov/org/linebusiness/ash/programs/id_badge/instructionsapplication

44. Contractor & Industrial Security Program: https://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentID/1040448

45. Orders and Notices:

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

47. Finance Standard Operating Procedures (SOP): https://my.faa.gov/org/staffoffices/afn/finance/sop

48. Forms: https://www.faa.gov/forms

3 Task Requirements The Contractor shall perform all tasks as described in this section.

3.1 Task 1 – Program Management Support

The Contractor shall provide program management support. The Contractor’s Program Manager (PM) shall formulate, plan, organize, and execute contract-related activities that meet the goals and objectives of the Program. The Contractor Program Manager is responsible for verifying that identified tasks are performed completely, continuously, efficiently, accurately, on time, on budget, and in compliance with the requirements. The Contractor shall participate as a member of a government-led team when directed by the Contracting Officer’s Representative (COR).

3.1.1.2 Kick-Off Meeting

The Contractor shall conduct a Kick-Off meeting between the Contractor and all stakeholders identified by the COR to review SOW requirements and to demonstrate that the Contractor fully comprehends 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 kickoff meeting. The Contractor shall provide meeting minutes (refer to section 3.1.10) to the COR within five (5) business days after the kickoff meeting.

3.1.2 Project Plans

The Contractor shall assist with creating and maintaining project plans which document the standard operating procedure (SOP) for each “Sub Program” in the list below to be contained in a Master Project Plan (MPP) that describes the specific Program Management systems and quality control processes to be implemented to ensure that every Sub Program action/requirement is accomplished exactly as required in this SOW. Each project plan shall identify which positions from the Task requirements staffing plan (refer to 3.1.3) support each activity on the project plan and which position leads each activity. The project plan shall also include a process map for each Sub Program and the staffing plan the Contractor has implemented to ensure its recruiting, onboarding, training, engagement, retention and adequate reach-back capacity results in the full staffing of all required positions at minimum vacancy rates. The Contractor shall keep these various project plans in an electronic book of SOPs organized by Sub-Program. Project plans shall be updated as changes occur to ensure they reflect the exact positions (staff), procedures, systems and processes that are in place to ensure compliance.

Sub-Programs:

1. Very High Frequency/Frequency Modulation (VHF/FM – Task 3.2)

2. Satellite Communications (SATCOM – Task 3.2)

3. Microwave Communications Network (P1 – Task 3.2)

4. High Frequency/Single Sideband (HF/SSB – Task 3.2)

5. Communications Support Team (CST – Task 3.3)

6. Information Technology (IT – Task 3.4)

7. Emergency Operations Network (EON – Task 3.5)

8. National Security Communications (Task 3.6)

9. Emergency Planning and Exercise (Task 3.7)

10. Intelligence Operations (Task 3.8)

11. Facilities Management and Maintenance (Task 3.9)

12. Emergency Notification System (ENS – Task 3.10)

13. Law Enforcement Assistance Program (LEAP – Task 3.11)

14. Regulatory Investigations Division (Task 3.11)

15. Washington Operations Center (WOC – Task 3.12)

3.1.3 Staffing Plans

The Contractor shall create and implement a Staffing Plan in Excel format which confirms that its recruiting, onboarding, training, engagement, retention and adequate reach-back capacity results in the full staffing of all required positions at minimum vacancy rates. For all 13 Tasks, including each of the sub-programs listed in 3.1.2 above, a Master Staffing Plan that integrates each of the requirements of this SOW shall be developed and maintained. For each position supporting a requirement, the staffing plan shall identify, at a minimum, the following:

1. Roles and responsibilities delegated to the position

2. Any other requirements supported by the position

3. The name of the position’s incumbent

4. If vacant, an ongoing record of the length of time the position has been vacant

The Contractor shall submit its current Staffing Plan to the COR monthly with the Monthly Report (refer to 3.1.6)

The Contractor PM shall support and assist with managing the RCOM Project Plan (refer to 3.1.2). The Contractor shall keep the Project Plan current and updated using Microsoft Project.

3.1.4 Risks to Projects and Work

The PMO and the Contractor shall work in partnership to identify risks to projects and work and to mitigate risks according to the FAA guidance. This includes identifying emerging risks, monitoring known risks, and reducing the effects of risk factors to acceptable levels. At a minimum, the Contractor shall, for each risk to a project,

1. Provide an analysis of the risk

2. Develop and execute a mitigation strategy

3. Monitor results and adjust the mitigation strategy until the risk is reduced to acceptable levels.

3.1.5 Weekly Status Reports

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

1. Status tracking to provide updates on Contractor staffing and vacancy issues

2. Clearance issues

3. Information on Contractor personnel working off site (away from the WOCC), specifically those who are working at a temporary alternate work location

4. Approaching project deadlines, such as end-of-year requirements

5. Identification of any risks and an assessment of those risks

6. Updates shall include a risk assessment, whether the schedule is on track, and whether additional resources are needed

3.1.6 Monthly Status Reports/Monthly Quality and Performance Report The Contractor shall provide Monthly Status Reports (MSRs). The Contractor shall provide an MSR that documents the previous month's activities and identifies all planned activities for the following month. The reports shall be delivered to the COR on 10th day of each month (or on the nearest business day thereto) and shall include, at a minimum, the following information:

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

2. Current Staffing Plan as described in 3.1.3 above, including Hours expended by task, labor category, and personnel (in Excel format)

3. Pending Staffing Status.

4. Pending Security Clearance Status.

5. 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 identifying risk areas (refer to 3.1.4), determining the status of outstanding risks associated with individual deliverables or tasks, and recommended remedial actions

6. Any additional information pertinent to the government’s administration of the performance of this effort, or as directed by the COR

7. Approved travel during the reporting period and travel planned for the next period.

8. Scheduled deliverables and planned delivery dates.

9. Actual delivery dates

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

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

12. Risks and Issues Review and Status

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

14. The Contractor shall submit the monthly quality and performance reports for approval ten (10) business days before the monthly status meetings.

3.1.7 Monthly Financial Reports

The Contractor shall provide Monthly Financial Reports on the 10th day of each month. Each report shall include the following for each Task:

1. CLINs used during the month.

2. Cost/hours funded or apportioned by CLIN.

3. Cost/hours used by CLIN.

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

5. Projected date when funds are exhausted.

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

7. Funds/hours remaining by CLIN.

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

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

3.1.8 Program Management Review (PMR)

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

1. Contract/Task Order Information.

2. Financial Summary.

3. Status of Deliverables.

4. Task Order Staffing Summary.

5. Performance Summary.

6. Accomplishments include corrective actions taken and risks resolved (refer to 3.1.4).

7. Risks, Issues, and Opportunities (RIO).

8. Action Item Summary.

9. Subcontractor Status, if any.

10. Quad Charts.

11. Backup Information.

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

3.1.9 Schedules

The Contractor shall assist in creating and maintaining a schedule for each sub-program identified in section 3.1.2 and the RCOM C3 Integrated Master Schedule (IMS) that integrates the information from each sub-program schedule. While tasks are planned and managed jointly, the RCOM C3 PMO will maintain the IMS throughout the program's life cycle. The schedule for each sub-program shall integrate the activities from the IMS with the corresponding sub-program program plan, the required resources from the corresponding sub-program staffing plan (refer to 3.1.3), the results/deliverables to be produced, and any risks (refer to 3.1.4) identified by stakeholders.

The Contractor shall fully staff and support each corresponding sub-program and document same in the Staffing Plan (refer to 3.1.3) for each task area.

The RCOM C3 PMO will work with the relevant program manager to enter information on all projects impacting a NAS facility (e.g., VHFFM, SATCOM, Secure Communications) into the FAA’s Corporate Work Plan (CWP) on projects designated in the PMO schedule.

C3 and the Contractor shall work in partnership to identify risks and mitigate risks according to 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.10 Meeting Minutes/Trip Reports

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

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

1. Remove unserviceable items that are not necessary to the performance of the contract from the GFE list.

2. Replace an unserviceable item necessary to contract performance at the Contractor’s sole expense (in the event of negligence or unusual wear and tear).

3. Replace an unserviceable item necessary to contract performance at the government’s sole expense (in the event of normal wear and tear)

If any issued GFE is no longer required during the execution of the Task Order, it shall be returned within ten (10) calendar days of the end of its use, and the return to the Government shall be documented as part of the Contractor’s inventory management. Once an unserviceable item has been replaced, such notice shall be documented in the ongoing GFE Inventory report. Comment by Pokrovnichka, Inna I (FAA): Is “Property” the same as GFE or different?

If they are the same use “GFE” for consistency purposes.

If “Property” is different from GFE then define property. Comment by Pokrovnichka, Inna I (FAA): Make clear to whom the property is being returned. If it’s the government state, “returned to the Government”. Comment by Pokrovnichka, Inna I (FAA): State is it’s calendar or business days.

3.1.12 Phase-in and Phase-Out Inventories

3.1.12.1 Phase-In Transition Plan and Period

To be initiated 30 calendar days before the commencement of a new contract. Comment by Pokrovnichka, Inna I (FAA): State if it’s calendar or business days The Contractor who has been awarded the contract (successor) shall submit a proposed Phase-in Plan twenty (20) business days after the contract award that describes actions necessary to successfully transition operational responsibilities from the incumbent Contractor to itself. Commencing within thirty (30) calendar days of the commencement of the Base Period, the successor shall participate in the incumbent’s Phase-Out Inventory procedure.

The successor’s participation in an incumbent Contractor’s “Phase-Out Inventory” procedure shall be to conduct its “Phase-In Inventory simultaneously” in accordance with the FAA Contractor’s Guide for Control of Government Property.

The incumbent shall provide the successor with a complete copy of its current, up-to-date GFE Inventory file with all attachments. The successor shall review the incumbent’s Inventory of Government-Furnished Equipment (GFE) with the incumbent as it completes its “Phase-Out Inventory of Government Furnished Equipment,” annotating any inaccuracy or item of inventory needed to execute the Contract that is not included in the documentation provided for later discussion with the COR. Upon completing this important exercise, the successor shall know what is contained in the GFE Inventory, where each item is located, and how to access information necessary to perform contract requirements, such as passwords, etc.

A Government representative designated by the COR will determine the accuracy of the Phase-Out Inventory report and confirm all Inventory changes during the contract term. Resolving all inconsistencies between the incumbent’s “Phase-In” and “Phase-Out” Inventory shall be at the government’s discretion. The Contracting Officer shall review all findings and determine an incumbent’s responsibility for any disparity. If the incumbent is determined responsible due to its failure to notify the government of a change in inventory, the incumbent shall correct the discrepancy before performance expiration, or the repair cost shall be deducted from the final payment.

The final thirty (30) calendar days of the contract will constitute the “Phase-Out Period.” During this period, the incoming Contractor (successor) workforce personnel shall be allowed to observe the outgoing Contractor's operations and performance methods. This allows for the orderly transition of facilities, equipment, and records and will verify and ensure the continuity of operations.

During this period, the incumbent Contractor shall continue to perform all contract requirements and shall not transfer such responsibility to the successor before the end of the last performance period. The incumbent Contractor shall fully cooperate with the successor and the Government so as not to default on any contract requirement or duty. The Contractor shall not disrupt or adversely impact its services or re-deploy its employees prior to the final day of performance. The Contractor is responsible to ensure a smooth and orderly transfer of responsibility to the successor.

3.1.12.3 Phase-Out Execution

Thirty (30) calendar days before the period of performance ends, the Contractor shall submit the following to the COR: Comment by Pokrovnichka, Inna I (FAA): State if it’s calendar or business days

1. All documentation as of the most recent revision.

2. A final financial report.

3. A final status report, including a projection of activities for the remainder of the contract term.

4. A copy of the phase-out inventory.

5. The Contractor shall schedule (coordinating date/time with the COR) and attend a closeout meeting with the FAA (details and participants to be determined by the FAA).

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

Upon completion of the final day of performance, the incumbent shall return the same property or property equal in type, kind, quality, and quantity of items as initially furnished by the Government and accepted by the Contractor. Government property shall be in the same condition as when furnished initially, less normal wear and tear.

3.2 Task 2 - C3 Communications Systems Engineering and Integration Support

C3 selects and fulfills the requirements for secure and redundant communications systems 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 (refer to 3.9.2) within the FAA community, Contractor or manufacturer maintenance, or C3 engineering support to troubleshoot problems, replace parts, and schedule preventive and corrective maintenance.

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

1. Very High Frequency/Frequency Modulation Radio (VHF/FM)

2. Satellite Communications (SATCOM)

3. Digital Microwave Communications (P1) Network

4. High Frequency/Single Sideband Radio (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 crises such as hijacking, natural disasters, terrorist acts, accident 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 the hardness needed to support routine and emergency operations. The Contractor shall maintain and operate systems consistent with FAA requirements for connectivity, redundancy, agency interoperability, restorability, resiliency, and hardness needed to support routine and emergency operations (refer to Section 2 above). This support includes the following areas: Comment by Pokrovnichka, Inna I (FAA): The reader needs to know where they can find the FAA requirements with which they are required to comply.

3.2.1 Requirements Analysis Support

The PMO C3 Division Manager AXE-400 is responsible for determining mission needs, developing operational requirements that address these needs, and then strategically planning and executing projects to meet these requirements—all aimed at delivering and sustaining secure and redundant communications systems that satisfy FAA mission needs.

The Contractor shall review and evaluate customer and/or system functional and technical requirements to assist in developing and maintaining the PMO’s project plans (refer to 3.1.2), requirements documents, cost/benefit analyses, work breakdown schedules (refer to 3.1.9), performance goals, processes and procedures, risk analyses (refer to 3.1.4), and quality assurance measurements. The Contractor shall also support the PMO’s requirements traceability matrix, which provides bidirectional performance traceability 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 shall analyze technical requirements to support solution development. In addition, the Contractor shall attend Technical Interchange Meetings (TIMS), prepare engineering diagrams, drawings, and data flow diagrams, conduct propagation studies, redline drawings, disposition plans, and white papers, and coordinate technical issues with the FAA. The Contractor shall also prepare detailed timelines and schedules (refer to 3.1.9) for assigned tasks and provide quality assurance of all work performed with third-party Contractors/vendors (if present).

3.2.3 Site Surveys, Evaluations, and Preparation Support

The Contractor shall conduct site surveys and generate site survey reports for all RCOM C3 AXE-400 PMO-supported systems. These site survey reports allow the FAA to help maintain systems or resolve issues at FAA facilities before hardware installation. Site survey information will include all coordination with facility personnel, a preliminary installation design, and identification of all obstacles that could interfere with the planned implementation. The Contractor site survey reports shall, at a minimum, address power requirements, HVAC requirements, floor plans, rack space, cable paths, facility design, local contact information (points of contact), and use constraints.

3.2.4 Program and Technical Documentation Support

The Contractor shall assist at all levels during the development of all required technical documentation, including but not 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 shall include the resolution of all comments dealing with specific NCPs.

3.2.5 System Safety Management

The RCOM C2 PMO shall 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 (SRMGSA).

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

In the SSPP, the Contractor shall 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

The RCOM C3 PMO staff and Contractors perform site installation and checkout with the assistance and support of local System Support Center (SSC) personnel, as needed. During these activities, all functionality, operability, and training are completed.

The Contractor shall participate and assist both the FAA and/or other vendors in installing all RCOM C3-related communications equipment (and is wholly responsible for all activities or collaborating with third parties). This includes the planning, physical installation of hardware and software, configuration, and the testing and cutover exercises required for system validation/acceptance for cutover to Full Operational Capability (FOC). As described in section 3.2.6.1, the Contractor shall have two (2) Certified and Authorized Climbers.

3.2.6.1 Two (2) Certified and Authorized Climber Requirements The Contractor shall provide at least two certified Authorized Climbers to support installation and troubleshooting on FAA towers. Training shall meet the following safety standards (as they pertain to Authorized Climber/Rescuer): OSHA CFR 1910.268, ANSI Z359, ANSI Z490, and NATE Climber/Rescuer Training Standard. These two certified Authorized Climbers shall also meet the following requirements:

1. Shall meet all CTS Industry Standards

2. Professional Electronics Background

3. 50% overnight travel

4. Experience in Diagnosing, Repairing, Programming, and Installing RF Equipment

5. Possesses Complex Understanding of Two-Way Radio Theory and RF Propagation Characteristics at Various Frequency Bands

6. Familiar With RF Design and Engineering

7. Proficient Operating Test Equipment (Communications Service Monitors, Watt meters, TDRs, FDRs, Multimeters)

8. IP Networking Experience

9. Data Cabling Experience a Plus (CAT 5/6, Coaxial, Fiber, Support Devices, etc.)

10. Competent Operating Basic Hand and Power Tools

11. Able to Lift 50 lbs. and Work in Unusual and Sometimes Difficult Positions (e.g., Climbing Ladders and Scaffolding, Crawl Spaces, High-

12. Proficient in MS Office Suite (Outlook, Word, Excel)

3.2.6.2 The following are the necessary skills and experiences the two certified authorized climbers shall possess:

1. Experience Reading Blueprints and/or Logic Diagrams

2. OSHA Safety Training and Low Voltage Certifications

3. Distributed Antenna System (DAS) Installation

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

1. Grounding systems

2. Power systems

3. VHF-FM radios, repeaters, and consolettes

4. VHF-FM antennas

5. Satellite Communications Systems

6. Microwave antenna towers and antennas

7. Microwave radio systems

8. Microwave waveguides

9. Dehydrators

10. High-frequency radio equipment

11. High-frequency antennas

3.2.7 Testing Support

All RCOM C3 systems and equipment are currently deployed and in service, and technical refresh projects are designed to replace aging equipment with the same form, fit, and function as commercially available COTS equipment without modification. The RCOM C3 test program comprises a combination of voluntary and prescribed testing to ensure RCOM C3 facilities and systems are always operational and ready. The Contractor shall assist the PMO C3 Program Office in testing 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 are 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 Contractor shall assist the RCOM C3 PMO Program Office in testing all installed hardware, software, and systems. The Contractor shall provide a Test Plan for each installation. The Test Plan shall 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 shall include test and verification procedures to verify proper installation and operation in the installed environment with Stakeholder approval. The COR or their designee shall approve the test plan before testing begins. Testing will validate that all installed hardware works as intended. The Contractor shall coordinate with William J. Hughes Technical Center and other FAA entities to perform acceptance testing, assisting with vendor/subcontractor oversight as needed. The Contractor shall also assist and/or complete spectrum approval and licensing documentation.

3.2.8 Preventive Maintenance and Repairs Support

The Contractor shall provide the RCOM C3 PMO with maintenance support for all installed systems following acceptance. When directed by the COR or their designee, the Contractor shall 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) requires 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 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 developing continuity plans and programs for the Federal executive branch, including continuity communications.

The Contractor shall assist the PMO with the continuous technical refresh of the NRCS to ensure the system is ready for use in a crisis. The VHF mission 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 regularly in areas where cellular phone coverage is spotty or unavailable.

3.2.10 Satellite Communications Engineering Support

The FAA continually requires satellite communications capabilities. Previously known as the Satellite Telephone Emergency Network (STEN), it is now more commonly known as the Satellite Communications (SATCOM) program. The original network was implemented in 1995, refreshed once in 2004, and undergoing a second refresh in 2021-2024/5. It also 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 emergency response actions, including re-establishing the NAS. The FSEP Facility Type is “SACOM.”

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 shall maintain the operational suitability of all deployed Satellite telephones. As more installations are added to the field or existing installations are refreshed, the Contractor shall provide deployment support by conducting site surveys (refer to 3.2.3), installing Subscriber Identity Module (SIM) cards, and tracking locations, usage, and logistical concerns in the program office inventory system.

The Contractor shall 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 integral to the agency’s emergency communication system and must remain operational 24 hours a day, 365 days a year. Once an issue has been reported, the Contractor shall immediately initiate technical support, including deploying replacement equipment/parts, within two (2) calendar days.

The Contractor shall support bi-monthly SATCOM exercises. These exercises shall be performed bi-monthly with the SATCOM program manager to verify the proper operation of the SATCOM system. All performance issues will be addressed before the next quarterly test.

The Contractor shall be capable of being an active, contributing participant in any potential future proof of concept projects, which may be designed to determine the 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, 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, 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.

The P1 network is a point-to-point, semi-mesh microwave radio network. It provides an alternate data transmission path for mission-essential communications traffic if the FAA Telecommunications Infrastructure (FTI) or FAA Enterprise Network Services (FENS) has experienced an interruption in service. The P1 network currently consists of 13 sites and 14 microwave links. The network is the alternative data transport infrastructure between the FAA’s crisis management/disaster recovery locations (Headquarters, Emergency Operations Center, and Primary Alternate Facility).