MIL-P-2453LA(NAVY)

7 May 1985
SUPERSEDING

M2L-P-24534(NAVY)
26 April 1976
(See 6.6)

MILIT~Y

SPEC1FICATION

PLANNSD NAINTENANCS SYSTEM: DEVELOPMENT OF

MAINTENANCE REQUIREMENT CARDS , MAINTENANCE
INDEX PAGES, AND ASSOCIATED DOCUMENTATION
;.

;
,.

.lhisspecificetion is approved for use by the Naval Sea Systems Commend,

.,
... . .. Department of the Navy, and is available for uae by all Departments and
A&nciea of the Departpcnt of Defense.
1.

.,.

SCOPE

and standards
1.1
~.
his
specification
identifies
the requirements
for the development and production of Maintenance Requirement Cards (MlfCS
),
Maintenance Index Pages (MIPa), and other associated documentation used with
the Navy Maintenance and Material Management (3-M) Syatema, Planned Maintenance
Syate,m(PM), OPNAVINST 4790.4, VOIUIM!1. This specification implements
Reliability C-enteredMaintenance (RCM) (ace 6 .3.33) methodology for the determination of maintenance reqplrementa (ace 6.5) and applies to all Ievela of
eyatem or equipment
grouping,and to all scheduledmeintenanc.e,
whether equipment
ia in use, ready for use, & in standby or lay up condition. This spec.
ificattOn
addreaaes the total scheduled maintenance program for a ship, trrespec.t
fve of
the maintenance
echelon
possessing the capability to perform the maintenance.;
that ia, organizational, lnter~diate, and depot level acheduledmaintenance
taska are considered. This apecification providee procedures for develOpiSSnt
of unscheduled maintenance within the PMS program. Planned maintenance eyatem
documentation shall be developed in accordance with this spec.lfieaCion. This
specification isintended for uae by PMS development activities and by ac.tivitiea
which menage, monitor, or coordinate that development.

Beneficial comments (recommcndationa, additiona, deletions) and any pertinent

data ..whichmay be of use in improving this document should be addressed to:
Commander, Naval Sea Systems Command, SEA 5523, Department of the Navy,
Washington, DC 20362-5101 by using the self-addreased Standardization Oocument
Improvement Proposal (DD Form 1426) appearing at the end Of this dOcu~nt
or by letter.
}:
i
,.
AMSC N3450
AREA MNTY

FIIL-P-24534A(
NAVY)

2.
2.1

APPLICABLE DUCUNSNTS
Government documents.

2.1.1 Specification, atandarda, and handbooka. Unless otherwise specified, the following specifications, atandarda, and handbooka of the issue 11sted
in that issue of the Department ofDefense Index of Speciflcationa and Standards
(DoDISS) specified in the solicitation form a part of this specification to the
extent epecifled herein.
SPECIFICATIONS .
MILITARY
MIL-H-38784
MIL-P-38790

- Manuala, Technical: General Style and Format

Requiremanta.
- Printing Production of Technical Nanuals:
General Requirements for.

STANDARDS
MILITARY
MIL-STD-12

- Abbreviations for use on Drawings, and in Specificationa, Standards and in Technical Documente.
MIL-STD-17-1
- Mechanical Symbols (other than Aeronautical,
Aaroapacecraft and Spacecraft Use).
MIL-STD-17-2
- Mechanical Symbols for Aeronautical, Aeroapacecraft and Spacecraft Use.
MIL-STD-1364
- Standard General Purpose Electronics Test
Equipment.
MIL-STD-1388-1 - Logistic Support Analyais.

I
NANDBOOKS
MILITARY
MIL-NDBK-267

- Guide for Selection of Lubricenta and Hydraulic

FluIda for Use in Shipboard Equipment.

2.1.2 Government documents, drawinga, and publications. thefollowing

Government documents, drawings, and publications form a part of this specification to the extent specified herein.
OEPARTNENT OF DEFENSE
DOD 5220.22-M - Industrial Security Manual for Safeguarding
Claaaified Information.
DEPARTMENT OF NAVY
OPNAVINST 5513 (SERIES) - Security Classification Guides.
NAVAL SEA SYSTSMS COWMAND (NAVS.EA)
0900-LP-09S-6010 - Ship WorkAuthorization Boundaries for Surface
Shipe.
0938-LP-011-4010 - Nuclear Powered Submarines Controlled
Atmosphere.

MILP-24534A(

NAVY)

STOOO-AA-IDX-010/PEETE - Electrical/Electronic Test Equipmant .Index

for Support Requirements of Shipboard
Electronic,Electrical, IC, Weapons, and
Reactor Syetems.
OP 1700 - Volume 1
- Standard Fire Control Symbols.
OP 1700 - Volume 2
- Standard Fire Control Symbols for Underwater Ralated @antities.
OP 1700 - Volume 3
- Standard Fire Control Symbols for !tisaile
Related Quantities.
OD 3000
- Lubrication of Ordnance Equipment.

NAVAL SUPPLY SYSTEMS COMMAND

NAVSUP PUBLICATION 4400 - M lost Shopping Guide.
CATALOGING NANDBOOK H4-2 - Federal Supply Code for Menufacturera,
Code to Name.
NAVAL PER.$ONNELSYSTEMS COMMAND
NAVPERS 18068D - Manual of Navy Enlisted Nanpower and Personnel
Classifications and Occupational Standarda.
UNITED STATES,GOVERNMENT PRINTING OFFICE
United Statea Government Printing Office (GPO) Style Nanual
(Application for copies should be addreaaed to the Superintendent of
Documents; Government Printing Office, Washington, DC 20402.)

~,
I

m
;.

(Copies of specificatione, etandarda, handbooka, end publications required

by contractor in connection with specific acquisition functions should be
obtained from the contracting activity or as directed by the contracting officer.
2.2 Other publications. he following documents form a part of thie
specification to the extent specified herein.
AMERICAN NATIONAL STANDARDS INSTITUTE (ANSI)
Y 14.15 - Electrical and Electronica Diagrams.
Y 14.15A.- Interconnection Diagram@.
Y 32.2
- Graphic Symbols for Electrical and Electronic Dlagrama.
Y 32.14 - Graphic Symbols for Logic Diagrama (Two State Devicas).
Y 32.16 - Reference Deaignar.ionsfor Electrical and Electronlca
Parta and Equfpmenta.
(Application for copies should be addresaed to the Americ8n National
Standarda Institute, Inc.,1430 Broadway, New York, NY 10018.)
2.3 Order of precedence. In the event of a conflict batween the text of
this specification and the references cited herein, the text of this apeclfication shall take precedence.
.3.

I
,

3.1

using

the

REQUIREMENTS
Maintenance

requirements.

RCM methodology

in

the

Maintenance
requlremente

requirements

investigation

shall
process.

be developed

MIL-P-24534A(NAVY)

3.2 Development coordination. The acquisition documants (see 6.3.1) for

each PMS development shall include the name and address of the PMS Coordinating
Activity (see 6_.2.
1 end 6.3.30) which will coordinate the development and preparation of the PMS docu=ntatiOn.. fie deaignitiOn Of this activity will be ~de
by NAVSEA.

3.2.1 RCM methodology. The followlng flow.diagram depicte the basic

relecionship between the Planned Maintenance Syetem Development Activity (PNSDA)
(see 6.3.26) end the PMS Coordinating Activity for development ueing the RCM
methodology in the requirements investigation process (see 6.3.34).

lWNCllON&
FAILIE
ANALYSIS

F=WlllA&LY 1
llCMSELE~

I I

RWISWANl
AFWWAL

MAIWTENAMS
REWREMENTS

TASK0EFWlW4

SWSOUEO

I
I
I
I

MLL-P-24>34A(NAVY)
-...

3.3 Planned maintenance system developer qualification. In addition co

technical
..qualifications.
,. Dersonnel develor.inzPMS documentalion shall be
qualified in MIP and MRC development (see 6.3.7) techniques. Techniques
shall include method study and work measurement procedures taught by NAVSEACEN,
or in an equivalent ,cotiercialck.uraeapproved by the PMS Coordinating Activity.
..

3.4 Security classification. The security claaaification of materials

to be used in KRC develbpmeritehall be governed by the applicable enclosure of
the OPNAVINST 5513 series security classifIcation guidea. The applicable
enclosure of the OPNAVINST 5513 aeriea is basad upon program, project, waapon
or ship for which HRC cards are being prepared. Security clasaificatton shall
be based Dn data actually extracted for the MRC card rather than the overall
clasaification c.fthe source documsnt. Inquiries concerning appropriate security
classification or.markings ahOuld be referred tO the COMNAVSEAsySCOM (SM 09B2).

3.5 Goverrueent-furniahadmsterial. The following msteriala, when required

to produce deliverable items specified in the acquisition document, will be
supplied aa Government-funished msterial.

(a) Master Systemaand Subayatema Index form (sac figure 1).

(b) Functional Failure Amalyaia form (eee figure 2).
(c) Mditional Functionally Significant Items Selection form (ace
figure 3).
Functionally
Significant Iteme Index form (see figure 4).
(d)
(e) Failure Modes and Effects Amalyeia form (ace figure 5).
(f) Logic Tree Analyaia form (ace figure 6).
(g) Servicing and lubrication Analyaia form (sac figure 7.).
[:] Maintenance Naquiremant Index form (ace figure 8).
faakDafinition form (eae figure 9).
(j) RCM Documentation Control Sheat (ace figure 10).
(k) Inactive Equi,pmantMaintenance Requirement Analyaia form,
(ace figure 11).
(1) Procedure Evaluation Sheet (aee figure 12).
(m) Maintenance Indax Page (MIP) form (see figure 13).
(n) Meintemance Index Page (liIP)continuation form (see figure 14).
(0) Naintenanca Requirement Card (NRC) form (ace figure 15).
(P) Maintenance Requirement Card (MRC) continuation form (ace
figure 16).
Requirement Card (MitC)centinuation page foldout
(q) lf.sintenance
form (aae figure 17 and figura 17a).
(r) NRC Quality tisurance Check Sheet (see figurea 18, 18a and 18b).
3.6 Requirements investigation proceaa. I%e requirements Investigation
proceae utilizaa maintenance task analyeie that shall determine the nervicing
and testing requirements neceeaary to maintain tbe system and equipmant in a
condition which will allow it to perfDrm within performence atandarda. The
scheduled maintenance task analyaia shall identify and justify required maintenance actiona and periodicities of accomplishment. Organizational, intermediate anddepot levels of scheduled or unscheduled maintenance requirements
may result from the analysis.process. Other maintenance analyaea which identify
maintenance requirements meeting the criteria of 3.6.1 may be substituted upon
approval of the PMS Coordinating Activity.

MIL-P-24534A(NAVY)

3.6.1 Scheduled maintenance requirement criteria. The development procedurck ahnll

,.. result in KSCS that meet the following criteria:
(a) Describe the minimum maintenance (see 6.3.27) for accomplishment
by maintenance personnel.
(b) Ensure system or equipment operation is within performance
standards and established readiness criteria.
Provide maintenance procedures that are not redundant with lower
(c)
level procedures at as high a level as possible (ace 3.6.5).
(d) Provide maintenance proceriureathat can be eafely conducted
while system or equip-nt ia operating in a functional mode.
3.6.2 P1.eintenance
ob.jectivea. The process described herein ia designed
to meet the following objectives:
(a)
(b)

Preservation.of the inherent design levels of reliability,

performance, and safety.
AccOmplish~nt Of this preaervatiOn a! the dnimum practical
costs (in terme of system.downtime, manpower, toole, materials)
based on the criteria of the user.

3.6.2.1 Maintenance objectives criteria. To meet these objectIves, the

following principles must be recognized:
(a)

Only engineering design c~nges can cOrrect deficiencies in

the inherent levels of safety and reliability.
(b) Any maintenance program et its .&at can only prevent deterioration of the inherent levels of safety and reliability achieved
through design.
(c) Maintenance plan determination ia c~Oaely related to overall
logietic eupport and to other syntem engineering disciplines such
as reliability, maintainability, aafety, ataudardization, human
Efficient maintenance planengineering, and training program.
ning requires input from and output to these related disciplines.

3.6.3 Teak selection criteria. Scheduled maintenance taaka ehould be

performed only vhen such tasks.will prevent a decrease in reliability, a loss
of miaaion capability, n deterioration of aafety to umecceptable levels, or
when the taaks will significantly reduce the life cycle cost of ownership of
the item (ace 6.3.23). Tasks will ba time directed (TD) (see 6.3.39), condition
directed (CD) (see 6.3.5), failure finding (FF) (see 6.3.14). Figure 19.illustrate the specific selection criteria for each task.
3.6.4 Structured approach. The methodologies shall accomplish the
followimg:
(a) Identify functions (see 6.3.17) prOvided by all ships syate=.
(b) Identify functional failure(s).
(c) Identify dominant feilure modes (see 6.3.15) causing these
failures.

MIL-P-24534A(NAVY)

,-

,,-..

(d)
(e)

~~
(f)

(g)

3.6.5 ~stem approach to maintenance requirements investigation and

development. The methodologies provided in this specification will uae a
system approach. Judgment will be based for selecting a maintenance requirement (fflt)
on:
(a)

Select and justify applicable and effective preventive maintenance tasks (see 6.3.31),for operating equiptrent.
Select and justify applicable and effective maintenance for
inactive equipmsnt.
In the absence of applicable (see 6.3.3) and effective taska
(ace 6.3.11) to prevent safety related failures, make a
recommendstion for a deaign change.
Identify unscheduled maintenance requirements.

(b)
(c)
(d)

Saverity of the effacte of the failure (see 6.3.12) for which

the task is designed to detect or prevent.
Capability of tha task to achieve the desired results.
Criticality of the.systema function.
Cost effectiveness of the task to the user.

Functional eystem hiearchiee provided by the Ship Work Authorization Boundary

(SWAS) ayatem, NAVSSA O9OO-LP-O98-6O1O, shall be utilized in determining what
conatitutea a given ayatem. Tha SWAS ayatam haa been selected for this purpose
bacause the configuration and logistic support data baaes for ahips are alao
atrwctured under the SWAB ayatem. Any changea considered necaaaary must be
approvad by the applicable Naval Sea Support Center. The SWAB ayatem deacribem
five levels of aystam identification, raferred to aa SWAS Iavela (ace figure 20).
or functional grouping. The eight major
3.6.5.1 SWAB level 1 - kfaj
functional groupa are:
SWAS

NAJOR FUNCTIONAL GROUPING

100

Hull Structura Group

Propulalon Plant Group
Electrical Plant Croup
Command and Surve11lance Group
Auxiliary Croup
Outfit and ?umiahinga, General
Armamant Group
Integration/Engineering

200
300
400
500
600
700
Soo

3.6.5.2 SWAB level 2 - Integration/Et@neering functional aubgrouPinE of

systems. This level groupa ayateme which operate together to,contribute to a
more apecific functional araa than described at SWAB level 1; for example:
200
230

Propulsion Plant Group

Propulsion Units

HIL-?-24534A(NAvY)

3.6.5.3 ..
SWAE level 3 - System and elements. ~is IeVeI groups SYSCeMS
and elemaqts ,togecher
.at.amore specific functionalbreakdown; for example:
,,,. ..
., .,,.,.~

200
Propulsion.
Plant_CKobp
230 . .
Propulsion Units
234
Propulsion &s Turbines

..*

3.6.5.4 SWAE level 4 - Subsystem or subelement. This level describes a

group of subeystem or subelemnte opereting together to perform a specific set
of functions for the system; for example:
200
230
23k
2341

Propulsion
Propulsion
Propulsion
Propuleion

Plent Grnup
Units
Gas Turbines
Gas Turbinee, Uein

3.6.5.5 SWAS level 5 - Components end equiprient. fhinlevel describes a

component or group of components designed to perform a eet of specific functione
for a eubsyatem or aubelenent; for example:
200
230
234
2341
2341N0

Propulsion Plent Group

Propulsion Units
Propulsion Gas Turbines
Propulsion Gas Turbines, Nain
Nozzle, Fuel, LN2500 Gas Turbine

.3.6.5.5.1 Gomponent Dictionary Codee (CDC). The last two characters of

the level 5 KWAB number are the CDC for the item. The CDC ie aeslgned by the
NAVSEACEN Ship Equipment Configuration Accounting System (SECAS) (eee 6.4) to
identify level 5 components and equipment.
3.6.5.6 Initial assignment for development. The aaaignment of syeteme for
development will be made at varioua SWAE levels. Further top down breakdnwn
partitioning shall be done by the PMSDA aa part of the investigative process in
phase 1 (see 3.7.2). If the acquisition docunw.ntspecifies a single equipmnt
for development, the partitioning and functional failure analysie phaees of the
requirements investigation proceseea will be bypaseed. Develop=nt will begin
with the functionally significant item selection, phase 3.
3.7 RGM development. RCM development shall be accomplished in phases as
apecified in the acquisition document (see 6.2.1). Each phase of the RCM
development ia as follows:
(a) Phase 1 - partitioning of each SWAS group Into ayeteme and
aubsyatema for further analysis and spacific definition of
boundaries and contents (see 3.7.2).
(b) Phase 2 - analysis of the functions of systems and subsystems
and of the ways in which thoee functions can fail (see 3.7.3).
(c) Phase 3 - selection of the additional functionally significant
items (FSIS)
(see 3.7.4 and 6.3.18).
(d) Phase 4 - analysis of the failure modes and effects of failure
(eee 6.3.13) of the FSI (see 3.7.5).

MIL-P-245-4A(NAVY)

(e)
(f)
,,,.
.,.,
.,
.,
.,,,.

(g)
(h)
(i)
(j)
(k)
(1)

Phaee 5 - decision logic

ae analysis (see 3.7.6).
Phase 6 - analysis of se. ,icing and Iubrication task requirement.e (see 3.7.7).
Phaae 7 - preparation of an index of MR determined nacesaary
and justified In phasea 5 and 6 (see 3.7.9).
Phase 8 - &thod study and procedure evaluation of tasks not
already coverad adequately by existing MRCS (ace 3.7.10).
Phase 9.- detsileddefinition of taaks (see 3.7.11).
Phase 10 - datarmination of inactive equipment maintenance (IEM)
requirements (bee .3.7.12).
Phaae 11 - determination of unscheduled maintenance requirements (see 3.7.13).
Phase 12,- prepsration of MRCS and formulation into MIPs (see
3.7.14, 3.11 and 3.12).

Forms specified herein shall be completed for esch phase of the analysis to
provide a complete development package for the system in accordance with the
data ordering document apecified in the acquisition document (see 6.2.2).
Devalopmsnt forms will be either typewritten or hand printed with a black
ballpoint pen. Camera raady copy data shall be typewritten.
3.7.1 Direction of twalve phase analysis. The distribution and review of
any existing PMS documentation before phase 6 of the analyaia shall bs prohibited.
~ia process la daaigned to be an objective determination of maintenance needa of
the ayatem based on facta, not a legalization of paat practicea.
3.7.2 Phasa 1 - Functional block diagrams and partitioning. The developar
shall aecura or prepare functional block diagrams, including interfaces. Tha
developer shall .&iuate these diagrams and partition the group to any lower
levels required to facilitate analyaia. These levels shall include at laast
AN nomenclature/MK, MOD/APL/RIC/CID on the diagrama. The level of partitioniog
shall be commensurate with the relative functional complexity of the group and
nwmber of equipment or components. Baaed upon tha partitioning, the developer
shall prepare meater system and Sub System Index Form (ace figure I). Subsequent
phaaea of tha analyais shall idantify apecific functions, define the failurea
of those functions, and determine the fallure modes and their effacta at the
leval where the failure occurs through the system level. The daveloper shall
ultimately determine if there la an applicable and effective task that will
pravent or detect functional failure. It is not beneficial or effective to
partition the group to a leval at which tasks will not be ganerated by aubaequent analyaia~ Erichsystem in the group shall be covared by one or more MIPa
at the discretion of the PUS Coordinating Activity. Taake generated aa a
result of.the analyaia may be directed at failure moda6 originating at leVel 5
(equipment and component)or below.

ML-P-24534A(xAvY)

3.7.2.1 Functional block diagram preparation. The format of the functional

blo,ck~@&x,.s~st@l ,b~
OT~~lY b~<ty~$~s
t~~ctive (gp~ f$gure 21). When approved
b! the PUSC@rdlp,nt:?g.~t+!l+fy, TYBt.ern,,
.qch?,vyg
ice .QF~~e
d~avlngareproduced
fr. appropriate
technic+!m$?nua~
or a,hip
inforq?tioi
-boo~a,
may be used with
aPPlicq.ble@ditiOna and nnnot.atione.
3.7.2.1.1 Functional block diagram contents. The functional block diagram
shall display all components of,the iyst?.ti,
their functional relationships to
one another, and in and out interfacea with other aygterne. @nerally, some
components of a system, although identified separately, may actually be grouped
together to form higher assemblies. Assemblies may be appr~priately labeled aa
a single box o.qche functional block diagr~.
Label components and aaaemblies
in the nyate,rn
by their co.mtpon
namg, including generic,n=,
MC, MOD, and AN
nomenclature or ocher identif.fer. Hardware such as .awitchboardaor valve manifolda, that are n,ot,
actually part of tbe .ayetemuder analysia, may be included
to @ tmplif
y the diagram and to enhapce rneaningf
ulw?ss. Suchhardwaremay ba

jdentif
ied by deecrip.tor
Qr .ncymclatu.re
lnch+ling
aaa!~~d SWABnumber.
.
3.7.2.1.2 Connections
and interfaces.The components
and asaembliea
of a
systemare connectedto eacho,ther
and interface
withochereyatemsthrough
electrical,
fluid, gaa, or mechq,nicallinkages. Linkages on the functional
block diagramshallbe aho,wnas heavy l$nes. Each co~riecti~nshall identify the
connation and the normal parameter value or range of valqea. In addition to
para=ter labels, interface connections shall be labeled with the SWAB number
of the ayatam, eubayatem or equip~nt from which the connection originates or
which receives the out interfa:es. Flow directional arrova shall be required
on connection lines.
3.7.2.2 Canpleting the master aysteme and aubsystema index. The Mater
Systeme and Subayateme Index form, (ace figure 1), is the key index to the
functional ayatem analyaia and ehall be prepared and completed as follows:
Block 1 - SWAS group number. Enter the SWAB group level 1 number,
a three-digit number containing two zeroes and the associated
nomenclature.
Enter the associated group nomen(b) Block 2 - Group nomenclature.
,
clature.
(c) Block 3 - Ship class. Enter the ship claae and the hull number
on which the analyeie la baeed.
[:] Block 4 - Prepared by. Enter the analysts name and the date.
Block 5 - Reviewed by, Enter tbe firat level reviewera nama
and the date.
(f) Block 6 - Approved by. Reserved for PMS coordinating activity
approval signature and date.
Block
7 - Revision. Enter ORIGINAL, or A, B, or C, sequentially,
(8)
and the date.
(a)

10

t41L-P-24534A(NAvY)

..
m

.. ..

(h)

(i)
(_l)

Block.8 - SWAB subgrouplsyatemfsubsystem number. Enter a number

identifying each subdivision through SWAB level 4. If the level
4 SWAB number cannot uniquely identify a subsystem, add a suffix
number to the level 4 SWAB number and use this throughout the
analysis.
Block 9 - Subgroup/system/subsyetem nomenclature. Enter the
nomenclature of each SWAB subdivision identified.
Block 10 - Serial number. Enter a serial number for thie form
as follows:
(1)

(2)

(3)
(4)

Segment 1 - enter the developing organization abbreviation,

followed by a slant (/).
Segmmt 2 - for developara, enter the development authorization number, followed by a slant (/); for other davalop=nt activities, asaign a development number, folloved by
a slant (/).
Segment 3 - enter the number 114 to indicate the F!aater
System8 and Subaystema Index form, followed by a slant (/).
Segment 4 - enter the highest indenture level (eee 6 .3.21)
SWAB for the development group assigned. If an entire
,groupin aasigned, this number ia.a level1 SwABnumbera three-digit number containing two zeros; for axample,
100, 200.

3.7.3 Phaae 2 - Functional failura analyais (FFA). Upon diraction frOm

the PMS Coordinating Activity. the developer shall perform the ayntem FFA and
documant the analys~a on the-PFA form (eee figure 2) for each Of the sYa~e~
and subayatema identified in phaae 1.
3.7.3.1 Purposes of the FFA.
document:

IheFFA ia performed to determine and to

(a)

A functional description of the ayatem and aubayatem including

protective features, installed monitoring and taating devicas,
redundancy provided, and any othar information associated with
the maintenance neada of the ayatem and visibility of failures.
(b) The definition of the epecific funccions of the ayatem.
(c) The definition of the interface of the system or subayatem with
other syatens.
(d) The definition of the functional failures of the system or
aubayatem.
3.7.3.2 Preparation gufdelinea. One FFA shall be required for each sub_
division identified in phase 1 and listed on the master ayetema and subsystem
index. If a ayatem in simple, only a single FFA shall be tequirad. The PFA when
complatad, shall describe the characteristic (see 6.3.4) of the system that must
be considered for potential preventive maintenance taaks. If a aystam Includeg
several relatively
complex subsystems, an FFA shall be required for the system
and for each subsystem. Only those elements unique to the system shall be
included in the syetem FFA. The functional block diagrams from phasa 1, technice~
anuals, and other pertinent references shall be !Isudas the basis for the FFA.
6

11

MIL-P-24534A(NAVY)

.3.7.3.3 Order of operation. ,The purpose of the analysis is to identify

potential sources of functional fail.[res. The FFA shall collect sufficient
information for the analyst to decide which items, if any, should be separately
selected as FSIS. The FFA requires a brief narrative description with emphaais
on asintenance needs. The FFA includes specific identification of deeign
feature.ethat provide mitigation of failure effects, such as redundancy, protective devices, and fail-safe features. It also Includes specific identification of deaiKn features that make evatem condition and maintenance needa visible:
for example,-built in test equipwn~ (BITE), and system Indicator.
3.7.3.3.1 Functions. A aystam msy provide a function (ace 6.3.17) by
providing information, providing flow and pressure of a fluid, nr converting
etored energy to motion. Functions of this type are called active functionsbeceusa they require activity nf the system. Loas of, or degradation of,
that activfty la a functional fallure. A ayatem my also provide a function
by not doing something, such as a tank holding fluid. Functions Of this tYPe
are called pasaive functions because they are inactive. An activity such
as a leak in the tank is a functional failure. When a function fails, alarma
or performance of the system may alert the operating crew immediately that the
function has @en lost. This type nf functinn is called an evident or visible
function eince ite loss 16 visible to tha crew. Functions, that give no
immediate indication that they have failed are called hidden functions. For
hiddan functions it is necessary to perform some special procedure to see if
the function la available. In a combatant ship, some systems are infrequently
used. The functions nf these infrequently ueed systems are hidden functions.
Some ayateme have co-functions, which are functions that are physically or
environmentally closely aasociated~ Failures in one function will adveraely
affeet other functions, even though these functions are normally independent.
All functions of the system shall be determined and documented.
3.7.3.3.2 Redundancy. Some degree of redundancy (see 6.3.32) msy have
been designed into the system. This level of redundancy was created to provide
inr.raasedavailability. Redundancy,exiats when the function can still be
obtained in the quality and quantities required after subsystem or equipment
fallure.
3.7.3.3.3 Interfaces. Systems usually receive input from other systems
and provide output to other eystems. Loss of input can cause a failure in
the system and 10BS of output can cause a failure in other systems. System
incerfa.ceaare addresaed separately in the FFA process because they are easily
overlooked and vary widely for different configurations of the same basic system.
In interfaces shall be aeaumed to be available. @t interfaces shall be
treated aa functions.
3.7.3.3.4 Installed safety devices inclusion. If safety or protective
devices, such aa circuit breakere, overloads, relief valves, or othar are
installed in a system, that system shall have a function to protect itself
and tha crew. These devices are easily overlooked because of their high
reliability; however, they shall be identified and documented as functions of
the system (see 6.2.1).

12

--

MIL-P-2&534A(NAVY)

3.?.3.3.5 Functional failures. A functional failure exists when a ayetem

or subsystem ceaaea to provide a required function: whether the function is
active (ace 6.3.2), passive (see 6.3.29,)
, evident, or ,hldden(see 6.3.20). The
definitionof what constitutes a failure ia of primary importance. Whenever 8
faflure is defined by some level of performance, condition,or dimension, the
appropriate standards must be stated to provide the basis for establishing
whether a failure has occurred. Where applicable, these definitions of failures
in terms of system parameters or performance atandarda are required. When
definin~ functional failures of functions orovided bv redundant items. the
failure-shallbe clearly defined as a fallure of all redundant items.
3.7.3.4 Completing the FFA form. The FFA form (see figure 2) shall be
completed as follows:
(a) Block 1 - SWAB number. Duplicate each entry in the Master
Systems and Subsystem Index form, block 8.
(b) Block 2 - N~encl~ture. Enter the nomenclature used on the
Master Sy.vtemsand Subsystems Index form, block 9, for the
selected ay.stemor aubsy.etem.
(c), Block 3 - Ship cl.as9.Duplicate the entrieA on the flaster
Systemsand Subsystems Index form. block 3.
(d) Block 4 - Prepared by, block 5 - Reviewed by, block 6 - Approved
by, block 7 - Revision. See inatructiona for the Master Syatema
and SubaYstemc Index form in 3.7.2.2d. throuzh 3.7.2.2x.
(e) Block 8 --Sources of Information. Enter the drawing, manual,
document and report numbers. Enter titles of reference material
actually used in this analysis.
(f) Block 9 - Description. Referring to the block diagram prepared
in phase 1, enter a brief physical and functional description
of the aubdivialon. Focus on what the hardware is and what
it doee, oriented toward preventive maintenance rleeds. After
this narrative, document the following IIpecif
ic information
about the syac.&, using che format below (pnrenthetteal statement describe the information to be documented):
(1) REDUNDANCY: Enter NONE or deacrlbe the redundant relationship.
(2) PROTECTIVE DEVICES: List the protective devices and the
circumstancesunder which they operate; for example, CIRCUIT
BRSAICER- 30 AMP, CASING RELIEF VALVE - LIFTS AT 150 POUNDS
PER SQUARE INCN (lb/in2), RESEATS AT 135 (lb/in2).
SNETY
FEATURZS: 0e6cribe special safety features such .99
(3)
interlocks.
(4) FAIL SAFE OR VNSAFE FEATURES: State whether system is fail
safe or unsafe; describe any fail safe features.
(5) CONDITION INDICATO~ : Document TYPE.INDICATES, and TO
UNOliin a single group for each indicator.

13

I
.

.. ,,.,. :; ..;

MIL-P-24534A(NAVY)

(6)

(7)

(8)
(9)

a. TYPE: EnterGACE, THERMOMETER, NETER, SITS, INDICATOR

LIGHT, AUDIBLE VISUAL ALARMS, & appropriate.
b. INDICATE5: Deecribe what the indicator tells about the
nystem.
c. TO WHOM: List the watch etaticm or the title of the
operator who observes theindicator. Specify the
conditions when that scetion 1s manned.
ENVIRONNENT: Oeacribe che environment co which the system
1s expoecd; for example, EXPOSEO TO UEATHER, EXPOSED TO
HIGH HU14101TY,EXPOSED TO HIGH HEAT, or other.
DUTY CYCLE: Oescribe the particulars of normal operational
practicee and estimated operational time per year. For
example, THE SYSTEM IS NORMALLY ON LINE U3iENUNDERWAY AND
IS AUTOMATICALLY CONTROLLEO. AIR CONPFL5SSORS
CYCLE ON AND
oFF UNDER CONTRDL OP ASSOCIATED RECEIVER PRSSSUBJ SWITCffiS..
COMPRMSORS RUN ABObT 250 HRS A YEAR, OEPENDING ON DEMAND.
USE KESTRICTIUNS: Enter any special restrictionson the
operation of che system; for example, cannot be safely
activated in port.
SPECIAL MAINTENANCE FEATURSS: Oescribe any special provislone

for

maintenance

installed;

for

example,

system

in

equipped with external teat connections enabling full

diagnostics while on ~ine.
of
(g) Block 10 - Functions and out interfaces. Enter a description
funeciona of che ayscem. Include self or crew protective features, out interfacesand all co-functions. State minimum
operational function parameters or performancestandards if
appropriate. Number funcctona sequentially;for examp~e, 1,
2, and 3.
(h) Block 11 - System in interfaces. Enter sources of input and
cricical values. Specify ch.sSWAB number for each _source.
(i) Block 12 - Functional failures. Enter the definiclon of what
conacicuces a failure for each funcclon and output interface
listed in block 10. There nay be several functional falires
for each function; all functional failures must be identified.
failure i.1, 1.2, 1.3; 2.:, 2.2, and
Nmber each functional
2.3, to correspond co the function number in block 10.
(j) BlOck 13 - Serial number. Enter a four-segmentseriai number as
follows:
(1) Segment 1 - see 3.7.2.2j(l).
(2) Segment 2 - see 3.7.2.2j(2).
(3) Segment 3 - enter che number 116, indicatingthe FFA form,
followed by a slant (/).
(4) Segment 4 --enter the SVAR number from block 1.
3.7.4 Phase 3 - Additlonai FSI Seiectiolland FSI index. The developer
shhll prepare the Additional FSI Selvccion forms for items considered ta be
canal
idate.+for selection as addirionai FSIS. After preparationof these
.AddtcionalFSI select tan. forms, che developsr shall prepare an inaex iisting
all

FSIS.

MIL-P-24534A(NAVY)
.
a

3.7.4.1 Preparation guidelines. Items listed on the Master Systems and

Subsystem Index are FSIS. Others will be selected by this analysia. Equipment
and repairableor rer)laceableassemblies are potential candidates. In the case
of simple systems, s~metimea St is practical to consider an entire system aa the
only FSI. Ultimately, a failure modes and effects analysis (FMEA) will be
required for each FSI. Functionally significant items should be selected at
such a level that the FMEA ia meaningful and simple. Careful review of the
system block diagram ia required to determine which Of the following apprOachea
will be used.
(a)
(b)

.
(c)

A ahgle PSI for the entire ayatem,

Functionally significant items aaaigned at aubaystem and aYate~
levels but not to equipment or other aasembliea,
Functionally significant items aaaigned at equipment and a.vaembly
level and subsystem and system levels. This approach permits
hybridsolutions; for example, relatively few equipments may
be considered for selection aa additional FSIa. The functlOne
and failurea of items not selected as additional FSIa are
comaidered in the analysis of the related aubaystem..

3.7.4.1.1 Method for additional FSI eelection. After chooatng the approach.
an Additional FSI Selection form,.(see figure 3) shall be prepared for each
candidate PSI.

3.7.4.2 Functionally significant items selection proceaa. The FSI

selection uroceaa fdantifies items other than the entire system or aubayatem that
=rit sepa~ate analyaia becauae of their Importance or complexity. Thla proceaa
determines and documents a brief description of the candidate FSIa similar to
that prepared in system and subsystem FPAs. The functions and functional
failurea of the FSI are determined and listed specifying values of parameter or
performance atandarda where applicable. A series of yea or no questions, based
on the analyats judgment of the FSI in question, are used to datermine the
validity of the analyata decision.
3.7.4.3 Cmmpletlng the additional FSI selection form. The Additional FSI
Selection form (ace figure 3) shall be cOmpleted aa follOwa:
(a)

(b)

Block 1 - SWAB number. Enter the SWAB number for the FSI
candidate. If the candidate Is below level 4 and does not
have a unique SWAB number, add a suffix number to the level 4
SWAB number and use this throughout the analyaia.
Block 2 - Nomenclature FSI candidate.
Enter the nomenclature
of

(c)
(d)

the

FSI

candidate.

Block 3 - Ship claas. Duplicate the entries on the Master

Systams and Subsystems Indax Form, block 3.
Block 4 - Prepared by, block 5 - Reviewed by, block 6 - Approved
by, and block 7 - Revision. See instructions for Maater Syatema
and Subsyatema Index form in 3.7.2.2d
through 3.7.2.2u.

15

MIL-P-24534A(NAvY)

8 - Description.
Enter a brief.functional description of
this item keyed to ite maintenance needs and provisions for tnain~,
.., tenance.:Identify redundancies, interface, BI~, and idicatOr&
including what they show about thesystem:
.r. . --.
. to whom. onerator
or watch title, re~ponaibilities, and conditions of manning the
station.
(f) Block 9 - Location. Enter the compartment numbers of spaces
where this item ia located.
(g) Block 10 - Quantity. Enter the quantity of items installed in
this system.
(h) Block 11 - Function(a). Enter definitions of the functions of
this item; number sequentially 1, 2, and 3. Under the Impact
coluam, block ha, enter a YES or NO in answer to the question,
Areany of these functione neceaaary for safety, mobility, or
miaaion?
Block 12 - Functional failurea. Enter the definitions of the
(i)
failure for each of the functions listed in block 11. Number
each 1.1, 1.2, 1.3; 2.1, 2.2, and 2.3 corresponding to the
appropriate function. Under the Impact column, block 12a, enter
a YES or NO in anawer to the question, Doany of these failrea
have a direct adverse impact on safety?
(j) Block 13 - Reliability. Under the Impact colunm, block 13a,
enter a YES or NO in anawer to the question, 1sthe eetiwted
corrective maintenance rate greater than 1 a year?
(k) Block 14 - Coat. Under the Impact column adjacent to block 14a,
enter a YES or NO in answer to the queetion, Ia this iteme
purchaae cost greeter than $5,000?
Block
15 - Maater FSI index transfer. If there la a YES in the
(1)
Impact column for any block (ha through l.is),enter YSS.
(m) Block 16 - Serial number. Enter a four-segment aerial number ae
follows:

(e)

Block

(1)
(2)
(3)
(4)

Segment 1 - aee 3.7.2.2j(l).

Segment 2 - aee 3.7.2.2j(2).
Segment 3 - enter the number 117, indicating the additional
FSI eelection form, followed by a slant (/).
Segmant 4 - enter the SWAB number from block 1.

3.7.4.4 Nonsignificant items. Items not selected aa FSIa will not be

given further item level analysia; they will be considered aa part of a higher
level PSI.
3.7.4.5 Preparing the FSI index. The FSI Index form (ace figure 4) will
ba completed aa follows:
(a)
(b)

BlOck 1 - System/aubsyatem SWAB number. Enter the highest level

SWAB number to be covered by the index.
Block 2 - System/subayetem nomenclature. Enter the associated
eyatemlsubeystem nomenclature for the SWAB number specified in
block 1.

16

MIL-P-24534A(NAVY)
.r

(c)

..0

,..,
(d)

(e)

(f)
(g)
(h)
.

Block 3 - ShipC1866. Enter the ship class and hull numbkr

to which the analysis applies.
Block 4 - Prepared by,.block 5 - Reviewed by, block 6- Approved
by, block 7 - Revision. Ses instmctions for Master Syete~. and
Subeysteme Index form, in 3.7.2.2d through 3.7.2.2g.
Block 8 - SWAB number. Duplicate the entry on each FFA form,
block 1, or AdditionalFSI Selection form, block 1, as applicable.
Block 9 - Nomenclature. Duplicete the sntry on esch FFA form,
block 2, or Additional FSI Selection form, block 2.
Block 10 - Location. Duplicate the entries in block 9 of the
Additional FSI Selection form for the item (equipment only).
Block 11 - Serial number. Enter a four-segment serial number
as follows:
(1)
(2)
(3)
(4)

f,
a

Sepnt
1 - eee 3.7.2.2j(l).
Seg~nt 2 - eee 3.7.2.2j(2).
Segment 3- enter the numbsr 118, indicating the FSI Index
form, followed by a slant (/).
Segment 4 - SWAB number from block 1.

3.7.5 Phase 4 - PMEA. Upon direction from the PMS Coordinating Activity,
the developer shall perform an FMEA and complete a form for each FSI identified
and approved in phaee 3. AriFMEA shall be required to determine the baaic
information needed for applying the decieion logic. The epecific purpoee Of
the FKEA la to determine the dominent failure odes (the manner in which the
functional failures identified in the FFA and the FSI process can occur) and
to determine the effects ofeach failure mode on the item where it occurs and
through higher levels.
3.7.5.1. Preparation guidelines. Each FSI on the PSI Index shall require
an FMsA. Each functional failure of each FSI must be analyzed. Copies of the
FFA, additional FSI Selection, and FSI Index forma, as wall as the ayatem block
diagram, shall be the baeis{for the F?4EA.
3.7.5.2 Functional failure modee. This Ff4BAdiffere from Other ~A
Droceesea because it @hall be used to filter out unimportant and unlikely
failure mmdes. Consideration can then be focused on the failure modes meet
important for preventive maintenance determination. The dominant failure (see
6.3.9) modes for each functional failure On the ~A
for? shall be listed. At
this atage it may be possible that the only failure for a particular PSI is
such that the effects are insignificant and the likelihood of the failure is
remote. For this reaaon, a mechaniem for ceaaing further analyeis of such
failure mudee shall be provided. After careful evaluation, the failure modes
that are most important, either because of their frequent occurrence reletjve
to t.]e
other failure modes or because of the severity of their effects, shall
be subjected to further analyeis.
3.7
.5.3 Completing the FMEA form.
completed se follows:

The PMSA fOrm (see figure 5) ehall be

MIL-P-24534A(NAvY)
(a) Block 1 - SWAB number. Duplicate each entry from the FSI Index
,..
form, ,block 8.
Block
2 - Nomenclature. Duplicate each entry from FSI Index
(b)
form, block 9.
(c) Block 3 - .Ship class. Dwplicate the entry from FFA form, block 3.
(d) Block 4 - Prepared by, block 5 - Reviewed by, block 6 - Approved
by, block 7 - Revision. See instructions for Msster Systems and
Subsystems Index form in 3.7.2.2d through 3.7.2.2g.
(e) Block 8 - Function(e). Enter the numbers of the functions
listed in FFA form, block 10, or the Additional FSI Selection
form, block 11.
(f): Block 9 - Functional failures. Dpplicate entries from FFA form,
block 12, or Additional FSI Selection form, block 12, as
applicable.
(g) Block 10 - Dominant failure modes. Enter the dominant failure
mode for each functional failure. Number sequentially to correspond to the appropriate functional failure and function; for
example, l.la., l.lb., 1.2a. Failure modes should be identified
at the level at which the analysis is made. If there are no
dominant failure modes. enter NONE.
(h) Block 11 - Failure effects (local, subsystem, sysiern). Enter the
details of the effects of each failure mode on the FSI where the
failure.,
mode occurs; at system and subsystem level if appropriate,
and the end effect. If the failure mode has no effect on a
particular level, enter NONE in the appropriate column. If the
particular of the effects are such that a safety hazard or
reduction in mission capability results, indicate:

--

-.
. .

(1) SAFETY HAZARD TO OPEWTORS

(2) SAFETY HAZA8D TO PERSONNEL IN VICINITY
(3) PARTIAL LOSS OF Capability TO DETBCT AND TRACK SURFACE
CONTACTS WITN RADAR
(4) TOTAL LOSS OF MOBILITY CAPABILITY
(5) If the details of the effects are such that only a redundant
item is lost, indicate using the phraae, LOSS OF REDUNDANCY.
(i)

(j)

Block 12- Tranafer (yes or no). Enter YSS if the failure mode
indicates further analyala should take place. If the failure
mode has insignificant effects, or it is only remotely likely
to occur, enter NO and provide rationale for this decision on
clearly labeled backup sheets. For failure modes of redundant
items, the likelihood of failure of redundant items must be considered. The PMS Coordinating Activity shall scrutinize this
area during the review process.
Block 13 - Serial number. Enter a four-segment aerial number as
follows:
(1)

Segnwnt 1 - see 3.7.2 .2j(l).

(2)
(3)

Segment
Segment

(4)

2 3 -

see 3.7.2 .2j(2).

enter the number

119, indicating the FMSA form,

followed by a slant (/).
Segment 4 - enter the SWAB number for the item from block8
of the FSI Index for the item.

18

MIL-P-2&534A(NAVY)

3.7.6 Phase 5 - RCM decision logic tree analysis. The developer shall
perform the decision logic tree analysis for each functional failure identified
in uhase 4. The results of the analysis shall be recorded on D.icislonLogic
Tree Analysis forms, with rstionale and justification backup sheeta. The
analysia of servicing and lubrication task requirements will be separately
treated in phase 6. If a need for a.specific servicing or lubrication task is
identified during the logic tree anslysis,this information should be held for
use in phase 6. The most critical step in the processing of FSIS is the application of decision logic. The logic consists of a series of yes or no questions
thatdetermine, the need for and availability of, applicable and effective
preventive maintenance tasks (ace figure 22).
3.7.6.1 Preparation guidelines. Each functional failure on the FMEA form
will be processed through the R(YMdecision logic tree. Only failure modes
receiving a YES in block 12 shall be considered in the logic tree analysis.
3.7.6.1.1 Review.of existing PMS documentation. Do not review existing
PMS documerrtatin;before doing the logic tree analysis. Use your knowledge
about the functions, functional failures, and failure modes to select each task.
3.7.6.2 Reliability centered maintenance decision logic tree - questiOn 1.
Ie the occurrence of a failure evident to the operating crew while it is per=ing its normal duties? This question sepsrates the functional fallure into two
groups:
(a)

(b)

Those functional failures which are evident to the crew during

routine duties. 2hefunctions in this group are those that
are operated either continuously or so often that the crew
knows whethera functional fallure has occurred.
Those functional failurea which are hidden from the crew until
the function }s actually demanded nf thla FSI. Functions in
this group are.those used intermittently or infrequently so that
the crew does not know whether a functional failure haa occurred
without some special check or test, or those that are not detectable until after another failure. For example, a failed shut
relief valve thst cannot be discovered by the crew until gverpreasurization damsges another Item in the ayatem. If an
applicable and effective preventive task is available for either
failure, it will be used. However, if no task is available that
will prevent the hidden failure, a specific task to find the
failure may be necessary
to tell the crew that restoration of
the function is needed and to improve the probabilf.
ty that the
function of the FSI will be availablewhen needed.
(1) If this question is answered yea, the rationale and justification required on the backup sheets must describe how this
failure is evident; that is, what ia observed, who (which
watch station or operator) observee it, and under what
cond~tions that watch etstinn or operator ntstion Is
actuslly manned. If this question actually msnned. If
snd Justificathis questlor.is snswered no, the rationsle
tion required should explain why the faiiure is hidden
from the crew.

.-

MIL-P-24534A(NAvY)

3.1.6.3 &liability centered maintenance decision logic tree - question 2.

Doesthe failure cause a loss of function or secondary damage that has ~ direct
and adverse effect on operating safety? This question separates the evident
functional failures into two groups:

,*

(n)

Those that directly impact operating safety. The functional

failures in this group are the evident failure modes of any
system which impact safety by their occurrence and the evident
failures of safety equipment and protective devices.
(b) Those that dO not impact operating safety. Functional failures
in this group will have impact o; eithe~ the capability of the
ship to perform its miseion or support functlone.
(1)

(2)

In considering how this question should be anawered, the

analyat must consider each dominant failure mode ahowrrin
the FMEA for each functional failure and ita effects. For
failures of protective devices or safety equipment, he must
also consider the effects of a second failure that requires
the safety equipment or protective devices to operate. The
effects of this worstcasesituation should be judged to
answer the question. The analyst should not assume more
than two failures to anawer this question, and this la the
onlyquesti6n in which ore than one f allure should be
considered at a time.
If the answer to this questionla yes,the rationale
and
justification
mustdescribetheparticulars
of the threat
to life, limb, or health of the crew.

3.7.6.4 fteliabilitycentered maintenance decieion logic tree - question 3.

Ooes the fallure have a direct and adverae effect on operational capability?
This question separates the evident, non-safety-related functional failures into
two groups:
(a) ThOae which affect tha ability of.the ahip to parform ita
military functions.
(b) Those that impact non-mlasion-related capabilities of the ship.
(1) men processing functional failurea through the logic tree,
if the answer to question 3 is no, postpone further analysis
of this failure until after completing the processing of the
safety and miaaion related failures. These failures have
only an economic impact, and scheduled maintenance for them
mwat be economically justified. The cost effectiveness of
ta,akafor these items can be affected by the taak results
for safety and miaaion related items; for exampla, a noncritical inspection msy not be economically justifiable
by itself if it requires excese time and cost, but if the
excess time and cost are determined to be required for a
safety cr mission related inspection, then the noncritical
inspection msy be justifiable if it is combined with the

20

-.

MIL-P-24534A(NAVY)

or miaaion related inspection. For this reaaon, the

economic aspects.of comt critical item tasks shOuld be
addressed only after the preventive maintenance requirements
for safety and mission critical itama (sac 6.3.36.end
6.3.28) are .detenuined.
If the anawer to this question ia yes, the rationale and
justification must describe the military functions which
are degraded by this failura.
sefety

(2)

3.7.6.5 Reliability centered maintenance decision logic trae - queatiOns

.4, 5, 6, amd i. Ia there an applicable and effective preventive taak (or
combination of taske) that will pravent functional failuraa? This qtiaationis
askad about tha dominant failure modes and separatea them into two groups:
(a)
(b)

Those for which an applicable and effective preventive meintanance

task (or teska) can ba spacified.
Those for which thare is no applicable and effective task.
(1)

AithOugh this Squestion ia askad in each of the four

branches, the anawer depends on tha criticality of the
failure.

3.7.6.5.1 APPliability.
A task or group of tasks ia applicable if, and
only if, tha task really doee prevent, discover, or reduca tha impact of the
fallure mmde in queetion. There are three types .oftaaks that prevent or reduce
failuras:
(a)

(b)

Cmndltion-diracted taaks. Theaa taska are periodic tests or

inspection to compare the existing conditions or performance of
the item with established atandarda. For a CD task to be appliaabla, the,,
occurrence of a specific failure mode ust be precedad
by a reduction in resistance to failure that la detectable aufficiantly in advance of actual failure so that appropriate action
can be taken to avoid the actual failure. This sat of condition
is callad potential failure. If the potantial,failura conditions
cannot be defined or if they are not detectable sufficiently far
in advance to avoid the failure, then nO CD task ia applicableTime-directed or hard-time taaks (sae 6.3.19) rework tsiska(RW)
(see 6.3.35) and lifa-limit taska (LL) (sac 6.3.24). Thaee are
tasks of DeKiOdiC restoration (RW) or replacement (LL) of an
item which is performad bafore the item reachea an age where
the risk of failure is much greater than at earlier egea. For
a TD task to be applicable, the item must exhibit an increaaed
risk of failure after some age has been reached. There must
be no con~ition that predicts failura. If the itam does not
exhibit this adverse age - reliability relationship, RW or LL
taske ere not applicable. Figure 23 display.athe characteristics
of an item for which herd time tasks are applicable..
(1)

Condition directed tasks are usually more effective than

RW o! LL tasks because, if selected properly, they rely
on a condition standard that is highly correlated to
future failure.

21

MIL-P-24534A(NAvY)

finding
tasks.
These tasks are intended to discover hid(c) Failure
den failures. For an FF task.to be applicable, functional
failure must not bc evident to the operating crew durinz
-.verformance of their ncirmalduties.

*. -,

3.7.6.5.2 Effective. A task that is applicable to a critical failure can

be effective only if it reduces the risk of failure to an acceptable level.
Other preventive tasks can be effective only if they are cost effective. Failure
finding tasks can be effective only if they increase the availability of the
affer.
ted function to an acceptable level.
3.7.6.5.3. Rationale and justification requirements for questions 4, 5, 6,
~.
The rationale and juatification required for yea anawera to questions 4,
5, 6, or 7 must address both the applicability
y and effestiveness of tasks
identified.
I

he applicability rationale for CD taaka must descritw the

potential failures that will bc discovered by the tasks that
will enable avoidance of actual failures.
(b) The applicability rationale for TO taaks must describe the
adverse age and reliability relationship the proportion of units
surviving to the age at which the taak is performed, the risk
of,premature failure and how the task will restore the Item to
achieve higher reliability.
(c) The effeCtiv6ne86 rationale must address how the tasks reduce the
risk of fallure to an acceptable level. Questions 5, 6, and 7
(except for safety related hidden failures and infrequently used
functions), must addreas the cost effactiveness of the tasks.
This will require consideration of the estimated time between
occurrence of potential failure and actual failure for CD tasks,
and comparison of this interwal with the task periodicity.
Consideration of the cost effectiveness of tasks.affecting
mission related failures should include loss of system availability, as well as a c.ompariaonof resource requirewnts to do
the tasks and repaira, versus repaira only without the preventive
task.

(8)

3.7.6.5.4 Dctenoination of maintenance interval. There are nn practicable

mathematical methods for selecting the right interval for a preventive maintenance task using the kinda of failure data normally available. A periodic
tack will not be effective .unleasit discovers or arrests a reduct.ioti
in functional failures. When there is a threat to safety and the associated failure
la time-related, a conservative approach based on past experience ia required
becauee the analyat must ensure a high level effectiveness. When there is nn
direct adverae effect on safety, the analyst ia adviaed to keep In mind that
he has an opportunity to explore without affecting safety. The interval of CD
taska depends upon the expected tine for a potential failure to progress to
functinnal failure. The interval of TD taaks depends upon the change of failure
rate with time. The interval of FF tasks depends on the confidence the user
desires to have that, when he wishes to use a hidden or infrequently used
function, it will bs available. Failure finding raske do not improve future
reliabllicy. Failure finding tasks only assure the user that he will not be
surprised by failures that exist but have not been discovered.

22

.-

*.

MIL-P-24534A(NAvY)

3.7.6.5.4.1 Importanceof periodic task selectio~

In all cases, selecting
any.periodic task means that you believe from careful consideration of the
available information that the user will be better off by doing tt than by not
doing it.
3.7.6.5.5 Reliability centered aintenance decision logic tree - question ~.
IS there an applicable and effective preventive maintenance taak (Or combin?tiOn
of tasks) that will prevent functional fsilures?
I
.

(a) This auestion isasked about safety related functional failures.

The c&urrence of such failures should be avoided if possible,
regardlessof cost. k applicable task can be effective only
if it reducei the risk of failure to a very low level. If
this que6tion
receives
change recommendation

a no answer,
a eafety
must be identified.

related

desi~

3.7.6.5.6 Reliability centered maintenance decision logic tree - question 5.

1sthere an applicable and effective preventive maintenance task (or combinntion
of tasks) that will prevent functional failures?
(a)

This question is asked about functional failures that affect

operating capability. This branch of the decision logic tree
relates to functione that are In regular, frequent use and
affect the ability of the chip to perform intended miesions.
An applicable task can be effective only if the value of the
resulting increase in reliability clearly exceeds the total
cost of the task. A task should not ba specified unleee it Is
both applicable and effective.

3.7.6.5.7 Ifaliabilitycentered maintenance decision logic tree - question 6.

Ia there an applicable and effective preventive maintenance task (or combinati~
of taska) that wiil prevent functional fallures?
(a)

2%1s question is asked about functional failurea that affect

support functions and thet are in regular, frequent uae, but
do not directly provide operating capability. An applicable
task can be effective only if the coste are clearly less than
the direct costs of the failures it prevents. A task should
not be specified unless it is both applicable and effective.

3.7.6.5.8 Reliability centered maintenance decision logic tree - question T.

Is there an applicable and effectivepreventive maintenance task (or combination
of tasks) that will prevent functional failures?
(a)

Ibisquestion is asked about functional failures that are not

evident to the crew while performing their normel duties.
These mav be safety, mission, or support related functions.
The anal~at must consider applicability and effectiveness as
previously described for similarly related on-line functione.

23

MIL-P-2453bA(NAVY)

3.7.6.6 F&liability centered maintenance decision logic tree - queetion g.

Is a scheduled FF task available and justified?

(a) This question is asked about hidden functional failures for

which no applicable and effective preventive taaka exist.
The failure in question here may be safety, mission, or
support related. The analyst must determine firat if there
is an applicable FF task. If there is, be must evaluate the
reliability of the item specifically related to this failure
mode, the effects of this failure mode remaining undetected
until the function ia next needed, and the benefita of
performing the task; A taak should not be specified unless
it is both applicable and effective. If the failure mode in
question is safety related, a safety related design change
recommendation should be identified If no taak is available
or if the task does not provide sufficient confidence that
the safety function will be available when needed.
3.7.6.7 Completing the logic tree analysis form. The Logic Tree Analyais
form (see figure 6) will be completed as follows:
Block 1 - SWAB number. Duplicate the entry on the FFA or the
Mditional FSI Selection form, block 1. (Start a new form for
each item.)
Block 2 - Nomenclature. Duplicate the entry on the FFA or
Additional FSI Selection form, block 2.
(c) Block 3 - Ship class. Duplicate the entry on the FSI Index
form. block 3.
(d) Block4 - Prepared by, block 5 - Reviewed by, block 6 - Approved
by, block 7 - Revision. See instructions for the Master Systems
and Subsystem Index form in 3.7.2.2d through 3.7.2.2E.
(e) Block 8 --Functional failure and failure mo~e(a). En~er functional failures and related failure modes receiving a YBS in
block 12 of the FMEA; number each aa numkred in the FMEA.
Block 9 - Criticality analyaia. Enter Y or N to signify a yes
or no answer to each of the first three logic tree queationa.
Poaaible alternatives are:

(a)

Question
1
Y
Y
Y
N

3
N/A
Y
N
tl/A

2
Y
N
N
NiA

24

A8aign
Criticality Claae
A
B
c
D

UIL-P-2&534A(NAVY)

Block

10 - Criticality

class.

Enter

A,

B, C,

or

D,

based

on

the answers in block 9. These letters identify the four main

branches of the logic tree as follows:

(h)

(i)
(j)
(k)
(1)
(d

(1)
(2)

Class
Class

A B -

(3)
(4)

class
Class

c D -

operating
safety
operating
capability
other regular
functions
hidden or infrequent
functions

Block 11 - Perindic maintenance (PM) task.

Enter a Y or N to
signify a yes or no answer to questions 4, 5, 6, or 7 in the
logic tree. If the criticality class for this failure is A,
the task must be able to reduce the risk to an acceptable
level; cost is not a consideration. If no tack is avaiLable,
a safety related design change recommendation must be
identified in block 13.
Block 12 - FF task. Enter Y or N signifying a yes nr no answer
to question 8 in the logic tree.
Block 13 - Design recommendation. Enter yes if one was identified for this failure. otherwise enter no.
Block 14 - Task description. Enter a brief description nf the
applicable and effective tasks.
Blnck 15 - Periodicity. Enter the perlodicity (see 3.11.5)
for ac.complishmsntof tasks in block 14.
Block 16 - Serial number. Enter a four-segnnt serial number
as follows:
(1)
(2)
[3)
,-.
(4)

1 - see 3:7.2.2j(l).
Segment 2 - see 3.7.2.2j(2).
Seftmsnt3

.. . - enter the number 120 to indicate the Logic

Tree Analysis form, followed by a slant (/).
Se~nt
4 - enter the SWAB number from block 1.

Segment

3.7.6.7.1 Decision logic tree questions rationale and justification

documentation. The rationale and justification for the answers to the deciaton
logic tree question will be documented in free form simple narrative ,on plain
paper eheets attached to the Logic Tree Amalysis form. The rationale and
justification for the questions pertinent to each functional failure analyzed
should be identified by functional failure number and description.
3.7.7 Phase 6 - Servicing and lubrication analysis. The developer shall
perform a servicing and lubrication analyaia and prepare a Servicing and Lubrication Analyais form (ace figure 7). Servicing and lubrication are preventive
maintenance tasks that should be analyzed through the PMEA and decision logic
tree processes, but since tbe bsnefita of such taska are fairly obvious, an
abbreviated analysis based on existing servicing and lubrication requiremant~
shall be perfonned.

25

FfIL-P-2453kA(NAvY)

S.7.!.1 Preparation guidelines. A servicing and lubrication analysis

shall be performed ,on,811 the systems and subsystems Identified in phaee 1.
Collect existing requirement for servicing and lubrication from the appropriate
f41tC6
and technical msnuals for theee systems and aubsysteme,

q,

3.7.7.2 Servicing and lubrication periodicities. The RCM tiervicingand

lubrtcation analysis is a simple , common sense evaluation of existing requirement
to justify performance of specific taaka at specific periodicitieh. Current
periodicities are frequently based only on manufacturer recommendations and
may be exceaaive. The goal here is to determine the tacks that really are
applicable and effective and determine their correct periodicity. In evaluating
these taaka, the following conaiderationa should be msde:
(a)

Are there evidencee from existing data on failed hardware of

.Inaufficientor exceaaive servicing or lubrication?
(b) What is the actual periodicity at which this taak is really
performed, and what materials and procedures are really used?
(c) Can the current method be improved?
(d) Can an approved alternative material be used? When practical,
common periodicities and msteriala should be eatabliahed ao
that several items can be serviced or lubricated at once and
the number of different msteriala required can be minimized.
3.7.7.3 Selection of lubricant and hydraulic fluids. Lubricant and
hydraulic fluids for hull, rmchanical, and electrical equipmsnt must be selected
from the approved list in accordance with MIL-NDBK-267. Lubricant and hydraulic
fluids for all other applications will be selected from the Planned Maintenance
Syetem Lubricants, Compounds, and Cleaning Agents Cross Reference Guide or OD3000.

3.7.7..4 Completing the eervicing and lubrication analyaia form. The

Servicing and Lubrication Analysis form (ace figure 7) shall be completed as
follows:
(a)

(b)
(c)
(d)

(e)

(f)

Block 1 - SWAB number. Enter the SWAB number of the system under
analyaia, aa defined in phase 1 on the Master Systems and
Subaystema Index, block B.
Block 2 - Nomenclature. Enter the nomenclature of the ayatem under
analyaia from block 9 of the Maater Systems and Subsystems Index.
Block 3 - Ship clasa. Duplicate the entry from block 3 of the
Master System and Subsystems Index.
Block 4 - Prepared by, block 5 - Reviewed by, block 6 - Approved
by, and block 7 - Reviaiorr. See instructions for the Maater
Systems and Subayatems Index form in 3.7.2.2d through 3.7.2.2g.
Block 8 - Item and task description. Enter the nomenclature of
each item and beneath that the description of each servicing and
lubrication taak pertinent to that item, including ~C SYSCCM
control numbers where appropriate.
Block 9 - Location. Enter the compartment number(s) where tbe
task Is performed.

26

MIL-P-2L534A(NAvY)
.-.

e
.

(g)

Block 10 - Quantity.
the task is performed

che quantity
are installed

of the item
upOn.Whl~h
in the system under

analysis.
Block 11 - Previous periodicity. Enter the most recently used
oeriodicity for this task on this or similar items. If this h
a new item; enter the manufacturera recommendation.
(i) Block 12 - Materialspecification. Enter the specification and
symbols of any material used; for example, oil, grease, fluid.
(j) Block 13 - Anelysis decision. Enter action taken by analysis;
NC-no chanRe. OM-omit. CM-change msterial, CP-change procedure;
and the revised periodicity, if appropriate.
(k) Block 14 - Explanation. Enter rationale and justification for
the analysis decisions in block 13; outline revised procedures,
and specify new materials as appropriate.
.(1) Block 15 - Serial number. Enter a four-aegu.entserial number as
follows:
(h)

(1)
(2)
(3)

(4)

Enter
that

Segment 1- see 3.7.2.2j(l).

Segment 2 - see 3.7.2.2j(2)
Segment 3 - enter the number 121, indicating the servicing
and lubrication analysis form (see figure 7), followed by
a slant (/).
Segment b - enter the SWAB number from block 1.

3.7.8 Safety related design recommendations. For sefety related failure

modes for which no applicable taaks exist or for which the availsble tacks do
not provide the required levels of effestiveness, recommendations for a aafety
related design change must U Identified and ao indicated on figure 6.
3.7.9 Phaae 7 - Audit and prapsration of the maintenance requirement

index. The developer shall assemble the phase 1 through phase 6 deliverables
Into a package and audit the analysis to ensure that it is complete and sccurate.
The developer shall indicate hia quality aasurance of the administrative accuracy
of the forms preparation and the technical accuracy of his analysis by signing
the Reviawed Byblocks of each form. The developer shall summarize the taaks
generated by preparing a maintenance requirement index form (see figure 8). This
form shall be used to list all taaka for the systems identified in the logic tree
analysis and the servicing and lubrication analysis. It shall reference existing
MRCS that satiafy the requinnents of each task, indicating clearly ta9ks not
covered by ,an existing KRC, tasks requiring a C01UbiI18ti0ZI
of existing MCRS
necessary to satiafy the task requiremsnte, and revisions of existing MRCS
necessary to aatiefy task requirements.
3.7.9.1 Preparation guidelines. A maintenance requirement index will be
prepared for each aubayatam identified and approved in phase 1 of the development.
3.7.9.2 Completing the maintenance requirement tndex form. The maintenance
requirement index form (see figure S) shsll be completed in SWAB order, with
taaks listed in order of increasing periodlcity, as follows:

o
27

MIL-P-24534A(NAvY)

(a) Block 1 - SUAB number. Enter the highest indenture level SWAB
number for the development group assigned. If an entire group
is assigried,this number is a level,1 SWAB number, a three-digit
number containing two zeroes; for example, 100, 200.
(b) Block 2 - Nomenclature. Duplicate the entry on the maater aystema
and subsystems index.form, block 2.
(c) Block 3 - Ship claaa. Ouplicate the entry on the master syatema
and subaysternsindex form, block 3.
Block
4 - Prepared by block 5 - Reviewed by, block 6 - Approved
(d)
and
block 7 - Re~iaion. See Instructions for the Master
Systems and Subsystems Index form in 3.7.2.2d through 3.7.2.2g.
(e) Block 8 - Analysia raference. Enter the serial number of the form
which documents the requirement for each task.
(f) Block 9 - Location. Enter the compartment number where the task
will be performed (refer to additional FSI selection form,
block 9).,
Block 10 - Equipment nomenclature (AN, MR/MOD/AFL/CIO) maintenance
(g) .
requirement. Enter the SWAB number and nomenclature of each item
from the FSI index. Block 10 includes a brief description of the
tasks for that equipment.
(h) Block 11 - Periodicity. Enter the periodicity for each cask.
Refer to the form which generated the taak.
(i) Block 12 - Reference +iRC. Enter the SYSCOM control numbers of
iiCa that satisfy the task requirement or can be revieed to do
ao. Indicate combination of MRCa by prefacing the group of
MRC SYSCOM control numbers with the abbreviation COMB. Indicate
tasks not covered by an existing MRC with NEW. Indicate division
of KRCFJby prefacing the MRC SYSCOM control number with the
abbreviation PART.
Block
13 - Serial number. Enter a four-segunt number as follows:
(j)
(1)
(2)
(3)

(4)

>,

Segment 1 - see 3.7.2.2j(l).

Segment 2 - see 3.7.2.2j(2).
Segment 3 - enter the number 123, indicating the maintenance
requirement index form (see figure 8), followed by a
slant (/).
Segment ,4 - enter the SWAB number from block 1.

3.7.10 Phase 8 - Method study and procedure evaluation for new taaks and
revised MRCS. When directed by the PMS Coordinating Activity, the devaloper
=p~m
a method study and a procedure evaluation in accordance with
3.10. for taaka not covered by existing
MRCS and taska reauirinz reviaiona of
existing MRCS.
3.7.11 Phase 9 - Maintenance requirements task dafinition. Upon completion
of phaae 8 review and approval, the PMS Coordinating Activity shall.direct the
developer to prepara task definition forms (see fig~re9). The task definition
proceea collects sufficient information about the detailed procedures of each
task so that a decision can be made as to the appropriate maintenance level
organization, intermediate, or depot) Co perform the tasks and to write the MRCS.
The task definition form resembles an MRC verification draft, with a few extra
blocks for additional information.
o

28

JIL-P-24534A(NAVy)

3.7.11.1 Preparation guidelines. Task definition forms shall be prepared

for tasks generated by the decision logic tree analysis snd specifically designated for ,.
further development by the P.MSCoordinating Activity. The tasks ao
designated will be those which the PMS Coordinating Activity coiwiders candidates
for organizscional level maintenance, based on information collected during the
analysis. Some tasks generated by the anslysis may obviously be more appropriate
for off ship accomplishment and these would not be designated for task definition.
They will be forwarded by the PMs Coordinating Activity to the cognizant planning
authority for incorporation into ship class maintenance plana. After the task
definition phase has collected more information about each remaining task, some
of these will alao be more appropriate for off ship accomplishment and will hs
forwarded to the cognizant planning authority. Selecting the echelon (organizational or off ship) that will perform each maintenance taak la an integral part
of the taak definition process. If the task frequency required to ensure safety
and mission capability requires on ship performsnce, the taak must .beaasigned
to the organizational level. If the task frequency permits performance by off
ship resources, a choice must be made. This choice will be constrained by the
ability of the ships crew to do the task without external skills, materials,
tools, or equipment.
3.7.11.2 C41mplet
ing the task definition form. The Task Definition form
(ace figure 9) shall be completed as follows:
(a)

(b)
(c)

(d)
(e)

(f)

(.s)
(h)

(i)

(j)

Taska covered by existing MRCS. For taaks covered by existtng

MRCS, a copyof the !fRCmay be attachad to the taak definition
form in lieu of filling in blocks 9. 10, 11, 12, 13, 14. 15. 16
and 17.
Block 1 - SWAB number. Duplicate the entry from block 1 of
the maintenance requirement index form.
Block 2 - Nomenclature. Enter the nomenclature of the item
upon which the task la performed from block 2 of the
maintenance requirement index form.
Block 3 - Ship class. Duplicate entries from block 3 of the
maintenance requirement index form.
Block 4 - Prepared by, block 5 - Reviewed by. block 6 for
Aptirovadby,,and block 7 - Revision. See instructions
the msater systems and aubsyatem index form in 3.7.2.2d
through 3.7.2.2g.
Block 8 - Equipment SWAB and nomenclature. Enter the SWAB
number and nomenclature of the item upon which the taak la
performed from block 10 of the maintenance requirement index
form.
Block 9 - Quantity installed. Enter the installed quantity of
the item on which this task must be performed.
Block 10 - Reference MRC. Enter the SYSCOM control number of
the KRC listed in block 12 of the aintenance requirement
index form.
Block 11 - Mairitenancerequirement description (task). Enter
a brief description for the tasks from block 10 of the maintenance requirement index in accordance with 3.11.10.
Block 12 - Safety precautions. Enter appropriate information
for this task in accordance with 3.11.11.

29

MIL-P-24534A(NAVY)

(k) Block 13 - Periodicity. Enter the periodicity of this task

from block 11 of the maintenance requirement index form.
(1) BlOck 14 - Retes and man-hours (N/lie). Enter expropriate informetton for this tack in conformance with 3.11.6 and 3.1,1.7.
(m) Block 15 - Total M/He. Enter the aum of the M/Ha from block 14.
(n) Block 16 - Elapsed time. Enter appropriate information in
block 16 (see 3.M
(o) Block 17 - Tools, parts, materiala, teat equipment. Enter
required items for this task in accordance with 3.11.12 and
other specific guidance provided by the PMS Coordinating
Activity.
Block
18 - Procedure. Enter the appropriate step-by-step
(P)
procedure for thie tack in conformance with 3.11.13.
(q) Block 19 - Ships crew (yea or no). Enter a YES or NO anewer
to the queetion. Canthie tack be done by the shipa crew
without external sk,ille,materiala, toole, or equipment?
(r) Block 20 - Level.
(1)
(2)

(s)

Block 21 - Location. Enter the compartment numbere of the

epaces where the item on which this tack is performed are
located.
Block 22 - Serial number. Enter a four-eegment serial number
aa follows:
(1)
(2)
(3)

Segmnt 1 Segwnt 2 Sep,~nt 3 definition

slant (/).

(6)

Segment

?
I

Enter the lowest maintenance echelon at which this teek

can be done.
Enter the level at which it should be done, if organizational workload must be minimized.

eee 3.7.2.2.j(l).
eee 3.7.2.2.j(2).
enter the number 124, indicating the task
form (see figure 9), followed by a

i -

enter the SWAB number for the item listed in

block 1, composed of the item number previously assigned
in the analyeis, followed by a daah (-) and a sequential
tack number for the item.

3.7.12 Phaee 10 - Inective Equipment Maintenance (IEM) documentation.

Inactive equipment maintenance requirement documentation shall be developed
and prepared. Upon completion of the IEN analysie the IEM requirement will be
eubjected to procedure evaluation ae specified in 3.10.

30

MIL-11
-2L534A(NAVY)
F
a

3.7.12.1 Inactive equipment maintenance analysis. Inactive

equipment
maintenance analyaia shall be the basis for determining the maintenance requirements to be performed when equipment 1s inactivated for periods of prolouged
idleness. Maintenance requirements shall prepare the equipment for the inactive
period (lay up maintenance), prevent equipment deterioration during the inaccive
period (periodic maintenance), prepare the equipment to become operational (start
up maintenance), and ensure,that the equipment is completely operational at the
end of the inactive period (operational test). The analysia shall identtfy:
the maintenance actions required, the source of the required actions, for example,
from existing PMS or technical
manuals,
and the required
procedures
not available.
when
tie ISf4 analysis
will
assume that the equipment
is in an operable
condition
che procedures to inactivate the equipment are implemented and shall be performed
using an inactive equipment maintenance requirement analysis form (see figure I1).
The analysis is a continuation of the requirements investigation process. At
the top of the IfNianalysis form, enter the equipment item nams or nomenclature,
the date, and the page number. The form shalt be filled out as follows:
will
occur if equipment Is
(a) column 1. List what degradation
inactive wh:le ship is (a) operational, and (b) in an industrial
environment.
Availability

(b)

For example,
Rsgular
Overhaul
(F.OH) , Restricted
modernization. Consider separately the
(RAV),

equipments internal workings, external surfacee, attachment,

connecting lines, piping, or valves. Under the Industrial
environment, consider what the effecte will be under conditions
Coneider
such ae lack of power and heating or cooling problem.
the effects if the equipment Ie expoeed to abnormal conditlone.
For example, having the bulkhead, overhead, and decking removed;
or industrial work in progress in the immediate area such aa
welding, chipping, sandblasting, or painting.
Column 2a. Considering location and equipment deeign, etate maintenance actions with alternatives
to protect and prevent degradation of the equipment under the condition listed in column 1. As
many alternatives as possible should be preeented. The actione
lieted stra11
prescribe the steps necessary to lay up the equipment
and maintain it in an inactive etate for a period of prolonged idleness. State the actions as maintenance requirements; for example.
(1) Remove equipment and place in a protected area.
(2) Lubricate and cover exposed areas.
(3) Inactivate radar set.

(c)

(d)

State what maintenance

actions
are required to
reactivate equipment that has been idle for a prolonged period.
Provide start-up maintenance where neceeeary and specify what
teete are required to eneure the operational readineas of tha
equipment.
Column 3. Considering coat and reeource expenditurea, determine
the effectiveness of each requirement listed in column 2. State
whether or not the procedure
would satiafy all requirements and
give the reaaon. Justification is required for each alternative

Column 2b.

Only the met

justification.
native

under

coat effective
Justification
different

requirement
should survive
the
may recoumtend mnre than one alter-

envi ronmentel

down period.

31

conditions

during

shut-

MIL-P-24534 A(NAvY)

(e) Column 4. tktablish the IEM periodicity; lay up maintenance (LU),

periodic maintenance (PM), start up maintenance (SU), or operational test (OT), for each requirement fully justified in
column 3. A UR may be used under more than one IEM periodicity.
For periodic maintenance, identify the periodicity of performance
required by adding acode to the PM indicator; for example,
PM(W); PM(M). Justify each periodicity decision. If a requirement 19 to be performed in an industrial environment only,
indicate by the notation (I);
for example, LU(I). This MS shall
be entered on the MIP with a note to describe the circumstance.
(f) Column 5. Review and list available maintenance procedures that
could satisfy the requirements justifiedin columns 3 and 4.
Maximum uae of existing maintenance procedures la required.
Apply existing procedures aa vritten or mmdify aa neceaaary.
Maintenance procedures requiring modification and maintenance
actions which must be developed should be flagged by circling.
Indicate the source of existing procedures. Some of the aorcea
will be technical manuala (TFfa),ordnance publications (OPa),
exf.stingMRCS, or MRCa to be developed as a result of phase 9.
(g) Column 6. Aaslgn a recommended periodicity for each requirement
justified in column 4. If there are no MRs justified in column 4,
indicate with the word none. This columm containa the key
information required in developing the IEM portion of the tfIP.
(h) Column 7. This column provides a summary and check-off list of
the development work required for ISf.f.Opposite each f4Rlisted
in column 6, indicate what must be done to complete the IEM
development with one of the following:

*.

(S) - the MS procedure exiacs on the PMS section of the MIP

and is to be used aa written.
(M) - the MR procedure exists on the operational maintenance
portion of the MIP; but, the procedure for periodicity
must be modified for LF2f.
(N) - a complete new procedure must be developed to satisfy
the MR and shall be subjected to procedure evaluation,
(see 3.10).
3.7.12.2 System level IEM. Maintenance index pages that list ayatem
level teata aa a combination of equipment and system level MRa shall include an
IEM section. System level tests shall be preceded by the following note: The
following tests shall be scheduled for accomplishment after completion of all
equipment level SU and OT.
3.7.13 Phase 11 - Unscheduled maintenance (UM). Unscheduled maintenance
documentation shall be prepared only when directed by the acquisition docyment
in accordance with the provisions of 3.9.
3.7.14 Phase 12 - Maintenance index page and maintenance requirement card
development and preparation. The PMS Coordinating Activity will direct the
contractor to develop verification draft MIPS and MRCS for specifically
designated
taska defined
in phases 9, 10, and 11. The tasks so designated will be those
that the PMS Coordinating Activity determines are appropriate for organizational
level accomplishment.
32

MIL-P-24534A(NAVY)

(a)

The PMS Coordinating

(b)

concerning the SWAB level (see appendix E)

at which MRCa shall be assembled into MIPS. Maintenance requirement cards requirfng servicing and lubrication (replenishment
or replacement of consumables) shall not contain taaks requiring
testa, inspectloni, adjuatmenta, alinement, calibration; separate
MRCS shall be prepared for these taska.
Maintenance index pages and MRCS shall be prepared aa specified
apecif

in

ic

3.11

Activity

shall

provide

the

developer

with

guidance

and 3.12.

The requirements investigation process

will produce a multitude of documents which eventually must be aasembled into a
into a cohesive, understandable package. RCM documentation control sheets have
been designed to provide an index of the forma completed for a development at
every atage of the development. The control aheeta provide a column for listing
the forms prepared in a development phase by aerial number, with provisions tn
connect related forms with straight lines to form a flow chart of that development. The completed control sheeta list serial numbers of all documents In the
development package and shall relate each form to its predecessor and succeaaors
in the analysis (ace figure .24).
3.8

RCM documentation

control.

3.8.1 Completing the RCM documentation control sheet. The RCM documentation control sheet (see f~gure 10) shell be completed as follows:
(a)

(b)
(c)
(d)
(e)
(f)
(K)
(h)
(i)

Block 1 - Development group. Enter the development group number

and name.
Block 2 - Ship/clasa. Enter the clase or chip hull number upon
which the development is baaed.
Block 3 - Devaloper. Enter the developing organization name.
Block 4 - Contract number. Enter the contractnumber under which
this development was conducted. if atmlicable.
Block 5 - Reifaion. Enter ORIGiNAL, O; A, B, or C for subsequent
reviaiona of the development.
Block 6 - Date. Enter the date when the entire development wae
completed or.revised.
Phaae 1. Enter 114, the laat three aegmenta of the Maater
Systams and Subeystema Index form aerial number.
Phaae 2. Eriter116, the laat three aegmenta of the FFA form
aerial number.
Phaae 3. Enter 117, in the left coIumn, adjacent to the FFA
form serial number for the ayatem or aubaystem containing the
FSI candidate; the last three segments of the FSI Salection form.
aerial number. If an FSI candidate waa not selected aa an PSI
and not listed on the FSI index, enter NSI balmw or to the right
of the PSI,Selection form serial numbar. Enter 118, in the right
column, above or below the horizontal line between the FFA form
and FSI form serial number, the last three segments of the FSI
index form aerial number prepared for each subdivision. Draw
connecting lines between related FFA form and FS1 SelectIon form
serial numbers.

33

MIL-P-24534A(NAVY)

(j)

(k)

(1)

(m)

(n)

(0)

Phase 4. Enter i19, the last three segments of the FMEA form
serial number, adjacenc to the associated FSI Selection form.
serial number for the items. Draw connecting lines between
the FSI Selection form and Ft4sAform serial numbers. If none
of the functional falluree of an item were selected for further
analysis, enter TERMINATED,.below or to the right of the PMEA
form serial number for the item.
Phase 5. Enter 120, in the left column, the last three segments
of the Logic Tree Analysis form aerial number. Align with
aaaociated FMXA serial numbers for each item. Draw connecting
lines to the aaaociated FMEA aerial number. If the logic tree
analysie did not determine a requirement for any taaks related
to the item, enter NO TASKS belw or to the right of the Logic
Tree Analysis form serial number. If safety related design
change recommendation were submitted, enter 122, in the right
column, the last three segments of the form uerial number of
such recommendations, adjscent but not on the same 1ine as the
Logic Tree Analysie form 8erial number.
Phase 6. Enter 121, the last three segments of the Servicing
and Lubrication Analyais form serial number. Horizontally
alfgn with the FSI Index form serial number for the associated
system and subsystem. If no servicing and lubrication tasks
(see 6.3.25) were required, enter NO TASKS below or to the
right of the Servicing and Lubrication Analyeia form aerial
number.
Phaae 7. Enter 123, the last three segments of the Maintenance
Requirement Index form serial number. Horizontally align with
the entry in the Phase 1 column for the system and subsystems.
Phase 9. Enter 124, the laat three aegmenta of the Taak Definition form serial number. Enter adjacent to the.RCM Logic Tree
Analysia form serial number or alined with the Servicing and
Lubrication Analysia form.serial number that determined the
task was required. Draw connecting lines to appropriate serial
numbers. If no MRC was prepared for a taak definition, enter
NO MRC below or to.the right of the taak definition form aerial
number.
Phase 12. Enter in the left column, the SYSCOM MRC control
number of each NRC prepared during this phase. Align with the
associated task definition form serial number and draw connecting lines. Enter the MIP number for each group of f4RCsin the
right column. Draw connecting lines between the MIP numbers
and associated SYSCOM MRC control numbers.

3.8.2 Deliverable. The developer shall asaemble and deliver to the PMS
Coordinating Activity, a final documentation package in accordance with the
data ordering document specifled in the acquisition document (eee 6.2.2 through
and including 6.2.2.2.

34

q.

.4.

MIL-P-2A534A(NAVY)

3.9 Development of UM analysis

and requirement
tasks.
The acquisition
document (see 6.2.1)
shall
Specify
the procedures
for determination
of UM
analysis and requirement taaks. The OM requirement taak, shall be documented
on &Ca and MIP~ as specified in 3.11.22 arid3.12.16.

3.9.1 Functions of the Uf4. Unscheduled maintenance requirements are those

documented actiona required ,toreturn system or equipment to an operational
condition within predetermined tolerances or limftationa. Unscheduled maintenance actiona evolve from system or equipment failures or other lndicationa of
system or equipmant degradation. Unscheduled maintenance includes alignment,
adjustment,
replacement, and repair procedures. Testing and other actions,
such aa open and inspect, not required as scheduled maintenance actions may
also be included as part of the UM. Unscheduled maintenance shall not include
maintenance actions which must be scheduled for performance on a repetitive
basis; for ezample, an alignment or adjustment that must be accomplished monthly
would be claaaified as scheduled maintenance and would he included within the
scheduled MIP/f4RCs.
3.9.2
cedures

Unscheduled maintenance

are

documented

on unscheduled

documentation.
MRCa (tMRCs)

Unscheduled
maintenance
prodesignated
by a U periodicity.

Unscheduled maintenance requirement cards will he listed on separate MIPa

itemizing only UM procedures. However. UMRCa may be included on the same MIP
es scheduled MRCS when approved by the PMS Coordinating Activity.

3.10 Procedure evaluation. Each F@ that evolves froiathe requirements

Investigation process (see 3.6) or IEH (see 3.7.12) shall be subjected to a
procedure evaluation. The procedure evaluation is a method study technique
that will:
(a) ~termine the moat practical method of accomplishing the task.
(b) Ensure that ,posaible hazarda and their elimination are considered.
(c) Ensure that the procedure developed is the best from an engineering standpoint commensurate with resources available to the user.
(d) .Snaurethat actions that do not support accomplishment of the
f4Rare eliminated.
3.10.1 Methodology for conducting the study. The methodology.for.conducting the method study ia contained in the following paragrapha:
3.10.1.1 Procedure evaluation sheet (PES). The mathOd study shall be
documented on PES (see fif!bre12). A PES shall be prepared for each MR that is
to be developed. l&en mo~e thanone page is required, the PES may include
centinuation pages. The PES may be handwritten or printed with a black pen.
Heading information shall be completed acroaa the top of the PES ae follows:
(a) SHIP SYSTSM, SUBSYSTEM OR EQUIPNEN2 BLOCK. Enter the nomenclature of the ship system, subsystem, or equipment.
(b) ACTIVITY/COWTRACT NO. BLOCK. Enter the activity or contract
numbar.
(c) LOCAL CONTROL NO. BLOCK. Enter the local control number.
(d) DATS AND PAGE BLOCK. Enter the date and page number.
(e) MRC CODE BLOCK. Enter the MRC code.

35

MIL-P-2453.4A(

NAVY)

(f) DEVELOPER BLOCK. Enter the developer of the PES.

(g) MAINTENANCE REQUIREMENT DESCRIPTION BLOCK. Enter a description
of the maintenance requirement. NOTE: When f1Lling in ths
follnwing information; the entries in all the colum% must be
related. For example, the entries in the SYMBOL, TIKE, EKAf.fINAto the entry in the first
TION, etc., columns must be related
line in the PRSSENT METHOD column.

..-. !

..,)

3.10.2 Record cnlumn. Maintenance requirements shall be method studied

in periodiqity sequence as established by maintenance analysis. More frequent
periodicities shall bs method studied first; for example, weekly requirements
before menthly requirements.
3.10.2.1 Present method column. A step-by-step method required to .accnmplish the MR stated in PES heading shall be entered.
When available,
previously
developed
methods shall
be used. If there are no previously developed methods,
a proposed method shall be entered.
3.10.2.2 Symbol column. Each step in the present method column shall be
carefully examined to determine primary and secondary action. Primary actions
are limited to the step or steps which actually accomplish the maintenance
action described in the MR. For example, for the FIRLubricatePedestal
Bsaring,only the steps actually pertaining to the lubrication of the bearing
are primary actions. All other steps that support the accomplishment of the
primary actinn are considered secondary actions. I%e a ropriate operation
proceaaing chart (OPC) symbolOfOf or an Opera~iOn andb for an inspection
shall be recorded after each corresponding step in the method. Larger symbols
ehall be used to identify each ajor step and small symbols to identify subste a.
Each s bol shall be numbered according to the type of symbol; for example, d
@
~
@
@
@
~
~
indicating six operation actions and three
inspection actions.

o
:3

3.10.2.3 Time column. Opposite each action symbol, enter the estimated
or observed time to perform the action in minutes and seconds.
3.10.3 Examination column. The method that is recorded in the first
column of the PES shall undergo close analysia and be exposed to extensive
what, where, when, how, and why questioning.
(a) once each primary action contained in the present method has
been determined, the following questinns shall be aaked to
asaist in determining the anawers to the basic five questions:
(1) What is accomplished (by the action in the procedure,
nnt the MR description)?
(2) Why should it be done (the action In the procedure)?
(3) Could anything else be done that would satisfy why it
shoula be done (the xccion in the procedure?
(4) where is it being dine? Why at that particular place?
(5) When should it be done (in the procedure, not the
periodicity of the MR description)?
(6) my then (in that sequence of the procedure)?
(7) Coultiit advantageously !X done anywhere else (In the
procedure)?

.-/

MIL-P-24534A(NAVY)

(8) How is it done (the manner in which it is performed in

the procedure)?
(9) Why fS it done that way (in the procedure)?
(10) Is there a better way thatit could be done?

/-

t
.

(b) Answers and remarks to questions about primary actions in the

present procedure shall be brief statements only, and not
improved steps or procedures. Statements shall bs entered
that may assist in developing a better step or procedure in
the create and develop phaae of the PES. Entries are not
required
on the PES for a step in the present procedure which
remains unchanged after questioning, but entries pertaining
to elimination or changea to procedural atepa shall be entered
to the right of the symbol reflecting the present pro~edural
action. When the questioning and the entering of remarks has
bsen completed for each primary action in the presentprocedure,
remaining Secondary actiona In the procedure shall be examined
to see how they have been affected. Elimination of primary
actiona should eliminate or change moat supporting steps. Any
secondary actiona remaining in the present method column shall
bs questioned for necessity and appropriate remarka entered in
the examination column of the PES.
3.10.3.1 Examination checkoff. Before proceeding to the final phaae of
the method study, signifi.iarit
points of the examination shall be reviewed.
The following statement shall serve as a checkoff for these points:

(a) The primary actiona of the present method have been identified
and analyzed, and pertinent remarks have been noted on the PES.
(b) Sacondary actions of the present method have been examined
for their necessity, and pertinent remarks have baen noted on
the PES.
(c) Questioning of all faceta in the present method has baen
concerned with the procedure for accomplishing the FIRand
not the Hlfdescription itself.
3.10.4 Create and develop columns. The maintenance procedure and all
other data elements for ariFfftC
shall be created and developed in this final
phase of method study.
(a)

A step-by-step maintenance procedure for accomplishing the MS

by a new improved- method shall be developed and en ered on
the PES. Information shall be entered for each proc1dure
pertaining to: time, tools, parts, materiala, and test equipmant; warnings, cautiona, notee; related maintenance, and the
number of men and their skill levels.

3.10.4.1 Improved method column. Develop the new procedure by:

(a) Eliminating unnecessary steps in the procedure which do not
support the accomplishment of the primary actions.
(b) Simplifying tasks.
(c) Changing the sequence or rearranging actions.
(d) Combining tasks when possible.

37

f!2L-P-24534A(

it

NAVY)

3.10.4 .1.1
Procedural
modification.
As the new procedure
18 developed,
1 column. Symbols and respectjve
shall
be entered by symbols in the Syrnbo

items shall be transferred from the record columns to the create and develop
columms for steps that are not eliminated. A no change note shall be entered
when a step remains the samein the Improvedmethod. When steps iarecombined,
the word combine shall be entered in the improved mathod column. A step that
ie simplified shall be entered in the simplified version with its symbol and
number from the Record column and the new time.entered as appropriate.
3.10.4.2 ~.
Enter the time, in minutee and eeconds, for each step in
the procedure as it 16 developed. The time shall be enteied immediately to tiie
right.of the symbol for the step developed. When the imuroved method is
completed, the time entered for each step shall be totaled by rate on the last
PES.. The totalshallba converted
to hoursand tenthsof hours. Thistima

shallappearon an MRC to indicatethe tha requiredforeachrateinvolved

to
performtheprocedure
in theimproved
methed.When~s of thesameperiodicity
utilizesimilarprocedures
and thetotalelapaedtimedoeenot exceed3.5hours.
theyshallbe documented
on the sameMRC.
3.10.4.3 Tools, parts, materiala, and test eqipmenc. Acro8s from each
applicable ateP in the prOcedure being developed, indicate the tools, parts,
materials, and test equipment necessary to accomplish the maintenance (see
3.11.12).
3.10.4.4 Warninga, cautiona and notes. Warnings, cautiona, and notes
shall be entered horizontally across from the applicable procedural step on the
PES and shall be used aa specified in 3.11.1.11, 3.11.13.2, and 3.11.13.3.

./

3.10.4.5 Related maintenance. The purpose cf thie phase of the ,method

study is to identify related maintenance. A maintenance action ie related when
one or more of the following condition exist:
(a)

(b)

a maintenance ection can bs performed before, in conjunction

with, or immediately after the task described in the MRC,
reeulting in a substantial savinga in time.
If the equipment can be opened once for the accompliahmsnt
of more than one MR.

If

3.10..4.5.1 Related maintenance types. There are two types of related

maintenance:
(a) A mandatory related maintenance action that must bs performed
concurrently or in conjunction with another maintenance actiuv.
because it iE an integral part of that procedure.
(b) A convenience related maintenance action that may be performed
concurrently to effect a eavlngs in HIlfsor materials.
3.10.4.5.2 Criteria. To be classified as related maintenance, the
following criteria shall apply:

38

MIL-P-24534A(NAVY)

(a) When scheduled concurrently or in conjunction with another task,

the execution of the related maintenance shall yield a savings
of manpower or mscerial resources.
(b) Related maintenance msy be used to take advantage of procedural
steps froteanother MRC which would otherwise be repetitious.
This is especially true for procedures available as situation
requirements or UM.
(c) The periodicity of the requirement under development shall be
equal to or less frequent than the related requirement. For
example, an annual requirement msy have a quarterly requirement
specified as,related maintenance, but the quarterly (more
frequent) requirement cannot specify the annual requirement
as related maintenance. Performance of the annual requirement
each time the quarterly requirement is accomplished would in
effect make the annual KRC a quarterly MRC.
(d) A complete eituation requirement MRC (eee 3.11:5.3) may be
related to periodic MRCe when the eituationrequirement la
applicable to more than one periodic MRC within the HIP.
To qualify, the situation requirement must.avoid le~thy
redundant procedures; for example, a lengthy turn on Procedure for a,combat eystem may be documented on a eituation
requirement f4RCand be related to seve:al periodic ~ca.
(e) Reference to another MRC for conditional use is not related
maintenance. For example, reference to another MRC for
corrective action when performance of a procedure doea not
meet a tnlerance requirement is not related maintenance.
(f) Related maintenance requirements ahsll normally be from the
same MIP. To relate MRCa from another MIP; approval of the
PMS Cuordinnting Activity shall be obtained.

1-

3.10.4.5.3 Determining and identifying related maintenance. Salated

maintenance information shall be investigated and sought throughout the
development cycle of maintenance procedures. When a documented related
msintanance requirement exieta that msy avoid repetition of a lengthy action
description, it ehall be identified in the related maintenance column of the
PSS. Alao to be considered and entered as related maintenance are taaks which,
in part, do or re-do some ofthe steps of the task being developed and through
proper identification would result in a savings of manpmver or material reaourcas.
Related maintenance procedures may be available within an MRC aet, or msy be
available within MRCa listed on other scheduled or unscheduled MIPs. Related
msintenanace shall be dete~ined and identified aa follows:

-.,

3.10.4.5.3.1 More frequent periodicity KRs. A MS with the more frequent

periodicity requirement shill be method studied before those of less frequent
periodicitiea (see 3.10.2). When this sequence la followed, certain repetitive
maintenance actiona will either appear in more than one procedure, or eimilar
(closely related) actions ~11 become evident. In either caie, these actions
shall be analyzed to determine if the procedures in which they appear can be
classed as related mairrteti.ence
requirements. The MR with the leaa frequent
periodicity shall identifythe periodicity code of the mere frequent requirement
as the related maintenance requirement so that proper advantage can be taken
during scheduling of the requirements. The periodicity code; for example, W-1,
S-2, of the more frequent periodiclty shall be entered on the PES when it haa
been determined:

39

MIL-P-24534A(NAVY)

(a) That a bOnafide relationship with a savings in M/H or material

exists.
(b) The prOcedure under development ia of a less frequent periodicity. When no related maintenance items are applicable, the
word none shall be enteredin the related maintenance column
on the PES.

@
J

3.10.4.5.3.2. Related maintenance requirements. Related maintenance

requirements shall be identified by the MRC code in the tools, parta, materiala,
test equipment block; for example, MRC EL-12:M-8; and, if required, in the procedural step of the MRC that will be developed from the PES. When it la important that the related task be accomplished at a apecific point in the procedure,
that action shall be included as a procedural step, for example, adjuat flyback
cnntact aaaembly a8 deacribad on MRC EL-12:!4-8. In addition to relating maintenance actinna to effeet a aavinga in ti/Hor material, maintenance may be
related to take advantage of atepa which would otherwise become repetitious.
2%1s la especially true for procedures available an situation requirements or
UM requirements. When the repetitious procedure is.less than IO procedural
steps in length, it shall be repeated in the subject procedure rather than
referred to as related. When the accomplishment of the related maintenance ie
mandatory becauae it contributes directly to the maintenance described on the
MRC being developed, it shall be identif
ied on the MIP by the symbol # following
the periodicity entered in the related maintenance column.
3.10.4.6 Number of men and rate. Aa each step la being develnped in the
improved method, determine an appropriate rate (ace 3.11.6) associated with the
procedural step and enter the rate and the quantity of men required in the rate
column on the PES.

@
.3

3.11 Preparation of MRC verification draft. Por each development or

redevelopment, the PliSDAshall submit to the PMS Coordinating Activity a
verification draft of each MRC in accordance with the data ordering documant
apecified in the cnntract or purchase order (see 6.2.2.). The verification
draft shall be in the format of the appropriate form (ace figurea 15, 16, and
17). A2though the verification draft shall be typed, atrike overa or the
correction of minor errora.will be acceptable. The HRC verification draft
shall comply with the following.
3.11.1 Style of text. Text shall be prepared in accordance with the
atylc specified in the following paragraphs and in appendices A through D.

3.11.1.1 Wording of text. The procedural stepa shall be factual, clear,

concise.
.. and not suaceDtible to miainterpretation (see appendix A). This
includee, but 1S not l~~ted to, the fOllOwinE requirements:
(a) Omit theory.
(b) mere possible, avoid phraseology requiring specialized knOwledge.
Technical phraae.ologywill be used only when no other word or
phraae will convey the intended meaning.
(c) Avoid euperfluous words and phrases.
-0
d

MIL-P-24534A(NAvY)

(d)
..

.0

.:,..

~~

, .,

(e)

SrIecif
v limits. When a measurement or adjustment is called for,
~he o~timum value will
be stated
followe~
by a range
cable;
for. example,
2000 (1995 or 2050) yards.

if

appli-

Normally, removal and inatallatioriprocedures shell be.complete.

Inatructiona such as reverse removal procedures shall not be
used. If a remval or installation procedure ia obvfoua, the
primary step shall -begiven as a command; the detaila shall
not be required. For example, the phrase, P.amoveattaching
bolts,
is aufficient when the method of removal will be
obvious to the technician.

3.11.1.2 Grammatical person and mode. The second person imperative ehall
be used for operational procedures; for example, %=@ve
rammer tank fluid filler
C&-.
The third pereon indicative shall be waed for description and discueai.on;
for example, Ground indicator light will flaah when poeition of S2 ia changed-.
3.11.1.3 Level of writing. The wording of MRCa shall be for a technician
who has a reading ability and comprehension thatcorreeponda to the training
experience leve1 of the rate required to accomplish the task.
3.11.1.4 Consistency. An NRC aet shall be prepared to assure consistency
.eqdcontinuity of content.

I
i -+

3.11.1.5 ,Useof numerals.

appendix C.,

3.11.106 No&nclature.
Official nomenclature shell be used if assigned.
N=nclature
shall be used to Drovide a cnnaiatent description of procedures
and equipment. The following ;equiremente will apply:
-

Use of numerals shall be .inaccordance with

(a) Nomenclature coneiatency shall be maintained; for example, a

part ide.nt
ified as a cover shell not be identified thereafter
aa a plate.
(b) Nomenclature and item name waed in the text shall agree with
nomenclature and item name on ralated engfneertng and design
drawhga and on.identification platea, except it shell be
ueed in its normal readina eequence; for esample, Radar Set
AWSPG-55B.
When
nomenclature ia other then official, lowercaae letters
(c)
shell be used; for example, parallas corrector, motor generator, antenna coupler.
When
two or more items hava the same nomenclature, a modifier
(d)
shall be added to clearly define the function of each item,
its distinctive physical properties, or both; for esemple,
eignal data converter and frequency converter.
The first time an equipiaentitem appears,
it ehall be identi(e)
fied fully. Further referencea may omit offi,cialnomenclature
modifiers where there is no possibility of confusion; for
example, the.name Missile Test Set W 1 Mod 1 introduces the
equipment by its official nomenclature. Thereafter, the
mark and mod designations may be omitted.
(f) Where more than one mod of equipment la described, each mod
shall be indicated; for example, Nagazine Mk 6 Mods O and 1.

41

MIL-P-24534A(

NAVY)

3.11.1.7 Capitalization and punctuation. Unless otherwise specified

herein, the United States Oovernmen.t.
Printing Office Style Manual shall be
ueed as a guide for capitallzationand punctuation (see appendices C and D).

a \

3.11.1.8 Spellin~. Unlees otherwfee speci:ied herein, the United States

Gc+ewent Printing Office Style Manual shall be the authority for spelling.
Worde not in the 6tyle manual ehall be spelled in accordance with Webster*a NInternational Dictionary.
I
3.11
.1.9
Abbreviations. The use of abbreviation shall be avoided whenever p-saible. If it ,ie necessary to uae an ebbreviatiti, the only abbraviatic*e
employed,shall be those in common usege and not eubject to misinterpretation.
Abbreviations that are not in common use and are to be used frequently in a NRC
should be ,clarifiedwhen first ueed by spelling out the word or complete phraae,
followed by the abbreviation in parentheses. Abbreviations ehall be in accordance
vfth MIL-STI+12, where applicable. Abbreviations not included in tbe NIL-STO-12
shell:

(a)
(b)
(c)

Reflect general Navy usage.

Be used when no doubt exists as to the interpretation by tha
rating specified on the MRC.
Be approved by the PNS Coordinating Activity.

3.11.1.10 Siizneand symbols. Signs and eymbols shall be ae listed in the

United Statee Government Printing Office Style Manual. The following rulas
shall be observed in the use of symbole:
(a) Fire control symbols shall be in accordance with &AVSSA OP
or extensions of these symbols require prior
1700. Deviations
aPProval by the P* Coordinating Activity.
(b) Chemical symbols ehall not be used unless they form part of
the nomenclature. In lieu of symbole, chemical nemee such ae
carbon dioxide and hydrogen peroxide shall be used.
(C) Graphic symbols shall be in accordance with fdV31Y32.2 for
electrical and electronic diagrams, MIL-S2W17-1 and tiSTO-17-2 for mechanical parte, and ANSI Y32.14 for logic
diagrams.
(d) Reference symbolsand designations for electrical and electronic perte and assemblies shell be as marked on the equipment (see 3.11.2.1). When not marked on the equipment,
they shall be as epecified in ANSI Y14.15, Y32.16 and supplemente thereto.

3.11.1.11 Warninse, cautiona, and notes. Warninge, cautions, and notes

shall be used ea adjuncts to the text and shall be used as eparingly aa possible
consistent with safety. Warninga, cautione, and,notea are outlined asfollova:
(a) WARNING: A etatement used to call attention to an operating
procedure or practice that, if not correctly followed, could
result In injury or death.

I
I

42

MIL-P-24534A(NAVY)

(1)

Warnings shall be listed in the safety precautions

block (see 3.11.11).
(2) Warnings shall be repeated verbatim immediately preceding each step for the procedures involved.
(3) Warnings shall be in the same order in the safety
precautions block as they appear in the procedure
block.
(4) Maintenance steps that include safety procedures within
the step need not be repeated aa a warning or listed
in the safety precaution block.
(5) Warnings shall not contain procedural stepe.
(b)

(c)

CAUTION: A statement used to cell attention to a maintenance

action thet, if not correctly followed could result in
equipment damage.
(1.) Cautions shall precede the instruction for the procedure
involved but shall not appear in the safety precaution
block.
NOTE: ArIyhelpful information that wfll improve, facilitate,
or provide supporting data for a task.
(1)
(2)
(3)

(4)

3.11.2

Notes shall not contain procedural steps.

N;t;; ~h~;l be used to amplify R periodicity codes (ace
. . . .
Notea shall be used to continue entries too numerous
for the space provided by one of the fixed blocks (aee
3.11.13.2).
Notes shall normally precede the text to which they apply.
Notea may follow the text if required for clarity. The
only exception to this rule ia that notes muet precede
alte~nate procedures (ace 3.11.13.8).

References.

3.11.2.1 )kWiPTIW
nt marking references. References to identifying numbers,
switch positions, and panel markings shall ba exactly aa marked on the equipment;
for example, spelling, abbreviatlona and capitalization. Where neceaaary,
explanation of thase markings may be included.
3.11.2.2 Figure references. The text shall refer to figurea which
support it. Figures shall be assigned figure numbers (see 3.14.5.1). When
referenceis made to a figure, the reference shall be to the .f igure number.
FigUrea shell be numberedsequentially starting with figure 1 within each NRC.
3.11.2.3 Health hazard precaution data referencea. When hazardous
chemicals or other adverse health factors are present in the environment or
will appear during the uae of the equipment and these health hazards cannot be
eliminated, appropriate warnings shall be included. Necessary protective
devices for personnel shall be listed on the MRC in the tools, parts, materials,
test equipmant block.

43

KIL-P-24534A(

tWVi )

3.11 .2.4
Figure
itero references.
Ubere references
are made in a given
procedure
to +everal
items in the same figure,
the figure
number need be given
only at the beginning of the references. Index numbers, letters, or ref~rence

symbols of the references shall be pl!c~d in wrenthesee in the body of the

text where pertinent. Care shall be taken that .euch references are entirely clear.
3.11.2.5 Measurement references. References to units.of measurement
shall be specified in the same units to which the equipment waa designed.
3.11.2.6 Model references. The procedural stepa shall refer only to
equipmcnt covered by the MRC. To facilitate later incorporation of additional
models, references to model designations or other unique identifiera shall be
held to a minimum constacent with clarity. Any such references made shail be
expressed in definite terms, such as model designation, part number, serial
number range, or similar means. Such terminology as on early serial numbers
or on some late mmdela is not acceptable.
3.11.2.7 Other publication references. Each PMS MIP and MRC aet shall be
a complete,
self-contained
maintenance
entity.
Unless
othervise
required
herein,
reference
to other publications
or instructions
shall
be approved by the PMS
Coordinating
Activity
before inclusion
in an MRC. References
shall
be restricted
to an extreme minimum so that each tfRC ehall
present
a complete planned maintenance tool.
3.11.2.8 Maintenance requirement card references. When reference ia made
to text elsewhere within the MRC or to other MRCS, it shall be aa specified in
3.11.13.4.

0
-\

3.11.2.9 ~ecif ication and standard references. When a Government or

military specification or standard is referenced, only the basic number shall
be used. The revision letter-suffix shall be omitted unless it is essential.
For example: P-C-444, MIL-C-5020, and MIL-STD-105.
3.11.2.10 Table references. When reference is msde to tablea, the
reference shall be to the table number. Tablea shall be numbered sequentially
starting with table 1 within each MRC.
3.11.2.11 Temperature referencea. Temperature readinga ahsll be written
aa indicated on the related instrument.
3.11.2.12 Tools, parts, materials, and test equipment references. Ml
portable and non-installed tools, pa;ta, materials, and test equipment required
for the maintenance procedures on the HP.Cehall be listed under appropriate
heading in the tools, parts, msteriala, test equipment block on the MRC.
3.11.3 Locator cards for classified MRCa. An unclassified single page
locator card (see figure 25) shall be prepared for each classified MRC. The
locator card shall b: a duplicate of the ilassif
ied f4RC in al 1 blocks except
the procedure block.
An exception
to this rule is when entries
in the cools,
For example,
a
parts,
materials
, test equipment block compromise security.
signal
generator
is listed
among the test equipment required;
the signal
generator
operates
at a frequency
which must be in the frequency of the prime

44

MIL-P-245

/---

equipment,
this type,

34A(

NAVY)

and the frequency

of the prime equipment is classified.
in the tools, parts, msterials, test
the only entry

In cases

of

equipment block
will be the phrase, Seeclaaaified MRC. The procedure block shall include
notes that are an extension of the data in the MRC Code and Rates M/H block.
One of the fnllowing statements shall appear in the procedure block:
Maintenance procedure with the requirement la CONFIDENTIAL.
Maintenance requirement card ia atowed in
.
Maintenance procedure with this requirement is SECRET.
Maintenance requirement card is atowed in

.*

I
(a)

3.11.4

If the per~odicity code contains an R (ace 3.11.5.3),a note

explaining when the requirement ia to be accomplished ahsll be
in the fi+at entry in the procadure block unless a note la
neceaaary to extend entries in the MRC code and rates M/H
blocks (ace 3.11.5 and 3.11.6), in which caae it would be the
second entry.

Ship

system,

aystern,

subsystem

and equipment

blocks.

These

blocks

in aa specified in the following paragrapha. SWAS level

nomenclature and numbers shall be aa specified in 3.6.5.
shall

be filled

3.11.4.1 Ship ayatem block.

-

number (ace 3.6 .5)

MRC ia applicable.

for

3.11 .4.2
the system

for

the

functional

System block.
containing
the

Enter the SWAS level

group containing

2 nomenclature
and
the item to which the

3 nomenclature
Enter the SWAE level
item to which the MRC ia applicable.

and number

and numbsr
3.11 .4.3
Subsystem block.
Enter the SWAS level
4 nomenclature
for the aubsystam containing the.item to which the f4RCla applicable.
3.11.4.4 Equipment block. Enter the SWAS level 5 nomenclature, the number
of the equipment or component to which the ffRCis applicable and the CDC. If
the MRC is applicable to the entire subsyaternor systern,enter SWAS level 4, or
level 3 nomenclature and number aa appropriate.
3.11.5 Maintenance requirement card code block. Enter a two-aegmant Code;
for example, 4416 Q-2, 7211 Q-1, or A-1OO Q-1. The first aagment is the MIP
aeriea code which wi 11 be provided by the applicable PMS Coordinating Activlty.
FfRCsapplicable to mnre thsn one MIP aeriea will have each MIP aer}es entered
in this block.
If more than four MIP aeriea are applicable, reference shal1
ba made to a note. The note shall be numbered and appear in the procedure block
block to provide the additional information. The second segmant ia the maintenance requirement perimdicity code. The following are the .oflYauthorized
periodicities:

45

MIL-P-24534A(NAVY)

(a)
D 2D 3D w2U If2M Q -

(1)

S
A
18M
24U
30M
36M
48M
54M
60M

daily
every 2 daya
every 3 daye
weekly
every 2 weeks
monthly
every 2 mnnths
quarterly

semiannually
annually
each 18 months
each 24 months
each 30 months
each 36 months
each 48 monthe
each 54 months
each 60 months

calender peric.dicitieemay be extended in 6-month increments. For example: 66U, 72M, 78Ff,and so forth,
up to the scheduled modernization for applicable ship
ciasaes in the extended operability cycle program.

(b) Non-calendar periodicizy.

R- situation requirement
U - unscheduled ~intenance

1
I

(c)

Inactive equipment maintenance.

LU
PM
SU
OT

lay-up maintenance
periodic maintenance
start-up maintenance
Operational test

3.11.5.1 Periodlcity numbering. When more than one MRC is prepared with
the same periodicity for the same equipment or eystem, each shall be coded
individually; for example, D-1, D-2, D-3. Note that each MRC ie asaigned a
periodicity code; however, one MRC may conaiat of several pages and include
more than oneHR. It is not acceptable to have two identically numbered
periodicity codes; for examPle, W-Z, W-2R or R-1, R-lW. When development
analyais reveala that a system or equipment should be tested in several modes or
configurations and each test can .utllizethe same procedure, it is unneceaaary
to provide several MRCS for each mode or configuration. For example, a coumnui~.
cation receiver ie to be tested to see if it has sufficient sensitivity in each
of.aix frequency bands. The teet procedure is the same for each frequency, bui
che switch setup, the teat equipment required, and the desired meter Indicati,x:
MY vary from band to band. The following method shall then be used:
(a) Develop one MRC to provide the step-by-step procedures.
(b) Assign the periodicity determined during requirements analyale,
but change it to include all the accomplishments required by
che varying equipment setup; for example, for a weekly requirenant consisting of six separate tegts which are to be scheduled
individually to ensure ail modes are tes:ed, periodicity code~
.
of W-1 through,W-6 are assigned to the six MRCS.
(c) Include in the preliminary procedure a matrix or a note which
associates each tesr.with the proper equipment and parameters.

46

MIL-P-24534A(NAvY)

3.11.5.2 Dual periodicity. When configuration, environmental, or utility

differences nf a permanent nature exist between installations of the same system
or equipmaut, a dual periodicity may be assigned if no nther aspeccs of the NRC
requires modificstinn to fit both perindicities; for example:
Equipment installed in a surface unit may see daily uae, while
the same equipment installed in a stibmarinemay be idle for long
periods nf time because of the nature of the ships mission.
This long period of idleness may make it unnecessary to perform
some KRa as frequently as in other installations. In this case,
a dual periodicity such aa M-l/Q-l or Q-1/S-2 msy be assigned.
(b) The paper tape unit of the input snd nutput console in the TARTAR
configuration is used mwch more frequently than the same paper
tape unit in the TERRIER cnnfiguration. To prevent burdening the
TSRRIER m@tenance
technician unnecessarily, a dual periodicity
may be assigned to the paper tape.unit MSS; for example, M-2/Q-3.
(c) Equipment is installed nn the weether deck in one shgp claas, but
is inatallid within a protected space in another ship class. TO
prevent excessive maintenance in the protected environment, a
dual periodicity may be assigned; for example, h-l/M-l.
(d) DUal periodfcitfea.may also be assigned when ahipa OPeratfOnal
tempo msy allnw reduced peric.dicitfesunder specific conditions;
for example, a teat should be performed daily at sea but may
nnly need;be performad weekly in port. Likewiee, some MRCS may
bs allowed to be performed leas frequently when the ship is
operating in CONUS than when the ship is deployed. Whenever
dual periodicities are assigned, a note is required on theMIP
(a)

/--

and MRC to explainthe conditions

governingthe dualperiodicities. For example,for an M-l/Q-l,write: NOTS:SSBN, schedule
quarterly; all others, schedule monthly. Delete unrequited
periodicity bydrawing a line through it. For a D-l/W-l, write:
NOTE: Accomplish daily when deployed and weekly when in CONUS.
3.11.5.3 R periodicity. Cslendar periodicitiea shall be aasigned when
possible. Requirements which cannnt be scheduled on a calendar basis shall be
assigned the situation requirement periodicity R. For example, maintenance
actions required prior t? cold weather operations, pre-firing teata, or inspection
of a aheft and propeller.when a boat is hoisted aboard. Situation requirements
msy also be used for procedures that are applicable to more than one MRC within
the KIP. For example, a lengthy turn-on nr shut-down procedure used with a
number of MRCS. Situation requirements shall be explained in a note on f41P.e
and
MRCa. The situation requirement code may alsn be used with S calendar periodicity
for certain situations. These situation fall within two general categories:
(a) When the situation governs the scheduling of the requirement;
for exs~le, R-lW. An example of this type of requirement ia
a lubrication action that mwat be performed weekly when a ahip
is at sea, but is not required while the equipment is idle
during an in-port period. This situstion calendar requirement
would be assigned a cnde of R-lW, and a nnte on the MIP and NRC
NoTE: When at aea, accomplish weekly.
would,specify the following

47

MIL-P-24534A(NAvY)

(b) ~en. the calendar periOdicity governsthe scheduling of the

requirement; for examp~e, Q-2R. The Q indicates that the
longest time between accomplishment is quarterly and the
requirement would be scheduled once each quarter. However, a
situation could arise which would dictate chat the requirement
be accomplished other than as echeduled by the calendar code.
When the situation was removed,-scheduling would revert to the
calendar basis. The calendar situation combination requires a
note to explain the situation combination on the 141P and the
MRC. The following are some examplee of combination calendar
and situation requirements:
(1) Qoarterly or after every 600 hours, whichever occurs firat
(2) Monthly or after each uae
(3) Semiannually or after each upkeep period
(4) Weekly or before getting underway, whichever occurs firet
3.11.5.4
U perioriicity.
Unscheduled
MRCS shall
designator
U for the periodlcity code. ArIKKC with

use

the

letter

@ .... . ..

prefix

a U periodicity should not

be scheduled in conjunction with a calendar or R periodicity. For equipment
with 100 or more UMRCS, the first 99 MRCS shall be numbered U-1 through u-99
and the remaining
shal 1 be numbered uelng a two-character
alphanumeric
eequence
numbering system.
TMe system shall
uae the letters
A through Z, excluding
I
and O, ae the first
character
and the number O through 9 as the second character;

for example, U-AO, U-Al, U-A9 and U-BO instead of U-1OO. U-101, U-109, and
U-110. Adjustment and alignment unscheduled MRCS will begin with U-1 and shall
be numbered sequentially. The arrangement of the adjustment and alignment
unscheduled UMRCS will be in a sequence to allow for the complete realignment
of the equipment if required.
3.11.5.5 Inactive equipment maintenance periodicity. Maintenance requirement carda developed expressly for IEM will be asaigned a periodicicy code Of
LU, PM, SU, or OT, as appropriate (see 3.7.12).

I
I

3.1.1.6 Ratea block. Identify and enter, by rate and rating, the number
of persona required to perform the MR. Entries in this block shall be made as
follows:
(a)

The Navy Enlisted Classification (NEC) shall be entered if

special ski11s are required. Appropriate special skill codes
shall be determined by reviewing section 11 of NAVPER8 18068D.
(b) When both hXC and rates are important to the task, both shall
be included. For example: Gfi2,with the NEC 0876 listed
beneath the rate.
(c) A commlaaioned officer or warrant officer may be required to
be preaent or available for a specific task indicated in a
maintenance procedure. Titles for officers shall be the
first entry in the block when applicable; for example, DCA,
ENO, Eng Ofi .
(d) In cases where more than one rating is required, ratings
shall be listed after the officers descendir+gby rate within
each rating category; for example, Eng. Off., BT1, BT2, DS2,
MMl, MM2.

I
MIL-P-2453~A(NAVY)

r
m

(e) When more than one person is required for a particular rate,
the appropriate number shall precede the rate; for example,
2xR1, 2sT1,,3ET2. When two or more persons of the name rate
are requir,edand their time requirements are not equal, each
person shall be listed separately. When additional personnel
are required because of aafety regulations, the rate and
number of such personnel shall alao be included.
(f) In caaes where either of two.similar rates can be assigned
the work on an MRC, both rates shall be listed, separated by
a slash. For example: BT/BRl, DS/ETl, GMG/FTG2, MU/BR2,
STIET2.
(g) MRCS with a calendar periodicity or R periodicity shall include
the necessary rates to perform the .~intenance. lfRCSwith a
U periodic+ty shall include rates when so directed by the PMB
Coordinating Activity., Inactive equipment maintenance procedural
MRCS (ace 3.11.21.1) shall also include rates.
(h) In cases where more then five rate entries are required to
perform the MRC, the rates block.will direct the reader to a
note (see 3.11.13.2).
3.11.7

Man-hours block.

(a)

Man-hours (converted to hours and tenthsof an hour) shall be

entered immediately to the right.of each rate in the rates
block. When the M/H figure is less than one hour; a zero shall
aPPear bafore the tenths of an hour portion; for example,
0.1, 0.4. When a commissioned officer or warrant ofEicer ie
required, ho M/H shall be aasigned for that person.
(b) The time entered shall indicate the M/H required for each
~
listing id ratea block as if they were performing their taeh
independently. When two or more of the same rate are required
and their time requirements are equal, the M/E will be the sum
of their requirements. When two or more persone of the same
rate are required end their time requirements are not equal,
each person ehell be lieted eeparetely.
(c) Equip=nt warmup time of 30 minutes or leee ehall be included
in the aeeignedHIM. Warmup time in exceee Of 30 minutee.
ehall not be included unleee the maintainer is required for
constant observance.
- or put away time ehall not be included in this
(d) Make ready,
block.
(e) When another MRC or procedure is referred to in the procedure
block and only a portion
of that BfRC or
accomplished,
time required
t,o do that

procedure

la

tb

be

portion shall be
included ~n the M/H of the pereon accon@liehing the taak of
the sub.j
ect MRC. However, if the referenced procedure is an
entire echeduled related MRC, the M/H of that MRC ehall not
be included.
3.11.8
block.

Total M/H block.

Total F@

ehall be the eum of each entry in H/H

49

MIL-P-24534A(NAVY)

3.11.9 Elapsed time block. The entry in this block shall indicate the
.elapaedtime, in clock hours and tenths of an hour, from startto finish of the
maintenance procedure. The time involved for preparation to accomplish the tagk
and cleanup time upon completion aha.11not be included. The elapsed time entry
doea not always duplicate the longest entry in M/H block.
It may be longer
when some personnel must wait for others to accomplish certain procedural steps.

3.11.10 Maintenance requirement description block. Each MR description

shall be numbered. The first letter of the first word in the MR deacriution
shall be capitalized with all other words in lower case. When authorized
abbrevi?tiona or proper nouns are included in the description, they shall be
completely capitalized or initially capitalized aa appropriate. The KR description shall be a complete sentence (second person imperative) and shall begin with an active verb; for example, inspect, teat, calibrate, adjust, lubricate,
clean, or replace. The description shall be as brief aa possible and shall
reflect precisely the task required. The description shall identify what ia
to be performed, leaving descriptions of performance in the procedure block.
3.11.10.1 Incidental
words.
Words such as disassemble, dismantle, remove,
or open are incidental to accomplishment of the requirement and should appear
as a step in the procedure, not in the MR description.
3.11.10.1.1 Identification of the complete maintenance action. IheMR
description shall clearly identify the complete maintenance action. For example:
Clean and inspect sump; clean and lubricate antenna drive gears. A simple statement
such aa, Cleanradio transmitter, is not acceptable when the MRC procedure
includes inspections not associated with cleaning the radio transmitter.

3.11.10.1.2 Intent of the maintenance task. The MR description shall

reflect the intent of the maintenance task. Use of verba describing ancillary
or incidental functions to the main intent of the task is unacceptable. For
example: clean off greaae fittings on fire pump bearing, inject greaae with a
grease gun,and inspect the old grease expelled; should be described with the
phraae, lubricate fire pump bearinga. Do not uae the phrase: Clean, inspect,
and lubricate fire pump.bearinga.
3.11.10.2 Multiple requirements. When multiple requirements are called
for on a single MRC, each specific requirement shall be identified and listed
in chronological order of performsnce; for example:
(a) Meaaure preamplifier gain.
(b) Test bearing accuracy.
3.11.10.2.1 Combination of multiple actions into one requirement. Multiple
actiona shall be combined in one requirement only when they are ao related that
the accomplishment of one causes the other action to start or the actions are
accomplished simultaneously. For example: 1. Clean and Inspecc sump; replace
lube oil filter.
3.11.10.2.2 Exceptions in certai~ situations. An exception to this
situation, however, is a MR description such as, Inspect Internai parts.
This requirement includes the inspection of a quantity of imiividal items too
terminology
is
numerous to attempt to cover in the t.fR description. Descriptive
needed in the HR descriptio,l
for a complex system or equipment comprised of a
50

HIL-P-2453bA(NAVY)

C_

mmber of units.
The
deecriptlve
enough to
is Intended.
In this
identification
of the

1.
2.
1.
1.

overall system or equipment title may not be sufficiently

allow.positive identification of the unit for which the KS
case, the.MS description shall include a noun nams
unit; for example:

Balance video receiver.

Msasure audio receiver gain.
Calibrate transmitter program control circuits.
Clean and inspect motor-generators.

3.11.11 Safety Precautions block. When all required safety precautions

are explicitly included in technical documentation available to the !rutIntainer,
thefirst entry in tNs block shall identify that documentation by publication
number and volwme. For example: Observe standard safety precautions In accordance with Safety Summsry in technical manual SW394-AC-KMA_OIO/LSIO. When such
asauranceis not available, the flrst entry shall be: Forces aflost comply with
Navy Safety Precaution forForces Afloat, OPNAVINST 5100 ser~ea; shore A@vitiea comply with Safety Precaution for Shore Activities, NAVMAT P-5100 series.
Whenthe documentation relates to a system or equipment which haa no utility
ashore. only the first sentence shall be entered. then utility will be shore
only, the f~rat sentence shall be omitted.
3.11.11.1 Mditional warnings. Additional Or more specific warnings
shall follow when applicable and shall be listed in the order in which they
aPPear in the procedure block.
F.

3.11.11.1.1 Additional warninga requiring the use of additional personnel.

For those actions which require additional personnel because of safety regulations
(see 3.11.6e), the phrase Do not work alone, ahslibe added to the applicable
aafety precaution. For example: Voltages dangerous to life are present when
interlock stitch ia bypasaed. Do not work alone.
3.11.11.1.2 Capitalization required. The first letter of the first word
in each safety precaution 6hall be capitalized, with all other words in lower
case, unless capital letters are required for another reaaon.
3.1I.11.2 Submarine auplications. In submarine application when sub-safe
boundaries are to be violated, comply with current re-entry control requirements.
The statement, Cmmply with current QA/Sub-Safe Instructions, shall aPPear in
this block.
3.11.11.3 Cleaning ablvent. The following standard safety precaution la
to be used whenever cleaning solvents are involved: Avoid prolonged contact
with, or inhalation of, cleaning solvents. Avoid use near heat or open flame
and provide adequate ventilation.

_-

3.11.12 Tools, parte, materiala, test equipment block. Enter and number
the requiredtest equipment, materiala, parts.,tools, and miscellaneous
requirements, in that order (ace figure 26). Each applicable category shall
have a heading. Items within the category shall be numbered and identified by
the applicable Standard PMS Item Name (SPIN) (ace 6.4) number in brackets. When

51

MIL-P-24534A(NAvY)

space allows, a tuo-colunm listing

shall
be used. Entries in this block shall
& selected from the SPIN and may be cross-referenced to the Standard PNS
Materials Identification Guide (SPMIG) (see 6.4).
These items are sorted
into
five baaic categories which are defined as,follows:
1

(a)

Category 1 - Portable

(b)

general purpoee PEETE that have potential PMS application.

All items are assigned a sub-category code (SCAT) which groups
ten~ equipment models having the same teat capability into one
code. Aboard ship, the Shipa Portable Electrical/Electronics
Teet Equipmsnt Wquirements List (SPETERL) established allmwancea for PEETE within each SCAT code. MRC test equipmsnt
requirements must be ayncbronized with the SPETERL.
Category 2 - Consumables.

electrical
and electronic
test equipment
(PEETE).
Category
1 is used only for PEETE as specified
in
NAVSEA-TM-STOOO-AA- lDX-010/PEETE.
This equipmsnt
includes
most

(1)

Consumables
to support

constitute
a majority
of
Pros.
Category
2 includes

msterials
required
a wide range nf

administrative and housekeeping items which may or tiy

not in fact be consumed in use. Some consumable items
(greaae, oils and snlvents) are cnnsumed each tiresthe
maintenance action is performed whereaa others (pails,
furine
1s and ladders) are not. Tools are not included
in category 2 even though snme toola mcy fit the general
description of a consumable item.
(2) Sxamples of consumable items include ropes, rags, oil,
cleaning solvents, brushes, corrosion protection agents,
sealants, and protective coatings. Bulk gaeket and
packing materials are considered repair parts (category 3)
since these are APL worthy items and must be listed on
APLa . By definition, any item appearing on an APL ie
considered a repair part.
(c)

Category 3 - Repair parts.

(1)

For purpnsee of MRC development, repair parts are defined

as any item which ie an integral part of the equipment.
For example: gaskets, mechanical seals, packing material,
O rings and filters. In general,
any item listed in a
technical manual or drawing parts list is considered a
repair part. An official definition of a repair part
is any item appearing on an Allowance Parts List (APL).
Although in some caaes repair parts will not appear mn
the APL, this does not necessarily mean the item la not a
the APL
repair part. In fact, it is a good indication
maY be tect.aically
Ca.
incenanee
all

(2)

deficient

in

that

it

cioes not

list

sig-.
ifi:tnc repair par.cs.
Although repair parts cent, citute a relatively
smail perPMS !@& nf a ship, they are probably
centage
of the total
the most critical of all requirements. A maintenance
action requiring parts cannoc be effectively completed
unless those parts are readiiy available from an onboard

52

MIL-P-24534A(NAVY)
/-

sgpply
department
stock.
In many casea,
of a specific consumable,
availability

the non-

requirement

the APL.

tool, equipage, or
even teat equipment may not jeopardize the aucceaaful
completion of a maintenance action because use of alternative materiala la often possible, although certainly not
desirable. With respect to moat repair parts, however, a
specific item must be used; there are no real alternatives. The medium for identification of PMS repair part

(d)

(2)

System

is

Category 4 covers hand tools of all types except special

tools. Special tools are by definition equipmentunique tools that are designed for a particular piece
of equipment by the manufacturer. Such tools always
have a manufacturers part number and Federal Supply Code
for Manufacturers (FSCM). In accordance with NAVSEA/
NAVSUP policy, special tools will be listed on an APL
and are, therefore, classified as repair parta.
Category 4 includes common hand tools typically found in
any work center tool box as well as other leaa common uae
tools. For example: precision measuring devices, dial
indicators, micrometer, torque wrenches, and gagea.
Equipage items are category 5 even though some may be
ua{d aa a tool; for example, Jacking gear.

Category :5 - Equlpage and special materials.

(1)

Category 5 covers all equipage items as well aa any other

special materials not otherwise covered under categories
1 through 4. As a general rule, all items which are
identified and supported through Allowance Equipage Lists
(~La) will be considered category 5. Not all category 5
items are AEL applicable. ~pical examples nf category 5
materiala ire as follows:
a.
b.
c.

d.
e.
f.
g.

the. Navy Supply

Category 4 - Tools
(1)

(e)

to

h.

i.

Teat equipments not lieted in the TEI which, therefore, do not qualify ae category 1.
Radiac equipment or doaimeters.
Sound powered phonee, binocular, teleacopea, boresighte, and portable equipage items of all typea;
for example, fana, pumps or blowers.
Soiler feedvater teeting equipment. Feedwater
chemicale are category 2.
LUbe or fuel oil sampling kite, centrifuges, and
testing apparatus.
,A21 items designated as controlled equipage.
Safety harnesa, lanyarde, and other safety equip~nt.
Special clothing items including rubber gloves, and
other items designated to protect users from chemical or toxic agenta.
Vacuum cleaners of all types.

53

MIL-P-24534A(twwf)

Chain fails, jacking gear devices,

and other handling equipment except common hydraulic jacks which
are considered category 4.
k. Special teat.tapes, diagnostic tapes, alignment or
tapea.
1. Special connecting and adapting devices necessary
to rig teat equipment to prime equipment if such
items are not supplied with the teat equipment.
m. Special software and support documents including
supplemental MRCS, equipment technical msnuals,
handbooks, guides, and Naval ships technical
manuals.

j.

3.11.12.1 Non-SPMIG tools, parta, materials, teat equipment. Entries in

the tools, parta, meteriala, test equipment block not covered by the SPIN or
SPMIG, shall be determined and listed as follows:
(a) Electronic and electrical test equipment shall be selected from
MIL-STD-1364. Test equipment will be identified by noun name,
nomenclature, and SCAT code according to NAVSEA STOOO-AA-IDX010/PEETE. When SCAT codes are not established, identify by
noun name, manufacturer, model number, and ASL number.
Materials
include lubricants, greaaea, solvents, cleaning
(b)
agenta, and other conaumablea, such aa tape, safety tags, or
pencils. Lubricant, greaaes, solvents, and cleaning agenta
will be identified by Military, Federal or Navy specification
military symbol and the item name. For example: Oil,
MIL-L-22851; Silicone compound, VV-D-1078. The Planned Maimtenancg System Lubricants, Compounds, and Cleaning Agenta - Cross
Reference Guide (see 6 .4) shall be the source of these nomenclatures. Other consumables shall be identified in accordance
with the nomenclature specified in the alphabetic index of
NAVSUP Publication 4400.
(c) Parta include all repair parts such as gaskets or O-rings.
Sepair parts will be identified by generic name, nranufacturers part number, and the FSCM. The illustrated parts
breakdown, menufacturera pamphlets. supply catalogs. APLs.
AELS are sources for these nomenclatures.
(d) Special tools such aa gage pieces or thrust bars shall be
identlfied by name, manufacturers part number, and FSCFt.
(e) Common tools shall be identified using the nomenclature format as listed ir.the alphabetic index of NAVSUP Publication
4400.
Miscellaneous

such as MI(CS,technical manuals,

requirements
or forms, shall be identified by standard nomenclature or
generic name.
(g) Uben the MRC procedure refers to another MRC or technical
manual for a step-by-sLa? procedure, that KIC or technical manual shali beIistei.
(h) @antities in excess of one and units af masure shall be
enclosed in parenthesis following tnenomenciacure ar.d
complete description of the itex. For exanpie: Wrench,
adjustable 8(2); Baking soda (2 15s).

(f)

54

MIL-P-24534A(NAVY)

,f-

(i)

..
(j)

(k)

(1)

(m)

(n)

(0)
(p)

(q)

(r)

(s)

Symbols of ,, 0, and % shall be entered for inch, foot,

degree, and percent. Fractions shall be typed with the
numerator and denominator separated by a slash; for
example, 1/2, 1/4, 1/6.
The term or equivalentshall not be used with any item
listed in the block. Equivalent items, if authorized,
shall be specified as a note in the procedure block.
A zero shall bs placed before the decimal point when
another figure does not precede the decimal. ThiSshall
occur even if there is a zero.after the decimal point:
for example; Wire, nonelectrical, 0.051.
A national stock number (NSN) shall not be included. National
stock numbers, when authorized, shsll .beapecified as a note
in the procedure block.
The solvents used aboard nuclear aubmsrinea shall be in
accordance with NAVSHIPS 0938-LP-011-4010. MRCa for
nuclear submsrine applications shall uae the phrsee,
approvedaafety cleaning eolvent.- For other ship
applications, apecific cleaners shall be identified.
Por documentation which will bs used in both nuclear
eubmsrine and other ships, a double statement will be
used; for example, Nuclear Submarines: Approved safety
cleaning solvent; other
ships: Solvent, P-D-680, type II.
When sub-safe boundaries are to be violated in eubmsrine
applications, current re-entry control requirements shall
be complied with and the Sub-Safe Re-entry Controi Form QA ifo~ 9 (NAVSHIPS 90S0/1) shall be included.
When fabrication of a unique tool is required, specification for fabrication shall be included on the MRC.
Only portable and non-installed equipmant required to IX&
form the maintenance procedures shallbe lieted in the
tools, parts, materials, and test equipmant block.
Installed equipment required to support the maintenance
procedures shall not be listed. This equipment shall,k
specified in the appropriate procedural step.
Each entry shall consist of one item only; for example, if
an oiler with lfIL-L-6068oil la required, the oiler will
be listed under the tool heading, and zhe oil will be
listed under the msterial beading (see figure 26). If
more than one oil is required, the procedural step shall
specify which oil is required for that step.
In the event that entries in this block must be centinued
to the second page, the heading information, Toole,
Parta, Materials, Test Equipment, shall be printed on
the second page.
In the evant that entries are to be provided by another
activity; for example, Sf4MSSite Team, the entry will ba
followed by the phrase, in parentheses (ace NOTE 1) and
an explanation provided in the note in the procedure
block (eee figure 27).

55

WL-P-24534A(KAVY)

3.11.13 Procedure block.

to accomplish the MR. Entries
standards:

This block shall

contain
step-by-step
procedures
in this block shall,conform to the following

mL

(a) The language used shall be free of vague and ambiguous terms
and shall use the simplest words and phraaea that will convey the intended meaning.
(b) Sentence structure shall be short and concise to facilitate
understanding and retention of thought. Steps shall be
straightforward and simple. Steps with compound clauses
shall
bs converted
into sub-steps.
Consistency
in choice of words and

terminology and organization of material is mandatory.

(d) Steps shall be written to consider the technical qualification of the rating required to do the task.
(e) Inspection and measurement steps shall ciearly specify limtts
so that a condition can be easily determined to be acceptable or unacceptable.
(f) When extensive punctuation is necessary for clarity, the
atep(s) shall be rewritten to eliminate that need.

(c)

3.11.13.1 Safety. Ensure that all procedures are a&fe. Whenever po~sible,
maintenance actions ehall be accomplished with equipment in a shutdown condition.
Procedural steps directingremoval of voltage or pressure shall be explicit as
to which switchee or valves are intended and shall include tag-o~t action in the
same step; for example, De-energize unit and tag-out 400 Hz exciter voltages.
Where components capeble of holding a charge are included In the circuitry, a
procedural step shall be provided to direct discharge of such components; for
example, short high-voltage, high-capacitance components co ground us,ingshorting
probe.

.
=

3.11.13.2 Notes. Notes shall be used to supply needed information that is

not an action step (see 3.11.1.11). Excessive verbiage shall be avoided and te
note shall be limited to necessary specifics. N:]tesshall be sequentially
numbered if there are more than one. Tolerances and clearances shall not be
given a!inotes but shall be included in the procedural step in which they are
observed.
3.11.13.2.1 Maintenance requirement cards having Z periodicity code.
Maintenance requirement carda having an R included in the periodicity code
shall have notes aa specified i~ 3.11.5.3. This note shall be the firat item
in the procedure block and aiso appear ioilowing the requirement on the MIF.

3.11.13.2.2 Maintenance requirement card procedural exceptions. When a

block Of an MRC (see figure 28) is tOOsmall tO enclOse all required entiiess
insert in parentheses the phrase, (see NOTE 1). In that note, list the entries
normally made in the block. For this purpose, rates and M/3 shall be cOnsider?d
as one.block, and the cctal ?l/Han.fciapsed time entered in their assigned space.
3 .11.13.3
Warnings
and cautiofis.
as necessary
in the procedure block as

cautlnns shall not be numbered.

Warnings

and cautions

shall

be included

specifiea in 3.il.1.11. warnings and

MIL-P-24534A(NAVY)

3.11.13.4 References. References to other publications shall be as

specified in 3.11.2.7. References to text elsewhere within the MRC or to other
MRCs shall be as follows:
.
(a) When writing procedural steps, it is permissible to .ae the
phrase, repeat step(a). The reference shall be to procedural atepnumbers only; for example, repeat steps 2.d.
through 2.f. to ensure accurate measurement. Unless the
sequencing is very clear and understandable, the phraae,
repeatstep(s),should not be used. Repeat steps which
aend the reader to a step which is already a repeat step
shall not be used.
(b) men certain taaks are to be accomplished in a specific
sequence in the subject f4RCand the procedure exists on
another MRC, that task and MRC may be referenced to avoid
repetition. The referenced PfRCmay have a calendar, R or
U periodicity.
(1)

When the referenced f.fRC

is to be accomplished in its
entirety, it shall:
a.
b.
c.

Be referancad as a step in the procedure; for

example; Lubricate unit as deacribsd on MRC Q-1.
Appear in the tools block; for example, MRC Q-1.
Appear.in the related maintenance column on the MIP;
for example, aa Q-l/, with the following notation
on the MIP, following the scheduling aid:. # f4andatory scheduling required.

(2) When,only a portion of the referenced MRC la to be accor

plished and the repetitious procedure is 10 procedural
steps or more in length, it shall:
a.

Be referenced as a step in the procedure; for

example, Accomplish steps 1.h. through 1.t. as
described on f4RCR-3.
b. Appearin the TEFIPTEblock as MRC R-3 but not in
~ related maintenance column on the f41Psince it
cannot be scheduled and marked aa completed.
c. Reflect the time required to accomplish that portion of the referenced MRC in the M/H block of
the subject KRC.
d. Rsflect in the TEMPTE block the test equipment,
materials, parts, tools and miscellaneous items
required to accomplish the refarenced stepa.
(3) Uheritherepetitious procadure is less than 10 procedural
atepe in length, it ehall be repeated in the subject
procedure rather than referred to as related maintenance.

57

-..

MIL-P-24534A(NAVY)

(c) Unscheduled maintenance requirement cards shall be referenced in

scheduled MRCS when it is desirable to establish a relationship
between the two. To do this, the appropriate step in the
scheduled MKC shall include a statement similar to the follc.wing:
If,measured value ia not within prescribed range, performMRC
U-2 (or steps 1.a. through l.k. of MRC U-3) and repeat this
measurement.

*
-

3.11.13.5 Fill-in blanka. Fill-in blanks are juatified in the procedure

when the data concerns valuea that vary from ship to ship due to installation
or configuration variances.
(a) IWO categories
Of blanks subject
to fill-ins are acceptable
for use in the Procedure block of an FIRC when approved by
the applicable
P14S Coordinating
Activity.
(1)

(2)

to
Fill-ins
for values or locations which are pertinent
the procedural step and which vary from installation
to installation.
Those blanks which require fill-in
data to complete the
blocks
of a table
from which other computations
are
msde.
A horizontal
line of the appropriate
length
shall
be inserted
in the proper
location
to accommodate the fill-in
infotmstion;
for example:

Md

the following values to determine MN.:

a. Signal generator output attenuator
b.
c.

(b)

RF cable attenuation
Directional
coupler

dBm
dB
dB

attenuation

safety requires that Ewitchea either remote to the system

or equipment being maintained or not considered as associated
with that system or equipment be set to the OFF position,
these switches shall be listed by item name and a fill-in
in which user personnel shall fill in data Pertinent
provided
to the individual installation; for example:

When

De-energize and tag main power supply switch located

De-energize and tag gyro input at
Da-energize

and tag

heater

When it is determined
that
it shall
be msndatory
thst
MIP as
tn the controlling

supply

switch

located

a fill-in
blank shall
the following
notation

be utilized,
be applied

a scheduling aid:

contain(a)
blanks
to be filled
in by
Until these fill-in
data
ships
force
before
implementation.
elements
are applied,
c!w WI cannot be effectively
accomAdvise
via PMS fcecback report
ii :ne required
fili plished.
in data ,1s not available
to ships
force.

MRc(s)

-.

58

MIL-P-24534A(NAVY)

a
I

3.11.13.6 Preliminary. When steps are necessary to prepare the system or

equipment for the maintenance action(s) prior to beginning the KR, the MRC will
contain a preliminary procedure. Typical preliminary stepa are: energizing
equipment, warming-up equipment, positioning switches, opening doors, eatabliahing
communication, preparing setup of teat equipment, and ensuring safe conditions.
(a)
(b)

(c)

(d)
>.
(e)

(f)

(g)

ID

(h)

Preliminary steps shall be listed under the heading Preliminary and shall appear before the first MR description.
The first letter of the word Preliminary shall be capitalized,
the entire word underlined or in boldface, and it shall not be
punctuated.
The word Preliminary shall be followed by a minimum of one line
of text befole continuing to the second page. If space does
not permit the one line of text, the preliminary heading will
be started on page 2 of the MRC.
Preliminary stepa are preparational actions and shall riot
include diadssembly or other action atepa that are part of
the requirement.
Steps in the preliminary procedure shall be identified by
alphabetical letters in lower case and punctuated by a
period. For example, a., b., c.
Preliminary information shall be concise and presented as
dosteps. Tables, figurea, and notes may be included as
required.
The time required to accomplish these steps shall be included in
M/ffaa specified in 3.11.7.
For system-level MRCS, the preliminary stepa may also include a
matrix liatinb?eauinment
with manning
-..
-. requirements, matrix for
alternative,a,and similar information.

3.11.13.7 Maintenance requirements. Maintenance requirement deacriptiona

from the MR description block shall be repeated, word-for-word, and all words
except articles, conjunctions, and prepositions shall be initially capitalized
(see appendix A).
(a) Each MR description shall be underlined or in boldface; for
example, 1; Clean, Inspect, and Lubricate Fueling Rig Blocks
and Fittinga. Following the MS description, list the atep-byatep procedure. The format shall be as specified in 3.14.4.
(b) ~fntenance requirement carda which require ordersand
reaponaes, procedural steps may be prepared in columnar
format using the layout, headinga, and numbering method shown
on figure 29. When clarity will be improved, indicate where
the task is to be performed. For example: d. At UD 101,
position S305 to OFF.
(c) If procedure evaluation concludes that a close-out statement
dependent on the ship a operational readineas condition is
required, use the statement, Return equipment to readinesa
condition. Use of this atatemant does not release the developer
from including procedural steps which return equipment to the
condition in which it stood before commencing the KS. The
close-out phraae is not to be used as a catchall
for example,
reinstalling
tags .

covers,

removing

59

test

equipment

or

removing

safety

MiL-P-2fb534A(NAVY)

3.11 .13.8

Alternate

procedures.

Alternate

procedures

shall

be provided

only in caaes where a dnOr configtirat

ion difference or the absence of required
tools or test equipmant cauaea the preferred method to be unworkable or uiprr
ductive. Before incorporation of alternate procedures in final documentation,
approval of PHS Coordinating Activity ia required. When altemate procedures
are provided, a note to that effect shall precede the preferred procedure.
Alternate procedures require the same care in preparation as do preferred
procedures. When alternate procedures are provided, they shall be positioned
from
on the f4RCto follow the preferred procedure. They shall be, separated
only by a note which describes the condition under
the preferred
procedure
which the altarnate ie to be used.

o
L

3.11.14 Figures. Figures may be used when they present procedural data
more clearly than text., Figurea used in lieu of text shall constitute an
integral part of the procedure and shall be clearly related within the text.
Figures used to augment the text shall depict exactly the condition described
in the text. Location instructions shall be as specified in 3.14.5.1. The
PFISDAshall attach a coPy of the figure
co che t-iiC verification
draft
and
indicate
on the figure
will
be in the form of
NAVSEACEN.

the MRC and th2 step(s)

to which it applies.
original
line art unless
otherwise
authorized

Figures
by the

3.1I.14.1 Line art standards. Line drawings shall be of a quality suitable

to be scanned and digitalized for computer composition and shall conform to the
follwing:
(a)

Size. Unl&8a otherwise authorized by the NAVSEACEN artwork will

be the same size aa the area it wilI occupy on the MRC. Art
work should be positioned ao that it can be read in the same
plane aa the procedural step (see figure 30). When this cannot
be done, the illustration shall be positioned so that a 90
degree clockwise turn of the MRC page will place the illuatracion
in the proper attitude for viewing (see figure 31). A minimum
of 1/4 Inch shall be allowed between illustrations and adjacent
text and bordera. when an illustration is of such a size that
it cannot be lagibly reproduced within the maximum image area,
it shall be arranged for production on an oversized reproducible
form aa a foldout page (ace figure 17). If it cannot be legibly
reproduced in this manner, it shall be divided for production
into two or more figures.
(b) Standards. Artwork will be done in black ink or tape on a white
matte background extending the full width of the artwork. Line
widths
on the artwork shall not be less than five roils(0.005
------inch). Mjacent line separation should be 10 roils(O.010 inch)
or more. captions, callouta, legends, and footnOtes shall be
in boldface capital letters equal in size to 10 points or more.

3.11.14.2 Halftones. Halftones will only be authorized by the NAVSEACEN

when photographs are the only medium :~la:cartclazrly cc,
fiveythe required
shall
be screened (85
information to shipboard personnel. Wmn used, halftones
line, 35 percant shadow dot, 15 percent highiight dot).

60

..

MIL-P-24534A(NAVY)

r.

3.11.15 Tables. Tables will be used to present data when the data can be
presented ~r.e clearly in tabular form. References in the procedural block
shell make the purpose of the table.clear. Tables of one line shall not be
used; imtead, the information shall be presented in a procedural step. Tables
shall be located aa specifled in 3.14.6.1.
3.11.15.1 Table size. Vertical tables are limited to 64 characters
acroas and 59 lines in length. Horizontal tables are limited to 99 characters
acroas and 35 lines in length. A 1/2 inch space maximum shall be allowed
vertically between tablee and adjacent text and a 1/4 inch apace minimum ehall
be allowed horizontally. When a table is of euch a size that it cannot be
legibly reproducedWIthin the prescribed image area, it shall be arranged for
reproduction on a foldout page. If it cannot be reproduced in thie manner it
shall be divided for reproduction ae two or more tables.
3.11.16 Location block. fiis block shall ~
data is provided by the NAVSSACEN.
3.11.17 Date block.
NAVSEACSN.

left blank unless fill-in

The date will be left blank unless provided by the

3.11.18 Page numbers block. All sheets that comprise one f4SCshell be
identified by completing the block titled Page of
on tha right aide
of the page.
,--.,

3.11.19 Vartical coding block. fiia block shell be left blank unless
code la supplied by NAVSS&SN.

6
3.11.20 Maintenance requirement carda for ayetem operability
teet(soT).
Ihe intentof the~C for SOTSis to providea fullydetailedtastprocedure
to the mainteoence personnel in as understandable a format ae POSSible. To
achieve this goal it may be neceaaary to include artwork on the NRC document
showing the different complax awitch and teet equipment arrangementa for each
teat to be performed. Furthermore, it la a requirement that ~Ce fOr SoTa.
explain the exact procedu,reefor the actual system cOnfiguration on each ship
References to other docuoientsand reliance of maintenance personnels knowledge
of ayatem setup procedures are unacceptable. FiRCsfor SOTa shall comply with
the requirements as specf.f
ied in the acwiei tiOn d-%nt
(see 6.2 1).

EN

3.11.21 Preparation of MRCe for IEM. Maintenance requirement carda for

are generated only when:
(a)

(b)

1E14 analysia

identiflea requiiemente not available in existing

PMS or not projected for development after scheduled maintenance
require~nt analyaie.
A scheduling MRC ie needed ae epecified in 3.11.21.2.

3.11.21.1 Inactive equipment maintenance procedure NRCS. Maintenance

requirement carda required to provide maintenance procedures for IEM that are
not available as scheduled NNC(S) (see figure 28) shall be develOped as sPecified
in 3.11.1 through 3.11.19.
e

61

FtIL-P-24534A(tiAvY)

3.11.21.2 Inactive equipment maintenance scheduling 14RC. NCXIM1lY) Ifiormation pertaining to the scheduling of ISM will.be included on the HIP by citi~
MRCS and providing supporting information in the form of scheduling notes. fiowever, some complex equipment may require a large numberof NINEcombined with
scheduling notes to control sequencing.of scheduling. In tireaecases, an 1~
scheduling card shall he prepared (see figure 32). Thescheduling card shall
provide scheduling information only and shall not include maintenance procedures
(see 6.2.1). Block content of the scheduling card shall be in accordance with
----the f6110wing:
(a)
(b)

(c)
(d)

(e)
(f)
(g)

Ship aYstem, sYstem, aubeyatem, andequipment block.g. Entries

shall be in accordance with 3.II.4.
Maintenance requirement card code block. Tbia is a two-segment
code (see 3.11.5). The first segment la the MIP series which
wI11 be provided by the NAVSEACEN. The second aegunt will &
an IEM periodicity; for example, LU, Pf4, SII or OT. The scheduling card shall always be the firat entry on the MIP and be the
first card of the series; for example, LU-1, PM-1, SU-1, OT-1.
Ratea, M/H, and elapsed time blocks.
These blocks shall be left

,blank.
Maintenance requirement description block. This block aball
describe the type of maintenance scheduling information. For
example: 1. Lay-up Maintenance.
Safety Precautions block. The standard entry in this block shall
be as follows: 1. Observe safety precautions as specified on
scheduled MRCa.
Tools, parta, material, teat equipment block. The word none
will be entered.
Procedure block. The firat entry shall be a note; for example,
NOTE: This is a scheduling card. Schedule and perform listed
MRCS for (LU, PM, SU, or OT, aa appropriate). The entry
following the note shall be the MN description. Each step
following the MN description shall be a statement of what is to
be accomplished, followed by reference to the appropriate MRC
or document containing the procedures (see figure 32). Notee
may be used to provide such informaticn as sequencing, special
personnel, and services requirements.

3.11.22 Preparation of MRC verification draft for UMRCS. Preparation of

UMRC verification drafts shall not be undertaken until directed by the FMS
Coordinating Activity. The UMRC verification draft will be prepared in the
manner as specified in3.11.1 through 3.11.19 with the following exceptions:
I

(a) Maintenance requirement card code block. Unscheduled MRCS shall

uae the letter prefix designator U for the periodicity code
(ace 3.11.5.4).
(b) Rates block. This block shall be left blank unless otherwise
directed by the PMS Coordinating Activity or acquisition
document.
(c) Man-hour block. This block shall be left blank unless otherwise
directed by the PMS Coordinating Activity.

62

,...-

MIL-P-24534A(NAVY)

(d)

other MRCS to avoid

auDrODriate follow-on
,corrective action, or to.lead into teat~eq~iremants verifying
thecorrective action. When the reference is made to other
MSCa, the reference shall be by MSC code rather than by SYSCOM
card control number or page.

unscheduled
redundant

MRCS my make reference

to
documentation.
to lead into

3.12 Preparation of MIPS. The MIP is designed to provide a clear, concise

index and cross-reference to all MRCS within a set and shall contain only
unclaaaified information. Maintenance index pages developed for scheduled
maintenance shall list both operational artdW.K. Unscheduled mafntenance may
alao be included when approved by the FNS Coordinating Activity (see 3.9.2).
Inactive equipment maintenance shall be separately titled and listed in a
aeparate section of the MIP (eee 3.12.15 and figure33). Maintenance index
pages verification copy still be typed on maintenance index forma (see figures
13 and 14), however erasures and strikeovers are permissible. The ~
Coordinatin& Activity shall provide the developer with specific guidance concerning
the SWAS level at which NRCS will be assembled into MIPs at this point. The
following procedures shall be applicable for preparing MIPs.
3.12.1 Ship system, system, subsystem, or equipment block. Enter the
nomenclature and SWAS number (see 3.6.5) for the lowest level to which all the
listed requirements apply.
3.12.2 Reference publications block. Where directed by the PNS Coordinating Activity, enter the identifying number of the publication providing the
most comprehensive maintenance information for the systernor equipment for which
the PUS documentation ia being prepared; for example, OPS, NAVSEA instruction
booka, manufacturers pamphlets, NAVSEA technical manuals, and so forth. If
additional apace is required, enter the phrase, See Note. A note will be
entered in the ,~ deacription block to provide the additional referenced publications.
3.12.3 Date block.
NAVSEACEN.

his

date shall be left blank unless provided by the

3.12.4 Configuration block. Nsinten.enceindex pages that index NRa for

SWAS levels 1, 2, or 3, or those that combine more than one SWAS level 4 grouping, shall contain the level 4 SWAS numbers and nomenclatures. me level 5
item numbers and nomenclature shall be included. When directed by the FMS
Coordinating Activity, enter the change configuration of systernor equfpmant
for which documentation is intended. F.achFIELD CNANGE, SHIPALT, ORDALT, or
other officially authorized hardware change considered in the development will
be included. Each change ~thataffects maintenance procedures shall be preceded
by an asterisk; for example, ORDALTS: 7167, 7380, *7662. men individual
elements which make up the system or equipment being documented are not readily
identifiable as part of the system or equipment, these elements and their
individual change configu~ation shall be listed in this block. When other
information regarding the composition of the system or equipment being documented
will facilitate maintenance or management, it will be included in this block.

63

MIL-P-24534A(NAVY)

brief statements such as LORA configuration or aerial numbere 7-30 only. If

additional apace is required, the configuration data will be continued in the KS
description block by uae of a note. When the configuration data is ao voluminous
as to be impractical to include on the MIP, enter the Identlflcatton of the
publication from which configuration data can be obtained. In those casea where
configuration data ia not required, this block will not be included on the HIP.

Use

*_
*

3.12.5 Test column. Each MRC that containa a test requirement shall be
asgigned one of the following codes that will be entered in the test column on
the MIP.
B- test ia at the intermediate (I) level only.
K - teat ia performed at the organizational (0) and I levels and
re,sultsare monitored by the Submersible Ship Balliatic Nuclear
(SSBN) Submarine Nalntenance
Monitoring
Support Office
(S=).
A 1 -

teat
test

is
ia

performed
scheduled

by shore activity
only.
at the O level
only and was developed

for

SWAB

level 1 testing.
2- test is scheduled at the O level only and was developed for SWAE
level 2 testing.
3- test is scheduled at the O level only and was developed for SWAB
level 3 testing.
4- test is scheduled at che O level only and waa developed for SWAB
level 4 testing.
5- test is scheduled at the O level only and waa developed for SWAS
level 5 testing.
6- teat may be scheduled at both O and depot (D) levels and developed
for level 1 (ship system) testing;for example, OCSOT f41PCS-3/4 la
ication program.
being used under-the Combat Syat~rnTest and-Certif
7- teat may be scheduled at both O and D levels and waa developed for
level 3 testing.
8- teat may be scheduled at both O and D levels and was developed for
level 4 testing.
9- test wv be scheduled at both O and D levels and waa develoDed for
SWAB level 5 (equipment or component) teating.
3.12.6 Other column. Enter the specialized management code, aa applicable,
kisted below. If the MRC is alao classified, a two-character code will be
entered. The second character apace will identify the f4RCssecurity cl~sif ication. If there ia no applicable specialized management code but the XRC is
clasaified, the claseification code will be in this column.
R-

RC -

denotes
an MR on Deap Submergence Recovery Vehicles
(DSRV)
ayatema and equipment
that is within
the scope of certification.
denotes
an MS on DSRV systems and equipment that is within
~C.
the scope of certification and is alao a confidential
of
denotes an MR (not test) developed under the. cognizance

c
s

Smlso .
- confidential
- secret

64

---

UIL-P-24534A(NAVY)

,(-=

3.12.7

SYSC(Nf
MRC control number column. In &he SYSCOM MRC control number
the cent rol number of any ,reappliedMXCa as recorded on the MRC.
In the case of newly developed MRCS i make no entries. The centrol number will
be aDDlied by the NAVSECEN. In the ISM section of the MIP (see 3.12.15); enter
SYSCOM contr~l numbers for only those MRCa which are asaigned an IBM periodicity
code.
column,

enter

3.12.8 Maintenance requirement column. nen the MRCS aggregated on 8 MIp

are applicable to a number of systems or equipment or ,units lower than the one
shown in the MIP heading,the specificsystemor equipment
unitshallbe entered

in,boldtype(orunderlined)
on the linepreceding
the actualMS (seeEigure34).
Bothitemnameand nomenclature
designation
shallbe provided.The~ descriptionshallbe writtenexactlyas it appearaon the applicable
MRC. The first
line of the first maintenance description shall be two spaces balow the scheduling aid or column border if no scheduling aids apply.
,

3.12.8.1 Notea. Notes shall be used to define R requirements in the

operational maintenance section of the MIP and to continue entries too numerous
for the space provided in the Reference publication and configuration blocks.
In addition, notes shall bs used to provide management information applicable
to a specific MRC; for example, NOTE: lhiaMRC applicable
to Mod 1 only. The

note(s)shallbs placedimmediately
afterthe laatMS description
for thatMRC
and shallbe unnumbered.If more thanone noteis requiredfor the sameNRC,
thenotedefiningthe R requirement
shallbe listedfirat.

.*

3.12.8.2 Scheduling aids. A21 notationa affecting the scheduling of MRs

shall ba located in the MN colwmn preceding the first MN description. When
scheduling aide include more than one topic, they shall be numbered under a
Scheduling aid heading; for example:
(a)

Scheduling aida:
(1)
(2)

(b)

Schedule MRC Q-3 for accomplishment only when dockside.

Revie,wNsintenance Requirements A-9 and A-11. Omit HRC(S)
which do not apply; no feedback report required.

Aateriaks and the symbol # will be used to call attention to

speclfic scheduling information as follmwa:
* This La a Safety of Ship item.
** por ~qhedli~ purposes only; no NRC is provided.
# Mandatory scheduling required.

3.12.8.2.1 Scheduling notations. The first scheduling notation shall be

located at leaat two spaces below the top line which bordera the MS column.
3.12.9 Periodicity column. Enter the periodicity code as shown on the
MRcs. Tha MRCS shall be listed in the following sequence of decreasing frequency: D, 2D, 3D, U, 2W, M,,2H, Q, S, A, 18M, 241i,30M, 36M, 48M, 56f4,60M,
R, and U. Within each periodicity group, list the MRCS in numerical sequence:
0-1, D-2, D-3, W-1, W-2, M-1, M-2, Q-lR, Q-2, A-1, 18M-1, R-1, R-2, U-1, U-2.

65

MIL-P-24534A(NAVY)

When reapplying previous1y developed MJtCs,the condition may occur where the
existing XRC is applicable but the number associated with the periodicity falla
out of consecutive order. Skipping of sequential code numbers is acceptable;
for example: Q-1, Q-3, &4, Q-7. Aeterieka are used in the periodicity columm
to call attention to scheduling aids applicable to specific MR. The standard
use of the asteriak is:
(a)

A single asterisk (*) ia weed to indicate safety of ship items

(see 6.3.37). The use of the term safetyof shipLa restricted
to submarine. The designation of safety of ship items will be
recommended by Maintenance RequirementDevelopment Activity
(MRJ3A)by annotation on the verification
COPYof XIP,for

L
L

example,Q-1*. The safetyof shipnotationshallbe entered

on the verification
copy.
(b)

3.12.10

The double asteriak (**) is used to indicate that the requirement

is listed for scheduling purposes only and there is no MRC.
The double asteriak shall be placed beneath the applicable
periodicity code in this column, and the notation entered in
the MR column.
htes

column. Enter the rates required as shown on the NRCS.

3.12.11 Man-hour column. Enter the M/H for each rate as shmvn on the MRCS.
3.12.12 Related maintenance column. Enter the periodicity codes for XRCa
which are identified as related during the procedure evaluation process. Entries
in the related maintenance column shall be listed only with the NRC of the
longest periodicity; for example, if a weekly and a monthly MRC are related, only
the monthly MRC would indicate the related maintenance. If two MRCa of the sams
frequency are related, the related MRC shall be entered with both MRCS. When the
related.MRC is from the same HIP, list only the periodicity code; for example,
u-3. When it is of another MIP, list the MIP series of the code also; for
example, EL-10:M-3. When the accomplishment of the related MRC is mandatory, a #
shall be placed after the periodicity code; for example, M-3{1. When the related
NRC is merely a convenience, the # shall be omitted. When there is no related
oshall be entered.
maintenance, the word None

e
.
\

3.12.13 Page number. All sheets that comprise one MIP shall be identified
of _
on the bottom of the sheet.
by completing the entry Page
3.12.14 SYSCOM MI? control number. This block shall be ieft blank unless
the numberis provided by the appropriate NAVSEACEN.
3.12.15 Inactive equipment maintenance requirements. The XEM reqn%ramenta
shall be listed on the MIP following the operational maintenance requirements
(see figure 33). The requirements will be separated from the operational
requirements by double horizontal lines and use of boldface print. The 1PM
section shall be titled Inactive EauiPment Maintenance. The first entry fOllOving the title
shall
be:
The following requirements will be scheduled when
.
equipment is inactivated for periods of prolonged idleness. When no IEM
requirements are justified during IEM analysis, enter the words, Nonerequired-.
The lEN requirements shall be entered as follows:

66

MIL-P-24534A(NAVY)

(a)

shall
be grouped under the following
sub
heads: Lay-Up Naimtenance, Periodic Neintenance, Start-Up
Maintenance, Operational Test. The subheads shall be initial
caps underlined.or boldface print.

The. IEM requirements

NOTS; When LU MRCS are prepared to support

system
or equipment
periods ofprolonged idleness, SU NRCS shall be required suitable
for system or equipment operation or activation.
(b) Within each subheading, the first card entered will be the
scheduling,
card, if applicable (see 3.11.21.2). Each MS
description shall be numbered. Applicable NRCS listed in the
operational maintenancesection of the MIP shall be reapplied
by relisting the FfRfollowed by a note; for example, NOTE:
Uae NRC M-5. If the periodicity of accomplishment for IEM
periodic maintenance differa from the operational requirement,
the note shall specify tbe frequency; for example, NOTS:
Accomplish MRC W-1 monthly. When IEN analysia requires use Of
only a specific section of the operational NRC, that section
will be identified by use of parentheses following the MRC; for
example, NOTS: Accomplish MRC Q-3 (NR-1).
(c) The word None- shall be entered for any eubhead where IEM doea
not apply.

(~

3.12.15.1 Inactive equipment &intenance-periodicity column. FOr new ~ce

developed exclusively to setiafy ISN requirements, enter the periodicity code
aa ahovn on the IEM MRC. Naintena,ncerequirements referring to an operational
equipment NRC or IEM scheduling NRC will not have an entry in the perludicity
column. llte
MRCa shall bslisted in the following sequence: LU, PM, SU, and m.
3.12.15.2 Inactive equipment maintenance-ratea and H)H coluema. Inactive
equipment NW making reference to equipment operational MRCS and IEM scheduling
carda do not require an entry in the Ratea and M/H column.
3.12.16 Unscheduled maintenance requirement MIP entries. When authorized
by the NAVSEACEN, UM requirements may be included on the operational maintenance
MIP folloving the scheduled requirements. Nhen indicated by the acquisition
document, UX requirements may alao be prepared on separate MIPa. The UM require
ments on scheduled MIPs or separate UM MIPa shall be prepared in the aama
Mnner aa apecified in 3.12, with the following exceptions:
3.12.16.1 Unscheduled maintenance-rates and M/H column. ihia
column shall
be left blank unless directed by the PMS Coordinating Activity.
3.12.16.2 Unscheduled maintenance-related maintenance coltwm. This coltmm
shall be used to identify series MRa and to identify mandatory related UMRCa;
for example, an alignment on one UMRC may necissitate an adjustment for a
When the related NRC is from the earns
different unit detailed on another WC.
F41P,list only the periodicity code; for example, U-3. When it is of another
MIP, list the MIP serieo segmsnt of the code also; for example, 5BBCOOO:M-1.

P.
w

3.12.16.3 Unscheduled maintenance-notes. Notea may be used to provide

management information applicable to the UMRC.

67

HIL-P-24534A(NAvY)

3.13 Documentation validation. The contractor La rasponalble for

accomplishing on site validation procedures as Specified in the acquisition
document (see 6.2.1).
3.14

Compoeition and layout reqtiikem&te.

3.14.1 General. The following are the requirements for composition and
layout of MIP and MRC verification drafts and camera ready copy for new
developments. Camera ready copY format shall be identical to the verification
draft.requirements specified in 3.11 and 3.12 and the layout requirements
apeciftad herein. Forma to ba used for the verification draft are available
from the NAVSBACEN. The verification draft will be used aa input to composition;
therefore, while the draft muat be readily legible, strikeovera and pen and ink
corrections will .be accepted. Camera ready copy will tw 20 percent larger than
the final printed size of 5 inches by 8 inches for MRCa and 8 inches by 10-1/2
inches for MIPs.
3.14.2 VPe aizaand face. Unlessotherwise
specifiedby the acquisition
document(sac6.2.1)
, a typewriter
with i2-pitch
spacing,approximately
10-point
typeface (IBM Selectric, Prestige Elite 72 type, or equivalent face and size)
shall be used to type information on the MSC and MIP forms.
Securitv ,----classification, when required, shall be placed on both verification (review) andcamera
ready copy in boldface capital lettere equal in size to 14 point.
3.14.3 Suacin&. Maintenance procadure text copy on KRC forme shall be
prepared in single column or multicoltmm format. For single COlumn fomt,
spacing requiremanta shall be in accordance with figure 35. Single spacing
shall ba used between atepa except where the acquisition documant (ace 6.2.1)
or PMS Coordinating Activity apeciflea double spacing to enhance readability.
Spacing requirement for multicolumn format shall be ae epecified in 3.11.13.7
and figure 29. A double apace shall pr6cede and follow notes, cautiona,
warninga, and columns with heading titles. The left margin on MRCS shall alwaya
ba one space in from the left borderline. There shall be an axception when it
isnzceeaary to liac 10 or more items in the firat column of the Tools, parta,
msceriala and teat equipment block; in thla caae the left margin spacing for
that particular page of the ?lSCshp11 ba two apacea in from the borderline, no
that there is always a full space be~ween the left borderline and any typed
material. All typed material on an MRC shall be arranged to align with tMa
msrgin. Maintenance index pagea shall be prepared with,single spacing between
lines of a given MS entry and batween Ml&.of the name M5C. A double space
shall separate KRC entries (ace figure 36).
3.14.4 Indentation and numbering of text. Following the KS description,
the step-by-step procedure shall be entered in continuous numerical and
alphabeticel sequence, using t~a following letcera and numbers to identify
steps and eubstepa as necessary:

68

MIL-P-2453bA(NAVY)

Set
Set
Set
Set
Set
Set

..

margin stop.2 spaces in

1st tab 5 spaces in
2nd tab 8 spaces in
3rd tab 12 spaces in
4th tab 16 spaces in
5th teb 20 spaces in

Procedure
1. The Maintenance Requirement Description.
a. Proceduralstep

When the alphabet ia uaed~through z and stepa still remain to be identified,

con.t
inue: aa., ab., and at. When az is reached, continue ba., bb., and bc.
lhe aacond and succeeding lines of any step shall be flush lefi-aligned with
the first line of that step. Fnr f4RCeprepared in multicolumn fnrmat, see
3.11.13.7 and figure 29.
3.14.5 Figures. Figures shall be used only when .eaeentialto a clear
presentation of the maintenance prncedure (ace 3.11.14). Figures shall be in
accordance with HIL-H-38784 and MIL-P-38790. Figures shall be numbered; for
example, figure 1. When a flgure is not adjacent to related text, or when
ntherwise required for clarity, a title shall be added.
3.14.5.1 Fi@re location. Figures shall be pnaitioned sn thatthey lie
in the same reading plane as the procedural atepa. When thla cannot be done,
figures shall be positioned so that a 90 degree clockwiserotation of the MSC
will poeition it for no~l
viewing. Artwork should be placed following the
procedural step to which it refers; however.it is unacceptable to allow large
blank spacea or to.otherwfse waste space because of artwork placement throughout
the MSC solely to cause the illustration to fnllow a specific procedural step.
If illustrations are large and their location would interfere with correct
sequencing of procedural,eteps and cause difficulty in understanding or interpretations, they may be ,,placedin numeric eequence on pages at the end of the
procedure.
3.14.6 Tables. Tables shall be used to.present data when the data can be
presented mere.clearly In tabular form. Elaborate or complicated tables shall
be avoided. Lines shall be usadbetween columns only. Tables shall be
numbered; for example, table 1. A descriptive titLe shall be added when requirad
for clarity in the procedure. The table number and title shell be placed below
the table. Positioning,instructions are the same as for figures (see 3.14.5.1).
3.14.6.1 Table location. A table should be placed followlng the procedural
step containing the first reference to it. When this in not possible because
of space limitations, it may beplaced at the beginning of a succeeding page,
on a separate page, or at the end of the procedural steps. ~en tables and
figure(s) are sequential, the table(s) shall precede the figura(s).

>

3.14.6.1.1 Troubleshooting tablee. When teet MSCS contain tables designed

to aaaiat in locating troubleshooting fault isolation procedures applicable to
malfunctions discovered during the test accomplishment, the,table shall be
located at the end of the procedure block. As a minimum, the table shall
identify the procedural steps applicable, publication number containing the

69

MIL-P-24534A(NAvY)

troubleshooting or ?auIt iaolation,,

procedures, and identifying informetion for
the applicable procedure~ within the technfcel publication. Spscific page or
paragraph numbers of the referen&id publicationwill not be provided.
3.15 Changes to PMS dorxnentetion. When changes to existing PMS documentation are required, the method of preparing the changes shall bs as follows:
3.15.1 Revised MRCS. Revised HRCS may be prepared in several formats.
The original MRC may be reproduced with the NRC page on one-half of the page.
This will allow ample room for making appropriate and legible changes (ace
figure 37). Revised MRCa msy also be prepared aa msrked up original MRCS or
retyped pages. The following requirements apply:
(a) Do not write over the original text when revising. A single
line should be drawn through the original text in such a
manner that the original text is still readable.
(b) When revfaions are written in the margin or to the side of
the MRC, draw a small arrow to show where the new information
ie to be inserted.
(c) Do not erase. Erasures leave a mark and it la unclear as to
whether it should bs included or not. Simply croes out worda
to be deleted.
Uhen
deleting a paragraph, or anything larger than three lines,
(d)
croaa out the deleted eection with an X. When deleting a line,
cross out with a single line.
3.15.2 Revised MIPs. A revieed MIP verification sheet shall be prepared
to provide a total listing of all MRCe (both existing and revised). The revised
MIP mey be a msrked-up copy of the eiietingMIP, or a new MIP verification
sheet (ace figure 38). The vertical coding column for the SYSCOM NRC control
number of the revised or changed cards shall be lined out or left blenk. NRcs
that have not been revised are identified on the K2P verification sheet by the
SYSCOM MRC control number.
4.

QUALITY ASSURANCE PROVISIONS

4.1 Responsibility for inspection. Unleaa otherwise specified in the

contract or purchaae order, the contractor is responsible for the performence
of all inspection requirements aa specified herein. Except as otherwise
specified in the contract nr purcbaae order, the contractor mey uae hia nwn or
any other facilities suitable for the performance of the Inspecting requirements
specified herein, unleae disapproved by the Government. The Government reeervea
the right to perform any of the inspections set forth in the,apecificetion
wheresuch inapectiona are deemed necessary to aeaure supplies and services
conform to prescribed requirements.
4.1.1
In-process
review.
The PMS Coordinating
Activity
may perform inThe P14SDAshall
provide
support
and materials
process
reviewa,
where necessary.
as required
to facilitate
in-process
reviews
specified
in the acqulaition
docu-

menta (see 6.2.1).

70

MIL-P-24534A(NAvY)

,r

4.2 Planned maintenance system development activity quality program

requirements. The PMSDA shall establish and maintain a quality aasurance
program to ensure that the editorial quality, technical accuracy, correctness
of composition, and graphic quality are consistent with the :requireuents of this
apecffication. Thequality asaurance check aheeta (ace figurea 18, 18a and 18b)
exhibit minimum recordkeeping requirements for NRCS and UMRCa needed to add nister this portion of quality.aaaurance.

Qwality program organization.

Effective
management
for quality
shallbs clearlydefinedby the PNSDA. Personnel performing quality functions
4.2.1

shell have the reaponsibility, authority, and organizationel freedom to identify

problems end to initiate, recommend, and provide eolutiona. Management shall
review the atatua and adequacy of the program throughout each development phaae.

4.2.1.1 Initial quality planning. The PMSDA, during the earlieat practical phase of contract performance, shall conduct.a complete reviev of the development requiremanta. This review shall identify and make timely proviaiona for
any special akilla, processes, methods, and procedures toaaaure the quality of
the development; and the preparation, inspection, veriffcatfon, and validation
of the documentation.
4.2.2 Government-furniahed material and data. Ihe PMSDA shall conduct a
review of Government-furnished material and data to determine compliance with
the terms of the contract and the adequacy of the source material. The PMSDA
shall report deficiencieewhich will impair the quality of the planned maintenance procedures to the PMS Coordinating Activity.
4.2.3 Inspection of documentation. Documentation that ia eubmitted by
term of the acquisition docwment aa deliverable items, shall be inspected by
the Pt4SDAfor compliance with Section 3.
4.2.4 Inspection for preparatfon for delivery. The packaging, packing,
end marking ehall bs inapettedby the PNSDA for compliance with Section 5.
5.

PACKAGING

(The preparation for delivery require=nts

epecified herein apply only for
direct Gove-nt
acquiaitfon. For tha axtent of applicability of the preparation for delivery requirementa of referenced documsnta liatad in section2.
see 6.2.1.)
5.1 Packegi~.
Unleaa otherwise apecified in the acquiaftion document
(see 6.2.1), packaging, packing, and marking for shipment shall be in accordance
with uI~-U-38784.
6.

N02SS

6.1 Intended uae. The MRCa and NIPs produced in accordance with this
specification
are intendedfor use in thePMS of the Navy3-f4program. They
aPPIY tO inspecting, cleaning. lubricating, replacing, adjueting, aligning,
calibrating, functional testing, and system testing.

71

MIL-P-24534A(NAVY)

6.2

Ordering data.

6.2.1 ~uisition
following:

requirements. Acquisition documentsshould epecffy the

(a) Title, number, md date of this specification.

(b) Identification of system, subsystem or equipment for which
the t@Cs end f41Peare to be prepared (see 3.6).
(c) Security,claesification of materialto be used in MRC development (eee 3.4).
(d) Schedules and identification of applicable tacks described in
this specifIcntion; theeeinclude applicable development
phaaes, preparation of the verification draft, documentation
validation, and shipment of deliverable Items (see 3.7, 3.11,
,3.13 and 6.2.2.2).
(e) IdentifIcation end address of PKS Coordinating Activity
(see 3.2).
(f)
Designation of validation site and procedure (ace 3.13).
F@quirement for in-proceea review support (ace 4.1.1).
(g)
Raquirementa for SOTa, MRCa (see 3.11.20).
(h)
Requirements for UM analyaia end requirement taska (ace 3.9).
(i)
Approval for uee of double spacing between MRC text procedural
(j)
,etepa (eee 3.14.3).
(k)
Exceptions to methods for preparation for delivery (eee 5.).
Exceptions to type size end type face (ace 3.14.2).
(1)

e
e

6.2..2 Data requiremenca. When this apecification iaused in an acquieition which incorporate a DD Form 1423, Contract Data S.equirementaList (CDSL),
the data requirements identified below ahe21 be developed as specified by an
approved Data Item Description (.DDForm 1664) end delivered in accordance with
the approved CDSL incorporated into the contract. When the proviaione of FAR
52.227-7031 are invoked and the DD Form 1423 la not used, the data specified
below shall be delivered by the contractor in accordance with the contract or
purchaae order requiramente. Deliverable data required by this specification
is cited in tha following paragrapha.

~---

72

MIL-P-24534A(NLVY)

/2

Paragraph no.

a
3.7.2
3.1.2

3.7.3
3.7.4
3.7.4

3.7.5
3.7.6
3.7.7
3.7.9

3.10

3.7.11
3.7.12

3.7.14
3.7.14
3.8
4.2

Data

requirement

title

Planned Maintenance System (PMS)

Functional Block Diagram Form
Planned Maintenance System
Master System and Subsystem.
Index Form
Planned Maintenance System (PMS )
Functional Failure Analysis Form
Additional FSI Selection Form
Functionally Significant Item
Index Form
Plannef3Maintenance System (PMS)
Failure Modea and Effects
Analysia Form
Lmgic Tree Analyais Form and
Rationale Back-p Sheets
Servicing and Lubrication
Analysis Form
Maintenance Requirement Index
Form
Planned Maintenance System (PMS)
Procedure Evaluation Sheet Form
Planned Maintenance System (PMS)
Taak Definition Form

InactiveEquipmentUsintenance
(IEM)AnalyslaForm
PlannedMaintenance
System(HS)
Maintenance
Requirement
Cards
Maintenance
Index Pagea
RCM Documentation Control Sheet
Form
Quality Assurance Check Sheet

Applicable

DID
no.
_!!@ST.!

DI-L-2202

DI-L-2203

DI-L-2205

DI-L-2207
DI-L-2206

DI-L-2204

DI-L-2208
DI-L-2209
DI-L-221(3

DI-L-2211

DI-L-2212

DI-L-2213
DI-L-2215
.DI-L-2216
DI-L-2214
DI-L-2217

(Dataitemdescriptions
relatedto thisspecification,
and identified
in
section6 will be approvedand listedas such in DoD 5000.19L.,.Vol. 11, AMSDL.
Copies of data item descriptions required by the contractors in connection
with specific acquisitionfumctiona should be obtained from the Naval Publication and Forms Center or ad directed by the contracting officer.)
6.2.2.1 The data requirements of 6.2.2 and any taak in aectiona 3, 4, of
5 of this specification required to be performed to meet a data requirement may
ba waived by the contracting/acquisition activity upon certification by the
offeror that identical data were submitted by the offeror and accepted by the
Gnvarnment under a previous contract for identical item acquired to this
specification. 2%1s does not apply to specific data which may be required for
each cofitractregardless of whether an identical item has been supplied previously (for example, test reports).

73

MIL-P-24534A(NAVY)

6.2.2.2 Delivery stagee for developments using the requirements investigation procees
for RCM maintenance methodology.aa epecified in table I.
=TABLE 1.

Ma,aterSystems and Subsystem Index

fonus, related Functional Block
Diagranm.

Functional Failure Analysis form.

Mditional FSI Selection and FSI Index

forme.

WEA

Logic Tree Analysfe Fome

rationale sheets.

Servicing and lubrication Analysis forme.

Maintenance Requirement Index forme.

Procedure Evaluation sheet form.

Taak Definition forms.

L!

Documents

~i~

~rouping

varied

by the

RCM deliverable documentation.

Phaee

Deliverable ~f

*..

forms.
and back up

a.

10

Inactive Equipment Meintenance (IEM) Analyeia

forme and Procedure Evaluation form.

11

Unscheduled Maintenance documentation

(eee 3.9).

12

MIP and KRC documentation and the

Documentation Package.

of documentation into
PllS Coordinating

deliverable

Act ivlt y.

74

packages

~Y

be

MIL-P-24534A(NAVY)

,P
.

6.Z.2.4 Assembly of the documentation package. Each set of MIPs and ~Cs
covering an approved system shall be accompanied by 2 sets of approved
documentationof the analysis assembled into an integrated, cohesive package
for that system:
(a) Covering title sheet identifying the system analyzed, PMSDA,
and the centractnumber under which the development was
accomplished.
Documentation
Control Sheet (see figure 10).
(b)
(c)
Master Systems and Subsystems Index form (ace figure 1) for
the system(a) analyzed.
Functional block diagrams.
(d)
Functional Failure Analyais form (see figure 2).
(e)
(f) Mditional Functionally Significant Item Selection form
(ace figure 3).
FunctionallySignificant Item Index form (see figure 4).
(s)
(h) Failure Modes and Effecta Analyais form (ace figure 5).
(i) Logic Tree Analysis form (ace figure 6) with rationale and
justification backup sheets.
Servicing and Lubrication Analyais form (see figure 7).
(j)
(k) Maintenance Requirement Index form (see figure 8).
(1) Procedure Evaluation Sheets form (ace figure 12).
(m) Task Definition form (see figure 9).
(n) Csmera-ready copy MIPs and MRCS (see fIgures 13 through 17).

P.

6.2.2.5 Completed documentation package. The completed package for each

system will bs retained by the cognizant Naval Sea Support Center and the cognizant technical activity
as a corporate
history
of the PMS development,
rationale,
justification,

and analyaia

procedure

and shall

be referred

to during

subsequent

feedback and revision proceaaes.

6.3 Terminology. The following definitions supplement those covered in
aPplfQble docments and apply to terms used in this specification.
6.3.1 Acquisition document. Documentation used to task a Planned Maintenance System Develop~nt Activity to develop PMS documentation. This includes,
but is not limited to, contracta, purchase ordera, task assignments, SEATASKS,
and technics2 manual contract requirements. ThIa documsnt la prepared by the
contracting activity.
6.3.2

Active function. A function which requires activity of an item.

6.3.3 Applicable task.

rence of a failure mode.

A task which reduces the probability of che occur-

6.3.4 Characteristic: Any ,specificquality, property, capacity or trait

of a systemrequipment.

6.3.5 Condition-directed task. Preventive maintenance tasks performed

to compare conditions with an appropriate standard to indicate the need for
corrective maintenance tasks to ensure continued operation. A CD task is an
inspection or teat to discover a potential
failure condition which can be
corrected before failure occurs.

75

MIL-P-24534A(NAvY)

6.3.6

Depend&it failure. A failure of an item which ia cauaed by failure

of an asenciateditem.

5-/

6.3.7 Development. The act of researching, examining, and niting

documentation.

PHS

6.3.8 Distribution. All the procedures involved with forwarding PMS

documentation to user activities and maintaining rekorda.
6.3.9 Dominant failure mode. A failure that ia important because of its
frequent occurrence or the serious consequences of the failure.
6.3.10 Ecorromica. The consideration of all forms of resource expenditure
versus the value to the user achieved through this resource expenditure.

6.3.11 Effective tasks. An applicable task which reduces the probability

of the occurrence of a failure mode to an acceptable level for safety-related
failurea; for other than safety-related failures, an applicable task that is
cost-effective.
6.3.12 Failure. The presence of an unsatisfactory condition. What
constitutes an unsatisfactory condition must be specifically identified for
each function.
6.3.13 Failure effects. The consequences of a fallure mode. Failure
effects begin at the indenture level where the independent,failure occurs and
may progress to higher indenture levels.

.-

.
6.3.14 Failure-finding task. A maintenance task which is a periodic
inspection or test to discover the functional failure of off-line and hidden
functions prior to these functions actually being needed.
6.3.15 Failure mode. me specific condition causing a functional fallure
(often best described by the condition after failure).
6.3.16 Finalization. All the procedures involved with standardizing,
coding, and printing PMS documentation.
6.3.17
perform.

Function. Any action or operation which an item ia intended to

6.3.18 Functionally significant item. An item whose failure would have

a significant impact on the availability of a required function or life-cycle
costs.
Preventive
maintenance tasks which
6.3.19 Hard-time task or TD task.
are r.erf
ormed at some interval without consideration of other variables. This
interval mav be based on calendar time. ouerational time. or the number of
reoccrrrinzevents (rounds fired.
etc.
. cvcles.
.
. starts.
. stODs).
.

6.3.20 Hidden function. A function provided by an item for which there

is no immediate indication of malfunction or failure. The demand for such
functions usually follows another failure or unexpected event.

76

MIL-P-24534A(NAVY)

/-

6.3.21
Indenture level. A level of relative importance in a hierarchical
set. The levels progress from the general to the specific.

6.3.22 Independent failure. A failure of an item which occurs without

bsing cauaed by the fallure of any other iteim.
component, asaembly,
6.3.23 Item. A ayatem, subaya.tem, equipment,
aubaasembly, or part, depending on the indenture level under discussion.
6.3.24 Life-1imit task. A TD preventive maintenance task which operates
by periodically replacing an old item with a new item before failure occurs
and discarding the old.item.
.-

6.3.25 Lubrication task. A preventive maintenance task which conaista of

periodic application of or determinationof need for a lubricant (grease, oil,
graphite, etc.).
6.3.26 Planned Maintenance System Development Activity. .Activity(commercial contractors, ISEAa, NAVSSACENa, etc.) which developa PMS documentation.
6.3.27 Minimum maintenance. The least amount of care and the longest
time between accomplishmsritwhich will ensure an acceptable degreeof reliability and availability
y.

6.3.28 Niaaion-critical item. An item whose failure degrades the capability of the chip to aatiafactorily perform ita mission.
6.3.29

Paaaive function.

A function which requires an item to be inactive.

q..

6.3.30 Planned Maintemence System Coordinatlug Activity. Activity which

funds, authorizes, managei, mnnitors, or coordinate PMS documentalion developed
by commercial contractor, ISP.AS,NAVSSACSNa, etc.
6.3.31 Preventive maintenance task. A maintenance taak which by ita
performance reduces the probability of occurrence of a particular fallure mude.
6.3.32 Redundancy. The design practice of duplicating the sources of a
function so that the function remains available after the fallure of one or
mnre iteme.
6.3.33 Reliability
y centered maintenance. A method for determining preventive maintenance requirements based on the analyala of the likely functional
failurea of hardware havi~ a significant impact on aafety, operations, and
euDport
functions. A decision logic tree ia used to identify the need for
..
apecific taaka.
6.3.34 Requiremente inveatIgatinn proceeo. Technique used to determine
scheduled maintenance requirements.

/--

6.3.35 Revnrk taak. A TD preventive

maintenance
task which operates by
periodically overhauling nr refurbishing an item to reatnre the item tn design
apecificationa.

8
77

f41L-P-24534A(NAvY)

6.3.36
Safety critical item. An item whose failure directly threatena
the life, llc+b,and/or health of the crew or others.

0. -+
L

6.3.37 Safety of ship item. A maintenance action vital to the maintenance

of a submarines watertight integrity or to its ability to return safely to the
surface.
6.3.38
Scheduled maintenance requirements. Those maintenance actione
essential to maintaining the system/equipment in a state of operational readiness
commensurate with its design characteristics.
6.3.39

6.4
SPMIG and
Naval Sea
Naval Sea
23702.

Time-directed task. A hard-time task (see 6.3.19).

Application for copies of OPNAV forme and other documanta (CDC, SPIN,
PMS Cross Reference Guide specified within should be addressed to
Support Center, Pacific, P.O. Box 85548, San Diego, CA 92138; or
Support Center, Atlantic, St. Juliena Creek Annex, Portsmouth, VA

6.5 The analysis process of the R(2I4methodology encompaasea all clasnification typea, classes and levels of maintenance development. Therefore specifying the claasification types, claaaea and levels of maintenance development,
as required in the baaic issue of this specification, are no looger required
and have been deleted in this revision.
6.6 Changes from previous issue. Aateriaka are not used in this revision to e
identify changea with respect to the previous issue, due to the extensiveness of
the Change8.

Preparing activity:.
Navy - SH
(Project MNTY-NO02)

Review activities:
Navy - EC, OS

L.....
78

MIL-P-2L53LA(NAVY)

FIGURE 1.

~ster

systems

and subaysterns

79

index

(Fo~

OPNAV ~7~~f114).

MIL-F-245.34A(
NAVY)

.,
..*

FIGIJRX2.

-k

Functional failure analyaia (Form OPNAV 4790/116).

._

80

MIL-P-24534A(NAVi)

/-.

1.ausmn6m

,-IC4A-SUCAQIM.

8
r.
I

&&r---l
i

d
lam

mgm

vm
-m.,.a

FIGURE 3.

Mditione.1 functionally significant items selection

(Form
OPNAV 4790/117).

81

MIL-P-24534A(NAvY)

,0.
m
al.

FIGURE .4. Functionally significant items index (Form OPNAV 4?90/118).

82

MIL-P-24534A(NAvY)

I
I

I
I
!

FIGURE 5.

Failure modes and effects analyaia (FormOPNAV4790/1

19).

83

M2L-P-24534A(NAVY)

I
FIGmt2 6.

Logic tree analysis (Form OPNAV 4790/120).

84

MIL-F24534A(NAW

FIGURS 7.

Servicin13and lubrication analysis (Form OPNAV 4790/121).

85

NIL-P-24534A(NAVY)

u-a

-w,

w..

mliuA-

,.

, *I,

M-,,.

, m

C4m

LCc#.ca

,?

0.
,-s.,
W*-

Ilm,nc.-

W.-

.a4n

m.

,. -w
mm

.PLc,t.

,,

?sS

!.

MP

.-..,

.-

FIGUNE 8.

Maintenance requirementindex (Form OPNAV 4790/123).

.-

86

MIL-P-24534A(NAVY)

-Mml

,%

ImmO

Mm

,m

I
m-.
nm

Kmxumm.mu=

i.
a
c

1 --

..-*

V.,

FIGUNE 9.

Task definition (Form OPNAV 4790/124).

87

HIL-P-2&534A(NAVY)

FIGURE 10.

RCM documentation control sheet (Form OPNAV 4790/125).

./

88

NIL-P-24534A(NAm)

,.

FIGUF.E11.

Inactive equip ent maintenance requirement analysis

(Form oPNAV 47901129).
89

UIL-P-24534A(NAVY)

FIGURE 12. Procedure evaluation aheat (Form OPNAV 4790/130).

.
90

.J

HIL-P-24534A(NAVY)

/--

mm

sONmxw, ,.3?
R4 >*

FIGURE

,Aa

,.-.,

C4

13. ~~ntenance index page, firatpage(ForMOPNAV479018~).

91

%&-~24534A(NAvY)

.-J

.m

. ,

.HeJ=

FIGUlt13
14. MIP continuation page (Form OPNAV 4790/85).

92

FfIL-P-24534A(NAVY)

UPaa?m

WMV8TCM

WEM

c0wutN7

MR2c0M

Mm

TOTAL
w
uNmnAMcc nmulMMRN7 -PnON

-w

..

i
[g

. .

FIGuRE 15.

Irum

Neinten.sncerequirement card firet pege (Form OPNAV 4790/82).

93

MIL-P-24534A(NAVY)

FIGURE 16. MRC continuation page (Form OPNAV 4790/83).

a
J

MIL-P-24534A(NAVY)

PAGE

AND

OF

,,

FIGURE 17. MRC continuation page foldout (Form OPNAV 4790/131).

95

MIL-P-24534A(NAvY)

J
PAGE.3

FIGUW

17.

MRC foldout

page

AND 4 OF

(Form OPNAV 4790/131) . -

ICSQL IN

COntinued

.-/

56

mIL-P-24534A(

NAVY)

FIGURE 18. @aIICY

assurance check sheet (Form OPN~V 4790/132).

97

MIL-P-24534A(NAvY)

mELIMINAIW

Chukod
BY

---

FINAL

m;.

C+19chti
0

oat,

No,

DESIRED STANOA!iD CONOITON

.
__
THE !OLLOWING cwcus

19

Ma,., ml,, ,.0 l.b,ic. n,, ,,, ,ti,n,,l,ea L, ~.un,n.n,

n.ma.r. IIem MOW .nd nonw.wa, .,8 d DMSI*I.,

20

paw number L.lc.ckis c.mperty f,u~

21

Repair wts

22

Ewicqc

23

Cln?iticwion

.,.

SIr.cwe.

d MRC

%WD1C.I*P8 *.

2s

Solw,nc*,

3,>1.18

,.

c.ropuly loswa.

3.11.72,
3,11,12.11
3.21.12.lg

ate MODWIYti,lgd in.

steps, ,L+ #e,m;.OIv,

,,,

m=,

3.1%.13

more than one

cont.,,

Orectie ,pp,,cab,,

.Ullm

32

,0

rMrhings, d appk.bh..

n,ntaed

W.m;os,0

3,11.!2b
3.11.12.lb

3,11.13C
3.11.12.Ic
3.11.12,3d

nd smcul malenals

Languaw. 1.. I..c.

.I.rma,a .,,,,,!4

Not.,

,pe,.

DIOP.rIy Ilwd

,,.
~==kl
24

..

.
CONcERN PROCEOURE BLOCK

Relwwc.
Parag,.f)h
, Sp+c.

,,,0,.

w,,,!,

____

sea mme,,.

_
,0 ethu put,l,c.,rnn,

3.11,13.4,
,,.

,e,,,K,~

3.11.2.7

a,, IX@C,ly made

___

SCFm.$uledMRC relw.nce,

31

UnSCImUu184MSC r.1.,mnces ,,,

as

F,II.in bhnks W, u,ca PIOw,,y.

33

Au mow .wah. r..ey - SI*OS, such S ene,n,zong ewmment,

warmup. VJlilionq
SW!l. k,. ,.m.q
ecar,. nd Watd!sh!.g
commummtcans, .. mcwvj
m Prehm)nav

34

MR C4scrwmon is ,Iaclly , ,. MB De.c,,c.:,on WC+ W,,II ,..

mm, Cwil.ls .ed ndor,mod. 01,. M,cux,

35

All ,IV9
SOQ-e,

3s

Altef,ulw P,Ou.jw.s

te

37

lanle,

am r.?l.r,ceo 8 ,,.,.

32

CI*O,,<I.I*,W
aoot,c.bl.

3.1!.! 3,,

D,OLWIY mad+

3.!1,134.
3.11.13.5

.2

3.11.11.6

wi,t,t. et! MR ,,.

in COn,,nucus tpha.nwna,,.ar

D,W&d

b,

,,,,

K.,.

Procmwal

00,im.rn

---~~

hlRC WI.,,,
ESRANCE
.?!O!M ,,0 ma

CEC

WEE,

Vrnbrti

ES,, I.o.a

stem
.,,
lad,!
..1..

8s *!.!M,

..6

teltmwa

3.11.15
31,.s

*, COmoh!$,o01 Wxwu,,

,,

coc,,F.nd
,,
no, ,U,,,p,l.
by

f.~e.

3 1%.13.2

#
,,.

3.11. !3.2

w...

3.11. !3.7

~,,,.,,,

mm.s.r.

ma

FIGU8E 18. @alitY

assurance check sheet (Form OPNAV 4790/132). - Cantinued

o -.
4

98

MIL-P-24534A(NAVY)

091.

0s18

THEFOLLOWNQ
A8819vI.IIoIIs

.,

J._5z-l

DESIRED
STANDARD
CONDITION

No.

CHECKS
.

CONCERN
-WRE

w+Irmwd

3.11.1.10

Flows n numt+rcdM ,.IOIMCW m t-t.

WI ,IMamd .xltolh

PI.!md wordsndP,lmls

07.

rwt.llz.tlcm momsstandard
ctwlla
urn m

-Is Slnldwds

3,!1.1.9

andSYmBOls
u. meslu.

Sgulq Mldtm,

SLOW

3.91.94
3.14.6.1
3.14.3

AWIMOIZ A
ADpOndl, c
3. f1,14.l

c..

c 0ML1?%
,.. ,*,

Riz

cc.

SMEE

l?,

FIGURE 18. Quality aasurance check sheet (Form OPNAV 4790/132). - Continued

99

f41L-P-24534A(NAVY)

J
TASK APPLICABILITY AND EFFECTIVENESS CRITERIA
TASK

APPLICABILITY

EFFECTIVENESS

~ma-Directed

Scheduled
(w

Rework

Probability of failure must

increase at an identifiable
nge. A large proportion of
units must sutvive to that
ege.

%r critical failures
The
ask must reduce the risk
>f failure to an acceptable
evel.
For all other failures The
task must be cost% ffecIive.

Scheduled
(LL)

Life Limit

ConditiorvDirected
(CD)

Failure Finding
(FF)

FIGURE 19. Tack

For safe.llfe items: Proba.

bility .ol failure below life
Ilmit must be zero.

A sale-life limit must re.

duce the risk of failure to
an acceptable level.

For economic.life
item%
Probability of failure must
increase at an identifiable
age. A large proportion of
units must survive to that
age.

An economic-life
limit
must be cost-effective.

Reduced
failure
resistance for a specific failure
mode must be detectable.
Rate of change in failure
resistance
must be rea.
srmably predictable.

For critical failures: The

task must reduce the risk
of failure to an acceptable
level.

Occurrence
of functional
failure must not be evidenl
to the operating crew dur
ing performance
of theil
normal duties.

The task must increase

availab)fity of the affacted
function to an acceptable
level.

app

For all other failures The

task muSt be COS1-SffeC
tive.

liability and effectiveness criteria.

100

MIL-P-24534A(NAVY)

m
/-

FIGURE 20.

Typical SWAB system breakdown.

101

MIL-P-24534A(NAvY)

nal

#Owluu,*

wutawmnm
. . ..____

NVM,m

s-cum

7211

GMI.5

w+,
GUM

sn,~,

DDG.9$3

FIGURE 21.

Functional block diagram (Form OPNAV 4790/133).

102

e--

MIL-P-24534A(NAVY)

FIGURE 22.

RQI decision logic tree.

103

MIL-P-24534A(NAVY)

CONDITIONAL
PROBABILITY
OF
FAILURE
(NAZARO RATEI

PROBABILllY OF
FAILURE INCREASES

TIME OR AGE
TIME

FIGUSE 23.

OIRECTEO
TASK IS APPLICABLE
IF ABOVE SITUATION
HOSTS

Characteristics of an item for which hard-time

tasks are applicable.

I
104

MIL-P-24534A(NAVY)

J
FIGURE 24.

com letd
(F~rm

RCM documentation
opNAV

COntrOl

4790/125).
.,

105

oheet

UIL-P-2&53hA(NAVY)

BHIPSYSTEM

SIJB6YSTEM

Mm CODE

R-28
BV8WH

E0uPuEN7

n-1

nNE.5
FTN3
F2WSN

AHISPS-39A
Radar Set

W
3.9
3.9

TOTAL W4

UA4NTENANCfW.WbREMENT DESCMF710N

7.8
1. Test

coordinate

data

computer

and display

console angle accuracy.

ELAPSEDTIME

3.9

2. Test display console range accuracy.

3. Test azimuth gated variable
ELSCAN operation.

SAFETYPRECAUTIONS

1. Forces afloat comply with Navy Safety Precaution for Forces

Afloat, OPNAVINST 5100 series.
2. When BATTLE SHORT svitch is on, protective interlock switch is
bypassed and voltages danserous to life are present. Do not work
alone.
tWLS. PARTS, MATERIALS,lES1 EWIPMf N1

rEST F.QUIFME~
1. [0945] oscilloscope,
50 Hffz 7 ns (SCAT 4308)

2. [1529] Voltmeter, Diff

ACIDC (SCAT 4208)

MISCELLAIWJUS
set,
1. [0637] Headset-chest
electrical, type H-ZOO/U,
sound-powered

HOTE: Numbers in brackets can be referenced to Standard PUS

(SPNIG)
for
stock
number
Materials Identification Guide
identification.

.
s

8
z

PROCEDURE
Maintenance
procedure
with this requirement is CONFIDENTLY.
Haitenance Requirement Card is stowed in

t-l
>

LCCATION

O%~ober 1981
MA$WENANCE REOUlmEUEN1CA~
m.vti-a:z-a---

FIGURE 25. Locator HRC (FOTM OPNAV 4790/82).

106

=
(MW

..

.J

FIGURE 26. MRC material categories (Form OPNAV L790/82).

107

ML-P-245

Wt? SYSTEU

34A( NAVY)

Wnmslsu

hmc Cajcif

u-1

A-1

lVSIEM

EOIJIPMEM1

Steering

RATES

and Diving

II

R-

I
4AIN7EIuACE
RECUWUEUT
DESCR!FWW4
!. Detexmirm ~teering and diving ram leakages.

mm

nwE
Wm Ws
!. Forces afloat comply with Navy Safety
Precautions for Forces Aflost, 0F?4AVINST5100 series.
!. Ensure rudder and planes are clear of personnel and equipment.
Have word passed to stand clearof rudder and planes during
tents.
WLS. PARTS. MATERIALS.TESTEOIJIWE.1
IATSR2ALS
1. [1408] ?ubins, nonmetallic,
flexible rubber (See Note I)
!. [0120] Seaker, laboratory,
25o M2 (See Note 1)
Pail, utility,
1. [2274]
plastic (See Note 1)
1. Bleederextension(SeeNote 1)

TIXILS
l; [0719] Key socket head screi
3116 (See Note 1)
MISCELLANEOUS

1. Supplemental Report form

2. [1327] Stopwatch

~E: Numbersin brackets can be referenced to Standard w

Materials Identification Guide (SPNIG) for stock

tttnnber
identification.

m
.

PRCCEDURE

iWTE1: Provided by SW
WE

Q
*

Site Team.

2: MS vill

be perfomed vhen directed EV Sf!2i8D

only on
ships equipped with bleeder extenders per drawing
SSBN 619-516-170917.

Pra2i0Snary
a. Obtain permission of cognizant officer(s) to perform NR.
b. Line up steering and diving hydraulic systa for
emergency (vital) operation.
1.

Dmtumine Steering

WASS?ZMO:

DIvttt.s

S=

LaskD8cm.

rudder and planes are clear of personnel and

equipent. Have imrd passed to stand clear of rudder
and planes duringtests.
Ensure

1,
.

0
:
.

LOCATON

OAlt

Narch 1981
htAtNTEMAtbCEUEUHREMENT ~
m.
,mm. *

FIGURE

27.

Unscheduled

MRC

(SW

reference)

(Form

OPNAV

c
iii

4790/82).

J
108

MIL-P-24534A(NAvY)
Mnc CCOE

Suw+vsrm

SMtPSWlsu

rank Level Indicating

system 4372

Interior
cmnwnicat ion
system 430

4372
R4TES
::y

rw

EOUiPMENT

iicating,Order and

Tank Level Indicating

teringSystems437

Systems4372NX

0=e?07AL

comply

with

0.1
0.4
0.2

1.2
ELA~O.~E

Remove pkot ec tive cover from indicators and

panels.
afloat

ml
(See

,TE~~W~17EouIREUENTOE5CRWTION

m wE
Forces

W-l

Navy Safety Precautions for Forces

series.
.. . -..
.
.-------. -_
_-..-.

Aflost, oPNAVINST 5100

LGxxG~-m
ne

___

IOmnE

.TE.Oue to space 1imitations in RATES M/H block, additional

rates and man-hours required are:
0.1
SN3

1C2
SNFN
FN

0.1
0.1
0.2

Remove Protective Cover from Z.ndicatorsand Panels.

Remove tape and fire-resistant
paper frun indicator and
a.
panel meter faces.
b. Remove safety tag and energize system.
c~dition.
c. Return equipment to readiness,

FIGURE 28.

IEM procedure

MRC

109

(Form OPNAV

r3

4790/82).

MIL-P-24534A(NAVY)

PROCEDURE (Contd)
STEP

PwfxwRE

mu1PKP3il

1.

sector
A.

W2DS

RESPONSE

,Perform
Air Tar8etTrackingand
B1a.ki.8

1.8 t.

ControlledAircraft
Target

US%II* normal
procedures.
If?fo

f?fDS

operating
enter
t.rgec

complex

see

and

esc.bli.h tr.ck.
2

Air
Czm-

troller

Vectoraircraftto start
flighcpattern(PointA
0 fi~re1.)

of

Set

NrDs

for
Initiaterequest
disitalco-icatios with
CFCC.

Set

cm

PressRW2EST/SNARLEswitch
SNASLE lemp.
co lip.ht

Enable

Soc

Press

Enable

SPC-60

RNASLE/RADUTE

switchto lightfXASLSlamp.
6

Rotate

WC

D3SiSfUT0R

NTDs

SELSC2

switchto RIDS.
7

Rotate

Wc

to

Pcsc

CCC-2AESV2fi
switch

A. t.rgec

CCC-2

g
.
.

arrive.

at point

B .. flightpattern,
1, assignt. WCS.
9

AA.

Assigned

figure

8
.
(status)

Reportwhen TBXCK lamp

comes on.

10

ccc-2

Record
RunRe
occurred.

11

Fcsc

Releaseasai#nmcncto GFCS.

Releaacd,

12

Air
cOcrol
ler

Vectoraircraftback to
pointA on flightpattern.
fi*ure1.

W.Sit/
Set

at

which

S13TS2: Repeat steps

TRACK

1.8 through 1.12 four

thrcwsh 1.10 once. Afcez

tlmea

(ReadinS)

and then

sixthacquisition,
vectoraircraftinboundtowardpointD, figure1.
steps

1,8

13

CW

k,,. SPG60 OPSSATEswitch

14

SSC-2

Obseme

K$MT

FIGURE 29. 14RCcolumnar

format

110

(status)

l*MP.

.MTEIUNCE SEcunfwnl

Operate

(Form

OPNAV 4790/83).

MIL-P-24534A(NAVY)

/-----

e,

F@m 1. LOuttm

of

elowrClOaanw ChOciPOknta

k. Inst811 dial indicatorbase attachmentto top flange of

cylinder
block.
1. Install dial indic.st.ar
with ball point in.contact with
angles
co
blower driving timing gear teeth at right

ensure
accurate
dial
reading,
m. Move blower driving timig gear

n.
o.

p.
q.
r.

until teeth of giar are

tight againstdriven gear teeth.
Set indieaccmdial to zero.
Hove driving timing gear in op~sit e direction uc il
read indicator.
teeth are stopped by driven gear teeth:
maximum
Proper
timing
gear backla$h
is minimum O .( M)Z.
0.008.
Jack ngine and repeat
steps
i.e.
through
l.o in three
additionallocations90 apart.
Remqve dial indicatorand base.
Remove outer cover from blower and clamp drive gear
backlash LOOI (figure 2) to lower rotor shaft end plate.

FIGURS 30.

Sample

profile

art

(Form OPNAV 6790/83).

111 .

MIL-P-24534A(NAVY)

-W

t-l
&

.&n

i-H-i---i-

3
I

Figure

wDwmt
..

--,...

=.,

..=

,..

:x:::a-:,m-z--=
- --

FIGURS 31.

......,

Sample landscape art (Form OPNAV 4790/83).

J
112

MIL-P-24534A(NAVY)

w :nmc

Mmmcc

Cwwmll

mm

lWNSN?

nAcooo

Lu-1

mm

Wl(

Ridar Sst

AUISPQ-55B
XSSRISS 26
row w
wmknAmcsRcwinrutln Mcam?nou
1.
.

hrform

CW6cDnuc

m mccAunoNI
1. Oboorw scsndardsafty procautkm in cccordmm withSafety
Smry in tSAVSSA
OP 4059,4256,4563Vohmc1.
mmt.MA1aRIAU,

Ceq

mcintmmcs,

lay++

11s7

90ul?~cN?
,,

Nom

*twnl
1! This is scircdulingcmd, Suhsdulod performlistedSW
for lay-up mcintmmcs.

IWS

1. Parfom *4P
)fcimtecmta.,
. Lubricut lemmr
ctucting

machanism.

S-7
b. Inspact and checkMquid cwlant looP.
w-lo
c. Checkhoct c%ehmg8r and purification
wit.
S4-6

NOTS21 Pecmrnot
step l.d,
d.

Zn.cpect

requirad

co

pwform MSCB Ii-tedin

L
lubrlcst
a Radm/Oirector
Mod 6 componcntm.

and

Q-B
Q-n

S-16
S-11
R-6

A-12
S-2
A-2

Q-13
S-5
t

t-p 1.d,uma chc followins cardsforMod S:

s-16 A-12 Q-13 Q-S S-11
s-2 s-5
Q-11 R-6 A-2

IOT123: In

e. In.wtivata
Lu-2

radar set.

FIGURE 32.

IEM scheduling

.}
t

Bf51C ( ?orm

113

OPIPAV4790/S2).

u
.

MIL-P-24534A(NAVY)

-;r
FC 1 Lhr.ush5, and 7
lC SC 1, 3

ID

?C 1

~~

.,.!, W.NC!Wmt,

..

..A ,chedul@
M- I /0-1

ba.k

..-.
aid:

Cmit

report

1.

BzsO N

1.

clean

nO f d-

and inspect

m-l /
Q-2

lrmnsmit

radio

All

0.4

Non,

Nor!,

other

ml

0.s

NnsN

0.1

0-1/

YnsN

0.8

s-l

wSN

0.2 Q++

H-1

et

tins

tra?~itti?a

met.

with .I.a.d-l..p
ir
m.nditlmi..
All other in.tall.ct.n.
perform quarmrly.
..
- . ..-.
i.

mfsn

monthly.

Per
frll
,emi.nnu)ly
Ifequlpm.nt
1s
1.8c.I
led1....tr.nmmc.l
c.bi..k

mm,

=%J

Reqircmmt
aPPIY;

conditioning.
P.. f0~

.Pcrateradio

Test

does fiot

if wivmenc is In.c.11.d
c.bimc 1. . epace with

air

istaliatic.s
N

&&

schmlul1.8 required.

closed-loop

11 MS>

llaiteluce

11 it

i. Ciem air filt.r.

NOTE:Perform w.rterly
in nvlromencal

mm

required.

1 )UndaCory

Q Bm8 N

R*viw

~C

9cm0
m=

Omcm.w

.- ...-- - ----..

W-II
N-21

spa..

INACTIVEEQU:YSNTmUiT2NASCE

&

me 10IIw1.s

requlr.aents

the

is

quipmenc

*+
A9 Cv.2.4 N

.111b. scheduled

inac Civatod

for

vr.lonted

wh.e
variods.

lkintenaOcX

I
l. tall
prOt*cc iv* COv.ris.
mors: Accomplish
if indamtri.2
par fotmed
rtiidi.

in

w-l
work

i.

Of .WiPOMt

ViC hit?

0.2

Mss

h,

to b.
.

r.i.t-.

nm.

Smrt-t!p
k9 CKL5 H

1.

ml

MaUv.

Prot..

...
c$v.

Su-1 R)2al 0.s 2WU

Cov*rinI.

V**mc W-lIQ-2.

1.Cl-m
m:

IIaimm

us.

nd inspect
radl.
~C Q-115-1.

crmmmitcins

mat.

1.

., ..,, -!. ,*

mn

aw

*.cm

,,

CONIML

.IJ*l

.. ..

R L- iol

..

1- I L

FIcami?33. MIP including inactive equipment maintenance (IEli~

(Form OPNAV 4790/82).

--- )
114

MIL-P-24534A(NAVY)

s,,,

s,!,

0.,,
JuIY

m.famlc, Wu=lwws

m Ew-m,

Sues.ur..

0P
0?
0P
0P

bbe , TOrPed O , SV
k. 32 Hod 14
sol
,PD-963 CUSS)

OD 4243>
OD L2987

4
EAl
335s
33s9

1981

SU395-AS*
flk32ffod14

-0101

w.
hi.

3f1P r-f lect.

OFLM2.TS:

8606,

OShL.T 9226;
8737,

9138,

ht%ever,

-it

sho.ld

be

Implemcntuf

before

OSDU?

.cion.

9226

=
AlrErlAnctFmmcwr OEsc.nlca

.,
.

install

&.

ATE,

1- I

IBM

t-l

M3
USN

).0

s-6

Lo

-2

PfSN

>.5

I.lw

1.5
2.5

a-1

3.U
1.0

f. I
!!- 1

rM3
2?!5N

1.5

M-1
Q-2

A-

2?!3
CMSN

l.:
1.:

Q-1

A-

2-HI
I!!SN

3.
3.

Q.:

Lm6u12n6id.:
Use 0P 3355end ..n[racc.r

prep. red data fur

SVT2 ~ 32 Plod 14, until release of p.blicaci.n
SU395-AE-M+O-U
I Ul~ 32 W 14.
.[ breech !mschaism
xmual tender calibration
HP ir gage should be performed just before
performing

*C

A-1

Seview Plain t,..,.

which

do not

Rewlrwnecs.

apply;

schedule

Per foma.ce

check,

FC RIP

in

mit

no feedback
of

PmC M-1

required

transmission

J-T1I61O.

URP~
TUBE W. 32
Instxct
torpedo cube md Cube loaded
13RPW
Test
!. Test
1. Test
,. Test

MX(*)

repcml

TUSE W 32
breech mechanisms
for leaks.
s.curine
mechanism.
firing
solenoid
valve
for leaks.
CM..al firing
operation.

3-2

WIXMSAD !43U6TSU CUf/TROL SUX

,.

l.+

and test

fw.need c.ancWI box

bulkhead

. . . . ..ti . . . . switches.

..~

!REECH mcsAs IsH M I

1. Perform
14 hour Press.,,

i.dic

-r..

q-l
drop

c-.1.

Q-1

r09.P~TDBL
W 32
1. l,pe.t,
.1.,.
nd lubricate
b.rrels.
mechanism.
nd =..
C.
Z. Lubricate
emecsency sq.ib
fireswitch
rouwu

TUBE JUNR1ON
lectrical

r.

Ir,spect

2.

inspect
mount
and seals.

barrel

.0

torpedo-.

Sec.ri.m
plunger.
s- I

20XSS
system.
junction

l.:

box cunnecttcms

SRCECH MSCHAN[S!4 ~
I
1. Lubricate
firing
valve
assembly
0-rln&>.
2. Perform
hydro, tat 1. lust
.f breech mvchanlsm
air
flasks.
TUW~
TUBE W 32
1. C1e.n.
inspect.
nd 1.bric~,e
r Lnni
2. Clean.
inspect
and Iubricatt
cylinder
assembly.

IWSN

breech

tucking

Safe-re.dY

FIGu3W

3fI.

MIP liGting
~quipmnt

s-:

requirements
under specific
SySted
headings
( Form OPNAV ~790/84).

.115

MI L-P-24534 A(NAVY)

Is

,W.

;WP SVSTEM

3 swce

SUB5YS1EM

;YSTEM

u% CODE

Guided f41ssi.le
Lamching System Ilk 10
All Mods

5ZEAAHT D-1

EOUIPMENT

WTES

F-

Gms Crxupoents

WH
\

GMtt2
3GKU3
G2tusN

I
1,
iiIN~NANCE RfWnEMENT OEscmrnON

0.5
::;\

TOTALWn

2.5 e

*trally
Iceatod

,1.Perform daily readiness test.

Uyy!
SFel, WIECAU7,0NS
1. Observe standard safety precautions in
accordance

with

SW394-AC-M24A-010

Safety
/LS 10

Smimary
I~sx

in

technical

manual

2. Soundtrain

warning
bell and loading horn before starting
motors.:
3. Verify that persoel are in a safe area before moving
equipment.
4. Verify that launcher training area is clear before opening
blast doors or moving 1.mncher.
1

00LS, PAWS. 14ATERIALS

TESTEOUIPMEN1

HISCEZ.LANF.OUS
1. [0637] He.adset-chestset,sound

povered

NOTE: Numbers in brackecs can be referenced to Standard PPfS

k----+

Materials Identification Guide (SPtfIG)for stock num-

.3

.
L

lhOTE1: Only POS qualified personnel, or trainee

mder
supervision of qua]ified operator, may operate equipment.

a. Establish phone communication with EP2, EP3, EP4, EP5 \

operators and 1a.ncher safety observer.
b. At SPl, position all circuit breakers to ON, except
CBZ2.
t
1. Perform Dai3y Readinese Test
1,

>

Wamiws,

Ca.tima

and Notes)

WASNZ2W: Sound train warning bell and loadias horn before

starting motors.
.
~.

At

EP2,

start

mm,.

I
DATE

LCCATC+4

July
~M;:~W4;E~E>WW

1981

REMEN1 CARD (MM

FIGURE 35. f4RCwith spacing standards (Form OPNAV 4790/.82)

.
.../

{16

MIL-P-24534A(NAVY)

-.

I
, mm.

-w.

IA=--

l..

Ii

.c~~,mll!l;,.

D
,,. ... ..
M.

Flint
wadlnltld
- WmPmh
mm
d
--\

U,l,C,

AWIJ?D-4
AluWD+A
#vwD-u

PC1 ,hreuIh
K 1.2
n 1 Ulr.ush

AsmD-4c
An/lmD-Ln

m
K

@
t

1.1
1.2

.,.

..,.,

,.t,.d]
i~,po..,
,rwidid.

1.

cl.-

~1.

T., t

mei

only,

.1,fit,.,..
b

over.,.
61,.,,
Ion f t.d.. . . . .

II. lent r.c.t..r ,...,,,.l

,7.
1. cl.-.
imp=,. & lnbrle.t. dir.cclen rind..
.. ..
1. Sch.d.l. Ant. . . .
F 11. U1
Son!:

$ccspl

I&h

AS-51b

duri.*

fW

.hl P,.

rnnv.1

..d

w.rh..l

w.r -

Prtod,

0.

1J

norm

1,1*
lb.

I cl.., .1, Illt.

r..
Mn,
u..Pmcn-l.
W*UM-1

v,

,. ,..,
W*.,.
dine, Ion f I.-*r
mm: u.. ImC0.1.

.4.

..t

,,--

/wlmt

./

Alrnatnt.nmc.

Lean blank who. mv Mm

is
womssa when maoplwwaMRCS,
..1- the svscw hwc controlnumber

FIGUNE 36.

lot..

MIP

MRC

rm.immww

m!-

nd M**
saIM WW

mustk 1!s!6.S
on I*

-.

by

To M MM in
COOrOm,lilw Dr,liitly

with spacing standarda (Porm OPNAV 4790/84).

117

.,-.

-, . . . . . .. . .. .. .

mLL-r-z4>*4A(NAVY)

. .
+===-t%

..

2. Clean ad ir,wt
pr.fllt.r
eh~k
3. l-pact
dehydrator for labs.
.m.
1.

v.lv,

1.s

(cVI).

dce-boof

m subject to bih Leqaraturt,~).

per f.im
1. ten,ee , COmpm.nt, ,,
MOugll co pett
Zlmtdllg nd muchi .Ithl,
4.,,
of
b.,rm..

2. ITi!ccks1-

M,ml?.tlmcpriorm
-01
.kln

F%!!&-- 3=,=7
0-r21w21z
h,,

-.

4V0
WY
/+?5
/769
/Jr9
/754

.2

. . . . . ...

1..

I
mm

-~%2z3/

FIGURE 37.

Corrected MRC for computer input (Form OPNAV 4790/82).

J
118

MIL-P-24534A(NAVY)

,,!

J-=@il--

!jij
:

!1-.--

I4

FIGURE 38. MIP marked up for revision (FO~

119/120

-------- --

QPNAv 4~~Q184~.

MIL-P-24534A(NAVY)

f--

10. SCOPE
his appendix provides word usage guidelines included in the
10.1 a.
Government Printing Office Style Manual (see 2.1.2) which shall be used unless
modified herein. The appendix is a mandatory part of the specification. The
information contained herein is intended for compliance.
10.2 Use of articlea in technical writinK.

(a) System or equipment titles. b article ia not used when system

or equip@ant titles contain nomenclatures AM, Mk, Hod, or unit
numbers; for example, Power is supplied to Sonar Set AN/BQR-2.
(b) Deletion of articlea. Deletion adda to brevity and impact and
is desirable whenever it doea not lead to confusion.
(

1)

Some.modifiers
expressions
the rest of

also have verb forms.

depends upon the uae of
the sentence
clarifies.

The meaning of such

the articlea,
unleaa
writer
The technical

must be careful; however, to keep the meaning clear.

This................couldmaan this..........or this.
Open door
Lead wirea
Wire gages
Slack line
Correct alignment
Test oscilloscope
(2)

Open the door.

Lead the wires.
Wire the gagea.

Slack the line.

Correct the alignment.
Test the oscilloscope.

The
the
the
the
the
the

open door
lead wlrea
wire gagea
alack line
correct alignment
teat oacilloacopa

In most cases, the article the should be eliminated from

the MRC.
Example a: Remove the paper from the typing unit.
Preferred: Remove papsr from typing unit.
Example b: Remove the typing unit from the bsse.
Preferred: Rsmove typing unit from base.

10.3 Personal pronouns. The personal pronouns commonly used on HICa are
it and their. These can usually be omitted without changing the meaning of
the eentence. When possible, they should be omitted.
10.4 Uae of that. It ie not necessary to unite eneurechat- on MRCS.
Ensurealone ia sufficient.
(a)

This rule does not apply to other worda, such ae verify, observe,
inform, advise, and eo forth.

121

MIL-P-24534A(NAVY)
APPENDIX A

(1) If these words are followed by a clause, the word that

For.example:
should introduce the clause.
Verify that the motor opz!rates
smoothly.
Ensure that the lamp is Ij.
t.
(2)

If these words are followed by a noun (and modifiera),

the word thatmay be omitted. For example:
Verify readings.
Observe standard safety precautions.

10.5 Choice of words. he following list contains words and expressions

that are preferred either because they are simple and short, or because they
convey a precise meaning. The choice of the most appropriate word for an
individual situation la left co the writer.

TNIs:

NOT THIS:

Thiswordmay usually

be omitted.
about, for, in, or
heard
ensure
HRC, 14Rcard
perform or accomplish,
o
This word should ba used only
when no more specific word la
appropriate (teat, verify, measure).
clean
clean off
wire-brush
claan with wire brush
solvent
cleaning solvent
begin, stare
commance
connect
connect together
build, make
construct
use (N)
consumption (N)
sure
confident
make
create
press
depress
find
detect
diametral
diametrical
Engineer Officer
Engineering Officar
for
for a period of
flush
flush out
freeze
freeze up
show
give evidence of
la lit, lights
ia illuminated
show
illustrate
in a clockwise (counterclockwise) direction clockwise, counterclockwise
if
in case of
start, begin
initiate
inspect for
inspect that

all
aa to
audible
ba sure
card, MRC card
carry out
check

\
122

MIL-P-2453&A(NAVY)
APPENDIX A

NOT THIS:

THIS:

is capable of
manually operate
observe for
outside of
physically inspect
prepare a mixture of
prior to
provided that
put together
recheck
revolve
run
scale information
should this condition exist
such that
take out
take apart
turn on (motor)
usage (N)
utilize (V)
visuslly inspect
warm up
f

wipe

can
operate

inspect for
outside
inspect
mlx
before
if
assemble, reassemble
inspect
turn
operate
acsle
if this condition exiets
S0 that
remove, withdraw
disassemble, dismantle.
start,restart (mOtOr>,;&ergize
,.:
.,
use (N)
use (V)
inspect
warm
renmve

off

~.

(a) The word secure-has more than 30 definitions. A more definite

verb should bs used if at all possible; for exaUIP1e, de-energize.
fasten, stop, stow, tighten. (b) The word type la a useful but often an unnecessary word. For
example, ball valve is preferred to ball-type valve. If the
word cype
- pst be used, the word of
should always fnllow it.
(c) preferred words and expressions.
NOT THIS:

TNIS:

(1) Operate the switch to OFF.

(1) Set (position) switch to OFF.

(2) Rsturn equipment to readiness
condition.
(3) Install new gasket nd reinstall
cover.
(4) rust spots
(5) Oil la free of foreign mstter.

(2),Restore equipment to nohsl condition.

(3) Reinstall cover using new gasket.
(4) spots of rust
(5) The oil is free from foreign mstter.

10.6
Flaws and conventions. Because of similar spelling or meaning,
certain worda are often misused. fiis cauaes confusing statements and leas of
clarity. The most commonly isused
words,
with definitions, are listed:

123

MIL-P-24534A(NAvY)

APPENOIX A
d

ABouT
APPROXIMATELY

in the general area

very close to

of

Approximately is. the word

L
that should

be

used with numbers.

ABOVE, BELOU

indicate high or low. For example, units on a bulkhead are

above or below each other, not over and under.

ACCEPT
EXCEPT

to

AFPECT

always a verb, means to act on; to impress; or to produce

a change in.
aa a noun, means result or consequence. As a verb, it means
to bring about, to accomplish.

EFFECT

get or receive.
to leave out, exclude.

AMONG
BETWEEN

implies more than two objects.

implies only two objects.

ANOUNT

NUMBER

refera to things meagured in bulk, weight, or euma.

refers to things that can be counted.

CITE
Srm

to use as an example, to quotx(verb).

location (noun), area.

CLOSE
SHuT

Electrical contacts are closed.

Valvee are shut.

CONPMS , COMPARE TO
CONPARE WITH
CONTRAST

used to point out likenesses.

used CO find likenesses or difference.
always means to find differences.

CONTINUAL

CONTINUOUS

frequently or closely repeated, with little or no time in

between.
without interruption, unbroken.

ASSURE
ENSURE
INSURS

to promise, give aseurance.

to make certain.
to obtain indemnity against.

EQUIPME~

the implements (as machi~ery or tools) used in an operation

or activity. Tbia meaning usually applies to everything
needed, except personnel, for efficient operation or
service. A collective noun meaning one or more pieces of
equipment.

FARTRER
FURTHER

expresses physical distance

expresses the sense of an idea

FEWER
LESS

refera only to numbers and things that are counted.

refers only to amount or quantity of things measured.

GREATER
LARGER

refers to quantity
refers

co size.

124

MIL-P-24534A(NAVY)
APPENDIX A
,7-

,,:+

,,,
,,,lDE~I,QU
SIMILAR

IF
UNETHSR

.,
used for
conditionsi
used in expressions of doubt.

IN
INTO

generally chows locatlog.

generally shows direction.

iNSTALL
RSINSTALL

something new.
the same thing that was previously removed.

RENSW

to restore to freshnees, fullneee, or aufficiency. For

example, renew oil.
to serve as a substitute for or a eucceeaor of. It
implies supplying a substitute or equivalent for something.
Replace is used with wear-out materiale that require
replacement such as batteriea, seala, and gagketa. For
example, replace gas>ets.

REPLACE
r

,,--,

exactly the same.

related in appearance or nature; alike, though not identical.

INSTALLED,
LOCATSD,
MOUNTED

When describing merely the location of something,

these words can usually be omitted without changing
the meaning of the sentence.

MINIMIZE
REDUCE

ahoul,dbe used only when something has been reduced to an

absolute minimum.
to leaaen to some degree.

NORMALLY

under usual conditions.

PRACTICAL
PRACTICABLE

useful, helpful.
possible to perform, feasible.

OBSERVE

to perceive, notice, or aee something. Observe iteplieano

judgement on the part of the obeervar.;it merely tells the
reader to notice something. For example, Obeerve unit 6
active search display on lower CRT and paeslve ae.erch
on upper CRT.

VERIFY

to prove the truth of by the presentation of evidence, to

substantiate. to determine the accuracy of. Verify
. Impliee
.
that the result, outcome, or condition
can only be correct.
For example, Verify that all status lights on 6A1 panel
are lit.

SIT
SET

to occupy a place.
to put in place.

125

ML-P-24534A( NAVY)
APPENDIX A
.,
THAT

. WHICH

20.

relative pronouns. That (see 10.4) is alweys restrictive; which can be.either restrictive or nonrestrictive.
That refers to persons and things; which ueually only to
thinge. A good iule of thumb to remember is if the clause
can be omitted without changing the meaning of the eentence,
introduce the clause with which. If not, use that.

beth

APPLICABLE DOCUMENTS

Thie section is not applicable to this appendix.

.-)
126

MIL-P-24534A(NAVY)

APPENDIX B

,f-

USE OF NUMERALS

10. SCOPE
10.1 =.
This appendix provides guidelines for the use of numerals.
Guidelines for the se of numerals included in the Government Printing Office
Style Manual shall be used unless modified herein. TWs appendix ia a mandatory
part of the specification; The information contained herein la intended for
compliance.
10;2 Written or figures. The rule for uee of numerals in technical
writing ia baaed on the general principle that the reader comprshende numerals
expressed as figures more readily than the written expression of the number.
(a) Men writing the procedural portion of the MRC, numbers shell
be expressed in arabic figuree when etating time, =asurement,
or quantity of material.
(b) Numeric expressions are written:

(1) At the beginning of a sentence.

(2) When two numbers are used in close proximity (one number
ia spelled out).
(3) When zero 1s used without aseoclated figuree.
10.3 Decimals. Uae a zero bafore the decimal point when another figure
does not precede the decimal even if there is a zero after the decimal point.
10.4 Commae. The comma is used in a number containing four or more
digits. Exceptions occur ii serial numbers, common and decimal fractions,
military time, and kilocycles and metere of not more than fuur figures pertaining to radio; for example, 2300 hours, 1450 kilohertz, 1100 ~tera.
10.5 Aligning figuree in columns.
(a) When double rows of fig.rea appear within a column, connected
by a daah, plus, or minue eign, the word to or a eimilar connecting word; the dashes, eigna, or words are aligned. Plus
and minue signs at the left of figures are placed close to the
figures regardless of alignment. For example:
+40.4
+98.1
-2.9

40 to 600
150 to 300
4 to 10
(b)

Decimal

points

that

refer

pounds
left.

at

the

column

are
to

aligned

mixed

except

units

(inchee

in

columne
arid

Yamfe,

coritaining
grams

numbere
and

kllogrsma,

and ounces), in which c-e the COIU~

IS aligned
on the
When a number in a column ia .a decimal, a zero is Naced
left of the decimal point. A zero alOne in a deci~l
is

placed

in

the unit

127

row and is

not

followed

by a period.

HIL-P-24534A(NAvY)
APPENDIX B

In
. columns vith mixed units and decimals of two or more places, no zero is
added on the right. When a column has mixed units with single decimals only,
a zero ie supplied on the right. For example:
39.37 inches
2.6 yards
28.35 grame
0.4356 kilogram
2,204.6 pounds
32,478 ounces

0.7
1.7
3.6
1.56
2.45
1.4
12.8
3.9

0.7
1.6
3.5
0
2.45
0
8.6
12.22

1,000,000

100,000
1,000
100
1
0.1
0.001
0.0001

0.7
1.0
3.5
6.0
12.4
132.0
18.0
24.6

10.6 Raction measurement.

(a)

If 8 fraction ia used alone with a unit of measurement, a hyph~~

should connect them. For example: Oil is stored in l/2-gallon
cana.
(b) If a cOmpound number is used with a unit of measurement, the
number itself ust be hyphenated. Therefore, no hyphen can be
used between the fraction and the unit of measurement. For
example: Oil is stored In 1-1/2 gallon cans.

10.1 Numbers in parentheses. Do not write a figure in parentheses after

writing out a number. This is proper only in legal or commercial writing.
10.8 Page Identification.

.3

(a) When there is more than one page of an MRC, it shal1 benumbered
in the vertical blocks on the right-hand side of the MRC. For
example: Page 1 of 3. A single page MRC is numbered,
Page 1 of l.
on
the MIP, Page 1 of 2 at the bottom of the .firat
(b)
. .. page
.. and Page
2 of 2 at the bottom of the second page would identity a two-page
A single
page MIP is numbered, Page 1 of 1.
U2P .
20. APPLICABLE DOCUMENTS. This section is nOt applicable to this appendix.

128

MIL-P-24534A(NAVY)
;F--

APPENDIX C

CAPITALIZATION

10.

SCOPE

10.1
~.
This
appendix
provides
guidelines
for CSpitAliZ8ti08.
capitalization
guidelines
includedin theGovernment
Printing Office
Style

Manual ehall ,@ used along with the guidelines enumerated in this appendix.
This appendix is a mandatory prirtof the 6pecification. Tha info~tioo
contained herein is intended for compliance.
,

10.2 Titles.

(a) capitalize
the firatletterof everyword, except articles,
short preposition.s,and short conjunctions.

(1)

ArtiCkS:
a, an, the
(2) Short prepositions: at, by, if, in, of, for...
(3) Short conjunctions: end, but, or...

(b) The words in the ship system, ayatem, subayatem, end equlpxerit
blocks are titles. The maintenance requirement description
eentence,ein the procedure block are titles.
(c) Capitalize both parts of hyphenated words in titlee; for example,
High-Pre,eaureAir System.

f.

10.3

Itemized lists.

(e) Theeeoccurin the tools,parts, materials, test quipment

block of the MRC (see figure 31) and aometi~a se eubatepe In
the procedure.

(1)

Capitalize all Iettera of category headings (eee 10.2(a)).

(2) Capitalize the first letter of the firet word in each
item. For example:
TEST EQUIPMSNT
1. [1422] Voltmeter O dB
IMW/600 Ohm (SCAT 4206)
NATERIALS
1. [1144] Tag, safety
2. [1364] Tarpaulin, cotton

duck

10.4 @oted exvrekaions on taga. capitalize the firetletterof each

word,exceptarticles,
shortpreposition,
and short conjunctions;
for x8=ple:
(a)
(b)

Do Not Open.
outof Service.

129

MIL-P-2453&A(NAVY)
APPENDIX C
0.
10.5 Notes, warnings, cautions. When used as a heading, capLtalize eech
letter in the worda: NOTE, WARNING, CAUTION. Capitalize the first letter in
the sentence which fOllOWS One of these.
10.6
belong

in

p%!%eaea

Write the namea of shipa in all capital letters. Side letters

after the ahip name; for example, USS HENDERSON (DD 785).

10.7 Abbreviatioaa.
(a) Ordinarily, abbreviation (ace 3.11.1.9) should not be capitalized. A few are capitalized, such aa HP, LP, Nk, Mod, and Nm.
Examples of those not capitalized are lb and ft.
If
one letter of a normally lower-case abbreviation must be
(b)
capitalized as part of a heading, capitalize all letters.
(c) Capitalize each letter in NAVAIR, NAVSEA, NAVELSX, ORDALT,
SMIPALT, and similarly authorized abbreviations.

..

10.8 Specific locations. When referring.to a specific location, capitalize

the first letter of each word. The uae of an identifying number or letter with
the name of the place makes it specific; for example:
(a) Area 1, Area 2, Area 3...
(b) Nachine Shop No. 1, Panel No. 6
10.9 Nsmea of equipment parta (switches, handlea, and aO forth).

o
-.;

(d

When the operator has to position an equipment part, the name

of the part shall be exactly aa imprinted on the equipment; for
example:

(1) Set TURRET EM31RGSTOP switch tO STOP.

(2)

get tlAN-AUTO switch

to AUTO.

(b) Do not capitalize the name of a part that 1s not imprinted on

the equipment; for example:
(1) Mount captaina firing
switch.
(2) Turret officers emergency switch
(c)

(d)

If both the item name and the nomenclature appear in a sentence,

capitalize the first letter of each word; for example, kijuat
Gun Sight ffk2.
If the equipment ia written but is not accompanied by identifying number, Nark, Mod, do not capitalize the name; for example,
~ju;t gun sight.

130

MIL-P-24534A(NAvY)
APPENDIX C

r-

..

10.10 Missiles. Capitalize all letters in missile names; for example,

TERRIER. Do not capitalize reference to missiles; for example, ballistic
missile.
10.11 Proper nouns now standard expressions. Sane expreeeions contain
words which were originally proper nouns, but which no longer have the meaning
of the proper nouns. They have newj independent maanings; the proper nouns ,are
no longer associated with the expressions. When we say arebic numerals, we
think of the numbers rather than the country of Arabia. When we aay plaster of
paris, we think of the material, not the city of Paris. Do not capitalize such
standard expressions which have come from proper nouns, if they no longer carry
the weight of the proper noun.
10.12 Noun with number.
to denote time or sequence
does
capitalized; for example:

A common noun used with

not
form
a proper
name.

a date, number of letter

Therefore,
it
is not

.
(a) chart B
(b) column 2
(c) figure 7
20.

(d)
(e)
(f)

page 2
table 4
step 2

APPLICASLE DOCOMSNTS. lhis section is not applicable to this appendix.

131/132

UIL-P-24531JA(N
AVY)

APPENDIX D
PUNCTUATION

10. SCOPE
10.1 =.
This appendix providea guidelines for punctuation. Punctuation guidelines included in the (;overnmentPrinting Office Style Manual shall
be usedunless modified herein. This appendix is a mandatory part of this
specification. The information (:ontained herein is Intendad for compliance.
10.2 Period.
.

(a)

Sentencee., Use a period at the end of a complete sentence.

DO not use e period to end a group of words that ia not a
sentence.
Titles.
Do not uae e period at the end of a title, unless the
(b)
title is a complete sentence.
(c) Itemized lists. DO not use e period at the end of itame under
tOOls, parts. macerfalas and test equipment block of the MRC.
(d) Abbreviations. oe not use a perimd after abbreviations on lfRCa,
unless the abbreviation spells a word. For example, no period
is required after qt, pt, gpd, vol, in-lb, and ft-lb. Parioda
are required aftar no. and fig.
(e) Referencea to procedural etepe. References to proceduralatepa
within an KRC ehall be epecific and shall be acceptable only in
the following formata:
(1)

Referencing one step:

x.----step

(2)

Referencing two steps:

x.----

(3)

1. c .---.

step* 1.s. ad lot.--- .

Referencing three or mote

x.-------etep

scepa:

la.(l) through 3.c.(9)(aa)-3- -.

10.3 Camma.
(a) Use a comma after each member within a series of three or more
worda, phraaes,lettera, or figures used with and, or, or nor.
(1)
(Z)

Using three nouns: Inspect for rust, dirt, 8nd old grease.
Using three modifiers:
Open inlet,
out let,
and discharge
valves.

133

MH.-p-2453k4(N.4vO
APPENDIX D

(3) Using four verbs: Clean, inspect,

compertment salvage valves.

lubricate,

and test lnter-

Abbreviations. When transitional expressions such as i.e. and

e.g. are used as introductory elements, they are always followed
by commss.
Uae a comms where it ia necessary to clarify and to
(c) w
prevent
misreading of a sentence. For example:
Avoidcontact

(b)

with,or inhalation
of, cleaning
solvents.
clauaesor phrases.
(d) Adverbial
(1) When an adverbial clauae corneaafter the resinthought,
when it ia quite short, and when there is no danger that
it can .bemisread, tbe comms nay be omitted. For example:
Replace piston valvea if worn.
(2) An introductory adverbial phraselausually set off from
the rest of the sentence by commas. For example: If
pointer rests to left of B msker, replace batteries.
(3) TO avoid cOnfuaion, sometimes it is necessary to punctuate
an adverbial phrase which comes after the main thought.
For example: Replace valvea, if worn, and gaaketa, if
deteriorated.
(e)

The uae of the comms is often a matter judgement. Cemmaa

should be used only for easy reading and for clarity.

-,
d

10.4 Colon.
(a) The colon Is ueed to fntroduce explanation, examples, quotations
and enumerations. A colon shall not be used after include, and are.
Titles. Use a colon after a merginal title when copy follows
(b)
the title. For example:
(1) NOTE: Accomplish after 672 hours of operation.
(2) CAUTION: To prevent damage to a generator or regulator,
do not operate engine below rated apeed without
netting regulator switch to off.
(c)

List. Uae a colon after a word that formally introduces a

~t.
For example:
(1)

...at Control Panel Mt 362, position switches:

Position

Nomenclature
CONVENTIONAL WIRS GUIDE POWER
FlitsCONTROL INDICATOR POWSR
PRESET POWER

ON
OFF
OFF

./

134

MIL-P-24534A(NAVY)
APpENDIX D

10.5 Semicolon.
(a)

(b)

(c)

Uae the eemicOlon between two main clauaes not linked by a

coordinating conjunction (and, but, or, nor, for)
or by the
connective ao and yet. For example: Be cautious of loose
barbs when handling wire;.wear gloves to prevent gouging hands.
A aemfcolon may be used to separate items in a series when the
items contain internal commas. For example: Inspect equipment
for pitting ,on outer aurfacea; wear, especially on reeving
parta; and cracks around edges.
OCInot uee a .aemicolo.between parts of unequal grammatical
rank, such aa a clause and a phraae or a main .&lauaeand a subordinate clauae. For example: Conettuct two wave shaping
networks; aa shown on figure 1.

10.6 Apostrophe.
(a)

(b)

Plural abbreviations. The generaI rule is to use an s to form

the plural of abbreviations written in all capital letters. In
technical writing, the accepted usage has allowed the apostrophe
to be omitted when a lower case s is used; for example, MIPs
and KRCa. ,
Poaaeaaivea. The posaeasive caae la not used in expreeaiona in
for example,
the motor frame
which one noun modifies
another;
or motor bearing.

10.7 Quotation marke

quotation

marks.

(quoted
expreaalons).
example:
De-energize
circuit

For

Enclose
and

statement
tag

Out

on
of

tage

Service.

In

10.8 Underline.
(a) Headings. Uae a solid line to underline the headings on MRCS
that are prepared in columnar format (see figure 29).
(b) Emphasia. !dhenemphasizing words, underline each wOrd separately.
Do not underline the entire expression with a sold line. For
example:
& not disturb
needle valve aettinK.
10.9 Parentheses.
(a)

(b)

Q?2E Useparentheaea to enclose worda or expreasiona that are

inaarted for comment, explanation, translation, or reference.

For example: At USWCS SWBD (Panel
123), poaition ZEROING switch
to ZERO.
Punctuation.
(1)

A reference in ps.rentheaeaat the end of a sentence is

placed before the period unleea it ia a complete sentence
in itself. For examples:
Release four latches (two on e8Ch side).
Connect oscilloscope to test point TF-7 (see figure 1).

135

.-

MIL-P-24534A(NAvY)
APPENDIX D

(2)

If

a sentence

(3)

end is placed before the period. For

example: Remove hinge and O-ring (see figure 3) from
mounting plate (acefigure 2).
Do not put a coma before a parenthesis.
the

(c)

one

at

contains

more than

one

parenthetic

reference,

the

Do not use parentheses

within
parentheses.
Double parentheses.
Use a pair of dashes for the outside
parentheses;
for example,
)-revealed
A ahipcheckmade
in 1972 by NSWSES (Code .4400

minor technical errors.

10.10 Hyphen (compounding rules).
(a)

Use a
(1)

(2)
(3)

(4)
(5)
1

(6)
(7)
(8)

(b)

-.

hyphen:

To join two or more words that serve aa a single modifier

before a noun; for example, fan-cooled area, shock-tested
valves.
In a long phrase in which several adjectives modify each
other; for example, air-motor-driven pump.
Tn hyphenate a combining verb form; for example, fan-cool
aIea, shock-test valvea.
To avoid an awkward union of letters; for example, reenergize, anti-icing.
When using a single letter to indicate shape, connect the
letter to the word modified with a hyphen; for example,
O-ring.
To separate
words
in equipment
titles on MRCa; fOr example,
Indicator-Transmitter,not Indicator/Transmitter.
Use a suspension hyphen in a seiiea; for example, one or
two-digit numbers.
When dividing words at the end of a line, hyphenate words
between syllables. Never divide a one-syllable word en~g
in cdsuch as sliced or mixed.

o
,

Do not use a hyphen:

(1) When the adjectives modify the noun independently.(not
forming a single modifying idea); for example, a vOlute
centrifugal pump, an emergency power source.
(2) In a long phrase in which more than two adjectives independently modify the noun. Separate such phrasea with commaa;
for example, multistate, mixed flow, volute centrifugal
pump. (A comma is not necessary between the laat two
adjective.)

.-

136

UIL-P-24534A(NAVY)
APPENDIX D
/--

(3)

When more
example,

(f+)

When

proper

than
one
salinity
nouns

word
is modifying
and temperature
are

u8ed

as

the
same
monitoring

word;
panels.

for

modifier.v;for eXample,

Atlantic Ocean salinity.

(c)

20.

Double compound words. When using two long compound words in

sequence, form the cotdpoundword8, and separate them with a
sla8h;
for example,
a cent rol rod drives a bevel-gear-Se~nt/
bevel-gear-arrangement.

APPLICABLE DOCUMENTS. This 8ection 1s not applicable to this appendix.

1371138

MIL-P-Z4>34A(

NAV!)

.-

APPENDIX E

/,----

MAIN
TENMCE

10.

INOEX PAGE (HIP) CONTROL NUMEERS

SCOPE

10.1 g.
This armendix
Drovides guidelines for maintenance index pege
..
numbering. MIPs which result from this ep~cification ere eyetem oriented eti
contain maintenance procedures previously covered by more than one MIP or MIP
Group. The index of maintenance procedures for items which function togethar
or comprise a system, will be listed on a single MIP. The number aasigned to
this NIP will allow cross reference to other Navy data systems and will identify
. .

the eyatem for functional

grouping of items
SWAB will be ueed ea illustrated in 10.1.2

by uae of the SWAS number.

The

to provide the generic identification

of the level of indenture Included on the MIP. The SWAS eeaigned to the NIP
will b the aama as used by the SECAS to identify the level of indentura flhetrated on figures E-1 and E-2. In the abaence of SECAS or SWAE data, the PMS
Goordineting Activity willcoordinate with the SECAS program to obtain numbers.
This appendix is a mandatory part of thie specification. The inf0L70Cti0n
contained herein is intended for compliance.
10.1.1 The SYSCOM MIP control numbers - segments. The SYSCOM MIp cOntrol
number aesigned to MIPa developed in accordance with thie SPacificatiOn ia
compoeed of three aegmenta.
;/---

SEGMENT
1

23

xxxx /xxx-xx

(a) The first segment is a four-digit identifier of the ayetem

or functional grouping of items on which the maintenance procedures provided by this MIP are to be performed. If any of
the last three positions of this segment conteine a O (zero),
the configuration block o.fthe HIp mwat contain the identificatiOn of thoee items which have been grouped tOgether fOr.~intenance purposes and are covered by the index of procedures listed
on the MIP. The conventions to be followed for grouping items
together for maintenance purposes are explained in 10.1.2.
The four-digit numbere and nomenclatures which identify eyetems
by hull will be found in SEGAS reporta by hull which list the
items which comprise subsystems at and below the fourth indenture

level. The firstsegmentof theSYSCOtl

MIP CentrolNumberwill
consistof thisnumber.
(b) The second segment indicetes the sequence of maintenance require(c)
/-

ments development for this functional grouping or system. This

number
will
not
change
unless the configuration changes.
The third segment indicates the date of the HIP. The first
position indicates the month and the second poeition indicates
the year.

139

MIL-P-24534A(NAVY)

APPENDIX E

10.1.2 Segment 1 -- SWAS level indenture. .The conventions for assignment

of the.four digits to the first segment of the SYSCOM MIP control number and
for grouping items which function together for maintenance purposes must follow
the top-down breakdown configuration data in the Navy. This data may be a
SECAS report
for
active
ahip9
and a Fitting
Out Management
Information
System
(POMIS) report
or other
approved
data
for
new constructing
ships.
(a) Thelowest level at which MIPa should be prepared is the
fourth indenture level (SWAE level 4) shown on figure E-1. MIPs
prepared for equipment or components (SWAS level 5) need prior
approval,of NAVSEA, Cnde 56G. MNCS will be prepared for all
items or combinations of items which require maintenance in
the fourth indenture level and will be listed on a MIP identified
by the four-digit number for the indenture level 4 grouping.
If it is desirable to combine the maintenance requirements for
(b)
onre than one level 4 grouping on a single MIP, a level 3 MIP
will result.
Such a MIP must contain the fLNCsfor all items
at level 3, level 4, and level 5 which require maintenance and
will be identified by the three-digit number for the level 3
grouping followed by a O (zero) to maintain a four-digit format.
If it is desirable tn combine the maintenance requirements for
(c)
mre than one level 3 grouping on a single MIP, a level 1 or 2
MIP will result. Such a MIP must contain
the NNCS for all
items or cnmbinattons of items to the lowest indenture level
which require maintenance and will be identified by the oneor two-digit number for the level i or 2 grouping followed by
two or three zeros to maintain a four-digit format.
High
level system tests which require the simultaneous operation
(d)
of items in different trees of the top-down breakdown atruccure
and have no common number amnng them, are to be included on
MIPs containing only test procedures. These will be identt.
fied
by special purpose four-digit numbers in the Weapons Syatema
File (WSF) such as 4401 - Integrated Communication System Test
(see figure E-2). If a special purpose number haa not been
asaigned to the combination of items which it is desired to
test, notify NAVSEA, Code 56G.
For inetancea deacribsd in 10.1.2b through 10.i.2d, the configu(e)
. .
ration block of the MIP must contain the level 4 item numbsr(s)
and nomanclatuke(a), both of which are covered by the IfIP.
The level 5 item number(a) and nomenclsture(s) should be included
when required foi clarity.
MIPs which resulted from developmanta
10.2 Alternate MIP numberin~
befora implementation of this specification may not be aasigned MIP numbers in
accordnficewith the SWAS levela. These MIPs uae two different numbering ayatema
aa detailed in 10.2.1.

140

*
d

._
J

..-.

-, . . . .

APPENDIX E
/--

10.2.1 Convent ional

HIP number in%.

A four segment code is used a~ follows:

SECMENT
2

1
xxx-

34

Xx lxxx-xx

(a) Segments 1 and 2 identify equip=nt groupings. Segmant 1 may

contain from one to three character and is followed by a daah.
Segment 2 may also contain from one to three character, follevad
by a alaah.
(b) Segment 1 Identifies the equipment group and segment 2 identifies
a specific subgroup
or component within an equipmant group. An
example
la A-137. The A haa been aaaigned to auxiliary engineering machinery and the 137 haa been aaaigned to the N-2
comprea.sor.
(c) Segment 3 Identifies a distinct veraion within the equipment
subgroup and may contain from one to three characters followed
by a daah. Segment 3 will include a P aa the first character
for.a preliminary MIP aa described in OPNAVINST 4790.4 Vol. 1.
(d) Segment f+la a two character code that identifies the month and
year. The first POSition indicatea the month and the second
position indicates the year. The Month codes uae a num?ric
idetifier for January through,September,. The letter6A. B.
and C are used for October, November and December; for e%emple,
AO is October
1$80.
MIP may be issued without MRCa to
(e)
In some cases
a preliminary
provide fleet personnel with a listing of maintenance requirements prior,to development of the KRCa. In this casa the date
code will be replaced with a 91 to indicate.preliminary without
NRcs. Revision of the 01 would be an 02. h%en NRCa are added,
then the date code will be iaaued.
10.3 Surface missile :#yatem(SMS) MIP numbering. The ~
utilizes a three segment c6de aa followe:

coding sYstem

SEGMENT
1

5xxXXxxixxx-KX
(a)

f--

Segpant 1 is a aeven character alpha-numeric code that identifien

equipment & system co which the MIP la applicable. The number
la the Equipment Identification Code (EIC) of that equipment
or system. When the equipment
to wfiichthe MIP la applicable
has more than one EIC, the first two character will be 52.

141

MI L-P-24534 A(NAvY)

APPENDIX E

(b)

Segment 2 indicates the specific configuration of the equipment

Identified by segment one. This number changes when maintenance
in
requirements are changed as a result of ORDALT installation
equipments. Segment 2 may be alphanumeric and consist of one
If the ftrst character is a U, the MIP
to three character.

(c)

Segment

is

for

unscheduled

,maintenance.

the dash) indicates the revlson level of

the MI? and may be one or two numeric characters.
3

(following

iO.4
Maintenance
Requirement
Card vertical
coding. i.@intenancerequirement
cards are aaaigned identification numbers by the PMS Coordinating Activity, aa
f Ollows:

..

SEGMENT
I

1234
Xxxxxxx

Segment 1 indicatea the security classification of the MRC; for

example, C for Confidential and S for Secret. Unclassified t.fftCs
do not use Segment 1.
(b) Segment 2 is a date code. The firat character indlcatea the
month. January through September are assigned 1 through 9.
October, November, and December use A, B, and C. The second
character indicates the year. A 21 birchdate would indicate
February 1981.
(c) SegmenC 3 la an alpha-numeric library control number.
(d) segment ~ is assignedthe letter Y to indicate repair parta
which are required for performance of the KRC. The letter N ia
used when the tiRCdoes not require repair parts. The letter U
ia used on UMRCS.

(d

20.

mPLICiiELE DOCUKSNTS. Ihia section is not applicable to this appendix.

142

MIL-P-24534A(NAVY)
APPENDIX E
/--..

SWAE

THE %IP

tNDENNUE LEVEW

!AIP

L2WL 1

\
.

MIP

LEVEL 2

Xxo

LEVEL 3

xxx
,-.

..

11

LEVEL 4

LEVEL 5

MIP NUMBER -,

MIP NuMBER --

XXOO 1AAA - BB
x~o

I AAA - BB

MIP NuMBER ---

XXXX IAAA - BB

MIP NUMBER ---

xxxo:~

t DEvELOPMENT DATE
]1

SEQUENCE NUMBER
SWAB NUMBER

FIGURE E-1. Indenture leVelS.

- Be

It

-J
DEvELOPMENT DATE

SEOUENCE NuMSER
SWAB NuMBER

MIL-P-24534A(NAvY)
APPENDIx E

.-7

.:

n
THE SHIP
SWAB

INDENTuRE LEVELS

Xoo

LEVEL 1

no

LEvEL 2

i
X5x

LEVEL 3.

.-.

Xxss

LEVEL 4

Xxxsxx

LEvEL 5

.
uI

TEST MIP

MIP NUMEER ---

ZZ.ZZIAAA.

LILI
t DEVELOPMENT DATE

t SEOUENCE NUMBER OF TEST MIP

SPECIAL NUMBER FROM SECAS OR
ESPECIALLY ASSIGNED BY NAVESA

FIGURE E-2. Test indenture

levels.

a
J

144

MIL-P-z4534A(NA.Y)

INOEX
Pagq

paragraph

Abbreviations

.,.
.:.
.

,f--..

Acquisition requirements
~ternate procedures
Analyais
Failure modes and effec,ts
F~nct10nal failure
Inactive equipment maintenance
RCM decision logic tree
Servicing and lubrication
Art work

3.7.5
3.7.3
3.7.12.1
3.7.6
3.1.7
3.11.14.1
3.11.1.7, Appendix c
3,11.1.11, 3.11.13*3
3.15
3.15.2
3.15.1

~pitalization
cam ion
Changea
to
PMS d6cuwntati0n
MIP changes
MRcs
Classification, security
~velopment material
f4RCa
~mtor
camfa
~Wosition
and layout
~nf igwrat ion block

requirements

Coordinating
Activi,tY. p~
Criteria
Scheduled maintenance
requirement
Taak selectiOn

logic tree
Analysis
~alysia form
Definitions
Deliverable item
oalivery, phased

3.6.1
3.6.3

I ,~
145

42, 129
42, %
70
70
70

b4

68
63
72
65
h
.

3.7.6
3.7.6.1
6.3
3.8.2, 6.2.2
6.2.2.Z

~cision

17
11
31
19
25
60

5
44

3.4
3.11.3
3.11.3
3.14
3.12.4
6.2.2
3.12.7
3.2

Contract data requirements

Cent rol number colwn.
MIp
@

42
12
60

3.11.1.9
6.2.1
3.11.13.8

6
6

19
24
75
34, 12
74

MIL-P-24536A(NAVY)

INDEX
Para-

Developer qualifications
Development
Coordination
Forma
Development, flow
Development, phaaes
Diagrame
Functional block
SVAB system
DOcumentation centrol
Documentation validation
Documents, Government
Elapsed
time
Equipment block,

3.2
3.5
3.2.1
3.7

4
5
4
8

3.7.2.1
3.6.5
3.8
3.13
2.1

MNC

Failure modes and effects analyais

Figures
Line art
LOcation
Size

References
Fill-in blanke
Functional failure analysia
Functionally significant items
Index
Selection
Functions

10
7
33
69
2

3.10.4.2, 3.11.9
3.11.4.4

38, 50
45

3.7.5
3.11.14, 3.14.5
3.11.14.1
3.14.5.1
3.11.14.1
3.11.2.2
3.11.13.5
3.7.3

17
60, 69
60
69
60
43
58
11

3.7.4.5
3.7.4.3
3.7.3.3.1

3.3

(hvernment documents
Government-furnishedmaterial
Grammatical person and mode

2.1, 2.1.2
3.5, 4..2.2
3.11.1.2

tIealthhazard precaution

3.11 .2.3

..
.

e-,
..J

16
15
12
2
5, 71
41
43

.-/

146

MLL-P-2i4>J4A(NAv

I )

INDEX

Paragraph
Inactive eauiu~nt maintenance
Amalysia
MIP entries
KRCs, verification copy
Procedure MSCS
Scheduling MsCs
System level
Indentation, MSCS
In-process review
Inspection

3.7.12
3.12.8
3.11.21
3.11:21.1
3.11.21.2
3.7.12.2
3.i4.4
4.1.1
h.1, 4.2.3

levels, SWAS
Level of writing
Locator cards

3.6.5
3.11.1.3
3.11.3

7
41
44

3.7.12
3.11.13.7
3.9.1

30
59
35

3.12.8
3.11.10
3.7.9
3.11.7, 3.11.8
3.7.2.2
3.11.2.5
3.10

65
50
27
49
10
44
35

3.12.15
3.15.2
3.12.16
3.12

66
70
67
63

3.12.4
3.12.3
3.12.15
3.12.8
3.12.11
3.12.6
3.12.9

63
63
66
65
66
64
65

Maintenance
Inactive equipment
Requirements
Unscheduled
Maintenance requirementdescription
HIP entry
KSC block
Maintenance Seauirementa Index
Man-hours

System and Subsystem Index

Measurements reference ;
Method Study
MIPa
1
IEM requirements
Sevised
Unscheduled maintenance
Verification draft
Master

HIP, blocks
Configuration
Date
ISM requirements
Maintenance requirement
Man-hours
Other column
Periodicity column

30
65
61
61
62
32
68
70
70, 71

7-..

147

- --.

MIL-P-24534A(NAVY)

INDEX
Paragraph

Rates column
Reference publications
Rslated maintenance
Scheduling aids
Ships system, system, subsystem, equipment
SYSCOM MRC control number
Test column
MRc
IEM
Reviai<ns
Scheduled MRCS
Unscheduled NRCS
Verification draft
MRC, blocks
Elapsed time
Location
Maintenance requirement description
Man-hours
MRC code
Preliminary
Procedures
Rates
Safety precautions
Ship system, system, subsystem, equipment
Tools, parts, materials, test equipment
Total an-hours

3.12.10
3.12.2
3.12.12
3.12.8.2
3.12.1
3.12.7
3.12.5

66
63
66
65
63
65
64

3.11.21
3.15.1
3.11
3.11.22
3.11

61
70
40
62
40

3.11.9
3.11.16
3.11.10
3.11.7
3.11.5
3.11.13.6
3.11.13
3.11.6
3.11.11
3.11.4
3.11.12
3.11.8

50
61
50
49
45
59
56
48
51
45
51
50

MIP
NRc
Numbering, IfRC
steps
Numerals

3.12.8.1
3.11.13.2
3.14.4
Appendix B

65
56
68
127

Objectives, aintenance program

Ordering data
Packaging
Partitioning
Periodicity

3.6.2
6.2
5.
3.7.2

6
72
71
9

3.11.5
3.11.5.2
3.11.5.5
3.12.9
3.11.5(b)
3.11.5.1
3.11.5.3
3.7.6.5.4
3.11.5.4

45
47
48
65
46
46
47
22
48

..

0
.....

Notes

Calendar
Oual
Inactive

equipment

MIP entries
Non-calendar
Number 1 ng
R period
icity
RCN, determination

of

U unscheduled

148

~~L-P-z6534A(NAVy)

INDEX
paragraph

$
~

3.7
3.9
2.3
3.11.13.6
3.11.13.8
3.11.13
3.10
3.10.1.1

phase development
un~cheduledmaintenance
precedence
preliminaryprOcedure
procedure,alternate
procedure,blOck
procedure evaluation
Procedure evaluetion sheet

3.11.1.7,

,>

Appendix

2.2

punctuation

publications

70
71
11

4.
6.2
fl.2.l

@ality assurance
~ality program require-nts
prOgram OrganizetiOn

48

3.11.6

-..

Rates
References
~uipment me.rk~w
Figure
Health hazard precaution data
Index
ne.asurement
Nodel
NRc
Publicat

3.11.2.1
3.11.2.2
3.11.2.3
3.11.2.fI
3.11.2.5
3.lr.2.6
3011.z.8, 3.11.13.4
3.11.2.7
3.11.2.9
3.11.2.10
3.11.2.11
3.11.2.12
3.11.13.4
3.10.4.5
3.10.4.5.2
3.10.4.5.3
3.12.12
3.6

iOns

Specifications and standard

Table
Temperature
T&ls,
partS,
MtIterialS,
IJKIScheduled
~C

test

equipment

~lated maintenance
Criteria
r.ktermining
MIP entries
R.equirewnts

Investigation

PrOcess

Safety devices inclusion in PMS

SafetY erecautiOn blOck
Safety in Procedure blOck
safety related design cha~e recO~endatiOn
Scheduling aids
Scope
SecurltY

class

~velopment material

43
h3
43
44
44
44
44, 57
44
44
44
44
44
57
38
38
39
66
5
12
51
56
21
65
1

3.7.3.3
3.11.11
3.11.13.1
3.7.s
3.12.8.2
1.1

5
44

3.4
3.11.3

if cation

8
35
3
59
60
56
35
35
42, 133
3

149

..

MIL-P-24534A(NAvY)
INDEx
Paragraph

Servicingand lubricationanalysis
Ship system block, MRC
Signs and symbols
Spacing
Spelling
St,andardPMS Item Name (SPIN)
Standard PM Materials IdentificationGuide
(sF?iIG)
Style of text
Submarineapplications
Subsystem block, 14RC
SYSCOM control number
MIP
MRc

3.7.7
3.11.4.2
3.11.1.10
3.14.3
3.11.1.8
3.11.12

3.12.7, Appendix E
3.11.19, Appendix E

65, 139
61, 139

Tables
Location

3.11.15, 3.14.6
3.14.6.1
3.11.2.10
3.11.15.1

61, 69
69
44
61

3.7.6.5.1
3.7.11
3.7.6.5.2
6.3
3.10.4.2, 3.11.9
3.11.12
3.14.2

21
28
22
75
38. 50
51
68

3.11.12
3.11.1
3.11.11.2
3.11.4.3

References
Size
Tasks, Maintenance
Applicability
Definition
Sffective
Temrdnology
Time, elapsed
Tools, parts, aterials, test equipment
Type size and face
Unscheduled
Tasks

25
45
42
68
42
51

51
40
51
45

L
,.

...@

maintenance

3.9
3.9.1

3s
35

Verificationdraft, IIIP
Scheduledmaintenance
Unscheduledmaintenance
Verificationdraft, MRC
Locator MRCB
ISn MRCa
IEM procedureHRCS
IEPIschedulingMRCS
UmacheduledMRCS

3.12
3.12
3.12.16
3.11
3.11.3
3.11.21
3.11.21.1
3.11.21.2
3.11.22

63
63
67
40
44
61
61
62
62

Warning?
Word usage
Wording of text

3.11.1.11.3.11.13.3
Appendix A
3.11.1.1

Functirrna

42, 56
121
40

~:

e
150

u...

WOuI-.,

,.,..,

0rP,c8,

,--

000-.-/,,,s.

INSTRUCTIONS.
In Q mntinuing eff.fl to nuke o.? .tmcbrdimtion docume.ta betlcr. 111. DoD. Pm*d= M farm for wc i.
submitting comments and suggatiom for improvemcnu. All ustm of mili~ry atandardiaation docur.enm me inrit.d to provide
long the Iac.ae tdge fOE3 NOT STAPLE), amd
rauations.
l%u form may be detached, folded along tht, lines indicstrd, taped
M., En btack E., be u specific M pouibfe bou! puticulm problem ueamucbM wordingwbicb rwtuired infmpretattmn, -ss
*

o rigtd, rntictive,
loon, ambiguous, or wu incoinpstible, nd Ci?e pmpod
,cobh-.
Enter in block 6 any mnurkt not refMed to wecifm pam6rspb
ackmowkcdgwnent

wIN be tiled

to YOU *thin

SO days

10 Iat YOU know

wordLu eh.n6ec
of th.

docurne nt.

that your. conun.nu

whkb would alkti~

If black f b ricd

-m

roedvwt

-d

NM

out, an
am bhu

umdtfemd.

NOTE: W
#pwNkatica

form nbty not ba wed to

mquirmitatti

request

on current contracts.

ta waim MY poztionof the refermced

copies of documcnu, nor to r.quest WVVCTS.devbtkoq

or ctuik.tim of
.tborisatian
CommenU submitted o. thki form do not constttuta or imply

document(a) or to

amend contractual

requiremeam

DEPARTMENT

OF THE NAVY

COKMA.NDER
NAVAL S&A SYSTEMS COMNAND (SEA 55Z3)
DEPARTMENTOF THE NAVY
WASHINGTON, DC 2036Z-5/O/
OFFICIALW61NES
~NAL.,*0.~.,v~T,

us,S~

111111

No POSTAOE
N6CESMRV
IF MAILCO
w TM?
UNWED STATE*

BuslNE:sNoR$p~~.,MA!!.
FIRSTCLASS

PO=AGE

WILL BE PAIO BY THE DEPARTMENT

OF THE NAVV

COM?4ANDER
NAVAL SEA SYSTEMS COMMAND (SEA 55Z3)
DEPAR~NT OF THE NAVY
WASHINGTON, OC 20362-5/01

STANDARDIZATION
DOcuwalw NUwmen

DOCUMENT
IMPROVEMENT
PROPOSAL
ASSOCiate
DoCUMENTATION
&lmtwtims-Rewr=S~,)

2. WCUWMT11?LE
REQUIREMENT CARDS MAINTENANCE INDEX
PAGES,
PLAfWEO
MAINTENANCE
SYSTEM:
DEfiELOPMENT
OF MAINTENANCE

UL-P-24534ACNAW)
, NAMC 0P9U9MIWIM0

4.7vPEo*

On OANIZATl ON

0n0AN12AT10NI~_j

f-J

0,,,-,:,

,,

.,
+4

nOBLtU

AMEM

P.-*

Mumbo?

Vld

W.rd,n,:

,. NAME

OF

WBUIITER

hat

MIJ - OP*ton*

1. Vhl.

b. WORK

cd)
MAILING

ADDRESS

(SIM.C

Clly.

SI.

ti,

ZIP Cdl

008!0-0!

. OATC

I
I

~D,?3%
1426

rmmwoua

EOITlON

I* OpOLeTE.

TRLEPMONS
- Optlmsl
OP 8uSMIUION

NUMDIR

[hdmd
G.

fYYMMDD)