Hand-Held Link 16 - Request for Information (RFI)

The Project Manager for Tactical Radios (PM TR) seeks industry interest regarding availability of representative radios to meet Hand-Held Link 16 (HHL16) transceiver communications requirements supporting Army ground and ground-to-air communications. The goal of the HHL16 radio is to support secure ground and ground-to-air information exchange in Army, Joint, and Coalition Link16 tactical networks. Of interest are HHL16 radios currently under development by industry under Research and Development (RAD) efforts, or other efforts that can be quickly adapted to meet fielding timelines. Product Manager, Helicopter and Multi Mission Radios (PdM HAMMR) is interested in responses for products that can be delivered in production quantities that satisfy functional and performance requirements. Delivery of production representative radios at the earliest possible date is desirable. If there are dependencies upon Government sponsorship to support certification activities, PdM HAMMR may consider requests for sponsorship independently from requests to provide Government funding. The Government will use responses to this Request for Information (RFI) to refine requirements, therefore, we urge respondents not to self-eliminate if a requirement or some aspect of a requirement is not met; rather we encourage you to respond to the RFI with an explanation of why you think your offering is still acceptable (for example, a requirement is unnecessary or overly restrictive, drives cost or Size, Weight, and Power (SWaP), will be met with growth, or other reasons). The requirements include but are not limited to the following: support for multiple configuration sets, waveform version/capability synchronization, and operational availability. Test activities will be determined before the draft Statement of Intent or Request for Proposal (RFP) is released for consideration, but may include assessments of contractor laboratory facilities, on-site assessments of technical demonstrations (requirements, Manufacturing Readiness Levels), manpower, stress testing, size and power evaluation, interoperability with network management and key loaders, interoperability with other Link16 radios and evaluation of technology readiness levels (TRL). The expected total quantity of radios to be procured has not yet been finalized due to Service budget and force priorities but is expected to be approximately 600 radios. THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes - it does not promise a statement of intent or constitute an RFP or a promise to issue either in the future. This request for information does not commit the Government to contract for any supply or service whatsoever. Further, the Government is not at this time seeking proposals and will not accept unsolicited proposals. Respondents are advised that the Government will not pay for any information or administrative costs incurred in responding to this RFI; all costs associated with responding to this RFI will be solely at the interested parties' expense. Not responding to this RFI does not preclude participation in any future solicitation, if issued. If a Statement of Intent or RFP is released, it will be synopsized on the Federal Business Opportunities (FedBizOps) website. It is the responsibility of the potential responder to monitor this site for additional information pertaining to this requirement. Description The HHL16 should consist of a single-channel radio with interface(s) supporting operation with an End User Device (EUD), such as a Personal Digital Assistant (PDA) or laptop, and an appropriate cable for tethering the radio to the EUD. The HHL16 radio should interoperate with hosts supporting a Platform J interface. The HHL16 radio must have the ability, when paired with an EUD ("tethered" mode), to support transmission and reception of all Link 16 messages implemented within the EUD's message host application. It must support a minimum set of Link 16 messages when operated without an EUD ("autonomous" mode). Requirements Overview The HHL16 radio shall provide reliable, secure, Link 16 network connectivity, including J-voice using 16 kbps format and J28.2(0) text messaging (chat), in a small, tactical form factor in the physical environments in which an Army user will operate. The HHL16 radio shall have two primary modes of operation: ? Autonomous (radio only) Mode - where the radio enters the network and transmits Precise Participant Location and Identification (PPLI) messages, or PPLIs with emergency indication, supports J-Voice, supports a critical subset of J-series messages, and maintains synchronization. ? "Tethered mode - a hand held device or laptop computer, also known as an EUD is connected via a Universal Serial Bus (USB), Ethernet or microphone/headset connection to the radio to display mission data (e.g., PPLI, emergency, and friendly, hostile, or target tracks). Priority waveform(s): a) Link16 (with Concurrent Multi-Netting (CNM), Concurrent Contention Receive (CCR), and Link 16 Enhanced Throughput (LET) capabilities) - J-series (MIL-STD-6016/STANAG 5016) Security: a) Type 1 encryption b) SECRET Radio Frequency Bands: a) 960-1,215 MHz Certifications and Accreditations (please estimate timeline and indicate dependencies for Government sponsorship/funding for any not yet completed): a) Waveform Standards Conformance Testing/Joint Interoperability Test Command (JITC) Certification b) Approval of DD Form 1494 Application for Equipment Frequency Allocation for the Link 16 Spectrum (stage 3 to support testing, stage 4 for fielding) c) National Security Agency (NSA) High Assurance Product Certification d) Risk Management Framework (RMF) Certification and Accreditations (for the HHL16 vendor provided components (e.g. radio, etc.)) e) EMC Features Additional Security Criteria: System designs which employ software configurable cryptographic engines and host modern software-defined Cryptographic Equipment Applications (CEA) and Communications Security (COMSEC)/ Transmission Security (TRANSEC) algorithms are more desirable. Embedded cryptographic capability is required. Key loading capability must include support for current force devices such as the Simple Key Loader (SKL) and Link 16 crypto modernized Over-The-Air-Rekey (OTAR). Components capable of being handled and transported as unclassified Controlled Cryptographic Items (CCI) are preferred as these will facilitate supportability within the current logistical infrastructure. Proposed solutions must have a cryptographic architecture compliant with NSA Management Directive 237 Number 10 (MD-10). Environmental/Power/Electromagnetic Interference/Electromagnetic Compatibility (EMI/EMC) Requirements. HHL16 solutions must be able to maintain high-performance capabilities while exposed to environmental extremes such as Artic or desert temperatures, low or high atmospheric pressures, humidity, high precipitation rates, and blowing dust and sand. The HHL16 radio must have control features which will ensure a successful EMC Features assessment. Reliability. HHL16 reliability requirements are identified in terms of radio mean time between failure (MTBF). It is desired that the HHL16 radio has demonstrated quantifiable reliability via formal reliability testing and use in the field. It is also desired that the quantified HHL16 radio reliability be traced to hardware and software causes. Respondents are requested to include responses to the following outlined questions with supporting documentation along with their response to this RFI Questionnaire. All data received in response to this RFI marked or designated as proprietary will be fully protected from release outside the Government. 1. Table 1 (attached) lists capabilities the Government desires within the HHL16 radio. Please indicate when these capabilities will be available within your solution using the following key: 1) available now or within a year from now, 2) available in a future increment (provide estimate for when), or 3) not on your current roadmap. 2. For the capabilities you identified as available in a future increment in question 1 above, in the notes of Table 1 please describe the technical challenges preventing you from providing those capabilities within the current increment. 3. If selected, could you provide 7 radios (and ancillaries) for capability testing within 30 days of notification? If no, what is the lead time to provide 7 radios (and ancillaries) for capability testing? 4. What is the expected quantity range tables typically used by your company? 5. What test equipment, tools, test software and/or analysis methodologies do you use to verify Built In Test (BIT) detection and isolation? Please describe your test and analysis methodologies in detail. 6. Please describe any testing you have conducted on your proposed HHL16 solution (e.g., Environmental, Electromagnetic Environmental Effects (E3), EMI/EMC, interoperability, performance). 7. The Army would appreciate a brief description of your approach to software/waveform updates and integration of new capabilities. Specifically, would you provide upgrade to the waveforms at no cost to the government and for how many upgrades would that be? 8. Please indicate what MIL-STD-6016 functional area was assumed when determining what minimum set of messages to implement within your HHL16's internal host function. What is your process for revising this message set if additions, deletions, or modifications are required? Is there a limit to the number of messages that can be supported by the internal host? 9. The Army would like to establish government organic Hardware and Software sustainment to the greatest extent possible. a. What is your company familiarization with establishing organic repair capabilities at government facilities such as a government depot? b. What is your company's experience/familiarizations with facilitating a government depot? c. Do you have established/proven Technical Data Package and Intellectual Property licensing strategies for Hardware/Software required to support organic sustainment? To what degree would you provide one of the following: unlimited rights, Government purpose rights, limited rights? d. To what percent are you willing to support government organic repair/sustainment support? e. What is your experience with establishing and executing a Private Public Partnership with a government? f. What is your ability to support Government supply provisioning/cataloging? 10. What is your process for addressing obsolescence issues for fielded systems and spare parts? 11. What is your projected/current repair cycle time for in-warranty repairs? 12. Provide Manufacturing/production capability/capacity (how many radios can be delivered to the Government per month) and timeline to ramp up to this rate. 13. Provide costs/quantity cost range tables for the prototypes and production assets (Reference: Government currently uses cost points at 1-25, 26-50, 51-100, 100+ for similar product.). 14. Briefly describe how an Other Transaction for a Prototype Project with your company would enhance mission effectiveness of military personnel in the description and requirements sections outlined above. 15. What would be your company's recommended nature of the potential Other Transaction Agreement (i.e. expenditure based, fix amount, or a hybrid)? 16. In performance of a potential Other Transaction for a Prototype Project, does your company anticipate significant nontraditional defense contractor participation in the prototype project? If not, will your company be willing to share the cost of the prototype project? 17. Provide the following information: a. Company Name b. Address c. CAGE d. DUNS e. Point(s) of Contact (POC) f. Indicate status as a traditional or nontraditional defense contractor (see 10 USC 2371(b) and 10 USC 2302(9)) All responses to this RFI shall be submitted no later than 5pm (Eastern Time) on 12 February 2019.