SPECIAL NOTICE
99 -- Request for Information for Joint Tactical Radio System ? Maritime/Fixed Station (JTRS-M/F) Cluster 3
- Notice Date
- 7/15/2003
- Notice Type
- Special Notice
- Contracting Office
- 4301 Pacific Highway Bldg OT4 Code 02, San Diego CA 92110-312= 7
- ZIP Code
- 00000
- Solicitation Number
- DON-SNOTE-030715-001
- Archive Date
- 8/1/2003
- Description
- DESCRIPTION: The objective of the Joint Tactical Radio System-Maritime/Fixed Station (JTRS-M/F) Cluster 3 program is to develop a Joint Tactical Rad= io System (JTRS) specifically for maritime and fixed station communication= requirements. The purpose of the development effort is to create the n= ext generation Maritime and Fixed Station Communication system which shall provide growth capabilities through an open system architecture that enables technology insertion through evolutionary acquisition or preplanned product improvements (P3I). JTRS-M/F shall be a multi-mode, multi-band, software definable radio system. This will result in increased operational flexibility, enhance= d interoperability and reduced life cycle cost. JTRS-M/F will be capable of transmitting voice, video, and data while operating in frequency bands from 2 MHz to 2000 MHz. In order to facilitate an orderly and cost-effective migration from legacy systems, the new JTRS-M/F shal= l maintain backward compatibility with selected legacy systems and provid= e a seamless technological transition path to support the next generation r= adio room. The JTRS-M/F will be defined as a complete end-to-end communicat= ions system with a combination of hardware elements, supporting software infrastructure, and government furnished waveform applications. This system will include all RF distribution and control equipment to support voice= , video, and data communications. The JTRS Program is a series of related but independent joint acquisiti= ons. The Army is the Service Acquisition Executive (SAE) for the joint activities executed by the JTRS Joint Program Office (JPO). The JPO is responsibl= e for defining, developing, validating, and maintaining the Software Communication Architecture (SCA) and acquiring software waveform applications. The JTRS-M/F (Cluster 3) Program Manager (Space and Naval Warfare Systems Command, P= MW 179) is responsible for developing JTRS-M/F hardware (with a SCA-compliant operating environment) and porting waveforms obtained from the JTRS JPO waveform repository to field the JTRS-M/F as a final consolidated product (as defined in the JTRS-M/F System Specification) in support of the Fleet and other service fixed stations. The key goals of the system are to ensure maximum scalability, modularity, and extensibility across all ship classes and fixed station= platforms. The anticipated release date for the official JTRS-M/F Cluster 3 Reques= t for Proposal (RFP) is in the summer 2003 timeframe with contract award anticipated 2nd Quarter of FY04. It is estimated that the successful offerors will= have approximately thirty (30) months from contract award to provide Enginee= ring Developmental Models (EDM) for testing. In the process of developing the Cluster 3 Request for Proposal, the Na= vy is interested in examining the benefits and technical feasibility of developing a ?core? part of JTRS that is common to Clusters 3 and 4. Cluster 4 is managed by the Air Force and is responsible for developing common JTRS hardware= for 65 plus airborne platforms. This CBD announcement is to invite potential offerors to submit informa= tion that allows the government to evaluate the benefits, disadvantages, and= technical feasibility of developing a ?core? part of JTRS that is commo= n to Clusters 3 and 4 specifically and to all Clusters in general. In generating a response, please address the following: =B7 What are potential common ?core? elements in the Clusters 3 (Mariti= me and Fixed Station) and Cluster 4 (Airborne) Joint Tactical Radio Systems? = In making this determination, please consider system architecture, softwar= e infrastructure, and interchangeable hardware modules. =B7 What are the pros and cons of having these ?core? elements common b= etween the Clusters? =B7 How would the ?core? elements be developed/shared between the Clust= ers if the Cluster Program Offices remained distinct acquisition programs with potentially different industry teams?What are the pros and cons of a merger of Clus= ter 3 and Cluster 4 into a single Cluster Program Office? Responses to the RFI must be received by 1600 EST on 30 July 2003 in writing and delivered to both the Cluster 3 Procurement Contracting Officer (PC= O) and the Cluster 4 PCO. Mark Lopez, the Cluster 3 PCO, can be reached at: Commander, Space and Naval Warfare Systems Command, 4301 Pacific Highway, San Diego, CA 92110-3127= , Attn: Mark Lopez, Code 02-33. Alternatively, responses can be emailed to mark.lopez@navy.mil or lopezm@spawar.navy.mil. Richard Fox, the Cluster 4 PCO, can be reached at: Department of the Ai= r Force, ESC/DIGR, 5 Eglin St., Building 1612, Hanscom AFB 01731-2100. THIS NOTICE OF INTENT IS NOT A REQUEST FOR COMPETITIVE PROPOSALS. The Government will not pay for any materials provided in response to t= his synopsis and submittals will not be returned to the sender
- Web Link
-
Click on the link to view the special notice
(https://e-commerce.spawar.navy.mil/command/02/acq/navhome.nsf/home= page?readform&db=3Dnavgenint.nsf&whichdoc=3DEFB2E78D63E7A89388256D63007= 4535F&editflag=3D0)
- Record
- SN00372068-W 20030717/030715214027 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |