Enhanced Bandwidth Efficient Modem (EBEM)

UPDATED 04 June 2025

Deadline extended to 27 June 2025 for submissions.

UPDATED 22 MAY 2025

Digital IF EBEM RFI

Solicitation Number:       TBD

Notice Type: Sources Sought

Synopsis:

Product Manager Wideband Enterprise Satellite Systems (PdM WESS), Fort Belvoir, VA, is seeking information from potential vendors for the contemplated purchase of Enhanced Bandwidth Efficient Modem (EBEM) Digital IF Modems (DMs) (EBEM DMs) and/or EBEM Virtual Modems (VMs) (EBEM VMs) to integrate with emerging Digital IF networks in DoD SATCOM Gateways. PdM WESS seeks EBEM DM/VM sources to capitalize on the transition of SATCOM ground segment architectures to Digital IF. “Digital IF EBEM” may be EBEM DM, “General Purpose Processor (GPP) based EBEM VM” (GPP-based EBEM VM), or “Field Programmable Gate Array (FPGA) based EBEM VM” (FPGA based EBEM VM).

Large and small businesses capable of delivering such EBEM DMs or VMs are requested to respond to this RFI. Such business may include those

• experienced in providing DoD SATCOM modems
• experienced in providing NATO STANAG 4486 compliant EBEM function
• experienced in developing DIFI Standard (IEEE-ISTO 4900-2021) or VITA 49.2 compliant Digital IF interfaces

Small business is defined by North American Industry Association Classification System (NAICS) "Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing" 334220, (750 employees or less).

PdM WESS is seeking to

• modernize existing DOD SATCOM Gateways
• address growth in DoD SATCOM user demand
• reduce EBEM footprint at DOD teleports
• capitalize on migration to the Digital IF ground segment architecture to gain advantage in terms of growth and resilience
• support management and control (M&C) automation

The target Digital IF ground segment architecture generally requires the following functions:

• Digital IF Modems, of which EBEM is the subject of this RFI
• Digital IF Combiner/Dividers
• IF Converters
• Digital IF signal chain management

The Government seeks information on the availability of equipment, subsystems, and/or software capable of addressing the following EBEM DM/VM need:

a. EBEM conforming to NATO STANAG 4486 and interoperable with the MD-1366.

b. Digital IF interfaces, interoperable with IEEE-ISTO 4900-2021 (DIFI Standard) Information Class 0x0000.

c. Bulk data traffic encryption conforming to NATO STANAG 4486 with a clear path to National Institute of Standards and Technology (NIST) validation IAW FIPS 140-3

d. Ethernet-based support for M&C automation through an Applications Programming Interface (API), documented to include a complete call library for use by third party integrators and M&C automation providers.

e. Clear path to necessary cybersecurity provisions

Information Requested:

Interested vendors are asked to provide the following specific information:

a. Company:  Name, address, and Commercial and Government Entity (CAGE) code.

b. Point of Contact:  Name address, phone number, and e-mail

c. EBEM Function:  The means of supporting the following aspects of EBEM emulation:

1. Payload:  Support for the EBEM waveform as identified in NATO STANAG 4486 Ed4 ANNEX F, specifically:
   1. “Embedded Channel” IAW Section 3.1.2 on pages F-6 through F-7, to support the features indicated in Section 3.2.5.2.1.2
   2. “User Data 1 Channel” IAW Section 3.1.3 on page F-7, to support internal Bit Error Rate Test (BERT) operation interoperability with legacy EBEM
   3. “User Data 2 Channel” IAW Section 3.1.4 on pages F-7 through F-8, to support Ethernet data traffic
2. Features:  EBEM emulation support IAW NATO STANAG 4486 Ed4:
   1. Selectable data traffic rate IAW ANNEX F Section 3.3.4.1.2.1 on pages F-13 and F-14
   2. Selectable symbol rate IAW ANNEX F Section 3.3.4.1.2.2 on pages F-14 and F-15
   3. Selectable scrambling IAW ANNEX F Section 3.3.4.2 on pages F-15 through F-16, “enabled” by default
   4. Selectable Adaptive Coding and Modulation (ACM) IAW ANNEX G Section 5.1 on pages G-53 through G-59, “disabled” by default
   5. Selectable Distant End Monitoring (DEM) IAW ANNEX G Section 5.3 on pages G-60 through G-81, “enabled” by default
   6. Selectable BERT patterns IAW ANNEX G Appendix 2 Sections 8.8.1 and 8.8.2 on pages G-2-47 through G-2-49
3. Bulk Encryption for Cover:  Support for selectable “encryption,” “enabled” by default, IAW NATO STANAG 4486 Ed4:
   1. ANNEX F Section 3.5 on pages F-61 through F-67, as applicable to “SMAT-authenticated circuits” to the exclusion of “PKI-authenticated (simplex capable) circuits”
   2. ANNEX G Section 5.4 on pages G-81 through G-107, as applicable to “SMAT-authenticated circuits” to the exclusion of “PKI-authenticated (simplex capable) circuits”
   3. SMAT loading and management, and likewise activation or deactivation of cryptography on any carrier, not to require EDIM Modem reboot or interrupt the operation of other carriers.
4. Waveform:  EBEM emulation to support NATO STANAG 4486 Ed4:
   1. Frame Format #1 (ITA) IAW ANNEX F Sections 3.3 through 3.3.4.2, “Scrambler,” on pages F-8 through F-16
   2. “Turbo Code” FEC and symbol mapping IAW ANNEX F Sections 3.3.4.3.1 through 3.3.4.3.1.7 on pages F-16 through F-34
   3. Support for these combinations of modulation and code rates (MODCODs), selected for power-bandwidth efficiency and listed in order of spectral efficiency:
      1. BPSK 1/2
      2. QPSK 1/2
      3. QPSK 2/3
      4. QPSK 3/4
      5. QPSK 7/8
      6. 16-APSK 1/2
      7. 8-PSK 3/4
      8. 16-APSK 2/3
      9. 16-APSK 3/4
      10. 16-APSK 7/8
      11. 16-APSK 19/20
   4. Ability to support “uncoded” operation IAW ANNEX F Section 3.3.4.3.1.6.5 on page F-33, for test and diagnostic purposes.
   5. Ability to also support “uncoded” operation excluding the EBEM modulation frame.

d. Digital IF Interfaces: The means of supporting adequate Ethernet interfaces:

1. In support of bandwidths as integrated, anticipating a Digital IF stream rate to RF bandwidth ratio of about 40 to 1 where 16 bit sample depth is employed throughout.
2. Providing redundant ports supporting spine-leaf architectures, with a minimum of dual 100GbE ports.

e. Digital IF Protocol: The means of supporting IEEE-ISTO 4900-2021 DIFI Standard compliance, specifically Information Class 0x0000. Explicit context packet field guidance will be provided by the Government to ensure plug-and-play interoperability and support for DOD CONOPS such as signal chain alignment.

f. Digital IF Performance:  The means of optimizing performance WRT these metrics:

1. Modulator Performance:  Carrier frequency accuracy, carrier power accuracy, digitization noise floor, spectral confinement, error vector magnitude (EVM).
2. Demodulator Performance:  Carrier frequency uncertainty, acquisition and reacquisition, synchronization retention, Doppler performance, bit error rate (BER) performance.
3. Demodulator Test Features:  Carrier frequency measurement, carrier power measurement, signal to noise ratio (SNR) measurement, BER testing, quasi-error free (QEF) indication.

g. M&C Provisions: The means of delivering a comprehensive API, and documentation to include a complete call set, for use by third party integrators and M&C automation providers.

h. Cybersecurity: The means of supporting Risk Management Framework (RMF) accreditation, and of supporting Zero Trust Architecture (ZTA) provisions to include:

1. External authentication based on server protocols such as Lightweight Directory Access Protocol (LDAP) or Active Directory (MS-ADTS)
2. Encryption of data at rest and data in transit
3. Auditing and logging
4. Other ZTA considerations

i. Physical Platform and Mission Integration:  Consider a “data center” type environment.

1. Is a 19 inch rack 1RU platform feasible for the function indicated?
2. What (multi-carrier) mission (i.e. Tx/Rx carrier pair) density (missions per 1RU) is realizable on a 1 RU platform or otherwise?
3. What costs per mission (i.e. cost-per-carrier-pair) are associated with such solutions?  In the case of VMs, please address total cost, host hardware plus VM software or firmware.
4. For VMs, what host platform attributes (hypervisor, operating system, CPU, GPU, memory, FPGA accelerator, network interfaces, etc.) are required to host such a VM? How many instances of such a VM could such a host platform support?

j. Acquisition Considerations:

1. Are commercial off-the-shelf (COTS) products contemplated with these functions in mind?
2. What similar products are on COTS product roadmaps?
3. Are any such products available immediately?  If so, then at what level of development are they available, e.g. fieldable or prototype?
4. What time horizon is realistic for fieldable versions of this product?
5. How would the Government best procure such products?
6. How can time-to-market be reduced?

k. Growth and Upgradeability:  What are the growth prospects of any such solutions in terms of:

1. Capability growth
2. Physical mission (carrier) density (Tx/Rx carrier pairs per 1RU)
3. Carrier data traffic and symbol rates
4. Applicability to other DOD SATCOM waveforms

Disclaimers:

This RFI is for planning purposes only and shall not be misconstrued to create an obligation on the part the of Government to enter into any agreement, nor to implement the actions contemplated, nor to serve as the basis for any claim for reimbursement for any costs associated with the preparation of responses submitted to the RFI. Questions regarding this announcement shall be submitted in writing by e-mail to the Contracting Officer. Verbal questions will NOT be accepted.

Answering this request:

Please furnish the above requested information by 13 June 2025. Please submit the requested information in PDF or Microsoft Word format to Contract Specialist Keith Magaw at keith.a.magaw.civ@army.mil.  

Contracting Office Address:

6590 Reconnaissance Street

Aberdeen, MD 21005

United States

Primary Point of Contact:

Keith Magaw

Contract Specialist

keith.a.magaw.civ@army.mil

Phone:  520-671-3696