About this file

This request for proposal solicits proposals for indefinite-delivery, indefinite-quantity multiple award contracts to provide production, systems engineering and integration services, and retrofits for Multifunctional Information Distribution System Joint Tactical Radio System terminals. The Naval Information Warfare Systems Command seeks to award contracts to support the Multiple Information Distribution Program Office. Production requirements include manufacturing and delivering terminals and shop replaceable units. Systems engineering and integration services involve technical support delivered through task orders. Retrofit requirements consist of retrofitting and upgrading terminals and line replaceable units. The response deadline is December 19, 2019, and the estimated contract award date is March 2020. Pricing must be proposed for delivery order 0001 using the provided pricing model. Subcontracting participation objectives target percentages for small businesses.

View the file

Other files

File Type Posted
Attachment 11 - CDRL Table Rev1.docx DOCX document
Attachment 25 - Small_Business_Participation_Data Rev1.docx DOCX document
RFP N00039-19-R-1000 (AMD 0001 (Conformed Copy)).pdf PDF
CDRL Package_N00039-19-R-1000_A_Series Rev1.pdf PDF
Attachment 12 - CDRL_General_Instructions.pdf PDF
Attachment 11 - CDRL Table.docx DOCX document
Attachment 22 - Warranty Prices.docx DOCX document
Attachment 17_MPO RFD Form.pdf PDF
Attachment 8 - DD254.pdf PDF
Attachment 19 - Contractor Database Instructions_July 2017.pdf PDF
CDRL Package_N00039-19-R-1000_A Series.pdf PDF
Attachment 13 - MIDS JTRS Configuration Management Plan.pdf PDF
Attachment 16_MPO NOR Form.pdf PDF
Attachment 15_MPO ECP Form.pdf PDF
Attachment 14 - GFP Module.xlsx XLSX spreadsheet
Attachment 10 -TEMPEST Questionnaire for ECP.pdf PDF
Attachment 24 - Past_Perf_Questionnaire_Survey.docx DOCX document
RFP N00039-19-R-1000.pdf PDF
Attachment 25 - Small_Business_Participation_Data.docx DOCX document
Attachment 8.1 - 1-MIDS-IT-ONSITE-FOUO-OPSEC-TEMP.pdf PDF
Attachment 20 - MIDS JTRS MAC Ordering Guide.pdf PDF
Attachment 23 - Past Performance Reference Info Sheet.docx DOCX document
Attachment 21 - Lot 9 Pricing Model.xlsx XLSX spreadsheet
Attachment 9 - NSA Questionnaire for ECPs.pdf PDF
Attachment 1 - Production SOW_20Aug2019.pdf PDF
Attachment 18 - CSDR Plan_MIDS JTRS Lots 9-13_12 July 2019.pdf PDF
Show all 26

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

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 Amendment 0001 is to:

1. Extend the proposal deadline from 05 Dec 2019 to 19 Dec 2019.

2. Revise Section G, Clause G-4 Point of Contact Regarding Patent Matters

3. Revise Sec J, Attachment 11 - CDRL Table, Attachment 25 - Small Business Participation Data, and Exhibit A - CDRLs A004, A005 and A006

4. Revise Section L, Provision L-1 Section 1.5.3. CDRL Price Table and delete Section 1.4.2.3 Cost/Price Proposal

5. Revise Section L, Provision L-3 Estimated Date of Aw ard.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 14

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

16C. DATE SIGNED

BY 06-Nov-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 N0003919R1000

X 9B. DATED (SEE ITEM 11)

23-Oct-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

06-Nov-2019

CODE

COMMANDER, NAVAL INFORMATION WARFARE

SYSTEMS COMMAND

02 CONTRACTS

4301 PACIFIC HIGHWAY

SAN DIEGO CA 92110-3127

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0003919R1000

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 05-Dec-2019 09:00 AM to 19-Dec-2019 09:00 AM.

SECTION G - CONTRACT ADMINISTRATION DATA

The following have been modified:

G-4 The Point of Contact regarding Patent Matters for this contract is:

Office of Patent Counsel / Code 360000

NIWC

53560 HULL STREET

San Diego, CA 92152-5001

(619) 553-3001

Do not submit interim and final invention reports to this address. See the clause at H-5 for the proper address.

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

Attachment 1 – Production Statement of Work (SOW) dated Aug 2019

*Attachment 2 – SE&I SOW dated Oct 2019

*Attachment 3 – Retrofit SOW dated Oct 2019

*Attachment 4 – MIDS JTRS (5) CMN-4 Index and Data List dated 25 May 2018 *Attachment 4.1 - MIDS JTRS (5) F-15 Index and Data List dated 19 Jan 2018 *Attachment 4.2 - MIDS JTRS (8) F-22 Index and Data List dated 22 Jun 2018

*Attachment 5– MIDS JTRS (7) TTNT Index and Data List dated 16 Dec 2016

*Attachment 6 – Core Terminal Index and Data List dated 11 May 2015

*Attachment 7 – BC1+ Index and Data List dated 8 May 2015 *Attachment 7.1 – BC2 Index and Data List dated 7 May 2015

Attachment 8 – DD Form 254 - Contract Security Classification Specification dated 16 July 2019 Attachment 8.1 – DD Form 254 Attachment: IT Systems Personnel Security Program Requirements dated 16 July

Attachment 9 – NSA Questionnaire for ECPs

Attachment 10 – TEMPEST Assessment Form for ECPs

Attachment 11 – License Rights, CDRL Table

Attachment 12 – CDRL General Instructions

Attachment 13 – Configuration Management Plan dated 16 January 2014

Attachment 14 – GFP Module Template

Attachment 15 – MPO ECP Form

Attachment 16 – MPO NOR Form

Attachment 17 – MPO Request for Deviation/Waiver (RFD/RFW) Form

Attachment 18 – Contract and Software Data Reporting (CSDR) Plan dated 12 July 2019

Attachment 19 – Contractor Database Instructions dated July 2017

Attachment 20 – MIDS JTRS MAC Ordering Guide

Attachment 21 – DO 0001 Lot 9 Pricing Model Template

Attachment 22– DO 0001 Lot 9 Price List A: Warranty Unit Prices

Attachment 23 – Past Performance Reference Information Sheet

Attachment 24 - Past Performance Questionnaire/Survey

Attachment 25 – Small Business Participation Data Form

Exhibit A – Contract Data Requirements Lists (CDRLs) dated Oct 2019

*Exhibit B –CDRLs dated Oct 2019

* These documents will not be posted publicly at this time and can be accessed via the MIDSVue workroom system: https://midsvue.topvue.com/topvue.

In order to obtain access to the MIDSVue website, all interested respondents shall:

1) Have a current and properly scoped DD 2345 on file with the Defense Logistics Information Services (DLIS). If the company does not have a current and properly scoped DD 2345 on file and cannot provide a Joint Certification Program (JCP) number, please visit DLIS at http://www.dlis.dla.mil/jcp/ for more information on how to complete and submit the DD 2345.

2) Provide the name, email address and phone number for each requested user, and the company's JCP number and Cage Code to Mr. Joseph Gonzales at Joseph.Gonzales1@navy.mil and Mrs. Brianne Justiniani at Brianne.Justiniani@navy.mil.

Request a MIDSVue account (if you do not already have a MIDSVue account) Request access by contacting MIDSVUE_ADMIN.fct@navy.mil to receive a access form.

Access MIDSVue Site at https://midsvue.topvue.com/topvue. Fill out the Requested information. For “Government POC” use Mrs. Brianne Justiniani. For “Justification” use the following statement: “Access is required to view the MIDS JTRS Request for Proposal N00039-19-R-1000”

Wait for “account approval email” - Account will be approved within 48 hours. If access is not granted within 48 hours, the company shall notify Mr. Joseph Gonzales at Joseph.Gonzales1@navy.mil.

In “account approval email”, click on link to activate account.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

L-3 ESTIMATED EFFECTIVE AWARD DATE

For Bidding/Proposal purposes the estimated effective date of contract award is MARCH 2020. However, this is only an estimated award date and it shall not be construed as providing any potential offeror with relief from all other requirements of this RFP.

L-1 SUBMISSION OF PROPOSALS

1.0 SOLICITATION OVERVIEW

This request for proposals is for the procurement of MIDS JTRS development and production requirements for fiscal years 2020-2025. IAW 52.216-27-Single or Multiple Awards, the Government may elect to award a single delivery order contract or award multiple delivery orders contracts for the same or similar supplies or services to one or more sources under this solicitation.

1.0.1 Receipt of Offers: Proposals are due no later than 9:00 AM Pacific Standard Time on 19 December 2019.

1.0.2 Validity of Proposals: Proposals submitted in response to this solicitation shall be valid for 360 calendar days from the solicitation closing date.

1.0.3 Submission of Electronic Proposals

(a) Offerors shall submit their proposals and any questions regarding this RFP electronically to NAVWAR under the instructions contained in this provision. Questions shall be submitted no later than (NLT) 5:00 PM Pacific Standard Time two (2) weeks prior to the proposal deadline. The Government will use its best effort to respond to Offeror questions and comments; however, responses are not guaranteed. Offerors are advised that the Government will make available to the public any Offeror questions and comments and the Government's associated responses; therefore, Offerors shall not provide questions or comments of a proprietary nature. Offerors shall also submit any proposal assumptions or exceptions to the RFP terms and conditions NLT 5:00 PM Pacific Standard Time two (2) weeks prior to the proposal deadline. The Government will use its best effort to address or resolve Offerors’ assumptions and exceptions; however, responses are not guaranteed.

Offerors shall submit their signed proposals as ‘PDF’ documents except for the pricing model, which shall be submitted in MS Office 2010 Excel compatible format. Electronic copies shall be submitted via the NAVWAR E- Commerce Select (NAVWAR E-C Select) under RFP Number N00039-19-R-1000. Offerors shall register in the NAVWAR E-Commerce Central (NAVWAR E-CC) and select their own password in order to submit a proposal.

Offerors are required to read the “Submitting a Proposal?” web page found in the SPAWAR E-CC. For information about “e-Proposal” submission, please visit the NAVWAR E-CC. The URL for the E-CC is https://e-commerce.sscno.nmci.navy.mil/command/02/acq/navhome.nsf/homepage?readform. Any questions regarding connection issues with the NAVWAR E-C Select or NAVWAR E-CC shall be directed to NAVWAR Paperless Helpdesk at 858-537-0644 or paperless.spawar@navy.mil. All other questions regarding this RFP shall be directed to Lindsay Nickel 619-524-5618 or lindsay.nickel@navy.mil

(b) Each electronic file shall also be clearly marked to show the proposal volume number, solicitation number and Offeror’s name. E-Proposal files shall not contain classified data. The Offeror’s e-proposal shall be IAW the requirements set forth below:

(1) Adobe Acrobat version 8.1.4 or greater shall be used to create the “PDF” files.

(2) The proposal submission files may be compressed (zipped) into one, self-extracting file entitled

“PROPOSAL.EXE” using WinZip version 11.2 or greater.

(3) Cost or Pricing Type Data: All information relating to cost and pricing type data shall be included only in the section of the proposal designated by the Contracting Officer as the Cost/Price Proposal. Under no circumstances shall cost and pricing type data be included elsewhere in the proposal. Paragraph cross-referencing between Cost/Price Proposal paragraphs and technical/management proposal paragraphs is requested to provide clarity.

(c) Proposals submitted electronically will be considered “late” unless the bidder or Offeror completes the entire transmission of the bid or proposal prior to the due date and time for receipt of bids or proposals. This paragraph (c) supplements the submission, modification and withdrawal of bids and proposals coverage in the FAR 52.215-1 “Instructions to Offerors--Competitive Acquisition” provision contained in the solicitation.

1.1 PROPOSAL REQUIREMENTS

Proposals submitted in response to this RFP shall be UNCLASSIFIED and shall consist of four (4) Volumes identified as follows:

Volume I: Contracts Documents Volume II: Mandatory Gate Criteria Volume III: Technical Proposal Volume IV: Cost/Price Proposal

In addition to all other requirements of this solicitation, each Offeror shall demonstrate its capability by means of a detailed written proposal in each of the areas indicated under Section M – Evaluation Factors for Award. Proposals submitted for consideration for award shall address the full scope of the solicitation. Failure to submit complete information in the manner below may be considered a “no response” and may result in the exclusion of the proposal from further consideration.

SECTION

VOLUME

PAGE LIMIT

1.2 I. CONTRACT DOCUMENTS No page limit

1.3 II. MANDATORY GATE CRITERIA No page limit

1.4 III. TECHNICAL PROPOSAL

1.4.1 Factor 1 – Integrated Master Schedule (IMS) 2 page limit

1.4.2 Factor 2 – Delivery Order 0001 10 page limit

1.4.2.1 Subfactor 2.1 - Delivery Schedule Adherence

1.4.2.2 Subfactor 2.2 – Terminal Maintainability – Repair Turn Around Time (TAT)

1.4.3 Factor 3 – Past Performance 4 pages total per

reference (E l i f

1.4.4 Factor 4 - Small Business Participation 10 page limit

1.5 IV. COST/PRICE PROPOSAL No page limit

1.1.1 Proposal Format: Tables of contents, blank pages, coversheets, requirements compliance matrices, lists of tables, lists of drawings, lists of figures, glossaries, and lists of proprietary data do not count against the page limitations. All proposal material must be contained within the page limit(s) identified for each volume, unless otherwise specified. Partial pages count as a full page. Pages shall be numbered consecutively within each section to indicate the volume, section, and page. For example, Page 19 of Volume I, Section 3 would be numbered I-3-19.

Type size shall be Times New Roman and no smaller than 12 point in the text and 10 point in spreadsheets. The Offeror’s electronic version of their proposal shall be prepared on standard 8 ½” by 11” paper, single-spaced, with 1” minimum margins excluding header and footer.

1.1.2. Proposal Content: An Offeror’s proposal is presumed to represent to Offeror’s best efforts to respond to the solicitation. Proposals submitted for consideration for award must address the full scope of the solicitation.

Proposals which address only part or portions of the solicitation will be considered unacceptable. Non-conformance may cause rejection of, or the downgrading of, the proposal. Proposals should be clear, concise and complete.

Organization, clarity, accuracy of information, relevance, and completeness are of prime importance.

Proposals shall correlate directly and sequentially with the following specific proposal preparation instructions.

Proposals shall be complete and self-sufficient, relate exactly to what is requested and proposed, and strictly adhere to the requirements of this solicitation. Offerors shall provide separate responses to each technical evaluation factor within the identified page limitations. Use of documentation by reference, and not incorporated into the proposal, will not be allowed. Where cross-referencing is used, the volume, attachment, exhibit and paragraph numbers, as appropriate, shall be referenced.

Material in excess of the page limits will not be evaluated.

The required content for each volume section is described below:

1.2 VOLUME I: CONTRACT DOCUMENTS. The completion and submission to the Government of the items in Volume I will constitute the offer. The Government’s acceptance of the offer will create a binding contract between the Government and Offeror. The Offeror’s proposal shall be signed by a company official having actual authority to bind the contractor contractually. The Offeror’s failure or refusal to assent to any of the terms and conditions of this RFP or its imposition of additional conditions or any material omission in its offer may constitute a deficiency, which may make the offer unacceptable to the Government.

1.2.1 Section 1: Cover Letter/Executive Summary. The Offeror’s proposal shall include a cover letter on company letterhead and signed by an individual who possesses authority to contractually bind the Offeror. The cover letter shall acknowledge receipt of all amendments (if any are issued) to the RFP. The cover letter shall identify all enclosures being transmitted as part of the response to the RFP. The Cover Letter shall provide a statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation and a point of contact including name, telephone number and email for correspondence regarding the proposal. It shall state: (1) Commercial and Government Entity (CAGE) number, (2) Data Universal Numbering System (DUNS) number, (3) Taxpayer Identification Number (TIN), (4) address(es) of the location(s) at which the Offeror intends to perform the proposed effort, (5) name, address and telephone number of the cognizant Defense Contract Audit Agency (DCAA) audit office, (6) the name, address and telephone number of the cognizant Defense Contract Management Agency (DCMA) office, and (7) a statement that the proposal is valid for no less than twelve (12) months from the solicitation closing date. The above listed information (items 1-7) shall also be provided for all proposed subcontractors.

1.2.2 Section 2: Exceptions to the RFP. The Offeror’s proposal shall include any exceptions to the provisions of the solicitation. The Offeror shall clearly state the exceptions and provide references to the applicable solicitation page, paragraph, or exhibit line item number. The Offeror shall provide a full explanation for all exceptions taken to the solicitation. Any material exceptions to the solicitation may render the proposal unacceptable and ineligible. If the Offeror takes no exceptions to the provisions of the solicitation, the Offeror shall state their unconditional assent to all terms, conditions, and provisions included in the RFP within Volume I: Contract Documents.

1.2.3 Section 3: Signed SF33 with completed Sections B through K. The Offeror’s proposal shall complete Sections B through K of the RFP and provide a signed SF33 acknowledging all amendments. Signature by the Offeror on the SF33 constitutes an offer, which the Government may accept.

Completion of annual representations and certifications via the System for Award Management (SAM) is a requirement of solicitation provision 52.204-8, but it is not a sufficient response to Section K of the solicitation. All representations and certifications included in Section K must be completed, including Defense Federal Acquisition Regulation Supplement (DFARS) provision 252.227.7017, which requires completion and signature even for a negative response.

1.2.4 Section 4: Proprietary Data Protection Agreement. Government will not use any contractor support personnel for the review of this source selection.

1.2.5 Section 5: Security Clearance Levels. Offerors must document that all facilities and personnel proposed to perform this contract possess at a minimum the security clearance levels required by the RFP (see Attachment 8 –

DD254).

1.2.6 Section 6: Contractor Responsibility Information. To aid in the determination of contractor responsibility, the following information is required:

a. Information regarding the general financial condition of your firm and specific plans for financing the proposed contract, including the latest available financial statements. If you are currently being audited, or have been audited by DCAA, provide the address, current telephone number, and current point of contact for the cognizant DCAA and the cognizant DCMA Office. This shall include the latest approval date of your Disclosure Statement (not applicable to Small Businesses) and most recent audit status, i.e., when was the last one performed, what were the findings, etc.

b. A listing of previous and/or ongoing experience in related areas. Include the contracting activity, program or item produced, contract number, current point of contact, current telephone number, duration of contract, type of contract, and total dollar amount of contract. Please ensure information provided is current. If the Offeror believes that information provided under Volume II Section 3: Past Performance Information (Factor 3) adequately addresses the requirements of this provision, please state here. Repetition of the same information is not necessary.

c. A summary of your:

1. Accounting procedures and controls;

2. Organization;

3. Production control procedures;

4. Property control system;

5. Quality assurance programs; and

6. Equipment and facilities relative to this effort.

d. If there will be subcontracting, provide the following information:

1. Methodology for the selection of proposed subcontractors, if any, and the benefit they would bring to the arrangement; and

2. Analysis performed on the subcontractor’s cost/price proposal to determine a fair and reasonable price.

e. A list of credit references, including suppliers. Provide company name, point of contact, and telephone number.

f. Any other additional information that will assist in a better or complete understanding of your firm and its capabilities.

1.2.7 Section 7: Systems and Compliances. The Offeror shall provide documentation that demonstrates they currently have an adequate Accounting System, Estimating System, and Purchasing System. If available, the Offeror shall include the report number and date of the cognizant DCAA office’s determination stating that the Offeror’s accounting system is adequate for the accumulation, reporting, and billing of costs under a cost reimbursement contract (attach a copy of the report). If the Offeror does not have a determination from DCAA regarding its accounting system, the Offeror shall provide documentation as to why their business systems have not been reviewed or why documentation cannot be provided, and justification as to the adequacy of their accounting system in accordance with Federal Acquisition Regulation (FAR) 16.301-3. Additionally, the Offeror must have a DCMA-approved Disclosure Statement prior to contract award in accordance with FAR 30.202-6. The Offeror shall include the report number and date of the cognizant DCMA office’s determination stating that the Offeror’s Disclosure Statement is adequate (attach a copy of the report).

1.2.8 Section 8: Organizational Conflict of Interest (OCI) Mitigation Plan(s). The Offeror’s attention is directed to FAR Subpart 9.5 relating to organizational conflicts of interest. It is the Government’s intent to avoid, neutralize, or mitigate potential conflicts as early in the acquisition process as possible. The Offeror shall submit draft versions of any required OCI Mitigation Plans, consistent with the guidance contained in FAR Subpart 9.5.

1.2.9 Section 9: Small Business Subcontracting Plan. Offerors, unless otherwise exempt due to being a small business* concern or a company performing outside of any state, territory, or possession of the United States, the District of Columbia, and the Commonwealth of Puerto Rico, shall, in accordance with FAR 19.7 and FAR 52.219-9, submit a Small Business Subcontracting Plan. Failure to submit and negotiate a subcontracting plan acceptable to the Contracting Officer may make the offer ineligible for award of a contract.

1.3 VOLUME II: MANDATORY GATE CRITERIA

The Government is conducting this Full and Open competition in accordance with (IAW) Federal Acquisition Regulation (FAR) 15.101-1 – Tradeoff Process. Any award to be made will be based on the following two-step approach:

1. Acceptable/Unacceptable Gate Criteria, which the Offeror shall substantiate in Volume II.

2. Only those Offerors who receive a rating of “Acceptable” in the first step will then be evaluated under the factors/subfactors set forth below and using the best value tradeoff approach provided under Volume III.

In order to meet the Mandatory Gate criteria and be determined acceptable, the Offeror must demonstrate the ability to provide National Security Agency (NSA) certified MIDS JTRS terminals that support Concurrent Multi-Netting-4 (CMN-4), Tactical Targeting Network Technology (TTNT), and F-22 capabilities within twelve (12) months of the anticipated award.

MIDS JTRS variants are required to employ embedded cryptographic engines, and the cryptographic capability is required to be software configurable and capable of hosting software-defined Cryptographic Equipment Algorithms (CEA) and networking waveform Communications Security (COMSEC)/ Transmission Security (TRANSEC) algorithms. The Software Defined Radio (SDR) is required to be capable of certified operation with different classification levels assigned to each channel. Key loading will be provided by current force devices such as the Simple Key Loader (SKL). To facilitate supportability within the current logistical infrastructure, it is desired that all components be capable of being handled and transported as unclassified Controlled Cryptographic Items (CCI).

The cryptographic architecture of the radio is required to be in compliance with NSA Management Directive 237 Number 10 (MD-10).

In order to demonstrate compliance with the Gate criteria, as part of its proposal, the Offeror shall provide the following:

JTRS Compliance/JTRS Software Communications Architecture (SCA) certification (defined in “JTRS Criteria for ‘JTRS Compliant’ and ‘JTRS Certified’ Designation,” JPEO JTRS Memo, 23 Jan 2012), NSA Type 1 Certification, Department of Defense DoD DIACAP accreditations, Joint Interoperability Test Command (JITC) certification, JTRS Test and Evaluation Laboratory (JTEL) SCA/Application Programming Interface (API) certification, Critical Program Information and Anti-Tamper Review Requirements (DoDI 5000.02), Equipment spectrum certification, Link 16 Electromagnetic Compatibility (EMC) Features certification, and Spectrum supportability (IAW DoDI

4650.01), Airworthiness compliance requirements, and Safe-For-Intended Use (SFIU) tests, which shall consist of (1) crash safety, (2) random vibration, (3) RE102 radiated emissions, electrical field, 10 KHz to 18 GHz, (4) CE102 conducted emissions, power leads, 10 KHz to 10 MHz, and (5) explosive atmosphere and a signed AFMC Form 3.

Only Offerors who have met the Gate criteria in Volume II above hwill be considered acceptable by the Government will be evaluated on their technical approach in Volume III. Offerors who do not meet the Gate criteria will be considered unacceptable and will be removed from consideration for award.

1.4 VOLUME III: TECHNICAL PROPOSAL. Each Offeror shall submit a written proposal in accordance with Sections 1 through 4 below to enable the Government to evaluate the extent to which the proposal meets the Government’s requirements. Wherever relevant, the Offeror is encouraged to use cross-references to the applicable sections of the proposal, rather than repeating that information in the several sections of this volume. No cost/price information shall be included in the technical volume.

Offerors shall prepare Volume III to address the four (4) separate factors as follows:

Factor 1 – Integrated Master Schedule (IMS)

Factor 2 – Delivery Order 0001

Subfactor 2.1 - Delivery Schedule Adherence

Subfactor 2.2 – Terminal Maintainability – Repair Turn Around Time (TAT)

Factor 3 – Past Performance

Factor 4 - Small Business Participation

1.4.1 Section 1: Integrated Master Schedule (Factor 1)

The Offeror shall submit an event-based Integrated Master Schedule (IMS) containing the events, significant accomplishments, and accomplishment criteria necessary to successfully design, qualify and deliver MIDS JTRS CMN-4, TTNT and F-22 variant terminals within twelve (12) months after the anticipated award date. The IMS should delineate the Offeror’s planned schedule for all activities, events, milestones, and critical paths associated with executing the program. The IMS shall include the program schedule with technical tasks and activities necessary to deliver MIDS JTRS CMN-4, TTNT and F-22 variant terminals within twelve (12) months after the anticipated award date.

The IMS must provide a plan to meet, at a minimum, the Government’s schedule requirements and required development, test, and delivery events, to reflect the proposed approach. The IMS must be resource loaded and leveled and shall cover all work planned in this contract. The IMS shall be prepared in accordance with DID DI- MGMT-81861A, Integrated Program Management Report – Format 6, and shall be submitted in both Portable Document File (PDF) and MS Project (2007 compatible) file formats.

For purposes of developing the IMS, the Government’s notional schedule is detailed below.

Contract Award 18 March 2020

Qualification Complete of each MIDS JTRS CMN-4, F-22 and TTNT variant terminal.

For the Offeror to propose

Delivery of one (1) each MIDS JTRS CMN-4, F-22 and TTNT variant terminal.

Twelve (12) months from anticipated award date

1.4.2 Section 2: Delivery Order 0001: Lot 9 Production (Factor 2)

This factor will be awarded as Delivery Order (DO) 0001 to the Offeror or Offerors who are awarded the basic IDIQ contract(s). See Attachment 1 for the DO 0001 SOW.

Page Limitation: Ten (10) pages, single sided not including copies of certificates/approvals/letters/excel spreadsheet. The ten-page limitation applies to Factor 2 as a whole. Type size shall be Times New Roman and no smaller than 12 point. Any additional pages included in the Offeror’s proposal beyond the page limitation will not be considered in the Government’s evaluation.

The Offeror shall submit a technical proposal to enable the Government to make a thorough evaluation and arrive at a sound determination as to whether or not the Offeror will meet the requirements of the Government. To this end, each technical proposal shall be so specific, detailed, and complete as to clearly and fully demonstrate that the prospective Offeror has a thorough knowledge and understanding of the requirements and has valid and practical solutions for any technical problems. Statements that paraphrase the specifications or attest that “standard procedures will be employed, etc.,” are inadequate. Offerors are reminded that both independent data (e.g., data currently in the Government’s possession) and data provided by Offerors in their proposals may be used to evaluate the Offeror’s proposal.

The Offeror shall propose its technical approach to DO 0001 to include the following:

1.4.2.1 Delivery Schedule Adherence (Subfactor 2.1)

The Offeror shall include in its proposal a narrative demonstrating Delivery Schedule Adherence.

In addition, the Offeror shall provide a table in the format below that depicts the number of MIDS JTRS or equivalent terminals that meet the requirements of the Attachment 1 –SOW that were contractually required to be delivered (per contract Section F) (Column B) and the actual number of terminals that were accepted by the Government (Column C) each month (Column A). The Government expects any and all contracts/DOs cited under Factor 3: Past Performance that were represented as meeting some or all of the requirements of the Attachment 1 – SOW to be included in the table below.

The table shall be populated with the most recent data that spans a two-year period, for example from 1 October 2017 through 30 September 2019. The Government acceptance date for each terminal is the inspector sign-off date recorded in the Wide Area Workflow invoice for that terminal. This table is included in the page count.

(A) Month/Year

(B) Number of Terminals Required to be delivered

(C) Number of Terminals Accepted

TOTAL

1.4.2.2 Terminal Maintainability-Repair Turn Around Time (Subfactor 2.2)

The Offeror shall include in its proposal a narrative demonstrating their understanding of Repair Turn Around Time (TAT) requirements.

Additionally, the Offeror shall provide an excel file using the below table format listing all MIDS JTRS or equivalent terminals delivered for repair at the Offeror’s facility with the most recent data that spans a minimum of a one-year period, for example from 1 October 2018 through 30 September 2019. The Excel spreadsheet will not be included as part of the page count. The Offeror shall ensure that the information in this Excel file is also provided in PDF format as part of the Technical Volume, which will be included in the page count. For failed items that were received from the Government at the Offeror’s facility and then are subsequently re-sent to a subcontractor or other partner facility for repair, the repair time starts when the item was first received from the Government at the Offeror’s facility, not when the repairing subcontractor or partner received the item. For repair efforts that have not been completed, identify the date the failed item was received at the Offeror’s facility.

S/N PLATFORM FAILURE

DESCRIPTION

WARRANTY

(YES or NO)

DATE

RECEIVED AT

OFFEROR’S

FACILITY

(WARRANTY)

DATE

FUNDING

RECEIVED FOR

REPAIR (NON-

WARRANTY)

READY FOR

ISSUE DATE

DATE

SHIPPED

AFTER

REPAIR

1.4.3 Section 4: Past Performance (Factor 3)

The Offeror shall provide past performance information on recent contracts/DOs performed by the Offeror and/or its proposed major subcontractors for efforts relevant to the requirements of this RFP. “Relevant” is defined as design, development and delivery of MIDS JTRS CMN-4, F-22 and/or TTNT variant terminals that have achieved NSA Type 1 Certification, Department of Defense (DoD) DIACAP accreditations. “Recent” is defined as a contract currently being performed or having been performed within the last five (5) years. For purposes of past performance, a “major subcontractor” is defined as a subcontractor that will be performing at least 10 percent of the total proposed effort (by dollar value) under any resultant contract.

Offerors shall submit a description of previous experience in designing, manufacturing and providing sustainment, to include Problem Report resolution, SIPRNET maintenance and repairs, retrofits or updates for each configuration, MIDS JTRS CMN-4, F-22, and TTNT, as described in this solicitation. Additionally, Offerors shall submit previous experience with development of future ERs, BCs and BUs software of the same or similar nature, including use of the same or similar processes and approaches, as this solicitation. As a part of this description, Offerors shall identify the organizational entity and location where the appraisal was performed, the type of evaluation, the organization performing the evaluation, and the level earned.

Past performance on Federal Government contracts shall be provided if available. If the Offeror has not performed on a Federal Government contract within the last five (5) years, information on relevant state, local Government, and/or commercial contracts and/or subcontracts may be submitted instead. Furthermore, past performance information may also include predecessor companies that have past performance similar and relevant to the requirements of this RFP.

Offerors that have no relevant record of past performance must submit a signed and dated statement to that effect. Offerors with no relevant past performance will receive a Neutral rating.

(1) Attachment 23: The Offeror shall provide past performance information by completing Attachment 23, “Past Performance Reference Information Sheet,” for up to three (3) contracts. This information shall be submitted for no more than three (3) of the most current and relevant contracts for the prime contractor and/or proposed subcontractors.

(2) Attachment 24: If the Offeror’s past performance information is located in the Contractor Performance

Assessment Reporting System (CPARS) or the Past Performance Information Retrieval System (PPIRS) (as indicated in Block 15 of Attachment 24), then it is not necessary for Attachment 24 - Contractor Performance Questionnaire/Survey to be submitted. If available, attach the most recent CPARS evaluation for each experience (not to be counted against the page limitation). If CPARS evaluations are unavailable, ensure that the contact information references (Block 9(a)/9(b)) are accurate.

For those Offerors whose past performance information is not located on the automated systems, Offerors shall contact their references and request that each reference complete Attachment 24 “Past Performance Questionnaire/Survey,” and email the survey directly to joseph.gonzales1@navy.mil no later than the proposal due date.

The Government may consider questionnaires received after the due date of the solicitation. The Government reserves the right to contact references for verification or additional information. The Government reserves the right to utilize other past performance information considered relevant that may be located in Contractor Performance Assessment Reporting System (CPARS) or other reporting systems.

The Government reserves the right to use past performance information obtained from sources other than those identified by the Offeror. This past performance information may be used for the evaluation of past performance.

The Government does not assume the duty to search for data to cure the problems it finds in the information provided by the Offeror. The burden of providing thorough and complete past performance information remains with the Offeror.

1.4.4 Section 4: Small Business Participation (Factor 4)

All Prime Offerors (Large AND Small Businesses) shall submit a completed Small Business Participation Data form (Attachment 25). All Offerors shall discuss their approach to meeting the following desired Subcontracting Participation Objectives (as a percentage of all subcontracted effort):

Small Business Categories Subcontracting Participation Objectives (Based on % of all Subcontracted effort)

Total Small Business (includes the below) 30.00% Small Disadvantaged Business (SDB) 5.00% Woman-Owned Small Business (WOSB) 5.00% HUBZone 3.00% Service Disabled Veteran-Owned Small Business

(SDVOSB) 5.00%

Note: Large business concerns are required to submit a separate Small Business Subcontracting Plan in accordance with FAR 19.7 and FAR 52.219-9. The requirement for the Small Business Subcontracting Plan is in addition to the information required within the Small Business Participation section.

For each subcontractor proposed, Offerors must ensure that the subcontractor names and values listed in the Small Business Participation Data attachment match the subcontractor names and values throughout the entire proposal (Technical and Cost/Price). In addition to RFP Small Business Participation Data form, each prime contractor (whether a small or large business) shall submit the cover sheet for their letter of commitment with each proposed small business subcontractor. (Each letter shall detail the teaming agreement between the prime contractor and each proposed small business subcontractor, but only the signed cover sheet is required).

1.5 VOLUME IV: COST/PRICE PROPOSAL

52.215-20 Requirements for Cost or Pricing Data or Information Other Than Cost or Pricing Data (Oct 1997), Alt IV

Submission of certified cost or pricing data is not required. This volume shall contain cost/price information only.

1.5.1 Delivery Order 0001 Cost/Price Proposal: The Offeror shall submit a cost/price proposal for Delivery Order (DO) 0001 according to the instructions below.

1.5.1.1 CLINs 0001, 0002 and 0005. The Offeror shall propose using the Attachment 21 - Pricing Model for CLINs 0001, 0002 and 0005 that does not include warranty in accordance with the requirements of Clause B-1, and MIDS JTRS Production Statement of Work (SOW) (See Attachment 1). For evaluation purposes, the Government will use terminal prices including warranty prices to calculate a total terminal price. The Government reserves the right to reject any pricing model submitted that demonstrates an excessively steep curve. “Excessively steep” is defined as the pricing curve having a slope that exceeds 2.5% change in price per 5% change in award percentage.

1.5.1.2 Attachment 21- Pricing Model, is hereby locked to depict the configurations of terminal variants. The Offeror shall price only those variants identified in Section M-2. The MIDS JTRS (5) variant will only be ordered with the new Cryptographic Subsystem/Protected Core Processor (CSS/PCP) Shop Replaceable Unit (SRU) and Dash 11 (-11) Internal Power Supply (IPS). Any other configuration will not be acceptable. Spare SRUs, such as Red I/O, CSS/PCP and Chassis, may be procured through a Fair Opportunity Exception (FOE) using the prices for spares outlined in the Offeror submitted Pricing Model. Therefore, Offerors should not submit a separate pricing model for spares.

1.5.1.3 Warranty prices. The Offeror shall provide a complete Price List A: Warranty Unit Prices (Attachment 22).

Terminals and/or spares may be ordered with or without the warranty. Those MIDS JTRS terminals and/or spares ordered with the warranty shall include the price of the warranty in the total terminal price.

1.5.2 IDIQ Contract Cost/Price Proposal: The Offeror shall also submit a filled-in Section B for the overarching IDIQ contract according to the instructions below.

In addition to the DO 0001 proposal, Volume IV should include a filled-in Section B for the overarching contract showing cost and fee in the CLIN table. CLIN ‘ceiling’ amounts have been specified by the Government for each CLIN in Section B and in the table below. The Offeror’s cost proposal should fill-in cost and fee amounts appropriate to each CLIN totaling the specified ceiling. ODC and Proposal Preparation CLIN 0010 and 0011 amounts are non-fee bearing and are all inclusive (include contractor burdens such as General & Administrative expense, etc.). The Offerors shall not change the ceiling amounts. The Offeror should refer to the Section B clauses for each CLIN-type for additional information in preparing its cost proposal. The Gov’t does not require detailed cost element information for the overarching contract-level CLINs.

1.5.3 CDRL Price Table: Not Applicable. For the CDRL CLINS, the Offeror shall insert “Not Separately Priced” (NSP) in Section B. The cost of CDRLs shall be included in the cost the Offeror proposes for CLINs 0001-0003, 0006-0008 and 0010 as described in Section B.

CLIN Type Supplies/Services Maximum Amount

0001 FFP MIDS JTRS Terminals $ 531,900,000

0002 FFP MIDS JTRS Spares $ 84,500,000

0003 FFP MIDS JTRS Retrofits $ 25,593,750

0004 NSP Warranty for CLIN 0001

0005 NSP Data Exhibit "A" (CDRL)

0006 CPFF MIDS JTRS SE&I $ 300,000,000

0007 CPFF SE&I Materials $ 28,288,000

0008 FFP MIDS JTRS SE&I $ 17,841,114

0009 NSP Data Exhibit "B" (CDRL)

0010 COST Travel/ODC $ 7,137,000

0011 COST Proposal Preparation Cost $ 3,568,300

TOTAL $ 998,828,164

1.5.4 CDRL Data Rights Table (If applicable): The Offeror shall also fill in the CDRL Data Rights Price column in Attachment 11 - CDRL Table for the overarching IDIQ contract. If there are any costs associated with receipt of "Government Purpose Rights" and “Unlimited Rights” the Offeror shall provide those proposed costs in the Cost Volume using Attachment 11, and the Government may modify the resulting contract to include those costs as a non-fee bearing firm fixed price option CLIN(s) to Section B of the RFP. The table in Attachment 11 delineates the Government’s technical data, computer software, and computer software documentation rights by CDRL item. The rights classification applies only to the extent the CDRL item or parts thereof meet the definition of technical data, computer software, or computer software documentation. (NOTE: this table is not all-inclusive; the Offeror may add additional CDRL items during proposal submission.).

(End of Summary of Changes)

File details come from the government source that posted it. Updated .