ISO 10303-1:2024

International
Standard
ISO 10303-1
Third edition
Industrial automation systems
2024-01
and integration — Product data
representation and exchange —
Part 1:
Overview and fundamental
principles
Systèmes d'automatisation industrielle et intégration —
Représentation et échange de données de produits —
Partie 1: Aperçu et principes fondamentaux
Reference number
© ISO 2024
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 2
3 Terms, definitions and abbreviated terms . 2
3.1 Terms and definitions .2
3.2 Abbreviated terms .2
4 Overview of the ISO 10303 series . 2
4.1 Purpose .2
4.2 Scope of the ISO 10303 series .3
4.3 Fundamental principles.3
4.3.1 General .3
4.3.2 Integrated resources (IRs) and Core model .3
4.3.3 Support for application protocols (APs) .4
4.3.4 Implementation methods .4
4.3.5 Implementations.4
4.3.6 Conformance testing .5
5 Architecture of the ISO 10303 series . 5
5.1 Overview .5
5.2 Types of architecture .6
5.2.1 General .6
5.2.2 Sharing interpretations in the initial architecture .6
5.2.3 Sharing interpretations in the modular architecture .6
5.2.4 Sharing interpretations in the extended architecture .7
6 Structure of the ISO 10303 series . 9
6.1 General .9
6.2 Description methods .9
6.2.1 Purpose .9
6.2.2 The EXPRESS modelling language .10
6.2.3 Transformation description methods .10
6.3 Implementation methods .10
6.3.1 Purpose .10
6.3.2 Use of formal language.10
6.3.3 Implementation methods for product data described using the EXPRESS
language .11
6.4 Integrated resources (IRs) . 12
6.4.1 Purpose . 12
6.4.2 Generic resources . 12
6.4.3 Application resources . 12
6.5 Application interpreted construct (AIC) . 12
6.5.1 Purpose . 12
6.5.2 Characteristics . 13
6.6 Application modules (AMs) . 13
6.6.1 Purpose . 13
6.6.2 Characteristics . 13
6.6.3 Business benefits . 13
6.7 Application protocols (APs) .14
6.7.1 Purpose .14
6.7.2 Definition of information requirements .14
6.7.3 Information representation for the modular architecture .14
6.7.4 Information representation for the extended architecture .14
6.7.5 Implementation methods .14
6.7.6 Conformance requirements . 15

iii
6.8 Core model . 15
6.8.1 Purpose . 15
6.8.2 Information representation in core technical capabilities . 15
6.9 Application domain models (ADMs) . 15
6.9.1 Purpose . 15
6.9.2 Information representation. 15
6.10 Usage guides . 15
6.10.1 Purpose . 15
6.10.2 Characteristics . 15
6.10.3 Document structure .16
6.10.4 Content .16
6.11 Conformance testing methodology and framework .16
6.11.1 Purpose .16
6.11.2 Procedures for conformance testing .16
6.11.3 Abstract test methods (ATMs) .16
6.12 Abstract test suites (ATSs) .17
7 Information object registration scheme . 17
Annex A (normative) Information object registration.20
Bibliography .21

iv
Foreword
ISO (the International Organization for Standardization) 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. 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. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 184, Automation systems and integration,
Subcommittee SC 4, Industrial data.
This third edition cancels and replaces the second edition (ISO 10303-1:2021), which has been technically
revised.
The main changes are as follows:
— all terms removed, and included in ISO 10303-2;
— inclusion of STEP extended architecture.
A list of all parts in the ISO 10303 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

v
Introduction
The ISO 10303 series of International Standards describe the computer-interpretable representation of
product information for the exchange of product data. The objective is to provide a neutral mechanism
capable of describing products throughout their life cycle. This mechanism is suitable not only for neutral file
exchange, but also as a basis for implementing and sharing product databases, and as a basis for archiving.
The information generated about a product during its design, manufacture, use, maintenance, and disposal
is used for many purposes. The use can involve many information systems, including some that can be
located in different organizations. In order to support such uses, organizations need to be able to represent
their product information in a common computer-interpretable form that is required to remain complete
and consistent when exchanged among different information systems.
This document is an overview of the ISO 10303 series. It specifies the overall scope of the ISO 10303 series
and describes the ISO 10303 series architectures and structure. It describes the various parts of the
ISO 10303 series and the relationships among them.
The ISO 10303 series is organized as a series of parts, each published separately.
Each part of the ISO 10303 series is a member of one of the following series: description methods,
implementation methods, conformance testing methodology and framework, integrated generic resources,
integrated application resources, Core model, application protocols (APs), abstract test suites (ATSs),
application interpreted constructs (AICs), application modules (AMs) and application domain models
(ADMs).
There is a set of standing documents that provide guidelines for developing International Standards
[1]
produced by ISO/TC 184/SC 4. These are listed in the SC 4 organization handbook .

vi
International Standard ISO 10303-1:2024(en)
Industrial automation systems and integration — Product
data representation and exchange —
Part 1:
Overview and fundamental principles
1 Scope
This document provides an overview of the ISO 10303 series.
This document defines the architectural principles of product information representation and exchange
used in the ISO 10303 series. It specifies the characteristics of the various sets of parts in the ISO 10303
series and the relationships among them.
The following are within the scope of this document:
— scope statement for the ISO 10303 series as a whole;
— overview of the ISO 10303 series;
— architectures of the ISO 10303 series;
— structure of the ISO 10303 series;
— overview of data specification methods used in the ISO 10303 series;
NOTE This includes the EXPRESS data specification language and graphical presentation of product information
models.
— introduction to the ISO 10303 series:
— integrated resources (IRs);
— application interpreted constructs (AICs);
— application modules (AMs);
— application domain models (ADMs);
— Core model;
— business object models (deprecated);
— application protocols (APs);
— implementation methods;
— usage guides;
— conformance testing methodology and framework;
— abstract test suites (ATSs);
— scheme for identification of schemas and other information objects defined in the ISO 10303 series.

2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO 10303-2, Industrial automation systems and integration — Product data representation and exchange —
Part 2: STEP Vocabulary
ISO/IEC 8824-1, Information technology — Abstract Syntax Notation One (ASN.1) — Part 1: Specification of
basic notation
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 10303-2 apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— IEC Electropedia: available at https:// www .electropedia .org/ ;
— ISO Online browsing platform: available at https:// www .iso .org/ obp.
3.2 Abbreviated terms
AO application object
CTC core technical capability
DTD document type definition
[2]
HDF hierarchical data format
[3]
SDAI standard data access interface
URL uniform resource locator
UML unified modeling language
[4]
XMI XML metadata interchange
XML extensible mark-up language
XLSX Microsoft Excel open XML spreadsheet
4 Overview of the ISO 10303 series
4.1 Purpose
The purpose of the ISO 10303 series is to specify a form for the unambiguous representation and exchange
of computer-interpretable product data throughout the life of a product. This form is independent of any
specific computer system. This form enables consistent implementations across multiple applications
and systems. The ISO 10303 series architecture permits different implementation methods to be used for
storing, accessing, transferring, and archiving product data. The ISO 10303 series define a rigorous process
for testing implementations for conformance.

4.2 Scope of the ISO 10303 series
The ISO 10303 series provides a representation of product information along with the necessary mechanisms
and definitions to enable product data to be exchanged. The exchange is among different information systems
and environments associated with the complete product life cycle, including product design, manufacture,
use, maintenance and final disposition.
Specifically, the ISO 10303 series provides:
— representation of product information, including components and assemblies;
— implementation methods for exchange of product data, including storing, transferring, accessing, and
archiving.
4.3 Fundamental principles
4.3.1 General
The ISO 10303 series separates the representation of product information from the implementation methods
used for product data exchange, product data access and product data archival.
NOTE The following are assumed:
— data access is machine-to-machine sharing of data;
— data exchange is exchange of machine-interpretable files;
— data archival is persistent storage of machine-interpretable data and associated defining schemata.
EXAMPLE ISO 10303-22, Standard data access interface (SDAI), specifies data access.
The ISO 10303 series implements a three-layer architecture where the business concerns are separate from
[5]
the specification of the information models, which are separate from implementation concerns.
A common resource provides a single representation of product information for many applications. This
representation may be adapted to meet the needs of specific applications.
An application protocol (AP) specifies the representation of product information for one or more applications.
The ISO 10303 series specifies the implementation methods that support the exchange of product data
defined in APs.
[6]
The ISO 10303 series uses EXPRESS or SysML to specify the representation of product information. This
use of the formal languages EXPRESS or SysML provides unambiguous and consistent representation and
facilitates development of implementations. The representation of product information shall be annotated
with a literal definition for each construct.
The ISO 10303 series provides a methodology and framework for conformance testing of implementations.
4.3.2 Integrated resources (IRs) and Core model
4.3.2.1 Integrated resources (IRs)
A set of IRs shall provide the specification of a representation of product information. Each IR comprises
a set of descriptions, written in a formal data specification language, applicable to product data known as
resource constructs. One set may be dependent on other sets for its definition. A single resource construct
may represent similar information for different applications.
The IRs in the ISO 10303 series are divided into two groups: generic resources and application resources.
The generic resources are independent of applications and may reference other resources. The application
resources may reference other resources and may add other resource constructs for use by a group of

similar applications. The IRs may reference product data descriptions written using EXPRESS from other
International Standards.
4.3.2.2 Core model
The Core model shall provide the specification of a representation of product information that is independent
of applications. It is equivalent to the IRs.
The Core information model is divided into a set of core technical capabilities (CTC). Each CTC comprises a
set of objects, relationships and descriptions, written in a formal data specification language. One CTC may
reference objects in other CTCs. A CTC can be reused in, or customised by, applications.
The Core model is mapped to the Reference ARM for SysML mapping (see 6.6) using the artefact ARM in
SysML. This relates it to the IRs.
4.3.3 Support for application protocols (APs)
The IRs and Core model each defines a generic information model for product information. They are not
sufficient to support the information requirements of an AP without the addition of application specific
constraints.
The ISO 10303 series defines APs in which the IRs or Core model are interpreted to meet the product
information requirements of specific applications. The interpretation is achieved by selecting resource
constructs from the IRs or the Core model, and their meaning may be refined by applying application specific
constraints. In the modular architecture (see 5.2.3), this interpretation results in an application interpreted
model (AIM) and a mapping specification. In the extended architecture (see 5.2.4), this interpretation results
in an application domain model (ADM). The AIM or ADM is documented as part of an AP.
The ISO 10303 series has a mechanism to ensure consistent interpretation when a resource construct
represents the same information requirement in different APs. The mechanism uses application modules
(AMs) that document the harmonized requirements along with the interpreted resource constructs.
NOTE 1 There is an alternative legacy mechanism that uses interpreted resource constructs appearing in more
than one AP as a documented application interpreted construct (AIC). New AICs cannot be created.
NOTE 2 See 6.5, 6.6 and 6.9 for more details on AICs, AMs and ADM.
The scope and information requirements of the APs are specified using the terminology of the application
domain. The AP provides a mapping to show how the interpretation of the IRs or Core model is used to meet
the information requirements of the application domain.
The ISO 10303 series provides ADMs that present complex models in a form that can be more understandable
to application experts.
4.3.4 Implementation methods
Each implementation method included in the ISO 10303 series (see 6.3.3.2) is specified by a mapping from a
formal information modelling language used in ISO 10303 (such as the EXPRESS language) onto the formal
language used for the method. The mapping is independent of the AP. The mapping is expressed in a formal
notation, where the notation is defined in a description method for transformation (see 6.2.3).
NOTE Standardized implementation methods that do not have a mapping from the EXPRESS language can be
used. These have a description method for transformation (see 6.2.3).
EXAMPLE Other standardized implementation methods are XML and Open API.
4.3.5 Implementations
An AP may specify one or more applicable implementation methods. These may be chosen from the set of
implementation methods in the ISO 10303 series (see 6.3), or other standardized implementation methods

for which there is a transformation description method (see 6.2.3). An AP implementation shall apply one or
more of the implementation methods specified in the AP.
4.3.6 Conformance testing
Conformance of an implementation to an AP is specified by the conformance requirements in the AP.
A set of tests, specified in an abstract test suite (ATS), may be defined for each AP. When associated with an
abstract test method (ATM), these tests can be used to assess the conformance of an implementation. The
overall framework for conformance assessment is specified in ISO 10303-31.
An ATM for each implementation method is specified in one of the conformance testing methodology and
framework set of the ISO 10303 series.
The scope of conformance testing of a specific implementation is the requirements specified for the
conformance classes claimed for the implementation in the protocol implementation conformance statement
(PICS). The tests are selected from the ATS, based on the conformance class claimed by the implementation.
Test results provide the basis for conformance assessment.
The ISO 10303 series contains ATSs and defines ATMs for performing conformance testing to provide a basis
for test results that are repeatable, comparable, and auditable. Inclusion of conformance testing procedures
in the ISO 10303 series is intended to promote widespread acceptance of test results.
5 Architecture of the ISO 10303 series
5.1 Overview
The ISO 10303 series architecture is designed to support the development of standards for product data
exchange, product data access and product data archival. The architecture is constrained by the following
concepts:
— the scope of what is standardized and what is conformance tested is set at the level of an application;
— information requirements are based on a model of a business activity;
— information requirements are standardized using a modelling language;
— a mapping is a specification of the data structures used from the IRs or the Core model and population
constraints against that usage satisfying application requirements.
EXAMPLE 1 An ARM-AIM mapping of the AO Activity is a query against an AIM data population of the entity
executed action. For each member of executed action in the data population, a member of Activity would be created.
EXAMPLE 2 A mapping from one entity in model X uses six entities as a target in model Y. It is not possible to map
from one of the six entities in model Y to the entity in model X. Instead, a query is used to locate the six entities in
model Y.
The ISO 10303 series is implemented through APs. An AP consists of the following major elements:
— an application activity model (AAM) describing the business process that the information model
supports;
— an application data planning model (ADPM) describing the primary concepts of an application domain
and the relationships among the concepts;
— an application reference model (ARM) specifying the information requirements (optional for the
[7][8][9][10]
extended architecture );
— an information model based on the IRs, called an AIM, that is a basis for implementations of the APs using
[11]
the modular architecture shall include an AIM. APs using the extended architecture may include an
AIM;
— an information model for data structures, called an ADM, that is a basis for implementations of the APs
using the extended architecture shall include an ADM.
The architecture is based on standardizing industry information requirements and mapping those
information requirements to an information model based on the IRs or the Core model. The Core model is
mapped to a reference ARM that is then mapped to the IRs. The process of mapping information requirements
to the IRs is known as "interpretation".
The ISO 10303 series architecture focuses on the information required by industrial processes rather than
on the processes themselves, as the processes can change over time, while the underlying information
requirements are longer lasting. This focus on information allows the ISO 10303 series to support data
exchange, data access, as well as product data archival.
Whenever a resource construct is used to represent the same information requirement in different APs, the
same interpretation of that resource construct shall be used.
5.2 Types of architecture
5.2.1 General
The general architectural principles described in 5.1 have been elaborated into three architectures:
— the "initial architecture",
— the "modular architecture", and
— the "extended architecture".
All architectures adhere to the fundamental principles described in 4.3.
NOTE The term "ISO 10303 series architecture", without qualification, refers to the general principles described
in 5.1 and the common aspects of its elaborations.
An ISO 10303 series project may use the initial architecture, the modular architecture, or the extended
architecture, although new projects are not encouraged to use the initial architecture.
5.2.2 Sharing interpretations in the initial architecture
An AIC shall be used to specify a piece of an AIM that can be used to exchange product data common to two
or more APs.
NOTE An AIC does not document the common information requirements or the mapping of those information
requirements into the AIM.
An AP that complies with initial architecture is called a "monolithic AP".
5.2.3 Sharing interpretations in the modular architecture
5.2.3.1 General
Rather than relying on harmonization occurring as a by-product of consistent interpretation across APs,
application requirements are first harmonized across domains and the resulting mappings are standardized
in AMs. AMs are reused by other AMs and ultimately by APs.
The implementable portion of the modular architecture has two core components:
— AM:
— a reusable data specification documented with an ARM;
— mapping;
— MIM;
— optional usage guide.
— AP: The use of a data specification to meet the requirements of business processes.
NOTE The business object model, originally included in the modular architecture, is deprecated.
The objectives and function of the architectural components are described in 5.2.3.2 and 5.2.3.3.
5.2.3.2 Application module (AM)
The design of an AM should maximize re-usability of the
a) harmonized requirements,
b) associated interpretation into the IRs,
c) data specification, and
d) software implementations.
The design shall support re-usability by the standards developer, implementer and user.
AMs replace AICs in the modular architecture. Each AIC shall be included in one AM. The objectives of AICs
and AMs are similar. They both standardize interpretation results for reuse in multiple APs. However,
AICs and AMs are created differently and have different content. AMs, unlike AICs, contain harmonized
information requirements and specifications of the mappings of those requirements to the IRs. An objective
of modularization is to document a concept one time and then to directly reuse that concept in other AMs. The
modular architecture uses EXPRESS rather than natural language for the documentation of requirements,
i.e. the ARM, in an AM. This allows the use of tools to validate the dependencies between AM ARMs.
5.2.3.3 Modular application protocol (AP)
An AP that complies with modular architecture is called a "modular AP". A modular AP is a documented use
of a set of AMs for a specific business process. The AMs used by an AP are organized in a tree structure. A
single, normatively referenced AP AM is the data specification for the AP. This AM normatively references a
collection of related AMs that provide the documentation of its information requirements and standardized
interpretations. The AP AM may include specific business process rules or constraints. The AP document
contains an activity model and conformance class definitions. Industry specific terminology can be mapped
[12]
(see guidelines ) to the generic AM terminology defined in an AP to make it more understandable to
reviewers from the application domain.
5.2.3.4 Business object model (deprecated)
The business object model is deprecated and replaced by the ADM.
5.2.4 Sharing interpretations in the extended architecture
5.2.4.1 General
The extended architecture is based on the modular architecture, and allows additional implementation
forms at the level of the ADM.
The additional implementable portion of the extended architecture has two core components:
— ADM: The data specification that provides the documentation of information requirements for a domain
that are parametrically mapped to the Core model.
— AP: The use of a data specification to meet the requirements of business processes.

The objectives and function of the ADM are described in 5.2.4.2. The objectives and function of the AP are
described in 5.2.4.3. The objectives and function of the Core model are described in 5.2.4.4.
5.2.4.2 Application domain model (ADM)
The ADM describes the information requirements and constraints of a specific application context in
a normative schema definition. The ADM is a specific view of selections of the STEP integrated model
constrained by the AP requirements.
The implementation schemas for the ADM shall be derived by applying implementation bindings specified in
the description methods.
5.2.4.3 Extended architecture application protocol (AP)
An extended architecture AP has a single documented ADM for a specific business process. The ADM
is the data specification for the AP that provides the documentation of its information requirements and
standardized interpretations. The ADM may include specific business process rules or constraints. The AP
document contains an AAM, ADPM and conformance class definitions.
5.2.4.4 Core model
The Core model is an information model shared by all ADMs. The Core model represents the product data
through its entire life cycle.
The Core model internal structure is composed of a set of Core Technical Capabilities (CTCs).
A CTC is constrained and defined as follows:
— a CTC shall be a consistent group of objects;
— an object is declared in one and only one CTC (i.e the CTCs do not overlap);
— a CTC is formalized as a set of objects and relations that may include references to objects in other CTCs
and which are fully defined, including all attributes and constraints, and fully documented;
— objects and relations may be used to derive an implementation form;
— a CTC shall provide interfaces and may provide auxiliary information;
— a CTC shall group functionally related elements;
— a CTC may be decomposed into sub-CTCs.
EXAMPLE The Multidisciplinary Simulation CTC is decomposed into Thermal Analysis CTC and Finite Element
Analysis CTC; or Product and Manufacturing Information (PMI) CTC is decomposed into Generate and Test (G&T) CTC,
Dimension and Tolerance (D&T) CTC, and Weld CTC.
5.2.4.5 ARM in SysML
The ARM in SysML is an artefact that provides an interface between the modular architecture and the
[13]
extended architecture. There is an AM ISO/TS 10303-400 “Reference ARM for SysML mapping” (see
6.2.2). The transformation of "Reference ARM for SysML mapping" into SysML is specified in the description
[14]
methods (see 6.2). The result of the transformation is the ARM in SysML artefact that is contained in Core
model (see 5.2.4.4).
The ARM in SysML contains the application objects (AOs) to which the core objects shall be mapped. The
purpose of the mapping is to ensure that each core object is traced to the AOs in an AM contained in the
AM “Reference ARM for SysML mapping”. Each AM has mappings from the AOs to MIM entities and STEP IR
entities (see 6.7.3). The ADM objects are mapped to the Core model objects, thus ensuring that each ADM
object is traced to the AOs in the AM.

6 Structure of the ISO 10303 series
6.1 General
The ISO 10303 series is divided into the following sets of parts. Each set has a unique function and consists
of one or more parts. The sets are listed below with their numbering scheme:
— description methods: ISO 10303-11 to ISO 10303-19 (see 6.2);
— implementation methods: ISO 10303-21 to ISO 10303-29 (see 6.3);
— conformance testing methodology and framework: ISO 10303-31 to ISO 10303-39 (see 6.11);
— integrated resources (IRs) (see 6.4):
— generic resources: ISO 10303-41 to ISO 10303-99 (see 6.4.2);
— application resources: ISO 10303-101 to ISO 10303-199 (see 6.4.3);
— application protocols (APs): ISO 10303-201 to ISO 10303-299 (see 6.7);
— abstract test suites (ATSs): ISO 10303-301 to ISO 10303-399 (corresponding to the associated APs
ISO 10303-201 to ISO 10303-299) (see 6.12);
— reference ARM for SysML mapping: ISO 10303-400 (corresponding to the Core model ISO/TS 10303-4000)
(see 6.6)
— application protocol (AP) modules: ISO 10303-401 to ISO 10303-499 (corresponding to the associated
APs ISO 10303-201 to ISO 10303-299) (see 6.7);
— application interpreted constructs (AICs): ISO 10303-501 to ISO 10303-523 (see 6.5);
— application modules (AMs): ISO 10303-1001 to ISO 10303-1999 (see 6.6):
— business object models: ISO 10303-3001 to ISO 10303-3099 (deprecated);
— Core model: ISO/TS 10303-4000 (see 6.8);
— application domain models (ADMs): ISO 10303-4401 to ISO 10303-4499 (corresponding to the associated
application protocol (AP) modules ISO 10303-401 to ISO 10303-499) (see 6.9);
— usage guides: ISO 10303-5001 to ISO 10303-5999 (see 6.10).
NOTE The business object models are deprecated.
6.2 Description methods
6.2.1 Purpose
The description of product data in the ISO 10303 series requires the use of formal data specification
languages to ensure consistency and avoid ambiguity. The languages are intended to be computer-
interpretable to facilitate the generation of application software and supporting tools. Supporting tools may
be used to present the languages in a human-readable form to facilitate human understanding.
The des
...