| Capability (C063):— representing_product_configuration | Date: 2007/06/22 12:22:11 Revision: 1.25 |
This section describes the EXPRESS information model for the capability.
Assembly_component_relationship
An Assembly_component_relationship is a type of View_definition_usage. It identifies a possibly quantified usage of a product version as a component of another product version.The relationship is established between two instances of Product_view_definition.
The inherited attribute relating_view identifies the Product_view_definition of the assembly.
The inherited attribute related_view identifies the Product_view_definition of the product version that plays the role of component.
The Assembly_component_relationship specifies that, in the initial_context of the Product_view_definition that is referred to as relating_view, it is considered that the product version that is indirectly identified with the related_view attribute, is a component of the product version that is indirectly identified with the relating_view attribute.
NOTE 1 In another context, the structure of the assembly may be described differently, adding, for example, an intermediate level between the products.
NOTE 2 This entity data type may be used to establish assembly relationships during design or to represent the composition of an assembly existing in the real world.
NOTE 3 An Assembly_component_relationship identifies an item in a parts list. Should the quantity be zero, the component would still be listed in the parts list.
In case the component is a part, the following additional specifications apply:
In case the component is a non-countable material, the following additional specifications apply:
EXAMPLE An assembly may require inclusion of ten grams of grease.
NOTE 4 This version of the Assembly structure module does not enable to represent the fact that the quantity of a fluid component is, for example 'at most 10 grams' or 'between 5 or 20 grams'. However, some ISO 10303 application protocols, for example ISO 10303-214, provide a representation for those requirements.
An Assembly_component_relationship shall be either a Next_assembly_usage, a or a Component_upper_level_identification.
ENTITY Assembly_component_relationship
ABSTRACT SUPERTYPE
OF (ONEOF (Next_assembly_usage,
Promissory_usage,
Component_upper_level_identification))
SUBTYPE OF (View_definition_usage);
quantity :
OPTIONAL
Value_with_unit;
location_indicator :
OPTIONAL
STRING;
WHERE
WR1: NOT(EXISTS(quantity)) OR ((NOT ('NUMBER' IN TYPEOF(quantity.value_component))) XOR (quantity.value_component > 0));
END_ENTITY;
quantity: the Value_with_unit that defines the amount of this usage of the component in the assembly. The value of this attribute need not be specified.
location_indicator: the text that identifies this usage of the component in the assembly in a diagram, list, chart, or on a physical piece of equipment. The value of this attribute need not be specified.
ENTITY Next_assembly_usage
SUBTYPE OF (Assembly_component_relationship);
END_ENTITY;
The effectivity_domain attribute identifies a domain of effectivity.
The item_usage_relationship attribute identifies a relationship which characterizes the use of the product with or within another product.
EXAMPLE This relationship may be an assembly-component relationship or a make-from relationship.
When the effectivity domain is a range of serial numbers, the serial numbers considered are those of the Product_configuration.
When the effectivity domain is defined using a production lot number, the production lot considered is one of the Product_configuration.
When the effectivity domain is an interval of time, the interval of time considered is related to the production of the Product_configuration.
NOTE When no effectivity constraint is applied to a View_definition_usage, the validity or applicability status of this View_definition_usage is unknown.
ENTITY Item_usage_effectivity;
effectivity_domain : Effectivity;
item_usage_relationship : View_definition_usage;
resolved_configuration : Item_design_association;
END_ENTITY;
effectivity_domain: the Effectivity that defines the domain of effectivity.
item_usage_relationship: the View_definition_usage whose applicability is constrained.
resolved_configuration: the Item_design_association that identifies the context where the item_usage_relationship is considered.
TYPE version_or_definition =
SELECT
(Product_version,
Product_view_definition);
END_TYPE;
If the design is a Product_view_definition, the Item_design_association represents the statement that, in the considered definition context, the product version, that is, the Product_view_definition is a valid way to implement the Product_configuration.
NOTE 1 This association might not be valid in all definition contexts of the product version.
If the design is a Product_version, the Item_design_association represents the statement that, in all definition contexts, the Product_version is a valid way to implement the Product_configuration.
NOTE 2 The association might not be valid for other versions of the product.
ENTITY Item_design_association;
configuration : Product_configuration;
design : version_or_definition;
UNIQUE
UR1: configuration, design;
END_ENTITY;
configuration: the Product_configuration for which a product solution is designated.
design: the Product_version or the Product_view_definition that identifies a product which is a valid implementation for the Product_configuration.
NOTE 1 The entity Product_configuration corresponds to the concept of configuration item defined, in some configuration management standards, as an item subject to configuration management.
EXAMPLE A Product_configuration may represent a component of a contracted product, onto which severe safety rules apply and for which configuration management is therefore rigorously applied.
NOTE 2 A Product_configuration may identify a variation of a Product_concept, an entire Product_concept, or some portion thereof.
NOTE 3 A Product_configuration can be established prior to the existence of a corresponding product.
ENTITY Product_configuration;
id : STRING;
name : STRING;
description :
OPTIONAL
STRING;
item_context : Product_concept;
INVERSE
corresponding_design : SET[0:1] OF Item_design_association FOR configuration;
END_ENTITY;
id: the identification of the identifier that distinguishes the configuration item.
name: the words by which the configuration item is known.
description: the text that provides further information about the Product_configuration. The value of the attribute need not be specified.
item_context: the Product_concept that defines the context in which the configuration item has been defined.
EXAMPLE Events may be used to bound a Dated_effectivity period, at planning phase.
ENTITY Dated_effectivity
SUBTYPE OF (Effectivity);
start_bound : date_or_event;
end_bound :
OPTIONAL
date_or_event;
END_ENTITY;
start_bound: the date or event that defines the lower bound of the interval of applicability.
end_bound: the date or event that defines the upper bound of the interval of applicability. The value of the attribute need not be specified. If the value for this attribute is not specified, the interval of applicability has no upper limit.
NOTE Instances of Effectivity may be applied to any kind of product or activity data, using the constructs defined in the Effectivity application module.
ENTITY Effectivity
SUPERTYPE OF
(ONEOF (Serial_effectivity,
Dated_effectivity,
Lot_effectivity,
Time_interval_effectivity));
id : STRING;
name : STRING;
description :
OPTIONAL
STRING;
END_ENTITY;
id: the identifier that distinguishes the Effectivity.
name: the words by which the Effectivity is known.
description: the text that provides further information about the Effectivity. The value of the attribute need not be specified.
ENTITY Lot_effectivity
SUBTYPE OF (Effectivity);
lot_id : STRING;
lot_size : Value_with_unit;
END_ENTITY;
lot_id: the identification of the batch of items.
lot_size: the size of the batch of items.
ENTITY Serial_effectivity
SUBTYPE OF (Effectivity);
start_id : STRING;
end_id :
OPTIONAL
STRING;
END_ENTITY;
start_id: the first valid serial number.
end_id: the last valid serial number. The value of the attribute need not be specified. If the value for this attribute is not specified, the interval of applicability has no upper bound.
ENTITY Time_interval_effectivity
SUBTYPE OF (Effectivity);
effectivity_period : Time_interval;
END_ENTITY;
effectivity_period: the Time_interval that defines the domain of validity.
ENTITY Market;
name : STRING;
market_segment_type :
OPTIONAL
STRING;
END_ENTITY;
name: the words by which the market is known.
market_segment_type:
the text that identifies a marketing category of products.
EXAMPLE 'Luxury automobiles', 'laptop personal computers', and 'budget personal stereos' are examples of market segment types.
The value of this attribute need not be specified.
NOTE 1 The definition of product concepts is driven by market and customer requirements and forecasting. A Product_concept often corresponds to the highest level item(s) manufactured by an organization for customers.
EXAMPLE 1 In an organization which manufactures cars and engines for cars, the car models will be represented by instances of Product_concept.
NOTE 2 The entity data type Product_concept enables to represent customer-oriented identification of products that are to be delivered to customers, while the entity data type Product enables to identify and to track the history of items that are designed and manufactured, as a tangible solution, or component of the solution, for a product concept.
NOTE 3 A product concept may be characterized by a set of product features identified by the customers or derived from customers' needs.
NOTE 4 Depending on the kind of industry and products, a product concept might be offered to the customers in one or many different configurations.
ENTITY Product_concept;
id : STRING;
name : STRING;
description :
OPTIONAL
STRING;
target_market :
OPTIONAL
Market;
UNIQUE
UR1: id;
END_ENTITY;
id:
the identifier for the Product_concept.
EXAMPLE 2 The id may be a sales model number.
name: the words by which the Product_concept is known.
description: the text that provides further information about the Product_concept. The value of the attribute need not be specified.
target_market:
the Market for which the Product_concept is intended. The value of the attribute need not be specified.
NOTE 5 In the MIM schema, the corresponding attribute is mandatory and refers to the entity data type product_concept_context. If target_market is not specified, empty strings shall be assigned to the attributes name and market_segment_type of the instance of product_concept_context.
TYPE any_number_value =
NUMBER;
END_TYPE;
TYPE any_string_value =
STRING;
END_TYPE;
TYPE length_measure =
REAL;
END_TYPE;
TYPE measure_value =
EXTENSIBLE
SELECT
(any_number_value,
any_string_value,
length_measure,
plane_angle_measure);
END_TYPE;
TYPE plane_angle_measure =
REAL;
END_TYPE;
EXAMPLE The number of parts in an assembly is a physical quantity that may be measured in a unit called 'parts'. Such a unit cannot be related to an SI unit.
ENTITY Context_dependent_unit
SUBTYPE OF (Unit);
WHERE
WR1: EXISTS(SELF\Unit.name);
END_ENTITY;
NOTE A Conversion_based_unit is often used to convert a unit in one system of units to a similar unit in another system.
EXAMPLE An Imperial inch is 25.4 millimetres
ENTITY Conversion_based_unit
SUBTYPE OF (Unit);
conversion_factor : Value_with_unit;
WHERE
WR1: EXISTS(SELF\Unit.name);
END_ENTITY;
conversion_factor: the Value_with_unit that defines the conversion.
EXAMPLE Newtons per square metre is a derived unit.
ENTITY Derived_unit
SUBTYPE OF (Unit);
elements : SET[1:?] OF Derived_unit_element;
END_ENTITY;
elements:
a set of units and their exponents whose product defines the Derived_unit.
NOTE Each element is one term in the Derived_unit.
ENTITY Derived_unit_element;
base_unit : Unit;
exponent : REAL;
END_ENTITY;
base_unit: the unit of a term in the Derived_unit.
exponent: the real number for the Derived_unit.
ENTITY Unit
SUPERTYPE OF
(ONEOF (Amount_of_substance_unit,
Electric_current_unit,
Length_unit,
Luminous_intensity_unit,
Mass_unit,
Plane_angle_unit,
Ratio_unit,
Solid_angle_unit,
Thermodynamic_temperature_unit,
Time_unit));
name : STRING;
si_unit : BOOLEAN;
END_ENTITY;
name: the words by which the Unit is known.
si_unit: the boolean value that indicates whether the Unit is one of the units defined in the SI system.
ENTITY Value_with_unit;
unit : Unit;
value_component : measure_value;
END_ENTITY;
unit: the Unit with which the physical quantity is expressed.
value_component: the value of the quantity.
A Product_view_definition is a collector of the properties that characterize the Product_version in the initial_context and additional_contexts.
EXAMPLE 1 The design of the SS Titanic and the as-built description of the SS Titanic can be represented as two instances of Product_view_definition.
ENTITY Product_view_definition;
id : STRING;
name :
OPTIONAL
STRING;
additional_characterization :
OPTIONAL
STRING;
initial_context : View_definition_context;
additional_contexts : SET[0:?] OF View_definition_context;
defined_version : Product_version;
WHERE
WR1: NOT (initial_context IN additional_contexts);
END_ENTITY;
id:
the identifier that distinguishes the Product_view_definition.
NOTE The value of this attribute may be an empty string.
name:
the words by which the Product_view_definition is known. The value of this attribute need not be specified.
NOTE 1 This attribute is mapped onto description for compatibility with pre-existing application protocols.
additional_characterization:
the text that provides further information about the Product_view_definition. The value of this attribute need not be specified.
NOTE 2 This attribute may be used to precise the kind of definition.
EXAMPLE 2 In case the Product_view_definition characterizes a mating, this attribute may identify the kind of mating. 'clipping', 'welding' are examples of additional_characterization for a mating definition.
initial_context: the View_definition_context in which the defined_version has been primarily characterized by the Product_view_definition .
additional_contexts: the set of instances of View_definition_context in which this Product_view_definition is also relevant.
defined_version: the Product_version of which the Product_view_definition provides a characterization.
NOTE Requirements and vocabularies vary among the industrial activity fields. This entity intends to identify such a domain.
ENTITY View_definition_context;
application_domain : STRING;
life_cycle_stage : STRING;
description :
OPTIONAL
STRING;
END_ENTITY;
application_domain:
the text that identifies the application context that bounds the universe of discourse.
EXAMPLE 1 'assembly study', 'digital mock-up', 'electrical design', 'mechanical design', 'preliminary design', 'process planning' are examples of application domains
If application_domain is an empty string, the View_definition_context shall be considered as not specific of any application domain.
life_cycle_stage:
the text that identifies a stage in the life cycle of a product.
EXAMPLE 2 'design phase', 'production', 'recycling phase' are examples of life cycle stages.
If life_cycle_stage is an empty string, the View_definition_context shall be considered as not specific of any life cycle stage.
description: the text that provides further information about the View_definition_context. The value of this attribute need not be specified.