[七步工作法标准模板.pptVIP

The red outline shows where the development of causes should be recorded on the FTA form. The failure or problem represents the trunk of the fault tree. Primary branches are on the left side of the fault tree and branch off of the main trunk. Secondary branches are transitional in nature and link the causal event series in the center of the fault tree. Tertiary branches link the transitional events to the actual product/process basic characteristics on the right side of the fault tree. Note: a basic characteristic may be listed under one or more tertiary branches of the fault tree. Some redundancies may occur. Try to keep the FTA around 1 or 2 pages. If the FTA is too narrow, beta error (customer risk) may be too large. Excessive fault tree beta error will result in the project having to recycle to pick up key input variables that were left behind. If the FTA is too broad, alpha error (producer risk) may be too large. The project will then become stalled because irrelevant key input variables will need to be investigated to determination if they are or are not important. The red outline shows where the development of causes should be recorded on the FTA form. The failure or problem represents the trunk of the fault tree. Primary branches are on the left side of the fault tree and branch off of the main trunk. Secondary branches are transitional in nature and link the causal event series in the center of the fault tree. Tertiary branches link the transitional events to the actual product/process basic characteristics on the right side of the fault tree. Note: a basic characteristic may be listed under one or more tertiary branches of the fault tree. Some redundancies may occur. Try to keep the FTA around 1 or 2 pages. If the FTA is too narrow, beta error (customer risk) may be too large. Excessive fault tree beta error will result in the project having to recycle to pick up key input variables that were left behind. If the FTA is