N6134025R0001 Amendment 0001 Mod.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:

1. Update the extended descriptions on CLINs 5000, 5001, 5002, and 8000 to reference correct SOW paragraphs.

2. Add Section J, Attachment 15, Solicitation Questions and Answ ers, dated 15OCT2024.

3. Update language in Sections L & M that resulted from questions and answ ers documented in Section J, Attachment 15, Solicitation Questions and Answ ers, dated 15OCT2024.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 26

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

16C. DATE SIGNED

BY 18-Oct-2024

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 N6134025R0001

X 9B. DATED (SEE ITEM 11)

12-Sep-2024

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 X is extended, 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

18-Oct-2024

CODE

NAWCTSD PROCUREMENT GROUP

GT25000

12211 SCIENCE DR

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:

N6134025R0001

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 28-Oct-2024 02:00 PM to 07-Nov-2024 02:00 PM.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 5000

The CLIN extended description has changed from:

Provide I/O training course IAW SOW paragraph 3.2.9.2.6.1 and deliver technical documentation and information for CDRL F001 as defined in DD1423, Exhibit F.

To:

Provide I/O training course IAW SOW paragraph 3.2.9.2.5.1 and deliver technical documentation and information for CDRL F001 as defined in DD1423, Exhibit F.

CLIN 5001

Provide maintenance training course training IAW SOW paragraph 3.2.9.2.6.2 and deliver technical documentation and information for CDRL F002 as defined in DD1423, Exhibit F.

Provide maintenance training course training IAW SOW paragraph 3.2.9.2.5.2 and deliver technical documentation and information for CDRL F002 as defined in DD1423, Exhibit F.

CLIN 5002

Provide cybersecurity training course training IAW SOW paragraph 3.2.9.2.6.3 and deliver technical documentation and information for CDRL F003 as defined in DD1423, Exhibit F.

Provide cybersecurity training course training IAW SOW paragraph 3.2.9.2.5.3 and deliver technical documentation and information for CDRL F003 as defined in DD1423, Exhibit F.

CLIN 8000

The contractor shall provide the initial support items necessary to support therequirements in accordance with SOW paragraphs 3.2.3.5 and A.3.3 and as described in attachments & exhibits.

The contractor shall provide the initial support items necessary to support the requirements in accordance with SOW paragraphs 3.2.9, 3.2.9.3.2, and A.3.3 and as described in attachments & exhibits.

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

LIST OF ATTACHMENTS

List of Attachments

Attachment Number

Document Description Date

1 Statement of Work (SOW) 230054, Aviation Electrician (AE) A-School Training Devices

17 APR 2024

2 Performance Specification (PRF) 230050 Flaps and Landing Gear Trainer

11 APR 2024

3 Performance Specification (PRF) 230051 Dual System Generator Trainer

11 APR 2024

4 Performance Specification (PRF) 230052 Aircraft Basic Electronic System Trainer

11 APR 2024

5 Performance Specification (PRF) 230053 Aircraft Jet Ignition System Trainer

11 APR 2024

6 Government Furnished Information (GFI) List 12 AUG 2024 7 NAWCTSD 4330/60 Data Item Transmittal (DIT)/Acceptance/

Rejection Form

JAN 2023

8 L-1 Offeror Summary Table (OST-1)

30 AUG 2024

9 L-2 Past Performance Questionnaire (PPQ)

10 L-3 Past Performance Contract Summary

11 L-4 Past Performance Contract Data

12 L-5 Relevancy Information of the Past Performance Contract 30 AUG 2024 13 L-6 Solicitation Questions 30 AUG 2024 14 L-7 Contractor Government Furnished Information Non-Disclosure

Agreement

15 Solicitation Questions and Answers 15 OCT 2024

Exhibit A Product Engineering Drawings and Associated Lists

AE_A001_PEDDAL_SIGNED

23 APR 2024

Requirements Traceability and Verification Matrix

AE_A002_RTVM_SIGNED

23 APR 2024

Software Product Design

AE_A003_SPD_SIGNED

23 APR 2024

Software Product Package

AE_A004_SPP_SIGNED

23 APR 2024

Safety Assessment Report

AE_A005_SAR_SIGNED

23 APR 2024

Test Procedure

AE_A006_TEST PROCEDURE_SIGNED

23 APR 2024

Test Inspection Report

AE_A007_TEST INSPECTION REPORT_SIGNED

23 APR 2024

Exhibit B Contractor’s Progress and Status Report

AE_B001_CPSMR_SIGNED

24 APR 2024

Integrated Program Management Data and Analysis Report

AE_B002_IPMDAR_SIGNED

24 APR 2024

Conference Minutes AE_B003_Conf Min_SIGNED

24 APR 2024

Conference Agenda AE_B004_Conf Agenda_SIGNED

24 APR 2024

Exhibit C Bill of Materials

AE_C001_BOM_SIGNED

24 APR 2024

Training System Sparing Product Data

AE_C002_TSSPD_SIGNED

24 APR 2024

Exhibit D Baseline Description Document

AE_D001_BDD_SIGNED

01 MAY 2024

Configuration Audit Plan

AE_D002_CAP_SIGNED

01 MAY 2024

Configuration Audit Summary Report and Certification

AE_D003_CASR_SIGNED

01 MAY 2024

Training Device Inventory Checklist/Record

AE_D004_TD ICL-R_SIGNED

01 MAY 2024

Item Unique Identification Marking Activity, Validation and Verification Report

AE_D005_IUID REPORT_SIGNED

01 MAY 2024

Trainer Facilities Report

AE_D006_TFR_SIGNED

24 APR 2024

Exhibit E Training System Maintenance Task Analysis

AE_E001_TSMTA_SIGNED

24 APR 2024

Training System Maintenance Manual

AE_E002_TSMM_SIGNED

24 APR 2024

Training System Operators Manual

AE_E003_TSOM_SIGNED

24 APR 2024

Exhibit F Training Program Structure Document – Instructor Operator Training Course

AE_F001_TPSD_IOTC_SIGNED

24 APR 2024

Training Program Structure Document – Maintenance Training Course

AE_F002_TPSD_MTC_SIGNED

24 APR 2024

Training Program Structure Document – Cyber Security Training Course

AE_F003_TPSD_CSTC_SIGNED

24 APR 2024

Attachments 8 - 15 are for RFP purposes only and will not be a part of the resultant contract award.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

INSTRUCTIONS AND NOTICES

INSTRUCTIONS TO OFFERORS

PART A: GENERAL INSTRUCTIONS

1.0 GENERAL

1.1 Section L contains instructions on how to prepare and submit proposals in response to this solicitation. These directions supersede any contrary information contained in the SF-33. Nonconformance with these instructions may result in an unfavorable proposal evaluation and/or elimination from consideration. Clear, concise, and logical organization should be emphasized during proposal preparation. Alternate proposals are not acceptable.

1.2 The Offeror shall submit sufficient information concerning all evaluation factors to enable Government personnel to fully assess and understand the Offeror’s approach, expertise, and capability to perform the requirements of the solicitation. In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Do not provide elaborate brochures or other presentation material beyond that necessary to present a complete and effective proposal. The burden of proof for all substantiation within the proposal rests with the Offeror, meaning, the Offeror shall include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions. Statements that the Offeror will provide a particular feature or objective without explaining how the Offeror proposes to meet that feature or objective are generally inadequate and may adversely impact the Government’s evaluation assessment of the Offeror. Also inadequate are the following types of statements:

unsupported statements that the Offeror allegedly understands the requirements and risks;

unsupported statements that the Offeror allegedly can or will comply with requirements;

unsupported statements that merely paraphrase the requirements;

undefined or explained statements such as “best commercial practices will be used”;

undefined or explained statements such as “standard procedures will be used”; and undefined or explained statements such as “well-known techniques will be employed.”

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. Proposal shall not include hyperlinks. The Government will not evaluate hyperlinked information. Price information (e.g., dollar values and/or hourly rates) shall appear only in Volume 2 Price.

1.3 Offerors are advised that the Government may incorporate any part of the Offeror’s proposal deemed beneficial to the Government into the final contract.

1.4 As used in this RFP, the following terms are defined: “Offeror” means the prime contractor with its CAGE code identified in Block 15A on Standard Form (SF) 33 Solicitation, Offer, and Award. “Joint Venture” (JV) means a partnership or teaming arrangement where the prime contractor consists of more than one legal entity. “JV Team Members” means the entities that make up a Joint Venture. “Entity” means any 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/UEI than the Offeror). “Principal Entities” means (a) the prime contractor; (b) JV Team Members; and (c) principal subcontractor(s) that are proposed to perform at least 10% of the proposed total cost/price for the contract.

2.0 PROPOSAL FORMAT

2.1 The Offeror shall submit its files electronically in separate Volumes, or Attachments as specified in Table 1.

Please submit the information contained within each Volume, Book, or Attachment as one file if possible. Do not provide separate files for each section/paragraph. Submission naming convention shall include a maximum of three letters to represent the Offeror’s name.

2.2 Use letter-sized (8 ½’ x 11”) pages, single-spaced, with one inch (1”) margins on all sides. Number the pages consecutively and use a 12-point, Times New Roman font. 10-point font in graphics and tables is permissible.

Offerors may use up to 11" x 17" pages for the sole purpose of more effectively presenting large or complex tables, graphics, and illustrations for evaluation. Regardless of the page size, it will be counted as one page.

Table 1

Volume Number Volume Title Page Limit

1 Technical 32

2 Price As needed

3 Past Performance As Needed

4 Administrative As Needed

Each Volume, Book, or Attachment shall be properly identified, numbered, and organized. Each Volume, Book, and Attachment shall also contain clearly identified sections and all pages shall be numbered and identified by the complete Offeror name, date, and solicitation number in the header or footer.

2.3 Operating System and Applications. The Offeror shall use Microsoft Office (MS) 2016 software or compatible, and Adobe software, if applicable, in the development of its proposal submission. Any Adobe document, letters, other signed documents, and evidence of compliance shall be provided as a fully searchable Portable Document Format (.pdf) files. Numerical data presented in MS Office format must not be pictorial (i.e., pasted as a picture out of a MS Excel file). The Offeror shall use formulas and functions to the maximum extent possible within all MS Excel spreadsheets. Use of other application software for submission of proposals is prohibited except where specific instructions for non-.pdf or Office 2016 applications are provided. The Offeror must provide the Government with full access to all documents and information provided in the submission package, unprotected and unlocked.

2.4 The Offeror is responsible for ensuring that its electronic proposal is virus free.

3.0 ELECTRONIC PROPOSAL SUBMISSION

3.1 All volumes of the proposal shall be submitted electronically through the Solicitation Module of the

Procurement Integrated Enterprise Environment (PIEE) at https://piee.eb.mil. No other submission method, such as mail, hand-carried, or other electronic system (e.g., DOD SAFE) are authorized by the solicitation unless specifically authorized by the Contracting Officer pursuant to paragraph 3.2 below. For instructions on how to post an offer, please refer to the Posting Offer demo:

https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf or https://pieetraining.eb.mil/wbt/sol/Posting_Offer.html. Offerors shall submit all proposal documents against Solicitation Number N6134025R0001 in the PIEE Solicitation Module. If a proposal is not submitted in the PIEE Solicitation Module against this Solicitation Number, then the submission will not be considered as having been submitted in response to this Solicitation. For example, any proposals that are submitted under the

PIEE Solicitation Module’s “Unsolicited Proposal” section are not considered to have been submitted in response to this Solicitation Number. Additionally, if a proposal is inadvertently submitted against a different Solicitation Number in the PIEE Solicitation Module, then that proposal will not be considered as a response to this Solicitation. Similarly, if a portion of a proposal is incorrectly submitted (such as in the wrong PIEE module, the PIEE Solicitation Module “Unsolicited Proposal” section or under another solicitation number), then the incorrectly submitted portion of the proposal will not be considered as having been submitted in response to this Solicitation and will therefore not be evaluated by the government.

3.1.1 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 Offeror. Documents submitted by the subcontractor directly to the Government must have the prime contractor’s name, CAGE, and RFP number on the first page of the document.

3.1.2 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 against this solicitation. The Government is not obligated to search for incorrectly submitted proposals in PIEE.

3.1.3 The submission date for all Volumes shall be no later than the date and time specified in Block 9 of the SF 33 of the RFP. Offerors are on notice that the PIEE system will determine a proposal as late, or untimely, if the submission is not fully submitted prior to the time specified in Block 9 of the SF 33. For example, if the time specified in Block 9 of the SF 33 is 2:00 pm, then the PIEE system will consider a proposal as late if it is submitted at 2:00:01, one second after the deadline. The PIEE system should notify an Offeror if the proposal was submitted after the deadline for submission, and whether a proposal is late. However, even if the PIEE system does not provide this notification, the contracting officer will utilize the time stamp(s) of the proposal submission(s) to make a determination if the proposal submission(s) was timely submitted.

3.1.4 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 Offeror 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 as shown in paragraph

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

3.2 The following alternate methods may be utilized when authorized by the Contracting Officer in accordance with paragraph 3.1.

3.2.1 Contractor proposals Submitted by Carrier: The Offeror shall submit electronic CD-ROM proposals via United States Postal Service or through a commercial carrier with next day delivery using the address provided below.

Naval Air Warfare Center Training Systems Division Code: GT25000 (Allison Laera/Julide Alonso) 12211 Science Drive Orlando, FL 32826 Solicitation Number: N61340-25-R-0001

3.2.2 Hand carried Proposals: Hand carried proposals must be delivered to the address above, attention Julide Alonso, Phone 407-380-4261 and Allison Laera, Phone 407-380-4659. If a proposal or amendment is hand carried, the Contractor must have current base access to deliver the proposal. Without base access, the Contractor may not get beyond the installation security gate to deliver its proposal. Guards are not authorized to accept proposals.

Each Volume shall be on a separate CD-ROM. Delivery time shall be coordinated with the contracting office to ensure availability to sign for the package.

3.2.3 Each Volume shall be on a separate CD-ROM. The package shall include all proposal volumes including the digitally signed document(s) submitted as part of the Cost/Price Volume. The package shall include a packing slip detailing the contents to include the volume number, and title. Also, the package shall be stamped or marked “Controlled Unclassified Information” and “Source Selection Information – See FAR 2.101 and 3.104.”

4.0 NOTICES TO OFFERORS

Notice Concerning Organizational Conflicts of Interest: Any Contractor having participated in the development of any requirements for this solicitation must identify the degree of participation and any recommended steps to be taken to mitigate any competitive advantage that may have resulted from said performance. Without the identification and mitigation recommendation, proposals submitted by Offerors having prior knowledge of the contract requirements will not be considered for award.

5.0 CHANGES TO SOLICITATION

For any changes and additional information to the solicitation please go to website: https://SAM.gov. Search the database for the solicitation number N61340-25-R-0001.

6.0 SOLICITATION QUESTIONS

Questions regarding this solicitation shall be submitted in writing with the use of Attachment L-6, Solicitation Questions. Each question or comment should reference the applicable document, page number, and paragraph number. Do not include any proprietary information in your question, because the Government will provide the question and answer to all potential Offerors. All questions must be submitted for the solicitation no later than 1400 Eastern Daylight Time (EDT) on October 03, 2024 via email to Julide Alonso at julide.n.alonso.civ@us.navy.mil with a copy to Allison Laera at allison.m.laera.civ@us.navy.mil. The Government is under no obligation to answer questions received, but will attempt to do so as time permits.

7.0 PROPOSAL SUBMISSION

All Proposals shall be UNCLASSIFIED.

8.0 OTHER INFORMATION

8.1 Acceptance Period: Any proposal submitted requires a minimum acceptance period of 180 calendar days. The “Acceptance Period” is the number of calendar days available to the Government for awarding a contract from the date specified in this solicitation for receipt of proposals. This provision supersedes any language pertaining to the acceptance period that may appear elsewhere in this solicitation. The Government may reject an offer allowing less than the minimum acceptance period.

The Offeror agrees to execute all that it has undertaken to do, in compliance with its offer, if that offer is accepted in writing within the acceptance period stated above.

8.2 Technical Data for Offerors: The technical data required by Offerors will be made available as part of the solicitation. Offerors are instructed to send a request for information utilizing Attachment 14, L- 7, Contractor Government Furnished Information Non-Disclosure Agreement via email to Julide Alonso, julide.n.alonso.civ@us.navy.mil with Allison Laera, allison.m.laera.civ@us.navy.mil copied.

All data is restricted from export by the Arms Export Control Act (Title 22, U.S.C., Sec. 2751 or Executive Order 12470). Contractors shall abide by these restrictions. All technical data is provided on an “as-is” basis. The Government shall not take responsibility for the accuracy of the information, as it may not be error free.

Upon award of the contract resulting from the subject solicitation, the unsuccessful Offerors shall either destroy and provide notification to the POC identified or return all technical data to the POC identified within 10 calendar days of receiving notification from the Government. In the event the solicitation is cancelled, all Offerors shall return the technical data to the POC identified within 10 calendar days of being notified by the Government that the solicitation is cancelled. The 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 POC within 10 days after contract award that they have complied.

The successful Offeror shall maintain possession of the data for use during contract execution, as may be directed by the Government.

PART B: SPECIFIC INSTRUCTIONS

1.0 VOLUME 1: TECHNICAL

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

The Offeror shall provide all information and data required to conduct a thorough and complete technical factor evaluation. The proposal shall describe how the Offeror will provide, organize and coordinate resources and perform technical activities to ensure compliance with the Statement of Work (SOW), Performance Specifications (PRF 230050, 230051, 230052, and 230053), Request For Proposal (RFP) requirements, and the timely delivery of the AE trainer platforms. In response to the Technical Factor the Offeror shall address the following subfactors in the technical portion of the proposal:

1.1 System Architecture

For the purpose of this proposal, the Offeror shall provide its approach for the trainer architecture information specific to the Aircraft Basic Electronic System Trainer (PRF 230052) by completing the following.

The Offeror shall provide a system schematic that identifies the key subsystems as identified by the Offeror in accordance with SOW Section 3.2.2.4 and PRF 230052 Section 3.1.1.

The Offeror shall (1) describe its approach to designing a trainer that meets the hardware requirements in accordance with SOW Section 3.2.2.4 and PRF 230052 Section 3.1.a, c-f and (2) clearly describe the plan to integrate the Instructor Operator Station (IOS) with each Student Station to meet the interface requirements between the IOS and student station, the instructor controls on the IOS, system faults, and the student station responses to the instructor inputs in accordance with SOW Sections

3.2.2.4 and 3.2.2.5 and PRF 230052 Sections 3.1.3.1 and 3.1.3.2.

1.2 Fabrication and Delivery

The Offeror shall describe its general plan for fabricating all four trainer types to meet the requirements found in SOW Section 3.1.2. The plan shall include a description of how the Offeror will provide the needed resourcing, personnel, and physical space to meet the requirements in accordance with SOW Section 3.1.2. The plan shall also include a timeline showing how the offeror will fabricate and deliver trainers in accordance with SOW Section 3.1.2.

1.3 Logistics

The Offeror shall describe its approach to developing a maintenance plan for the Aircraft Basic Electronic System Trainer in accordance with SOW Sections 3.2.9.1 and PRF 230052 Sections 3.1.5 and 3.1.15.1. The Offeror shall describe how the system design approach considers supportability obsolescence and interchangeability issues in accordance with SOW Sections 3.2.3.1.3 and 3.2.9.3.3. The Offeror shall also describe the approach to developing a Contractor Logistics Support (CLS) plan that supports the sustainability and maintenance of the trainer during the CLS period, including discussions of (1) the response time for emergencies, (2) lead times on hardware, (3) accessibility to Offeror maintenance and sustainment personnel contacts, and (4) the plan for any required maintenance in accordance with SOW Sections 3.2.11 and subparagraphs and A.3.6.

1.4 Data Rights

The Offeror shall provide a software architecture diagram identifying: (1) each software the Offeror proposes to include in the trainers and (2) which software interfaces with which other software.

The Offeror shall, for each software the Offeror proposes to include in the trainers that is not Commercially available Off-The-Shelf (COTS) per FAR 2.101, specify the (1) libraries, compilers, and other components needed for that software to perform its function or needed to modify that software, (2) native code development environment, and (3) code language.

The Offeror shall, for each technical data deliverable and each software the Offeror proposes to include in the trainers as well as the libraries associated with that software, identify the rights offered to the Government. The Offeror shall identify the rights as Unlimited, Government Purpose, Limited, or Restricted (as described in DFARS 252.227-7013 and 252.227-7014); or specifically negotiated or commercial. If offering a specifically negotiated license(s) or commercial license(s), include the proposed license(s). The Offeror shall state whether it is proposing to provide the source code, compiler, and the design environment for each software the Offeror proposes to include in the trainers.

2.0 VOLUME 2: PRICE

The Price Volume shall stand alone and be submitted in a separate volumes. The volume shall be prepared in accordance with the instructions below as a self- contained document requiring no cross-referencing to other proposal documents.

As this is a competitive acquisition with adequate price competition anticipated, any price documentation requested need not be certified cost or pricing data in accordance with FAR 15.403-1(b)(1). However, in the event that all of the criteria that establishes adequate price competition IAW FAR 15.403-1(c)(1) is not met after receipt of proposals, the Government may request additional cost or pricing data as necessary from the Offeror. IAW FAR 15.403-4, the Offeror may be required to provide a Certificate of Current Cost or Pricing Data prior to award.

The Offeror shall provide additional cost or pricing information and certify the data prior to award if requested by the Government.

The Offeror shall provide a copy of Section B populated with unit and total prices for all CLINs/SLINs.

The Offeror shall explain any appearance of unbalanced pricing. Unbalanced pricing exists when, despite an acceptable total evaluated price, the price of one or more contract line items is significantly overstated or understated as indicated by the application of cost or price analysis techniques.

3.0 VOLUME 3: PAST PERFORMANCE

The following is a list of Section L Attachments that the Offeror shall utilize to provide information to address the elements below.

Attachment 8, L-1 Offeror Summary Table (OST-1) Attachment 9, L-2 Past Performance Questionnaire (PPQ) Attachment 10, L-3 Past Performance Contract Summary Attachment 11, L-4 Past Performance Contract Data Attachment 12, L-5 Relevancy Information of the Past Performance Contract Attachment 13, L-6 Solicitation Questions Attachment 14, L-7 Contractor Government Furnished Information Non-Disclosure Agreement

3.1 Past Performance Submission Information

a) 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 (i.e. entity identified in Block 15A of Standard Form 33) – No more than three contract references;

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

Principal Subcontractors (i.e. an entity proposed to perform at least 10% of the proposed effort) – No more than two contract references for each Principal Subcontractor.

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

3.2 Authorization Letter(s)

The Offeror should submit a signed “Release of Past Performance Authorization Letter(s)” with written consent from each principal entity (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 3 (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.

3.3 Commercial and Government Entity (CAGE) Code/Unique Entity ID (UEI)

Only past performance of the offeror (including JV Team Members and principal subcontractors) is relevant. The Government will only consider past performance of some other CAGE Code/UEI if (1) the offeror demonstrates that it acquired that other CAGE Code through a corporate acquisition, reorganization, or merger and the personnel, facilities, or other resources of that other CAGE Code are now a part of the offeror and will be used to perform the requirements of the solicitation, or (2) the Government is required by 13 CFR 125.11 to consider the past performance where the offeror submits the information required by 13 CFR 125.11.

If the offeror submits a past performance reference for an entity with a CAGE Code other than the CAGE Codes listed in Attachment L-1, then the offeror shall provide a written explanation as to how that performance is reflective of the offeror and any related information, such as corporate acquisition or merger information or information required by 13 CFR 125.11. If there is any ambiguity as to whether a proposed entity (i.e. prime offeror, JV team member, or principal subcontractor) performed the past performance reference, the record will not be considered.

3.4 Attachment L-1 Offeror Summary Table (OST-1)

The offeror shall complete the table similar to the one below (OST – 1) to be submitted with this volume. This table should summarize the prime, JV, JV team member or subcontractor with CAGE Codes/UEI numbers, roles and responsibilities, as well as their work description, and the % of effort under the instant contract award.

Attachment L-1 Offeror Summary Table (OST-1)

Offeror:

Offeror Name:

Indicate Prime, JV, JV Team Member, Subcontractor or Entity Name(s)

Physical Location of Entity

CAGE

Codes/UEI

Roles and Responsibilities with Work Description

Workshare - % Total Proposed Price

Percentage Total Under the instant contract award (not dollar amounts, percentages must add up to 100%)

100%

OST-1 Table Instructions:

Offeror Name: Fill in name of Prime Contractor & indicate Prime, JV, JV Team Member or Subcontractor.

Entity Name: List all entities who will be involved with performance or management of the requirements of this solicitation. Add rows as necessary.

Physical Location of Entity: List the physical location of each entity.

CAGE Codes/UEI: Provide the CAGE Codes/UEI numbers associated with the entity that is proposing to perform the work for this solicitation.

Roles and Responsibilities with Work Description: Provide brief work description and Program Role and Responsibility for each entity identified.

Workshare % Total Under the contract award: Provide the percentages of effort to include all entities so that the % totals add up to 100%.

3.5 Past Performance Questionnaires and CPARS

3.5.1 Contract Performance Assessment Reporting System (CPARS) and PPQs 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-2) 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 more than six months prior to the RFP’s release date where contract performance is still ongoing.

All questionnaires should be forwarded by 1400 EDT 24 October 2024, 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 via e-mail to Julide Alonso, Contract Specialist, at email:

julide.n.alonso.civ@us.navy.mil.

3.5.2 Unless the Government directly solicits additional PPQ’s as described in paragraph 3.5.1 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 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.

3.6 Past Performance Relevancy Instructions

3.6.1 The Offeror shall complete Attachments L-3 (Past Performance Contract Summary), L-4 (Past Performance Contract Data) and Attachment L-5 Relevancy Information of the Past Performance Contract for all contracts proposed for Past Performance. The Offeror shall complete the attachments according to the instructions below for the L-3 table, L-4 table, and L-5 table and submit it within this section. The contract references identified as P1, T1, or S1 in the L-3: Past Performance Contract Summary Attachment shall be the same P1, T1, or S1 contracts identified in the L-4: Past Performance Contract Data Attachment and the same for L-5: Relevancy Information of the Past Performance Contract. As set forth below, Offerors are required to cite specific pinpointed page numbers and paragraphs in L-5 that reference the documents in Volume 3 as 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 contract award’s work.

3.6.2 To enable the Government to perform a comparison of the past performance contract’s product or service similarities to the instant contract solicitation’s work for each past performance contract, the Offeror shall only provide the following for each contract reference noted in Attachment L-3 (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 into the conformed contract through the proposal submission date. The Government will not evaluate standalone modification documents. 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. These documents should be included in Volume 3 as Supporting Documentation for Past Performance.

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.

3.6.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, except as requested in section 3.6.10 below. 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 to assess similarity to the Scope, Complexity and Magnitude the Government provides below to the instant contract’s solicitation. Should the Government identify information within the documents in Volume 3 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 Volume 3 documents in order to cure the Offeror’s proposal beyond the specific references provided by the contractor.

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

3.6.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 three (3) delivery orders/task orders issued under that single-award indefinite delivery contract or agreement, and those three orders will count as one past performance contract reference. Any past performance information for orders in excess of three will not be considered in the evaluation.

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

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

3.6.8 Attachment L-3: Past Performance 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 B T3

T4

JV Team Member C T5 T6

Subcontractor A S1

S2

Subcontractor B S3

S4

Attachment L-3 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-C-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.

3.6.9 Attachment L-4: Past Performance Contract Data

Provide the information identified below in an MS Word Table for each past performance contract identified.

Prime or Joint Venture Company, JV Team Member, or Subcontractor

(Follow same reference notations as referenced in L-3 Instructions, Contract Reference above)

P1 P2 P3 S1 S2

1 Contractor’s Name

2 Contractor’s Role in the Past Performance Contract, and Contractor’s Proposed Role in the Instant Contract

3 Contract Title

4 Contract Number

5 Contract Type: Firm-fixed-price, cost-reimbursable-fixed-fee, etc.

6 Procuring Agency

7 Description of Product or Service

8 Acquisition Phase of Contract – Development versus Production

9 Period of Performance

10 Dollar Value of Contract

11 Dollar Value of Effort Performed by the Contractor

12 Place of Performance1

13 CAGE Code and/or UEI 2

14 Do CPARS exist? Yes or No3

15 If CPARS exist, state the number of CPARS that exist

16 If CPARS exist, state the completion dates

17 Agree to Allow Coordination with Prime Offeror? Yes or No.

18 The Number of Questionnaires the Contractor Sent

19 Point of Contact’s Name, Phone Number, Fax Number, and Email Address for each questionnaire sent

20 Did Performance Take Place Within Required 5 Year Period? Yes or No

1 Place of Performance should be the location of the government or contractor’s facility where the predominance of the work was performed.

2 Provide the CAGE Code and UEI of the company performing the work. If the CAGE Code or UEI is different than the past performance entity proposed to perform the solicitation’s effort, please explain the reason.

3 As part of its Past Performance Volume, the offeror shall provide printed CPARS that are referenced in the table as part of the past performance volume.

3.6.10 Attachment L-5 Relevancy Information of the Past Performance Contract to the instant contract award. For each past performance contract, provide the following information and use specific, pinpointed past performance contract’s costs/prices, terms, conditions, Statement of Work, the Performance Work Statement, and/or the Specification pages and paragraphs as requested in section 3.6.3 above and when addressing items 1-8 in the table below.

Attachment L-5 Relevancy Information of the Past Performance Contract

Provide the information identified below in an MS Word Table for each past performance contract identified.

Prime or Joint Venture Company, JV Team Member, or Subcontractor

(Follow same reference notations as referenced in L-3 Instructions, Contract Reference above)

P1 P2 P3 S1 S2

1 Contract Types: Compare the contract type of the past performance contract to the contract type of this solicitation’s effort.

2 Total Dollar Amounts: Compare the total dollar amount of the past performance contract to the total proposed dollar amount of this solicitation’s effort.

3 Dollar Amounts Actually Performed: Compare the dollar amount of the effort actually performed by the company under the past performance contract to the dollar amount of the effort proposed to be performed by the company under this solicitation’s effort.

4 Locations and Divisions: Compare the location and division of the company that performed the past performance contract effort to the location and division of the company that is proposed to perform this solicitation’s effort.

5 Period of Performances: Compare the period of performance of the past performance contract to the period of performance actually performed under that past performance contract to that of the company proposed to perform.

6 Compare similarities: Compare the similarity of the product or service actually performed by the company under the past performance contract to the product or service proposed to be performed by the company proposed to perform under this solicitation’s effort for scope.

7 Compare similarities: Compare the similarity of the product or service to perform under this solicitation’s effort for Magnitude.

8 Compare similarities: Compare the similarity of the product or service to perform under this solicitation’s effort for Complexity.

3.7 Demonstrated Past Performance Instructions

3.7.1 For each past performance contract, the Offeror shall provide all available CPARS in their entirety in accordance with the timelines stated in sections 3.1, 3.5.1, and 3.5.2 that address…