MIL-HDBK-2155 -FAILURE REPORTING ANALYSIS

Downloaded from http://www.everyspec.com m MIL-HDBK-2 155 11 December 1995 NOTE: Mil-SId-2 155(AS) bm been redesignated m n Handbook, nnd is to be used for guidance purposes only. For administrative expediency, the only physicnl change from Mil-Std-2 155(AS) is this cover page. However, this document IS no longer to be cited m n requirement. [1 cited us n requirement, Contractors Interpret mny disregnrd its contents tbe requirement of this document tmd only M guidance. DEPARTMENT OF DEFENSE HANDBOOK FAILURE REPORTING, ANALYSIS AND CORRECTIVE ACTION TAKEN AMSC FSC RELI NIA DISTRIBUTION unlimited. STATEMENT A. Approved for public release; distribution is Naval 08733.everyspec. 2. D. pertinent data which may be of use addressed to: Gmnanding Officer. and Corrective Action System MI L-STD-2155(AS) 1. NJ Standardization Document Improvement at the end of this document or by letter. C. dards Department (Code 93). Benef Iclal comments (recomnendatlons. Lakehurst.com +41L-STD~2155(’AS) DEPARTMENT OF DEFENSE 14ashlngton. 20301 Failure Reporting. by using the self-addressed Proposal (OD Form 1426) appearing Naval Al r Systems for use by aI 1 Depart- addi t!ons. il . Th{s Mf 1 f tary Standard is approved for use by the (lxmnand. Department of the Navy. Analysis.Downloaded from http://www. deletlons) and any in tmproving this document should be Engineering Speciflcatlons and StanAlr Engineering Center. and IS aval I able ments and Agencies of the Department of Defense. analysls IS performed to the extent that the fal lure cause is understood. Corrective action options and flexlbi 1lty are greatest during design evolution when even major design changes can be considered to el Imlnate or significantly reduce susceptibi lity to known fal lure causes. Early implementation of corrective action also has the advantage of provldlng visibility of the Early adequacy of the corrective action in the event more effort is required. and verlf!ed to prevent further recurrence of the failure. implemented. iil . Analysis.com MiL-STO-2 155(AS) FOREHORD I A disciplined and aggressive closed loop Failure Rep&t!ng. and engineering manpower to expend on an anal Ysis Of a Particularly complex fal lure occurrence or the implementation of preferred corrective These 1Iml ts are determined by item priority. potential Inherent in ml lltary systems. The earlier a failure cause IS Identified and posltlve corrective action implemented. and Corrective Action System (FRACAS) is considered an essential element in the early and sustained achievement of the reliability and maintainability equipment. These options and f)extbility become more 1 imi ted and expensive to Implement as a design becomes firm. and associated software. The acquiring activity has the responsibj lity of determining these limits in Iight of accepted norms established in successful programs or even h! gher standards of performance as warranted by a particular program. actions. program urgency. The essence of a closed loop FRACAS is that failures and faults of both hardware and software are formal Iy reported. available technology.everyspec. and engineering Ingenuity. and detai led attention to each failure or fault as it occurs should limit the s{tuation in which prioritization of open investigations causes a backlog which results in a number of correctable deficiencies being left to field service to resolve over the years. It IS recognized that there are pragmatic 1 Imits to the resources In time. and positive corrective actions are identified. money. the scarer both the producer and user real ize the benef Its of reduced fai lure occurrences in the factory and in the field.Downloaded from http://www. These 1 Imits Wi 11 vary from program to program. . . . .. . . . Laboratory analysis . . . requirements .11 3. . . . . . . . . . .2 3. .1 REFERENCED EKKWENTS Issues ofdocuments~ 3. . . . . . . .4 GENERAL REQUIREMENTS Contractor responsibility FRAC. . . . . . . . . . . . . . . . .com MI L-STD-2155(AS) CONTENTS @ Paragraph 1. . . . 2 2 2 2 2 2 2 2 3 3 3 3 3 3 . . . . . . 4. . . . . . . . . .3 4. . . . . . Failure cause. Purpose. . . . . . . .. . . . . . . . . . Failure Review 60ard Failure documentation . . .everyspec. .2 1 . ... : :::::. .5 3. . . . .1 4. . . . . . Corrective action effectivity Failure. . 4 . . . . . Closed IWP faflure reporting Contractor . . . . . . . . .2.. . . . . . Application. . . . . . . . . . . . .12 DEFINITIONS Terms. . . . . . . .. . . .6 3. . . . . . Fault . 1. . . . . . . . . . I Ill . . . . . . . . .10 3. . . . . . . . . other other 2. . . . . . . .2 SCOPE. . . . . .1 3. . 2. .8 3. . . 1 I 1 1 1 . . 3. . Fa{lure symptom. . . . . . .4S planning . . . . . . . . . . . . . . . . . . . . iv . . . . . . . . . Fallu~eanalysis . . . . Acquiringactlvity . . . . . . . . . . . .. . . Failure Review Board. . . . . . . . . .9 3. . . . . . . . . . . . . . . . .. . . . . . . .3 3.1 1. . . .7 3. system . .. . . Relationship to Integration with . . . . activities . .4 3. .2 4. . . . . . . .Downloaded from http://www.1 1 .2. . . . . . . . . . . . . 4. . . . . . . . . . . . . . . . . Paragraph 5. . . . . . . . Results of failure analysis . . . . . . . . . . . . . . . . . 10. . . . . . . . . . . . . . . . . . . . ..1 50. .9 . . . . . .2 50. . . .4 50. . . . . . . . .. . . . . . . .. . . .8 v .com 141L-}TD-2155(AS) CONTENTS (CS3NTINUED).. . 8 8 8 9 9 10 10 . . .4 GENERAL . . . . . . . . . . . . . .8 . . . ..4 ::: OETAILEO RETIREMENTS .. . . . . . . .. . . . . Effect iveness of FFbWW . . . . . . . . . Request of FRKASplan . Tailoring requirements . . . . . . . .:::lj FRACAS data collection . . .~ .-.. .4 .. . .2 50.. . . . .. Oata items . Oat . . . .. . . . Failure analyses . . . . 60. . . . . . . .Downloaded from http://www. . . . . . . . .4 4 4 11111JJ115 . . .. . . . . 7 . . . . . . . . . .2 5. . . . .9 . . . . . . . . Failure verif!catlon Correctiveaction. . . . . lJII1ll. . .2 GENERAL RETIREMENTS . .. Duplication of effort . . . . .. . . . . . . . . . . 60.2 [0. . . . .2. .lllll: Failure report close-out Identification and control APPENDIX APPLICATION Paragraph . . . Scope . . .. . .3 50. . . . . . . . . .8 . . . . .1 5. .. . 50. . .2. .. . .1 50. . . 5 5 A ANO TAILORING GUIOE 10..2. . . .1. . . . .-9 . . . . . . . . . . . ‘. . . . . . 5. .-8 .10 . . . . 40. . . . . .. . . . . .. . . . . . . Failures . Failure analysis . . . .. . . . .4 OETAILREOUIREMENTS . . .. .3 5. . . . . . . . ..1 40. FMEW . . ..3 10.. . . .everyspec.. . . Failure re~rting . .. .2 50. .. . .1 50. . . . Relationship of FRACAS to 20. ..3 50. . . . .8 Importance of FRACAS . 50. . . . . REFERENCEO DOCUMENTS 30.1. . . . . . . . . ... . . . .1 OATA ITEM DESCRIPTIONS (DID) . . ..1. of failed Items . Requirement addition Failuredata. . . . . . . . . .”l . .1 10. DEFINITIONS 40.1. . FRACAS planning and documentation Primary Object ice . .2.. Downloaded from http://www. THIS PAGE INTENTIONALLY v{ LEFT BLANK .com MI L-ST@2155(AS) .everyspec. human engineering. REFERENCED ODUJMENTS The fol lowing 2. qual tty assurance. management. and implement the FRACAS requl rement of MI vide management visibll!ty and control improvement of hardware and associated uti I ization of fai lure and maintenance tive corrective actions to prevent fai reduce the maintenance tasks. The FRACAS effort shall be coordinated and integrated with other program efforts such as reliabi Iity. implementing the FFWAS requirement of MI L-STD-785.everyspec.. and parts. MI L-STO-781. in addition to 1 . Models and Related Terms Item MI L-STO-470 Maintai Systems ODD-STO-480 Configuration Deviations MI L+TD-721 Definitions ability nabi 1 i ty Program Control and Haivers of Terms 1 for .Engineering for Reliability Exchangeabi and I i ty.1 Relationship to other requirements. system safety. test. for a Fai lure Reporting.2. software by timely and disciplined data to generate and implement effeclure recurrence and to simplify or 1.Downloaded from http://www. and processes control . This standard. test. program phases of demonstration and validation and full scale development. This standard applies to acquisitions for the design.1 Issue of documents. is intended to complement the requirements of MIL-STO-47D. 2. maintainabi 1 ity. the issue in effect form a part of this STANOARDS MILITARY MI L-STD-280 Definitions of Item Levels. f abdication.2.com MI L-STD-2155(AS) 1. docurents of for proposal. materials. lshes untform requirements and criteria Corrective ActIon System (FRACAS) to L-STD-785.1 Purpose.2 Integration with other activities. . configuration integrated logi sties support to preclude duplication of effort and to produce integrated cost effective results. SCOPE This standard establ 1. This standard primarily applies to the and associated canputer programs. and operation of military systems. and Maintain- . MI L-STD-1 679. equipment. on the date of invitation for bid or request standard to the extent specified herein. 1 . . FRACAS is Intended to profor reliability and maintainability .2 Application. and MI L-STD-2068. development. Analysis.. Equipment Changes. letter of intent or purchase orders.everyspec. cause made by use of available physical or activates a fai lure assembly techniques. of failure syasptoms. and For the al lotment.7 logical evidence. definitions 3. and publications Wlthf speclf{c acquisition functions activity or as directed by the con- Mean!ng of terms not defined in MI L-STO-280 and MI L-STD-721 activity. project orders.2 Acquiring contractor) which contract or other A5) L&. in which this document may be incorporated by reference. 3. etc. reasoning from examination of data. when not perform one or more of under specified conditions. associ ati On. DEFINITIONS the 3. 2 I or item serial number Into the ttem.6 Failure requi-&ions 3. required by contractors should be obtained from tracting officer.4 Contractor. . Purpose of th~s standard. or activity through with sub. uil 1 be or has been The date Incorporated An event i n which an i tern does within the specified limits A determination Failure analysis.5 requirements document of agreement.1 ~.~gn”Qual if~catlon and Production Exponential Di strlbution System for Software Systems . mechanism.g. comPanY. 3. identified. a 3. 3. on another in accordance contractor.3 Ciosed loop fai lure reportinq system.5 corrective its Corrective action 3. and laboratory analysis resul ts. defective software error. .Downloaded from http://www. or ~ndi vi dual Uhi ch undertakes performance under the terms of a contract.8 Fai lure cause.com i. ) 3. positive corrective actions are. e. to prevent recurrence. analyzed (engineering or laboratory anaiysis). drawings.iIL-STD=215ki( MI L-STD-781 Reliabii:lty tance Tests: HIL-STD-785 Rel iabi 1 ity Program ment and Product Ion #iIL-STD-1679 Meapon MI L-STD-2068 Relatability (Copies of speclflcations. and that the adequacy of implemented corrective actions is verified by test. action effectivity. design weakness. in connection the contracting and Equipment Accep- Tests ha~dbcmks. the term “contractor” also includes Government operated activi ties undertaking performance of a task. Develop- Oeve lopment Development standards. A controlled system assuring that al 1 failures and faults are reported. The circumstance that induces soldering. herein are (government. That activity levies FAA~. The term “contractor” 1s defined as any corporation.. analysis.12 Laboratory destruct I ve and nondestructive tion. sis. then a description of how the existing function wi II be employed to meet acquiring activity requirements shall. Flow diagrams that depict fai led hardware and failure data flow also shall be documented in the plan. and corrective action system shall be used with modification only as necessary to meet. analysis. The FRtS shal I have authority to require Fai lure investigations and analyses by other contractor organizations The acquiring activity and to assure implementation of corrective actions. di ssec- GENERAL REi)UIREt4ENTS A ciosed loop fat lure reporting.$fIL-. .11 detuning. manufacturing. analy4.sT~2l55(As) 3.respcwrstbi 1 i ty and authority to assure that fal lure causes are identified and corrective act~ons are effected. 3. SYIIP tom.com . 4. corrective act ton status.Downloaded from http://www.3 Failure Review Board. a failure mechan}sm us!ng such as x-ray. tractor to act on the FR6 sha 11 be identified i n the FRACAS procedures and the scope or extent of their authority shall be identified.2 FRACAS planning. analysts. and the feedback of corrective actions into design. tractor and his subcontractors. 4.10 the 3. The determination of laboratory. analysis Of fa~lure$. and so forth. requirements specified by the acquiring activity. and corrective action system (FRACAS) stsal 1 be implemented by the conThe system shal 1 be maintained for reporting. appropriate contractor 0r9anf Zatt0nS With the level of . reserves the right to appoint a representative to the FRB as an observer. event.9 A group consisting of representatives from Fai lure Review Board. be provided for acquiring activity review. If the contractor can identify and use an already exi$ting function to perform the FRB functions.everyspec.1 Contractor responsibi Iity. and test process. The contractor’s existing data collection. in performance due to failure maladjustmmt. and to assure The personnel appointed by the conadequate corrective actions are taken. spectrographic analysts. Failures occurring in specified levels of assemblies in tests at subcontractors’ facilities shall be integrated into the contractor’s data CO1 lection system for tracking and incorporation in the fai lure summary and status reports. procedures for the initiation of fai lure reports. The contractor’s procedures for implement i ng FRACAS and for tracking and nmitoring fat lure analysis and corrective action status shal 1 be described in the FRACAS plan. the. techniques or microphotography. or condltlon or occurrence. The FRB shall meet on a regular basis to review fai lure data from a~propriate inspections and tests including subcontractor test failures. FRACAS planning t nvolves the preparation of written 4. J . wfth 3. Any circumstances. Irrctlcates its ex~stence wtrlch A degradation misalignment. and correction of hardware fai lures and software errors that occur in contractually specified levels of assembly during in-plant tests and that occur at installation or reroute test sites. A Fai lure Review Board (FRB) shal 1 be estab1 i shed to review fai lure trends. of associated parts. Failure faf lure ~. 5. The verification of the GFM fai lure shal 1 be documented for notification to the acquiring activity. Reported fal 1ures ‘shal 1 ‘be evaluated or analyzed as appropriate to determine the cause of fai lure. symptoms of failure. The format of the form(s) used to record fai lure and associated data is important only to the extent that i t simpllf ies the task of the data recorder. The fai lure report shall include information that permits identification of the failed Item. FRACAS procedures shal 1 include requirements for documenting the results and conclusions of fai lure invest \ gatlons and analyses. Fai lures and faults that occur during appropriate inspections and tests shall be reported. .Downloaded from http://www. Failure verification is determined either by repeating ‘the fai lure mode on the reported Item or by evidence of fai lure (leakage residue. etc. Failure documentation shall include a uniform reference ident!f Icatlon to provide ccsnplete traceabl llty of al I records and actions taken for each reported fai lure.. ‘ corrective actions taken. mechani sins. and for Coi Iecting and recording corrective maintenance information and times. BIT indication. > application study.3 Fa!lure ver!flcat!on. The fai lure analysis of other than GFM fai lures shal 1 be conducted at the lowest level of hardware or software necessary to identtfy the causes. knowledge of previous fai lures and fai lure analyses. when appl i cable. These records shal 1 be organl zed to perm!t effi c$ent retrl eval for fat lure trendl ng.. Analysis of government furnished material (GFM) failures shall be limited to verifying that the GFM fa!lure was not the result of the contractor’s hardware. .4 Fatlure documentation. 811 software problems ldenti f 1 ed durt ng the i nspectlons and tests shal 1 be reported in accordance with the requirements of MI L-STD-1679. provides for item and data traceabi 1 i ty. mtcroscoptc analysis. failures. 5. and effectiveness of corrective actions.2 Failure analysis. and corrective action monitoring.g. DETAILED RETIREMENTS 5. test.1 Failure reporting. that may be necessary to determine fai lure cause. All reported fai lures shall be verified as actual or an explanation provided for lack of verification. fal lure susmrary and status reports. etc). . . damaged hardware. The investigations and analyses of faflures shall consist of any applicable method (e.fatlure investigations and analySes.everyspec. and potential effects of the fai lure and to serve as a basis for decisions on the corrective action to be implemented. Records shal 1 be maintained for al 1 rgported 4. assignable fat lure causes. or procedures. Al 1 fat 1ure reports and software problem reports shal 1 be verif 1ed for accuracy and correctness and subm{ tted on standard forms. and provides the information required by the acquiring activity as lt becomes available 5. softw$re. x-ray analyses. and item operating time at time of failure. dissection. built-in-test (BJT) Indications. Procedures for initiating fai’iure reports shal 1 include requirements for verifyfng fal lures using BIT. test cond{tlons.com MI L-STD-:2155(AS) . 5 . a corrective action shal 1 be developed. distributed. The rationale to support no corrective action shal 1 be documented and approved by responsible authority.6 Identification and control of failed items. or mishandled to the extent of obliterating facts which might be pertinent to an analysis.Downloaded from http://www.everyspec.com MI L-STW2155(AS) Hhen th”e” cause of a fal lure has been determined. Unless otherwise specified. anal YseS. All open reports. documented.5 Fai lure report close-out. and implemented to el lml nate or reduce the recurrence of the fat lure. Fai led items shal I be control led pending authorized disposition after completion of fai lure analyses. Fai led items shal 1 not be opened. and corrective be reviewed to assure timely failure report close-outs. 5. Each reported fai lure shall be analyzed and corrective action taken in accordance with the requirements of this standard in a timely manner so as to obtain lnxnediate benefits of the corrective action and to minimize an unmanageable backlog of open failures from occuraction suspense dates shal 1 ring. 5. 5. Corrective action implementation shall be approved by responsible contractor personnel (and acquiring activity as required).4 Corrective actibn. change control procedures shal 1 be i n accordance with OCIO-STO-480. A fai lure report shal 1 be considered closed-out upon completion of corrective action implementation and verification or rationale In those instances where corrective action was not implemented. All failed items shall be conspicuously marked or tagged and control led to assure disposition per contract requirements. Downloaded from http://www.com I I THIS PAGE INTENTIONALLY LEFT BL4NK .everyspec. *. . contractual structure. fal lure . 10. An FMECA benefits the experience of actual failures and the!r consequences. ‘“” analysfs. test. . Tailoring of requirements may take the form of deletion. safety. 7 . -‘: 10..everyspec. and 5 to adapt the requirements to specific i tern characterssties. The depth “and detai 1 of” the FRACAS effort WI 11 be defined in appropriate contractual and other program documentation.com I t41~-STO-2155(AS) I APPENDIX .Downloaded from http://www.4 Relationship of FRACAS to FMECA. 10. and corrective action syst~ (F~~S). An FMECA is an analytical ly derived identif i cation of the conceivable hardware fai lure modes of an i tern and the potential adverse effects of those modes on the system and misston. The FMECA’s primary purpose is to inf Iuence the system and i tern design to either eliminate or minimize the occurrences of a hardware failure The f~ms represents the “real UOrl d“ or the consequences of the fai lure. there 1s a synergistic effect when the two efforts are coupled. and other contractual means. addition. maintainabi 1 i ty. The tailored FIWAS requirements are specified in the contractual provisions to include Input to the statement of work. Significant differences between the two worlds are cause for a reassessment of the item design and the differing fai iure criteria that separates the FFWXS and FUECA. or acquisition phase. APPLICATION 10.1 acquiring reporting. Each provi slon of this standard should be reviewed to determine the extent of appl tcabi i ity. and integrated logi sties support. acquiring activity options. . FRACAS by providing a source of comprehensive fai lure effect and fai lure severity information for the assessment of actual hardware fai lure Actual failure experience reported and analyzed in FRACAS occurrences. Al th&gh the respective FRACAS and Fai lure Mode Effects and Critical ity Anaiysts (FMECA) effort are designed and capable of being performed Independent 1y of each other. 4. A AND TAILORIMG GUIDE GENERAL 10. Thls appendix provl des notes for the guidance of the activl ty in generating the contractual requirements for. worid” experience as reported and There should be agreement between the “real assessed in the FRACAS and the “analytical world” as documented in an FMECA.2 Tailoring re@rements. Identification of the coincident generation of FRACAS tasks or use of such tasks by the reliability program and other disciplinary areas is required in the rel iabi 1i ty program plan or other appropriate program documentation to avoid dupl icatlon of effort by the acquiring activity and the contractor.3 Dupl lcatton of effort.~‘. A review of the contractual requirements Is necessary to avoid duplication of effort between the reliability program and other program efforts such as qual ity. provides a means of verifying the completeness and accuracy of the FMECA. or alteration to the statements In Sections 3. contract data requ{ rements 1 Ist (CORL). Each 00 ‘FOTrn. As the design matures. the ‘reg. The plan submitted .ui@ent. bihen an FRB is required by the acquiring should be asked to identify the personnel appointed of their authori ty.2... ~0. the .t 11 can be identified.Fi@CAS i.com I %f%w’ . or data.implementatiop of F.foc review should de<crlbe the flow of fai led hardware and failure data thro:~g~~t}the contractor ~s organ.. and the feedback of corrective actions into the design. for a F~CAS norcna 11 y WI 11 eq. .1:3 “Requirement addition. wi 11 be control led.ful 1 scale development (FSD) . ” they are del tverable 1 terns. REFER$~E~:~E~~$~ @# $~o~. If a FRACAS plan is requested In the.of .“ This early implementation . but the opticms become limited and implementation is rore difficult.ctt Ye action “option: and flexibtl ity are ~ qreatest . f ai \ ure analyses.fmportarici . .RACAS requirements Wi 11 involve If any of these some “form ‘of. document.everyspec. the contractor to act on the FRB and to . and test process. Each separate data item -!dentified’for del f very ❑ust be included on a 00 Form 1423 yhich must be.Downloaded from http://www. directives for spec.20.i zat Ion. 50.ii.c~b I’e)” ..contractor should be asl(ed to describe how he plans to ispiement ‘the FRAC4S. “’.. I “. 40. RFP.to valida~lon-or. corrective actions st.2 Request of FRACAS plan.50.40 . systems. ‘The primary objective of a closed-loop FRACAS 5. .~tr%s’t. other closely related functions or the FRB that should be closely coordinated to assure is avoided. 1 Pri&ry objective. .uest for proposal (RFP) and contract. FRACAS ~lanning I I - >. ‘ 50.authorf zed Oata Item Description (OID) and must incftide a Spec’ffiic ‘contract reference that specifies Refer to governing and author! zes. .1. .implement ‘corrective actions. indicate the scope or extent 8 L a requirement for a Failure the reporting. the work to be done for each data 1 tern. contractor prepared plan. are to be rgcetved by the acquiring acttv~ty.0..Oata i tens.ilETAIL ”iEoiJIRE14ENTS ‘ 50~1 .jA9~~1 30: DEF~NITIONS.ific information on how to ccatplete the 00 Form 1423. He should be asked ‘to identify and discuss the procedures that wil 1 be : used to control f ai lure report WI! tlation. the easier it 1s to. however. included as a“’part of the req. “The eatl ter fat lure’ causes are tdenttf ied.1 423 entry aui&t refer to an . form.. “and “documentation.: . ject . ~ENERAL-’REQUIRENENT5 @~~: A~~l !. .The . .. and ‘associated software subapply’ to#Ie deyelop~nt et.of a“ FRACA5 1s i~rtant because corre. The timely di ssemlnatlon of accurate fat lure information is necessary so remedial actions nay be taken promptly to prevent the recurrence of the fal lure or fault. The addition of Revieu Board (FRB) wi 11 provide added assurance that and corrective actions taken ‘on jdentif ied fai lures may be. . . is to document fal 1ures and faults and to disseminate the data. There efforts that are similar to that duplication of effort activity.duricsg des{gn evolution. manufacturing. analysis. should be asked to define the scope and content of hls fai 1ure data system. .2. The contractor’s procedure for failure report i ni tia. ~. The information on who discovered the fai it failed.2. system ts the fal l’ure sunsnary and status report. The level of analysis always should be sufficient to provide an understanding of the cause of fat lure so that logically derived . A failure analysis plan then should be developed to describe the steps the analysis wil 1 take and to preclude pre. what fai led.“coir ~he “ w kc or-and ‘< The fal lure data system . l%d’ contractor.3 “Failure analysis.:h~l~ .. manageable aggregates for purposeful ~~aludtio ‘1”’ %y b6 !“-h“ ti(e ..4 Fatlure data.everyspec.1.co~~~ct. . acqu{ring actfvlty.ls. the contractor should have a method for accounting for fat 1ure reports and should audit the completed forms periodical ly to verify that failure reports are being submitted prcmptl y. One of the first steps tn any fai lure analysis is the review of the fat lure information by cognizant personnel.u! 1 ~. ““” 50.mature disposal of f ai led i terns prior to being subjected to required analyses. I I 1 I I Failure data. pertinent i nformat ion about the fai lure should be docussanted on a f al 1ure report form. Failure analysis is”the determination”of tk c“ause of a fai lure. functi@:.2 FRACAS data collection. us Fpl on y. here It “fa! led. store.Downloaded from http://www. and retrieve faflure Information and to p?ovide” the’ rsean’s-for “’ “”” displaying the data tn a meaningful form. 50. In addi t ion. 9 I . Each failure should be verified ●nd then ana!wed to the extent necessary to identify the cause of fai lure and any contributing factors.be designed t~.tion should identify and describe the data that should be recorded for both hardware fai lures and software errors to assure that fai lures are adequately described and that the proper harduare or software has been reported. Thi s:report .2 Failures. system or equipment fat lures typically occur during tests or operation by the contractor or the acquiring #(hen a fai lure occurs. ” Essential surrounding a failufe” or fault to fai lure documentation must proylde lure.provtde info~tion about the fai lure of Ilke Items or slmflar. The’ fa) 1ure analysts can range from a simple Investigation of the” circumstances surrounding the failure to a sophisticated laboratory analysis of the failed parts.? failure data A useful output management and engineering personnel. input data in reports documenting fai inputs should document all conditions faci I itate cause determination.1 Effectiveness of FRAC4S. when 11 be prevented.2.is ‘accurate.uislch can be used. During development.: and to” lndi cate how it will be maintained.. and how future faflures wi A FRACAS will be effecttve only if the lures and faults . 50. to provide Indications of failure treftds:and “to evaluate’ the tiiid for and the extent of contemplated corrective actions.ti. 50. corrective acrlons can be aevelopea.com MIL+TD>2155(AS) (IRPENL)IX’”A 1 I I I I 1 . The outputs of a f ai lure data system should be tailored to prov!de sumnarles and spectal’”reports ”for “Iioth of. .~n as mb ed in 50. the fai led item should be identified and al 1 activity. After a corrective action is implemented.2. 50. Hhen thfs standard is uqed in an acquisition that incorporates CDRL.1 DI-R-21598 DI-R-2 178 Reciul rement Development Susmsary Analysis. contract or purchase standard are ci ted in the fol lowing paragraphs. functions should be obtained from the by the Contracting Officer. Vol . {t shoulId lke a’onjtored to assure that the corrective action has removed the fai lure causes and has not introduced new problems. Copies of EsIDs required by the contractors in connection with specific acquisition.9 (n) (2) are invoked and DD Form 1423 is not used. and delivered in accordance with the approve~ CORL” ~ncorporat~d into “the contract. AMDSL. COriectlve action to alleviate a problem may range f rcm new controls implemented ! o manufacturing or test to a change in design or changing a part to one better sui ted to operational The generated corrq$i ve +c:t!on should be documented i n detai I requ~rements.AS Project No.Downloaded from http://www. and System Plan and Production Fai lure Report Computer Software Trouble Report DIDs reiated to this standard wil 1 be apprcwed and i isted as such in EK)O 5000.4 60. I Q@. DATA ITEM DESCRIPTIONS (DIO) 60. Corrective Action ReDOrt. the data requirements identified below shal I be develooed as sDecified bv an aooroved DID. Hhen the provisions of DAR 7-104. Fail ure 5. the contractor shal 1 deliver the data specified below in accordance with the Del iverable data sourced to this order requirements.2 01-R-21597 4. DD Form 1664. 11. RELI-N035 10 . so that i t can be impi emented and verif6ed~”Z~ the ProPer level. Naval Pub] ications and Forms Center. or as directed Preparing activity: Navy . should be fed-back to cognizant petsoiinel so they can decide on an appropriate course of action to al leviate the problem. 19L.everyspec. Paragraph Applicable 4. DD Form 1423.4 DI-R-21599 DID Data Fai lure Reporting.com -i41kSTD~2 155(AS) APPENDIX A I I The results of fal lure analysts Results of failure analysis. .ATION & Tv- ❑ Of OmOANIZAT#ON f--J ADORE= (s-t. OATE I DD &“::. 1 NAME OF SUSUllTINO 0ROAN17. City.— MA. - 00. Sti.com .” f-J ●ROWLEM (U VzImO” R--L.— Wsn Ormn mmdfr. & -. . WORK (1-=IM* CA) . a? C-J ❑ .NG ADD.S1-. -m. NAME OF SUOMITTE R (La. .1- 1.0u9 EOITIOId IS OCSOI. .ETE.iond b..everyspec. L. O* SU8U1SS1ON [YYMMDD1 Arm . MA”w. d WO.. Ml. . 1426 PR~v. Stiw..- .i .Downloaded from http://www.: 1 nEblARcS .: TELEPHONE NWSER AmEAS N“nml. ESS . IxY.. Mm.-dh#: ...81w — W. ZIP Cdl - Oullonti t.cru”. 12s03 THE Commander Naval Air Systems ~nd Washington.. NAVY 111111 No POSTME w-m” w mAILED an uN#TeO OFFICIAL U61NES *EWAI. THE (AIR 51122) C. .”ST CL- P6RM. DC 20361 WASMING1ON OEMRTMENTOF 0.com I (Fold daaJ *b Mu) 1( 0EPARThlEN7 OF lHE .everyspec.T PAID “o.TV Porn PRIVATE USE UOO I BUSINESS REPLY MAIL t 1WmAGE WILL m w 1 F. . NAVY Tm STATES .Downloaded from http://www. . Documents Similar To MIL-HDBK-2155 -FAILURE REPORTING ANALYSIS Skip carouselcarousel previouscarousel nextRCMpr1- individual sub-category research areasvvtemplateAn Examination of Factors Affecting Human ReliabilityRCMA_04.10.08BDV01I02P0137Chapter 8 FMEAConcepts and Techniques of Value Analysis to Effectively Control Cost00 1 Coveraudit of a specific ESREL 2011.pdfEmployee Referral - 31st Dec6 Probalistic Introduction90-Day Performance ReviewDesignFuzzy TOPSIS Approach for FMECA (Bozza)Whipstock Brochure from ITSA_Capital_Investment_Review_ProcessTLP621_datasheet_en_20071001Enhancing Seal ReliabilityMaintenance ManagementIntroduce to Software Validation & TestingDesign of Goods and ServicesEquipment Reliability SondiniProtocol for Validation of FSMS_FinalVersionValidation Part 11 Annex11 ComplianceManual de Instalacion FMR20RAMS MANAGEMENT OF RAILWAY SYSTEMSBoiler PlanPMmanual3Electric Motor Energy and Reliability Analysis Using the US112618-5229-M.PharmMore From B Srinivasa RaoSkip carouselcarousel previouscarousel nextWhy Do We Need Work Orders_ We Don’t !! _ BMA IncSpline Program Ver 1.1Cause & Effect Diagram, 3 Leg Why Why FormGage Repeatability and Reproducibility StudyPre Control_Process Control ChartBasic Problem Solving TemplateThe Power Of Six Sigma The Power of Six SigmaIndia Tax Calculator 2009Pare ToList of Quality RecordsTQM MapElectronic_Diary_2010CLIR Points StatusTQM MapFooter MenuBack To TopAboutAbout ScribdPressOur blogJoin our team!Contact UsJoin todayInvite FriendsGiftsLegalTermsPrivacyCopyrightSupportHelp / FAQAccessibilityPurchase helpAdChoicesPublishersSocial MediaCopyright © 2018 Scribd Inc. .Browse Books.Site Directory.Site Language: English中文EspañolالعربيةPortuguês日本語DeutschFrançaisTurkceРусский языкTiếng việtJęzyk polskiBahasa indonesiaYou're Reading a Free PreviewDownloadClose DialogAre you sure?This action might not be possible to undo. Are you sure you want to continue?CANCELOK