ISO 10303-203:1994/Amd 1:2000

I NTERNATIONAL IS0
10303-203
STANDARD
First edition
1994-1 2-1 5
AMENDMENT 1
2000- 1 1 -01
Industrial automation systems and
integration - Product data representation
-
and exchange
Part 203:
Application protocol: Configuration
controlled design
AMENDMENT 1
Systemes d'automatisation industrielle et integration - Representation et
echange de donnees de produits -
Partie 203: Protocole d'application: Conception contrelee de configuration
AMENDEMENT 1
Reference number
IS0 10303-203:1994/Amd. 1 :2000( E)
0 IS0 2000
IS0 10303-203:1994/Amd.l:2000(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not
be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this
file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The IS0 Central Secretariat accepts no liability in this
area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General lnfo relative to the file; the PDF-creation parameters
were optimized for printing. Every care has been taken to ensure that the file is suitable for use by IS0 member bodies. In the unlikely event
that a problem relating to it is found, please inform the Central Secretariat at the address given below.
0 Is02000
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic
or mechanical, including photocopying and microfilm, without permission in writing from either IS0 at the address below or ISO's member body
in the country of the requester.
IS0 copyright office
Case postale 56 CH-1211 Geneva 20
Tel. + 41 22 749 01 1 I
Fax +41 227490947
E-mail copyright@iso.ch
Web www.iso.ch
Printed in Switzerland
ii
0 IS0 2000 -All rights reserved

I
IS0 10303-203:1994/Amd.l:2000(E)
Foreword
IS0 (the International Organization for Standardization) is a worldwide federation of national standards bodies (IS0
member bodies). The work of preparing International Standards is normally carried out through IS0 technical
committees. Each 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. IS0 collaborates closely with the International Electrotechnical
Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISOAEC Directives, Part 3.
Draft International Standards adopted by the technical committees are circulated to the member bodies for voting.
Publication as an International Standard requires approval by at least 75 YO of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this Amendment may be the subject of patent
rights. IS0 shall not be held responsible for identifying any or all such patent rights.
Amendment 1 to International Standard IS0 10303-203:1994 was prepared by Technical Committee lSO/TC 184,
Industrial automation systems and integration, Subcommittee SC 4, lndustrial data.
0 IS0 2000 -All rights reserved
iii
IS0 10303-203:1994/Amd.l:2000(E)
Introduction
This document amends IS0 10303-203:1994, Industrial automation systems and integration - Product data
representation and exchange - Part 203: Application protocol: Configuration controlled design. The corrected
document supersedes IS0 10303-203:1994.
The purpose of the modifications to the text of IS0 10303-203:1994 is to correct errors in the EXPRESS definitions
likely to cause compilation problems and to replace the object identifier for the document and the applicable
schema.
iv 0 IS0 2000 -All rights reserved

OISO IS0 10303-203:1994/Amd.l:2000(E)
Industrial automation systems and integration - Product data
representation and exchange -
Part 203:
Application protocol: Configuration controlled design
Amendment 1
Modifications to the text of IS0 10303-203:1994
Table of contents, pp. iii-iv, clause 2, p. 3, clause 5.2, pp. 89-242, annex A, pp. 270-400 and index,
pp. 482-515
The purpose of these modifications is to correct Express errors that were not detected at the time of
publication due to the immaturity of the checking tools at that time. The corrections have been
documented in change pages for readability. The following pages replace Clause 2, Clause 5.2, Annex
A and the index of IS0 10303-203:1994 in their entirety as well as pages iii and iv of the table of
contents. The net affect of these changes in the short listing is:
- corrected geometric-representation-item-3d rule
- corrected assembly shape is defined function
- corrected subtype-mandatory-shape-representation rule
- corrected cc-design-date-time-correlation function
- added USES from AICs and removed the OLD 203 entities and functions
- added dummyjri constant
- added dummy-tri constant
- added degenerate-toroidal-surface (per TC2)
- added approvalgerson-organization-constraints (to solve type pruning issue)
- added approval-date-time-constraints (to solve type pruning issue)
- removed cartesian-transformation-opertor-2d (per tc2)
- removed offset-curve-2d (per tc2)
- added property-definition-representation (per seds 57)
- added representation-relationship (per seds 57)
- added b-spline-curve (per seds 57)
- added b-spline-surface (per seds 57)
- added conic (per seds 57)
- added point-replica (per seds 57)
- added swept-surface (per seds 57)
- added oriented-closed-shell (per seds 57)
- added path (per seds 57)
- added brep-with-voids (per seds 57)
Since the long listing is generated from the short listing, the best method of presenting the long listing
is to republish it as change pages. The index is being reissued to aid in navigation of the revised short
and long listings. The clause 2 changes were made so the document references the appropriate 500
series parts.
IS0 10303-203:1994/Amd.l:2000(E) as0
4.1.1 1 part-identification . 14
4.1.12 shape . 14
4.1.1 3 source-control . 14
4.1.14 wireframe-with-topology . 15
4.2 Application objects . 15
4.3 Application assertions . 33
5 Application interpreted model . 39
5.1 Mappingtable . 39
5.2 AIM EXPRESS short listing . 89
5.2.1 Fundamental concepts and assumptions .
5.2.2 Configuration controlled design constants .
5.2.2 Configuration controlled design types .
5.2.3 Configuration controlled design entities . 105
5.2.3 Configuration controlled design imported entity modifications . 116
5.2.4 Configuration controlled design rules . 131
5.2.5 Configuration controlled design functions . 194
6 Conformance requirements . 243
6.1 Conformance class 1 entities . 244
6.2 Conformance class lb entities . 245
6.3 Conformance class 2 entities . 247
6.4 Conformance class 3 entities . 250
6.5 Conformance class 4 entities . 251
6.6 Conformance class 5 entities . 253
6.7 Conformance class 6 entities . 254
Annexes
A AIM EXPRESS expanded listing . 270
B AIM short names of entities . 401
C Protocol Implementation Conformance Statement (PICS) proforma . 412
D Implementation method specific requirements . 414
E Information object registration . 415
...................................................
E . 1 Document identification
E.2 Schema identification . 415
E.2.1 config-control-design expanded schema . 415
E.2.2 config-control-design short form schema . 415
F Application activity model . 416
F.l AAMdefinitions . 417
F.2 AAMDiagrams . 420
...
OISO IS0 10303-203:1994/Amd.l:2000(E)
G Application reference model . 423
HAIMEXPRESS-G . 431
J AIM EXPRESS listing . 471
K Application protocol usage guide . 472
K.l Usage test purposes . 472
K.2 Examplepart . 476
LBibliography . 481
Index . 482
Figures
Figure F.l . IDEFO basic notation . 416
Figure F.2 . A0 Manage product development in IDEFO . 421
Figure F.3 . A3 Develop product design in IDEFO . 422
Figure G.l . ARM diagram 1 of 7 in IDEFlX . 424
Figure G.2 . ARM diagram 2 of 7 in IDEFlX . 425
Figure G.3 . ARM diagram 3 of 7 in IDEFlX . 426
Figure G.4 . ARM diagram 4 of 7 in IDEFlX . 427
Figure G.5 . ARM diagram 5 of 7 in IDEFl X . 428
Figure G.6 . ARM diagram 6 of 7 in IDEF1 X . 429
Figure G.7 . ARM diagram 7 of 7 in IDEFlX . 430
Figure H.l . application context . AIM EXPRESS-G diagram 1 of 39 . 432
Figure H.2 . product definition . AIM EXPRESS-G diagram 2 of 39 . 433
Figure H.3 . product category . AIM EXPRESS-G diagram 3 of 39 . 434
Figure H.4 . property definition . AIM EXPRESS-G diagram 4 of 39 . 435
..................... 436
Figure H.5 . property representation . AIM EXPRESS-G diagram 5 of 39
. shape representation relationship . AIM EXPRESS-G diagram 6 of 39 . 437
Figure H.6
. representation . AIM EXPRESS-G diagram 7 of 39 . 438
Figure H.7
Figure H.8 . geometric representation items . AIM EXPRESS-G diagram 8 of 39 . 439
Figure H.9 . topological representation items AIM EXPRESS-G diagram 9 of 39 . 440
Figure H.10 . point . AIM EXPRESS-G diagram 10 of 39 . 441
Figure H.11 . geometric orientation . AIM EXPRESS-G diagram 11 of 39 . 442
Figure H.12 . curve . AIM EXPRESS-G diagram 12 of 39 . 443
Figure H . 13 . conic . AIM EXPRESS-G diagram 13 of 39 . 444
Figure H.14 . bounded curves . AIM EXPRESS-G diagram 14 of 39 . 445
Figure H . 15 . surface curve . AIM EXPRESS-G diagram 15 of 39 . 446
Figure H.16 . b-spline curve . AIM EXPRESS-G diagram 16 of 39 . 447
Figure H.17 . surface . AIM EXPRESS-G diagram 17 of 39 . 448
iv
IS0 10303-203:1994/Amd.l:2000(E) @IS0
2 Normative references
The following standards contain provisions which, through reference in this text, constitute provisions of
this International Standard. At the time of publication, the editions indicated were valid. All standards
are subject to revision, and parties to agreements based on this International Standard are encouraged to
investigate the possibility of applying the most recent editions of the standards indicated below.
Members of the IEC and IS0 maintain registers of currently valid International Standards.
IS0 3 1 : 1992, Quantities and units.
IS0 1000: 1992, SI units and recommendations for the use of their multiples and of certain other units.
ISO/IEC 8824-1 : 1998, Information technology - Abstract Syntax Notation One (ASN. I): Specification
of basic notation.
IS0 10303-1 : 1994, Industrial automation systems and integration - Product data representation and
exchange - Part I: Overview and fundamental principles.
IS0 10303-1 1 :1994, Industrial automation systems and integration - Product data representation and
exchange - Part 11: Description methods: The EXPRESS language reference manual.
IS0 10303-21 : 1994, Industrial automation systems and integration - Product data representation and
exchange - Part 21: Clear text encoding of the exchange structure.
IS0 10303-3 1 : 1994, Industrial automation systems and integration - Product data representation and
exchange - Part 31: Conformance testing methodology and framework: General concepts.
IS0 10303-41 : 1994, Industrial automation systems and integration - Product data representation and
exchange - Part 41: Integrated generic resources: Fundamentals of product description and support.
IS0 10303-42: 1994, Industrial automation systems and integration - Product data representation and
exchange - Part 42: Integrated generic resources: Geometric and topological representation.
IS0 10303-43: 1994, Industrial automation systems and integration - Product data representation and
exchange - Part 43: Integrated generic resources: Representation structures.
IS0 10303-44: 1994, Industrial automation systems and integration - Product data representation and
- Part 44: Integrated generic resources: Product structure configuration.
exchange
as0 IS0 10303-203: 1994/Amd.l:2000(E)
IS0 10303-501, Industrial automation systems and integration Product data representation
and exchange I Part 501: Application interpreted construct: Edge-based wireframe.
IS0 10303-502, Industrial automation systems and integration I Product data representation
and exchange I Part 502: Application interpreted construct: Shell-based wireframe.
IS0 10303-507, Industrial automation systems and integration - Product data representation and
exchange I Part 507: Application interpreted construct: Geometrically bounded surface.
IS0 10303-509, Industrial automation systems and integration - Product data representation and
exchange I Part 509: Application interpreted construct: Manifold surface.
IS0 10303-5 10, Industrial automation systems and integration - Product data representation and
exchange I Part 51 0: Application interpreted construct: Geometrically bounded wireframe.
IS0 10303-5 1 1, Industrial automation systems and integration - Product data representation and
exchange I Part 51 1: Application interpreted construct: Topologically bounded surface.
IS0 10303-5 12, Industrial automation systems and integration - Product data representation and
exchange I Part 512: Application interpreted construct: Faceted boundary representation.
IS0 10303-5 14, Industrial automation systems and integration - Product data representation and
exchange I Part 514: Application interpreted construct: Advanced boundary representation.
3a
IS0 10303-203 : 1994/Amd. 1 : 2000( E)
This Page Intentionally Left Blank
3b
IS0 10303-203: 1994/Amd.l:2000(E) @IS0
3 Definitions and abbreviations
For the purposes of this part of IS0 10303, the following definitions and abbreviations apply.
3.1 Terms defined in IS0 10303-1
This part of IS0 10303 makes use of the following terms defined in IS0 10303-1.
- abstract test suite;
- application;
- application activity model;
- application context;
- application interpreted model;
- application object;
- application protocol;
- application reference model;
- assembly;
- component;
- conformance class;
- conformance requirement;
- data;
- data exchange;
- implementation method;
- information;
- integrated resource;
- interpretation;
IS0 10303-203:1994/Amd.l:2000(E)
OISO
43) product-requires-product-category
44) product-requires-version
45) product-version-requires-approval
46) product-version-requires-person-organization
47) product-version-requires-security-classification
48) restrict-action-request-status
49) restrict-approval-status
50) restrict-certification-type
5 1) restrict-contract-type
52) restrict-date-time-role
5 3) restrict-document-type
54) restrict-person-organization-role
55) restrict-product-category-value
56) restrict-security-classification-level
57) security-classification-optional-date-time
5 8) security-classification-requires-approval
59) security-classification-requires-date-time
60) security-classification-requires-person-organization
6 1 ) start-request-requires-approval
62) start-request-requires-date-time
63) start-request-requires-person-organization
64) start-work-requires-approval
65) start-work-requires-date-time
66) subtype-mandatory-action
67) subtype-mandatory-effectivity
68) subtype-mandatory-product-context
69) subtype-mandatory-product-definition-formation
70) subtype-mandatory-product-definition-usage
7 1 ) subtype-mandatory-representation
72) subtype-mandatory-representation-context
73) subtype-mandatory-shape-representation
74) unique-version-change-order-rule
75) versioned-action-request-requires-solution
76) versioned-action-request-requires-status
5.2 AIM EXPRESS short listing
This clause specifies the EXPRESS schema that uses elements from the integrated resources and contains
the types, entity specializations, rules, and functions that are specific to this part of IS0 10303. This clause
also specifies modifications to the textual material for constructs that are imported from the integrated
resources. The definitions and EXPRESS provided in the integrated resources for constructs used in the AIM
may include select list items and subtypes which are not imported into the AIM. Requirements stated in the
IS0 10303-203:1994/Amd.l:2000(E) OISO
integrated resources which refer to such items and subtypes apply exclusively to those items which are
imported into the AIM.
EXPRESS mecification:
*)
SCHEMA config-control-design;
USE FROM application-context-schema -- IS0 10303-41
(application-context,
application-protocol-definition,
product-context,
product-definition-context,
product-concept-context) ;
USE FROM product-definition-schema -- IS0 10303-41
(product,
product-definition,
product-definition-formation,
product-definition-formation-with-specified-source,
product-definition-relationship,
product-category,
product-category-relationship,
product-related-product-category,
product-definition-with-associated-documents) ;
USE FROM product-structure-schema -- IS0 10303-44
(product-definition-usage,
assembly-component-usage,
next-assembly-usage-occurrence,
promissory-usage-occurrence,
quantified-assembly-component-usage,
specified-higher-usage-occurrence,
assembly-component-usage_substitute,
alternate-product-relationship) ;
USE FROM configuration-management-schema -- IS0 10303-44
(configuration-item,
confi.guration-design,
configuration-effectivity) ;
OISO IS0 10303-203: 1994/Amd.l:2000(E)
USE FROM product-concept-schema -- IS0 10303-44
(product-concept ) ;
USE FROM product-property-definition-schema -- IS0 10303-41
(product-definition-shape,
property-definition,
shape-aspect,
shape-aspect-relationship) ;
USE FROM product-property-representation-schema -- IS0 10303-41
(context-dependent-shape-representation,
property-definition-representation,
shape-representation,
shape-representation-relationship,
shape-definition-representation) ;
USE FROM representation-schema -- IS0 10303-43
(functionally-defined-transformation,
item-defined-transformation,
global-uncertainty-assigned-context,
mapped-item,
representation,
representation-context,
parametric-representation-context,
representation-item,
representation-map,
representation-relationship,
representation-relationship_with_transformation,
using-representations);
USE FROM geometry-schema -- IS0 10303-42
(axisl-placement,
axis2_placement_2d,
axis2_placernent_3d,
b-spline-curve,
b-spline-curve-with-knots,
b-spline-surface,
b-spline-surface-with-knots,
bezier-curve,
bezier-surface,
boundary-curve,
Cartesian-point,
IS0 10303-203: 1994/Amd.l:2000(E)
cartesian~transformation~operator~3d,
circle,
composite-curve,
composite-curve-on-surface,
composite-curve-segment,
conic,
conical-surface,
curve,
curve-bounded-surface,
curve-replica,
cylindrical-surface,
degenerate-pcurve,
degenerate-toroidal-surface,
dimension-count,
dimension-of,
direction,
ellipse,
evaluated-degenerate-pcurve,
geometric-representation-context,
geometric-representation-item,
hyperbola,
intersection-curve,
line,
offset_curve_3d,
offset-surface,
outer-boundary-curve,
parabola,
pcurve,
plane,
point,
point-on-curve,
point-on-surface,
point-replica,
polyline,
quasi-uniform-curve,
quasi-uniform-surface,
rational-b-spline-curve,
rational-b-spline-surface,
rectangular-composite-surface,
rectangular-trimmed-surface,
reparametrised-composite-curve-segment,
seam-curve,
IS0 10303-203: 1994/Amd.l:2000(E)
spherical-surface,
surface,
surface-curve,
surface-of-linear-extrusion,
surface-of-revolution,
surface-replica,
swept-surface,
toroidal-surface,
trimmed-curve,
uniform-curve,
uniform-surface,
vector) ;
USE FROM topology-schema -- IS0 10303-42
(closed-shell,
connected-edge-set,
connected-face-set,
edge-curve,
edge-loop,
face-bound,
face-outer-bound,
face-surface,
open-shell,
oriented-closed-shell,
oriented-face,
path,
POlY-loop,
topological-representation-item,
vertex-loop,
vertex-point,
vertex-shell,
wire-shell) ;
USE FROM geometric-model-schema -- IS0 10303-42
(brep-with-voids,
edge-based-wireframe-model,
faceted-brep,
geometric-curve-set,
geometric-set,
manifold-solid-brep,
shell-based-surface-model,
shell-based-wireframe-model) ;
IS0 10303-203: 1994/Amd.l:2000(E) OISO
USE FROM action-schema -- IS0 10303- 41
(action,
action-method,
action-request-solution,
action-request-status,
action-status,
action-directive,
directed-action,
versioned-action-request) ;
USE FROM certification-schema -- IS0 10303-41
(certification,
certification-type) ;
USE FROM approval-schema -- IS0 10303-41
(approval-date-time,
. approval-person-organization,
approval,
approval-status,
approval-relationship) ;
USE FROM contract-schema -- IS0 10303-41
(contract,
contract-type);
USE FROM security-classification-schema -- IS0 10303-41
(security-classification,
security-classification-level) ;
USE FROM person-organization-schema -- IS0 10303-41
(person-and-organization,
organization-relationship,
personal-address,
organizational-address,
organizational-project,
person-and-organization-role) ;
USE FROM date-time-schema -- IS0 10303-41
(date-and-time,
date,
calendar-date,
ordinal-date,
IS0 10303-203: 1994/Amd.l:2000(E)
week-of-year-and-day-date,
date-time-role);
USE FROM document-schema -- IS0 10303-41
(document-with-class,
document-usage-constraint,
document-type,
document-relationship) ;
USE FROM effectivity-schema -- IS0 10303-41
(effectivity,
serial-numbered-effectivity,
dated-effectivity,
lot-effectivity);
USE FROM management-resources-schema -- IS0 10303-41
. (approval-assignment,
certification-assignment,
contract-assignment,
date-and-time-assignment,
person-and-organization-assignment,
document-reference,
security-classification-assignment,
action-assignment,
action-request-assignment) ;
USE FROM measure-schema -- IS0 10303-41
(measure-value,
area-measure,
count-measure,
descriptive-measure,
context-dependent-measure,
parameter-value,
plane-angle-measure,
positive-length-measure,
positive-plane-angle-measure,
mass-measure,
solid-angle-measure,
volume-measure,
named-unit,
context-dependent-unit,
conversion-based-unit,
IS0 10303-203:1994/Amd.l:2000(E) OISO
si-unit,
area-unit,
length-unit,
mass-unit,
plane-angle-unit,
solid-angle-unit,
volume-unit,
measure-with-unit,
area-measure-with-unit,
length-measure-with-unit,
mass-measure-with-unit,
plane-angle-measure-with-unit,
solid-angle-measure-with-unit,
volume-measure-with-unit,
global-unit-assigned-context);
USE FROM aic-edge-based-wireframe; -- IS0 10303-501
USE FROM aic-shell-based-wireframe; -- IS0 10303-502
USE FROM aic-geometrically-bounded-surface; -- IS0 10303-507
USE FROM aic-manifold-surface; -- IS0 10303-509
USE FROM aic-geometrically-bounded-wireframe; -- IS0 10303-510
USE FROM aic-topologically-bounded-surface; -- IS0 10303-511
USE FROM aic-faceted-brep; -- IS0 10303-512
USE FROM aic-advanced-brep; -- IS0 10303-514
(*
NOTE - The schemas referenced above can be found in the following parts of IS0 10303:
application-context-schema IS0 10303-41
produc t-definition-sc hema IS0 10303-41
produc t-structure-schema IS0 10303-44
configuration-management-schema IS0 10303-44
product-concept-schema IS0 10303-44
product-property-definition-schema IS0 10303-41
product-property-representation-schema IS0 10303-41
OISO IS0 10303-203:1994/Amd.1:2000(E)
IS0 10303-43
representation-schema
geometry-schema IS0 10303-42
IS0 10303-42
geometric-model-sc hema
action-schema IS0 10303-41
IS0 10303-41
certification-schema
approval-schema IS0 10303-41
contract-schema IS0 10303-41
security-classification-schema IS0 10303-41
person-organization-schema IS0 10303-41
IS0 10303-41
date-time-sc hema
document-schema IS0 10303-41
IS0 10303-41
effectivity-schema
management-resources-schema IS0 10303-41
measure-schema IS0 10303-41
aic-edge-based-wireframe IS0 10303-501
aic-shell-based-wireframe IS0 10303-502
aic-geometrically-bounded-surface IS0 10303-507
aic-manifold-surface IS0 10303-509
aic-geometrically-bounded-wireframe IS0 10303-510
IS0 10303-5 11
aic-topologically-bounded-surface
aic-faceted-brep IS0 10303-512
IS0 10303-514
aic-advanced-brep
5.2.1 Fundamental concepts and assumptions
IS0 10303-203 is designed to be used in the configuration control of three dimensional product design data.
The fundamental concept of this schema is that the organization controls the configuration of these types of
product designs. This schema is not designed to control product designs through drawing control. It is
designed to provide a vehicle to control the configuration of the three dimensional design.
5.2.1.1 Relating the shape of a product to its configuration data
The shape of products in this part of IS0 10303 is represented by the shape-representation entity. This
entity and its subtypes define the geometric andor topological entities which make up a particular
representation type. Each mechanical part or assembly that is of interest will be given by an instance of the
product entity. Each product will, in turn, have at least one version given by an instance of the product--
definition-formation entity. Each version may have one or more definitions given by the product--
definition entity. Each definition may have its shape represented. This is done using the AIM entities by
relating the product-definition instance to the appropriate shape-representation instance. The concept
of the shape of a product-delinition is given by an instance of the entity product-definition-shape. That
shape of the product is then connected to the shape-representation entity by an instance of shape--
definition-representation. A shape-definition-representation inherits attributes from its supertype
IS0 10303-203:1994/Amd.l:2000(E) OISO
property-definition-representation that reference the shape-representation entity that contains the
characterized-definition. This
geometry and/or topology for the shape of the part and a select type called
type allows for the representation of a shape-aspect, shape-aspect-relationship or a characterized--
product-definition which is also a select type. To specify that the property of interest is the shape of the
product-definition, the product-definition-shape subtype of property-definition shall be used. The
product-definition-shape entity is constrained to use the characterized-product-definition select type.
The characterized-product-definition select type allows for the representation of a product-definition
or a product-definition-relationship via a reference through its select list. This reference ensures that the
product-definition-shape entity will be used to define the shape of a product-definition. If the property
of interest is an aspect of the shape of the product-definition or the relationship between two aspects of the
shape of the product-definition, the property-definition shall be used and its definition attribute shall
reference an instance of shape-aspect or shape-aspect-relationship. In order to specify the shape of a
product, the product-definition entity will be referenced here. The constraint
subtype-mandatory-shape-representation (see 5.2.5.73) specifies that one of the subtypes of
shape-representation shall be used to specify the shape of the part. The representation of a shape-aspect
or shape-aspect-relationship may be given by any set of representation-items.
5.2.1.2 Relating the shape of a component to the shape of its assembly
There are two methods that may be used to relate a component part's shape to the shape of the assembly part
in which it is assembled. The first method consists of defining the shape for each part (component and
assembly), and then relating the two shapes and providing the information that defines the orientation of the
component part with respect to the assembly part through a transformation. The second method consists of
defining the shape for each part (component and assembly), and then incorporating the shape of the
component directly in the shape of the assembly. The first method shall be used to relate the shapes that are
represented by different representation types. The second method may be used for the incorporation of a
components representation into the assembly's representation if the two types are the same.
Both methods employ the shape-representation and product-definition entities. The first method also
employs the product-definition-relationship, shape-representation-relationship AND
representation-relationship-with-transformation (an instance of each entity forming a complex entity
context-dependent-shape-representation
instance of the two entities with an AND relationship) and
entities. The second method employs the mapped-item and representation-map entities.
When using the first method to relate the shape of the component to the shape of the assembly, each of the
shape-representation entities that define the shapes of the component and assembly product-definitions
is related through references in the shape-representation-relationship entity. Orientation information, in
this case, will be provided by the formation of a complex instance of the shape-representation-relationship
AND representation-relationship-with-transformation entities. The representation-relationship--
with-transformation entity references a transformation which is a select type allowing the orientation to
be defined using an axk2-placement-3d entity in each representation for an item-defined-transformation
or a Cartesian-transformation-operator entity for a functionally-defined-transformation. In addition,
OISO
IS0 10303-203:1994/Amd.l:2000(E)
an instance of the context-dependent-shape-representation must be given to explicitly relate the shape--
representation-relationship that defines the relationship of the two shapes to the product-definition--
relationship that defines the assembly-component relationship between the two product-definitions.
When using the second method to relate the shape of the component to the shape of the assembly, the
shape-representation entity that defines the geometry and/or topology for the component part's shape is
referenced by an instance of a representation-map entity that is referenced by the mapping-source
attribute of an instance of the mapped-item entity. The attribute mapped-representation of the
representation-map will reference the shape-representation subtype that defines the geometric and/or
topological representation of the shape. The instance of the mapped-item entity is then added to the set of
items in the shape-representation entity that defines the geometry and/or topology for the assembly part.
5.2.1.3 Types of shape representation
This part of IS0 10303 defines eight types of representation for shapes of parts - wireframe representations
using edge based and shell based models, wireframe representations that are geometrically bounded, manifold
surface models, surface models that are geometrically bounded, faceted boundary representation solid models
and boundary representation solid models. Each of these types of representation is self contained meaning
that one type may not contain another type. Each of the types is given by a subtype of the shape--
representation entity. Each subtype contains local rules that govern the types of geometric and/or
topological entities that can be used in it. Every shape-representation must be one of the subtypes unless
it is used as the representation of the shape of an assembly used in method 1 above. In that case, the shape--
representation instance will contain only axis2-placement-3d entities in its set of items in order to define
the orientation of the components' representations in it. Since the rules in each of the subtypes will conflict
shape-representation that is referenced by a representation-map to implement
with each other, any
method 2 above must be of the same type as the shape-representation that has the mapped-item that
references that representation-map in its set of items.
5.2.1.4 Use of global rules
Many of the relationships among different entities in the integrated resource parts of IS0 10303 are specified
using the most generic cardinality of zero or more between two related entities. This cardinality means that
the relationship is optional or there may be one or more instances of a related entity that is related to a single
instance of the relating entity. This part of IS0 10303 uses global rules to constrain that cardinality. In some
cases the constraint is made to be one to one, and in some instances at least one. Examples of these rules
include contract-requires-person-organization, approval-requires-approval-date-time, and
certification-requires-approval for exactly one, and change-request-requires-person-organization
and product-requires-version for one or more.
Global rules are also used to restrict the values of STRING type attributes to be only those that are applicable
within the context of configuration controlled 3d design of mechanical parts and assemblies. Examples of
these rules are restrict-approval-status and restrict-person-organization-role.
IS0 10303-203:1994/Amd.l:2000(E) @IS0
5.2.1.5 Assignment of units
Units are assigned to the representation of shape on a global basis. This is done by the creation of an instance
of the global-unit-assigned-context. This entity contains an attribute that allows for a set of units to be
assigned to a representation-context. Each of the shape-representation entities has a context for its
representation. If units of measure are desired for a particular instance of shape-representation, then that
instance shall have a global-unit-assigned-context in its context-of-items attribute.
5.2.2 Configuration controlled design constants
EXPRESS specification:
*)
CONSTANT
(*
5.2.2.1 dummy-gri
A dummy-gri identifies a geometric-representation-item which has a null name value for use in
constructor functions.
EXPRESS wecification:
*)
dummy-gri : geometric-representation-item := representation-item(' I) 11
geometric-representation-item();
(*
5.2.2.2 dummy-tri
A dummy-tri identifies a topological-representation-item which has a null name value for use in
constructor functions.
EXPRESS specification:
*)
dummy-tri : topological-representation-item := representation-item(' I) I I
topological-representation-item0 ;
END-CONSTANT;
(*
as0 IS0 10303-203: 1994/Amd.l:2000(E)
5.2.3 Configuration controlled design types
5.2.3.1 work-item
A work-item identifies the product-definition-formation that is the result of initial design activity or a
modification to a design.
EXPRESS specification:
*)
TYPE work-item = SELECT (product-definition-formation) ;
END-TYPE;
(*
5.2.3.2 change-request-item
A change-request-item is the product-definition-formation of the part that is to be affected by the
change-request .
EXPRESS mecification:
*)
TYPE change-request-item = SELECT (product-definition-formation);
END-TY PE ;
(*
5.2.3.3 start-request-item
A start-request-item is the product-definition-formation of the part that is to be created by the start--
request.
EXPRESS specification:
*)
TYPE start-request-item = SELECT (product-definition-formation) ;
END-TYPE ;
(*
5.2.3.4 certified-item
A certified-item applies a certification to a part that is supplied by an external organization. The
certification stipulates that the external organization is qualified to produce the part.
OISO
IS0 10303-203:1994/Amd.l:2000(E)
EXPRESS specification:
*)
TYPE certified-item = SELECT (supplied-part-relationship) ;
END-TYPE ;
(*
5.2.3.5 approved-item
An approved-item assigns an approval to a product-definition-formation, product-definition,
planned-effectivity, configuration-item, security-classification, change-request, change, start--
request, start-work, certification, or contract to indicate the approval status of the selected aspect of
the design.
EXPRESS spec ification:
*)
TYPE approved-item = SELECT
(product-definition-formation,
product-definition,
configuration-effectivity,
configuration-item,
security-classification,
change-request,
change,
start-request,
s tart-work,
certification,
contract) ;
END-TYPE ;
(*
5.2.3.6 contracted-item
A contracted-item associates a particular product-definition-formation with a contract.
OISO IS0 10303-203: 1994/Amd.l:2000(E)
EXPRESS specification:
*)
TYPE contracted-item = SELECT (product-definition-formation) ;
END-TYPE ;
(*
5.2.3.7 classified-item
A classified-item applies security-classification to a particular product-definition-formation or a
relationship between two product-definitions for a particular usage.
EXPRESS specification:
*)
TYPE classified-item = SELECT
(product-definition-formation,
assembly-component-usage) ;
END-TYPE ;
(*
5.2.3.8 person-organization-item
A person-organization-item assigns a person-and-organization to a change-request, start-request,
approval, configuration-item, product, product-definition-formation, product-definition, contract,
or security-classification. The role for the person-and-organization is controlled by the cc-design--
person-and-organization-correlation function given in 5.2.6.2.
EXPRESS sDecification:
*)
TYPE person-organization-item = SELECT
(change,
start-work,
change-request,
start-request,
configuration-item,
product,
product-definition-formation,
product-definition,
contract,
security-classification) ;
IS0 10303-203: 1994/Amd.l:2000(E)
END-TYPE ;
(*
5.2.3.9 date-time-item
A date-time-item assigns a date-and-time to a product-definition, change-request, start-request,
change, start-work, approval-person-organization, contract, security-classification, or certification.
The role for the date-and-time is controlled by the cc-design-date-time-correlation function given in
5.2.6.3.
EXPRESS mecification:
*)
TYPE date-time-item = SELECT
(product-definition,
change-request,
start-request,
change,
start-work,
approval-person-organization,
contract,
security-classification,
certification) ;
END-TYPE ;
(*
5.2.3.10 specified-item
A specified-item assigns a specification to either a product-definition or a shape-aspect.
EXPRESS wecification:
*)
TYPE specified-item = SELECT
(product-definition,
shape-aspect);
END-TYPE ;
(*
@IS0 IS0 10303-203: 1994/Amd.l:2000(E)
5.2.4 Configuration controlled design entities
5.2.4.1 Configuration controlled design entity definitions
5.2.4.1.1 mechanical-context
A mechanical-context is a product-context that is applicable to those products that are mechanical.
NOTE - The use of this entity defines a viewpoint for the context of a product. It is not intended to be a
classification or categorization of a type of product. The definition of the product-context to be mechanical
using this entity is specifying the way that the product acts within the data exchange.
EXAMPLE 21 - A printed circuit assembly is defined in a mechanical context when its physical properties
such as shape are of interest, and are defined so that its fit within the assembly in which it used may be
specified. Other properties of the printed circuit assembly such as connectivity requirements and functional
requirements would not be specified in a mechanical context.
EXPRESS mecification:
*)
ENTITY mechanical-context
SUBTYPE OF (product-context);
WHERE
WR1: SELF.discipline-type = 'mechanical';
END-ENTITY;
(*
Formal propositions:
WR1: the discipline-type of the mechanical-context entity shall contain the value 'mechanical'.
5.2.4.1.2 design-context
A design-context is a product-definition-context that defines a life cycle stage of design as the frame of
reference for product-definition entities.
NOTE - A further refinement within the context of design may be made using the application-context--
element entity.
I
OISO
IS0 10303-203:1994/Amd.l:2000(E)
EXPRESS specification:
*)
ENTITY design-context
SUBTYPE OF (product-definition-context);
WHERE
WR1: SELF.life-cycle-stage = 'design';
END-ENTITY;
(*
Formal DroDositions :
WR1: the life-cycle-stage of the
...