MIL-STD-3034

5. DETAILED REQUIREMENTS

5.1 RCM process. RCM is the process used to determine the maintenance requirements for new and in-service
equipment or systems. The process is composed of up to twelve phases. RCM development in structured phases
ensures that every maintenance action specified in a maintenance package can be justified in accordance with the
fundamental RCM principles used by both DoD and commercial entities.

The initial maintenance package provides the baseline for system expectations. As operational experience is
developed (failure data, inspection results, etc.), the maintenance package will be monitored and improved as
required.

RCM development shall be accomplished in phases as specified in the acquisition document. The twelve phases of
the RCM development process are:

a. Phase 1 - System partitioning and functional block diagram (FBD). Partitioning along major system and
subsystem boundaries to facilitate analysis and specify analysis boundaries (scope) and approach (see 5.1.1).

b. Phase 2 - Functional failure analysis (FFA). Analysis of the functions of systems and subsystems and of
the ways in which those functions can fail (see 5.1.2).

c. Phase 3 - Additional functionally significant item selection (AFSI). Selection of the additional functionally
significant items (AFSIs) (see 5.1.3).

d. Phase 4 - Failure modes and effects analysis (FMEA). Analysis of the failure modes and effects of failure
(see 5.1.4) of the FSIs.

e. Phase 5 - Decision logic tree analysis (LTA) (see 5.1.5).

f. Phase 6 - Servicing and lubrication analysis. Analysis of servicing and lubrication task requirements (see
5.1.6).

g. Phase 7 - Inactive equipment maintenance (IEM) task identification (see 5.1.7).

h. Phase 8 - Corrective maintenance task identification (see 5.1.8).

i. Phase 9 - Maintenance requirements index (MRI) (see 5.1.9).

j. Phase 10 - Maintenance requirement task definition (see 5.1.10).

k. Phase 11 - Maintenance procedure validation (see 5.1.11).

l. Phase 12 - Maintenance requirement card (MRC) and maintenance index page (MIP). Development and
preparation of MRCs and formulation into MIPs (see 5.1.12).

5.1.1 RCM Phase 1 - System partitioning and functional block diagram. The assigned boundaries of an RCM
analysis may encompass anywhere from a single sub-assembly to an entire subsystem. Large multi-subsystem
assignments are typically split along boundaries as defined in the Expanded Ships Work Breakdown Structure
(ESWBS) before beginning the detailed RCM analysis. This level of partitioning is typically accomplished at the
programmatic level. Care must be taken when defining what the boundaries of a single development will
encompass so that no items are forgotten or are covered within multiple developments (see figure 2). The RCM
process, as described in Phases 1 through 12, is usually performed within a boundary that encompasses at most a
single subsystem. Within this process the assigned developer(s) may still find it advantageous to subdivide the
subsystem to simplify the analysis. This hierarchical approach to dividing subsystems enables the identification of
an optimum level for the actual performance of the RCM process steps (see 6.2).

7
S o u r c e : h t t p : / / w w w . a s s i s t d o c s . c o m -- D o w n l o a d e d : 2 0 1 3 - 0 3 - 1 2 T 1 9 : 1 5 Z
C h e c k t h e s o u r c e to v e r i f y t h a t this is t h e c u r r e n t v e r s i o n b e f o r e use.