a study to evaluate the performance, operational capability and costs of fielding alternative systems to meet current Navy EVA requirements as defined in the Aircraft Survivability (AS) Initial Capabilities Document (ICD)

Closed Special Notice Posted

Solicitation number
EVARFI
Agency
Responses due
Set-aside
No set-aside

Opportunity facts

NAICS code
541512 Computer Systems Design Services
Place of performance
TBD, United States

Notice details come from SAM.gov. Updated .

Notice text

2 versions

Update #2 · Latest ·



Request for Information (RFI):
Enhanced Visual Acuity (EVA)


I. SUMMARY


This announcement constitutes a Request for Information (RFI) for planning purposes (FAR 15.201(e)) to obtain cost, 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 EVA requirements as defined in the Aircraft Survivability (AS) Initial Capabilities Document (ICD), and other pertinent documents identified for enhanced visual acuity. 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 EVA is increased situational awareness primarily in low light (night) conditions and secondarily in a Degraded Visual Environment (DVE), defined as the presence of obscurants (e.g. fog, dust, blowing sand, heavy rain, etc.), that reduce aircrew visibility to the point where situational awareness is lost and aircraft control cannot be maintained as it is in visual meteorological conditions. EVA alternatives are limited to head mounted systems. Integration of the alternatives with available sensors on the study platform(s) will be assessed.


The current three Naval (i.e. USN and USMC) aviation platforms that are the focus of the study are the AH-1Z, UH-1Y, and MH-60S. Applicability of alternatives for use in other Naval aviation platforms will also be considered. Initial Operating Capability (IOC) of FY-19 is currently planned, but the schedule for alternatives could allow for an earlier IOC date.


II. RFI ATTACHMENTS


There are four attachments to this RFI. The four attachments are:


1. System Metrics template;
2. MIL-STD-881C-based Electronic Systems Work Breakdown Structure template;
3. Manufacturing Readiness Self-Assessment template;
4. Technology Maturity Self-Assessment template.


III. CONTENT OF RFI RESPONSE


Responses to this RFI shall encompass EVA solutions. Six items are requested:


1. Volume 1.0 SYSTEM INFORMATION & PROGRAMMATICS;
2. Volume 2.0 SUPPORTING INFORMATION;
3. Volume 3.0 COST;
4. Completed System Metrics spreadsheet;
5. Completed Manufacturing Readiness Self-Assessment
6. Completed Technology Maturity Self-Assessment document.


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 & PROGRAMMATICS


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, Aircrew Operation and Controls, Compatibility with Chemical and Biological gear, Supportability, Environmental Qualifications and sensors which are integrated with the system or solution.
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 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.4 Describe how hardware and software commonality among different platforms is accomplished. Describe how software is loaded into the system.
1.5 Describe how the system is compatible with Optimized Top Owl (OTO) and Helmet Display Tracking System (HDTS) in use by AH-1Z, UH-1Y and MH-60S including helmet tracking. Describe how helmet/head tracking (including accuracy) is accomplished when the alternative is not used with OTO or HDTS.
1.6 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.7 Provide the system reliability block diagrams, models, and predictions for Mean Time Between Failures (MTBF). 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.8 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.9 Describe current or planned maintenance/inspection procedures.
1.10 Describe unique packaging, handling, storage, and transportation requirements including service life, storage life, and hazardous materials.
1.11 Provide a projected master schedule that includes installation, test events and projected delivery of twenty (20) units. If a commercial off the shelf (COTS) configuration is available indicate when that configuration could be delivered.
1.12 Identify the type of data rights which will be provided to the government.


2.0 SUPPORTING INFORMATION


Please provide supporting information and/or rationale for the entries in the attached System Metrics spreadsheet 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


3.1 Acquisition Cost


To the extent possible, provide Rough Order of Magnitude (ROM) cost estimates for total Acquisition cost comprised of development cost and procurement cost including any recurring software costs such as license fees. 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 Structure (WBS) to report the costs in today's (FY2014) dollars. If WBS definitions are required, please refer to the complete MIL-STD-881C which is available on the internet at http://www.everyspec.com/MIL-STD/MIL-STD-0800-0899/MIL-STD-881C_32553/.


3.2 Operations and Support (O & S) Cost


Provide insight into the O & S cost required to field the system. Describe the vendor's preferred maintenance approach for the system (i.e. O-Level to OEM). For the helmet mounted portion of the system, explain how the maintenance is expected to differ from the current night vision goggle system used on the AH-1Z, UH-1Y, and MH-60S platforms. Although unscheduled maintenance is discussed in sections 1.8 and 1.9 above, please provide details regarding any scheduled maintenance for the system to include the following:
• Description of scheduled maintenance task
• Where maintenance will be performed
• Time between maintenance actions
• Time required to perform maintenance


If required, please describe any manpower/training impacts this system will have on the AH-1Z, UH-1Y, and MH-60S platforms.


NOTE: YOU WILL NOT BE HELD TO THESE COSTS SHOULD THIS RFI RESULT IN AN RFP, HOWEVER THE COSTS SHOULD BE AS ACCURATE AS POSSIBLE.


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 August, 4, 2014, 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 EVA 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.


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 EVA study team.


V. POINTS OF CONTACT
EVA 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

.

Update #1 ·

 


Request for Information (RFI):
Enhanced Visual Acuity (EVA)


I. SUMMARY


This announcement constitutes a Request for Information (RFI) for planning purposes (FAR 15.201(e)) to obtain cost, 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 EVA requirements as defined in the Aircraft Survivability (AS) Initial Capabilities Document (ICD), and other pertinent documents identified for enhanced visual acuity. 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 EVA is increased situational awareness primarily in low light (night) conditions and secondarily in a Degraded Visual Environment (DVE), defined as the presence of obscurants (e.g. fog, dust, blowing sand, heavy rain, etc.), that reduce aircrew visibility to the point where situational awareness is lost and aircraft control cannot be maintained as it is in visual meteorological conditions. EVA alternatives are limited to head mounted systems. Integration of the alternatives with available sensors on the study platform(s) will be assessed.


The current three Naval (i.e. USN and USMC) aviation platforms that are the focus of the study are the AH-1Z, UH-1Y, and MH-60S. Applicability of alternatives for use in other Naval aviation platforms will also be considered. Initial Operating Capability (IOC) of FY-19 is currently planned, but the schedule for alternatives could allow for an earlier IOC date.


II. RFI ATTACHMENTS


There are four attachments to this RFI. The four attachments are:


1. System Metrics template;
2. MIL-STD-881C-based Electronic Systems Work Breakdown Structure template;
3. Manufacturing Readiness Self-Assessment template;
4. Technology Maturity Self-Assessment template.


III. CONTENT OF RFI RESPONSE


Responses to this RFI shall encompass EVA solutions. Six items are requested:


1. Volume 1.0 SYSTEM INFORMATION & PROGRAMMATICS;
2. Volume 2.0 SUPPORTING INFORMATION;
3. Volume 3.0 COST;
4. Completed System Metrics spreadsheet;
5. Completed Manufacturing Readiness Self-Assessment
6. Completed Technology Maturity Self-Assessment document.


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 & PROGRAMMATICS


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, Aircrew Operation and Controls, Compatibility with Chemical and Biological gear, Supportability, Environmental Qualifications and sensors which are integrated with the system or solution.
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 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.4 Describe how hardware and software commonality among different platforms is accomplished. Describe how software is loaded into the system.
1.5 Describe how the system is compatible with Optimized Top Owl (OTO) and Helmet Display Tracking System (HDTS) in use by AH-1Z, UH-1Y and MH-60S including helmet tracking. Describe how helmet/head tracking (including accuracy) is accomplished when the alternative is not used with OTO or HDTS.
1.6 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.7 Provide the system reliability block diagrams, models, and predictions for Mean Time Between Failures (MTBF). 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.8 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.9 Describe current or planned maintenance/inspection procedures.
1.10 Describe unique packaging, handling, storage, and transportation requirements including service life, storage life, and hazardous materials.
1.11 Provide a projected master schedule that includes installation, test events and projected delivery of twenty (20) units. If a commercial off the shelf (COTS) configuration is available indicate when that configuration could be delivered.
1.12 Identify the type of data rights which will be provided to the government.


2.0 SUPPORTING INFORMATION


Please provide supporting information and/or rationale for the entries in the attached System Metrics spreadsheet 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


3.1 Acquisition Cost


To the extent possible, provide Rough Order of Magnitude (ROM) cost estimates for total Acquisition cost comprised of development cost and procurement cost including any recurring software costs such as license fees. 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 Structure (WBS) to report the costs in today's (FY2014) dollars. If WBS definitions are required, please refer to the complete MIL-STD-881C which is available on the internet at http://www.everyspec.com/MIL-STD/MIL-STD-0800-0899/MIL-STD-881C_32553/.


3.2 Operations and Support (O&S) Cost


Provide insight into the O&S cost required to field the system. Describe the vendor's preferred maintenance approach for the system (i.e. O-Level to OEM). For the helmet mounted portion of the system, explain how the maintenance is expected to differ from the current night vision goggle system used on the AH-1Z, UH-1Y, and MH-60S platforms. Although unscheduled maintenance is discussed in sections 1.8 and 1.9 above, please provide details regarding any scheduled maintenance for the system to include the following:
• Description of scheduled maintenance task
• Where maintenance will be performed
• Time between maintenance actions
• Time required to perform maintenance


If required, please describe any manpower/training impacts this system will have on the AH-1Z, UH-1Y, and MH-60S platforms.


NOTE: YOU WILL NOT BE HELD TO THESE COSTS SHOULD THIS RFI RESULT IN AN RFP, HOWEVER THE COSTS SHOULD BE AS ACCURATE AS POSSIBLE.


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 August, 4, 2014, 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 EVA 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.


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 EVA study team.


V. POINTS OF CONTACT

EVA 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

Files

On GovTribe

Work this opportunity

  • Track it in your pipeline
  • Find teaming partners
  • Similar opportunities
  • Ask GovTribe AI about this opportunity

GovTribe for Federal Contractors