SOURCES SOUGHT
B -- This Request for Information requests the nomination of approaches, ideas, applications, and equipment that could function as the core Command & Control application and major subcomponents of Shipboard Protection System (SPS).
- Notice Date
- 9/29/2004
- Notice Type
- Sources Sought
- Contracting Office
- N00024 1333 Isaac Hull Avenue S.E. Washington Navy Yard, DC
- ZIP Code
- 00000
- Solicitation Number
- N0002404R6234
- Response Due
- 10/18/2004
- Description
- The Navy is interested in gathering information on the availability of equipment, systems, and approaches that will provide both short-term and long-term solutions to the current Anti-Terrorism / Force Protection (AT/FP) gaps and inefficiencies associated with self-protection of ?afloat? assets by providing a Shipboard Protection System (SPS) to all Naval vessels (minus submarines, but including MSC ships). PMS 480, the Anti-Terrorism Afloat Program Office within PEO Littoral and Mine Warfare, has been tasked to function as the Navy?s responsible acquisition activity for all Shipboard and Expeditionary AT/FP initiatives, and will manage any contractual effort associated with providing this SPS capability to the fleet. Vision / Objective System. To ensure / enhance the ability for Naval vessels to accomplish self-protection while moored to a pier, at anchor, or during restricted maneuvering, the Navy requires a fully integrated and seamless sensor, analysis, and response system that will provide the means for 360o situational awareness (SA) associated with and to counter asymmetric AT/FP threats around-the-clock with no increase in manning. The operational concept for the initial and objective systems will provide a flexible layered defense with situational awareness, deterrence, and engagement zones being defined by the system operator. This system should be modular and expandable and should support installation / operation on multiple ship classes / platforms within the Navy. The initial increment of this system must immediately provide the ability to support standalone operations for a single vessel and must be designed to ultimately be integrated with / within multi-ship and/or sho! re side AT/FP envelopes. This capability must be available, operable, and supportable in both overseas and continental U.S. ports and waterways. This capability will provide surveillance, detection, identification, tracking, deterrence, engagement, and command & control functions for both own-ship and own-ship deployable assets that can be applied to appropriately counter surface, subsurface, and airborne threats. Initial System Requirements. The initial ?standalone? system will be applied to multiple ship classes and will focus on dealing with / countering surface threats. This initial system will include a common core Command & Control (C2) application / capability, shipboard sensors, and engagement means. This capability should be designed as an ?open architecture?, net-centric compliant application that is capable of: 1. Controlling (ideally automatically/remotely) shipboard sensors and lethal & non-lethal engagement assets (e.g., electro-optics, hailing devices, guns, etc.) that will provide 360o coverage against surface threats from the waterline out (where practical), 2. Receiving data feeds and interoperating with the surface search radars and other intelligence inputs, 3. Generating, displaying, and using SA overlays (that can be shared with patrol boats launched from own-ship), 4. Providing automated features and decision aid tools that will assist the operator and watch officer in defending their ship. 5. Functioning as a ?plug & play? host for current and future capabilities, 6. Being eventually integrated with other existent C2 applications / the ship?s combat system. Call for Information. This RFI requests the nomination of approaches, ideas, applications, and equipment that could function, when assembled and integrated, as the core C2 application and major subcomponents of SPS. Additionally, request input on what the nominal installation set would be and request your notional timeline and cost parameters on what it would take to developed/manufacture/integrate/install your proposed solution set. All inputs received will aid the government in understanding the appropriate mix of technologies available and the acquisition approach the government will take. An SD&D RFP (with manufacturing options) may be developed and released as a result of inputs received.
- Record
- SN00684471-W 20041001/040929212404 (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 |