Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF MAY 04, 2013 FBO #4179
SOURCES SOUGHT

15 -- Airborne Resupply/Logistics for Seabasing (AR/LSB) Recapitalization

Notice Date
5/2/2013
 
Notice Type
Sources Sought
 
NAICS
332510 — Hardware Manufacturing
 
Contracting Office
Department of the Navy, Naval Air Systems Command, NAVAIR HQ, Building 2272, 47123 Buse Road Unit IPT, Patuxent River, Maryland, 20670, United States
 
ZIP Code
20670
 
Solicitation Number
AR_LSB_Recapitilization_RFI_2
 
Point of Contact
Donna M Bibee, Phone: 301-342-1302
 
E-Mail Address
donna.bibee@navy.mil
(donna.bibee@navy.mil)
 
Small Business Set-Aside
N/A
 
Description
•· I. SUMMARY This is a Request for Information (RFI) to assist in the refinement of the requirements and update the Market Research for the Medium Lift/Long Range (ML/LR) Carrier Onboard Delivery (COD) mission, led by the NAVAIR (AIR-1.0) COD Recapitalization Program Office. This is NOT a Request for Proposals. NO SOLICITATION DOCUMENTS EXIST AT THIS TIME. Office of the Chief of Naval Operations, Director Air Warfare (OPNAV N98) has identified the continued operational need for an aircraft carrier based aircraft capable of performing the ML/LR COD mission in support of the Carrier Strike Group (CSG). This RFI is considering needs and options for carrier based COD aircraft in the 2026 timeframe. The purpose of this RFI is to enable the COD Recapitalization Program Office to determine the existence of sources that can deliver systems capable of performing the above mentioned Navy COD mission with the following constraints no later than the 4th quarter of Fiscal Year 2026. II. CONSTRAINTS The following constraints apply: • The system must IOC for fleet use no later than 4Qtr FY2026. • The system must be suitable for operations from CVN 68 and CVN 78 class aircraft carriers. - Capable of day and night operations without negatively impacting CVN combat sortie generation rates. - CVN Deck spot factor not to exceed 1.86 in a wings folded configuration. - Not exceed an Aviation Consolidated Allowance List (AVCAL), including Intermediate (I) and Operational (O) level maintenance and bulk spares of ~ 32,000 lbs and ~ 5,400 cu ft. - Not require unique Support Equipment (SE) that accumulatively exceeds ~ 17,750 lbs and ~ 2,000 cu ft. - CVN turn-around time, including launch and recovery, taxi, cargo/passengers on/off load, and refueling, not to exceed 45 minutes. • The system must be effective in the primary COD mission and secondary missions of Air-to-Air Refueling, Casualty Evacuation (CASEVAC), Naval Special Warfare (NSW) Support, and Missions of State. The system must be: - Capable of an unrefueled Operational Range of no less than 1,150 nm when operating under Tropical Day conditions. - Capable of transporting no less than 700 cu ft or 6,000 lbs of cargo/passengers to the Operational Range while operating under Tropical Day conditions. - Capable of carrying a combined payload of no less than 8,600 lbs, including 20 passengers, or 700 cu ft of volume to and from the Sea Base when operating under Tropical Day conditions. - Capable of a Self-Deployment trans-oceanic transit range of no less than 1,850 nm under Tropical Day conditions. - Compliant with Federal Aviation Association/International Civil Aviation Organization (FAA/ICAO) Communications, Navigation, Surveillance /Air Traffic Management (CNS/ATM) mandates. - Compliant with FAA and ICAO requirement for passenger transport, including but not limited to capabilities such as Controlled Flight Into Terrain (CFIT) Avoidance, Traffic alert Collision Avoidance System and weather avoidance radar. - Capable of providing Aerial Refueling tanker support (probe-and-drogue) to Carrier Air Wing (CVW) aircraft. - System must provide no less than aural and visual warning to aircrew and cueing to countermeasures to defeat man portable air defense system (MANPAD threats such as the Russian Strela (SA-7 and SA-14), Igla (SA-16 and SA-18)) and the U.S.-manufactured FIM-92 Stinger. - Capable of having a Main cargo deck that accommodates transport of palletized and non-palletized cargo, passengers and passenger configurations (plus baggage) (or equivalent CASEVAC Capability to include ambulatory) and be compatible with the U. S. Navy Carrier (CVN) Aviation environment. •The system must be reliable and sustainable with - A service life of no less than 7,500 hours; - An Operational Availability (AO) of no less than 75%; and - System must have a Mean Flight Hours Between Operational Mission Failure (MFHBOMF) of no less than 10 hours. • System must be affordable and cost effective. - Your System must have an average annual O & S cost per aircraft in base year 2011 dollars no greater than the C-2A(R) aircraft. - Your System must be able to transport the minimal Internal Payload to the minimal Operational Range when operating in Tropical Day Conditions in terms of Cargo Ton - Nautical Mile (nm) per Gallon (gal) of fuel consumed. III. CONTENT OF RFI RESPONSE The capabilities described herein are intentionally broad to ensure a comprehensive market survey. Responses to this RFI should describe the capability available from each proposed alternative identified for the mission and constraints defined herein. All respondents are requested to provide the following and shall clearly identify any elements of the system that would be delivered with less than Government purpose rights: 1. A general description of the aircraft segment including propulsion system, cargo handling capabilities, mission avionics, performance characteristics, and landing gear configurations. Provide reference design mission(s) and constraints. As applicable, provide further detailed descriptions of the following: Aircraft Design Criteria Amplifying Information Dimensional configuration drawings illustrating aircraft geometry • Folded and unfolded wings (if applicable) • Tie-down points • Inboard profile illustrating the locations of major subsystems Breakdown of aircraft weight (in pounds) • Include design gross take-off weight, aircraft weight empty, operating weight empty, structural weight, useful load, payload weight, fuel weight, maximum carrier recovery weight (i.e. fuel and payload bring-back) Aircraft fuel capacity(ies) • Internal, external, unusable capability Aircraft performance data • Take-off weight/endurance as a function of speed and altitude at Sea Level/Tropical Day • Payload-Range curves • Flight envelope Altitude vs. airspeed/Mach number Cargo system • Describe methods of securing cargo including but not limited to tie-down fittings, restraints, cargo cage, and floor fittings. • Describe the ability to withstand the following loading conditions as applicable: o Trap Landing: 20 g longitudinal, 20 g vertical, and 10 g lateral loading conditions o No-Trap Landing: 4 g forward, 3 g aft, 3 g lateral, 3 g vertical-up • Ability to reconfigure interior to accommodate cargo only, passengers only, and a mixture of cargo and passengers • Limits on cargo positioning due to weight, balance and volume limitations • Describe methods of loading and unloading cargo including but not limited to winches, rails, rollers, and pulleys. • Describe the Air Vehicle capability to transport litters • Describe ability to accommodate wooden pallets, Type 463L half pallets as specified in MIL-HDBK-774 and MIL-P-27443(II) Tanking System • Describe the concept for a probe-and-drogue recovery tanker mission capability, including but not limited to configuration, mission duration, "fuel give" capacity, and altitude vs speed assessments • Ability and time estimates to reconfigure between Tanker and COD configurations, passengers and/or cargo Propulsion and power system • Engine(s) model and version • Engine specifications (dimensions, thrust, weight, specific fuel consumption, etc.) • Engine ratings (take-off, maximum continuous, maximum climb, maximum cruise, etc.) • Typical fuel flow values for takeoff/carrier launch, climb, cruise, loiter, and idle • Engine control system • Electrical power generation capabilities, margins, and growth potential Aircraft service life related to notional use spectrum • Start with Design Life and discuss the various adjustments for the proposed system to meet the missions 2. Describe the CVN integration and suitability of the system, interface concepts, and the ability of the system to interoperate with CVN support, hangar/deck operations, launch, recovery, Carrier Control Area, and mission operations. As applicable, provide further detailed descriptions of the following: CVN Integration Design Criteria Amplifying Information Ability to integrate with Government CVN systems and interfaces • Supportability, hangar/ deck operations, launch, recovery, Carrier Control Area (CCA), and mission operations as described in NAVAIR document Shipboard Interface Reference Document System suitability for carrier operations • Maintenance and supportability, hangar and flight deck handling, launch and recovery, and CCA operations CVN flight and mission operations support concept • Mission planning, manning, space requirements, data requirements, security requirements, and integration with CVN mission systems • Platform configuration, performance, avionics equipage, software capabilities, and automation capabilities 3. A general description of the system's operations and support concept to include cargo handling, logistics, maintainability, training, etc. As applicable, provide further detailed descriptions of the following: System Operations and Support Design Criteria Amplifying Information Cargo handling operations, on land and in a maritime environment • Ability to handle standardized cargo containers, pallets, etc. • Support equipment for loading and unloading cargo Sustainability in a maritime environment • Logistics philosophy, maintenance, corrosion resistant features, training, open architecture features etc. Manning/staffing assessment for each fielded system and total force in aggregate • Estimated training requirements • Assume systems will be maintained and operated by fleet Sailors 4. An estimated schedule for system development, testing and deployability assessment to enable deployment of capabilities by 4Qtr FY2026. Identify block/spiral development plans. 5. An assessment of system and subsystem technology, manufacturing, and integration readiness levels with supporting data expressed as Technology Readiness Levels (TRL's). 6. A rough order of magnitude that includes development, procurement, and support costs. Provide Air Vehicle (airframe, avionics, propulsion and accessories, payload, and air vehicle software), system test/evaluation, system engineering/program management, training, data, support equipment, initial spares and repair parts costs. Provide estimated total software lines of code by software segment and software breakdown by new, modified and reused code. Identify any investment dollars to date. IV. SECURITY INFORMATION The Government anticipates a comprehensive response to this RFI that may contain CLASSIFIED information. To the extent practical, responses should be UNCLASSIFIED, complemented by CLASSIFIED appendices as required. Companies are to adhere to the National Industrial Security Program Operating Manual (NISPOM) procedures for the transmittal of classified responses. Company responses should clearly indicate the system(s) / technology area(s) addressed and include a one page cover letter, and a three page (maximum) executive summary, with no limit on the detailed content. Companies are not limited to a single response. V. SUBMISSION INFORMATION Parties interested in responding to the RFI must submit a statement of interest no longer than five (5) pages to Ms. Donna Bibee (email address: donna.bibee@navy.mil) no later than seven (7) days from the RFI issue date with the following additional data, in order to verify credentials: 1. CAGE code; 2. POC name and telephone number to contact for any necessary clarification, to receive additional information, for additional data required by the analysis, and for information on any necessary non-disclosure agreements; 3. An UNCLASSIFIED description of the concept(s) for meeting the top level required system capabilities listed at the beginning of this RFI; and 4. A description of the company's ability to manage, secure and transmit information up to the level of classification required. Full response submissions to the RFI shall be received no later than 07 June 2013. Unclassified data submissions shall include electronic media, Microsoft Office 2007 compatible and three (3) hard copies to: Naval Air Systems Command ATTN: Ms. Donna Bibee (AIR 2.4) 47123 Buse Road Bldg. 2272 Room 353 Lexington Park, MD 20653 Ms. Bibee's telephone is (301) 342-1302 and the email is donna.bibee@navy.mil. Classified information shall be provided as appendices to the full response. Classified appendices (up to SECRET NOFORN) shall be in compliance with current DoD Directives and procedures. Classified appendices shall also include electronic media, Microsoft Office 2007 compatible and three (3) hard copies, with the outer envelope addressed to: Outer Address: DEPARTMENT OF THE NAVY COMMANDER NAVAL AIR SYSTEMS COMMAND 47123 BUSE RD, BLDG 2272 RM 353.8 PATUXENT RIVER, MD 20670 The inner packaging should be addressed to: DEPARTMENT OF THE NAVY COMMANDER NAVAL AIR SYSTEMS COMMAND 47123 BUSE RD, BLDG 2272 RM 353.8 PATUXENT RIVER, MD 20670 ATTN: AIR 1.0P Brian Scolpino Address inquiries regarding submission of classified information to Mr. Brian Scolpino at (301) 757-9090. DO NOT SEND ANY CLASSIFIED INFORMATION VIA UNCLASSIFIED EMAIL. As stated above, this is NOT a Request for Proposal. THIS SYNOPSIS IS NOT TO BE CONSTRUED AS A COMMITMENT BY THE GOVERNMENT, NOR WILL THE GOVERNMENT PAY FOR ANY INFORMATION SOLICITED OR PROVIDED. VI. ADDITIONAL INFORMATION This RFI is an exchange of information between Government and Industry. It is a step in the iterative process aimed at understanding the existence of sources that can deliver an inventory of fleet operable systems capable of performing the ML/LR COD mission described herein. Additional RFIs requesting further detail may be issued in the future to continue the Government's informational exchange with Industry. Information received as a result of this request is expected to be sensitive and/or proprietary to the responding company and will be protected as such. Any proprietary information received in response to this request will be properly protected from any unauthorized disclosures; however it is incumbent upon the respondent to appropriately mark all submissions. The Government will not use any proprietary information submitted to establish the capability, requirements, approach, or solution so as to not inadvertently restrict competition. In order to complete its review, NAVAIR 1.0 must be able to share the information within the Government and any responses marked in a manner that will not permit such internal Government review may be returned without being assessed / considered. In addition support contractors will provide ongoing support and are expected to be utilized as part of this market research. Any objections to release of information to any of the support contractors must be clearly and prominently delineated in the cover letter to any submission. Further, any markings affixed to submissions must clearly allow for disclosure to the support contractors to which the respondent has no objection.
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/spg/DON/NAVAIR/N00019/AR_LSB_Recapitilization_RFI_2/listing.html)
 
Place of Performance
Address: To be determined, United States
 
Record
SN03051621-W 20130504/130502235130-e6a75056cc07f6714e31c4908dc492fc (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 |
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.