Atch 1_PWS LMR Ethernet Backhaul.pdf

Performance Work Statement (PWS) for Vandenberg SFB ELMR Ethernet Migration

1.0 Introduction

This Performance Work Statement (PWS) defines the requirements for migrating the Vandenberg Space Force Base (VSFB) Enhanced Land Mobile Radio (ELMR) backhaul network from Time-Division Multiplexing (TDM) circuits to Ethernet, ensuring compliance with the Department of Defense Chief Information Officer DAF/CIO mandate by Aug 2025.

This migration modernizes the ELMR backhaul to the Peterson AFB and Barksdale AFB cores, improving reliability, security, and ensuring seamless integration with existing and future ASTRO systems.

2.0 Objectives

The objective is to transition VSFB's ELMR backhaul network to a Layer 3 Ethernet infrastructure, meeting DoD and DISA requirements and ensuring compatibility with the USLA ELMR Core. This includes upgrading customer edge/Defense Information Systems Agency (DISA) boundary devices, implementing enterprise-grade routers and switches at all remote sites, and ensuring seamless integration with existing ASTRO systems.

3.0 Scope of Work

The Contractor shall provide all design, labor, materials, equipment, and supervision necessary to complete the following tasks:

3.1 Equipment Provisioning and Installation:

• Provide and install one (1) Firewall Router and associated mounting equipment, modules, SFP, and power cabling (TAA Compliant) at the VSFB Data Center Operation (DCO).

• Provide and install four (4) Ethernet Switches and associated mounting equipment, modules, SFP, and power cabling (TAA Compliant) one at each remote site (Radio Frequency (RF), Dispatch, Network Management (NM)).

• Provide fiber conversion if required at each remote site.

3.2 Network Configuration and Integration:

• Configure routers and switches according to IMSC LMR Backhaul design standards and DISA requirements for Layer 3 Ethernet. Support Routed, VPLS, EVPN, and MPLS deployments as needed. Accommodate DISA-mandated Multiprotocol BGP (MP-BGP) with an MX104 or suitable replacement. Support single, redundant, and aggregated DISA circuits.

Implement Layer 2/Layer 3 pathing for ASTRO25 infrastructure, including EVPN, VPLS, and Pseudo-Wire services. Utilize MPLS Traffic Engineering and ensure path diversity.

• Configure MPLS using Resource Reservation Protocol - Traffic Engineering (RSVP-TE). Enable Constraint-Shortest Path First (CSPF) on all core switch processors (CSPs). Define at least one primary Label Switched Path (LSP) per connection. Implement LSP protection using Fast Reroute (FRR) and secondary paths. Configure BGP as the default for all Layer 3 links and route exchange. Use OSPF for interoperability with existing Global Grid Manager (GGM) Layer 3 deployments.

• Implement a three-layer QoS scheme using DSCP markings. Police/shape ingress traffic on all Provider Edge (PE) routers to prevent queue overrun.

Shape egress queues to enforce per-hop behavior. Rewrite QoS headers (MPLS EXP, DSCP, IEEE 802.1 VLAN tags) on all PE egress traffic.

• Integrate the new Ethernet backhaul with the existing ASTRO system.

Configure edge equipment for monitoring via the Unified Event Manager (UEM) using MIBs. Ensure compliance with ASTRO cybersecurity requirements, including STIGs and protocol encryption.

3.3 Testing and Documentation:

• The contractor shall identify and provide approved industry and OEM procedures that outline, sequence, and indicate qualifications for system acceptance, such as 24-hour burn-in, etc. The test procedures will be provided to the Government for review and approval prior to the beginning of any testing. The testing will ensure the system is fully functional, meets the intended use per this PWS and is installed by any required OEM Military Unique Deployment Guides (MUDG) to provide military unique features.

Military unique features, to include Muli-Level Precedence and Preemption, shall be incorporated into the test procedures. The approved test procedures will be used as a final completion checklist at the date of the installation.

Contractor shall provide an Installation Test Acceptance Plan

• Conduct comprehensive testing with DISA and LMR Cores at Peterson AFB and Barksdale AFB, including Y.1564 Ethernet certification testing. Provide "as-installed" documentation. As installed documentation refers to documents that explain the capabilities of computer software or provide instructions for using the software. It includes owner's manuals, user's manuals, installation instructions, and operating instructions. Tailored documentation, such as an Installation Guide and a Deployment Guide, is crucial for supporting users and deployment teams.

3.4 Cybersecurity Support:

• Maintain the system's Authority to Operate (ATO). Provide support to perform Nessus vulnerability scans and annual STIG audits. Update cybersecurity documentation, including Visio diagrams, hardware/software lists, ports, protocols, and services (PPS).

3.5 Warranty and Sustainment: Provide a one-year warranty and enhanced support services.

4.0 Deliverables

• Installed and configured equipment data sheets

• Test results and as-installed documentation rack elevations

• Updated topology diagrams

• Cybersecurity reports (monthly vulnerability scans, annual STIG audits, updated documentation)

5.0 Performance Standards

• Network compliant with DoD and DISA requirements, including specified performance metrics for bandwidth (100Mbps core to remote, 10Mbps site to core), jitter (10ms point-to-point, 6.7ms meshed), dropped packets (<0.01%), and latency (<374ms call setup time).

• MPLS and dynamic routing protocols configured as specified by DISA.

• Three-layer QoS scheme implemented and validated.

• Cybersecurity requirements are met, including STIG compliance and protocol encryption.

• All backhaul devices are monitored through UEM.

6.0 Period of Performance:

• June 25 to Aug 25

7.0 Place of Performance:

• Vandenberg Space Force Base, CA

8.0 Government-Furnished Equipment/Information:

• Rack space, site preparation, network connectivity (fiber), storage, classroom, DISA Layer 3 MPLS circuit, circuit information.

9.0 Security Requirements:

• Compliance with all applicable security requirements guides for the Department of Defense information technology systems.

10.0 Acceptance Criteria:

• Successful completion of testing and validation procedures demonstrating compliance with all LMR PMO, Motorola and LMR managers requirements.

• An assigned Government site POC will authorize site acceptance. Site acceptance shall conclude upon successful installation, commissioning, connecting and testing of the system, and receipt of all deliverables. Before site acceptance the system shall operate without an outage-causing failure for a minimum of seven (7) consecutive days prior to Government acceptance. AFTO Form 747 shall be used to document this completion. The AFTO Form 747 shall be forwarded through COR for approval prior to base signature. The Contracting Officer Representative (COR) will be the final signatory on the site acceptance form or AFTO Form 747. The Contractor shall notify the Government upon completion of all delivery order tasks. The Government reserves the right to refuse final acceptance until all discrepancies have been resolved to the satisfaction of the Government. The Contractor shall prepare a project discrepancy list, report detected issues during meetings and track all discrepancies until resolved. The Government will review and monitor all discrepancies and deliverables. The discrepancy list shall include any problem(s) detected and identified during the upgrade. The Contractor shall retain a history of discrepancies. Problems identified during the upgrade period shall be documented, provided to the Government, and corrected prior to final acceptance.