N00024-20-R-6405-0005.pdf

N0002420NR99504

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 Cummary of Changes

1. CONTRACT ID CODE PAGE OF PAGES

J 1 37

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

16C. DATE SIGNED

BY 22-Feb-2021

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

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

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

X 9B. DATED (SEE ITEM 11)

05-Jan-2021

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

22-Feb-2021

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2060

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0002421R6405

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

AMENDMENT 0005

# Date Source Page

Section/ Paragraph

Question Proposed Action/Change

Answers

52 2/19/2021 RFP

Section L provides procedures related to the submission of classified information, however the delivery address for the classified information is not provided within the solicitation nor the DD254. We respectfully request the Government to provide an appropriate delivery address for the classified portion of the proposal submittal.

The Government to provide an appropriate delivery address for the classified portion of the proposal submittal.

See Amendment 0005, section

L 1.1

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

1.0 General

The proposal shall be specific and complete so as to clearly demonstrate to the Government that the Offeror has a thorough comprehension of and capabilities to perform all aspects of the solicitation requirements.

The Offeror shall submit all information required by this solicitation. Failure to comply with the terms and conditions of the solicitation may result in the Offeror being removed from consideration for award. The Offeror’s proposal shall be based on the technical and contractual requirements contained in this solicitation (including those documents, exhibits, and other attachments to the solicitation identified in Section J). Offerors are required to submit a proposal encompassing all items listed in Section B herein.

The solicitation will be made available only through the Government-wide point of entry at: https://beta.sam.gov/

Offerors are hereby notified that from time to time, the Government may post additional information to the website relating to this solicitation (e.g. responses to questions, amendments, etc.). It is the Offeror’s responsibility to check the website for any such information.

(a) Communications with the Government Offerors may electronically submit written questions (unclassified only) requesting clarification of solicitation requirements in accordance with the Bidder’s Question Submittal Form (Attachment L-1). No comments, questions or inquiries shall be made of any Government person other than the points of contact listed below. The Government intends to distribute all bidder questions and associated responses via public posting to the BETA.SAM website.

It is the Government’s intention that all other publication of questions and answers in response to the solicitation will be announced via the https://beta.sam.gov/ website. However, an answer that contains technical data whose export is restricted by the Arms Export Control Act (Title, U.S.C. Section 2751 et seq. or Executive Order 12470) will be sent directly to those Offerors who have an approved executed DD254 and a signed “Terms of Use” letter.

The Government will not entertain any proposed revisions to the terms and conditions contained in this solicitation submitted as part of the Offeror’s proposal, including any attachment/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 as non-compliant. As such, any questions or suggestions related to the terms and conditions of this solicitation shall be made known by the Offeror in accordance with this section and the deadline for questions below.

It is the Government’s intention that questions and responses will be distributed electronically to all offerors.

Information provided with each question shall include the document name, document date, specific page, paragraph, clause or other definitive citation requiring clarification.

No information contained in the answers to bidder’s question shall supersede any information contained in the solicitation (including amendments).

The deadline for receipt of questions is close of business (COB), 1700 Eastern Standard Time, thirty (30) days from date of solicitation release (see Block #5 on SF33 cover page).

UNCLASSIFIED QUESTIONS

Written unclassified questions related to this solicitation shall be submitted electronically as follows, using the subject line “Subject: Hammerhead (N00024-20-R-6405) Bidders Question (Insert name of Offeror)”.

Unless otherwise specified, the Naval Sea Systems Command PCO and Contract Specialist are the sole points of contact for this acquisition.

Roy Williams Kevin Richter Contracting Officer Contracting Specialist roy.williams@navy.mil kevin.richter@navy.mil

(202) 781-3106 (202) 781-4211

CLASSIFIED QUESTIONS

If an Offeror needs to ask a question on classified material, it shall notify the Contract Specialist and the PCO. Do not send any classified questions via these email addresses. An appropriate channel for the Offeror to pose a classified question will then be established.

(b) Availability of Section J Attachments and Competition Bidders Library National Security Policy, as implemented by the Department of the Navy, does not support release of information related to this competition to non-U.S. contractors sources due to national security and national defense purposes.

Therefore, only US sources are authorized the full disclosure required to receive the information required to submit an offer and perform as a prime on the Hammerhead contract. Disclosure of any documents marked as NOFORN to foreign nationals (regardless of clearance, export licenses, or international agreement) or transmits said enclosures outside the geographical bound or custom territory of the United States of America is prohibited. Non-U.S.

subcontractors are not precluded from participating in providing components or subsystems, as long as they are approved to receive up to SECRET information, adhere to the U.S. Prime’s security agreements, and comply with all regulations and laws, including International Traffic and Arms Regulations (ITAR) export license requirements.

All Offerors must also comply with the Industrial Security Regulations (DOD 5220.22-4) and the National Industrial Security Program Operating Manual (NISPOM) (DOD 5220.22-M). The specified Section J Attachments and the Bidder’s Library may be obtained by submitting a completed TOU agreement and completed DD254 to the Contract Specialist. Once the security approval has been obtained the information will be emailed or mailed to the Offeror.

Potential Offerors shall submit the TOU agreement and DD254 no later than 10 days after solicitation release.

Section J attachments and the Competition Bidders Library containing relevant GFI attachments are available as a CD-ROM. Companies requesting a copy of the Section J attachments and the Competition Bidders Library set must provide the Contracting Officer a completed TOU agreement and DD254 indicating that the requesting company has a Defense Security Service (DSS) issued SECRET facility clearance, providing for SECRET personnel clearances and SECRET safeguarding capability. The Government will not provide sponsorship for new or upgraded personnel or facility clearances. Companies requesting a copy of the Section J attachments and Competition Bidders Library must provide their company’s valid FEDEX or UPS number to be charged for shipping. Upon receipt of the Terms of Use letter by the Contract Specialist, the J attachments and Competition Bidders Library will be made available in a secure manner to the Offeror so long as the Offeror has met the security requirements as described above. Offerors shall note that with the exception of GFI and certain J attachments, all other documents provided with the Bidder’s Library are for informational purposes during the solicitation phase and will not be included in the contract at award document.

(c) Proposal Delivery Information

(a) Due to ongoing restrictions resulting from the global COVID-19 pandemic, hand delivery of proposals is not possible at this time to the Washington Navy Yard. Offerors are instructed to submit their proposal electronically via the DoD SAFE application located at https://safe.apps.mil.

(b) Offerors wishing to submit a proposal in response to this solicitation shall notify the Contracting Officer and Contract Specialist noted as points of contact on this solicitation no later than three business days prior to the proposal deadline of this solicitation and no earlier than 14 calendar days prior to the proposal deadline. The Offeror shall provide their name and e-mail as contact information so the Government can generate a pick-up request from the DoD SAFE application to be sent to the Offeror, which is valid for 14 calendar days.

(c) Offerors shall address their package with the RFP number and Offeror’s company name. Offerors shall click the “Confirm Delivery” button within the DoD SAFE app in order to receive a confirmation of pick up by the Government. The DoD SAFE system records the time that files are submitted for transmission. Offerors are responsible for ensuring that they drop-off their proposal and generate a drop-off time prior to the proposal submission date and time. In the event of a dispute of proposal time submission, the pick-up e-mail with the system generated drop off time within the body of the e-mail shall serve as the official time that the proposal was submitted to the Government. Late proposal submissions will be handled in accordance with FAR 52.215-1.

1.1 Solicitation Response Requirements

The solicitation response shall be contained in four separate Volumes, with proposals delivered by the date of the closing of the solicitation which, unless an extension has been granted, is in accordance with Block 9 specified in Section A of this solicitation.

For Volumes 1-4, the number of copies required and the page limit are shown in the table below:

Volume Title Delivery Location

Original Page Limit

Solicitation, Offer, Award See Above 1 None

2 Technical Proposal 1 NAVSEA HQ 1 200

3 Past Performance NAVSEA HQ 1 10

4 Cost/Price Proposal NAVSEA HQ 1 None 1 The total page count identified excludes Appendix Documents specified below, the Table of Contents, Tables, and Figures, the Cross Reference Matrix, the Glossary of Terms Abbreviations and Acronyms, and Index of Terms.

Table of Contents, Tables, and Figures. The Table of Contents should include all numbered and titled paragraphs. A separate list of tables and figures used in the proposal volume should be appended at the end of the Table of Contents.

Glossary of Terms, Abbreviations, and Acronyms. The Glossary of Terms, Abbreviations, and Acronyms should include all abbreviations, acronyms, and terms which are either newly introduced, uncommon, or specialized.

Cross Reference Matrix. The Cross Reference Matrix shall clearly identify the location(s) in the Offerors proposal that address or respond to each numbered requirement in Section L, in accordance with Attachment L-2. A complete Cross Reference Matrix shall be provided in the front of volumes 2 and 3.

Index of Terms. The Index of Terms should include key words, phrases, or alphanumerical terms, and refer to where they appear in the text of the proposal volume.

Offeros who intend to submit a classified annex to their proposal shall contact the contracting officer to make arrangements. It is the Government’s intent to allow a classified annex to be submitted via electronic means if the Offeror has such capabilities (i.e. SIPRNET).

Offerors shall segregate any classified information contained in its proposal and present it in a separate binder/file in conjunction with Volume I. Information presented in the separate binder/file containing classified content shall clearly identify the section, and topic to which it applies for evaluation. The classified information shall be wrapped separately from the unclassified portions of the proposal, but the entire proposal package may be submitted together in accordance with NISPOM guidelines. Classified wrapping shall be prominently marked on all sides as to the classification level of the material contained therein. Pages submitted in a supplemental classified binder/file count towards the page limitation stated in Section L. In the event classified information is found within the unclassified sections of the proposal, that section will be destroyed.

The following procedures related to the submission of classified information shall be followed:

• Cross-referencing between the classified content and any relevant portions of Volume I is required.

• The classified content shall not exceed the classification GENSER Secret.

• The classified content shall be appropriately marked on the front, back, and spine as to the highest level of classified material contained therein.

• Page, paragraph, table, graphic, and figure markings shall be in accordance with Chapter 4 of the NISPOM.

• Strict adherence protocols of the DD 254 shall be in place to determine if any portion of the Offeror’s proposal is classified.

• Classified information shall be handled, packed, and shipped or delivered in accordance with and shall conform to the instructions contained in the DD 254 and the National Industrial Security Program Operating Manual

(NISPOM).

No pricing information is to be included in the technical Volume 2 (including appendix documents). No pricing information is to be included in Volume 3 past performance other than the contract values of previous contracts submitted for evaluation. “Pricing information,” is defined as facts, statistics, or data describing the consideration an Offeror will receive in exchange for furnishing the supplies and services described in this solicitation.

Electronic proposal submissions and supporting information shall be as indicated above. All view graphs shall be in Microsoft PowerPoint 2010 (or compatible) (limited to file extension .pptx). All spreadsheets or mathematical computations (cost data) shall be in Microsoft Excel 2010 (or compatible) (limited to file extension .xlsx) format and shall be working versions, including formulas and computations. Formulas shall be maintained in each Excel sheet to permit verification of calculations, and revision of output(s) through variation of inputs(s). Excel files shall not include macros or pivot tables. Submitted files shall not reference external data. Submission of locked spreadsheets is not acceptable. All spreadsheets should be “unlinked” to separate documents to allow for cost/price evaluation. All text shall be in Microsoft Word 2010 (or compatible) (limited to file extension .docx) or searchable Adobe Acrobat Portable Document Format (PDF) (limited to file extension .pdf). All schedules, including Integrated Master Schedule (IMS) (master program schedule that is aligned to the Government Integrated Master Plan (IMP)), shall be in Microsoft Project 2010 (or compatible) (limited to file extension .mppx).

The narrative material should consist of the following:

Proposal shall be typed in Times New Roman font with the type no smaller than 12 point on a standard page, defined as one side of a sheet 8 ½ inches by 11 inches.

Oversize pages are to be fold out format, with each fold out counted as a single page. Fold out pages may be used for diagrams, charts or graphic material only and may not exceed 11 inches by 17 inches. Fold out pages may only include narrative sufficient to describe the diagram, chart or graphic material. Of the 200 page count limitation, 25 pages may be fold out pages in Volume 2 Technical Proposal submission. There is no limit on the number of fold out pages in Volume 4 Cost/Price Proposal. Fold out pages may only include narrative sufficient to describe the diagram, chart, or graphic material and may only be single-sided.

Text shall be 1.5 spaced with minimum margins as follows:

Left Hand 1.0 inch Right Hand 1.0 inch Top 0.5 inch Bottom 0.5 inch

Text within tables, diagrams, pictorial charts, or graphic material may use Times New Roman font no smaller than 8 point

Every paragraph, figure and table shall be numbered.

Pages in excess of the page count limitation will be removed prior to the evaluation. If the proposal exceeds the page limit identified in the table above, the Government will remove all pages exceeding the specified page count from the back of the substantive proposal volume (not the appendices or any other content excluded from the Volume 2 – Technical Proposal page limitation) prior to the evaluation of the proposal and those removed pages will not be reviewed or evaluated.

Proposal material, with the exception of fold outs, shall be presented on double-sided pages only and in a single column on each page (refer to Section I, FAR 52.204-4). Each single-sided fold out counts as 1 page.

Pages are to be numbered sequentially and tabs are to be used for chapter breaks. It is not acceptable to restart numbers in subsequent chapters within the proposals.

A date shall be placed on each page of the proposal corresponding to the date of the initial proposal. Any pages that may be revised as a result of discussions (if required) shall contain revision numbers and dates.

The SDP shall be provided as an attachment to the technical proposal with no page limit.

The Offeror’s company name shall appear at the top of each page and all pages shall be numbered. The page count shall include all material with printed matter and figures. Pages excluded from the page count must contain only material pertinent to the page heading or be blank and marked "Intentionally Left Blank." Index pages and Tabs are required and shall be cross-referenced to the Table of Contents. Every page, except those marked as blank, must be numbered.

The cover page of each volume shall contain:

The document number and title (i.e., Volume 2 – Technical Proposal);

The solicitation number;

The full company name of the Offeror;

The address, point of contact and phone number for the Offeror;

The Offeror’s position regarding disclosure of proposed data in accordance with the provision entitled

“Restrictions on Disclosure and Use in Proposals”.

1.2 Discussions and Final Proposal Revision (FPR)

Pursuant to FAR 52.215-1, the Government intends to make a contract award based on initial proposals. Therefore the Offeror’s proposal shall contain the Offeror’s best terms from a price and technical standpoint. However, the Government reserves the right to conduct discussions if the PCO determines them to be necessary. If discussions are held, the Contracting Officer will make the determination as to which proposals are in the “Competitive Range.”

The competitive range shall be determined based on the results of the evaluation of initial proposals, considering all evaluation criteria, and shall include the most competitive proposals. The number of proposals within the competitive range may also be reduced if the Contracting Officer determines the number of most competitive proposals that might otherwise be included within the competitive range exceeds the number at which an efficient competition can be conducted. If discussions are held, Offerors selected to participate in the discussion shall be advised of weaknesses, deficiencies and risks in their proposals as well as adverse past performance ratings to which the Offeror has not had an opportunity to respond.

At the end of discussions (if conducted), the Government will request Final Proposal Revisions (FPRs) from all Offerors still within the competitive range. If it is determined that an Offeror is no longer in the competitive range, they will not be given an opportunity to submit an FPR.

(a) Proposal Content

The proposal shall consist of, and must include, the following to be eligible for award:

Volume 1 – Solicitation, Offer and Award Documents (SF 33 – RFP): See Section L, Section 2.0 for the content and format requirements Volume 2 – Technical Proposal: See Section L, Section 3.0 for the content and format requirements Volume 3 – Past Performance: See Section L, Section 4.0 for the content and format requirements Volume 4 – Cost/Price Proposal: See Section L, Section 5.0 for the content and format requirements

Information presented shall appear in the proposal in the same order it appears under the description of each proposal volume as delineated in Sections 2.0 through 5.0 below.

Proposals must present information in sufficient depth for the Government to make a comprehensive evaluation of the Offeror’s understanding of, and capability to, meet the requirements of this solicitation. Offerors bear the burden of submitting a clear and unambiguous proposal that is fit for evaluation. Offerors shall provide all information necessary to demonstrate their ability to meet the requirements of the solicitation. Discussion of each factor in the proposal shall be self-contained (i.e., data shall be organized to enable Government personnel to thoroughly evaluate the proposal against specific factors established in Section M.

2.0 Volume 1: Solicitation, Offer and Award Documents (SF 33 – RFP)

2.1 Solicitation Set

The following sections detail what Offerors shall address in Volume 1 of its proposal:

a) Cross Reference Matrix for Volumes 2 and 3.

b) Solicitation Sections A through K completed by the Offeror, as follows:

1. Standard Form 33 (SF 33), “Solicitation, Offer, and Award,” with blocks 12 through 18 completed/signed by the Offeror. Block 12 shall be made valid for 270 days from the date of the offer.

2. Section K, “Representations, Certifications, and Other Statements of Offerors,” completed by the Offeror. Identify if the information is in Online Representations and Certifications Application (ORCA), or provide if not already in the ORCA system. Refer to Section K for the complete list of items to provide. See Section 2.2 in Section L for the number of copies to submit.

3. Sections A through K: Offeror must fill in all areas of the RFP listed as “Offeror fill-ins” and provide any other information or data required by the solicitation.

c) Letter of Transmittal

The Letter of Transmittal shall identify all enclosures being transmitted and shall be used only to transmit the proposal and shall include no other information.

The Offeror shall include a statement signed by an authorized representative of the Offeror, on the Offeror’s letterhead, stating that the accompanying Proposal:

a. Is for all requirements as stated in the solicitation (including all attachments, appendices, and amendments thereto);

b. Is made without qualification or exception to any terms and conditions appearing in the solicitation;

c. Is valid for the period stated in Section L 2.1.b.1 ; and

In addition, the Letter of Transmittal must contain the following certification regarding the classified and other restricted information made available:

I, [insert signatory’s name, title, company], hereby certify that [company] will ensure that, if [company] is excluded from the competitive range or not selected for award of this contract, any and all copies, notes, or other materials produced using the classified or other restricted information provided in connection with solicitation N00024-20-R-6405 will be destroyed within 100 days from receipt of notice that [company] was excluded from the competitive range or not selected for award under this solicitation.

2.2 Equal Employment Opportunity

In order for the Contracting Officer to comply with EEO pre-award clearance procedures of FAR 22.805, the Offeror shall include in its proposal a list containing the following information:

Name, address, telephone number, estimated dollar value, and the applicable regional office of the Office of Federal Contract Compliance Programs of the prospective Contractor , and of any corporate affiliate at which work is to be performed.

Name, address, telephone number, estimated dollar value and the applicable regional office of the Office of Federal Contract Compliance Programs of each proposed first-tier subcontractor with a proposed subcontract estimated at $10M or more, including the dollar value of all options and the maximum quantity of supplies or services to be acquired.

2.3 Small Business Subcontracting Plan (to be incorporated as Section J, Attachment 7 at contract award)

See solicitation provision, SMALL BUSINESS SUBCONTRACTING PLAN (NAVSEA), included below. For all large businesses, the Small Business Subcontracting Plan called for in the provision shall be submitted with Volume I.

The Small Business Subcontracting Plan will be reviewed for compliance and adequacy for purposes of making a responsibility determination.

2.4 Publicizing Contract Actions

In accordance with NMCARS 5205, the Government intends to publicize contract award. Offerors shall complete Attachment L-3 in anticipation for possible contract award.

3.0 Volume 2: Technical Proposal

The Technical Proposal shall present the Offeror’s proposed system design, technical approach, program management approach, and other information in sufficient detail to demonstrate that the design will achieve the performance requirements of the Hammerhead Statement of Work (SOW) and the System Performance Specification (SPS) with low technical and schedule risk. The SOW and SPS are referenced attachments to the RFP.

The narrative shall demonstrate that the proposed technical solution is likely to meet the SOW and SPS. The use of graphics or models is encouraged where it can simplify or shorten the narrative. The Technical Proposal shall be specific and complete so as to clearly demonstrate to the Government that the Offeror has a thorough comprehension of and capabilities to perform all aspects of the solicitation requirements, as well as all other provisions of this solicitation. The technical proposal shall also provide evidence of past performance on efforts of similar size and complexity.

The Technical Proposal shall address the following Factors and Elements.

3.1 Factor 1.0 – Technical Approach

The Technical Proposal shall be specific and complete so as to clearly demonstrate to the Government that the Offeror has a thorough comprehension of and capabilities to perform all aspects of the solicitation requirements including system design, software development, system safety, product support, test and evaluation, and integration of cybersecurity to design and produce a product that meets its requirements within cost and schedule.

Element 1.1 System Requirements and Design

The Offeror shall detail how the proposed system will achieve the requirement set forth in the SPS and Interface Requirements Specifications (IRS).

The Offeror shall describe the proposed passive/active acoustic sensor system design including choice and physical layout of individual hydrophone receive elements, choice and physical layout of individual hydrophone transmit elements, signal conditioning and receive and transmit electronics, digitization rate and effective bit depth, and predicted system noise floor. The Offeror shall describe the proposed signal processing and target detecting architecture. Detailed algorithm descriptions and implementation methodologies for the processing system shall be included. The Offeror shall provide power consumption estimates for the overall sensor/signal processing/algorithm processing system and describe how the proposed energy storage system will supply this power while meeting size, weight, and mission duration requirements of the SPS. The Offeror shall describe the technical maturity of the proposed sensor system and provide a risk assessment of not meeting the performance requirements of the SPS.

The Offeror shall describe how the Hammerhead capsule and mooring system design will meet the capsule depth range and water depth range requirements in the SPS.

The Offeror shall show how the passive/active acoustic sensor performance will not degrade due to current induced capsule motion and tilt in water currents up those specified in the SPS.

Element 1.2 Systems Engineering

The Offeror shall describe its technical and technical management processes of systems engineering. Include the efforts for planning, controlling, and conducting a fully integrated engineering effort. The Offeror shall describe its strategy for reliability and maintainability, and hardware and software configuration management. Include any new technologies or developmental components intended for use.

The Offeror shall describe its use of Systems Engineering Decision Analysis tools (trade studies, analyses, modeling, and simulation). The Offeror shall describe trade studies, analyses, models, and simulations proposed to meet the requirements set forth in the SOW and SPS.

The Offeror shall describe the use of modeling, simulation, and analysis to support or supplement verification of requirements. Describe the level of verification and validation that would be required for modeling, simulation, and analysis efforts.

The Offeror shall describe Technical Performance Measures they will use to manage the proposed system design.

The Offeror shall identify and classify risk regarding systems engineering, design and Test & Evaluation. Identify the plans for reduction of risks rated as moderate or high. Identify contingency plans for high-risk areas.

The Offeror shall describe its strategy for performing model-based systems engineering (MBSE), to include a description of how MBSE efforts will be fully integrated with the Offeror’s approach to systems engineering processes and technical management.

The Offeror shall provide a description of software architecture, the allocation of functions and processes to specific computer resources, how the allocations support the system requirements, and how requirements are flowed down to software.

The Offeror shall describe the test and evaluation approach and test programs that will be implemented to verify compliance with the requirements in the SOW and SPS.

The Offeror shall describe the ability to design and proof any special test equipment required. The Offeror shall describe its approach to test equipment design and use.

The Offeror shall describe its understanding of the Cybersecurity requirements relevant to Hammerhead in the following specifications, standards, and Hammerhead program documentation including: DoDI 8500.01, DoDI 8510.01, and Hammerhead SOW.

The Offeror shall describe its capability, facilities, personnel security, and Cybersecurity workforce to complete integration, implementation and testing of the security controls, and the capability to implement a vulnerability management process to support the achievement of an authorization to operate for Hammerhead.

The Offeror shall describe its understanding of the program protection requirements relevant to Hammerhead in the following specifications, standards, and Hammerhead Program documentation including: DoDI 5200.39, DoDI 5000.02, DoDI 5200.44., and the Hammerhead program protection approach.

The Offeror shall describe its software development plan relevant to the Hammerhead program.

Element 1.3 Safety

The Offeror shall submit a draft version of their System Safety Program Plan (SSPP) in accordance with the content defined in the SOW. The SSPP may be formatted as desired by the Offeror but must contain the information described by the SSPP Data Item Description (DID) (DI-SAFT-81626) and MIL-STD-882E Task 102. The SSPP is not page limited but should contain only essential materials and should avoid unnecessary content.

The Offeror shall describe its understanding of the system safety requirements and software safety requirements as described in the SPS and IRS.

The Offeror shall discuss all pertinent details for ensuring that the proposed system design is safe for operation in the intended environment (including operation, transport, assembly, disassembly, maintenance, and storage), to include descriptions of safety analyses that need to be accomplished.

The Offeror shall describe its understanding of the Weapon System Explosive Safety Review Board (WSESRB) process per NAVSEAINST 8020.6E. The Offeror shall describe its understanding of required specifications and standards. The Offeror shall describe its strategy for how it will meet all WSESRB safety review board requirements in order to meet the program and test schedules.

The Offeror shall describe its understanding of the Software System Safety Technical Review Panel (SSSTRP) process per NAVSEAINST 8020.6E. The Offeror shall describe its understanding of required specifications and standards, including the Joint Software System Safety Engineering Handbook. The Offeror shall describe its strategy for how it will meet all SSSTRP safety review board requirements in order to meet the program and test schedules.

The Offeror shall describe test and evaluation activities to support system safety and software safety, including a description of certifications that must be completed.

The Offeror shall describe how Commercial-Off-the-Shelf (COTS) and Non-Developmental Item (NDI) parts will be certified for use in a weapon system.

Element 1.4 Production and Manufacturability

The Offeror shall describe its overall manufacturing approach including production processes, procedures, material handling and controls for the fabrication of the proposed design, and facilities required during the manufacturing process. At a minimum, the Offeror shall address the following critical areas of production:

Major subassemblies that will be procured from subcontractor/vendors Manufacturing processes proposed to minimize production costs of HH EE units;

The Offeror shall identify and classify risk dealing with the manufacturing approach. Identify the plans for reduction of risks rated as moderate or high. Identify contingency plans for high-risk areas.

The Offeror shall describe its strategy to prevent hardware obsolescence, including technology insertion.

The Offeror shall describe its approach to quality management during production, especially its policies, processes, and procedures for planning and production of the end item.

3.2 Factor 2.0 Data Rights

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 Hammerhead (HH) Encapsulated Effector (EE) System over their life cycle to include maintainability, reparability, and re-procurement. 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.

Do not include cost or price information in this volume. The price for this list shall be included under the price proposal, Volume IV. The Government desires at least a Government Purpose Rights (GPR) license, as defined at DFARS 252.227-7013 and - 7014, in all non-commercial technical data and computer software. The Offeror shall describe how it will support the Government’s desired level of license rights. The Offeror shall provide the documentation required in the following subparagraphs:

In the event an Offeror (including its sub-Offerors or suppliers, or potential sub-Offerors or suppliers, at any tier) proposes to deliver any commercial or noncommercial TD/CS/CSD with less than such license rights as desired by the Government (identified under Section M), the Government will evaluate the potentially adverse impact on the Government's ability to use, modify, release, or disclose such TD, CS, or CSD. Further, the Government will consider the adverse impact of less than the license rights desired by the Government in the best value determination. The data rights license offered shall be incorporated into the successful Offeror's contract upon award. The Offeror shall provide the following information as attachments to its offer:

The Offeror (including its sub-Offerors or suppliers, or potential sub-Offerors or suppliers, at any tier) shall list all noncommercial TD, CS, and CSD that it asserts will be delivered with other than an unlimited rights license.

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, the Offeror shall provide sufficient information to enable the Contracting Officer to evaluate and validate the listed assertions. Additionally, if there is no TD, CS, or CSD to be identified in the 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 7017 List shall be incorporated into the contract as Attachment 9A.

For those items in Attachment 9A where less than the Government’s desired level of license rights (identified under Section M) are being provided, the Government requests, but does not require, that the Offeror provide a Data Rights License Upgrade Option (CLIN 0020) and list any TD, CS, and/or CSD for which the Government may obtain the desired level of license rights. If the Offeror is proposing such a Data Rights License Upgrade Option under CLIN 0020 then the Offeror shall also provide a second 7017 Assertions List with the assertions applicable to the CLIN. If awarded a contract, this second 7017 list shall also be incorporated into the contract as Attachment 9B.

The Offeror (including its sub-Offerors or suppliers, or potential sub-Offerors or suppliers, at any tier) shall list all noncommercial TD, CS, and CSD that it intends to deliver with other than an unlimited rights license 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. If the Offeror does provide assertions, the Offeror shall provide sufficient information to enable the Contracting Officer to evaluate and validate the listed assertions. Additionally, if there is no TD, CS, or CSD to be identified in the 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 7028 List shall be incorporated into the contract as Attachment 10A.

For those items in Attachment 10A where less than the Government’s desired level of license rights (identified under Section M) are being provided, the Government requests, but does not require, that the Offeror provide a Data Rights License Upgrade Option (CLIN 0020) and list any TD, CS, and/or CSD for which the Government may obtain the desired level of license rights. If the Offeror is proposing such a Data Rights License Upgrade Option under CLIN 0020 then the Offeror shall also provide a second 7028 Assertions List with the assertions applicable to the CLIN. If awarded a contract, this second 7028 list shall also be incorporated into the contract as Attachment 10B.

If the Offeror (including its sub-Offerors or suppliers, or potential sub-Offerors or suppliers, at any tier) proposes to submit any noncommercial TD, CS, or CSD that should be delivered with a specifically negotiated license rights license (as discussed at DFARS 252.227-7013, 252.227-7014, or 252.227-7018), submit a statement entitled “Supplemental Information- Noncommercial Technical Data, Noncommercial Computer Software, Noncommercial Computer Software Documentation.” The statement shall provide a complete description of the Government’s ability to use, modify, release, perform, display, or disclose such TD, CS, or CSD. In addition, the Offeror shall provide the underlying executed licenses agreements for that TD, CS, or CSD. Any statement provided will be incorporated into the contract as Attachment 11A.

For those items in Attachment 11A where less than the Government’s desired level of license rights (identified under Section M) are being provided, the Government requests, but does not require, that the Offeror provide a Data Rights License Upgrade Option (CLIN 0020) and list any TD, CS, and/or CSD for which the Government may obtain the desired level of license rights. If the Offeror is proposing such a Data Rights License Upgrade Option under CLIN 0020 then the Offeror shall also provide a second statement with the assertions applicable to the CLIN.

If awarded a contract, this second statement shall also be incorporated into the contract as Attachment 11B.

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 an unlimited rights license. The list shall include: (1) identification of the TD, CS, or CSD;

(2) basis for asserting restrictions; (3) asserted rights category (e.g., a specifically negotiated license, or the license customarily offered to the public); and (4) name of the person asserting restrictions. For any item designated as 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 12.

Offerors shall provide a written summary and analysis of how the proposed commercial licenses in TD, CS, and/or CSD will affect the unimpeded, innovative, and cost effective operation, maintenance, repair, overhaul, modernization, and upgrade of Hammerhead (HH) Encapsulated Effector (EE) System throughout its lifecycle, and allow for the open and competitive procurement of Hammerhead (HH) Encapsulated Effector (EE) System requirements.

3.3 Factor 3.0 Program Management

Element 3.1 Schedule

The Offeror shall describe efforts to meet the required program milestones identified in the SOW in a master program schedule, which shall include interdependencies of events, resources, and critical path. The Offeror’s master program schedule shall include, at a minimum, the following events:

Initial Baseline Review (IBR) System Requirements Review (SRR) System Functional Review (SFR) Preliminary Design Review (PDR) Critical Design Review (CDR) Risk Reduction Testing Contractor Test (CT) Certification Test(s) Prototype Delivery System Verification Review (SVR)

The Offeror shall describe its project control methodologies and tools.

The Offeror shall identify and classify schedule risk. Identify the plans for reduction of risks rated as moderate or high and identify contingency plans for high-risk areas.

Element 3.2 Cost Accounting & Management

The Offeror shall provide a complete Contract Work Breakdown Structure (CWBS), expanded at least three levels.

The Offeror shall describe its processes and methodologies for controlling costs, including the use of an EVMS system. Include the information requested by DFARS Provision 252.234-7001 NOTICE OF EARNED VALUE

MANAGEMENT SYSTEM.

Element 3.3 Resources

The Offeror shall describe the proposed labor mix to support the tasking described in the SOW exclusive of any labor mix directed by the Government for specific CLINs.

The Offeror shall provide resumes for the following key personnel with no less than three years of experience:

Program Manager, systems engineer, cybersecurity, and safety. Please see table below with descriptions:

Position Minimum Position Experience Minimum

Supervisory Experience

Desired Education

Program Manager 5 Years in DoD Acquisition or Navy Management or Industry Management

2 Years BS/BA in related field or 10 of 15 years of in-depth related experience

Systems Engineer 3 years as Lead Systems Engineer

2 Years BS/BA in related field or 10 of 15 years of in-depth related experience

System Security Engineer 3 years in Security including Computer Security

N/A BS/BA in related field or 5 of 10 years of in-depth related experience

System Safety Engineer 3 years in System Safety N/A BS/BA in related field or 5 of 10 years of in-depth related experience

Resumes shall contain years of experience, current position/title/company, educational and professional development history, chronology of professional experience with emphasis on SOW-related experience, and current level of security clearance.

Resumes shall not exceed 3 pages in length. Offerors may supplement each 3-page resume with information that sets forth work experience and qualifications that are directly related to this requirement. It is the Offeror’s responsibility to provide information and evidence that clearly demonstrates the ability of proposed personnel to satisfactorily fulfill the contract requirements. The number of resumes specified is based on the assumption that each individual will be available on a full-time basis. If this is not the case, and a proposed Key Person will be available only on a part-time basis, additional resume(s) are required to equal the equivalent of a full-time person.

If the employee is not a current employee of the Offeror (or a proposed subcontractor), a copy of the accepted offer letter shall be provided. An additional copy of this letter shall be provided in the Cost Proposal which identifies a projected start date and the agreed to annual salary.

The Offeror shall describe any specialized facilities or capabilities, including subcontractor facilities and capabilities, relevant to performing the tasks described in the SOW.

Element 3.4 Subcontractor & Small Business Management The Offeror shall describe its strategy for use of subcontractors, including the use of small businesses, to support the development, integration, test, and production of the proposed system.

The Offeror shall describe its approach to subcontractor management including quality control and interface management.

Element 3.5 Risk Management The Offeror shall describe its approach to a Risk Management program which identifies, assesses and mitigates risk.

4.0 Volume 3, Factor 4.0 – Past Performance

Element 4.1 Past Performance

The Offeror shall provide Department of the Navy’s Contractor Performance Assessment Reporting System (CPARS)…