N0042121R007700002_Amendment.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to update Section L language. See Section A Summary of Changes for details.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 24

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

16C. DATE SIGNED

BY 04-Nov-2021

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street , County, State and Zip Code) X N0042121R0077

X 9B. DATED (SEE ITEM 11)

13-Oct-2021

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

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

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

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

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

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

04-Nov-2021

CODE

NAWCAD PROCUREMENT GROUP

21983 BUNDY ROAD, BLDG 441

PATUXENT RIVER MD 20670

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0042121R0077

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been added by full text:

AMEND 0002

Amendment 0002 incorporates the following changes:

Section L Part A para 2.2 – delete mention of DoD SAFE Paragraph 3.0 – change DoD SAFE to PIEE Paragraphs 4.0 and 4.1 – Replace paragraph with new directions for submitting proposals in PIEE Attachment L-2 Vol 2 T-1 – Row 8 CLINs updated Attachment L-7 Price Attachment – Quantities updated

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS

L – 1 CONTENT OF PROPOSALS (SERVICES) (5 Apr 2021)

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to fully assess the capabilities of the Offeror to perform all requirements of the solicitation. The proposal must be sufficient in detail and scope to enable evaluation and provide the evaluators a clear understanding of the Offeror’s approach, expertise, and capability as required by the solicitation. Proposals must demonstrate that the Offeror has a thorough understanding of all requirements, associated risks, and is able, willing, and competent to devote the resources necessary to meet all requirements. The Offeror shall not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. Offerors are advised that the Government may incorporate any part of the Offeror’s proposal deemed beneficial to the Government, into the final contract, without discussions. Price information, (e.g., dollar values and/or hourly rates) shall appear only in Annex B (Small Business Subcontracting Plan), and Volume 4 (Price). Alternate/streamlined proposals are not acceptable.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the responsibility of the Offeror to present enough information to allow the Government to evaluate its proposal without discussions. Unsubstantiated statements that the prospective Offeror understands, can or will comply with the specifications, or paraphrasing the requirements or parts thereof are considered inadequate and may render a rating of unacceptable.

The Offeror shall include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. The detailed information must be included in the most logical place and summarized and referenced in other areas if an overlap exists. Do not provide elaborate brochures or other presentation material beyond that sufficient to present a complete and effective proposal.

Throughout these instructions, “Offeror” is defined as the prime contractor with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. A “Joint Venture” (JV) is a partnership or teaming arrangement that is formed for the purpose of responding to this solicitation when the prime contractor consists of more than one legal entity. “JV Team Members” are the entities that make up a JV. The term “entity” is used to mean any or all of the following: prime contractor, JV, JV team members, any subcontractor, and corporate parent, division, subsidiary, or affiliate (e.g., any contractor with a different CAGE Code/DUNS than the Offeror). The following entities are defined as principal entities and only principal entities will be used in the past performance evaluations: (a) the prime contractor; (b) JV Team Members; and (c) other entities that are to perform at least 20% of the proposed total price for the contract. Offerors are advised that in order to demonstrate work commitment, each principal entity must be identified in Volume 4 Price and associated with a commensurate dollar value.

Questions: Offerors may submit questions requesting clarification of solicitation requirements by emailing the contract specialist at lauren.a.wright23.civ@us.navy.mil. It is required that all questions be received within 10 calendar days of the date this solicitation is issued.

2.0 PROPOSAL FORMAT

2.1 Electronic Submission of Proposal

This section is intended to provide information to Offerors on the electronic format and application software to be used for submitting proposals. Proposals should be formatted using a Times New Roman 12-point normal font (no reduction permitted). 10-point font is acceptable for Tables and Graphics.

2.2 Electronic Proposal Media

All proposal information shall be marked with “Source Selection Information – See FAR 2.101 and 3.104”. Refer to Part A Section 4.0 for more details.

2.3 Operating System and Applications

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

2.4 Hyperlinks

Offerors shall not use hyperlinks in proposal volumes.

2.5 Virus Free Electronic Submission

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

2.6 Multimedia

The Offeror shall not embed sound or video files within the proposal submission.

2.7 Graphics

Large files require greater computer system resources and are discouraged. The Offeror is encouraged to:

- Simplify the color palette used in creating figures and minimize the use of color print or graphics to the maximum extent possible;

- Minimize size of graphics files; and

- Avoid scanned images

2.8 File Extensions and Naming Conventions

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

Table G-1 File Extensions Type of Application/Files Valid Extensions

Adobe Portable Document Files .pdf Microsoft Word 16 Documents .docx Microsoft Excel 16 Workbook files .xlsx Microsoft Power Point 16 Presentation files .pptx Microsoft Project 16 Project Files .mpp

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

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

Table G-2 Offeror Electronic File Naming Convention Title File naming convention

VOLUME 1 – EXECUTIVE SUMMARY AND CONTRACT

ADMINISTRATION

Vol 1 ES#.docx

Table ES-1 Offeror Summary Table ES-2 Relevant Contract Summary

Table ES-3 Business System Status

Vol 1 ES Tables.xlsx

VOLUME 2 - TECHNICAL Vol 2 Tech#.docx Table T-1 Technical Cross Reference Matrix Vol 2 Tech CRM.xlsx

Integrated Master Schedule (IMS) Vol 2 Tech IMS.mpp Airworthiness Checklist Vol 2 AWC #.docx

VOLUME 3 - PAST PERFORMANCE Vol 3 PP#.docx Table PP-1 Past Performance Contract Data Vol 3 PP-1 PP Con

Data.xlsx Release of Adverse Past Performance Authorization Letters; and/or

Past Performance Point of Contact Information Rel Ad PP Ltr#.pdf;

and/or PP POC Info#.docx

VOLUME 4 – PRICE Vol 4 Price#.docx CLIN Pricing Vol 4 CLIN

Price#.xlsx

ANNEXES

Annex A: Contractual Documentation Support (CDS)*for Past Performance

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

Annex B: Small Business Subcontracting Plan and Table T-2 Small Business Goals

Ann B SBSP.docx

Annex C: DCAA/DCMA Reports, Audits, and Determinations Ann C DCMA.pdf

* Contractual Documentation Support (CDS) is defined as the documents provided by an Offeror (e.g. Statement of Work (SOW), Performance Work Statement (PWS), Statement of Objectives (SOO), Technical Direction Letters (TDL), CDRLs, etc.) to demonstrate an Offeror performed the work.

3.0 PROPOSAL CONTENT AND VOLUMES

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

Each volume and annex of the proposal shall be submitted as an electronic original copy as specified in Table G-3 (Proposal Structure). The Offeror shall submit all electronic copies of the proposal to the Procurement Integrated Enterprise Environment (PIEE) website address provided in Section 4.0 (Proposal Submission and Packaging).

Suggested page counts for each volume, if any, are also specified in Table G-3 (Proposal Structure). The title and table of contents pages, as well as tables, are not included in the suggested page count.

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

Price information, (e.g., dollar values and/or hourly rates) shall not be included in any volume other than Annex B (Small Business Subcontracting Plan) and Volume 4 Price.

Table G-3 Proposal Structure Volume Number Volume/Annex Title Suggested Pages

VOLUME 1 – EXECUTIVE SUMMARY AND CONTRACT

ADMINISTRATION

2 VOLUME 2 - TECHNICAL 75

3 VOLUME 3 - PAST PERFORMANCE 25

4 VOLUME 4 – PRICE As many as needed

Annex A Contractual Documentation Support (CDS) for Past Performance As many as needed

Annex B Small Business Subcontracting Plan and Table T-2 Small Business Goals

As many as needed

Annex C DCAA/DCMA Reports, Audits, and Determinations As many as needed

Table G-4 lists the attachments provided to the Offeror within Section L.

Table G-4 Section L List of Attachments Section L Attachment

Number Electronic File Title Contents

L-1 L-1 Vol 1 ES Tables.xlsx Table ES-1 Offeror Summary, Table ES-2 Relevant Contract Summary for Past Performance, and Table ES-3 Business System Status

L-2 L-2 Vol 2 T-1 CRM.xlsx Table T-1 Technical Cross Reference Matrix L-3 L-3 Vol 3 PPQ.docx Past Performance Questionnaire L-4 L-4 Vol 3 PP-1 PP Cont Data.xlsx Table PP-1 Past Performance Contract Data

L-5 RESERVED – Removed in Amendment

RESERVED – Removed in Amendment 0001

L-6 L-6 Airworthiness Checklist.docx Public Aircraft Operations Airworthiness Checklist

L-7 L-7 Vol 4 Pricing Sheet Vol 4 Pricing Sheet

Annex B Table T-2 Small Business Goals Table T-2 Small Business Goals

4.0 PROPOSAL SUBMISSION AND PACKAGING

All Proposals shall be UNCLASSIFIED.

All volumes of the proposal shall be submitted electronically through the Solicitation Module of the PIEE at https://piee.eb.mil. No other submissions, such as mail, hand-carried, proprietary, or other electronic system (e.g., DOD SAFE) will be evaluated. In the event of a PIEE system outage preventing the offeror from submitting a timely proposal, see paragraph 4.1 below. All proposals received after the exact time specified for receipt shall be treated as late submissions. 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 confirm receipt of proposals and all electronic communications. Screen shots of the submission should also be taken to validate a submission was accepted in the PIEE system.

The submission date for all Volumes shall be no later than the date and time specified in Block 9 of the SF 33 of the RFP.

4.1 In the event of a PIEE System outage within 24 hours of the proposal due date that prevents the offeror from submitting a timely proposal, the Contractor shall immediately notify the Contracting Officer. This notification shall occur prior to the proposal submission deadline and shall be made in writing. The notification may be in conjunction with verbal notification, but verbal notification alone shall not be sufficient. The Offeror shall obtain written approval from the Contracting Officer to submit the proposal via an alternate method described in paragraph

4.2 below. The Contractor shall have 24 hours to provide their proposal upon contracting officer approval. In the event the Contractor does not provide notification to the contracting officer until after the closing date and time, the contracting officer will follow the procedures identified in the Federal Acquisition Regulation (FAR) 15.208.

4.2 The following alternate methods may be utilized:

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

NAWCAD Procurement Group Attn: A2526005 Lauren Wright, Contract Specialist

21983 BUNDY ROAD, BLDG 441 PATUXENT RIVER MD 20670

Solicitation Number: N0042121R0077

4.2.2 Hand Carried Proposals: Hand carried proposals must be delivered to the address above, attention David Silverstone and/or Lauren Wright. If a proposal or amendment is hand carried, the Contractor must have current base access to delivery of the proposal. Without base access, the Contractor may not get beyond the installation security gate to deliver its proposal. Guards are not authorized to accept proposals. Each Volume shall be on a separate CDROM. Delivery time shall be coordinated with the contracting office to ensure availability to sign for the package.

Regardless of which alternate method is used, the Offeror shall package the CD-ROMs in the most efficient manner possible grouping like volumes to the maximum extent possible. Each Volume shall be on a separate CDROM. The package shall include all proposal volumes including the digitally signed document(s) submitted as part of the Cost/Price Volume. The package shall include a packing slip detailing the contents to include the volume number, title, and copy number. Also, the package shall be stamped or marked “For Official Use Only” and “Source Selection Information – See FAR 2.101 and 3.104.”

Offerors may submit questions related to the solicitation to the Government by emailing their questions to lauren.a.wright23.civ@us.navy.mil by 4:00 PM ET on 22 October 2021.

Proposals shall be valid for 180 days from the proposal submission due date.

4.3 CHANGES TO SOLICITATION

For any changes and additional information to the solicitation, please go to website: https://beta.sam.gov/

Search the database for the solicitation number: N0042121R0077

4.4 TECHNICAL LIBRARY

A Technical Library of information directly related to the requirements of this solicitation is available to all Offerors intending to propose as a Prime or JV. The Technical Library will include Memorandum of Agreements (MOAs) for host basing support information, Interface Control Documents (ICDs) for selected interfaces to and from Government Furnished Property, and PWS referenced documents. The Technical Library will be made available through DoD SAFE (Secure Access File Exchange) https://safe.apps.mil/. Contact the Procurement Contracting Officer (PCO) or Contract Specialist (CS) via email to obtain access to the Technical Library via DoD SAFE.

PCO:

David Silverstone Naval Air Warfare Center Aircraft Division Patuxent River, MD 20670 Email: david.s.silverstone.civ@us.navy.mil

CS:

Lauren Wright Naval Air Warfare Center Aircraft Division Patuxent River, MD 20670 Email:lauren.a.wright23.civ@us.navy.mil

PART B SPECIFIC INSTRUCTIONS

Pricing information shall only appear in the Price volume and Annex B.

1.0 VOLUME 1 – EXECUTIVE SUMMARY AND CONTRACT ADMINISTRATION

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-1 Executive Summary Tables (ES-1 (Offeror Summary), ES-2 (Relevant Contract Summary for Past Performance), and ES-3 (Business System Status)).

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

a. Offeror Summary Table

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

(2) For the Past Performance evaluations, contract references that relate to a different CAGE code/DUNS than the proposed entity will be considered if the CAGE code/DUNS was created as a result of a offeror corporate acquisition, reorganization, merger, or other administrative reason and refer to the same division in the same physical location for where the work is being performed or from where the work is being directed In Accordance With (IAW) the proposed roles and responsibilities. All current CAGE Codes/DUNS must appear in Table ES-1 (Offeror Summary) which indicates a commitment of work for those entities. To facilitate the Relevancy determination for Past Performance, the Offeror shall provide a written explanation if multiple CAGE codes/DUNS for the same physical location are applicable to one entity. The written explanation shall detail the distinct roles and responsibilities for entities with different CAGE codes/DUNS at the same physical location for where the work is being performed or from where the work is being directed. The description shall include all changes in the organization as a result of a corporate acquisition, reorganization, merger, or other administrative reason and explain how the changes impact the relevance of any contract references provided.

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

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

Table ES-1 Offeror Summary Offeror:

Entity Name

Physical Location of

Entity

CAGE

Codes/DUNS

Roles and Responsibilities with Work Description

Workshare - % Total Proposed

Cost/Price

Principal Entity Yes or

No?

b. Relevant Contract Summary for Past Performance Table

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

Table ES-2 Relevant Contract Summary for Past Performance Offeror:

Entity Name

Contract Reference

Number

Type

Contract Title

*Description of Changes/Additions from Early

Information

Prime or Joint Venture Company

P1

P2

P3

JV team member A (where applicable)

T1

T2

T3

T4

JV team member N (where applicable)

T5

Subcontractor A

S1

S2

S3

Subcontractor B S4

S5

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

c. Technical

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

d. Contract Administration

The Offeror shall provide the following contract administration information:

(1) Offeror Representatives and Information

The Offeror shall provide a summary sheet comprised of the information listed below for the prime or JV and for each member of a JV, if applicable.

(A) PRIME CONTRACTOR

(i) Business Name;

(ii) Address;

(iii) Principal point of contact for this solicitation (Name, title, phone number, email);

(iv) Secondary point of contact for this solicitation (Name, title, phone number, email);

(v) Individuals authorized to negotiate with the Government and contractually bind the Offeror

(Name, title, phone number, email);

(vi) Establishment Taxpayer Identification Number (TIN);

(vii) TIN of Parent Corporation (if applicable);

(viii) DUNS;

(ix) CAGE code; and

(x) Business size for this effort (large or small);

(B) JV TEAM MEMBERS or other entities that are proposed to perform at least 20.00%

(i) Business Name;

(ii) Address;

(iii) DCMA point of contact and telephone number, if applicable;

(iv) DCAA point of contact and telephone number, if applicable;

(v) DUNS; and

(vi) CAGE code;

(2) Government Agency Information

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

(3) Business System Compliances

The Offeror shall indicate the most recent date, which the Offeror’s cognizant DCMA/DCAA determined the adequacy of the Offeror’s systems (including but not limited to Accounting, Property, and Purchasing). If the Offeror’s systems’ status is not adequate, list the date of the last adequacy determination and the current status of any systems reviews or ongoing audits;

Business Systems Status Table: The Offeror shall complete Table ES-3 (Business Systems Status, Attachment L-

1) showing the current status and or determinations regarding its business systems. If any item is not applicable to the Offeror or for contract performance, so state and justify. If any item has been determined to be unapproved/inadequate outline the potential impact on contract execution, mitigation plan, and correction plan.

Submit relevant DCAA/DCMA reports, audits, and determinations in Annex C: DCAA/DCMA Reports, Audits, and Determinations.

Table ES-3 Business Systems Status

Business System

(D)FAR

Status

Comments Accounting System FAR 16.301-3 Estimating System DFARS 215.407-5 CAS Disclosure Statements FAR 30.202-6(b) Purchasing System FAR 44.3 Property Management System FAR 45.105

This information is to facilitate the PCO’s responsibility determination and any need to discuss information related to this does not constitute discussions.

(4) 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 as part of Annex B ((Small Business Subcontracting Plan).

The SB Subcontracting Plan of the successful Offeror(s) will be reviewed and approved by the PCO prior to contract award as part of the responsibility determination. See FAR 19.702(a)(1) Statutory requirements, regarding failure of the apparent successful Offeror to negotiate and submit a SB Subcontracting Plan or submit a Comprehensive or Commercial SB Subcontracting Plan acceptable to the Contracting Officer. The successful Offeror’s approved SB Subcontracting Plan will be incorporated into the resultant contract and contractor performance against the plan will be monitored by the Government during contract execution.

The Offeror shall describe or provide documentation of how they will meet the SB Goal of 5% of total proposed subcontracted dollars. In addition, describe the Offeror’s approach for how the 5% of total proposed subcontracted dollars will be allocated to the Socioeconomic SB Concerns.

(5) Terms and Conditions

Offerors shall not take exception to contract terms and conditions and shall provide the following statement: “No exceptions are taken to the terms and conditions or any requirement of the solicitation.” Any exceptions will make the proposal ineligible for award.

(6) Joint Ventures

If proposing as a JV, the Offeror shall provide a copy of the JV agreement. IAW 13 CFR 121.103(h), a JV must be in writing and must do business under its own name; must be identified as a JV in the System for Award Management (SAM); may be in the form of a formal or informal partnership or exist as a separate limited liability company or other separate legal entity; and, if it exists as a formal separate legal entity, may not be populated with individuals intended to perform contracts awarded to the JV (i.e., the JV may have its own separate employees to perform administrative functions, but may not have its own separate employees to perform contracts awarded to the

JV).

(7) Contract Documents

The Offeror shall provide the following documents within this section:

(A) Original signed SF33 (Solicitation, Offer, and Award) cover page of the solicitation and a signed SF30 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 SF33 Block 12 “fill-in” (proposal validity date) shall be completed with an amount of no less than 180 days after submission due date;

(B) Signed Representations, Certifications, and Acknowledgements (Section K); and,

(C) Completed copy of all FAR, DFARS, NAVAIR, special clauses, and provisions requiring contractor fill-ins

2.0 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 Volume 2 Table T-1 Technical Cross Reference Matrix (CRM), Attachment L-6 Airworthiness Checklist, Annex B – Small Business Subcontracting Plan, Table T-2 Small Business Goals.

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

Table T-1 Cross Reference Matrix Section L –

Proposal Instructions Volume or Paragraph Numbers

Section L - Proposal

Instructions Volume or

Paragraph Title

RFP

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

CLIN(s)

Offeror’s Proposal

Volume 2 Technical

2.1

Stand-up Attachment 1, PWS

Paragraph 3.1.3; Section M - Part B 1.0 Technical

2.2

Aircraft Performance Requirements

Attachment 1, PWS Paragraph 3.1; Section M -

Part B 1.0 Technical

0002, 0003, 0004

2.3 Hoist Capability

Requirements

Attachment 1, PWS Paragraph 3.1; Section M -

Part B 1.0 Technical

0002,

2.4 Airworthiness Data Attachment 1, PWS

Paragraph 3.3;

Section M - Part B 1.0 Technical

2.5 Aircraft Support Attachment 1, PWS

Paragraphs 3.4 and 3.7;

Section M - Part B 1.0

Technical

0002, 0003,

2.6 Aircraft Availability Attachment 1, PWS

Paragraphs 3.4 and 3.7;

Section M - Part B 1.0

Technical

0002, 0003,

2.7 Small Business

Management

Section K; Section M - Part B 1.0 Technical

0001, 0002, In this volume, provide the information described below:

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

Throughout the Technical Volume, the Offeror should identify any proposed capability, approach or feature that exceeds a requirement or provides merit associated with a performance or operational benefit to the Government.

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

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

2.1 Capability Stand-Up

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

2.1.2. Aircraft Acquisition and Import Plan: The Offeror shall provide an acquisition and import plan, for each aircraft proposed for this contract. The Offeror shall submit proof of ownership or signed lease agreements by serial number. The Acquisition and import plan shall include the dates of all major milestones, for example date of purchase, date of shipping, delivery schedules, etc.

2.1.3. 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.4. Aircraft modification plan: For each aircraft proposed that requires modification to meet the performance requirements of PWS paragraphs 3.1.1 and 3.1.2, 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.5. Master Schedule to achieve Full Operational Capability (FOC): The Offeror shall submit a proposed master schedule for completion of all stand-up requirements, including the date that they will be able to provide full performance of services under CLINs 0002, 0003 and 0004 including availability of all aircraft for tasking. The Offeror shall include a minimum of 45 days for Government processing of NAVAIR IFC(s). The schedule shall contain, at a minimum, the milestones provided in PWS paragraph 3.1.4 and all other significant events required to obtain FOC, such as aircraft acquisition events (customs, delivery, contract dates), completion of aircraft modifications including providers, submission of IFC data package under CDRL A001, assets transportation, completion of stand-up of the maintenance organizations, completion of aircrew hiring, required training completion, all data requirements listed in the Airworthiness checklist, etc. The Offeror shall submit a draft of the IMS (CDRL A008) as part of their proposal for CLIN 0001.

2.1.5.1 Six Months to FOC: Aircraft shall be fully operational no later than six (6) months from the effective date of the initial TO containing CLIN 0001. The offeror shall provide a schedule for meeting this six (6) month fully operational requirement.

2.1.6. Ground and Flight Operating Procedures (GOPS/FOPS): The Offeror shall submit a plan detailing the schedule and milestones for updating existing Government approved GOPS and FOPS. 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 paragraphs 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 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.

2.2.1 Offerors shall provide the following performance characteristics for all aircraft proposed for this effort.

Medium Lift Aircraft Performance Characteristics

Heavy Lift Aircraft Performance Characteristics

Speed/Altitude: Speed/Altitude:

Service Ceiling: Service Ceiling:

Service Radius: Service Radius:

Time On Station: Time On Station:

Configuration/Special Equipment:

Configuration/Special Equipment:

Substitution of Aircraft: Substitution of Aircraft:

Hoisting Capability: Hoisting Capability:

External Lifting Capacity:

External Lifting Capacity:

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

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

2.4 Airworthiness Data

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

Offerors shall provide the following documentation:

2.4.1 Airworthiness Certification Plan: All aircraft under this contract will require a NAVAIR issued IFC. The Offeror shall submit a plan detailing its approach to obtaining a NAVAIR IFC In Accordance With (IAW) PWS paragraph 3.3, which shall include the original certification authority such as the specific military service, the source of supporting data such as the Original Equipment Manufacturer/Manufacturing (OEM), and major milestones. This requirement can be satisfied by submitting an existing active NAVAIR IFC, United States Air Force (USAF) Military Flight Release (MFR), or United States Army Airworthiness Release (AWR), if the aircraft can satisfy the requirements of this solicitation within the limits of the submitted IFC, MFR, or AWR.

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

2.4.3. Parts Life Tracking Process and Status Report:

2.4.3.1. The Offeror shall demonstrate that all parts with OEM/military-defined life limits have been identified, and the Offeror shall submit a plan for replacing those parts on/before their expiration dates.

2.4.3.2. The Offeror shall include for each aircraft type proposed, the complete list of the parts, including structural components, for which the OEM or prior military user has established a life limit. The Offeror shall include for each life-limited part: (a) the flight hours, cycles, calendar date, or other limiting parameters, which require removal or overhaul (b) the organization(s) that will be used to acquire or overhaul the replacement parts.

2.4.4. Aircraft Modifications Status Report: If submitted with the proposal, an active NAVAIR IFC satisfies this requirement. If the proposed aircraft configuration does not have an active NAVAIR IFC, the Offeror must submit the following:

2.4.4.1. The Offeror shall include for each individual aircraft proposed a list of all currently installed modifications and configuration changes made after the initial Federal Aviation Administration (FAA) certification or after the aircraft was retired from military use.

2.4.4.2. The Offeror shall demonstrate the airworthiness of each aircraft modification made after the initial FAA certification or after the aircraft was retired from military use IAW PWS paragraph 3.3. For each modification, the Offeror shall provide a copy of the airworthiness certification from the OEM, FAA, military service, or alternatively, the engineering substantiation report that clearly states that the modification is airworthy.

2.4.5. Maintenance History Report: This requirement can be satisfied by submitting an existing active NAVAIR IFC, USAF MFR, or US Army AWR, if the aircraft can satisfy the requirements of this solicitation within the limits of the submitted IFC, MFR, or AWR. If the proposed aircraft configuration does not have an active NAVAIR IFC, USAF MFR, or US Army AWR, the Offeror must submit the following:

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

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

2.4.6. Fatigue Life Status report:

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

2.4.6.2. The Offeror shall provide for each individual aircraft: (a) the current total counts on tracked items (e.g.

flight hours/landings) that have been accumulated since the aircraft was manufactured, and (b) the means used to determine the current accumulated counts since the aircraft was manufactured.

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

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.

2.7. Small Business Management

2.7.1. SB Utilization Strategy: All Offerors (Large and SB) shall address their strategies for utilizing SB Concerns in the performance of this contract, whether as a JV, teaming arrangement or subcontractor. SB Offerors may meet this requirement using work they perform themselves. For purposes of this solicitation, the term SB Concern shall also include the subcategories of Veteran-Owned Small Business (VOSB), Service-Disabled Veteran-Owned Small Business (SDVOSB), HUBZone SB (HUBZone), Small Disadvantaged Business (SDB), and Women-Owned Small Business (WOSB). Each subcategory of SB shall be addressed. This strategy is separate from, but shall be consistent with, the SB Subcontracting Plan, if such a Plan is required. The Offeror shall describe or provide documentation of how they will meet the SB Goal of 5% of total proposed subcontracted dollars. In addition, describe the Offeror’s approach for how the 5% of total proposed subcontracted dollars will be allocated to the Socioeconomic SB Concerns. Offerors are advised that while the SB Subcontracting Plan must be submitted to be eligible for award, where applicable, the acceptability of the content of that plan is part of the responsibility determination assessment and not part of the evaluation. In describing its SB Utilization Strategy for this solicitation, the Offeror shall, as applicable:

(1) Describe its approach to identifying SB Concerns;

(2) Describe the extent of participation of SB Concerns on this contract, including a detailed description of the supplies and services for each SB Concern subcategory, and the complexity and variety of the work SB Concerns are to perform. For each SB Concern specifically identified in the proposal, provide the SB Concern's CAGE Code, or, if the SB Concern is not registered in the System for Award Management (SAM), at a minimum provide evidence of self-certification in accordance FAR 19.703(b) as an SB Concern. Where possible, provide documentation regarding enforceable commitments to utilize each SB Concern.

(3) Identify what processes have been implemented to correct past inabilities to meet proposed goals and any validated improvements;

(4) Describe its specific efforts and new, contract-specific initiatives to ensure the resulting contract meets or exceeds proposed goals. These efforts shall include, but are not limited to: sponsoring program specific outreach events and industry conferences, establishing Mentor-Protégé relationships and market research using websites such as the NAVAIR Office of Small Business Programs website [http://www.navair.navy.mil/osbp] and the Small Business Administration’s Dynamic Small Business Search tool (http://dsbs.sba.gov/dsbs/search/dsp_dsbs.cfm) to locate SB concerns;

(5) Provide goals, expressed as dollars and percentages of total contract value and…