Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF OCTOBER 10, 2003 FBO #0682
MODIFICATION

A -- Sources Sought Synopsis for the Maneuver Air Defense Concepts and Technologies for the Enhanced Area Air Defense System

Notice Date
10/8/2003
 
Notice Type
Modification
 
Contracting Office
US Army Aviation and Missile Command DAAH01, ATTN: AMSAM-AC, Building 5303, Martin Road, Redstone Arsenal, AL 35898-5280
 
ZIP Code
35898-5280
 
Solicitation Number
W31P4Q-04-R-R003
 
Response Due
11/7/2003
 
Archive Date
1/6/2004
 
Point of Contact
GAYLE NORMAN, (256) 876-2053
 
E-Mail Address
Email your questions to US Army Aviation and Missile Command DAAH01
(GAYLE.NORMAN@REDSTONE.ARMY.MIL)
 
Small Business Set-Aside
N/A
 
Description
NA This modification is a continuation of RFI information pertaining to W31P4Q-04-R-R003: MANEUVER AIR DEFENSE SYSTEM CONCEPTS AND TECHNOLOGIES It is recognized that industry and other government agencies could possess information relevant to development of the system concept or critical technologies that are not currently available to the MADS study team. For this reason, and in order to create an open environment for future competitions that may be associated with any MADS Program, the Aviation and Missile Research Development and Engineering Center (AMRDEC), on behalf of the RDECs and SMDTC, is providing this Sources Sought Notice as an RFI. S ystem concepts and critical technologies, for both tiers, emerging from this study and identified below are the subject of the RFI. No preconceived system or technology solutions are imposed for the MADS Program. However, the respondents will be credited for the incorporation of currently planned Army systems or technologies in their ideas. In addition, compatibility of proposed system concepts or technologies with support and organic assets expected to be in the field in the 2015 timeframe is essential. Any idea from any source that contributes to the MADS Program is encouraged. The respondent may also submit responses to other system and critical technology issues perceived as important, but not listed below. System Issues: The EAADS will attack and defeat RAM, UAV, CM, RW and limited FW aircraft, short ranged TBMs, and tactical SAMs as defined in the operational requirements above. The EAADS will include the following technical requirements: preferential defense and engagem ent, effectiveness, threat volume/duration, defended area, keep out range, strategic and tactical mobility, power requirements, size, weight, logistics, cost-effectiveness, all-weather-24 hour operations in the presence of battlefield obscurants, shoot-on- the-move (desired), and technology maturity in the 2010 timeframe for a 2015 Block 1 First Unit Equipped and 2020 for a Block 2 capability. The EAADS System is a UE asset to protect the force and high value assets and will interface with FCS and Future Fo rce battle management. The RFI seeks innovative ideas for the following system issues: system architecture, Shooter/Sensor/BMC4I functional distribution, effective battle management and control of EAADS??????s Sensors and Shooters, engagement timelines, management of EAADS asset s to achieve efficient destruction of small hard munitions, low cost-per-kill, low life-cycle cost, system and technology modeling and simulation, and demonstrated technologies to transition to System Development and Demonstration (SDD). Special emphasis will be given but not limited to the following: the lethality required to defeat the threat weapon(s) and the kill mechanism required to deliver that lethality; the delivery mechanism of the effect; the capability required to detect, classify, and identify the targets, and guide/direct the delivery mechanism; and the system construct required to perform the target acquisition functions, develop the threat picture, provide preferential defense, perform weapons pairing, and deliver the kill mechanisms to defe at the threat. System concept responses should include a list of critical technology issues associated with the respondent??????s concept. Critical Technology Issues: Inner Tier Shooters: Projectiles and Missiles: The weapon must provide an operational capability to destroy the aerial threats, particularly the RAM and tactical SAM targets, to a range of 10Km, utilizing a potential mix of final protective fires (gun launched projectiles) and short range missiles. Th e weapon technical requirements include the following: kill mechanism lethality, range and elevation/azimuth coverage, aerodynamic stability and control, kinematic maneuverability, intercept velocity, miss distance, probability of kill per shot, guidance navigation control (GNC) performance, initial poi nting accuracy, slew rate, reaction time, firing rate and quantity, time from weapon fire to target kill, transportability, power, and signature. The weapon will interface with the EAADS fire control; legacy Forward Area Air Defense (FAAD) command, contro l, and intelligence (C2I), Joint Tactical Radio System (JTRS), Enhanced Position Location Reporting System (EPLRS), and the BMC4I networks. The RFI seeks innovative ideas for the following critical projectile and missile technologies: warhead kill mechanism, muzzle velocity and round dispersion for projectiles, seeker/sensor, guidance and control methods including active flow control techniqu es and deployable micro-actuators, secure uplink/downlink techniques, on-board IFF capability, propulsion, advanced materials, component miniaturization and packaging, low weight, low cost, acceleration hardening, efficient ablation materials, ballistic ca se hardening, fuze survivability and safety, fuzing function and accuracy, and projectile and missile models and simulations. Special emphasis will be given but not limited to the following: the tradeoff between projectiles and missiles as a function of r ange, enhanced lift and reduced drag, seeker acquisition and tracking, superior end-game maneuverability, demonstration of the ability to guide a munition to intercept, miniaturized packaging, the compatibility of the inner tier munition with the MANPADS r equirement, a direct fire capability for self-defense or a multi-functional role, and delivery of a kill mechanism on the target with sufficient lethality to defeat the threat. High Energy Laser Weapons (HEL): The weapon must provide an operational capability to destroy the EAADS threats. The weapon will have the following requirements: range and elevation/azimuth coverage, lethality, dwell time, slew rate, firing rate and quantity, size, weight, power, and sign ature. The weapon will interface with the EAADS fire control, Legacy FAAD C2I, JTRS, EPLRS and the BMC4I networks. The RFI seeks innovative ideas for the following critical weapons technologies: power (fuel cells/chemical/battery), kill mechanism, pointing mechanism with automatic lock-on and tracking, advanced materials, environmental effects (chemical scrubbers), co mponent miniaturization and packaging, kill evaluation and target switch logic, target type identification and energy required to kill logic, battlefield combat identification embedded within laser tracking mode, and high energy laser models and simulation s. Special emphasis will be given but not limited to the following: the provision of adequate power to the weapon, dwell time on the target, and the ability to mature cost effective technology in a transportable maneuverable weapon configuration to addre ss the EAADS saturation threat. High Power Microwaves (HPM): The weapon must provide a means of destroying the EAADS threats. The weapon will have the following requirements: range and elevation/azimuth coverage, lethality, slew rate, pointing accuracy, illumination time, firing rate and quantity, power density, siz e, weight, and signature. The weapon will interface with the EAADS fire control, Legacy FAAD C2I, JTRS, EPLRS and the BMC4I networks. The RFI seeks innovative ideas for the following critical weapons technologies: prime and pulse power, energy control, RF source, frequency tracking, antenna enhancements, kill mechanism, sensing of target destruction/switching to new target, kill assessm ent, advanced pointing and tracking mechanisms, advanced materials, light weight, reduced size and signature, electro-magnetic interference/jamming reduction, component miniaturization and packaging, and high powered microwave models and simulations. Spec ial emphasis will be given but not limited to the following: the delivery of a kill mechanism on the target with sufficient lethality to defeat the threat. Outer Tier Shooters: The weapon must provide an operational capability to destroy the a erial threats, particularly UAV, CM, RW and limited FW aircraft, and short ranged TBMs, to a range of 40Km. The weapon technical requirements include the following: kill mechanism lethality, range and elevation/azimuth coverage, aerodynamic stability and control, kinematic maneuverability, intercept velocity, miss distance, probability of kill per shot, GNC performance, initial pointing accuracy, slew rate, reaction time, firing rate and quantity, time from weapon fire to target kill, transportability, po wer, and signature. The weapon will interface with the EAADS fire control, Legacy FAAD C2I, JTRS, EPLRS and the BMC4I networks. The RFI seeks innovative ideas for the following critical weapons technologies: multi-purpose warhead kill mechanism, seeker/sensor, guidance and control methods including active flow control techniques and deployable micro-actuators, secure uplink/downli nk techniques, on-board IFF capability, propulsion, advanced materials, component miniaturization and packaging, low weight, low cost, acceleration hardening, efficient ablation materials, ballistic case hardening, fuze survivability and safety, fuzing fun ction and accuracy, and weapon models and simulations. Special emphasis will be given but not limited to the following: seeker acquisition of low signature targets, in-flight datalinks, end-game maneuverability, cost effective engagement of a diversified threat, and the ability to upgrade planned Army systems to defeat the EAADS threat out to 40Km. Sensors: The EAADS surveillance sensor(s) will support multiple missions with the primary missions being the operational capability for battlefield surveillance, early warning, target identification and type classification for EAADS. The surveillance sensors will operate cooperatively with other sensors and FCS and have the following technical requirements: angle accuracy, resolution, detection/acquisition range, recognition/identification capability, target position and rate accuracy, single/multiple target tracki ng capability, field-of-view/field-of-regard, clutter rejection/dynamic range, mobility, size, weight, and communications. The sensor(s) will interface with the EAADS fire control, Legacy FAAD C2I, FCS, JTRS, EPLRS and the BMC4I networks. The EAADS fire control sensor(s) must have the operational capability to provide data to support engagement operations, surveillance and targeting and target assignment for EAADS weapons. Fire control sensor(s) will have the following technical requirements: field-of-vi ew, fire control sensor modules, prime power, antenna, signal processor, waveforms, packaging size and weight, distributed apertures, thermal management, target tracking, platform, and local communications requirements including latency, and compatibility with multiple weapons types. Fire control will interface with the EAADS BMC4I and with EAADS weapons. The RFI seeks innovative ideas for the following critical radar/electro-optic/infrared technologies: transmitter/receiver modules, prime power, antenna, signal processor, waveforms, packaging, distributed apertures, sensor fusion, thermal management, laser s, optics, detectors, scanners, platform compatibility, and sensor models and simulations. Special emphasis will be given but not limited to the following: maximizing RF transmit power within tightly constrained weight, space, and prime power limitations ; cost-effectiveness; and the type and number of sensors required to provide data to support EAADS functions that include surveillance, force warning, situational awareness, common operational picture, airspace management, counter battery, target identific ation and type classification, and inner tier fire control. The objective is to minimize the number and types of sensors required to perform the complete EAADS mission. BMC4I: The EAADS BMC4I communications and battle manager must provide operational capability for force operations planning, coordination, directing, and controlling of EAADS in support of the UA. The BMC4I links FCS passive defense, active defense, and attack operations to provide timely assessment of the AMD threat, and must include intelligence preparation of the battlefield, rapid dissemination of tactical warning, and post-strike assessment to the FCS element. For each EAADS operational element, a BMC4I node must provide the capability for planning FO and some EO. It must also provide the capability for coordinating, directing, and controlling E AADS engagement operations for surveillance in support of the UE and the UA. All nodes require embedded training capabilities. In developing concepts for the EAADS BMC4I system, the following technical requirements should be considered: Battery/Platoon FO and certain EO nodes, hardware/software/network architecture, battle management planning models and simulations, engagement planning models and simulations, threat discrimination, interoperability, communications. BMC4I communications and battle manage r will interface with EAADS and external surveillance and warning systems, intelligence assets, decision-making facilities, and EAADS fire control elements. The EAADS BMC4I fire control manager must provide engagement operations, RAM surveillance, plannin g, coordination, directing, and controlling of EAADS weapons in support of the UA. EAADS BMC4I fire control will have the following technical requirements: fire control nodes, engagement operations, architecture, fire control models and simulations, inter operability, platform, and local communications requirements including latency, compatibility. The EAADS BMC4I fire control will interface with the EAADS BMC4I communications and battle manager, fire control sensors, and with EAADS weapons. The RFI is seeking innovative ideas for the following BMC4I Communications and Battle Manager technologies: BM planning models and simulation tools, engagement planning models and simulation tools, and surveillance processing, BMC4I uncertainty analysis t ools, decision aids, impact point prediction, data processors, interoperability translator, and packaging. The RFI seeks innovative ideas for the following critical EAADS BMC4I fire control technologies: Engagement architecture, controlling of rules of en gagement and management by exception strategies, algorithms and software development, communications elements to reduce data latency and prioritize messages for critical engagement operations, data protocols and unique algorithms, use of expanded bandwidth , enhanced data rates, high-speed processing, span of control, rules of engagement, precision pointing, computational equipment, and BMC4I fire control models and simulations. Special emphasis will be given but not limited to the following: the quantity, speed, accuracy, and latency of data exchange between the fire control and weapon during multiple simultaneous engagements and the degree of centralization (or decentralization) of BMC4I functions to include surveillance, force warning, situational awaren ess, common operational picture, airspace management, counter battery, target identification and type classification, and inner tier fire control. The question is how should functions such as engagement operations be distributed between potential elements such as the acquisition sensor, operations center, fire control node, weapon platform, and weapon. The objective is to design the network architecture to execute the functions within the time and accuracy required to perform the complete EAADS mission. RESPONSE INSTRUCTIONS The system concept and critical technology ideas provided by respondents will be used to augment and refine the current government system concepts and associated critical technologies. These ideas must be provided in the form of a whitepaper described bel ow. Each whitepaper should address a single system concept or critical technology topic. Multiple whitepaper submittals are encouraged on any o ne or number of topics. We seek this information by 1700 hours (CST), 7 November 2003 in the form of unclassified electronic Microsoft Word files (1 file per topic) (recommended less than 5 Megabyte) attached to your email transmittal. The file name shou ld contain the information in whitepaper Sections 1. and 2. defined below (i.e., Inner Tier Shooter-XYZ Corp-1). If there are multiple papers on the same topic, then increment the file name sequentially (i.e., Inner Tier Shooter-XYZ Corp-2, etc.). Whitep apers submitted in response to this solicitation are limited to 10 pages, single-spaced, 11 font, Times New Roman, 1 inch margins, with embedded figures (if used) in Microsoft Word. The whitepapers must be organized according to the section outline below. Narrative lengths in parenthesis are suggested for each section, but the total number of pages is fixed. Anything beyond 10 pages will be discarded. 1. Technology Area (1 line) Choose from: MADS System, Inner Tier Projectile, Inner Tier Missile, Inner Tier HEL, Inner Tier HPM, Outer Tier Shooter, Surveillance Sensor, Fire Control Sensor, BMC4I Battle Manager and Communication, BMC4I Fire Control. 2. Contractor or Agency Identification (1 line) 3. Critical Issue (0.5 page) Name the issue and why you think it is critical. 4. Historical Approaches (if any) (1.5 pages) What were previous shortcomings that your idea overcomes? 5. System Concept or Critical Technology Idea (5 pages) Your idea for the system concept or the critical technology. Include substantiating modeling, simulation, or testing data, identifying your own contributions. Emphasize the innovative aspect of your idea and why it is feasible. 6. Relevant Experience (1 page) Include names of principal investigators, contract or IR&D identifier, title of effort, customer email address, U.S. dollar equivalent value, start and completion dates. 7. Technology Development Plan (2 pages) What would it take to mature your system concept or critical technology to transition to SDD in 2010? Include cost, schedule, and milestones. The whitepapers will be reviewed by government personnel and their support contractors. All information provided will be adequately protected. Any proprietary information must be identified. To be reviewed, the statement ??????Releasable to Government A gencies and their supporting Contractors for Review Only?????? must accompany any proprietary submission. The government reserves the right to request further clarification or request presentations to enhance our understanding of the respondent??????s sub mittal. All respondents will be notified of the disposition of their whitepaper. Material from respondent whitepapers, with the exception of identified proprietary information, may be incorporated into revisions of the MADS S&T Program Plan. Whitepapers that fail to comply with the instructions or present ideas not pertinent to MADS may not be reviewed. In accordance with Federal Acquisition Regulations paragraph 15.201 (e.), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Responses to this RFI shall be provided to AMRDEC Procurement Directorate as email attachments (??????return receipt requested?????? to provide the only indication of receipt) to Gayle.Norman@redstone.army.mil AND James.Baumann@rdec.redstone.army.mil or ma il responses to: US Army Aviation and Missile Command, AMSAM-AC-OS-RAX, ATTN: Gayle Norman, Redstone Arsenal, AL 35898.
 
Place of Performance
Address: US Army Aviation and Missile Command DAAH01 ATTN: AMSAM-AC, Building 5303, Martin Road Redstone Arsenal AL
Zip Code: 35898-5280
Country: US
 
Record
SN00449670-W 20031010/031008213224 (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 |
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.