SOW.pdf

v3.1_MARCH2023

STATEMENT OF WORK (SOW)

Mission Model Naval Simulation Capability

1.0 Background

Naval Undersea Warfare Center Division, Newport (NUWCDIVNPT), Code 60 and Naval Air Warfare Center Aircraft Division (NAWCAD), Warfare Effectiveness Department require a mission-level modeling capability in order to assess the performance of undersea warfare capabilities at a holistic level across domains and phases of naval warfare. Naval Simulation System (NSS) is a mission-level model intended to focus on command, control, and communications (C3). NSS will provide a common baseline of models, scenarios, and databases to ensure assessments of warfighting capabilities are comparable between domains.

1.1 Places of Performance: NUWCDIVNPT, NAWCAD, and the contractor’s facility

1.2 Authorized User: NUWCDIVNPT Code 60 and NAWCAD

1.3 Sponsor: NUWCDIVNPT Code 60

1.4 Types of Funding: Overhead

2.0 Scope

The contractor shall provide help desk support for Naval Simulation System (NSS) with ObjectStore.

NSS will be located on computers on both NUWCDIVNPT Code 60’s Research, Development, Test and Evaluation computers, as well as systems utilized by NAWCAD.

The contractor shall notify NUWCDIVNPT and NAWCAD when patches, updates, or changes are made to NSS. This notification shall include a description of the changes made along with the latest version of

NSS.

The contractor shall digitally receive and send data up to the SECRET//NOFORN level which may include Foreign Government Information (FGI). This is to ensure timely and accurate debugging and support by the contractor.

Additionally, both Code 60 and NAWCAD have the option to enact a 3 day site visit by the contractor to NUWCDIVNPT and NAWCAD respectively. The trip shall consist of 3 consecutive workdays for 8 working hours per day to a total of 24 hours.

For both NUWCDIVNPT and NAWCAD the trip shall occur in May of 2025, and the option shall be exercised by March 1, 2025.

3.0 RESERVED

4.0 Technical Requirements

The contractor shall provide NUWCDIVNPT Code 60 and NAWCAD with help desk services in accordance with Government Furnished Information (GFI), and an optional site visit at each location for technical support. Helpdesk support hours may be used for correspondence, bug fixes, and software updates requested by NUWCDIVNPT and NAWCAD.

4.1 NSS Software Technical Support

4.1.1 The contractor shall optionally provide NUWCDIVNPT with onsite support services with database/scenario development, scenario modeling, and installation corrections. One 3-day trip to Newport, RI is required in support of this task. The onsite support will consist of three consecutive workweek days (8 hours each day for a total of 24 hours). No software changes will be implemented onsite at NUWCDIVNPT during the onsite support trip. The trip shall occur during the month of May 2025, and the option shall be exercised by March 1 2025.

4.1.2 The contractor shall provide NUWCDIVNPT 100 hours of phone/email help desk service support for scenario development, bug fixes, and answering questions for NSS software licenses over the course of the Period of Performance. Phone/email help desk service support shall be provided as needed Monday – Friday, excluding Federal Holidays, 8:00 AM to 5:00 PM pacific time. The contractor shall incorporate any software changes implemented within the 48 hours of help desk support into a self-installing NSS software patch and provide it to NUWCDIVNPT via secure website, CD, or another mutually agreed-upon mechanism at the end of the period of performance.

4.1.3 The contractor shall optionally provide NAWCAD with onsite support services with database/scenario development, scenario modeling, and installation corrections. One 3-day trip to Patuxent River, MD is required in support of this task. The onsite support will consist of three consecutive workweek days (8 hours each day for a total of 24 hours). No software changes will be implemented onsite at NAWCAD during the onsite support trip. The trip shall occur during the month of May 2025, and the option shall be exercised by March 1 2025.

4.1.4 The contractor shall provide NAWCAD 50 hours of phone/email help desk service support for scenario development, bug fixes, and answering questions for NSS software licenses over the course of the Period of Performance. Phone/email help desk service support shall be provided as needed Monday – Friday, excluding Federal Holidays, 8:00 AM to 5:00 PM pacific time. The contractor shall incorporate any software changes implemented within the 48 hours of help desk support into a self-installing NSS software patch and provide it to NAWCAD via secure website, CD, or another mutually agreed-upon mechanism at the end of the period of performance.

5.0 Progress Reports

N/A

6.0 Government Furnished Information

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

Number Title Applicable SOW Task Number

6.1 Details on computer network systems, which will host

software products required to support NSS software

4.1.2, 4.1.4

6.2 Bug Reports 4.1.2, 4.1.4

6.3 Scenario information pertaining to bug reports and

studies in order to enable contractor support through proper understanding of modeling intent.

4.1.1-4

7.0 RESERVED

8.0 RESERVED

9.0 RESERVED

10.0 Security Compliance

10.1 Program Protection (Classified)

SECURITY: All Contractor personnel shall adhere to the Security provisions of 32 CFR Part 177 – National Industrial Security Program Operating Manual (NISPOM) and the security requirements of the attached DD254. While performing work associated with NUWCDIVNPT, Contractor personnel shall comply with the NUWCDIVNPT Security Manual and, if at another facility, the security regulations of the host facility. Applicable FAR and DFARS clauses 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.

Contract shall have access to GENSER, SECRET, NOFORN, and FGI classified information only:

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 Commander, Naval Undersea Warfare Center, Division Newport, Newport, RI 02841.

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