N0002422R5206 Amendment 0003.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

See continuation page.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 29

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

16C. DATE SIGNED

BY 25-Apr-2022

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 N0002422R5206

X 9B. DATED (SEE ITEM 11)

15-Mar-2022

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, 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

25-Apr-2022

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2030

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0002422R5206

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been added by full text:

L-209-H009 NOTIFICATION OF POTENTIAL ORGANIZATIONAL OR PERSONAL CONFLICT(S) OF

INTEREST (NAVSEA) (APR 2022)

(a) Offerors are reminded that certain existing contractual arrangements may preclude, restrict or limit participation, in whole or in part, either as a subcontractor or as a prime contractor under this competitive procurement. Of primary concern are those contractual arrangements in which the Offeror provides support to PEO IWS 5.0, or related laboratories (if applicable), in support of operation of the office or any of its programs. General guidance may be found in FAR 9.505; however, this guidance is not all-inclusive. The Offeror's attention is directed to the "Organizational Conflict of Interest" (OCI) or similar requirement which may be contained in current or completed contract(s) which prohibits the prime or subcontractor from providing certain supplies or services to the Government as described above during the period of the current "support" contract(s) or for a period after completion of the "support" contract(s). Notwithstanding the existence or non-existence of an OCI or similar requirement in current or completed contract(s), the Offeror shall comply with FAR subpart 9.5 and identify whether an OCI exists and not rely solely on the presence of an OCI or similar requirement.

(b) Offerors also are reminded that certain potential conflicts of interest may arise where an Offeror has unequal access to nonpublic information about a competitor that may provide the Offeror with an unfair competitive advantage and preclude, restrict or limit participation, in whole or in part, either of the individual, subcontractor or prime contractor under this competitive procurement. For example, a potential conflict may arise if former Department of Navy employee(s), subcontractors, or teaming partners of the Offeror may have gained access to nonpublic information about a competitor through participation in previous or ongoing performance or during the solicitation development/source selection process associated with this competitive procurement, and then participates in the formation of the Offeror’s proposal. Other potential conflicts of interest may arise where either the former Department of Navy employee(s), subcontractors, or teaming partners of the Offeror under this competitive procurement set the ground rules for competition; for example, by drafting specifications or assisting in the drafting of the statement of work. General guidance may be found in FAR 3.101 and 9.505; however, this guidance is not all-inclusive.

(c) If an Offeror identifies a potential conflict of interest that exists at any tier, that Offeror is requested to notify the Contracting Officer within 14 days of the date of this solicitation. The Offeror shall provide: (1) the contract or previous source selection’s solicitation number and name and phone number of the Contracting Officer for the contract which gives rise to a potential conflict of interest; (2) a copy of the requirement; (3) the statement of work and technical instruction from the existing contract, as applicable; (4) a brief description of the type of work to be performed by each subcontractor under the competitive procurement; (5) a brief description of the individual’s, subcontractor’s, or teaming partner’s unequal access to nonpublic information about a competitor, which may lead to a conflict of interest in the formation of the Offeror’s proposal, or establishment of ground rules for this competitive procurement, as applicable; (6) an OCI mitigation plan, as applicable; and (7) any additional information the Contracting Officer should consider in making a determination of whether a conflict of interest exists. The Government may independently verify the information received from the Offeror. The requirement to identify potential conflicts of interest as outlined herein continues until contract award. Notwithstanding the above, the Government reserves the right to determine whether a conflict of interest exists based on any information received from any source.

(d) The Government will notify an Offeror of any conflict of interest within 14 days of receipt of all required information. Those Offerors deemed to have a conflict of interest may be ineligible for award. Failure to provide the information in a timely manner does not waive the Government's rights to make a conflict of interest determination. The Offeror is notified that if it expends time and money on proposal preparation, such expenditure is at its own risk regardless of whether the Government determines a personal or organizational conflict of interest does or does not exist.

(e) Any potential prime contractor which proposes an individual, subcontractor, or teaming partner later determined to have a conflict of interest and deemed ineligible to participate in the current competition, may not be granted the opportunity to revise its proposal to remove the ineligible individual, subcontractor or teaming partner. The Government reserves the right to determine which Offerors remain in the competitive range through the normal source selection process.

(f) If the Offeror determines that a potential organizational and/or personal conflict of interest does not exist at any tier, the Offeror shall include a statement to that effect in its response to this solicitation.

(End of provision)

The following have been modified:

SECTION L

1.0 GENERAL INFORMATION

In order to be considered for contract award under this procurement, the Offeror shall possess a Defense Security Service SECRET facility clearance with SECRET personnel clearances and SECRET safeguarding capability, all issued by the United States Government, by the time of award. SECRET facility physical construction must meet the requirements as defined in DoD 5205.07-M Vol 3. The Offeror (and any subcontractors performing SECRET-level work) shall not be:

• Under foreign ownership or control

• Under a special security agreement

• Restricted in access to Compartmented Information, Cryptographic Materials or Systems, Restricted Data, or Formerly Restricted Data.

The Government will not entertain any proposed revisions to the terms and conditions contained in this solicitation submitted as part of Offeror’s proposals, including any attachment or exhibit referenced therein. Therefore, any offer that includes “redlines,” condition(s) of offer, or any other deviation from the requirements of the solicitation may be rejected by the Government.

For proposal purposes, the estimated date of Award is fourth quarter of Government Fiscal Year 2022 (4Q FY22). The Government reserves the right to award sooner or later if necessary. The start and end dates will be updated accordingly upon Award.

Each Offeror is required to submit a proposal that is sufficiently detailed and complete to fully demonstrate an understanding of, and compliance with, all of the requirements of the solicitation. Proposals shall contain only material directly related to this acquisition. Offerors shall submit all information required by this solicitation.

Offerors’ proposals shall be based on the requirements contained in this solicitation (including those documents, exhibits, and other attachments to the solicitation identified in Section J). Offerors shall submit a proposal encompassing all of the line items listed in Section B of this solicitation. FAILURE TO FOLLOW THE

INSTRUCTIONS OR CONFORM TO ALL REQUIREMENTS OUTLINED IN THIS SOLICITATION

MAY RESULT IN REJECTION OF THE OFFEROR’S PROPOSAL.

Proposals submitted in response to the solicitation must contain a complete description of all pertinent aspects of the effort proposed by the Offeror. Offerors shall not assume that previously submitted data or prior experience presumed to be known to the Government (e.g., previous projects performed for the Government) will be considered as part of the proposal.

General statements such as, “the Offeror understands,” “the Offeror can or will comply with the requirements,” “standard procedures will be used,” “well-known techniques will be used,” or statements which merely paraphrase the solicitation in whole or in part do not constitute compliance with the requirements for proposal content. Data previously submitted, or presumed to be known (e.g., data or services previously submitted or performed for the Government) cannot be considered as part of the proposal unless explicitly incorporated into the proposal.

Discussions of each topic in the proposal shall exhibit continuity and logical progression.

1.1 GOVERNMENT-WIDE POINT OF ENTRY (GPE)

This solicitation will be made available only through the Internet on the SAM.gov website (https://sam.gov). From time to time, the Government may post additional information to the SAM.gov website relating to this solicitation (e.g. responses to questions, solicitation amendments, etc.). It is the responsibility of prospective Offerors to monitor the SAM.gov website for any such information.

1.2 COMMUNICATIONS WITH THE GOVERNMENT

Unless otherwise specified, the Naval Sea Systems Command Procuring Contracting Officer (PCO) and Contract Specialist (CS) are the sole Government points of contact for this acquisition.

Shannon Vineyard Procuring Contracting Officer shannon.l.vineyard.civ@us.navy.mil

(202) 812-0429

Courtney Schlusser Contract Specialist courtney.j.schlusser.civ@us.navy.mil

(202) 781-3399

1.3 AVAILABILITY OF ATTACHMENTS AND GFI

The Government will make Government Furnished Information (GFI) available to Offerors containing information to assist in the preparation of a proposal. GFI may contain classified data and/or technical data whose export is restricted by the Arms Export Control Act (Title, U.S.C. Section 2751 et seq. or Executive Order 12470).

To request the GFI, please submit a completed copy of the DD Form 254 and a current copy of your company’s approved DD Form 2345, Military Critical Technical Data Agreement (verifying eligibility and authority to receive export-controlled information) via email to the PCO and CS identified in L.1.2 above. Please reference the name of your company and “N0002422R5206 GFI Request” (without quotes) in the subject line of the message. In the body of the email, provide the name and email address of a company individual who will receive a secure download link for the unclassified GFI. If the Government has already granted your company access to the GFI for this procurement, please indicate this also in the body of the email. Offerors that previously executed a Terms of Use Agreement (TOUA) during the pre-solicitation phase for this solicitation must still submit a request via email to the PCO and CS to obtain GFI, and resubmit new TOUA.

The Government will verify the DD Form 254 and DD Form 2345 submission. Upon successful verification, the Government will provide a copy of a TOUA that must be signed by an authorized representative of the prospective Offeror and returned to the Government. Upon receipt of a duly executed TOUA, the Government will provide via email to the designated company representative a secure DoD Secure Access File Exchange (SAFE) download link for the GFI. Over the course of the procurement, the Government may provide additional or revised GFI to the same designated company representative.

The deadline to request access to the GFI shall be the same as the deadline to submit bidder’s questions regarding this solicitation.

1.4 SUBMISSION OF QUESTIONS AND COMMENTS

Offerors shall submit written questions and comments related to this solicitation using the Bidder’s Question Submittal Form (Attachment S-2) for this solicitation. For ease of Government review and to minimize response time, Offerors shall submit this form in the original file format. Do not convert the form to Portable Document Format (PDF). To ensure the Government understands the context of the question, Offerors shall detail the applicable document name, document date or version, page, paragraph, clause or other specific citation to which the question applies. Information contained in the Government’s responses to bidder’s question shall not supersede any information contained in the solicitation (including amendments). In the event of a discrepancy between a response to a bidder’s question and the content of the solicitation, the solicitation shall take precedence.

Offerors shall not submit comments, questions, or inquiries to any Government representative other than the PCO and CS identified herein.

The Government intends to distribute bidder’s questions and associated responses via public posting to the Governmentwide point of entry (GPE). However, any question or response that contains classified or controlled unclassified information will not be posted publicly, but rather will be sent directly to those Offerors who have an executed TOUA and meet the security requirements detailed herein.

In the event that a prospective Offeror wishes to submit a comment or question that the prospective Offeror believes addresses a subject that is specific or proprietary to the Offeror, then the Offeror shall mark the question accordingly on the submission form and provide justification to support its claim. If the Government concurs with this identification, the Government will respond only to that potential Offeror. If the Government does not concur with this identification, it will inform the submitting Offeror and will not provide any further response. The Offeror may resubmit the question without the proprietary marking.

Offerors shall submit in accordance with this section any questions or suggestions related to the terms and conditions of this solicitation prior to the deadline for questions.

The deadline for receipt of questions is March 29, 2022. Any questions received after this date may not be answered prior to receipt of proposals.

1.4.1 UNCLASSIFIED QUESTIONS

Submit written unclassified questions related to this solicitation via email to the PCO and CS identified in Section L

1.2 above. Reference “N0002422R5206 Question from [name of Offeror]” (without quotes or brackets) in the subject line of the message.

1.5 SOLICITATION SECURITY CLASSIFICATION

This solicitation is unclassified, although some information provided in conjunction with this solicitation may be classified. All employees of the Offeror working on the classified portion of its proposal shall have active security clearances at the appropriate classification level. Offerors must provide a completed DD Form 254 in order to gain access to and handle classified materials. Offerors must meet all clearance requirements detailed in the DD Form 254 by the time of contract award.

The Government does not anticipate a need for Offerors to submit classified material in any proposal volume.

OFFERORS SHALL NOT PLACE ANY CLASSIFIED INFORMATION IN ANY PORTION OF ITS

PROPOSAL.

1.6 AWARD WITHOUT DISCUSSIONS

Pursuant to the provision under this section entitled FAR 52.215-1, “Instructions to Offerors – Competitive Acquisition,” the Government intends to award a single contract on the basis of a proposal submission without conducting discussions with Offerors, but reserves the right to conduct discussions per FAR 15.306 “Exchanges with Offerors After Receipt of Proposals” if determined by the PCO to be necessary. Each Offeror shall submit only one proposal. No alternate proposals will be accepted, and the submission of multiple proposals will result in rejection of all proposals submitted by the offeror. Therefore, each Offeror’s proposal submission shall contain the Offeror’s best terms from a price and technical standpoint. However, the Government may contact any, all, or a limited number of Offerors with questions concerning their proposals as permitted under FAR Part 15. Upon the conclusion of discussions, if they occur, the Government will request Final Proposal Revisions (FPRs) from all Offerors still within the competitive range.

1.7 PROTECTING CONTROLLED UNCLASSIFIED INFORMATION

Pursuant to DFARS 252.204-7008(c)(1), prospective Offerors are advised that proper safeguarding of Controlled Unclassified Information (CUI) is considered a special standard of responsibility for this solicitation. See FAR subpart 9.1. Failure to properly safeguard and mark Controlled Unclassified Information in a prospective Offeror’s proposal in accordance with applicable regulation and policy (to include Executive Order 13556, the Defense Federal Acquisition Regulations Supplement and DoD Instruction 5200.48) may preclude the PCO from being able to provide the required affirmative determination of responsibility. If the PCO is unable to affirmatively determine the prospective Offeror to be responsible, the prospective Offeror will be ineligible for award.

2.0 GENERAL PROPOSAL INSTRUCTIONS

The completion and submission to the Government of an offer shall indicate the Offeror’s unconditional acceptance of the terms and conditions in the solicitation.

The Government encourages Offerors to contact the PCO and CS via the Bidder’s Question Process as outlined in Section L.1.4 above.

Offerors shall take care to submit a legible, neat, orderly, concise and comprehensive proposal. Elaborate brochures or artwork, expensive paper or bindings, or expensive visual or presentation aids beyond those sufficient to present a complete and comprehensive proposal are unnecessary. Clarity is essential. The use of brochures shall be minimized and if used will count against page limits.

2.1 PROPOSAL STRUCTURE, FORMAT, AND PAGE COUNTS

Offerors shall structure proposal submittals such that the required content is organized as follows:

VOLUME

TITLE

PAGE LIMIT

PAPER

ORIGINAL

DUPLICATES

ELECTRONIC

COPIES

I Technical Approach and

Production Capabilities

150 1 1 1

II Management Approach 50 1 1 1

III

Past Performance

See Note 1

IV Cost/Price Proposal

None 1 1 1

VOLUME

TITLE

PAGE LIMIT

ORIGINAL

DUPLICATES

ELECTRONIC

COPIES

V Standard Form (SF)

33/Completed Contract None 1 1 1

Note 1: The total page limit for this volume will vary depending on the number of subcontractors for which the Offeror must provide past performance information. The past performance narrative for the Offeror shall not exceed five pages in length. The past performance narrative for applicable subcontractors (see Section L.3.3) shall not exceed two pages in length for each subcontractor. Therefore, the page limit for this volume shall be (5 + 2x), where x represents the number of applicable subcontractors. For further details, see the instructions for Volume III.

Each Offeror shall submit paper hard copies and separate electronic copies on CD-ROM or DVD media in the quantities specified above. All copies shall contain the same information and format as the original. See Section L.3 and subparagraphs for instructions regarding proposal content that must be submitted solely on electronic media and omitted from the paper versions of the volume, including the original and any copies thereof. Proposal content designated by this solicitation for electronic submission only (e.g., Integrated Master Schedule, Contract-wide Staffing Plan, etc.) does not count against the solicitation page limits. Each submitted paper proposal page shall also include standard 2-3/4" center-to-center holes positioned symmetrically at the top of each page (i.e. 2-hole file binder punch on top edge).

Offerors are advised that the quality of information contained in a proposal is significantly more important than quantity. In this respect, Offerors shall strictly observe the page count limitations for each volume. Pages in excess of the applicable page count limit will be removed by the PCO from the back of the respective volume prior to evaluation and shall not be read or evaluated by the Government. It is not necessary to supply the maximum number of pages allowed for each volume; fewer pages may be submitted. Offerors shall organize proposal content sections using index pages or tabbed index divider pages with clear cross-referencing to the table of contents. All pages shall be consecutively numbered within each volume (e.g., 1,2,3,), with the exception of the Cost/Price Volume. For the Cost/Price Volume only, pages must be numbered consecutively within each section, but page numbering may restart at the beginning of each section.

Section L.3 identifies specific items that will be exempt from the page count limitations set forth above. In addition, the following proposal content will be exempt from the page count limitations:

• Cover letter

• Table of contents

• Title pages

• Annex pages

• Index pages

• Tabs

• Glossary

• Attachment J-S1 - Contract-wide Staffing Plan, template to be completed by Offeror

• Attachment J-S2 - Bidder’s Question Submittal Form, template to be completed by Offeror

• Attachment J-S3 - RESERVED

• Attachment J-S4 - Integrated Master Schedule (IMS)

• Attachment J-S6 - Total Cost/Price Build Up Spreadsheet

• Attachment J-S7 - Small Business Subcontracting Plan, incorporated upon award as Attachment J-12

• Attachment J-S8 - Contractor Award Information, template to be completed by Offeror

The Government may consider any failure on the part of an Offeror to comply with these instructions to be an indication of how the Contractor will comply with contract requirements during contract performance. Therefore, if any questions arise, the Government encourages Offerors to contact the PCO and CS via the Bidder's Question Process outline in Section L.1.4.

2.2 LABELING AND PACKING

Offerors shall pack and submit all proposal binders in cardboard (or equivalent) boxes that may be lifted and handled manually. Offerors should observe a reasonable maximum weight for each box and avoid overloading any single box. Boxes must be sequentially numbered with the box numbers marked on all sides of each box, and written on all sides of the outside wrapper, if necessary. Submit all copies of electronic media in a single box. If submitting more than one box, include in one of the boxes a master packing list summarizing the contents (i.e., volume number, copy number, and volume name) of each box, by box number. These instructions also apply to all subcontractor submissions.

Offerors shall submit all volumes in three-ring binders with index tabs or tabbed index divider pages separating each section. Each proposal section shall start on a new page. Each volume shall contain a table of contents that lists the sections, subsections, and page numbers. Each volume shall also include a glossary explaining all abbreviations and acronyms used.

Offerors are responsible for the condition of delivered proposals. Binders and their contents that are broken apart or received in a disorderly fashion will be reassembled by the Government in a manner with expeditiousness as the rule. The Government is not responsible for proper reassembly of such binders. Thus, binders may not be reassembled as originally sent.

The first page of each proposal volume shall display the information required by FAR 52.215-1(c)(2) and shall also contain the volume number, volume title, security classification level of the volume and serial/copy number. If an Offeror wishes to restrict the disclosure or use of its proposals, the Offeror shall use the legend permitted by FAR 52.215-1(e) and prominently indicate the specific pages and paragraphs that contain proprietary information. Each page of an Offeror’s proposal shall be labeled with the Offeror’s name, solicitation number and date corresponding to the date of the proposal, and CUI designation.

All information relating to contract pricing data shall be included only in the section of the proposal designated as the Cost/Price Volume IV. UNDER NO CIRCUMSTANCES SHALL OFFERORS INCLUDE CONTRACT COST AND PRICING DATA IN VOLUMES I THROUGH III. In the event that pricing data are included in Volumes I through III, that data will be excluded from the evaluation.

Unless otherwise stated in this solicitation, Offerors shall ensure that electronic versions of proposals do not contain any information not included in the paper versions. In the event of a discrepancy between the paper version and electronic version of a proposal, the electronic version will govern. Electronic proposal submissions and supporting information shall be submitted on CD-ROM or DVD media in a format that can be accessed using a standard PC-compatible CD-ROM/DVD drive. via the Procurement Integrated Enterprise Environment (PIEE) website (https://piee.eb.mil) and shall be sent to both the PCO and Contract Specialist listed in local text G-242-H001. If files are password protected, passwords shall also be provided to the PCO and Contract Specialist listed in G-242- H001. The Government will not accept submissions on any other electronic media, such as flash memory cards or USB flash drives. All files submitted to the Government shall be compatible with Microsoft Office 2016. All viewgraphs shall be submitted in Microsoft PowerPoint format. All spreadsheets shall be submitted in Microsoft Excel format with all mathematical equations used for calculations visible and traceable. All text and proposal narrative shall be submitted in Microsoft Word format. All schedules shall be submitted in Microsoft Project format.

No fields or documents may be password protected. Offerors shall not embed sound or video files into the electronic files. All Microsoft Excel files shall be completely readable and editable such that the Government may readily ascertain the validity of the pricing or other data contained therein. All data and tables shall be submitted in a printable format.

Each CD-ROM/DVD shall be labeled with the solicitation number, proposal volume number and title, the Offeror’s name, date of submittal, security classification level, serial/copy number, any restrictive marking permitted by the FAR (See FAR Part 15), and “Source Selection Information – See FAR 2.101 and 3.104.” The Offeror shall also submit a hardcopy directory listing with each CD-ROM/DVD submitted. Separate files shall be used to enable rapid retrieval of all contents, including exhibits, appendices, and attachments, if any. Prior to submittal, the Offeror shall screen all CD-ROMs/DVDs to ensure that the media does not contain computer viruses or other malware. Each volume shall be organized into directories within the CD-ROM/DVD that duplicate the volumes and partitions used in the paper version of the proposal.

All unclassified CD-ROMs shall be marked CUI//SP-SSEL//FEDONLY. Offeror proposals shall comply with the requirements of Executive Order 13556 and DoD Instruction 5200.48.

2.3 PAGE SIZE AND FORMAT

The narrative material in each proposal shall be single-spaced, typed, or printed in 12-point Times New Roman font.

Paper, excluding foldouts, shall be 8 1/2 × 11 inches (standard letter size) with a minimum margin of 1 inch around the page. Text within tables, diagrams, pictorial charts, or graphic material may use no smaller than 8-point font in Times New Roman or Arial typeface.

Every section, figure, and table shall be numbered; paragraphs within sections do not need to be numbered.

Proposal material shall be presented on double-sided pages only and in a single column on each page in accordance with FAR 52.204-4. Each double-sided page counts as 2 pages.

Foldout sheets may be used for charts and graphs where necessary to depict organization, layout, or implementation schedules. Foldouts shall be uncomplicated to preserve clarity. Extensive written text or tabular data, beyond that reasonably required for clarity, shall not be included in the material presented on the foldout sheet. Foldout pages shall fold entirely within the volume and shall not exceed 11 × 17 inches. Each non-blank side of a foldout page will count as two pages for page count purposes. Foldouts for the entire proposal are limited to a total of 25 foldout sheets. Foldout sheets contained in the Cost/Price Proposal (Volume IV) do not count towards the 25 foldout sheet limit.

2.4 PROPOSAL SUBMISSION

Proposals in response to this solicitation shall be submitted to the Government no later than the time specified in Block 9 of the SF 33. “Local time” shall refer to the time zone for Washington, DC.

Telegraphic offers, facsimile offers, or offers submitted by electronic commerce will not be considered. Any proposals received through these means will be deleted or destroyed. Furthermore, the Government will not consider telegraphic, facsimile, or electronic commerce modifications of offers, or withdrawals of offers.

Each Offeror shall submit electronic copies using the method and quantities specified above. Electronic copies delivered via the Procurement Integrated Enterprise Environment (PIEE) website (https://piee.eb.mil), Solicitation Module, shall be sent to both the PCO and Contract Specialist listed in local text G-242-H001. If files are password protected, passwords shall also be provided to the PCO and Contract Specialist listed in G-242-H001.

The preferred method of response is by overnight delivery service, such as FedEx, UPS, or DHL. Do not use the United States Postal Service.

All copies of the proposal shall be submitted to the CS at the address below.

Naval Sea Systems Command Attn: Courtney Schlusser, SEA 02534S 1333 Isaac Hull Ave SE Mail Stop 2040 Washington Navy Yard, DC 20376-2040

N0002422R5206

PROPOSAL

DO NOT OPEN IN MAIL ROOM

https://piee.eb.mil/

For instructions on delivering hand-carried proposals, see the provision in this section entitled L-204-H002, SPECIAL PROPOSAL RECEIPT REQUIREMENTS FOR WASHINGTON NAVY YARD.

2.5 MAJOR SUBCONTRACTOR PROPOSALS

For the purposes of this solicitation, major subcontractors are defined as any cost-reimbursement subcontractor proposed to perform 10% or more of the cumulative hours under CLINs X002 and X008. However, where otherwise minor subcontractors cumulatively perform more than 20% or more of the cumulative hours under CLINs X002 and X008, all subcontractors performing under cost-reimbursable arrangements are considered major subcontractors and must propose as such.

Major subcontractors may submit proposals or supporting information directly to the Government. The prime Offeror shall be responsible for the timeliness of any major subcontractor submissions. Failure to submit major subcontractor proposals by the proposal due date may render the entire proposal, including the prime Offeror's proposal unacceptable. All subcontractors that do not meet the definition of major subcontractor are minor subcontractors.

3.0 PROPOSAL CONTENT REQUIREMENTS

Offerors shall provide the information requested in the following paragraphs in the volumes indicated. If additional information is provided in other volumes or sections, Offerors shall provide clear references to the location in the proposal where the information may be found.

An Offeror’s proposal shall be sufficiently detailed to enable Government evaluation members to make a thorough evaluation against specific factors established in Section M, and to arrive at a sound determination as to whether or not the prospective Offeror will be able to perform in accordance with the stated requirements. Discussions of each topic in the proposal shall exhibit continuity and logical progression. Data shall be organized to enable Government personnel to thoroughly evaluate the proposal. A concise, legible, neat, orderly and comprehensive proposal is required. The Government does not assume the duty to search for data to cure problems it finds in proposals.

3.1 VOLUME I: FACTOR 1 – TECHNICAL APPROACH AND PRODUCTION CAPABILITIES

Do not include cost or price information in this volume. The information contained in this volume shall enable Government personnel to thoroughly evaluate and arrive at a sound determination of whether or not the proposal meets the requirements of the solicitation. To this end, this volume shall be specific, detailed, and complete enough to demonstrate clearly and fully that the Offeror has an adequate technical approach to meeting the solicitation requirements, a sufficient understanding of the program objectives and has a thorough understanding of the solicitation requirements for accomplishing the efforts under this solicitation and the technologies involved. The proposal shall also demonstrate that the Offeror has sufficient experience and capability to successfully perform its proposed technical approach. Proposals may include block diagrams, flow diagrams, sketches, drawings, schematics, and interface descriptions required to describe the Offeror's proposed concept. The technical section shall sufficiently show how the Offeror proposes to comply with the Government's requirements and must include a full explanation of the methodology and procedures to be followed. The Offeror shall also identify and evaluate any risks associated with the Offeror’s proposed approach and propose mitigation steps to minimize the Government’s risk in accepting the Offeror’s proposed solution.

The Offeror shall clearly state any and all assumptions made in developing the proposed solution. Attachments J-2 and J-3 provide a complete list of all Government Furnished Information (GFI) and Government Furnished Property (GFP) that the Government intends to provide under this contract. The Offeror shall not assume the use of any GFI or GFP not listed in Attachments J-2 and J-3. The Technical Approach and Production Capabilities Volume shall address the following elements:

Element 1: System Design Element 2: Ship Interfaces Element 3: System Compatibility and Interoperability

Element 4: Software Production Approach Element 5: Logistics Management, Reliability and Maintainability

An extended description of desired proposal content is included below:

3.1.1 Element 1: System Design

3.1.1.1 The Offeror shall provide detailed and comprehensive descriptions of the proposed AN/SRQ-4 CDL system.

The descriptions shall include any drawings, functional diagrams, analyses, part numbers, National Item Identification Numbers (NIINs) and other material necessary to convey a clear understanding of the proposed equipment design and ability of the proposed design to meet all the requirements of the Performance Specification for the Common Data Link (CDL) Hawklink AN/SRQ-4 which shall be referred to in this document as the “AN/SRQ-4 Specification” and Statement of Work For Common Data Link Hawklink AN/SRQ-4 Procurement which shall be referred to in this document as the “SRQ-4 SOW”. The descriptions shall include explanations of the functionality allocated to each of the individual system components, the interconnections between individual system components, and the interconnections between system components and existing ship and aircraft equipment. The maturity of the proposed systems shall be described, and for each individual system component the proposal shall describe whether, and to what extent, the component is already in production. If a proposed system component requires modifications from components that are currently in production, then the type and extent of the required changes shall be described and documented in ECP (Form 1692) delivered with the proposal. The Offeror shall identify and describe any unique or specialized test equipment necessary to support, install, align, or maintain its equipment other than 10-MHz to 18-GHz spectrum analyzer, Navy Subcategory (SCAT) code 4338.

The Offeror shall describe the current status of each component of the proposed system relative to each of the following requirements contained in the AN/SRQ-4 Specification and SRQ-4 SOW:

a. Compliance with Design Verification and Environmental Qualification (ENV Qual) requirements cited in the Design Verification and ENV Qual columns of AN/SRQ-4 RTS Specification Figure SRQ-1907.

If not currently compliant, the Offeror shall describe in detail how they will meet these requirements in time to support the Section F delivery schedule.

b. Shipboard Shock (see AN/SRQ-4 Specification paragraph 3.2.5.14) performance and shipboard

Installation Control Drawing (ICD) compliance of Offeror’s proposed system. The description shall include all above deck components and all below deck components to be provided by the Offeror. The Offeror shall provide a description and schedule of all remaining steps necessary for Navy shock approval including schedule needed to incorporate all equipment changes and schedule needed for interaction with and response from Navy subject matter experts and technical warrant holders. A description of existing compliant shipboard shock certifications may be provided if applicable.

c. Compliance with TEMPEST (see AN/SRQ-4 Specification paragraphs 3.3.2.3 and 4.1.1.8). If not currently compliant, the Offeror shall describe in detail how they will become so in time to support the Section F delivery schedule. The description shall include schedule needed to incorporate all equipment changes and schedule needed for interaction with and response from Navy subject matter experts and technical warrant holders. A description of existing compliant TEMPEST performance may be provided if applicable.

d. Compliance with MIL-STD-461E Electromagnetic Interference/Electromagnetic Compatibility

(EMI/EMC) requirements of the AN/SRQ-4 RTS Specification. If not currently compliant, the Offeror shall describe in detail how they will become so in time to support the Section F delivery schedule.

e. Compliance with AN/SRQ-4 Specification and SRQ-4 SOW crypto requirements using a CCM Crypto

Core suite implementation. The Offerfor’s implementation shall be certified by the NSA. If not currently compliant, the Offeror shall describe in detail how they will become so in time to support the Section F delivery schedule.

f. Compliance with Commercial Off the Shelf (COTS) Software Supportability requirements of SRQ-4 SOW paragraph 4.1.29. If not currently compliant, the Offeror shall describe in detail how they will become so in time to support the Section F delivery schedule.

h. Compliance with AN/SRQ-4 Specification and SRQ-4 SOW CDL waveform requirements using CDL

Rev F and BE-CDL Rev C (or later). If not currently compliant, the Offeror shall describe in detail how they will become so in time to support the Section F delivery schedule.

i. Compliance with Risk Management Framework (RMF) implementation requirements in accordance with DODI 8500.01 Cybersecurity and DODI 8510.01 Risk Management Framework for DOD Information Technology (IT).

j. Compliance and certification with the Joint Interoperability Test Command (JITC) office. If not currently compliant, the Offeror shall describe in detail how they will become so in time to support the Section F delivery schedule.

k. Compliance with Controlled Unclassified Information requirements found in Executive Order 13556, DoD Instruction 5200.48, and NIST 800-171.

Test results or demonstration of compliance shall be included with the proposal for all system components that have already completed the tests and demonstrations in paragraphs 3.1.1.1 a through 3.1.1 k of this section. For all system components that have not already completed the tests or demonstrated compliance with paragraphs 3.1.1.1 a through 3.1.3 k, and for system components, which are changed from those which have previously demonstrated compliance, the Offeror shall propose a plan for verifying compliance with all of these requirements prior to the first production delivery. If the proposed schedule substitutes analysis, similarity, inspection or demonstration for a PIDS requirement for Test, then the Offeror shall provide data demonstrating that the differences between the proposed system component and a previously tested component are sufficiently minor to justify this approach. In this case, Government-approved unclassified test reports for the previously tested component shall be included with the proposal. If not currently compliant, the Offeror shall describe in detail how they will become compliant in time to support the RFP Section F delivery schedule.

3.1.1.2 The Offeror shall describe the extent to which proprietary or otherwise limited or restricted components, subsystems, interfaces, and software are used. For rights in Technical Data/Computer Software/Computer Software Documentation (TD/CS/CSD), the Contractor shall explain the degree to which the proposal provides the level of technical data rights (commercial and noncommercial) and rights in computer software that will enable the Navy to sustain the AN/SRQ-4 RTS throughout its lifecycle. If an Offeror proposes to deliver any commercial or noncommercial TD/CS/CSD with less than Government Purpose Rights (GPR), the Offeror shall describe the impact on the Government's ability to use, modify, release or disclose such TD, CS, or CSD. The use of proprietary algorithms, designs, processes or interfaces shall be described. The Offeror shall provide justification and rationale for all intellectual property and data rights assertions.

i. DFARS 252.227-7017 ASSERTIONS LIST The Offeror shall list all noncommercial TD, CS, and CSD that it asserts will be delivered with other than unlimited rights. Specific instructions and requirements concerning this list are set forth in the DFARS 252.227-7017 provision incorporated at Section K of this solicitation. If the Offeror does provide assertions, this paragraph shall also serve as the PCO’s request for the Offeror to submit evidence and information to evaluate and validate the listed assertions. Additionally, if there is no data or software to be identified in the DFARS 252.227-7017 list, the Offeror shall submit the list and enter “None” in the body of the list. If the Offeror is awarded a contract, the DFARS 252.227-7017 list shall be incorporated into the contract.

ii. DFARS 252.227-7028 ASSERTIONS LIST The Offeror shall list all noncommercial TD, CS, and CSD that it intends to deliver with other than unlimited rights and that are identical or substantially similar to noncommercial TD, CS, or CSD that the Offeror has delivered to, or is obligated to deliver to, the Government under any contract or subcontract.

Specific instructions and requirements concerning this list are set forth in the DFARS 252.227-7028 provision incorporated at Section K of this solicitation. Additionally, if there is no data or software to be identified in the DFARS 252.227-7028 list, the Offeror shall submit the list and enter “None” in the body of the list. If the Offeror is awarded a contract, the DFARS 252.227-7028 list shall be incorporated into the contract.

iii. SUPPLEMENTAL INFORMATION STATEMENT The Offeror shall include in its offer a statement entitled “Supplemental Information—Noncommercial Technical Data, Noncommercial Computer Software, Noncommercial Computer Software Documentation” (the statement) that, for each item of noncommercial TD, CS, or CSD that the Offeror asserts should be delivered with specifically-negotiated license rights (as discussed at DFARS 252.227-7013 and/or DFARS 252.227-7014), sets forth a complete description of all such proposed restrictions on the Government’s ability to use, modify, release, perform, display, or disclose such TD, CS, or CSD. This information shall be provided by referencing and delivering any and all proposed license agreements that are attached to the statement. The Offeror shall submit the statement dated and signed by an official authorized to contractually obligate the Offeror. If there is no information to be included in the statement, the Offeror need not submit the statement. If the Offeror is awarded a contract, any statement provided will be incorporated into the contract.

iv. COMMERCIAL RESTRICTIONS LIST The Offeror shall submit a list entitled “Commercial Technical Data, Commercial Computer Software, and Commercial Computer Software Documentation-Government Use Restrictions” (the Commercial Restrictions List), that the Offeror (including its sub-Offerors or suppliers, or potential sub-Offerors or suppliers, at any tier) intends to deliver with other than unlimited rights license. The list shall include: (1) identification of the data or software; (2) basis for asserting restrictions; (3) asserted rights category; and

(4) name of the person asserting restrictions. For any item designated as non-developmental items (NDI), the Offeror shall provide details of the Agency and level therein that paid for development and the contract number(s) and dates wherein payments were received. If there is no information to be included in the Commercial Restrictions List, the Offeror shall submit the list and enter "None" in the body of the list. If the Offeror is awarded a contract, the Commercial Restrictions List shall be incorporated into the contract as Attachment J-10

3.1.2 Element 2: Ship Interfaces

The Offeror shall describe in detail how its proposed equipment complies with Ship ICD 45105-0001. The description shall demonstrate that the proposed system is operational with the intended platforms without requiring change to those platforms. The description should utilize drawings, functional diagrams, analyses, and any other material considered necessary by the Offeror, to convey a clear understanding that the proposed equipment meets platform installation requirements. The Offeror shall provide written narratives for each system/subsystem physical and electrical interfaces that demonstrate compliance to ICD requirements. The narratives shall describe the current maturity of the proposed equipment and the type and extent of any changes that will be made to bring the equipment into full compliance with either set of Ship ICDs. If not currently compliant, the Offeror shall describe in detail how they will become so in time to support the RFP Section F delivery schedule.

The Offeror shall describe compliance with Interface Design Specification (IDS) computer message definitions.

The description shall demonstrate that the proposed software will interface with SPOP and MH-60R AOP without requiring alterations to either of these programs. The description shall utilize any material considered necessary by the Offeror to convey a clear understanding that the proposed software meets the equipment interfacing requirements. To establish full compliance with the SAU07000 IDS, the description shall also describe the current maturity of the proposed software, including the total planned source lines of code (SLOC), planned SLOC re-use from existing software, amount of new or modified SLOC required, and the extent of and plan for any remaining coding or test efforts required. The Offeror shall describe the qualification and compliance status of its proposed systems with these computer message definitions.