N00019-18-R-0033-A0006.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

This amendment updates Section L, Part A, Paragraph 1.0 General to state that no further questions w ill be addressed after May 10, 2019.

All other terms and conditions remain unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

1 17

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

16C. DATE SIGNED

BY 09-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 N0001918R0033

X 9B. DATED (SEE ITEM 11)

01-Apr-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 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

09-May-2019

CODE

NAVAL AIR SYSTEMS COMMAND

AIR-2.4.4.1 BLDG 2807

48195 SHAW RD

PATUXENT RIVER MD 20670

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0001918R0033

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

L - 1 CONTENT OF PROPOSALS

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, with or without discussions. Alternate proposals are not acceptable.

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

The Offeror shall include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. There is no need to repeat information in more than one volume. The detailed information must be included in the most logical place and summarized and referenced in other areas if an overlap exists.

However, pricing information shall only be contained in Volume 4. Do not provide elaborate brochures or other presentation material beyond that sufficient to present a complete and effective proposal.

The Government advises the Offeror that taking exception or deviating from any term or condition of the RFP may result in the assessment of a deficiency to the 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 evaluations: (a) prime contractor; (b) JV Team Members and (c) other entities that are proposed to perform at least 25% 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 1 and associated with a workshare equivalent to the percentage of the total proposed price.

Offerors may submit questions requesting clarification of solicitation requirements by emailing the contract specialist at alison.grosch@navy.mil. It is required that all questions be received on or before May 10, 2019. All questions and answers will be posted to the FBO website at https://www.fbo.gov.

2.0 PROPOSAL FORMAT AND SUBMISSION

Proposals should be formatted using a Times New Roman 12-point normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for/printed on standard 8.5 x 11-inch paper. If Government attachments have a different format/font, the Offeror may use the format/font in the attachment as provided. All pages should be numbered with volume, paragraph, and page numbers. When fold-out pages are used, they must not exceed 11 x 17 inches and will be counted as 1 page. Drawings may be provided separately and may be any size but should be folded to approximately 8.5 x 11-inch standard size and will count as 1 page. If the Offeror uses graphs to convey information, the graphs must show enough detail to easily discern the information described.

Graphs and tables should be presented in no smaller than a 10 point font and should contain a grid, which allows values to be read directly from the graph to the same detail that a 10 x 10 to the ½ inch grid provides. Graphic resolution should be consistent with the purpose of the data presented. Text utilized in charts, figures, and graphics should also be no smaller than a 10 point font and may use a font type selected by the Offeror. Each volume, book, or annex should be provided separately in a 3-ring binder. The binders should be of an appropriate thickness for the number of pages it contains (e.g., a 30-page book should not be placed in a 2-inch binder).

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. 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. If a discrepancy exists between the original paper copy of the proposal and the original electronic copy on the CD-ROM disk, the original paper copy shall take precedence.

2.1.1 Electronic Proposal Media

The Offeror shall submit all volumes of its proposal electronically on CD-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 CD-ROM, keeping the portions of the proposal that contain pricing information on separate CD-ROM(s) from the portions of the proposal that do not contain pricing information. For this solicitation, Volume 4 Price contains price information and should be delivered on separate CD-ROM(s) from the remainder of the proposal.

Table G-3 (Proposal Structure) identifies the proposal structure for each volume. The Offeror should submit a total of three sets of CD-ROMs. The first set of CD-ROM disks should be marked "Original” and the second and third sets of CD-ROM disks should be marked "Backup”. The “Original” set and one “Backup” set should be submitted to the PCO, and one “Backup” set should be submitted to the Contract Specialist IAW para 4.0 below. These CD-

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

Valid file extensions are shown in Table G-1.

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, or compatible, 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 Office 2010 applications are provided.

2.1.3 Hyperlinks

Offerors may use hyperlinks within and among proposal volumes. However, there shall be no links from volumes that do not contain price information to volumes that do contain price information.

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

Executive Summary, 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, book, or annex as one file if possible. Offerors should not provide each section/paragraph as separate files.

The Offeror shall ensure that the electronically submitted files are directly traceable to paper copy submittals.

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 Technical Vol 2 Tech#.docx

Technical Cross Reference Matrix Vol 2 Tech CRM.xlsx

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

4 Price Vol 4 Price#.docx

Annex A Relevant Portions of Final Versions of Previous SOW/PWSs for

Past Performance

AnnA Rel SOW

PWSs#.pdf and AnnA 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 # etc.

(If needed)

List other Annexes here TBD

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 additional hard and/or electronic copies as specified in Table G-3 (Proposal Structure). The Offeror shall submit all paper and/or electronic copies of the proposal to the address provided in Section 4.0 (Proposal Submission). 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.

Price information, (e.g., dollar values) shall not be included in any volume other than Volume 4 Price.

Table G-3 Proposal Structure

Volume Number Volume Title

Written

Page

Limit

Copies Required

1 EXECUTIVE SUMMARY 15

1 Original Hard Copy/1

Hard Backup Copy/1

Original Electronic

Copy/2 Backup

Electronic Copies

2 TECHNICAL 75

1 Original Hard Copy/1

Hard Backup Copy/1

Original Electronic

Copy/2 Backup

Electronic Copies

3 PAST PERFORMANCE 15

1 Original Hard Copy/1

Hard Backup Copy /1

Original Electronic

Copy/2 Backup

Electronic Copies

4 PRICE N/A

1 Original Hard Copy/1

Hard Backup Copy /1

Original Electronic

Copy/2 Backup

Electronic Copies

Each volume shall contain the following information:

a. Cover and title page

b. Title of proposal and proposal number as applicable

c. Offeror’s name, address, and POC

d. Solicitation number

e. Proposal volume number

f. Copy number

g. Table of Contents (The table of contents must provide sufficient detail to enable easy location of important elements)

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 Attachment Name

L-1 Vol 1 ES Tables Table ES-1 Offeror Summary and

Table ES-2 Relevant Contract

Summary

L-2 Vol 3 PPQ Past Performance Questionnaire

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

Contract Data

4.0 PROPOSAL SUBMISSION

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

The Offeror shall submit proposals via United States Postal Service or commercial carrier using the addresses provided below. Proposals shall not be submitted by facsimile or electronically via email.

One original hard copy, one original electronic copy, and one backup electronic copy shall be mailed to the following address:

NAVAL AIR SYSTEMS COMMAND

ATTN: Code: AIR- 2.4.4.1 (Attn: Ms. Diana Harritt)

Solicitation Number: N0001918R0033

48195 Shaw Road

Bldg 2807, Rm. 105

Patuxent River, MD 20670

One (1) Hard Backup Copy, One (1) electronic backup copy of the entire proposal, including all volumes, annexes, attachments, shall be mailed to the following address:

NAVAL AIR WARFARE CENTER

AIRCRAFT DIVISION LAKEHURST

ATTN: Code 2.5.2.1.4 AG (Attn: Ms. Alison Grosch)

Solicitation Number: N0001918R0033

Route 547, Mail Stop 562-306

Joint Base MDL, NJ 08733-5000

5.0 PROPOSAL PACKAGING

The Offeror shall package the proposal volumes in cartons or equivalent packaging containers in the most efficient manner possible grouping like volumes to the maximum extent possible. Also, each carton shall be single person portable. Each box should include a packing slip detailing the contents to include the volume number, title, and copy number. Also, each box should be stamped or marked “For Official Use Only” and “Source Selection

Information – See FAR-2.101 and 3.104.”

Note: Any documents which contain pricing data shall be on a separate CD-ROM disk(s) from the non-price proposal information.

6.0 CLASSIFIED DATA

All proposals must be UNCLASSIFIED.

7.0 SOLICITATION CHANGES

For notice of any changes and additional information provided by the Government for the solicitation, please go to www.FedBizOpps.gov.

PART B SPECIFIC INSTRUCTIONS

1.0 VOLUME 1 – EXECUTIVE SUMMARY

Note: All proposals shall remain valid for a period of 180 days from the time of solicitation closing. This volume shall not contain any reference to price aspects of the offer. Pricing information shall only appear in the Price

Volume 4.

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 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 evaluation, 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, 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 will perform the work.

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

http://www.fedbizopps.gov/

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 for the principal entities. The Offeror shall complete the table according to the instructions within the attachment and submit it as a separate electronic file. The contract references designated in Table ES-2

(Relevant Contract Summary) shall be used in completing Attachment L-2 Volume 3 Table PP-1 (Past

Performance Contract Data). For example, the contracts identified as P1, T1, S1, or C1 in the Relevant

Contract Summary Table are the same P1, T1, S1, or C1 contracts identified in the Past Performance Contract

Data table.

Technical - The Offeror shall provide a succinct summary of what is proposed for each element, describing the approach or the design configuration and/or 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, identity where in the Technical Volume (e.g., paragraph and page number as a minimum) the details of these features or approaches are provided.

c. Contract Administration - The Offeror shall provide a summary of any exceptions or deviations, and proposed

Section H clauses.

2.0 VOLUME 2 – TECHNICAL

Note: This volume shall not contain any reference to price aspects of the offer. Pricing information shall only appear in the Price Volume 4.

The Offeror shall submit a Cross Reference Matrix (CRM) for the Technical Volume as the first page of Volume 2, similar to the example below, to help ensure that all solicitation requirements are addressed and to facilitate the evaluators’ review of the Offeror’s proposal. The CRM should be a single integrated matrix and cross-reference the proposal volumes and paragraphs to specific solicitation requirements, as well as other parts of the proposal that contain relevant information. The Offeror’s CRM may be identical to the example below or revised such as to add columns to indicate the page number on which information may be found, identify where other relevant information in the proposal is located, or provide other comments. The CRM does not count against any of the proposal page limitations and shall be submitted with the Technical Volume.

EXAMPLE OF A CROSS REFERENCE MATRIX (CRM)

Section L –

Proposal

Instructions

Government

SOW/PWS

Section M

Evaluation

Factor Offeror’s Proposal Reference

CLIN

Reference

Volume 1

Technical

Example: Para 3.1

Note: This column shall address all paragraphs in

Sections xx and xy of the SOW/PWS

2.A Provide reference to Offeror’s Proposal

Volume I – Technical. Example: Refer to appropriate page number in Offeror’s written proposal

The proposal shall include information / documentation in sufficient detail to clearly identify the Offeror’s overall qualifications to accomplish the scope of the work of the resulting contract. The proposal shall be subdivided into the following sections, in the order listed, and shall be written to match the following format.

a. Design Approach Element

Performance Characteristics

b. Program Management Element

Schedule and Milestones

Manufacturing Capacity and Facilities

Quality Assurance (QA) Program

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. The Offeror is responsible for demonstrating the benefit to the

Government with substantiating information. 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. The burden of proof rests with the Offeror.

2.1 Design Approach Element

This section shall include information in sufficient detail to permit a thorough evaluation of the proposed design’s ability to meet or exceed the requirements, as more specifically required below.

The Offeror shall provide a detailed narrative of how the proposed C-Band Radar Transponder meets or exceeds the following requirements as more specifically defined in the Statement of Work Attachment 1, in the Performance

Specification (PMA208-C-Band-Transponder-17007), and in the Range Commanders Council Standard 262-14

(RCC Standard):

a. The Offeror shall describe its anticipated Production Reliability Acceptance Test Procedures in accordance with

SOW Paragraph 3.3.3 Production Reliability Acceptance Test Procedures and the requirements of the

Performance Specification (PMA208-C-Band-Transponder 17007). Within its description, the Offeror shall identify what facilities and equipment will be used to conduct the High Vibration, High Temperature Cycle and

Combined Temperature/Vibration Cycle tests.

b. The Offeror shall describe the anticipated regular periodic maintenance cycle associated with its proposed C-

Band Transponder in accordance with SOW paragraph 3.8.2.

c. The Offeror shall quantify the heat generated by the proposed C-Band Transponder assuming an interrogation repetition frequency of 1,000 cycles per second (PRF = 1 kHz) in accordance with paragraph 3.5.1 of

Performance Specification (PMA208-C-Band-Transponder 17007) and RCC 262-14, section 3.4.6, Equipment

Category 6 (Sea Level to 70,000) feet, which states that the unit shall operate continuously from -54F to 71F, intermittently from 71F to 85F, and survive (non-operational) from -62F to 85F. Intermittent is defined as 30 minute of operation followed by 15 minutes on non-operation (de-energized).

d. The Offeror shall describe the equipment required for tuning and maintenance of its proposed C-Band

Transponder as required by SOW paragraph 3.8.2 and 3.8.4, including identification of whether the equipment is commercial, commercial-off-the-shelf or specialized, the life limits of the equipment, a description of the availability of replacement equipment, and the time associated with obtaining replacement equipment.

e. The Offeror shall describe the dimensions of the proposed C-Band Transponder in accordance with

Performance Specification (PMA208-C-Band-Transponder 17007) Paragraph 3.1 and RCC Standard Paragraph

2.4.2.

f. The Offeror shall describe the weight of the proposed C-Band Transponder in accordance with Performance

Specification (PMA208-C-Band-Transponder 17007) Paragraph 3.1 and RCC Standard Paragraph 2.4.1.

2.2 Program Management Element

The Program Management Element section of the proposal shall demonstrate the Offeror’s understanding of the management required to successfully perform on this contract. The following information shall be required:

a. Schedule and Milestones: The Offeror shall provide a schedule that clearly indicates compliance with all program milestones from contract award to delivery of qualified production units. The Offeror shall address the following major reviews, schedules, and meetings identified in the SOW:

a. Preliminary Design Review (PDR)

b. Critical Design Review (CDR)

c. Production Readiness Review (PRR)

d. Technical Interchange Meetings (TIM)

b. Manufacturing Capacity and Facilities: The Offeror shall describe the overall production capability including facilities, major equipment, and space necessary to perform production efforts. The Offeror shall address the availability and utilization of production resources in performance and production efforts.

c. Quality Assurance (QA) Program: The Offeror shall describe and provide detailed information on its quality assurance program in accordance with SOW Paragraph 5.6.1.

3.0 VOLUME 3 – PAST PERFORMANCE

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 Past Performance Questionnaire (PPQ)

Attachment L-3 Past Performance Contract Data (PP-1)

For this volume, the Offeror shall identify all relevant contracts (where for the purpose of these instructions the term contract also refers to delivery order or task order), or those portions of a relevant contract, whose performance is within five years of the proposal due date for the principal entities, identified in Table ES-1 (Offeror Summary).

The relevant contracts provided for each principal entity shall be relative to its proposed role and responsibilities identified in Table ES-1 (Offeror Summary). Commercial contracts may be included. Offerors shall also identify relevant contracts within the past five years of the proposal due date that had any show-cause notices, cure notices, or termination for default. The Offeror shall complete Table ES-2 (Relevant Contract Summary for Past

Performance) provided in Attachment L-1 (Executive Summary Tables), for all contracts proposed as relevant for

Past Performance.

In Annex A (Final Versions of Previous Statement of Work (SOW)/Performance Work Statement (PWS)/Other

Supporting Documentation for Past Performance), the Offeror shall provide electronic copies of the complete final versions of the SOW/PWS or other supporting solicitation/contract documentation from each contract or delivery/task order reference identified in Table ES-2 (Relevant Contract Summary). Annex A should only be provided in electronic format and should not be provided in paper copy. For contract references that contain delivery/task orders, additionally provide the work description for each specific delivery/task order. For contract references where the Offeror performed as a subcontractor, the Offeror shall also provide a complete electronic copy of the SOW/PWS or other documentation of the agreement between the prime and subcontractor that clearly defines the portions of the work effort of the Prime’s SOW/PWS that the Offeror performed as a subcontractor.

Contract Performance Assessment Reporting System (CPARS) and Questionnaires will be the primary customer feedback data used to evaluate the Offeror’s past performance. The Past Performance Information Reporting

System (PPIRS) will be the primary method used to retrieve the CPARS for this source selection. For all contracts identified that do not have a CPARS, the Offeror shall forward a copy of Attachment L-2 Past Performance

Questionnaire to that contract’s Procuring Contracting Office (PCO), Administrative Contracting Officer (ACO), and Program Manager (PM); or commercial contractor equivalents. Please forward all questionnaires within two weeks from this solicitation’s release date to allow adequate time for the recipient to respond. Note that the Offeror should not reference this solicitation’s number when distributing the past performance questionnaires to customers.

The Offeror should include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to the PCO and Contract Specialist, identified in Section 4.0 (Proposal Submission). The Offeror shall ensure that all points of contact are current and include an email address and phone number. The Offeror shall not conduct follow-up actions with regard to this questionnaire, other than to confirm receipt by the recipient. The

Government may contact customers identified by the Offeror to obtain follow-up Past Performance Information as needed.

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

3.1 Authorization Letter(s)

The Offeror should submit a signed “Release of Adverse Past Performance Authorization Letter(s)” with written consent from each principal entity (including JV team members), authorizing the release of adverse past performance information to the Prime. The signed letter(s) should be included in a separate tab within Volume 3

(Past Performance). This authorization letter allows the Government to coordinate past performance issue(s) with the Prime Offeror. For any principal entity (including JV team members) that does not provide an authorization letter with such written consent, the Offeror shall provide point of contact information for each principal entity.

This contact information shall include a name, address, phone number, and email address (including JV team members), with whom the Government may coordinate any issues and obtain responses as needed. Offerors are advised that if it does not submit the Release of Adverse Past Performance Authorization Letters with written consent, then the Government will address any past performance issues directly with the principal entity (including

JV team members), and the Offeror will forfeit the opportunity to participate in any related discussions.

3.2 Relevant Contract Data

For each contract identified for past performance in Table ES-2 (Relevant Contract Summary) provided in

Attachment L-1 (Executive Summary Tables), the Offeror shall complete Attachment L-3 Table PP-1 (Past

Performance Contract Data), according to the instructions within the attachment and submit it as a separate electronic file. Please note that this form is a summary of the principal entities’ relevant contract data. All detailed information and comparative analysis of the past performance contract references to this solicitation’s requirements shall be provided in Volume 3 (Past Performance), Section 3.3 (Evaluation), of the Offeror’s proposal. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing Volume 3 (Past

Performance) and all contract references shall be numbered the same throughout all of the Offeror’s proposal volumes (i.e., the contracts identified as P1, S1, T1, C1 etc.)

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

3.3 Evaluation

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

For each contract identified in Attachment L-3 Table PP-1 (Past Performance Contract Data), the Offeror shall provide contract data regarding relevancy, past performance information, demonstrated systemic improvement as described below, organized by contract reference. As this information is presented in the proposal, demonstrate the relevancy of the principal entities past performance with respect to this solicitation’s requirements. For any contract references where the principal entities are aware of problems, the Offeror shall describe the issues in section 3.3.b

(Past Performance Information). For each past performance problem identified, describe the status of the systemic improvement efforts in section 3.3.c (Demonstrated Systemic Improvement).

a. Relevancy:

Offerors are required to explain what aspects of the referenced contracts are deemed relevant, as defined by Section

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

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

For a discussion on CAGE Code/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 evaluations.

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

Performance assessments.

b. Past Performance Information:

For the relevant contracts, provide a brief description of past performance in delivering quality services/products.

Include in these descriptions any information that demonstrates the level of performance obtained, where available;

provide quantifiable measures/trends to demonstrate past and current performance. Also describe past problems, including when they occurred, what the circumstances were surrounding the situation, and what the consequences were as a result of the problem.

For Small Business Utilization, any Large Business team members shall provide copies of the final or most recent

SF 294s/Individual Subcontracting Reports (ISRs) for the three most relevant Government contracts provided in the

Past Performance section of its proposal. The Small Business Offeror may provide this information in a format substantially the same as the ISR. If the Offeror is a participant in the DoD Comprehensive Subcontracting Test

Program, the Offeror shall provide copies of DCMA's most recent “Review of Contractor's Comprehensive

Subcontracting Program” (DCMA Form 640), and three final or most recent SF 295s/Summary Subcontracting

Reports (SSRs), and explain how the results shown in these documents demonstrate the offeror’s SB Utilization

Strategy. If applicable, note whether the contract met or exceeded Small Business (SB), Veteran-Owned Small

Business (VOSB), Service-Disabled Veteran-Owned Small Business (SDVOSB), HUBZone Small Business

(HUBZone), Small Disadvantaged Business (SDB), and Women-Owned Small Business (WOSB) small business utilization and subcontracting goals.

c. Demonstrated Systemic Improvement:

Identify systemic improvement actions taken to resolve any past problems identified in 3.3.b (Past Performance

Information). Provide the records of such results and indicate where they are documented, preferably in

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

4.0 VOLUME 4 – PRICE

4.1 Ground Rules and Assumptions

As this is a competitive acquisition with adequate price competition anticipated, certified cost or pricing data in accordance with FAR 15.403-1 is not required. However, in the event that adequate price competition does not exist after receipt of proposals, the Government reserves the right to request additional cost or pricing data as necessary from both the Offeror and subcontractors. Further, the Offeror may be required to provide a Certificate of Current

Cost or Pricing Data prior to award, pursuant to FAR 15.406-2.

The Offeror shall provide sufficient information to support its price as well as an explanation of all ground rules and assumptions that affect the price estimates.

If subcontractors are proposed, they shall provide the same information required for the prime contractor, unless otherwise noted below.

4.2 Pricing Information

This requirement is being set-aside for the small business. The Offeror shall provide a breakout to demonstrate how the prime contractor will not pay more than 50 percent of the amount paid by the Government for contract performance, excluding the cost of materials, to subcontractors that are not similarly situated entities, in accordance with FAR clause 52.219-14 (DEVIATION 2019-O0003).

The Offeror shall complete Section B of the RFP, which will be included in the model contract documents provided under paragraph 4.3 below, as follows:

a. Fill-in the unit prices for all CLINs, except those listed as Not Separately Priced (NSP)

b. Fill in per unit prices for each quantity range provided under the Stepladder Pricing Note for CLINs 0101, 0201, 0301, 0401, and 0501.

The Offeror shall explain any appearance of unbalanced pricing. Unbalanced pricing exists when, despite an acceptable total evaluated price, the price of one or more line items, including stepladder pricing ranges, is significantly overstated or understated as indicated by the application of cost or price analysis techniques. Any apparent imbalances in the pricing, high or low proposed prices, or any other anomalies should be fully explained.

All price and price supporting information shall be contained in Section B of the RFP and the price proposal. No price or pricing information shall be included in any other volume including cover letters. Offerors are responsible for submitting sufficient information to enable the Government to fully evaluate their price proposal.

4.3 Contract Administration Information

The Offeror shall provide the following contract administration information:

a. 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).

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

(2) ALL OTHER ENTITIES

(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;

(vi) CAGE code; and

(vii) Percentage of work and role and responsibility performing.

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

c. 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;

d. Terms and Conditions:

All exceptions and deviations that the Offeror takes from the provisions of the solicitation and its applicable documents shall be included in this section.

An exception is where an Offeror states it will not comply with a solicitation requirement, usually involving contract terms and conditions. A deviation is where an Offeror states it will not comply with a solicitation requirement but proposes an alternative to meet the intent of the requirement, usually involving a SOW requirement. An exception or deviation may be considered a deficiency.

The Offeror shall provide one of the following two statements in this section. If the Offeror takes any exceptions or deviations to the provisions of the solicitation and its applicable documents, the Offeror shall provide the following statement: “All exceptions and deviations taken from the solicitation terms, conditions or requirements, including any applicable documents, are included in this section.” If the Offeror does not take any such exceptions or deviations, then the Offeror shall provide the following statement: “No exceptions or deviations are taken to the terms and conditions or any requirement of the solicitation.”

If proposing an exception or deviation, the Offeror shall provide a detailed description for each in this section.

Indicate the difficulty with the applicable requirement and the proposed solution. Specifically identify the portion of the solicitation and the proposal, which are affected. Also identify any proposed H-clauses containing unique contract terms and conditions not covered by clauses in this solicitation and associated with an exception or deviation identified in this section. The Government will review the information and may elect to clarify the requirement via an amendment or clarify the requirement by holding discussions.

e. Model Contract Documents: For evaluation purposes, in the event there is any discrepancy between these contracts documents and any other volume, Volume 4 (Price) shall take precedence. The Offeror shall provide the following model contract documents as a separate electronic file and as a separate section in this volume.

(1) Signed SF33 for basic solicitation and acknowledgment of each amendment, including completion of any

RFP clause or provision that requires a fill-in or response. The SF-33 Block 12 “fill in” (proposal validity date) shall be completed for at least 180 days after proposal submission.

(2) Signed Representations, Certifications, and Acknowledgements and/or System for Award Management

(SAM).

(3) Section B with Proposed Pricing in accordance with Section 4.2…