6 Configuration management schema

6.1 General

The subject of the configuration_management_schema is the identification of items, the composition of which is to be managed. The item to be managed is specified as a configuration_item. It is usually visible to customers of the organization that does the configuration management. If the item being managed is a product, the schema facilitates the establishment of the association of appropriate versions of the product to the configuration_item.

This schema also provides the capability to record the associations established to enable the tracking of the associations.

The functionality of configuration management is achieved using the entities configuration_item, configuration_design, and configuration_effectivity.

The configuration management schema of this part of ISO 10303 covers the following capabilities:

• the identification of the configuration_items and the respective product_concepts of which they form constituent.
• the identification of a product_definition or product_definition_formation that realizes the configuration_item.
• the association of the appropriate versions of a product to build a configuration_item. This association is referred to as configuration_effectivity.

Three of the ways to apply configuration_effectivity are:

• serial_numbered_effectivity, where the configuration_effectivity is based on serial numbered instances of manufactured products;
• dated_effectivity, where the configuration_effectivity is based on dates when instances of the product are manufactured;
• lot_effectivity, where the configuration_effectivity is based on instances of lots of products manufactured.

NOTE 1   The definitions of serial_numbered_effectivity, dated_effectivity, and lot_effectivity are given in the effectivity_schema in ISO 10303-41.

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.

REFERENCE FROM basic_attribute_schema    --  ISO 10303-41
  (description_attribute_select,
   get_description_value,
   get_name_value,
   name_attribute_select);



REFERENCE FROM effectivity_schema    --  ISO 10303-41
  (effectivity);



REFERENCE FROM product_concept_schema    --  ISO 10303-44
  (product_concept,
   product_concept_feature_association);



REFERENCE FROM product_definition_schema    --  ISO 10303-41
  (product_definition,
   product_definition_effectivity,
   product_definition_formation);



REFERENCE FROM product_structure_schema    --  ISO 10303-44
  (product_definition_occurrence,
   product_definition_usage);



REFERENCE FROM support_resource_schema    --  ISO 10303-41
  (bag_to_set,
   identifier,
   label,
   text);
(*



NOTE 2   The schemas referenced above are specified in the following parts:

basic_attribute_schema	ISO 10303-41
effectivity_schema	ISO 10303-41
product_concept_schema	ISO 10303-44
product_definition_schema	ISO 10303-41
product_structure_schema	ISO 10303-44
support_resource_schema	ISO 10303-41

NOTE 3   See Annex D for a graphical representation of this schema.

6.2 Fundamental concepts and assumptions

The following concepts and assumptions apply.

• Configuration management may be applied to products and parts of products to be designed or manufactured;
• An organization determines which products are to be under its configuration management control. These products become the configuration items of the organization. These are usually higher-level functional elements that act as the focal points for managing the effectivity of lower-level constituents;
• A product concept may identify a customer view of a product based on a static set of configuration items or may be configurable based on customer selected options that are defined for it.

6.3 configuration_management_schema type definitions

6.3.1 cms_description_attribute_select   

EXPRESS specification:

*)
TYPE cms_description_attribute_select = SELECT BASED_ON description_attribute_select WITH
   (configuration_design);
END_TYPE;
(*

6.3.2 cms_name_attribute_select   

EXPRESS specification:

*)
TYPE cms_name_attribute_select = SELECT BASED_ON name_attribute_select WITH
   (configuration_design);
END_TYPE;
(*

6.3.3 configuration_design_item   

EXPRESS specification:

*)
TYPE configuration_design_item = SELECT
   (product_definition,
    product_definition_formation,
    product_definition_occurrence);
END_TYPE;
(*

6.4 configuration_management_schema entity definitions

6.4.1 configurable_item   

EXAMPLE    A customer order for a car specifies the model of car ordered and also certain features of the car, such as colour "red", trim "leather grey", "sun roof", and "aluminium rims". The car that is ordered can be represented by a configurable_item. The model of car can be represented by the product_concept that plays the role item_concept for the ordered car. Each of the features of the ordered car can be represented by a product_concept_feature.

EXPRESS specification:

*)
ENTITY configurable_item
  SUBTYPE OF (configuration_item);
  item_concept_feature : SET[1:?] OF product_concept_feature_association;
END_ENTITY;
(*

Attribute definitions:

item_concept_feature: the product_concept_feature_association instances associated with the configurable_item.

6.4.2 configuration_design   

NOTE 1   Organizations may establish this association before any actual units are planned and before any details of the design have been established.

EXPRESS specification:

*)
ENTITY configuration_design;
  configuration : configuration_item;
  design : configuration_design_item;
DERIVE
  name : label := get_name_value (SELF);
  description : text := get_description_value (SELF);
UNIQUE
  UR1: configuration, design;
WHERE
  WR1: SIZEOF (USEDIN (SELF, 'BASIC_ATTRIBUTE_SCHEMA.' + 'NAME_ATTRIBUTE.NAMED_ITEM')) <= 1;
  WR2: SIZEOF (USEDIN (SELF, 'BASIC_ATTRIBUTE_SCHEMA.' + 'DESCRIPTION_ATTRIBUTE.DESCRIBED_ITEM')) <= 1;
END_ENTITY;
(*

Attribute definitions:

configuration: a configuration_item that specifies that the product_definition or product_definition_formation is a candidate to be treated as a single unit in the configuration management process.

design: a product_definition or product_definition_formation representing a design that is a candidate to be treated as a single unit in the configuration management process.

name: the label by which the configuration_design is known.

NOTE 2   This attribute is an upwardly compatible addition to configuration_design as specified in ISO 10303-44:1994.

description: the text that characterizes the configuration_design.

NOTE 3   This attribute is an upwardly compatible addition to configuration_design as specified in ISO 10303-44:1994.

Formal propositions:

UR1: The combination of configuration and design shall be unique within a population of configuration_design.

WR1: Each configuration_design shall be the named_item in at most one name_attribute.

NOTE 4   The name_attribute data type is defined in the basic_attribute_schema in ISO 10303-41.

WR2: Each configuration_design shall be the described_item in at most one description_attribute.

NOTE 5   The description_attribute data type is defined in the basic_attribute_schema in ISO 10303-41.

NOTE 6   A template for constraining the population of the entity data types defined in the basic_attribute_schema is described in annex E of ISO 10303-41.

6.4.3 configuration_effectivity   

EXAMPLE    A fuel injection pump in a 200 HP engine is effective for a certain date range in a particular truck. This information is captured prior to any production plans existing for the 200 HP engine in a configuration_effectivity entity.

NOTE    The product_definition_effectivity data type is a subtype of the effectivity data type. Other subtypes of effectivity are defined in the effectivity_schema in ISO 10303-41. An instance of this entity may also be an instance of either a serial_numbered_effectivity, a dated_effectivity, or a lot_effectivity.

In the case where the applicability of the product_definition_usage is defined using serial_numbered_effectivity or lot_effectivity, the product that provides the context for the serial number or the lot number is specified by the configuration_design.

EXPRESS specification:

*)
ENTITY configuration_effectivity
  SUBTYPE OF (product_definition_effectivity);
  configuration : configuration_design;
UNIQUE
  UR1: configuration, SELF\product_definition_effectivity.usage, SELF\effectivity.id;
WHERE
  WR1: 'PRODUCT_STRUCTURE_SCHEMA.PRODUCT_DEFINITION_USAGE' IN TYPEOF (SELF\product_definition_effectivity.usage);
END_ENTITY;
(*

Attribute definitions:

configuration: a configuration_design for which the configuration_effectivity applies.

Formal propositions:

UR1: The combination of configuration, usage, and id shall be unique within a population of configuration_effectivity.

WR1: The usage shall be a product_definition_usage.

6.4.4 configuration_item   

NOTE 1   A configuration_item may be a variation of a product_concept, an entire product_concept, or some portion thereof.

NOTE 2   A configuration_item can be established prior to the existence of a corresponding product_definition or product_definition_formation.

NOTE 3   The association between a configuration_item and a corresponding product_definition or product_definition_formation is established using a configuration_design.

EXPRESS specification:

*)
ENTITY configuration_item;
  id : identifier;
  name : label;
  description : OPTIONAL text;
  item_concept : product_concept;
  purpose : OPTIONAL label;
END_ENTITY;
(*

Attribute definitions:

id: the identifier that distinguishes the the configuration_item.

name: the label by which the configuration_item is known.

description: the text that characterizes the configuration_item. The value of this attribute need not be specified.

NOTE 4   The description may identify the specification and function of the configuration_item.

item_concept: a product_concept associated with the configuration_item.

purpose: a descriptive label providing a reason to create the item_concept. The value of this attribute need not be specified.

6.4.5 configuration_item_relationship   

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 configuration_item_relationship;
  name : label;
  description : OPTIONAL text;
  relating_configuration_item : configuration_item;
  related_configuration_item : configuration_item;
END_ENTITY;
(*

Attribute definitions:

name: the label by which the configuration_item_relationship is known.

description: the text that characterizes the configuration_item_relationship. The value of this attribute need not be specified.

relating_configuration_item: one of the configuration_items that is a part of the association.

related_configuration_item: the other configuration_item 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.

© ISO 2021 — All rights reserved