v4.4_AUGUST2025

STATEMENT OF WORK (SOW)

CONFIGURATION MANAGEMENT (CM) AND INTEGRATED LOGISTICS SUPPORT (ILS)

FOR THE MARITIME SURVEILLANCE SYSTEMS (MSS) PORTFOLIO

1.0 Background

The Naval Undersea Warfare Center Division, Newport (NUWCDIVNPT) is the Navy’s principal research, development, test, and evaluation (RDT&E) center for submarine and undersea warfare systems. The NUWCDIVNPT Sensors and Sonar Department (Code 15) is responsible for the full life-cycle support for a variety of undersea surveillance systems.

This SOW establishes the requirement for comprehensive technical and administrative support services for the execution of baseline and configuration management for the Maritime Surveillance Systems (MSS) portfolio. The primary tool for managing this data shall be the Government-designated Configuration Management Professional (CMPro) software suite.

1.1 Places of Performance

NUWCDIVNPT, Newport, RI Purvis Systems, Middletown RI

1.2 Authorized Users

NUWCDIVNPT Code 15

1.3 Sponsors

Program Executive Office Undersea Warfare Systems (PEO-UWS) Maritime Surveillance Systems Program Office (PMS485)

1.4 Types of Funding

Operations and Maintenance, Navy (O&MN) Research, Development, Test & Evaluation (RDT&E) Other Procurement, Navy (OPN)

2 Scope

The Contractor shall provide engineering, technical, and administrative services to support the configuration and data management of the Maritime Surveillance Systems (MSS) portfolio. The scope includes the administration and technical execution of configuration management functions using the CMPro database. Contractor’s administrative duties shall include user account management, workflow customization, data entry, and report generation. Server-side maintenance is excluded. The Contractor shall support all functional modules of CMPro as required by the Government.

2.1 Program or Systems Supported

Maritime Surveillance Systems (MSS) portfolio inclusive of Fixed Surveillance Systems, Mobile Surveillance Systems, and Deployed Surveillance Systems

3 Applicable Documents

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

NUMBER TITLE

REVISION/

DATE

APPLICABLE

SOW TASK

3.1 DoD Issuances

3.1.1 MIL-HDBK-61A 07-Feb-2001 4.1.1 - 4.1.4

3.1.2 Department of Defense Manual (DODM)

8140.03 Feb 2023 4.1.2, 3.1.3

MIL-STD-31000B, Technical Data Packages

31-Oct-2018 4.1.2

3.1.4 Engineering Change Proposal, DD FORM

20-Apr-2015 4.1.2

3.2 Navy Issuances

3.2.1 Secretary of the Navy (SECNAV) M-

5510.30 Jan 2020 4.1.1

4.0 Technical Requirements

The Contractor shall perform the following CM-specific tasks IAW the ADs in Section 3.0 and using Government Furnished Information (GFI) in Section 6.0. Upon award of a funded Task Order, the Government will issue formal requests for Configuration Management Support work via email, detailing which tasking is required and specifying any applicable GFI and Applicable Documents/Databases the Government anticipates the Contractor will require to perform the tasking.

4.1 Configuration Management Support

General

Upon receipt of a Government request for work via email, the Contractor shall provide an estimate to the Government for the completion of such work, detailing number of hours applicable to each labor category necessary to complete tasking. The COR will review all quotes with an estimated value of $5,000 or less and authorize the Contractor to proceed or engage with the Contracting Officer (KO) if needed. For any quotations for configuration management support above $5,000, the Contractor shall not proceed until the KO has provided written authorization. The Contractor shall track the expenditure of hours per labor category, on both the contract and task order levels, ensuring that the hours for work performed do not exceed the total funded amount.

4.1.1 Configuration Identification

The Contractor shall utilize CMPro to compile, review, and maintain Configuration Item Verification Reports (CIVRs) to document the hardware, software, and firmware baseline for MSS configurations. The Contractor shall identify all configuration items from the system level down to the component level. Upon receipt of Government request via email, the Contractor shall provide Unique Identifier (UID) labels for units and spare parts.

Deliverable: CDRL A001 – Configuration Identification Report Deliverable: CDRL A002 – Unique Identification (UID) Labels

4.1.2 Engineering Change Proposal Support

The Contractor shall use CMPro to draft, track, and manage Preliminary Engineering Change Proposals (PECPs), Engineering Change Proposals (ECPs), and Engineering Change Instructions (ECIs). The Contractor shall provide review of change documentation for technical and logistical accuracy, participate in the Configuration Review Board (CRB) and Configuration Control Board (CCB) process, adjudicate comments, and track the workflow status of all change documents. The Government is the final approval authority for all change documentation.

Deliverable: CDRL A003 – Engineering Change Proposals (ECPs) Deliverable: CDRL A004 – Engineering Change Instructions (ECIs) Deliverable: CDRL A005 – Configuration Review Board Status Report

4.1.3 Configuration Status Accounting (CSA)

The Contractor shall provide on-site or remote users of the CMPro database to maintain, track, and report on CSA records. This includes maintaining records for each as-designed, as-built, and as-modified system variant. The Contractor shall track the history of any change and the status of configuration audit findings within the CMPro database.

Deliverable: CDRL A006 – Configuration Status Accounting (CSA) Information

4.1.4 CM Meeting Support

The Contractor shall utilize outputs from CMPro to prepare materials for, attend, and document minutes for Government-led CM-focused meetings, such as Configuration Review Boards (CRBs). The Contractor shall track and report on action items resulting from these meetings.

Deliverable: CDRL A007 – Meeting Minutes Deliverable: CDRL A008– Presentation Material Deliverable: CDRL A009 – Action Item Reports

5.0 Progress Reports

Reserved

6.0 Government Furnished Information

The following Government Furnished Information (GFI) will be made available under this contract.

Number Title Applicable SOW Task

Number

6.1 Access to the Government-provided CMPro database.

ALL

6.2 Access to Navy Data Environment (NDE), NAVSEA Configuration Data Managers Database (CDMD-OA)).

4.1.2

6.3 Applicable baseline CM documentation for the MSS portfolio.

ALL

7.0 Government Furnished Property

Reserved

8.0 Quality Surveillance and Performance Standards

Reserved

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

Exception #1 national security for Code 15 MARITIME SURVEILLANCE Program.

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). 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. To include initial and annual OPSEC 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.