N6134019R0096 SF30 Amendment 03.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to provide the follow ing:

1. To update Section L-Instructions, Conditions and Notices to Bidders.

2. Where track changes w ere not apparent the changes are highlighted in pink. All other items remain unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

1 18

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 24-Apr-2020

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street , County, State and Zip Code) X N6134019R0096

X 9B. DATED (SEE ITEM 11)

03-Mar-2020

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

24-Apr-2020

CODE

NAWCTSD 253

CODE 2.5.3.7.1

12211 SCIENCE DRIVE

ORLANDO FL 32826-3224

N61340 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N6134019R0096

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

PART A GENERAL INSTRUCTIONS

1. GENERAL

Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to fully assess the capabilities of the Offeror to perform all requirements. The proposal must be sufficient in detail and scope to enable evaluation and provide the evaluators a clear understanding of the Offeror’s approach, expertise, and capability as required by the solicitation. Proposals must demonstrate that the Offeror has a thorough understanding of all requirements and associated risks and is able, willing, and competent to devote the resources necessary to meet all requirements. The Offeror shall not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. Offerors are advised that the Government may incorporate any part of the Offeror’s proposal deemed beneficial to the Government, into the final contract. Price information, (e.g., dollar values and/or hourly rates) shall appear only in Annex B (Small Business Subcontracting Plan), Volume 4 (Price), and Volume 5 (Contract Administration). Alternate proposals are not acceptable

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the responsibility of the Offeror to present enough information to allow the Government to evaluate its proposal.

Unsubstantiated statements that the prospective Offeror understands, can or will comply with the specifications, or paraphrasing the requirements or parts thereof are considered inadequate and may render a rating of unacceptable.

The Offeror must include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. There is no need to repeat information in more than one volume. The detailed information must be included in the most logical place and may be summarized and referenced in other areas if an overlap exists.

Do not provide elaborate brochures or other presentation material beyond that sufficient to present a complete and effective proposal.

Throughout these instructions, “Offeror” is defined as the prime contractor with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. A “Joint Venture” (JV) is a partnership or teaming arrangement that is formed for the purpose of responding to this solicitation when the prime contractor consists of more than one legal entity. “JV Team Members” are the entities that make up a Joint Venture. The term “entity” is used to mean any or all of the following: prime contractor, JV, JV team members, any subcontractor, and corporate parent, division, subsidiary, or affiliate (e.g., any contractor with a different CAGE Code/DUNS than the Offeror).

The following entities are defined as principal entities and only principal entities will be used in the corporate experience evaluation: (a) the prime contractor; (b) JV Team Members; and (c) other entities that are proposed to perform at least 20.00% of the proposed total price for the contract; and (d) entities that are proposed to perform a critical function, whether technical or financial, in the performance of the resulting contract. Critical functions include but are not limited to: visual systems, software, and databases. Offerors are advised that in order to demonstrate work commitment, each principal entity must be identified in Volume 4 Price and associated with a commensurate dollar value.

2. PROPOSAL FORMAT AND SUBMISSION

Unless otherwised stated, proposals must be formatted using a Times New Roman 12 point normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for standard 8.5 x 11 inch paper.

If Government attachments have a different format/font, the Offeror may use the format/font in the attachment as provided. All pages should be numbered with volume, paragraph, and page numbers. If the Offeror uses graphs to convey information, the graphs must show enough detail to easily discern the information described. Graphs and tables should be presented in no smaller than a 10 pt. font. Graphs should contain a grid, which allows values to be read directly from the graph to the same detail that a 10 x 10 to the ½-inch grid provides. Graphic resolution should be consistent with the purpose of the data presented. Text utilized in charts, figures, and graphics should also be no smaller than a 10pt font and may use a font type selected by the Offeror. Each volume, book, or annex should be provided separately in a 3-ring binder. The binders should be of an appropriate thickness for the number of pages it contains (e.g., a 30-page book should not be placed in a 2-inch binder).

2.1 Electronic Submission of Proposal

This section is intended to provide information to the Offeror on the electronic format and application software to be used for submitting proposals. Use of the software and procedures described in this section will reduce the amount of time and effort needed to receive and install proposals onto the electronic evaluation system, and will ensure that the proposals received are suitable for reading electronically.

2.1.1 Electronic Proposal Media

The Offeror should submit all volumes of its proposal electronically via DOD Safe compatible with the operating system and applications defined in Section 2.1.2 (Operating System and Applications). For this solicitation, Annex B Small Business Subcontracting Plan; Volume 4 Price; and Volume 5 Contract Administration, contain price information and should be delivered in separate files from the remainder of the proposal.

2.1.2 Operating System and Applications

The proposals will be accessed utilizing the Microsoft Windows 10 Operating System. Proposal information shall be submitted using the following applications: Microsoft Word 2016, Microsoft Excel 2016, Microsoft PowerPoint 2016, and Microsoft Project 2016; however, letters and other signed documents shall be provided as a fully searchable Portable Document Format (.pdf) file. Use of other application software for submission of proposals is prohibited except where specific instructions for non-.pdf or Office 2016 applications are provided.

2.1.3 Hyperlinks

Offerors may use hyperlinks within and among proposal volumes. However, there shall be no links from volumes that do not contain cost/price information to volumes that do contain cost/price information and the hyperlinks shall not lead to an external site.

2.1.4 Virus Free Electronic Submission

Offerors are responsible for ensuring that its electronic proposal is virus free. The Offeror shall certify, in its proposal cover letter, that all electronic proposal information delivered throughout the evaluation (e.g., original proposal submission, responses to evaluation notices, Final Proposal Revisions) has been or will be checked for viruses and certify that its files are virus free. The Offeror should specify the software, version, and virus definition used/that will be used to check the data.

2.1.5 Multimedia

The Offeror should not embed sound or video (e.g., MPEG) files within the proposal submission.

2.1.6 Graphics

Large files require greater computer system resources and are discouraged. The Offeror is encouraged to:

a. Simplify the color palette used in creating figures and minimize the use of color print or graphics to the maximum extent possible;

b. Minimize size of graphics files; and

c. Avoid scanned images.

2.1.7 File Naming Conventions

Valid extensions for files using their associated applications are listed below in Table G-1 (file Extensions):

Table G-1 File Extensions

Type of Application/Files Valid Extensions Portable Document Files .pdf Microsoft Word documents .docx Microsoft Excel documents .xlsx Microsoft Power Point .pptx Microsoft Project .mpp

The Offeror shall follow the basic structure of the file naming convention in Table G-2 (Offeror Electronic File Naming Convention) for electronic file submissions (e.g., proposal volumes, attachments, appendices), where "#" represents the sequential numbering of files. Offeror’s shall keep the file name as short as possible (i.e., under 40 characters) so that the files are accessible on Government share drives. Files with longer names may become corrupt or inaccessible.

The Offeror should provide one folder for each volume or annex, containing all electronic files requested within the volume or annex. Please submit each volume, book, or annex as one file if possible. Offerors should not provide each section/paragraph as separate files.

The Offeror shall ensure that the electronically submitted files are directly traceable to paper copy submittals.

3. PROPOSAL CONTENT AND VOLUMES

The Offeror must present its proposal information in a manner that facilitates a one for one comparison between the information presented and Section L proposal instructions. Proposal information must be structured such that its paragraph numbers/letters correspond to the proposal instructions paragraph numbers/letters, although the Offeror may add lower tier sub paragraphs.

Each volume and annex of the proposal shall be submitted as original electronic copies as specified in Table G-2 (Proposal Structure). Suggested page counts for each volume, if any, are also specified in Table G-2 (Proposal Structure). The title and table of contents pages, as well as tables, are not included in the suggested page count.

Information submitted as an Annex to a particular proposal volume could include manuals, specifications, plans, procedures, and company policies, as well as other information requested in “Part B Specific Instructions” and do not count towards the suggested page count.

Price information, (e.g., dollar values and/or hourly rates) shall not be included in any volume other than Annex B Small Business Subcontracting Plan; Volume 4 Price, and Volume 5 Contract Administration.

Table G-2 Proposal Structure

Volume

Volume/Annex Title Suggested

Pages

Electronic Copies

Required

File Naming Convention

1 Executive Summary 15 1 Original Vol 1 ES.docx

Table ES-1 Offeror Summary Table ES-2 Relevant Contract Summary

1 Original Vol 1 ES Tables.xlsx

2 Technical 60 1 Original Vol 2 Tech.docx

Technical Cross Reference Matrix

1 Original Vol 2 Tech CRM.xlsx

3 Corporate Experience 35 1 Original Vol 3 CE#.docx

Table CE-1 Applicable Contracts For CE Elements

1 Original Vol 3 CE ACE.xlsx

4 Price As Needed 1 Original Vol 4 Price#.docx

5 Contract Administration As Needed 1 Original Vol 5 CA#.docx

Annex A Level 7 FTD Technical Documentation

As Needed 1 Original Ann A Lvl7 FTD.docx

Annex B Small Business Subcontracting Plan*

As Needed 1 Original Ann B SBSP.docx

Annex C

Relevant Portions of Final Versions of Previous SOO/SOW/PWSs/Other Supporting Documentation

As Needed 1 Original

Ann C Rel SOW PWSs.pdf or AnnC

Rel SOW PWSs .docx

Annex D DCAA/DCMA Reports, Audits, and Determinations

As Needed 1 Original

Ann D DCAA_DCMA.pdf or Ann D

DCAA_DCMA

.docx *Although the Small Business Utilization Strategy is part of the Technical evaluation, it shall be submitted as part of Volume 5 Contract Administration. This is required from all Offerors, regardless of size. In addition, the Small Business Subcontracting Plan is only required from Large Business Offerors

Each file must contain the following information:

a. Cover and title page;

b. Title of proposal and proposal number as applicable;

c. Offeror’s name, address and POC;

d. Solicitation number;

e. Proposal volume/annex number;

f. Copy number; and

g. Table of Contents (The table of contents must provide sufficient detail to easily locate important elements). At a minimum, it must include the paragraphs identified in the CRM.

Table G-3 lists the attachments provided to the Offeror within Section L.

Table G-3 Section L List of Attachments

Section L Attachment Number Electronic File Title Attachment Name L-1 Vol 1 ES Tables Table ES-1 Offeror Summary and

Tables ES-2 Corporate Experience L-2 Vol 2 CRM Cross Reference Matrix L-3 Vol 3 CE Tables Table CE-1 Applicable Contracts

For CE Elements

L-4 Vol 4 Pricing Spreadsheet Pricing Spreadsheet

4. PROPOSAL SUBMISSION AND PACKAGING

All Proposals shall be UNCLASSIFIED.

4.1 PROPOSAL SUBMISSION

Method of delivery shall be through the use of https://safe.apps.mil coordinated with the point of contact listed below.

Proposals shall be submitted using the address provided below. The initial Proposal shall not be submitted by facsimile or electronically via email.

(Electronic Copies) Cynthia Armound Naval Air Warfare Center Training Systems Division 12211 Science Drive, Orlando, FL 32826-3266 Email: cynthia.armound@navy.mil Phone: 407-380-8460

Note: SAFE restricts the maximum file submission at 8 GB. In the Comments box put the following information:

Offeror name, Solicitation number, POC, Backup POC. When files are encrypted for submission, send an email with the “passphrase” to the PCO and the Contract Specialist as listed on the https://beta.sam.gov website.

Creating a Drop-off

1. For “outside or unauthenticated users” In order for an outside user to create a drop-off, they must receive a drop-off request from the PCO or the CS. If interested in submitting a response to the Solicitation, the Offeror must contact the PCO and CS to notify them no later than 10 working days in advance of the proposal submission date. When the PCO or the CS generates a drop-off request for you, you will receive an email with a link to submit your drop-off. This link is good for a one-time submission; ensure that the submission is sent to both the PCO and the CS.

2. For “CAC Authenticated users” Create a “drop-off” with the PCO and the CS as the recipients.

Offerors are hereby notified that the Government will not reimburse for any costs incurred for solicitation preparation, to include pre-award site visits.

5. CHANGES TO SOLICITATION

For any changes and additional information to the solicitation, please go to website: https://beta.sam.gov/

Search the database for the solicitation number N61340-19-R-0096

6. COMPETITION LIBRARY

A competition library of information related to GBTS activities is available by request from the Procuring Contracting Officer (PCO) or Contract Specialist (CS) listed below. The data contained in the competition library is for informational purposes only. The Government does not guarantee the accuracy or completeness of the information. When the request is submitted to the PCO/CS, a copy of the competition library, or updates, will be submitted electronically through https://safe.apps.mil.When updates to the competition library are made, notification will be sent from the PCO/CS to the offerors, and the offerors will be able to request the updates from the PCO/CS.

Procuring Contracting Officer (PCO):

Erin Young Naval Air Warfare Center Training Systems Division 12211 Science Drive, Orlando, FL 32826-3266 Email: erin.b.young@navy.mil Phone: 407-380-4155

Contract Specialist (CS):

Cynthia Armound Naval Air Warfare Center Training Systems Division 12211 Science Drive, Orlando, FL 32826-3266 Email: cynthia.armound@navy.mil Phone: 407-380-8460

PART B SPECIFIC INSTRUCTIONS

1. VOLUME 1 – EXECUTIVE SUMMARY

Note: This volume shall not contain any reference to price aspects of the offer.

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

Attachment L-1 Executive Summary Tables (ES-1 (Offeror Summary), ES-2A (Corporate Experience

Contract Summary)

The purpose of the Executive Summary is to provide the Government with an overview of the Offeror’s entire proposal, excluding price. The Executive Summary volume should be divided into the sections outlined below:

a. Offeror Summary Table:

(1) The Offeror shall complete Table ES-1 (Offeror Summary), provided in Attachment L-1 (Executive Summary Tables), according to the instructions within the attachment, and submit it within this section and as a separate electronic file. This table summarizes the Offeror and its entities’ proposed type and level of work, indicating a commitment to that effort during contract performance. Offerors are advised that in order to demonstrate work commitment, each entity identified in Table ES-1 (Offeror Summary) must be identified in Volume 4 (Price) and associated with a dollar value commensurate with the Percent of Total Proposed Price identified in Table ES-1 (Offeror Summary). Therefore, this table must be a reflection of what is proposed in Volume 4 (Price).

(2) For the Corporate Experience evaluation, contract references that relate to a different CAGE code/DUNS than the proposed entity will be considered if the CAGE code/DUNS was created as a result of a corporate acquisition, reorganization, merger, or other administrative reason and refer to the same division in the same physical location for where the work is being performed or from where the work is being directed in accordance with the proposed roles and responsibilities. All current CAGE Codes/DUNS must appear in Table ES-1(Offeror Summary Table) which indicates a commitment of work for those entities. The

Offeror shall provide a written explanation if multiple CAGE codes/DUNS for the same physical location are applicable to one entity. The written explanation shall detail the distinct roles and responsibilities for entities with different CAGE codes/DUNS at the same physical location for where the work is being performed or from where the work is being directed. The description shall include all changes in the organization as a result of a corporate acquisition, reorganization, merger, or other administrative reason and explain how the changes impact the contract references provided.

Note: “Place of Performance” for this solicitation pertains to the physical location of the prime or other entities that are deploying personnel or responsible for the work; not the Government site where the work is being performed. If work is being performed at a contractor site, then that would also pertain to Place of Performance.

(3) Additionally, if applicable, the Offeror shall provide a description of the legal relationship between JV entities.

Table ES-1 Offeror Summary

Offeror:

Entity Name

Physical Location of Entity

CAGE

Codes/DUNS

Roles and Responsibilities with Work Description

Workshare - % Total Proposed Cost/Price

Principal Entity Yes or No?

Total Proposed cost/price (must add up to 100%) 100%

b. Contract Summary Tables:

The Offeror shall complete Tables ES-2 (Corporate Experience Contract Summary) provided in Attachment L-1 (Executive Summary Tables), for all contracts proposed for the principal entities for Corporate Experience. The Offeror shall complete the tables according to the instructions within the attachment and shall submit them within this section and as a separate electronic file. The contract references designated in Table ES-2 (Corporate Experience Contract Summary) shall be used in completing Volume 3 Table CE-1 (Applicable Contracts for CE Elements).

Tables ES-2 Contract Summary for Corporate Experience

Offeror:

Entity Name Contract Reference

Contract Number

Contract Type

Contract Title *Description of Changes/Additions from Early Information

Prime or Joint Venture Company

P1

P2

P3

T1

JV team member A (where applicable)

T2

T3

JV team member N (where applicable)

T5

Subcontractor A

S1

S2

S3

Subcontractor B

S4

S5

c. Technical The Offeror shall provide a succinct summary of what is proposed for each element, describing the approach or the design configuration and/or the proposed solution. In general, the description should be a short paragraph that provides only the factual description of what is proposed without adjectives or discussions of benefit. In a separate paragraph, identify significant features or approaches of its proposal that exceed requirements, enhance performance or operations, or reduce risk with benefit to the Government. Specifically identity where in the Technical Volume (e.g., paragraph and page number as a minimum) the details of these features or approaches are provided.

VOLUME 2 - TECHNICAL

Note: This volume shall not contain any reference to price aspects of the offer. Section 2.10 Small Business Utilization Strategy shall be submitted in Volume 5 Contract Administration, Section 5.f.

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

Attachment L-2 Volume 2 Table T-1 Cross Reference Matrix (CRM)

The Offeror shall complete Table T-1 (Technical CRM), provided in Attachment (L-1) and submit it as the first page of Volume 2 (Technical) and as a separate electronic file. The Technical CRM is included to help the Offeror develop its proposal and to ensure traceability of Section L paragraphs to the requirements. The Offeror’s Technical CRM may be identical to the one provided or revised to add information. For example, the Offeror’s Technical CRM may cross-reference its proposal volumes, paragraph numbers, and pages to specific solicitation requirements identified within the table, as well as other parts of the proposal that contain relevant information.

Table T-1 Cross Reference Matrix

Section L – Proposal Instructions Volume or Paragraph Numbers

Section L - Proposal Instructions Volume or Paragraph Title

PWS

Volume 2 Technical

2.1 FTD Delivery Overview PWS section 2

2.2 Level 7 FTD PWS Addendum B, paragraph

1.2.1

2.3 Level 6 FTD PWS Addendum B, paragraph

1.2.2

2.4 Six-Degree-of-Freedom (6-DOF)

Short Throw Motion System

PWS Addendum B, paragraph 1.2.1.a; Appendix C, paragraph 10.h

2.5 FTD Simulation /Stimulation PWS Addendum B, paragraph

1.2.6

2.6 Software and Database Updates PWS Addendum B, paragraph

1.2.7.2.c

2.7 Visual System PWS Addendum B, paragraphs

1.2.1.b, 1.2.7.1; Appendix C, Section 11

2.8 Management PWS section 4; PWS Addendum

A, section 1 and section 4

2.9 Instructor Staffing PWS paragraph 4.2.3; PWS

Addendum A, section 1 and section 2

2.10 Small Business Utilization N/A

In this volume, provide the information described below:

Throughout the Technical Volume the Offeror should identify any proposed capability, approach or feature that exceeds a requirement or provides merit associated with a performance or operational benefit to the Government.

The Offeror should also identify any proposed capability, approach or feature that reduces risk inherent in the program. Specifically, explain the benefits to the Government in technical terms and the degree of impact it will have to performance, operations and/or risk. Offerors are advised that any offer to exceed a requirement or to provide a feature with performance and/or operational benefits may be included in the resulting applicable Contract within the proposed cost/price.

The Offeror shall demonstrate the extent to which its proposed capabilities will meet the requirements. The extent and the type of substantiation may vary, but each paragraph in the Technical Volume must be substantiated. The method of demonstration is at the discretion of the Offeror, however, Offerors are advised that risk may be assessed based on the level of confidence that the Offeror provides the Government with its substantiating information. The burden of proof rests with the Offeror.

2.1 FTD Delivery Overview: The Offeror shall provide a diagram of the FTD footprint, detailed installation schematic and installation sequence in Government facilities. The Offeror shall include dimensions of the support/installation equipment and any restrictions or limitations associated with the installation process.

The Offeror shall provide a Gantt chart or other schedule graphic illustrating the following proposed events and other critical path items identified below:

a. Design and Build schedule including site visits by Government SMEs as detailed in PWS section 2 and paragraph 4.1.3;

b. FTD installation schedule in Government facilities to include CNATRA SME pilot evaluation of FTDs in-factory and on-site NAS Whiting Field;

c. The Offeror’s process and timeline to obtain a FAA National Simulator Program (NSP) Technical Letter of Equivalency for first Level 7 FTD; and

d. Key dates and milestones of Technical Interchange Working Group meetings as well as CDRL deliveries.

The Offeror shall discuss the proposed approach to ensure the FTDs will be installed and operational so that the trainers are Ready for Training per Government Schedule in Section F.2. Also, provide a description of the barriers, risks, and critical path items associated with installing the FTDs. For any barriers, risks, or issues identified, the Offeror shall provide the potential mitigation measures.

2.2 Level 7 FTD: For the proposed TH-73 Level 7 FTD, please provide the following:

1. Narrative of the design approach and plan to obtain a FAA NSP Technical Letter of Equivalency on the first TH-73 Level 7 FTD. The Technical Letter of Equivalency will include all PWS Addendum B requirements.

In Annex A to the Technical Volume, provide Offeror’s non-“parent” helicopter simulator information and documentation to include any Level 6 FTD, Level 7 FTD, and Level D FFS SOQs, for comparable helicopter simulators; comparable meaning a helicopter simulator used to conduct training in IFR and VFR environments, that includes glass cockpit avionics systems, and is of similar size and performance parameters to the TH-73. Documentation will be used to make a determination of whether the following required capabilities are present:

o A six-degree-of-freedom (6-DOF) short throw motion system capable of minimum 60hz motion response and reliably recreating the effects of helicopter flight as outlined in PWS Addendum B paragraph 1.2.1.a and further defined in PWS Appendix C paragraph 10.h;

o A high fidelity, adaptive and reactive, blade element based aerodynamic modelling solution that functions seamlessly with motion and visual system solutions while meeting or exceeding the criteria described in 14 CFR Part 60, Appendix D;

o A fully functioning “Avionics Suite matching TH-73 aircraft systems”, found at PWS Addendum B paragraph 1.2.7.2.c; and o A visual system capable of particle physics based night scene modeling with Near Infrared (Near IR) overlay spectrum for Night Vision Goggle stimulation, found at PWS Addendum B paragraph 1.2.7.1.b and Appendix C paragraph 7.k.1.

If the required capabilities are not present in the non-“parent” helicopter simulator information, provide the Offeror’s proposed approach as to how the Offeror will both ensure that the required capabilities would meet pertinent FAA Qualification Performance Standards for a Level 7 FTD and PWS requirements and install those capabilities in the contractor-provided FTDs in time to meet the training schedule.

Additionally, provide a description of the barriers, risks, and critical path items to meeting FAA Qualification Performance Standards and PWS requirements, obtaining a FAA NSP Technical Letter of Equivalency on first TH-73 Level 7 FTD, and meeting the training schedule. For any barriers, risks, or issues identified, the Offeror shall provide the potential mitigation measures.

2.3 Level 6 FTD: For the proposed TH-73 Level 6 FTD, please provide a description of the proposed approach as to how the Offeror will leverage the TH-73 Level 7 FTD with required FAA NSP Technical Letter of Equivalency to ensure that the required capabilities would meet pertinent FAA Qualification Performance Standards for a Level 6 FTD and PWS requirements, and install those capabilities in the FTDs in time to meet the training schedule.

Additionally, provide a description of the barriers, risks, and critical path items to meeting Level 6 FTD FAA

Qualification Performance Standards and PWS requirements, and meeting the training schedule. For any barriers, risks, or issues identified, the Offeror shall provide the potential mitigation measures.

2.4 Six-Degree-of-Freedom (6-DOF) Short Throw Motion System: For the proposed TH-73 Level 7 FTD 6-DOF Short Throw Motion System, please provide the following:

a. Table of Recommended Training, Testing, and Checking Credit for FAA qualified Level 7 FTD with short throw motion system

b. Description of short throw motion system and how PWS Addendum B paragraph 1.2.1a, PWS Appendix C paragraph 10.h, and 14 CFR Part 60, Appendix D requirements will be met.

2.5 FTD Simulation /Stimulation: For the TH-73 Level 6 and Level 7 FTDs, please provide the approach to simulation/stimulation to produce the required FTDs. At a minimum, the Offeror shall describe:

Avionics System;

Flight Dynamics model;

Engine Performance Data;

Licenses;

OEM parts;

OEM relationships necessary to acquire data and parts; and Timeline to acquire and incorporate data

Additionally, the Offeror shall identify any barriers, risks, and critical path items associated with acquiring data and parts necessary to provide the FTDs while meeting the training schedule. For any barriers, risks, or issues identified, the Offeror shall provide the planned mitigation measures.

2.6 Software and Database Updates: For the proposed TH-73 Level 6 and Level 7 FTDs, please provide a description of the Offeror’s approach to manage software and database updates associated with the TH-73 Level 6 and Level 7 FTDs to include at a minimum (does not include visual database):

Navigation database updates;

Avionics software updates;

OEM directed changes;

Relevant existing license or subscription agreements with OEMs; and Timeline to acquire and incorporate software database updates

Additionally, provide a narrative discussion of the barriers, risks, and critical path items to manage software and database updates associated with the TH-73 Level 6 and Level 7 FTDs, and meeting the training schedule. For any barriers, risks, or issues identified, the Offeror shall provide the planned mitigation measures.

2.7 Visual System: The Offeror shall provide a description of how the offeror’s proposed Visual System will meet the following requirements:

Visual System Requirements to include Image Generator and Projector information (found in PWS Addendum B paragraphs 1.2.1.b, 1.2.7.1.b);

Visual scene and effects requirements (found in PWS Addendum B paragraph 1.2.7.1); and Visual environment requirements (found in PWS Addendum B paragraph 1.2.7.1 and Appendix C paragraph 10.c and Section 11). Of primary concern will be the timeline to develop visual database and how it will meet the Government schedule requirement.

Additionally, the Offeror shall identify the barriers, risks, and critical path items to fielding this visual solution in time to meet the training schedule. For any barriers, risks, or issues identified, the Offeror shall provide the planned mitigation measures.

2.8 Management: The Offeror shall provide a description of the proposed management approach to meeting the program requirements found in the PWS, Addendum A, and Addendum B. The description shall include how the Offeror will provide continuous interaction both during and after the technical interchange period with Training Air

Wing Five (TW-5) subject matter experts in order to ensure that provided Flight Simulation Training Devices meet TW-5 training needs. Also, discuss how/if/when program management focus would/should shift from production to delivery. The Offeror shall also provide a brief description of what it believes the background of an ideal contractor program management candidate should be.

2.9 Instructor Staffing: Describe how the offeror intends to assemble its Contract Instructor (CI) workforce (DOL wage category 15020). Explain:

Its history in hiring CIs, if any;

Its approach to staffing the Site Manager and Alternate Site Manager positions;

Its phased approach to hire prospective CI personnel as defined in PWS Addendum A section 1;

How it intends to achieve necessary T/M/S certification for prospective CI personnel, to include any MOUs or other potential agreements with the aircraft OEM or other contractor;

If it intends to hire current TH-57 CIs, how it would achieve T/M/S certification, if different from above;

and Its approach to overall CI staffing (number of Full-Time and Part-Time CIs). Briefly discuss how its workforce would be staffed to meet 10% daily schedule variability requirements in PWS Addendum A paragraph 4.5.1.1, carry-over hours requirements in PWS Addendum A paragraph 4.6, AIT requirements in PWS Addendum A paragraphs 4.5.1.2, 4.8, scheduling inefficiencies, and other time lost in a CI workyear to collateral duties, corporate administration, vacation, sick leave, mandatory training, etc.

2.10 Small Business Utilization Strategy:

THE OFFEROR SHALL SUBMIT THIS INFORMATION AS PART OF VOLUME 5 CONTRACT

ADMINISTRATION, SECTION 5.f. NO SMALL BUSINESS INFORMATION SHALL BE INCLUDED IN

THE TECHNICAL VOLUME.

All Offerors (Large and Small Businesses) shall address their strategies for utilizing SB concerns in the performance of this contract. For purposes of this solicitation, SB categories are SB, Small Disadvantaged Business (SDB), Veteran-Owned SB (VOSB), Service-Disabled Veteran-Owned SB (SDVOSB), HUBZone SB, and Women-Owned SB (WOSB). A SB concern may fall into multiple categories and should be accounted for in each applicable category. Each subcategory of SB shall be addressed. (This strategy is separate from, but shall be consistent with, the SB Subcontracting Plan provided by the Offeror in Annex B (if required). The SB Prime Offeror may include its own participation within this SB Participation Plan. The minimum proposed small business goal is 30% of the total contract value (inclusive of options); if a lower value is proposed it should be clearly explained why 30% cannot be met. In describing its plan for this solicitation, the Offeror shall, as applicable:

1. Describe the extent of participation of SB Concerns on this contract and the details of each work scope anticipated to be performed by SB Concerns;

i. Identify the name, CAGE code, and any associated socio-economic categories (SB, SDB, VOSB, SDVOSB, HUBZone, and WOSB) of each SB Concern planned for utilization in the execution of this contract;

2. Provide targets, expressed as dollars and percentages of total contract value (inclusive of options but exclusive of the 52.217-8 option) for SB participation in each SB category. Note: This calculation is different from the calculation required by FAR 52.219-9 in the Subcontracting Plan, as the Plan requires percentage of subcontracting value.

3. If proposing less than 30% SB Participation for this contract, the Offeror shall provide a detailed explanation clearly supporting the rationale for doing so.

VOLUME 3 – CORPORATE EXPERIENCE:

Note: This volume shall not contain any reference to the cost or price aspects of the offer.

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

Attachment L-3 Table CE-1 Applicable Contracts for Each Corporate Experience Element

For this volume, the Offeror shall complete Table CE-1 (Applicable Contracts for Each Corporate Experience Element), provided in Attachment L-2, according to the instructions within the attachment, and submit it as the first section of Volume 3 (Corporate Experience) and as a separate electronic file. Within Table CE-1 (Applicable Contracts For Each Corporate Experience Element) the Offeror shall identify the portions (sections and paragraphs) of the contract reference’s SOW/PWS or other supporting solicitation/contract documentation, submitted as Annex C, to clearly identify how Corporate Experience performing past tasks are similar to evaluation elements 3.1.1 through 3.1. 3. If the Offeror performed as a subcontractor for a contact reference, identify those portions (sections and paragraphs) of the SOW/PWS or other documentation of the agreement between the prime and subcontractor and submit in Annex C. Only contract references designated in Table ES-2 (Corporate Experience Contract Summary) shall be used in completing this Volume.

For this Volume, the Offeror shall identify contracts, or those portions of a contract, whose performance is within five years of the proposal due date and contains efforts similar to those efforts required by this solicitation for the principal entities identified in Table ES-1 (Offeror Summary). Each Entity shall provide up to three contracts for each section 3.1.1 to 3.1.3 (for a total of no more than nine contracts) based on their roles and responsibilities as described in Table ES-1. The experience provided shall only relate to Corporate Experience, which is the experience gained through contracted or demonstrated work. The experience of the principal entities personnel or any personnel will not be considered in this Corporate Experience evaluation. If proposing as a JV team, Offerors should include the Corporate Experience of the JV as a whole, as well as the Corporate Experience for each JV team member. In general, more recent Corporate Experience will be considered a better indicator of future performance than older Corporate Experience.

Corporate experience information provided shall be: for similar programs/contracts (as defined in section 3.1 (Evaluation Elements)); for the same corporate entity (e.g., with the same CAGE code/DUNS) as referenced in Table ES-1 (Offeror Summary); and related to the roles and responsibilities identified in Table ES-1 (Offeror Summary). For example, if a principal entity is assigned to perform Non-Destructive Test/Inspection and submits information regarding software development, the software development experience would not be applicable as it was not proposed as an assigned role/responsibility for the principal entity.

For a discussion on CAGE Code/DUNS, refer to Section 1.0 Volume 1 (Executive Summary). Offerors should be advised that the CAGE Code/DUNS for each referenced contract is considered as part of the determination if the contract reference will be included in the Corporate Experience evaluation. Note: Any information regarding CAGE Code/DUNS should be included within Volume 1 (Executive Summary) and does not need to be repeated here.

3.1 Evaluation Elements

The Offeror shall provide a comparative analysis between the principal entities’ roles and responsibilities identified in Table ES-1 (Offeror Summary) and the Corporate Experience requested in subparagraphs 3.1.1 through 3.1. 3. In a paragraph to a page per contract reference, for each element in 3.1.1 through 3.1.3 below, describe the extent to which previous Corporate Experience performing requirements similar to this solicitation can be leveraged in future performance of work. Similarity is the extent to which the Offeror’s contract references (or documented work efforts) correspond to the specific tasks required by this solicitation. At a minimum, address the specific items within each element, however, when drafting each element description, consider the contract reference’s period of performance, the amount of time in performance, recency of the performance, frequency of the applicable activities, the technical nature of the work in comparison to the proposed effort, and the entity’s proposed role and responsibility.

3.1.1 Visual Database Development – The Offeror shall demonstrate experience in Visual Database development to include physics based, interactive modelling for the purpose of flight simulation. The Government has particular interest in the following areas of demonstrated experience:

Pre-existing visual databases and a list or range of modelled airfields, areas and facilities, Terrain and obscurant modelling that can be applied to flight training, Night and NVG scene modelling, specifically:

o Infrared (IR) projection for NVG training o Visual and IR blending o Night and IR scene visual effects, halos, scattering, etc.

3.1.2 Instructor Cadre Management - The Offeror shall demonstrate experience in Instructor Cadre Management to include each of the following:

CIS contracts, Instructor Training and standardization, Instructor Experience, selection and hiring process, Instructor scheduling and coordination.

3.1.3 Device Maintenance Management - The Offeror shall demonstrate experience in Device Maintenance Management to include each of the following:

Device OEM updates and currency, Reoccurring software updates and currency management, including aircraft avionics and FTD software updates, Device maintenance management and availability rates.

5. VOLUME 4: - PRICE

5.1 Volume Content:

(a) This Volume shall contain the Contract Compliance information specified below as follows:

i. Offeror Summary Table: The Offeror shall complete the table below. The Offeror shall include all subcontractors and JV team members who will be involved with the performance of the contract and list all sites where the work will be performed. If a JV teaming or subcontracting arrangement is proposed, identify the work share, distribution elements, and ratios that each contractor will perform using the table below. Also provide a definition of the legal relationship between the entities if it is other than a Prime/subcontractor relationship.

Contractor Name (Indicate Prime, JV Team Member, or Sub)

Place of Performance/

CAGE

CODE/DUNS #

Brief Work Description and/or Program Responsibility

% of Total Proposed Price

(b) This Volume shall also contain a copy of Section B with the Contract Line Item (CLIN) and Sub-CLIN Unit Prices and, for evaluation purposes, the Total Prices filled in using the estimated quantities value in the solicitation and the instructions below. Section B prices shall be provided separately in one digital data copy in MS Office 2010 Excel format utilizing template L-4 attached. Within all Excel spreadsheets, the Offeror shall use formulas and functions to the maximum extent possible and avoid using output type “value only” cells. If links are utilized, supply those referenced files. Spreadsheets shall not be protected.

(c) All price and price supporting information shall be contained in Section B and the price proposal. No price or pricing information shall be included in any other technical volume including cover letters. Offeror are responsible for submitting sufficient information to enable the Government to fully evaluate their price proposal.

5.2 Ground Rules and Assumptions:

(a) As this is a competitive acquisition with adequate price competition anticipated, certified cost or pricing data in accordance with FAR 15.403-1 is not required. However, in the event that adequate price competition does not exist after receipt of proposals, the Government reserves the right to request additional cost or pricing data as necessary from both the Offeror and subcontractors. Further, the Offeror may be required to provide a Certificate of Current Cost or Pricing Data prior to award, pursuant to FAR 15.406-2.

(b) The Offeror shall provide sufficient information to support its price/cost as well as an explanation of all ground rules and assumptions that affect the price/cost estimates.

(c) If subcontractors are proposed, they shall provide the same information required for the prime contractor, unless otherwise noted in the Price/Cost Information section below

5.3 Contract Prices for Firm Fixed Price CLINs/SLINs

The Offeror shall provide a copy of Section B of the solicitation populated with the CLIN unit prices and CLIN total prices using each CLIN’s quantity value.

Provide the proposed price for each CLIN/SLIN using Section B. The Offeror shall explain any appearance of unbalanced pricing.

6. VOLUME 5 – CONTRACT ADMINISTRATION

The Offeror shall provide the following contract administration information.

a. Offeror Representatives and Information: The Offeror shall provide a summary sheet comprised of the information listed below for the entities identified in Table ES-1 (Offeror Summary).

(1) PRIME CONTRACTOR

i. Business Name;

ii. Address;

iii. Principal point of contact for this solicitation (Name, title, phone number, email);

iv. Secondary point of contact for this solicitation (Name, title, phone number, email);

v. Individuals authorized to negotiate with the Government and contractually bind the Offeror (Name, title, phone number, email);

vi. Establishment Taxpayer Identification Number (TIN);

vii. TIN of Parent Corporation (if applicable);

viii. DUNS;

ix. CAGE code;

x. Business size for this effort (large or small); and

xi. Percentage of work and role and responsibility performing.

(2) ALL OTHER ENTITIES

i. Business Name; Address; DCMA point of contact and telephone number, if applicable;

ii. DCAA point of contact and telephone number, if applicable;

iii. DUNS;

iv. CAGE code; and

v. Percentage of work and role and responsibility performing.

b. Government Agency Information: Provide the mailing address, telephone, fax numbers, email address, and facility codes for the Offeror’s local Defense Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA), and Government Paying Office. In addition, provide the name, telephone number, fax number, and email address for the Administrative Contracting Officer (ACO) at DCMA.

c. Business System Compliances: The Offeror shall indicate the most recent date that the Offeror’s cognizant

DCMA/DCAA determined the adequacy of the Offeror’s systems (including but not limited to Accounting, Property, and Purchasing). If the Offeror’s systems’ status is not adequate, list the date of the last adequacy determination and the current status of any systems reviews or ongoing audits;

Business Systems Status Table: The Offeror shall complete Table CA-1 (Business Systems Status) showing the current status and or determinations regarding its business systems. If any item is not applicable to the Offeror or for contract performance, so state and justify. If any item has been determined to be unapproved/inadequate outline the potential impact on contract execution, mitigation plan, and correction plan.

Submit relevant DCAA/DCMA reports, audits, and determinations in Annex D (DCAA/DCMA Reports, Audits, and Determinations).

Table CA-1 Business Systems Status

Business System

(D)FAR

Reference

Status

Comments

Accounting System 16.301-3 Estimating System 215.407-5 CAS Disclosure Statements (1) 30.202-6(b) Purchasing System 44.3 Earned Value Management System 242.302(S-71) Property Management System 45.105

1. An adequate CAS Disclosure Statement is a condition for award for Offerors subject to full CAS requirements regardless of any best value determination.

This information is to facilitate the PCO’s responsibility determination and any need to discuss information related to this does not…