MIL-STD-1629-RevA - Barringer and Associates, Inc.

More documents

Recommendations

Info

MIL-STD-1629ATASK 103FMECA-MAKNTH??IIBILITY INFORMATION1. Purpose. l%e purpose of the FMECA+naintainability informationanalysis is to provide ~rly criteria for maintenance planninganalysis (MPA), logistics support analysis (LSA), test planning,inspection and checkout requirements, and to identify maintainabilitydesign features requiring corrective action.1.1 Application. The FMECA-maintainability informationanalysis, Task 103, supplements the FMEA, Task 101, and shall not beimposed without imposition of Task 101.‘1.2 ‘-. Planning for the FMECA-maintainability informationanalysis includes the contractor’s procedures for assuring thecoincident use of this analysis when logistic support analysis in accordancewith MIL-ST&1388 and the maintenance planning analysis inaccordance with MIL-sTD-2080 are required by contract.2.-Mcurnents referenced in Task 103:STANDARDSMilitaryMIL-STD-2080 Maintenance Plan Analysis for Aircraft andGround Support Equipments3. FMECA-xuaintainability information worksheet. Documentationof the maintainability information is accomplished by completing theapproved FMECA-maintainability information worksheet. An example of anFM’ECA-maintainability workshee~ format is shown in Figure 103.1.Completed worksheets shall be included in Che FMECA report, GeneralRequirements, 4.5, following the FMEA worksh+t for the same indenturelevel. The following information is the same as that given in the FMEAworksheet and shall be transferred to the FMECA-maintainability informationworksheet:a. Identification numberb. Item/functional identificationc. Functiond. Failure modes and cduscsc. Failure effects (Jocal, next higher level, end)f. Severity classificaLioIlTASK 103
MIL-STD-1629A3*1 Failure predictability. Enter information on knownincipient failure indicators (e.g., operational performance variations)which are peculiar to the item failure trends and permit predictingfailures in advance. When a failure is predictable in advance, describethe data that must be collected, how it will be used to predict failure,and identify any tests or inspections that may be accomplished to detectevidence of conditions which could cause the failure mode.. .3.2 Failure detection means. Identify how each failure modewill be detected by the organizational level maintenance technician andto what indenture level they will be localized. Describe the method bywhich ambiguities are resolved when more than one failure mode causesthe same failure indication. Describe any monitoring or warning devicethat will provide an indication of impending failure and any plannedtests or inspections which could detect occurrence of the failure mode.Identify to what indenture level failures can be isolated by the use ofbuilt-in-test features and indicate when ancillary test equipment willbe required for fault isolation.3.3 Basic maintenance actions. Describe the basic actionswhich, in the analyst’s judgement, must be taken by the maintenancetechnician to correct the failure. Identify the special design provisionsfor modular replacement and tileprobable adjustmcn~ and calibril&iunrequirements following repair.3.4 Remarks. Any pertinent remarks pertaining to and clarifyln~any other columns shall be noted. Notes regarding recommendations fordesign improvement shall be recorded and further amplified in the FMECAreport, General Requirements, 4.5.4. Ordering data. The following details shall be specifiedin the appropriate contractual documents:a. Task 101 (see 1.1 of Task 103).h. Logistic support analysis (See 1.2 of Task 103).c. Maintenance planning analysis (see 1.2 of Task 103).TASK 103—24 November 1980
Page 1 and 2: MIL-STD-1629A24 NOVEMBER 1980SUPERS
Page 3 and 4: MT7,-STW 1629AFOREWORDIThe~failure
Page 5 and 6: ----MIL-STD-16Z9ACONTENTS(Continued
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: MI I.-sTI)-I629AINCREASINGCRITICALI
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 and 58: MIL-STD-1629ACONTENTS (Continued)Fi
Page 59 and 60: MIL-STD-1629ASPECIFICATIONSMilitary
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

MIL-STD-1629-RevA - Barringer and Associates, Inc.

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?