Downloaded from [Link]
com
ML-STD-1629A
Notlct 2
28 November 1984
MILITARY STANDARD
PRCUDURES FOR PERFORMING
A FAILURE MOtX
EFFECTS AND CRITICALITY ANALYSIS
loan holders of MIL-STD-1629A
1. The followlng pages of MIL-STD-1629A have been rev~sed and supersede the
pages llsted:
!!k!@x Date Superseded Page Date
v 24 November 1980 v Reprinted uio change
v! 28 November 1984 v! 7 June 1983
A-1 28 Hovember 1984 A-1 24 November 1980
A-2 28 November 1984 lieu
A-3 28 November 1984 New
A-4 28 November 1984 A-2 24 November 1980
2, Make the followlng pen and Ink changes:
k. Exlstlng page A-3, change page number to A-5.
b. Exlst\ng page A-4, Change page number to A-6.
ExlWng page A-5, change page number to A-7.
;“ ExIstlng page A-6, change page number to A-8.
3. RETAIN THIj NOTICE AND INSERT BEFORE TABLE OF CONTENTS.
4. Holders of MIL-STD-1629A w1ll verffy that the page changes Indicated
herein have been entered, Thls n~t!ce vIII be retatned as a check sheet.
Thi$ !ssuartce ts a separate publication. Each notice ~s to be retained by
stock~ng points unt!l the Military Standard Is completely revises or canceled.
Custodians: Preparing Activity
Army - CR Navy - AS
Atr Force - 17 (Project No. RELI-0037)
Review ActWltles:
Navy - SH, 0s
Army - EA, AR
AMSC N3388 FSC RILI
Downloaded from [Link]
MIL-STD-1629A
CONTENTS (Continued)
Paragraph Page
4.3.1 Norksheetformats. . . . . . . . . . . ● ● ● ● ● ● ●
6
4.3.2 Ground rules and assumptions . . . . . . . . . . . . 6
4.3.3 Indenture level . . . . . . . . . . . . . . . . . . . 6
4.3.4 Coding system . . . . . . . . . . . . . . . . . . . 6
4.3.5 Failure definition . . . . . . . . . . . . . . . . ●
7
4.3.6 Coordination of effort... . . . . . . . . . . . . 7
4.4 General procedures . . . . . . . . . . . . . “ “ “ ●
7
4.4.1 Contributing Information . . . . . . . . . . . . . . 7
[Link] Technical specifications and development plans . . . 7
[Link] Trade-off study reports . . . . . . . . . . . . . . 8
[Link] Design data and drawings . . . . . . . . . . . . . . 8
[Link] Reliability data. . . . . . . . . . . . . . . . .
●
8
4.4.2 FMEA process. . . . . . . . . . . . . . . . “ “ ● ●
8
4.4.3 Severity classification . . . . . . . . . . . . . . . 9
4.5 FMECA Report. . . . . . . . . . . . . .. + . “ ● ●
10
4.5.1 Summary . . . . . . . . . . . . . . .0 . . “ “O ●
10
4.5.2 Reliability critical item lists . . . . . . . . . . . 10
[Link] Category I and Category II failure mode list . . . . 10
[Link] Single failure points list . . . . . . . . . . . . . 11
5. DETAIL REQUIREMENTS . . . . . . . . . . . . ..*.o 11
5.1 Tasks . . . . . . . . . . . . . . . . .+*= . ● = 11
Tasks
101 FAILURE MODE AND EFFECTS ANALYSIS . . . . . . . . . . 101-1
102 CRITICALITY ANALYSIS . . . . . . . . . . . . . . . . 1o2-
103 FMECA-MAINTAINABILITY INFORMATION . . . . . . . . . . 1o3-
104 DAMAGE MODE ANI) EFFECTS ANALYSIS . . . . . . . . . ●
104-
105 FAILURE MODE, EFFECTS, AND CRITICALITY ANALYSIS PLAN. 1o5-
FIGURES
Figure
Task 101
101.1 Example of a functional block diagram . . . . . . . . 101-9
101.2 Example of a rellablllty block diagram . . . . . . . 101-10
101.3 Example of FMEA worksheet format . . . . . . . . . . 101-11
Task 102
102.1 Example of CA worksheet format . . . . . . . . . . . 102-6
102.2 Example of criticality matrix . . . . . . . . . . . 102-7
v
Downloaded from [Link]
MIL-STD-1629A
MIL-STD-1629A
CONTENTS (Continued)
F!gure Page
Task 103
103.1 Example of FMECA-maintainability information
uorksheetformat. . . . . . . . . . . . . . . . ●
103-3
Task 104
104.1 Example of damage mode and effects analysis format . 104-5
APPENDIX
APPENDIX A. APPLICATION AND TAILORING GUIDE . . . . . . . . . . A-1
Paragraph
10. GENERAL. . . . . . . . . . . . . . . . . . . . . . A-1
10.1 Scope .*.● .*.* 0==. .* A-1
10.2 Tallortng ;equ~remen&”. . . . . . . . . . . . . . ●
A-1
10.3 Dupllcatlon of effort . . . . . . . . . . . . . . . A-1
20. REFERENCED DOCUMENTS (not applicable) . . . . . . . A-1
40 GENERAL REQUIREMENTS . . . . . . . . . . . . . . . ●
A-1
40.1 Orderlngdata. . . . . . . . . . . . . . . . . . ● ● A-1
40.2 Data Item descriptions (DID) . . . . . . . . . . . ●
A-2
50. APPLICATION CRITERIA . . . . . . . . . . . . . . . . A-2
50.1 General considerations . . . . . . . . . . . . . . . A-2
50.1.1 Level ofdetall . . . . . . . . . . . . . . . . . “ A-2
50.1.2 Timing. . . . . . . . . . . . . . . . ..* .. . A-2
50.1.3 Intended use. . . . . . . . . . . . . . . . . . ●
A-3
50.2 FMEA(tasklOl). . . . . . . . . . . . . . . . . . A-3
50.3 CA(task102L . . . . . . . . . . . . . . . . . . A-3
50.4 FMECA-maintainability information (task 103) . . . . A-3
50.5 DMEA(task 104) . . . . . . . . . . . . . . ...= A-4
50.6 FMECAPlan (task 105).... . . . . . . . . . . . A-4
50.7 Criticality number (Cr) calculation example . . . A-4
APPENDIX A FIGURES
Figure
Al Basic card entry instructions . . . . . . . . . . . A-2
vi
28 November 1984
Downloaded from [Link]
MIL-STD-1629A
APPENDIX A
APPLICATION AND TAILORING GUIDE
10. GENERAL
10.1 W?!?” This appendix provides notes for the gufdance of the
procuring activity In generating the contractual requirements for a fa~lure
mode, effects, and criticality analysis (FMECA).
10.2 Tailoring requirements. Each provision of this standard should
be reviewed to determine the extent of applicability. Tailoring of
requirements may take the form of deletion, additio~, or alteration to the
statements In Sections 3 and 4 and any specified tasks to adapt the
requirements to specific system characteristics, procuring activity options,
contractual structure, or acquisition phase. The tal?orlng FMECA requirements
are specified in the contractual provisions to include input to the statement
of work, contract data item list (CDRL), and other contractual means.
10.3 Duplication of effort. It is Incumbent upon the procuring
activity to review the contractual requirements to avoid duplication of effort
between the reliability program and other program efforts such as safety,
malnta~nablllty, human engineering, test and evaluation, survivability and
vulnerability, maintenance planning, and Integrated logistics support.
Identlficatlon of the coincident use of FMECA results by the reliability
program and other disciplinary areas is required in the FMECA plan or other
appropriate program documentation to avoid duplication of effort by the
procuring activity and the contractor.
20. REFERENCED DOCUMENTS (not applicable)
30. DEFINITIONS (not applicable)
40 GENERAL REQUIREMENTS
40.1 Ordering data. The procuring activity shall specify the
followtng:
a. Title, number and date of this standard.
b. Task number(s) required.
c. FMECA plan (Task 105) if required.
d. Indenture level of analysis (4.3.3) required.
e. Steps to be used in the FMECA process (4.4.2).
f. FMECA report (4.5) if required. Code A In block
8 of DD1423 if preliminary draft is required. An
automated LSAR output report LSA-060 or a
nonautomated LSAR report, if required. If an
automated LSAR output report is required, the
information at figure Al must be specified.
A-1
28 November 1984
.-
Downloaded from [Link]
HIL-STD-?629A
LSA-060. LCN Master File.
Basic Card Entry Instructions. ---
CARD COLUMN DESCRIPTION INSTRUCTIONS
1 SelectIon Indicator Mandatory entry of “S”.
(SEL IND)
2-4 Report SelectIon Number Mandatory entry of “060” which is
(RSN) report number identifying the out-
put report requested.
5 Report Control Code (RCC) Mandatory entry of an alphanumeric
code; “A’’-’’Z”,“0’’-’’9”,which will
uniquely identify this report
number selection. If a trailer or
option card is associated with thts
report selection, it must match the
RCC on the basic slection card.
(If necessary, instructions for
trailer cards will be provided
by the requiring authority).
Type Card (TYPE) Mandatory entry of “A” (basic
card). If a listing of the entire
content of the LCN Master File is
desired, no further data is
required to be entered on this
card with the exception of cc 35.
7 Sequence Code (SEQCD) Leave blank.
8-18 Start Logistic Support Enter the LCN identifying the
Analysis Control Number first Item to be included In the
(START LCN) report. It identifies the system,
subsystem, or component for which
the report is desired. Data
element definitions (DEi)) are
contained in appendix F of
MIL-STD-1388-2A. See DED 197
for a complete definition of LCN.
19 Alternate LCN Code (ALC) If the report is required for an
alternate design or maintenance
concept of an associated LCN, en-
ter the ALC. See DED 023 for a
complete definition of ALC.
FIG Al Basic card entry instructions
A-2
28 November 1984
Downloaded from [Link]
MIL-STD-1629A
20-30 Stop LCN Enter the Stop LCN to Indfcate the
point where the LSAR ADP system
will stop extracting Information
from the file. If no Stop LCN is
entered, all data from and
subordinates to the Start LCN will
be considered as applicable for
the report. See DED 197.
31-33 Useable on Code (UOC) Enter the UOC for the model of
the equipment for which the
report Is to be developed.
The UOC must match a UOCen-
tered on the record of the
Start LCN. Data not matching
the UOC entered will be omit-
ted from the report. A blank
UOC will result in selection
of all UOCS within the speci-
fied Start and Stop LCN
range. See DED 536 for a
complete definition of UOC.
34 Service Designation Code Enter “A”, Army; “F”, Air
Force; “N”, Navy; “M”, Marine
Corps’ “O”, Other and “X”, all
when the output report deals
with specific task related data
to be reported and output re-
port headers.
35 B Sheet Mandatory entry of “F” to
Option Code obtain the FMECA data only. An “F”
entry wI1l always result in Header
Prints.
36 Header Print If the output is required to
Option (HEADER) have data element headers for
each record type, enter “X”.
37 Magnetic Tape Option Leave blank.
FIG Al (cent’d) Basic card entry instructions
A-3
28 November 1984
Downloaded from [Link]
MI L-STD-1629A.
40.2 Data ttem descriptions (DID). The following listed DIDs provide
a source of possible data Item description and format requirements for
required data.
SOURCE DATA REQUIREMENTS APPLICABLE DID
Task 105 Failure Mode, Effects and DI-R-7086
Criticality Analysis (FMECA} Plan
General Failure Mode, Effects and DI-R-7085A
Requirements Critlcallty Analysis (FMECA) Report
Section 4-5
and Task 101
50. APPLICATION CRITERIA
50.1 General considerations. This standard has been structured to
facilitate the tailoring of FMECA requirements based upon individual program
needs. Program variables such as system complexity, funding, and scheduie
influence the level of detail and timing of the FMECA and must be considered
when tailoring the requirements. All programs do not require the same level
of detail and all programs should not wait until full scale development to
implement the FMECA requirements.
50.7.1 Level of detail. The level of detail applies to the level of
indenture at which failures are postulated. The FMECA can be accomplished at
various levels of indenture from system to part level depending upon the
information available and the needs of the program. The lower-the indenture
level, the higher the level of detail since more failure modes will be
considered. The choice of the level of indenture must be compatible with the
program cost and schedule constraints and the system reliability
requirements. A less detailed analysis which is available in time to
contribute to system reliability is more valuable than a more detai?ed
analysis which Is late and makei changes costly and unfeasible. In general,
the FMECA should not be performed below the level necessary to identify
critical Items or to the level required by the LSA candidate list, whichever
is lower. The depth and detail of the FMECA effort must be defined in
appropriate contractual and program documentation.
50.1.2 w- The objective of the FMECA is to support the declslon
making process. If the analysis fails to provide usable information at or
before a project decision point, then it has made no contribution and is
untimely. The time-phasing of the FMECA effort is important and should be
identified in the FMECA plan to assure that analysis results will be available
to support the project decision points during system development. Since
program cost and schedule constraints require that available resources be used
where they are most cost effective, the earliest possible availability of
FMECA results is Important so that the impact on cost and schedule can be
minimized.
A-4
28 November 1984 *u.m. GovsnMMcwTPRINTIMG OF?ICC 1904-0ss+s0/10167
