PDM-UG: Product Concept Identification
From WikiSTEP
This page belongs to the PDM Usage Guide.
The products that are sold by an organization to its customers are often defined as variations or configurations of a common product model, referred to as product concept. This product concept is defined in a market context and can be seen as a logical container for all of its variations. In the PDM Schema, product concept identification is the representation of these product concepts with their related market context.
Contents |
The Instance Model: EXPRESS entities and attributes
The EXPRESS entities and attributes essential to support the requirements to represent product concept identification information are illustrated in Diagram 63 below.
Diagram 63: Product concept identification Instance Diagram
Product concept
A product_concept describes a class of similar products that an organization provides to its customers. It represents the idea of a product as identified by potential or actual customer requirements. Therefore, a product_concept may exist before the parts have been defined that implement it.
Depending on the kind of industry and products, a product_concept might be offered to the customers in one or many different configurations. If exactly one configuration is defined, the product_concept corresponds to a particular part design. If the product concept is offered in different configurations, each of these configurations is a member of the class of products defined by this product_concept.
Attributes
- The id attribute specifies the identifier of the product_concept. It is usually assigned by the organization that provides the product belonging to that product_concept to its customers. This identifier must be unique within the given scope.
- The name attribute specifies the nomenclature, or common name, by which the product_concept is referred.
- The description attribute specifies additional information about the product_concept.
- The market for the products belonging to a product_concept is further described in the market_context attribute. All product_concepts must have a related product_concept_context, which specifies their market context.
| ENTITY product_concept | Attribute Population | Remarks |
| id | type: identifier = string | must be unique |
| name | type: label = string | |
| description | type: text = string | OPTIONAL |
| market_context | type: entity = product_concept_context | reference to the associated product_concept_context (see Product concept context) |
===Preprocessor Recommendations=== There might be several levels of product concepts defined in a company. The description of product concept structures and relationships is not supported by the current PDM Schema version. It is therefore recommended to instantiate the lowest level product_concept that is offered to the customer.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== A product_concept represents a conceptual idea of a class of similar products that are offered to a market. No design or manufacturing related product data can be attached to the product_concept directly. The members of that product class are the different configurations that are available for the product_concept. Within the PDM Schema, these configurations are defined explicitly as configuration_items (see Configuration items), each of them being potentially related to the parts that implement the particular configuration. A product_concept will usually be referenced by at least one associated configuration_item specifying a particular product configuration.
In addition, a product_concept may be referenced by the following entity:
- applied_organizational_project_assignment to represent projects associated to the product_concept (see Applied organizational project assignment).
Product concept context
The product_concept_context entity is a subtype of application_context_element. It defines the market context in which a product_concept is defined and may include information characterizing the potential customers of the products of the associated product_concept. The application domain is identified by the associated application_context entity.
Attributes
- The market_segment_type is a label that identifies the kind of consumer preferences associated with a product_concept.
| ENTITY product_concept_context | Attribute Population | Remarks |
| name | type: label = text | Specifies a label by which the product_concept_context is known. |
| frame_of_reference | type: entity = application_context | see #application_context|Application context |
| market_segment_type | type: label = text |
===Preprocessor Recommendations=== It is recommended to instantiate this entity exactly once in the data set. There is no standard mapping for the name and market_segment_type attributes of a product_concept_context. Neither AP203 nor AP214 define requirements for a product_concept_context. It is therefore recommended to use the default values for the entities and attributes not supported by the preprocessor as described in the 'General information' section of this usage guide.
===Postprocessor Recommendations=== There are no specific postprocessor recommendations.
===Related Entities=== Related Entities: There are no specific related entities.
