SOURCES SOUGHT
A -- JTRS High Frequency (HF) Waveform
- Notice Date
- 2/2/2006
- Notice Type
- Sources Sought
- NAICS
- 541511
— Custom Computer Programming Services
- Contracting Office
- ACA, ITEC4, Directorate of Contracting , 2461 Eisenhower Avenue, Alexandria, VA 22331-0700
- ZIP Code
- 22331-0700
- Solicitation Number
- W91QUZ-06-R-0017
- Response Due
- 3/10/2006
- Archive Date
- 5/9/2006
- Small Business Set-Aside
- N/A
- Description
- Request for Information, JTRS High Frequency (HF) Waveform 1.0 Description The Army Contract Agency, Information Technology, E-Commerce, and Commercial Contracting Center (ITEC4), in support of the Joint Tactical Radio Systems (JTRS) Joint Waveforms Program Office (JWPO), is seeking information from interested parties on how the JTRS program can address communications and interoperability requirements of and strategies for the acquisition of a High Frequency (HF) software waveform application that is suitable for the JTRS Software Defined Radios and compliant with: ** The Software Communications Architecture (SCA) and ** The Performance Specification for the JTRS HF Waveform and ** The NSA Unified INFOSEC Criteria (UIC)(Classified) This is a request for information only as defined in FAR 15.201(e). It does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. Responses to this notice shall not be construed as offers and cannot be accepted by the Government to form a binding contract. The U.S. Government will not pay for any information or administrative cost incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the interested partys expense. Not responding to this RFI will not preclude participation in any future RFP if issued. Release of reference technical documentation is limited to United States corporations and United States citizens. 2.0 Background The Department of Defense established the JTRS program to provide a family of software programmable radios based on the Software Communications Architecture (SCA). As such, the JTRS will provide reliable secure multi-channel voice, data, imagery, and video communications and eliminate communications problems caused by 'stovepipe' legacy systems. The JTRS will achieve these objectives through the procurement and fielding of a digital, programmable, modular communication system based on software-defined radio technology. JTRS will provide interoperability through the capacity to communicate with current tactical communications systems in the near term. In the future, JTRS will provide integrated information sharing through new waveforms to support joint operations. This interoperability will help meet the demands of U.S. Military forces and Joint/Coalition allies. The JTRS Operational Requirements Document (ORD), version 3.2, identifies four separate Threshold waveforms that constitute the HF Waveform to be developed. WF ID WF Name W8 HF-ISB ALE W9 HF-SSB ALE AJ W11 STANAG 5066 (HF Message Protocol) W12 STANAG 4529 (HF NB Modem) Additionally, ORD 3.2 identifies several other waveforms that use frequencies in the HF range that are being acquired under separate efforts for a variety of reasons. WF ID WF Name W10 Link-11/TADIL-A W14 HF ATC Data Link W21 Link-11B/TADIL-B As part of this waveform initiative, the JTRS program is evaluating the means by which they can establish a legacy HF capability within the JTRS family of communications products. This RFI solicits industrys views on the state of HF radio technologies and uses, insights into methodologies for developing a JTRS HF capability that will be interoperable with DoD/non-DoD HF standard radios, and comments on issues that could affect the affordability, reliability, and maintainability of the JTRS HF waveform. 3.0 Requested Information This RFI requests information from industry regarding the JTRS HF waveform requirements as well as information regarding possible acquisition strategies (i.e., phasing plans, characteristic groupings, etc.). The questions below provide a starting point for information input. 3.1 Identificat ion of current possible solutions: 3.1.1 Are there any existing technologies that could satisfy the JTRS HF requirements? Please quantify and explain any required modifications where possible. 3.2 Technology Information: 3.2.1 Based on the requirements in the Performance Specification for the JTRS HF Waveform, Version 2.0, January 2006 (Draft), (see Paragraph 4.0 below) which requirement(s) will be the primary cost and schedule drivers in the development of the HF waveform? 3.2.2 What recommendations, if any, are there for changes to the HF Waveform Performance Specification requirements that could positively affect cost/schedule? 3.2.3 Are there specified modes in the HF Waveform Performance Specification that are not used operationally today? 3.2.4 In responding to the above questions, specifically consider and address the following items. 3.2.4.1 MIL-STD-188-110B. Including the optional modes in the general requirements section and Appendix A; 16-Tone Differential Phase-Shift Keying (DPSK) mode, and Appendix B; 39-Tone Parallel mode, and Appendix C; HF Data Modem Waveforms for Data Rates above 2400 bps, and Appendix D; Subnetwork Interface, and Appendix E; Data Link Protocol, and Appendix F; HF Data Modems for Multiple Channel Systems. 3.2.4.1.1 ANDVT capability 3.2.4.1.1.1 Specifically address the relationship and association between the following optional mode requirements and the usefulness of providing ANDVT capability. 3.2.4.1.1.2 Advanced narrowband digital voice terminal (ANDVT) (thirty-nine tone) voice mode. If included, this mode shall be in accordance with MIL-C-28883 and STANAG 4197 to include error correcting codes and mode bits as part of the waveform application. 3.2.4.1.1.3 Sixteen-tone differential phase-shift keying (DPSK) mode. If included this mode shall be in accordance with Appendix A. 3.2.4.1.1.4 Thirty-nine-tone DPSK mode. If included, this mode shall be in accordance with Appendix B with additional functions as provided in MIL-C-28883 to include error correcting codes and mode bits as part of the waveform application. 3.2.4.1.1.5 Sixteen-tone DPSK mode for digital data applications. If included, the mode shall be in accordance with MIL-C-28883. 3.2.4.1.2 Address requirements for NBFM, AME and CW modes. 3.2.4.1.3 Address requirements to be over-the-air interoperable with all ARC-220 HF modes. 3.2.4.1.4 Address the requirement to interface with MD-1295/A Improved Data Modem (IDM), specifically addressing what 110B modem functionality should/could be embedded in HF Waveform (vice external operation) allowing interoperability with legacy HF systems using external IDMs. 3.2.4.1.5 Address mixed modes of ANDVT utilization (also KY-99/KY-100 modes) whereby the ANDVT Black digital output is used to drive a 110B serial tone modem. 3.2.4.2 MIL-STD-188-141B including Appendix A; Automatic Link establishment System (2G), and Appendix B; Linking Protection, and Appendix C; Third-Generation HF Link Automation, and Appendix D; HF Radio Networking, and Appendix E; Application Protocols for HF Radio Networks, and Appendix F; Anti-Jam and Anti-Interference Techniques, and Appendix H; Management Information Base for Automated HF Radio Network. 3.2.4.2.1 Multichannel operation shall provide, as a minimum, one nominal 3-kHz channel in the USB and one in the LSB (i.e., ISB; two independent, simultaneous, 3-kHz channels). 3.2.4.2.2 Specifically address the requirement to implement the Alternative Quick Call capability as defined in Appendix A. and the benefits of this functionality. 3.2.4.2.3 Address the increased performance capabilities of 3G ALE vice 2G ALE and the 3G requirement that 3G ALE must be implemented in addition to, but not in lieu of, Basic 2G ALE. Address pros and cons of spiral effort for implementation of 3G ALE. 3.2.4.2.4 Address the utility vice complexity of providing ISB functionality. 3.2.4.2.5 Address the HF networking capability benefits of being compliance to; Appendix D; HF Radio Networking, and Appendix E; Application Protocols for HF Radio Networks, and Appendix H; Management Information Base for Automated HF Radio Network. 3.2.4.2.5.1 Address the maturity of these HF networking requirements. 3.2.4.2.5.2 Compare and distinguish between these networking requirements and the requirement to be complaint with the data communications profile of STANAG 5066 (including all 5066 annexes). Address whether these HF networking standards (188-141B and 5066) complement each other or are stand-alone requirements. 3.2.4.2.5.4 Address pros and cons of spiral efforts to introduce HF networking compliant with 188-141B. 3.2.4.3 Address the impact on the HF Waveform of the requirement to be interoperable with the Army Automated Communications Engineering Software (ACES) that supports joint interoperability by providing communications and network planning. ACES combines the planning with key management, and automated key generation and distribution using the Army Key Management System (AKMS). 3.3 Programmatic Information 3.3.1 What acquisition strategies may be available that could reduce implementation technical, schedule, and/or cost risk? 3.3.2 What strategies may be available that could support post- production software support for the HF waveform? 4.0 Technical References. The Government has the following documentation available for use in formulating responses to this RFI: 4.1 Performance Specification for the JTRS HF Waveform, Version 2.0, January 2006 (Draft) 4.2 Software Communications Architecture (Version 2.2.1) Electronic copies of these references may be requested thru the JTRS JWPO. Requests should be submitted via e-mail to robert.middleton@hqda.army.mil and must include the name, company/organization, phone number, and e-mail address of a designated point of contact. 4.3 NSA Unified INFOSEC Criteria (UIC)(Classified) is available for review in the JTRS JWPO to properly cleared personnel. Requests to review the UIC should be submitted via e-mail to robert.middleton@hqda.army.mil and must include the name, clearance verification, company/organization, phone number, and e-mail address of a designated point of contact. 5.0 RESPONSES Interested parties should respond to this RFI with a white paper formatted as detailed below. An optional opportunity to provide additional material will be available at Industry Day (see below). Please be advised that all responses become government property. White papers, in Microsoft Word compatible format, are due to the JTRS JWPO no later than 15:00 EST, March 10, 2006. Responses shall be submitted via e-mail to gail.strickland@hqda.army.mil and robert.middleton@hqda.army.mil. Proprietary information, if any, should be minimized and, if present, clearly marked. To aid Government planners, please segregate proprietary information. 5.1 Section One: Administrative Information Provide company name and address and the phone number, fax number, and e-mail of a designated point of contact. 5.2 Section Two: Identification of current technologies Describe any technical capabilities that exist or could be modified to satisfy JTRS HF requirements. This description should include assumptions, feasibility, and risk for these options. 5.3 Section Three: Question Responses Shall be used to address the questions posed in Section 3 of this RFI. Any assumptions, technical feasibility, or overall risk considered in answering these questions should be addressed. 5.4 Section Four: Questions to the Government: Shall be used by responders to pose questions to Government for consideration and response at Industry Day. 5.5 Optional presentations If the ven dor wishes to provide the Government further information at the Industry Day session(s), they shall provide any briefing material, in Microsoft PowerPoint 2003 compatible format, via e-mail to gail.strickland@hqda.army.mil and robert.middleton@hqda.army.mil. These materials are due no later than 15:00 EST, March 28, 2006. As with the white paper, proprietary information, if any, should be minimized and must be clearly marked. 6.0 Industry day The Government plans to conduct an Industry Day for the JTRS HF waveform effort. The tentative date for the Industry Day is April 4, 2006 in Northern Virginia. In addition to the Governments presentation, the Government will be available to support one-on-one vendor presentations. If required, an additional day will be set aside for vendor presentation. Further details on the Industry Day will be published as addenda to this RFI NLT March 15, 2006. 7.0 Government Support Contractors The Government will utilize contractors from the following organizations to assist in the review and evaluation of RFI responses. These vendors have executed a Non-Disclosure Agreement (NDA) and are bound to safeguard any proprietary information supplied by responders. Additional companies may be added at a later date. Alion Science and Technology; Engineering, Management, and Integration (EM&I); SRA International; Booz, Allen, and Hamilton (BAH); Log/Sec Corporation MITRE. 8.0 Points of Contact This is a JTRS JWPO RFI. Non-technical, acquisition process questions regarding this request should be submitted by e-mail to gail.strickland@hqda.army.mil and robert.middleton@hqda.army.mil. Responses to non-technical questions will be answered via e-mail and announced to all responders.
- Place of Performance
- Address: ACA, ITEC4 Directorate of Contracting , 2461 Eisenhower Avenue Alexandria VA
- Zip Code: 22331-0700
- Country: US
- Zip Code: 22331-0700
- Record
- SN00979042-W 20060204/060202212404 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |