CUI

Pacific Missile Range Facility (PMRF) Helicopter Services

N0042126R0002

SECTION L; INSTRUCTIONS, CONDITIONS,

AND NOTICES TO OFFERORS

Naval Air Systems Command (NAVAIR) Program Manager, Adversary and Specialized Aircraft (PMA-226)

Contracted Air Services (CAS)

29 June 2026

Controlled by: PMA-226 CUI Category: SSEL Distribution Statement: D POC: Shane Dalpiaz, shane.m.dalpiaz.civ@us.navy.mil

Distribution Statement D: Distribution authorized to the Department of Defense and U.S. DoD contractors only (SSEL) (29 June 2026). Other requests for this document must be referred to PMA-226.

PART A GENERAL INSTRUCTIONS

1. GENERAL

Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to 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 with a clear understanding of the Offeror’s approach, expertise, experience, and capability as required by the solicitation. All proposals must clearly demonstrate that the Offeror has a thorough understanding of all requirements and associated risks; is able, willing, and capable of devoting the resources necessary to meet all requirements; and has valid and practical solutions for all requirements and potential risk areas. The Offeror shall not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. The Government advises Offerors 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. THE GOVERNMENT ADVISES THE OFFEROR THAT NO ALTERNATE PROPOSALS WILL BE CONSIDERED. Cost/Price information, (e.g., dollar values and/or hourly rates) shall appear only in Volume 1 (Contract Administration), Volume 4 (Price), and Volume 5 (Small Business). Offerors shall ensure that price files remain separate from the rest of the proposal files. If the Government conducts a pre-award site survey or material condition inspection, as discussed in Section L, paragraph 2.0, the results of the pre-award site survey or material condition inspection may be included in the evaluation of the Technical Elements. If the Government contacts the previous airworthiness certification authority, any information obtained may be included in the evaluation of the technical factor.

In presenting material in the proposal, the Offeror should emphasize clarity, brevity, and logical organization in its proposal and understand that quality of information is more important than quantity.

It is the responsibility of the Offeror to present enough information to allow the Government to evaluate its proposal without discussions.

However, the Government reserves the right to conduct discussions if the Contracting Officer later determines them to be necessary. Unsubstantiated statements that the prospective Offeror understands, can or will comply with the specifications, or paraphrasing the requirements or parts thereof are 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 Offeror shall include detailed information in the most logical place and use a summary or reference to 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.

This solicitation and the resulting contract require the contractor to achieve and maintain Cybersecurity Maturity Model Certification (CMMC) current status for the full duration of the contract performance.

The CMMC requirements are specified in DFARS Clause 252.204-7021, Cybersecurity Maturity Model Certification Requirement. The Government's verification of the offeror's CMMC status is a part of the responsibility determination. An offeror that does not have a current status at the level required by paragraph (d)(1) of DFARS 252.204-7021 (as set forth in DPC Deviation at Part 240, see

DARS Tracking Number: 2026-O0025) in the DoD's Supplier Performance Risk System (SPRS) will be considered ineligible for award.

Throughout these instructions, the “Offeror” is the Prime Contractor with its Commercial and Government Entity (CAGE) code identified in Block 15A on Standard Form (SF)-33, Solicitation, Offer, and Award. For purposes of this evaluation, the Prime Contractor is the Principal Entity. The Government will only use contract references from the Principal Entity in the Past Performance evaluations.

2. PROPOSAL FORMAT AND SUBMISSION

Offerors shall format all proposals 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 Times New Roman 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) are authorized by the solicitation unless specifically authorized by the Contracting Officer pursuant to the paragraphs regarding PIEE System outages 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.

It is the Offeror’s responsibility to follow the registration instructions found on the PIEE website. The Government advises Offerors to register the proper company points of contact in PIEE based on their CAGE codes and that the proper roles are assigned well in advance of the solicitation closing date. 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 Request for Proposal (RFP). Offerors are responsible for submitting proposals, and any modifications or revisions, to reach the Government office designated in this solicitation by the date and time specified. While Offerors are encouraged to submit documents early, any submission, modification, or revision received at the Government office after the exact date and time specified is “late” and will not be evaluated or considered for award. In the event there is acceptable evidence to establish that the submission, and any modifications or revisions were received at the Government installation designated for receipt of offers and was under the Government’s control prior to the date and time set for receipt of offers, the Procuring Contracting Officer (PCO) will accept the submission.

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 should keep the portions of the proposal that contain pricing information separate from the portions of the proposal that do not contain pricing information. 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 Government uses Microsoft Windows 11 Operating System to access proposals. Offerors shall submit proposal information using Microsoft 365 applications. However, Offerors shall submit letters and other signed documents as a fully searchable Portable Document Format (.pdf) file. Use of other application software for submission of proposals is prohibited.

2.1.3 Hyperlinks

The Offeror shall not use hyperlinks in proposal volumes.

2.1.4 Virus Free Electronic Submission

The Offeror is 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) are virus-free. The Offeror shall specify the software, version, and virus definition used to check the data.

2.1.5 Multimedia

To reduce file sizes, the Offeror shall not embed sound or video (e.g., MPEG) files within the proposal submission. The Offeror is encouraged to simplify the color palette used in creating figures; and minimize size of graphics files; and avoid scanned images.

2.1.6 File Naming Conventions

Valid extensions for files using their associated applications follow:

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-1 (Offeror Electronic File Naming Convention) for electronic file submissions (e.g., proposal volumes, attachments, appendices), where “#” represents the sequential numbering of files. Offerors shall keep file names short (i.e., under 40 characters) so that the files are accessible on Government share drives.

Files with longer names often 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, or annex as one file if possible.

Offerors should not provide each section/paragraph as separate files.

Table G-1 Proposal Structure

Volume Number Title File naming convention Suggested

Pages 1 Contract Administration Vol 1 CA#.docx 20

CA-1 Offeror Business Systems Status CA-2 Relevant Contract Summary Vol 1 CA Tables.xlsx As Needed

2 Technical Vol 2 Tech#.docx 25 T-1 Technical Cross Reference Matrix Vol 2 CRM.xlsx 2

3 Past Performance Vol 3 PP#.PDF and Vol 3 2 PP#.docx 25

Table PP-1 Past Performance Contract Data

Vol 3 Con Data.PDF and Vol 32 PP-1 Con Data.xlsx As Needed

Past Performance Questionnaire Vol 2 PPQ#.pdf As Needed 4 Price Vol 4 Price#.docx As Needed CP-1 Pricing Sheet Vol 4 CP Tables.xlsx As Needed

5 Small Business Vol 5 SBPCD.docx Vol 5 SBSP.docx As Needed

Annexes

Annex A Final Versions of Previous SOO/SOW/PBWSs/Other Supporting Documentation for Past Performance

AnnA PPR#.pdf or AnnA PPR#.docx Please note: The Offeror shall provide a .pdf or .docx versions of the documents.

As Needed

Annex B Technical Volume Supplementary Information

AnnB TechDocs.pdf or AnnB TechDocs.docx As Needed

3. PROPOSAL CONTENT AND VOLUMES

The Offeror shall present its proposal information in a manner that facilitates a one-for-one comparison between the information presented and these proposal instructions. Offerors shall structure proposal information such that the proposal 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 Section B Specific Instructions and do not count towards the suggested page count.

Table G-2 Section L List of Attachments

Section L Attachment Number

Electronic File Title Attachment Name

L-TL Technical Library TL

L-1 Contract Administration Tables, CA-1 (Offeror Business System Status) and CA-2 (Relevant Contract Summary)

CA-1 & CA-2

L-2 Technical Cross Reference Matrix T-1 L-3 Airworthiness Checklist AWCL L-4 Past Performance Contract Data PP-1

L-5 Past Performance Questionnaire PPQ

L-6 Price Tables, CP-1 (Pricing Sheet) CP-1

L-7 Small Business Participation Commitment Document

(SBPCD) SBPCD

4. PROPOSAL SUBMISSION AND PACKAGING

All Proposals shall be UNCLASSIFIED.

The submission date for all volumes shall be no later than the date and time specified in Block 9 of Standard Form 33 of the solicitation. The Government requests that Offerors submit Tables CA-1, and CA-2 from Volume 1, Contract Administration, Table PP-1 for all contract references from Volume 3- Past Performance, and Annex A, 14 calendar days prior to the submission date/time specified on Standard Form 33 (Block 9). Offerors shall indicate any changes made to the information delivered early in the final submission provided on the date and time specified in Block 9 of Standard Form 33 of the solicitation. If the Offeror does not make any changes form the advance submittal, please state so at the beginning of Volume 1 Contract Administration and Volume 2 Past Performance.

Method of delivery, such as by hand, United States Postal Service or commercial carrier, are not authorized. Offerors will follow the directions for electronic submittal identified in paragraph 2.1.

5. CHANGES TO SOLICITATION

The Government will post all amendments to this solicitation at https://www.sam.gov/

Search the database for the solicitation number N0042126R0002.

6. Technical Library

A CAS PMRF Helicopters Technical Library of information directly related to the requirements of the N0042126R0002 solicitation is available to all Offerors intending to propose as a Prime Offeror.

Offerors can access the Technical Library under PIEE (Attachment L-TL).

PART B SPECIFIC INSTRUCTIONS

1. VOLUME 1 – CONTRACT ADMINISTRATION

Prerequisite:

a. Aircraft Ownership and/or Leasing Documentation

The Offeror shall provide proof of ownership and/or leasing documentation for all proposed Sikorsky H-3 variant aircraft by Type/Model/Series (T/M/S) and serial number for this solicitation.

Proof of ownership information by Type/Model/Series (T/M/S) and serial number(s) for solicitation and compliance of this prerequisite.

b. Facility Clearance

The Offer shall provide proof that it has a facility security clearance at a minimum level of secret.

c. Air Mobility Command Carrier Air Review Board Certification (CARB)

The offer shall provide proof that they have an approved CARB for their company and the Sikorsky H-3 variant aircraft that are providing in support of this solicitation and compliance of this prerequisite

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

Attachment L-1 Contract Administration Tables, CA-1 (Offeror Business System Status), and CA-

2 (Relevant Contract Summary)

The Offeror shall divide the Contract Administration Volume into the sections outlined below:

a. Prerequisite:

• Aircraft Ownership and/or Leasing Documentation

• Facility Clearance

• CARB Certification

b. Offeror Business Systems Status

The Offeror shall complete Table CA-1 (Offeror Business Systems Status) showing the status and or determinations regarding its business systems. The Offeror shall indicate the most recent date that the Offeror’s cognizant Defense Contract Management Agency (DCMA)/ Defense Contract Audit Agency (DCAA) determined the adequacy of the Offeror’s systems (including but not limited to Accounting, Property, and Purchasing). If any item is not applicable to the Offeror or for contract performance, state and justify.

In the event the status of an Offeror’s system is not adequate, list the date of the last adequacy determination and the status of any systems reviews or ongoing audits. If any system was unapproved or deemed inadequate, outline the potential impact on contract execution, mitigation plan, and correction plan.

Table CA-1 Offeror Business Systems Status

Business System (D)FAR Reference Status Comments Accounting System 16.301-3 Estimating System 215.305 CAS Disclosure Statements 30.301 Purchasing System 44.3 Property Management System 45.105 CMMC (Level 2–Self or C3PAO) 204-7019/7020/7021/7024/7025

d. Relevant Contract Summary The Offeror shall complete Table CA-2 (Relevant Contract Summary) to delineate all contract references that relate to the Prime Contractor for Past Performance.

For this solicitation, contract references shall relate to the same CAGE code/ Unique Entity Identifier (UEI) as the proposed entity. The Offeror shall explain any contract reference that relates to different CAGE code/UEI than the proposed entity. Explanation of why a different CAGE code/UEI is appropriate for inclusion in the evaluation is required. Please describe if the discrepancy in the CAGE code/UEI is a result of a corporate acquisition, reorganization, merger, or other administrative reasons and explain how the changes impact the contract references provided.

Table CA-2 Relevant Contract Summary

Offeror:

Entity Name Contract

Reference Number*

Contract Number

Contract Title

List any Changes/Additions from Early Information

Prime P1 P2 P3

*Add rows as needed to list all similar contracts

e. Offeror Representatives and Information

Provide the name, title, phone number and email address of the Offeror’s principal point of contact for the solicitation. In addition, the Offeror shall identify those individuals authorized to negotiate with the Government and contractually bind the Offeror. The Offeror shall provide its company/division’s street address, county and facility code; CAGE code; UEI; size of business (large or small); and labor surplus area designation.

f. Government Agency Information

Provide the mailing address, telephone, fax numbers, email address and facility codes for the Offeror’s cognizant Contract Administration Office, DCAA, and Government Paying Office. In addition, please provide the name, telephone number, fax number and email address for the Administrative Contracting Officer (ACO) at the DCMA.

g. Model Contract Documents:

1. Original signed SF33 (Solicitation, Offer, and Award) cover page of the solicitation and a signed

SF-30 cover page of each amendment (as applicable) with all applicable Blocks completed and acknowledgement of receipt of each amendment (as applicable) to this solicitation. The SF-33 Block 12 “fill-in” (proposal validity date) shall be completed in accordance with (IAW) Section A (Solicitation/Contract Form);

2. Signed Representations, Certifications, and Acknowledgements or System for Award Management (SAM) reference;

3. Section B with proposed pricing;

4. A completed copy of all Federal Acquisition Regulation (FAR), Defense Federal Acquisition Regulation Supplement (DFARS), Naval Air Systems Command (NAVAIR), and special clauses and provisions requiring contractor fill-ins.

h. Terms and Conditions:

Submission of a signed offer to the Government constitutes agreement and acceptance of the terms and conditions of the solicitation in a FFP contracting environment.

An exception to the terms and conditions or proposed deviation is a deficiency. A deficiency renders the Offeror’s proposal unawardable. An exception occurs if/when an Offeror states it will not comply with a solicitation requirement, usually involving contract terms and conditions. A deviation is where an Offeror states it will not comply with a solicitation requirement but proposes an alternative to meet the intent of the requirement, usually but not exclusively, involving a PWS requirement.

2. VOLUME 2 - TECHNICAL

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

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

Attachment L-2 T-1 Cross Reference Matrix (CRM) Attachment L-3 Airworthiness Checklist

A CRM, Table T-1, is included to help the Offeror develop its proposal and to ensure traceability of Section L paragraphs to the requirements. The Offeror’s CRM may be identical to the one provided or revised to add information. For example, the Offeror’s 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. Include the Table T-1 Cross Reference Matrix at the beginning of Volume 2 Technical.

Table T-1 Example Cross Reference Matrix

Section L – Proposal

Instructions Volume or Paragraph Numbers

Section L - Proposal Instructions Volume or Paragraph Title

RFP Sections (e.g. Sections F, H, and M)

PWS CLIN

Offeror Proposal

Reference

Volume 2 Technical

2.1 Capability Stand Up Section M, Part

II, A. Technical 3.2 0001

2.2 Aircraft Performance

Requirements

Section M, Part II, A. Technical 3.1 0002, 0003, 0004

2.3 Hoist Capability

Requirements

Section M, Part II, A. Technical 3.1 0002, 0003, 0004

2.4 Airworthiness Data Section M, Part

II, A. Technical 3.4 0007

2.5 Aircraft Support Section M, Part

II, A. Technical 4.0 0002, 0003, 0004

2.6 Aircraft Availability Section M, Part

II, A. Technical 4.0 0002, 0003, 0004

Throughout the Technical Volume, the Offeror shall 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 shall also identify 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. All technical proposals shall address each of the following elements:

2.1 Capability Stand Up

2.1.1 Regeneration Plan

For proposed aircraft which are not currently airworthy, the Offeror shall submit a plan detailing the efforts required to bring the aircraft into flyable status. The plan shall include an integrated schedule and shall specify the organization(s) performing the work.

2.1.2 Aircraft Modification Plan

For each aircraft proposed that requires modification to meet the performance requirements of PWS paragraph 3.1, 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(s) performing the modification(s), source of data supporting the modification(s) and airworthiness certification authority.

2.1.3. Integrated Master Schedule (IMS) to achieve Capability Stand Up per PWS Section 3.2

The Offeror shall submit a proposed master schedule using Microsoft Project .mpp format for completion of all stand up requirements, including the date that they will be able to provide full performance of services under CLINs 0002 through 0004 including availability of all aircraft for tasking. The Offeror shall include a minimum of 30 days for Government processing of NAVAIR IFC(s) (If applicable). The schedule shall contain, at a minimum, the milestones provided in PWS paragraph 3.2.1 and all other significant events required to obtain Capability Stand Up, such as aircraft acquisition events (customs, delivery, contract dates), completion of aircraft modifications including providers, submission of IFC data package (if applicable) (see Attachment L-3 Airworthiness Checklist), assets transportation, completion of stand up of the maintenance organizations, completion of aircrew hiring, required training completion, any data requirements listed in Attachment L-3 Airworthiness Checklist, etc. The Offeror shall submit a draft of the IMS as part of their proposal.

2.1.3.1 Three (3) Months to full stand-up capability

Aircraft shall be fully operational no later than three (3) months from award of the contract. The offeror shall provide a schedule for meeting this three (3) months or less for full stand-up capability.

The offeror may propose less than 3 months for full stand-up capability.

2.1.3.2. Ground and Flight Operating Procedures (GOPS/FOPS) (IF APPLICABLE)

If the Offeror has existing Government- approved GOPs and FOPs, the Offeror shall submit a plan detailing the schedule and milestones for updating existing Government approved GOPs and FOPs to meet the requirements of this effort. When no approved GOPs/FOPs exist, the Offeror shall submit its plan for the development and approval of GOPS/FOPS for this effort.

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 PWS Table 3.1.1 and 3.1.2. Each aircraft proposed, after any modifications, shall meet or exceed the performance requirements specified in the PWS. Supporting data (published performance data, flight manuals, etc.) shall be submitted electronically to clearly substantiate how the aircraft meets the performance requirements.

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.

The Offeror shall submit a Performance Requirements table for the Technical Volume by completing the below Table T-2.. A separate table for each TMS of aircraft proposed for this effort shall be provided (the proposed aircraft must meet or exceed all performance requirements as stated in PWS Table 3.1.1 and 3.1.2).

Table T-2 Performance Requirements

MEDIUM LIFT - PERFORMANCE REQUIREMENTS

Speed/Altitude:

Service Ceiling:

Service Radius:

Time On Station:

Configuration/ Special Equipment:

Substitution of Aircraft:

Hoisting Capability:

External Lifting Capacity:

Internal Capacity:

HEAVY LIFT - PERFORMANCE REQUIREMENTS

Speed/Altitude:

Service Ceiling:

Service Radius:

Time On Station:

Configuration/ Special Equipment:

Substitution of Aircraft:

Hoisting Capability:

External Lifting Capacity:

Internal Capacity:

2.3 Hoist Capability Requirements

For each T/M/S aircraft proposed for use on this contract, the Offeror shall substantiate how the aircraft’s hoist system will meet the performance requirements described in PWS paragraphs 3.1.1 and

3.1.2. Each hoist for the proposed aircraft shall meet or exceed the performance requirements specified in the PWS, after any modifications. Supporting data (published performance data, operating manuals, etc.) shall be submitted electronically to substantiate how the hoist(s) meets the performance requirements.

2.4 Airworthiness Data

2.4.1 FAA Airworthiness Certificate

The Offeror shall provide a plan to secure FAA approval for each aircraft modification required to meet the performance requirements of PWS 3.1.. The plan shall include a compliance checklist and define the source for development of FAA approved data and demonstrate that major alterations to aircraft with Standard and/or Special Restricted Category Airworthiness Certificates will be certified as airworthy and properly documented using FAA Form 337 signed in blocks six (6) (Conformity) and seven (7) (Return to Service) by persons authorized under 14 CFR § 43 and citing FAA approval data.

Aircraft operating under any other certificate category, including but not limited to Special Airworthiness Certificate in the Experimental Category, are not authorized for the performance of this contract due to the operational risks and stringent reliability requirements of the mission.

2.4.2 NAVAIR Airworthiness

The Offeror shall identify any aircraft modification(s) required to meet the performance requirements of the PWS, where civil operating rules, limitations, or restrictions will restrict FAA certification for captive carriage only.

2.4.3 Aircraft Fatigue Life and Life Limited Parts

The Offeror shall demonstrate that each aircraft proposed has the remaining part lives to allow the aircraft to be safely operated throughout the four year 364 day ordering period of the planned contract, based on projected combined aircraft usage rates as identified in Section B, CLIN 0003/0004. The Offeror shall indicate any life limited part that will require replacement or overhaul during the ordering period and identify the organization that the Offeror shall use to perform the maintenance.

2.5 Aircraft Support

2.5.1 Aircraft Maintenance Strategy

The Offeror shall provide an explanation of its maintenance organization and strategy for conducting both scheduled and unscheduled aircraft maintenance. Documentation of executed sub- contracting or teaming agreements (e.g. copies of executed agreements) shall be provided for substantiation where applicable.

2.5.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.5.3 Aircraft Parts

For each proposed T/M/S, the Offeror shall provide its proposed source of OEM, FAA or equivalent certified parts.

2.5.4 Maintenance and Engineering Data

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

2.6 Aircraft Availability

2.6.1 Method of Performing Services

The Offeror shall describe its method of ensuring pilot and aircrew (excluding maintenance personnel) availability to ensure it will be capable of conducting the missions detailed in the PWS while meeting the mission effectiveness metric described in the QASP (Attachment 3) at the end of the stand-up period.

2.6.2 Aircraft Availability/Reliability

The Contractor will be required to provide aircraft to support each mission as scheduled. The Offeror shall describe in detail its method of ensuring it meets the mission effectiveness metric described in the QASP (Attachment 3).

2.6.2.1. The Offeror shall include a discussion of managing scheduled and unscheduled maintenance for all aircraft types proposed to enable contract mission completion with minimum impact to the fleet.

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

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

For this Volume, the Offeror shall identify relevant contract references, or those portions of a relevant contract reference, whose performance is within five (5) years of the solicitation release date and contains efforts that are similar to those efforts (e.g., end product or service, type effort, contract tasks, contract type, contract dollar value, etc.), required by this solicitation for the Prime. Offerors shall also identify relevant contract references within the past five (5) years that had any show-cause notices, cure notices, or termination for default. The Offeror shall complete Table CA-2 (Relevant Contract Summary) provided in Attachment L-1 (Contract Administration Summary Tables), for all contract references 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 and Corporate Experience), the Offeror shall provide electronic copies of the complete final versions of the SOW/PWS or other supporting contract documentation from each contract or delivery/task order reference identified in Table CA-2

(Relevant Contract Summary). For contract references that contain delivery/task orders, the Offeror shall 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 Past Performance Questionnaires (PPQs) are the primary customer feedback data used to evaluate the Offeror’s past performance. The www.CPARS.gov system is the primary paperless method the Government will use to retrieve the CPARS for this source selection. For all contract references identified that do not have a CPARS, the Offeror shall forward a copy of Attachment L-5 PPQ to the cognizant Procuring Contracting Office (PCO), Administrative Contracting Officer (ACO), and Program Manager (PM), or commercial contractor equivalents for that contract reference. Offerors shall forward all PPQs within two weeks from this solicitation’s release date to allow adequate time for the recipient to respond. Note: The Offeror should not reference this solicitation’s number when distributing the PPQs to customers. The Offeror shall include instructions requesting recipients to send completed PPQs via e-mail to Sherona Thomas, Contract Specialist, at sherona.thomas.civ@us.navy.mil and David Silverstone, Contracting Officer, at david.s.silverstone.civ@us.navy.mil within two weeks of receipt. The Offeror shall ensure that all points of contact are current, include an email address, and phone number. The Offeror shall not conduct follow-up actions regarding any PPQs, 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.

3.1 Contract Reference Data

The Offeror shall complete Attachment L-4 Table PP-1 (Past Performance Contract Data) for each contract reference provided, following the instructions provided within the attachment. The Offeror shall submit the completed Attachment L-4 within this section and as a separate electronic file. Please note this form is a summary of the prime’s contract reference data. Offerors shall provide all detailed information and comparative analysis of the past performance references to this solicitation’s requirements in Volume 3.0, Section 3.2 (Evaluation), of the Offeror’s proposal. Offerors shall use the contract references designated in the PP-1 table when completing this Volume. Offerors shall ensure consistency by using the same numbering for all contract references throughout all Offeror’s proposal volumes (i.e., the contract references identified as P1, P2, P3, etc.). Offerors may include commercial contract references.

Table PP-1 Past Performance Contract Data 1 Offeror Name 2 Entity Name

3 Contract Reference

4 Title of Contract

5 Contract Number

6 Contract Type mailto:sherona.thomas.civ@us.navy.mil mailto:david.s.silverstone.civ@us.navy.mil

Table PP-1 Past Performance Contract Data

7 Relevant Delivery/Task Order Numbers (if applicable)

8 Subcontract Number/PO Number

9 Procuring agency

10 Description of product or service

Period of performance - Start Date

Period of performance - End Date

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

13 a. Scope

For each attribute below, briefly describe how the contract reference demonstrates relevance and list Contractual Documentation Support (CDS) references that document the scope of the past performance contract submitted.

Helicopter services must have MK-30 target launch from a MK145 and target recoveries and at least one (1) of the following elements:

• Transport of personnel/hazardous material to/from shore facilities or offshore facilities

• Firefighting support

b. Magnitude

Contract total value of greater than $5.0 M, or annual task order value greater than $1.0 M.

c. Complexity

For each attribute below, briefly describe how the contract reference demonstrates relevance and list CDS references that document the complexity of the past performance contract submitted.

Helicopter Services must have the following elements:

• Providing maintenance support and modifications of rotary wing aircraft; external lift, transport of personnel, firefighting, and visual surveillance utilizing rotary wing aircraft.

• Obtaining Airworthiness Certificate(s) for rotary wing aircraft from the FAA or other FAA or DoD recognized Civil and Military Airworthiness Authorities.

Table PP-1 Past Performance Contract Data

• Maintaining Continuing Airworthiness of rotary wing aircraft (FAA or Military).

15 Date of last completed CPARs

16 Date past performance questionnaires were sent.

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

18 Gov't PCO or Commercial Purchasing Agent Name:

Phone:

Email:

19 Gov't ACO Name:

Phone:

Email:

20 Gov't PM or Commercial PM Name:

Phone:

Email:

21 Other POC:

Name:

Title:

Phone:

Email:

3.2 Evaluation

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

For each contract or delivery order reference identified in Attachment L-4 Table PP-1 (Past Performance Contract Data), the Offeror shall provide data regarding relevancy, past performance information (PPI), and demonstrated systemic improvement as described below, organized by contract reference. Offerors shall present information in the proposal to demonstrate the relevancy of the Prime’s past performance with respect to this solicitation’s requirements. For any contract references where the Prime is aware of problems, the Offeror shall describe the issues in section 3.2.b (PPI.) For each past performance problem identified, describe the status of the systemic improvement efforts in section 3.2.c (Demonstrated Systemic Improvement.)

a. Relevancy: Offerors are required to explain what aspects of the contract references the Offeror deems relevant to this solicitation’s requirements. To demonstrate relevancy, Offerors should provide a comparative analysis to this solicitation’s requirements. In Annex A, Offerors shall provide one electronic copy of the Statement of Work (SOW), / Performance Work Statement (PWS) from each of the referenced contracts identified in Table PP-1. Within the comparative analysis, Offerors should identify the relevant portions (sections, paragraphs and page numbers) of the referenced contract’s SOW/PWS to clearly identify how past tasks performed are similar to this solicitation’s requirements. In addition, the referenced sections only need to be referenced/identified. Offerors shall not break out specific paragraphs separately from the complete SOW/PWS.

To facilitate the relevancy determination, the Offeror shall provide an explanation of why multiple CAGE codes are proposed. In its explanation, Offerors shall identify all applicable CAGE codes along with their defined roles and responsibilities, and a description of all such changes in the organization of the company within Volume 1, Contract Administration when submitting past performance for CAGE code(s)/UEI that are different from the prime Offerors.

In addition, the Offeror shall provide a narrative within this section explaining how the changes affect the relevance of any past performance contract references provided.

b. PPI: Offerors shall provide a brief description of performance in delivering quality products in each of the areas identified below. Offeror shall include 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 any consequences realized because of the problem. The Government will review past performance feedback as it relates to the following:

1. Quality Performance: Meeting technical requirements

2. Schedule Performance: Meeting schedule requirements

3. Management Performance: Managing the contracted effort

4. Small Business Subcontracting: Large Business Offerors shall show which efforts they met or exceeded Small Business, Veteran-Owned Small Business (VOSB), Service- Disabled Veteran-Owned Small Business (SDVOSB), HUBZone Small Business Historically Underutilized Business Zones (HUBZone), Small Disadvantaged Business (SDB), and Women-Owned Small Business (WOSB) small business utilization and subcontracting goals.

c. Demonstrated Systemic Improvement: The Offeror shall identify systemic improvement actions taken to resolve any past problems identified in 3.2.b Past Performance Information.

The Offeror shall provide the documented records of improvement results, preferably recorded in Government systems such as CPARS. The Offeror shall describe the techniques, elements, and tools used to correct problems on the past contract and, if applicable, how it may apply these techniques, elements, and tools on the solicitation requirements. The Offeror shall provide quantifiable evidence or metrics that substantiate or demonstrate systemic improvement claims to demonstrate that previous problems are unlikely to occur on the solicitation requirements. 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. The Government may consider discounting problems if the Offeror can demonstrate the correction of problems through demonstrated systemic improvement. Systemic Improvement is demonstrated when the Government can verify that the Offeror prevented the recurrence of past problems. Examples include the identification of the root cause of a problem, a corrective action plan that systemically addressed the past problem, a description of how and when the plan was implemented, documented timeframe to demonstrate successful implementation of the corrective action; and performance data, preferably through Government records, to show performance improvements.

4. VOLUME 4 – PRICE

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

Attachment L-6 CP-1 Pricing Sheet

4.1 Contract Prices

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

Provide the proposed price for each CLIN using Pricing Sheet, Attachment L-6, CP-1. The Offeror shall provide a narrative for all priced CLINs describing the build-up of the proposed unit price, assumptions used for each CLIN, and the basis of estimate for the unit price proposed showing build-up calculations of the unit sell price. The Offeror shall explain any appearance of unbalanced pricing.

Offerors are forewarned that if there are discrepancies between Section B, Attachment L-6 Pricing Sheet, and Volume 4 Price Narrative, Section B prevails.

4.1.1 CLIN 0001 Capability Stand Up

The Offeror shall propose a unit price and shall not exceed the Not-to-exceed (NTE) amount shown in Section B in Pricing Sheet Attachment L-6 for CLIN 0001.

The Offeror shall include costs associated with management, logistical, engineering and administrative efforts required for developing GOPs/FOPs and obtaining Airworthiness certification of their aircraft.

This also includes costs associated with airworthiness data review meetings and the Post Award Conference (PAC) (PWS section 4.2.1.1) as well as any travel costs incurred for these meetings. This shall not include aircraft acquisition or aircraft leasing costs.

4.1.2 CLIN 0002 Aircraft Readiness

The Offeror shall propose a unit price for this CLIN in Section B and in Pricing Sheet Attachment L-6.

The unit price multiplied by the quantity of months is used to develop the total price for this CLIN in Section B. The Offeror shall include fixed costs that will be incurred regardless of the number of missions performed. It shall also include costs associated with Contractor Furnished Equipment (CFE), tools; full-time aircrew, non-touch support personnel, hull and liability insurance, aircraft modernization, uninsured damage, navigation services, refurbishment, computer-based maintenance programs, recurrent training, weather services, depreciation of the aircrafts, leasing etc. This also includes costs associated with Program Management Reviews (PMR) (PWS section 4.2.1.2) including any travel costs incurred for these meetings. The Offeror shall include all costs to perform calendar driven maintenance during the contract ordering period.

The following costs shall not be included in the price of this line item:

a. Costs incurred by the Contractor which are associated with the variable pricing for flight services (CLIN 0003/0004) e.g., Parts – airframe, avionics, engine consumables, engine restoration costs, landing/parking fees, inspection fees, dynamic components, lifetime limited parts, tools, passports, visas, shipment or trans-shipment of aircraft, supplies, etc.

b. Costs for flights such as, but not limited to, maintenance test flights, the ferrying/transporting of personnel, aircraft or equipment to and from maintenance facilities, or to train aircrew, are to be included in the variable unit price and are not allowable as a direct (fixed) cost under this CLIN.

Fuel costs shall not be charged to this or any other CLIN as this is “dry” contract where the Government will provide appropriate fuel cards for each of the Contractor’s aircraft (PWS section 4.2.2).

4.1.3 CLIN 0003 Medium Lift Services/0004 Heavy Lift Services

The Offeror shall propose a unit price. The unit price multiplied by the quantity of minutes is used to develop the total price for this CLIN in Section B and in Pricing Sheet Attachment L-6. The Offeror shall include all variable costs associated with flying aircraft capable of meeting the requirements of the PWS, including costs that are specific to the mission associated with this CLIN such as the costs per flight minute. It shall include costs for flying the aircraft, maintaining the aircraft, aircrew support personnel; equipment, tools, materials, spare parts, replacement parts, and time change items.

4.1.4 CLIN 0005 Travel/Material/Shipping

The Offeror shall propose the Government provided NTE amount listed in Section B and Pricing Sheet Attachment L-6.

4.1.5 CLIN 0006 Aircraft Modification

The Offeror shall propose the Government provide NTE amount listed in Section B and Pricing Sheet Attachment L-6.

4.1.6 CLIN 0007 Administrative & Technical Data (NSP)

This CLIN is not separately priced. Therefore, the Offeror shall not propose any price for this CLIN.

4.2 Government Fuel Costs

As stated in PWS section 4.2.2, this is a “dry” contract, and the Government will provide access to fuel and provide fuel cards under the Aviation Into-Plane Reimbursement (AIR) card program for each of the Contractor’s aircraft. Offerors shall not include cost of fuel to fly Government missions in any CLINs.

5. VOLUME 5 – SMALL BUSINESS

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

Attachment L-7 Small Business Participation Commitment Document (SBPCD)

5.1 Small Business Participation Commitment Document (SBPCD)

All Offerors (whether a Large (including non-profit entities) or Small Businesses) shall complete the provided Attachment L-7 SB-1 Small Business Participation Commitment Document (SBPCD) and submit it in this Volume. (Note: FAR 15.304 does not exempt Small Businesses from submitting a SBPCD). The SBPCD shall list the planned small business participants and identify a minimum small business participation commitment of 10% of the total proposed contract price.

The SBPCD shall provide the Offeror’s commitment for each of the following categories: Small Business (SB), Small Disadvantaged Business (SDB), Women-Owned Small Business (WOSB), Veteran-Owned Small Business (VOSB), Service-Disabled Veteran-Owned Small Business (SDVOSB), and HUBZone Small Business (HUBZone). Each small business participant identified in the SBPCD shall have an active registration in SAM or provide a written certification of its small business or socio-economic status consistent with the NAICS code size standard identified in the solicitation.

The Government intends to incorporate the SBPCD into the resultant contract as Attachment 5 in Section J.

The SBPCD is separate from, but shall be consistent with, the SB Subcontracting Plan (as required from Large Businesses). The Government advises Large Business Offerors that while the SB Subcontracting Plan must be submitted in accordance to be eligible for award, the acceptability of the content of that plan is part of the responsibility determination assessment and not part of the SBPCD evaluation.

5.2 Small Business (SB) Subcontracting Plan

Large Business Offerors shall provide their SB Subcontracting Plan conforming to the requirements of FAR 19.7 and DFARS 219.7 in this Volume. The PCO will review and approve the SB Subcontracting Plan of the successful Offeror(s) prior to contract award as part of the responsibility determination. The Government will incorporate the successful Offeror’s approved Subcontracting Plan into the resultant contract as Attachment 6 in Section J. The Government will monitor the contractor’s performance against the plan during contract execution.