Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF AUGUST 23, 2007 FBO #2096
MODIFICATION

A -- 1.4 Program Goals

Notice Date
8/21/2007
 
Notice Type
Modification
 
Contracting Office
N68936 Naval Air Warfare Center Weapons Division Dept.1 429 E. Bowen Rd - Stop 4015 China Lake, CA
 
ZIP Code
00000
 
Solicitation Number
N6893607R0061
 
Response Due
10/3/2007
 
Archive Date
1/26/2008
 
Point of Contact
Debra Zamarron (760) 939-9658 John D. Watkins, (760) 939-8158
 
E-Mail Address
Email your questions to Debra Zamarron
(debra.zamarron@navy.mil)
 
Description
The purpose of this amendment (amendment 0001) is to distribute the revised Section 1.4, Program Goals, provided in the attachment to the original synopsis (N6893607R0061). Also provided is the questions and answers which were discussed at Industry Day held at NAWCWD, China Lake on 15 August 2007, and the Industry Day Attendance Log. The following specifications have been designated as program goals and were defined in order to indicate the target characteristics and operating environments that are extremely important. The overall goal is to develop a weapon 0/0 sensor that is capable of attacking the following target types in the environments listed. 1. Provide a sensor that can detect and track, and report (to the DASH core processor) moving, relocateable, and stationary targets in adverse weather conditions. Sample Target Descriptions: ships, technicals (armed civilian vehicles), armor, air defense units, small boats, structures, and specific aim points on targets greater than 9 m2 (stationary or moving). Typical target radar cross sections for analysis can be: Ford Pickup: 10 dBsm; 7 meter boat: 15 dBsm; Armor: 13 dBsm; and a Frigate at 50 dBsm. For infrared analysis use an Effective Target Contrast of 2 C and an NET ≤ 130 milliKelvin. 2. Demonstrate the ability to detect and track moving targets with a minimum discernable velocity of no more than 5 knots, with 1 knot desired, and a maximum velocity not less than 80 knots. 3. Demonstrate the ability to detect and track moving targets executing weaving maneuvers up to 0.3 g's. 4. Demonstrate the ability to detect and guide to stationary targets in adverse weather conditions. 5. Demonstrate the ability to detect and track the targets in a variety of weather and environmental conditions defined as: a. Clear Weather: 23 km visibility b. Haze/Smoke/Dust: 5 km visibility c. Rain < 5mm/hour d. Fog < 0.5 km visibility e. High Humidity: 21 g/m3 f. 0/0 Conditions: Zero meters visibility, zero meters ceiling g. Day and Night h. Military Operations in Urban Terrain Environment i. Desert Environment (China Lake range representative) j. Rural Environment k. Mountainous Environment l. Forest Environment m. Jungle Environment n. Ice and Snow Environment o. Maritime Environment (littorals included, NAWCWPNS Sea Range Pt. Mugu representative) i. Maximum Sea State of 6 (winds to 33 knots) 6. Demonstrate a detection range in excess of 6 nmi against a 10 dBsm target. Available prime power is a function of the weapon and power source. Weapons with batteries can be assumed to have 100W available. Other weapons with generators can have up to 400 W available. If more power is required that will be a trade study at the weapon system level. 7. Demonstrate a sensor field of regard in excess of 50 degrees in elevation and azimuth (? 25? from boresight) 8. Demonstrate the sensor relative target location error supports a weapon system CEP of less than 3 meters. 9. Demonstrate the sensor has sufficient resolution to support Automatic Target Recognition algorithms and aim point selection on targets with a physical extent greater than 9 m2. Lock On After Launch (LOAL) requirement. 10. Demonstrate a sensor tracker than can maintain tracks on the five targets nearest the cue location until they fall out of the sensor field of regard. this tracking capability must be part of the sensor processor, not part of the DASH Core Processor. 11. Demonstrate the sensor in a 5" diameter form factor such as the DSU-33 volume. The goal is for the production DASH to fit entirely in the DSU-33 volume. For demonstration hardware, the "back end" components can exceed the DSU volume; however the aperture should remain in the DSU-33 form factor to simplify flight certification. 12. Demonstrate the sensor supports both lock on after launch (LOAL) and lock on before launch (LOBL) functionality for fire and forget operation. 13. Demonstrate off axis launch capability up to at least 25 degrees. A Zuni type application where the target is at least 25 degrees off the missile axis in primarily a lock on before launch application. 14. Demonstrate that the 0/0 sensor tracker can provide track update rates in excess of 5 Hz to the DASH core processor for the final ten seconds of flight. 15. Demonstrate that the sensor provides enough information to perform target identification or that the sensor design accommodates the inclusion of an imaging sensor into the DASH form factor. a. Target identification will include distinguishing combatant water and land craft from noncombatant water and land craft. b. Target identification includes distinguishing a machine gun equipped pick up truck from a noncombatant pick up truck. 16. Provide analysis that the 0/0 sensor can be produced affordably to support a DASH production cost of $15,000.00 per round for a 6,000 unit production rate for 5 years. The $10K portion for the 0/0 sensor is a rough estimate with the core processor and imaging sensor, if required, additional, but staying under the $15K total. 17. Demonstrate the sensor design does not require significant launcher and launch platform interface modifications. For the initial demonstration show the sensor test operation is compatible with existing aircraft and weapon interfaces. 18. Demonstrate the sensor subcomponent design is compatible with a variety of weapon airframes including Zuni, JDAM (DSU-33), JSOW, and Tomahawk. 19. Demonstrate the tracker output is compatible with the DASH core processor and sensor fusion algorithms, use of a STANAG or NATO format is desired. a. The DASH Core Processor design is to be determined b. The DASH Sensor Fusion algorithms are an out year development. c. Flexibility in message format and utilizing standard communication interfaces between subcomponents is desired. 20. Demonstrate the sensor is compatible with a captive carry environment on an F/A-18 C/D including flight elevations of 30,000 feet. 21. Demonstrate the ability of the sensor to detect and signal the core processor when the weapon is a specified distance from target impact. NOTE: DASH INDUSTRY DAY QUESTIONS AND ANSWERS, AND ATTENDEE SIGN-IN SHEET CAN BE FOUND IN THE ENCLOSED ATTACHMENT. NAICS Code = 541710 Place of Performance = N/A Set Aside Default = N/A
 
Record
SN01380030-W 20070823/070822071218 (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 |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.