Solicitation - N6660426R0200.pdf

SECTION

15A. NAME AND

ADDRESS

OF OFFEROR

SOLICITATION, OFFER, AND AWARD 1. This Contract is a Rated Order under the Defense Priorities and Allocations System (DPAS) - Code of Federal Regulations - at 15 CFR 700.

RATING PAGE OF PAGES

2. CONTRACT NUMBER 3. SOLICITATION NUMBER 4. TYPE OF SOLICITATION 5. DATE ISSUED 6. REQUISITION/PURCHASE NUMBER

CODE7. ISSUED BY 8. ADDRESS OFFER TO (If other than item 7)

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

9. Sealed offers in original and copies for furnishings the supplies or services in the Schedule will be received at the place specified in item 8, or if hand carried, in the depository located in until local time

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision Number 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. FOR

INFORMATION

CALL:

A. NAME B. TELEPHONE (NO COLLECT CALLS)

AREA CODE NUMBER EXTENSION

C. EMAIL ADDRESS

11. TABLE OF CONTENTS

(X) DESCRIPTION PAGE(S) (X) SECTION PAGE(S)DESCRIPTION

A B C D E F G H

I

J

K

L

M EVALUATION FACTORS FOR AWARD

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

REPRESENTATIONS, CERTIFICATIONS AND OTHER

STATEMENTS OF OFFERORS

PART IV - REPRESENTATIONS AND INSTRUCTIONS

LIST OF ATTACHMENTS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

CONTRACT CLAUSESSOLICITATION/CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/COSTS

DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

PACKAGING AND MARKING

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

CONTRACT ADMINISTRATION DATA

SPECIAL CONTRACT REQUIREMENTS

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

OFFER (Must be fully completed by offeror)

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause Number 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments to the SOLICITATION for offerors and related documents numbered and dated):

10 CALENDAR DAYS (%) 20 CALENDAR DAYS (%) 30 CALENDAR DAYS (%) CALENDAR DAYS (%)

DATEAMENDMENT NUMBERAMENDMENT NUMBER DATE

CODE FACILITY 16. NAME AND THE TITLE OF PERSON AUTHORIZED TO SIGN OFFER

(Type or print)

15B. TELEPHONE NUMBER

AREA CODE NUMBER EXTENSION

15C. CHECK IF REMITTANCE ADDRESS IS

DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

17. SIGNATURE 18. OFFER DATE

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL OPEN COMPETITION UNDER THE

UNITED STATES CODE AT:

10 U.S.C. 3204(a) ( )41 U.S.C. 3304(a)

24. ADMINISTERED BY (If other than Item 7)

26. NAME OF CONTRACTING OFFICER (Type or print)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

AUTHORIZED FOR LOCAL REPRODUCTION

Previous edition is unusable

23. SUBMIT INVOICES TO ADDRESS SHOWN IN

(4 copies unless otherwise specified)

25. PAYMENT WILL BE MADE BY

27. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

28. AWARD DATE

CODE

ITEM

STANDARD FORM 33 (REV. 12/2022)

Prescribed by GSA - FAR (48 CFR) 53.214 (c)

SEALED BID (IFB) INVITATION FOR BID

NEGOTIATED (RFP) REQUEST FOR

PROPOSAL

(Hour) (Date)

PART I - THE SCHEDULE PART II - CONTRACT CLAUSES

Section A - Solicitation/Contract Form

MK48 Heavyweight Torpedo Source and Sensor Kits

NUWCDIVNPT POC: Margaret Echard, margaret.j.echard.civ@us.navy.mil

Surveillance Criticality Designator (SCD): A

Companies requesting access to Applicable Documents, which include Controlled Unclassified Information (CUI) Specific Controlled Information, must be registered with the DoD Joint Certification Program (JCP). For further information on registration, visit the JCP website: https://www.dla.mil/logistics-operations/services/joint-certification-program/

Two-Step Process:

STEP ONE: Submit Request to Government Point of Contact (POC)

To request applicable documents, the Offeror must contact the Government POC via email and provide the following documentation.

POC: Margaret Echard Email: margaret.j.echard.civ@us.navy.mil.

1. Active CAGE Code: Offeror’s currently active CAGE code.

2. Certified DD Form 2345 (Military Critical Technical Data Agreement): A copy of the firm’s current DD Form 2345.

3. CMMC Unique Identifiers: The CMMC UIDs from the Supplier Performance Risk System (SPRS) for each contractor information system intended to process, store, or transmit CUI during performance of the resulting contract.

NOTE: The name and e-mail address of the individual requesting documents must match the Data Custodian listed on the firm’s certified DD Form 2345. Additionally, the CAGE code identified on the DD Form 2345 must match the contractor’s currently active CAGE code in the System for Award Management (SAM). The Government POC will verify JCP certification and CMMC status in SPRS before authorizing the release of documents.

STEP TWO: Document Delivery via DoD SAFE

Upon successful verification, the POC will utilize the DoD Secure Access File Exchange (SAFE) (https://safe.

apps.mil) “Drop Off” feature to transmit the documents.

Recipient: The certified JCP Data Custodian will receive an automated email containing a link and a unique passcode.

Expiration: Access to the documents will expire seven (7) days from the date the link and passcode are generated.

N6660426R0200

Section B - Supplies or Services & Prices or Costs

Additional Information/Notes

Item Supplies/Service Quantity Unit Unit Price Amount

Firm-Fixed-Price (FFP) production and testing of Torpedo Source and Sensor Kits. Work shall be performed In Accordance With (IAW) Statement of Work (SOW) Sections 4.1-4.5, and the approved Technical Data Package

(TDP).

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

Pricing Arrangement: Firm Fixed Price

200 Kit

Option Line Item

FFP production and testing of Torpedo Source and Sensor Kits. Work shall be performed IAW SOW Sections 4.1-4.5, and the approved TDP.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

Pricing Arrangement: Firm Fixed Price

200 Kit

Option Line Item

FFP production and testing of Torpedo Source and Sensor Kits. Work shall be performed IAW SOW Sections 4.1-4.5, and the approved TDP.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

Pricing Arrangement: Firm Fixed Price

200 Kit

Option Line Item

FFP production and testing of Torpedo Source and Sensor Kits. Work shall be performed IAW SOW Sections 4.1-4.5, and the approved TDP.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

Pricing Arrangement: Firm Fixed Price

200 Kit

Option Line Item

FFP production and testing of Torpedo Source and Sensor Kits. Work shall be performed IAW SOW Sections 4.1-4.5, and the approved TDP.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

Pricing Arrangement: Firm Fixed Price

200 Kit

Option Line Item

FFP production and testing of Torpedo Source and Sensor Kits. Work shall be performed IAW SOW Sections 4.1-4.5, and the approved TDP.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

Pricing Arrangement: Firm Fixed Price

200 Kit

Cost-Plus-Fixed-Fee (CPFF) Level of Effort for engineering and technical services. Work shall be performed IAW SOW Section 4.6.

Pricing Arrangement: Cost Plus Fixed Fee

2,000 Hours

Option Line Item

CPFF Level of Effort for engineering and technical services. Work shall be performed IAW SOW Section 4.6.

Pricing Arrangement: Cost Plus Fixed Fee

2,000 Hours

Option Line Item

CPFF Level of Effort for engineering and technical services. Work shall be performed IAW SOW Section 4.6.

Pricing Arrangement: Cost Plus Fixed Fee

2,000 Hours

Option Line Item

CPFF Level of Effort for engineering and technical services. Work shall be performed IAW SOW Section 4.6.

Pricing Arrangement: Cost Plus Fixed Fee

2,000 Hours

Option Line Item

CPFF Level of Effort for engineering and technical services. Work shall be performed IAW SOW Section 4.6.

Pricing Arrangement: Firm Fixed Price

2,000 Hours

CPFF Level of Effort for engineering and technical services. Work shall be performed IAW SOW Section 4.6.

Pricing Arrangement: Cost Plus Fixed Fee

2,000 Hours

Not Separately Priced (NSP). Delivery of all data requirements IAW Exhibit A, DD Form 1423, and the SOW. Costs for data generation are included in the price /cost of CLINs 0001 through 0012.

Pricing Arrangement: Cost Plus Fixed Fee

1 Lot

Additional Regulation or Supplemental Clauses Incorporated by Full Text

B-216-H006 FEE TABLE (NAVSEA) (MAR2019) (Mar 2019)

CPFF Labor CLIN Fee Rate Per Hour*

*The offeror shall divide the proposed fee for each CLIN by the quantity of labor hours indicated to complete the table. Fee is calculated based on cost less FCCOM; if FCCOM is proposed, necessary columns may be added.

In the event of any inconsistency between the above table and the CLIN pricing, the CLIN pricing shall take precedence.

(End of Text)

B-232-H006 LIMITATION OF COST OR LIMITATION OF FUNDS CLARIFICATION (Oct 2018)

The clause entitled "Limitation of Cost" (FAR 52.232-20) or "Limitation of Funds" (FAR 52.232-22), as appropriate, shall apply separately and independently to each separately identified estimated cost.

(End of Text)

B-232-H005 PAYMENTS OF FEE(S) (LEVEL OF EFFORT)--ALTERNATE I (Oct 2018)

(a) For purposes of this contract, "fee" means "target fee" in cost-plus-incentive-fee type contracts, "base fee" in cost-plus-award-fee type contracts, or "fixed fee" in cost-plus-fixed-fee type contracts.

(b) The Government shall make payments to the Contractor, subject to and per the clause in this contract entitled "Fixed Fee" (FAR 52.216-8) or "Incentive Fee", (FAR 52.216-10), as applicable. Such payments shall be submitted by and payable to the Contractor pursuant to the clause of this contract entitled "Allowable Cost and Payment" (FAR 52.216-7), subject to the withholding terms and conditions of the "Fixed Fee" or "Incentive

Fee" clause, as applicable. Fee paid per hour shall be based on total fee dollars divided by total hours to be provided. Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract.

(End of Text)

Section C - Description/Specifications/Statement of Work

STATEMENT OF WORK (SOW)

Code 85 MK48 Heavyweight Torpedo Source and Sensor Kits

1.0 Background

The MK48 Heavyweight Torpedo (HWT) is a U.S. Navy submarine launched anti-submarine and anti-surface warfare weapon. The MK48 HWT is a high performance, self-propelled underwater vehicle that contains complex electronic and mechanical subassembly systems for providing propulsion, steering, navigation, and target detection. The system technologies include acoustic SONAR, guidance and control electronics, electrical power, hydraulic systems, mechanical pumps, and propulsion.

1.1 Places of Performance

The primary place of performance is the contractor's site.

1.2 Authorized Users

NUWCDIVNPT Code 85

1.3 Sponsors

NAVSEA PMS 404

1.4 Types of Funding

Weapons Procurement, Navy (WPN)

Special Deposits (SPDP)

2.0 Scope

The contractor shall produce, test, and deliver MK48 HWT Source and Sensor Kits. Each Kit consists of four

(4) Sources (P/N:6146769) and two (2) Sensors (P/N: 6146770). The scope encompasses hardware production and Factory Acceptance Testing (FAT), Quality Management System (QMS) maintenance, configuration management, failure analysis and reporting, and Integrated Product Team (IPT) facilitation.

Additionally, upon issuance of a Government Technical Instruction (TI), the contractor shall provide engineering and technical services for production issue resolution and obsolescence management, technical assistance during Government-led test events, and the development, evaluation, and proposal of design improvements.

2.1 Program or Systems Supported

MK 48 HWT

3.0 Applicable Documents

The contractor shall perform the tasking required in Section 4.0 in accordance with the below Applicable Documents (ADs).

Program Unique Documents

Number Title Date / Revision Applicable SOW Section

3.1 Configuration Management Plan for Undersea Weapons Program (PMS404), PEO SUB S0199- 133-A-O-C

August 2010, Rev D

4.3

3.2 Source and Sensor Technical Data Package N/A 4.1, 4.2.1

Other Government Documents

Number Title Date / Revision

Applicable SOW Section

3.3 Failure, Reporting, Analysis and Corrective Action Taken (MIL-HDBK-2155) (See https://quicksearch.dla.mil/qsSearch.aspx)

11 December

4.4

3.4 ANSI/ESD S20.20-2021: Protection of Electrical and Electronic Parts

14 December

4.2.2

Non-Government Documents

Number Title Description Date / Revision

Applicable SOW Section

3.5

ANSI/ISO/ASQ

Q9001

Quality Management Systems - Requirements Standard October 2015 4.2

3.6

ANSI/EIA-649-

C

National Consensus Standard for Configuration Management February 2019 4.3

3.7

IPC/WHMA-A-

Requirements and Acceptance for Cable and Wire Harness Assemblies (See https://www.ipc.org)

October 2025, Rev F

4.2.1

3.8 IPC-A-610

The Standard for Acceptability of Electronics Assemblies Endorsement Program (See https://www.ipc.org/)

March 2024, Rev J

4.2.1

3.9 IPC-TM-650 IPC Test Methods Manual 1 January 2015 4.2.1

3.10 IPC-QL-653

Qualification of Facilities that Inspect/Test Printed Boards, Components and Materials (See https://www.ipc.org/)

1 November

4.2.1

3.11 IPC-MI-660

Guidelines for Incoming Inspection of Printed Board Materials (See https://www.ipc.

org/)

1 February

4.2.1

3.12 NIST National Institute of Standards and Technology (NIST) 4.2.3

N6660426R0200 https://quicksearch.dla.mil/qsSearch.aspx https://quicksearch.dla.mil/qsSearch.aspx https://www.ipc.org https://www.ipc.org https://www.ipc.org/ https://www.ipc.org/ https://www.ipc.org/ https://www.ipc.org/

4.0 Technical Requirements

4.1 Production Hardware Fabrication, Testing and Delivery

The contractor shall build and test production Source and Sensor Kits in accordance with the Technical Data Package (TDP) (AD 3.2) and Government-approved Factory Acceptance Procedures defined below.

4.1.1 FAT Procedures (Planning)

The contractor shall revise the existing Factory Acceptance Test (FAT) Procedures and deliver for Government approval. The FAT Procedures shall detail the specific steps required to execute and verify the Quality Conformance Tests identified in the TDP assembly specifications (AD 3.2). The FAT Procedures shall include a comprehensive list of all test equipment and test fixtures required for FAT execution.

4.1.2 FAT Execution and Data Logging (Testing)

Upon Government approval of the FAT Procedures, the contractor shall perform FAT on all fabricated hardware to verify that all individual components of the Source and Sensor Kits meet their respective requirements as specified in the TDP (AD 3.2).

The contractor shall electronically log and store all required test data collected during FAT in accordance with the approved procedures. The contractor shall use non-proprietary formats consistent with optimal commercial practices.

4.1.3 Hardware Delivery (Inspection and Acceptance)

The contractor shall deliver the Source and Sensor Kits following the successful completion of the FAT Procedures and applicable Defense Contract Management Agency (DCMA) inspection.

Deliverable: CDRL A007 Test Procedure - Factory Acceptance Test Procedure

4.2 Quality

The contractor shall implement and maintain a Quality Management System (QMS) in accordance with AD 3.5.

The contractor shall respond to and close any Corrective Action Requests (CARs) issued by the Government -including those issued by the Defense Contract Management Agency (DCMA) or any other Government agency designated by the Procuring Contracting Officer (PCO) - within seventy-five (75) calendar days of CAR notification.

4.2.1 Design, Fabrication and Testing Quality Standards

The contractor shall implement the Association Connecting Electronics Industries (IPC) Class 3 Industry Standard quality requirements, as specified in ADs 3.7 through 3.11, when designing, fabricating and testing the Source and Sensor Kits.

4.2.2 Electrostatic Discharge Control Program

The contractor shall utilize an Electrostatic Discharge (ESD) control program in accordance with AD 3.4.

4.2.3 Calibration

The contractor shall utilize a calibration program in accordance with AD 3.12. The contractor shall ensure that all equipment requiring calibration is maintained in a calibrated state prior to and during use.

4.3 Configuration Management

The contractor shall revise and update the Configuration Management Plan in accordance with ADs 3.1 and 3.6 and submit for Government review and approval. The contractor shall use the approved Configuration Management Plan to track changes and repairs for Sources and Sensors and GFE.

The contractor shall document any changes to the Sources and Sensors hardware or Technical Data Package (TDP) - arising from obsolescence or technical issues and required to maintain production and delivery - as Engineering Change Proposals (ECP), Notices of Revisions (NOR), or Requests for Variance (RFV), as applicable. The contractor shall provide supporting rationale and technical justification for all proposed changes.

The contractor shall obtain Government approval prior to implementing ECPs, NORs and RFVs.

The contractor shall utilize the Government's web-based CMPro system to submit all ECPs, NORs, and RFVs, along with all required supporting documentation. All documents uploaded to CMPro shall be in Microsoft Office or searchable Adobe PDF formats. Additionally, the contractor shall provide a Lead Engineering Summary for each ECP and RFV submission.

Deliverables:

CDRL A002 Configuration Management Plan

CDRL A003 Engineering Change Proposals

CDRL A004 Notice of Revisions

CDRL A005 Request for Variance

4.3.1 "As-Built" Configuration List

The contractor shall develop and submit an As-Built Configuration List. In addition to the baseline Data Item Description (DID) requirements, the list shall explicitly detail configuration information, including implemented ECPs, NORs, and RFVs.

Deliverable: CDRL A006 As Built Configuration List

4.4 Failure Analysis and Reporting

The contractor shall perform failure analysis and reporting on all non-conformances that occur during the execution of the approved Factory Acceptance Test (FAT) Procedures.

The contractor shall establish, document and implement a failure analysis program in accordance with the guidelines established in AD 3.3.

The contractor shall perform root cause analysis on each non-conformance to the lowest level to determine Root Cause Corrective Action (RCCA). The contractor shall validate any proposed retroactive corrective action and verify the effectiveness of corrective and preventative actions. If the contractor is unable to determine a single root cause, the contractor shall submit a full fault tree showing the evidence developed during the root cause analysis as part of the Failure Analysis and Corrective Action Report.

Deliverable: CDRL A008 Failure Analysis and Corrective Action Report

4.4.1 Systemic Non-Conformances

The contractor shall develop, document and submit a Corrective Action Plan for systemic non-conformances.

The Government will provide the specific definition of and threshold for a systemic non-conformance, which is defined as three or more units displaying fundamentally identical non-conformance symptoms.

The contractor shall isolate the failure cause to the lowest possible level. In cases where it is not practical to determine the root cause, the contractor shall provide:

(1) A fault tree type diagram showing all the evidence accumulated during the investigation;

(2) A description of how the evidence supports or refutes any plausible failure scenarios; and

(3) The rationale for terminating the investigation above the root cause level.

Deliverable: CDRL A009 Corrective Action Plan

4.5 Integrated Product Team Meetings

The contractor shall host and facilitate remote biweekly Integrated Product Team (IPT) meetings, including leadership and working groups, to achieve program goals. The initial IPT meeting shall occur no later than one

(1) month after contract award. The contractor shall ensure appropriate personnel participate in all IPT meetings to review and discuss ongoing progress, schedule status, the condition of Government Furnished Equipment (GFE), and to resolve program issues, including those relating to the Fault Isolation Team (FIT).

The contractor shall record and submit Meeting Minutes for each IPT meeting. The minutes shall include a summary of discussions, a list of participants, and a log of all generated action items.

Deliverable: CDRL A001 - Record of Meetings/Minutes - Meeting/Minutes/Logs

4.6 Engineering and Technical Services

Upon receiving Technical Instructions (TI) issued by the Government, the contractor shall provide engineering and technical services in accordance with Section H NAVSEA text H-216-H002 'LEVEL OF EFFORT-- ALTERNATE I.' These services shall not be utilized to resolve manufacturing defects, rework, or delivered non-conformances resulting from the contractor's failure to adhere to the TDP or its Quality Management System

(QMS).

4.6.1 Production Issue Resolution and Obsolescence Management

The contractor shall provide engineering and technical services to resolve externally driven issues that affect production (e.g., component obsolescence or TDP part shortages). This may include the fabrication of modified Source and Sensor Kit test articles and prototypes required to validate that the proposed design changes continue to meet all TDP performance requirements.

4.6.2 Government-led Qualification and Integration Testing

The contractor shall provide engineering and technical services, including on-site technical assistance, for Government-led integration testing of baseline Source and Sensor Kits in the torpedo system, and for Government-led qualification testing of modified Source and Sensor Kits at both the component and system level. The contractor shall provide technical troubleshooting, data collection, and perform analysis of the Kits during these events. The specific test events, locations, and required levels of effort will be defined in individual TIs.

4.6.3 Design Improvements

The contractor shall provide engineering and technical services to develop and evaluate proposed design improvements. This may include fabrication of prototype Source and Sensor Kits. Upon Government approval via the Engineering Change Proposal (ECP) process, the contractor shall implement design improvements into the production baseline.

5.0 Contract Status Report

The contractor shall prepare a Contractor's Status Report that indicates the progress of work, status of the program(s), and existing or potential problem areas for all assigned tasks.

The contractor shall include the following in the Contractor's Status Report:

- Status of manufacturing and testing on deliverable hardware.

- Subcontract and supplier performance against the established schedule baseline.

- Updates on obsolescence issues and failure analysis.

- Financial and Level of Effort (LOE) status for all CPFF engineering services, including hours and costs expended per active Technical Instruction (TI), cumulative hours and costs incurred to date, and the remaining balance of hours and funding.

Deliverable: CDRL A010 Contractor's Status Report

6.0 Government Furnished Information

RESERVED

7.0 Government Furnished Property

The Government may provide Government Furnished Property (GFP). The contractor shall adhere to DFARS Clause 252.245-7005 for the management and reporting of Government Property and shall use the GFP Module of the Procurement Integrated Enterprise Environment (PIEE) as specified in the clause. In addition, the contractor shall prepare and submit a Government Property (GP) Inventory Report to capture GFP status in accordance with CDRL A011.

Deliverable: CDRL A011 Government Property Inventory Report

8.0 Quality Surveillance and Performance Standards

The Government will conduct quality surveillance via various methods including formal and informal meetings, review of technical reports, review of monthly progress reports, and review of deliverables. Contractor performance will be evaluated in the areas of technical quality, schedule/timeliness, management, small business utilization and regulatory compliance as follows:

- Technical Quality: The Government will evaluate technical quality using approval of the CDRLs, as well as delivery and acceptance of end items associated with the tasking specified in Section 4.0 above;

- Schedule/Timeliness: The Government will evaluate the contractor's ability to meet delivery schedules;

- Management: The Government will evaluate the contractor's ability to integrate and coordinate all activities needed to execute the contract;

- Small Business Utilization: The Government will evaluate the contractor's compliance and progress in meeting the goals outlined in their approved Small Business Subcontracting Plan. The evaluation will be based on the review of periodic subcontracting reports submitted by the prime contractor.

- Regulatory Compliance: The Government will evaluate the contractor's compliance with the terms and conditions of the contract relating to applicable regulations and codes.

9.0 Information and Communication Technology (ICT) Accessibility Requirements

The Government has determined that this procurement is exempt from Accessibility Standards (36 C.F.R. Part 1194, Appendix A).

10.0 Security Compliance

10.1 Program Protection

SECURITY: All contractor personnel shall adhere to the Security provisions of 32 CFR Part 117 - National Industrial Security Program Operating Manual (NISPOM) and the security requirements of the attached DD254.

While performing work at a Government Facility, contractor personnel shall comply with the security regulations of the host facility. Applicable FAR, DFARS, NMCARS clauses, and NAVSEA text shall be adhered to in the performance of this contract. Security incidents shall be promptly reported through the companies Facility Security Officer (FSO), to the Contracting Officer's Representative (COR), Technical Point of Contact (TPOC), and the Cognizant Security Office to NUWCDIVNPT Security.

Controlled Unclassified Information (CUI) including Legacy FOUO and Covered Defense Information (meeting the definition of 48 CFR 252.204-7012(a)) generated and/or provided under this contract shall be marked and safeguarded as specified in DoD Instruction 5200.48, CUI available at:

https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF. Any product containing Covered Defense Information shall be assigned a distribution statement (distribution statements B through F) in accordance with DoDI 5230.24 (Distribution Statements on Technical Documents); and DoDI 5230.24, Enclosure 3 Procedures, available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi /523024p.pdf

INFORMATION SECURITY: If the work is performed at the contractor's facility, the contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI in accordance with National Industrial Security Program Operating Manual (NISPOM) codifying 32 CFR Part 117, NISPOM Rule, and SECNAV M-5510.36B. If the work is performed at the Government's facility, the contractor shall comply with facility policy.

CUI INCIDENT REPORTING AND RESPONSE: The contractor shall promptly report any unauthorized, inadvertent, or illegal release or disclosure of CUI to the Contracting Officer's Representative / Technical Point of Contact (TPOC), Procuring Contracting Officer, and the Security Office. Contractor personnel shall coordinate this effort through the relevant industry site FSO.

PUBLIC RELEASE: Any controlled unclassified information pertaining to this contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release through the appropriate U.S. Government Office.

10.2 Operations Security (OPSEC)

OPSEC is a process that identifies critical information to determine if friendly actions can be observed by adversary intelligence systems, determines if information obtained by adversaries could be interpreted to be useful to them, and then executes selected measures that eliminate or reduce adversary exploitation of friendly critical information.

The contractor shall develop and implement, and update and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the contractor and any subcontractor during performance of the contract. The contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. The contractor developed OPSEC program may include Information Assurance and Communications Security (COMSEC). The OPSEC program shall be in accordance with National Security Presidential Memorandum (NSPM) 28, and at a minimum shall include:

1) Assignment of responsibility for OPSEC direction and implementation.

2) Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

3) Establishment of OPSEC education and awareness training.

4) Provisions for management, annual review, and evaluation of OPSEC programs.

5) Flow down of OPSEC requirements to subcontractors when applicable.

While performing aboard Government sites, the contractor shall: comply with all OPSEC instructions and policies; include OPSEC as part of its ongoing security awareness program and take all required Agency training; Be responsive to the Supporting OPSEC Manager on a non-interference basis; and Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the Requiring Organization and contractor in support of the mission.

10.3 Electronic Spillage

Electronic Spillage (ES) is defined as a situation where information of higher classification than a system is authorized to process is introduced into that system, intentionally or otherwise. If a contractor is determined to be responsible for an ES, all direct and indirect costs incurred by the Government for ES remediation will be charged to the contractor.

Requirements Production, testing and delivery of MK48 Heavyweight Torpedo Source and Sensor Kits and associated engineering and technical services.

Additional Regulation or Supplemental Clauses Incorporated by Full Text

C-202-H001 ADDITIONAL DEFINITIONS--BASIC (Oct 2018)

(a) Department means the Department of the Navy.

(b) Commander, Naval Sea Systems Command means the Commander of the Naval Sea Systems Command of the Department of the Navy or his duly appointed successor.

(c) References to The Federal Acquisition Regulation (FAR) All references to the FAR in this contract shall be deemed to also reference the appropriate sections of the Defense FAR Supplement (DFARS), unless clearly indicated otherwise.

(d) National Stock Numbers Whenever the term Federal Item Identification Number and its acronym FIIN or the term Federal Stock Number and its acronym FSN appear in the contract, order or their cited specifications and standards, the terms and acronyms shall be interpreted as National Item Identification Number (NIIN) and National Stock Number (NSN) respectively which shall be defined as follows:

(1) . The number assigned to each approved Item Identification under the National Item Identification Number (NIIN) Federal Cataloging Program. It consists of nine numeric characters, the first two of which are the National Codification Bureau (NCB) Code. The remaining positions consist of a seven digit nonsignificant number.

(2) . The National Stock Number (NSN) for an item of supply consists of the applicable National Stock Number (NSN) four-position Federal Supply Class (FSC) plus the applicable nine-position NIIN assigned to the item of supply.

(End of Text)

C-204-H001 USE OF NAVY SUPPORT CONTRACTORS FOR OFFICIAL CONTRACT FILES (Oct 2018)

(a) NAVSEA may use a file room management support contractor, hereinafter referred to as "the support contractor", to manage its file room, in which all official contract files, including the official file supporting this procurement, are retained. These official files may contain information that is considered a trade secret, proprietary, business sensitive or otherwise protected pursuant to law or regulation, hereinafter referred to as "protected information". File room management services consist of any of the following: secretarial or clerical support; data entry; document reproduction, scanning, imaging, or destruction; operation, management, or maintenance of paper-based or electronic mail rooms, file rooms, or libraries; and supervision in connection with functions listed herein.

(b) The cognizant Contracting Officer will ensure that any NAVSEA contract under which these file room management services are acquired will contain a requirement that:

(1) The support contractor not disclose any information;

(2) Individual employees are to be instructed by the support contractor regarding the sensitivity of the official contract files;

(3) The support contractor performing these services be barred from providing any other supplies and/or services, or competing to do so, to NAVSEA for the period of performance of its contract and for an additional three years thereafter unless otherwise provided by law or regulation; and,

(4) In addition to any other rights the contractor may have, it is a third party beneficiary who has the right of direct action against the support contractor, or any person to whom the support contractor has released or disclosed protected information, for the unauthorized duplication, release, or disclosure of such protected information.

(c) Execution of this contract by the contractor is considered consent to NAVSEA's permitting access to any information, irrespective of restrictive markings or the nature of the information submitted, by its file room management support contractor for the limited purpose of executing its file room support contract responsibilities.

(d) NAVSEA may, without further notice, enter into contracts with other contractors for these services. Contractors should enter into separate non-disclosure agreements with the file room contractor. Contact the Procuring Contracting Officer for contractor specifics. However, any such agreement will not be considered a prerequisite before information submitted is stored in the file room or otherwise encumber the government.

(End of Text)

C-204-H002 IMPLEMENTATION OF ENHANCED SECURITY CONTROLS ON SELECT

DEFENSE INDUSTRIAL BASE PARTNER NETWORKS

(Sep 2024)

1. System Security Plan and Plans of Action and Milestones (SSP/POAM) Reviews

a) Within thirty (30) days of contract award, the Contractor shall make its System Security Plan(s) (SSP(s)) for its covered contractor information system(s) available for review by the Government at the contractor's facility.

The SSP(s) shall implement the security requirements in Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012, which is included in this contract. The Contractor shall fully cooperate in the Government's review of the SSPs at the Contractor's facility.

b) If the Government determines that the SSP(s) does not adequately implement the requirements of DFARS clause 252.204-7012 then the Government shall notify the Contractor of each identified deficiency. The Contractor shall correct any identified deficiencies within thirty (30) days of notification by the Government.

The contracting officer may provide for a correction period longer than thirty (30) days and, in such a case, may require the Contractor to submit a plan of action and milestones (POAM) for the correction of the identified deficiencies. The Contractor shall immediately notify the contracting officer of any failure or anticipated failure to meet a milestone in such a POAM.

c) Upon the conclusion of the correction period, the Government may conduct a follow-on review of the SSP(s) at the Contractor's facilities. The Government may continue to conduct follow-on reviews until the Government determines that the Contractor has corrected all identified deficiencies in the SSP(s).

d) The Government may, in its sole discretion, conduct subsequent reviews at the Contractor's site to verify the information in the SSP(s). The Government will conduct such reviews at least every three (3) years (measured from the date of contract award) and may conduct such reviews at any time upon thirty (30) days' notice to the Contractor.

2. Compliance to NIST 800-171

a) The Contractor shall fully implement the CUI Security Requirements (Requirements) and associated Relevant Security Controls (Controls) in NIST Special Publication 800-171 (Rev. 2) (NIST SP 800-171), or establish a SSP(s) and POA&Ms that varies from NIST 800-171 only in accordance with DFARS clause 252.204-7012(b) (2), for all covered contractor information systems affecting this contract.

b) Notwithstanding the allowance for such variation, the contractor shall identify in any SSP and POA&M their plans to implement the following, at a minimum:

(1) Implement Control 3.5.3 (Multi-factor authentication). This means that multi-factor authentication is required for all users, privileged and unprivileged accounts that log into a network. In other words, any system that is not standalone should be required to utilize acceptable multi-factor authentication. For legacy systems and systems that cannot support this requirement, such as CNC equipment, etc., a combination of physical and logical protections acceptable to the Government may be substituted;

(2) Implement Control 3.1.5 (least privilege) and associated Controls, and identify practices that the contractor implements to restrict the unnecessary sharing with, or flow of, covered defense information to its subcontractors, suppliers, or vendors based on need-to-know principles;

(3) Implement Control 3.1.12 (monitoring and control remote access sessions) - Require monitoring and controlling of remote access sessions and include mechanisms to audit the sessions and methods.

(4) Audit user privileges on at least an annual basis;

(5) Implement:

i. Control 3.13.11 (FIPS 140-2 validated cryptology or implementation of NSA or NIST approved algorithms (i.

e. FIPS 140-2 Annex A: AES or Triple DES) or compensating controls as documented in a SSP and POAM);

and,

ii. NIST Cryptographic Algorithm Validation Program (CAVP) (see https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program);

(6) Implement Control 3.13.16 (Protect the confidentiality of CUI at rest) or provide a POAM for implementation which shall be evaluated by the Navy for risk acceptance.

(7) Implement Control 3.1.19 (encrypt CUI on mobile devices) or provide a plan of action for implementation which can be evaluated by the Government Program Manager for risk to the program.

3. Cyber Incident Response

a) The Contractor shall, within fifteen (15) days of discovering the cyber incident (inclusive of the 72-hour reporting period), deliver all data used in performance of the contract that the Contractor determines is impacted by the incident and begin assessment of potential warfighter/program impact.

b) Incident data shall be delivered in accordance with the Department of Defense Cyber Crimes Center (DC3) Instructions for Submitting Media available at http://www.acq.osd.mil/dpap/dars/pgi/docs /Instructions_for_Submitting_Media.docx. In delivery of the incident data, the Contractor shall, to the extent practical, remove contractor-owned information from Government covered defense information.

c) If the Contractor subsequently identifies any such data not previously delivered to DC3, then the Contractor shall immediately notify the contracting officer in writing and shall deliver the incident data within ten (10) days of identification. In such a case, the Contractor may request a delivery date later than ten (10) days after identification. The contracting officer will approve or disapprove the request after coordination with DC3.

4. Naval Criminal Investigative Service (NCIS) Outreach

The Contractor shall engage with NCIS industry outreach efforts and consider recommendations for hardening of covered contractor information systems affecting DON programs and technologies.

5. NCIS/Industry Monitoring

a) In the event of a cyber incident or at any time the Government has indication of a vulnerability or potential vulnerability, the Contractor shall cooperate with the Naval Criminal Investigative Service (NCIS), which may include cooperation related to: threat indicators; pre-determined incident information derived from the Contractor's infrastructure systems; and the continuous provision of all Contractor, subcontractor or vendor logs that show network activity, including any additional logs the contractor, subcontractor or vendor agrees to initiate as a result of the cyber incident or notice of actual or potential vulnerability.

b) If the Government determines that the collection of all logs does not adequately protect its interests, the Contractor and NCIS will work together to implement additional measures, which may include allowing the installation of an appropriate network device that is owned and maintained by NCIS, on the Contractor's information systems or information technology assets. The specific details (e.g., type of device, type of data gathered, monitoring period) regarding the installation of an NCIS network device shall be the subject of a separate agreement negotiated between NCIS and the Contractor. In the alternative, the Contractor may install network sensor capabilities or a network monitoring service, either of which must be reviewed for acceptability by NCIS. Use of this alternative approach shall also be the subject of a separate agreement negotiated between NCIS and the Contractor.

c) In all cases, the collection or provision of data and any activities associated with this statement of work shall be in accordance with federal, state, and non-US law.

(End of Text)

C-211-H018 APPROVAL BY THE GOVERNMENT (NAVSEA) (JAN 2019) (Jan 2019)

Approval by the Government as required under this contract and applicable specifications shall not relieve the Contractor of its obligation to comply with the specifications and with all other requirements of the contract, nor shall it impose upon the Government any liability it would not have had in the absence of such approval.

(End of Text)

C-211-H016 SPECIFICATIONS AND STANDARDS (NAVSEA) (OCT 2018) (Oct 2018)

(a) Definitions.

(i) A "zero-tier reference" is a specification, standard, or drawing that is cited in the contract (including its attachments).

(ii) A "first-tier reference" is either: (1) a specification, standard, or drawing cited in a zero-tier reference, or (2) a specification cited in a first-tier drawing.

(b) Requirements. All zero-tier and first-tier references, as defined above, are mandatory for use. All lower tier references shall be used for guidance only unless specifically identified below.

(End of Text)

C-211-H017 UPDATING SPECIFICATIONS AND STANDARDS (NAVSEA) (DEC 2018) (Dec 2018)

The contractor may request that this contract be updated to include the current version of the applicable specification or standard if the update does not affect the form, fit or function of any deliverable item or increase the cost/price of the item to the Government. The contractor should submit update requests to the Procuring Contracting Officer with copies to the Administrative Contracting Officer and cognizant program office representative for approval. The contractor shall perform the contract in accordance with the existing specifications and standards until notified of approval/disapproval of its request to update by the Procuring Contracting Officer. Any approved alternate specifications or standards will be incorporated into the contract.

(End of Text)

C-227-H009 ACCESS TO DATA OR COMPUTER SOFTWARE WITH RESTRICTIVE

MARKINGS (NAVSEA) (JAN 2019)

(Jan 2019)

(a) Performance under this contract may require that the Contractor have access to technical data, computer software, or other sensitive data of another party that contains restrictive markings. If access to such data or software is required or to be provided, the Contractor shall enter into a written agreement with such party prior to gaining access to such data or software. The agreement shall address, at a minimum, (1) access to, and use of, the restrictively marked data or software exclusively for the purposes of performance of the work required by this contract, and (2) safeguards to protect such data or software from unauthorized use or disclosure for so long as the data or software remains properly restrictively marked. In addition, the agreement shall not impose any limitation upon the Government or its employees with respect to such data or software. A copy of the executed agreement shall be provided to the Contracting Officer. The Government may unilaterally modify the contract to list those third parties with which the Contractor has agreement(s).

(b) The Contractor agrees to: (1) indoctrinate its personnel who will have access to the data or software as to the restrictions under which access is granted; (2) not disclose the data or software to another party or other Contractor personnel except as authorized by the Contracting Officer; (3) not engage in any other action, venture, or employment wherein this information will be used, other than under this contract, in any manner inconsistent with this requirement; (4) not disclose the data or software to any other party, including, but not limited to, joint venturer, affiliate, successor, or assign of the Contractor; and (5) reproduce the restrictive stamp, marking, or legend on each use of the data or software whether in whole or in part.

(c) These restrictions on use and disclosure of the data and software also apply to information received from the Government through any means to which the Contractor has access in the performance of this contract that contains restrictive markings.

(d) The Contractor agrees that it will promptly notify the Contracting Officer of any attempt to gain access to any information with restrictive markings. Such notification shall include the name and organization of the individual, company, or Government representative seeking access to such information.

(e) The Contractor shall include this requirement in subcontracts of any tier which involve access to information covered by paragraph (a), substituting "subcontractor" for "Contractor" where appropriate.

(f) Compliance with this requirement is a material requirement of this contract.

(End of Text)

C-227-H006 DATA REQUIREMENTS (NAVSEA) (OCT 2018) (Oct 2018)

The data to be furnished hereunder shall be prepared in accordance with the Contract Data Requirements List, DD Form 1423, Exhibit A, attached hereto.

(End of Text)

C-227-H010 COMPUTER SOFTWARE AND COMPUTER DATA BASES DELIVERED TO OR

RECEIVED FROM THE GOVERNMENT (NAVSEA) (JAN 2019)

(Jan 2019)

(a) The Contractor agrees to test for viruses, malware, Trojan Horses, and other security threats such as those listed in NIST Special Publication 800-12 Rev 1, An Introduction to Computer Security, The NIST Handbook, Chapter 4, in all computer software and computer data bases (as defined in the clause entitled "Rights In Noncommercial Computer Software and Noncommercial Computer Software Documentation" (DFARS 252.227-7014)), before delivery of that computer software or computer data base in whatever media and on whatever system the computer software or data base is delivered whether delivered separately or imbedded within delivered equipment. The Contractor warrants that when delivered any such computer software and computer data base shall be free of viruses, malware, Trojan Horses, and other security threats such as those listed in NIST Special Publication 800-12 Rev 1.

(b) The Contractor agrees that prior to use under this contract, it shall test any computer software and computer data base received from the Government for viruses, malware, Trojan Horses, and other security threats listed in NIST Special Publication 800-12 Rev 1, An Introduction to Computer Security, The NIST Handbook, Chapter 4.

(c) Any license agreement governing the use of any computer software or computer software documentation delivered to the…