RFI ICAS Information 05FEB25.pdf

ICAS RFI Attachment

Integrated Condition Assessment System (ICAS)

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. NSWCPD Division 53 is directly involved with the HM&E Cyber, Monitoring & Information Systems and supports the development, modernization, acquisition, and life cycle maintenance of Remote

Monitoring and Condition Based Maintenance Systems across various platforms.

b. This RFI is for engineering and technical services required to provide engineering, technical, logistics, training, cyber, program support, and sustainment for the development, prototyping, implementation, installation, deployment, and in-service support of Integrated Condition Assessment System (ICAS) technologies for naval ship systems on surface and amphibious ship classes.

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

Maintenance of ICAS. The Contractor shall provide a full spectrum of ICAS engineering and programmatic activities related to being the Navy’s surrogate for ICAS 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. The Contractor shall provide and maintain a quality control plan for all activities performed as part of this contract. Tasks include but are not limited to performing systems engineering analysis in order to interface systems with

ICAS; 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. The purpose of ICAS is to enable automated monitoring, trending, and digital log keeping in support of Condition Based Maintenance. Since the early 1990’s, the United

States Navy has been augmenting control systems by installing ICAS. The Navy capitalizing on Commercial Off the Shelf (COTS) software has successfully deployed ICAS on approximately sixty-five (65) vessels.

ICAS is a software based system consisting of two major components: (1) ICAS Software

Shell & (2) Configuration Data Set (CDS).

The ICAS Software Shell is a Commercial Off the Shelf (COTS) software product provided by IDAX Inc. for which the U.S Navy holds Government Purpose Rights (GPR) in accordance with the DFARS 227.7103-5(b). The software is developed in a shell type architecture to allow for varied implementation of machinery monitoring and Condition

Based Maintenance (CBM). This shell is identical, vice version revisions, on all Navy installations. GPR has allowed the Government System Engineering Process (SEP) to make changes to the software via in-house or third party contract support. Thus, the government version of ICAS has diverged somewhat from the commercial version rendering it Government Off the Shelf (GOTS) via COTS.

Each workstation accommodates a unique Configuration Data Set (CDS) for ICAS, which contains the engineering information of the system monitored per naval vessel. CDS requirements are generated from Reliability Centered Maintenance (RCM) and Failure

Mode and Effects Analysis (FEMA) analysis conducted by In-Service Engineering Agents

(ISEAs) and other Subject Matter Experts (SMEs). The CDS, when input into the ICAS

Software Shell, converts acquired sensor data into useful information. Data is trended, evaluated, and fused to recommend equipment maintenance be accomplished based on evidence of need.

A typical U.S. Navy ICAS installation consists of one to five Windows-based workstations, one in each major machinery compartment, connected by an active Local Area Network

(LAN).

A typical ICAS installation on a surface combatant hull monitors the following machine/systems:

i. Main Propulsion

ii. Reduction Gear

iii. Line Shaft Bearings

iv. Controllable Pitch Propeller

v. Ship Service Gas Turbine Generator

vi. Fuel Oil Service

vii. Main Propulsion Lube Oil

viii. Lube Oil Fill, Transfer, and Purification

ix. Air Conditioning

x. Refrigeration

xi. Distilling Plant

xii. Reverse Osmosis

xiii. Auxiliary Boiler

xiv. Firemain

xv. Seawater Pumps

xvi. Fuel Oil Fill and Transfer

xvii. High Pressure Compressed Air

xviii. Low Pressure Compressed Air

ICAS, depending on the Ship Class and architecture, also contains the Machinery Control

Message Acquisition System (MCMAS) module. MCMAS is a diagnostic tool that greatly reduces both cost and man-hours spent troubleshooting ship mechanical and electrical failures by providing increased, continuous data extraction and analysis capabilities. The operating principle of MCMAS is to examine all status change messages, then process and convert contents into engineering data that is both displayed on line and stored to optical disk for future retrieval and analysis.

The current MCMAS data acquisition system collects all 5K + available machinery controls system parameters every second, with a powerful data reduction and analysis feature. MCMAS captures the communications between Machinery Control System

(MCS) consoles and converts them to a Windows-based data file. MCMAS can also be used for long-term analysis to provide Reliability Maintainability and Availability (RM&A) assessment information and to develop operational performance profiles.

e. ICAS also contains links to digital Navy logistic products such as the Engineering

Operational Sequencing System (EOSS), Planned Maintenance System (PMS), and

Integrated Electronic Technical Manuals (IETMs); which link directly to the appropriate section or card as well as enabling browsing of the entire books.

Typically, ICAS will interface to an existing machinery control database to receive pertinent information without duplicating sensor or processing hardware. For additional data points not provided by MCS, ship’s force utilizes a Portable Data

Terminal (PDT) to upload data, via a serial interface, to the ICAS workstations.

Figure 1 below provides a high-level diagram of ICAS.

f. ICAS is utilized on board various USS Arleigh Burke (DDG-51), USS Ticonderoga (CG-47), USS San Antonio (LPD-17), USS Whidbey (LSD-41), USS Harpers Ferry (LSD-49) and USS

Avenger (MCM) Class ships; for a total of 65 ships. ICAS is used by ships force, in-service engineering agents, and Regional Maintenance Center (RMC) personnel.

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 ICAS. The following sections includes tasking that will be applied to and scaled as necessary for the

ICAS program.

b. As ISEA the Contractor shall be responsible for full spectrum of ICAS 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 ICAS.

Figure 1 - ICAS High Level Diagram

2. Perform troubleshooting on ICAS equipment such as computer hardware, computer operating systems, and computer peripherals.

3. Assistance with identifying drawing discrepancies, configuration issues, equipment deficiencies, and special or operational interference.

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

iii. System Problem Tracking

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

iv. Requirements Management

1. Maintain requirements for ICAS.

2. Develop new requirements as necessary.

v. System Design

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

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.

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

ICAS 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 ICAS https://www.nde.navy.mil/

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

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 for all naval vessels utilizing ICAS.

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

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

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

1. Evaluate technical documentation and provide input to ensure that ILS documentation is updated.

2. Provide system red lines to drawings and equipment schematics.

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. Support shipping of materiel and assets required for supporting of tasks listed herein.

7. Provide support with staging (drawing material from inventory in accordance with designs) of materiel and assets required for supporting of tasks listed herein

8. Provide shipboard operator and maintainer ICAS training.

9. Operator and Maintainer System Training Support

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

b. Assist Government activities in classroom training and instruction.

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

Maintenance Center (RMC) personnel.

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

11. Provide updates to related Engineering Operational Sequencing System

(EOSS) as necessary.

12. Provide updates to related technical manuals as necessary.

13. Provide updates to Approved Parts Lists (APL) as necessary.

x. Installation Guidance

1. Complete shipboard installations, troubleshooting support 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 ICAS test procedures during lab and shipboard test evolutions.

xii. Obsolescence Management

1. Develop ICAS 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 ICAS 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.

c. As the SSA the Contractor shall have overall responsibility for the ICAS 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 ICAS:

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 ICAS 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.

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 ICAS, Tasks include:

i. Maintain ICAS Authority to Operate in accordance with the Risk Management

Framework (RMF)

ii. Cybersecurity posture sustainment tasks related to new and existing ICAS 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.

iii. 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. Develop and present technical presentations and information to various entities such as peers, shipboard installation managers, ship’s force representatives, and program sponsors.

g. Development and Test Facility

i. At the Contractor site, the Contractor shall establish an ICAS development and test facility.

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

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

1. Development of ICAS software and hardware changes.

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

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

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

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

ICAS.

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)

5. 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.