2. MECS2 PWS.pdf

USMC Enterprise Commercial Satellite Services (MECS2) Contract

Enclosure XX, PWS Page 1 of 30 Pages

Performance Work Statement (PWS)

FOR

United States Marine Corps (USMC) Enterprise Commercial Satellite Services (MECS2)

AT

[PERFORMANCE LOCATION]

18 January 2024 Version

1.1

DRAFT

Controlled by: Commercial Satellite Communications Office (CSCO) Distribution: NONE

POC: TBD

Page 2 of 30 Pages

SECTION I – 1.0 Description of Services SECTION II – 2.0 Technical Performance Requirements SECTION III – 3.0 Service Summary SECTION IV – 4.0 Deliverables SECTION V – 5.0 Government Furnished Property, Equipment, Material, Information, Or Services SECTION VI – 6.0 Security Requirements SECTION VII – 7.0 General / Additional Information

Page 3 of 30 Pages

SECTION I – 1.0 Description of Services

1.1 General

The USMC has a global mission set that requires the ability to rapidly respond to changes in defense postures across all combatant command regions. In order to provide the necessary command and control and secure communications requirements, the USMC must be able to flexibly alter coverage and technical support. In support of this mission, the USMC established the Marine Corps Centralized Commercial Bandwidth (MC3B) initiative to provide Conti-nental United States (CONUS) and Outside the Continental United States (OCONUS) Commercial Satellite Com-munications (COMSATCOM) capacity and network access to meet USMC commercial Beyond Line of Sight (BLOS) requirements. Historically, the USMC leveraged Fixed Satellite Service (FSS) Ku-band transponder capac-ity in Geostationary Orbit (GEO) using Time Division Multiple Access (TDMA) and Frequency Division Multiple Access (FDMA) methods to support USMC Satellite terminal BLOS hub-spoke architectures, BLOS Point-to-Point (P2P) links and BLOS access to intra-theater, tactical communications gateways, or Department of Defense (DoD) fixed, regional teleport sites, and regional hub nodes.

The USMC requires the ability to obtain CONUS and OCONUS COMSATCOM transponder capacity plus the op-tion to purchase or lease Commercial SATCOM as a Solution (Managed Services) that provide managed and inte-grated, diverse, multi-orbit, multi-spectrum transport services that connect commercial telecommunications and IT infrastructure directly to the Marine Corps Enterprise Network (MCEN). This combined approach ultimately pro-vides the required transport to support the consumption rates and low latency requirements that underpin the Marine Corps’ MCEN 2030 data-centric environment.

1.2 Scope

This requirement is for transponded bandwidth capacity and end to end managed services leveraging all available satellite transmission frequency bands, Cellular services, and access methods to lease or purchase options for multi-ple service models and Managed Services solutions to achieve global coverage in five (5) regions in multi-orbit and multi-band; deliver high capacity services and mobile spread spectrum services; provide Worldwide Internet Proto-col (IP) backhaul from commercial gateways to the MCEN through Government Entry Points (GEP) and to the De-partment of Defense Information Network (DoDIN), to include Program Management support, bandwidth manage-ment and analysis tools, and access to provided SATCOM network monitoring tools via non-secure and secure net-works.

The Government may require the ability to port bandwidth from one pool to another on very short notice to meet the needs of emergency and contingency operations.

The Government requires the ability to place orders for USMC Headquarters (HQ) Information, Command, Control, Communications and Computers (IC4) as well as placing direct orders for support of the individual Marine Expedi-tionary Force (MEF) commands providing global support for the USMC mission.

The Government may require the option of supporting short-term contingency / emergency needs of other United States military services when their mission is interfacing with USMC operations via orders directly from that sup-porting military service. Joint support orders may be placed as well.

Additional services to include, but not limited to equipment purchase or lease, training and logistics for equipment, bandwidth re-grooming, network monitoring, tech refresh, and emerging technologies support.

1.3 Background

The USMC has a global mission set that requires the ability to rapidly respond to changes in defense postures across all combatant command regions. Historically, the USMC has accomplished its global mission via a singular pool of transponded capacity provided by geosynchronous satellites. Due to changing threat vectors and commercial innova-tions, the USMC is modernizing its response and sustainment operations. The USMC maintains the requirement for a robust and resilient terrestrial network for the backhaul of data, however the satellite transmission architecture

Page 4 of 30 Pages needs can no longer be supported by legacy standards. Modernization of operations will allow the USMC to remain responsive, flexible, and efficient in their data requirements as they are in all other aspects of operations.

SECTION II – 2.0 Technical Performance Requirements

The USMC MECS2 contract is to provide access to multi-orbit commercial satellite communications in all commer-cially available frequency bands via on orbit and terrestrial resources, day-to-day resource management that has worldwide coverage and is available twenty-four hours a day seven days a week.

The USMC has a global mission set that requires the ability to rapidly respond to changes in defense postures across all combatant command regions. In order to provide the necessary command and control and secure communications requirements, the USMC must be able to flexibly alter coverage and technical support. The Government may require the ability to port bandwidth from one pool to another on very short notice to meet the needs of emergency and con-tingency operations. The Government may require the lease or purchase of terminals and/or terminal equipment to meet emergent or contingency operational needs. The Government may require surge support in any commercially available orbit or frequency band during the base or any option period, and surge modifications will be within the technical specifications of the task order and provide increased service support for the defined task areas of this PWS. This support may be provided via traditional transponded capacity services or via managed services.

All performance requirements (tasks) written below are critical to the requested services. The performance require-ments include the following task(s):

2.1 Task 1 – Transponded Bandwidth

2.1.1 Subtask 1.1 – Transponded Space Segment Coverage: Space segment shall be capable of providing global landmass coverage (within LAT 72ºN to 62ºS) in the following four regions: Americas (Longitude 160ºW – 40ºW);

Western Pacific (WPAC) (Longitude 80ºE - 160ºW); Europe Africa (EURAF) (Longitude 40ºW - 80ºE); and South-west Asia (30ºE - 75ºE). A fifth region identified as the Polar Region (north of 72° N) may require optional service support over the life of the contract. When support is required, this will be specified at the task order level. Addi-tional sub-regions with each of the five regions may be defined at the order level. Meeting the coverage area is de-fined as closing the satellite link for all terminals operating within the defined coverage area. Provide the technical and functional activities as required for integration of all tasks specified within this PWS.

2.1.1.1 Americas Region. Coverage shall include at a minimum, the continental United States, Central and South America, Hawaii (required coverage over entire state of Hawaii), and Alaska to include Bering Seas and Aleutian Islands.

2.1.1.2 WPAC Region. Coverage shall include at a minimum, Thailand, Japan (including Okinawa), Marianas Is-lands (Guam, Saipan, and Tinian), Solomon Islands, Micronesia Islands (Chuuk Lagoon), Palau, Korean Peninsula, Philippines, India, Nepal, and Australia. Any satellite(s) considered for use in the WPAC pool providing coverage to Japan must have landing rights in operational locations in Japan/Okinawa.

2.1.1.3 EURAF Region. Coverage shall include at a minimum, Democratic Republic of Congo, Djibouti, Senegal, Tunisia, Germany, Poland, Italy, Kosovo, Estonia, Lithuania, Latvia, Ukraine, Libya, Norway, Sweden, France, Fin-land, Czech Republic, Slovakia, Austria, Hungary, Albania, Serbia, Croatia, Greece, Turkey, Somalia, Spain, and United Kingdom.

2.1.1.4 SWA Region. Coverage shall include at a minimum, Iraq, Afghanistan, Bahrain, Egypt, Pakistan, United Arab Emirates, Israel, Jordan, Kuwait, Oman, Qatar, and Yemen.

2.1.1.5 Polar Region. Polar region service may be required over the life of the contract. When Polar support is re-quired, the location and type of support will be specified at the task order level.

2.1.2 Subtask 1.2 – Required Space Segment Capacity

Page 5 of 30 Pages

Space segment capacity shall be provided to the regions defined in Subtask 2.1.1. Multiple satellites and transpond-ers may be provided within region; space segment capacity on any given transponder shall be contiguous.

2.1.3 Subtask 1.3 – Required Space Segment Quality

Government Furnished Equipment (GFE) and technical parameters to be used for link budgets are contained in PWS Attachment A, Technical Specification. Link budgets shall be prepared based on a worst-case scenario location. The worst-case scenario is defined as the satellite communications link budgets with the least amount of link margin when all other factors are considered [terminals specifications, effective isotropic radiated power (EIRP), system gain to noise temperature ratio (G/T), data rate, modulation, and coding, etc.]. All additional technical details/specs are identified in PWS Attachment A, Technical Specification, government reserves the right to make deletions and additions as required; all links will be engineered at the best possible modulation rate.

The link margin shall be sufficient to support the target bit error rate, enhance link robustness, and counter the effect of rain and other propagation effects as well as antenna pointing errors and collateral degradations. Space segment must be offered on a satellite(s) that is currently on-orbit, operational, and station-kept; inclined orbit satellites will not be considered. The vendor shall meet a link availability of 99.5 percent.

Unless otherwise specified in the contract, the vendor(s) shall offer Transponded Bandwidth Pools and Managed Services solutions on a non-pre-emptible basis; that is, the bandwidth shall not be preempted for any reason and shall be replaced in the event of failure. Contracts may specify system-pre-emptible bandwidth (i.e., bandwidth that may be pre-empted in the event of a transponder or satellite failure elsewhere in the satellite provider’s system), or service-pre-emptible bandwidth (i.e., bandwidth that may be preempted to establish another user, such as cable res-toration service). Pricing for system-pre-emptible and service-pre-emptible bandwidth services shall be negotiated at the time of order.

2.1.4 Subtask 1.4 – Transponded Bandwidth Portability

The vendor shall provide the ability to relocate or “port” Transponded Bandwidth Pools as user requirements change. When portability is exercised, evidence of equivalent net present value shall be provided by the vendor.

Subject to availability, the ported bandwidth shall be available for use within fourteen (14) calendar days of the for-mal request by HQMC IC4 for routine operations, and within 48 hours for emergency or critical operations. Porta-bility shall consist of redeployment of the following:

Portability shall consist of redeployment of the following:

• One transponder/satellite to another

• Between beams or transponders on a single satellite

• One frequency band to another

• One region to another

2.2 Task 2 – Managed Services

2.2.1 Subtask 2.1 –Managed Service Solutions

Managed Service solutions shall offer links capable of supporting the user requirement with link margins that are adequate to overcome degradation that may be caused by equipment or the local environment.

2.2.1.1 Coverage Areas - Managed Services coverage areas should include global coverage at a minimum with op-tions for local and regional service plans.

2.2.1.2 Capacity - The vendor shall provide multiple options for bulk data purchases and varying data rates to in-clude committed information rates and maximum information rates.

2.2.1.3 Connectivity - Vendors shall provide Commercial Internet Service Provider (C-ISP) access at the regional commercial gateways. Vendors shall establish connectivity from the commercial gateway(s) to the MCEN through the USMC Commercial Multi-Protocol Label Switching (C-MPLS) environment through established government entry points (GEP) and government identified meet-me-points.

Page 6 of 30 Pages

2.2.2 Subtask 2.2 – Required Services Protection

Managed Satellite and Cellular services will include varying levels of Transmission Security requirements in the areas of traffic flow security; network and link layer encryption and protection of satellite Telemetry, Tracking, and Control (TT&C). Managed Services that do not meet security requirements may be considered by USMC on a case-by-case basis.

2.2.2.1 The vendor shall ensure that no less than Federal Information Processing Standard (FIPS) 140-3 grade de-vices are implemented or as otherwise directed by the government based on capabilities or as otherwise directed in support of USMC mission needs.

2.2.2.2 Encryption of link-layer frames used to transport terminal control, identification, and/or provide user traffic encryption at a minimum with Advanced Encryption Standard (AES-256).

2.2.2.3 To provide traffic flow security, Terminal IDs will be obfuscated and encrypted to avoid adversary recogni-tion of traffic patterns to a specific terminal.

2.2.2.4 To protect terminal access and authorization to the SATCOM network, the vendor will provide key manage-ment, generation, and distribution for authentication and access using FIPS/National Security Agency (NSA) ap-proved algorithms. In circumstances where FIPS/NSA approved algorithms are not available, authentication meth-ods will adhere to direction of the USMC in support of mission needs.

2.3 Task 3 – Worldwide Internet Protocol (IP) Reach-back Service The vendor shall provide worldwide reach-back connectivity to the Marine Corps Enterprise Network (MCEN) for remote USMC users using commercial bandwidth and or services provided under this contract. The requirements to meet this reach-back capability are as follows:

2.3.1 The vendor shall operate and maintain the necessary government furnished equipment (i.e., satellite communi-cations TRANSEC-ENABLED modems using at a minimum the Federal Information Processing Standard Publica-tion (FIPS 140-3) grade solutions including their applicable TRANSEC licenses, networking equipment, and any ancillary equipment and parts necessary to support the worldwide reach-back) at all commercial teleports. The ven-dor provides continuous operation when teleports/ground control stations to include shifting services to other spot beams and regional gateways upon service disruption due to weather, natural disasters, and cyber-attack. The vendor will provide technical support to users 24 hours a day, 7 days a week, 365 days a year.

The vendor shall be responsible for all installation, operation, and maintenance of commercially/government pro-vided equipment. Commercially provided equipment shall be compatible with the TRANSEC-modems and software identified in PWS Attachment A – Technical Specification.

Equipment and software upgrades to commercially/government provided equipment will be approved by the Gov-ernment through the Engineering Change Proposals (ECP) process described in PWS Paragraph 13a.

2.3.2 The vendor shall be capable of configuring their equipment from their location in the United States. The gov-ernment reserves the right to have a U.S. Government representative at the vendor location to provide oversight of the equipment and connectivity as required.

2.3.3 The vendor shall allow U.S. Government representatives access to all commercial teleport facilities to install, maintain, and inspect GFE as necessary.

2.3.4 The vendor shall be capable of providing alternate means of SATCOM Network Timing & Control for all sat-ellite architecture at each commercial teleport.

Page 7 of 30 Pages

2.3.5 The vendor shall be capable of landing remote USMC users IP traffic from a commercial teleport through local C-ISP access and providing connectivity to DoDIN PoPs through DISA Layer 3 Virtual Private Network Multipro-tocol Label Switching (L3VPN-MPLS) and USMC commercial MPLS environments. DoDIN PoP’s include, but are not limited to, GEP sites.

The current identified Government entry PoPs are located at:

- Camp Lejeune, North Carolina

- Camp Pendleton, California

- Marine Forces Reserve, New Orleans, LA

- Camp Foster, Okinawa, Japan

- MCBH, Kaneohe Bay, Hawaii

- Darwin, Australia

- Naval Support Activity Naples, Italy

- Naval Support Activity Bahrain, Manama, Bahrain

2.3.6 Connectivity between commercial teleports, PoPs, GEP sites must support best possible throughput, but at a minimum Optical Carrier (OC3) speed and below 200ms latency thresholds. The vendor will utilize government-identified preferred routing protocol. The vendor primary routing protocol shall be MPLS The vendor will provide a secondary Layer 3 VPN if leveraging C-ISP backhaul.

2.3.7 Terrestrial connectivity between commercial teleports, GEP sites, and the MCEN shall utilize geographically diverse circuits, validated by detailed layout records (DLR). DLR shall illustrate the physical routing of the circuits leaving the location as well as the long-haul path.

2.3.8 Each geographically diverse terrestrial link shall be equally sized to handle the aggregate data rate in the case of a failure/unavailability of the other link. The Vendor shall not utilize load-balancing to circumvent this require-ment.

2.3.9 Each geographically diverse terrestrial link shall be configured to be “active” in the case of a failure/unavailability of the other link. Change requests to circuit paths shall be provided as an Engineering Change Proposal and must include the revised DLR with the change proposal.

2.3.10 The vendor shall be capable of providing C-ISP backhaul from any LEO commercial teleport / landing station to the identified Government entry PoPs for MCEN access. Services shall land at approved commercial locations and landing locations shall not reside within the borders of any prohibited country or state of concern.

Deliverable: Detailed Layout Records

2.4 Task 4 – Program Management Support

2.4.1 Subtask 2.4.1 – Bandwidth Manager

The vendor will provide a bandwidth manager to serve as the primary liaison between the USMC and satellite ven-dors in managing various aspects of operational program support. The bandwidth manager is responsible for:

2.4.1.1 Providing centralized management of bandwidth to ensure users on various carriers do not conflict.

2.4.1.2 Collecting and providing usage data for out-year bandwidth needs.

2.4.1.3 Providing support for link budgets and engineering for commercial Ku, Ka, X, C, L-band, UHF band SAT- COM requirements. Link budgets will be engineered to the optimal throughput for bandwidth allocation.

Page 8 of 30 Pages

2.4.1.4 Receiving and processing commercial Satellite Access Requests (SAR) from requesting units and producing Satellite Access Authorization within seven (7) calendar days. All SAR, GAR, and Transmission Plans will be sub-mitted via SIPR Net. For high priority missions as identified by the Bandwidth Manager, Satellite Access Authoriza-tion/Gateway Access Request (SAA/GAR), and Transmissions Plans shall be generated within 24 hours.

2.4.1.5 Coordinating with commercial bandwidth providers Tactical Systems Support Center, Headquarters Marine Corps (HQMC) Deputy Commandant Information (DC I), Director, Information, Command, Control, Communica-tions, and Computers (Dir IC4), Supporting Establishment then publish the transmission plan.

2.4.1.6 Developing and executing engineering activities to include transmission planning, link budget analysis, net-work design, budgetary pricing, network enhancements, and technical briefings.

2.4.1.7 Attending and supporting USMC meetings associated with commercial SATCOM issues as directed by

HQMC IC4.

2.4.1.8 Coordinating with the technical Point of Contact (POC) from the government on the pre-configured, leased terminals and assignable to Non PoR and PoR terminals that use Managed Services.

2.4.1.9 Coordinating with the technical POC from the government on the technical refresh of each leased terminal at the end of a performance period.

2.4.1.10 Providing support for link budgets and engineering for Managed Services requirements across all orbits.

Link budgets will be engineered to the optimal throughput for bandwidth allocation.

2.4.1.11 Collecting and providing monthly usage reports to HQMC IC4.

2.4.1.12 The Bandwidth Manager’s primary place of performance will be Marine Corps Tactical Systems Support Activity (MCTSSA) at Camp Pendleton, CA.

2.4.2 Subtask 2.4.2 – Managed Services Manager

The vendor will provide a managed services manager to serve as the primary liaison between the USMC and man-aged service providers in managing various aspects of operational program support. The managed services manager is responsible for:

2.4.2.1 The Managed Services Manager will serve as the primary coordinator for vendor(s) providing Managed Ser-vices solution between the government and the satellite vendor in managing various aspects of operational program support for leased, Non-Program of Record, and Program of Record (PoR) terminals across each orbit. Provide ser-vice management of all managed services under this task order and services procured through other acquisition vehi-cles as directed by USMC.

2.4.2.2 Providing centralized management of managed services (LEO, MEO, GEO) to ensure users on various ser-vices do not conflict on shared managed service plans or simultaneous operations plans.

2.4.2.3 Collecting and providing usage data for out-year service needs.

2.4.2.4 Receiving and processing requests from various USMC units for commercial managed services against the pool of available services on contract for usage. For high priority missions as identified by HQ USMC, the provi-sioning of available services shall be completed within 48 hours.

2.4.2.5 Developing and executing engineering activities to include link analysis for availability of requested ser-vices, network design, budgetary pricing, network enhancements, and technical briefings.

2.4.2.6 Attending and supporting USMC meetings associated with commercial SATCOM issues as directed by

HQMC IC4.

Page 9 of 30 Pages

2.4.2.7 Coordinating with the technical Point of Contact (POC) from the government on the pre-configured, leased terminals and assignable to Non PoR and PoR terminals that use Managed Services.

2.4.2.8 Coordinating with the technical POC from the government on the technical refresh of each leased terminal at the end of a performance period.

2.4.2.9 Providing support for link budgets and engineering for Managed Services requirements across all orbits.

Link budgets will be engineered to the optimal throughput for bandwidth allocation.

2.4.2.10 Providing all necessary access documentation for each managed service, to include but not limited to, op-tion files, boot files, subscription service identification numbers, etc. as necessary for operation.

2.4.2.11 Collecting and providing monthly usage reports to HQMC IC4.

2.4.2.12 The Managed Service Manager’s primary place of performance will be Marine Corps Tactical Systems Support Activity (MCTSSA) at Camp Pendleton, CA. The USMC reserves the right to request relocation of the po-sition to the National Capital Region if it is determined that the Camp Pendleton location is not supporting opera-tional needs.

2.4.3 Subtask 2.4.3 – Bandwidth and Managed Services Management and Near-Real-Time Reporting Tool

2.4.3.1 The contractor shall have continuous, uninterrupted, near real time transparency via a monitoring and situational awareness portal. The contractor shall report bandwidth utilization for all bandwidth ordered under the subject contract at a minimum of near real time. Availability reports shall be accompanied by associated coverage maps. The contractor shall manage all data within the tool and ensure that it is up-to-date in accordance with the proposed interval of reports. This tool will be administratively managed by the vendor and will be operationally managed by the USMC. The tool shall be in the form of a database with a graphical user interface (GUI) providing ease of use to the USMC. Reporting capabilities shall include:

a. Provides the ability for requesting terminals and services from available Managed Services offerings and the ability for approval and management of requests.

b. Allows for the posting and downloading of files for the purpose of disseminating information pertinent to USMC users. Information includes but is not limited to all deliverable reports, operating procedures, usage reports, and satellite footprint files in a format that will allow for display with Google Earth Software, transmission plans and frequency matrices. Real-time monitoring for satellite anomalies, interference data, and spectrum data disrupting the service, including Electro Magnetic Interference (EMI) / Radio Frequency Interference (RFI) identification, characterization, and geo-location compliant with the EMI/RFI Reporting Checklist. Fault, incident, degradation, and outage reporting. Incident management and service resolution, and trouble tickets for out-of-tolerance and carrier-related alarms.

c. Real-time monitoring of the network and service availability.

d. Fault, incident, degradation, and outage reporting. Incident management and service resolution, and trouble tickets for out-of-tolerance and carrier-related alarms.

e. Allows the user to view all ongoing and scheduled maintenance events as well as 48-hour scheduled maintenance notifications.

f. Semi-annual sun transit reporting for each seasonal eclipse event.

g. On-demand and monthly reports such as usage report by site and terminal, and network performance.

h. Ability to drill-down on a specific terminal or event.

i. Ability to track equipment configuration, modifications, and component replacements by serial number.

j. Provide a means to assign carriers to specific users. i.e., units.

k. Provide a calendar-based interface to track and account for used and unused carriers.

l. Provide search capabilities to easily track and account for used and unused carriers.

m. Provide search capabilities to easily track and account for units utilizing used carriers.

Page 10 of 30 Pages

n. Near-real-time verification of actual carrier utilization by assigned unit.

o. Provide a means to reserve carriers.

p. Provide a means to upload Satellite Access Request’s (SAR) when generating reservations.

q. Provide a means to generate Satellite Access Authorization’s (SAA).

r. Provide a means to upload the latest transmission plan from XML file generated through the transmission plan builder.

s. Provide a means to manually assign each satellite on the transmission plan to a bandwidth pool.

t. Provide a means to manually assign each satellite, transponder, and carrier as ported to and from a satellite, transponder, and carrier or carriers. The bandwidth pool must be tracked by its link to the satellite previ-ously established.

u. Provide a means to establish start dates when the new transmission plan begins, which create the end date for the previous transmission plan. This functionality must provide a means of accurately placing the band-width in each pool and prevent from tracking the same bandwidth in multiple pools.

v. Provide a means to track equipment configuration, modifications, and component replacements by the se-rial number.

w. Provide a means to update the organization chart associated to the end users.

x. Contains a historical database of monitored data collected and stored over the past 30 days.

y. Provide a forecasting tool that has the following functionality:

i. Forecasts can be created using all filter criteria available from the usage and history tracking data.

ii. The Forecast tool will generate a 24-month forecast.

iii. Each forecast will include graphs for “Available Bandwidth Per Region,” as well as, “Percentage of Available Bandwidth Per Region.”

iv. For each month in the forecast range, the tool must provide the user the ability to view increases or decreases in the expected number of active terminals in inventory.

v. Forecast tool must include functionality to allow the user to view the expected average bandwidth usage per terminal.

vi. Forecast tool will include the functionality to allow the user to export forecast data to a CSV or Excel file.

z. Provide Near Real Time (NRT) status that shows the performance of an assigned channel.

aa. Provide a method for tracking all leased managed service subscriptions in all orbits; LEO, MEO, and GEO.

bb. Provide a means for users to track user access information for managed services.

cc. Provide a means for tracking services access logs and data usage for each leased managed service.

dd. Provide the ability to track purchased access credits for applicable services.

ee. Provide the ability to track and log service outages and various leased managed services for historical tracking.

ff. Provide the ability to schedule usage for each managed service across the fleet of available terminals and units.

gg. Accommodates a minimum of 25 simultaneously logged on users.

hh. The tool shall have the ability to provide all data offered through the aforementioned capabilities exported into a format compatible with other applications such as CodeMettle, a commercial data management soft-ware currently owned and operated by the Government.

ii. Include productivity and management methods such as quality assurance, progress/status reporting and pro-gram reviews. Provide the centralized administrative, clerical, documentation, and related functions.

2.4.3.1 The Contractor shall provide a portal accessible to the Contracting Officer's Representative (COR) and HQ USMC IC4 Planners and Technical Team via Hyper Text Transfer Protocol with Secure Sockets Layer (HTTPS).

The Portal must be accessible through public internet network. The Contractor Portal and all corresponding monitoring and control tools shall reside on the contractor's servers. Web portal shall be provided no later than 90 days after contract award.

2.4.3.2 Web Portal access may be required through Secret Internet Protocol Router Network (SIPR). Contractor shall identify their commercial requirements to support a SIPR instance of their web portal and any limitations from such operation (i.e. no access to coverage maps, etc.)

Page 11 of 30 Pages

2.4.3.3 The contractor shall manage user access to the Web Tool for both contractor and government personnel. The contractor shall administer and assign all usernames and passwords to the portal for both Contractor and Govern-ment personnel. The contractor shall provide multifactor authentication to access the Web Tool. The contractor shall manage user access to the Web Tool for the Government and shall provide access only to users approved by the designated Government POC; this may include Contractors working on behalf of the Government.

2.4.3.4 Web Tool Security. The contractor shall design the web-based monitoring tool to provide a minimum protection following DFARS Clause 252.204-7012 and NIST SP 800-171, to ensure all information transmitted is secure, and provide PKI access to the Web Tool. The contractor shall prevent unauthorized access to the Web Tool by implementing CUI protections as described in DFARS Clause 252.204-7012 and NIST SP 800 171 for each authorized user. The contractor shall provide a hierarchy of users, roles, and assigned domains. The contractor shall control access to the Web Tool by an administrator. Administrative features shall include the capability of recording any items created, edited, and deleted. These records shall be retained and accessible to the Government for the duration of the contract. The contractor shall provide different levels of access to the Web Tool to the users based on the level of appropriate authorization to data and resources, and also based on the credentials of the authenticated user as described by the Government. Additionally, the tool shall be secured in accordance with USMC Network and IA/Cyber/TRANSEC Security Policies. Reference the following policy documents from the USMC:

a. MCO 5239.2B Marine Corps Cybersecurity 5 Nov 15

b. NIST.FIPS.140-3 DTD 22 MAR 19

c. DODI 8540.01 Cross Domain Policy - DTD 8 MAY 2015

d. MIL-STD-1472H DOD Design Criteria Standard Human Engineering DTD 15 SEPT 2020

e. USMC Enterprise Cyber Security Directive DTD 31 MAR 2012

f. ECSM 018 MCAAP_4Jun2020_DCI_IC4

2.4.3.5 Web Tool Training. The contractor shall develop a curriculum for Web Tool user training. The curriculum shall be delivered within 90 calendar days after initial task order start date. The contractor shall provide two virtual training session during initial standup. Training sessions shall be scheduled after the Web Tool and training curriculum have been delivered and accepted by the Government. Initial training shall be conducted within 90 days of contract award. The training schedule will be approved by the Government at least 30 calendar days in advance of each training session. The contractor shall be prepared to conduct virtual refresher training at the Government location through the life of the contract at the Government's request.

2.4.3.6 Web Tool Design Demonstration. The contractor shall demonstrate their proposed Web Tool solution at the Kick-Off Meeting. If the Government determines updates need to be made, the contractor shall provide an updated version of the tool as requested by the Government.

2.4.3.7 Web Tool Delivery. The Web Tool shall be accessible on-line and ready for use within 90 calendar days after BPA start date. The Web Tool will be formally accepted by the Government after meeting all of the requirements of Section 4.3.

Deliverable: Data Export

2.4.3.8 The vendor shall also provide the information listed in 2.4.3.1 on Secure Internet Protocol Network (SIPR- Net). The vendor shall also provide terminal Geo Location information on SIPRNet.

Deliverable: Data Export SIPRNet

2.4.4 Subtask 4.4 – Transition Support

No later than 30 days prior to contract service start date, the vendor shall provide a timeline with sufficient detail to ensure all services will be in place no later than prescribed requirements in accordance with this PWS. Contract start date is thirty calendar days (30) prior to in-service start date. At in-service date, all services must be in place and fully operational to ensure a seamless transition from the current service.

Deliverable: Transition Plan

Page 12 of 30 Pages

2.5 Task 5 – Operations Support

2.5.1 Subtask 5.1 – General Service and Capability Requirements

2.5.1.1 Flexibility/Optimization

The vendor shall support re-grooming efforts at the Government’s request when reconfiguration of the bandwidth is necessary to support evolving mission needs. The Government will submit updated Technical Specifications to the vendor via the Regional Satellite Support Center (RSSC). Timeline for vendor to process and disseminate updated Transmission Plans is three (3) business days from receipt of updated Technical Specification. Flexibility/optimiza-tion/re-grooming shall redistribute resources in a manner, which enables the USMC to gain spectral, operation, and/or price efficiencies. The vendor will acquire additional bandwidth services as necessary to satisfy any new re-quirements requested by the USMC via HQMC IC4. Further information on Transmission Plan requirements is identified in subparagraph 2.6.2. The vendor shall coordinate all grooming efforts with HQMC IC4.

2.5.1.2 Network Monitoring (NetOps)

The vendor shall be capable of collecting and delivering the near real-time monitoring, fault/incident/cyber inci-dents/outage reporting, and availability consistent with commercial best practice. The vendor shall also immediately report faults, incidents, cyber incidents, and outages to the RSSC-West at Peterson Space Force Base, Colorado/ COR and HQMC IC4. The vendor shall implement robust, standards-based cybersecurity to DoD-specified levels including means to maintain positive control of space systems, including network C2, in a contested or degraded operational environment. The vendor’s NetOps monitoring capability should address the following metrics at a min-imum:

• Satellite anomalies likely to disrupt service - Satellite

• Interference Data – Satellite

• Spectrum Data – Satellite

• Satellite access and de-access by authorized users

• Satellite access by unauthorized users

• Terrestrial network health (Teleport to PoP)

• Cyber incidents

• Allow government access to monitor Cyber incidents

• TRANSEC- The vendor shall provide the ability to monitor the status of the provided TRANSEC protections en-acted on the network as part of the vendor's proposed solution between modems.

2.5.2 Subtask 5.2 – Frequency Clearances (FC) and Approvals

The vendor shall support Host Nation Agreement (HNA) efforts in obtaining international approvals for radio spec-trum operations under this contract in foreign nations. The vendor shall ensure that international services provided under this contract/contract may be provided as scheduled with the full approval of each affected host nation. Typi-cal services may include, but are not limited to host nation approvals, landing rights, operating agreements, site li-censes, and frequency clearances. If host nation support becomes necessary during the life of the contract, contract line-item numbers will be added to the order at the time they are required and shall be invoiced at pass-through rates.

The vendor may be required to provide HNAs for any nation covered within the limits defined in the coverage area, as needed by the user. The vendor shall provide the Government with copies of regulatory licenses and approvals obtained to operate and use the spectrum for countries within the required service region

The vendor(s) shall support Host Nation Agreement (HNA) and Host Nation Coordination (HNC) efforts in obtain-ing international approvals for radio spectrum operations under this contract in foreign nations. The vendor shall ensure that international services provided under this contract may be provided as scheduled with the full approval of each affected host nation. Typical services may include, but are not limited to: host nation approvals, landing rights, operating agreements, site licenses, and frequency clearances.

2.5.2.1 FCs for all required shall be required at service start. Terminal specifications and quantities to be provided post award.

2.5.2.2 If host nation support becomes necessary during the life of the contract, contract line-item numbers will be added to the order at the time they are required and shall be invoiced at pass-through rates.

Page 13 of 30 Pages

2.5.2.3 The vendor may be required to provide HNAs/HNCs for any nation covered within the limits defined in the coverage area, as needed by the user. A temporary FC shall be requested in order to meet the service start date re-quirement while the permanent license is processed.

2.5.2.4 FCs shall be requested for the maximum time period allowed by the host nation, up to the life of the contract.

The vendor shall provide the Government with copies of regulatory licenses and approvals obtained to operate and use the spectrum for countries within the required service region in the local language and English.

2.5.2.5 The Bandwidth Manager will coordinate, track, and forecast HNA/HNC status to include but not limited to technical requirement collection and submission, process tracking and update, and terminal inspection.

2.5.2.6 The Managed Services Manager will coordinate, track, and forecast HNA/HNC status to include leased ter-minals but not limited to technical requirement collection and submission, process tracking and update, and terminal inspection.

2.5.2.7 The Bandwidth Manager will receive direction from the USMC of terminal fielding to specific area requiring Host Nation (HN) coordination and will contact individuals responsible for obtaining HN authorization for up-to-date requirements as these change from HN to HN and terminal to terminal – this includes obtaining all technical documentation along with concept of operations, terminal equipment’s configurations, terminal locations, and opera-tional periods.

Deliverables: Host Nation Support Effort

2.5.3 Subtask 5.3 – Electro Magnetic Interference (EMI)/Radio Frequency Interference (RFI) Identification, Characterization, and Geo-location The vendor shall provide legible EMI/RFI identification, characterization, and geo-location in accordance with the EMI/RFI Reporting Checklist. Such services include the ability to identify and characterize sub-carrier EMI/RFI being transmitted underneath an authorized carrier, and the ability to geo-locate the source of any and all EMI/RFI.

The vendor shall also immediately report the existence of EMI/RFI to the RSSC-West/COR/HQMC IC4 and Band-width manager. Additionally, the vendor shall make best efforts to geo-locate the source of the interference and re-port findings (as documented in the EMI/RFI Reporting Checklist). The vendor shall support Government exercises focused on the resolution of EMI/RFI interference scenarios as directed, no more frequently than quarterly. The ven-dor (and/or subcontractors) shall provide initial acknowledgement of EMI/RFI to the RSSC-West by telephone within ten (10) minutes. Best effort geo-location of the interfering signal source, spectrum analyzer screenshots, and characterization (as described in the EMI/RFI Reporting Checklist) shall be provided within thirty (30) minutes of vendor EMI/RFI detection or Government request if events are detected by the Government. Updates of such infor-mation shall be provided to the Government upon change, upon request, or every two (2) hours from initial report, until incident resolution. If secure email and/or voice communications are not available, the vendor (and subcontrac-tors) shall use a mutually agreed upon media and voice communications capability capable of protecting sensitive but unclassified data. Upon incident resolution, the vendor shall provide a Summary of Action Report, summarizing the incident, corrective actions taken, and incident resolution, to the RSSC-West/ COR/HQMC IC4 and Bandwidth manager.

Deliverable: EMI/RFI Reporting Checklist, Summary of Action Report

2.5.4 Subtask 5.4 – Fault Management.

The vendor shall monitor and maintain positive control of services provided. When attempting to access or re-access the satellite, the operator will always contact the Network Operations Center (NOC) for the lease at the contact in-formation provided on the Transmission Plan and conduct a peak and polarity adjustment prior to accessing the sat-ellite.

2.5.4.1 Fault Reporting.

For all services being provided, the vendor shall report fault information to the RSSC-West. Fault information in-cludes but is not limited to detection, identification, and isolation of faults, and initiation, tracking, and completion of corrective actions. The vendor shall electronically report fault information with the associated signal parameters

Page 14 of 30 Pages for out-of-tolerance alarms and carrier-related alarms via trouble tickets to the RSSC-West as well as provide a sum-mary of fault trends and detailed statistics in its Monthly Status Report. Trouble tickets shall be updated every 2 cal-endar days for non-serious issues regardless of change in status, and daily for serious issues. Serious issues are those that impact service and cause interruptions or outages. Non-serious issues are those that cause no service interrup-tion or outage but hinder the ability to establish new service.

Deliverable: Trouble Ticket

2.5.4.2 Service Interruption and Restoration

For service outages, the vendor shall provide verbal and written status reports to the RSSC-West. These reports are in addition to all electronic reports and monthly reports. These reports shall identify the affected service(s) and the cause of outage if known, and the actions already taken and planned to correct the outage. Initial reports shall be provided by phone to the RSSC-West within 10 minutes of detection. Initial trouble tickets shall be submitted to the RSSC-West within 30 minutes and updated hourly thereafter until service is restored. For outages known to be due to failures in vendor-provisioned elements, the vendor shall initiate conference calls between the vendor’s operation center, the COR, the RSSC-West, HQMC IC4, Bandwidth Manager and/or Managed Service Manager and for satel-lite related issues, the applicable satellite operations center (SOC) supporting the vendor’s service. For outages last-ing 120 minutes or more, the vendor’s Program Manager (PM) shall participate in the conference calls. For outages lasting 240 minutes or more, the vendor’s senior management shall participate in the conference calls.

Deliverable: Trouble Ticket

2.6 Task 6 – Reporting

2.6.1 Subtask 6.1 – Monthly Status Report

The vendor shall deliver a Monthly Status Report to the COR, HQMC IC4, Contracting Officer, Contract Specialist, and the RSSC-West that addresses the following topics:

• Number of active terminals using the services leased

• Status of active monitoring, management, and control

• Downtimes (to include and relevant trouble ticket number, carrier, start, and stop time of trouble event in ZULU time, summary of event, and credit given to the customer)

• EMI/RFI Incidents regardless of whether downtime was incurred (to include any relevant trouble ticket number, carrier, start and stop time of incident in ZULU time, and summary of event)

• Troubleshooting and customer assistance provided

• HNA issues

• Planned Changes

• Cyber Incidents

Deliverable: Monthly Status Report

2.6.2 Subtask 6.2 – Transmission Plan

Where applicable, the vendor shall operate services in accordance with the vendor submitted and satellite operator approved Transmission Plan provided within five (5) calendar days of award and at least 24 hours prior to the start of the lease. Timeline for vendor to process and disseminate updated Transmission Plans is three (3) calendar days from receipt of updated Technical Specification. A copy of all such plans shall be provided to the COR and the RSSC-West and HQMC IC4. The Transmission Plan shall be submitted electronically in MS Excel format and XML format. The Government will provide the tool required to build and convert the Transmission Plan to the XML format. Information to be contained in the Transmission Plan is as follows.

General Information:

• Vendor name/logo

• Tracking number

Page 15 of 30 Pages

• Date of Transmission Plan

• Transmission Plan revision

• Vendor PM contact information (name, phone number, and email)

• Vendor NOC contact information (phone number and email)

• Satellite Owner/Operator(s) Operations Center contact information

• Leases begin and end date

• Satellite(s) name and orbital position included on lease

• Transponder(s) included on lease

• Beacon(s) center frequency and polarization for each satellite

Transponder Technical Characteristics Table:

• Satellite name and position (degrees)

• Transponder identification (ID)

• Transponder bandwidth MHz

• Usable bandwidth MHz

• Leased bandwidth MHz

• Saturated flux density at 0 Db per degree Kelvin (Db/K)

• Uplink Center Frequency MHz, Polarization, Antenna/Beam

• Downlink center frequency MHz, polarization, antenna/beam

• Transponder translation frequency

Technical Parameters Table:

• Carrier ID (CXR ID)

• Lineup reference ID

• Transmit and receive terminal ID

• Data rate

• Reed-Solomon code (n,k)

• Modulation and forward error correcting rate

• Symbol rate

• Allocated bandwidth

• Allocated power-equivalent bandwidth

• Transmit center frequency

• Receive center frequency

• Required Energy per bit to Noise ratio (Eb/No) value

• Target Eb/No value

• Uplink EIRP

• Carrier input back off

• Carrier output back off

• Percentage leased bandwidth, leased power, transponder bandwidth, and transponder power

Deliverable: Transmission Plan

2.6.3 Subtask 6.3 – Semi-Annual Sun Transit Reporting

The vendor shall provide semi-annual sun transit reports at least fourteen (14) business days prior to each seasonal eclipse event.

Deliverable: Semi-Annual Sun Transit Report

2.7 Task 7 – Information Assurance (IA) and Cyber Security

2.7.1 Subtask 7.1 – Information Assurance

IA is applicable to Satellite Access Center, Satellites, and Vendor Enclave controlling/managing satellite communi-cations resources. Details of the vendor solution IA security posture shall be documented in the Government pro-vided COMSATCOM IA Questionnaire (CIAQ). The vendor shall ensure that for all controls identified as part of the CIAQ, or other cybersecurity requirements, that the implementation of the control or mitigation identified are in

Page 16 of 30 Pages place at the period of performance start date. The vendor shall continually monitor and verify IA is maintained in accordance with the CIAQ so long as the contract is in effect. The vendor may be subject to Government and/or in-dependent verification.

2.7.1.1 Communication and Data Protection Using External Certificate Authority (ECA) PKI The DoD Cyber Exchange (Public) has established the ECA program to support the issuance of DoD-approved cer-tificates to industry partners and other external entities and organizations.