Capability EXPRESS information model

This section describes the EXPRESS information model for the capability.

From module : part_and_version_identification - using subset

Part

NOTE 1   A Part does not represent an actual physical object that is or was existing in the real world.

NOTE 2   A complex instance of the Part entity and of the Document entity may be created in order to represent a document that is a component of a manufactured product, for example a user manual of a car.


ENTITY Part
  SUBTYPE OF (Product);
WHERE
  WR1: SIZEOF(['part', 'raw material', 'tool']*types_of_product(SELF))=1;
END_ENTITY;


From module : product_identification - using subset

Product

A Product is the identification of a product or of a type of product. It is a collector of data common to all revisions of the Product.

NOTE 1   Products that this entity data type can represent, include:

• products existing in the real world;
• products that may come into existence as a consequence of some realization process. This includes parts and documents;
• products that are functions.

In the interpreted models, these various meanings are represented within instances of the entity product_related_product_category, with prescribed values of the category name. For example, the category name 'document' shall be used when characterizing the fact that a product is actually a document.

NOTE 2   A product is identified by an organization or a person in an organization. The definition of the domain of uniqueness and the mechanism for guaranteeing the uniqueness of product id are outside the scope of this application module.

NOTE 3   A product may have zero or more versions. A version of a product is represented with an instance of the entity Product_version or of one of its specializations.


ENTITY Product;
  id : STRING;
  name : OPTIONAL STRING;
  description : OPTIONAL STRING;
END_ENTITY;


id:

the identifier that distinguishes the product.

NOTE 4   A particular codification for the values of this attribute may be specified in the EXPRESS schemas that use or specialize this entity, or in an agreement of common understanding between the partners sharing this information.

name: the words by which the product is known. The value of this attribute need not be specified.

description: the text that provides further information about the Product. The value of this attribute need not be specified.

From module : product_version - using all

Product_version

NOTE    The set of all instances of Product_version of the same Product represents the history of the product.


ENTITY Product_version;
  id : STRING;
  description : OPTIONAL STRING;
  of_product : Product;
END_ENTITY;


id: the identifier for the Product_version.

description: the text that provides further information about the Product_version. The value of this attribute need not be specified.

of_product: the Product, the Product_version identifies a version of.

From module : product_as_individual - using subset


TYPE product_as_individual_identification_item = SELECT BASED_ON identification_item WITH
   (Product_as_individual,
    Product_as_individual_version,
    Product_as_individual_view);
END_TYPE;


Product_as_individual

A Product_as_individual is a type of Product that identifies an individual artefact that has been made or is planned to be made. It is a collector of data common to all revisions of the Product_as_individual.

NOTE 1   Revisions (Product_as_individual_version) of Product_as_individual are used to represent whether an individual artefact has yet to be made or has been made. The Product_as_individual_version subtype Product_as_planned is used to represent the revision of an individual artefact that has yet to be made and the subtype Product_as_realized is used to represent the revision of an individual artefact that has been made.

NOTE 2   Where physical products are being represented, the Product_as_individual represents the physical or planned physical realization of a product.

NOTE 3   It is likely, but not essential, that the artefact, was or will be made from a product design. The product design will be represented by a Product which will be related to the Product_as_individual by Product_design_to_individual.

NOTE 4   Many physical products may be produced from a given design. A single Product may lead to many Product_as_individuals.


ENTITY Product_as_individual
  SUBTYPE OF (Product);
END_ENTITY;


Product_as_individual_version

A Product_as_individual_version is a type of Product_version. It is a revision of a Product_as_individual and acts as a collector of the definitions of this revision.


ENTITY Product_as_individual_version
  ABSTRACT SUPERTYPE OF (ONEOF (Product_as_planned,
                                Product_as_realized))
  SUBTYPE OF (Product_version);
  SELF\Product_version.of_product : Product_as_individual;
END_ENTITY;


of_product: the Product_as_individual that the Product_as_individual_version identifies a version of.

Product_as_individual_view

A Product_as_individual_view is a type of Product_view_definition that defines a characterization view of a version of a Product_as_individual.

NOTE    The Product_as_individual_view entity type supports the representation of different views of a Product_as_individual for different purposes. Multiple views of the same Product_as_individual are represented by different instances of Product_as_individual_view for the same Product_as_individual_version.


ENTITY Product_as_individual_view
  SUBTYPE OF (Product_view_definition);
  SELF\Product_view_definition.defined_version : Product_as_individual_version;
END_ENTITY;


defined_version: the Product_as_individual_version of which the Product_as_individual_view provides a characterization.

Product_as_realized

NOTE 1   Where physical products are being represented, the Product_as_realized represents the physical product - something one can touch.

NOTE 2   The artefact may have been made from a version of a product design (Product_version). If this is the case, then the relationship between the artefact (Product_as_realized) and the design (Product_version) is represented by Product_design_version_to_individual.

NOTE 3   The artefact may have been planned and represented by Product_as_planned. In which case, the actual artefact (Product_as_realized) is related to the planned artefact (Product_as_planned) by the Product_planned_to_realized relationship.


ENTITY Product_as_realized
  SUBTYPE OF (Product_as_individual_version);
END_ENTITY;


Product_design_version_to_individual


ENTITY Product_design_version_to_individual;
  product_design_version : Product_version;
  individual_product : Product_as_individual_version;
END_ENTITY;


product_design_version: the version of the product design that is being made.

individual_product: the product that has been or is planned to be made from this version of the design.

From module : product_relationship - using subset

Product_relationship


ENTITY Product_relationship;
  relation_type : STRING;
  description : OPTIONAL STRING;
  relating_product : Product;
  related_product : Product;
END_ENTITY;


relation_type: the text that specifies the nature of the relationship between the instances of Product .

relating_product: one of the instances of Product that is a part of the relationship.

related_product: the other instance of Product that is a part of the relationship. If one element of the relationship is dependent on the other, this attribute shall be the dependent one.

From module : state_observed - using subset


TYPE state_classification_item = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON classification_item WITH
   (Applied_state_assignment,
    State,
    State_relationship);
END_TYPE;



TYPE state_of_item = EXTENSIBLE GENERIC_ENTITY SELECT;
END_TYPE;


Applied_state_assignment


ENTITY Applied_state_assignment;
  described_state : State;
  assigned_to : state_of_item;
  role : State_role;
END_ENTITY;


described_state: a State the subject has or is in.

assigned_to: the subject which has or is in a State.

role: the purpose of the association of the Applied_state_assignment with product or activity data.

State

NOTE 1   A state's existence can be just a state that an object is currently in, a predicted state that an object will eventually be in, or an observed state that an object has been in.

NOTE 2   The period of existence may be an instant or longer.


ENTITY State
  SUPERTYPE OF (ONEOF (State_observed,
                       State_predicted));
  name : STRING;
  description : OPTIONAL STRING;
END_ENTITY;


name:

the words by which the State is known.

NOTE    Identifiers are assigned to State using statechar_identification_item.

State_assertion


ENTITY State_assertion;
  name : STRING;
  description : OPTIONAL STRING;
  asserted_state : State;
  conformance_state : State_definition;
END_ENTITY;


name: the words by which the State_assertion is known.

description: the text that provides further information about the State_assertion. The value of the attribute need not be specified.

asserted_state: the subject State being asserted.

conformance_state: a particular State_definition the subject State is being asserted against.

State_role


ENTITY State_role;
  name : STRING;
  description : OPTIONAL STRING;
END_ENTITY;


name: the words by which the State_role is known.

description: the text that provides further information about the State_role. The value of the attribute need not be specified.