MIL-STD-1629-RevA - Barringer and Associates, Inc.
MIL-STD-1629-RevA - Barringer and Associates, Inc. MIL-STD-1629-RevA - Barringer and Associates, Inc.
MIL-STD-1629A1. SCOPEl.l Sco e. This standard establishes requirements and proceduresfor performing+a ailure mode, effects, and criticality analysis (FMECA) tosystematically evaluate and document, by Item failure mode analysis, thepotential impact of each functional or hardware fajlure on mission success,personnel and system safety, systen performance, maintainability, andmaintenance requirements. Each potenttal failure is ranked by the severity ofits effect in order that appropriate corrective actions may be taken toeliminate or control the high risk items.1.2This standard applies to the acquisition of alldesignated DoDY*sys ems and equipment. It pr~marjly applies to the programacttvtty phases of demonstration and validation and full-scale engineeringdevelopment; e.g., design, research and development, and test and evaluation.This standard also can be used during production and deployment to analyze thefinal hardware design or any major modifications. The FMECA tasks containedin this standard apply to all items of equipment. This standard does notapply to software. Appendix A contains additional application and tailoringguidelines.1.3 Numbering system. The tasks are numbered sequentially as theyare introduced into this standard with the fjrst task being number 101.1.4 Revisions.1.4.1 Standard. Any general revision of this standard which resultsin a revision of sections 1, 2, 3, or 4 will be indicated by revision letterafter this standard number, together with date of revision.1.4.2 Tasks. Any revisions of FMECA tasks are indicated by a letterfollowing the ~ For example, for task 101, the first revision is 101A,the second revision is 101B. Mhen the basic document is revised, thoserequirements not affected by change retain their existing date.1.5referenced by2. REFERENCED DOCUMENTSMethod of reference. The tasks contained herein shall bespecifying:a. This standard number.b. Task number(s).c. Other data as called for in individual task.2.1 Issues of documents. The following documents of the issue heffect on the date of Invitation for bid or request for proposal, arereferenced in this standard for information and guidance.1————.=——.ss? a>~—_—_—._—— .—————._—_—_. ..— -=—->._—. .
MIL-STD-1629ASPECIFICATIONSMilitary4MIL-N-241OOManual, Technical; Functionally OrientedMaintenance Manuals for Systems and E@~ntSTAIIDARDSMilitaryMIL-sTr)-280MIL-sTll-47flMIL-STD-721MIL-STD-756MIL-STD-780MIL-STD-785MIL-STD-882MIL-STD-1388MIL-STD-1591MIL-STD-2072MIL-STD-2080HANDBOOKSMilitaryMIL-HDRK-217MIL-HDBK-266Definitions of Item Levels, ItemExchangeability, Models and Related TermsMaintainability Program Requirements (forSystems and Equipment)Oefinitfons of Te?ms for Reliability andMaintainabilityReliability PredictionWork Unit Codes for Aeronaut~cal Equipment;Uniform Numbering SystemReliability Program for Systems andEquipment Development and ProductionSystem Safety Program RequirementsLogistics Support AnalysisOn Aircraft, Fault Diagnosis, Subsystems,Analysis/Synthesis ofSurvivability, Aircraft; Establishment andConduct of Proqrams forMaintenance Engineering, Planning, andAnalysis”the for Aeronautical Systems,Subsystems, Equipment and Support EquipmentReliability Prediction of ElectronicEquipBentApplication of Reliability CenteredMaintenance to Naval Aircraft, WeaponSystems and Support Equipment-(copies of specifications, standards, drawings, and publications requiredby contractors ~n connection with specific procumbent functions should beobtained from the procuring activity or as directed by the contractingofficer.)z~ne 19832
- Page 7 and 8: MI1.-STD-1629A1. SCOPEThis standard
- Page 9 and 10: MTL-STD-1 629A3. DEFINITIONS3.1 Ter
- Page 11 and 12: !’11 L-!;’J’l)- 1629A3. 1.17.
- Page 13 and 14: .MT1.-ST~-l629A4.3.5 Failure defini
- Page 15 and 16: MTT,-sTn-1629Afor each mission, mis
- Page 17 and 18: ?f?l.-STD-l629Ab. Des~ripGlon of de
- Page 19 and 20: MT1,-STD-1629A3.2 Functional approa
- Page 21 and 22: MI J,-STD-16?9Afunctional block dia
- Page 23 and 24: MI L-STD-1629A5.6.2 Next higher lev
- Page 25 and 26: Ml 1,-STD-1079Afurther amplified in
- Page 27 and 28: MIL-STD-1629A. --1III[IIIIIIIIIIIii
- Page 29 and 30: MIL-STD- 1629ATASK 102CRITICALITYAN
- Page 31 and 32: IMII.-ST1)-162(]Ashown in Figure 10
- Page 33 and 34: MIL-STD-1629Awhere:C* = Criticality
- Page 35 and 36: MI I.-sTI)-I629AINCREASINGCRITICALI
- Page 37 and 38: MIL-STD-1629A3*1 Failure predictabi
- Page 39 and 40: .--— .-—--— , --—— ——
- Page 41 and 42: MTL-STD- 1629A4\l Damage modes. All
- Page 43 and 44: NI 1.-[; 1’1)- 1(); ?!)Au0.-.mr-r
- Page 45 and 46: MI I,-ST1)-1629A3. Content. The FME
- Page 47 and 48: —..-A 1MIL-STD-1629AAPPENDIXA10.
- Page 49 and 50: MIL-STD-1629A50.1.3 Intended use. T
- Page 51 and 52: MIL-STD-1629AWhere:C= “ Criticali
- Page 53 and 54: INSIRUCII ONS: In ● continuing ef
- Page 55 and 56: MIL3TD-1629ANotice 17 June 1983MILI
- Page 57: MIL-STD-1629ACONTENTS (Continued)Fi
- Page 61 and 62: MIL-STD-1629Ad. Functional Failure
- Page 63 and 64: MIL-STD-1629A..2’Ilm.o.,id1-< xQ
- Page 65 and 66: —MIL-STD-1629A50.5 DMEA (Task 104
- Page 67 and 68: MIL-STD-1629ACONTENTS (Continued)Pa
- Page 69 and 70: .-MIL-STD-1629AAPPENDIX AAPPLICATIO
- Page 71 and 72: 20-30Stop LCNMIL-STD-1629AEnter the
- Page 73: NOTICE OFCANCELLATIONNOT MEASUREMEN
<strong>MIL</strong>-<strong>STD</strong>-<strong>1629</strong>A1. SCOPEl.l Sco e. This st<strong>and</strong>ard establishes requirements <strong>and</strong> proceduresfor performing+a ailure mode, effects, <strong>and</strong> criticality analysis (FMECA) tosystematically evaluate <strong>and</strong> document, by Item failure mode analysis, thepotential impact of each functional or hardware fajlure on mission success,personnel <strong>and</strong> system safety, systen performance, maintainability, <strong>and</strong>maintenance requirements. Each potenttal failure is ranked by the severity ofits effect in order that appropriate corrective actions may be taken toeliminate or control the high risk items.1.2This st<strong>and</strong>ard applies to the acquisition of alldesignated DoDY*sys ems <strong>and</strong> equipment. It pr~marjly applies to the programacttvtty phases of demonstration <strong>and</strong> validation <strong>and</strong> full-scale engineeringdevelopment; e.g., design, research <strong>and</strong> development, <strong>and</strong> test <strong>and</strong> evaluation.This st<strong>and</strong>ard also can be used during production <strong>and</strong> deployment to analyze thefinal hardware design or any major modifications. The FMECA tasks containedin this st<strong>and</strong>ard apply to all items of equipment. This st<strong>and</strong>ard does notapply to software. Appendix A contains additional application <strong>and</strong> tailoringguidelines.1.3 Numbering system. The tasks are numbered sequentially as theyare introduced into this st<strong>and</strong>ard with the fjrst task being number 101.1.4 Revisions.1.4.1 St<strong>and</strong>ard. Any general revision of this st<strong>and</strong>ard which resultsin a revision of sections 1, 2, 3, or 4 will be indicated by revision letterafter this st<strong>and</strong>ard number, together with date of revision.1.4.2 Tasks. Any revisions of FMECA tasks are indicated by a letterfollowing the ~ For example, for task 101, the first revision is 101A,the second revision is 101B. Mhen the basic document is revised, thoserequirements not affected by change retain their existing date.1.5referenced by2. REFERENCED DOCUMENTSMethod of reference. The tasks contained herein shall bespecifying:a. This st<strong>and</strong>ard number.b. Task number(s).c. Other data as called for in individual task.2.1 Issues of documents. The following documents of the issue heffect on the date of Invitation for bid or request for proposal, arereferenced in this st<strong>and</strong>ard for information <strong>and</strong> guidance.1————.=——.ss? a>~—_—_—._—— .—————._—_—_. ..— -=—->._—. .
Change language