Functional Block Diagrams

LATEST REVISION RECORD:

|SH. |




DISTRIBUTION:

|REVISIONS |
| 0 |70034AR |J. Mialback| | | | | | |
| |12/15/98 |V. Jacoby | | | | | | |
| | | | | | | | | |
| | || | | | | | |
| | | | | | | | | |
| | | | | | | | | |


TABLE OFCONTENTS

1.0 Scope 3


2.0 Applicable Documents 3


3.0 System Models 3


3.1 Functional Block Diagrams .................................................................. 3


3.2 Context Model 7


3.3 Structure Models 8


3.4 Behavior Models 10


3.5 Simplicity Models……………………………………………….. 12



SCOPE

The purpose of this document is to giveguidelines for the various models used in the GE Appliances design process. A summary:
1. Functional Block Diagrams: identify subsystems, functions, and interfaces
2. Context models: use to identify interfaces
3. System Allocation models: identify subsystems, CTQ flowdown, and subsystem options/reuse
4. Behavior models: functions of new features, scenarios
5. Simplicity models: showsubsystem/subassembly reuse across a product family
Note that the information contained in one type of diagram overlaps with one or more of the others. This overlap results from the fact that each diagram represents a view of the same system. If a particular diagram is required for a T- or P-review, the first review is noted in bold. It is expected that the diagrams will be further refined and included insubsequent reviews as well.

APPLICABLE DOCUMENTS


GEA Design For Six Sigma Training Materials

Design For Reliability Course Materials
Design For Reliability Tips

SYSTEM MODELS


1 Functional Block Diagrams (FBDs) Figures 1 & 2

Use: Capture key system and subsystem functions and inputs/outputs. Essential for conducting FMEA (Failure Mode and Effects Analyses). Thesubsystems defined in these diagrams are used to organize the information in the reliability allocation spreadsheets. These diagrams are required at P0.
Syntax: The rules for constructing FBDs are fairly loose. The boxes should represent systems/subsystems/components and should contain a list of functions. The functions can also be included beside the boxes, if it is clear which functions belong towhich box. Arrows between boxes represent inputs and outputs and should be labeled. Alternatively, a more schematic approach, where symbols for components (i.e., filters, condensers, etc.) are used, may be useful. Additional information, such as CTQs or other notes can be added as appropriate. Note that “structural”-type subsystems such as Backsplash, Chassis, etc., do not have many functions,other than “hold”, “hide”, “provide access”, or input/output. For these subsystems it is more useful to indicate information such as retention forces, bolt hole diameters and/or screw sizes/placement. Technically, these diagrams are a variant of the structure diagrams described later However, like FBDs, they are required at P0 and are typically developed along with the other subsystem FBDs....