SOURCES SOUGHT
A -- Automatic Rocket Identification
- Notice Date
- 7/29/2005
- Notice Type
- Sources Sought
- Contracting Office
- US Army Aviation and Missile Command (Missile), ATTN: AMSAM-AC, Building 5303, Martin Road, Redstone Arsenal, AL 35898-5280
- ZIP Code
- 35898-5280
- Solicitation Number
- W31P4Q05R0391
- Response Due
- 8/19/2005
- Archive Date
- 10/18/2005
- Small Business Set-Aside
- N/A
- Description
- The Army is conducting studies to define the elements and components for the next generation 2.75 inch diameter rocket launcher. The 2.75 Inch Rocket System has many different types of rockets. (A rocket type is defined as a motor and a specific ty pe of warhead. The entire rocket assembly is named for the warhead type.) More types are planned and projected for future development. Currently, one type or rocket is loaded into a specific set of tubes in the launcher, called a zone. Each zone can on ly handle one type of rocket at a time. The future rocket launcher will be capable of firing both new rockets as well as current stocks of MK66 motors. In order to achieve maximum flexibility for loading, it is desired that the launcher be able to fire a ny type of rocket loaded into any tube at any time. Ideally, the loaders will place any rocket in any tube, in a random fashion, and the system will detect and determine the rocket type. This concept is called a zoneless launcher, or infinite zoning . Automatic identification is seen as a means whereby sensors attached to each tube will read a signature tag, or an identifying mark, on each rocket and determine its type. This will be similar to barcode scanning at a retail checkout. This informatio n will be stored and used by the onboard Launcher Electronics Assembly (LEA) for tube selection during a fire mission. Examples of possible technologies that may be applicable to the Automatic Identification (Auto-ID) requirement include, but are not limi ted to: bar codes and readers, Radio Frequency Identification tags and readers, 2-D matrix and readers. Other technologies and approaches can be considered. In all cases, the identification process will take place after all rockets are loaded, and at the time that the aircraft crew turns on the weapons system power and energizes the LEA. This may occur several times during a single mission. Auto-ID may also be used to determine if rockets remain in the tubes after an attempt has been made to fire. The general requirements and operating environment for the Auto-ID are as follows: - The reader, or reading head, must fit between the tubes. This is defined as the space between three tubes, with outside diameters of 2.93 inches, arrange so that their centers form an equilateral triangle, 3.03 inches on a side. See the attached drawin g from the launcher Technical Data Package. It is provided to illustrate the area available between tubes for a reading head. - There is to be one reader head per tube. - The reader head may be up to 12 inches in length. - The maximum distance from the read head to the signature tag will be .060 inches, (1.5mm). - A window in the side of the tube may be use to allow the reader to see the identifying marking. The window material will be transparent in the spectrum that the reader works in. The window material must be able to work in a high heat environment wi thout losing transparency; the reader head must be able to see through scratches and dirt that will appear as rockets are loaded and fired. - The reader must be able to operate in a temperature range of -50oF to 140oF. It must also be able to survive brief temperature excursions up to 500oF. - The reader head must operate in the launcher high vibration environment. - The signature tag (e.g. barcode or similar item) must not add significantly to the rocket diameter. - The tag must be readily applicable to existing and future stocks of rockets with a minimum of equipment. - The tag must not require power, other than possibly the stimulus from the reader head (such as the case with RFID tags). - The tag must work when applied to any material that may be part of the rocket, to include the metal motor case or the metal warhead, and it must be readable by the selected reader head when the rocket is inside the aluminum launch tube. - Since the rocket may be randomly oriented in roll (sometimes even rotating d uring pre-fire carriage), the tag will rarely be directly under the reader head; therefore readability must be independent of the rocket roll orientation (Placing several ID tags around the rocket is acceptable.). - While repackaging of the reader head to fit within the allotted volume is likely, to the greatest extent possible, the device should use off-the-shelf components. - The reader must be able to accurately read and interpret the ID signature even when the launcher window and rocket ID tag are smeared with rocket exhaust residue and oily bore cleaner. - The signature tag must be durable, sustaining a minimum of 129 flight hours and 50 rocket firings, per tube, without loss of readability or reliability. - The Auto-ID sub-system must have a probability of an accurate reading in excess of .999 at all times and in all conditions. - The reading head must function in an electromagnetically noisy environment without degradation. - The Auto-ID sub-system must not produce any signals that will interfere with other systems in the launcher or on the platform aircraft. The Auto-ID subsystem must not produce any external signature detectable more than 10 feet from the aircraft under an y circumstances. - The Auto-ID solution should utilize low cost technology for this unique application, since there will be up to 19 units in a single launcher. Interested and capable sources are asked to submit a white paper compatible with Microsoft Word containing a description of appropriate technologies that they possess, or are conducting, and how these technologies could be applied to this project. Drawing s/sketches of the reader heads shall be submitted on CD. Responses should be made within forty five (45) days from publication of this notice. Of additional interest are the internal technical capabilities of the interested party in the above described activity. Responses to this request for information may not be submitted by fax or by electronic means; any so sent will be disregarded. Send five (5) copies of written responses to the attention of U.S. Army Aviation and Missile Command, AMSAM-AC-OS-RB/Building 5400, (Mr. Earnest Taylor), Redstone Arsenal, AL 35898-5254. Drawings will be provided by the technical POC upon request. Techni cal questions can be addressed to Mr. Don Davis, US Army RDECOM, AMRDEC, Propulsion and Structures Directorate, Redstone Arsenal, AL, 35898, telephone: (256) 876-5089, fax: (256) 876-2639, e-mail: don.davis1@us.army.mil. This is for information purposes only. This notice does not constitute an Invitation for Bids or a Request for Proposal, and it is not a commitment by the U.S. Army to procure products or services. The GOVERNMENT DOES NOT INTEND TO AWARD A CONTRACT ON THE BASIS OF THIS REQUEST FOR INFORMATION OR OTHERWISE PAY FOR THE INFORMATION SOLICITED. However, respondents to this Request for Information will not be excluded from consideration for separate contract services ancillary to this demonstration program or for contract participation in any potent ial follow-on hardware development activity. Acquisition POC is Ms. Elaine Cameron, 256-876-8761 (voice), 256-876-1631 (fax), elaine.cameron@redstone.army.mil (email), US Army Aviation and Missile Command, AMSAM-AC-RD-RB, Redstone Arsenal, AL, 35898. Con tracting Officer is Mr. Earnest Taylor, (256) 876-8762, earnest.taylor@redstone.army.mil.
- Place of Performance
- Address: US Army Aviation and Missile Command (Missile) ATTN: AMSAM-AC-RD-RB, Building 5400 Redstone Arsenal AL
- Zip Code: 35898-5280
- Country: US
- Zip Code: 35898-5280
- Record
- SN00858098-W 20050731/050729212401 (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 |