Application module: Product as individual | ISO/TS 10303-1164:2011-10(E) © ISO |
This clause specifies the information requirements for the Product as individual application module. The information requirements are specified as the Application Reference Model (ARM) of this application module.
NOTE 1 A graphical representation of the information requirements is given in Annex C.
NOTE 2 The mapping specification is specified in 5.1. It shows how the information requirements are met by using common resources and constructs defined or imported in the MIM schema of this application module.
This clause defines the information requirements to which implementations shall conform using the EXPRESS language as defined in ISO 10303-11. The following begins the Product_as_individual_arm schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Product_as_individual_arm;
(*
The following EXPRESS interface statements specify the elements imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
Configuration_item_arm;
--
ISO/TS 10303-1056
USE FROM
Identification_assignment_arm;
--
ISO/TS 10303-1021
USE FROM
Product_identification_arm;
--
ISO/TS 10303-1017
USE FROM
Product_version_arm;
--
ISO/TS 10303-1018
USE FROM
Product_view_definition_arm;
--
ISO/TS 10303-1019
(*
NOTE 1 The schemas referenced above are specified in the following part of ISO 10303:
Configuration_item_arm ISO/TS 10303-1056 Identification_assignment_arm ISO/TS 10303-1021 Product_identification_arm ISO/TS 10303-1017 Product_version_arm ISO/TS 10303-1018 Product_view_definition_arm ISO/TS 10303-1019
NOTE 2 See Annex C, Figures C.1and C.2 for a graphical representation of this schema.
This subclause specifies the ARM types for this application module. The ARM types and definitions are specified below.
The product_as_individual_identification_item type is an extension of the identification_item type. It adds the data types Product_as_individual and Product_as_individual_version to the list of alternate data types.
EXPRESS specification:
*)
TYPE
product_as_individual_identification_item =
SELECT
BASED_ON
identification_item
WITH
(Product_as_individual,
Product_as_individual_version);
END_TYPE;
(*
The product_design_view_or_configuration type allows for the designation of the data types Product_configuration and Product_view_definition.
EXPRESS specification:
*)
TYPE
product_design_view_or_configuration =
SELECT
(Product_configuration,
Product_view_definition);
END_TYPE;
(*
The product_version_or_configuration type allows for the designation of the data types Product_configuration and Product_version.
EXPRESS specification:
*)
TYPE
product_version_or_configuration =
SELECT
(Product_configuration,
Product_version);
END_TYPE;
(*
This subclause specifies the ARM entities for this module. Each ARM application entity is an atomic element that embodies a unique application concept and contains attributes specifying the data elements of the entity. The ARM entities and definitions are specified below.
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.
EXAMPLE 1 The design of a personal computer is represented by a Product.
EXAMPLE 2 The personal computer with a serial number on a persons desk is represented by a Product_as_individual and an associated revision represented by Product_as_realized.
EXAMPLE 3 The personal computer that has been ordered, allocated a serial number for manufacturing planning, but not yet manufactured, is represented by a Product_as_individual and an associated revision represented by Product_as_planned.
EXAMPLE 4 HMS Daring is the first of a new class of ships known as Type 45 Destroyers. It is due to enter service in two years time.
EXPRESS specification:
*)
ENTITY Product_as_individual
SUBTYPE OF (Product);
END_ENTITY;
(*
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.
EXAMPLE 1 The car on my drive is represented by a Product_as_individual. The current configuration status of the car can be represented by a Product_as_realized related to the Product_as_individual. If a safety modification is made to the car resulting in a new configuration status of the car, then this may be represented by a new Product_as_realized.
EXAMPLE 2 HMS Daring is the first of a new class of ships known as Type 45 Destroyers. It is due to enter service in two years time.
EXPRESS specification:
*)
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;
(*
Attribute definitions:
of_product: the Product_as_individual that the Product_as_individual_version identifies a version of.
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.
EXPRESS specification:
*)
ENTITY Product_as_individual_view
SUBTYPE OF (Product_view_definition);
SELF\Product_view_definition.defined_version : Product_as_individual_version;
END_ENTITY;
(*
Attribute definitions:
defined_version: the Product_as_individual_version of which the Product_as_individual_view provides a characterization.
NOTE 1 It may be planned to make the artefact from of a version of a product design (Product_version). If this is the case, then the relationship between the artefact (Product_as_planned) and the design (Product_version) is represented by Product_design_version_to_individual.
NOTE 2 If the planned artefact (Product_as_planned) is subsequently made into an actual artefact (Product_as_realized) then they are related by the Product_planned_to_realized relationship.
EXPRESS specification:
*)
ENTITY Product_as_planned
SUBTYPE OF (Product_as_individual_version);
END_ENTITY;
(*
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.
EXPRESS specification:
*)
ENTITY Product_as_realized
SUBTYPE OF (Product_as_individual_version);
END_ENTITY;
(*
EXPRESS specification:
*)
ENTITY Product_design_to_individual;
product_design : Product;
individual_product : Product_as_individual;
END_ENTITY;
(*
Attribute definitions:
product_design: the design of the product that is being made.
individual_product: the product that has been or is planned to be made from this design.
EXPRESS specification:
*)
ENTITY Product_design_version_to_individual;
product_design_version : product_version_or_configuration;
individual_product : Product_as_individual_version;
END_ENTITY;
(*
Attribute definitions:
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.
EXPRESS specification:
*)
ENTITY Product_design_view_to_individual;
product_as_individual_view : Product_as_individual_view;
product_view_definition : product_design_view_or_configuration;
END_ENTITY;
(*
Attribute definitions:
product_as_individual_view: the product as individual view represented by a Product_as_individual_view entity.
product_view_definition: the product design, that is either a Product_view_definition or a Product_configuration.
EXPRESS specification:
*)
ENTITY Product_planned_to_realized;
planned_product : Product_as_planned;
realized_product : Product_as_realized;
END_ENTITY;
(*
Attribute definitions:
planned_product: the planned product represented by a Product_as_planned entity.
realized_product: the realized product represented by a Product_as_realized entity.
*)
END_SCHEMA; -- Product_as_individual_arm
(*
© ISO 2011 — All rights reserved