N0001925R0003-0003.docx

N0001925R0003

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 12-May-2025 04:00 PM to 19-May-2025 09:00 AM.

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

Exhibit/Attachment Table of Contents

TBD

TBD

TBD

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to assess the capabilities of the Offeror to meet 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. All proposals must clearly demonstrate that the Offeror has a thorough understanding of all requirements and associated risks; is able, willing, and competent to devote 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. Price information, (e.g., dollar values and/or hourly rates) shall appear only in Volume 1 (Contract Administration), Volume 5 (Price), and Volume 6 (Small Business).

In presenting material in the proposal, the Offeror is advised 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. 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. Offerors shall not modify requested information in the Section L Attachments. Additionally, the information provided in the attachments shall be consistent across proposal volumes and alternate proposals are not acceptable.

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.

Throughout these instructions, “Offeror” is defined as the prime contractor with its Commercial and Government Entity (CAGE) code identified in Block 17 on Standard Form (SF) 1449, 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. Entities are defined in Section M.

2.0 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 each page with volume and page number. 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-point font.

2.1 Electronic Submission of Proposal

The Offeror shall submit all volumes of the proposal electronically through the Solicitation Module of the Procurement Integrated Enterprise Environment (PIEE) at https://piee.eb.mil. No other proposal 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. All proposal information shall be marked with “CUI/Source Selection Information – See FAR 2.101 and 3.104.” Instructions on how to post an offer to the Solicitation Module in the PIEE system, please refer to the Posting Offer demo: are available at https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf.

Offerors shall follow the registration instructions found on the PIEE website. Prime offerors shall 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. 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.

It is 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 will not 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 8 of the SF 1449 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. If there is an unanticipated PIEE System outage within 24 hours of the proposal due date and the outage has interrupted normal Government processes so that proposals cannot be received by the exact time specified in the solicitation, the Contractor shall immediately notify the Contracting Officer. This notification shall occur prior to the proposal submission deadline and shall be made in writing. The Offeror shall obtain written approval from the Contracting Officer to submit the proposal via an alternate method or the Contracting Officer may advise the Offeror that the Government will follow the procedures set forth in FAR 15.208(d) for amending the solicitation closing date.

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 ensure the content and attachments that contain pricing information [Volume 1 (Contract Administration), Volume 5 (Price), and Volume 6 (Small Business)] are kept separate from the other proposal volumes that do not contain pricing information. The Offeror shall ensure that price information is delivered as separate files from the remainder of the proposal volumes. 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 10 Operating System to access proposals. Offerors shall submit proposal information using the following applications: Microsoft Word 2016, Microsoft Excel 2016, Microsoft PowerPoint 2016, and Portable Document Format (.pdf). Offerors shall submit letters and other signed documents as fully searchable .pdf files. The Offeror shall ensure that its proposal Volumes and Annexes are fully searchable .pdf files. 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:

The Offeror shall follow the basic structure of the file naming convention in Table G-1 (Offeror File Naming and Proposal Structure) 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) to ensure the files are accessible.

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. If the Offeror is unable to upload the files as described herein, please upload each individual file with the proper file naming convention as outlined in table G-1 below.

Table G-1 Offeror File Naming and Proposal Structure*

Contract Administration Tables Table CA-1 Offeror Business System Status Table CA-2 Workshare Summary Table CA-3 Relevant Contract Summary for Past Performance

Contract Pricing Attachment Tables Table CPA-1 Pricing Worksheet Table CPA-2 SE Maint & Cal Table CPA-3 Det Daily Travel Table CPA-4 Field Transportation Table CPA-5 Field Daily Travel Table CPA-6 Burden Rates

As Needed

Volume 2 (Prerequisite) Paragraph 2.1.1 – Title 14, CFR, Part 145 Certification

Volume 2 (Prerequisite) Paragraph 2.1.2 – Data

PP POC Info#.pdf As Needed

Annexes

*Table G-1 Note: The Offeror shall ensure that all submitted .pdf files are fully searchable. Additionally, the Offeror may submit Microsoft Excel files as is and need not convert them into .pdf or Microsoft Word files.

3.0 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

Table CA-2 Workshare Summary Table CA-3 Relevant Contract Summary

Table CPA-2 SE Maint & Cal Table CPA-3 Det Daily Travel Table CPA-4 Field Transportation Table CPA-5 Field Daily Travel Table CPA-6 Burden Rates

4.0 PROPOSAL PACKAGING AND EARLY SUBMISSION:

All proposals must be UNCLASSIFIED.

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

If an Offeror makes changes to its proposal volumes, including attachments submitted as part of that volume from a previous submittal, the Offeror shall resubmit the entire proposal volume.

5.0 CHANGES TO SOLICITATION

The Government will post all amendments to this solicitation in the Solicitation Module of the U.S. Government PIEE website.

6.0 TECHNICAL LIBRARY

A Technical Library of information directly related to the requirements of this contract is available to Offerors. The library will be disseminated via PIEE.

Distribution of data contained in the technical library to subcontractors and team members shall be the responsibility of the Offeror that was granted access and shall be limited to a “need to know” basis. All guidance contained herein with regard to handling, distribution and destruction of the data shall be flowed down to all subcontractors and team members. Those who take receipt of any library data shall comply with all laws, export controls, and distribution statements associated with the data.

To request access to the Technical Library information, Offerors must contact Jadyn McGlone at jadyn.s.mcglone@boeing.com or (610) 591-5997 in order to obtain a Non-Disclosure Agreement. The aforementioned information shall be provided to Ms. Karin Jensvold at karin.p.jensvold.civ@us.navy.mil when access is requested.

Upon review of written request and verification of Offeror’s status, access to the technical library data will be provided.

PART B: SPECIFIC INSTRUCTIONS

1.0 VOLUME 1 – CONTRACT ADMINISTRATION

The Offeror shall provide the following information in the Volume 1, Contract Administration:

1.1 Attachment L-1, Contract Administration Tables

The Offeror shall complete the following tables: Table CA-1 (Offeror Business System Status); Table CA-2 (Workshare Summary); and Table CA-3 (Relevant Contract Summary)

1. Table CA-1 Offeror Business System Status The Offeror shall complete Attachment L-1, 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.

2. Table CA-2 Workshare Summary The Offeror shall complete Attachment L-1, Table CA-2 (Workshare Summary) to summarize the Offeror’s pertinent information by CAGE code/UEI to include the proposed type and level of work to indicate a commitment of work for those entities.

3. Table CA-3 Relevant Contract Summary The Offeror shall complete Attachment L-1, Table CA-3 (Relevant Contract Summary) to delineate all contract references that relate to the proposed Entities for Past Performance.

For this solicitation, contract references shall relate to the CAGE code/UEI of a proposed entity. The Offeror shall explain why a referenced contract relates to a different CAGE code/UEI than the proposed entity . Please describe if the discrepancy in the CAGE code/UEI is a result of a corporate acquisition, reorganization, merger, or other administrative reason, explain how the changes impact the contract references provided and applicable information concerning the completion of contract novation.

1.2 Attachment L-2, Contract Pricing Attachments Tables:

The Offeror shall complete the Tables CPA-1 through CPA-5 within Attachment L-2, Contract Pricing Attachment Tables in accordance with the “Instructions” tab therein and as specified below.

If the Offeror proposes a CLIN at zero dollars ($0.00), the Offeror shall describe in its Contract Administration Summary how the work associated with the CLIN will be accomplished and where the cost is otherwise covered and shall propose a corresponding H Clause in the Model Contract.

Worksheets locked for editing contained within Attachment L-2, CPA Tables will become IDIQ contract Attachments (2)-(4) and will be incorporated into the contract at time of award. The prices proposed in Attachment L-6 OPS shall be consistent with the prices proposed in Attachment L-2, CPA Tables. The prices proposed in Attachment L-2, CPA Tables will take precedence.

1. Table CPA-1 Pricing Worksheet The Offeror shall complete Attachment L-2, Table CPA-1 (“Pricing Worksheet” Tab) in accordance with the “Instructions” Tab. Values in Column AF (“CLIN Values”) shall align with the values entered into Section B of the Model Contract after all tabs are completed.

2. Table CPA-2 Support Equipment Maintenance, Calibration, and Repair The Offeror shall complete Attachment L-2, Table CPA-2 (“SE Maint & Cal” Tab) in accordance with the “Instructions” Tab. This will become IDIQ Contract Attachment (2), Appendix (A).

3. Table CPA-3 Daily On-Site Detachment Travel Expenses The Offeror shall complete Attachment L-2, Table CPA-3 (“Det Daily Travel” Tab) in accordance with the “Instructions” Tab. This will become IDIQ Contract Attachment (2), Appendix (B).

4. Table CPA-4 Round-Trip Field Team Transportation The Offeror shall complete Attachment L-2, Table CPA-4 (“Field Travel” Tab) in accordance with the “Instructions” Tab. This will become IDIQ Contract Attachment (2), Appendix (C).

5. Table CPA-5 Daily On-Site Field Team Travel Expenses The Offeror shall complete Attachment L-2, Table CPA-5 (“Field Daily Travel” Tab) in accordance with the “Instructions” Tab. This will become IDIQ Contract Attachment (2), Appendix (D).

6. Table CPA-6 Burden Rates by Contract Year The Offeror shall complete Attachment L-2, Table CPA-6 (“Burden Rates” Tab) in accordance with the “Instructions” Tab. This will become IDIQ Contract Attachment (4).

1.3 Model Contract Documents:

The Offeror shall provide the following:

1. Original signed SF1449 (Solicitation/Contract/Order for Commercial Items) cover page of the solicitation and a signed cover page of each amendment (as applicable) with all applicable Blocks completed and acknowledgement of receipt of each amendment (as applicable) to this solicitation;

2. Section B with proposed pricing calculated in accordance with pricing Note B-1, using the values from the “CLIN Value” column in the “Pricing Worksheet” Tab of Attachment L-2, CPA Tables (Contract Pricing Attachment Tables);

3. All Federal Acquisition Regulation (FAR), Defense Federal Acquisition Regulation Supplement (DFARS), Naval Air Systems Command (NAVAIR) clauses, special clauses, and provisions requiring Offeror fill-ins.

4. Section H proposed clauses, if applicable, in accordance with Section L, paragraph 1.2;

5. A statement indicating that the proposal is valid for 365 days; and

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

7. A written plan describing how it will continue to perform the essential contractor services listed in Section J Attachment (1), Performance Work Statement, during periods of crisis in accordance with the provision at DFARS 252.237-7024. The Offeror’s submitted document will become Attachment (17) to the awarded IDIQ contract.

1.4 Offeror Representatives and Information

Offerors shall provide the name, title, phone number and email address of the Offeror’s principal point of contact for the solicitation. Also, 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; and size of business (large or small).

1.5 Government Agency Information

Offerors shall provide the mailing address, telephone, email address and facility codes for the Offeror’s cognizant Contract Administration Office, local Defense Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA), and Government Paying Office. In addition, please provide the name, telephone number, and email address for the DCMA Administrative Contracting Officer (ACO) at DCMA.

1.6 Terms and Conditions:

Offerors shall not take any exceptions or deviations from the terms and conditions or any requirement of the solicitation. 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 involving a PWS requirement. An exception or deviation is a deficiency. A deficiency renders the Offeror’s proposal unawardable.

Offerors shall include the statement, “The Offeror takes no exceptions or deviations to the terms and conditions or requirements of this solicitation” in this section.

2.0 VOLUME 2 – TECHNICAL PRE-REQUISITES

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

2.1 Pre-Requisites

Each Prime proposing to perform the work must provide documentation to demonstrate that the Offeror’s team meets the pre-requisites listed below. The Offeror shall provide documentation to demonstrate current and unexpired certifications/licenses of the entity proposed as the aircraft maintenance depot repair station. Offerors are reminded that the burden of proof for all substantiation within the proposal rests with the Offeror for this assessment. The Offeror may provide a substantiating explanation for each pre-requisite documentation submittal.

2.1.1 Title 14, CFR, Part 145 Certification

The Offeror shall identify in Volume 2 (Prerequisite), the entity proposed as the aircraft maintenance depot repair station. The Offeror shall provide authoritative documentation demonstrating the proposed entity identified as the aircraft maintenance depot repair station has a current Title 14, CFR, Part 145 Certification for aircraft in the Design group “C,” “D,” or “E” as defined by the International Civil Aviation Organization (ICAO) Classification Group. The Offeror shall provide the 14 CFR 145 accepted Repair Station Operation Specification that includes all class ratings and limited ratings to ensure that the repair station is capable of meeting the requirements of this solicitation. The Offeror shall provide the 14 CFR 145 accepted Repair Station Manual Capabilities List that include applicable airframe(s), engines, etc. that demonstrates the repair station is determined to have the tools and equipment, technical documentation and trained staff to support aircraft maintenance.

2.1.2 Data

The Offeror shall demonstrate through substantiating documentation its ability to access and obtain the data necessary to meet the PWS requirements in accordance with PWS paragraph 29.0 (Data (CLIN 0051)). The Offeror shall provide one of the following:

a. An existing signed agreement in Annex D (Technical Data); or

b. If the Offeror does not currently have existing agreements in place, then provide a Letter of Intent (LOI) from the original equipment manufacturer. The LOI shall include the schedule that indicates an executed signed agreement will be in place by the end of the Transition Phase-In (CLIN 0001) period, in accordance with PWS paragraph 29.0. The LOI and schedule shall be provided in Annex D.

3.0 VOLUME 3 – TECHNICAL

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

Attachment L-3 Proposed Benefits/Features Matrix

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

A CRM, Table T-2 below, 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-2 Cross Reference Matrix at the beginning of Volume 3 – Technical.

Table T-2 Cross Reference Matrix

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

0013, 0014

Offerors shall complete Attachment L-3 to summarize any proposed benefits or feature of its proposal for the Government to consider when evaluating the Offeror’s proposal. Offerors shall provide a summary of those aspects of its proposal that meet the definition of a Significant Strength, Strength, or Risk Reducer based on the Section M definitions in Attachment L-3. Offerors shall also thoroughly explain the proposed benefits or features in the relevant section of its proposal.

If a proposed benefit or feature is not clearly detailed in Attachment L-3, the Government may not consider this information in its evaluation. The Government advises Offerors that any offer to exceed a requirement or to provide a feature with performance and/or operational benefits may be included in the resulting applicable Contract and shall be reflected within the Offeror’s proposed Price.

Throughout the Technical Volume, the Offeror shall demonstrate the extent to which its proposed capabilities will meet the requirements. The extent and the type of substantiation may vary, but the Offeror should substantiate each paragraph in the Technical Volume.

3.1 Material and Supply Management

3.1.1 The Offeror shall describe its strategy to supply the C-40A (737-700C) fleet worldwide with commercial parts utilizing a one-for-one commercial parts pool to meet Part 121 requirements, Non-Mission Capable Supply (NMCS)/Aircraft on Ground Requisitions and Partial-Mission Capable Supply (PMCS)/Mission degraded Requisitions performance metrics outlined in PWS Appendix I, (Performance Metrics).

3.1.2 The Offeror shall provide its Letters of Intent (LOIs), or if applicable, Letters of Agreement (LOAs), for commercial parts and material to comply with the PWS requirements at each MOB site, detachment site, and depot facility. The LOIs or LOAs shall correspond to the Offeror’s proposed price in Volume 5 – Price. The Offeror shall demonstrate how it will maintain and supply storeroom operations at each MOB site.

3.1.3 The Offeror shall describe its experience providing supply support for ICAO Airplane Design Codes “C”, “D” or “E”.

3.2 Commercial Line Maintenance and Ground Operating Procedures (GOPs) (14 CFR Part 121 & 43) for VMR-1 and VR-51

3.2.1 The Offeror shall describe its staffing approach to ensure compliance with Commercial Line Maintenance in PWS paragraph 7.0 (USN and USMC Commercial Line Maintenance (CLM)).

3.2.2 The Offeror shall describe its approach to ensuring all Commercial Line Maintenance activities are accomplished in accordance with PWS paragraph 7.6 (Line Maintenance Activities). The description shall also include an approach to each sub paragraph under PWS paragraph 7.6. The Offeror shall describe its approach to meeting PWS performance metrics in Appendix I, (Performance Metrics) for Non-Mission Capable Maintenance (NMCM) and Partial-Mission Capable Maintenance (PMCM) aircraft in CONUS and OCONUS locations.

3.2.3 The Offeror shall address its methods and procedures to develop Ground Operating Procedures (GOPs) to release an aircraft Safe for Flight in accordance with PWS paragraph 7.2 (Ground Operating Procedures). The Offeror shall explain how it plans to manage CLM 24 hours a day 7 days a week (24/7) (VMR-1 and VR-51) while simultaneously complying with Detachment Support Operations in PWS paragraph 11.0 (Detachment Support).

3.2.4 The Offeror shall describe its experience providing CLM for ICAO Airplane Design Codes “C”, “D” or “E”.

3.3 Depot-Level Support and Facilities

3.3.1 The Offeror shall describe its ability to provide support for simultaneous depot inductions on multiple aircraft as required by PWS paragraph 12.1.1 (Depot Capacity).

3.3.2 The Offeror shall identify its combined repair and shipping interval timeframes for the following items/components: Auxiliary Power Unit (APU) Heavy Maintenance, Aft Airstairs Overhaul, Main Landing Gear Overhaul, and Nose Landing Gear Overhaul.

3.3.3 The Offeror shall describe its approach, inclusive of procedures and methods, to meeting Turn Around Times (TAT) for Scheduled Depot-Level Maintenance one (1) through eleven (11) C-Checks in PWS paragraph 12.0 (Scheduled Depot-Level Heavy Maintenance: C-Checks).

3.3.4 The Offeror shall describe its experience providing support of Aircraft, Auxiliary Power Unit (APU) Heavy Maintenance, Aft Airstairs Overhaul, Main Landing Gear Overhaul, Nose Landing Gear Overhaul end items, and performing strip and paint for ICAO Airplane Design Codes “C”, “D” or “E”.

3.4 Aircraft On Ground (AOG) Support

The Offeror shall address its strategy to provide AOG repairs to include dispatching Depot Field Teams (DFTs) to Continental United States (CONUS) and Outside Continental United States (OCONUS) locations in support of C-40A operations as well as its strategy for drop-in maintenance (DIM) in PWS paragraphs 14.0 and 15.0.

4.0 VOLUME 4 – 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 utilize to provide information for this volume:

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 SOW/PWS or other supporting solicitation/contract documentation from each submitted contract reference or delivery/task order reference identified in Table CA-3 (Relevant Contract Summary). Offerors shall highlight the relevant portions and specific paragraphs that relate to the solicitation requirements. For contract references that include delivery/task orders that meet the relevancy definition in Section M, 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 an electronic copy of the awarded contracts’ SOW/PWS or other documentation and 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.

The 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 CPARS.gov system is the primary paperless method used to retrieve the CPARS for this source selection. For all contracts identified that do not have a CPARS, or for a current contract where the latest CPARS is greater than 12 months old, the Offeror shall forward a copy of Attachment L-5 PPQ to that contract’s Procuring Contracting Office (PCO), Administrative Contracting Officer (ACO), and Program Manager (PM); or commercial contractor equivalents. Offerors shall forward all questionnaires within two weeks from this solicitation’s release date to allow adequate time for the recipient to respond. Offerors shall not reference this solicitation’s number when distributing the past performance questionnaires to customers. The Offeror shall include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to the aforementioned contract specialists. 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 with regard to this questionnaire, other than to confirm receipt by the recipient.

4.1 Authorization Letter(s)

The Offeror shall submit a signed “Release of Adverse Past Performance Authorization Letter(s)” with written consent from the Entity, authorizing the release of adverse past performance information to the Offeror. The Offeror shall include the signed letter(s) as a separate file within Volume 4 (Past Performance). This authorization letter allows the Government to coordinate past performance issue(s) with the Offeror.

For Entities that do not provide an authorization letter with such written consent, the Offeror shall provide point of contact information for each Entity. This contact information shall include a name, address, phone number, and email address 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 JV team members, and the Offeror will forfeit the opportunity to participate in any related discussions.

4.2 Relevant Contract Data

The Offeror shall complete Attachment L-4 Table PP-1 (Past Performance Contract Data) for each relevant contract identified, following the instructions provided within the attachment and submit as a separate electronic file. Offerors acknowledge that Table PP-1 is a summary of the Offeror’s contract references. Offerors shall provide all detailed information and comparative analysis of the past performance references to this solicitation’s requirements in Volume 4, Section 4.3 (Evaluation), of the Offeror’s proposal. Offerors shall use the contract references designated in Table CA-3 (Relevant Contract Summary) when completing this Volume. In general, the Government considers recent performance more relevant than older performance. Offerors may include commercial contracts. Offerors shall use the same numbering (e.g., the contracts identified as P1, S1, T1 etc.) for all contract references throughout all of the Offeror’s proposal volumes and Tables CA-3 and PP-1.

4.3 Evaluation

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

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

a. Relevancy In Annex A, Offerors shall provide one electronic copy of the SOW/PWS from each of the referenced contracts identified in Table PP-1. Offerors shall identify the relevant portions (sections, paragraphs and page numbers) of the referenced contract’s SOW/PWS to clearly identify how past tasks performed are relevant to this solicitation’s requirements. In addition, the referenced sections only need to be referenced/identified, and do not need to be broken out 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 proposed Entity. 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. Past Performance Information Offerors shall provide a brief description of performance in delivering quality products in each of the areas identified below. Offerors shall include any information that demonstrates the level of performance obtained. Where available, the Offeror shall provide quantifiable measures/trends to demonstrate past and current performance. Also, the Offeror shall describe past problems, including when they occurred, what the circumstances were surrounding the situation, and any consequences realized because of the problem.

(1) Quality Performance: Meeting technical requirements (i.e., the quality of technical performance, e.g., performing analysis, design, testing);

(2) Schedule Requirements: Able to meet the schedules agreed upon with the Government;

(3) Management Performance: Managing the contracted effort (i.e., program management, e.g., cooperation with customer, subcontract management); and

(4) Small Business Subcontracting: Large Business Entities shall show which efforts met or exceeded small business utilization and subcontracting goals for 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).

c. Demonstrated Systemic Improvement The Offeror shall identify systemic improvement actions taken to resolve any past problems identified in 4.3.b Past Performance Information. The Offeror shall provide the documented records of improvement results, recorded in Government systems such as CPARS, or another performance system. 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, through performance system records, to show demonstrated improvements.

5.0 VOLUME 5 – PRICE

The following is the Government provided Price attachment that the Offeror shall use to provide the Offeror’s proposed price:

Attachment L-6 Offeror Price Summary (OPS)

The Government will not review additional price attachments or additional price documentation in the Offeror’s price volume that is not included in the Offeror’s OPS and Price narrative. The prices proposed in Attachment L-6 (OPS) shall be consistent with the prices proposed in Attachment L-2 (CPA-1, Pricing Worksheet). The prices proposed in Attachment L-2 (CPA-1, Pricing Worksheet) will take precedence.

5.1 Instructions

While this competitive commercial acquisition is being competed under FAR Part 12, the price analysis evaluation is being completed using FAR Part 15.

This is a competitive commercial acquisition with adequate price competition anticipated. The price documentation requested is not considered certified cost or pricing data in accordance with FAR 15.403 and shall not be certified in accordance with FAR 15.406-2. By providing a price proposal submission, the Offeror grants the PCO, or authorized representative, the right to examine records and request additional information from the Offeror that form the basis of the pricing proposal. This examination and review may take place at any time before contract award.

5.1.1 Offeror (i.e., Prime contractor)

The Offeror shall provide a single Price narrative as part of its price volume submission. The Offeror shall complete Attachment L-6 OPS in accordance with instructions and definitions. The Offeror shall return the completed copy as part of its price volume submission.

Any discrepancies (e.g., attachments, declarations, etc.) between the Offeror’s Technical volume and the Offeror’s Price volume may result in the Offeror’s proposal not eligible for award.

5.1.2 General

The burden of proof of the Offeror’s proposed price is with the Offeror.

· The Offeror shall present the price proposal in a format (i.e., Attachment L-6 OPS, Offeror’s Price narrative) for the Government to evaluate the Offeror’s price proposal submission in accordance with the Government’s instructions and evaluation criteria.

· For CLIN 0013 Support Material Replacement and CLIN 0014 Government Property Replenishment, the Offeror shall provide adequate substantiating information and documentation in support of the price realism analysis for the Government to understand the Offeror’s assumptions to evaluate the Offeror’s price proposal submission.

The Offeror’s Attachment L-6 OPS shall be unprotected and unlocked, with linked cells and worksheets unhidden, and formulas intact to show mathematical operations.

The Offeror shall not link information between the Offeror’s Attachment L-6 OPS and any other Microsoft Excel files (e.g., Government attachments, files on the Offeror’s computers).

In the Offeror’s Attachment L-6 OPS, the Offeror shall use formulas and functions to the maximum extent possible.

· The Offeror’s input data in the yellow “CY1-CY5” tabs shall be:

· A hard-coded value (e.g., 2.34% for the G&A rate in the Offeror’s G&A cost formula) or

· A hard-coded value in a single location (e.g., 2.34% for the G&A rate in cell AY9) and used in the Offeror’s formulas.

· The Offeror’s numerical data shall not be in a pictorial format.

· The Offeror shall ensure the Offeror’s Attachment L-6 OPS does not contain any circular references or errors (e.g., #DIV/0!, #REF!, etc.).

5.2 Price Narrative

The Offeror’s Price narrative shall include information to support the Government’s unbalanced price evaluation for the Offeror’s proposed “Unit Price” or “Burdened Rate” in Attachment L-6 OPS “BUP” tab for all CLINs, including locations and/or squadrons. The Offeror shall explain the appearance of unbalanced pricing issues. The Government will verify and validate the Offeror’s explanation. The Government may or may not accept the Offeror’s explanation.

The following information applies to CLINs 0013 and 0014. The Offeror’s Price narrative shall include information to support the Government’s price realism evaluation of the Offeror’s proposed price for CLIN 0013 Support Material Replacement and CLIN 0014 Government Property Replenishment.

The Government has provided the following instructions to the Offeror including potential information to be included in the Price narrative to support the Government’s price realism evaluation. The Offeror shall provide a single Price narrative to include, as necessary, the following:

· Ground Rules and Assumptions,

· CLINs 0013 and 0014 pricing,

· Indirect Rates,

· Costs related to doing business OCONUS, and

· Substantiating documentation.

5.2.1 CLINs 0013 and 0014 Ground Rules and Assumptions

The Offeror shall include all ground rules and assumptions as part of the Price narrative. The Offeror shall include adequate substantiating information (e.g., vendor quotes) and documentation for the Government to understand the assumptions and evaluate the price proposal submission.

The Offeror shall explain the appearance of inconsistencies with the Offeror’s proposed cost elements in the buildup of the Offeror’s proposed price. The Offeror shall explain any high or low proposed prices as compared to historical data or other anomalies.

5.2.2 CLINs 0013 and 0014 Pricing

The Offeror shall provide a description of its pricing for CLIN 0013 Support Material Replacement and CLIN 0014 Government Property Replenishment. As necessary within the description, the Offeror shall provide information (e.g., Material, Shipping, Entity, etc.) for the Government to evaluate and validate the Offeror’s proposed price in Attachment L-6 OPS yellow “CY1-CY5” tabs. The Offeror shall reference the substantiating documentation in the Offeror’s Price narrative’s Appendix A, which shall correspond to the Offeror’s Letters of Intent or Letters of Agreements in Volume 3 - Technical.

If the Offeror proposes an Entity other than the Prime to complete work for either CLIN 0013 and/or CLIN 0014, then the Offeror shall reference that Entity’s vendor quote in the…