| Integrated generic resource: Product structure configuration | ISO 10303-44:2021(E) © ISO |
The subject of the product_concept_schema is the idea of a product as defined by customer needs, i.e., a product concept. A product concept may exist before a product has been defined. A product concept identifies a collection of independent product features or capabilities. A product concept may also have product features identified specifically for it. Conditions among those features for a particular product may be specified to manage dependencies and define the valid product variations for a particular product concept.
EXAMPLE An automobile may have two types of engines identified as product features. One is a low power engine; the other is a high power engine. Air conditioning may also be identified as a product feature for the same automobile. A condition could be specified that if the air conditioning is present, the high power engine is necessary.
This clause defines the information requirements to which implementations shall conform using the EXPRESS language as defined in ISO 10303-11. The following EXPRESS declaration begins the product_concept_schema and identifies the necessary external references.Each implementation of an AP that uses this schema and that encodes entity names shall use the encoding specified in Annex A. Each reference to this schema in an open system shall use the identifier encoding specified in Annex B. This schema is illustrated in Annex D using the EXPRESS-G notation.
EXPRESS specification:
*)
SCHEMA product_concept_schema;
REFERENCE FROM
support_resource_schema
--
ISO 10303-41
(text,
label,
identifier);
REFERENCE FROM
application_context_schema
--
ISO 10303-41
(product_concept_context);
(*
NOTE 1 The schemas referenced above are specified in the following parts:
support_resource_schema ISO 10303-41 application_context_schema ISO 10303-41
NOTE 2 See Annex D for a graphical representation of this schema.
The following concepts and assumptions apply.
NOTE Examples and diagrams of the manner in which the entities of this part of ISO 10303 may be used to represent the combinations of product features are included in annex E!!!.
EXAMPLE "AND", "NOT", and "OR" are concept_feature_operator names.
NOTE 1 The meaning of the operation and the list of allowed values for the name attribute can be specified in each annotated EXPRESS schema that uses or specializes this entity or in an agreement of common understanding between the partners sharing this information.
NOTE 2 Annex E contains examples of this entity and figures that depict the relationships between it and the other entities of this schema.
EXPRESS specification:
*)
ENTITY concept_feature_operator;
name : label;
description :
OPTIONAL
text;
END_ENTITY;
(*
Attribute definitions:
name: the label by which the concept_feature_operator is known.
NOTE 3 The name designates the operation.
description: the text that characterizes the concept_feature_operator. The value of this attribute need not be specified.
NOTE The meaning of the association can be specified in each annotated EXPRESS schema that uses or specializes this entity or in an agreement of common understanding between the partners sharing this information.
EXPRESS specification:
*)
ENTITY concept_feature_relationship;
name : label;
description :
OPTIONAL
text;
relating_product_concept_feature : product_concept_feature;
related_product_concept_feature : product_concept_feature;
END_ENTITY;
(*
Attribute definitions:
name: the label by which the concept_feature_relationship is known.
description: the text that characterizes the concept_feature_relationship. The value of this attribute need not be specified.
relating_product_concept_feature: one of the product_concept_features that is a part of the association.
related_product_concept_feature: the other product_concept_feature that is a part of the association. If one element of the relationship is dependent upon the other, this attribute shall be the dependent one.
NOTE 1 When specified as the condition for a conditional_concept_feature, a concept_feature_relationship_with_condition defines a constraint for the use of a product_concept_feature. Complex conditions can be constructed for a product_concept_feature by using the concept_feature_relationship_with_condition to relate conditional_concept_features to each other.
NOTE 2 Annex E contains examples of this entity and figures that depict the relationships between it and the other entities of this schema.
EXPRESS specification:
*)
ENTITY concept_feature_relationship_with_condition
SUBTYPE OF (concept_feature_relationship);
conditional_operator : concept_feature_operator;
END_ENTITY;
(*
Attribute definitions:
conditional_operator: the concept_feature_operator used in the relationship between the relating_product_concept_feature and the related_product_concept_feature.
EXAMPLE A condition of negation is specified by using a concept_feature_operator with a name of "NOT" and a product_concept_feature_relationship_with_condition in which the related_product_concept_feature and the relating_product_concept_feature reference the same instance of product_concept_feature.
NOTE 1 Complex combinations of product_concept_features may be constructed using conditional_concept_features as operands of a concept_feature_relationship_with_condition.
NOTE 2 Annex E contains examples of this entity and figures that depict the relationships between it and the other entities of this schema.
EXPRESS specification:
*)
ENTITY conditional_concept_feature
SUBTYPE OF (product_concept_feature);
condition : concept_feature_relationship_with_condition;
END_ENTITY;
(*
Attribute definitions:
condition: the concept_feature_relationship_with_condition that establishes the condition for the conditional_concept_feature.
NOTE 1 A product_concept will often correspond to the highest level item(s) manufactured by an organization for a customer. It may be characterized by a set of product features identified by the customers or derived from customers' needs. The definition of product concepts is often driven by market and customer requirements and forecasting.
EXAMPLE 1 If an organization manufactures cars and engines for cars, the cars will be represented by product_concept instances. If another organization manufactures engines for cars, the engines will be represented as product_concepts in that organization.
EXPRESS specification:
*)
ENTITY product_concept;
id : identifier;
name : label;
description :
OPTIONAL
text;
market_context : product_concept_context;
UNIQUE
UR1: id;
END_ENTITY;
(*
Attribute definitions:
id: the identifier that distinguishes the product_concept.
EXAMPLE 2 The id could be a sales model number.
name: the label by which the product_concept is known.
description: the text that characterizes the product_concept. The value of this attribute need not be specified.
NOTE 2 This attribute can be used to convey the purpose, functionality, and selected features for the product_concept.
market_context: the frame of reference in which the product_concept is defined.
NOTE 3 The frame of reference for the product_concept is not restricted to a market context. To be upwardly compatible with product_concept as specified in ISO 10303:1994, the name of the market_context attribute is unchanged.
NOTE 4 The value of the market_context attribute can be constrained in each annotated EXPRESS schema that uses or specializes this entity data type or in an agreement of common understanding between the partners sharing this information.
Formal propositions:
UR1: The id shall be unique within a population of product_concept.
EXAMPLE "Luxury equipment" is a characteristic that distinguishes between a standard, low-price car and a topclass car.
NOTE The categorization of product_concept_features is accomplished through the mechanisms defined in ISO 10303-41 for collecting product data into groups. The name of the group indicates the category of the collected items.
EXPRESS specification:
*)
ENTITY product_concept_feature;
id : identifier;
name : label;
description :
OPTIONAL
text;
END_ENTITY;
(*
Attribute definitions:
id: the identifier that distinguishes the product_concept_feature.
name: the label by which the product_concept_feature is known.
description: the text that characterizes the product_concept_feature. The value of this attribute need not be specified.
NOTE The meaning of the association can be specified in each annotated EXPRESS schema that uses or specializes this entity or in an agreement of common understanding between the partners sharing this information.
EXPRESS specification:
*)
ENTITY product_concept_feature_association;
name : label;
description :
OPTIONAL
text;
concept : product_concept;
feature : product_concept_feature;
END_ENTITY;
(*
Attribute definitions:
name: the label by which the product_concept_feature_association is known.
description: the text that characterizes the product_concept_feature_association. The value of this attribute need not be specified.
concept: the product_concept that is being associated.
feature: the product_concept_feature that is being associated.
NOTE The meaning of the association can be specified in each annotated EXPRESS schema that uses or specializes this entity or in an agreement of common understanding between the partners sharing this information.
EXPRESS specification:
*)
ENTITY product_concept_relationship;
name : label;
description :
OPTIONAL
text;
relating_product_concept : product_concept;
related_product_concept : product_concept;
END_ENTITY;
(*
Attribute definitions:
name: the label by which the product_concept_relationship is known.
description: the text that characterizes the product_concept_relationship. The value of this attribute need not be specified.
relating_product_concept: one of the product_concepts that is a part of the association.
related_product_concept: the other product_concept that is a part of the association. If one element of the relationship is dependent upon the other, this attribute shall be the dependent one.
*)
END_SCHEMA; -- product_concept_schema
(*
© ISO 2021 — All rights reserved