N6134022R0036 Amendment 0004.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 revise the follow ing:

1. Revise the submission date for Volume 4 (Section L, Part A, Paragraph 4.6).

2. Revise and clarify PPQ instructions and information (Section L, Part B, Paragarph 2.4.1 and 2.4.2).

1. CONTRACT ID CODE PAGE OF PAGES

J 1 28

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

16C. DATE SIGNED

BY 12-Dec-2022

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 N6134022R0036

X 9B. DATED (SEE ITEM 11)

05-Oct-2022

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

12-Dec-2022

CODE

NAWCTSD PROCUREMENT GROUP

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:

N6134022R0036

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

SECTION L

PART A GENERAL INSTRUCTIONS

1.0 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 an 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 Volume 3, Attachment L-2 (Price / Administration) and Volume 4 Small Business, Attachments L-3 and L-4 (Small Business Participation Commitment Document). Alternate or streamlined 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 shall 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 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.

Offerors are expected to comply with all requirements of the RFP. The Government advises Offerors that taking exception to or deviating from any term or condition of the RFP may make an offer unacceptable and the Offeror ineligible for award.

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 when the prime contractor consists of more than one legal entity. “JV Team Members” are the entities that make up a Joint Venture.

A “principal subcontractor” is defined as a subcontractor who provides at least 20% of the proposed total price. 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).

2.0 PROPOSAL FORMAT AND SUBMISSION

2.1 Electronic Submission of Proposals

This section is intended to provide information to the Offerors 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 upload proposals and will ensure the proposals received are suitable for reading electronically during evaluation.

Proposals must be formatted using a Times New Roman 12 pt Normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for standard 8.5 x 11 inch paper. All pages should be numbered with section and page numbers. Graphs and tables shall be presented in no smaller than a 10 pt font and should contain a grid, which allows values to be read directly from the graph. Graphs and Tables that fit on an 8.5” X 14” printed page will be counted as one page. Drawing may be of any size and will count as one page. Graphic resolution, including such data as tables or charts, should be consistent with the purpose of the data presented. When using Government supplied templates, no modifications to font or scaling is required. All proposal documents must be compatible with Microsoft Office 2016 and/or the latest Adobe Acrobat Reader Portable Document Format (PDF), where applicable. No active scripts or macros shall be imbedded in any files.

The Offeror is responsible for ensuring electronic proposals are virus free and shall run an anti-virus scan before submission. Offerors may use hyperlinks within and among proposal volumes that do not include price information. However, there shall be no links from any other volume into the Price Volume or into any other portion of the proposal that contains price information. In order to reduce file sizes, the Offeror shall not embed sound or video (e.g., MPEG) files within the proposal submission. The Offeror is encouraged to simplify the color palette used in creating figures; and minimize size of graphics files; and avoid scanned images.

The Offeror shall keep the portions of the proposal that contain pricing information in separate files from the portions of the proposal that do not contain pricing information. Price information (e.g., dollar values and/or hourly rates) shall appear only in Volume 3, Attachment L-2 (Price / Administration) and Volume 4 Small Business, Attachments L-3 and L-4 (Small Business Participation Commitment Document).

Table G-2 (Proposal Structure) in Section L, Part A, 3.0 identifies the proposal structure for each volume. Each file shall contain a title page clearly marked with the Offeror's name and address, the point of contact's name and phone number, the proposal volumes contained therein, and “Source Selection Information – See FAR 2.101 and 3.104”.

2.2 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

The Offeror shall follow the basic structure of the file naming convention in Table G-2 (Proposal Structure) 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 shall provide one document for each volume or annex as listed in Table G-2, containing all electronic files requested within the volume or annex. Offerors should not provide each section/paragraph as separate files. Zip files are not allowed. The only exception to this is for Annex A, a separate document for each Past Performance reference should contain all the documentation for that reference.

3.0 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 and/or 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 electronically as specified in Table G- 2 (Proposal Structure) per the instruction provided in Section 4.0 (Submission and Packaging).

Offerors shall not submit more pages than the maximum page count identified in Table G-2 (Proposal Structure). The title and table of contents pages, as well as any drawings or spreadsheets, are not included in the maximum page count.

Table G-2 Proposal Structure

Volume Number

Volume/Annex Title File Naming Convention

Maximum Page Count

1 TECHNICAL Vol 1 Tech#.docx

1a Ownship Physics Demonstration

Vol 1a Tech#.docx and/or Vol 1a Tech#.xlsx

Demonstration system and test procedures only

1b Stress Test Demonstration

Vol 1b Tech#.docx and Vol 1b

Tech#.xlsx

DVD / Blu-ray, hardware specifications, and spreadsheet only

1c Modular Open System and Data Rights Approach Narrative

Vol 1c Tech#.docx

As Needed

1d Technical Approach

Vol 1d Tech#.docx and Vol 1d

Tech#.xlsx

10 page document and spreadsheet

2 PAST PERFORMANCE Vol 2 PP#.docx 10

2a Past Performance Contract Summary (PP-1)

Vol 2 PP-1.xlsx 1 file per offeror

2b Past Performance Contract Data

(PP-2)

Vol 2 PP-2.xlsx 1 file per offeror, with different tabs for each contract reference 3 PRICE / ADMINISTRATION Vol 3 Price.docx As Needed 4 SMALL BUSINESS Vol 4 SB.docx As Needed

Annex A

Supporting Documentation for Past Performance

AnnA PP Supporting Docs.docx or .pdf

As Needed

Annex B

Attachment from Technical Volume, DFARS provision 252.227-7017

AnnB 252.227- 7017.xlsx

As Needed

Annex C

Attachment from Technical Volume, DFARS provision 252.227-7028

AnnC 252.227- 7028.xlsx

As Needed

Each volume or annex 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 or annex number; and

f. 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

Electronic File Title Attachment Name

L-1 Vol 2 PPQ Past Performance Questionnaire

L-2 Vol3, L2 Price Attachment Vol 3, L2 Price Attachment L-3 Vol 4 SBPCD-IDIQ Vol 4 SBPCD-IDIQ L-4 Vol 4 SBPCD-D01 Vol 4 SBPCD-D01 L-5 NSS Question and Answer Form NSS Question and Answer

Form L-6 Vol 4 DO-1 T-Cs Delivery Order 1 Terms and

Conditions (T&Cs) L-7 GFI files for solicitation

(multiple) (multiple)

L-8 GFI files for Technical Volume

1.1.1 Ownship Physics

Demonstration (multiple)

(multiple)

PP-1 Vol 2 PP Contract Summary PP1 Past Performance Contract Summary

PP-2 Vol 2 PP Contract Data PP2 Past Performance Contract Data

4.0 PROPOSAL SUBMISSION

4.1 All proposals shall be UNCLASSIFIED. The submission date for each Volume of the proposal shall be no later than the date and time specified in Section L, Part A, Paragraph 4.6.

Offerors are hereby notified that the Government will not reimburse for any costs incurred for solicitation preparation. Proposals shall be valid for 270 days from the proposal due date.

4.2 All volumes of the proposal shall be submitted electronically, with the exception of the technology demonstration media required at Section L Part B 1.1.1 and 1.1.2, through the Solicitation Module of the Procurement Integrated Enterprise Environment (PIEE) at https://piee.eb.mil. No other submissions are authorized by the solicitation. For instructions on how to post an offer, please refer to the Posting Offer demo:

https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf.

It is the Offeror’s responsibility to follow the registration instructions found on the PIEE website.

It is advised that all potential prime Offerors and their subcontractors ensure the proper company points of contact are registered in the site based on their CAGE codes and have the proper roles assigned well in advance of the solicitation closing date. Subcontractors are only required to register in PIEE if they want to submit their proprietary proposal information separate from the prime offer. Documents submitted by the subcontractor directly to the Government must have the prime contractor’s name, CAGE Code, and the solicitation number on the first page of the document.

The Solicitation Module will only allow a total of 1.9 Gigabytes (GB) inclusive of all files to be uploaded to the module. If an Offeror anticipates their submission to be larger than 1.9 GB, the Offeror must coordinate at least 3 business days in advance with the Solicitation Contracting Officer and Contract Specialist (David Kors and Duane Drury). Proposals that are rejected by the Solicitation Module will not be considered by the Government. Therefore, Offerors should consider submitting proposals in advance of the deadline.

It is also the Offeror’s responsibility to confirm receipt of proposals and all electronic communications. Screen shots of the submission should also be taken to validate a submission was accepted in the PIEE system for this solicitation. The Government is not obligated to search for incorrectly submitted proposals in PIEE.

4.3 For the technology demonstration media required at Section L, Part B, 1.1.1 and 1.1.2, each Offeror shall coordinate with PCO David Kors (david.a.kors.civ@us.navy.mil) and Contract Specialist Duane Drury (duane.p.drury.civ@us.navy.mil) at least 72 hours in advance of dropoff of the media at NAWCTSD, 12211 Science Drive, Orlando, FL 32826. The proposal media shall be submitted no later than the date and time specified in Section L, Part A, Paragraph 4.6.

4.4 Upon award of a contract or cancellation of the solicitation, all Offerors shall coordinate with the PCO to arrange for return of the technology demonstration media described in the paragraph above.

4.5 If there is an unanticipated PIEE System outage within 24 hours of the proposal due date and the outage has interrupted normal Government processes so that proposals cannot be received by the exact time specified in the solicitation, the Contractor shall immediately notify the Contracting Officer. This notification shall occur prior to the proposal submission deadline and shall be made in writing. The notification may be in conjunction with verbal notification, but verbal notification alone shall not be sufficient. The Offeror shall obtain written approval from the Contracting Officer to submit the proposal via an alternate method which will be provided by the Contracting Officer or the Contracting Officer may advise the Offeror that the Government will follow the procedures set forth in FAR 15.208(d) for amending the solicitation closing date.

4.6 Proposal volumes shall be submitted no later than the following date for each portion of the proposal:

Table G-4 Proposal Due Date

Volume Number

Volume/Annex Title Due Date

1 TECHNICAL

Volume

Volume/Annex Title Due Date

1a Ownship Physics Demonstration

23 January 2023, 10:00

AM EST

1b Stress Test Demonstration 23 January 2023, 10:00

AM EST

1c Modular Open System and Data Rights Approach Narrative

9 January 2023, 10:00 AM

EST

1d Technical Approach 9 January 2023, 10:00 AM

EST

2 PAST PERFORMANCE

9 January 2023, 10:00 AM

EST

2a Past Performance Contract Summary (PP-1)

9 January 2023, 10:00 AM

EST

2b Past Performance Contract Data

(PP-2)

9 January 2023, 10:00 AM

EST

3 PRICE / ADMINISTRATION

23 January 2023, 10:00

AM EST

4 SMALL BUSINESS

23 January 2023, 10:00

AM EST

Annex A

Supporting Documentation for Past Performance

9 January 2023, 10:00 AM

EST

Annex B

Attachment from Technical Volume, DFARS provision 252.227-7017

9 January 2023, 10:00 AM

EST

Annex C

Attachment from Technical Volume, DFARS provision 252.227-7028

9 January 2023, 10:00 AM

EST

Failure to submit each portion of the proposal by the date in Table G-4 will result in the proposal being considered late and therefore the proposal will not be evaluated. For portions of the proposal that are required to be submitted no later than 9 January 2023, 10:00 AM EST, Offerors are not authorized to submit a revision to that portion of the proposal with the supplemental portions of the proposal due no later than 23 January 2023, 10:00 AM EST. All volumes shall be submitted by the method as provided in Section L, Part A, Paragraphs 4.1 – 4.5.

5.0 CHANGES TO SOLICITATION

For any changes and additional information to the solicitation, please go to website:

https://sam.gov/content/home

6.0 TECHNICAL LIBRARY

6.1 A Technical Library of draft documentation directly related to the requirements of this contract was made available to all potential Offerors with approved access prior to the solicitation being released. Final documentation and GFI (Attachment L-7 and L-8) are provided with the solicitation. To obtain access to the Technical Library, please see the instructions associated with this notice on https://sam.gov/content/home and search for solicitation number N6134022R0036.

6.2 Upon award of a contract resulting from the subject solicitation or cancellation of the solicitation and within 10 calendar days of being notified, unsuccessful offerors shall destroy any and all copies of the technical data or data produced from the usage of the technical data in development of the offeror’s proposal and certify in writing to the PCO within 10 days after contract award that they have complied.

7.0 SOLICITATION QUESTIONS

7.1 Questions regarding this solicitation shall be submitted in writing using the NSS RFP Question and Answer Form (Attachment L-5). The Government may answer questions prior to the deadline for proposal submission provided that those questions are received no later than 3 business days following the date of the Industry Solicitation Conference.

Any questions regarding this solicitation shall be submitted in writing on Attachment L-5 by electronic mail to the following addresses:

Duane Drury, Contract Specialist, duane.p.drury.civ@us.navy.mil and David Kors, PCO, david.a.kors.civ@us.navy.mil

Each question shall reference the applicable document, paragraph, and page number. Questions, if answered, will be provided to all potential offerors via amendment to the solicitation;

therefore, do not include proprietary information in your questions.

7.2 The Government reserves the right not to respond to any questions concerning this solicitation received after the time frame specified above. Accordingly, offerors are encouraged to carefully review all solicitation requirements and submit questions to the Government early in the proposal preparation cycle.

PART B SPECIFIC INSTRUCTIONS

1.0 VOLUME 1 - TECHNICAL

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

The Offeror shall complete Table T-1 Cross reference Matrix (CRM), and submit it as the first page of Volume 1 (Technical). 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

Paragraph Numbers / Title

RFP

Sections (e.g.

Sections F, H, and

M)

SOW (Base or Delivery Order

(DO1)

Base SOW 210023

D01 SOW 210024

Performance Specification (PRF) System Specification

210025

1.0 Volume 1

1.0.1 Statement of

Compliance (Prerequisite Criteria)

3.1.1.4

1.1 Technology

Demonstration

1.1.1 Demo 1 – Ownship

Physics

DO1 3.2.8.5

DO1 3.2.8.6

3.1.3.1 and subsection 3.1.3.1.1.a, b, c, d, f, & g 4.3.3.a thru c

1.1.2 Demo 2 – Stress

Test

3.1.3.2.1 thru 3.1.3.2.4

3.1.3.4.3 thru 3.1.3.4.5 3.1.7.1.ooo 3.1.7.3 3.1.8.3.c, d & g.1 3.1.6.o.6 & 8 3.1.10.b,c, & g

4.3.6.1 and subsection 4.3.6.1.b & c

1.2 Modular Open

System and Data Rights Approach

3.1.1 and subsections 3.1.1.1 3.1.1.2 3.1.1.2.1 3.1.1.5 3.1.1.5.1

1.3 Technical

Approach

DO1 3.2.1.1.1 3.1.2.a thru d 3.1.8.5

In this volume, provide the information described below:

Offerors shall not self-identify proposal information that they believe rises to the level of a strength or significant strength. Those determinations will be made solely by the evaluation team; self-identified “strengths” and “significant strengths” will only be addressed in the technical evaluation if the evaluation team makes an independent determination that the information qualifies as a “strength” or “significant strength” as defined in Section M.

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 burden of proof rests with the Offeror.

1.0.1 Statement of Compliance (Prerequisite Criteria): The Offeror shall provide certification that its proposed maritime simulation software has an active Class A Statement of Compliance (SOC) for Bridge Operation in accordance with DNVGL-ST-0033.

1.1 Technology Demonstration

1.1.1 Ownship Physics Evaluation: The Offeror shall provide a demonstration system (hardware and software) that demonstrates how the proposed technology accurately simulates the ownship model in conformance with the provided real world data (PRF 3.1.3.1 and subsection 3.1.3.1.1.a, b, c, d, f, & g). The Offeror shall provide Test procedures IAW DO1 SOW 3.2.8.5 & 3.2.8.6, PRF 4.3.3.a thru c, and DI-NDTI-80603A for Government execution using the demonstration system. There are no restrictions as to the type of hardware submitted for the Ownship Physics Evaluation.

1.1.2 Stress Test Demonstration: The Offeror shall submit a 30 to 60 minute DVD / Blu-ray video demonstration of technology stress test performance conducted IAW with PRF 4.3.6.1, 4.3.6.1.b & c. The geographic database demonstrated shall be San Diego (PRF 3.1.7.1.ooo). The entity models demonstrated shall be representative of the specified entity list (PRF 3.1.7.3). The DVD / Blu-ray video shall demonstrate virtual scene performance by showing a recording of a 4K resolution 60 Hz refresh rate virtual scene display (PRF 3.1.3.2.1 thru 3.1.3.2.4, PRF

3.1.3.4.3 thru PRF 3.1.3.4.5, PRF 3.1.8.3.g.1, and PRF 3.1.10.b, c, & g) and shall also display the following real time performance metrics:

a. Framerate (PRF 3.1.8.3.c, PRF 3.1.6.o.6); and,

b. Entity update rate (PRF 3.1.8.3.d, PRF 3.1.6.o.8)

The Offeror shall submit hardware specifications used for recording the video demonstration.

The Offeror shall not utilize computer hardware that exceeds the following specifications:

Processor Intel Core i7-8700 6-core 12MB Cache*

Graphics Card GeForce RTX 2080*

Memory 2 X 8GB DDR4 2666MHz

* Brand name or equivalent

If the Offeror’s stress test demonstration shows that stress test performance thresholds are being exceeded and if the Offeror is proposing new requirements in excess of the threshold, the Offeror shall provide an excel spreadsheet noting the current performance requirements and the proposed revised performance requirement for incorporation into the resultant contract should the Offeror be selected for award. Language shall be IAW IEEE 29148-2018 section 5.2 and shall be free of references to vendor products and brand names.

1.2 Modular Open System and Data Rights Approach

The Offeror shall describe the proposed technical approach to satisfy Modular Open System Approach requirements (PRF 3.1.1 and subsections 3.1.1.1, 3.1.1.2, 3.1.1.2.1, 3.1.1.5, 3.1.1.5.1).

The Offeror shall list each software item, identifying whether it is commercial or non-commercial. For any vendor-specific commercial computer software or non-commercial computer software, the Offeror shall explain how the use affects third party sustainment and modification of the system throughout the system’s lifecycle. Vendor -specific computer software does not include third party commercially available off-the-shelf (COTS) computer software, such as Microsoft Windows or Red Hat Linux, which are sold in substantial quantities (see FAR 2.101 for definition of COTS).

The Offeror shall submit assertions for non-commercial technical data and computer software, other than unlimited rights, in accordance with:

DFARS 252.227-7017 (Submit as Annex B of solicitation response) DFARS 252.227-7028 (Submit as Annex C of solicitation response)

If the Offeror is proposing specifically negotiated license rights for non-commercial computer software, the Offeror shall submit the proposed modifications to standard license rights (the Offeror shall list the specifically negotiated license right in its assertion and provide a copy of the agreement, marked in accordance with DFARS 252.227-7017). If the Offeror is proposing commercial computer software with a license that is greater than what is customarily provided to the general public, that Offeror shall submit a specifically negotiated license in the same format as required non-commercial computer software

The assertion lists from Annex B and Annex C will be incorporated into the resulting contract as Section J attachments. Pursuant to the requirements set forth in DFARS 252.227-7017, Offerors are required to specifically identify and assert whether any technical data, including computer software documentation, or computer software will be delivered with other than unlimited rights (at the base contract level and delivery order level). As indicated in DFARS 252.227-7017(e), an Offeror's failure to submit, complete, or sign the aforementioned Technical Data and Software Rights Assertions with its offer may render the offer ineligible for award. In accordance with the content and formatting requirements for the Technical Data and Software Rights Assertions (set forth in DFARS 252.227-7017), the Offeror's Technical Data and Software Rights Assertions shall comply with the following requirements:

For technical data (other than computer software documentation) pertaining to items, components, or processes developed at private expense, identify both the deliverable technical data and each such item, component, or process. For computer software or computer software documentation identify the software or documentation.The Offeror shall not assert license restrictions on items, component, or processes themselves. The asserted license restrictions shall pertain to software or technical data that relates to items, components, or processes.

The Offeror's Assertions shall not include technical data or software that will not be furnished to the Government under the resulting contract.

The Offeror shall provide a concise (but specific) description of the technical data and software deliverables that will be furnished to the Government with restrictions, rather than generically asserting license restrictions in "technical data" or "technology".

The Offeror is responsible for ensuring that Data and Software Rights Assertions from its subcontractors comply with the aforementioned content and formatting requirements (in accordance with DFARS 252.227-7017).

1.3 Technical Approach

1.3.1 The Offeror shall describe the overall technical approach to re-host the NSST software baseline to current generation state-of-the-art software technology (DO1 SOW 3.2.1.1.1). The Offeror’s technical approach shall address the following specific PRF requirements:

a. Quality of training (PRF 3.1.2.a thru d)

b. Instructor operator workload (PRF 3.1.8.5)

The Offeror shall provide an excel spreadsheet noting the current performance requirements and the proposed revised performance requirements for the technical elements being evaluated in this paragraph and any additional proposed performance requirements. Language shall be IAW IEEE 29148-2018 section 5.2 and shall be free of references to vendor products and brand names. Information provided on this spreadsheet does not constitute a list of self identified strengths or signifcant strengths. The information on this list will only be addressed in the technical evaluation if the evaluation team makes an independent determination that the information qualifies as a “strength” or “significant strength” as defined in Section M. The evaluation team will review the applicabilty of listed proposed revised performance requirements in conjunction with the techincal approach narrative to be provided with this paragraph for potential incorporation into the requirements documents for the awardee.

2.0 VOLUME 2 - PAST PERFORMANCE

Note: This volume shall not contain any reference to the 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 Past Performance Questionnaire (PPQ) Attachment PP-1 Contract Summary Attachment PP-2 Past Performance Contract Data

2.1 Past Performance Volume Information

2.1.1 The Offeror shall identify contracts whose performance is within five years of the solicitation issued date shown in block 5 of the SF33 in accordance with the following:

Past performance references may only be submitted from the following entities: prime contractor, JV, JV team member, and principal subcontractors.

The totality of the offeror’s proposal shall not include more than five past performance references with the following additional limitations:

Prime Contractor– No more than three contract references;

Joint Venture / Joint Venture Member – No more than three total contract references from the Joint Venture or from individual Joint Venture members that are part of the Joint Venture; and

Principal Subcontractors – No more than two contract references for each Principal Subcontractor.

2.1.2 Past Performance references must contain at least 1 day of performance within the prior 5 year timeframe of the date shown in block 5 of the SF33. If there is at least one day of performance within the 5 year timeframe, the performance of the entire contract will be considered. However, as stated in Section M, recent performance will be considered more influential when assigning the Performance Confidence Assessment rating when compared to performance references that are older.

2.2 Authorization Letter(s)

The Offeror should submit a signed “Release of Past Performance Authorization Letter(s)” with written consent from each principal subcontractor (including JV team members), authorizing the release of past performance information including adverse past performance information to the Prime. The signed letter(s) should be included, each on their own page, as part of Part B, Volume 2 (Past Performance). This authorization letter allows the Government to coordinate past performance issue(s) with the Prime Offeror. For any principal entity (including JV team members) that does not provide an authorization letter with such written consent, the Offeror shall provide point of contact information for each principal entity. This contact information shall include a name, address, phone number, and email address (including JV team members), with whom the Government may coordinate any issues and obtain responses as needed. Offerors are advised that if it does not submit the “Release of Past Performance Authorization Letters” with written consent, then the Government will address any past performance issues directly with the principal entity (including JV team members), and the Prime Offeror will forfeit the opportunity to participate in any related discussions.

2.3 CAGE Code

For the Past Performance evaluations, contract references that identify a different CAGE code and / or UEI than the proposed entity (prime contractor or subcontractor) will be considered if the CAGE code/UEI 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/UEI must appear in Table Admin

– 1 (Offeror Summary Table) which indicates a commitment of work for those entities. To facilitate the Relevancy determination for Past Performance, the Offeror shall provide a written explanation if multiple CAGE codes/UEI 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/UEI 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 relevance of any contract references provided. If there is any ambiguity as to whether the proposed Offeror, JV Team Member, or principal subcontractor performed the work identified in the Offeror’s proposal, the record will not be considered. Additionally, if applicable, the Offeror shall provide a description of the legal relationship between JV entities. If there are no differences, then, state “None” for this paragraph.

2.4 Past Performance Questionnaires and CPARS

2.4.1 Contract Performance Assessment Reporting System (CPARS) and Past Performance Questionnaires (PPQ) will be the primary customer feedback data used to evaluate the Offeror’s demonstrated past performance. The Offeror shall forward a copy of the PPQ (Attachment L-1) to the past performance contract customer’s Program Manager (PM), PCO and Contracting Officer Representative (COR) – with a copy to the Contract Specialist – for the following past performance contracts:

a. Ongoing or completed Past Performance contracts that do not have CPARS Reports.

b. Past performance contracts with CPARS Reports completed by the Assessing Official whose evaluation period is more than six months prior to the RFP’s release date where contract performance is still ongoing. In this situation, the PPQ should only provide performance information for the period of performance since the last CPAR was completed.

All questionnaires should be forwarded within 14 calendar days from the RFP release date, with a copy forwarded to the Contract Specialist. The Offeror shall include instructions for its customers to send completed questionnaires within two weeks of the customer’s receipt of the questionnaire to Duane Drury, CS, via email at duane.p.drury.civ@us.navy.mil.

2.4.2 Unless the Government directly solicits additional PPQ’s as described in paragraph 2.6.5 of this section, a PPQ is not required and shall not be submitted for past performance contracts that are ongoing and have a completed CPARS report that is within 6 months from the date of issuance of the solicitation as shown in block 5. The Government will not evaluate PPQs provided by offerors for completed contracts with a final CPAR submitted or for past performance contracts that are ongoing and have a completed CPARS report that is within 6 months from the date of issuance of the solicitation.

2.5 Past Performance Relevancy Instructions

2.5.1 The Offeror shall complete Attachments PP-1 (Contract Summary) and PP-2 (Past Performance Contract Data) for all contracts proposed for Past Performance. The Offeror shall complete the attachments according to the instructions below the PP-1 and PP-2 tables and submit it within this section. The contract references identified as P1, T1, or S1 in the PP-1:

Contract Summary Attachment shall be the same P1, T1, or S1 contracts identified in the PP-2:

Past Performance Contract Data Attachment. As set forth below, Offerors are required to cite specific pinpointed page numbers and paragraphs in PP-2 that reference the documents in Annex A (Supporting Documentation for Past Performance) so the Government may perform a comparison of the past performance contract’s product or service similarities to the instant solicitation’s work.

2.5.2 To enable the Government to perform a comparison of the past performance contract’s product or service similarities to the instant solicitation’s work for each past performance contract, the Offeror shall only provide the following for each contract reference noted in Attachment PP-1 (Contract Summary): 1) conformed contract document; and 2) complete SOW or PWS, and/or complete Performance Specification; and if applicable 3) subcontract agreement.

A conformed contract includes the contract document that incorporates all modifications through the proposal submission date and is dated and signed by the Contracting Officer. In the event that a Contracting Agency is unable to provide a signed conformed copy, the reference will only be considered if the Contracting Officer of the Past Performance reference sends an email to the Solicitation Contracting Officer and Contract Specialist (David Kors and Duane Drury) stating that the unsigned conformed copy is valid. The e-mail must include the contract reference’s modification number and date, which must match the reference provided by the Offeror. The Offeror is responsible for providing the unsigned conformed copy as part of its proposal and shall indicate in Attachment PP-2 block 4 that the PP reference PCO has provided the information required by this paragraph. The email from the PP PCO must be received by the proposal receipt date. The Government will not evaluate standalone modification documents.

These documents should be included in Annex A (Supporting Documentation for Past Performance). For contract references where the Offeror, JV Team Member, or principal subcontractor performed as a subcontractor, the Offeror, JV Team Member or principal subcontractor shall also provide a complete electronic copy of the SOW or PWS or other documentation of the agreement between the prime and subcontractor that clearly defines the portions of the work effort of the Prime’s SOW/PWS that the Offeror, JV Team Member, or principal subcontractor performed as a subcontractor..

NAWCTSD is not responsible or accountable for the clarity of an Offeror’s past performance contract. Information necessary to substantiate the relevancy of a past performance contract must be clear through a plain reading of the conformed copy of the past performance contract, its Statement of Work, the Performance Work Statement, the Specification, and / or subcontract agreement without further explanation. Offerors shall submit the entire Statement of Work, Performance Work Statement, Specification, and/or subcontract agreement. The Government does not want to receive, and the Government will not consider, any document submitted by the Offeror regarding past performance other than the documents referenced in this paragraph. The Government will not consider a document referenced within a Statement of Work, the Performance Work Statement, the Specification, and/or the subcontract agreement.

2.5.3 The Government does not want to receive, and the Government will not consider, an Offeror’s explanation or description of the alleged past performance effort or what the Offeror allegedly performed under a past performance contract. Government evaluators will compare the specific, pinpointed past performance contract’s costs/prices, terms, conditions, and Statement of Work, the Performance Work Statement, and/or the Specification pages and paragraphs that the Offeror cites in Attachment PP-2 to assess similarity to the Scope, Complexity and Magnitude the Government provides below for the instant solicitation. Should the Government identify information within the documents in Annex A that is not specifically referenced by the Offeror, the Government may utilize the information as part of its relevancy evaluation. However, the Government is not obligated to search for information throughout the Annex A documents in order to cure the Offeror’s proposal beyond the specific references provided by the contractor.

2.5.4 An Offerors’ proposal will be considered as noncompliant when the Offeror submits a past performance proposal that repeatedly fails to provide specific, pinpointed pages and paragraphs for the past performance Statement of Work, Performance Work Statement, the Specification and/or subcontract agreement, or fails to submit the fully executed conformed past performance contract and its Statement of Work, the Performance Work Statement, the Specification and / or the subcontract agreement. As a result, the Government may not perform an evaluation of that proposal and, instead, the Government may reject that Offeror’s proposal as noncompliant.

Should an Offeror’s proposal be rejected as noncompliant, its proposal will not be part of a competitive range determination.

2.5.5 For a single-award indefinite delivery past performance contract or other agreement (such as a Basic Ordering Agreement (BOA)), Offerors may propose the entire basic contract or agreement as a single past performance contract reference or Offerors may propose specific task or delivery orders as a single past performance contract reference. If an Offeror proposes individual task or delivery orders as separate past performance references, each order will count toward the record limit per Offeror. If an Offeror proposes an entire single-award indefinite delivery contract or agreement as a past performance contract reference, the Offeror may provide the past performance information for up to five (5) delivery orders/task orders issued under that single-award indefinite delivery contract or agreement, and those five orders will count as one past performance contract reference. Any past performance information for orders in excess of five will not be considered in the evaluation.

2.5.6 Task or delivery orders awarded under Multiple-Award Contracts (MACs) will be considered standalone “contracts” for purposes of past performance evaluation. Thus, Offerors may not propose an entire MAC as a past performance contract reference. In this situation, Offerors only receive past performance credit for work performed in the task or delivery order.

2.5.7 For both single award indefinite delivery contracts and MAC’s, the Government will only consider the Statement of Work, the Performance Work Statement, the Specification and / or the subcontract agreement from individual task or delivery orders. The Offeror will not be given credit for performance that has not been identified at the order level.

Attachment PP-1: Contract Summary

Offeror Name:

Entity Name Contract Reference

Contract Number

Contract Type

Contract Title

Prime or Joint Venture Company

P1 P2 P3

JV Team Member A T1 T2

JV Team Member N T3 T4

Subcontractor A S1 S2

Subcontractor B S3 S4

Attachment PP-1 Instructions:

Offeror Name: Fill in name of Prime Contractor;

Entity Name: Fill in the name of the entity that performed the submitted past performance contract and state the role of the entity (i.e.: Company X, Prime Offeror;

Company Y, JV Team Member, Company Z, Subcontractor);

Contract Reference: Provide a unique contract reference number for all contracts proposed as relevant for Past Performance. Utilize P1...Pn for the prime or Joint Venture Team proposing for this solicitation (regardless if the referenced contract was performed as a Prime or subcontractor), utilize T1...Tn for each JV team member proposed as part of a Joint Venture for this solicitation (only include contract references labeled as T1…Tn where the same Joint Venture Team members previously performed as a Joint Venture Team), utilize S1...Sn for subcontractors proposing for this solicitation (regardless if the work on the referenced contract was performed as a prime or subcontractor);

Contract Number: Provide the Contract Number (e.g., N00019-12-R-0001) for the referenced contract, inclusive of the basic contract number and delivery / task order number if applicable;

Contract Type: Include the Contract Type (FFP, etc.) for the referenced contract;

Contract Title: Include the Contract Name for the referenced contract;

Attachment PP-2: Past Performance Contract Data

Offeror Name:

1 Entity Name

2 Contract Reference

3 Title of Contract

4 Contract Number

5 Contract Type

6 Delivery/Task Order Numbers (if applicable)

7 Subcontract Number/PO Number

8 Procuring agency

9 Description of product or service

Period of performance – Start Date Period of performance – End Date

CAGE Code (if not the same as the proposed entity, explain as per Section L, Part B paragraph 2.3)

12 Magnitude: Dollar value of contract (Total)

a. Scope:

i. Provide the specific citation from the Annex A contract reference documents associated with:

Delivering systems with associated data following the DoD or commercial standards for systems engineering

b. Complexity:

i. Provide the specific citation from the Annex A contract reference documents associated with:

Delivering high fidelity models that accurately simulate the physics and visualizations of Military Maritime vessels, maritime vessels, or military vehicles and geographic areas based on real world data; and

ii. Provide the specific citation from the Annex A contract reference documents associated with:

Delivering trainer consoles that accurately emulate the functions and haptics of consoles onboard Military Maritime vessels, maritime vessels, or military vehicles; and

iii. Provide the specific citation from the Annex A contract reference documents associated with:

Delivering training systems at two sites with at least one site OCONUS.

15 Date of last completed CPARs

16 Date past performance questionnaires were sent

Points of Contact who can validate performance on the past performance contract, specific delivery order or task order number referenced above.

18 Gov't PCO or Commercial Purchasing Agent

Name:

Phone:

Email:

19 Gov't ACO

Name:

Phone:

Email:

20 Gov't PM or Commercial PM

Name:

Phone:

Email:

21 Other:

Name:

Title:

Phone:

Email:

Attachment PP-2 Instructions: (Provide a separate Table for each contract reference) Offeror Name: Specify the name of the Prime Offeror;

1. Entity Name: Specify the name of the entity who performed the work on the contract reference;

2. Contract Reference: Specify the contract reference used in the Relevant Contract Summary (Attachment PP-1);

3. Title of Contract: Provide the title of the referenced contract;

4. Contract Number: Provide the contract number (e.g., N00019-10-C-1234) for the contract reference;

5. Contract Type: Specify the contract type for the contract reference (e.g., FFP, CPFF, CPIF, or FPIF);

6. Delivery/Task Order Numbers (if applicable): If a task / delivery order is being submitted from a MAC, this field should only include 1 task / delivery order number.

If multiple task / delivery orders are being submitted from a single award ID/IQ, all task / delivery orders being submitted as a single past performance…