REQUEST FOR WHITE PAPERS (RWP)

RWP Number N00421-21-9-0003

RWP Title: U.S. Marine Corps AH-1Z/UH-1Y Deployable Reconfigurable Mission Rehearsal Trainer (H-1 MRT)

White Papers Due Date/Time Deadline Extension: August 14, 2020 / 11 AM EDT Submit White Papers To RWP@cmgcorp.org

N00421-21-9-0003

Naval Air Warfare Center Aircraft DivisionOther Transaction Agreement

Statement of Need (SON)

Title of Requirement: U.S. Marine Corps AH-1Z/UH-1Y Deployable Reconfigurable Mission Rehearsal Trainer (H-1 MRT)

Project Number: N00421-21-9-0003

Estimated Prototype Price: $4.5M - $5.0M

Estimated Delivery Date of Prototype: March 2023

Project Security Classification: Unclassified

Minimum Acceptable Data Rights: Government Purpose

Problem Statement:

The Marine Light Attack Helicopter Squadrons (HMLA) have identified a requirement for a small, light, deployable mission training/mission rehearsal-training device capable of completing specific Training and Readiness (T&R) skill tasks for AH-1Z and UH-1Y pilots. The goal of the H-1 program is to provide a deployable reconfigurable AH-1Z and UH-1Y Mission Rehearsal Trainer (H-1 MRT) that will improve standardization and the application of Risk Management (RM) through the execution of Scenario-Based Training (SBT).

Desired Objective (product, system, tool, capability, process, analysis or model):

The desired objective of this effort is to deliver and install one deployable reconfigurable H-1 MRT to Camp Pendleton, California. Ancillary deliverables are anticipated to include, but not be limited to: technical data package, training manuals, etc. If this prototype is successful, the H-1 Program may desire to pursue production H-1 MRTs.

Minimum capability requirements of the Prototype:

The H-1 MRT shall have adequate capability and capacity to train HMLA pilots in initial and refresher decision-making training for the following tasks: Target Sighting Systems (TSS)/Britestar operation (sensor manipulation, display interpretation, aerial intercept geometry and control actuation), Cyclic and collective manipulation/button-toggle-trigger selection, Heads-Up Display (HUD), Multifunction Displays (MFDs), and basic flight operations related to Escort, Close Air Support (CAS), and Assault Support (AS) operations. Additional training requirements include land-based and shipboard takeoff, taxi, and landing procedures. To support these procedural requirements, the device shall include Landing Helicopter Assault (LHA)/Landing Helicopter Dock (LHD)/Amphibious Transport Dock (LPD)/ Dock Landing Ship (LSD) shipboard environments, Optical Landing Systems (OLS), Horizontal Position Indicator (HPI), Field Carrier Landing Practice (FCLP)/Deck Landing Qualifications (DLQs),

N00421-21-9-0003

and Tactical Air Navigation (TACAN)/Flight Instrument operations. The H-1 MRT shall be capable of SBT for pilots for the H-1 Core Mission Essential Tasks as shown in Table-1 Applicability Matrix listed below (excerpts from 3500.104B AH-1Z Training and Readiness (T&R) Manual, and 3500.20C UH-1Y Training and Readiness (T&R) Manual; note that all acronyms are articulated therein). To support SBT objectives/tasks, the device shall include weather, fuel, external stores (with aerodynamic and performance variables), and emergency procedural training.

Table-1: Mission Rehearsal Trainer (MRT) Training and Readiness (T&R) Applicability Matrix

Event Number T&R Description UH-1Y AH-1Z2300 Intro Day RECCE * *2500 Intro FCLP * *2700 NVD LLL A/C EPs *  3102 ASPT ESC REVIEW * *3202 Urban CAT *  3204 Long Range Degraded Nav CAT *  3206 CASEVAC Trk Code *  3300 Intro CAS * *3302 Intro NVD CAS * *3304 Intro Urban CAS * *3305 Armed Recon * *3306 Aerial Interdiction   *3307 SCAR * *3308 TRAP * *3400 IDF Control * *3401 FW/RW Ctrl Intro * *3402 FW Control * *3403 NVD FW Ctrl Intro * *3404 FAC(A) Review * *4105 MAT Intro *  4108 High Threat Insert *  4200 Helo ESC Med/High Threat * *4201 CAS Med/High Threat * *4202 Med/High Threat SCAR *  4205 AR Med/High Threat   *4206 AI Med/High Threat   *4207 SCAR   *4209 OAAW   *4300 OWP DACM   *4500 Conduct TAC(A) Proc *  5101 Instruments *  5102 INST Rev   *5200 (S) UH-1 Mission Profiles *5200 Rkt/Gun/Sys Rev *5201 OAS Scenario Dev/Instruction *5201 F/S Ord Del Rev *

N00421-21-9-0003

5210 Intro Sim Functions   *5211 Rev Sim Functions   *5400 FAC(A)I * *5904 NSI Standardization SIM * *6100 Annual INST Check * *6906 FAC(A) Stan track *6906 FAC(A) Standardization *

The MRTs shall incorporate an open architecture design enabling the maximum reuse of hardware and software for future modifications/upgrades to support AH-1Z and UH-1Y configurations to reduce future procurement costs. The USMC Tactical Environment (TEn) hardware and software is what all Marine Corps trainers use for network training; the system can be integrated into a trainer to allow communication with the network. The MRTs shall utilize the TEn, which will be provided as Government-Furnished Equipment (GFE), to enable interoperability and linking between multiple, co-located, MRTs. The MRT shall replicate the USMC AH-1Z and UH-1Y aircraft cockpit (i.e., switches, knobs, and displays) using flat screen/touch screen technology and include stick and rudder capability similar in function to the AH-1Z and UH-1Y aircraft. The MRT shall be designed to operate using shipboard and standard power, and include adequate surge protection. MRTs shall be designed in a manner enabling it, or its components, to be capable of being transported on LHA, LHD, LPD, and LSD class vessels, operate in a shipboard environment, and possess tie down capability.

Additional Desired Capabilities:

The H-1 MRTs should utilize AH-1Z and UH-1Y Operational Flight Programs (OFP) similar to those currently installed on AH-1Z and UH-1Y aircraft and their respective Flight Training Device (FTDs) series flight simulators. MRTs should incorporate technologically viable hardware and software components including, but not limited to, the following: Personal Computer (PC) - Based Host computer, Instructor Operator Station (IOS) computers, Software Support Environment (SSE), Visual Display System (VDS), Control Loaders, and Input/Output (I/O) components. These components should be reliable, supportable, and maintainable to prevent or mitigate technical obsolescence. The MRTs should utilize realistic flight models for simulated flight and integrate a relevant and robust threat environment that is capable of supporting linked training to other MRTs installed in the same location for network training capability. MRTs should replicate the full-spectrum operational aural cues of the AH-1Z and UH-1Y aircraft cockpit resident in the AH-1Z and UH-1Y FTD series flight simulators. MRTs should be capable of set-up/tear-down in a period of time not to exceed 75 minutes (Threshold requirement, T)/ 60 minutes (Objective, O), and Packaged for Shipping, Handling and Transportation (PHS&T) by two (2) people. When fully assembled, the MRT should not exceed 6 feet in length, width, and height.

Available Government Furnished Equipment/Information/Software (GFE/GFI/GFS):

1. Tech Refresh Mission Computer (GFE)2. NATOPS and NATIP for both AH-1Z and UH-1Y (GFI)3. Training and Readiness Manuals for both AH-1Z and UH-1Y (GFI)

N00421-21-9-0003

4. Government Owned Aerodynamic Model for both AH-1Z and UH-1Y (GFS)5. Aural cues for both AH-1Z and UH-1Y (GFS)6. Tactical Environmental network (TEn) (GFS)

Evaluation Factors for White Papers:

PMA-205/NAWC-TSD will conduct an evaluation of all eligible WPs submitted in response to this RWP based on an integrated assessment of the following:

The degree to which the solution meets the requirements of the SON. Evaluation of the potential impacts of the data rights assertions. Evaluation of significant nontraditional or one-third (1/3) cost share, if applicable. Evaluation of proposed ROM price against government funding profile.

White paper responses shall be limited to 15 pages.

*******Only Government personnel will evaluate the White Papers*********

Production: Successful completion of the initial prototype may result in award of follow-on production under provisions of Other Transaction Authority 10 U.S.C. § 2371b(f).

N00421-21-9-0003

WHITE PAPER INSTRUCTIONS

Overview

An RWP is issued by CMG to solicit White Papers from consortium members that detail their proposed technology solutions to address the challenges outlined in the corresponding Government Statement of Need (SON).

CMG members can submit White Papers individually, or collaborate via a team. CMG will work with each interested member to ensure that government expectations are met and statutory compliance is maintained. Draft White Papers must be submitted to CMG by the member deadline specified in this RWP for review for completeness and compliance. Upon completion of that review, the White Papers will be forwarded to the Government by CMG.

CMG members solely are responsible for all expenses associated with responding to this RWP. White Papers shall conform to the White Paper Template and adhere to the formatting instructions.

Non-traditional Defense Contractor Participation or Cost-Share Commitment

Each Prototype Project awarded under an Other Transaction Agreement (OTA) must meet at least one of the following conditions:

1. There is at least one Non-traditional Defense Contractor (NDC), small business or nonprofit research institution participating to a significant extent in the Prototype Project, or

2. At least one-third of the total cost of the Prototype Project is to be paid out of funds provided by parties to the transaction other than the Federal Government.

What is an NDC?

An NDC is an entity that is not currently performing and has not performed, for at least one year preceding the issuance of a prototype project solicitation, any contract or subcontract for the DoD that is subject to full coverage under the FAR-based Cost Accounting Standards (“CAS”). Full CAS coverage is required typically for contracts greater than $50 million. Firm-fixed price contracts and contracts with small businesses are exempt from all

N00421-21-9-0003

CAS requirements regardless of dollar value.

How Does an Entity Determine if it is an NDC?

A review of an entity’s DoD cost-plus contracts and subcontracts on which it has performed during the previous year will aid in determining NDC status. If none of the contracts or subcontracts was subject to full CAS coverage, then the entity is an NDC. OTA awards do not impact NDC status, as CAS does not apply to OTAs.

Are Small Businesses Automatically Considered NDCs?

Yes. Since contracts and subcontracts with small businesses are exempt from all CAS requirements, small businesses are deemed NDCs under OT Authority. An entity is considered a small business based upon its applicable North American Industry Classification System (“NAICS”) designation (as described at 13 C.F.R. §121.201) for the specific nature of the work being proposed.

Are Nonprofit Research Institutions Considered NDCs?

The 2018 NDAA made Nonprofit Research Institutions essentially the same as NDCs with respect to OT Authority.

Can a Subsidiary or a Division of a Corporation Qualify as an NDC?

Yes. Provided the definition of an NDC is met, the entity can be at the prime level, team members, sub-awardees, lower-tier vendors or intra-company business units, including a subsidiary or division of a Traditional Defense Contractor.

Regarding NDC Participation, What does “Significant” Mean?

Significant participation is determined on a project basis and is based on the importance of the NDC contribution to the overall execution or outcome of the proposed project. OT Authority statute does not prescribe a monetary threshold or percentage value to justify significance. Examples of “significant” participation are:

Supplying a new key technology or product, or unique capability;

Causing a material and quantifiable reduction in the project cost or schedule;

N00421-21-9-0003

Causing a measurable increase in the performance of the prototype;

Accomplishing a significant amount of the effort;

Value-added analysis not based on percentage of project work or value.

How does a Traditional Defense Contractor Satisfy the Cost-sharing Requirement?

If the member responding to an RWP is a Traditional Defense Contractor and there is no significant participation by an NDC in the project, the Traditional Defense Contractor is required to expend resources on the project amounting to one-third of the project cost. Cost-sharing does not involve funds paid directly to the Government. There are two types of cost-sharing:

Cash—outlays of funds to perform under the project for labor, materials, new equipment or subcontractor effort; sources can include new IR&D funds, profit or fee from another contract, and overhead or capital equipment expense pool;

In-Kind—reasonable value of equipment, materials or other property used in performance under the project.

White Paper Format

The White Paper (WP) template is provided as an attachment to this RWP. The following formatting requirements apply:

Times New Roman 10 (or larger), single-spaced, single-sided, 8.5 by 11 inches

Smaller type may be used in figures and tables, but must be clearly legible

Margins on all sides (top, bottom, left and right) should be at least 1 inch

Refer to the SON for the requirement specific page limit. The page limit excludes the White Paper Cover Sheet and Affirmation of Business Status Certification(s)

WPs shall include a cover sheet, not counted toward the page limit, that includes:

o Prototype Project Title

N00421-21-9-0003

o Primary point of contact, secondary point of contact, and FSO, if applicable, including name, address, phone, and e-mail contact information

o Total Solution Rough-Order-of-Magnitude price

Shaded text in the White Paper Template indicates areas for entry of information by the member. Shading should be removed before submittal of the White Paper.

DO NOT SUBMIT ANY CLASSIFIED INFORMATION

Technical Requirements

Each WP shall contain the following information:

Background and Benefits of Proposed Solution

Technical Approach, including clearly defined prototype solution

Schedule and Deliverables

Participants, including description of contributions and significance of each

N00421-21-9-0003

Data Rights Assertions: Identify any intellectual property, patents and inventions involved in the proposed solution and associated restrictions on Government use of that intellectual property, patents, and inventions. The following information shall be presented for all assertions:

o Technical data, computer software or patent to be furnished with restriction

o Basis for assertion

o Asserted rights category

o Name of entity asserting restrictions

If no restrictions are applied, insert “None” in each column.

Data Rights Withholding: Identify any technical data or software involved in the proposed solution that shall NOT be delivered for Government use. The following information shall be presented:

o Technical data and computer software being withheld

o Name of entity owning the technical data and computer software

If no restrictions are applied, state No Withholding.

Cost Section Requirements

The Government will be considering affordability in making its source selection decision; therefore, the White Paper shall contain cost information as requested in the table in Section 6.0 of the White Paper Template.

Evaluation Criteria

The Government will conduct an evaluation of all eligible WPs submitted in response to this RWP based on criteria identified within the SON.

Basis for SelectionIt is the Government’s intention to select, negotiate and fund Prototype Projects from the submitted WP(s). The WP selection will be conducted in accordance with the Government’s procedures and the evaluation criteria identified herein. The Government will make a determination whether to:

Select the WP(s), or some portion of the WP(s), and/or

N00421-21-9-0003

Retain the WP(s) in a library for potential future requirements in accordance with the terms of the OTA.

The WP selection decision will be provided to CMG, and the Government will issue a Request for Proposal(s) to CMG for the selected WP(s).

Affirmation of Business Status Certification

Each participant proposed in the WP shall complete the Business Status Certification which is provided as an attachment to this RWP.

These certifications shall be included as an attachment to the WP and will not count toward the page limit.

Export Control

Research findings and technology developments arising from the resulting RWP may constitute a significant enhancement to the national defense and to the economic vitality of the United States. As such, in the conduct of all work under the subsequent PPA(s), the recipient will comply strictly with the International Traffic in Arms Regulation (22 CFR 120-130), the National Industrial Security Program Operating Manual (DoD 5220.22-M) and the Department of Commerce Export Regulation (15 CFR 730-774).

Points of ContactQuestions regarding White Paper procedures should be directed to the CMG Contract Management Office, 540-937-6300 or via email to RWP@cmgcorp.org.

N00421-21-9-0003

WHITE PAPER TEMPLATE

RWP Number Insert RWP Number from Request for White Papers (RWP) cover page

Proposed Project Title Insert Title from RWP cover page

Submittal Date To be completed by ConsortiumSubmitted By Insert Consortium Member nameFacility CAGE Code Insert Facility CAGE Code

Consortium Member Point of Contact (POC)**Note: POCs shall be from the prime member’s corporation, please do not insert contact information for subcontractor participants.

POC NamePOC AddressPOC PhonePOC Email

Primary Secondary FSO

Total Project ROM Price

$ Insert Total Proposed Project Price Including 3.8% Consortium Fee

Proposed Project Resource Share

$ Insert Amount of Resource Share (if applicable)

Net Government Cost

$ Insert total ROM price less Proposed Resource Share

Signed (electronic signature is acceptable)

Amounts should be presented in whole dollars only

N00421-21-9-0003

X

SECTION 1.0 BACKGROUND AND BENEFITS OF PROPOSED SOLUTION

Describe the proposed solution, including how the Government’s requirements shown in the Statement of Need are being addressed. Provide a brief description of the “new” capability that will result.

SECTION 2.0 TECHNICAL APPROACH

Describe the design and detailed technical approach for achieving the proposed prototype solution. Clearly describe the proposed prototype and ensure that it is included as a deliverable in Section 3.0.

SECTION 2.1 PROJECT TASKS

Describe the specific tasks required for project execution. If a phased/element approach is indicated in the Government Statement of Need, the tasks shall be detailed by phase/element.

SECTION 2.2 RISKS

Describe the technical maturity of the proposed solution and its readiness to meet the Government’s requirements. Describe any technical, cost and schedule risks associated with achieving the proposed solution.

SECTION 2.3 FACILITY/PERSONNEL CLEARANCE

The current personnel and facility(ies) level of [Consortium Member name]’s is [Insert classification level].

N00421-21-9-0003

SECTION 3.0 PROJECT SCHEDULE AND DELIVERABLES

Milestone DeliverableEstimated Delivery

(Months after Award)

Insert list of milestones

Insert list of deliverables associated with each milestone (at a minimum, the proposed prototype and a final report must be included as deliverables)

Insert estimated lead time in terms of months after award for each milestone/deliverable.

The total proposed project duration is [Insert proposed period of performance in months] months from project award.

SECTION 4.0 PARTICIPANTS

N00421-21-9-0003

Participants (including Consortium Member)

Business Status(check one)

Participant Contribution andSignificance to Overall Project

Insert Consortium Member

Traditional Non-traditional Nonprofit

Research Institution

Insert detailed, quantifiable description which addresses the following:

A.)What specific tasks will this Participant be accomplishing for this project?

B.)Why are these Participant's tasks significant to this project?*

C.)How is this Participant uniquely qualified to provide these tasks for this project?

Insert separate row(s) for each additional participant. Delete row(s) as applicable if Consortium Member is the only participant.

Traditional Non-traditional Nonprofit

Research Institution

Insert detailed, quantifiable description which addresses the following:

A.)What specific tasks will this Participant be accomplishing for this project?

B.)Why are these Participant's tasks significant to this project?*

C.)How is this Participant uniquely qualified to provide these tasks for this project?

*Significance is defined as supplying a new key technology or product, accomplishing a significant amount of the effort, causing a material reduction in the cost or scheduling or causing an increase in the performance. Any vendor proposing labor costs must be listed as a participant.

SECTION 5.0 DATA RIGHTS

Data Rights Assertions: All intellectual property, patents and inventions involved in the proposed solution and the associated restrictions on the Government’s use of that intellectual property, patents and inventions are presented in the table below. If no assertions are being made, state as such.

N00421-21-9-0003

Data Rights Withholding: Identify any technical data or software involved in the proposed solution that shall NOT be delivered for Government use are presented in the table below. If none, state No Withholdings.

Technical Data/ Computer

Software/ Patent to be Furnished with Restrictions

or Withheld

Basis for Assertion or Withholding

Asserted Rights Category

Name of Entity Asserting

Restrictions or Withholding

Identify the technical data/software/patent to be furnished with restriction or withheld (insert “None” if no restrictions apply)

Indicate whether development was exclusively or partially at private expense. If development was not at private expense, enter the specific reason for asserting that the Government’s right should be restricted

Insert asserted rights category (e.g., limited rights (data), restricted rights (software), government purpose rights, SBIR data rights or specifically negotiated license)

Insert corporation or individual

*If COTS licenses will be required, please list them here.

SECTION 6.0 ROUGH ORDER OF MAGNITUDE (ROM) COST

Resource Share (if applicable) is proposed as follows:

Cash into Project: [Describe and quantify the proposed cash contribution(s) being made for use on the project, or insert N/A].

In-Kind Contributions: [Describe and quantify the proposed in-kind contribution(s) being made for use on the project, or insert N/A].

N00421-21-9-0003

*Amounts should be presented in whole dollars only

N00421-21-9-0003

Cost Element Total Description/Comments

Prime Contractor Labor $ Insert generic position titles, estimated rates and labor hours

Subcontractor/Consultant Labor

$ Insert generic position titles, estimated rates and labor hours. If more than one Subcontractor is listed, provide cost break-out by Subcontractor.

Material/Equipment $ Insert list of proposed material/equipment

Other Direct Costs (ODC)

$ Describe proposed ODC (outside services, conference fees, software licenses, other fees/royalties, etc.)

Travel $ Describe estimated travel (e.g., travel to customer site(s) for meetings, etc.)

Proposed Project Total $ Sum of cost elementsConsortium Fee $ Cost-share amount (if applicable)

Total Project ROM Price $ Amount after cost share is deducted

Proposed Project Resource Share

$ 3.8% Applied to Total Price per OTA terms

Net Government Cost $ To be confirmed by CMG

Affirmation of Business Status CertificationEach participant shall complete a separate certification. These certifications will not count toward the page limit. Participant Name      Proposed NAICS Code      Industry Size Standard (Small/Large)      DUNS No.      CAGE Code      Active SAM Registration Yes No Expiration Date:     Address 1      Address 2      City/State/Zip      POC Name/Title      POC Phone/Email      

Check one of the following boxes:

Non-traditional Defense Contractor (NDC) — A Non-traditional Defense Contractor is an entity that is not currently performing and has not performed, for at least the one-year period preceding the issuance of this Request for White Papers by the Department of Defense, any contract or subcontract for the Department of Defense that is subject to full coverage under the cost accounting standards prescribed pursuant to Section 1502 of Title 41 of the U.S. Code and the regulations implementing such section.

All small businesses are considered NDCs. A small business is a business concern as defined under Section 3 of the Small Business Act (15 U.S.C. 632). To be considered a small business for the purposes of this RWP, a concern must qualify as a small business under the size standard for the proposed North American Industry Classification System (NAICS) code, as described at 13 C.F.R. 121.201.

Nonprofit Research Institution — means a nonprofit institution, as defined in 15 U.S.C. §3703, and includes federally funded research and development centers, as identified by the National Scientific Foundation in accordance with the Government-wide Federal Acquisition Regulation issued in accordance with 41 U.S.C. §1303(a)(1) (or any successor regulation thereto).

Traditional Defense Contractor — A traditional defense contractor is an entity that does not meet the definition of a Non-traditional Defense Contractor (NDC) or a Nonprofit Research Institution.

This is to certify that the above is accurate, complete and current as of insert date for insert RWP number.

N00421-21-9-0003

Signature (electronic signature is acceptable)

X

Date Signed      

N00421-21-9-0003