N0042123R0064-0002.pdf

N0042123R0064

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

Update Section L, 4.4.1, Section M, C. Price, and post additional Q&As.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 42

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

16C. DATE SIGNED

BY 04-Jun-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 N0042123R0064

X 9B. DATED (SEE ITEM 11)

08-May-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 is extended, X is not extended.

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

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

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

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

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

04-Jun-2024

CODE

NAWCAD PROCUREMENT GROUP

21983 BUNDY ROAD, BLDG 441

PATUXENT RIVER MD 20670

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been modified:

DESCRIPTION OF CHANGES

The purpose of Amendment 0002 is to reflect changes from Industry questions / Government responses to include:

1) Section L, 4.4.1 to read from, "The Offeror shall propose the quantity (no less than three months)", to "The Offeror shall propose the quantity (no less than four months)".

2) Section M, C. Price, to read from, "The Government will confirm that the proposed price for NTE CLINs is equal to the Government provided NTE amount listed in Section B." to “The Government will confirm that the proposed price for NTE CLINs does not exceed the Government provided NTE amount listed in Section B”

The purpose of Amendment 0001 is to reflect changes from Industry questions / Government responses to include:

1) Section A

a) The required proposal due date/time has changed from 10-June-2024 1400 Eastern Standard Time to 24- Jun-2024 1400 Eastern Standard Time.

2) L Attachment

a) L-6 Vol 4 Price Worksheet

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

SECTION L

Section L - Instructions, Conditions and Notices to Bidders

PART A GENERAL INSTRUCTIONS

1. GENERAL

Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to fully assess the capabilities of the Offeror to perform all requirements.

The proposal must be sufficient in detail and scope to enable evaluation and provide the evaluators a clear understanding of the Offeror’s approach, expertise, and capability as required by the solicitation. Proposals must demonstrate that the Offeror has a thorough understanding of all requirements and associated risks and is able, willing, and competent to devote the resources necessary to meet all requirements. The Offeror shall not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. Offerors are advised that the Government may incorporate any part of the Offeror’s proposal deemed beneficial to the Government, into the final contract, with or without discussions. Alternate proposals are not acceptable.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the responsibility of the Offeror to present enough information to allow the Government to evaluate its proposal without discussions. 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.

Throughout these instructions, “Offeror” is defined as the prime contractor with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. A “Joint Venture” (JV) is a partnership or teaming arrangement that is formed for the purpose of responding to this solicitation when the prime contractor consists of more than one legal entity.

“JV Team Members” are the entities that make up a Joint Venture. The term “entity” is used to mean any or all of the following: prime contractor, JV, JV team members, any subcontractor, and corporate parent, division, subsidiary, or affiliate (e.g., any contractor with a different CAGE Code/Unique Entity Identifier (UEI) than the Offeror). The following entities are defined as principal entities and only principal entities will be used in the past performance evaluation: (a) the prime contractor; (b) JV Team Members; and (c) other entities that are proposed to perform at least 20.00% of the proposed total price for the contract. Offerors are advised that in order to demonstrate work commitment, each principal entity must be identified in Volume 4 Price and associated with a commensurate dollar value.

2. PROPOSAL FORMAT AND SUBMISSION

Proposals should be formatted using a Times New Roman 12 point normal font (no reduction permitted), single-spaced. The Offeror shall number all pages with volume, paragraph, and page numbers. If the Offeror uses Graphs to convey information, the graphs must show enough detail to understand the information described. The Offeror shall present graphs and tables in no smaller than a 10 pt. font.

2.1 Electronic Submission of Proposal

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 submissions, such as mail, hand-carried, or other electronic system (e.g., DOD SAFE or the Contracting Communication Module (CCM) within PIEE) are authorized by the solicitation. For instructions on how to post an offer to the Solicitation Module, 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.

The Government advises prime Offerors and their subcontractors to register the proper company points of contact in PIEE based on their CAGE codes with 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.

In the event of a PIEE System outage within 24 hours of the proposal due date that prevents the offeror from submitting a timely proposal, 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 Contractor shall have 24 hours to provide their proposal upon contracting officer approval. In the event the Contractor does not provide notification to the contracting officer until after the closing date and time, the contracting officer will follow the procedures identified in the Federal Acquisition Regulation (FAR) 15.208.

It is also the Offeror’s responsibility to confirm receipt of proposals and all electronic communications. Offerors should take screen shots of the submission to validate acceptance of the submission in the PIEE system for this solicitation. The Government is not obligated to search for incorrectly submitted proposals in PIEE. 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 solicitation. Offerors are responsible for submitting proposals, and any modifications or revisions, through the PIEE system by the date and time specified. While Offerors are encouraged to submit documents early, any submission, modification, or revision received through the PIEE system after the exact date and time specified is “late” and will not be evaluated or considered for award. The Government requests that Offerors submit Tables ES-1 and ES-2 from Volume 1, Executive Summary, Table PP-1 for all contract references from Volume 3-Past Performance, and Annex A, 14 calendar days prior to the submission date specified in Block 9 of the SF 33 of the solicitation.

2.1.1 Electronic Proposal Media

The Offeror shall submit all volumes of its proposal electronically and ensure compatibility with the operating system and applications defined in Section 2.1.2 below. The Offeror shall keep the portions of the proposal that contain pricing information separate from the portions of the proposal that do not contain pricing information. For this solicitation, Annex B (Small Business Subcontracting Plan), Attachment L-5, (Small Business Participation Commitment Document);

Volume 4 Price, Volume 5 Contract Administration, and Volume 6, Small Business, contain price information and shall be delivered in separate files from the remainder of the proposal.

The Offeror is responsible for ensuring electronic proposals are virus free in accordance with Section 2.1.4.

2.1.2 Operating System and Applications

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

2.1.3 Hyperlinks

The Offeror shall not use hyperlinks in proposal volumes.

2.1.4 Virus Free Electronic Submission

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

The Offeror should specify the software, version, and virus definition used/that will be used to check the data.

2.1.5 Multimedia

The Offeror should not embed sound or video (e.g., MPEG) files within the proposal submission or images in searchable PDF documents within the proposal submission. Government sourced documents may be excluded from being searchable.

2.1.6 File Naming Conventions

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

Table G-1 File Extensions

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

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

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

Table G-2 Offeror Electronic File Naming Convention

Volume Number

Title File naming convention Suggested Pages

1 Executive Summary Vol 1 ES#.docx 15 Table ES-1 Offeror Summary

Table ES-2 Relevant Contract Summary Vol 1 ES Tables.xlsx As Needed

2 Technical Vol 2 Tech#.docx 40* Technical Cross Reference Matrix Vol 2 Tech CRM.xlsx 3

3 Past Performance Vol 3 PP#.docx 25 Table PP-1 Past Performance Contract Data Vol 3 PP-1 PP Con Data.xlsx As Needed

Release of Adverse Past Performance Authorization Letters; and/or Past Performance Point of Contact Information

Rel Ad PP Ltr#.pdf; and/or PP POC Info#.docx

4 Price Vol 4 Cost-Price#.docx As Needed

Price Tables Vol 4 Matrix.xlsx CLIN Pricing Matrix Vol 4 Tier Pricing.xlsx

5 Contract Administration Vol 5 CA#.docx Table CA-1 Offeror Business Systems Status Vol 5 CA Tables.xlsx As Needed

6 Small Business Vol 6 SB#.docx Vol 6 SBPCD.docx

As Needed

Annexes Annex A Relevant Portions of Final Versions of

Previous SOO/SOW/PBWSs for Past Performance Relevancy and Past Performance

AnnA PPR#.pdf and AnnA PPR#.docx Please note: The Offeror should provide both a .pdf and .docx version if they are available. If not, a .pdf version only is acceptable.

As Needed

Annex B Small Business Subcontracting Plan Vol 6 SBSP.docx

Annex C DCAA/DCMA reports, audits, and determinations

Vol 5 DCMA_DCAA.docx

* Technical supporting documentation (e.g. OEM manuals and Airworthiness data) will not be included in the suggested page count.

3. PROPOSAL CONTENT AND VOLUMES

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

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

Table G-3 Section L List of Attachments

Section L Attachment

Electronic File Title Attachment Name

L-1 Vol 1 ES Tables Table ES-1 Offeror Summary and Table ES-2 Relevant Contract Summary

L-2 Vol 2 T-1 CRM Cross Reference Matrix

L-3 Vol 3 PPQ Past Performance Questionnaire

L-4 Vol 3 PP-1 PP Con Data Table PP-1 Past Performance Contract Data

L-5 Vol 6 SBPCD SBPCD L-6 Vol 4 Price Worksheet Price Worksheet L-7 Vol 2 PAO AW Checklist PAO and Airworthiness

Checklist L-8 Vol 4 HI Historical Information L-9 Vol 5 CA-1 Business System Status

4. PROPOSAL PACKAGING AND EARLY SUBMISSION:

4.1 PROPOSAL SUBMISSION

All Proposals shall be UNCLASSIFIED

The submission date for all Volumes of the proposal shall be no later than the date and time specified in Block 9 of Standard Form 33 of the solicitation. However, it is requested that one electronic copy of Table ES-1 (Offeror’s Summary), Table ES-2 (Relevant Contract Summary);

Table PP-1 (Past Performance Contract Data); and Annex A (Final Versions of Previous SOW/PWSs/Other Supporting Documentation for Past Performance) be submitted two weeks prior to the submission date/time specified on Standard Form 33 (Block 9).

In the official proposal submission, please indicate any changes made to the information delivered two weeks early in the submission provided on the date and time specified in Block 9 of Standard Form 33 of the solicitation. If no changes are made, please state so at the beginning of Volume 1 (Executive Summary), Volume 3 (Past Performance). Proposals shall be submitted in accordance with Block 9 on the SF33. Proposals shall be valid for 365 days from proposal due date.

5. SOLICITATION QUESTIONS

Questions regarding this solicitation shall be submitted via email to david.s.silverstone.civ@us.navy.mil and sheryl.m.pope.civ@us.navy.mil. 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 1200 Eastern Standard Time (EST) on 14th calendar day after the date that the solicitation is issued. The Government is under no obligation to try to answer questions received after that date, but may answer the question if time permits.

6. CHANGES TO SOLICITATION

The Government will post all amendments to this solicitation at https://www.sam.gov/. Search the database for the solicitation number N0042123R0064.

7. TECHNICAL LIBRARY

A Technical Library containing applicable documents related to this solicitation, N0042123R0064, is available to all Offerors intending to propose as a Prime Offeror. If required for proposal development, it is the Offeror’s responsibility to request access to, and ensure receipt of, the Technical Library by contacting the Contract Specialist, Ms. Sheryl Pope, sheryl.m.pope.civ@us.navy.mil and the PCO, Mr. Dave Silverstone, david.s.silverstone.civ@us.navy.mil. The data contained in the competition library is for informational purposes only. The Government does not guarantee the accuracy or completeness of the information.

PART B SPECIFIC INSTRUCTIONS

1. VOLUME 1 – EXECUTIVE SUMMARY

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

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

Attachment L-1 Executive Summary Tables (ES-1 (Offeror Summary) and ES-2 (Relevant Contract Summary))

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

a. Offeror Summary Table

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

(2) For the Past Performance evaluations, contract references that relate to a different CAGE code/UEI than the proposed entity 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 ES-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/ UEIs 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.

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

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

Table ES-1 Offeror Summary

Offeror:

Entity Name

Physical Location of Entity

CAGE

Codes/UEI

Roles and Responsibilities with Work Description

Workshare - % Total Proposed Price

Principal Entity Yes or No?

Total Proposed Price (must add up to 100%) 100%

b. Relevant Contract Summary Table

The Offeror shall complete the Table ES-2 (Relevant Contract Summary) provided in Attachment L-1 (Executive Summary Tables), for all proposed Past Performance contract references for each principle entity. The Offeror shall complete the table according to the instructions within the attachment and submit it within this section and as a separate electronic file. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing Volume 3 Table PP-1 (Past Performance Contract Data). For example, the contracts identified as P1, T1, S1, or C1 in the Relevant Contract Summary Table are the same P1, T1, S1, or C1 contracts identified in the Past Performance Contract Data Table.

Table ES-2 Relevant Contract Summary for Past Performance

Offeror:

Entity Name

Contract Reference

Type

Contract Title

*Description of Changes/Additions from

Early Information

Prime or Joint Venture Company

P1

P2

P3

JV team member A (where applicable)

T1

T2

T3

T4

JV team member N (where applicable)

T5

Subcontractor A

S1

S2

S3

Subcontractor B S4

S5

* Contracts deleted should be identified in a narrative paragraph following Table ES-2.

c. Technical

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

d. Contract Administration The Offeror shall provide a summary of any exceptions or deviations, and proposed Section H clauses addressed in Volume 5 (Contract Administration).

2. VOLUME 2 - TECHNICAL

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

for this volume:

Attachment L-2 Volume 2 Table T-1 Cross Reference Matrix (CRM) Attachment L-7 Vol 2 PAO and Airworthiness Checklist

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

Table T-1 Cross Reference Matrix

Section L – Proposal

Instruction s Volume or Paragraph Numbers

Section L - Proposal

Instructions Volume or

Paragraph Title

RFP

Sections (e.g.

Sections F, H, and M)

SOO/SOW/

PWS

CLIN Offerors Proposal Reference

Volume 2 Technical

2.1 Capability Stand-

up

M Part B, 2.0 Technical

3.5 0001, 0004

2.2 Aircraft

Performance Requirements

M Part B, 2.0 Technical

3.2, 3.3 0003, 0006

2.3 Airworthiness

Data

M Part B, 2.0 Technical

3.6 0001, 0004

2.4 Aircraft

Operations and Support

M Part B, 2.0 Technical

3.2.1,3.3.1,3.6, 4.1, 4.6

0002, 0003, 0005, 0006, 0013

In this volume, provide the information described below:

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

The Offeror shall use the assumed contract award date referenced below in provision LTXT.215- 9503 when developing integrated schedules and plans required throughout this volume.

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

2.1 Capability Stand-Up

2.1.1 Offeror shall provide a list of proposed aircraft by Type/Model/Series (T/M/S) and serial number.

2.1.2 Aircraft Ownership: The Offeror shall submit proof of ownership or signed lease agreements by serial number at time of proposal submission. Each aircraft must be located in the United States and capable of flying at the end of the capability standup period.

2.1.3 Regeneration Plan: For aircraft which are not currently airworthy, the Offeror shall submit a plan that starts at the assumed contract award date detailing the efforts required to bring the aircraft into an airworthy status. The plan shall include an integrated schedule and shall specify the organizations performing the work. A current and effective, FAA issued, airworthiness certificate can meet this requirement.

2.1.4 Aircraft modification plan: For each aircraft proposed that requires modification to meet the performance requirements of PBWS paragraphs 3.2 and 3.3, the Offeror shall submit a plan detailing the modifications required to bring the aircraft into compliance. Plans shall include all significant modifications required, major milestones, organization performing the modification(s), source of data supporting the modification(s) and airworthiness certification authority. Any modifications currently in-process or otherwise planned prior to the initiation of the contract shall be included.

2.1.5 Master Schedule to achieve Full Operational Capability: The Offeror shall submit a proposed master schedule for completion of all stand-up requirements, including the date that they will be able to provide full performance of services under CLINs 0003 and 0006 including availability of all aircraft for tasking. The offeror shall include a minimum of 45 days for Government processing of NAVAIR IFC(s) after the IFC Data package has been received under CDRL A001. The schedule shall contain, at a minimum, the milestones provided in PBWS paragraph 3.5.4 and all other significant events required to obtain full FOC, such as the completion of aircraft modifications including, but not limited to, providers, submission of IFC data package under CDRL A001, assets transportation, completion of stand-up of the maintenance organizations, completion of aircrew hiring, required training completion, all data requirements listed in the Airworthiness checklist. The schedule shall contain milestones for drafting Ground and Flight Operating Procedures (GOPS/FOPS) in accordance with 8210.1D and allow 30 days for government approval after submission. The Offeror shall submit a draft of the Integrated Master Schedule (CDRL A007) as part of their proposal for CLINs 0001 and 0004.

2.2 Aircraft Performance Requirements

For each T/M/S aircraft proposed for use on this contract, the Offeror shall substantiate how the aircraft will meet the performance requirements described in PBWS paragraphs 3.2 and 3.3.

Each aircraft proposed, after any modifications shall meet or exceed the performance requirements specified in the PBWS. Supporting data (published performance data, flight manuals, etc.) shall be submitted to substantiate how the aircraft meets the performance requirements. Complete flight manuals are requested if available electronically.

Note: If any supporting data is in a language other than English, the salient portions of the data needed to evaluate the aircraft performance characteristics must include with it, an English translation of the appropriate pages, and documentation of the method of translation including the qualifications of the translator.

2.3 Airworthiness Data: The Offeror shall provide the following documentation.

Note: Offerors are advised that a number of factors can affect the time and potential for offerors to receive a NAVAIR issued IFC. Factors include but are not limited to: aircraft type, aircraft pedigree, prior aircraft modifications, aircraft maintenance, prior aircraft certifications, proposed modifications and quality of engineering substantiation data.

2.3.1 The Offeror shall complete attachment L-7 Airworthiness Checklist detailing status of the documentation which will be required as part of the NAVAIR IFC process and submit it as a separate electronic file for each aircraft proposed. Provide explanation of missing data along with specific details as part of response to paragraph 2.3.1. This requirement can be satisfied by submitting an existing, active, NAVAIR IFC, United States Air Force (USAF) Military Flight Release (MFR), or United States Army Airworthiness Release (AWR), if the aircraft can satisfy the requirements of this solicitation within the limits of the submitted IFC, MFR, or AWR.

2.3.2 Maintenance History Report: This requirement can be satisfied by submitting an existing active NAVAIR IFC, USAF MFR, or US Army AWR, if the aircraft can satisfy the requirements of this solicitation within the limits of the submitted IFC, MFR, or AWR.

2.3.2.1 The Offeror shall provide, for each aircraft proposed, an accounting for the timeframe from manufacture to proposal submittal date that the aircraft has been maintained in accordance with the requirements established by the OEM, prior military user(s), or (as appropriate) civil authorities. The Offeror shall provide a list of documentation, and be able to provide if required, all data and records supporting the accounting of maintenance.

2.3.2.2 The Offeror shall include for each individual aircraft a description of the process and method used by the Offeror to establish the aircraft's maintenance history prior to taking possession of the aircraft.

2.3.2.3 The Offeror shall identify and explain any lapses in the documented maintenance history of any individual aircraft, from the time it was manufactured to the present.

2.3.3 Fatigue Life Status report:

2.3.3.1 The Offeror shall include for each aircraft type proposed, the OEM's structural fatigue life limits.

2.3.3.2 The Offeror shall provide for each individual aircraft: (a) the current total counts on tracked items (e.g. flight hours/catapults/landings) that have been accumulated since the aircraft was manufactured, and (b) the means used to determine the current accumulated counts since the aircraft was manufactured.

2.3.3.3 The Offeror shall demonstrate all proposed aircraft have the remaining fatigue life to allow the aircraft to be safely operated throughout the four-year and 364-day ordering period of the contract, based on projected combined aircraft usage rates as described in Section B, CLINs 0003 and 0006.

2.4 Aircraft Operations and Support:

2.4.1 Aircraft Maintenance Strategy: The Offeror shall provide an explanation of its maintenance organization and strategy for conducting both scheduled and unscheduled aircraft maintenance to meet the effectiveness metric described in the QASP (Section J Attachment 2).

Documentation of executed sub-contracting or teaming agreements (e.g. copies of executed agreements) shall be provided for substantiation where applicable

2.4.1.1. The Offeror shall explain how they plan to meet 14 CFR § 91.409(f) and also include discussion on how airworthiness will be maintained for configuration changes required for CAO and PAO flights.

2.4.1.2 The Offeror shall include a discussion of managing airframe usage and availability for all aircraft types proposed to enable efficient coverage of hours projected by type. The Offeror shall describe its method of ensuring pilot and aircrew availability to ensure it will be capable of conducting the missions to include a description of its strategy for pilot and maintainer retention.

2.4.2 Aircraft Logistical Strategy: The Offeror shall provide its proposed logistical strategy for supporting each proposed T/M/S. Documentation of executed sub-contracting or teaming agreements (e.g. copies of executed agreements,) shall be provided for substantiation where applicable.

2.4.2.1 For each proposed T/M/S, the Offeror shall provide its proposed source of OEM, Federal Aviation Administration (FAA) or equivalent certified parts.

2.4.2.2 For each proposed T/M/S, the Offeror shall provide its proposed source of OEM, FAA or equivalent certified maintenance and engineering data.

3. VOLUME 3 - 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-3 Past Performance Questionnaire (PPQ) Attachment L-4 Past Performance Contract Data (PP-1

For this volume, the Offeror shall identify all relevant contracts (where for the purpose of these instructions the term contract also refers to delivery order or task order), or those portions of a relevant contract, whose performance is within three years of the proposal due date for the principal entities, identified in Table ES-1 (Offeror Summary). The relevant contracts provided for each principal entity shall be relative to its proposed role and responsibilities identified in Table ES-1 (Offeror Summary). Commercial contracts may be included. Offerors shall also identify relevant contracts within the past three years of the RFP release date that had any show-cause notices, cure notices, or termination for default. The Offeror shall complete Table ES-2 (Relevant Contract Summary for Past Performance) provided in Attachment L-1 (Executive Summary Tables), for all contracts proposed as relevant for Past Performance.

In Annex A (Final Versions of Previous Statement of Work (SOW)/Performance Work Statement (PWS)/Other Supporting Documentation for Past Performance), the Offeror shall provide electronic copies of the complete final versions of the SOW/PWS or other supporting solicitation/contract documentation from each contract or delivery/task order reference identified in Table ES-2 (Relevant Contract Summary). Annex A should only be provided in electronic format and should not be provided in paper copy. For contract references that contain delivery/task orders, additionally provide the work description for each specific delivery/task order. For contract references where the Offeror performed as a subcontractor, the Offeror shall also provide a complete electronic copy of the SOW/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 performed as a subcontractor.

Contract Performance Assessment Reporting System (CPARS) and Questionnaires will be the primary customer feedback data used to evaluate the Offeror’s past performance. www.cpars.gov will be the primary method used to retrieve the CPARS for this source selection. For all contracts identified that do not have a CPARS, the Offeror shall forward a copy of Attachment L-3 Past

Performance Questionnaire to that contract’s Procuring Contracting Office (PCO), Administrative Contracting Officer (ACO), and Program Manager (PM); or commercial contractor equivalents. Please forward all questionnaires within two weeks from this solicitation’s release date to allow adequate time for the recipient to respond. Note that the Offeror should not reference this solicitation’s number when distributing the past performance questionnaires to customers. The Offeror should include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to the PCO/Contract Specialist, identified in 4.1 (Proposal Submission). The Offeror shall ensure that all points of contact are current and include an email address and phone number. The Offeror shall not conduct follow-up actions with regard to this questionnaire, other than to confirm receipt by the recipient. The Government may contact customers identified by the Offeror to obtain follow-up Past Performance Information as needed.

Offerors are reminded that the Government reserves the right to use information to evaluate past performance obtained from sources other than those identified by the Offeror. The Government may send additional questionnaires and/or obtain information from sources identified by the Government evaluation team.

3.1 Authorization Letter(s)

The Offeror should submit a signed “Release of Adverse Past Performance Authorization Letter(s)” with written consent from each principal entity (including JV team members), authorizing the release of adverse past performance information to the Prime. The signed letter(s) should be included in a separate tab within 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 Adverse 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 Offeror will forfeit the opportunity to participate in any related discussions.

3.2 Contract Reference Data

For each contract identified for past performance in Table ES-2 (Relevant Contract Summary) provided in Attachment L-1 (Executive Summary Tables), the Offeror shall complete Attachment L-4 Table PP-1 (Past Performance Contract Data), according to the instructions within the attachment and submit it within this section and as a separate electronic file. Please note that this form is a summary of the principal entities’ contract reference data. All detailed information and comparative analysis of the past performance contract references to this solicitation’s requirements shall be provided in Volume 3 (Past Performance), Section 3.3 (Evaluation), of the Offeror’s proposal. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing Volume 3 (Past Performance) and all contract references shall be numbered the same throughout all of the Offeror’s proposal volumes (i.e., the contracts identified as P1, S1, T1, C1 etc.)

If a contract has D.O.s/T.O.s, provide a separate contract reference and separate PP-1 tab for each D.O/T.O. The Offeror may use one reference number/PP-1 tab for multiple D.O.s/T.Os if they are the same work effort and performed under the same CPAR; however, identify the dollar amount and period of performance for each. Do not provide a contract reference to the basic contract.

In general, recent performance will be considered a better indicator of future performance. If the Offeror is proposing as a JV, the Offeror should provide the relevant contracts for the JV as a whole, and for each team member of the JV.

Table PP-1 Past Performance Contract Data

Offeror Name:

1 Entity Name

2 Contract Reference

3 Title of Contract

4 Contract Number

5 Contract Type

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

11 CAGE Code (if not the same as Offeror, explain)

Dollar value of contract (Total) Dollar value of contract (Annualized)

Brief Work Description and/or Program Responsibility for this past contract

a. PWS/SOW paragraphs from contract reference associated with: (SCOPE) (1) Contracted Air Services involving Contractor provided high performance turbo fan or turbo jet aircraft employing Fighter Tactics, Electronic Warfare Missions, or Contracted Close Air Support (CCAS) (2) Contracted Air Services involving Contractor provided high performance turbo fan or turbo jet aircraft supporting multiple sorties a day.

b. PWS/SOW paragraphs from contract reference associated with: (Complexity) (1) Providing Aircraft Basing and Maintenance Support involving Operations, logistics, and maintenance in support of Sortie Generation and Execution (2) Obtaining FAA Airworthiness Certificate or Military Airworthiness Authorities for high performance turbo fan or turbo jet aircraft and Maintaining Continuing Airworthiness of high performance turbo fan or turbo jet aircraft.

c. PWS/SOW paragraphs from contract reference associated with: (Magnitude) Contract total value of greater than $5.0 M, or annual task order value greater than $1.0 M.

14 Date of last completed CPARs

15 Date past performance questionnaires were sent

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

Gov't PCO or Commercial Purchasing Agent

Name:

Phone:

Email:

Gov't ACO

Name:

Gov't PM or Commercial PM

Other:

Title:

Phone:

Email:

3.3 Evaluation

The burden of providing thorough and complete past performance and systemic improvement information remains with the Offeror.

For each contract reference identified in Attachment L-4 Table PP-1 (Past Performance Contract Data), the Offeror shall provide contract data regarding relevancy, past performance information, and demonstrated systemic improvement, as described below, organized by contract reference.

As this information is presented in the proposal, demonstrate the relevancy of the principal entities past performance with respect to this solicitation’s requirements. For any contract references where the principal entities are aware of problems, the Offeror shall describe the issues in section 3.3.b (Past Performance Information). For each past performance problem identified, describe the status of the systemic improvement efforts in section 3.3.c (Demonstrated Systemic Improvement).

a. Relevancy: Offerors are required to explain what aspects of the referenced contracts are deemed relevant, as defined by Section M, to this solicitation’s requirements. To demonstrate relevancy, Offerors shall provide a comparative analysis to the scope, magnitude, and complexity or similarity of this solicitation’s requirements. Within the comparative analysis, Offerors should identify the relevant portions (sections, paragraphs, and page numbers) of the referenced contract’s SOW/PWS (Annex A) to clearly identify how past efforts performed are similar to this solicitation’s requirements. In addition, the referenced sections only need to be identified and the full text does not need to be broken out separately from the complete SOW/PWS.

The reference contract(s) provided should be relative to each principal entity’s proposed role/responsibility identified in Table ES-1 (Offeror Summary) versus relative to the whole solicitation.

For a discussion on CAGE Code/UEI, refer to section 1.0 Volume 1 (Executive Summary).

Offerors should be advised that the CAGE Code/UEI for each referenced contract is considered as part of the Relevancy determination, which determines if the contract reference will be included in the Past Performance evaluations.

Note: Any information regarding CAGE Code/UEI should be included within Volume 1 (Executive Summary) and does not need to be repeated here.

Offerors are advised that contracts assessed as not relevant by the Government will not be considered in the Past Performance assessments.

b. Past Performance Information: The Offerors shall provide a brief description of past performance in delivering quality services. Include in these descriptions any information that demonstrates the level of performance obtained, where available; provide quantifiable measures/trends to demonstrate past and current performance. Also describe past problems, including when they occurred, what the circumstances were surrounding the situation, and what the consequences were as a result of the problem.

c. Demonstrated Systemic Improvement: Identify systemic improvement actions taken to resolve any past problems identified in 3.3.b (Past Performance Information). Provide the records of such results and indicate where they are documented, preferably in Government record systems. Describe the techniques, elements, and tools used to correct problems on the reference contract and, if applicable, how these techniques, elements, and tools may be used for the contract to be awarded as the result of this solicitation. Provide quantifiable evidence or metrics that substantiate or demonstrate claims of improvement and to demonstrate that the past problem will not occur on the contract to be awarded as the result of this solicitation. It is incumbent upon the Offeror to explain the relevance of the data provided and substantiate that improvements from past performance problems are being made. The Government does not assume the duty to search for data to cure the problems it finds in the information provided by the Offeror. Consideration for discounting problems may be given when those problems are addressed through demonstrated systemic improvement. Demonstrated systemic improvement may be indicated by information as it relates to preventing recurrence of past problems, including: identification of the root cause of a problem, a corrective action plan that systemically addresses the past problem, how and when the plan was implemented, documented timeframe to demonstrate when corrective action was implemented and became successful; and performance data, preferably through Government records, to show performance improvements. With regard to performance improvement data, explain the likelihood to which the problem will not reoccur on during the performance of this prospective contract based on the amount of time that good performance was sustained in consideration of the nature of the past problem and effort.

4. VOLUME 4 – PRICE

for this volume:

Attachment L-6 Price Worksheet Attachment L-8 Historical Information

4.1 Price…