Downloaded from http://www.everyspec.

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
v v!

Date 24 28 28 28 28 28 November 1980 November 1984 Hovember 1984 November 1984 November 1984 November 1984

Superseded Page
v

Date Reprinted uio change 7 June 1983 24 November 1980

A-1 A-2 A-3 A-4

v! A-1 lieu New A-2

24 November 1980

2,

Make the
k. b. ;

followlng pen Exlstlng page A-3, Exlst\ng page A-4, ExlWng page A-5, ExIstlng page A-6,
THIj NOTICE AND

and Ink changes: change page number Change page number change page number change page number

to A-5. to A-6. to A-7. to A-8.

3.

RETAIN

INSERT BEFORE TABLE OF CONTENTS.

4. Holders of MIL-STD-1629A w1ll verffy that the page changes Indicated Thls n~t!ce vIII be retatned as a check sheet. herein have been entered, ts a separate publication. Thi$ !ssuartce Each notice ~s to be retained by stock~ng points unt!l the Military Standard Is completely revises or canceled.

Custodians: Army - CR
Atr Force - 17

Preparing Activity Navy - AS (Project No. RELI-0037)

Review ActWltles:
Navy - SH, 0s Army - EA, AR

AMSC N3388

FSC RILI

Downloaded from http://www.everyspec.com

MIL-STD-1629A CONTENTS Paragraph 4.3.1 4.3.2 4.3.3 4.3.4 4.3.5 4.3.6 4.4 4.4.1 4.4.1.1 4.4.1.2 4.4.1.3 4.4.1.4 4.4.2 4.4.3 4.5 4.5.1 4.5.2 4.5.2.1 4.5.2.2 5. 5.1 Tasks Norksheetformats. . . . . . . . . . . Ground rules and assumptions . . . . . . . . . . . . Indenture level . . . . . . . . . . . . . . . . . . . Coding system . . . . . . . . . . . . . . . . . . . Failure definition . . . . . . . . . . . . . . . . Coordination of effort... . . . . . . . . . . . . . General procedures . . . . . . . . . . . . Contributing Information . . . . . . . . . . . . . . Technical specifications and development plans . . . Trade-off study reports . . . . . . . . . . . . . . Design data and drawings . . . . . . . . . . . . . . . . . . . . . . Reliability data. . . . . . . . . FMEA process. . . . . . . . . . . . . . . . Severity classification . . . . . . . . . . . . . . . . FMECA Report. . . . . . . . . . . . . .. + .0 . . O Summary . . . . . . . . . . . . . . Reliability critical item lists . . . . . . . . . . . Category I and Category II failure mode list . . . . Single failure points list . . . . . . . . . . . . .
G G G G G G G G G G G G G G G

(Continued) Page 6 6 6 6 7 7 7 7 7 8 8 8 8 9 10 10 10 10 11 11 11

DETAIL REQUIREMENTS . . . . . . . . . . . . ..*.o Tasks . . . . . . . . . . . . . . . . .+*= .

101 102
103 104 105

FAILURE MODE AND EFFECTS ANALYSIS . . . . . . . . . . CRITICALITY ANALYSIS . . . . . . . . . . . . . . . . FMECA-MAINTAINABILITY INFORMATION . . . . . . . . . . DAMAGE MODE ANI) EFFECTS ANALYSIS . . . . . . . . . FAILURE MODE, EFFECTS, AND CRITICALITY ANALYSIS PLAN.
G

101-1 1o21o3104-

1o5-

FIGURES Figure Task 101 101.1 101.2 101.3 Task 102 102.1 102.2 Example of CA worksheet format Example of criticality matrix . . . . . . . . . . . . . . . . . . . . . . 102-6 102-7 Example of a functional block diagram . . . . . . . . Example of a rellablllty block diagram . . . . . . . Example of FMEA worksheet format . . . . . . . . . . 101-9 101-10 101-11

Downloaded from http://www.everyspec.com

MIL-STD-1629A

MIL-STD-1629A CONTENTS (Continued)

F!gure Task 103 103.1 Example of FMECA-maintainability information uorksheetformat. . . . . . . . . . . . . . . .

Page

103-3

Task 104 104.1 Example of damage mode and effects analysis format APPENDIX APPLICATION AND TAILORING GUIDE . . . . . . . . . . . 104-5

APPENDIX A. Paragraph 10. 10.1 10.2 10.3 20. 40 40.1 40.2 50. 50.1 50.1.1 50.1.2 50.1.3 50.2 50.3 50.4 50.5 50.6 50.7

A-1

GENERAL. . . . . . . . . . . . . . . . . . . . . . .*. .*.* 0==. .* Scope Tallortng ;equ~remen&. . . . . . . . . . . . . . Dupllcatlon of effort . . . . . . . . . . . . . . .

G

A-1 A-1 A-1 A-1 A-1 A-1

G

REFERENCED DOCUMENTS

(not applicable)

. . . . . . .
G

. . . GENERAL REQUIREMENTS . . . . . . . . . . . . Orderlngdata. . . . . . . . . . . . . . . . . . Data Item descriptions (DID) . . . . . . . . . . .

G G

A-1
A-2 A-2 A-2 A-2 A-2

APPLICATION CRITERIA . . . . . . . . . . . . . . . . General considerations . . . . . . . . . . . . . . . Level ofdetall . . . . . . . . . . . . . . . . . Timing. . . . . . . . . . . . . . . . ..* .. . . . . Intended use. . . . . . . . . . . . . . . FMEA(tasklOl). . . . . . . . . . . . . . . . . . CA(task102L . . . . . . . . . . . . . . . . . . FMECA-maintainability information (task 103) . . . . DMEA(task 104) . . . . . . . . . . . . . . ...= FMECAPlan (task 105).... . . . . . . . . . . . Criticality number (Cr) calculation example . . .
G

A-3 A-3 A-3 A-3 A-4 A-4 A-4

APPENDIX A FIGURES Figure Al Basic card entry instructions . . . . . . . . . . . A-2

vi

28 November 1984

Downloaded from http://www.everyspec.com

MIL-STD-1629A APPENDIX A APPLICATION AND TAILORING GUIDE 10. GENERAL

This appendix provides notes for the gufdance of the 10.1 W?!? procuring activity In generating the contractual requirements for a fa~lure mode, effects, and criticality analysis (FMECA). Each provision of this standard should Tailoring requirements. 10.2 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, The tal?orlng FMECA requirements contractual structure, or acquisition phase. are specified in the contractual provisions to include input to the statement of work, contract data item list (CDRL), and other contractual means. It is Incumbent upon the procuring 10.3 Duplication of effort. 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. 30. 40 40.1 followtng: REFERENCED DOCUMENTS DEFINITIONS (not applicable)

(not applicable)

GENERAL REQUIREMENTS Ordering data. The procuring activity shall specify the

a. b. c. d. e. f.

Title, number and date of this standard. Task number(s) required. FMECA plan (Task 105) if required. Indenture level of analysis (4.3.3) required.

Steps to be used in the FMECA process (4.4.2). 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 If an nonautomated LSAR report, if required. automated LSAR output report is required, the information at figure Al must be specified.
A-1

28 November
.-

1984

Downloaded from http://www.everyspec.com

HIL-STD-?629A LSA-060. LCN Master File. Basic Card Entry Instructions. CARD COLUMN
1 ---

DESCRIPTION SelectIon Indicator (SEL IND) Report SelectIon Number (RSN)

INSTRUCTIONS Mandatory entry of S.

2-4

Mandatory entry of 060 which is report number identifying the output report requested. Mandatory entry of an alphanumeric code; A-Z, 0-9, which will uniquely identify this report If a trailer or number selection. 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). 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. Leave blank. Enter the LCN identifying the first Item to be included In the It identifies the system, report. 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. the report is required for an alternate design or maintenance concept of an associated LCN, enter the ALC. See DED 023 for a complete definition of ALC.

Report Control Code (RCC)

Type Card (TYPE)

7 8-18

Sequence Code (SEQCD) Start Logistic Support Analysis Control Number (START LCN)

19

Alternate

LCN Code (ALC)

If

FIG Al Basic card entry instructions A-2 28 November 1984

Downloaded from http://www.everyspec.com

MIL-STD-1629A

20-30

Stop LCN

Enter the Stop LCN to Indfcate the point where the LSAR ADP system will stop extracting Information If no Stop LCN is from the file. entered, all data from and subordinates to the Start LCN will be considered as applicable for the report. See DED 197. Enter the UOC for the model of the equipment for which the report Is to be developed. The UOC must match a UOCentered on the record of the Start LCN. Data not matching the UOC entered will be omitted from the report. A blank UOC will result in selection of all UOCS within the specified Start and Stop LCN range. See DED 536 for a complete definition of UOC. 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 report headers. Mandatory entry of F to obtain the FMECA data only. An F entry wI1l always result in Header Prints.

31-33

Useable on Code (UOC)

34

Service Designation Code

35

B Sheet Option Code

36

Header Print Option (HEADER)

If the output is required to have data element headers for each record type, enter X.
Leave blank.

37

Magnetic Tape Option

FIG Al (centd) Basic card entry instructions A-3 28 November 1984

Downloaded from http://www.everyspec.com

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 Task 105

DATA REQUIREMENTS Failure Mode, Effects and Criticality Analysis (FMECA} Plan Failure Mode, Effects and Critlcallty Analysis (FMECA) Report

APPLICABLE

DID

DI-R-7086

General Requirements Section 4-5 and Task 101 50.

DI-R-7085A

APPLICATION

CRITERIA

This standard has been structured to 50.1 General considerations. 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 All programs do not require the same level when tailoring the requirements. of detail and all programs should not wait until full scale development to implement the FMECA requirements. The level of detail applies to the level of Level of detail. 50.7.1 The FMECA can be accomplished at indenture at which failures are postulated. various levels of indenture from system to part level depending upon the The lower-the indenture information available and the needs of the program. level, the higher the level of detail since more failure modes will be The choice of the level of indenture must be compatible with the considered. program cost and schedule constraints and the system reliability A less detailed analysis which is available in time to requirements. contribute to system reliability is more valuable than a more detai?ed In general, analysis which Is late and makei changes costly and unfeasible. 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. The objective of the FMECA is to support the declslon 50.1.2 wIf the analysis fails to provide usable information at or making process. before a project decision point, then it has made no contribution and is The time-phasing of the FMECA effort is important and should be untimely. 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