SOURCES SOUGHT
A -- Market Survey for Potential Improvements in Navy Mid-Air Collision Avoidance Capability (MCAC) - Templates
- Notice Date
- 4/24/2013
- Notice Type
- Sources Sought
- NAICS
- 334511
— Search, Detection, Navigation, Guidance, Aeronautical, and Nautical System and Instrument Manufacturing
- Contracting Office
- Department of the Navy, Naval Air Systems Command, Naval Air Warfare Center Aircraft Division Pax River, Building 441, 21983 Bundy Road Unit 7, Patuxent River, Maryland, 20670, United States
- ZIP Code
- 20670
- Solicitation Number
- 41011GW
- Archive Date
- 7/11/2013
- Point of Contact
- Glenn Woods, Phone: (301) 995-7643, Elizabeth K. Sheard, Phone: 3017372633
- E-Mail Address
-
Glenn.Woods@navy.mil, elizabeth.sheard@navy.mil
(Glenn.Woods@navy.mil, elizabeth.sheard@navy.mil)
- Small Business Set-Aside
- N/A
- Description
- Technology Maturity Self-Assessment MIL-STD-881C-based Electronic Systems Work Breakdown Schedule System Metrics Spreadsheet Request for Information (RFI): Mid-Air Collision Avoidance Capability (MCAC) I. SUMMARY This announcement constitutes a Request for Information (RFI) for planning purposes (FAR 15.201(e)) to obtain price, delivery and capabilities. This is NOT a Request for Proposals. NO SOLICITATION DOCUMENTS EXIST AT THIS TIME. This RFI does not constitute an Invitation for Bids (IFB), a Request for Proposals (RFP), a Request for Quote (RFQ) or an indication that the Government will contract for any of the items and/or services contained in this notice. The Director, Air Warfare Division (OPNAV N98) and the NAVAIR Program Management Acquisition Executive (AIR-1.0) are sponsoring a study to evaluate the performance, operational capability and costs of fielding alternative systems to meet current Navy Mid-Air Collision Avoidance Capability (MCAC) requirements as defined in the Aircraft Survivability (AS) Initial Capabilities Document (ICD), OPNAV Instructions 13210.1A and other pertinent documents identified for collision avoidance capability. To support the study, Naval Air Systems Command (NAVAIR) Warfare Analysis and Integration Department (AIR-4.10) is conducting a market survey to obtain industry input relative to addressing current shortcomings. Responses will assist in the requirements generation process, development of the acquisition strategy, and budgetary submission. The primary purpose of a MCAC is to alert / warn the host aircraft's pilot(s) of other aircraft (i.e. "traffic") that pose an air-to-air collision threat to their aircraft. MCAC will use aural/visual and optionally tactile alert or warning to notify the aircrew of conflicting traffic or potential collisions. The primary goal is to reduce preventable accidents, loss of life or injury, and preserve valuable war fighter assets. The secondary purpose of a MCAC is to provide Situational Awareness (SA) of the surrounding airspace to the host aircraft's pilot(s). To do this, MCAC will need to sense traffic (i.e. have inputs from sensors). Once given this information, MCAC would be expected to track nearby aircraft, evaluate the potential for a mid-air-collision with one or more of these contacts and then respond with an aural/visual and optionally tactile alert or warning. These alerts, warnings, directives must (1) convey a sense of urgency, (2) be intelligible over other aircraft cockpit conditions, and (3) be easily understood by the host aircraft's pilot(s) throughout the warning / alert condition. Unnecessary alerts, warnings and directives must be minimized. The current four Naval (i.e. USN and USMC) aviation platforms that are the focus of the study are the AH-1Z, UH-1Y, MH-60R and MH-60S. Applicability of alternatives for use in other Naval aviation platforms will also be considered. The study will evaluate the use of a MCAC in domestic and international civil airspace, when operating in military training areas or on test ranges, and combat operations in high threat environments. Information regarding systems that perform collision avoidance in some or all of the operating environments listed above is desired. Threat vulnerabilities and potential effects from jamming will be considered. Initial Operating Capability (IOC) of FY-20 is currently planned, but mature alternatives could allow for an earlier IOC date. II. RFI ATTACHMENTS There are three attachments to this RFI. The three attachments are: 1. System Metrics template; 2. MIL-STD-881C-based Electronic Systems Work Breakdown Schedule template; 3. Technology Maturity Self-Assessment template. III. CONTENT OF RFI RESPONSE Responses to this RFI shall encompass end-to-end MCAC solutions. Five items are requested: 1. Volume 1.0 SYSTEM INFORMATION; 2. Volume 2.0 SUPPORTING INFORMATION; 3. Volume 3.0 COST; 4. Completed System Metrics spreadsheet; 5. Completed Technology Maturity Self-Assessment document. Templates for the System Metrics spreadsheet, MIL-STD-881C-based Electronic Systems Work Breakdown Schedule, and the Technology Maturity Self-Assessment are provided as attachments to this RFI. The requested contents of the three volumes are described in the following paragraphs. Requested content for the System Metrics spreadsheet and the Technology Maturity Self-Assessment document are contained within those documents. 1.0 SYSTEM INFORMATION 1.1 Provide a general description of the proposed system or solution. Responses should include these areas of interest: System Architecture, Applicable Standards, Operational Capabilities, Supportability, Environmental Qualifications, and level of encryption of broadcasted signals supported. 1.2 Provide configuration drawing(s) illustrating and quantifying the proposed system's geometric footprint, to include layout and system weight. 1.3 Is the proposed system presently in service? If so, identify the customers. What is the current production rate? What are the maximum production capacities? 1.4 What changes are planned to the existing system? Describe any changes required to allow the system to operate in various military aircraft (e.g. fixed wing, rotary wing, tiltrotor). 1.5 Describe how hardware and software commonality among different platforms is accomplished. Describe how software is loaded into the system. 1.6 Describe the capabilities of a situational awareness (SA) display if provided as part of the system. Describe how the SA display zooms, pans, and prevents overlapping of displayed symbology (i.e. cluttered display). 1.7 Describe the system's use of a modular open systems architecture. Describe the use of open standards with respect to the hardware and software including FACE (Future Airborne Capability Environment) conformance. 1.8 Provide the system reliability block diagrams, models, and predictions for Mean Time Between Failures. Predictions should be at the system and subsystem level. Include the basis for prediction and/or source of measured data. For measured data, provide usage information, including the environment (i.e. Aviation 3-M, commercial, etc.), and how the resultant reliability values were calculated for each WRA/SRA. Provide supporting data for the environmental parameters utilized. For items where usage data is not available, provide a prediction (using MIL-HDBK-217 as guidance), considering worst -case operating conditions of Airborne Rotary Winged (ARW), as defined in MIL-HDBK-217F, and thermal conditions of 55°C ambient temperature. In addition describe: a. Ground rules and assumptions used in the reliability predictions; b. Identification and allocation of software defects to the system reliability predictions as well as the process in place to mature software; c. Specific reliability design features such as redundancy or graceful degradation; d. How any COTS items and Non Developmental Items will be integrated into the system to meet subsystem level reliability requirements. 1.9 For the Mean Time to Repair (MTTR) and Maximum Time to Repair (MaxTTR) 95% provide the basis for prediction and/or source of measured data; provide a prediction (using MIL-HDBK-472 as guidance) for configuration items where empirical data is not available. Maintainability predictions shall assume a deployed maintenance scenario, i.e. utilizing the approved support concept without any additional support personnel or services. In addition, describe: a. Ground rules and assumptions used in MTTR and MaxTTR 95% calculations; b. Specific design for the maintainer and maintainability features. 1.10 Provide a list of all known software problems which affect functionality with descriptions of the problems. 2.0 SUPPORTING INFORMATION Some of the entries in the attached System Metrics spreadsheet require supporting information and/or rationale. Please provide the supporting information and/or rationale in this volume. Please structure the document such that it is clear for which entry in the System Metrics spreadsheet the supporting information and/or rationale is being provided (include the row number). 3.0 COST To the extent possible, provide Rough Order of Magnitude (ROM) cost estimates for total Acquisition cost comprised of development cost and procurement cost. When supplying the procurement cost, provide the number of units assumed for procurement. Please use the attached MIL-STD 881C-based Electronic Systems Work Breakdown Schedule (WBS) to report the costs in today's (FY2013) dollars. The complete MIL-STD-881C is available on the internet at http://www.everyspec.com/MIL-STD/MIL-STD-0800-0899/MIL-STD-881C_32553/. NOTE: YOU WILL NOT BE HELD TO THESE COSTS SHOULD THIS RFI RESULT IN AN RFP. IV. RESPONSE, SUBMITTAL, AND INSTRUCTIONS Interested parties should address all inquiries related to this RFI to the Government point of contact (POC), Mr. Glenn Woods at (301) 995-7643 or via email to Glenn.Woods@navy.mil. All responses submitted must specify on the cover page of the response, or in the transmittal letter submitted with the response, the business size/status of the organization (i.e., large business, small business, certified 8(a) concern, veteran-owned, HUB zone, women-owned, etc.). Small businesses which possess the required capability are encouraged to submit responses to this notice. Additionally, submissions shall include the CAGE code of the respondent, as well as POC information which may be utilized for any necessary clarification or to obtain additional data required by the analysis. Provide full unclassified response via one hardcopy and CD ROM that is Microsoft Office 2007 compatible or compatible with Adobe Acrobat 8.0. It is requested that the responses be in Times New Roman, 12 point font. Full response submissions to the above requested supporting unclassified data must be received no later than 4:00 PM EDT June 26, 2013 to the following address DEPARTMENT OF THE NAVY COMMANDER NAVAL AIR SYSTEMS COMMAND ATTN: GLENN WOODS 48110 SHAW ROAD, BLDG 2187 RM 1180-C1 PATUXENT RIVER MD 20670 In addition to the CDROM, unclassified responses shall be provided via email (if transmittal total size is less than 12 MB) to glenn.woods@navy.mil in a format compatible with Microsoft Office 2007 OR Adobe Acrobat 8.0. The Government does not anticipate that a comprehensive response to this RFI will contain CLASSIFIED information. To the extent practical, responses should be UNCLASSIFIED, complemented by CLASSIFIED appendices only if necessary. Classified information shall be provided by the respondent as appendices to the full response. Classified appendices (up to SECRET NOFORN) shall be in compliance with current DoD directives and procedures. Provide classified appendices, if applicable, via one hardcopy and CD ROM that is Microsoft Office 2007 compatible or compatible with Adobe Acrobat 8.0. The outer envelope addressed to: Outer Address: DEPARTMENT OF THE NAVY COMMANDER NAVAL AIR SYSTEMS COMMAND 48110 SHAW ROAD, BLDG 2187 RM 1180-C1 PATUXENT RIVER MD 20670 Inner: DEPARTMENT OF THE NAVY COMMANDER NAVAL AIR SYSTEMS COMMAND 48110 SHAW ROAD, BLDG 2187 RM 1180-C1 PATUXENT RIVER MD 20670 ATTN: AIR 4.10 Security Address inquiries regarding submission of classified information to Ms. Monica Smith (301) 757-2405. 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. Following a review of the responses received, NAVAIR may elect to schedule one-on-one meetings with some respondents or ask follow-up questions to gain additional information about the proposed solution(s). IV. ADDITIONAL INFORMATION This RFI is an exchange of information between Government and Industry. It is the first step of an iterative process aimed at understanding the existence of sources that can deliver a system capable of performing the MCAC function 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 4.10 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. Interested sources are advised that the employees of the following commercial firm under contract to the Government may serve as technical reviewers of information provided in response to the RFI: SAIC, Lexington Park, MD. By submission of a response, a source gives the Government permission to release proprietary information to employees of the organization listed above. Employees of the organizations that participate in the MCAC study are required to sign and submit Non-Disclosure Agreements (NDAs) held on file with the Government Furnished Information (GFI) Request Point of Contact (POC): The point of contact for SAIC is Mr. Craig Hurley, phone: (301) 862-6261, email: craig.a.hurley@saic.com. If any submitting company wishes to obtain a separate NDA with the aforementioned contractor prior to response submission, please contact the POC referenced above. If such NDA is obtained, please provide a copy to the Government with the response to this RFI. Beyond the above commercial firm, the Government will not release any marked proprietary information, received in response to the RFI, to any firm, agency, or individual outside the Government or MCAC study team. 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. V. POINTS OF CONTACT MCAC questions may be directed to the POC, Mr. Glenn Woods at (301) 995-7643 or via email to Glenn.Woods@navy.mil. Responses to questions from interested parties will be answered as applicable. Security submission of response questions may be directed to Ms. Monica Smith at (301) 757-2405. E-mail monica.smith@navy.mil
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DON/NAVAIR/N00421/41011GW/listing.html)
- Place of Performance
- Address: TBD, United States
- Record
- SN03044325-W 20130426/130424234528-a6996aa75a8ab648693e7814a8d898cf (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 |