RFI CG47 ISC Information 020425.pdf

CG 47 ISC RFI Attachment

CG 47 Integrated Ship Control System

1. Background

a. The Cyber secure Hull, Mechanical, & Electrical (HM&E) Control Systems & Networks

Department (NSWCPD Department 50) supports US Navy HM&E Controls, Navigation, Casualty Control, Conditioned-Based Maintenance, and Network Systems on all US Navy

Surface Combatant, Amphibious, and Aircraft Carrier ships.

b. This RFI is for engineering and technical services required to perform development, modernization, deployment and life cycle maintenance for the CG 47 Class Integrated Ship

Control (ISC) System. For the purposes of this RFI, ISC includes

i. Machinery Control System (MCS)

ii. Ship Control System (SCS)

iii. Local Area Network (LAN)

c. The work to be performed includes all activities to completely provide for Life-cycle

Maintenance of the ISC project. The contractor provides a full spectrum of ISC engineering and programmatic activities related to being the Navy’s surrogate for ISC In-Service

Engineering Agent (ISEA) and Software Support Agent (SSA). Activities to be performed include but are not limited to: fleet engineering support, system design, requirements management, maintenance, configuration management, engineering change development, integrated logistics support, System verification and validation, obsolescence management, computer program development, Risk Management Framework (RMF) Support, image development, system administration of the laptop, equipment tracking and installation.

Tasks include but are not limited to performing systems engineering analysis in order to interface systems with the ISC; troubleshooting hardware issues with interfaced systems at

ISEA sites in Philadelphia or at system OEM sites; sustainment and fleet modernization efforts around the world; upgrading the cyber security features of the existing and future systems; Supporting the RMF process; and addressing obsolete hardware with the most cost effective solutions possible.

d. ISC is currently operational on the following active ships:

i. CG58 USS Philippine Sea

ii. CG59 USS Princeton

iii. CG60 USS Normandy

iv. CG62 USS Robert Smalls

v. CG64 USS Gettysburg

vi. CG70 USS Lake Erie

vii. CG71 USS Cape St. George

e. Systems Overview - Machinery Control System (MCS)

The CG-47 Machinery Control System (MCS) program oversees In-Service Engineering Agent

(ISEA) and Software Support Agent (SSA) activities for the control systems installed on the

Navy’s Ticonderoga-class hulls. Key responsibilities for managing this program include creating and maintaining comprehensive system documentation, managing system requirements effectively, upgrading the hardware and software components of the system, and conducting essential program management functions. Additionally, the program emphasizes continuous risk management and ensures system safety and cybersecurity compliance.

The program also focuses on maintaining critical support infrastructure, performing thorough system verification and validation, and providing ongoing fleet support to include integrated logistics support and obsolescence management. Configuration control of both system hardware and software is crucial, along with collaborating with an integrated product team to ensure seamless operation of system interfaces. The program includes delivering end-user training and support during the operational phase of the system’s lifecycle. Finally, the MCS program historically served as the system integrator for the ISC program.

i. MCS In-Service Hardware Configuration:

1. For the purposes of this RFI, only one shipboard hardware configuration is currently in active service for the CG-47 MCS program:

2. Ship-Set (SS) 20 Equipment – This configuration exists on eight in-service hulls: CG-58, CG-59, CG-60, CG-62, CG-64, CG-65, CG-70 & CG-

71. A ship-set consists of 19 data acquisition units (DAU), 22 Operator

Station Units (OSU), & 6 relay enclosures. See Figure 1 for MCS Block

Diagram. (Figure 1 does not show the relay enclosures or four of the

Type 4 DAUs)

a. The DAUs meet Versa-Module Eurocard (VME) hardware standards. The DAUs can be further broken down into different types. Most of the ship-set consists of Type 1 DAUs. There are three Type 3 DAUs, and four Type 4 DAUs. Type 3 DAUs provide remote monitoring and control of the shipboard Gas Turbine

Generators. Type 4 DAUs provide remote and local monitoring and control of the Gas Turbine Modules. The Type 4 DAUs are not VME. Instead, they use Micro Net hardware and they operate on GAP code.

b. The OSUs consist of 15 Reduced Sized Operating Systems

(RSOS), 5 Standard Operator Station Units (SOSU), 1 EOOW desk station, and 1 station in the CO’s cabin. The computer hardware was provided by Hexagon and includes their NEMA and rack mount offerings.

ii. In-Service Software Configurations:

1. Currently, there are eight active Integrated Ship Controls (ISC) software versions deployed across the fleet. Key configuration items include

a. Operator Station Units (OSUs) which have a Windows operating systems (Win XP-Windows 10). The primary application on the

OSUs is the Human Machine Interface (HMI) which operates on

Wonderware software.

b. Type 1 & Type 3 Data Acquisition Units (DAU) software utilizes

ADA code.

c. Type 4 DAU software utilizes Woodward GAP block code.

Final estimates for core software include 1,127,361 source lines of

ADA code, a 140 MB Human-Machine Interface (HMI) file, and a

1.99 MB ECU GAP file.

Figure 1 - ISC MCS Block Diagram

f. System Overview - Ship Control System (SCS)

i. The CG 47 SCS provides the operator remote steering and propulsion control from the bridge and other operator locations through the interfacing with the steering gear and propulsion control systems. Additional stations provide operators with status information that allows the crew to maintain a high level of situational awareness over steering and propulsion functions. The CG 47 SCS system is a safety critical system since failures can result in loss of life or loss of ship.

ii. The CG 47 Class SCS project consists of a suite of equipment that includes the

Electronic Chart Display & Information System - Navy (ECDIS-N) functionality and Serial Track Steering Interface (STSI). The CG 47 Class SCS includes the

Voyage Management System (VMS), VMS Network Switch Configuration Files, Vector Data Update (VDU), Ship Control Console (SCC), and Bridge Wing Display

Unit (BWDU) system.

iii. The control consoles consist of a Helm and Lee Helm station located in the

Ship Control Console (SCC) in the Pilot House as well as Port and Starboard

Aft Steering Stations. The software, provided by Northrop Grumman Marine

Service (NGMS), provides the Helmsman with an interface with which to control the direction and thrust of the ship. See Figures 2-4 for SCS Block

Diagrams.

iv. Software is provided from the following groups:

1. Voyage Management System (VMS) software provided by Northrop

Grumman Corporation (NGC) displays electronic navigation charts.

2. Steering software provided by NGC allows steering and propulsion orders.

3. Vector Data Update (VDU) utility software provided by NGC loads and updates Digital Nautical Charts (DNCs).

4. Bridge Wing Display Unit (BWDU) system software & hardware developed by Aeronautical & General Instruments (AGI) and provided by Quality Performance Inc. for CG 47 Class hulls. The system displays navigation, steering and propulsion data for increased situational awareness.

5. The Operating System Image is provided by NSWCPD Code 526

Figure 2 - CG IBS SS 9 System Block Diagram

Figure 3 - CG IBS SS-18 System Block Diagram

Figure 4-CG 47 IBS Bridge Wing Display Unit System Block Diagram

g. System Overview - Local Area Network (LAN)

i. The ISC system relies on the CG ISC Networks to provide real-time control data distribution among the connected sub-systems. The ISC Networks provide data communications paths for MCS, SCS, Onboard Trainer, and Condition-Based

Monitoring System. The system itself is focused on the requirements of distributed real-time control and monitoring systems, with the associated and required fault tolerance and survivability. See Figures 5-6 for LAN Block

Diagram.

ii. The Hardware configuration for the CG ISC Networks are divided into the following areas:

1. Build one (1G ISC LAN):

a. Primary LAN

i. Four (4) Core Siemens/RuggedCom RSG2200s

1. One (1) in each LAN rack

ii. Eight (8) Edge Siemens/RuggedCom RSG2100s

1. Two (2) in each LAN rack

iii. Network Management Station (NMS)

1. One (1) Hexagon Federal Rack mounted computer and Keyboard/Video/Mouse (KVM)

b. Fiber Optic Cable Plant (FOCP)

i. Singlemode Fiber Optic Cables – Network switch to switch connections

ii. Multi-Mode Fiber Optic Cables – Network switch to end-user connections

c. Back-Up LAN

i. Three (3) Siemens/RuggedCom RSG2100s

2. Build two (2G ISC LAN):

a. Primary LAN

i. Four (4) Siemens/RuggedCom MX5000REs

ii. Network Management Station (NMS)

1. One (1) Rugged Science Operator Interface Panel (OIP)

b. Fiber Optic Cable Plant (FOCP)

i. Singlemode Fiber Optic Cables – Network switch to switch connections

ii. Multi-Mode Fiber Optic Cables – Network switch to end-user connections

c. Back-UP LAN

i. Three (3) Siemens/RuggedCom RSG2100s

iii. The software configurations are broken up in two (2) categories; 1G ISC LAN and

2G ISC LAN. Both network categories include the Primary network, ISC LAN, and the Standby network, Propulsion Back-Up LAN (BUL) as well as the Network

Management Station (NMS).

a. Build one (1G ISC LAN):

i. RSG2200 and RSG2100 Rugged Operating System (ROS) (Primary)

ii. RSG2100 Rugged Operating System (ROS) (BUL)

iii. NMS software v2.6.x and Adaptation Data (AD) kit 2.6.0.x

iv. Network switch configuration files

b. Build two (2G ISC LAN):

i. MX5000RE Rugged Operating System on Linux (ROX)

ii. RSG2100 Rugged Operating System (ROS) (BUL)

iii. NMS software v2.7.x and Adaptation Data (AD) kit 2.7.0.x

iv. Network switch configuration files

c. Active CG47 Class Integrated Ship Controls (ISC) Ships

i. 1G ISC LAN:

1. CG58 USS Philippine Sea

2. CG59 USS Princeton

3. CG60 USS Normandy

4. CG62 USS Robert Smalls

5. CG64 USS Gettysburg

ii. 2G ISC LAN:

1. CG70 USS Lake Erie

2. CG71 USS Cape St. George

Figure 5 - 1G ISC LAN Block Diagram

Figure 6 – 2G ISC LAN Block Diagram

h. Lab Equipment - Machinery Control System

i. The CG-47 MCS program also maintains essential hardware and software support infrastructure at the Philadelphia Land Based Engineering Site (LBES).

This includes SS8, SS9 and SS20 hardware, comprehensive software covering the entire history of the ISC program, Programmable Logic Controllers (PLCs), various DAU test racks, Software Support Agent (SSA) laptops, multiple HMI development stations, Visual SourceSafe software, and extensive documentation housed on the Code 515 Development Network Server (DNS).

LBES equipment is used to verify and validate software development efforts before final delivery to the fleet. Additional details are contained in the MCS

Software Development Plan (SDP). The LBES hardware specifically consists of the following equipment some of which must be maintained at LBES:

1. Required to remain at LBES

a. 3 SS8 Triple Set SOSUs

b. 1 SS20 MCS Rack

c. 6 SS20 DAUs (Type 1)

d. 3 SS20 DAUs (Type 3)

e. 2 SS20 DAUs (Type 4)

f. 4 SS20 RSOSs

g. 2 SS20 SOSU Pedestals

2. To be transferred to vendor site.

a. 11 SOSU rack mount computers (Various Configurations)

b. 2 PLC racks

c. 10 DAU Unit Test Chassis

d. 10 Legacy development desktops

e. 2SS8 DAUs (Type 4)

f. 4 SS8 DAUs (Types 1 & 2)

g. 3 SS8 DAUs (Type 3)

h. 5 SS8 RSOSs

i. 1 SS9 MCS/IBS Rack

j. 1 SS9 MCS Rack

k. 3 SS9 SOSU Pedestals

l. 4 SS9 RSOSs

m. 2 SS20 RSOSs

n. 1 SS20 SOSU Pedestals

i. Lab Equipment - Ship Control System

i. SS1-8 Racks & SS9-17 Rack

ii. Helm & Lee Helm Console

iii. SCIO & HCIO Boards

1. The SCIO and HCIO boards send digital signals to the different components on the ship control systems. It controls things like sonalert and the throttle control and indicator panel.

iv. APC Rack

v. Buffalo Computer Graphics (BCG) Simulator Desk

vi. BCG Computer runs simulation software for VMS

vii. BCG Radar Simulator Program

1. Simulates Radar Video and Automatic Identification System (AIS) Data

viii. Radar Wall

j. Lab Equipment - Local Area Network

i. The CG-47 ISC LAN system maintains essential hardware and software support infrastructure at the Philadelphia Land Based Engineering Site (LBES). These include SS8, SS9 and SS20 hardware and comprehensive software covering the entire history of the ISC program. The LBES network hardware specifically consists of the following equipment:

1. Four (4) RSG2200s (SS9/20, 1G)

2. 12 RSG2100s (SS9/20, 1G)

3. Two RSG2100s (1G & 2G BUL)

4. Four (4) MX5000s (2G)

5. Rack-mounted NMS computer (SS9/20, 1G)

6. NMS OIP (2G)

7. APCON Intellipatch 3000 (non-shipboard equipment)

8. Four (4) RSG2200s (SS8, 1G, all ships decommed)

9. 8 RSG2100s (SS8, 1G, all ships decommed)

ii. Equipment that can be used as lab assets in contractor’s facility

1. SS8 1G ISC LAN which consists of four (4) RSG2200s and eight (8)

RSG2100s network switches. These can be repurposed to support activeSS9/20 1G ISC LAN.

2. There are two full 2G ISC LAN shipsets at the NSWCPD warehouse. One shipset can be repurposed and used as lab assets to support active ships.

2. Requirements

a. The contractor shall provide all In-Service Engineering Agent (ISEA) and Software

Support Agent (SSA) activities necessary for Life-Cycle Maintenance of the ISC. The following sections includes tasking that will be applied to and scaled as necessary for the

ISC program.

b. As ISEA the contractor shall be responsible for full spectrum of ISC engineering and logistic support for the operation, repair and maintenance of related fleet assets and resolution of fleet emergent problems. In-Service Engineering Agent Activities to be performed include:

i. Fleet Engineering Support

1. Provide remote and on-site (shipboard) troubleshooting and root cause analysis support for ISC.

2. Work with the obsolescence team in support of material CASREP and execute harvesting from decom ships, testing and shipment of material.

3. Perform troubleshooting on ISC equipment such as computer hardware, computer operating systems, and computer peripherals.

4. Assistance with identifying drawing discrepancies, NIIN/NSN discrepancies, configuration issues, equipment deficiencies, and special or operational interference.

5. Offer both distance and on-site support to the fleet for CASREPs and 2-

KILO requests related to the CG-47 ISC, ensuring timely resolution of issues.

a. Prepare and submit documentation, such as Technical

Assistance Visit Request (TAVR) reports, to provide stakeholders with a comprehensive overview of how CASREPs or 2-KILO requests were addressed by CG-47 ISC personnel.

6. Develop integrated test plans for all software and hardware system developments, including electric plant testing, integrated bridge system testing, and network testing, ensuring comprehensive validation.

7. Conduct AP2 and AP3 assessments upon request from a hull’s port engineer, providing detailed evaluations to support system readiness and performance.

ii. Review and respond to Fleet Inquiries and Casualty Reports (CASREPs)

iii. System Problem Tracking

1. Implement and track test ISC failures, issues and possible improvements in a System Problem/Improvement Report (SPIR) database.

2. Work with NSWCPD Corona to track failure rates and provide recommendations as necessary.

iv. Requirements Management

1. Maintain requirements for ISC.

2. Develop new requirements as necessary.

3. Review requirements solicitation forms provided by system stakeholders in accordance with procedures detailed in the various program plans. Reviewing the suggested changes for quality impacts to the system.

4. Oversee and update the system’s Hardware Requirements Specification

(HRS), Software Requirements Specification (SRS), and Interface

Requirements Specification (IRS) documents, ensuring accuracy and completeness.

v. System Design

1. Develop technical designs for future changes to the ISC.

2. Troubleshoot problems on deployed operational systems and provide design solutions as necessary.

3. For design changes review of technical documentation related to all variants of deployed systems and systems.

4. Follow the Peer Review Process outlined in the SEP documentation to ensure all work products meet established standards.

5. Develop and maintain peer review workbooks for all work products that require mandatory peer reviews, ensuring thorough documentation and tracking of the review process.

6. Development of Ship Change Documents (SCD), Engineering Change

Requests (ECR), Design Decision Memorandums (DDM), Problem

Reports (PR), Change Requests (CR) and Alteration Work Instruction

(AWI) for ship system alterations including review of technical documentation, procedure development and implementation, as well as equipment and parts procurement assistance for planned modernization projects.

vi. Maintenance Support

1. Development of Ship Change Documents (SCD), Engineering Change

Requests (ECR), Design Decision Memorandums (DDM), Problem

Reports (PR), Change Requests (CR) and Alteration Work Instruction

(AWI) for ship system alterations including review of technical documentation, procedure development and implementation, as well as equipment and parts procurement assistance for planned modernization projects.

2. Troubleshoot hardware issues with interfaced systems at ISEA sites in

Philadelphia or at system OEM sites.

3. Develop, update and review logistical documentation associated with

ISC equipment.

vii. Engineering Changes (System Improvements and New Functionality)

1. Utilize the “Entitled Process” for creating and approving Ship Change Documents (SCDs) in Navy Data Environment (NDE), and the “Fleet Modernization Process” for accomplishing all changes, modifications, and alterations to ships and equipment in the Fleet through the portal located at https://www.nde.navy.mil/.

2. Develop and maintain tracking sheets for various types of work products, including test equipment tracking, purchase order tracking, test procedure tracking, failed asset tracking, and equipment calibration tracking.

viii. Configuration Management (CM)

1. Maintain configuration control of documentation and software updates from vendors and other technical departments and provide analysis of any potential impacts that updates would have on ISC

2. Establish configuration control practices, implement and maintain proper configuration management of equipment, software, and documentation.

a. Collaborate with NSWCPD Program Office to maintain and update the configuration management of CG-47 ISC hardware.

https://www.nde.navy.mil/

3. Implement configuration version control practices and processes

(checkout/check-in, version number control, system/software baselines, merge, build, testing, and release) to software, hardware, requirements, firmware, images, technical manuals, test procedures, and support documentation.

4. Provide configuration version control using locally established forms, templates, databases, and applications (Visual Source Safe (VSS), GIT, Telelogic DOORS, Atlassian, SharePoint, Excel, Word, Access, and

Project).

5. Perform virus scanning and software diffs for all media delivered to ships, ensuring that all software is secure and the correct version is being delivered.

6. Generate and apply labels for shipboard media deliveries in accordance with the CMP requirements.

7. Participate in CCB meetings as necessary to gain approval for changes to CG-47 ISC hardware or software baselines.

8. Regularly back up all technical, program, and business information that supports the CG-47 MCS program, ensuring data integrity and availability.

9. Provide metric information for the purposes of improvement and enhancement of performance and maintenance efforts.

ix. Integrated Logistics Support, Tech Manuals, Documentation, Training

1. Assist Code 311 with updating logistics products, including Allowance

Parts Lists (APL), National Stock Numbers (NSN), and ILS certs ensuring accuracy and alignment with current system configurations.

2. Conduct reviews of system drawings and submit Liaison Action

Requests (LARs) to the Planning Yard as required for necessary revisions.

3. Develop and generate inventory reports on OM&S (Operating Material and Supplies) inventory levels.

4. Provide support in accessing planning yard ILS repositories.

5. Maintain inventory of incoming and outgoing material and assets.

6. Offer comprehensive support for requisitions, including the management of storage, packaging, staging, shipping, and handling for replacement parts requested by system operators.

a. Verify and update firmware on VME 5532S Repeater Cards using the Quartus software programming tool as part of the fleet requisition process.

7. Operator and Maintainer System Training Support

a. Assist with development of course materials, auditing on going courses and providing input into curriculum development.

b. Provide support to the CG-47 Smart Ship San Diego schoolhouse and the Great Lakes training schoolhouse, assisting with training needs and resource availability.

c. Provide On-The-Job Training (OJT) for Ship’s force and Regional

Maintenance Center (RMC) personnel.

i. Deliver specialized training to sailors on the operation and administration of the ISC system aboard ships, ensuring they are equipped to manage and restore the system software.

ii. Provide hands-on training for sailors on the operation of the ISC system aboard ships, focusing on system functionality, troubleshooting, and maintenance of the system’s hardware.

8. Provide updates to related Planned Maintenance System (PMS) Card as necessary.

9. Provide updates to related Engineering Operational Sequencing System

(EOSS) as necessary.

10. Perform regular assessments of CG-47 MCS reliability, availability, and maintainability as part of the system’s overall readiness evaluations.

x. Installation Guidance

1. Provide shipboard installation, troubleshooting, and test assessment plans, routine status, metrics, and final trip reports.

2. Provide support for facilitating, preparing and tracking the shipment of items to and from the waterfront.

3. Provide installation support for various cable types, connector types, computer systems, and wiring harnesses.

xi. System Verification and Validation

1. Develop and maintain software and equipment installation, equipment checkout, system troubleshooting and system assessment work products. The work products shall include the following: operational and endurance parameters, testing procedures, test plans, maintenance procedures, installation procedures, operational procedures, equipment installation drawings, equipment installation requirements, equipment removal packages, troubleshooting plans, troubleshooting guides, and pass/fail criteria.

2. Develop test procedures to exercise requirements of fielded systems and future fielded systems.

3. Conduct ISC test procedures during lab and shipboard test evolutions.

xii. Obsolescence Management

1. Develop ISC obsolescence plans from identification to solution.

2. Assist in managing the business and engineering obsolescence concerns of various stakeholders.

3. Develop obsolescence solutions to problems with regard to balancing cost, need date, integration into existing systems, conflicting stakeholder desires, and other factors.

4. Develop technical plans and solutions for ISC obsolescence problems.

Update and maintain plan as project progresses.

5. Identify obsolescence issues through proactive expert knowledge of the systems situations by working with other groups and departments, and by using available data and reports.

6. Manage asset recovery efforts in collaboration with Code 311 through the Equipment Recovery System (ERS), facilitating the harvesting of obsolete equipment from decommissioned ships.

7. Provide detailed and timely responses to remedy tickets related to the

CG-47 ISC, ensuring efficient resolution of issues.

8. Research and assess form, fit, and function (F/F/F) replacements for obsolete CG-47 ISC equipment, ensuring compatibility and system functionality.

9. Assist NAVSUP by diagnosing and repairing Digital Vibration Interface

(DVI) boxes, including identifying, configuring, and replacing faulty XM-

123 modules.

c. As the SSA the contractor shall have overall responsibility for the ISC software components. SSA objectives include:

i. Accomplish tasks necessary to ensure that fielded software continues to fully support its operational mission.

ii. Maintain Software Configuration Management integrity.

iii. Manage/execute Software Development Life-Cycle -Software requirements, design, development, test and ship installation.

d. As SSA the contractor shall perform the following tasks as necessary for ISC:

i. Maintain organization framework, processes and resources to support software.

ii. Perform software code change designs and modifications.

iii. Perform Configuration Management Activities (see CM activities above).

iv. Manage software requirements, design, interfaces and system integration.

v. Supply/Install/Support tactical ISC software to the fleet.

vi. Review shipboard SCDs for Software Impact.

vii. Duplicate, troubleshoot & resolve software problems.

viii. Provide technical support to ILS elements affected by software changes.

ix. Develop software enhancements and system functionality improvements.

x. Track Software Issues and Potential Improvements.

xi. Test software configuration changes and modifications prior to shipboard installation & test.

xii. Develop software unit tests in order to demonstrate that the modified computer programs satisfy the requirements.

xiii. Investigate reported system software problems under controlled conditions.

xiv. Integrate new software with new hardware ensuring compatibility.

xv. Manage and ensure System Software Safety.

1. Regularly update and manage the CG-47 ISC System Safety Project Plan to ensure it aligns with safety requirements and program objectives.

2. Continuously monitor the CG-47 ISC program for potential safety risks by utilizing Hazard Analysis Reports (HAR) in accordance with

NAVSEAINST 5100.12B.

3. Maintain and regularly update the CG-47 System Hazard Analysis matrix to track and mitigate safety hazards effectively.

4. Receive approval from the SEP (PfS) prior to conducting milestone audits to ensure compliance with safety and security standards.

xvi. Perform Verification and Validation of software changes.

xvii. Develop and/or modify computer image based on program additions / removal

/ modification and cybersecurity or operating system updates.

e. The contractor shall provide Cybersecurity (e.g. ATO, OS Patches, SW hardening)

Support for the ISC, Tasks include:

i. Maintain ISC Authority To Operate (ATO) in accordance with the Risk

Management Framework (RMF)

ii. Regularly update and manage the CG-47 ISC Pre-Installation Check-Out (PICO) plans to ensure it reflects the latest requirements and procedures.

iii. Cybersecurity posture sustainment tasks related to new and existing ISC software, and hardware. The tasking will be in relation to Risk Management

Framework (RMF) packages and cyber posture maintenance of the afloat and land-based test environment. .

iv. Development of RMF deliverables, testing, equipment scanning, answering cybersecurity controls, validation and applying cybersecurity controls to equipment contained in RMF packages.

f. The contractor shall conduct Planning and Program Management Activities

i. Tracking program spend rates and burn curves.

ii. Developing briefs and program documents.

iii. Participate in technical meetings and program reviews to provide action-item-tracking support and to draft meeting minutes.

iv. Develop Plan of Actions and Milestones (POA&Ms) for initiatives and provide status on the progress of those milestones.

v. Manage project efforts in support of an Integrated Master Schedule, as required.

vi. Generate project plans, concepts of operation, and management outlines.

vii. Develop and present technical presentations and information to various entities such as peers, shipboard installation managers, ship’s force representatives, and program sponsors.

viii. Develop and maintain tracking sheets for various types of work products, including test equipment tracking, purchase order tracking, test procedure tracking, failed asset tracking, and equipment calibration tracking.

ix. Support work outside normal duty hours, as required, in order to accomplish tasking listed throughout this section.

x. Provide administrative support for contracted employees who are travelling to remote locations. This includes submitting any access requests, Joint Personnel

Adjudication System (JPAS) requests, country clearance requests, and other paperwork required for travel to the specific location.

xi. The contractor shall provide administrative services and support assistance, to include facilitation of media destruction; coordination/planning for meetings and conferences; developing and formatting reports in accordance with Navy policies, regulations, and instructions; preparation and submittal of contractor monthly status, incurred cost, and burn rate analysis reports in addition to monthly invoices.

xii. Prepare formal technical presentations and technical documentation. The contractor shall assist with the development, maintenance, modification and generation (e.g., printing) of documentation including technical posters, brochures, presentation materials, web-based documentation, and manuals.

xiii. Develop/Maintain System Development Plans/Project System Development

Plans.

xiv. Use a Work Breakdown Structure (WBS) to determine the necessary labor resources for project development and support, ensuring resource allocation meets project goals.

xv. Prepare and submit TPS to the NSWCPD CG 47 Program Manager, detailing WBS tasks, required resources, and associated costs for each line item.

g. Development and Test Facility

i. At the contractor site, the contractor shall establish a ISC development and test facility.

1. The site should be physical and cyber secure, it also shall maintain an

ATO Ashore package supporting laboratory equipment for all equipment.

ii. NSWCPD will transfer current assets at the NSWCPD ISC development and test facility. The contractor shall procure additional assets as needed.

iii. The ISC development and test facility will be used for:

1. Development of ISC software and hardware changes.

2. Verification and Validation of ISC software and a hardware changes prior to shipboard installation.

3. Verification and Validation of integration and interfaces with external systems prior to shipboard installation.

4. Recreation of ISC issues to assist with troubleshooting and resolution.

iv. The contractor shall maintain and upgrade lab assets as necessary to support

ISC.

v. Perform scheduled quarterly maintenance on CG-47 ISC equipment at the Land-

Based Engineering Site (LBES) to ensure optimal performance.

vi. Offer technical assistance to LBES engineers by powering down equipment before planned outages, assisting with equipment startup for interface testing, and providing requested technical data on the system.

h. Systems Engineering

i. The contractor shall engage in systems engineering practices according to the

NSWCPD Systems Engineering Process (SEP). The Systems Engineering Process

(SEP) is a flexible set of Process Management, Project Management, Engineering and Support processes. The NSWCPD SEP is based on level 3 of the Capability

Maturity Model Integration (CMMI). All NSWCPD SEP Process descriptions, templates and associated documentation will be available to the contractor.

The NSWCPD SEP includes the following process areas:

1. Project Management

a. Project Planning (PP)

b. Project Monitor and Control (PMC)

c. Requirements Management (REQM)

d. Supplier Agreement Management (SAM)

e. Integrated Project Management (IPM)

f. Risk Management (RSKM)

2. Engineering

a. Requirements Development (RD)

b. Technical Solutions (TS)

c. Product Integration (PI)

d. Verification (VER) and Validation (VAL)

e. Safety Engineering & Safety Management are included as

Process Areas

3. Support

a. Configuration Management (CM)

b. Process & Product QA (PPQA)

c. Measurement & Analysis (MA)

d. Decision Analysis and Resolution (DAR

4. Process Management

a. Org Proc Focus (OPF)

b. Org Proc Def (OPD)

c. Org Training (OT)

i. Quality Management

i. Quality Management System - The contractor shall provide its Quality

Management System (QMS) Level 1 and Level 2 Procedures meeting the requirements of ASQ/ANSI/ISO 9001:2015.

ii. Quality Management Plan – The contractor shall be subject to adhering to requirements such as Higher-Level Quality Inspection Clauses, NAVSEA

Technical Specifications, NAVSEA Standard Items, and Internal NSWCPD requirements such as Standard Operating Procedures and Quality Management

Procedures. The contractor shall provide a Quality Management Plan, detailing how requirements will be met, objective quality evidence will be documented, and sub- contractors will be approved and managed.