MODIFICATION
16 -- Request for Information (RFI): Mission Enhanced Little Bird (MELB) Cockpit Upgrade
- Notice Date
- 11/22/2013
- Notice Type
- Modification/Amendment
- NAICS
- 336413
— Other Aircraft Parts and Auxiliary Equipment Manufacturing
- Contracting Office
- Other Defense Agencies, U.S. Special Operations Command, Technical Applications Contracting Office (TAKO), ATTN: AMSAM-TASO-K, Lee Boulevard, Building 401, Fort Eustis, Virginia, 23604-5577
- ZIP Code
- 23604-5577
- Solicitation Number
- RFI-0001-H92241
- Archive Date
- 12/7/2013
- Point of Contact
- Anthony Ciccariello, Phone: 7578783299
- E-Mail Address
-
anthony.ciccariello1@us.army.mil
(anthony.ciccariello1@us.army.mil)
- Small Business Set-Aside
- N/A
- Description
- Cockpit Avionics Integration Program Request For Information Synopsis: Request for Information (RFI): Mission Enhanced Little Bird (MELB) Cockpit Upgrade 1.0 - SUMMARY: 1.1 - The Government has a requirement for the sustainment, modernization and enhancement of the A/MH-6 Mission Enhanced Little Bird (MELB) avionics cockpit. 1.2 - To fulfill this requirement, the United States Special Operations Command (USSOCOM), is investigating alternative acquisition approaches, identifying the feasibility and practicality of each in order to select the most favorable course of action. One alternative under consideration is a hardware and software, "total avionics cockpit", solution. To that end, the Government is seeking interested industry organizations that can furnish the personnel, facilities, equipment and materiel necessary to develop an integrated avionics system cockpit for the A/MH-6 platform with the potential for follow-on avionics systems life-cycle sustainment and support thru 2030. Additionally, as a follow-up to receipt of RFI responses, a Market Research Interchange Meeting (MRIM) may be held for this requirement, tentatively scheduled that is to be TBD. 1.3 - THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes - it does not constitute a Request For Proposal (RFP) or a promise to issue an RFP in the future. This RFI does not commit the Government to contract for any supply or service whatsoever. Further, the Government is not, at this time, seeking proposals and will not accept unsolicited proposals. Respondents are advised that the Government will not pay for any information or administrative costs incurred in responding to this RFI. All costs associated with responding to this RFI will be solely at the interested parties' expense. Not responding to this RFI does not preclude participation in any future RFP, if issued, however it is highly recommended that you respond to the RFI if your company has the capabilities the Government is seeking. If an RFP is released, it will be synopsized on the Federal Business Opportunities (FedBizOpps). It is the responsibility of the potential sources to monitor these sites for additional information pertaining to this requirement. 2.0 - BACKGROUND: 2.1 - Since the baseline A/MH-6M began fielding in November 2003, the MELB Program Management Office (PMO) has conducted a series of modification (preplanned and unplanned) programs to keep the aircraft updated with customer requirements and modernized mission equipment. The preplanned Block 3.0 configuration is the continuation of a block upgrade strategy designed to extend the service life of the A/MH-6M while long-term alternatives for aircraft replacement are analyzed. Part of the Block 3.0 program includes a digital cockpit upgrade for a digital moving map (DigMap), battle field networking, and interfaces for rapid insertion planned technology upgrades. 2.2 - Weight discipline is a critical element of this program. The end state of the Block 3.0 modification is successful implementation of the identified level of engineering, performance, and cognizance without increasing the basic empty weight of the aircraft. 3.0 - DESCRIPTION OF NEED: Objectives for the MELB Block 3.0 Cockpit Avionics Integration Program and vendor capabilities/qualifications include: 3.1 - Cockpit Avionics Functionality: The following provides a high-level list of the required MELB Block 3.0 system avionics capabilities: 3.1.1 - Avionics System Management/Data Load/Maintenance 3.1.2 - Aircraft Systems State Display 3.1.3 - Navigation 3.1.4 - Flight Management 3.1.5 - Communications Management 3.1.5.1 - Two-channel data-capable radio in conjunction with existing communications equipment (see Section 3.3 - Hardware below). 3.1.6 - Weapons Management 3.1.7 - Mission Sensor Management 3.1.8 - Tactical Situation Management 3.2 - Avionics Systems Integration: 3.2.1 - Interested parties should consider solutions that provide existing and desired capabilities including the functionality stated above and that follow the guidance below regarding hardware components with Size, Weight, Power, and Cooling (SWaP-C) considerations. 3.2.2 - Interface. Any proposed integrated avionics cockpit will be required to interface with a multitude of onboard systems and have the ability to easily integrate new aircraft systems. Integration of cockpit avionics into the aircraft will be performed by a third party vendor. Coordination with this third party will be necessary for full platform integration considerations such as installation, weight, power, cooling, data, and data interface requirements. 3.2.3 - A current and notional console layout is available upon request (Reference paragraph 3.7). 3.3 - Hardware: 3.3.1 - Overall considerations for hardware includes: 3.3.1.1 - Cube. Space is extremely limited in the A/MH-6 series of aircraft for cockpit displays, cabin Line Replaceable Units (LRUs), and wire runs. In general, available space for avionics includes areas behind and beneath the consoles, area directly forward of the center console, under the pilot/copilot floorboards, and avionics racks behind the pilot seats (Diagrams with approximate dimensions are available upon request (Reference paragraph 3.7).) 3.3.1.2 - Weight. As previously mentioned, weight is a critical element of this program. The weight of the cockpit trade space is estimated to be 120 pounds. (additional information regarding candidate core avionics components for removal/replacement is available upon request (Reference paragraph 3.7).) This weight value is only an estimate to be used for preliminary planning. 3.3.1.3 - Power. The A/MH-6 cockpit must operate on 28VDC power. The aircraft does not contain an AC generator. Additionally, aircraft start must be performed on battery power. As a result, critical aircraft state information must be displayed during the start sequence. 3.3.1.4 - Environment. The A/MH-6 cockpit will be exposed to harsh environmental conditions such as sand, dirt, debris, and moisture due to frequent open cockpit operations. 3.3.1.5 - Night Operation. The A/MH-6 cockpit must be compatible with Night Vision Goggle (NVG) operations. 3.3.1.6 - The avionics system equipment will be of the manufacturer's current design (Technology Readiness Level (TRL) Level 7 or higher desired), military and/or civil qualified, and capable of performing its intended function in accordance with the operation and performance requirements specified herein. 3.3.2 - Upon request, a list of some of the avionics LRUs planned to be retained as a part of the aircraft configuration may be provided (reference paragraph 3.7). These LRUs, including Identification, Friend or Foe (IFF), radios, Tactical Airborne Navigation (TACAN), Air Data Computer (ADC), and Radar Altimeter, must integrate with any proposed cockpit design. 3.3.3 - Mission-specific equipment and functionality, such as Forward Looking Infrared (FLIR), may also be integrated into this platform as a part of the cockpit avionics integration effort. The Government's primary intent for this RFI is the investigation of candidate cockpit solutions with a focus on reduction in weight attributed to core equipment. 3.4 - Software Development: Interested vendors will be expected to provide software development and support for the Operational Flight Program (OFP). This support includes: 3.4.1 - System development (research, analysis, design, implementation and test or support of these activities) 3.4.2 - Software DO-178C compliance capable (Software maintained/updated at DO-178C assurance levels potentially up to Level A, as appropriate.) Please provide examples of how OFP has been tested and qualified to Level A, B, and C. 3.4.3 - Standard acquisition documentation for software development per DoDD 5000.1 3.5 - Avionics System Test/ Flight Test Support: 3.5.1 - Experience and capability to accomplish the successful integration of 3rd party hardware and software to include 3rd party source code. 3.5.2 - Systems integration/testing/verification (Planning, documentation updates/generation, and execution of systems integration activity including Systems Integration Laboratory (SIL) modifications, SIL lab test execution, including nominal and off-nominal (corner-case, exception handling, robustness) requirements-based and operational/mission-based scenario testing, leading to requirements proof of compliance and air worthiness documentation, and on and off-site development flight test support, as necessary.) 3.5.3 - SIL and test stand build, modification, and maintenance in support of software development and test (Objective uses to include, but not limited to, software/system test and verification, Pilot Vehicle Interface (PVI) demonstration and evaluation, and operator training. Capabilities including maximum utilization of real avionics hardware and wiring, simulation/stimulation capabilities to produce dynamic flight environment and data capture ability for analysis/investigation of system anomalies.) 3.6 - Organization/Personnel/Facilities: Request provide corporate and personnel experience in development, testing, and support of complex avionic system software. Please address:: 3.6.1 - Capability Maturity Model Integration (CMMI) Level 5. 3.6.2 - Aviation software and systems development, integration, and support of complex avionics systems, capabilities including, but not limited to, communication, navigation, guidance, controls & displays, sensors, weapons, and data bus structures such as MIL-STD-1553, ARINC 429, and Ethernet. 3.6.3 - Conduct of structural and test coverage analysis. 3.6.4 - Capability to maintain software development and system integration test lab environments. 3.6.5 - Systems integration and flight test support of complex avionics systems. 3.6.6 - Development of dynamic simulation capabilities. 3.6.7 - Familiarity with military and commercial standards. 3.6.8 - Familiarity with Real Time Operating System (RTOS) and Real Time Environments (RTEs) for software development. 3.6.9 - Acquisition experience to successfully collaborate with suppliers in the solicitation and acquisition of new/replacement hardware. 3.6.10 - Familiarity with Integrated Product Teams (IPTs) and comfortable with working in collaborative environments 3.6.11 - Capabilities to install, operate, and maintain Government Furnished Equipment (GFE) provided SIL test benches supporting MELB system. 3.6.12 - It is anticipated that development effort performed will have access to, or will generate, classified information. Consequently, interested companies must be US companies, possess at least a SECRET facility clearance, and personnel identified for assignment to a classified effort must possess, or have the ability to obtain, secret level security clearance. 3.7 - More detailed system information as stated above are available upon requests addressed to the contact (reference paragraph 9.0) provided that the contractor/vendor/interested party is registered in the Central Contractor Registration (CCR), not be on the debarred list, and have submitted a Defense Logistics Agency (DLA) Joint Certification Office approved DD Form 2345, Militarily Critical Technical Data Agreement. 4.0 - Requested Information: 4.1 - Interested parties are invited to submit technical information describing their organization's ability/capability to meet the Description of Need as detailed above. This request is part of the Government's on-going market research in accordance with Federal Acquisition Regulation (FAR) Part 10. 5.0 - Recommended Responses: 5.1 - Interested parties are requested to respond to this RFI with a white paper. The white papers should be provided in PDF or Microsoft Word for Office 2003 or later compatible format, supplemented with Microsoft Word, Excel, PowerPoint, PDF, or JPG attachments as necessary. The responses are due on 15 November 2013 at 2:00 p.m (EDT). All documents shall be submitted via e-mail only to Mr. Anthony Ciccariello (anthony.ciccariello1.civ@mail.mil). 5.2 - Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that submissions will not be returned. 5.3 - The Government intends to utilize personnel from Cruz Associates, Inc., Yorktown, Virginia, and Yahwehs Computers, Inc., Williamsburg, Virginia to provide technical advice and support in review of submitted information. By submitting a response to this RFI, the Contractor consents to the Government disclosing Contractor proprietary information to the aforementioned contractors to develop the acquisition approach. The contracts with each of the identified companies have the Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.227-7025, Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends, in the contracts with the Government and employees of these companies have individual non-disclosure statements on file with the company. 5.4 - No page limit is imposed on the white paper in response to this RFI, but the responders are encouraged to make their responses clear and concise without superfluous information. Provide the following information: 5.4.1 - Cover Sheet 5.4.2 Section A: Corporate/Team Introduction and Executive Summary Respondent Name, Point of Contact, Title, Date, E-Mail Address, Phone #, Fax #, Organization/Office Symbol, Address, and overnight delivery address (if different from mailing address). 5.4.3 - Section B: Corporate/Team Technical Capability Description to meet the description of need listed above. The contractor shall also identify and address any performance characteristics that they believe will be difficult to achieve during program execution 5.4.4 - Section C: Corporate/Team Systems Engineering, Systems Integration, and Test and Evaluation Capability. 5.4.5 - Section D: Corporate/Team Software Engineering Capability. 5.4.6 - Section E: List of previous and current customers and current contract vehicles that are being used by the Government of similarly complex Aviation post-deployment software and systems support. 5.4.7 - Section F: Miscellaneous 5.4.7.1 - Business type - (large business, small business, small disadvantaged business, 8(a)-certified small disadvantaged business, HUBZone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business) based upon North American Industry Classification System (NAICS) code 334220 -- Other Communications Equipment Manufacturing. "Small business concern" means a concern, including its affiliates that is independently owned and operated, not dominant in the field of operation in which it is bidding on Government contracts, and qualified as a small business under the criteria and size standards in 13 CFR part 121. A small business concern for the purposes of this procurement is generally defined as a business, including its affiliates, that has no more than 750 employees. Respondents are cautioned, however, that this is a general description only. Additional standards and conditions apply. Please refer to Federal Acquisition Regulation FAR 19 for additional detailed information on Small Business Size Standards. The FAR is available at http://www.arnet.gov. 5.4.7.2 - The facility security clearance of the vendor. 5.5 - Other Special Requirements: SUBMIT WHITE PAPERS ONLY. No contract will be awarded based solely on this announcement or on the basis of an Industry Day. 6.0 - QUESTIONS 6.1 - Questions regarding this announcement shall be submitted in writing by e-mail to the Contracting Specialist, email address: anthony.ciccariello1.civ@mail.mil. Verbal questions will NOT be accepted. Questions will be answered by posting answers to the FedBizOpps website; accordingly, questions shall NOT contain proprietary or classified information. The Government does not guarantee that questions received more than 21 days after the RFI issue date will be answered. 7.0 - USE OF INFORMATION 7.1 - The purpose of this notice is to gain information leading to Government/Industry collaboration for development of USSOCOM technology capabilities and to assist in accelerating the delivery of these capabilities to the warfighter. All proprietary information contained in the response shall be clearly marked. The Government will protect all proprietary information from unauthorized disclosure. The Government will not use proprietary information submitted from any one firm to establish future capability or requirements. 8.0 - MARKET RESEARCH INTERCHANGE MEETING: 8.1 - The MELB Block 3.0 Cockpit Avionics Integration MRIM will start at TBD. The location for this event is TBD. Additional information regarding this MRIM will be provided in future updates to this RFI. 8.2 - The MRIM shall consist of an overview briefing by the Government to the general audience followed by optional individual vendor briefs to the Government. During the overview briefing, the Government plans to present the MELB Block 3.0 Cockpit Avionics Integration Requirements. This general session will be followed by a set of scheduled individual sessions where vendors may present the Government their candidate solutions. These sessions will be limited to seventy-five minutes. Respondents are reminded that, during the individual sessions, all questions and Government answers that are not specific to a Respondent's solution will be posted to FedBizOps. Competition sensitive information, however, will not be posted to FedBizOps. 8.3 - All vendor information will be treated confidentially and discreetly. No cameras, tape recorders or other reproduction devices will be allowed. Vendor hardware is permitted for demonstration purposes. 8.4 - The Government briefing charts and sanitized questions/answers from the individual sessions will be made available on FedBizOps approximately two weeks following the conclusion of the MRIM. 8.5 - The Government will require sign in of interested parties and will post this list to as a change to this announcement. 9.0 - CONTACT: 9.1 - All information received in response to this RFI that is marked Proprietary will be handled accordingly. Responses to the RFI will not be returned. 9.2 - All interested, capable, and responsible sources that wish to respond to this RFI are asked to provide input to Mr. Anthony Ciccariello Contract Specialist via email at anthony.ciccariello1.civ@mail.mil by 15 November 2013, no later than 2:00 pm EST. Any questions will be forwarded to the Contract Specialist by e-mail only. Primary Point of Contact: Mr. Anthony Ciccariello anthony.ciccariello1.civ@mail.mil 757-878-0730 ext 247
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/ODA/USSOCOM/FortEustisVA/RFI-0001-H92241/listing.html)
- Record
- SN03240077-W 20131124/131122234615-c162390b41edfa6bb622b27d448c2a63 (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 |