MODIFICATION
15 -- REQUEST FOR INFORMATION (RFI) For Vertical Unmanned Aerial System (VUAS)
- Notice Date
- 9/15/2006
- Notice Type
- Modification
- NAICS
- 334511
— Search, Detection, Navigation, Guidance, Aeronautical, and Nautical System and Instrument Manufacturing
- Contracting Office
- Department of the Navy, Naval Air Systems Command, NAVAIR HQ, Building 2272 47123 Buse Road Unit IPT, Patuxent River, MD, 20670
- ZIP Code
- 20670
- Solicitation Number
- Reference-Number-0010187687
- Response Due
- 10/10/2006
- Archive Date
- 10/31/2006
- Point of Contact
- Joseph Pestar, Contract Specialist, Phone 301-757-8949, Fax 301-757-8959, - Jessica McGee, Contract Specialist, Phone 301-757-8941, Fax 301-757-8959,
- E-Mail Address
-
joseph.pestar@navy.mil, jessica.mcgee@navy.mil
- Description
- Amendment 1 to Solicitation Reference Number-0010187687 is issued to: Provide additional VUAS data and descriptions. The government will not release the Vertical Unmanned Aircraft System (VUAS) Initial Capabilities Document (ICD) or Concept of Operations (CONOPS). VUAS performance requirements provided in the original RFI and data requested of industry remain unchanged. (2) Extend deadline for submission of requested data to close of business October 17, 2006. This notice does not constitute an Invitation for Bids or a Request for Proposal, and it is not a commitment by the Department of the Navy to procure products or services. All questions pertaining to this notice should be submitted in writing to Mr. Joseph Pestar, Contract Specialist, Email joseph.pester@navy.mil or Ms. Jessica McGee, Contracting Officer, Email jessica.mcgee@navy.mil. In accordance with the Vertical Unmanned Aircraft System (VUAS) Initial Capabilities Document (ICD) that established a requirement for a VUAS as a follow-on to the Pioneer Unmanned Air Vehicle (UAV) System, the Department of the Navy is conducting an Analysis of Alternatives (AoA) to determine VUAS performance capability requirements. The purpose of this RFI is to obtain current industry data on systems / air vehicles capable of meeting or exceeding Marine Corps VUAS capabilities required to support Expeditionary Maneuver Warfare (EMW) and Ship-To-Objective Maneuver (STOM). To assist industry in providing the necessary detail for the Marine Corps to evaluate current technology, outlined below are VUAS (1) key considerations, (2) operating concepts, and 3) Notional Performance. (1) Key Considerations: 2015 Initial Operational Capability (IOC) to replace the current Marine Corps tactical UAS Responsive and persistent ISR, providing targeting products to the maneuver element commander, and serving as a communications relay Seamless integration into a network-centric C2 environment Shipboard compatibility and scalability to allow deployment with all levels of the Marine Air Ground Task Force (MAGTF) (2) Operating Concepts: The VUAS concept is closely linked to MV-22 and the F-35B JSF operations, and will require speeds and ranges to support these aircraft. The minimum speed required would be 200 kts, but 240 kts would be preferred. The VUAS must be expeditionary, i.e., operate simultaneously with other organic MAGTF aircraft from all air-capable ships and operate from austere, forward operating locations with minimal personnel and logistics footprint. The system must be highly survivable, using passive measures to the greatest degree possible to reduce system signature, and low visual, infrared and acoustic signatures, and reduced Radar Cross Section (RCS) to operate in a high threat environment. The VUAS will have a reduced physical footprint and require no more than, or fewer, personnel to operate the system compared to current systems. With reduced manpower to maintain and operate the system, it must have a high degree of automation and reliability to successfully support continuous operations by a scalable JTF/MAGTF. The entire VUAS system must be scalable to support MAGTF operations from the relatively small Special Purpose MAGTF level to the larger, reinforced Marine Expeditionary Force, be capable of supporting any Joint Task Force (JTF) to which a MAGTF is attached, and operate as a detachment without the loss of functionality or capability. The system must be capable of reaching ranges to provide Combat Search and Rescue (CSAR), Tactical Recovery of Aircraft and Personnel (TRAP), target acquisition/designation and battle damage assessment for the F-35B and other strike platforms. The system must have sufficient air vehicle endurance to support EMW / STOM operations necessary for future Seabased / Joint Forcible Entry Operations, with 10 days continuous airborne coverage at a range of 100 nm from the seabase. Time on station must be sufficient to support the various missions and will be based upon the speed and distance required to arrive on station. A time on-station of 4.0 hrs at 200 nm is envisioned. During operations, the system must have the ability to be retasked either while airborne or, after a short redirection period on the ground to refit its payload and/or refuel. The system should be designed to provide maximum agility and the ability to respond to meet the parameters of a six hour planning cycle. The system must be easily transportable in theater by organic MAGTF aircraft, thereby possessing some degree of self-deployability and not rely on strategic lift to relocate once in theater. The system must be all-weather capable to include operations in day/night, and adverse weather (rain, salt spray, fog, dust, transient icing and temperature extremes). The system should strive to use common ?plug and play? modular payloads and a common ground station that can easily integrate and be interoperable with other current joint or future systems that will be employed by the JTF in the 2015 timeframe. Information obtained from the system must be readily distributed through the network to various supported units. The information must be relevant to the user and in a format useful to the requestor. (3) Notional Performance: The Navy intends to pursue an evolutionary acquisition strategy. Proposed for increment one is a reliable and ship-deployable UAS that provides a baseline electro-optical / infrared, and radio communications capability. The initial mission areas envisioned for the first increment are as follows: - Timely Intelligence, Surveillance, Reconnaissance - Target acquisition, identification, and designation - Airborne (beyond line of sight) communications relay service of voice, data and imagery Additional future Modular Mission Payload (MMP) sensors and aircraft systems to support mission requirements could include: - Imagery Intelligence (IMINT), Signals Intelligence (SIGINT), Measurement and Signature Intelligence (MASINT) - Intelligence data (Order of Battle) and Intelligence Preparation of the Battlefield refresh and support - Screen areas beyond and/or adjacent to JTF/MAGTF objectives - Indication and warning of weapons of mass destruction employment - Detached escort to screen rotary wing and fixed wing missions - Surface-to-air missiles (SAM)/anti-aircraft artillery indication and warning - Information to complete final coordination on objectives and targets - Precision-guided munitions and sub munitions delivery - Battle Damage Assessment (BDA) - Anti-air warfare capability - Very shallow water mine and beach obstacle detection
- Record
- SN01145458-W 20060917/060915221728 (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 |