DI-PSSS-81823C

Reliability-Centered Maintenance (RCM) Class Maintenance Plan (CMP)

The RCM Class Maintenance Plan (CMP) documents the overall maintenance strategy for a ship class, including prescribed maintenance tasks, material condition assessments, and availability routines across organizational, intermediate, and depot level maintenance activities.

Approval DateNovember 9, 2023

AMSC NumberN10447

Preparing ActivitySH

Project NumberPSSS-2023-017

OPR—

DTIC Applicable—

GIDEP Applicable—

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

DI-PSSS-81823B

DI-PSSS-81829ADI-PSSS-80986BDI-PSSS-80988BDI-PSSS-80987BDI-PSSS-80990A

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Reliability-Centered Maintenance (RCM) Class Maintenance Plan (CMP) provides the overall maintenance strategy for a ship class, as well as a listing of all prescribed maintenance tasks accomplished by organizational, intermediate and depot level maintenance activities, including material condition assessment, life renewal (preventive and corrective maintenance), alterative maintenance (ship change and alteration) tasks and availability routines. The RCM CMP provides the Government the transparency into the development of the CMP to assure that it is developed in accordance with all current policies and directives.

This Data Item Description (DID) contains the format, content, preparation instructions and intended use information for the data product resulting from the work task described in 5.1.12 of MIL-STD-3034A.

This DID is related to DI-PSSS-81829A, RCM Corrective Maintenance (CM) Development Report; DI-PSSS-80986B, RCM Maintenance Requirements Index (MRI); DI-PSSS-80988B, RCM Task Definition Report; DI-PSSS-80987B, RCM Procedure Validation Report; DI-PSSS-80990A, RCM Documentation Control Sheet.

This DID supersedes DI-PSSS-81823B.

Preparation Instructions

1Reference Documents.The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.

2Format.The CMP report shall be in Contractor's format.

3Content.The CMP report shall contain all the information specified in this DID.

3.1CMP Organization.The CMP shall identify the ship class's overall maintenance program in narrative form. The plan shall also identify all data elements for each applicable configuration-based CMP maintenance requirement developed using the Reliability-Centered Maintenance (RCM) analyses process, as specified in MIL-STD-3034A.

3.2CMP Maintenance Program.Provide the ship class's overall maintenance program as defined in OPNAVINST 4700.7, Section 201.4. and Chapter 7. The overall maintenance program must be defined to properly determine applicable maintenance requirements. The overall maintenance strategy for a class shall be considered as an integral component to the CMP and provided in narrative form as follows.

3.2.1Executive Summary.Provide an executive summary that includes a narrative overview of the development of the CMP and its goals. The executive summary shall provide insight into how the CMP was formulated and the maintenance policies that affected its process and products.

3.2.2Maintenance Program Strategy.Provide a description of the overall maintenance program for the ship class over the entire ship class life to include:

3.2.2.1Salient and maintenance worthy features of the ship's design, e.g., types of propulsion systems, weapons systems, integrated combat systems, aviation launch, recovery, storage and maintenance, and strategic systems, etc.

3.2.2.2Class specific deviations from standard designs, margins, or materials with future maintenance implications, e.g., use of uncommon materials for hull or structural systems, uncommon hull forms, unusual propulsion types, non-standard construction techniques, etc.

3.2.2.3Summary of the Required Operational Capabilities and Projected Operating Environment (ROC and POE).ROC and POE features shall be mapped to important class specific equipment and their critical material condition parameters.

3.2.2.4An overview of the maintenance strategies for critical systems and equipment, specialized facilities, capabilities, and personnel.

3.3CMP Maintenance Requirement Development.Maintenance requirements (tasks) shall be condition-based to the maximum extent possible and be identified in the CMP. CMP maintenance requirements shall include Preventive Maintenance, e.g., Condition-Directed, Time-Directed, Failure Finding, Servicing and Lubrication tasks, Corrective Maintenance tasks, Alterative Maintenance tasks, material condition assessment requirements, and availability routines. Each CMP maintenance requirement shall be developed with engineered periodicities and contain standardized maintenance data to the maximum extent possible. Each CMP maintenance requirement shall contain the following data fields to relate to maintenance task information:

3.3.1System / Expanded Ship Work Breakdown Structure (ESWBS).Enter the ESWBS of the system, equipment, component for the maintenance requirement, as contained in NAVSEAINST 4790.1 (Series). The maintenance requirement shall include the ESWBS level 5 number of the equipment/component to which the task is applicable. If applicable to the entire subsystem/system, the ESWBS level 4/level 3 number shall be used.

3.3.2System / ESWBS Description.Enter the long system description for a referenced ESWBS value in 3.3.1, as contained in NAVSEAINST 4790.1 (Series). Identify the ESWBS level 5 description of the equipment/component to which the task is applicable. If applicable to the entire subsystem/system, the ESWBS level 4/level 3 description shall be used.

3.3.3Maintenance Requirement Description (MRD) - Planned Text.Enter a concise description of specific maintenance actions required for the maintenance requirement. The task description shall begin with the maintenance action verb, e.g., "Replace", "Clean", "Inspect", etc.

3.3.4Current Ship's Maintenance Project (CSMP) Summary.Enter an abbreviated version of the task description. All abbreviations shall be identified in accordance with ASME Y14.38 (Abbreviations and Acronyms for Use on Drawings and Related Documents). This field shall be in the format of "Action" - "Equipment Noun Name" and shall be limited to 30 characters. This data element shall contain the information for Block 37 of the OPNAV 4790/2-Kilo.

3.3.5Problem Description.Enter a brief narrative explanation of the maintenance problem/trigger that requires performance of the maintenance requirement. This data field shall have a 2000-character limit and shall contain information for the first portion for Block 35 of the OPNAV 4790/2-Kilo.

3.3.6Recommended Solution.Enter a narrative explanation of the maintenance required to correct the problem described, complete the scheduled task, or scheduled ship change, as applicable. This 2000-character field shall expound upon the task description and shall contain the information for the second portion for Block 35 of the OPNAV 4790/2-Kilo. The recommended solution shall include amplifying information, e.g., reporting requirements, situational requirements, and relationships with other tasks.

3.3.7Planned Periodicity.Enter the periodicity (frequency) of the maintenance requirement in months, based on information identified by the applicable RCM analyses. The periodicity shall identify the longest period between scheduled maintenance tasks selected to ensure that a predicted failure will not occur and shall specify acceptable equipment maintenance during an operational condition.

3.3.8Situational Periodicity.Enter an "R" to indicate a situational periodicity for an applicable condition, e.g., pre-deployment, dry-docking, etc. If no applicable situation exists, enter a "U" for an unscheduled maintenance requirement.

3.3.9Situational Periodicity Condition.Enter the ship specific condition, e.g., operational, maintenance event, etc. for maintenance requirements with an "R" entered in the "Situational Periodicity" field of 3.3.8.

3.3.10Recommended Maintenance Level (RML).Enter the applicable RML to identify the activity level that will perform the work for the maintenance requirement. Applicable entries shall include:

3.3.10.1D - Depot

3.3.10.2I - Intermediate

3.3.10.3TAV - Technical Assist Visit

3.3.10.4O - Organizational

3.3.11Capable Maintenance Level (CML).Enter the applicable activity level capable to perform the maintenance, if the RML activity became unavailable. The CML shall identify O, I, TAV or D level as defined in 3.3.10.

3.3.12Man-Days.Enter the number of man-days, up to five digits, required to perform the maintenance requirement based on one person working an eight-hour workday.

3.3.13Material Cost Estimate.Enter the estimated material cost to accomplish the full intent of the maintenance requirement for one equipment. This field shall be limited to six figures and rounded to the nearest dollar. The estimate shall be configuration specific and based on the corresponding Task Material List (TML).

3.3.14Maintenance Requirement Identifier.Enter a unique identifier for the maintenance requirement under development. The alpha-numeric identifier shall include search and filtering capabilities for various parameters, e.g., system, task type, etc.

3.3.15Unit Identification Code (UIC).Enter the assigned UIC value for the specific entity, e.g., ship hull, shore facility, etc. to which the maintenance requirement is applicable.

3.3.16Class.Enter the applicable ship class designation for the CMP maintenance requirement under development.

3.3.17Hull Identification.Enter the identity of the ship hull applicable to the CMP maintenance requirement under development. Hull identification shall contain the following data fields:

3.3.17.1Ship Type.Enter the ship type, e.g., "DDG", "CVN", "SSN", etc. based on the Class defined in 3.3.16.

3.3.17.2Hull Number.Enter the applicable hull number for the ship.

3.3.18Hull Name.Enter the narrative ship name of the hull identified in 3.3.17, applicable to the maintenance requirement under development.

3.3.19Maintenance Instruction Document (MID).Identify all maintenance instruction documents applicable to the maintenance requirement under development. MIDs shall contain applicable Maintenance Requirement Cards (MRC), as well as technical and design information for acceptable restoration, overhaul, refurbishment, inspection, and testing of systems, components and equipment.

3.3.20Document Type.Enter the Maintenance Instruction Document type and number that dictates the need for the maintenance requirement, e.g., NSTM, MRC, CSWT, TM, CLAD, of the MIDs identified in 3.3.19 above.

3.3.21Document Title.Enter the narrative title of the MIDs identified in 3.3.19 above.

3.3.22Maintenance Instruction Comments.Enter applicable Maintenance Instruction comments. These comments shall contain additional detailed information about the MID being used, e.g., page number, chapter, etc., as applicable. This field shall be limited to 2000 characters.

3.3.23Hierarchical Structure Code (HSC).Enter the HSC to identify the functional and hierarchical relationship of the ship, ship system, and equipment configuration records, as contained in NAVSEAINST 4790.1. The HSC shall also identify essential data organization that will be used for its efficient and effective control, display, and retrieval.

3.3.24Equipment Functional Description (EFD).Enter the EFD to identify the function performed by a specific piece of equipment within a system. The EFD shall include a full description of each unique and complete HSC.

3.3.24.1The EFD's Equipment System Designator (ESD) shall be identified at its next higher level of indenture.Each EFD shall be identified as a unique identifier within the ship's CMP database and shall be identified consistently across the ship class.

3.3.24.2The EFD shall show a one-to-one correspondence between HSC and EFD.When major equipment types are involved, the EFD identification shall begin with the identity of the major equipment, followed by the unit identity. The noun name shall be included in accordance with ASME Y14.38. The remainder of the functional description shall follow with a comma and no space. Abbreviations shall be from right to left, when applicable.

3.3.25Equipment System Designator (ESD).Enter the ESD to identify the principal system/subsystem into which a group of individual components are combined to perform a specific function. The ESD shall have a valid entry and shall be uniformly identified across the class with standardization controlled by the Configuration Data Manager (CDM). The description shall begin with the identity of the principal equipment/subsystem followed by any unit identity. The ESD shall be contained within the EFD, where the ESD represents up to the first five characters of the HSC. ESDs shall be fifteen-alpha/numeric characters and shall be specified to all data records.

3.3.26Repairable Identification Code (RIC).Enter the RIC to identify the systems, equipment, components, tools, and materials addressed by the maintenance requirement. Also referred to as the Allowance Parts List (APL)/Allowance Equipage List (AEL), this identifier shall be as contained in NAVSEA Technical Specification 9090-700.

3.3.27Noun Name.Enter the noun name to identify the component at the lowest echelon, e.g., unit, type designator, assembly, etc. having its own configuration identity. The component may have its own RIC. The noun name shall be a nomenclature description of the equipment and shall be the same nomenclature assigned to the Equipment Identification Code (EIC).

3.3.28Component Identification (COMP_ID).Enter the Component ID, employing the local numbering system used to identify equipment, e.g., Station Number: "1A BOILER", Valve Mark: "ASW 25", etc. A description of the component may be entered.

3.3.29Record Identification Number (RIN).Enter the applicable RIN to identify the ship (hull) specific number assigned to an individual RIC/APL record. RIN information can be derived from the configuration information contained in the Model Based Product Support (MBPS) Navy Product Data Management (NPDM) module.

3.3.30Location.Enter the identification of the onboard location of an installed equipment/component, and the space and location of the equipment on which maintenance was required.

4Media Requirements.The narrative portion of the CMP media shall be delivered in Microsoft Word. The CMP maintenance requirements and applicable data elements shall be delivered in Comma Separated Value (CSV) format for upload to the electronic database specified in the contract.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer