HEEWJ_Amendment-2_Modification_Document.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 make changes in sections A amd L for proposal submission and delete clauses in Section I.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 37

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

16C. DATE SIGNED

BY 20-May-2019

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 N0042118R0009

X 9B. DATED (SEE ITEM 11)

21-Mar-2019

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

(a) By completing Items 8 and 15, and returning 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

20-May-2019

CODE

NAVAL AIR WARFARE CENTER AD-PAX-

CODE 2.5.1.13

21983 BUNDY RD

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:

N0042118R0009

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time 13-Jun-2019 01:00 PM has been added.

The solicitation issue date has changed from 21-Mar-2019 to 20-May-2019.

The depository location See Section L has been added.

The number of offeror copies required 1 has been added.

The following have been modified:

SECTION A INFORMATION

POINTS OF CONTACT

CONTRACT SPECIALIST: LCDR Brij Mohan

TELEPHONE NUMBER: (717) 605-3542

EMAIL ADDRESS: brij.mohan1@navy.mil

PCO: Michael J. Coon

TELEPHONE NUMBER: 301-757-7114

EMAIL ADDRESS: michael.coon@navy.mil

(1) This acquisition is a full and open competition that will result in placement of a Single-Award Indefinite Delivery, Indefinite Quantity (IDIQ) contract.

(2) The Product/Service Code (PSC) for this procurement is V121

TRANSPORTATION/TRAVEL/RELOCATION - TRANSPORTATION: AIR CHARTER.

(3) The resulting IDIQ contract will have a Four-Year and 364-Day ordering period; however, any task order issued shall not have a period of performance that extends past the final day of the ordering period of this contract.

(4) The Contractor will be required to have a SECRET Facility clearance upon award. Security clearance requirements are identified in Section C – Performance-Based Work Statement (PBWS), and Attachment

(1) – DD Form 254.

(5) The proposed months to complete stand up for CLINs 0001, 0002, 0003, 0007 and 0008 are at the

Contractor’s discretion based on its technical strategy provided the proposed months comply with the not-to exceed values.

(6) The months included in CLINs 0001, 0002, 0003 are not-to-exceed values, however the Contractor may propose less months to complete these CLINs if desired. Be advised, however, that the final months incorporated into the contract will be based on the winning Contractor’s proposal and changed to those values throughout the contractual document. The total number of months for CLINs 0001, 0002 and 0003 shall not exceed 16 months for the total effort. To achieve Initial Operational Capability (IOC) and Full Operational Capability (FOC), the contractor shall deliver capability IAW sections F.

(7) The months included in CLIN 0007 shall correspond to the months proposed for the longest lead time stand up CLIN for CLINs 0001, 0002 and/or 0003, not to exceed 16 months.

(8) The months included in CLIN 0008 shall correspond to the months proposed for contract performance after total stand up capability (completion of CLINs 0001, 0002, and 0003) is achieved. This CLIN would be either 44 months (if the full stand up capability of 16 months is proposed) or it could be more than 44 months if the stand up capability for all three CLINS (0001, 0002, and 0003) is less than 16 months.

CLINs 0007 and 0008 when combined, shall not exceed a total of 60 months.

(9) Proposals shall be submitted no later than Thursday 13 June 2019 by 13:00 EST. Proposals shall be valid for 180 days from submission date. (See Section L)

Note: Amendment 2 makes the following changes/additions which will be highlighted throughout.

1. Section A number (9) and Section L, 4.0 Proposal submission and packaging, Paragraph 4.1 Proposal submission, Proposal submission due date and time.

2. Section L, 4.0 Proposal submission and packaging, Paragraph 4.1 Proposal submission, building number and fill in information for clauses 52.232-2 and 5252.233-9500.

3. Section I, Delete clauses 52.211-11 and 52.245-2.

SECTION I - CONTRACT CLAUSES

The following have been deleted:

52.211-11 Liquidated Damages--Supplies, Services, or Research and

Development

SEP 2000

52.245-2 Government Property Installation Operation Services APR 2012

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

DESCRIPTION

L – 1 CONTENT OF PROPOSALS (SERVICES) (June 2017)

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

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

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

Throughout these instructions, “Offeror” is defined as the prime contractor with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. A “Joint Venture” (JV) is a partnership or teaming arrangement that is formed for the purpose of responding to this solicitation when the prime contractor consists of more than one legal entity. “JV Team Members” are the entities that make up a Joint Venture. The term “entity” is used to mean any or all of the following: prime contractor, JV, JV team members, any subcontractor, and corporate parent, division, subsidiary, or affiliate (e.g., any contractor with a different CAGE Code/DUNS than the Offeror).

The following entities are defined as principal entities and only principal entities will be used in the past performance and corporate experience evaluations: (a) the prime contractor; (b) JV Team Members; (c) other entities that are proposed to perform at least 20% of the proposed total price for the contract or (d) entities that are proposed to perform a critical function in the performance of the resulting contract. Critical functions include providing primarily EW design services or primarily EW training services, or aircraft services. Offerors are advised that in order to demonstrate work commitment, each principal entity must be identified in Volume 5 Price and associated with a commensurate dollar value.

Description of Relevancy process – Offerors are advised that relevancy determination is performed in the Past Performance evaluation. See Section L Part B paragraph 4.3 for details. Only contracts determined to be Very Relevant or Somewhat Relevant in the Past Performance evaluation will be further evaluated for Corporate Experience or Past Performance.

2.0 PROPOSAL FORMAT AND SUBMISSION

2.1 Electronic Submission of Proposal

This section is intended to provide information to the Offeror 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. Use of the software and procedures described in this section will reduce the amount of time and effort needed to receive and install proposals onto the electronic evaluation system, and will ensure that the proposals received are suitable for reading electronically.

2.1.1 Electronic Proposal Media

The Offeror shall submit all volumes of its proposal electronically on DVD-ROM(s) compatible with the operating system and applications defined in Section 2.1.2 (Operating System and Applications). The Offeror should put as much proposal material as possible on each DVD-ROM, keeping the portions of the proposal that contain pricing information on separate DVD-ROM(s) from the portions of the proposal that do not contain pricing information.

For this solicitation, Annex B (Small Business Subcontracting Plan); Volume 5 Price; contain price information and should be delivered on separate DVD-ROM(s) from the remainder of the proposal.

Table G-3 (Proposal Structure) identifies the proposal structure for each volume. The Offeror should submit two sets of DVD-ROMs. The first set of DVD-ROM disks should be marked "Original” and the second set of DVD-

ROM disks should be marked "Backup”. The sets of DVD-ROM disks should be clearly marked with the Offeror's name and address, the point of contact's name and phone number, the proposal volumes contained therein, and “Source Selection Information – See FAR 2.101 and 3.104”.

2.1.2 Operating System and Applications

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

2.1.3 Hyperlinks

Offerors shall not use hyperlinks in proposal volumes.

2.1.4 Virus Free Electronic Submission

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

2.1.5 Multimedia

The Offeror should not embed sound or video (e.g., MPEG) files within the proposal submission.

2.1.6 Graphics

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

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

b. Minimize size of graphics files; and

c. Avoid scanned images.

2.1.7 File Naming Conventions

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

Table G-1 File Extensions

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

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

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

Table G-2 Offeror Electronic File Naming Convention

Volume Number

Title File naming convention

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

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

2 Corporate Experience Vol 2 CE#.docx Table CE-1 Applicable Contracts For CE Elements Vol 2 CE ACE.xlsx Table CE-2 Evaluation Area Summary Vol 2 CE EAS.xlsx 3 Technical Vol 3 Tech#.docx Technical Cross Reference Matrix Vol 3 Tech CRM.xlsx List other attachments here 4 Past Performance Vol 4 PP#.docx Table PP-1 Past Performance Contract Data Vol 4 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

5 Price Vol 5 Price#.docx Annexes

Annex A Relevant Portions of Final Versions of Previous SOW/PWSs for Past Performance and Corporate Experience

Ann A Rel SOW PWSs#.pdf and Ann A Rel SOW PWSs #.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 Ann B SBSP.docx Annex C Technical Data Ann C Tech.docx

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 original and one additional electronic copy as specified in Table G-3 (Proposal Structure). The Offeror shall submit all electronic copies of the proposal to the address provided in Section 4.0 (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, such as tables provided in response to RFP requirements and from the Section L attachments, 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. Each Annex should include an index or table of contents to clearly identify what information is included in the annex and where the information is located. Additionally, the individual subcontracting reports for the past performance volume is 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); Volume 5 Price.

Table G-3 Proposal Structure

Volume Number

Volume/Annex Title Suggested

Pages

1 EXECUTIVE SUMMARY 15

2 CORPORATE EXPERIENCE 25

3 TECHNICAL 75

4 PAST PERFORMANCE 50

5 PRICE As Needed

Annex A Relevant Portions of Final Versions of Previous SOO/SOW/PWSs/Other Supporting Documentation for Past Performance and Corporate Experience

As Needed

Annex B Small Business Subcontracting Plan As Needed Annex C Technical Data As Needed

Table G-4 Section L List of Attachments

Section L Attachment Number Electronic File Title Attachment Name L-1 Vol 1 ES Tables Table ES-1 Offeror Summary, Table ES-2 Relevant Contract Summary, and Table ES-3 Business Systems Status

L-2 Vol 2 CE Tables Table CE-1 Applicable Contracts for CE Elements and Table CE-2 Evaluation Area Summary

L-3 Vol 3 T-1 CRM Table T-1 Cross Reference Matrix L-4 Vol 4 HEEWJ PPQ Past Performance Questionnaire L-5 Vol 4 PP-1 PP Cont Data Table PP-1 Past Performance

Contract Data L-6 Historical Travel Information Historical Travel Information

4.0 PROPOSAL SUBMISSION AND PACKAGING

4.1 Proposal Submission

Clearly mark all packages with the solicitation number. The submission date for all Volumes of the proposal shall be no later than the date and time specified in Block 9 of Standard Form 33 (Solicitation, Offer and Award) of the solicitation.

The Government requests an advance electronic copy on a DVD-ROM of Table ES-1 (Offeror’s Summary), Table ES-2 (Relevant Contract Summary); Table PP-1 (Past Performance Contract Data); Table CE-1 (Corporate

Experience Element - Contract Reference Matrix); Table CE-2 (Evaluation Area Summary) and Annex A (Final Versions of Previous SOW/PWSs/Other Supporting Documentation for Past Performance and Corporate Experience) be submitted two weeks prior to the submission date/time specified on Standard Form 33 (Block 9). In the official electronic proposal submission, please indicate any changes made to the information delivered two weeks early in the submission provided on the date and time specified in Block 9 of Standard Form 33 of the solicitation. If no changes are made, please state so at the beginning of Volume 1 (Executive Summary), Volume 2 (Corporate Experience), and Volume 4 (Past Performance).

Method of delivery, such as by hand, United States Postal Service or commercial carrier, shall be coordinated with Michael Coon, the Procuring Contracting Officer (PCO) (301) 757-7114 and/or contract specialist listed below.

Electronic proposals on DVD-ROM shall be submitted using the address provided below. The initial Proposal shall not be submitted electronically via email.

NAWCAD

ATTN: Mr. Brij Mohan Code: AIR- 2.5.1.13 Solicitation Number: N00421-18-R-0009 Street Address: 21983 Bundy Road, Bldg 3272 Patuxent River, MD 20670

Proposals shall be submitted no later than Thursday 13 June 2019 by 13:00 EST. Proposals shall be valid for 180 days from submission date

4.2 Proposal Packaging

The Offerors shall package the DVD-ROMs containing the electronic proposals in cartons/envelopes or equivalent packaging containers in the most efficient manner possible. Each package should identify its contents by including a packing slip detailing the original DVD-ROM and copies for each proposal volume. The outside of the package should be plain and shall contain only pertinent shipping /mailing information. The inside package shall be stamped or marked ― “For Official Use Only”; and “Source Selection Information – See FAR-

2.101 and 3.104”, for the intended recipient identified in 4.1 (Proposal Submission). The original set of DVD- ROM electronic proposals should be marked for NAWCAD PCO, AIR-2.5.1.13 identified in section 4.1 (Proposal Submission). The original set shall include all proposal volumes on DVD-ROM, a completed and original signed Standard Form 33; acknowledgement of all solicitation amendments, if applicable; and Representations, Certifications and Other Statements of Offerors or Respondents (Section K of this solicitation) and other applicable fill-ins. Note: Any documents, which contain price data, shall be on a separate DVD-ROM disk(s) from the non-price proposal information.

4.3 Changes to Solicitation

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

Search the database for the solicitation number N00421-18-R-0009.

4.4 Technical Library

In accordance with the solicitation, 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 Joint Venture.

PART B SPECIFIC INSTRUCTIONS

1.0 VOLUME 1 – EXECUTIVE SUMMARY

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) and ES-2 (Relevant Contract Summary))

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

a. Offeror Summary Table

(1) The Offeror shall complete Table ES-1 (Offeror Summary), provided in Attachment L-1 (Executive

Summary Tables), according to the instructions within the attachment, and submit it within this section and as a separate electronic file. This table summarizes the Offeror and its entities’ proposed type and level of work, indicating a commitment to that effort during contract performance. Offerors are advised that in order to demonstrate work commitment, each entity identified in Table ES-1 (Offeror Summary) must be identified in Volume 5 (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 5 (Price).

(2) For the Corporate Experience and 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 corporate acquisition, reorganization, merger, or other administrative reason and refer to the same division in the same physical location for where the work is being performed or from where the work is being directed in accordance with the proposed roles and responsibilities. All current CAGE Codes/DUNS must appear in Table ES-1(Offeror Summary Table) which indicates a commitment of work for those entities. To facilitate the Relevancy determination for Past Performance and Corporate Experience, 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 Price

Principal Entity Yes or No?

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

b. Relevant Contract Summary Table The Offeror shall complete the Table ES-2 (Relevant Contract Summary) provided in Attachment L-1 (Executive Summary Tables), for all contracts proposed as relevant for Past Performance and/or Corporate Experience 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) shall be used in completing Volume 2 Table CE-1 (Applicable Contracts for CE Elements) and Volume 4 Table PP-1 (Past Performance Contract Data). For example, the contracts identified as P1, T1, S1, or C1 in the Relevant Contract Summary Table are the same P1, T1, S1, or C1 contracts identified in the Past Performance Contract Data Table, which are the same P1, T1, S1, or C1 contracts identified in Table CE-1 (Applicable Contracts for CE Elements).

Table ES-2 Relevant Contract Summary for Corporate Experience and Past Performance

Entity Name Contract Reference

Contract Number

Contract Type

Contract Title *Description of

Changes/Additions from Early Information

Prime or Joint Venture Company

P1

P2

P3

JV team member A (where applicable)

T1

T2

T3

T4

JV team member N (where applicable)

T5

Subcontractor A

S1

S2

S3

Subcontractor B

S4

S5

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

c. Technical

The Offeror shall provide a succinct summary of what is proposed for each element, 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 entities identified in Table ES-1 (Offeror Summary).

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;

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

xi. Percentage of work and role and responsibility performing.

b) ALL OTHER ENTITIES

i. Business Name; Address; DCMA point of contact and telephone number, if applicable;

ii. DCAA point of contact and telephone number, if applicable;

iii. DUNS;

iv. CAGE code; and

v. Percentage of work and role and responsibility performing.

(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 that 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) 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.

Table ES-3 Business Systems Status

Business System

(D)FAR

Reference

Status

Comments

Accounting System 16.301-3 Estimating System 215.407-5 CAS Disclosure Statements 30.202-6(b) Purchasing System 44.3 Earned Value Management System 242.302(S-71) Property Management System 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 Small Business

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 as well as 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 Subcontracting Plan will be incorporated into the resultant contract and contractor performance against the plan will be monitored by the Government during contract execution.

(5) Contract Documents:

(1) 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 SF-33 Block 12 “fill-in” (proposal validity date) shall be completed IAW Section A (Solicitation/Contract Form);

(2) Signed Representations, Certifications, and Acknowledgements or Online Representations and Certifications Application (ORCA) reference;

(3) A complete copy of all FAR, DFARS, NAVAIR, and special clauses and provisions requiring contractor fill-ins and

(4) Section H (including any other proposed clauses. All Offeror proposed H Clauses, or other contract additions, in full text, if applicable. If an Offeror proposes to perform work above or not included in this solicitation (e.g., including, but not limited to, an aspect of a proposal that the Offeror believes the Government should evaluate as a strength), the Offeror must include contractually binding additions for the contract award document. These additions may be H clauses, additions to the PBWS, additions to the CDRLs (if data is to be delivered), or other additions. For the H clause, it must state as a minimum: a) the Offeror’s performance responsibilities; b) the performance periods, including delivery dates, if applicable;

and, c) the financial responsibilities and liabilities of the Offeror. The Offeror’s proposal should include information regarding any Government performance and financial responsibilities incurred as a result of any proposed H clause or other proposed additions for the contract award document.

(5) A complete copy of the Small Business Subcontracting Plan provided in Annex B ((Small Business Subcontracting Plan) or a reference to the Small Business Subcontracting Plan provided in Annex B, that will be attached to the contract upon award.

2.0 VOLUME 2 – CORPORATE EXPERIENCE

Notes:

(1) Relevancy – The relevancy of submitted Corporate Experience and Past Performance Contract References will be determined in the Past Performance evaluation through the process discussed in subparagraphs 4.2 and 4.3 (below). Only contracts determined to be Very Relevant or Somewhat Relevant in the Past Performance evaluation will be further evaluated for Corporate Experience or Past Performance.

(2) This volume shall not contain any reference to the price aspects of the offer.

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

Attachment L-2 Corporate Experience Tables (Table CE-1 Applicable Contracts for Each Corporate

Experience Element, and Table CE-2 Evaluation Area Summary)

The Offeror shall complete Table CE-1 (Applicable Contracts for Each Corporate Experience Element) below, provided in Attachment L-2, according to the instructions within the attachment, and submit it as the first section of Volume 2 (Corporate Experience) and as a separate electronic file. Within Table CE-1 (Applicable Contracts for Each Corporate Experience Element) the Offeror shall identify the relevant portions (sections and paragraphs) of the contract reference’s SOW/PWS or other supporting solicitation/contract documentation to clearly identify how Corporate Experience performing past tasks are similar to evaluation elements 2.2.1 through 2.2.4. If the Offeror performed as a subcontractor for a contact reference, identify relevant portions (sections and paragraphs) of the SOW/PWS or other documentation of the agreement between the prime and subcontractor. Only contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing this Volume and all contract references shall be numbered the same throughout all of the Offeror’s proposal volumes (i.e., the contracts identified as P1, S1, T1, etc.). All contracts evaluated for Corporate Experience will also be evaluated for Past Performance.

Table CE-1 Applicable Contracts for Each Corporate Experience Element

1 Offeror Name

2 Entity Name

3 Contract Reference

4 Title of Contract

5 Contract/TO/DO/Subcontract Number

2.2.1 Obtaining Flight Clearances Applicable PWS/SOW Section/Paragraph from Contract Reference Applicable to Obtaining Flight Clearances

2.2.2 Experience using EW Applicable PWS/SOW Section/Paragraph from Contract Reference Applicable to Experience using EW

2.2.3 Ground Operations Procedures (GOPs)/

Flight Operations Procedures (FOPs)

Applicable PWS/SOW Section/Paragraph from Contract Reference Applicable to Ground Operations Procedures (GOPs)/ Flight Operations Procedures (FOPs)

2.2.4 Experience using the same FAA

Aircraft class and type as proposed for CAS

HEEWJ

Applicable PWS/SOW Section/Paragraph from Contract Reference Applicable to Experience using the same FAA Aircraft class and type as proposed for CAS HEEWJ

For this Volume, the Offeror shall identify relevant contracts, or those portions of a relevant contract, whose performance is within five years of the RFP release date and contains efforts similar to those efforts required by this solicitation for the principal entities identified in Table ES-1 (Offeror Summary). The experience provided shall only relate to Corporate Experience, which is the experience gained through contracted work. The experience of the principal entities personnel or any personnel will not be considered in this Corporate Experience evaluation. If proposing as a JV team, Offerors should include the Corporate Experience of the JV as a whole, as well as the Corporate Experience for each JV team member. In general, more recent Corporate Experience will be considered a better indicator of future performance than older Corporate Experience.

Corporate experience information provided shall be: for similar programs/contracts (as defined in section 2.2 (Evaluation Elements)); at the same physical location (e.g., with the same CAGE code/DUNS) as referenced in Table ES-1 (Offeror Summary); and related to the roles and responsibilities identified in Table ES-1 (Offeror Summary). For example, if a principal entity is assigned to perform Non-Destructive Test/Inspection and submits information regarding software development, the software development experience would not be relevant as it was not proposed as an assigned role/responsibility for the principal entity.

For a discussion on CAGE Code/DUNS, refer to Section 1.0 Volume 1 (Executive Summary). Offerors should be advised that the CAGE Code/DUNS for each referenced contract is considered as part of the Relevancy determination, which determines if the contract reference will be included in the Past Performance and Corporate Experience evaluations. Note: Any information regarding CAGE Code/DUNS should be included within Volume 1 (Executive Summary) and does not need to be repeated here.

Contract relevancy will be determined in the Past Performance evaluation. Only contract references identified in the Volume 2 (Corporate Experience) and determined relevant in the past performance evaluation will be evaluated in Corporate Experience.

2.1 Evaluation Area Summary Table

The Offeror shall complete Table CE-2 (Evaluation Area Summary), provided in Attachment L-2 (Corporate Experience Tables). Table CE-2 (Evaluation Area Summary) should provide a list of the Prime’s and JV team members’ referenced contracts that provide examples of corporate experience performing tasks similar to those required for evaluation areas 2.2.1 through 2.2.4. Mark the cells in Table CE-2 with an “X” where the referenced contract included the experience indicated in evaluation areas 2.2.1 through 2.2.4.

Table CE-2 Evaluation Area Summary

C on tr ac t R ef er en C on tr ac t

N um be r 2.2.1

Obtaining Flight Clearances

2.2.2 Experience Using EW

2.2.3 GOPs/FOPs

2.2.4 Experience using same FAA Aircraft class and

type

N

V A

IR

F li gh t C le ar an ce s

O th er D

O D

F lig ht C le ar an ce s

O th er G ov er nm en t A ge nc y

C le ar an ce s

E S

D R

FM

J am m in g

E xp er ie nc e in d ev el op in g G

O P s/ F

O P s

T ra in in g re qu ir ed p er so nn el to en su re c om pl ia nc e w ith G

O Ps

M ai nt ai ni ng a nd u pd at in g G

O P s to p er fo rm a ir v eh ic le m od if ic at io n an d in st al la tio ns

O pe ra tin g an d m ai nt ai ni ng sa m e ai rc ra ft c la ss a nd ty pe

F

A A ir w or th in es s D ir ec ti ve s an d O

E M

S er vi ce

B ul le ti ns

L og is ti cs a nd m ai nt en an ce su pp or t i n re m ot e an d no n-re m ot e lo ca tio ns

P1 Pn T1 Tn

2.2 Evaluation Elements

The Offeror shall provide a comparative analysis between the principal entities’ roles and responsibilities identified in Table ES-1 (Offeror Summary) and the Corporate Experience requested in subparagraphs 2.2.1 through 2.2.4. In a paragraph to a page per contract reference, for each element in 2.2.1 through 2.2.4 below, describe the extent to which previous Corporate Experience performing requirements similar to this solicitation can be leveraged in future performance of work. Similarity is the extent to which the Offeror’s contract references (or documented work efforts) correspond to the specific tasks required by this solicitation. At a minimum, address the specific items within each element, however, when drafting each element description, consider the contract reference’s period of performance, the amount of time in performance, recency of the performance, frequency of the applicable activities, the technical nature of the work in comparison to the proposed effort, and the entity’s proposed role and responsibility.

2.2.1 Obtaining Flight Clearances

The Offeror shall demonstrate its experience in obtaining NAVAIR Flight Clearances IAW NAVAIR Instruction 13034.1, other DoD (e.g. USAF, U.S. Army), or Other Government Agency (OGA) (non-commercial) Clearances.

The Offeror shall provide the initial and most recent approved flight clearances, military flight releases, or airworthiness releases for proposed contract references. Therefore, the Offeror may submit up to two clearances per contract reference.

2.2.2 Experience using EW

The Offeror shall demonstrate its experience in EW operations similar to those required by the HEEWJ effort (PBWS para xxx). EW operations will include Electronic Warfare Support (ES), and DRFM jamming. ES experience is defined as low power signal detection and signal identification. DRFM jamming experience is defined as programming and/or adaptive programming of DRFM jammers against radar systems.

2.2.3 Ground Operations Procedures (GOPs)/ Flight Operations Procedures (FOPs)

The Offeror shall demonstrate its experience in developing GOPs/FOPs, training required personnel to ensure compliance with GOPs, and maintaining and updating those GOPs to perform air vehicle modification and installations within the scope of contract activities in accordance with DCMA INST 8210.1. Offerors must also demonstrate GOPs/FOPs were approved by providing the cover sheet signed by the Government Flight Representative (GFR) for each applicable contract referenced.

2.2.4 Experience using the same FAA Aircraft class and type as proposed for CAS HEEWJ

The Offeror shall demonstrate its experience in operating and maintaining the same aircraft class and type proposed for this effort. This will include FAA Airworthiness Directives and OEM Service Bulletins, logistics and maintenance support in remote and non-remote locations.

3.0 VOLUME 3 - 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-3 Volume 3 Table T-1 Cross Reference Matrix (CRM)

The Offeror shall complete Table T-1 (Technical CRM), provided in Attachment L-3 and submit it as the first page of Volume 3 (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)

PBWS

paragraph

CLIN Offeror’s Proposal Reference

Volume 3 Technical

3.1 Aircraft

Performance

3.2 Airworthiness

3.3 Aircraft Support

3.4 Technical

Approach

3.5 Small Business

Utilization Strategy

In this volume, provide the information described below:

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

The Offeror should also identify any proposed capability, approach or feature that reduces risk inherent in the program. Specifically, explain the benefits to the Government in technical terms and the degree of impact it will have to performance, operations and/or risk. Offerors are advised that any 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. 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. One method of demonstration is documented performance in an operational environment (an environment that addresses all of the operational requirements and specifications required of the system to include platform/packaging) or a simulated operational environment (a real environment that can simulate all of the operational requirements and specifications required of the system). Another method of demonstration is independent testing/evaluation in a non-operational (laboratory) environment (a simulated environment that allows for testing to determine if a system will meet the operational requirements and specifications of the system) at the system-level. Documentation from OEM for the aircraft or systems utilized can be used as a basis for demonstration. The instructions below provide specific guidance for the type of demonstration. However, the Offeror is advised that application of this guidance is not a guarantee that the Offeror's demonstration will be deemed adequate or without risk. The burden of proof rests with the Offeror.

3.1 Aircraft Performance

The Offeror shall demonstrate how each proposed aircraft will meet the requirements described in PBWS paragraph

4.1 and Appendix D. Supporting data (e.g. OEM flight manuals, published performance data, etc.) shall be submitted in Annex C to substantiate the aircraft meets the performance requirements.

3.2 Airworthiness

The Offeror shall provide the following documentation relating to aircraft airworthiness.

3.2.1 Parts Life Tracking Process and Status Report

The Offeror shall demonstrate that all parts with OEM defined life limits have been identified, and the Offeror shall submit a plan for replacing those parts on/before their required dates. This information is part of draft of CDRL A003.

3.2.2 Aircraft Pedigree Report

The Offeror shall demonstrate that each aircraft modification made to the proposed aircraft since manufacture has been certified as airworthy. For each modification, the Offeror shall provide a copy of the airworthiness certification or, alternatively, the engineering report that clearly demonstrates that the modified aircraft is airworthy.

3.2.3 Maintenance History Report

The Offeror shall provide, for each aircraft proposed, an accounting for the timeframe from manufacture to proposal submittal date that the aircraft has been maintained in accordance with the requirements established by the OEM, or 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.

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

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.

3.2.4 Fatigue Life Status Report

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

The Offeror shall provide for each individual aircraft: (a) the current total counts on tracked items (e.g. flight hours/take-offs and 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.

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 performance period of the contract, based on projected combined aircraft usage rates as described in Section B, CLINs 0004-0006. This information is part of CDRL A003.

3.3 Aircraft Support

The Offeror shall provide the following documentation relating to aircraft support.

3.3.1 Aircraft Maintenance Strategy

The Offeror shall provide an explanation of its maintenance organization and strategy for conducting both scheduled and unscheduled…