Loren Data's SAM Daily™

FBO DAILY ISSUE OF MAY 18, 2006 FBO #1634
SOURCES SOUGHT

14 -- Control methods for Objective Force Active Protection System (OFAPS)guided inteceptor.

Notice Date

5/16/2006
 

Notice Type

Sources Sought
 

NAICS

541710 — Research and Development in the Physical, Engineering, and Life Sciences
 

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

W31P4Q-06-R-0197
 

Response Due

6/7/2006
 

Archive Date

8/6/2006
 

Small Business Set-Aside

N/A
 

Description

The purpose of this Request for Information (RFI) is to gather, from industry, possible control methods for the Objective Force Active Protection System (OFAPS) guided interceptor. Examples of possible technologies that may be applicable include, bu t are not limited to; canards, fins, thrust vector control, and discrete control thrusters. Other technologies and approaches can be considered. The general missile system requirements are as follows: " Missile Outer Diameter: 4 inches " Missile Length: 36 inches " Missile Flight Time: 0.5 seconds " Missile Weight: 30 lbs +/- 1 " Pointing Error: 1.5 mrad Response Details 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 one or number of topics. Responses to this RFI are due by 1700 hours (CST), 7 June, 2006 in the form of unclass ified electronic Microsoft Word files (1 file per topic, recommended less than 5 Megabyte) attached to your email transmittal. The file name should contain the technology area and the contractor or agency identification, shown below in Example 1. If ther e are multiple papers on the same topic, then increment the file name sequentially as shown below in Example 2 Example 1: Thrust Vector Control Method-XYZ Corp-01. Example 2: Thrust Vector Control Method -XYZ Corp-02, The whitepapers should be no longer than 10 pages, single-spaced, in 11 font, Times New Roman, with 1 inch margins, and embedded figures (if used) in Microsoft Word. The whitepapers must be organized according to the section outline below. White Paper Section Descriptions: 1. Technology Area (1 line). 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 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? Include a rough order-of-magnitude (ROM) cost estimate, start to finish schedule, and milestones. The whitepapers will be reviewed by Government personnel and Government support contractors. All information provided will be treated confidentially and will not be disclosed outside of the Government. Any proprietary information must be appropriately ma rked with appropriate Department of Defense legends in accordance with Defense Federal Acquisition Regulation Supplement part 227.7103-3. The Government reserves the right to request further clarification or request presentations to enhance our understand ing of the respondents submittal. 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 OFAPS Pr ogram Plan. RFI responses will be accepted from United States companies/ organizations only. Whitepapers that fail to comply with the above instructions, or present ideas not pertinent to OFAPS control system, 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. No award is intended as a result of this RFI. Information submitted in response this RFI is submitted at no cost to the Government. Responses to this RFI should be e-mailed to Gayle Norman (gayle.norman@redstone.army.mil ), as attachments, with a return receipt requested to provide indication of receipt. Responses may also be mailed to AMSAM-AC-RD-RB, BLDG 5400, Redstone Arsenal, AL 3 5898, ATTN: Gayle Norman.
 

Place of Performance

Address: US Army Aviation and Missile Command (Missile) ATTN: AMSAM-AC, Building 5303, Martin Road Redstone Arsenal AL

Zip Code: 35898-5280

Country: US
 

Record

SN01049116-W 20060518/060516220931 (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 |