PWS_RFI_Posting.pdf

CUI

Military Sealift Command

Civilian Mariner Wireless Network Installation and Sustainment

Continuation of Production Contract

Organization: Military Sealift Command (MSC) Title: Civilian Mariner Wireless Network (CivMar WiN) Installation and Sustainment Contract Place of Performance: Ship layberth locations (CONUS and OCONUS) Government and commercial shipyard facilities (CONUS and OCONUS) MSC, and subordinate command, government facilities (CONUS and OCONUS) NIWC LANT government facilities Contractor facilities Period of Performance: 16 June 2027 to 15 June 2032 Quantity: Initial installation of CivMar WiN on thirty-six (36) ships. Technology refresh, coupled with network expansion, of CivMar WiN on thirty-five (35) additional ships. Operations and sustainment of CivMar WiN on seventy-one (71) ships, one (1) development instance and one (1) production baseline instance at a government facility and associated cloud management environments.

Table of Contents

1. Introduction/Background

2. Scope

3. References / Specifications

4. Requirements

4.1 Program Management Support

4.1.1 Program Management

4.1.2 Quarterly In-Progress Reviews

4.1.3 Meeting Support

4.1.4 Status and Progress Reporting

4.1.5 Contract Closeout

4.2 Design and Architecture Support

4.2.1 Network

4.2.2 Satellite Communications

4.2.3 Cloud Network

4.3 Systems Engineering Support

4.3.1 Systems Engineering

4.3.2 Requirements Gathering and Analysis

4.3.3 Cybersecurity Compliance Planning

4.3.4 System Architecture Development

4.3.5 Detailed Technical Design

4.3.6 Site Surveys and Needs Assessment

4.3.7 Radio Frequency Engineering and Analysis

4.3.8 Technical Reviews

4.3.9 Documentation

4.4 Cybersecurity Engineering Support

4.4.1 Cybersecurity Engineering and Analysis

4.4.2 RMF Cyber Remediation

4.4.3 Cybersecurity Documentation and Support

4.5 Integration and Implementation

4.5.1 Integration and Implementation Planning

4.5.2 Procurement and Staging

4.5.3 Installation

4.6 Operations and Sustainment

4.6.1 Operations and Sustainment Requirements

4.6.2 Service Management

4.6.3 Service Level Objectives

4.6.4 Roles and Responsibilities

5. Surge Support

5.1 Design and Architecture Surge Support

5.2 Cybersecurity Engineering Surge Support

5.3 Systems Engineering Surge Support

5.4 Integration and Implementation Surge Support

5.5 Operations and Sustainment Surge Support

6. Data Deliverables

7. Delivery Method

8. Patents, Data Rights, and Copyrights

9. Security

9.1 Organization

9.1.1 Security Classification

9.1.2 Clearance Eligibility

9.1.3 Security Officer

9.2 Personnel

9.2.1 Personnel Clearance

9.2.2 Physical Access to Government Facilities and Installations

9.2.3 Identification and Disclosure Requirements

9.2.4 Government Badge Requirements

9.2.5 Common Access Card (CAC) Requirements

9.2.6 Accessing Navy Enterprise Resources Planning System

9.2.7 Mandatory Training

9.2.8 Accessing Government Information Systems and Nonpublic Information

9.3 Operations Security (OPSEC) Requirements

9.3.1 Local and Internal OPSEC Requirement

9.3.2 OPSEC Training

9.3.3 MSC OPSEC Program

9.3.4 Classified Contracts

9.4 Information System Security

9.4.1 Hardware and Software

9.4.2 Safeguards

9.4.3 Utilization of a Government-Owned and Government-Controlled Computer Asset

9.5 Enhanced Security Controls

9.5.1 Systems Security Plan and Plan of Action and Milestones Reviews

9.5.2 Compliance to NIST 800-171

9.5.3 Cyber Incident Response

9.5.4 Naval Criminal Investigative Service Outreach

9.5.5 Naval Criminal Investigative Service Industry Monitoring

10. Government Furnished Information

11. Government Property

11.1 Government-Furnished Property

11.2 Government-Furnished Equipment

11.3 Government-Furnished Material

11.4 Contractor-Acquired Property

11.5 Government Property Management

11.5.1 Designated Government Property Administrator

11.5.2 Contractor Property Management System

11.5.3 Government Property Tracking and Reporting

11.5.4 Government Property Transferring Accountability

11.5.5 Government Property Lost or Damaged Items

11.5.6 Government Property Delivery and Disposition

11.6 Transportation of Equipment/Material

12. Travel

12.1 Travel Management

12.2 Travel Locations

12.2.1 Medical Screening for Fleet Support

12.2.2 OCONUS Travel Requirements

12.2.3 General OCONUS Requirements

12.2.4 OCONUS Immunization Requirements

12.2.5 Emergency Medical Screening for OCONUS Travel

12.2.6 Letter of Authorization

13. Quality Assurance

14. Performance Requirements Summary

15. Combatting Trafficking in Persons (CTIP) Certification

16. Whistleblower Requirements

17. Contracting Officer Representative: .............................................. Error! Bookmark not defined.

18. Enclosures: ..................................................................................... Error! Bookmark not defined.

1. Introduction/Background

This Statement of Work (SOW) outlines the requirements for delivering the Civilian Mariner Wireless Network (CivMar WiN), an end-to-end Low Earth Orbit (LEO) satellite communications (SATCOM) connectivity and wireless network system to Military Sealift Command (MSC) ships and end-users. MSC ships include the Fleet Replenishment Oiler, T-AO 187 and T-AO 205 class, the Dry Cargo and Ammunition, T-AKE class, the Fast Combat Support, T-AOE class, the Expeditionary Fast Transport, T-EPF class, the Expeditionary Sea Base, ESB class, the Submarine Tender, AS class, the Command, LCC class, the Hospital, T-AH class, the Rescue and Salvage, T-ARS class, and the Towing, Salvage and Rescue, T-ATS class, the Ocean Surveillance, T-AGOS class, the Oceanographic Survey, T-AGS class, the Submarine Support, T-AGSE class, the Large, Medium-Speed Roll-on/Roll-off, T-AKR class, the Roll-on/Roll-off Container, T-AK class, and other auxiliary and commercially chartered classes of ships. The services will include the provision of a core shipboard network stack, commercial SATCOM backhaul, wireless distribution (Wi-Fi and/or 5G), network segmentation and security, installation, testing, Risk Management Framework (RMF) process management to support Authority to Operate (ATO), technical drawings and documentation, program and logistics management, and planning, design and integration into MSC and Navy enterprise networks.

2. Scope

The objective of this contract is to build upon the prototype efforts and continue the production effort to expand the MSC prototype architecture, transition the capability to full production, and scale the solution across additional MSC vessels. This contract will deliver, operate, refresh and sustain the end-to-end communications infrastructure, ashore and afloat, for MSC ships and end-users in the following performance areas:

• Program Management Support

• Design and Architecture Support

• Systems Engineering Support

• Cybersecurity Engineering Support

• Integration and Implementation

• Operations and Sustainment

3. References / Specifications

Document Number/Title Classification Distribution Document Date

3.1 DISA Security Technical Implementation

Guides (STIGs) Unclassified TBD Most current

3.2

SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations SP 800-53 Rev. 5, Security and Privacy Controls for Info Systems and Organizations | CSRC (nist.gov)

Unclassified TBD 10-Dec-20

3.3

SP 800-37 Rev. 2, Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy SP 800-37 Rev. 2, Unclassified TBD 1-Dec-18 https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final https://csrc.nist.gov/publications/detail/sp/800-37/rev-2/final

Document Number/Title Classification Distribution Document Date

RMF: A System Life Cycle Approach for Security and Privacy | CSRC (nist.gov)

3.4 NIST Special Publication 800-207 Zero Trust Architecture SP 800-207, Zero Trust Architecture | CSRC (nist.gov)

Unclassified TBD 01-Aug-20

3.5 DoD Enterprise Identity, Credential, and Access Management (ICAM) Reference Design, Version 1.0

Unclassified TBD 01-Jun-20

3.6

Committee on National Security Systems (CNSS) Instruction No. 1253, Security Categorization and Control Selection for National Security Systems https://www.dcsa.mil/portals/91/documents/ctp/ nao/ CNSSI_No1253.pdf

Unclassified TBD 27-Mar-14

3.7 Department of Defense (DoD) 5G Strategy (U) Unclassified TBD 2-May-20

3.8 Dr. Shalliam Rix, P. SPAWAR Enterprise Architecture (EA) Model-Based Systems Engineering (MBSE) Process, v.0.2. SPAWAR.

Unclassified TBD 28-Jul-17

3.9 Architecture Data Model: Architecture Description Document, v.1.0. SPAWAR Enterprise Architecture Working Group.

Unclassified TBD 2016

3.10 National Strategy to Secure 5G of the United

States of America. Unclassified TBD 20-Mar

3.11

DoDI 3200.20: Scientific and Engineering Integrity https://www.esd.whs.mil/Portals/54/Documents/ DD/ issuances/dodi/320020p.pdf?ver=2019-04- 16-084237-223

Unclassified TBD 15-Oct-18

3.12

DoDI 3222.03: DoD Electromagnetic Environmental Effects (E3) Program https://www.esd.whs.mil/Portals/54/Documents/ DD/ issuances/dodi/322203p.pdf?ver=2019-02- 26-101527-160

Unclassified TBD 10-Oct-17

3.13

DoDI 4630.09: Communications Waveform Management and Standardization, CH 1 https://www.esd.whs.mil/Portals/54/Documents/ DD/ issuances/dodi/ 463009p.pdf?ver=_AodYK2mcqGmezDUQiIG hA%3d%3d

Unclassified TBD 10-Oct-17

3.14

DoDI 4650.01: Policy and Procedures for Management and Use of the Electromagnetic Spectrum, CH 1 https://www.esd.whs.mil/Portals/54/Documents/ DD/ issuances/dodi/465001p.pdf?ver=2019-01- 24-112300-743

Unclassified TBD 17-Oct-17

3.15 DoDI 5200.44: Protection of Mission Critical Functions to Achieve Trusted Systems & Networks (TSN)

Unclassified TBD 15-Oct-18 https://csrc.nist.gov/publications/detail/sp/800-37/rev-2/final https://csrc.nist.gov/publications/detail/sp/800-37/rev-2/final https://csrc.nist.gov/publications/detail/sp/800-207/final https://csrc.nist.gov/publications/detail/sp/800-207/final https://www.dcsa.mil/portals/91/documents/ctp/nao/%20CNSSI_No1253.pdf https://www.dcsa.mil/portals/91/documents/ctp/nao/%20CNSSI_No1253.pdf https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/320020p.pdf?ver=2019-04-16-084237-223 https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/320020p.pdf?ver=2019-04-16-084237-223 https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/320020p.pdf?ver=2019-04-16-084237-223 https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/322203p.pdf?ver=2019-02-26-101527-160 https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/322203p.pdf?ver=2019-02-26-101527-160 https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/322203p.pdf?ver=2019-02-26-101527-160 https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/%20463009p.pdf?ver=_AodYK2mcqGmezDUQiIGhA%3d%3d https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/%20463009p.pdf?ver=_AodYK2mcqGmezDUQiIGhA%3d%3d https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/%20463009p.pdf?ver=_AodYK2mcqGmezDUQiIGhA%3d%3d https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/%20463009p.pdf?ver=_AodYK2mcqGmezDUQiIGhA%3d%3d https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/465001p.pdf?ver=2019-01-24-112300-743 https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/465001p.pdf?ver=2019-01-24-112300-743 https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/465001p.pdf?ver=2019-01-24-112300-743

Document Number/Title Classification Distribution Document Date https://www.esd.whs.mil/Portals/54/Documents/ DD/ issuances/dodi/520044p.pdf?ver=2019-04- 04-095238-053

3.16

DoDI 8320.05: Electromagnetic Spectrum Data Sharing, CH 1 https://www.esd.whs.mil/Portals/54/Documents/ DD/ issuances/dodi/832005p.pdf?ver=2019-01- 24-135438-937

Unclassified TBD 22-Nov-17

3.17

DoDI 8420.01: Commercial Wireless Local- Area (WLAN) Devices, Systems, and Technologies https://www.esd.whs.mil/Portals/54/Documents/ DD/issuances/dodi/842001_dodi_2017.pdf https://www.esd.whs.mil/Portals/54/Documents/ DD/issuances/dodi/842001_dodi_2017.pdf

Unclassified TBD 3-Nov-17

3.18

DoDI 8510.01: Risk Management Framework (RMF) for DoD Information Technology (IT), CH 2 https://www.esd.whs.mil/Portals/54/Documents/ DD/ issuances/dodi/ 851001p.pdf?ver=qEE2HGN_HE4Blu7161t1T Q%3d%3d

Unclassified TBD 28-Jul-17

3.19

DoDI 8551.01: Ports, Protocols, and Services Management (PPSM) https://www.esd.whs.mil/Portals/54/Documents/ DD/ issuances/dodi/855101p.pdf?ver=2019-02- 26-101525-833

Unclassified TBD 27-Jul-17

3.20 Military Communications-Electronics Board

Pub 8: Standard Spectrum Resource Format Unclassified TBD 2-Mar-09

3.21

NEMA Publication 250-2014: Enclosures for Electrical Equipment (1000 Volts Maximum) Enclosures for Electrical Equipment (1,000 Volts Maximum) (nema.org)

Unclassified TBD 31-Dec-14

3.22

FIPS Publication 140-3: Security Requirements for Cryptographic Modules FIPS 140-3, Security Requirements for Cryptographic Modules | CSRC (nist.gov)

Unclassified TBD 22-Mar-19

3.23 DoD Cloud Strategy Unclassified TBD Dec-18

3.24 DoD Electromagnetic Spectrum (EMS) Strategy

Roadmap and Action Plan Unclassified TBD 20-Feb-14

3.25 DoD Cloud Computing Security Requirements

Guide Unclassified TBD 6-Mar-17

3.26 3GPP TS 23.167 V16.2.0, IP Multimedia Subsystem (IMS) emergency sessions (Release 16)

Unclassified TBD Most current https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/520044p.pdf?ver=2019-04-04-095238-053 https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/520044p.pdf?ver=2019-04-04-095238-053 https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/520044p.pdf?ver=2019-04-04-095238-053 https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/832005p.pdf?ver=2019-01-24-135438-937 https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/832005p.pdf?ver=2019-01-24-135438-937 https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/832005p.pdf?ver=2019-01-24-135438-937 https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/842001_dodi_2017.pdf https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/842001_dodi_2017.pdf https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/842001_dodi_2017.pdf https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/842001_dodi_2017.pdf https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/%20851001p.pdf?ver=qEE2HGN_HE4Blu7161t1TQ%3d%3d https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/%20851001p.pdf?ver=qEE2HGN_HE4Blu7161t1TQ%3d%3d https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/%20851001p.pdf?ver=qEE2HGN_HE4Blu7161t1TQ%3d%3d https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/%20851001p.pdf?ver=qEE2HGN_HE4Blu7161t1TQ%3d%3d https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/855101p.pdf?ver=2019-02-26-101525-833 https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/855101p.pdf?ver=2019-02-26-101525-833 https://www.esd.whs.mil/Portals/54/Documents/DD/%20issuances/dodi/855101p.pdf?ver=2019-02-26-101525-833 https://www.nema.org/standards/view/Enclosures-for-Electrical-Equipment https://www.nema.org/standards/view/Enclosures-for-Electrical-Equipment https://csrc.nist.gov/publications/detail/fips/140/3/final https://csrc.nist.gov/publications/detail/fips/140/3/final

Document Number/Title Classification Distribution Document Date

3.27

NENA 08-752 v1, Technical Requirements for Location Information to Support IP-Based Emergency Services https://cdn.ymaws.com/www.nena.org/resource/ resmgr/ Standards/NENA_08- 752_v1.1_Location_fo.pdf

Unclassified TBD Most current

3.28

DISA DISN Connection Process Guide, Ver. 6 https://dl.dod.cyber.mil/wp-content/uploads/connect/pdf/unclass- DISN_CPG.pdf

Unclassified Sep-16

3.29 Army Regulation 702–19 Reliability, Availability, and Maintainability Unclassified TBD 28-Apr-15

3.30 DoD 5G Strategy Implementation Plan Unclassified TBD Dec 2020

3.31 DoD Cybersecurity Test and Evaluation

Guidebook, Ver 2.0 Unclassified TBD Feb 2020

3.32 FMG Framework to Conduct 5G Testing Unclassified TBD Nov 2020

3.33 NSA/CSA Cybersecurity Solutions Enterprise Gray Implementation Requirements Annex V1.0

Unclassified TBD Apr 2019

3.34 N7.72.9085.010-WP MSC Drawing

Development Unclassified Online 9 June 2022

3.35 MSC N721 Structural Analysis Minimum

Design Requirements Unclassified Online Most Current

3.36 COMSC Instruction 4700.16 – MSC General

Technical Requirements Unclassified Online Most Current

3.37 N6.16.5320.1-WP Information Technology Service Management – Change Management Procedure

Unclassified Online Most Current

3.38 MSC General Technical Requirements (GTRs)

– DWG 7081122 Unclassified MSC Virtual

Tech Library Most Current

3.39 ABS Marine Vessel Rules Part 4 – Rules for Building and Classing, Vessel Systems and Machinery

Unclassified Online Most Current

3.40 IEEE 45 Recommended Practice for Electrical Installations on Shipboard Unclassified Online Most Current

3.41 46 CFR Chapter I Subchapter J -- Electrical Engineering Unclassified Online Most Current https://cdn.ymaws.com/www.nena.org/resource/resmgr/%20Standards/NENA_08-752_v1.1_Location_fo.pdf https://cdn.ymaws.com/www.nena.org/resource/resmgr/%20Standards/NENA_08-752_v1.1_Location_fo.pdf https://cdn.ymaws.com/www.nena.org/resource/resmgr/%20Standards/NENA_08-752_v1.1_Location_fo.pdf https://dl.dod.cyber.mil/wp-content/uploads/connect/pdf/unclass-DISN_CPG.pdf https://dl.dod.cyber.mil/wp-content/uploads/connect/pdf/unclass-DISN_CPG.pdf https://dl.dod.cyber.mil/wp-content/uploads/connect/pdf/unclass-DISN_CPG.pdf

4. Requirements

4.1 Program Management Support

4.1.1 Program Management

The contractor shall provide program management (PM) services to supervise both onsite and offsite employees involved in this contract. The contractor shall provide non-GFP materials, services, personnel, direction, coordination and control needed to design, test, implement, refresh and sustain solutions required by this contract. The contractor shall adhere to industry best practices in project, program, and contract management for the MSC CivMar WiN project to enable timely and effective performance and compliance with Department of Defense (DoD), Department of Navy (DON), and MSC guidelines.

The contractor shall manage and oversee authorized activities performed by contractor personnel (including subcontractors and teaming partners) to satisfy documented MSC CivMar WiN performance requirements. The contractor shall plan, manage, and supervise work activities, ensuring effective performance support. The contractor shall escalate contract risks and issues to the Contracting Officer Representative (COR) as needed. The contractor shall identify and report personnel, cost, schedule and/or resource issues or potential issues, and provide sufficient information and recommendations to minimize the risk of non-performance.

4.1.2 Quarterly In-Progress Reviews

Due to the pace of planned installations and the need for additional coordination, the contractor shall conduct quarterly In-Progress Reviews (IPRs), unless otherwise notified by the Government. The IPRs will address the contract status and provide details regarding technical, programmatic, scheduling, capability implementation, operations, administration and contract issues.

4.1.3 Meeting Support

The contractor shall support contract management, technical, and project meetings, as well as official reviews. The meetings may be internal meetings with MSC and the contractor or external meetings with MSC, customers, stakeholders, and the contractor. The meetings may be weekly, bi-weekly, ad-hoc, plan of action and milestones (POAM) and schedule-driven reviews, or pre-scheduled conferences. The contractor shall document meeting minutes and provide to the COR and designated participants within three business days.

4.1.4 Status and Progress Reporting

The contractor shall develop and provide monthly status reporting submissions (CDRL A001, Production Order Status Report). The status report will include completed, current, and planned activities and assessment of risk to schedule, cost, and performance for the MSC CivMar WiN project. The status report will also include service support metrics such as the number of tickets received, resolved, network outages, and any active issues.

4.1.5 Contract Closeout

Contract closeout concludes with a final review and formal handover of contractually required deliverables to MSC. Final review and handover activities include:

• Final Review: Conducting a final review of authorized installation, integration, systems engineering, cybersecurity engineering, modernization, capability enablement, as well as operations and sustainment activities, validating that all contractually required tasks have been completed to the required then-current standards.

• Handover Documentation: Providing MSC with the contractor-developed and/or received relevant technical documentation, including test reports, operator manuals, and technical guides.

• Formal Handover Meeting: Holding a meeting with MSC and stakeholders to review the completed work and address any final questions or concerns.

• Support Continuation of Operations: Establishing a transition plan for ongoing sustainment support and maintenance (CDRL A013 Transition Plan), so MSC has access to necessary resources and support channels.

There will be a contract phase-out period commencing 60 days prior to the end of the contract.

The purpose of the phase-out period is to ensure a smooth transition of services and support from the predecessor contract to the successor contract. Upon notification from the Government, the contractor shall provide the services necessary to ensure a successful transition of services to the awardee under a subsequent contract for the same or similar requirement. No later than 90 days prior to the end of the contract, the contractor shall develop, with input from the Government, a plan of action to facilitate the transition of services to the incoming contractor with no degradation in services (CDRL A013 Transition Plan).

4.2 Design and Architecture Support

4.2.1 Network

The contractor shall update and maintain detailed network architecture diagrams (CDRL A002, Architecture Diagrams) and design documentation (CDRL A003, Design Documentation) for CivMar WiN. Developed architecture and designs will incorporate the latest relevant industry standards and technologies to support MSC’s development and modernization of communications networks. The contractor shall maintain and update the CivMar WiN technical baseline on an annual basis, including the detailed network designs and architecture. The contractor shall conduct design reviews with MSC stakeholders (CDRL A010, Design Reviews) in support of annual baseline updates.

4.2.2 Satellite Communications

The contractor shall update the reference and solution architecture for commercial SATCOM deployments taking into consideration authorization boundaries, operational requirements and existing infrastructure. The contractor shall develop, update, and maintain architecture diagrams (CDRL A002, Architecture Diagrams) and design documentation (CDRL A003, Design Documentation) for commercial SATCOM deployments supporting CivMar WiN. The contractor shall maintain and update the CivMar WiN technical baseline on an annual basis, including the commercial SATCOM deployment design and architecture. The contractor shall conduct design reviews with MSC stakeholders (CDRL A010, Design Reviews) in support of annual baseline updates.

4.2.3 Cloud Network

The contractor shall maintain and update cloud network architecture diagrams and design documentation (CDRL A002, Architecture Diagrams) for the currently deployed cloud architecture hosted in the Navy Enterprise Azure environment (CDRL A003, Design

Documentation). Developed architecture and designs will incorporate the latest relevant industry standards and technologies to support MSC’s development and modernization of communications networks. Cloud network design shall support the service level objectives (SLOs) and provide for centralized management of CivMar WiN installations and services on MSC ships from the Navy Enterprise environment. The contractor shall maintain and update the CivMar WiN technical baseline on an annual basis, including the detailed cloud network designs and architecture. The contractor shall conduct design reviews with MSC stakeholders (CDRL A010, Design Reviews) in support of annual baseline updates.

4.3 Systems Engineering Support

The MSC CivMar WiN contract builds upon the prototype design efforts and continues the production effort to expand the MSC prototype architecture, scale the solution across additional classes of MSC vessels and integrate the solution with DON enterprise solutions.

4.3.1 Systems Engineering

The contractor shall create a Systems Engineering Management Plan (SEMP) (CDRL A009, SEMP). The SEMP will describe the project structure, the technical processes to implement and sustain the system, the process to verify, validate, and update requirements, and the processes that will be used to conduct configuration / change management. The contractor shall develop, update and maintain functional and allocated baseline configurations as the basis for Engineering Change Management processes. The contractor shall use Digital Engineering to develop and/or modify model-based systems engineering (MBSE) models, model views and reference architectures (CDRL A035, MBSE Models). The contractor shall create and execute system and services, Test Plans (CDRL A007, Test Plans). The contractor shall deliver test results (CDRL A012, Test Results).

The contractor shall maintain and update the technical baseline on an annual basis, including requirements gathering, system architecture development, detailed technical design, site surveys, and compliance planning.

The contractor shall conduct the following engineering reviews with MSC stakeholders (CDRL A010, Design Reviews) in support of annual baseline updates:

• Preliminary Design Review (PDR)

• Critical Design Review (CDR)

• Test Readiness Review (TRR)

4.3.2 Requirements Gathering and Analysis

The contractor shall conduct requirements gathering and analysis to maintain, and/or update the system requirements traceability matrix (SRTM) baseline for CivMar WiN. The contractor shall maintain and update the CivMar WiN SRTM baseline on an annual basis. The purpose of gathering requirements is to establish and maintain the requirements baseline, facilitate continuous compliance monitoring, and make updates as new capabilities and compliance requirements are defined (CDRL A014, Technical Documentation).

4.3.3 Cybersecurity Compliance Planning

Given the critical nature of MSC operations and the stringent security requirements of the DoD, maintaining compliance with relevant standards is paramount. The contractor shall develop a

POAM to address the then-current applicable regulations and standards, including the RMF during the systems engineering phase.

Cybersecurity compliance planning activities include:

• Maintaining Compliance: Identifying relevant compliance requirements during the systems engineering phase, required to successfully complete the RMF process

• Developing POAMs: Outlining tasks, milestones, metrics, resources, and objectives to resolve open findings and implement compliance requirements on new technologies to satisfy the completion of the RMF process

• Implementing POAMs: Coordinating with MSC to put the RMF POAM tasks into action, track progress, and resolve open findings

• Managing Risk: Preparing documentation and evidence required for the RMF process to achieve ATO

4.3.4 System Architecture Development

Based on the gathered requirements, the contractor shall expand the high-level system architecture for CivMar WiN to include additional classes of MSC ships and integration with the Navy Enterprise Azure Cloud environments and integration with Navy Enterprise Flank Speed services and systems. The contractor shall update and maintain the architecture to capture the overall structure of the communications network, including core components, distribution, network segmentation, and security mechanisms. The architecture will serve as a blueprint for the detailed technical design and will enable components to work together seamlessly to meet system requirements and operational suitability.

The system architecture will include:

• A logical network diagram showing core network elements and their interconnections

• Specifications for network hardware and software components

• Security architecture, including firewalls, intrusion detection systems, and encryption

• Plans for network segmentation to isolate different user groups and services

• The latest relevant industry standards and technologies to support DoD and DON requirements for zero trust architecture (ZTA) implementation using zero trust principles and technologies such as multi-factor authentication (MFA), data loss prevention (DLP), micro-segmentation, and Identity, Credential, and Access Management (ICAM) solutions as part of the design

4.3.5 Detailed Technical Design

The contractor shall refine and expand upon the detailed technical designs to include additional classes of MSC ships and integration with the Navy Enterprise Azure Cloud environments and integration with Navy Enterprise Flank Speed services and systems. Developed network architectures and designs shall incorporate and account for operational traffic flows, data and application requirements, integration of Flank Speed Edge Azure Stack Hyperconverged Infrastructure (HCI), and logically separate the operational traffic, data and applications from the Mariner personal device traffic and data. This requires specifying the exact configurations and settings for each network component, developing custom configurations to meet specific system requirements, and ensuring that critical design elements adhere to relevant standards and best practices (CDRL A003, Design Documentation).

Detailed technical design activities include:

• Selecting and configuring routers, switches, connection and access points, and other network devices

• Designing networks to support centralized management from shore and provide robust coverage and performance on selected platforms or classes of ships

• Implementing network segmentation and VLANs to enhance security and manageability

• Developing detailed security configurations, including firewall rules, access control lists, and encryption protocols

• Limiting or throttling per device usage to allow for equitable access and bandwidth sharing The technical design will also incorporate a Service Management plan (CDRL A033, Service Management Plan) to create an agreed upon framework for meeting system service level objectives.

4.3.6 Site Surveys and Needs Assessment

To permit the system design to be tailored to the unique environment of each ship class, the contractor shall conduct comprehensive site surveys and requirements assessments (CDRL A017, Site Survey). This involves visiting ships and end-user locations to assess physical layouts and structural boundaries, existing infrastructure, and environmental and operational conditions.

The site surveys will identify any potential challenges or constraints that need to be addressed in the design.

Wireless network location coverage will be based on identified wireless access areas provided by the government and include identified crew berthing spaces, working spaces (e.g. Wheelhouse, Supply office, Electricians Workshop, etc.) and common areas (e.g., mess decks, libraries, and gyms). Additionally, some working spaces may require wired versus wireless network coverage.

Wired network locations will be based on identified wired access areas provided by the government and will be limited to working spaces. Surveys will also assess and determine the network connectivity, whether wired or wireless, required to replace the legacy MSC Shipboard Management Information System (SMIS) or Network Management System (NMS) networks and Consolidated Afloat Networks and Enterprise Services (CANES) unclassified networks.

During the site surveys, the contractor shall:

• Map out the physical network layout for each class of targeted ship, including key areas where network components will be installed, including shipboard compartments. Physical layout will identify locations of structural penetrations. Fire, water, and other ratings must be maintained per pertinent regulations

• Assess existing cabling and power infrastructure

• Identify potential sources of interference or environmental challenges for network installations and operations

• Gather detailed information on user needs and usage patterns

4.3.7 Radio Frequency Engineering and Analysis

The contractor shall create Radio Frequency (RF) Models (CDRL A004, RF Models) for each class of ship using a modeling and simulation tool to characterize the performance of wireless networks. The contractor shall validate, update, and maintain the RF models after conducting surveys per ship class.

4.3.8 Technical Reviews

The contractor shall develop presentation materials for the PDR, CDR, and TRR.

4.3.9 Documentation

The contractor shall produce or update detailed documentation to support the implementation, operation and maintenance of the network. This documentation will include technical designs, configuration guides, ship installation drawings, integrated logistics support documentation, and compliance plans, ensuring that identified stakeholders have a clear understanding of the network design and how it will be implemented. Ship installation drawings are subject to review and approval by MSC N6 and N7 prior to submission for regulatory approval by ABS and will conform to applicable standards and requirements for certification.

Documentation deliverables include:

• High-level system architecture diagrams (CDRL A002, Architecture Diagrams)

• Detailed network design documents that illustrate the overall network architecture including the cloud environment, and provide the detailed interconnections between satellite terminals, routers, switches, access points, servers, and other network and management devices (CDRL A003, Design Documentation)

• Cabling schematics that provide detailed illustrations of the cabling infrastructure, including cable types, lengths, and connection points (CDRL A014, Technical Documentation)

• Coverage maps that identify and show the coverage areas of wireless access points to provide adequate signal strength and coverage throughout the required shipboard locations (CDRL A014, Technical Documentation)

• Physical layout drawings that include floor plans and rack layouts which detail the physical placement of equipment on MSC ships and at end-user locations, including the location of wired network termination points. This includes the positioning of devices in racks, cable routing, and power supply arrangement. These detailed installation drawings must include connection methods to shipboard structure, foundation construction, and modifications to the existing ship structure (CDRL A014, Technical Documentation)

• Contract Guidance Drawings (CGDs) by ship class (CDRL A018, Drawing Packages) to specify the installation methods and requirements necessary to install the CivMar WiN system onto the designated platform(s). CGD drawings will be developed in accordance with References 3.34 through 3.41. The minimum drawings will be included in each CGD Package will include:

o Electrical Bill of Material showing part numbers, cable types, and cable lengths Block Wiring diagram showing interconnectivity and compartment designation of components One-line diagram showing cable types, lengths, circuits, phases, locations of components, protective device sizes and settings

If equipment is to be hardwired, support circuit information and locations in accordance with the above must be provided

Weights and moments calculations and data for everything installed by the drawings o Arrangement and Structural Arrangement drawings showing locations of contractor installed and removed equipment authorized under this contract.

Installation and removal drawings detailing the physical layout changes to the ship. Bulkhead and deck penetrations will indicate how structural and safety integrities will be maintained. Any mounted equipment will show foundation design and installation instructions to shipboard structure.

Identified and authorized structural modifications to the ship for equipment installation will be supported by sound engineering practices and analysis. Structural Analysis calculations will address the static and dynamic loading on the installation found within its operating environment for equipment exceeding 300 lbs. of overall weight or as deemed necessary by the designated approving engineer. Calculations may include, but are not limited to, first principles structural analyses, finite element analyses, ships motion calculations, weld and connection analyses, and vibration analyses. Analyses must address Structural Analysis Minimum Design Calculations requirements

Bill of Material for structural installations, removals, and modifications (CDRL A019, Installation Documentation)

Weights and moments calculations for everything installed by the drawings

Work items and installation cost estimates to support shipboard installation and identify any required industrial assistance

• Configuration guides (CDRL A006, Configuration Documentation) that provide step-by-step instructions for setting up and configuring CivMar WiN including:

o Device Configurations: Documenting the specific settings and parameters for each network device, including routers, switches, access points, firewalls, servers, etc. This includes IP addressing schemes, routing protocols, VLAN configurations, and security settings o Security Configurations: Providing detailed instructions for implementing security controls, such as firewalls, intrusion detection/prevention systems, access control lists, and encryption protocols. These configurations protect the network against threats and compliant with then-current security standards o Software and Firmware Updates: Documenting the procedures for updating software and firmware on network devices to run the latest, most secure versions

• Site survey reports and needs assessment findings (CDRL A017, Site Survey)

• Maintenance documentation that provides detailed information on how to maintain and support the CivMar WiN over its lifecycle (CDRL A027, Operations and Maintenance Manual). Maintenance documentation will be developed for compatibility with, and inclusion in, the MSC Shipboard Automated Maintenance Management (SAMM) system and will include:

o Detailed maintenance procedures. The contractor shall update and maintain the CivMar WiN shipboard maintenance requirements and detailed procedures for performing shipboard maintenance. Maintenance procedures shall be incorporated into SAMM, and may be performed by ship’s crew or Field Service Engineers (FSEs) o Maintenance schedules for regular maintenance activities, such as hardware inspections, software updates, security audits, and performance evaluations. The contractor shall provide proposed maintenance windows, which will be negotiated with MSC key stakeholders prior to finalization. Following determination, planned maintenance windows will be formalized and promulgated to MSC ships via Naval message by MSC key stakeholders o Backup and recovery procedures for backing up network configurations and data, as well as steps for recovering from system failures or data loss o Change management plan outlining the processes for making changes to the network, including how to assess the impact of changes, document modifications, and obtain necessary approvals

• Tailored Product Support Plan with a master list of materials, licensing and warranty information, instructions to access vendor knowledge base portals, sparing plan and inventory, preventative maintenance plan, and system update plan (CDRL A028 Product Support Plan)

• Compliance plans and RMF documentation (CDRL A034, Cybersecurity Documentation)

• System Operability Verification Test (SOVT) (CDRL A029, SOVT) The contractor shall develop a comprehensive and detailed design that addresses the then-current MSC, regulatory, and design standard requirements and sets the stage for successful implementation, operations and sustainment.

4.4 Cybersecurity Engineering Support

4.4.1 Cybersecurity Engineering and Analysis

The contractor shall provide technical, engineering, and implementation services to support the RMF process. The contractor shall maintain and comply with the following cybersecurity requirements: Security Requirements Guides (SRGs), Security Technical Implementation Guides (STIGs), Information Assurance Vulnerability Management (IAVM) as well as other security policies applicable to the overall system solution. For the current system, the contractor shall maintain logs locally and report any security incidents per DON and MSC policy/process. The contractor shall work with MSC to design and implement the future state system to provide automated log data feeds to the Navy Cybersecurity Service Provider (CSSP).

The contractor shall maintain and update the CivMar WiN technical baseline on an annual basis.

The contractor shall evaluate new devices, systems, and products for security vulnerabilities prior to inclusion in the baseline. The contractor shall follow DoD Approved Products List (APL) to the extent possible for the use of only approved devices and review any deviations where approved products are not available with the government (CDRL A003, Design Documentation) (CDRL A012, Test Results).

4.4.2 RMF Cyber Remediation

The contractor shall actively analyze and remediate vulnerabilities in accordance with United States Cyber Command (USCYBERCOM) IAVM Notices, Directives, and Orders. The contractor shall maintain ongoing visibility of updates and impacts to the system and conduct vulnerability scans weekly and real-time monitoring of systems in accordance with RMF guidelines.

4.4.3 Cybersecurity Documentation and Support

The contractor shall provide support in the compilation, evaluation, and submission of contractually required Cybersecurity authorization artifacts to include RMF (CDRL A034, Cybersecurity Documentation). The contractor shall also be responsible for providing any previously developed vendor Military Unique Deployment Guides (MUDGs) and engineering and technical services in support of cyber defense.

4.4.3.1 RMF Initiation and System Categorization

The contractor shall initiate the RMF process and system categorization. The contractor shall perform the following tasks:

• Identify and engage key stakeholders, including MSC security personnel, IT staff, and compliance officers, to facilitate their involvement throughout the RMF process.

• Define the scope of the RMF process, including the boundaries of the information system, the assets involved, and the overall objectives for risk management.

• Provide support in defining the categorization of the information system by analyzing the potential impact on confidentiality, integrity, and availability in case of a security incident, and determining the overall security categorization of the system (e.g., low, moderate, or high).

4.4.3.2 Security Controls Selection

The contractor shall select appropriate security controls that will protect the system. The contractor shall perform the following tasks:

• Identify the system baseline appropriate security controls based on the system’s categorization level.

• Tailor the selected controls to address specific MSC system threats, vulnerabilities, and organizational requirements.

• Document the selected and tailored security controls in a System Security Plan (SSP), providing a comprehensive overview of the planned security measures.

4.4.3.3 Security Controls Implementation

The contractor shall implement security controls ensuring they are effectively integrated into the network infrastructure. The contractor shall perform the following tasks:

• Deploy the selected technical, administrative, and physical security controls across the network, including encryption, access controls, and monitoring systems.

• Validate that authorized and implemented controls are properly configured and aligned with the security requirements.

• Document the implementation process, detailing how each control has been deployed and configured.

4.4.3.4 Security Control Assessment

The contractor shall assess the implementation of the security controls to verify their effectiveness and identify any weaknesses. The contractor shall perform the following tasks:

• Conduct vulnerability assessments, penetration testing, and security audits.

• Document the assessment findings, including any identified vulnerabilities and the overall security posture of the system.

• Analyze the assessment results to determine the residual risk levels and identifying areas that require further mitigation.

4.4.3.5 Authorization

The contractor shall support the government in obtaining authorization to operate the network.

The contractor shall perform the following tasks:

• Evaluate the residual risks and determine whether they are acceptable within the organizational risk tolerance.

• Provide input to support government preparation of an authorization package.

• Provide input to the SSP, assessment reports, and POAM for addressing any residual risks.

• Support presentation of the authorization package to the Authorizing Official (AO) for review and ATO decision.

4.4.3.6 Continuous Monitoring

The contractor shall maintain the security posture of the network, addressing any new risks or changes in the environment. The contractor shall perform the following tasks:

• Conduct regular assessments to monitor the effectiveness of security controls and identify any new vulnerabilities.

• Monitor the network for security incidents and breaches and respond promptly to mitigate any threats.

• Coordinate with the cyber security provider for continuous monitoring of the system.

• Verify changes to the network are assessed for security impact and that controls are updated accordingly.

• Maintain up-to-date documentation of the security posture, assessment results, and any incidents, and providing regular reports to stakeholders.

4.5 Integration and Implementation

4.5.1 Integration and Implementation Planning

The contractor shall develop and maintain an integration and implementation plan by ship class for the installation of CivMar WiN. The contractor shall conduct a site survey (CDRL A017, Site

Survey Report) and develop required drawings and integration documents (CDRL A018, Drawing Packages) for each class of ship. The contractor shall support development and submission of required integration and installation documentation such as Transportation Alteration (TRANSALT) documentation (CDRL A019, Installation Documentation).

4.5.2 Procurement and Staging

The contractor shall procure and stage equipment and software solutions in a government or contractor facility prior to deployment into operational environments. The contractor shall implement configurations and conduct pre-validation activities to verify CivMar WiN is functional prior to shipment and implementation. Staging will include CivMar WiN specific configurations, as well as functional and acceptance testing of equipment.

Procurement, configuration, assembly, pre-testing, quality assurance, and documentation are essential elements with the building and staging process. The contractor shall fulfill the additional building and staging requirements necessary for the successful deployment of CivMar WiN.

4.5.2.1 Procurement of Hardware and Software

The contractor shall procure the necessary hardware and software components as specified in the detailed technical design (CDRL A016 Procurement Plan). This involves sourcing routers, switches, wireless access points, cabling, racks, servers, network management software, security appliances, and other required components. Procurements must be Trade Agreement Act (TAA) compliant, and where applicable, leverage existing DoD/DON enterprise agreements in coordination with MSC and key stakeholders, e.g., National Aeronautics and Space Administration (NASA) Solutions for Enterprise-Wide Procurement (SEWP).

Procurement activities include:

• Identifying and selecting vendors that meet quality, reliability, and compliance standards

• Coordinating with suppliers for timely delivery of components

• Verifying that items procured under this contract meet the specifications outlined in the design documents

• Managing the procurement process to stay within authorized budget and timeline constraints

• Ensuring onboard spare and repair parts are provided at delivery

• Providing the technical documentation for items procured under this contract

4.5.2.2 Configuration and Customization

The contractor shall configure procured hardware and software components to meet the specific requirements of MSC. This involves setting up the hardware and software components according to the detailed technical designs, ensuring the contractor developed or updated configurations are optimized for performance, security, and reliability.

Configuration and customization activities include:

• Setting up routers and switches with appropriate network protocols, IP addressing schemes, and routing configurations

• Configuring wireless access points to provide robust wireless coverage, including SSID setup, channel management, and security settings

• Implementing network segmentation and VLANs as specified in the design

• Setting up firewalls, intrusion detection/prevention systems, and other security appliances with custom rules and policies

• Installing and configuring network management and monitoring tools within the cloud environment

4.5.2.3 Assembly and Integration

The contractor shall assemble and integrate approved system components into a cohesive CivMar WiN system to verify proper configuration…