NACRC_RFI_2016_1_13_1.docx
DOCX document 72 KB Posted
- Solicitation number
- N68335-16-RFI-0084
About this file
Revised RFI
View the file
Other files
| File | Type | Posted |
|---|---|---|
| NACRC_RFI_Clarifications_2016_1_13.docx | DOCX document | |
| NACRC_System_Metrics_template_2016_1_5.xlsx | XLSX spreadsheet | |
| NACRC_TMSA_Template_2015_11_30.docx | DOCX document | |
| NACRC_RFI_2015_12_1.docx | DOCX document | |
| NACRC_System_Metrics_template_2015_11_10.xlsx | XLSX spreadsheet | |
| NCRC_MIL-STD-881C-based_Electronic_Systems_WBS_Template_2015_10_1.docx | DOCX document | |
| NACRC_RFI_NDA_2015_11_24.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
UNCLASSIFIED
Request for Information (RFI):
NIMITZ-Class Aircraft Carrier Recovery Capability (NACRC)
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 (RFP). NO SOLICITATION DOCUMENTS EXIST AT THIS TIME. This RFI does not constitute an Invitation for Bids (IFB), a Request for Proposals, 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 Program Executive Officer for Tactical Aircraft Programs [PEO(T)] are sponsoring a study to evaluate the performance, operational capability, costs, and schedule of developing, installing, and supporting alternative arresting gear systems or approaches to meet the 2025 air wing identified in the CVN-21 Operational Requirements Document (ORD), Change 2, dated June 22, 2007 [CVN-21 ORD Re-validation Joint Requirement Oversight Council Memorandum (JROCM 040-15) dated April 27, 2015] and to account for weight growth associated with projected out-year carrier air wing CVW compositions. To support the study, Naval Air Systems Command (NAVAIR) Mission Engineering and Analysis Department (AIR-4.0M) 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 platforms that are the focus of the study are all active NIMITZ-Class aircraft carriers. Modification to the existing Mk-7 arresting gear, hybrid arresting gear system solutions, back fit of the Advanced Arresting Gear (AAG) – like arresting gear systems (partial or in full), and commercially available solutions, to include alternate build or planned Pre-Planned Product Improvement (P3l) strategies, will be considered for potential material solution alternatives.
Throughout this RFI the term “arresting gear system” is defined as one set of all the equipment required to arrest an aircraft. The term “shipset” is defined as the combination of sets of arresting gear systems that are installed on an aircraft carrier.
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 Structure template;
3. Technology Maturity Self-Assessment template.
III. CONTENT OF RFI RESPONSE
Responses to this RFI shall encompass NACRC solutions. Four items are requested:
1. Volume I TECHNICAL DESCRIPTION DOCUMENT (TDD);
2. Volume II COST;
3. Completed System Metrics spreadsheet;
4. Completed Technology Maturity Self-Assessment document.
The requested contents of the two 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.
VOLUME I - TECHNICAL DESCRIPTION DOCUMENT (TDD)
1. INTRODUCTION
1.1. Description of Alternative
Provide a general description of the proposed arresting gear shipset or solution for a NIMITZ-Class aircraft carrier. Responses should include these areas of interest: System Architecture, Applicable Standards, Operational Capabilities, and Environmental Qualifications which are integrated with the arresting gear system design or solution.
1.2. Definitions
Provide definitions for terms and abbreviations used in the TDD.
1.3. Reference Documents
Provide list of all referenced documents.
1.4. Programmatic Assumptions
Provide a list of programmatic assumptions used in development of the RFI response.
1.5. Top Level Schedule
Provide a projected master schedule that includes development, production, installation, test events and projected delivery of up to ten (10) shipsets for installation on NIMITZ-Class carriers, plus three (3) additional land based arresting gear system units. The three land based units will be installed at the Jet Car Track Site (JCTS), NAWCAD Lakehurst, Runway Arrested Landing Site (RALS), NAWCAD Lakehurst, and Mk-7 Arresting Gear site, NAWCAD Patuxent River. The JCTS and RALS sites will be used to support developmental testing. The NAWCAD Patuxent River site will be installed after completion of Milestone C of the acquisition process. If a commercial off the shelf (COTS) configuration is available indicate when that configuration could be delivered.
1.6. Data Rights
Clearly identify any information or arresting gear system elements that would be delivered with less than government purpose rights. Describe what open standards would be implemented and what proprietary standards would be implemented.
2. ARRESTING GEAR SYSTEM DESCRIPTION
2.1. Shipset Overview
Provide an overview of the shipset for a NIMITZ-Class aircraft carrier including identification of major subsystems.
2.2. Technical Assumptions
Provide a list of technical assumptions associated with the arresting gear system, to include defining any terms and abbreviations for Volume I.
2.3. Arresting Engine Subsystem
Provide a description of the arresting engine subsystem including the principles of operation.
2.4. Arresting Control Subsystem
Provide a description of the arresting control subsystem including the principles of operation.
2.5. Drive Fairlead Subsystem
Provide a description of the drive fairlead subsystem.
2.6. Operator Controls
Provide a description of the operator controls.
2.7. Ancillary Support Subsystems
Provide a description of the ancillary support subsystems including the principles of operation.
3. NIMITZ-CLASS CARRIER INTEGRATION
3.1. Shipset Configuration Layout
Provide configuration drawing(s) illustrating and quantifying the proposed shipset’s geometric footprint for both CVNs 68-75 and CVNs 76-77 NIMITZ-Class aircraft carrier, to include layout, area with height restrictions and system weight in long tons (2,240 lbs.). Identify the area with height required for each compartment in which equipment will be installed. Maximum available height is 8 foot. Identify the number of arresting engines and arresting wires for CVNs 68-75 and CVNs 76-77. Identify the run-out length in feet for each arresting engine.
3.2. Integration with Ship Services
Provide a description of the integration with all required ship services such as electrical, heating, ventilation and air conditioning (HVAC), seawater, chilled water, potable water, pressurized air, etc. required for installation of the shipset on NIMITZ-Class Aircraft Carriers.
3.3. Carrier Integration & Test Schedule
Provide a projected schedule for the carrier integration and test period that includes carrier modification/installation activities and test events necessary (not to include Aircraft Compatibility Testing or Flight Deck Certification) to check out the shipset aboard ship. Identify all required services such as crane and rigging, fire watch, etc.
4. ARRESTING GEAR PEFORMANCE
4.1. Arrestment Runout Tracking
Describe how the arresting gear system will maintain the recovering aircraft within the boundaries of the runout zone up to the maximum worst case aircraft engagement of 20 feet off-center (port or starboard offset) and the worst case skewed approach angle relative to the centerline of the flight deck landing area. Identify the maximum approach angle relative to the centerline for an approach on the centerline and ten feet (10 ft.) and twenty feet (20 ft.) off the centerline. Provide details on how the runout tracking was determined including all assumptions used.
4.2. Arresting Gear Energy Absorption Envelope
Identify the energy absorption envelope including the lower limit and upper limit in foot pounds (ft-lbs) . Describe the landing conditions [combinations of Max/Min A/C weights (lbs.) and Max/Min Engagement Speed (knots)] during which the arresting gear system can completely absorb the total arrestment energy (forward kinetic energy plus thrust energy) of the aircraft. Provide details on how the values were determined including a description of the arrestment loads being transferred to the aircraft for the Max/Min conditions. Use the Energy equation located in Paragraph 2.4 of the Government Furnished Information when performing energy calculations.
4.3. Peak to Mean Quotient
Provide the Peak to Mean ratio for aircraft with a landing weight of less than or equal to 25,000 lbs. and for aircraft with a landing weight of greater than 25,000 lbs. The term "mean" refers to the average hookload, as applied over the entire arrestment. "Peak" refers to the maximum instantaneous hookload impressed upon the aircraft, usually occurring shortly after engagement, as a result of arresting gear system response. Provide details on how the quotients were determined including all assumptions used.
4.4. Imparted Loads
Provide the imparted loads, which are the forces imparted onto the A/C by the arresting gear system during all arrestment phases. Provide the hook load in lbs. and the g load imparted onto the aircraft in g/sec for F/A-18 C/D, F/A-18E/F, EA-18G, F-35C, E-2 C/D, T-45C, and C-2A. Provide details on how the values were determined.
4.5. Arrestment to Battery Cycle Time
Identify the arrestment to battery cycle time in seconds. This time is the operational cycle of the arresting gear system for a single arrestment, defined as the time interval from when the aircraft initially engages the arresting gear system until the arresting gear system is fully retracted and in battery state. Battery state is defined as the arresting wire being in tension and on wire supports and the arresting gear is ready to engage incoming aircraft.
4.6. Sustained Recovery Rate
Identify the number of recoveries over a thirty (30) day period with air operations ongoing for twelve (12) hours per day. Provide details on how the value was determined including all assumptions used.
4.7. Surge Recovery Rate
Identify the number of recoveries over a four (4) day and a six (6) day period with air operations ongoing for twenty-four (24) hours per day. Provide details on how the value was determined including all assumptions used.
4.8. Peak Recovery Rate
Identify the number of recoveries over a 21 minute period. Provide details on how the value was determined including all assumptions used.
4.9. System Availability (Ao)
Provide the prediction for system availability for the shipset. Describe the availability of the arresting gear shipset considering mean cycles between operational mission failures, mean corrective maintenance duration, mean logistics delay time, and duty cycle. The Ao represents the minimum required equipment to recover aircraft, which could encompass a variable number of wires depending on selected architecture and redundancy. Provide details on how the value was determined including all assumptions used.
4.10. Mean Cycles Between Operation Mission Failures (MCBOMF) Provide the system reliability block diagrams, models, and predictions for Mean Cycles Between Operational Mission Failures (MCBOMF) for the shipset. One "cycle" is defined as one complete within specification arrestment/retract/ready sequence. An operational mission failure occurs when an operational anomaly, situation, or failure(s) results in the following: less than two arresting wires being operationally ready for the next event; barricade function not being operationally ready for the next event. 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 Naval, Sheltered and Naval, Unsheltered, 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;
How any COTS items and Non Developmental Items will be integrated into the system to meet subsystem level reliability requirements.
4.11. Mean Time to Repair (MTTR)
Provide the prediction for MTTR at the Organizational Maintenance Level ("O-Level") in hours. 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.
4.12. Mean Cycles Between Corrective Maintenance Actions (MCBCMA) Provide the reliability prediction with summation of all failure rates (no redundancy included) in hours. Provide details on how the value was determined including all assumptions used.
4.13. Critical System Reliability (ReCRSYS)
Provide the prediction of the critical system reliability of a controlled arrestment (no loss of life or loss of the aircraft) once an aircraft is engaged to the arresting gear system. Provide details on how the value was determined including all assumptions used.
4.14. Maximum Cable Tension
Identify the maximum cable tension experienced during aircraft arrestment operations, expressed as a ratio to cable breaking strength. Provide details on how the value was determined including all assumptions used.
4.15. Time to Convert from Arresting Wires to Barricade
Identify the time in minutes required to convert to emergency barricade recovery operations from normal operations Describe the steps required to convert to barricade operations. The Barricade Webbing Assembly to be used is NAVAIR Part Number 620007-108/1 (standard) or NAVAIR Part Number 614148-3 (E-2/C-2 arrestments only). The Barricade assembly is coupled to the arresting gear two clevis socket assemblies, NAVAIR P/N 317894-1 and lock rings, NAVAIR P/N 317894-1.
4.16. Time to Convert from Barricade to Arresting Wires
Identify the time in minutes required to convert from emergency barricade recovery operations to normal operations Describe the steps required to convert from barricade operations. The Barricade Webbing Assembly to be used is NAVAIR Part Number 620007-108/1 (standard) or NAVAIR Part Number 614148-3 (E-2/C-2 arrestments only). The Barricade assembly is coupled to the arresting gear two clevis socket assemblies, NAVAIR P/N 317894-1 and lock rings, NAVAIR P/N 317894-1.
5. SYSTEM DEVELOPMENT
Provide an overview of how any required system development will be accomplished. Provide detailed information on the following topics:
a) Software Product Engineering
b) Software Integration
c) Performance Modeling and Simulation including Verification, Validation, and Accreditation (VV&A)
d) Systems Integration Laboratory
e) Design Tools and Analysis
f) Developmental Testing (component and system)
g) Required Test Facilities (hardware and software)
6. PRODUCT SUPPORT DESCRIPTION
6.1. Product Support Management Approach (i.e. O-Level to OEM) Provide information regarding the product support strategy through the various phases of the acquisition life cycle for the proposed solution to include: engineering & manufacturing, developmental test support, operational test support, initial fielding, interim support, production, operational and depot support. Detail all assumptions used.
6.2. Design Interface & Maintenance Planning
Provide a top down breakdown (TDBD) of the proposed solution to the lowest replaceable unit. If a TDBD is not available, provide an estimate on the number of items predicted and rationale for the basis of the estimate. In addition, provide the estimated number of scheduled and unscheduled maintenance tasks including overhauls and maintenance concept for the proposed solution. Provide rationale and basis for the estimate detailing assumptions used. Identify any Hardware and/or Software standardization included in the proposed solution.
6.3. Training
Provide information on your training concept for the proposed solution. Include information regarding training system design, and materials & equipment required to adequately train operators and maintainers (courseware, curricula, instructor lead training, computer based training, simulators/virtual/immersive, maintenance training aids, part task trainers, and mock-ups). Provide specific examples of your experience in design, development and delivery of training systems to the Government. Provide the methodology used to determine the training requirements and your experience with NAVAIR and CNATT training requirements.
6.4. Technical Data
Define the technical data package for the proposed solution to include design documentation e.g. engineering drawings, models, operations and maintenance technical manuals, etc.
6.5. Support Equipment (SE)
Describe any anticipated support equipment requirements for operations and maintenance of the proposed system or solution. Provide details for each level of maintenance in the support strategy to include quantities and nomenclatures for the equipment.
6.6. Manpower and Personnel
Provide Manpower and Personnel Assessment that identifies the operators and maintainers that will be needed to support the proposed solution. Identify the number of operators and maintainers including anticipated personnel and skill levels.
7. TECHNICAL RISKS
Describe risks associated with the development, production, test, installation and operation of the system. Identify the likelihood and consequence of all identified risks. For consequences, quantify impacts where possible. Provide proposed mitigations for all identified risks. A notional example in a sample template is also provided below; however, note that this is a generic and summary-level risk. Additional detail, as applicable, is requested.
| Risk Statement |
| Risk Description |
| Likelihood |
(Highly Likely; Likely; Unlikely) Consequence (Severe Impact; Moderate Impact; Low Impact) Mitigation Strategy(ies)
| Given the limited physical constraints of the platform such as height and weight restrictions, there is a possibility of requiring modifications to physical characteristics of the platform and/or increased design complexity leading to cost and schedule impacts. |
| Historically, physical constraints of the platform have limited specific design characteristics, leading to increased schedule and cost requirements for the successful execution and use of the capability. Relevant examples include example 1, example 2 and example 3. Impacts to programmatic resources could reflect the following: impact 1, impact 2 and impact 3. |
| Likely: It is likely that this risk, given specific circumstances, could be realized within a particular timeframe. |
| Moderate: The consequence of realizing this risk would moderately impact schedule, cost and potentially technical performance if not addressed adequately. (3 months delay and $300k cost increase). |
| There are multiple mitigation strategies that may address this risk. |
Strategy 1: To minimize cost, schedule and technical performance, actual physical characteristics of the platform may be changed to address challenges.
Strategy 2: Another mitigation strategy.
VOLUME II - COST
2.0 Acquisition Cost
To the extent possible, provide Rough Order of Magnitude (ROM) cost estimates for total Acquisition cost in CY16$K comprised of development cost to include design and prototype development, QTY (1) initial shipset deliverables (number of arresting gear systems per shipset is variable based on system design) and QTY (2) arresting gear systems for test support at the JCTS and RALS sites, NAWCAD Lakehurst. Procurement cost should include hardware material, assembly and test/checkout. When supplying the procurement cost, provide per engine cost and common hardware cost for up to QTY (9) additional shipsets and QTY (1) additional land based arresting gear system unit at NAWCAD Patuxent River. Software costs should include any recurring software costs such as license fees.
Please use the attached MIL-STD 881C-based Electronic Systems Work Breakdown Structure (WBS) to report the costs in today’s (FY2016) 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/.
2.1 Operations and Support (O&S) Cost
Identify the O&S cost required to operate the system over a fifty (50) year period based on the information provided in Volume I, Section 6, Product Support Description.
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. GOVERNMENT FURNISHED INFORMATION (GFI)
Information concerning the current Mk-7 Mod 3 Arresting Gear on CVNs 68-75 and the Mk-7 Mod 4 Arresting Gear on CVNs 76-77 will be provided in a separate correspondence after receipt of the letter of intent (LOI) and a signed GFI Non-Disclosure Agreement (NDA) is returned. Please see Section V Response, Submittal, and Instructions for more information on the LOI. The GFI package will be Controlled Unclassified Information (CUI).
V. 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 with copies to Mr. Thomas Mischke, (301) 342- 8326, Thomas.Mischke@navy.mil.
Receipt of GFI:
To receive the Government Furnished Information, responding parties must submit a LOI (UNCLASSIFIED) no longer than six pages to the Government POC no later than 4:00 PM EST 26 January, 2016 with the following additional data in order to verify credentials (do not submit classified information):
(1) An UNCLASSIFIED description of your company’s experience and plan for addressing the questions listed in this RFI.
(2) CAGE code and CUI Mailing Address. Respondents must verify in the LOI that the Mailing Address that is associated with the CAGE Code is able to receive FEDEX packages.
(3) Point of Contact (POC) cleared to receive the CUI GFI package.
(4) Describe your company’s ability to manage and secure up to CUI information.
(5) POC to contact for any necessary clarification, to receive additional information, and for additional data desired by the analysis.
(6) Signed GFI NDA. The GFI NDA shall be signed by an authorized company representative and any employees that view or handle the data in the GFI package.
(7) Level of Classification for the Full Response. For additional guidance see Full Response Submissions section below.
(8) Current certified DD2345.
The letter of intent should be UNCLASSIFIED and include both an executive summary and a description of the plan to address the questions defined in the RFI. The cover letter and the GFI NDA pages do not count towards the six pages.
The Government Furnished Information is marked export control as follows:
WARNING: THIS DOCUMENT CONTAINS TECHNICAL DATA WHOSE EXPORT IS RESTRICTED BY THE ARMS EXPORT CONTROL ACT (TITLE 22, U.S.C. SEC 2751 ET SEQ) OR THE EXPORT ADMINISTRATION ACT OF 1979, AS AMENDED, (TITLE 50, U.S.C. APP 2401, ET SEQ). VIOLATIONS OF THESE EXPORT LAWS ARE SUBJECT TO SEVERE CRIMINAL PENALTIES. DISSEMINATE IN ACCORDANCE WITH PROVISIONS OF OPNAVINST 5510.161.
The GFI will be mailed on a CD to your designated data custodian on your certified DD2345. The information shall be handled in accordance with clauses 5252.227-9507 and 5252.227-9508 as follows:
| 5252.227-9507 | NOTICE REGARDING THE DISSEMINATION OF EXPORT-CONTROLLED TECHNICAL DATA (NAVAIR) (OCT 2005) | |
| (a) Export of information contained herein, which includes release to foreign nationals within the United States, without first obtaining approval or license from the Department of State for items controlled by the International Traffic in Arms Regulations (ITARS), or the Department of Commerce for items controlled by the Export Administration Regulations (EAR), may constitute a violation of law. | ||
| (b) For violation of export laws, the contractor, its employees, officials or agents are subject to: | ||
| (1) Imprisonment and/or imposition of criminal fines; and | ||
| (2) Suspension or debarment from future Government contracting actions. | ||
| (c) The Government shall not be liable for any unauthorized use or release of export-controlled information, technical data or specifications in this contract. | ||
| (d) The contractor shall include the provisions or paragraphs (a) through (c) above in any subcontracts awarded under this contract. |
| 5252.227-9508 | QUALIFIED U.S. CONTRACTORS FOR EXPORT-CONTROLLED TECHNICAL DATA (NAVAIR) (JUL 1998) | |
| (a) By Department of Defense (DoD) Directive 5230.25 (hereinafter referred to as "the Directive"), a program was established to allow Qualified U.S. Contractors to obtain export-controlled technical data under certain conditions. A "Qualified U.S. Contractor" is a private individual or enterprise (hereinafter described as a "U.S. Contractor") that, in accordance with procedures established by the Under Secretary of Defense for Research and Engineering, certifies as a condition of obtaining export-controlled technical data subject to the Directive from the Department of Defense, that: | ||
| (1) The individual who will act as recipient of the export-controlled technical data on behalf of the U.S. contractor is a U.S. citizen, or a person admitted lawfully into the United States for permanent residence and is located in the United States; | ||
| (2) Such data are needed to bid or perform on a contract with the Department of Defense, or other U.S. Government agency, or for other legitimate business purposes in which the U.S. Contractor is engaged, or plans to engage. The purpose for which the data are needed shall be described sufficiently in such certification to permit an evaluation of whether subsequent requests for data are related properly to such business purpose. | ||
| (3) The U.S. Contractor acknowledges its responsibilities under U.S. export control laws and regulations (including the obligation, under certain circumstances to obtain an export license prior to the release of technical data within the United States) and agrees that it will not disseminate any export-controlled technical data subject to the Directive in a manner that would violate applicable export control laws and regulations. | ||
| (4) The U.S. Contractor also agrees that, unless dissemination is permitted by the Directive, it will not provide access to export-controlled technical data subject to the Directive to persons other than its employees or persons acting on its behalf, without the permission of the DoD component that provided the technical data. | ||
| (5) To the best of its knowledge and belief, the U.S. Contractor knows or no person employed by it, or acting on its behalf, who will have access to such data, who is debarred, suspended or otherwise ineligible to perform under U.S. Government contracts; or has violated U.S. export control laws or a certification previously made to the Department of Defense under the provisions of the Directive. | ||
| (6) The U.S. contractor itself is not debarred, suspended, or otherwise determined ineligible by any agency of the U.S. Government to perform on U.S. Government contracts, has not been convicted of export control law violations, and has not been disqualified under the provisions of this Directive. | ||
| (b) Private individuals or enterprises are certified as Qualified U.S. Contractors by submitting a DD Form 2345 to Commander, Defense Logistics Information Services (DLIS), Federal Center, Battle Creek, Michigan 49017-3084. | ||
| (c) Canadian contractors may be qualified in accordance with the Directive for technical data that do not require a license for export to Canada under section 125.12 of the International Traffic in Arms Regulations and section 379.4(d) and 379.5(e) of the Export Administration Regulations, by submitting an equivalent certification to the DLIS. |
Full Response Submissions:
All Full Response RFI Submissions 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 2010 compatible or compatible with Adobe Acrobat X.
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 EST 15 March, 2016 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 2010 OR Adobe Acrobat X.
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 2010 compatible or compatible with Adobe Acrobat X. 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).
VI. 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 NACRC 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.0M 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 firms under contract to the Government may serve as reviewers of information provided in response to the RFI:
· Boulevard Consulting Group, 2001 Jefferson Davis Hwy, Suite 412, Arlington, VA 22202
· CSC Government Solutions LLC, 1201 M Street SE, Suite 400, Washington, DC 20003
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 Boulevard Consulting Group is Mr. Ryan Burge, phone: (703) 566-6913, email: ryan.burge@boulevardcg.com.
The point of contact for CSC Government Solutions LLC is Ms. Camilla Woolard, phone: (703) 461-2307, email: cwoolard@csgov.com
If any submitting company wishes to obtain a separate NDA with the aforementioned contractors prior to response submission, please contact the POCs referenced above. If such NDA is obtained, please provide a copy to the Government with the response to this RFI.
Beyond the above commercial firms, 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 NACRC 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.
VII. POINTS OF CONTACT
NACRC questions may be directed to the POC, Mr. Glenn Woods at (301) 995-7643 or via email to Glenn.Woods@navy.mil with copies to Mr. Thomas Mischke, (301) 342- 8326, Thomas.Mischke@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.
File details come from the government source that posted it. Updated .