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

More documents

Recommendations

Info

.M17,-STW1629Athe analysis results to pro~ide design guidance. Worksheet formats,ground rules, analysis assumptions, identification of the lowest indenturelevel of analysis, coding system description, failure definitions, andidentification of coincident use of the FMECA by the contractor’s reliabilityorganization and other organizational elements shall be considered inthe F’KECAplanning.4.3.1 Worksheet formats. The contractor’s formats, whichorganize and document the FMECA and other analysis methods containedherein, shall include the information shown in the example formats inFigures 101.3, 102.1, 103.1 and 104.1. The initial indenture level ofanalysis shall be identified (item name) on each worksheet, and eachsuccessive indenture level shall be documented on a separate worksheetor group of worksheets.4.3.2 Ground rules and assumptions. The contractor shalldevelop ground rules and analysis assumptions. The ground rules shallidentify the FMECA approach (e.g. , hardware, functional or combination),the lowest indenture level to be analyzed, and include general statementsof what constitutes a failure of the item in terms of performance criteriaand allowable limits. Every effort should be made to identify andrecord all ground rules and analysis assumptions prior to initiation ofthe analysis; however, ground rules and analysis assumptions may beadded for any item if requirements change. Additional ground rules andanalysis assumptions shall be documented and separately identified forinclusion in the FMECA report.4.3.3 Indenture level. The indenture level applies to thesystem hardware or functional level at which failures are postulated.Unless otherwise specified, the contractor shall establish the lowestindenture level of analysis using the following guidelines:a. The lowest level specified in the LSA candidate listto assure complete inputs for each LSA candidate.b. The lowest indenture level at which items are assigneda catastrophic (Category I) or critical (CategoryII) severity classification category (see 4.4.3).c. The specified or intended maintenance and repairlevel for items assigned a marginal (Category ITT)or minor (Categorv IL’)severity classificationcategory (see 4.4.3).4.3.4 Coding system. For consistent identification of systemfunctions and equipment and for tracking failure modes, the contractorshall adhere to a coding system based upon the hardware breakdown structure,work unit code numbering system of MIL-STD-780, or other similar uniformnumbering system. The coding system shall be consistent with the reliabilityand functional block diagram numbering system to provide complete visibilityof each faililr[;mode arid j1% rc,l,tt jI_II-IL.jI iI,f+(~t.~,f~ s:;~(l-,pl,.(i
.MT1.-ST~-l629A4.3.5 Failure definition. The contractor shall develop generalstatements of what congtitute8 a failure of the item in terms of performanceparameters and allowable limits for each specified output. The contractor’sgeneral statements shall not conflict with any failure definitionsspecified by the procuring activity.4.3.6 Coordination of effort. Consideration shall be given tothe requirements to perform and use the FMECA in support of a reliabilityprogram in accordance with MIL-STD-785, maintainability program inaccordance with MIL-STD-470, safety program in accordance with MIL-STD-882, survivability and vulnerability program in accordance with MIL-STD-2072, logistics support analysis in accordance with MIL-STD-1388, maintenanceplan analysis (MPA) in accordance with MIL-STD-2080, fault diagnos~sanalysis in general accordance with MIL-sTD-1S91, and other contractualprovisions. The contractor shall identify the program organizationresponsible for performing the F’MECA and assure that the FMECA resultswill be used by other organizational elements to preclude duplication ofeffort.4.4 General procedure. The FMECA shall be performed inaccordance with the requirements specified herein to systematicallyexamine the system to the lowest indenture level specified by the procuringactivity. The analysis shall identify potential failure modes. Whensystem definitions and functional descriptions are not available to thespecified indenture level, the initial analysis shall be perfomed tothe lowest possible indenture level to provide optimum results, Whensystem definitions and functional definitions are complete, the analySiSshall be extended to the specified indenture level.4.4.1 Contributing information. System definition requires areview of all descriptive info~ation available on the system to beanalyzed. The following is representative of the information and datarequired for system definition and analysis.4.4.1.1 Technical specifications and development plans . Technicalspecifications and development plans generally describe wl]at constitutesand contributes to the various types of system failure. These willstate the system objectives and specify the design and test requirementsfor operation, reliability, and maintainability. Detailed informationin the plans will provide operational and functional block diagramsshowing the gross functions the system must perform for successfuloperation. Time diagrams and charts used to describe system functionalsequence will aid in dctcmining the time-stress as well as feasibilityof various means of failure detection ~nd correction in the operdLingsystem. Acceptable performance limits under specified operating andenvironmental conditions will be given for the system and equipments.Information for developing mission and environmental profiles willdescribe the mission performance requirements in terms of functionsdescribing the tasks to be performed and related to the anticipatedenvironments for each mission phase and operating mode. Function-timerelationships from whicl] the time-stress !t’1.{ti(lns}lip of the environmentalb.
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: !’11 L-!;’J’l)- 1629A3. 1.17.
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 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
show all

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

Create successful ePaper yourself

Delete template?

Save as template?