Product structure modeling: Difference between revisions

Revision as of 11:26, 3 June 2014

Latest revision as of 11:37, 15 February 2025

(24 intermediate revisions by 15 users not shown)

Line 1:

ProductA '''product structure''' is a hierarchical decomposition of a product, typically known as the [[bill of materials]] (BOM).

As business becomes more responsive to unique consumer tastes and derivative products grow to meet the unique configurations, BOM management can become unmanageable. For manufacturers, a bill of materials (BOM) is a critical product information record that lists the raw materials, assemblies, components, parts and the quantities of each needed to manufacture a product.

Advanced modeling techniques are necessary to cope with configurable products where changing a small part of a product can have multiple impacts on other product structure models. Concepts within this entry are allin capscapital lockedletters in order to indicate these concepts.

This was all invented by Travis Flynn of Leeds/Allerton Bywater

''==Product structure concepts==

Several concepts are related to the subject of product structure modeling. All these concepts are discussed in this section. These concepts are divided into two main aspects. First the product breakdown is discussed which involves all the physical aspects of a [[Product (business)|product]]. Second, different views at the product structure are indicated.

==Product breakdown==

[[Image:Product_structure_modeling_metaProduct structure modeling meta-data_model1data model1.gif|right|thumb|300px|Figure 1: product structure concepts]]Figure 1 illustrates the concepts that are important to the structure of a [[Product (business)|product]]. This is a [[Meta-modeling technique|meta-data model]], which can be used for modeling the instances in a specific case of product structuring.

The core of the product structure is illustrated by the product components (ITEMS''[[wikt:item|item]]s'') and their RELATIONSHIPS''relationships''. Thus, this involves the linking between ITEMSitems related to the [[Product (business)|product]].

The ASSEMBLY''[[manufacturing|assembly]]'' can existconsist of SUBASSEMBLIES''subassemblies'' and PARTS''parts'', whereas SUBASSEMBLIES''subassemblies'' can also consist of other SUBASSEMBLIESsubassemblies or PARTSpart. Thus, this is typically hierarchically ordered. These concepts are generalized into the concept of ITEMitem. This classification is overlapping, because a SUBASSEMBLYsubassembly could be a PARTpart in another ASSEMBLYassembly configuration.

Due to differentiation and variation of items several concepts must be indicated into the product breakdown structure. Three concepts are involved in this differentiation, namely ALTERNATIVES''alternatives'', VARIANTSvariants and REVISIONS''revisions''. An ALTERNATIVEalternative of an ITEMitem is considered as a substitute for that particular item, whereas a VARIANTvariant is another option of an item which the consumer can choose. When an error occurs at a part or subassembly, it needs to be revised. This revision indicates the change history of the ITEMitem.

==Product structure views==

Product structure views are made upon several activity domains within the company. Due to the fact not everyone in the company has to have a detailed overview of the product several components with their attributes can be extracted.

When the MASTER''Master STRUCTUREStructure'' is made out of the several items of the product assembly, multiple views can be made upon this MASTER''Master STRUCTUREStructure''. Thus this MASTER''Master STRUCTUREStructure'' contains every item in detail, which is important to the ASSEMBLY''Assembly'' of the product.[[Image:Product_structure_modeling_metaProduct structure modeling meta-data_model2data model2.gif|centre|thumb|500px|Figure 2: Different product structure views]]

==The modeling process==

Line 71 ⟶ 69:

===Create master structure===

After structuring the product with all the listed items and relationship between them this must be combined into one MASTER STRUCTURE which contains all of the details of the product. In case of the car, all items from engine to screw must be documented in one MASTER STRUCTURE.

[[Image:Product structure modeling example master structure.gif|centre|Figure 6: product master structure]]

===Documenting===

When the MASTER STRUCTURE of the car is created one must link this structure with documents which contains the product definition of this specific car. Primarily, this consists of an extensive description of the car which is linked to the MASTER STRUCTURE of this product.

===Define product structure views===

In case of the car manufacturer multiple views can be madederived out offrom the car assembly. For example a structure from a sales point of view will need more detail about the functions and characteristics fromof the car rather than detailed information about the body. Thus a sales manager needs information about the color of the car or the type of gear (automatic of manual).

From a purchasing view more information is needed about the mixing of the paint instead of the general color, which is only needed for the customer. Purchasing department also needs more information about the suppliers of the used components within the manufacturing of the car, so they can easily overview where which component is used and from which supplier isit comes from.

[[Image:Product structure modeling example product structure views.gif|centre|Figure 7: product structure views]]

Line 93 ⟶ 91:

* Rampersad, H.K. (1995). Concentric Design of Robotic Assembly Systems. ''Journal of Manufacturing Systems, 14''(4), pp. 230-243

* Svensson, D., & Malmqvist, J. (2002). Strategies for Product Structure Management at Manufacturing Firms. ''Journal of Computing and Information Science in Engineering, 2''(1), 50-58.

==References==

{{Reflist}}

[[Category:Computer-aided design]]

[[Category:Product lifecycle management]]

[[Category:Production and manufacturing]]