Loren Data Corp.

'

 
 

COMMERCE BUSINESS DAILY ISSUE OF JUNE 9,1999 PSA#2363

US Army ARDEC, AMSTA-AR-PC, Picatinny Arsenal, New Jersey 07806-5000

13 -- RAPTOR INTELLIGENT COMBAT OUTPOST SOL DAAE30-99-R-0014 DUE 070999 POC Shelley R. Czapkewicz, Contract Specialist, (973) 724-3985 WEB: US ARMY TACOM-ARDEC Procurement Network, http://procnet.pica.army.mil/cbd/SRCSgt/060719991/060719991.htm. E-MAIL: Shelley R. Czapkewicz, sczapkew@pica.army.mil. The U.S. Army is conducting a market survey to determine whether a commercially available system exists that will meet the requirements for Raptor -- Intelligent Combat Outpost. The Raptor is an integration of smart/brilliant munitions, sensors, communication systems, computers and software which jointly result in a controlled autonomous munition field that is more flexible in usage, more lethal to the enemy and safer to friendly forces and non-combatants than previous existing systems. The Raptor system, as developed to date, consists of a Sensor Suite, a command and control Gateway, a Combat Engineer Control Station (CS) and software/hardware improvements to the Wide Area Munition (WAM). A commercially available Raptor System must satisfy the following requirements: (1) Field components must be hardened for transport (unpackaged) and drop from emplacing vehicles at 5 kph with automatic activation. The weight should not exceed 35 lb. (including batteries for its 90 day mission life). (2) Field components must have a non-lethal, anti-disturbance capability that precludes compromise of sensitive target algorithms and/or radio encryption keys and reports tampering to the CS. (3) Field components must be capable of autonomous operation, have an employed life compatible with WAM Product Improvement Program (PIP) PIP munitions (up to 90 days required), and have a field replaceable power source. (Use of standard Army battery or a readily available commercial battery is required.) (4) Field components must be operational in hot and basic climatic conditions after storage in hot, basic and cold climatic conditions. (5) The Sensor Suite, consisting of at least three (3) but no more than four (4) sensors arrays, must be capable of effectively monitoring at least a 1 km grid square of terrain and operating in all weather battlefield conditions. (6) The Sensor suite must be able to detect (the ability to distinguish an object of military interest), classify (the ability to distinguish by general type, i.e., light track, heavy track, heavy wheeled), and track (determine the approximate speed, approximate direction and approximate number of vehicles in the formation) threat vehicles and provide early warning to the WAM field's gateways and their CS. (7) The Raptor Sensor Suite must act as a sentry that supports arming of the Raptor controlled munitions, such as WAM, before the arrival of threat targets. A Raptor sensor suite must autonomously report the approach of heavy tracked, light tracked and heavy wheeled threat vehicles 70%-90% of the time, as an average among these target classes, when any of these vehicles come within 1 km of the center of the grid square where the sensor suite is employed. (8) Given detection, a Raptor sensor suite must have a 70% probability of determining and reporting the estimated location, speed, direction, and number of heavy tracked and light tracked vehicles that pass within 500m 2 kms of the center of the grid square where the sensor suite is employed. (9) A Raptor sensor must have a 70%-95% probability of detecting and reporting when any vehicle comes within 50m of its location. (10) A functional Raptor gateway, upon receipt of any command generated by the Raptor CS, must have a 90% probability of being able to detect a break in its communications network within ten (10) minutes of occurrence and alert the CS with the location of the break. (11) Raptor gateways/obstacles must be capable of being remotely programmed with several engagement tactics using the WAMs to support the commander s intent. Tactics include when to arm, directing multiple munitions to attack the same target simultaneously, directing multiple munitions to attack different targets simultaneously, and directing munitions to hold their fire against specific target types. (12) The Raptor communication network must provide a message completion rate of 80%-90% for messages not initiated by the CS. (13) Required communications ranges for Raptor components are as follows: (a) 35km between the CS and the furthest field component, (b) 5kms (Line of Sight) between sensor array units and gateways, (c) 500m (Line of Sight) between gateway and munitions, and (d) 5kms (Line of Sight) between gateways. (14) The Raptor field, non-munition components, must provide a 25%- 100 increase in the probability of kill performance of individual WAM munitions. (15) The Raptor CS must be able to: (a) send redeploy commands, receiving confirmation the message was acted upon within ten (10) minutes or less, (b) store and retrieve Raptor obstacle databases, such as report status of obstacles, sensor data, obstacle boundaries, etc. to Army Battle Command Systems (ABCS), (c) interface with ABCS systems and be compatible with the Joint Technical Architecture, (d) interface with the Centurion Remote Control Unit (RCU), to receive and send Raptor obstacle reports and pass control of the Raptor obstacles as required, (e) determine status of field components, including the WAM munitions, any time after emplacement, (f) controlling and monitoring at least 5—10 Raptor obstacles simultaneously, (g) hand-off control to another Raptor CS, (h) importing terrain data utilized by ABCS systems and utilizing standard NIMA terrain data, and (i) link to the Combined Arms Tactical Trainer/Synthetic Environment Core technology to execute training, mission planning and rehearsals for collective mission tasks from platoon through joint level in the virtual, live and constructive training environments. (A Raptor obstacle is defined as one sensor suite, 2 gateways, and 16 WAM munitions.) Responses to this notice must be submitted in accordance with Note 25. This is not a request for proposal, and should not to be construed as a commitment by the U.S. Army. See Numbered Note 25. Posted 06/07/99 (D-SN339963). (0158)

Loren Data Corp. http://www.ld.com (SYN# 0167 19990609\13-0003.SOL)


13 - Ammunition and Explosives Index Page