W904TE-19-I-0001.pdf

REQUEST FOR INFORMATION (RFI) / SOURCES SOUGHT (SS) NOTICE

Low Earth Orbit (LEO) and Medium Earth Orbit (MEO) Satellite Service

THIS IS A REQUEST FOR INFORMATION (RFI) AND NOT A SOLICITATION. This RFI is for planning purposes only and shall not be considered as an invitation for bid, request for quotation, request for proposal, or as an obligation on the part of the Government to acquire any products or services. Your response to this RFI will be treated as information only. No entitlement to payment of direct or indirect costs or charges by the Government will arise as a result of contractor submission of responses to this announcement or the Government use of such information. This request does not constitute a solicitation of proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated, or received for this effort. The information provided may be used by the Government in developing an acquisition strategy, or performance work statements, or specifications. Interested parties are responsible for adequately marking proprietary or competition sensitive information contained in their response. The Government does not intend to award a contract on the basis of this RFI or to otherwise pay for the information submitted in response to this RFI.

By submitting information in response to this RFI, respondents consent to the release and dissemination of submitted information to any Government or non-Government entity to which PEO-EIS TAO releases and/or disseminates the information for review. As such, to the extent that any information submitted in response to this RFI is marked as, or construed to be proprietary or business-sensitive, respondents are hereby notified (a) of the potential that such information may be disclosed to third parties and (b) that submission of information in response to this RFI constitutes consent to disclosure of submitted information. NO phone calls and/or request for a Solicitation will be accepted or acknowledged. Company Brochures are NOT desired.

Technical questions regarding this RFI should be directed to Ms. Janine A. Kerns, 301-619- 1724, or Janine.a.kems.civ@mail.mil, or mailed to PEO-EIS, Technology Applications Office, ATTN: SFAE-PS-TS-TAO-C (Janine A. Kerns) 1671 Nelson Street, Fort Detrick, MD 21702- 5044 No later than 9 July 2019.

The Government requests responses to this RFI be submitted NO LATER THAN 31 July 2019 at 3:00 PM EDT. All Interested parties must submit in writing (no more than 25 pages, single spaced) their capabilities, experience and familiarity with providing the services stated below.

Sections 1 and Section 2 must be answered in the same order as shown within this document with the items properly referenced. A response with ' no ' or ' not provided with the given architecture' is an appropriate answer, but failure to respond to an identified item may be considered a negative response during review of the provided information. The complete response to Section 1 and Section 2 to this RFI shall be limited to a total of 25 pages. Additional attachments may be provided, but will not be considered as part of the RFI response. Marketing materials are not a sufficient response to the RFI. The responses should be in Adobe Acrobat Portable Document Format (PDF) or in a format compatible with Microsoft Office. Please submit your responses via email to: Ms. Janine Kerns at Janine.A.Kerns.civ@mail.mil.

INTRODUCTION/SCOPE

The United States (U.S.) Army Program Executive Office for Electronic Information Systems (PEO-EIS) Technology Applications Office (TAO) is requesting information regarding Satellite Services and Terminals to provide Beyond Line of Site (BLOS) communications

BLOS communications are critical in providing Command and Control (C2) to military forces engaged in combat operations beyond line of site of a Joint / Tactical Operations Center (JOC/TOC). BLOS communications enable gathering of actionable intelligence by relaying intelligence information and data from an area of interest back to a JOC/TOC for Processing, Exploitation, and Dissemination (PED) operations. The vast majority of BLOS communications in the tactical environment today are provided by satellite communications. Continuous improvements in space based communications have resulted in significant improvements in satellite design resulting ih the ability to reduce Size, Weight, and Power (SW AP) for mobile platform and ground based satellite terminals. Disparate satellite services that include developments in Low Earth Orbit (LEO) constellations, Medium Earth Orbit (MEO) and High Throughput Satellite (HTS) commercial services have the potential to significantly improve the flow of information between the tactical environment and Mission Command elements on the battlefield. As a result, the Government is seeking information related to better ways to realize an end to end, comprehensive, and global service focused on Ultra Sat terminals (.:S30 CM parabolic or equivalent and or Electronically Steerable Arrays (ESA) in a form factor 12 by 12 inch flat or conformal) for aircraft, maritime, ground vehicular Communications on the Move (COTM) and individual operator terminals (dismounts) in a form factor small enough to carry in a rucksack.

Additionally, the Government is seeking efficient, service-based, satellite communications capabilities for airborne enroute mission planning and Shipboard Carry On Satellite Systems (SCOSS) which may require COTM satellite terminals larger than the primary RFI focus (Ultra Sat terminal form factors) . This RFI defines specific areas of interest related to such a service offering.

SATELLITE SERVICE DESIRED

1. The satellite service shall be comprehensive, end to end, including terminals that might be made available as part of the service and in compliance with the Federal Acquisition Regulation (FAR) and or terminals that may be procured or developed by the Government and authorized for use by the service· provider. The satellite service shall include ground entry points, terrestrial backhaul, Network Operations, and secure methods for billing the Government.

I .a. The satellite service shall be global in nature or at a minimum shall provide full earth coverage from 65 degrees North to 65 degrees South latitudes. If service is not yet in operation, provide the projected dates of available global service.

1.b. The satellite service shall include global dedicated and physically redundant terrestrial connectivity tying the service-provided satellite entry points back to the Eastern seaboard of the United States.

1.c. The satellite service shall include a secure Network Operations Center (NOC) manned full time, year round and capable of responding to and resolving trouble calls on a global nature. The NOC shall have a SIPR node to enable classified communications between the Government and the service provider. The satellite service provider shall define how user traffic will be handled at the secure facility. The information on handing of user traffic includes defining if the operation center can store classified information (and to what level of classification) as well as the current ability to provide cleared personnel for management of the classified material / information or the ability to clear personnel to meet this requirement.

1.d. The satellite service provider shall identify authorizations for terminal frequency clearance and host nation landing rights provided by the service provider. The service provider shall identify blackout zones including providing rationale for restricted areas where terminals may not be utilized. The satellite service provider shall demonstrate to the Government full understanding of Army Regulation 5-12 (Army Use of Electromagnetic Spectrum) as it relates to approvals for service provided satellite terminals. The service provider shall demonstrate how terminal developmental efforts geared toward accessing the service provider' s satellite services will attain spectrum and host nation access.

l .e. The satellite service provider shall provide various service offerings through an agreed to Service Level Agreement (SLA) that defines Committed Information Rates (CIR) on a per simultaneous operation basis. CIR is the minimum data rate that the associated terminal will provide to users via network connectivity at all times as outlined in the SLA. Each simultaneous operation as defined by the Government means one global instantiation at a given time accessible by "N' number of service registered terminals/modems for a given service with a defined CIR (dependent on mission and current capabilities). (Example: For airborne mission planning capabilities, the Government may decide to license 30 possible service terminals or modems that can access up to 8 global simultaneous operations at any given time in any location globally available by the service being provided. In the pool of 30 possible terminals, users should be able to come into the service and exit the service in a dynamic manner without the need to check in with the NOC. In the event the Government unintentionally attempts to enter the service with a 9th simultaneous operations, the service provider NOC or automated service capability will prevent the non-licensed access). In the example provided, the Government realizes there may be different terminal types in the pool that require different space resources ( additional satellite Effective Isotropic Radiated Power (EIRP) for a lower performing Tail Mount Antenna (TMA) vs a Fuselage Mount Antenna (FMA) for instance). This RFI will provide a scenario example for which RFI recipients can use to develop a response.

1.f. The satellite provider shall provide information on the ability to isolate user services through ground entry points (for global satellite services) located in the continental United States and user specified countries.

1.g. The satellite provider shall define the altitude of constellation satellites and the latency from the user terminal to the location at the Gateway where the user receives data from the provider.

1.h. The satellite provider shall define the coverage area for the constellation. If the constellation is in development or has future development efforts, the satellite provider shall identify the coverage area and date of completion for each phase. This includes defining the number of satellites, number of satellites in view to user terminals within the coverage area, and the lowest (as well as average) look angle that user terminals will experience. The satellite provider shall identify cell size (coverage area) for one beam for satellite coverage and the number of beams per satellite (include beam types if more than one type is in use). The satellite provider shall identify whether beams are on all the time everywhere in the defined coverage area (including areas where there is no active customer). If active cell/spot beam coverage is not on all the time, then the satellite service provider shall explain how a non-covered area gets activated, the process to activate an uncovered area, and the time it takes to accomplish activation.

1.i. Encryption: The satellite provider shall identify encryption used throughout the architecture to include type of encryption, layer of encryption (physical/logical), and who has access to the data (host nation, etc.). This shall include identifying what portions of data are encrypted (header data, long/lat data, message data, etc.) and shall include level of detail for the following items:

• User Data Links from User Terminal to Satellite

• User Data Links from Satellite to User Terminal

• Data Link from Satellite to Gateway (include User Terminal Gateway if appropriate)

• Data Link from Gateway to Satellite (include User Terminal Gateway if appropriate)

• Control Links between the Gateway and the Satellite

• Control Links between Satellite and User Terminal (if appropriate)

• Gateway Data

• MPLS (Multiprotocol Label Switching)/ Fiber between Gateways (if app_ropriate)

• User Data Storage (Gateway or Tech Control Facility, if appropriate)

• Identify Key Management procedures for each (storage, rotation, etc.).

1.j. The satellite service provider shall provide information on the architecture support for user terminal to user terminal communications. The satellite service provider shall identify any limitations to this service, such as minimum terminal size or performance ( e.g. gain-to-noise temperature (G/T), EIRP, etc.), or if a user gateway would be required.

1.k. The satellite service provider shall provide information on whether the user will be able to monitor beam movement or control beam/select beam movement (identify all options). The satellite service provider shall identify the availability of user Gateway terminals (to include if the user community may "own" a Gateway and any restrictions on installation locations) and the control that a user Gateway terminal (if an option) would have over data through the Gateway.

The satellite service provider shall provide information on the capability for monitoring real-time updates of the performance of the system to include users, resource allocations and interferers.

1.1. The satellite service provider shall identify terminal operations when Global Positioning System (GPS) data is not available and the amount of drift that is acceptable for the user terminal's location data provided by the user terminal. Identify if the capability exists to manually set the GPS data and the acceptable distance from the actual location that is acceptable.

Identify any throughput reductions that result from inaccuracies in the GPS location data.

Identify if the user terminal can be brought into operations without identifying the user terminal location.

1.m. The satellite service provider shall provide information on any inherent data protections as part of the architecture (for example, narrow beams require that the interferer is within the same beam). The satellite service provider shall define all International Telecommunications Union/ Federal Communications Commission (ITU/FCC) filings and the date of the filing for the spectrum (provide spectrum details) that provide protection for priority of service over other constellations. The satellite service provider shall detail any capabilities that can be provided to mitigate interference (beamforming, nulling, frequency separation, frequency hopping). For example, a provider should detail an ability to reduce interference by nulling an interfering frequency or reduce interference by frequency hopping or frequency spreading.

1.n. The satellite service provider shall identify how services are routed through the constellation and between Gateways, to include between the User Terminal and the Satellite, when transitioning between Satellites for the User Terminal, between Gateways (if appropriate), and from User Terminal to User Terminal (if appropriate). This should include defining break before · make or make before break for the type of architecture, defining how secure user terminal Generic Routing Encapsulation (GRE) tunnels would be maintained, and the type of routing used (physical/logical). The satellite service provider shall define process for determining and selecting Gateway landing location and the ability to utilize terrestrial fiber/copper to route user terminal data.

1.o. The service provider shall include information on any planned Optical Inter-Satellite Links capability that will transport data between satellites and date(s) that this service will be available, if not initially available on the architecture. Include information on the following:

• Throughput for optical links

• How optical links change the architecture

• Security improvements provided by optical links (if appropriate)

• Risks to the architecture from optical links (if appropriate)

• Can user terminal traffic transition directly to a Gateway within the United States (not received at other Gateways)

• Can user terminal traffic travel directly between user terminals (not received at Gateway)

• Can user terminal traffic travel directly between User Gateway and User Terminal (not received at service provider Gateway)

• Can the user define the landing location (for user terminal data) l .p. The satellite service provider shall define any optical capability to the ground ( optical link from the satellite-to-the-ground and from the ground-to-the satellite) that will or can be provided in the current/planned architecture and the date that the capability will be available to users. The satellite service provider shall define any data protection and/or vulnerabilities provided by this capability and associated characteristics of this upgrade/change to the architecture to include throughput and latency for these links. The satellite service provider shall describe any mixed

Radio Frequency (RF)/Optical environments if they are required during the transition to an optical ground service capability or if it is required as part ofthis type of service For example, low throughput RF beacon for initial entry into the architecture (for antenna pointing). The satellite service provider shall define any throughput I outage level expectations from weather as part of optical ground service since it would be more heavily impacted from adverse weather, sandstorms, etc. The satellite service provider shall define how data will transition through the architecture (physical/logical routing in use) for optical ground service, to include terminal transition between satellites and how the architecture would maintain secure user terminal GRE tunnels to support a make before break architecture.

1.q. The satellite service provider shall define when the architecture will be available for testing the capability to support user requirements. The satellite service provider shall define any phased development and when each phase of the development would be available for testing.

1.r. The satellite service provider shall provide test reports showing any previous tests on the architecture as an attachment to this RFI (will not be counted against 20 page limit for the RFI).

2. SATELLITE SERVICE TERMINALS DESIRED

The Government prefers options for satellite service-provided terminals as part of the overall service-based end-to-end offering. The Government would also consider cost share development of needed, but yet unrealized, terminals.

2. a. The satellite service provider shall complete Table one that outlines maximum and minimum CIRs available by terminal size. In addition, the satellite service provider shall provide the minimum data rate that can be supported by the architecture in Transmit and Receive.

Beyond the candidate list in Table 1, the Government is interested in Ultra-Sat options not listed but available by candidate satellite service providers. Any additional SLAs that show standard CIR costs for lower rates would be beneficial. If the terminal size will not be available in the satellite service provider's architecture, the satellite service provider shall identify this limitation and provide data for the smallest terminal that can be used for this capability.

TABLE 1

Tem1inal Type Use Case Identify Minimum and Maximum SW AP I Spectrum Terminal cost:

(example) (example) CIR available for Size Provided (example) RFI Response

(Minimum Threshold Provided) (example) Ultra-Sat scoss 3 Mbps Transmit (Minimum) 12xl2x4 inch ROM/Month Electronically Steered Array 18 Mbps Receive (Minimum) Ultra-Sat Airborne 3 Mbps Transmit (Minimum) I 2x I 2x4 inch ROM/Month Electronically Steered Array 18 Mbps Receive (Minimum) Ultra-Sat Ground Vehicular 3 Mbps Transmit (Minimum) 12xl2x4 inch ROM/Month Electronically Steered Array 18 Mbps Receive (Minimum) Ultra-Sat Dismount: MANET 3 Mbps Transmit (Minimum) 12xl2x4 inch ROM/Month Electronically Steered Array BLOS Extension 18 Mbps Receive (Minimum) Ultra-Sat :::;30 CM Parabolic scoss 3 Mbps Transmit (Minimum) :::;30 CM Parabolic or ROM/Month or equivalent Flat Panel Array 18 Mbps Receive (Minimum) equivalent Flat Panel Array Ultra-Sat :::;30 CM Parabolic Airborne 3 Mbps Transmit (Minimum) ::S30 CM Parabolic or ROM/Month or eauivalent Flat Panel Array 18 Mbps Receive (Minimum) equivalent Flat Panel Array Ultra-Sat 90 CM Parabolic Ground Vehicular 3 Mbps Transmit (Minimum) ::S30 CM Parabolic or ROM/Month or equivalent Flat Panel Array 18 Mbps Receive (Minimum) equivalent Flat Panel Array Ultra-Sat Sensor Data Exfil 3 Mbps Transmit (Minimum) 6" X 6" X 4" ROM/Month

3 Mbps Receive (Minimum) Ultra-Sat Tactical UAS 6 Mbps Transmit (Minimum) Best effort ROM/Month

3 Mb s Receive (Minimum Ultra-Sat Rotary Wing 3 Mbps Transmit (Minimum)

18 Mb s Receive Minimum

Note: All rates are user throughputs to and from the terminal

Best effort ROM/Month

2.b. The satellite service provider shall provide the monthly cost for terminals at multiple CIRs.

The estimate may be tiered to show different CIRs for each terminal size. For example, an SLA at the maximum CIR, an SLA at a standard CIR, and an SLA at a minimum CIR. The satellite service provider shall provide any bundling of services that would reduce costs for the user (for example, a percentage reduction once a certain level price level is reached). The satellite service provider identify options available for traffic prioritization to guarantee a level of service over the network, such as Quality of Service (QoS).

2.c. The satellite service provider shall identify the minimum terminal Transmit Effective Isotropic Radiated Power (EIRP) in dBW and Receive GIT in dB/K for terminal access to the vendor' s constellation. The satellite service provider shall identify the minimal terminal size that would be able to access the constellation. The satellite service provider shall identify if carrier spreading is required to meet the minimum terminal size or throughput requirements and any Spectral Density Adjacent Satellite Interference concerns.

2.d. The satellite service provide shall provide a list of current user terminals that are available / planned. Include options for fixed antenna, ,communications on the move, maritime antennas, and antennas for aircraft. This list shall include shock/vibe data as well as any water resistant/ waterproof ratings. List any terminals that are being developed for Government use and whether the terminal will be provided as part of service or whether the terminal must be purchased separately:

TABLE2

Terminal Type Terminal Size Maximum ClR available Terminal Info Terminal Cost (examole) (examole) (examole SLA oarameter) (examole) (examole)

Electronically Steered Array l2" xl2" x4" Transmit 50Mbps / Receive 50Mbps Ka-band (list Bands) ROM (Flat Panel) (user throughput) RHCP TX/ LHCP RX

(example)

2.e. The satellite service provider shall define frequencies in use by the terminals and architecture. The following chart has been provided to .show expectations.

TABLE3

Frequency Frequency Type of Polarization TXElRP RXG/T Notes

Date Available

XX XXX XX

(examole) (examole) (examole) (examole) (examole) (Additional Info) User Terminal to Satellite 29GHz - 3I GHz Circular (LHCP) xx dBW xx dB/k Satellite to User Terminal 19.2 GHz - 21.2 GHz Circular (RHCP) xx dBW xx dB/k

Gateway to Satellite 29GHz - 3I GHz Circular (LHCP) xx dBW xx dB/k Satellite to Gateway 19.2 GHz - 21.2 GHz Circular (RHCP) xx dBW xx dB/k

2.f. The satellite service provider shall define User Gateway terminals (if available). Provide a list of Gateway terminals that are available / planned and the following details:

TABLE4

Terminal Type Terminal Size Maximum CIR available Terminal Info Terminal Cost Date (define ifGW or UTI (example) (example SLA parameter) (examole) (examole) Available

Electronically Steered Array 2mx 2m TX 200Mbps / RX 200Mbps Ka-band (I ist Bands) ROM XX XXX XX

(Flat Panel) RHCP TX/ LHCP RX (COST) User Terminal

Parabolic 4m TX 2Gbps / RX 2Gbps Ka-band (li st Bands) ROM XX XXX XX

(Gatewav Onlv) RHCP TX/ LHCP RX (COST) Parabolic 3m TX 800Mbps / RX 800Mbps Ka-band (li st Bands) ROM XX XXX XX

(Gateway or User Terminal) RHCP TX/ LHCP RX (COST)

2.g. The satellite service provider shall identify the time required to provision a new terminal within the architecture, to include external support and any ephemeris data that must be downloaded. The satellite service provider shall identify the time required for active terminal provisioning. If there are time frames that increase the provisioning time, please identify those time frames (for example, a terminal reenters the network after a predetermined time frame or the terminal reenters the network after provisioning, but has a different geographic location).

2.h. The satellite service provider shall define the modem architecture in use to include modem type, the ability of vendors to procure/work with the modem architecture (will the chipset be available for use by terminal vendors), and what capabilities are available with the modem (waveforms or technology).

2.i. The satellite service provider shall detail the open system architecture being provided for future terminal development. This includes defining if the architecture is modem terminal agnostic and if terminal developers will be able to leverage the modem chipset when developing terminals. The satellite service provider shall list all modems that can be used within the architecture and identify if there will be a mix of homogenous services with the ability obtain raw capability and apply a user modem.

2.j. The satellite service provider shall ensure satellite terminals are auto acquire capable and provide information on the time the system requires to complete acquisition (already provisioned in the architecture with measurement from cold start to modem lock).

2.k. The satellite service provider shall detail how terminals switch between satellites in the architecture. A make before break architecture is preferred when user terminals transition between satellites. The satellite service provider shall identify how services will transition to a new satellite and if a make before break architecture will be provided to include how the terminal makes the transition and how the data connection is impacted during the transition between satellites. ESA satellite terminals are required for this architecture since user terminals must constantly switch between satellites and previous experience with a similar architecture show mechanical failures introduce risk for the user.

2.1. The satellite service provider shall ensure terminal pointing and tracking capability use open standards.

2.m. The satellite service provider shall ensure any terminals owned by the Government and or terminals developed on a cost share basis with the satellite service provider include a full Interface Control Document (ICD) and allow the Government full purpose rights to use as required by the Government. Terminals solely developed by the satellite service provider shall be the intellectual property of the service provider.

2.n. The Government operates airborne capabilities with two classes of airborne qualified terminals (small and large). Though the Government expects to meet its desires for smaller platforms with 30 cm or smaller antenna designs, larger platforms can and should host larger aperture antennas to gain satellite resource efficiencies and to allow for greater data rates as requirements increase in the future. As a result, the satellite service provider shall identify airborne terminals in the 30 cm or smaller as well as larger platform sizes. ·

2.o. The Government operates SCOSS capabilities and is interested in systems that can support employment in pairs enabling the Government to mitigate ship structure blockage such that the Government can maintain a continuous transmissions link. As a result, the satellite service provider shall identify any SCOSS terminal capability.

2.p. The satellite service provider shall identify any foreign built (outside the United States) terminals, terminal parts, modems, and software that are part of user terminals, or Gateways.

(U) 3. SATELLITE SERVICE AFFORDABILITY

The Government is interested in an affordable, bundled, mobility and ground based satellite service offering. The satellite service provider shall use a simultaneous operations based approach in identifying affordability based on the example scenario provided below. Rough Order Magnitude (ROM) service costs shall be provided as part of the overall RFI response. The ROM estimate may include per MHz or per GHz cost that could be used by the Government for cost comparison. The Government understands these ROM estimates do not constitute a commitment on the part of satellite service providers to the Government.

Scenario Example

General: The Government is engaged in continuous efforts on a global scale with daily training events that require satellite based support. For purpose of this example, desired simultaneous operations have been identified. In the event use is required outside the allocated simultaneous operations pool, a pay as you go structure would be needed.

Aero Scenario Primary: Desire for 4 large aero and 4 small aero based Global simultaneous operations with CIR's. The Government requests CIR confirmation and ROM estimates.

Ground Vehicular COTM Scenario (GVCS): The Government intends to share the simultaneous operations identified in the Aero primary scenario above. As it relates to GVCS tactical use, ESA Ultra-Sat solutions are required.

SCOSS: The Government is interested in systems capable of data rates outlined in the RFI along with associated ROM costs for three global simultaneous operations. For Ultra-Sat SCOSS systems identified in this RFI, the Government intends to share the simultaneous operations identified in the Aero Primary scenario above.

Ground Tactical COTM: The Government is interested in systems capable of ground tactical COTM services (manpack/backpack) and associated ROM costs for simultaneous operations to support this type of service. The satellite service provider shall consider mounted and dismounted (backpack with quick removal/setup) options and the ROM costs associated with each option.

Ground Fixed: The Government is interested in systems that can support a mix of low to high throughput for fixed terminal locations. This includes options associated with user Gateway terminals to support user terminals and optioq_s associated with higher throughput user terminals at fixed/semi-fixed locations. The user should provide ROM costs (and simultaneous operations) that would support these types of services.

Radio over Satellite Scenario: The Government is interested in handheld radio over satellite service provider bandwidth. The satellite service provider shall provide a solution for utilizing a handheld radio, providing up conversion of the carrier signal, and how the network would be utilized on the satellite service provider's constellation. This will include the amount of bandwidth required to support this low throughput voice and data capability.

Tactical UAS and Rotary Wing Scenario: The Government is pursuing both capabilities having fielded nothing to date. The Government requests interested parties response on availability and ROM cost for service.

ACRONYMS

BLOS Beyond Line of Sight C2 Command and Control CIR Committed Information Rate COTM Communications on the Move EIRP Effective Isotropic Radiated Power ESA Electronically Steerable Array FAR Federal Acquisition Regulation FCC Federal Communications Commission FMA Fuselage Mount Antenna GIT Gain-to-noise-temperature GRE Generic Routing Encapsulation GPS Global Positioning System GVCS Ground Vehicular COTM Scenarios HTS High Throughput Satellite ICD Interface Control Document ITU International Telecommunications Union JOC Joint Operations Center LEO Low Earth Orbit LHCP Left Hand Circular Polarization MEO Medium Earth Orbit MPLS Multiprotocol Label Switching NOC Network Operations Center PED Processing, Exploitation and Dissemination QoS Quality of Service -RHCP Right Hand Circular Polarization RF Radio Frequency RFI Request for Information ROM Rough Order Magnitude RX Receive scoss Shipboard Carry On Satellite System SLA Service Level Agreement SWaP Size, Weight and Power TMA Tail Mount Antenna TOC Tactical Operations Center TX Transmit