CNR RFI REVISED 26SEP20.pdf

REQUEST FOR INFORMATION REVISION #2

NAICS Code: 515111

I 1 | P a g e

NOTE: RFI-Revision 1- Extension to response date from 21; to 28 September 2020 RFI-Revision 2- Extension to response date from 28 September; to 05 October 2020

The U.S Army Program Executive Office Command, Control, & Communications-Tactical (PEO C3T), Project Manager Tactical Radio (PM TR), Product Manager Waveforms (PdM WF) and the Army Contracting Command (ACC)- Aberdeen Proving Ground (APG) are seeking information from industry to assist with developing and planning of a potential new requirement.

This is a Request for Information (RFI) to be used for market research purposes. This is not a Request for Proposals (RFP). This notice is issued solely for informational and planning purposes and it does not constitute a promise to issue an RFP in the future. Responses to this RFI are not considered offers or proposals and the Government will not award a contract based on this RFI. The Government is not soliciting for proposals and will not accept unsolicited proposals. Respondents are advised that the Government will not pay for the information submitted in response to this RFI or any costs incurred in responding to this RFI. All costs associated with responding to this RFI will be solely at the interested parties' expense. It is the responsibility of the potential responder to monitor the website for additional information pertaining to this requirement.

The information provided and received in response to this announcement is subject to the conditions set forth in FAR 52.215-3 -- Request for Information or Solicitation for Planning Purposes.

THIS IS A REQUEST FOR INFORMATION (RFI) NOTICE ONLY. THIS IS NOT A REQUEST FOR

PROPOSALS (RFP). NO SOLICITATION IS AVAILABLE AT THIS TIME.

1. Overview/Purpose/Description of Procurement

The ACC-APG is issuing this RFI on behalf of PEO C3T, PM TR, and PdM WF as part of ongoing market research for Combat Net Radio (CNR).

This RFI is to assess information on the Single Channel Ground and Airborne Radio System (SINCGARS) with FH2/CT2, FH3, and an ability to support future waveforms which may include different modulation techniques and faster frequency hopping (FH). SINCGARS will be used to support Fires and Air Defense in contested areas with limited data capabilities. The Government anticipates meeting modernization goal on or before FY24.

This RFI is for market research on the CNR capability available in Non-Developmental Item (NDI), Commercial off-the-shelf (COTS), Government off-the-shelf (GOTS), and Modular Open Systems Approach Technologies. CNR solutions under consideration will include Single Purpose / Single Band or Single Purpose/ Multiband SDR (Software Defined Radio) technologies. Submitted technologies can be either a replacement radio solution as a whole or upgrades/retrofits to the radios listed in Table 1 below.

The CNR solution will use the existing radio ancillaries as much as possible for the upgraded platforms.

The CNR solutions will fit into the existing SINCGARS Vehicle Amplifier Adapter (VAA, AM-7239) or describe alternative innovations.

Solutions are needed for Personal Radio (Manpack) and Vehicle Radio (single and dual mounted radio) configurations. There are potential requirements for both configurations. Responders may address either configuration or both configurations in response to this RFI.

I 2 | P a g e

Responders are encouraged to provide Rough Order Magnitude (ROM) price points for the following quantities (or other recommended price points/breaks for their radio replacement and/or upgrade solutions):

Quantity ROM Price 10,000 $ 100,000 $ 200,000 $ 300,000 $

The Government has not finalized a formal acquisition strategy.

Table 1. OPTIONS FOR REPLACEMENT OR UPGRADE

Family Method Explanation

SINCGARS

RT-1523E/F/G

Replacement New radio solution.

Upgrade/Retrofit

Voice /Data Encryption

Circuit Card replacement (Black/Red) to accommodate FH2/FH3, cryptographic modern requirements to include Tactical Secure Voice Cryptographic Interoperability Specification (TSVCIS), and Advanced Encryption Standard (AES) 256.

I 3 | P a g e

2. Scope of Effort

This effort may require the responder to provide engineering, software development, hardware development, technical support, lab operations, test and evaluation, system demonstrations, certification, integration, technical documentation, sustainment and supportability documentation, initial training, and program management. Upon completion of the engineering phase of this requirement, the Government may procure hardware to evaluate CNR solutions for fielding to operational units to collect feedback and inform future requirements documents and Basis of Issue (BOI). The Government may also procure an initial quantity of production kits for early testing/inventory purposes.

3. Technical Characteristics

The CNR is to provide assured voice (single channel voice radio running (FH3/CT2 (Cipher Text) (i.e., SINCGARS modernized waveform), and limited data for C2 including Fires and Air Defense Artillery (ADA) communications, designed primarily around the SINCGARS single channel radio. The radio’s Radio Frequency (RF) section must support VHF (30-88 MHz) operations. See Attachment A.

This CNR solution must support SINCGARS FH3/CT2, FH2 CT2, and FH2/CT1.

As a new radio solution or upgrade to radios from Attachment A, the following applies:

1. The CNR solution shall maintain the existing modes, functionality, and capabilities.

2. The CNR solution shall maintain interoperability between legacy and CNR upgraded radios with minimal operator action.

3. The CNR solution shall be interoperable with the modernized SINCGARS waveform.

4. The CNR solution shall be compliant with Tactical Secure Voice Cryptographic Interoperability

Specification (TSVCIS) v.2.2 or higher. This supports both legacy and joint coalition use.

5. The CNR solution shall support Black keying methods and Key Management Infrastructure (KMI) awareness. It shall also support legacy Saville Automatic Remote Keying (SARK) and modern Over-the-air rekeying (OTAR) capabilities.

6. For radios identified in Table 1, the CNR solution shall conform to current SINCGARS Size, Weight, and Power (SWaP) guidelines. See Attachment B.

7. For radios identified in Table 1, all design shall be delivered with documentation sufficient for any qualified contractor(s) to produce the hardware/software required for the CNR solution.

8. For radios identified in Table 1, all design shall be delivered with documentation sufficient for any qualified contractor(s) to logistically support the hardware required for the CNR solution.

9. For radios identified in Table 1, documentation shall be provided for sufficient operator training in hardware and software required for the CNR.

10. For radios identified in Table 1, the CNR solution shall have processing power capacity reserved for future waveform enhancement.

11. For radios identified in Table 1, the CNR solution shall have internal memory capacity reserved for future waveform enhancement.

12. All software/firmware used and/or changes in the CNR solution shall be submitted with appropriate documentation and the Government shall have Government Purpose Rights (GPR).

13. The CNR solution shall describe required TMDE (Test Measurement and Diagnostic Equipment) and sustainment levels of maintenance.

14. The CNR solution shall provide for (in design and logistical support) future upgrades to Communications Security (COMSEC) and Transmission Security (TRANSEC) capabilities.

I 4 | P a g e

4. Requested Information

Responders are encouraged to address the items below in their submissions:

1. ROM prices for the table in Section 1.

2. When responding to technical and manufacturing related items, please refer to your company’s

Manufacturing Readiness Level (MRL) and or Technology Readiness Level (TRL).

3. Any other costs associated with procurement of the responder’s radio solution (e.g. Non

Recoverable Engineering (NRE) cost, special tooling or equipment, mounts, costs associated to bring radio back to factory reset, etc.)

4. Identify past (limit to five (5) years) or current contracts that your company has been either prime or subcontractor that include NSA certification processes and involve cryptographic and COMSEC and TRANSEC requirements. What innovative approaches has your company taken to simplify and/or accelerate NSA certification activities, and what was the result (e.g., in terms of schedule, resource, risk)?

5. What information and/or documents are missing that would otherwise allow your company to submit a proposal?

6. Describe your company’s overall strategy on the technical requirements for radios listed in Table 1: Radio design supporting modular upgrades to COMSEC and TRANSEC subsystems (hardware and software, algorithm/mode and function) to attain higher performance (e.g., increased throughput, message completion rate, simplified keying, updated standards, etc.), and/or greater resiliency (e.g., increased EW-resistance (Electronic Warfare), anti-jam, etc.) with minimal impact (e.g. field upgradable).

7. Describe how the CNR solutions will comply with MIL-STD-810G, MIL-STD-2169B and MIL-

STD-464C.

8. Describe how interoperability will be maintained between legacy radios and upgraded radios.

9. Describe how your company would implement a mode that maintains backward compatibility for both voice and data (Fires and ADA).

10. Describe your strategy to support future waveforms which may include different modulation techniques and faster frequency hopping.

11. Describe your overall strategy to provide ROM pricing for evaluation and limited prototyping of your suggested solution(s) for the radio identified in Attachment A.

12. Describe and provide a breakout of how your company’s R/T solution including ancillaries will reuse or replace existing ancillaries for the CNR solution.

13. Does your company have obsolescence issue(s) that need to be addressed in your suggested solution(s)? If so, how does your company plan to address current and projected obsolescence issue(s)?

14. Describe any unique operator training required for your suggested solution(s).

15. Describe how your suggested solution(s) will be implemented into existing physical configurations.

Is your suggested solution(s) a field level or depot level modification? For your proposed ungraded solution, what maintenance level can implement the upgrade?? Will special tools and/or maintenance training be required to implement the suggested solution(s)?

16. Describe any technical, logistic, and programmatic risks your company foresees in executing the suggested solution(s).

17. The Government is exploring Government as well as contractor / industry cryptographic modules / solutions. If required, when does the Government cryptographic module solution need to be provided for your company have to incorporate into your suggested solution? What information on Government cryptographic standards would your company need to design to?

I 5 | P a g e

18. Will your company be using a proprietary cryptographic chip in your suggested solution(s)? Has it been used in another radio/system? What System(s)? Has your company independently marketed that cryptographic chip to other Customers (i.e., outside of your company) and for what purpose?

In what quantities? Will your company be willing to provide the cryptographic chip in bulk quantities? Provide reasoning in either case.

19. Does your company currently have a qualified second source contractor? Please describe your company’s experience in qualifying secondary sources Low Rate Initial Production (LRIP).

What would be the anticipated lead time and at what milestone would such a process be inserted in your suggested solution? What does your company foresee regarding Government participation in qualifying second source?

RESPONSE GUIDELINES:

Interested parties are requested to respond to this RFI with a white paper. Submissions should not exceed 30 single-spaced pages, 12-point type with at least one-inch margins on 8 1/2” X 11” page size.

Responses must specifically describe the responder’s ability to meet the requirements outlined in this RFI.

Oral communications are not permissible. https://beta.sam.gov will be the sole repository for all information related to this RFI.

Companies who wish to respond to this RFI should send responses to gregg.g.martin.civ@mail.mil no later than 10:00 AM Eastern Time (ET) Zone on 21 28 September 05 October 2020.

INDUSTRY DISCUSSIONS:

Government representatives may choose to meet with respondents and hold one-on-one discussions. Such discussions would only be intended to obtain further clarification of potential capability to meet the requirements, including any development and certification risks.

QUESTIONS:

Questions regarding this announcement shall be submitted via email to gregg.g.martin.civ@mail.mil Verbal questions will NOT be accepted. The Government will not reimburse companies for any costs associated with the submissions of their responses.

https://beta.sam.gov/ mailto:gregg.g.martin.civ@mail.mil

I 6 | P a g e

DISCLAIMER:

This Request for Information (RFI) and is not a Request for Proposals (RFP). This RFI is not to be construed as a commitment by the Government to issue a solicitation or ultimately award a contract.

Responses will not be considered as proposals nor will any award be made as a result of this RFI.

All information contained in the RFI is preliminary as well as subject to modification and is in no way binding on the Government. The Government does not intend to pay for information received in response to this RFI. Responders to this invitation are solely responsible for all expenses associated with responding to this RFI. This RFI will be the basis for collecting information on capabilities available. This RFI is issued solely for information and planning purposes. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received in this RFI that is marked “Proprietary” will be handled accordingly. Please be advised that all submissions become Government property and will not be returned nor will receipt be confirmed. IAW FAR 15.201(e) (Federal Acquisition Regulation), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract.

*Prospective contractors are hereby notified that the Government may utilize Systems Engineering and Technical Assistance (SETA) support contractor services being provide by Booz Allen Hamilton, JANUS Research Group, and Sev1Tech in the review process of white papers. If interested vendors would like to establish a Proprietary Data Protection Agreement (PDPA) between the listed Vendors above please contact ACC APG for coordination.

REQUEST FOR INFORMATION

I 7 | P a g e

ATTACHMENT A.

SINCGARS Mode Name

PT CT CT2

SC FH/

FHM

FH2/

FH2M

FH3/

FH3M SC FH/

FHM

FH2/

FH2M SC

Reserved

FH2/

FH2M

FH3/

FH3M

1. Voice X X X X X X X X X X X

2. 1200 bps SINCGARS Data Mode

(SDM) T T T X T T T T T T X

3. 2400 bps SDM T T T X T T T T T T X

4. 4800 bps SDM T T T X T T T T T T X

5. 16 kbps transparent data mode T T T X T T T T T T X

6. 1200 bps Enhanced Data Mode

(EDM) T T T T T T T T T T T

7. 2400 bps EDM T T T T T T T T T T T

8. 4800 bps EDM T T T T T T T T T T T

9. 9600 bps EDM T T T T T T T T T T T

10. 1200 bps RS-232 EDM T T T T T T T T T T T

11. 2400 bps RS-232 EDM T T T T T T T T T T T

12. 4800 bps RS-232 EDM T T T T T T T T T T T

13. 9600 bps RS-232 EDM T T T T T T T T T T T

14. GPS Time X T T T X T T X T T T

15. Electronic Remote Fill (ERF) transmit and receive X T T X X T T X T T X

16. SARK receive X X X X T T T X X X X

17. 5 kHz/10 kHz channel offset O X X X O X X O X X X

18. Scan Mode O X X X O X X O X X X

19. F1/F1 Retransmit (voice, data only if packet mode is also implemented) O O O O O O O O O O O

20. Homing Mode (Aircraft Radio only) O O O O O O O O O O O

21. Cue Mode transmit X T T X X T T X T T X

I 8 | P a g e

ATTACHMENT A, CONT.

22. Cue Mode receive X T T X X T T X T T X

23. Radio Based Situational Awareness (RBSA) X X X X T T T T T T T

24. SARK transmit (applies to Cryptographic Sub System

(CSS))

X X X X O O O O O O O

NOTES:

1. PT – Plaintext, CT – Ciphertext, CT2 – Ciphertext 2, SC – Single Channel, FH – Frequency Hopping, FHM – Frequency Hopping

Master, FH2 – Frequency Hopping 2 (EOM – Enhanced Operational Mode), FH2M – Frequency Hopping 2 Master, FH3 – Frequency Hopping 3, FH3M – Frequency Hopping 3 Master

2. T: Threshold, Td: Delayed Threshold, O: Objective, X: Not Supported

3. F1/F2:

4. F1/F1:

I 9 | P a g e

ATTACHMENT B.

(Advanced) System Improvement Program (ASIP) External Interface/Capabilities

Interface Connector Notes

Steerable Null Antenna Port (SNAP) System Also used to interface with other external equipment

External Control System RS-232 interface to remote front panel functions

ICM (Intercom) System Connects to the Vehicular Intercom System Vehicle Power Input System Powers radio when installed in Vehicle

Adapter

RF Power Interfaces (PA) Interfaces System RF PA Controls and Status 2/6 Wire Remote Control Interface System There are three modes of operation (Modes

A, B, and C) which are available for remote control. These modes are mutually exclusive and are based entirely on the type of equipment at both ends of the two-wire link.

Mode A and B allow remotely locating the Black Side of a SIP from the Red side, and the COMSEC side of an ASIP.

Mode C allows remote controlling the ASIP from an Intra Vehicle Remote Control

(IVRC).

Retransmit (RXMT) Aud/Data/RXMT Ability to connect two ASIPs as Retransmit

Station Audio Aud/Data/RXMT Handset Mil-Std -188-RF114 Data Aud/Data/RXMT Synchronous Data RS232 Data Aud/Data/RXMT RS-232 Async Data Packet Data Aud/Data/RXMT X.21 data interface to Internet Controlled

(INC)

Audio Aud/Fill Handset Fill Aud/Fill COMSEC and Electronic counter-counter-measures (ECCM) Fill Interface

GPS Interface GPS Input for External GPS and Out for Internal

GPS

Enhanced Display Control Unit (ECDU) Interface

GPS Interface to ECDU when Internal GPS is installed