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-1629Aoperation for performing the specific function. Mission functions andoperational modes shall be identified starting at the highest systemlevel and progressing to the lowest indenture level to be analyzed.When more than one method of performing a particular function is available,the alternative operational modes shall be identified. All multiplefunctions utilizing different equipment or groups of equipment alsoshall be identified. The functions and outputs for each indenture levelalso may be presented in a function-output list or in narrative form.4.1.2 Environmental profiles. The environmental profiles whichpresent the anticipated environmental conditions for each mission andmission phase shall be defined. When a system will be utilized in morethan one environment each different environmental profile shall bedescribed. The intended use, through time, of the system and its equipmentsshall be developed from the mission time statements for each environmentalprofile. The use time-environment phasing is used in determining thetime-stress relationships and the feasibility of failure detectionmethods and compensating provisions in the operating system.4.1.3 Mission time. A quantitative statement of system functiontimerequirements shall be developed and included in the system definition.Function-time requirements shall be developed for items which operate indifferent operational modes during different mission phases and foritems which function only if required.4.1.4 Block diagrams. Block diagrams which illustrate theoperation, interrelationships, and interdependencies of functionalentities of a system shall be constructed to provide the ability fortracing failure mode effects through all levels of indenture. Bothfunctional and reliability block diagrams are required to show thefunctional flow sequence and the series dependence or independence offunctions and operations. Block diagrams may be constructed in conjunctic]nwith or after defining the system and shall present the system as abreakdown of its major functions. More than one block diagram willusually be required to display alternative modes of operation, dependingupon the definitiolt established for the system. All inputs and outputsof the item as a whole shall be shown on the diagram and clearly labeled.Each block shall be designated by a consistent and logical item numberthat reflects the functional system breakdown order. A uniform numberingsystem developed in functional system breakdown order is required toprovide traceability and tracking throu~h all Ieveh of indenture. ??lL-STD-780 provides an example of a uniform numbering system for aeronauticalequipment that can be used as a guide in the development of a consistentand logical identification code for block diagrams. Figures 101.1 and101.2 depict examples of functional anu reliability block diagrams.4.1.4.1 Functional block diagrams, A functional block diagramillustrates tileoperation and interrelationships between functionalentities of a system as defined in engineering data and schematics. A.TASK10I2~1Yevcm!>l?r!9(90101-3—————- -E _x==- S=-.-——=.-G.=.-—_.—- =—--—.—-. T—-... ...-.—e.——— ——————

MI J,-STD-16?9Afunctional block diagram will provide a functional flow sequence for thesystem and each indenture level of analysis and present hardware indentureand can be used for both hardware and functional method FMEA’s. MIL-M-24100 procedures and techniques for dcvcl.opins major functiol~ dia~rnmsmay be used for guidance in developing functional block diagrams.4.1.4.2 Reliability block diagrams. A reliability block diagramdefines the series dependence or independence of all functions of asystem or functional group for each life-cycle event. The reliabilityblock diagram will provide identification of function interdependenciesfor the system and can be used for a functional method FMEA. MIL-STD-756 procedures illustrate a me~hud which may be used to develop reliabilityblock diagrams.5. FMEA worksheet. The documentation of the FMEA is thenext step and is accomplished by completing the columns of the approvedFMEA worksheet. An example of an FMEA worksheet format is shown inFigure 101.3.5.1 Identification number. A serial number or other referencedesignation identification number= assigned for traceability purposesend er.!-eredOn :h~’l~J~>~ksbf>[J~ . ~,~!.!i ff,!-,-} idOT)t. ifjcal jI)7 4-mje in itc’(.’.(lrddrlrewith Ceneral Requirements, 4.3.4, shall bs used to provide consistentidentification of system functions an equipment and provide completevisibility of each failure mode and its relationship to the systemfunction identified in the applicable block diagram.5.2 Item/functional identification. The name or nomenclatureof the item or system function being analyzed for failure mode andeffects is listed. Scl~ematic dia~ram symbols or drawing numbers shallbe used to properly identify the i~enlor function.5.3 Function. A concise statement of the fui~ction performedby the hardware item shall be listed. This shall include both theinherent function of t]~epart and its relationship to interfacing items..-●5.4 Failure modes and causes. All predictable failure modesfor each indenture level analyzed shall be identified and described.Potential failure modes si}a~ll~etic~t’rl::il]ed b~ ux~mination of itemc)u~puts and functional outputs ider)~illed in ,:pplicable block cli~~ramsand schematics. Failure modes of tileindiy~idu~l item function shall hepostulated 011 ~~~eb~sis ~[ L]I~StdtuU ~uquiru~iunts in t]leSyStem deflnitiOllnarrative and the failure definitions incl~ldcd in the ground ru]es. Tl]emost probable causes associated with tilepostulated failure mode shallbe identified and described. Sinct” :] f“;+i lure mode may have more thanLJ!lecause, all prob;lbl~>indt’pCIIIdc’n: c;{u‘

<strong>MIL</strong>-<strong>STD</strong>-<strong>1629</strong>Aoperation for performing the specific function. Mission functions <strong>and</strong>operational modes shall be identified starting at the highest systemlevel <strong>and</strong> progressing to the lowest indenture level to be analyzed.When more than one method of performing a particular function is available,the alternative operational modes shall be identified. All multiplefunctions utilizing different equipment or groups of equipment alsoshall be identified. The functions <strong>and</strong> outputs for each indenture levelalso may be presented in a function-output list or in narrative form.4.1.2 Environmental profiles. The environmental profiles whichpresent the anticipated environmental conditions for each mission <strong>and</strong>mission phase shall be defined. When a system will be utilized in morethan one environment each different environmental profile shall bedescribed. The intended use, through time, of the system <strong>and</strong> its equipmentsshall be developed from the mission time statements for each environmentalprofile. The use time-environment phasing is used in determining thetime-stress relationships <strong>and</strong> the feasibility of failure detectionmethods <strong>and</strong> compensating provisions in the operating system.4.1.3 Mission time. A quantitative statement of system functiontimerequirements shall be developed <strong>and</strong> included in the system definition.Function-time requirements shall be developed for items which operate indifferent operational modes during different mission phases <strong>and</strong> foritems which function only if required.4.1.4 Block diagrams. Block diagrams which illustrate theoperation, interrelationships, <strong>and</strong> interdependencies of functionalentities of a system shall be constructed to provide the ability fortracing failure mode effects through all levels of indenture. Bothfunctional <strong>and</strong> reliability block diagrams are required to show thefunctional flow sequence <strong>and</strong> the series dependence or independence offunctions <strong>and</strong> operations. Block diagrams may be constructed in conjunctic]nwith or after defining the system <strong>and</strong> shall present the system as abreakdown of its major functions. More than one block diagram willusually be required to display alternative modes of operation, dependingupon the definitiolt established for the system. All inputs <strong>and</strong> outputsof the item as a whole shall be shown on the diagram <strong>and</strong> clearly labeled.Each block shall be designated by a consistent <strong>and</strong> logical item numberthat reflects the functional system breakdown order. A uniform numberingsystem developed in functional system breakdown order is required toprovide traceability <strong>and</strong> tracking throu~h all Ieveh of indenture. ??lL-<strong>STD</strong>-780 provides an example of a uniform numbering system for aeronauticalequipment that can be used as a guide in the development of a consistent<strong>and</strong> logical identification code for block diagrams. Figures 101.1 <strong>and</strong>101.2 depict examples of functional anu reliability block diagrams.4.1.4.1 Functional block diagrams, A functional block diagramillustrates tileoperation <strong>and</strong> interrelationships between functionalentities of a system as defined in engineering data <strong>and</strong> schematics. A.TASK10I2~1Yevcm!>l?r!9(90101-3—————- -E _x==- S=-.-——=.-G.=.-—_.—- =—--—.—-. T—-... ...-.—e.——— ——————

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

Saved successfully!

Ooh no, something went wrong!