Attch J-14_Sample Maintenance Plan.pdf

i

MAINTENANCE PLAN SAMPLE

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors only;

Critical Technology; 16 March 2020. Other requests for this document shall be referred to PEO IWS 5.

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979, as amended (Title 50, U.S.C., App. 2401 et seq.).

Violations of these export laws are subject to severe criminal penalties.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of content or reconstruction of the document.

ii

PEO IWS 5

SURFACE SHIP USW COMBAT SYSTEMS

[SYSTEM NAME]

MAINTENANCE PLAN

SIGNATURE PAGE

Recommended By:

CONTRACTOR

Maintenance Planning (LEM)

Date:

Approved By:

AN/SQQ-89 (ISEA)

Approved By:

ASW Product Support Manager iii

FOREWORD

This Surface Ship Undersea Warfare (USW) Combat Systems Maintenance Plan has been developed to support the achievement of PEO IWS 5 logistic goals for [SYSTEM]/[CONFIGURATION]. This plan is intended to describe how the maintenance concept will be implemented, prescribe Integrated Logistics

Support (ILS) actions for maintenance tasks that will be required for the system and equipment during its life cycle, and explain the technical requirements for ILS products. These goals consist of achieving maximum Operational Availability (AO) and increasing ship self-sustainability through the following:

ILS product development

Improved preventive and corrective maintenance

Enhanced Performance Monitoring/Fault Detection/Fault Localization (PM/FD/FL)

Reduced troubleshooting and repair turnaround time

Reduction in overall maintenance program cost

This plan will be maintained by the Maintenance Planning Logistics Element Manager (LEM). Specific comments or questions concerning this Maintenance Plan should be addressed to:

Program Support Manager, PEO IWS 5

Program Executive Office, Integrated Warfare Undersea Systems

1333 Isaac Hull Avenue SE, Building 197, Room 1E 2600

Washington Naval Yard, DC 20376 iv

RECORD OF CHANGES

Change No. Date Title or Brief Description Entered By

- June 2020 Draft Submittal v

TABLE OF CONTENTS

Sections Page

INTRODUCTION

PURPOSE

SCOPE

SYSTEM DESIGN FOR SUITABILITY REQUIREMENTS

MAINTENANCE ORGANIZATION

GENERAL

PEO IWS 5

PEO IWS 5 PRODUCT SUPPORT MANAGER

LOGISTICS MANAGER

MAINTENANCE PLANNING LOGISTICS ELEMENT MANAGER

TECHNICAL DESIGN AGENT

NAVAL SEA LOGISTICS CENTER

NAVAL SUPPLY SYSTEMS COMMAND

MAINTENANCE LEVELS

[SYSTEM]/[CONFIGURATION] SYSTEM ................................................. ERROR! BOOKMARK NOT DEFINED.

SYSTEM FUNCTIONAL DESCRIPTION

SERVER LOADOUT

AN/SQQ-89A(V)15 SYSTEM HARDWARE

3.3.1. SONAR SUBSYSTEMS/COMPONENTS

O-LEVEL DIAGNOSTICS/TEST DEVICES ...................................... ERROR! BOOKMARK NOT DEFINED.

3.4.1. PORTABLE MAINTENANCE DEVICE ............................................... ERROR! BOOKMARK NOT DEFINED.

3.4.2. ORGANIZATIONAL TOWED ARRAY TEST SET ............................... ERROR! BOOKMARK NOT DEFINED.

I-LEVEL DIAGNOSTICS/TEST DEVICES ........................................ ERROR! BOOKMARK NOT DEFINED.

3.5.1. ELEMENT LEVEL ACQUISITION AND PLAYBACK SYSTEM ......... ERROR! BOOKMARK NOT DEFINED.

3.5.2. ACOUSTIC DATA ACQUISITION AND ANALYSIS SOFTWARE ...... ERROR! BOOKMARK NOT DEFINED.

3.5.3. IN-WATERS ......................................................................................... ERROR! BOOKMARK NOT DEFINED.

3.5.4. WET DOME PHASE TEST .................................................................. ERROR! BOOKMARK NOT DEFINED.

3.5.5. PORTABLE TOWED ARRAY TEST SET ............................................. ERROR! BOOKMARK NOT DEFINED.

3.5.6. SURFACE SHIP RADIATED NOISE MEASUREMENT ..................... ERROR! BOOKMARK NOT DEFINED.

3.5.7. SPIDER TOOL ..................................................................................... ERROR! BOOKMARK NOT DEFINED.

3.5.8. WQM-9 TEST UNIT ............................................................................. ERROR! BOOKMARK NOT DEFINED.

DIAGNOSTICS/TEST DEVICES ....................................................... ERROR! BOOKMARK NOT DEFINED.

3.6.1. DAQNET TESTER ............................................................................... ERROR! BOOKMARK NOT DEFINED.

3.6.2. Cyber Security Tool Kit ...................................................................... ERROR! BOOKMARK NOT DEFINED.

MISSION CRITICAL FUNCTIONS IN TI-18..................................... ERROR! BOOKMARK NOT DEFINED.

3.7.1. PROCESSING ELEMENTS ................................................................. ERROR! BOOKMARK NOT DEFINED.

3.7.2. SENSOR ELEMENTS .......................................................................... ERROR! BOOKMARK NOT DEFINED.

3.7.3. INFRASTRUCTURE AND SERVICES ................................................ ERROR! BOOKMARK NOT DEFINED.

SEGMENT REDUNDANCY ............................................................... ERROR! BOOKMARK NOT DEFINED.

MAINTAINABILITY DEMONSTRATION........................................ ERROR! BOOKMARK NOT DEFINED.

MAINTENANCE CONCEPT

PURPOSE

MAINTENANCE APPROACH

vi

4.2.1. ORGANIZATIONAL LEVEL MAINTENANCE

4.2.2. INTERMEDIATE LEVEL MAINTENANCE......................................... ERROR! BOOKMARK NOT DEFINED.

4.2.3. DEPOT LEVEL MAINTENANCE

COMMERCIAL OFF-THE-SHELF/NON-DEVELOPMENT ITEM .. ERROR! BOOKMARK NOT DEFINED.

MINI-STOCK-POINT .......................................................................... ERROR! BOOKMARK NOT DEFINED.

INTERIM INVENTORY CONTROL POINT...................................... ERROR! BOOKMARK NOT DEFINED.

LOCAL AREA NETWORK MAINTENANCE ................................... ERROR! BOOKMARK NOT DEFINED.

FIBER-OPTIC REPAIR ....................................................................... ERROR! BOOKMARK NOT DEFINED.

CONDITION-BASED MAINTENANCE

MAINTENANCE ASSIST MODULES

SYSTEM UNIQUE MAINTENANCE ................................................. ERROR! BOOKMARK NOT DEFINED.

4.10.1. HARDWARE ........................................................................................ ERROR! BOOKMARK NOT DEFINED.

4.10.2. SOFTWARE ......................................................................................... ERROR! BOOKMARK NOT DEFINED.

DISPOSITION

LOGISTICS SUPPORT

SUPPLY SUPPORT

TECHNICAL DOCUMENTATION

MAINTENANCE INDEX PAGE/MAINTENANCE REQUIREMENT CARDS

SUPPORT AND TEST EQUIPMENT ................................................. ERROR! BOOKMARK NOT DEFINED.

MANPOWER AND TRAINING

PURPOSE

MANPOWER

6.2.1. ORGANIZATIONAL LEVEL MANPOWER

6.2.2. INTERMEDIATE LEVEL MANPOWER

6.2.3. DEPOT LEVEL MANPOWER

TRAINING

6.3.1. PERSONNEL SKILL REQUIREMENTS

ADVANCED CAPABILITY BUILD (ACB-17) ............................................ ERROR! BOOKMARK NOT DEFINED.

ADVANCED CAPABILITY BUILD-17 OVERVIEW

ACB-17 SONSYM

7.2.1. SONSYM STATUS INDICATORS ........................................................ ERROR! BOOKMARK NOT DEFINED.

7.2.2. PERFORMANCE MONITORING ....................................................... ERROR! BOOKMARK NOT DEFINED.

7.2.3. STATUS REPORTING ......................................................................... ERROR! BOOKMARK NOT DEFINED.

7.2.4. HARDWARE TAB (HOME SCREEN) ................................................. ERROR! BOOKMARK NOT DEFINED.

7.2.5. HARDWARE STATUS ......................................................................... ERROR! BOOKMARK NOT DEFINED.

7.2.6. STRING STATUS ................................................................................. ERROR! BOOKMARK NOT DEFINED.

7.2.7. RECONFIGURATION MANAGEMENT ............................................. ERROR! BOOKMARK NOT DEFINED.

7.2.8. FUNCTIONAL VIEW ........................................................................... ERROR! BOOKMARK NOT DEFINED.

7.2.9. NTP TIME TAB .................................................................................... ERROR! BOOKMARK NOT DEFINED.

7.2.10. TEMPERATURE TAB .......................................................................... ERROR! BOOKMARK NOT DEFINED.

7.2.11. STORAGE MANAGER TAB................................................................. ERROR! BOOKMARK NOT DEFINED.

7.2.12. NETWORK MANAGEMENT ............................................................... ERROR! BOOKMARK NOT DEFINED.

7.2.13. NETWORK TOOLS TAB ...................................................................... ERROR! BOOKMARK NOT DEFINED.

7.2.14. LOGGING ............................................................................................ ERROR! BOOKMARK NOT DEFINED.

RECONFIGURATION MANAGEMENT ........................................... ERROR! BOOKMARK NOT DEFINED.

COMMERCIAL OFF-THE-SHELF CUSTOMIZED HUMAN-MACHINE INTERFACE ....................... ERROR!

BOOKMARK NOT DEFINED.

ALERTS DESCRIPTION

vii

INFORMATION ASSURANCE EFFECTS ON O-LEVEL MAINTENANCE ...... ERROR! BOOKMARK NOT

DEFINED.

CYBER AND INTRUSION SECURITY

RED HAT ENTERPRISE LINUX 7

CYBERSECURITY TOOLKIT ............................................................ ERROR! BOOKMARK NOT DEFINED.

8.2.1. OPEN-SOURCE SECURITY ............................................................... ERROR! BOOKMARK NOT DEFINED.

8.2.2. HOST INTRUSION DETECTION SYSTEM ........................................ ERROR! BOOKMARK NOT DEFINED.

8.2.3. NETWORK INTRUSION DETECTION AND PREVENTION TOOL .. ERROR! BOOKMARK NOT DEFINED.

8.2.4. INTEGRITY MEASUREMENT ARCHITECTURE .............................. ERROR! BOOKMARK NOT DEFINED.

8.2.5. LINUX PLUGGABLE AUTHENTICATION MODULES..................... ERROR! BOOKMARK NOT DEFINED.

8.2.6. LIGHTWEIGHT DIRECTORY ACCESS PROTOCOL ........................ ERROR! BOOKMARK NOT DEFINED.

8.2.7. VIRUS SCANNING .............................................................................. ERROR! BOOKMARK NOT DEFINED.

8.2.8. APPLICATION WHITELISTING ......................................................... ERROR! BOOKMARK NOT DEFINED.

8.2.9. ACCESS CONTROL ............................................................................ ERROR! BOOKMARK NOT DEFINED.

TWO-FACTOR AUTHENTICATION

RADIUS SERVER ................................................................................ ERROR! BOOKMARK NOT DEFINED.

TRUSTED PLATFORM MODULE ..................................................... ERROR! BOOKMARK NOT DEFINED.

FIREWALL SWITCH .......................................................................... ERROR! BOOKMARK NOT DEFINED.

SOLID STATE DRIVES ...................................................................... ERROR! BOOKMARK NOT DEFINED.

APPENDIX A. [CONFIGURATION] MAINTENANCE TROUBLESHOOTING

TROUBLESHOOTING AT THE O-LEVEL ....................................... ERROR! BOOKMARK NOT DEFINED.

O-LEVEL EQUIPMENT TROUBLESHOOTING WITH SONSYM ..... ERROR! BOOKMARK NOT DEFINED.

O-LEVEL TROUBLESHOOTING NOT ADDRESSED IN SONSYM .. ERROR! BOOKMARK NOT DEFINED.

ILS PRODUCT REQUIREMENTS FOR UNITS

TROUBLESHOOTING REQUIREMENTS

ACRONYMS AND ABBREVIATIONS ................................................................. ERROR! BOOKMARK NOT DEFINED.

LIST OF FIGURES

Figure 3-1. Server Loadout

Figure 3-2. Unit 139 TAPS .......................................................................................... Error! Bookmark not defined.

Figure 3-3. Units 830-835 Display Consoles ............................................................... Error! Bookmark not defined.

Figure 3-4. Unit 837 MFP ........................................................................................... Error! Bookmark not defined.

Figure 3-5. Unit 858 AI&R ......................................................................................... Error! Bookmark not defined.

Figure 3-6. Unit 839 and Unit 840 E-Status Boards .................................................... Error! Bookmark not defined.

Figure 3-7. Data Processing Units (845/846/847) ....................................................... Error! Bookmark not defined.

Figure 3-8. Unit 858 Receiver I/O ............................................................................... Error! Bookmark not defined.

Figure 3-9. Unit 859 Transmitter I/O........................................................................... Error! Bookmark not defined.

Figure 3-10. Unit 871 Equipment Rack ....................................................................... Error! Bookmark not defined.

Figure 3-11. Mission Critical Enclosure (MCE) .......................................................... Error! Bookmark not defined.

LIST OF TABLES

Table 7-1. SONSYM Functions ........................................................................... Error! Bookmark not defined.

Table 7-2. SONSYM Status Indicators ................................................................. Error! Bookmark not defined.

Table 7-3. SONSYM Log Types .......................................................................... Error! Bookmark not defined.

Table 7-4. Alert Descriptors ................................................................................. Error! Bookmark not defined.

Table 7-5. Alert Stages ......................................................................................... Error! Bookmark not defined.

Table A-1. ILS Product Requirements

Table A-2. Troubleshooting Requirements ........................................................... Error! Bookmark not defined.

REFERENCE DOCUMENTS

DOCUMENT/TITLE NUMBER

Ships’ Maintenance and Material Management (3-M) Manual NAVSEAINST 4790.8 (series)

Maintenance Policy For United States Navy Ships OPNAVINST 4700.7 (series)

Classified Material Destruction Report OPNAV 5511/12

Department of Defense Standard Practice

Reliability-Centered Maintenance (RCM) Process

MIL-STD-3034A

Reliability-Centered Maintenance Handbook S9081-AB-GIB-010/MAINT

Logistics Product Data GEIA-STD-0007-B

Logistics Product Data Reports TA-HB-0007

Product Support Analysis TA-STD-0017

Department of the Navy Information Security SECNAV M-5510.36A

Program and Remanence Security Guidebook DON IA Pub P-5239-26

Department of Defense Handbook, Product Support Analysis MIL-HDBK-502A

Fiber Optic Cabling Systems Requirements and Measurements MIL-STD-1678-1D Change 1

Fiber Optic Cable Topology S9086-PF-STM-010/CH-408

Fiber Optic Cable Topology Installation Standard Methods For

Naval Ships

MIL-STD-2024B(SH)

PEO IWS 5 Surface Ship USW Combat Systems Integrated

Logistics Support Plan (ILSP)

PEO IWS 5B-12-ILSP-011R2

PEO IWS 5 Surface Ship USW Combat Systems TB-37 Multi-

Function Towed Array (MFTA) Maintenance Plan

IWS 5-TB-37MP

Operational Availability of Equipment and Weapons Systems

OPNAV INSTRUCTION

3000.12A

Operational Requirements Document (ORD) AN/SQQ-89

Improvement Program

ORD #667-76-05

INTRODUCTION

PURPOSE

The purpose of this Maintenance Plan is to define how maintenance will be accomplished for the

[SYSTEM]/[CONFIGURATION]Surface Ship Undersea Warfare (USW) Combat System

Program. This plan reflects maintenance planning progress as of the latest issue date.

SCOPE

This Maintenance Plan reflects a systems approach to maintenance and provides Program

Executive Office (PEO) Integrated Warfare Systems (IWS) 5 with the information necessary to make logical Logistic Support (ILS) planning and management decisions.

The Logistics Support Analysis (LSA) process performed in support of the Maintenance

Philosophy will be used to establish all maintenance requirements for preventive and corrective maintenance of the system. This document serves as the source for

[SYSTEM]/[CONFIGURATION] approved maintenance requirements and activities. It contains information relative to the following:

Maintenance level concepts and the identification and assignment of maintenance tasks and support materials

The support requirements of the Regional Maintenance Centers (RMCs), In-Service

Engineering Activity (ISEA), Intermediate Maintenance Activities (IMAs), and Original

Equipment Manufacturers (OEMs)

Troubleshooting philosophy, techniques, and aids

Manpower/manning/skill requirements, including identification of training requirements and manpower loading

Applicable Packaging, Handling, Storage, and Transportation (PHS&T) requirements

SYSTEM DESIGN FOR SUITABILITY REQUIREMENTS

The [SYSTEM]/[CONFIGURATION] maintainability requirements focus on influencing system design in such a way that system downtime associated with preventive or corrective maintenance is minimized. This influence involves primarily the selection of a reliable set of equipment and a design that provides fast and accurate fault detection, localization, access, troubleshooting, replacement, and repair validation of a failure.

The measure of a system’s maintainability is identified as Mean Time to Repair (MTTR). MTTR represents a statistical average time required to perform maintenance. From initial design, a maintainability prediction is performed using predicted values for times associated with fault detection, troubleshooting to a failed Lowest Replaceable Unit (LRU), removal and replacement of the LRU, and post-repair validation. As part of the validation process, the maintainability prediction results shall be validated during the planned Maintainability Demonstration (M-DEMO).

Per the Operational Requirements Document (ORD) 667-76-05, the desired MTTR is 30 minutes to one hour. Suitability requirements are listed in the ORD for the [SYSTEM] and set the baseline for maintenance and sustainment initiatives. Suitability requirements in the ORD include:

Suitability Requirements Threshold Objective

Operational Availability 0.85 0.90

Mean Time Between Mission Critical Failure (Software) 25 hrs.

(Hardware) 168 hrs.

Same

Mean Time to Repair 60 min 30 min

AO is a primary measure of readiness for weapon systems and associated equipment. It is determined by reliability (Mean Time Between Failure - MTBF), maintainability (Mean Time to

Repair - MTTR), and supportability (Mean Logistics Delay Time - MLDT). It is calculated as follows:

AO =

𝑀𝑇𝐵𝐹

𝑀𝑇𝐵𝐹+𝑀𝑇𝑇𝑅+𝑀𝐿𝐷𝑇

The [SYSTEM] shall attain this AO threshold during any given 60-day mission cycle. System uptime includes equipment in standby or off condition if the equipment is not required for the mission. Downtime is the time the system is down for repair of operational mission hardware failures or the restoration from operational mission software faults. Downtime also includes planned maintenance time with a periodicity less than or equal to the test duration time that prevents the system from performing its operational mission. The planned maintenance time that is of a periodicity greater than the test duration time is considered neutral time and is not included in the availability calculation.

When ORD 667-76-05 implemented the Acoustics Rapid Commercial off-the-Shelf (COTS)

Insertion (ARCI) design process, PEO IWS 5 started the Maintenance Free Operating Period

(MFOP) program with the goal of determining the benefits/feasibility of designing a system that would operate for a specified time period without requiring maintenance. An Oracle database was added to the [SYSTEM] ARCI systems in order to measure progress towards that goal and to support improved “software only troubleshooting.” The MFOP server captures various categories of data during the system operations including the following:

Server temperature

Processor/memory usage

Display/server lineup

Array Performance Monitoring

Network/software errors

User initiated recovery actions

Application specific reliability metrics (time to build Link Lofar Gram (LLG), time to promote a Contact Follower (CF) success of medium frequency active pings, etc.)

Because ARCI is part of the AN/SQQ-89A(V)15 spiral development process, MFOP data is continually being updated and evaluated, and the access to the historical system’s reliability data also continues to expand to allow for more in-depth system analysis. These additional data resources may include the following:

Fleet Support Data (Corona)

Materials Readiness Database

Reliability, Maintainability, Availability (RMA) data

Failure Reporting, Analysis, and Corrective Action System (FRACAS) data

Failure Mode, Effects and Criticality Analysis (FMECA)

One of the primary design focuses of the [SYSTEM] system is the ability to operate in a degraded condition. The period of time that constitutes system availability does not include any interval where the system is unable to execute a required function; thus, it is operating in a degraded condition.

Per the performance specification, scheduled Organizational (O)-Level preventive maintenance will not exceed 30 minutes per day or three work hours during any one-week period. Preventive maintenance at the O-Level is limited to inspection, cleaning, lubricating, and offline testing of the equipment.

MAINTENANCE ORGANIZATION

GENERAL

PEO IWS 5 systems consist of multiple variants resulting from installed upgrades and changes in subsystem architecture. The overall responsibility for the PEO IWS 5 Maintenance Planning function resides with the PEO IWS 5 Product Support Manager.

PEO IWS 5

PEO IWS 5 provides Program Management direction for Maintenance Planning life-cycle support decisions. PEO IWS 5 establishes program policy, milestones, schedules, and sets priorities.

PEO IWS 5 PRODUCT SUPPORT MANAGER

PEO IWS 5 provides Program Management direction for ILS and sustainment policy, milestones and schedules, and sets priorities across various projects.

LOGISTICS MANAGER

The PEO IWS 5 Program Support Manager has established an organization that delegates responsibility and authority to specific individuals and organizations in key logistic support areas to help meet PEO IWS 5 management and priority requirements. As part of this delegation, the

Logistics Manager is responsible for ILS. Further definition of the Program Support Manager and

Logistics Manager’s responsibilities are detailed in the PEO IWS 5 Integrated Logistics Support

Plan (ILSP).

MAINTENANCE PLANNING LOGISTICS ELEMENT MANAGER

The PEO IWS 5 Program Support Manager has assigned a Maintenance Planning Logistics

Element Manager (LEM), and delegated responsibility and authority for this Maintenance Plan.

TECHNICAL DESIGN AGENT

The Technical Design Agent (TDA) provides technical inputs for new and existing systems, technical support for towed array and fire control systems and Project Team representation. The

TDA also provides guidance for any upgrades or changes to the [SYSTEM] system.

NAVAL SEA LOGISTICS CENTER (NAVSEALOGCEN)

Naval Sea Logistics Center (NSLC) develops the Readiness-Based Sparing (RBS) model for all

AN/SQQ-89A(V)15 systems. The model is formulated from data obtained from the Reliability

Block Diagrams (RBDs), components’ fleet-wide historical maintenance and repair data, and other various sources to calculate the amount of spares required to meet the AO threshold stated in the

ORD. Funds are provided by Naval Sea Systems Command (NAVSEA) 04 to execute the sparing analysis. Additional parts desired by the Program Acquisition Resource Manager (PARM) to support an AO higher than the threshold are funded by the PARM out of end item funds.

NAVAL SUPPLY SYSTEMS COMMAND

When new equipment is budgeted, the ILS manager completes the Program Support Data (PSD).

Among other functions, the PSD establishes the budget for Maintenance Assistance Modules

(MAMs), Installation and Check-Out (INCO) material, and On-Board Repair Parts (OBRPs). The

PSD also establishes the Material Support Date (MSD), which is the date Naval Supply Systems

Command (NAVSUP) assumes responsibility for filling fleet requisitions.

MAINTENANCE LEVELS

Depot (D)-Level maintenance is performed by contractor or government personnel at certified maintenance facilities.

Intermediate (I)-Level maintenance is performed by RMCs, ISEAs, or IMAs either onboard or at designated maintenance facilities.

Organizational (O)-Level is performed by shipboard technicians onboard the host platform.

[SYSTEM]/[CONFIGURATION]

SYSTEM FUNCTIONAL DESCRIPTION

The total functionality of the [SYSTEM]/[CONFIGURATION] system is organized into a structure of sensor, processing, control, and support segments. The system is capable of reallocating some functional segments into secondary or spare processors in the event of a failure.

Processing for some functional segments is distributed throughout more than one unit. The

[SYSTEM]/[CONFIGURATION] segments include the following:

Sensor and Processing Segments:

Undersea Warfare Control Functional Segment (UCFS)

Towed Array Functional Segment (TAFS)

Common Segments:

Common Displays

Common Storage

Control and Display Segments:

Beamformer Functional Segment (BFFS)

Hull Active Transmit Functional Segment (HATFS)

Hull Passive Processing Functional Segment (HPPFS)

Support Segments:

Common Enterprise Services (CES)/Sonar System Manager (SONSYM)

Recorder Functional Segment (RecFS)

SERVER LOADOUT

In the [CONFIGURATION] system, considerable effort went into consolidating the functionality and storage capabilities of the servers. As a result, the servers (now with 10 core processors) can process multiple functional segments that were once processed by individual servers in the previous version. Additionally, with the implementation of the S416 servers, the

[CONFIGURATION] engineers were able to reduce the number of Surface ASW Synthetic

Trainer (SAST) servers from 27 to 19. Document the server allocation breakdown for the current system.

SERVER P/N #1 SERVER P/N #2 SERVER P/N #3 Total function 3 4 7 function 4 18 22

Figure 3-1. Server Loadout

[SYSTEM] SYSTEM HARDWARE

The [SYSTEM]/[CONFIGURATION] provides surface warships with a seamlessly integrated

USW/ASW detection, localization, classification, and targeting capability. The system presents an integrated picture of the acoustic tactical situation by receiving and processing active and passive sonar sensor data from a variety of sensors (hull-mounted array, towed array, and sonobuoys). In addition to active and passive detection, the system provides a full range of USW functions to include underwater fire control, onboard training capability, a highly evolved display subsystem, and integration with the Light Airborne Multi-Purpose System (LAMPS) helicopter for sonobuoy signal processing. The following sections provide a brief description of the [CONFIGURATION] subsystems/components.

3.3.1 SONAR SUBSYSTEMS/COMPONENTS

Describe each unit, provide photos and functional layout, and make a brief statement on O-level maintenance requirements. For example:

Unit 139 – Towed Array Power Supply

The Towed Array Power Supply (TAPS) utilizes a rugged, shock-mounted equipment enclosure that incorporates a new replaceable/cleanable particle filter for the power supplies. The enclosure contains the following:

Four constant current COTS power supplies (three for array use and one spare)

Cabinet power control assembly/panel

Ethernet and Thermal Monitor assembly

Power Conditioner assembly

Fans and/or blowers required for forced air cooling

The TAPS, housed in an air-cooled unit, does not contain any computer processing elements.

Control and status functions are provided by discrete components resident within the Cabinet

Power Control Function and dedicated COTS power supply circuitry. The Power Control Function provides local and remote control of TAPS cabinet power, array power, interlock functions, remote control and monitoring of TB-37 Power Supply parameters, remote monitoring of Power Control

Panel switch selection, and remote monitoring of the TAPS thermal sensor status. The TAPS design allows the [SYSTEM] maintenance technicians to repair components within the Control

Panel Assembly (A1) and cabinet enclosure (see Figure 3-2). The technicians may remove and replace the following: A1 faceplate indicators, switches, meters, and alarms, internal electronic components (including relays, transformers, resistors, CCA board, and gaskets), internal TAPS cabinet components, key sight power supplies, thermal monitor and probes, thermistor switches, power conditioner, Ethernet switch, and air filters and blowers.

Figure 3-2 Unit 139 TAPS

MAINTENANCE CONCEPT

PURPOSE

The maintenance concept provides the basis for maintaining the

[SYSTEM]/[CONFIGURATION]ASW Combat System in the fleet. To ensure that the system can be maintained in the most efficient manner, emphasis is placed in the following areas:

Describe maintenance concept areas

MAINTENANCE APPROACH

The [SYSTEM] maintenance approach is based on mission duration and criticality, hardware and software technologies, personnel capabilities, and maintenance strategies. Maintenance planning includes various analyses that are performed using the general guidelines of the Product Support

Analysis (PSA) (MIL-HDBK-502A) processes. These analyses include FMECA, RCM, and

LORA, which are used to develop maintenance strategies based on identified maintenance drivers and trade off studies. The resulting strategies will include the use of BIT, Built-In Test Equipment

(BITE), MAMs, PM/FD/FL, Support and Test Equipment (S&TE), and progressive levels of repair. Calibrated items are listed in the Maintenance Requirement Cards (MRC)

4.2.1. ORGANIZATIONAL LEVEL MAINTENANCE

Describe all system unique o-level tools required to support the system.

4.2.2. INTERMEDIATE LEVEL MAINTENANCE

Describe all system unique i-level tools required to support the system.

4.2.3. DEPOT LEVEL MAINTENANCE

Describe all system unique d-level tools required to support the system.

CONDITION-BASED MAINTENANCE

The TB-37s are removed for condition-based maintenance during shipyard availabilities as part of the CMP process. The TB-37s are returned to the depot, where they are screened for outstanding

Engineering Change Proposals (ECPs) and general maintenance or upgrade. Upon completion, the

TB-37s are returned to the ship. The ISEAs play a proactive role in the conditional-based maintenance.

MAINTENANCE ASSIST MODULES

MAMs are a subset of system components that are used to eliminate FL ambiguities while conducting system diagnostics. A MAM is used to isolate a fault to an assembly; it is not a substitute for testing individual components to the piece-part level. A MAM can be interchanged or installed by ordinary module replacement without structural disassembly, alteration, modification, or related repairs to the equipment for each equipment application. The purpose of a MAM is to reduce the acquisition costs associated with the development of BIT/BITE, system diagnostics, and test equipment for troubleshooting.

On Board Repair Parts (OBRPs)

OBRPs can be provided during the Interim Support period based on projected failures, or, after fielding, based on demand. Unlike MAMs, the OBRP is an actual spare part provided to fleet users to ensure Ao is achieved. Budget cuts and an Ao of .93 for the AN/SQQ-89 program eliminated our participation in wide spread OBRP allowance. The 2019 MARRC-RB properly calculated Ao for the system at .72. Based on demand the following OBRPs were calculated for

TI12+ and TI14 platforms and will be carried over to TI18 and following upgrades.

The initial formulation of the OBRPs list is determined from several evaluation factors and data references including the part’s criticality, reliability, vendor reliability data, design developmental data, and its historical performance if used in previous TI installations. Using the Reliability

Block Diagram with all associated information, NSLC performs a RBS which results in the final on-board sparing recommendations to achieve optimal Ao. The MAMs and OBRP lists are combined with the list of special tools and enough consumables (recording tapes, xbt canister, etc.)

to support a 6-month deployment. This material is the initial outfitting or ILS on-load material.

In addition, recent direction to treat the TB-37 as mission critical will require that single points of failure in the data and power path be addressed by providing OBRPs. Requests from the ISEA and the availability of harvested parts results in the addition of the following OBRPs being added to [CONFIGURATION] platforms.

DISPOSITION

In accordance with DoD Manual 4140.01, Volume 11, all Navy items of supply must be assigned

DEMIL code either locally, or as part of the ICAPS file submission. In order to ensure military and commercial technology does not reach unauthorized users, equipment disposition is managed by the

Program Office. PEO IWS 5.0 ensures the recovery, reutilization, recycling, conversion, redistribution, transfer, and destruction of ASW components and materiel. Destruction planning for ASW material is included in depot certification process to ensure the depot has the ability to harvest re-useable assets and safely dispose of unserviceable assets that may require special handling, total destruction, or environmental waste permits.

LOGISTICS SUPPORT

SUPPLY SUPPORT

The APLs and Allowance Equipment Lists (AELs) shall be created to align with the content of this plan. Additionally, any spares determined as part of the RBS analysis and required materials for the maintenance, repairs, and replacement (identified in the IETMs and Training material) shall be included on the APLs/AELs. This maintenance plan is not intended to dictate the manner or means in which supply support is performed, but rather to more clearly define the areas to provision.

TECHNICAL DOCUMENTATION

The system technical documentation compliments SONSYM by providing the user with additional troubleshooting steps and removal and replacement procedures, if required. Technical documentation corrective maintenance shall not provide details that are not within O-Level maintenance capability or that are lower than the designated LRU level.

For continued availability with widely dispersed equipment locations onboard, the troubleshooting and corrective maintenance shall be available independent of system operation. The reality of the need for the technical documentation when the system is not available is probable, which drives the requirement for making technical documentation available via portable means. The technical documentation will be loaded onto the PMD to assist in maintenance actions. This maintenance plan is not intended to dictate how the technical documentation is developed and delivered, but rather refine which troubleshooting and corrective maintenance components are necessary for inclusion.

MAINTENANCE INDEX PAGE/MAINTENANCE REQUIREMENT CARDS

The MIPs and MRCs shall be developed through an RCM analysis-based approach. As part of the

RCM analysis, the following guidelines shall be applied during the identification of O-Level preventive maintenance tasks using MRCs for the [SYSTEM] TI-18/ACB-17:

Scheduled IAW the Periodic Maintenance Requirements Scheduling Subsystem.

Preventive maintenance will be minimized while at sea and will be performed when the ship is in port between missions wherever possible.

All preventive maintenance will be achievable at the O-Level utilizing the skills, documentation, and material available to onboard O-Level maintenance personnel.

No new skill requirements are to be introduced for preventive maintenance unless absolutely necessary as a result of new technology for the [SYSTEM] system. PEO IWS

5 shall be notified upon identification of any additional skill requirements.

There will be no redundancy of data developed for the [SYSTEM]. The use of existing preventive maintenance documentation shall be maximized to the extent applicable for

[SYSTEM] equipment. Preventive maintenance tasks will not cause increased risk of maintenance-induced failures (i.e., opening electronics enclosures to grease drawer slides or inspect electronic sub-components).

MANPOWER and TRAINING

PURPOSE

The Organizational, Intermediate and Depot Level manpower and training requirements needed to operate and maintain the [SYSTEM] are described in the following paragraphs.

MANPOWER

6.2.1. ORGANIZATIONAL LEVEL MANPOWER

O-Level maintenance and repair is performed by Ship’s Force as part of the [SYSTEM] support.

The shipboard Sonar Technician Surface (STG) manning is authorized by the Shipboard

Manpower Document for the operation and maintenance of the [SYSTEM] system and is documented IAW NTSP N96-NTSP-S-30-8115K (Under Revision). All O-Level maintenance is performed by the STG IAW the current technical documentation. 3 maintainers per ship have network training.

6.2.2. INTERMEDIATE LEVEL MANPOWER

I-Level maintenance and screening of the [SYSTEM]/[CONFIGURATION] is performed by

SMEs who leverage their experience with previous [SYSTEM] systems. The number of personnel required at a given I-Level site is determined by the number of ships home ported in the area, the operational tempo of each area, and the number of repair evolutions. I-Level maintenance can be performed at the RMCs, IMA, or by the ISEA.

6.2.3. DEPOT LEVEL MANPOWER

D-Level manpower fluctuates and is leveraged across [SYSTEM]/[CONFIGURATION] requirements for multiple programs for the US and Foreign Military Sales (FMS) surface fleets.

The personnel requirements are determined by the number of failed items repaired, the number of outstanding ECPs, and the availability of parts to perform these repairs and upgrades.

TRAINING

[SYSTEM]/[CONFIGURATION] maintenance training shall align with the troubleshooting and corrective maintenance outlined herein. As part of the training, the students shall be instructed in utilizing all troubleshooting (SONSYM and technical documentation) and corrective maintenance tools. This maintenance plan is not intended to dictate the manner or means in which training is conducted, but rather to more clearly define the areas of instruction.

6.3.1. PERSONNEL REQUIREMENTS

New V54B (formally 0524) - [SYSTEM]/(V)15 EC204 Surface Ship USW Combat Systems

Sensor Operator ( 3 per ship)

Performs [SYSTEM] system set-up and configuration procedures based on USW mission parameters. Operates the Acoustic Sensor Functional Segment (ASFS), Passive Acoustic

Functional Segment (PAFS), LAMPS Sonobuoy Functional Segment (LSFS), Torpedo

Recognition and Alertment Functional Segment (TRAFS), Sonar Performance Prediction

Functional Segment-Sonar Tactical Decision Aid (SPPFS-STDA), and Common System

Services Functional Segment (CSSFS) in all tactical situations to effectively detect, classify, localize, track and attack USW and small object contacts. Recognizes and interprets system alerts and degraded/casualty indications. Operates the System Resource Manager (SRM) to perform system reconfiguration, clear faults, or assist the maintenance technician with system troubleshooting.

New V55B (formally 0525) - [SYSTEM] Surface Ship USW Combat Systems Maintenance

Technician.

Performs system light-off and shut-down, and O-level maintenance on all [SYSTEM] Functional

Segments. Recognizes and interprets system alerts and degraded/casualty indications and malfunctions. Utilizes the SRM built-in Performance Monitoring/Fault Detection/Fault

Localization (PM/FD/FL) function to locate and identify faults specific to an LRU. Performs preventive maintenance procedures as delineated in prescribed maintenance requirements documentation.

New V56B (formally 0527) - AN/SQQ-89A(V)15/ Surface Ship USW Combat Systems

Journeyman

Directs, coordinates, monitors, and manages the performance of AN/SQQ-89A(V)15/(V)15

Sonar Control manned watch stations. Interprets sensor and support equipment outputs, recognizes and responds to environmental and tactical changes, and provides continuous tactical advice. Obtains and maintains a full understanding of the USW situation and makes effective use of the system's sensor and processing resources to achieve mission success. Performs all internal and external communications between the Sonar Control Watch Team and all other ship Watch

Teams. In a dual role, operate the Undersea Warfare Control Functional Segment (UCFS) in all tactical situations to effectively classify, localize, track, and attack USW and small object contacts. Contact handling responsibilities include track management coordination including system-level add, merge, and drop functions; working with the plotting team in developing TMA solutions; and coordinating contact classification changes between the Sonar Control and CIC teams. Fire control responsibilities include engagement planning and target prosecution using the

OTS torpedoes and VLA. Recognizes and interprets system alerts and degraded/casualty indications. Operates the SRM to perform system reconfiguration, clear faults, or assist the maintenance technician with UCFS troubleshooting.

The training outlined is divided into the following four categories:

Initial Training: Required training for current crew members onboard including system operators and maintainers affected by the ship change.

Initial/Follow-on Training: Initial training required for personnel currently onboard as well as “Follow-on” training for replacement crew.

Interim Training: When Follow-on training is required and is not online prior to installation, Interim training will cover the rotation of “initially” trained crew until the

Follow-on training is in place and Ready for Training (RFT).

Follow-on Training: Required training intended for personnel detailed to the ship as replacement crew.

SYSTEM SOFTWARE CAPABILITIES

ADVANCED CAPABILITY BUILD-XX OVERVIEW

The AN/SQQ-89 Improvement Program was established by ORD 667-76-05. The objective of the program was to help improve the system’s Measures of Performance (MOP), while also focusing on the continuous and rapid development and deployment of new technology on the AN/SQQ-89 system. This was made possible by taking advantage of the system Open System Architecture

(OSA) and Acoustics Rapid COTS Insertion (ARCI) designs. This allows engineers to take a build upon or spiral approach in the development of the TI and ACB which has been mandated to be updated every two years, even years for Hardware (TI) and odd years for Software (ACB).

Though ACB-17 promises to improve on the reliability of GUI alert notifications and is expected to give the operators access to additional resources that were disabled in ACB-15, software developers have focused on improving the ACB-17 software package from underneath the hood, in the areas of signal processing, software reliability, and accuracy of data analysis.

ACB-17 SONSYM

Features of SONSYM include multi-tiered views of system health, including physical hardware, functional string hardware and software status, and network and NTP status. SONSYM provides the operator with the tools for PM, FL, and reconfiguration management. The SONSYM display uses tabs for the operator to select the various supported health views and maintenance displays. Refer to Table 7-1 for available SONSYM functions:

Function Description

PM

SONSYM provides the current status of the system based primarily on exception reporting and indicates the severity of the error, the physical hardware that detected the error, and the functionality that is impacted by the error.

Reconfiguration

Management

SONSYM provides methods to determine load compatibility to move a function to a different server when a failure occurs.

FL

When PM is unable to fully diagnose the problem and the component is taken offline for diagnostics, SONSYM manages the suite of available diagnostics for each chassis in the system and provides the HMI for running the tests and reporting the results.

COTS-Customized

HMI

SONSYM provides technology-specific managers for these components that include custom HMIs designed to only provide the subset of available information that is most useful in diagnosis and recovery.

Describe maintenance screens and tabs within the system.

ALERTS DESCRIPTION

Describe all system alerts as they relate to system status and maintenance.

CYBER AND INTRUSION SECURITY

Describe system cyber and intrusion security. This may require a separate dlassified addendum.

Example includes:

RED HAT ENTERPRISE LINUX 7

The Red Hat Enterprise Linux 7 (RHEL7) operating system provides a rich application infrastructure with built-in mechanisms for identity management, resource allocation, and performance optimization with enhanced security prevention. The IETM will include all procedures for creating and deleting user accounts and privileges.

TWO-FACTOR AUTHENTICATION

Two-Factor Authentication (2FA), also known as “multi-factor authentication,” is a two-step verification process that provides an extra layer of security. 2FA requires not only a password and username, but the operator’s hardware token (i.e., DoD Common Access Card (CAC)).

USB ports have been added to the PMDs, NGWs, and Multi-Plotter units to allow the connection of a portable CAC reader that will be issued to sites as a special tool at the end of the

[CONFIGURATION] installation.

APPENDIX A.

[CONFIGURATION] MAINTENANCE TROUBLESHOOTING

A.0 ILS PRODUCT REQUIREMENTS FOR UNITS

ILS Product Requirements is a list of the basic Maintenance Philosophy broken down by each unit to support the O-Level LRU requirements in support of [SYSTEM]/[CONFIGURATION]/ACB-

17 systems for ILS products.

Table A-1, ILS Products Requirements, identifies the major ILS areas and the appropriate support to be provided based on the basic Maintenance Philosophy, such as identification of what component level shall be provided, areas that are required to be covered in the technical documentation, what is required for training, and what PMS or Environmental, Safety, and Health

(ESH) concerns require addressing by component level and type. Table A-2, Troubleshooting

Requirements, goes into further detail related specifically to Maintenance Training and technical documentation requirements.

Major items will be called out as I-level, and smaller items not specifically called out in the ILS

Products Requirements table are considered I-Level and shall be addressed by the designated

RMC, ISEA, or IMA.

Table 0-1. ILS Product Requirements

Unit Item Item Type Training

Requirement

Technical

Documents Supply Support

MC

E

Cabi net

Applies to

Units 845, 846, 847, 858, and

Controls/Indicators Troubleshoot

Remove/Replace

Troubleshoot

Remove/Replace Provision

Power/Circuit

Breakers

Troubleshoot

Remove/Replace

Troubleshoot

Remove/Replace Provision

Cabinet Hardware Remove/Replace Remove/Replace Provision

EMI Filters Remove/Replace Remove/Replace Provision

Heat Exchanger/Fans Remove/Replace Remove/Replace Provision

845, 846, Server

Server

Troubleshoot

Remove/Replace

Configure BIOS

Troubleshoot

Remove/Replace

Configure BIOS

Provision

CMOS Battery Troubleshoot

Remove/Replace

Troubleshoot

Remove/Replace Provision

Disk Drives

Troubleshoot

Remove/Replace

Reinstall Software

Troubleshoot

Remove/Replace

Reinstall Software

Provision

Network

Switch Network Switch

Troubleshoot

Remove/Replace

Troubleshoot

Remove/Replace Provision

Update/Validate-

Software/Firmware

Configure Switch

Update/Validate-

Software/Firmware

Configure Switch

Fans Troubleshoot

Remove/Replace

Troubleshoot

Remove/Replace Provision

SFP Modules Troubleshoot

Remove/Replace

Troubleshoot

Remove/Replace Provision

Power Supplies Troubleshoot

Remove/Replace

Troubleshoot

Remove/Replace Provision

Hard Drives

Troubleshoot

Remove/Replace

Reinstall Software

Troubleshoot

Remove/Replace

Reinstall Software

Provision

Table 0-1. ILS Product Requirements

TROUBLESHOOTING REQUIREMENTS

Document the required technical documentation and Maintenance Training tasks broken down by equipment type to support the O-Level LRU requirements in support of the system. For example:

Table A-2. Troubleshooting Requirements

Equipment

Type Method Training and Technical Document Requirements

Server

SONSYM

Troubleshooting

Using SONSYM status to troubleshoot server/installed circuit card failures based on color indications

FL Testing using available views

Server Status using Hardware View

Bring up SONSYM on the PMDs

Recognize hardware failures from interface failures, and how to access the error message indicating a failed condition

Time (NTP, AEGIS, System Clocks/Hardware Clocks)

Interfaces (NTDS, IRIG, D/A, A/D, Power)

Cybersecurity Scans

Corrective

Maintenance

Solid State Drives remove and replace procedures

Software reload IAW the SVD Loading BIOS configuration file (ACB-17)

Troubleshooting with monitor and keyboard and booting with the system

System boot sequence

VIPs

Other system Nodes

PXE Boot (LAN)

NFS

Driver loading for PCIe cards

Table A-2. Troubleshooting Requirements

Equipment

Type Method Training and Technical Document Requirements

View logs to see if issues are noted

Command line to assist in troubleshooting. Examples include:

o Log on to programs and using tail -f, more, cat to view log files o NFS, symptoms of an NFS failure and steps to restart the

NFS servers o Using RIP disk to troubleshoot

Basic Network

Switch

Troubleshooting

Operation (i.e., how does the network switch communicate on the 89A(V)15 network)

How the switches are connected to each other both internal and external to MCEs

How data is moved from one functional segment or server to another external to the MCE. Include protocols

Switch configuration files: what they are used for and how they boot the switch