SOURCES SOUGHT
10 -- Sources Sought for Development of the Hydra-70 Modernized Rocket Launcher
- Notice Date
- 5/12/2011
- Notice Type
- Sources Sought
- NAICS
- 332995
— Other Ordnance and Accessories Manufacturing
- Contracting Office
- AMCOM Contracting Center - Missile (AMCOM-CC), ATTN: AMSAM-AC, Building 5303, Martin Road, Redstone Arsenal, AL 35898-5280
- ZIP Code
- 35898-5280
- Solicitation Number
- W31P4Q-11-R-0169
- Response Due
- 6/27/2011
- Archive Date
- 8/26/2011
- Point of Contact
- Sarah Marcial, 256-876-4168
- E-Mail Address
-
AMCOM Contracting Center - Missile (AMCOM-CC)
(sarah.k.marcial@us.army.mil)
- Small Business Set-Aside
- N/A
- Description
- The US Army Aviation and Missile Command (AMCOM) Program Executive Office (PEO) Missiles and Space (M&S), Program Management (PM) Joint Attack Munition Systems (JAMS) is seeking information on industry's ability to provide a Modernized Rocket Launcher (MRL). The overall objective of the MRL is to improve the reliability of the Hydra 2.75-Inch Weapon System while also providing for growth to support future advanced Hydra rockets. The intent of this Request for Information (RFI) is to support a market analysis by identifying sources capable of developing the MRL; to identify potential MRL concepts supporting the requirements described within; to support Government analysis and trade studies; and to understand industry's ability to develop and qualify the MRL within a 36 month time period. This RFI is used for information purposes only and does not constitute a solicitation. No contract or other binding instrument will occur as a result of this request for information. Definitions: The following definitions are applicable to this RFI: (a) Best Value - A balanced solution that meets all threshold requirements, meets or has a clearly identified path to meet all objective requirements, utilizes a design approach that enables growth and upgrades, is applicable to the Joint Services, addresses ownership cost and supports a low-risk development effort. (b) Smart Interface - Provides for power, digital communication and discrete signals between the MRL and a smart interface rocket. The signal characteristics are defined in MIS-ICD-55810 and include Operating Power (28VDC nominal at 140 Watts continuous); Safety Enable Power (28VDC nominal at 140 Watts up to 2 seconds); Communication (wired Fibre Channel and EBR-1553); and three discrete signals. A maximum of four Smart Interface 2.75-Inch Hydra Rockets are permitted to simultaneously receive power from the launcher. The smart interface physical interface is not yet specified in MIS-ICD-55810. (c) Weapon - The terms weapon, munition, rocket, 2.75-Inch Hydra Rocket and Hydra-70 Rocket are synonymous and refer to an all-up-round rocket configuration. (d) 23 pound (lb) Rocket - A notional rocket with a weight of 23 lbs and having an overall center of gravity 30.0 inches forward of the aft end of the assembled rocket. (e) 31 lb Rocket - A notional rocket with a weight of 31 lbs and having an overall center of gravity 38.8 inches forward of the aft end of the assembled rocket. (f) 35 lb Rocket - A notional future rocket with a weight of 35 lbs; utilizing a MK66MOD4 or compatible rocket motor; and having an overall center of gravity 41.5 inches forward of the aft end of the assembled rocket. (g) Smart Interface 2.75-Inch Hydra Rocket - A 35 lb rocket which also provides a smart interface. The smart interface is physically located on the rocket not less than 52 inches from the aft end of the rocket and not more than 60 inches from the aft end of the rocket. A smart interface rocket is the same as a smart interface 2.75-Inch Hydra Rocket. (h) Maintenance Facility - A facility capable of fully servicing the MRL to include functional tests, performance tests, fault detection and isolation, fault log data extraction, reprogramming, health monitor data extraction, repair, refurbishment and any required maintenance beyond normal cleaning. (i) Unless otherwise specified, any reference to the launcher or the MRL applies to all launcher configurations. (j) A tube is a historical description of the rocket-carrying component or subassembly of the rocket launcher. In the context of this RFI, one tube carries and provides interfaces to one loaded rocket at a time. While a tube is the historical solution, the RFI does not mandate a tubular solution. (k) The word shall indicate a threshold requirement. (l) The word should indicate an objective requirement. Precedence: For the purpose of this RFI the following order of precedence applies: This RFI (highest), followed by MIS-ICD-55808 and MIS-ICD-55810, followed by reference information contained within the separate supporting technical data package. Requirements: (a) There shall be two launcher configurations. One configuration is designated the small configuration launcher. The other configuration is designated the large configuration launcher. (b) The small configuration launcher shall be capable of accommodating a total simultaneous weapon load of no less than seven rockets per load. The large configuration launcher shall be capable of accommodating a total simultaneous weapon load of no less than nineteen rockets per load. (c) The small configuration launcher shall be capable of accommodating no less than four smart interface rockets per load. The large configuration launcher shall be capable of accommodating no less than eight smart interface rockets per load. The launcher should be capable of accommodating a complete load of smart interface rockets. (d) The small configuration launcher shall be compatible with the Kiowa OH-58F platform. The large configuration launcher shall be compatible with the Apache AH-64D Blk III platform. The large configuration launcher should be compatible with the Navy Cobra AH-1Z platform. Complete characterization of the individual platform interfaces and induced environments is not provided as part of this RFI. Platform compatibility is defined as meeting the requirements described in this RFI to include MIS-ICD-55808, dimensional envelope, weight, suspension, center of gravity and captive carry life compliance. In all cases it is assumed that the platform meets the interface requirements of MIS-ICD-55808. (e) The launcher shall be compatible with the following rockets, all utilizing the MK66 MOD4 rocket motor and IAW MIS-ICD-55810: M151 warhead with M423/M427 fuze; M156 warhead with M427 fuze; M229 warhead with M423/M427 fuze; M255A1 warhead with M439 fuze; M257 warhead w/M442 fuze; M261 warhead w/M439 fuze; M264 warhead w/M439 fuze; M267 warhead w/M439 fuze; M274 warhead with integral fuze; M278 warhead with M442 fuze; and WTU-1/B warhead. The launcher shall be compatible with the 23 lb, 31 lb and 35 lb rockets defined herein. The launcher shall be compatible with the Smart Interface 2.75-Inch Hydra Rocket defined herein. (f) The launcher shall interface to the platform electrically and logically IAW MIS-ICD-55808 to the extent necessary to meet the requirements described herein. (g) The launcher shall interface to the rocket electrically and logically IAW MIS-ICD-55810 to the extent necessary to meet the requirements described herein. (h) The launcher shall interface to the platform mechanically using fourteen inch spaced suspension lugs with sway brace pad areas IAW MIL-STD-8591. (i) The small configuration launcher shall have a dimensional envelope no greater than 12.0 inches high by 12.0 inches wide by 77.0 inches long. The small configuration launcher should have a dimensional envelope no greater than 9.75 inches high by 9.75 inches wide by 77 inches long. The small configuration launcher shall extend no more than 30 inches in front of the forward suspension lug. The large configuration launcher shall have a dimensional envelope no greater than 19.5 inches high by 19.5 inches wide by 77.0 inches long. The large configuration launcher should have a dimensional envelope no greater than 16.5 inches high by 18.0 inches wide by 77 inches long. When installed on the platform, height is measured in the vertical direction, width is the direction perpendicular to the platform, and length is the direction parallel to the fore-aft axis of the platform. Height, width and length directions are orthogonal to one another. Dimensional excursions will be allowed on the top side of the launcher to accommodate suspension lugs, interface connectors and electronics, all on a non-interference basis with the platform. (j) The small configuration launcher, with no rockets loaded, shall weigh no more than 60 pounds. The small configuration launcher, with no rockets loaded, should weigh no more than 43 pounds. The large configuration launcher, with no rockets loaded, shall weigh no more than 145 pounds. The large configuration launcher, with no rockets loaded, should weigh no more than 105 pounds. (k) The launcher shall provide for a center of gravity (CG) location within +3/-3 inches (relative to the fore/aft lengthwise direction of the launcher) of the midpoint between the two suspension lugs when using the following rocket loads: Load Number 1 - Empty launcher (no rockets loaded); Load Number 2 - A 23 lb rocket loaded in every tube; Load Number 3 - A 31 lb rocket loaded in every tube; Load Number 4 - If the total number tubes in the concept is an even number, then half of the tubes shall be loaded with 35 lb rockets and half of the tubes shall be loaded with 23 lb rockets. If the total number of tubes in the concept is an odd number, then load the total number of tubes divided by two and rounded up to the next whole number with 35 lb rockets and load the remainder of the tubes with 23 lb rockets. The launcher should provide for a combined CG location within +3/-7 inches (fore/aft) of the midpoint between the two suspension lugs for any combination of rockets listed in the weapon compatibility requirement. (l) The launcher shall operate and meet all requirements during exposure to the following ambient temperature environments: -40C <= Temperature <= +55C continuous; +55C < Temperature < = +71C for 30 minutes followed by an unpowered cool-down time period of not less than one hour. The launcher should operate and meet all requirements during exposure to the following ambient temperature environments: -54C <= Temperature <= +55C continuous; +55C < Temperature <= + 71C for 30 minutes followed by an unpowered cool-down time period of not less than 30 minutes. The nomenclature <= indicates less-than-or-equal. (m) The launcher shall operate and meet all requirements after exposure to the following ambient temperature environment: -54C < Temperature < +71C continuous. (n) The launcher shall be capable of determining if a properly loaded rocket utilizes an externally, electrically programmable fuze. The launcher shall be capable of discriminating between an M433 fuze and an M439 fuze for a properly loaded rocket. For each smart interface compatible tube, the launcher shall be capable of identifying the rocket type for each properly loaded Smart Interface 2.75-Inch Hydra Rocket. The launcher should be capable of identifying the rocket type for all properly loaded rockets listed in the weapon compatibility requirement. (o) The launcher shall be capable of performing Power-On Built-in-Test (BIT), Continuous BIT and Initiated (Commanded) BIT. The launcher shall maintain BIT result data in launcher non-volatile memory. The launcher shall make BIT result data available via the MIL-STD-1760 interface and IAW MIS-ICD-55808. (p) The launcher shall be capable of no less than 192 rocket uploads/downloads per tube for any combination of rockets in any sequence prior to any required servicing due to the upload/downloads. The launcher shall be capable of no less than 48 rocket firings per tube for any combination of rockets in any non-ripple fire sequence prior to any required servicing due to the firings. The launcher shall be capable of no less than three (3) rocket firings from each tube for any combination of rockets for a launcher-emptying ripple fire sequence prior to any required servicing due to the firings. (q) While loaded with any combination of weapons specified herein, the launcher shall be capable of no less than 500 captive carry flight hours on the host platform prior to requiring service due to the captive carry flight hours. (r) The launcher shall be cleanable in the field. The launcher shall be serviceable in a maintenance facility. (s) The launcher shall be supportable using current or modified Army inventory support equipment. Current Army inventory equipment includes the AN/AWM-101A and the Launcher Test Station (LTS). The launcher should be supportable in the field using only passive loopback cables when the launcher is installed on the platform and powered by the platform. The launcher should be supportable at a maintenance facility using only a loopback capability with passive adapter cables and the current or modified Army Launcher Test Station. If the launcher concept supports the platform compatibility AH-1Z objective requirement, then the launcher should be supportable at the Navy organizational level (O-level) using the current or modified AN/AWM-103A. If the launcher concept supports the platform compatibility AH-1Z objective requirement, then the launcher should be supportable at the Navy intermediate level (I-level) using the current or modified Common Rack and Launcher Test Set (CRALTS). (t) While operating power is applied to the launcher, the launcher shall acquire health data consisting of periodically sampled environmental data including temperature and humidity; transient environmental event data including shock events; and launcher usage data including power-on time and rocket launch history. The launcher shall store health data within launcher internal non-volatile memory which is separate from the operational flight program memory. The launcher shall make health data available via the MIL-STD-1760 interface. (u) The launcher shall be reprogrammable using external equipment without disassembly of the launcher and IAW MIS-ICD-55808. (v) The launcher, when packaged in its shipping and storage container, shall be transportable, stackable and storable using pallets. The launcher, when packaged in its shipping and storage container, shall be protected from natural environments. Natural environments include humidity, sand, rain, dust, snow, salt fog, fungus, solar loading and temperature shock. (w) The launcher concept shall support a development program with a 36 month timeline with the following notional schedule milestones: System Functional Review/System Requirements Review - Month 3; Preliminary Design Review - Month 6; Form-Fit (non-functional) prototypes available (mass, CG, and dimensional representative) - Month 6; Functional prototype available for laboratory integration and software test (non-form, non-fit) - Month 9; Unique or modified support/test equipment functional prototype available (if applicable) - Month 9 ; Critical Design Review - Month 12; Form, fit and function prototypes available - Month 15; Initiate test in the U.S. Army Aviation and Missile Research Development and Engineering Center (AMRDEC) Weapon Integration Lab - Month 15; Initiate platform integration (OH-58F) - Month 16 ; Initiate captive carry demonstration flights (OH-58F) - Month 18; Initiate Qualification Environmental and Ground Tests - 18; Initiate Qualification Flight Tests (OH-58F) - Month 22 ; Initiate platform integration (AH-64D Block III) Month 28; Initiate captive carry demonstration flights (AH-64D Block III) - Month 29; Complete Qualification Tests (OH-58F) - Month 30; Initiate Qualification Flight Tests (AH-64D Block III) - Month 31; Complete Qualification Tests (AH-64D Block III) - Month 36. (x) The launcher concept shall support a launcher development program requiring delivery of developmental and qualification launchers with embedded software in accordance with the following: Small launcher (Engineering Use - Form, Fit), Quantity (Qty) 5 in Year 1; Large launcher (Engineering Use - Form, Fit), Qty 5 in Year 1; Small launcher (Engineering Use - Functional), Qty 2 in Year 1, Qty 3 in Year 2; Large launcher (Engineering Use - Functional), Qty 2 in Year 1, Qty 3 in Year 2; Small launcher (Qualification Support - Non-functional, Form, Fit, Flight-worthy), Qty 10 in Year 2; Large launcher (Qualification Support - Non-functional, Form, Fit, Flight-worthy), Qty 10 in Year 2; Small launcher (Qualification - Functional, Form, Fit), Qty 5 in Year 2, Qty 25 in Year 3; Large launcher (Qualification - Functional, Form, Fit), Qty 5 in Year 2, Qty 25 in Year 3. (y) The launcher concept shall support a post-development launcher production program requiring launcher production in accordance with the following: Small launcher, Qty 125 in Year 4, Qty 225 in Year 5, Qty 225 in Year 6, Qty 225 in Year 7; Large launcher, Qty 175 in Year 4, Qty 308 in Year 5, Qty 300 in Year 6, Qty 300 in Year 7. (z) The launcher concept shall support a launcher sustainment program requiring launcher deliveries of a combination of production, serviced and refurbished launchers in accordance with the following: Small launcher, Qty 150 in Year 8 and beyond; large launcher, Qty 175 in Year 8 and beyond. The ratio of new production launchers to serviced and/or refurbished launchers starting in year 8 will be a function of the launcher concept. (aa) The following launcher attributes are extremely important: (i) Compatible with threshold weapons; (ii) Compatible with threshold platforms; (iii) Compliant to MRL Interface Control Documents MIS-ICD-55808 and MIS-ICD-55810. The following launcher attributes are very important but less important than the extremely important attributes: (i) Supports low risk program execution (technical, schedule, cost); (ii) Amount of ground clearance margin (over the MIL-STD-1289 requirement) for the small configuration launcher installed on Kiowa OH-58F. The current ground clearance of the M260 launcher on the OH-58D is approximately twice the minimum required by the MIL-STD-1289; (iii) Ownership Cost (Production, Logistics and Sustainment); and (iv) Upgradeability. The following launcher attributes are important but less important than the very important attributes: (i) Number of smart interface capable tubes in excess of the threshold amount; (ii) Automatic rocket identification capability; (iii) and minor or no impact to currently fielded Army support equipment. Information Requested: The Government requests interested parties provide a white paper description of their Modernized Rocket Launcher concept(s). A maximum of three white papers, corresponding to three concepts, may be submitted by each responding organization. Each concept should be documented in a separate white paper. Each white paper shall be no more than fifteen (15) one-sided pages in length, on 8.5 inch by 11 inch paper, and font size no smaller than Arial 10. Smaller fonts are acceptable only if the text is embedded in a figure that is predominately graphical in nature. All text shall be clearly readable. The white paper shall be readable by Microsoft Office Word 2003. The white paper shall be unclassified. The white paper shall be provided with proper markings to identify proprietary information. Each white paper should do the following: (a) Describe the best value concept; (b) State assumptions made; (c) Identify which threshold (shall) and objective (should) requirements the concept meets; (d) Provide an explanation for each threshold and objective requirement the concept does not meet; (e) Describe the path to meet all threshold and objective requirements, if not already met, including any recommended changes to requirements; (f) Identify which requirements significantly affect the technology, schedule and cost to develop and produce the concept in accordance with the program schedule described herein; (g) Discuss how the concept addresses ownership cost; (h) Identify concept dependencies on proprietary interfaces, technologies, software and designs; (i) Summarize your organization's capabilities relevant to the MRL; (j) Describe any additional opportunities and benefits enabled by the concept such as compatibility with additional platforms including the F/A-18 E/F Hornet, MH-60R Seahawk, and Unmanned Aerial Vehicles; shipboard compatibility; and adaptability of the MRL to support weapons that do not adhere to the Hydra 2.75-Inch rocket form factor. Responses should include: a.Company Name, CAGE Code, DUNS number, Company Address, and Place of Performance Address b.Point of contact, including: name, title, phone, and email address c.Size of company, average annual revenue for the past three years, and number of employees d.Whether the business is classified as a Large, Small, Small Disadvantaged, 8 (a), Women Owned Small Business, Veteran Owned Small Business, and/or Service Disabled Veteran Owned Small Business This Request for Information is for information and planning purposes only. This Request for Information does not constitute a solicitation. In accordance with Federal Acquisition Regulation (FAR) 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Responders are responsible for all expenses associated with responding to this RFI. All interested parties are advised that the Government will not provide any form of compensation or reimbursement for the information provided. No contract or other binding instrument will occur as a result of this Request for Information. Therefore, all costs associated with the provided Request for Information submissions will be solely at the expense of the concern submitting the information. All information provided in the RFI responses to the Government that is marked proprietary will be handled accordingly. All submittals will be treated at a minimum as For Official Use Only. The Government utilizes Scientific Engineering and Technical Assistance (SETA) personnel as support contractors. In accordance with Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.227-7025, Government SETA support contractors are restricted in their use of Government Furnished Information (GFI). It is expected that SETA personnel from the following companies will support the Government on a need-to-know basis in the review of submittals to this RFI: (a) BCF Incorporated; (b) Camber Corporation; (c) DCS Corporation; (d) Digital Fusion Incorporated; (e) Dynetics; (f) On-Line Applications Research Corporation (OAR); (g) Science Applications International Corporation (SAIC); (h) System, Simulation and Studies Incorporated (S3); (i) Torch Technologies, Inc.; (j) University of Alabama - Huntsville and (l) Wyle - Aerospace Group. If the RFI responder desires to execute company-to-company non-disclosure agreements (NDAs) with all of the Government SETA companies listed above, the responder may request company point of contact information from the Army Contracting Command-Redstone POC identified herein. The Government does not manage and does not control company-to-company NDAs. Submittal to the Government in response to this RFI constitutes permission to disclose information contained therein to SETA personnel from all the SETA companies listed above on a need-to-know basis. Responses to this RFI may be submitted by any entity interested in doing business with the U.S. Federal Government. The Government will provide an informational technical data package to qualified requestors. The technical data is reference information only and is subject to change. The technical data includes information that is both export controlled and distribution limited. In order to receive the technical data package the requestor must be a U.S. company, must be a U.S. Department of Defense (DoD) Contractor and must be capable of serving as a prime contractor to fully develop the MRL. Requests for the technical data package should be provided to the Army Contracting Command-Redstone POC identified in this RFI. A Modernized Rocket Launcher Request for Information Technical Data Package Request Form will then be provided to the requestor. Once the requestor has provided the required information and the requestor's qualification to receive the technical data is verified, the package will be provided via standard U.S. Mail. The only approved use of the technical data package is to support a response to this RFI. No other use or additional distribution of the information is authorized. Responses to this RFI will not be returned and results of this RFI will not be provided. It is requested that each white paper be provided on a separate Compact Disc (CD) with appropriate markings to: US Army Contracting Command-Redstone, ATTN: CCAM-TM-A, Sarah Marcial or Margaret Yourich, Building 5303, Martin Road, Redstone Arsenal, AL. No email submissions will be accepted. Interested parties may submit questions relative to this RFI prior to expiration of this RFI to the Army Contracting Command-Redstone contact person(Sarah Marcial- email- sarah.k.marcial@us.army.mil, phone- 256-876-4168; Margaret Yourich - email- margaret.yourich@us.army.mil, phone- 256-842-7253).
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/b54dd31340a0e8637f5458bc96dc42f7)
- Place of Performance
- Address: US Army Contracting Command-Redstone (CCAM-TM-A), ATTN: CCAM-TM-A, Sarah Marcial or Margaret Yourich, Building 5303, Martin Road Redstone Arsenal AL
- Zip Code: 35898-5280
- Zip Code: 35898-5280
- Record
- SN02446610-W 20110514/110512234802-b54dd31340a0e8637f5458bc96dc42f7 (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 |