ISO 10303-44:1994

Industrial automation systems and integration — Product data representation and exchange — Part 44: Integrated generic resources: Product structure configuration

Systèmes d'automatisation industrielle et intégration — Représentation et échange de données de produits — Partie 44: Ressources génériques intégrées: Configuration de structure de produits

General Information

• Status: Withdrawn
• Publication Date: 14-Dec-1994
• Withdrawal Date: 14-Dec-1994
• ICS: 25.040.40 - Industrial process measurement and control
• Technical Committee: ISO/TC 184/SC 4 - Industrial data
• Drafting Committee: ISO/TC 184/SC 4/WG 12 - STEP product modelling and resources
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 02-Apr-2012
• Completion Date: 12-Feb-2026

Relations

• Corrected By: ISO 10303-44:1994/Cor 1:1999 - Industrial automation systems and integration — Product data representation and exchange — Part 44: Integrated generic resources: Product structure configuration — Technical Corrigendum 1
• Effective Date: 06-Jun-2022
• Revised: ISO 10303-44:2000 - Industrial automation systems and integration — Product data representation and exchange — Part 44: Integrated generic resource: Product structure configuration
• Effective Date: 15-Apr-2008
• Parent: ISO 10303-44:1994/Cor 1:1999 - Industrial automation systems and integration — Product data representation and exchange — Part 44: Integrated generic resources: Product structure configuration — Technical Corrigendum 1
• Effective Date: 15-Apr-2008

Standards Content (Sample)

INTERNATIONAL
ISO
STANDARD
10303-44
First edition
1994-12-15
Industrial automation Systems and
integration - Product data representation
and exchange -
Part 44:
Integrated generic resources: Product
structure configuration
Sys t&mes d ‘a u toma tisa tion industrielle et in tkgra tion - Repksen ta tion
et khange de donnees de produits -
Partie 44: ßessources gbnbiques integrees: Configuration de structure de
produits
Refet-ence number
ISO 10303-44: 1994(E)
Page
Contents
.........................................................
1 Scope
...............................................
2 Normative references
..........................................
3 Definitions and abbreviations
.............................................
4 Product structure Schema
.................................................
4.1 Introduction
.................................
4.2 Fundamental concepts and assumptions
.............................. 1
4.3 Product structure Schema entity definitions
alternategroduct relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1
product definitioi usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2
- -
make from usageoption . . . . . . . . . . . . . . . e . . . . . . . . . . . . . . . . . . . . . .
4.3.3
make-from-usage Option group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4
- -
- -
4.3.5 assembly component usage . . . . . . . . . . . . . . . s . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . o . . . e . . . . . . . . . . . . . . . 13
4.3.6 quantified assembly component usage
- - -
4.3.7 next assembly usage occurrence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-
-
4.3.8 specified higher usage-occurrence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.9 promissory usage occurrence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
- -
4.3.10 assembly component usage Substitute . . . . . . . . . . 0 . . . . . . . . a e . . . . . . . .
- - -
............................................. 19
5 Product concept Schema
................................................. 19
5.1 Introduction
.................................
5.2 Fundamental concepts and assumptions
concept .
5.3 Product concept Schema entity definitions: product
-
...................................... 20
6 Configuration management Schema
.................................................
6.1 Introduction
................................. 22
6.2 Fundamental concepts and assumptions
........................
6.3 Configuration management Schema entity definitions
.......................................... 22
6.3.1 configuration item
......................................... 23
6.3.2 configuration-design
...................................... 24
6.3.3 configuration-effectivity
-
0 ISO 1994
All rights reserved. Unless otherwise specikl, no part of this publication may be reproducecl or
utilized in any form or by any means, electronie or mechanical, including photocopying and
microfilm, without permission in writing from the publisher.
International Organkation for Standardkation
Case Postale 56 l CH-1 211 Geneve 20 l Switzerland
Printed in Switzerland
ii
ISO 10303=44:1994(E)
%O
Annexes
A Short names of entities . . . . .
B Information Object registration .
.......................................... 27
B. 1 Document identification
.......................................... 21
B.2 Schema identification e
C Computer-interpretable listings . . . e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
D Graphical model representations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
....................................................... 33
EExamples
E.l Introduction
.................................................
E.2 Example of a mechanical assembly product .
E.3 Examples of product structure reports 33
.................................
E.3.1 Example: A numeric, multi-level, indented product structure report . 35
E.3.2 Example: A labelled occurrence, multi-level, indented product structure report . 36
E.3.3 Example: A numeric, multi-level, indented, extended product structure report . 37
E.4 BOM and Parts list data structures .
E.4.1 BOM data structure 37
E.4.2 Parts list data structure . : : : : : : 38
..................................................................
E.5 Representation of product structure data structures using Part 44 entities .
E.6 Generating product structure reports 45
..................................
E.7 Summary . 45
F Bibliography . . . . . . . . . . . . . . . . . . . e . . . . . . . . . . . . . e . . . . . . . . . . . . . . . . . . . 47
Index. 48
Figures
FigureE.1 -Part44exampleproduct 34
......................................
Figure E.2 - Part 44 example product: graphical product structure . 35
Figure E.3 - BOM data structure for Part 44 example product . 38
Figure E.4 - Parts list data structure for Part 44 example product . 39
Figure E.5 - BOM data structure examples using Part 44 entities . 40
Figure E.6 - Parts list structure examples using Part 44 entities . 41
Figure E.7 - BOM data structure of Part 44 example product 42
.........................
Figure E.8 - Simple specified higher usage occurrence 43
............................
Figure E.9 - Identifying specific usages with specified higher usage occurrence .
Figure E.10 - Complex specified higher usage occurrence 46
.........................
Tables
Table 1 - Example 8 Make from usage Option group . . . . . . . . . . . e . . . . . . . . . . . . . . . . 11
Table 2 - Example 9 Make-from-usage-Option-group . . . . . . . . e . . . . . . . . . . . . . . . . . . . 11
- - - -
. . .
QIso
ISO 10303=44:1994(E)
Foreword
The International Organization for Standardization (ISO) is a worldwide federation of national Standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Esch member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO
collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
Draft International Standards adopted by technical committees are circulated to the member bodies for
voting. Publication as an International Standard requires approval by at least 75% of the member bodies
casting a vote.
International Standard ISO 1030344 was prepared by Technical Committee ISO TC184, Inckustrial
Subcommittee SC4, Industrial data and global manufacturing
automation systems and integration,
languages.
ISO 10303 consists of the following Parts under the general title Industrial automation systems and
integration - Product data representation and exchange:
- Part 1 Overview and fundamental principles;
- Part 11 Description methods: The EXPRESS language reference manual;
- Part 21 Implementation methods: Clear text encoding of the exchange structure;
- Part 22 Implementation methods: Standard data access interface;
- Part 31 Conformance testing methodology and framework: General concepts;
- Part 32 Conformance testing methodology and framework: requirements on testing laboratories and
cl ients;
- Part 41 Integrated generic resources: Fundamentals of product description and support;
- Part 42 Integrated generic resources: Geometrie and topological representation;
- Part 43 Integrated generic resources: Representation structures;
- Part 44 Integrated generic resources:
Product structure configuration;
- Part 45 Integrated generic resources: Materials;
- Part 46 Integrated generic resources: Visual presentation;
- Part 47 Integrated generic resources: Shape Variation tolerantes;
Process structure and properties;
- Part 49 Integrated generic resources:
iV
ISO 10303=44:1994(E)
OISO
- Part 101 Integrated application resources: Draughting;
- Part 104 Integrated application resources: Finite element analysis;
- Part 105 Integrated application resources: Kinematics;
- Part 201 Application protocol: Explicit draughting;
- Part 202 Application protocol: Associative draughting;
- Part 203 Application protocol : Configuration controlled design;
- Part 207 Application protocol : Sheet metal die planning and design;
- Part 210 Application protocol : Printed circuit assembly product design data;
- Part 213 Application protocol: Numerital control process Plans for machined Parts.
The structure of this International Standard is described in ISO 10303-1. The numbering of the Parts of
this International Standard reflects its structure:
- Part 11 specifies the description method;
- Parts 21 and 22 specify the implementation methods;
- Parts 31 and 32 specify the conformance testing methodology and framework;
- Parts 41 to 49 specify the integrated generic resources;
- Parts 101 to 105 specify the integrated application resources;
- Parts 201 to 213 specify the application protocols.
Should further Parts be published, they will follow the Same numbering Pattern.
Annexes A and B form an integral part of this part of ISO 10303. Annexes C, D, E and F are for
information onlv.
Diskette
Users should note that this part of ISO 10303 comprises a diskette:
the short names of entities given in annex A are also included on the diskette;
- the EXPRESS listings (annex C) are provided on the diskette only;
a method to enable users to report errors in the documentation is given. Full details arc
provided in the file.
V
wo
ISO 10303=44:1994(E)
Introduction
ISO 10303 is an International Standard for the computer-interpretable representation and exchange of
product data. The objective is to provide a neutral mechanism capable of describing product data
throughout the life cycle of a product independent from any particular System. The nature of this
description makes it suitable not only for neutral file exchange, but also as a basis for implementing and
sharing product databases and archiving.
This International Standard is organized as a series of parts, each published separately. The parts of ISO
10303 fall into one of the following series: description methods, integrated resources, application
protocols, abstract test suites, implementation methods, and conformance testing. The series are described
in ISO 10303-1. This part of ISO 10303 is a member sf the integrated resources series. Major
subdivisions of this part of ISO 10303 are:
- the product structure Schema;
- the product concept Schema;
- the configuration management Schema.
The product structure Schema:
- defmes a product in terms of its composition as a set of constituents or consumed products. A
product may be assembled from the constituents or produced by consuming other products, or both;
- defines mechanisms for expressing the composition relationship.
The product concept Schema identifies the product concept as a set of specifications for a product derived
from analysis of customer needs for the product. It represents the idea of a product based on customer
nee& and not as it might be designed or built.
The configuration management Schema identifies those products participating in the manufacture sf
another product whose configurations are under the direct control of an organization.
Industrial automation is concerned with the management of the information including the following:
- product structure and its complexity;
- product configuration and its complexity;
- product Change.
Product structure is focussed on that aspect of product design defining a product in terms of a nested
decomposition into constituents. The product structure Schema of this part and the product definition
Schema of ISO 10303-41 together define the representation of the information that manages the
complexity of product structure. An example of the use sf the information represented is the generation
of bill-of-material reports.
vi
ISO’ 10303=44:1994(E)
Vi0
Product configuration is concerned with the specification of manufacturing or assembly Plans for specific
products. The planning includes specification of the actual constituents of a product which are to be
included in a planned unit of production. The configuration management Schema and the product
structure Schema represent the information that manages the configuration of a product. The concept of
effectivity is used to manage the configuration of a product.
Change management is involved with the changes over time in a product as new Versions of a product
are developed. This part of ISO 10303 is concerned with changes that affect the organization of
constituents into interrelated structures. The configuration management Schema represents information
on the structural form of the definition of a product as the product changes and is enhanced during the
product life cycle. Representation of information on other aspects of Change management is defined in
the product definition Schema and the Change Schema of ISO 1030341.
vii
This page intentionally left blank

ISO 1030344: 1994(E)
INTERNATIONAL STANDARD *ISO
Industrial automation Systems and integration -
Product data representation and exchange -
Part 44:
Integrated generic resources:
Product structure configuration
1 Scope
This part of ISO 10303 specifies the resources to manage the structure and configuration of a product
during its life cycle.
The following arc within the scope of this part sf ISO 10303:
- the relationship among the components and assemblies of a product;
- the relationship among products and their components as made by modification of other products;
EXAMPLE 1 - The machining of a product from another product.
- the description sf a product as defined by customer needs;
- the management of the structure for configuration of assemblies and components as planned for
manufacture;
- the decomposition of a product to support different product life cycle activities;
NOTE 1 - An Organkation may need to decompose a product into one bi11 of materials that enumerates
each component with respect to the number of that component used in an assembly, and into a second bi11
of materials that decomposes a product with multiple assemblies into the individual components.
See annex E for more examples of different product structure reports that are supported.
- multiple Versions of a Single product which are equivalent with respect to form, fit, and function.
The following are outside the scope of this part of ISO 10303:
- the relationships among different product definitions for the Same product;
EXAMPLE 2 - The relationship of a product definition for a component in a preliminary design to a
corresponding product definition for the same component in a detailed design;
- administrative activities of the product life cycle including approvals, security classifications,
contractual arrangements, and supplier organizations;
OISO
- the Change process for a product, including the reason for Change and what aspect of a product has
changed;
- the decisions made, and their reasons, during the product life cycle;
- the physical connections among components sf a product;
- the properties that a product constituent may have;
NOTE 2 - A mechanism is defined in ISO 18303-41 to support the association of properties with
components. The actual associations are included in various application protocols which are Parts of this
International Standard. For example, the details of what a material property is and how it is defined are out
of scope, as well as the fact that a component has a material property.
- the information for as-built manufacturing, manufacturing planning, and logistical structure and
configurations;
- multiple Versions of a Single product that are not form, fit, and function equivalent.
NOTE 3 - The concept of Versions of a product is defmed in ISO 10303-41.
2 Normative references
The following Standards contain provisions which, through reference in this tewt, constitute provisions
of this part of ISO 10303. At the time sf publication, the editions indicated were valid. All Standards
are subject to revision, and Parties to agreements based on this part of ISO 10303 are encouraged to
investigate the possibility of applying the most recent editions sf the Standards indicated below. embers
of IEC and ISO maintain registers of currently valid International Standards.
ISO/IEC 8824-1: J> Information technology - Open Systems Interconnection - Abstract Syntax
- Part 1: Specification of Basic Notation
Notation One (ASN. i)
ISO 10303-1: 1994, Mustrial automation systems and integration -- Product data representation and
exchange - Part 1: Overview andjbuiamental principles.
- Product data representation and
ISO 10303- 11: 1994, Industrial automation systems and integration
exchange - Part 11: Description methods: ?he EXPRESS language reference manual.
ISO 1030341: 1994, Industrial automation systems and integration - Product data representation and
exchange - Part 41: Integrated generic resources: Fundamentals of product description apuil support.
ISO 10303-42: 1994, Industrie21 automation systems and integration - Product data representation and
Part 42: Integrated generic resources: Geometrie and topological representation.
exchange -
ISO 10303-43: 1994, Industrial automation systems and integration - Product data representation and
Part 43: Integrated generic resources: Representation structures.
exchange -
IN To be published.
WO
3 Definitions and abbreviations
3.1 Terms defined in ISO 103034
This part of ISO 10303 makes use of the following terms defined in ISO 10303-1.
- assembly;
- component;
- product.
3.2 Other definitions
For the purposes of this part of ISO 10303, the following definitions apply.
3.2.1 ancestor nsde: any node that tan be reached from a given node, by successive traversals of links
in the reverse direction. For a given node, its ancestor nodes include all parent nodes, all parent nodes
of these parent nodes, etc.
3.2.2 bill-of-material structure (BOM): a structural description of a product in terms of its nested
constituents.
NOTE - See annex E for examples of bill-of-material structures.
3.2.3 Child node: the node to which a link is pointing.
3.2.4 constituent: a subdivision of a product, either a component or an assembly.
3.2.5 directed acyclic graph (DAG): a collection of nodes and directed links such that no node is an
ancestor (or descendant) of itself.
3.2.6 descendent node: any node that tan be reached from a given node, by successive traversals of
links. For a given node, its descendent nodes include all children nodes, all children nodes of these
children nodes, etc.
3.2.7 effectivity: a characteristic that indicates when a product is allowed, approved or permitted to be
used in another product.
3.2.8 ferm, fit, and functisn of a product: the form is the shape of the product, the fit is the way the
product interfaces with other products, and the function is the purpose that the product serves.
3.2.9 leaf node: a node that has no children.
3.2.10 link: a unidirectional relationship from onenode to another node within a directed acyclic graph.
3.2.11 lot: a collection of actual units treated as a Single unit.
vm
ISO 10303=44:1994(E)
3.2.12 node: an element of a directed acyclic graph, connected to other such elements by links.
3.2.13 parent node: the node from which a link is initiated.
3.2.14 Parts list structure: a structural description sf a product in terms sf a hierarchy of all distinct
usages of its constituents.
NOTE - See annex E for cases of Parts list stmctures.
3.2.15 promissory use: the intention to use a constituent in an assembly.
3.2.16 root node: a node that has no parents.
3.2.17 tree: a restricted type of directed acyclic graph in which there is only one root node, and in
which each node has at most one parent.
3.3 Abbreviations
For the purposes of this part of ISO 10303, the folbwing abbreviations apply.
BOM bill-of-material.
management.
CM configuration
DAG directed acyclic graph.
4 Product structure Schema
stmcture Schema and identifies the necessary
The following EXPRESS declaration begins the product
- -
external references.
EXPRESS specification:
*
)
SCHEMA product structure schema;
- -
definition schema
REFERENCE FROM product
- -
(product,
product definition relationship,
acyclicZproduct_deFinition_relationship);
REFERENCE FROM measure schema
(measure with unit);
- -
REFERENCE FROM support resource schema
(identifier, label,-text); -
*
(
OISO ISO 10303=44:1994(E)
NOTE - The schemas referenced above tan be found in the following Parts of ISO 10303:
product definition Schema ISO 103034
- -
measure schema ISO lO303-41
-
support resource Schema ISO 103034
- -
4.1 Introduction
the definitions of:
The subject of the product s tructure Schema is the relationship between
-
- products which are assembled to make other products;
- products which are changed to make other products.
These relationships are defined as specialisations of relationships among product definitions as specified
in the product definition Schema sf ISO 10303-41. In addition, any product that is used in a product
structure may have alternaive products specified for that use. Collectively these relationships are referred
to as a product structure.
The product structure defines the different methods by which a product tan be represented as being made
up of constituents. Product structure relationships are established among the constituents that make up
a product. Product structure is an aspect of product definition.
The relationships between product definitions are specializations of the general relationship among product
definitions in the product definition Schema of ISO 10303-41. They are represented in this International
Standard using a subtype of the product definition relationship entity as defined in the product
definition Schema of ISO 10303-41. The sibtypes of iroduct detinition relationship defined in this
Schema establish additional constraints and meanings to the Supertype in ISO 1030341.
The product structure concept applies to multiple definitions of the structure of a Single product Version.
The different definitions correspond to different organization requirements for defining the structure of
a product during the life cycle of the product ’s development.
EXAMPLE 3 - An Organkation may define a bill-of-material for both a design engineering release life cycle
activity, as weil as for a manufacturing engineering activity.
This Schema supports the concept of making a product from another product. This concept deals with the
relationship between a product and the results of a process applied to that product which produces a new
product.
The product structure Schema develops the following specific concepts for use in representing the
-
various forms of product structure:
- the alternate product relationship is used to convey the information that two products have a
relationship whereby one product may be used in the place of another product;
represents the fact that any actual unit of one design tan be
- the make from usage Option
- - -
manufactured by consuming or modifying an actual unit of another design;
NOTE 1 - Typically the consumed product is referred to as stock or raw material.

- the make from usage Option group is used to represent one specific combination of products that
tan be madefrom ä Single produ;;
NOTE 2 - Typically the Single product is referred to as stock or raw material.
the assembly component usage establishes relationships between designs within one of four
-
different subtypesr
a) The quantifiedassembly-component-usage represents the relationship between a constituent
and an assembly. For discrete constituents, several occurrences of the constituent are represented
by the Single constituent and the quantity representing the number of occurrences of it. For non-
discrete constituents the quantity represents a unit of measure other than a unitless number;
b) The next assembly usage occurrence represents the relationship between an occurrence of a
constituent Gd its immediate assembly;
c) The specified higher usage occurrence represents the relationship between a specific use of a
constituent with-respect- to a ion-immediate/non-parent ancestor assembly within the product
structure;
d) The promissory usage occurrence represents the relationship between a constituent and an
- -
ancestor assembly within an Overall product structure without any specification of the intermediate
assemblies being represented.
4.2 Fundamental concepts and assumptions
Product structures are modelled by directed acyclic graphs (DAG). In these models, nodes represent
product definitions, and the directed links represent composed-of relationships. In this Schema, nodes
correspond to product definition entities and the links correspond to assernhly component wage
- - -
entities.
NOTE 1 - For a detailed discussion of graph theory, sec [ B]+
Many forms of product structure tan be represented using this Schema. ‘RVO product structures of special
Utility are bill-of-material and Parts list structures.
NOTE 2 - Examples and diagrams of th e manner in which the entities of this part may be used to represent
product structures are included in annex E.
A parts list structure is a specific form of a bill-of-material that ca-n be represented by a tree. bill-of-
material structure may require a more general DAG.
For a general product structure, in Order to identify the usage of any constituent within an assembled
product, it is necessary to identify the path between the assembled product and the constituent. The
specified higher usage occurrence entity provides this capability.
- - -
ISO 10303=44:1994(E)
OISO
4.3 Product structure Schema entity definitions
4.3.1 alternate product relationship
- -
The alternste product relationship is used to convey the information that two products have a relationship
whereby one product, ehe alternste product, may be used in the place of another product, the base
product.
When one product is an alternate for another product it is understood that there is no interest within the
organization to keep track of which product, the base or any alternstes specified, is used as a particular
instance sf the base product within a product structure.
NOTE - An organization may track design changes for a base Part, and establish effectivity conditions for the
use of that base part in various assemblies to be manufactured. The use of an altemate product implies that
an organization does not specify any particular version of the altemate product or establish effectivities relating
to it.
The two products specified in the entity are equivalent with respect to form, fit, and function, as
determined by the organization.
EXAMPLE 4 - Two screws of the same size are products. One screw has a Cross head and the other has a
straight head. These head shapes are properties of the respective products. Within a particular organization,
the two screws are considered equivalent with respect to form, fit, and function: they both have sufficiently
close physical shape, they take up the same space when used, and they both serve to fasten two things
together. Thus, one of these two screws could be considered to be an altemate part. for the other screw. A
.
different organization might consider the formsto be different.
The use of the alternate psoduct refationship entity shall be defined in the context of the product
structure of the base produ&. The relationship established by the use of alternate
product relationship
- -
need not be symmetric. If B is an alternate product for A, it is not required that A is also an alternate
product for B.
EXPRESS snecification:
*
ENTITY alternate product-relationship;
name : label;
definition: text;
alternate : product;
base : product;
basis : text;
UNIQUE
URl: alternate, base;
WHERE
WRl: alternate SB: base;
END ENTITY;
* -
(
OISO
Attribute defmitions:
alternste: a product that may be used in place of the base product.
base: a product for which another product may be used as an alternate.
basis: a text description to specify the rationale and domain of applicability of the alternate product.
Formal nronositions:
URl: The combination of the alternate product and the base product shall be unique.
WRl: The instance for the alternate shall not be the Same as the instance of the base attribute.
4.3.2 product definition usage
- -
The product definition usage is a specialization of the product definition relationship entity of ISO
10303-41 for-use withinhe context of product structure definitioi and management. This specialization
related product definition.
adds meaning to the two attributes: relating product definition,
- - - -
The subtypes of this entity represent different kinds of product structure relationships between the
referenced pair of product defini tions. One subtype, make from usage Option, represents the
-
relationship between a product and another product, where one product isiade from the other. The other
subtype, assembly component usage, represents the relationship between an assembly and one of its
- -
constituents.
EXPRESS specification:
*
)
product definition usage
ENTITY
SUPE R ,TYPE OF-(ONEOF (make from usage Option,
assembly Compon Znt usag
e) 1
SUBT Y PE OF (product definitioz relat ionship)
P
- -
UNIQUE
URl: SELF\product definition relatio nship-id
SELF\product-definition-relatio nship.re Rating product definition,
SELF\product-definition-relatio nshipxe lated product definition;
- - - -
WHERE
WRl: acyclic product definition rel ationshi
P
-
(SELF,- -
definition],
[SELF\product definition relationship.related product
'PRODUCT STRUCTURE SCHEMÄ.PRODUCT DEFINITION ÜSAGE.' +
-
-
'RELATED-PRODUCT DEFINITION');
- -
END ENTITY;
* -
(
Attribute definitions:
SELF\product definition relationship.id: An identifier for a usage of a product definition. It is used
definition usage where the pair of product definition
to distinguish between twoinstances of product
- - -
attributes are the Same.
wo ISO 10303=44:1994(E)
EXAMPLE 5 - If four identical bolts are used to attach two plates, there may be a need to identify one
specific bolt for some purpose. It ne& to be torqued to a greater degree than the rest. The id attribute then
is used to identify this specific bolt ’s requirement, even though all four bolt product definition usages will
-
have the same attribute pair of product definitions.
-
SELAproduct defmition relationship.reIating product definition: a product definition that is made
-
from or serves& the asseibly for the related Foduct definition.
- -
SELAproduct definition relationship.related product definition: a product definition from which
the relating priduct definition is made or whGh is the component in the relatiig product definition
-
assembly. - -
Formal txonositions:
product defhition, and related product defhition uniquely identify
URl: The inherited id, relating
- - - -
an instance of product-definition-usage.
WRl: The graph structure of product definition nodes and product definition usage links shall be
acyclic. Esch product definition sha16not be a descendant of itself inthe graph &ucture.
-
definition relationship defined in ISO 10303-41.
NOTE - This rule uses the function acyclicgroduct
- -
4.3.3 make from usage Option
- - -
The make from usage Option identifies that a product is made from another product through machining
- - -
or some other unspecified process.
In situations in which a product is made from another product using a sequence of processes, the
intermediate products will be related using the make from usage
Option entity.
- - -
A product to be modified tan be an assembly.
NOTE 1 - Generally, the assembly component usage differs from the make from usage Option in that the
- - -
constituents of an assembly are us& in the ass&nbly without any Change.
A make from usage Option applies to designs, represented by product definitions, rather than the
- -
actual units ofthe designs. A make from usage Option relationship isindependent of any specific
manufactured instances of actual unitsand is-repres&ed by the attribute references, inherited from the
Supertype entities, to the relating product definition and related product definition.
- - - -
A product definition may be the relating product definition of many make from usage Option
relationshipi, and a product definition may be the rehed product definition ofmany-make jrom -
usage Option relationships.- Further, there may be multiple make from usage Option mstanc&
definition and related product defizition iair of product -
refereicing the Same relating product
- - - - -
defini tions.
EXAMPLE 6 - Consider the case of a shaft which tan be machined from either a casting or a forging. All
three, the shaft, the forging and the casting, are represented by separate instances of product definitions.
usage Option entity exist, one between the relatinggroduct definition
Two instances of the make from
- - - -
OISO
ISO 10303=44:1994(E)
shafi and the relatedgroduct-definition forging, the other between the relatinggroduct definition shafi
-
and the relatedgroduct-definition casting.
EXPRESS sPecifkation:
*
ENTITY make from usage Option
SUBTYPE OF (prÖduct definition-usage);
ranking :-INTEGER;
ranking rationale : text;
qyantity : measure with unit;
-
WHERE
WRl: ranking > 0;
END ENTITY;
*-
(
Attribute definitions:
definition made from
SELF\product definition relationshipxelating product definition: a product
-
the related product defir-&ion product. - -
- -
definition from which
SELNproduct definition relationship.related product definition: a product
-
- -
the relating priduct defiiition is made.
- -
ranking: an integer which ranks the preference for use of the related product definition input
product definition among all make from usage Option instances with the same value for the inherited
relating-product definition attribute. fiis is ä positive integer value that only has meaning when
-
comparing it with corresponding values for make from usage Options sharing the Same relating -
product definition product definition. It is a relative r&king v&e, not an absolute ranking. A lowr
- -
product definition product definition, and a higher
value indicates a higher preference for the related
- - -
value indicates a lower preference.
NOTE 2 - Special care is required when assigning these values. If different organizations use different ranges
of values, and if populated data sets from these organizations are merged, and multiple xnake~from~usage~-
definition
Options from both organizations then exist in the merged file for a Single relatinggroduct
-
product definition, then non-comparable vaiues for this attribute may res&.
-
ranking rationale: text which describes the rationale used for the ranking.
-
EXAMPLE 7 - Examples of ranking rationale are tost and lang lead time.
-
quantity: the number of physical instances of the relating product definition product definition that
- - -
tan be made from one unit of a related product definition product definition.
- - -
Formal propositions:
WRl: The value of ranking shall be positive.
ISO 10303=44:1994(E)
OISO
Informal DroDositions:
IPl: If make from usage option.quantity.value
component is represented by a NUMBER then its
value shall begreaterthan Ö.
Option group
4.3.4 make from usage
- - -
The make from usage Option group is used to indicate that several different products may be made
from a siigie pGduct.A make from usage Option group instance shall represent a collection of
make from usage Option instances thät defin& one bssible combination of product definitions that
- - - -
tan be made from another Single product
definition.
-
The Single product constraint is represented by the fact that the related product definition product -
definitions for all of the instances of the make from usage Options within a singlemake
from usage--
- - -
Option group collection shall be the Same. - - -
-
EXAMPLE 8 - Suppose a bar stock, represented by product definition D, tan be tut twice so as to create
three relatingqroduct definition products, X, Y, and 2.
The make from usage optiongroup
representing this Situation would aggregate three make from usage Options ac sho& in tagle 1:
- - -
Table 1 - Example 8 Make from
usage Option group
- - -
-
id
relatingqroduct - relatedqroduct - quant ity
definition - definition -
l I I
1 X D 1
I ,
2 Y D
3 Z D
It is possible to use a product to make more than one combination of other products.
EXAMPLE 9 - The bar stock product definition D may also be tut to produce two product definitions
X and one product definition T. In thG case the corresponding make from usage optionxioup would
aggregate the follo&#ing make from usage Options, shown in table 2: - - -
- - -
Table 2 - Example 9 Make from usage Option
group
- - - -
F ,
id relatingqroduct - relatedgroduct - quantity
definition - definition -
r
l
2 X D 2
L
1 T D 1
4 1
A Single make from usage Option instance may be part of multiple make from
usage Option groups.
-
- - - - - -
OISO
ISO 10303=44:1994(E)
EXPRESS specification:
*)
ENTHTY make-from-wage-Option-group;
members : SET [2:?] OF make from usage Option;
- -
WHERE
WRl: SIZEOF (QUERY (example <* members i
examplezelated product definition
:=: members[l].~ePated-&oduct_definition)) =SIZEOF(members);
END ENTITY;
*-
(
Attribute definitions:
product definition
members: a collection of make-from-usage-Option instances whose relating
- -
product definition.
instances tan be made from the Same related
-
-
Formal propositions:
WRl: All instances of members shall share the Same instance of product definition for their respective
-
related product definition.
- -
4.3.5 assembly component usage
-
-
component usage
The assembly component usage relates a constituent to its assembly. Title assembly
- -
entity is a subtype of the product definition usage entity that establishes a relationship between
definitions within one of thi followingthree product structures:
product
-
- bill-of-material (BOM) structure;
- Parts list structure;
- promissory use structure.
component usage entity has four subtypes specified in this part of ISO 10303:
The assembly
- -
- quantified assembly component usage;
- -
-
-
next assembly usage occurrence;
- - -
fied hi usage occurrence;
- speci gher
- - -
-
promissory usage occurren ,Ce.
- -
The quantified assembly component usage represents the relationship between a constituent and an
assembly where, for discrete constituents, several occurrences of the constituent are represented by the
Single constituent and a quantity representing the number sf occurrences of it. The quantity represents
a unit of measure other than a unitless number for non-discrete constituents. The next assemhly usage -
occurrence represents a relationship between a component and its immediate assembly in aproduk
structure. The specified higher usage occurrence shall be used to represent the explicit relationship
-
- -
ISO’ 10303=44:1994(E)
@ISO
between a descendent component and any ancestor higher-level assembly. The promissory usage -
occurrence shall be used to represent intended relationships between a lower-level constitu&t and-a
higher-level assembly, when intermediate constituents and their relationships are yet undetermined.
In a BOM structure, product definition entities represent nodes and next assembly usage occurrence
- -
or quantified assembly coiponent usage entities represent links. -
- -
In a Parts list tree structure, a product definition entity represents the root node. The next
assembly -
- -
usage occurrence entities represent nÖdes at each intermediate level of the structure. The specified--
higher usage occurrence entities enable links to higher-levels of the structure.
- -
In a promissory use structure, product definition entities represent nodes, and promissory
usage -
- -
occurrence entities represent links between the nodes.
NOTE I- In Order to allow for extensions to this entity in other Parts of ISO 10303, the SUPERTYPE clause
of this entity is only partially explicit. If the subtypes defined in this part of ISO 10303 were a complete
categorization, the SUPERTYPE clause of this entity could properly read:
SUPERTY PE OF (quantifkl assembly component usage ANDOR
ONEOF (next assembly us&e occurreie,
- -
specifkd higher usage occurrence,
promissob usagi occtkrence))
- -
EXPRESS specification:
*
)
ENTITY ass embly compo nent us
ge
SUPERTYP 'E OF (ONEOF (ne2 ssembly usage
acc urrence,
speci ied higher us
occurrence,
KP-
promi sor? usage-oc curr
'ence))
SUBTYPE lroduct defini ion üsage)j
OF (P
referenc e des ignato r
: OPT ONAE identifi er;
-
.
END ENTITY
* -
(
Attribute definitions:
SELFlproduct definition relationship.relating product definition: an assembiy for which the
- - - -
related product definition is its constituent.
- -
SELF\product definition relationship.related product definition: a constituent for which the
relating prod;t definitik is its parent assembly.
-
- -
reference designator: identifier for the assembly component usage, in addition to the id attribute
- -
inherited from the product definition relationshipr
- -
NOTE 2- The reference designator attribute may be constrained to be unique by an application protocol.
OISO
ISO 10303=44:1994(E)
y csmponent usage
4.3.6 quantified assemb
- r,- am
The quantified assembly component usage establishes the relationship between an assembly and one
of its constituek when there is a n&& to specify the quantity of the Child constituent used in the
assembly.
NOTE - Generally, for production planning or material planning purposes, several occurrences of a constituent
are lumped together, and a quantity is specified to account for the several occurrences. A typical example
would be the specifying of an occurrence of a rivet used for joining aeroplane structures and denoting the
number of such rivets used on the entire aeroplane. If each of the occurrences of the rivets used is to be
assembly usage occurrence entity may be used. As many instances of the next -
specifkd, then the next
-
- - -
of occurrences of the rivets will exist in this case.
...