A04 Statement of Work.pdf

STATEMENT OF WORK

FOR

MODERNIZATION AND ENGINEERING

SUPPORT FOR THE NEDU OCEAN

SIMULATION FACILITY CONTROL

SYSTEM

1.0 SCOPE

The Ocean Simulation Facility Control System (OSF-CS) is a life-safety critical, standalone Platform IT (PIT) system located at the Navy Experimental Diving Unit (NEDU). The system requires comprehensive hardware and software modernization to replace obsolete components, reconstitute a laboratory environment, and achieve a secure, Windows 11-compliant baseline. The primary goal of this effort is a one-time migration and modernization project. This SOW encompasses the engineering support required to reconstitute a test lab, modernize the OSF-CS hardware and software, and provide all necessary technical support to ensure a successful migration. The contractor shall provide all personnel, technical expertise, and project management to perform the phased tasks outlined below.

2.0 APPLICABLE DOCUMENTS

The following documents, of the exact issue shown, form a part of this SOW to the extent specified herein. In the event of conflict between the documents referenced herein and the SOW, the contents of this SOW shall take precedence.

2.1 Military Standards:

List the standard here otherwise “none”

2.2 Military Specifications:

List the standard here otherwise “none”

2.3 Other Documents:

DoD Manual 8140.03, DoD Cyberspace Workforce Framework (DCWF)

3.0 REQUIREMENTS (CDRL A001, A002, A003, A004, A005, A006, A007, A008)

The Contractor shall execute the modernization project in a single, phased effort, providing necessary artifacts and deliverables in accordance with the Contract Data Requirements List (CDRL).

3.0.1 The Contractor shall reconstitute the NEDU-provided laboratory environment at the Contractor's off-site facility. To bypass physical facility power constraints, the Contractor shall virtualize the system architecture using Rockwell Automation Studio 5000 Logix Emulate in place of hosting the physical Variable Speed Drive (VSD) hardware. To ensure compliance with stringent cybersecurity requirements, this virtualized environment shall be hosted and maintained on a dedicated server platform. A dedicated computer, provided by the Government, shall be utilized by the Contractor and integrated to host the LabVIEW and emulation environment The Contractor shall provide an Off-Site Lab Reconstitution & Emulation Validation Report (confirming successful Studio 5000 Logix, Studio 5000 Logix Emulate, Server Deployment, and LabVIEW configuration) (CDRL A001).

3.0.2 To ensure compliance with stringent cybersecurity requirements and support additional virtualization, the

Contractor shall procure, furnish, deploy, and configure a dedicated server platform. This dedicated server infrastructure will securely host the virtualized development and emulation environment.

3.0.3 A dedicated computer, provided by the Government, shall be utilized by the Contractor and integrated to host the LabVIEW and emulation environment (CDRL A002).

3.0.4 The Contractor shall replace obsolete operator workstations with modern Windows 11-capable hardware while initially retaining the current Windows 10 environment.

3.0.4.1 The Contractor shall provide the following hardware/configurations:

Virtualization Server: One Dual-socket rack server, high core count, 512 GB+ RAM, redundant PSU; sized to securely host the virtualized OSF-CS development, emulation, and test environment.

Storage Configuration: One Enterprise NVMe/SSD array with RAID for VM datastores, snapshots, and lab/validation images.

UPS / Rack / PDU: One Rack-mount UPS, PDU, rails, and rack accessories for safe power and mounting.

Cabling / KVM / Network: Structured cabling, KVM access, transceivers, and miscellaneous network connectivity items.

Miscellaneous Infrastructure & Incidentals: Mounting hardware, labels, media, removable storage, and incidental infrastructure components.

3.0.5 The Contractor shall perform a comprehensive analysis to identify and mitigate any interoperability issues with the planned upgrade to a Windows 11 environment. The Contractor shall deliver a Windows 11 Interoperability Analysis Report, detailing all potential risks, issues, and recommended mitigation strategies.

(CDRL A003).

3.0.6 The Contractor shall execute a phased upgrade from Windows 10 to Windows 11, starting with the maintenance laptop, followed by the lab environment. The Contractor shall deliver a test report from the upgraded Windows 11 maintenance laptop and confirming successful Windows 11 lab environment upgrade.

(CDRL A004).

3.0.7 The Contractor shall upgrade main software components to the latest stable versions as the final deliverable.

3.0.8 The Contractor shall perform system hardening on the final baseline by applying applicable DISA STIGs and SRGs. The Contractor shall deliver:

o Final, modernized, and verified codebase (CDRL A005).

o Technical Hardening Artifacts (STIG .ckl files and ACAS .nessus scans) to support the Government-led Risk Management Framework (RMF) effort CDRL (A006).

o Final Project Report and Government-signed Factory Acceptance Test (FAT)[GG1.1]

[GG2.1]Report (CDRL A007).

3.0.9 The Contractor shall provide a Monthly Status Report (CDRL A008), outlining status of all tasking.

3.1 PLACE OF PERFORMANCE

Performance Site Location Authorized Activities & Scope

Navy Experimental Diving Unit (NEDU)

321 Bullfinch Rd, Panama City Beach, FL 32407

Physical workstation swaps, live-system integration, Windows 11 maintenance laptop deployment, on-site testing, and final Government Acceptance Testing (GAT).

Contractor Facility Contractor-Owned and Operated Facility (Off- Site)

Reconstitution of the NEDU-provided laboratory environment, hosting of the LabVIEW environment (including server infrastructure), software code modernization, and development-level validation.

3.2 RMF RESPONSIBILITY MATRIX

Task Responsible Party Description eMASS Entry Government (NEDU) All data entry and package management within eMASS.

Policy Development Government (NEDU) Creation of SSP, SLCM, and other RMF-required policies.

Technical Scans Contractor Execution of ACAS scans and STIG checklists on the modernized system.

Artifact Delivery Contractor Delivery of raw .nessus and .ckl files to the NEDU ISSM for RMF package inclusion.

4.0 GOVERNMENT FURNISHED PROPERTY (GFP):

4.1 The Government will provide the following GFI and GFE to the contractor:

Studio 5000 Logix Software & Licensing.

On–Site Physical Spare VSD Hardware (accessible at NEDU during validation windows).

LabVIEW Host Computer & OSF–CS Workstations (new computer hardware).

Legacy Source Code and System Documentation (unclassified OSF–CS codebase).

4.2 Access to Government Facilities

The Government will provide the contractor access to Government facilities to accomplish statement of work tasking.

The Contractor shall provide a list of employees who require access to these areas, including standard security clearance information for each person, to the Procuring Contracting Officer (PCO) no later than three business days after the date of award. Access to Government buildings at Naval Support Activity Panama City (NSA PC) is from 0600 to 1800 Monday through Friday, except Federal holidays. Normal work hours are from 0700 to 1700, Monday through Friday. Contractor employees shall be under Government oversight at all times. Government oversight requires that a Government employee be present in the same building/facility whenever Contractor employee(s) are performing work under this task order. Contractor personnel are not allowed to access any Government buildings at NSA PC outside the hours of 0600 to 1800 without the express approval of the Procuring Contracting Officer (PCO). When a Government facility is closed or early dismissal of Federal employees is directed due to severe weather, security threat, or a facility related problem that prevents personnel from working, onsite Contractor personnel regularly assigned to work at that facility should follow the same reporting and departure directions given to Government personnel.

5.0 DATA DELIVERABLES

Data shall be provided in accordance with the Contract Data Requirements List (CDRL) DD Form 1423.

All source code must be delivered in its native, un-compiled, human-readable format.

The U.S. Government shall have unlimited Government Purpose Rights (GPR) to all technical data, computer software, source code, and documentation developed, delivered, or generated under this Statement of Work.

6.0 PERIOD OF PERFORMANCE

The items on this order shall be delivered no later than 12 months after Contract award.

7.0 SECURITY

This requirement is UNCLASSIFIED. The Contractor will not require access to nor be required to generate classified information to perform the requirement.

7.1 Release of Information

Release of information shall be in accordance with Section I, DFARS Clause 252.204-7000, Disclosure of Information. All technical data provided to the contractor by the Government shall be protected from public disclosure in accordance with the markings contained thereon. All other information relating to the items to be delivered or services to be performed under this task order may not be disclosed by any means without prior approval of the appropriate NSWC PCD authority. Dissemination or public disclosure includes, but is not limited to, permitting access to such information by foreign nationals or by any other person or entity;

publication of technical or scientific papers; advertising; or any other proposed public release. The contractor shall provide adequate physical protection to such information to preclude access by any person or entity not authorized such access by the Government.

7.2 Controlled Unclassified Information (CUI)

Controlled unclassified information (CUI) is official information that requires the application of controls and protective measures for a variety of reasons and has not been approved for public release, to include technical information, proprietary data, information requiring protection under the Privacy Act of 1974, and Government-developed privileged information involving the award of contracts. CUI is a categorical designation that refers to unclassified information that does not meet the standards for National Security Classification under Executive Order 13526, but is (a) pertinent to the national interest of the United States or to the important interests of entities outside the Federal Government, and (b) under law or policy requires protection from unauthorized disclosure, special handling safeguards, or prescribed limits on exchange or dissemination.

7.3 Minimum Requirements for Access to Controlled Unclassified Information (CUI)

Access to CUI requires security clearance eligibility based on a Tier 3 Background Investigation. In addition, all contractor personnel performing work requiring privileged access on the OSF-CS must meet the requirements of the DoD Cyberspace Workforce Framework (DCWF) as outlined in DoD Manual 8140.03, holding valid baseline certifications (e.g., Security+, CASP+, or CISSP) and relevant OS/CE training.

Contact for validation that employees have the required eligibility, prior to providing access to CUI.

7.4 Minimum Protection Requirements for Controlled Unclassified Information

Security classification guides and unclassified limited documents are not authorized for public release and cannot be posted on a publicly accessible webserver or transmitted over the Internet unless appropriately encrypted.

7.5 CUI

CUI must be marked, controlled and safeguarded in accordance with DoDI 5200.48, DoD Information Security Program: Controlled Unclassified Information (CUI).

7.6 Security of Unclassified DoD Information on Non-DoD Information Systems (DoDI 8582.01)

7.6.1 DoD Policy

Adequate security shall be provided for all unclassified DoD information on non-DoD information systems.

7.6.2 Information Safeguards

Unclassified DoD information that has not been cleared for public release may be disseminated by the Contractor, grantee, or awardee to the extent required to further the contract, grant, or agreement objectives, provided that the information is disseminated within the scope of assigned duties and with a clear expectation that confidentiality will be preserved. Examples include:

(a) Non-public information provided to a Contractor (e.g., with a request for proposal).

(b) Information developed during the course of a contract, grant, or other legal agreement (e.g., draft documents, reports, or briefings and deliverables).

(c) Privileged information contained in transactions (e.g., privileged contract information, program schedules, contract-related event tracking).

Note: It is recognized that adequate security will vary depending on the nature and sensitivity of the information on any given non-DoD information system. However, all unclassified DoD information in the possession or control of non-DoD entities on non-DoD information systems shall minimally be safeguarded as follows:

(a) Do not process unclassified DoD information on publically available computers (e.g., those available for use by the general public in kiosks or hotel business centers).

(b) Protect unclassified DoD information by at least one physical or electronic barrier (e.g., locked container or room, logical authentication or logon procedure) when not under direct individual control of an authorized user.

(c) At a minimum, overwrite media that have been used to process unclassified DoD information before external release or disposal.

(d) Encrypt all information that has been identified as CUI when it is stored on mobile computing devices such as laptops and personal digital assistants, compact disks, or authorized removable storage media such as thumb drives and compact disks, using the best encryption technology available to the Contractor or teaming partner.

(e) Limit transfer of unclassified DoD information to subcontractors or teaming partners with a need to know and obtain a commitment from them to protect the information they receive to at least the same level of protection as that specified in the contract or other written agreement.

(f) Transmit e-mail, text messages, and similar communications containing unclassified DoD information using technology and processes that provide the best level of privacy available, given facilities, conditions, and environment. Examples of recommended technologies or processes include closed networks, virtual private networks, public key-enabled encryption, and transport layer security

(TLS).

(g) Encrypt organizational wireless connections and use encrypted wireless connections where available when traveling. If encrypted wireless is not available, encrypt document files (e.g., spreadsheet and word processing files), using at least application-provided password protected level encryption.

(h) Transmit voice and fax transmissions only when there is a reasonable assurance that access is limited to authorized recipients.

(i) Do not post unclassified DoD information to website pages that are publicly available or have access limited only by domain or Internet protocol restriction. Such information may be posted to website pages that control access by user identification and password, user certificates, or other technical means and provide protection via use of transport layer security or other equivalent technologies during transmission. Access control may be provided by the intranet (vice the website itself or the application it hosts).

(j) Provide protection against computer network intrusions and data exfiltration, minimally including:

(1) Current and regularly updated malware protection services, e.g., anti-virus, anti-spyware.

(2) Monitoring and control of both inbound and outbound network traffic (e.g., at the external boundary, sub-networks, individual hosts), including blocking unauthorized ingress, egress, and exfiltration through technologies such as firewalls and router policies, intrusion prevention or detection services, and host-based security services.

(3) Prompt application of security-relevant software patches, service packs, and hot fixes.

(k) Comply with other current Federal and DoD information protection and reporting requirements for specified categories of information (e.g., medical, proprietary, Critical Program Information (CPI), personally identifiable information, export controlled) as specified in contracts, grants, and other legal agreements.

(l) Report loss or unauthorized disclosure of unclassified DoD information in accordance with contract, grant, or other legal agreement requirements and mechanisms.

(m) Do not use external IT services (e.g., e-mail, content hosting, database, document processing) unless they provide at least the same level of protection as that specified in the contract or other written agreement.

7.7 Operations Security (OPSEC)

Operations Security (OPSEC) is concerned with the protection of critical information: facts about intentions, capabilities, operations, or activities that are needed by adversaries or competitors to bring about failure or unacceptable consequences of mission accomplishment. The Contractor, subcontractors and their personnel shall employ OPSEC countermeasures to mitigate the susceptibility of critical information to exploitation.

Critical information includes information regarding:

Operations, missions, and exercises, test schedules or locations;

Location/movement of sensitive information, equipment, or facilities;

Force structure and readiness (e.g., recall rosters);

Capabilities, vulnerabilities, limitations, security weaknesses;

Intrusions/attacks of DoD networks or information systems;

Network (and system) user identifications and passwords;

Movements of key personnel or visitors (itineraries, agendas, etc.); and

Security classification of equipment, systems, operations, etc.

The Contractor, subcontractors and their personnel shall employ the following countermeasures to mitigate the susceptibility of critical information to exploitation, when applicable:

Practice OPSEC and facilitate OPSEC awareness;

Immediately retrieve documents from printers assessable by the public;

Shred sensitive and Controlled Unclassified Information (CUI) documents when no longer needed;

Protect information from personnel without a need-to-know;

When promulgating information, limit details to that essential for legitimacy;

During testing and evaluation, practice OPSEC methodologies of staging out of sight, desensitization, or speed of execution, whenever possible.

8.0 DISTRIBUTION LIMITATION STATEMENTS

Distribution Statements and Warning Notices: The Contractor shall place the appropriate Distribution Statement on information associated/generated with this contractual effort, per the applicable Security Classification Guide, and carry forward the markings on documents provided by the government, along with the following statements on all technical documents/media, as applicable.

WARNING - THIS DOCUMENT CONTAINS TECHNICAL DATA WHOSE EXPORT IS RESTRICTED BY

THE ARMS EXPORT CONTROL ACT (SECTION 2751 OF TITLE 22, UNITED STATES CODE) OR THE EXPORT CONTROL REFORM ACT OF 2018 (CHAPTER 58 SECTIONS 4801-4852 OF TITLE 50, UNITED

STATES CODE). VIOLATIONS OF THESE EXPORT LAWS ARE SUBJECT TO SEVERE CRIMINAL

PENALTIES. DISSEMINATE IN ACCORDANCE WITH PROVISIONS OF DOD DIRECTIVE 5230.25 AND

DOD INSTRUCTION 2040.02.

DESTRUCTION NOTICE - CLASSIFIED INFORMATION, DESTROY IN ACCORDANCE WITH

SECNAVINST 5510.36, (DON INFORMATION SECURITY PROGRAM) OR NISPOM RULE.

UNCLASSIFIED LIMITED DOCUMENTS, (E.G., CUI, DISTRIBUTION STATEMENT CONTROL)

DESTROY PER DODI 5200.48.