HEALY STEERING CONTROL SYSTEM REPLACEMENT SOW

DEPARTMENT OF HOMELAND SECURITY

CG-SURFACE-A3

COAST GUARD CUTTER HEALY STEERING CONTROL

SYSTEM REPLACEMENT STATEMENT OF WORK

September 9, 2026

2026-SOW-HEALY-STEERING CONTROL SYSTEM-00

US Coast Guard 2703 Martin Luther King Jr Ave SE Stop 7816

Washington, DC 20593-7816

RECORD OF CHANGES

Version Revision Date

Description of Changes Person(s) Requesting Change

1. Table of Contents

2. Scope

2.1 Objective

2.2 Period & Places of Performance

2.3 Kick-off & Progress Meetings

3. Government Furnished Documents

3.1 Coast Guard Drawings

3.2 Technical Publication Manuals

3.3 Additional Reference Information

4. Requirements

4.1 Engineering Services

4.2 Existing System Baseline

4.3 Ship Check

4.4 Design Replacement Steering Control System

4.5 Factory Acceptance Test (FAT)

4.6 Removal and Installation

4.7 Dockside Acceptance Test (DAT)

4.8 Underway Testing

4.9 Cybersecurity

4.10 System and Data

4.11 Commissioning and Onboard Training

4.12 Warranty

4.13 Quality Assurance

4.14 CUI Handling Requirements

5. Contractor Personnel

5.1 Qualified Personnel

5.2 Employee Identification

5.3 Employee Conduct

5.4 Removing Employees for Misconduct or Security Reasons

6. Master Deliverables List

2. Scope

The US Coast Guard requires the existing steering control system on USCGC HEALY to be replaced with a commercially available (COTS) PLC-based design. Any replacement system must interface with existing auxiliary and navigation systems, as defined in this Statement of Work (SOW). Documentation will be provided for existing interfacing systems such as electro-hydraulic steering gear, and communications protocols with navigation systems.

All electronic components within the existing steering control system and sub-systems (e.g.

Rudder Servo Amplifier (RSA), Rudder Repeat Back (RRB), Rudder Angle Transmitter (RAT), and Steering Failure Alarm (SFA) Panel) shall be replaced with in-kind or upgraded technical solutions to retain capabilities, but vendors are not required to replicate the existing system exactly.

2.1 Objective

This Statement of Work (SOW) contains three objectives:

2.1.2 The first objective is to plan and document the design for a replacement steering control system, ensuring compatibility with the Full Follow Up Electro-hydraulics (FFU), Autopilot System, and Dynamic Positioning System (DPS).

2.1.3 The second objective is to install and successfully test a replacement steering control system that will be commercially supported for at least 10 years. Ideally, this technical solution should utilize Programmable Logic Controllers (PLCs) and must not use proprietary software.

2.1.4 The third objective is to provide cybersecurity services and documentation to ensure that the replacement steering control system’s confidentiality, integrity, and availability remains intact. The documentation of the technical solution must be sufficiently detailed to comply with CG Cybersecurity Authority to Operate (ATO).

2.2 Period & Places of Performance

The period of performance (POP) for this effort is from 1 April 2027 until 31 May 2030.

Places of performance for this SOW include any USCG or contractor facilities, and onboard USCGC HEALY in Portland, Seattle, and/or underway.

2.3 Kick-off & Progress Meetings

2.3.1 Kick-off Meeting

The Contractor shall attend a post-award Kick-off Meeting with the Contracting Officer (KO) and the Contracting Officer's Representative (COR) no later than 14 business days after contract award. The purpose of this meeting is to discuss the technical and contracting objectives of this

SOW.

2.3.2 Progress Meetings

The Contractor's Project Lead shall be available for recurring progress meetings with USCG stakeholders as needed. Meetings may take place at contractor or USCG facilities, or on any USCG platform. These meetings will be used to present deliverables, discuss progress against the IMS, exchange information, and resolve emergent technical issues. The Contractor shall provide a progress report to the COR monthly.

3. Government Furnished Documents

3.1 Coast Guard Drawings

420-WAGB 185-6 Rev D Steering Gear A & D

420-WAGB 320-552 Rev E Steering Gear Hydraulic Pump Unit Schematic Diagram

420-WAGB 320-553 Rev E Steering Gear Hydraulic Pump Unit Assembly

420-WAGB 320-554 Rev E Steering Gear Hydraulic Pump Unit Assembly Parts List

420-WAGB 410-512 Rev Y Steering Failure Alarm Assembly Installation Dwg.

420-WAGB 410-580 Rev E Polar Icebreaker DPS Cable Block Diagram DPS Network

420-WAGB 410-583 Rev A Steering Control System Block Wiring Diagram and details

420-WAGB 436-13 Rev- Steering Gear Power Failure Alarm CKT PF1 Isometric Wiring Diagram

420-WAGB 436-14 Rev A Steering Gear Power Failure Alarm CKT PF1 elementary wiring diagram

420-WAGB 561-1 Rev A Steering Cont Sys CKT LP & Failure Alarm

420-WAGB 561-2 Rev B Steering Cont Sys CKT LP & Failure Alarm

420-WAGB 561-501 Rev A General Arrangement Steering Gear Parts List

420-WAGB 561-502 Rev A General Arrangement Steering Gear

420-WAGB 320-2 Rev BC Power System One Line Diagram

3.2 Technical Publication Manuals

5121_436_A Steering Control System (Gyropilot Failure Alarm) 7.3

5130_438_A Dynamic Positioning System Volume 1 (DPS)

5131_438_A Dynamic Positioning System Volume 2 (DPS)

5217_561_A Steering Gear, Electro-Hydraulic Model 2111

5124_ 436_A Steering Control System (3-Faced Rudder)

5033B_252_A Machinery Plant Control and Monitoring System (MPCMS) CH 1- 4

5035B_252_A Machinery Plant Control and Monitoring System (MPCMS) – Volume 3

5036B_252_A MPCMS operator interface guideS9WAG-AV-SIB-030/WAGB-20 Ship Information Book (SIB) – AUX Machinery, Piping, & HVAC Systems

S9WAG-AV-SIB-020 Ship Information Book (SIB) – Propulsion Plant

S9WAG-AV-SIB-060 Ship Information Book (SIB) – Electronic Systems

3.3 Additional Reference Information

ALCOAST 224/26 Establishment of the CUI Program and Interim CUI Implementation Guidance

COMDTINST 4105.2 U.S. Coast Guard Technical Data Management (TDM) Policy

420-WAGB 252-657 MPCMS RTU/Outstation No.2

Surface Forces Logistics Center Standard Specification 0000 (SFLC Std Spec 0000), Series General Requirements

Surface Forces Logistics Center Standard Specification 3041 (SFLC Std Spec 3041), Shipboard Electrical Cable Test

Surface Forces Logistics Center Standard Specification 3042 (SFLC Std Spec 3042), Shipboard Electrical Cable Removal, Relocation, Splice, Repair, and Installation

Surface Forces Logistics Center Standard Specification 6310 (SFLC Std Spec 6310), Requirements for Preservation of Ship Structures

46 CFR Part 58 – Main and Auxilliary Machinery

46 CFR Part 111 – Electric Systems, General Requirements

46 CFR Part 113 – Communication and Alarm Systems and Equipment

International Maritime Organization (IMO) Safety of Life at Sea (SOLAS), 2004

American Bureau of Shipping (ABS)

National Institute of Standards and Technology (NIST) 800-37 Rev 2, Risk Management Framework for Information Systems and Organizations

National Institute of Standards and Technology (NIST) 800-52 Rev 2, Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations

National Institute of Standards and Technology (NIST) FIPS 140-2, Security Requirements for Cryptographic Modules

National Institute of Standards and Technology (NIST) FIPS 199, Standards for Security Categorization of Federal Information and Information Systems

National Institute of Standards and Technology (NIST) SP 800-88 (Series) Guidelines for Media Sanitization

National Institute of Standards and Technology (NIST) SP 800-171 Protecting CUI in Nonfederal Systems and Organizations

DoD Instruction 8510.01, Risk Management Framework for DoD Systems

DOD 5200.48 Controlled Unclassified Information

Homeland Security Acquisition Regulations (HSAR) 3052.204-71, Contractor Employee Access

Homeland Security Acquisition Regulations (HSAR) 3052.204-72, Safeguarding of Uncontrolled Unclassified Information

IEC 61131-3: Programming Languages (edition 4.0 - 2025)

4. Requirements

4.1 Engineering Services

4.1.1 Technical solutions for replacement steering control system must meet the design and safety requirements of 46 Code of Federal Regulations (CFR) Subparts 58, 111, and 113;

the International Maritime Organization (IMO) Safety of Life at Sea (SOLAS); and the American Bureau of Shipping (ABS).

4.2 Existing System Baseline

4.2.1 System Overview

The steering system positions the rudders through a variety of operational modes, including automated control via the INS (Inertial Navigation System) Autopilot and DPS (Dynamic Positioning System), as well as manual control via INS Electronic Manual, Backup Manual, and local Steering Gear Room (SGR) functions. It consists of two major sections: (1) electrohydraulic steering gear and (2) the steering control system.

4.2.2 Architecture

The current system is comprised of up to six (6) remote control locations, each with varying degrees of automation, with accompanying Rudder Angle Indicators (RAIs) and one (1) local control station. This serves as the interface to the hydraulics controlling two identical sets of steering gear (port and starboard).

Figure 1. CGC HEALY Steering System Architecture

4.2.3 Hydraulic Configuration

Each steering gear consists of one rudder actuator assembly, two Hydraulic Power Units (HPUs), and associated hydraulic controls. Only one HPU operates the rudder(s) at a time, with the other acting as a standby unit.

4.2.4 Operational Modes

Steering gears operate independently but in parallel to one helm order during autopilot, manual electronic, or manual analog modes. When driven by the Dynamic Positioning System (DPS), the gears may be operated independently.

4.2.5 Redundancy & Fail-Safes

4.2.5.1 The steering control system must select, from any control station, which HPU is active/standby.

4.2.5.2 Operation must not depend on the identical hydraulics set; if one HPU fails, the other must be capable of operating the system alone. Either steering gear will operate with the other out of service.

4.2.5.3 Analog backup methods are strictly required as a redundant fail-safe in the event of system failures.

4.2.6 Scope Limitations

4.2.6.1 OUT OF SCOPE

Neither the steering hydraulics nor the hydraulic control units/panels will be changed under this project.

4.2.6.2 IN SCOPE

Work is strictly limited to the electronic components within the existing steering control system, as represented in Figure 2.

Figure 2. Architecture to be Replaced

4.3 Ship Check

4.3.1 Ship Check Execution

The contractor shall perform a ship check(s) on USCGC HEALY WAGB-20 to complete the following objectives:

4.3.1.1 Validate that the existing steering system configuration aligns with the Government Furnished Documents in Section 3.0 and the baseline defined in Section 2.1.

4.3.1.2 Identify all electronic components and drawings that require replacement or updating due to obsolescence, including the components and locations highlighted in Figures 2 and 3.

4.3.1.3 Document all discrepancies found within existing drawings and technical manuals.

4.3.2 Ship Check Deliverables

Following the ship check(s), the contractor shall develop and submit the following deliverables to the COR for approval:

4.3.2.1 A ship check report that includes:

4.3.2.1.1 Photographs of all equipment and label plates inspected.

4.3.2.1.2 A brief description of tasks accomplished and equipment investigated.

4.3.2.1.3 A detailed description and sketches of any discrepancies found.

4.3.2.1.4 A formal, preliminary list of obsolete hardware and system drawings recommended for replacement or modification.

4.3.2.1.5 A list of all system safeties: alarms, devices, shutdowns.

4.3.2.2 An Integrated Master Schedule (IMS): A detailed project schedule, developed electronically, detailing all tasks, resource allocations, critical paths, and completion & milestone dates for the entire project (including Design, FAT, Rip-out & Installation, DAT, Underway Testing, and Training).

4.3.2.2.1 The IMS shall include a three (3) week review period after submission of each deliverable for USCG review and comment.

4.3.2.2.2 The IMS initial draft shall be delivered within 14 calendar days of completing final ship check, to be updated monthly thereafter.

Figure 3. Steering Control Locations to be Replaced

4.4 Design Replacement Steering Control System

4.4.1 Design Phase Requirements

The contractor shall design a steering control system utilizing commercially available, PLC-based system/components. The design process shall adhere to the following requirements:

4.4.1.1 The design must meet all safety and performance requirements outlined in 46 CFR Subparts 58, 111, and 113, IMO SOLAS, and American Bureau of Shipping (ABS) rules.

4.4.1.2 The contractor shall map all communication pathways between the replacement system and existing shipboard architecture (including MCS, DPS, and ECDIS) to ensure full compatibility and fail-safe operations.

4.4.1.3 The contractor shall conduct a reliability and failure analysis of the proposed design to ensure that the failure of one component or HPU does not disable the redundant steering capabilities.

4.4.1.4 The design must account for power loss resilience and shall not require vendor-proprietary tools for routine Coast Guard maintenance.

4.4.1.5 The contractor shall conduct a formal Design Review Meeting (conducted virtually or at a USCG-designated facility) approximately 60 days after contract award. The purpose of this meeting is to present and gain USCG approval for the system, architecture, interfaces, and other draft documents.

4.4.2 Design Phase Deliverables

To validate the design phase, the contractor shall develop and submit the following design deliverables to the COR for approval:

4.4.2.1 An Interface Control Document (ICD) documenting the technical interface requirements, pinouts, and data specifications for communication between the new steering components and existing legacy systems.

4.4.2.2 A Requirements Traceability and Verification Matrix (RTVM) mapping every SOW requirement and Coast Guard specification to the contractor’s specific hardware/software design choices. The RTVM shall be an MS Excel document and include the following fields for each component:

4.4.2.2.1 Requirement Text Verification methods (Inspection, Analysis, Demonstration, Test).

4.4.2.2.2 Reference to requirements for verification method (e.g., ABS SVR section that establishes how the requirement is to be verified).

4.4.2.2.3 Verification document (The Contractor’s document or other artifact that reports the inspection, analysis, demonstration or test that verifies the requirement).

4.4.2.2.4 Verification Result (S-Verified to meet requirement; U-Verification failed) (i.e. A SOW paragraph or ABS section that establishes how this requirement is to be verified).

4.4.2.2.5 Link to higher level requirement for decomposed requirements.

4.4.2.3 A Failure Mode Effects Analysis (FMEA) detailing potential failure points within the new PLC architecture and how the system will safely respond or transition to backup analog control.

4.4.2.4 Draft Technical Publications and Provisioning Technical Data (PTD) reflecting the new system operation, troubleshooting, and maintenance procedures.

4.4.2.5 A comprehensive System Design Presentation/Slide Package detailing the proposed steering control system architecture, physical layout, and interface details. This package shall serve as the agenda for the Design Review Meeting.

The package shall include:

4.4.2.5.1 The overall system architecture, subsystem design, and component details.

4.4.2.5.2 A review of cybersecurity design considerations within Systems, Subsystems, and Component selections.

4.4.2.5.3 A review of interfaces between subsystems and components.

4.4.2.5.4 A review of network architecture to include details of internal and external connections.

4.4.2.5.5 A review of data flows end-to-end through the system.

4.4.2.5.6 Equipment assembly drawing reviews.

4.4.2.5.7 Equipment review selections.

4.4.2.5.8 Life Cycle Supportability review of the system, including any projected obsolescence issues and expected level of repair for components within the system.

4.4.2.5.9 Summary of RTVM results.

4.4.2.5.10 Summary of FMEA results.

4.4.2.5.11 System documents list (schematics, etc.).

4.4.2.5.12 Design risks and mitigation plans.

4.4.2.5.13 Hardware to Software Mapping Review (IT Mapping).

4.4.2.6 A Design Booklet that shall:

4.4.2.6.1 Detail the overall system architecture, each subsystem design, and design of components that make up those subsystems.

4.4.2.6.2 Include a review of cybersecurity design considerations, and how cybersecurity requirements have been factored into the design of Systems, Subsystems, and Components.

4.4.2.6.3 Include a description of the sequence of Operation of the HEALY Steering Control System. The descriptions shall include a Sequential Functional Chart (SFC) in accordance with IEC 61131-3 section 2.6.

Actions, action blocks, transitions, and their included elements shall use descriptive text in lieu of Functional Block Diagram (FBD), Ladder Logic (LD), Structured Text (ST), and Instruction Lists (IL).

a. Each sequence shall identify monitored signals, interfaces with external systems, and other information relevant to the operation of HEALY’s Steering System.

b. The logic of operation shall describe the logic in HEALY’s Steering System functions and address every configuration and operating mode.

4.5 Factory Acceptance Test (FAT)

4.5.1 FAT Requirements

The contractor shall conduct a Factory Acceptance Test (FAT) at their facility prior to shipping the replacement steering control system. The FAT process shall adhere to the following requirements:

4.5.1.1 The contractor shall perform test procedures at the contractor’s facility to demonstrate that the proposed steering system meets all requirements outlined in S9WAG-AV-SIB-030/WAGB-20.

4.5.1.2 The contractor shall ensure all test equipment is properly calibrated prior to starting any test.

4.5.1.3 The contractor shall physically assemble the system and simulate shipboard interfaces, inputs, and outputs to the maximum extent possible to verify hardware and software functionality.

4.5.1.4 The test execution must specifically demonstrate all redundancy fail-over scenarios between the programmable logic controllers (PLCs), loss of power recovery, and the successful transition to analog backup control.

4.5.1.5 Notification of any inspection or test shall be made to the COR in writing at least fourteen (14) calendar days prior to performance IAW SFLC Std. Spec 0000. The USCG reserves the right to observe the FAT.

4.5.2 FAT Deliverables

To validate the FAT, the contractor shall develop and submit the following deliverables to the COR for approval:

4.5.2.1 FAT Test Plan, Test Procedures, and Test Report Template. These documents must be submitted to and approved by the USCG prior to the commencement of any testing.

4.5.2.2 A Factory Acceptance Test Report shall be submitted to the COR for review and approval following testing completion. The FAT phase will not be considered complete until this test report is approved by the USCG without any outstanding comments.

4.6 Removal and Installation

4.6.1 Removal and Installation Requirements

The contractor shall remove the existing steering control system components and install the new system in accordance with the Government-approved Removal and Installation Work Package (see 4.6.2). The contractor is responsible for all mechanical and electrical work required for the removal and installation, including but not limited to:

4.6.1.1 Removal and disposal of all obsolete electronic components, consoles, cabinets, and cabling identified in the Rip-Out drawings.

4.6.1.2 If shipboard structure requires modification, the contract shall submit a Condition Found Report (CFR) to the COR and proceed with necessary approved action(s) in accordance with SFLC Standard Specification 6310.

4.6.1.3 Running, terminating, and testing all new cabling between the steering control stations, PLCs, and existing shipboard interfaces (MPCMS, DPS, Steering Gear) in accordance with SFLC Standard Specifications 3041 and 3042.

4.6.1.4 Restoring all disturbed areas to their original condition upon completion of the installation.

4.6.1.5 Government Retention: Prior to any disposal actions, the contractor shall coordinate with the COR to identify any Government-directed Mandatory Turn In (MTI) equipment to be retained.

4.6.1.6 Disposal Compliance: The disposal of all remaining equipment shall be performed in strict accordance with all applicable USCG, DoD, federal, state, and local policies regarding electronic waste (e-waste) and hazardous materials

(HAZMAT).

4.6.1.7 Timeline: All removal, turnover, and disposal actions shall be completed in conjunction with the installation of the new steering control system prior to the start of Dockside Acceptance Testing (DAT).

4.6.2 Removal and Installation Work Package

Thirty (30) calendar days prior to beginning any removal or installation work, the contractor shall develop and submit a comprehensive Installation Work Package to the COR for approval. This package shall provide sufficient detail to define the entire rip-out, installation, and disposal from start to finish, and shall contain the following:

4.6.2.1 Rip-Out and Installation Drawings: A complete set of drawings clearly delineating:

4.6.2.1.1 All components, cables, and conduit to be removed.

4.6.2.1.2 The arrangements and installation details for all new equipment, including required maintenance envelopes.

4.6.2.1.3 All required electrical modifications.

4.6.2.2 Detailed Installation Procedures: Comprehensive plan describing entire rip-out and installation sequence, including:

4.6.2.2.1 A sequential plan for rip-out and installation procedures.

4.6.2.2.2 A list of all tools and equipment required.

4.6.2.2.3 A detailed labor breakdown, including the number and type of personnel required for each major installation event.

4.6.2.2.4 A detailed list of all new cables required for the installation, including cable type, length, termination points, and connector/pinout information for all system interfaces.

4.6.2.3 Redline Drawings: Physical and digital sets of drawings redlined with red ink to mark all physical and electrical changes, cable reroutes, and terminal terminations made during rip-out and installation. The master redlined drawing shall be delivered to the COR immediately upon completion of the physical installation.

4.6.2.4 Removal and Disposal Record: A formal log detailing all removed equipment, including part numbers and physical locations.

4.6.2.4.1 The log must explicitly categorize items that were turned over to the USCG for retention versus items that were disposed of by the contractor and include copies of all official e-waste or HAZMAT disposal/recycling certificates.

4.7 Dockside Acceptance Test (DAT)

4.7.1 DAT Requirements

The contractor shall conduct a Dockside Acceptance Test (DAT) onboard USCGC HEALY while pier-side following system installation and prior to underway testing. The DAT process shall adhere to the following requirements:

4.7.1.1 The contractor shall perform test procedures to demonstrate that the installed steering system meets all requirements outlined in S9WAG-AV-SIB- 030/WAGB-20 and interfaces correctly with shipboard systems (MCS, DPS, ECDIS).

4.7.1.2 The contractor shall ensure all test equipment is properly calibrated prior to starting any test and provide proof of calibration upon request.

4.7.1.3 The DAT shall verify the integrity of all new cabling, terminations, and network communications identified in the Installation Work Package (section 4.6) and Drawing 420-WAGB-410-580.

4.7.1.4 The contractor shall demonstrate all local and remote-control station functionalities, including all alarm points, steering mode transitions, and emergency shutdown procedures.

4.7.1.5 Notification of any inspection or test shall be made to the COR in writing at least twenty-four (24) hours prior to performance IAW SFLC Std. Spec 0000.

4.7.2 DAT Deliverables

The contractor shall develop and submit the following deliverables to the COR for review and approval:

4.7.2.1 A DAT Test Plan, Test Procedures, and Test Report Template. These documents, including a physical copy of the test procedure, shall be submitted to and approved by the USCG at least 48 hours prior to commencement of shipboard testing.

4.7.2.2 A DAT Test Report following completion of testing. The report must document all test results.

4.7.2.2.1 The DAT phase will not be considered complete until the test report is approved by the USCG without any outstanding comments or unresolved failed tests.

4.8 Underway Testing

4.8.1 Underway Test Requirements

The contractor shall conduct Underway Testing onboard USCGC HEALY to validate the final performance of the installed steering control system. The testing shall adhere to the following requirements:

4.8.1.1 The contractor shall perform test procedures to demonstrate that the steering system meets all performance requirements outlined in S9WAG-AV-SIB- 030/WAGB-20 under actual underway conditions.

4.8.1.2 The contractor shall ensure all specialized test and monitoring equipment is properly calibrated prior to getting underway.

4.8.1.3 The test must demonstrate full functionality across all steering modes, including:

4.8.1.3.1 Primary/Automated Modes:

a. DPS (Dynamic Positioning System) Interface

b. INS Autopilot

4.8.1.3.2 Manual Remote Modes

a. Inertial Navigation System (INS) Electronic Manual

4.8.1.3.3 Backup & Local Modes

a. Backup Manual

b. Steering Gear Room (SGR) Electronic Full-Follow-Up (FFU)

c. SGR Analog Full-Follow-Up (FFU)

d. SGR Non-Follow-Up (NFU)

4.8.1.4 Testing shall verify control and proper system response from all steering control locations including:

4.8.1.4.1 Main Ship Control Console (MSCC)

4.8.1.4.2 Port & Starboard Bridge Wing Stations (Secondary Conning)

4.8.1.4.3 Aloft Conning Station

4.8.1.4.4 Science Conning Station

4.8.1.4.5 Steering Gear Room (Local Control)

4.8.1.5 The contractor shall demonstrate system recovery and fail-safe transitions while the vessel is underway.

4.8.1.6 The contractor shall provide on-site technical support for the duration of the underway period to troubleshoot anomalies and witness system performance alongside USCG personnel.

4.8.1.7 Notification of any inspection or test shall be made to the COR in writing at least fourteen (14) calendar days prior to performance IAW SFLC Std. Spec 0000. The USCG reserves the right to witness Underway Testing.

4.8.2 Underway Test Deliverables

The contractor shall develop and submit the following deliverables to the COR for review and approval:

4.8.2.1 An Underway Test Plan, Test Procedures, and Test Report Template. These documents must be submitted to the COR and approved by the USCG at least 48 hours prior to the vessel getting underway.

4.8.2.2 An Underway Test Report, submitted to the COR for review and approval following completion of test.

4.8.2.2.1 The Underway Testing phase is only considered complete upon USCG approval of the final test report without any outstanding comments or unresolved system issues.

4.9 Cybersecurity

4.9.1 Cybersecurity Technical Requirements

The replacement steering control system must comply with all relevant Department of Homeland Security (DHS), Department of Defense (DoD), and USCG cybersecurity mandates. The contractor shall ensure the system’s confidentiality, integrity, and availability by adhering to the following:

4.9.1.1 Compliance Standards: The system must comply with Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs) and Security Requirements Guides (SRGs). Applicable guidance can be found at https://cyber.mil/stigs/.

4.9.1.2 RMF Strategy & System Categorization: The Risk Management Framework (RMF) [NIST SP 800–37] will be utilized as the Assessment and Authorization (A&A) strategy. The USCG will act as the lead for conducting System Categorization in accordance with NIST FIPS Publication 199 to determine the system’s Confidentiality, Integrity, and Availability (CIA) Impact Levels.

4.9.1.3 ATO Support & Mitigation: The contractor shall answer, rectify, and mitigate any controls, risks, and vulnerabilities to meet cybersecurity requirements for an Authority to Operate (ATO) approval as defined in DoDI 8510.01.

4.9.1.4 Safeguarding & HSAR Compliance: The contractor shall comply with HSAR 3052.204-71 (Contractor Employee Access), HSAR 3052.204-72 (Safeguarding of Controlled Unclassified Information), and requirements for basic safeguarding of covered contractor information systems and cyber incident reporting. See section 4.14 for detailed CUI handling requirements.

4.9.1.5 Information Sharing: The contractor shall not share CG-specific configuration, settings, or technical data with any other organization or company. Approval can only be granted by the USCG if sharing is required for successful system integration.

4.9.1.6 Technical Data Handling & Destruction: The contractor shall hold only necessary Coast Guard-owned technical material until otherwise directed by the COR. Technical data shall be returned securely via CG-approved methods within 30 calendar days. USCG sensitive technical information must be transmitted utilizing CG-approved encryption tools validated under FIPS 140-2 (or successor) and NIST 800-52. If mailed, the contractor shall use a trackable method (USPS, UPS, FedEx) and immediately provide the COR with tracking information. The contractor shall send self-certification that data destruction requirements have been met to the COR within 30 calendar days of contract termination.

4.9.1.7 Hardware/Software Updates: Any updates or changes required to existing hardware or software will be reviewed by SFLC-LREPL and SFLC-BOD, and approved by the Security Officer (SO). This shall not circumvent contractor internal Engineering Change (EC) reviews outlined in their software configuration management plan.

4.9.1.8 Cybersecurity Point of Contact (POC): The contractor shall designate a primary Cybersecurity POC (e.g., CISO or equivalent) to interface directly with the USCG cybersecurity team.

4.9.1.9 System Integrity & Access Constraints:

4.9.1.9.1 The contractor shall not assist with, nor independently attempt, altering any connections or interfaces outside the direct scope of the steering control system without prior written authorization from the COR and USCG C5ISC.

4.9.1.9.2 The contractor shall not connect any removable media to controlled systems or the control systems network enclave other than items explicitly approved on the configuration hardware/software list (e.g., portable electronic devices, flash drives, external hard drives, smartphones).

4.9.1.9.3 Vulnerability Scanning & Remediation: The contractor shall perform vulnerability scans on all applicable hardware and software using Tenable NESSUS, SCAP, or ACAS. Results will be validated by a USCG Cyber Team Scan prior to the Dockside Acceptance Test (DAT). If timelines do not permit government validation scanning prior to the DAT, the contractor shall remediate all CAT I and CAT II findings discovered during the first government-led scan.

4.9.1.9.4 Physical Port Security: The contractor shall provide Physical Port Protection. Any unused USB, Ethernet, or Serial ports on new consoles, network switches, or PLCs must be physically blocked or administratively disabled in the hardware BIOS/firmware. If disabling a port degrades operational performance, the contractor must document the constraint in a POA&M.

4.9.2 Cybersecurity Deliverables

To validate the cybersecurity posture of the system, the contractor shall develop and submit the following deliverables to the COR for approval (See Master Deliverables Table in Section 6):

4.9.2.1 Hardware and Software List: A detailed inventory matching the procured hardware and the Software Bill of Materials (SBOM) for asset and configuration management.

4.9.2.2 Vulnerability Scan Reports: Copies of all raw and summarized vulnerability scans (NESSUS, SCAP, or ACAS) conducted by the contractor.

4.9.2.3 Risk Management Framework (RMF) Data Package required for ATO process:

4.9.2.3.1 Documented STIG/SRG implementation records.

4.9.2.3.2 A Draft Disaster Recovery Plan.

4.9.2.3.3 Topological Network Diagrams.

4.9.2.3.4 Applicable Technical Manuals.

4.9.2.3.5 A list of all known Common Vulnerabilities and Exposures (CVEs) associated with the procured hardware/software.

4.9.2.3.6 A Plan of Action and Milestones (POA&M) detailing the mitigation strategy for any open vulnerabilities or physical security constraints.

4.10 System and Data

4.10.1 System and Data Technical Requirements

The contractor shall deliver a system and associated data that adhere to the following technical standards:

4.10.1.1 Hardware Requirements

4.10.1.1.1 System and equipment redundancy shall be provided, including backup equipment with the same form, fit, and function.

4.10.1.1.2 The contractor shall use redundant Rockwell Automation Programmable Logic Controllers (PLCs), or an approved equal, for system control.

4.10.1.1.3 PLCs shall have at least 40MB of user memory, organic to the processor module.

4.10.1.1.4 Enclosures for System Controllers shall include electrical protection ensuring that failure of one signal, such as an electrical short to ground or supply, will not impact other signals.

4.10.1.1.5 The system must be designed for power-loss resilience; hardware and software shall not be damaged by a loss of power and shall return to a fail-safe state upon power restoration.

4.10.1.1.6 All cabinets and consoles shall be equipped with tamper-proof locks and keys.

4.10.1.2 Software Requirements

4.10.1.2.1 PLC Software code shall be in accordance with IEC 61131-3, using Ladder Diagram (LD) or Functional Block Diagram (FBD) logic.

4.10.1.2.2 Configuration and maintenance of the system shall not require vendor-specific special hardware or software tools and/or equipment.

4.10.1.2.3 The Microsoft operating system for any ancillary computers shall be Windows 11.

4.10.1.2.4 PLCs shall have the capability to check for digitally signed firmware against digital certificates provided from the vendor.

4.10.1.3 Technical Manual Requirements

4.10.1.3.1 The Contractor shall provide technical manuals for the steering control system and each individual component

4.10.1.3.2 Technical manuals shall be delivered in Microsoft® Office Word or Microsoft® Office Excel format compatible with Microsoft® Windows 11. Commercial Off the Shelf (COTS) manuals from vendors that cannot supply manuals in the above format shall be furnished in an unlocked Portable Document Format (PDF) file.

4.10.1.3.3 The manuals shall include the right to publish and distribute as USCG Technical Publications with no royalty for the purposes of operating and maintaining the equipment supplied under this contract.

4.10.1.3.4 The technical manuals shall consist of commercial equipment manuals (including owner’s manuals and service manuals), primary OEM drawings, parts lists, and supplemental data for all installed systems and components. All manuals must contain the following:

a. System Description – Identify and describe the purpose, interconnection, and functional operation of the system and all components.

b. Component Description – Include sufficient information to identify and describe all major system components.

c. Functional Description – Discuss the control philosophy used in the system design and provide a detailed description of the controls used.

d. Operating Procedures – Identify all system operations and evolutions, which involve personnel. Detailed step-by-step operating procedures for these operations and evolutions shall be provided.

e. Maintenance Procedures – Provide a list of required and recommended preventive maintenance procedures for all items provided for installation on the ship. Each procedure listed shall identify the equipment or component requiring maintenance, the maintenance to be performed, the reference to the technical manual, and the frequency of the procedure. Detailed step-by-step procedures for maintaining the system shall be provided.

f. Emergency Procedures – Identify conditions requiring emergency operations and provide procedures to be followed in the event of their occurrence. Emergency operation is defined as an operation under conditions of system malfunction or failure such as loss of power, component failure, physical damage, or fire. Detailed step-by-step procedures for dealing with emergencies shall be provided.

g. Troubleshooting Procedures – Identify and provide detailed step-by step troubleshooting procedures for determining causes of system failure.

h. System Limitations, Precautions, Set Points – Identify all system operational limitations. State all precautions to be taken during normal operation to preclude potentially unsafe conditions. List system operation set points, which represent the normal operation of the system.

i. Parts List – The parts list and illustrated parts breakdown (IPB) shall be included in the manual. The illustrated parts breakdown shall identify component parts and the relationship to the parts list.

4.10.1.4 Provisioning Data Requirements

4.10.1.4.1 The contractor shall provide detailed Provisioning Technical Data for all end items, components, and subcomponents.

4.10.1.4.2 Data shall be sufficient to physically and electrically identify each end item and its form, fit, and function.

4.10.1.4.3 The PTD must be keyed directly to the final system drawings and Illustrated Part Breakdowns (IPBs).

4.10.2 System and Data Deliverables

To validate the system and data requirements, the contractor shall develop and submit the following to the COR for review and approval:

4.10.2.1 Provisioning Technical Data (PTD) Package: A comprehensive data package containing:

4.10.2.1.1 Engineer Data for Provisioning (EDFP): Data providing the physical and descriptive characteristics of all items for lifecycle support, including the following:

a. Physical characteristics

b. Fit, form, function of the item

c. Location

d. Sketches or photographs with descriptive characteristics

e. Government or industry specifications or standards

f. Engineering, commercial or production drawings

4.10.2.1.2 Bill of Materials (BOM): An indentured list of all components, including manufacturer, part number, part description, material, quantity, cost, and drawing piece number.

4.10.2.1.3 Recommended Spare Parts List: List of recommended spare parts for onboard repair parts (OBRP) and stock system parts. The spare parts list shall list applicable manufacturer’s maintenance tasks for each line item (both preventive and corrective).

4.10.2.1.4 Detailed Logistics Data: A detailed parts list containing, at a minimum, the following data fields for every component:

a. Logistics Control Number (LCN)

b. End Item Acronym

c. System End Item Identifier

d. Item Indenture Code

e. Item Nomenclature

f. Useable on Code

g. Unit Height

h. Unit Length

i. Unit Width

j. Unit Weight

k. Price Per Item

l. Item Quantity Per System & Subsystem

4.10.2.2 Final Technical Manuals: A complete set of technical manuals meeting all the content and format requirements specified in 4.10.1.3.

4.10.2.3 Final Drawings: A complete set of drawings showing final onboard configuration of HEALY’s steering control system to be submitted to the COR for approval.

4.10.2.4 Backup Software Copy: A backup or bootable copy of all software and configuration files required for the operation, maintenance, or system repairs of any microprocessor or PLC-based equipment.

4.10.2.5 Password Lists: A complete list of all passwords required for operation and maintenance.

4.11 Commissioning and Onboard Training

4.11.1 Commissioning and Training Requirements

Following the successful completion of Underway Testing, the contractor shall formally commission the system and provide onboard training to USCG personnel.

4.11.1.1 Commissioning. The contractor shall provide the services of a qualified field service engineer or technician to assist during initial system set-up, perform final performance adjustments, and officially commission the system for operational use. The contractor shall arrange for the attendance of any necessary Original Equipment Manufacturer (OEM) technical representatives to ensure all warranties are maintained.

4.11.1.2 Onboard Training. The contractor shall provide onboard training for USCG personnel. This training shall cover all technical, functional, operational, and maintenance aspects of the new steering control system. Training shall include procedures that USCG personnel will be responsible for completing both before and after warranty expiration. Training must cover:

4.11.1.2.1 System start-up, shutdown, and operational procedures.

4.11.1.2.2 Interpretation of all displayed data, alarms, and safety features.

4.11.1.2.3 Emergency procedures, including fail-safe transitions.

4.11.1.2.4 Preventive and corrective maintenance procedures.

4.11.1.2.5 First-level troubleshooting for common faults.

4.11.2 Commissioning and Training Deliverables

To validate commissioning and training phase, the contractor shall develop and submit for USCG approval the following deliverables:

4.11.2.1 Commissioning Report. A signed statement regarding the completion of commissioning services. The COR shall obtain a release signature from the Contractor or his representative from the field service site. The Contractor shall forward a copy of the signed release document to the COR with the commissioning report.

4.11.2.2 Training Plan. A detailed plan, submitted to the COR for review and approval prior to the training event, outlining the training curriculum, learning objectives, and evaluation criteria.

4.11.2.3 Training Materials. A complete package of all presentation slides, user guides, and technical documentation used during the training. These materials shall be provided in a format that allows for futures use by the Coast Guard without requiring and internet connection or USB media.

4.12 Warranty

If material or components in the steering system are customarily awarded in the trade by a standard commercial warranty, such warranty shall be incorporated into this Contract and thereby provided to the Government at no additional cost. Any standard commercial warranty provided shall be identical to the standard commercial warranty normally offered by the Contractor to the Contractor's most favored customer. Offerors shall attach a copy of the warranty terms with their offer. The Contractor shall provide documentation that clearly identifies and defines the warranty terms and conditions as agreed upon between the Contractor and the USCG.

4.12.1 A written report of all warranty work shall be submitted to the COR within 48 hours of completion. Note: Submission of this report via email is acceptable.

4.12.2 Warranty Service Reports shall include at a minimum the following information:

4.12.2.1 Technical Representative’s name and affiliation

4.12.2.2 Telephone and/or email contacts

4.12.2.3 Name and Hull Number of the cutter involved

4.12.2.4 Time and date of arrival and departure

4.12.2.5 Equipment model and serial number

4.12.2.6 Conditions found

4.12.2.7 Repairs required

4.12.2.8 Parts required

4.12.2.9 Parts expended

4.12.2.10 Likely cause of failure(s)

4.12.2.11 Recommendations

4.13 Quality Assurance

The contractor shall identify a Technical Supervisor to be the single point of contact for the USCG Contracting Officer's Representative (COR) for all efforts performed under this SOW.

This individual shall possess the necessary qualifications to perform the work described and be proficient in the use of all specified hardware and software. The Technical Supervisor shall have full authority to act on all matters pertaining to the performance of services under this agreement, including ensuring all contractor employees are aware of, understand, and abide by all established Coast Guard rules, regulations, and safe work practices.

4.14 CUI Handling Requirements

4.14.1 The contractor shall adhere to the following requirements regarding the retention, safeguarding, and disposition of U.S. Coast Guard (USCG) Controlled Unclassified Information (CUI):

4.14.1.1 Authorized Retention Limit: The contractor shall retain USCG-provided or contractor-generated CUI on non-federal information systems or in physical contractor facilities only for the duration explicitly necessary to fulfill the performance requirements of this contract. Unauthorized long-term storage or archiving of USCG CUI beyond the active contract performance period is strictly prohibited.

4.14.1.2 Safeguarding Standards: During the active retention period, the contractor shall continuously safeguard all CUI in strict compliance with ALCOAST 224/26 (Establishment of the CUI Program and Interim CUI Implementation Guidance), DoDI 5200.48 (Controlled Unclassified Information), and the applicable security controls specified in NIST SP 800-171 (Protecting CUI in Nonfederal Systems and Organizations).

4.14.1.3 End-of-Contract Disposition: Upon contract expiration, contract termination, task order completion, or upon the explicit written direction of the Contracting Officer (CO) or Contracting Officer’s Representative (COR), the contractor’s authorization to retain CUI terminates immediately. The contractor shall promptly and securely return all physical and electronic CUI to the USCG or sanitize and securely destroy all CUI on contractor networks, hardware, and physical files in accordance with NIST SP 800-88 (Series) (Guidelines for Media Sanitization).

4.14.1.4 Certification of Destruction: If destruction is directed by the CO or COR, the contractor shall submit a formal, written Certification of Destruction to the CO/COR within 45 days of contract completion. This certification must affirm that all USCG CUI has been completely and permanently purged from contractor systems and that no copies have been retained.

4.14.1.5 Subcontractor Flow-Down: The contractor shall ensure that these retention and disposition requirements flow down to all subcontracts that involve access to, or retention of, USCG CUI.

4.14.1.6 Transfer of CUI material will be via digitally encrypted means to and from the government.

5. Contractor Personnel

5.1 Qualified Personnel

The contractor shall provide qualified personnel to perform all requirements specified in this SOW.

5.2 Employee Identification

Contractor personnel visiting Government facilities shall wear an identification badge that, at a minimum, displays the Contractor name, the personnel’s photo, name, clearance-level and badge expiration date. Visiting Contractor personnel shall comply with all Government escort rules and requirements. All Contractor personnel shall identify themselves as Contractors when their status is not readily apparent and always display all identification and visitor badges in plain view above the waist.

5.3 Employee Conduct

Contractor’s personnel shall comply with all applicable Government regulations, policies and procedures (e.g., fire, safety, sanitation, environmental protection, security, “off limits” areas, wearing of parts of DHS uniforms, and possession of weapons) when visiting or working at Government facilities. The Contractor shall ensure Contractor personnel present a professional appearance at all times and that their conduct shall not reflect discredit on the United States or the Department of Homeland Security. The Project Manager shall ensure Contractor personnel understand and abide by Department of Homeland Security established rules, regulations and policies concerning safety and security.

5.4 Removing Employees for Misconduct or Security Reasons

The Government may, at its sole discretion (via the Contracting Officer), direct the Contractor to remove any Contractor personnel from DHS facilities for misconduct or security reasons. Removal does not relieve the Contractor of the responsibility to continue providing the services required under the contract. The Contracting Officer will provide the Contractor with a written explanation to support any request to remove personnel.

6. Master Deliverables List

Deliverable # SOW Ref Deliverable/Event Due Date/Frequency Distribution

1 2.3.1 Kick-off Meeting Within 14 business days of contract award COR, Contracting

Officer

2 2.3.2 Progress Meetings As needed, coordinated with COR

3 4.3.2.1 Ship Check Report Within 14 calendar days of completing final ship check

4 4.3.2.2 Integrated Master Schedule (IMS)

Draft within 14 calendar days of completing final ship check; updated monthly thereafter

5 4.4.2.1 Interface Control Document (ICD)

45 calendar days after contract award

6 4.4.2.2

Requirements Traceability and

Verification Matrix (RVTM)

Draft within 45 calendar days after contract award, with ICD; Final updated prior to DAT

7 4.4.2.3 Failure Mode

Effects Analysis

(FMEA)

60 calendar days after contract award

8 4.4.2.4

Draft Technical Publications and

Provisioning Technical Data

(PTD)

14 calendar days prior to formal design review

9 4.4.2.5 System Design

Presentation Package

14 calendar days prior to formal design review

10 4.4.2.6 Design Booklet 14 calendar days prior to formal design review

11 4.5.2.1

Factory Acceptance Test Plan, Procedures, and Report Template

30 calendar days prior to scheduled FAT

12 4.5.2.2 Factory

Acceptance Test Report

Within 14 calendar days of completing FAT

13 4.6.2.1 Rip-Out and Installation Drawings

30 days prior to starting onboard work

14 4.6.2.2 Detailed

Installation Procedures

30 days prior to starting onboard work

15 4.6.2.3 Redline Drawings Immediately upon completion of installation

16 4.6.2.4 Removal and

Disposal Record

Within 14 calendar days of completing physical rip-out and installation

17 4.7.2.1

Dockside Acceptance Test Plan, Procedures, and Report Template

14 calendar days prior to scheduled DAT

18 4.7.2.2 Dockside

Acceptance Test Report

Within 14 calendar days of completing DAT

19 4.8.2.1

Underway Test Plan, Procedures, and Report Template

14 calendar days prior to sea trials

20 4.8.2.2 Underway Test

Report Within 7 calendar days of test completion

21 4.9.2.1 Hardware and Software List

30 days after completion of final shipcheck

22 4.9.2.2 Vulnerability Scan

Reports Submitted with FAT and

DAT Test Reports

23…