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

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

barringer1.com
from barringer1.com More from this publisher
13.07.2015 Views

MIL-STD-1629ACONTENTS(Continued)FigureTasLJ03103.1Task 104104.1APPENDIX A.Paragraph10.10.110.210.320.30040.40.140.250.50.150.1.150.1.250.1.350.250.350.450.550.6PageExample of FMECA-maintainability informationworksheet format . . . . . . b . . ● . ● ● ● ● ● ●103-3Example of damage mode and effects analysis fo~at ~ 104-5APPENDIXAPPLICATION AND TAILORING GUIDE . . . . . . . . . . A-1GENERAL . . . . ● . . . . . . . ● ● = = ● - ● ● “ ● ‘-1Scope .*.** ● **** ● **** A-1Tailoring=r;q;i;~e;t~ . . . . . . . . . . . . . . . A-1Duplication of effort . . . . ● . ● . . . s ● ● “ ● A-iREFERENCED DOCUMENTS (not applicable) . . . . . . . A-1DEFINITIONS (not applicable) . . . . . . . . ● ● ● ● A-lCENTRAL REQUIREMENTS. . . . . . . . . ..*oo ● A-lOrdering data . . . . . . . . c . . ● ● ● ● ● ● ● ● A-lData item descriptions (DID) . . . . . . . . . ● . ● A-2APP1,ICATION CRITERIA . . . . . . . . . . . ● ● ● ● ● A-2General considerations . . . . . . . ● ● ● ● ● c ● ● A-2Level of detail . . . . . . . . . . ● s c ● ● ● ● s A-2Timing. . . . . . . . . . . . . ● = ● ● ● ● ● ● ● “ A-2Intended use. . . . ● . ● ● . . ● . ● ● “ ● ● “ ● c A-3FMEA(tasklOl) . . . . . . . ● . . ● . ● ● ● ● ● ● A-3CA(task 102) . . . . . . . . . . . . . ● ● ● “ “O A-3FMECA-maintainability informa~ion (task 103) . . . . A-4DMEA (task 104) ● ..0 ● *** ● *** ● * A-4Criticality numbe; iCj)”c~lculation examPle Q ● ● ● ‘-4-—vi

MI1.-STD-1629A1. SCOPEThis standard establishes requirements and proceduresfor performing a failure mode, effects, and criticality analysis (FMECA)tO systematically evaluate and document, by item failure mode analysis,the potential impact of each functional or hardware failure on missionsuccess, personnel and system safety, system performance, maintainability,and maintenance requirements. Each potential failure is ranked by theseverity of its effect in order that appropriate corrective actions maybe taken to eliminate or control the high risk items.1.1SssE”1.2 Application. This standard applies to the acquisition ofall designated DoD systems and equipment. It primarily applies to theprogram ac~ivity phases of demonstration and validation and full-scaleengineering development; e.g. , design, research and development, andtest and evaluation. This standard also can be used during productionand deployment to analyze the final hardware design or any major modifications.The FMECA tasks contained in this standard apply to all items ofequipment. This standard does no~ apply to software. Appendix A containsadditional application and tailoring guidelines.1.3 Numbering system. The tasks are numbered sequentially asthey are introduced into tt-iistandard with the first task being number101.J;4 Revisions,1.4.1 Standard. Any general revision of this standard whichresults in a revision of sections 1, 2, 3, or 4 will be indicated byrevision letter after this standard number, together with date of revision.1.4s2 Tasks. Any revisions of FMECA tasks are indicated by aletter following the task. For example, for task 101, the first revisionis 101A, the second revision is 101B. When the basic document isrevised, those requirements not affected by change retain tl~eir existingdate.1.5 Method of reference. The tasks contained herein shall bereferenced by specifying:a. This standard number.b, Task nurriber(s).co Other data as called for in individual task.2. REFERENCED DOCUMENTS2.1 Issues of documents. The following documents of theissue in effect—on the date cf invitation for bid or request for proposal,are referenced in this standard for il]form;+tjnrland ~uict,ance.*

MI1.-<strong>STD</strong>-<strong>1629</strong>A1. SCOPEThis st<strong>and</strong>ard establishes requirements <strong>and</strong> proceduresfor performing a failure mode, effects, <strong>and</strong> criticality analysis (FMECA)tO systematically evaluate <strong>and</strong> document, by item failure mode analysis,the potential impact of each functional or hardware failure on missionsuccess, personnel <strong>and</strong> system safety, system performance, maintainability,<strong>and</strong> maintenance requirements. Each potential failure is ranked by theseverity of its effect in order that appropriate corrective actions maybe taken to eliminate or control the high risk items.1.1SssE”1.2 Application. This st<strong>and</strong>ard applies to the acquisition ofall designated DoD systems <strong>and</strong> equipment. It primarily applies to theprogram ac~ivity phases of demonstration <strong>and</strong> validation <strong>and</strong> full-scaleengineering development; 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 the final hardware design or any major modifications.The FMECA tasks contained in this st<strong>and</strong>ard apply to all items ofequipment. This st<strong>and</strong>ard does no~ apply to software. Appendix A containsadditional application <strong>and</strong> tailoring guidelines.1.3 Numbering system. The tasks are numbered sequentially asthey are introduced into tt-iist<strong>and</strong>ard with the first task being number101.J;4 Revisions,1.4.1 St<strong>and</strong>ard. Any general revision of this st<strong>and</strong>ard whichresults in a revision of sections 1, 2, 3, or 4 will be indicated byrevision letter after this st<strong>and</strong>ard number, together with date of revision.1.4s2 Tasks. Any revisions of FMECA tasks are indicated by aletter following the task. For example, for task 101, the first revisionis 101A, the second revision is 101B. When the basic document isrevised, those requirements not affected by change retain tl~eir existingdate.1.5 Method of reference. The tasks contained herein shall bereferenced by specifying:a. This st<strong>and</strong>ard number.b, Task nurriber(s).co Other data as called for in individual task.2. REFERENCED DOCUMENTS2.1 Issues of documents. The following documents of theissue in effect—on the date cf invitation for bid or request for proposal,are referenced in this st<strong>and</strong>ard for il]form;+tjnrl<strong>and</strong> ~uict,ance.*

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!