ISO/TS 23164:2025

Automation systems and integration - Core vocabulary for industrial data

This document specifies a vocabulary for industrial data that defines generic terms for things that exist in more than one industrial domain. The following are within the scope of this document: - definition of terms for generic types of industrial thing; EXAMPLE 1 Definitions of the terms “material object”, “artefact” and “product” are within the vocabulary. - definition of terms relevant to assemblies, systems and their breakdown structures; - definition of terms relevant to activities and participation in activities; - definition of terms relevant to positions and roles in organizations; - definition of terms relevant to behaviour, capability and function; - definition of terms relevant to state and condition; - definition of terms relevant to specifications, designs and plans; - definition of terms relevant to versions, alternatives and configurations for specifications, designs and plans; - definition of terms relevant to signals and other carriers of information and to devices that process signals and information; - definition of terms relevant to physical quantities and properties. The following are outside the scope of this document: - definition of terms that are relevant to data themselves, rather than the things that data are about; EXAMPLE 2 Definitions of the terms “data” and “information” are not within the vocabulary. - definition of terms that are relevant to representations. EXAMPLE 3 Definitions of the terms “representation” and “model” are not within the vocabulary.

Systèmes d'automatisation et intégration — Vocabulaire de base pour les données industrielles

General Information

• Status: Published
• Publication Date: 06-Jan-2025
• ICS: 01.040.25 - Manufacturing engineering (Vocabularies)
• ICS: 25.040.01 - Industrial automation systems in general
• Technical Committee: ISO/TC 184/SC 4 - Industrial data
• Drafting Committee: ISO/TC 184/SC 4 - Industrial data
• Current Stage: 6060 - International Standard published
• Start Date: 07-Jan-2025
• Due Date: 28-Dec-2024
• Completion Date: 07-Jan-2025

Overview

ISO/TS 23164:2025 - Automation systems and integration - Core vocabulary for industrial data is a Technical Specification (first edition, 2025) that defines a core vocabulary for industrial data. It specifies generic terms that apply across multiple industrial domains (e.g., material object, artefact, product) and provides a consistent set of definitions to enable interoperability between data models, ontologies and software used in automation and integration projects.

Key Topics

The document focuses on standardized terminology and covers:

• Generic types of industrial things (e.g., material object, artefact, product)
• Assemblies, systems and breakdown structures (whole‑part relationships)
• Activities and participation (actors, processes, services)
• Positions and roles in organizations
• Behaviour, capability and function (what things do)
• State and condition (status, lifecycle)
• Specifications, designs, plans, versions and configurations
• Signals, information carriers and processing devices
• Physical quantities and properties

It explicitly excludes definitions that concern data itself (for example “data” and “information”) and representations or models. The specification is organized into structured term groups (see clause and annex structure) and includes informative annexes on development methodology and guidance for term groups.

Practical Applications

ISO/TS 23164:2025 is intended to be a practical tool for:

• Data architects and ontology engineers mapping between industrial data models and reference data libraries
• System integrators and automation vendors implementing interoperability between PLM, MES, ERP and control systems
• Digital twin developers who need consistent terminology across models and systems
• Standards writers and domain experts creating or aligning specialized taxonomies
• Asset owners and business stakeholders seeking improved data integrity and a common language for cross‑domain collaboration

Benefits include clearer semantics across projects, easier mapping of reference data, and reduced ambiguity when linking models and software for industrial automation and integration.

Related standards

ISO/TS 23164:2025 is produced by ISO/TC 184/SC 4 and is intended to support other ISO industrial data standards. It references practices and overlaps with standards and models such as ISO 10303, ISO 15926‑2 and IEC 81346‑1, and is conceptually analogous to the Dublin Core approach for metadata in the document domain.

Keywords: ISO/TS 23164:2025, core vocabulary, industrial data, automation systems, data integration, digital twin, ontology, reference data, interoperability.

Standards Content (Sample)

Technical
Specification
ISO/TS 23164
First edition
Automation systems and
2025-01
integration — Core vocabulary for
industrial data
Systèmes d'automatisation et intégration — Vocabulaire de base
pour les données industrielles
Reference number
© ISO 2025
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: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions .1
3.2 Terms related to particular and kind .2
3.3 Terms related to artefact, product and material object .3
3.4 Terms related to part and component .4
3.5 Terms related to things that are aggregations of parts .5
3.6 Terms related to activity and participation .9
3.7 Terms related to breakdown.10
3.8 Terms related to behaviour, capability and function .11
3.9 Terms related to state . 13
3.10 Terms related to person, organization, position and role in organization .14
3.11 Terms related to process and service .16
3.12 Terms related to requirement, design and specification .16
3.13 Terms related to method and plan .17
3.14 Terms related to physical quantity and physical property .17
3.15 Abbreviated terms .21
Annex A (informative) Development methodology .22
Annex B (informative) Guidance on groups of terms .25
Annex C (informative) Definitions of terms in sources .32
Bibliography .38

iii
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 documents 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.
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.

iv
Introduction
The terms and definitions in this document are applicable to all ISO/TC 184/SC 4 standards. Depending upon
the standard, these terms can be implemented as classes, relationships, properties or other types of model
or ontology element. The core terms can be used in the documentation of the links between the different
standardized data models, ontologies and software applications that need to work together to produce a
digital twin for an industrial activity. The terms in the set can also help with data integrity by making sure
we are talking about the same thing.
This document:
— provides a vocabulary that is not only understandable by ISO/TC 184/SC 4 experts, but also by domain
engineers and by business decision makers;
NOTE 1 Many of the terms and definitions can already exist in the Oxford English Dictionary or in standards,
but the definition of an integration layer requires their selection and so even these terms are included.
— enables the development of reference data that are equally applicable to all ISO/TC 184/SC 4 standards;
NOTE 2 Domain experts will produce detailed taxonomies that specialise generic items identified by terms in
the set. The domain experts will not need detailed knowledge of any particular ISO/TC 184/SC 4 standard or of
any particular top-level ontology.
— defines an interface to reference data developed outside ISO/TC 184/SC 4, and thereby enables its use by
all ISO/TC 184/SC 4 standards.
NOTE 3 This document is intended to be analogous in the industrial domain to the Dublin Core in the document
management domain. The original Dublin Core metadata set consisted of only 15 terms. This initial set has since
been expanded to 55 terms. This document is of a similar size.
The role of this document in the development of reference data libraries is shown informally in Figure 1.
Figure 1 — Role of this document in the development of reference data libraries
A top-level ontology in Figure 1 addresses generic issues such as the representation of whole-part
relationships, change over time, and the distinction between actual objects, requirements and plans.
At present ISO 10303 does not contain a top-level ontology. However, the Integrated Resource data models
can be regarded as containing an informal top-level ontology. ISO 15926-2 is a top-level ontology.

v
The reference data libraries for different domains in Figure 1 are shown as independent. In practice there
are large overlaps. This document shows which reference data items are specialisations of the same generic
item, and therefore make the overlaps easier to manage.
The approach used to develop the content of this document and to define its scope is described in Annex A
“Development methodology”.
The guidance on groups of terms and their motivation is contained in Annex B “Guidance on groups of terms”.
NOTE 1 The methodology followed in the development of this document has been to:
a) define a thing about which industrial data is held using natural language;
b) assign a preferred term consisting of one or more English language words to the thing.
Because the things and their definitions are primary with terms assigned to them, this document can also be called a
“thesaurus”.
NOTE 2 In this document the preferred terms are unique. In some cases, admitted terms are also given, which are
not necessarily unique.
NOTE 3 Where possible the terms are taken from international standards.
NOTE 4 The terms can be used in the text definitions and descriptions of entities and attributes in industrial data
models, and of classes and relationships in industrial ontologies. The terms can be used in the text definitions and
descriptions of items within industrial data libraries for particular industrial domains.

vi
Technical Specification ISO/TS 23164:2025(en)
Automation systems and integration — Core vocabulary for
industrial data
1 Scope
This document specifies a vocabulary for industrial data that defines generic terms for things that exist in
more than one industrial domain.
The following are within the scope of this document:
— definition of terms for generic types of industrial thing;
EXAMPLE 1 Definitions of the terms “material object”, “artefact” and “product” are within the vocabulary.
— definition of terms relevant to assemblies, systems and their breakdown structures;
— definition of terms relevant to activities and participation in activities;
— definition of terms relevant to positions and roles in organizations;
— definition of terms relevant to behaviour, capability and function;
— definition of terms relevant to state and condition;
— definition of terms relevant to specifications, designs and plans;
— definition of terms relevant to versions, alternatives and configurations for specifications, designs and plans;
— definition of terms relevant to signals and other carriers of information and to devices that process
signals and information;
— definition of terms relevant to physical quantities and properties.
The following are outside the scope of this document:
— definition of terms that are relevant to data themselves, rather than the things that data are about;
EXAMPLE 2 Definitions of the terms “data” and “information” are not within the vocabulary.
— definition of terms that are relevant to representations.
EXAMPLE 3 Definitions of the terms “representation” and “model” are not within the vocabulary.
2 Normative references
There are no normative references in this document.
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp

— IEC Electropedia: available at https:// www .electropedia .org
3.2 Terms related to particular and kind
3.2.1
particular
individual
thing existing in space and time
EXAMPLE 1 The pump with serial number “X12345”, which was supplied by Fred Bloggs and Co. to UGE Inc. on
2019-09-27, is a particular pump.
EXAMPLE 2 The computer file http:// www .uge .com/ annual -report/ 2019 .docx is a particular computer file. It was
created at a particular time and may be deleted in the future. It exists on a particular server somewhere.
Note 1 to entry: The term “individual” is used in ISO/TS 10303-1164:2023, 4.3.1, and ISO 15926-2:2003, 3.1.6.
Note 2 to entry: IEC 81346-1:2022, 3.16 defines the term “product individual” with the same meaning as particular
product (3.3.3).
Note 3 to entry: The term particular is used as a qualifier of another term.
Note 4 to entry: In this document, the term particular is not used on its own, except where the qualified term is
understood.
Note 5 to entry: “Realized” is a natural term where qualified term is product (3.3.3), but less natural where the
qualified term is person (3.10.2).
Note 6 to entry: The term “individual” is used on its own in OWL to mean an object within the domain. In OWL DL
(OWL statements following specified syntactic restrictions that are interpreted using the OWL 2 Direct Semantics) an
OWL individual cannot also be an OWL class. In OWL-Full (which need not follow the above semantic restrictions and
is interpreted using the OWL 2 RDF-Based Semantics) an OWL individual can also be an OWL class.
Note 7 to entry: The space and time within which a particular thing exists can be unknown.
Note 8 to entry: Some ontological approaches describe plans for the future or scenarios in terms of particular things
that exist in possible worlds. The vocabulary defined here neither prescribes nor precludes such approaches.
Note 9 to entry: ISO 10303 allows a particular thing to be either actually existing or planned for the future. A particular
thing that is actually existing is also called “realized”.
Note 10 to entry: In ISO/TS 10303-4000:2023 and in the Application Reference Model of ISO 10303-242:2022, term
“product” is replaced by “part” so that the following terms are used: “individual part”, “planned individual part” and
“realized individual part”.
3.2.2
kind
class
type
things that have something in common
EXAMPLE 1 Pump is a kind of material object (3.3.2). Each particular (3.2.1) material object of this kind is intended
to add mechanical energy to a fluid. This is a generic kind of material object.
EXAMPLE 2 The “Fred Bloggs and Co. model A-101 pump” is a kind of material object. Each particular pump of this
kind has a rated power of 1 kW. There are many other quantitative properties possessed by each particular pump of
this kind. This is a specific kind of material object.
Note 1 to entry: The term “class” is used in ISO 15926-2:2003, 3.1.1, and ISO/TS 10303-54:2005, 3.2.1.
Note 2 to entry: The terms “type” and “class” are used in IEC 81346-1:2022, 3.17 and 3.20, with meanings which are
both similar to kind.
Note 3 to entry: The term kind is a qualifier of another term, usually in the form “kind of”. In this document, the term
kind is not used on its own as a noun, except where the qualified term is understood.

Note 4 to entry: Depending on the what all things of a kind have in common, a kind can be “generic” or “specific”. A
generic kind is one that is defined in sources used throughout industry, such as standards. A specific kind is often
defined by an organization as part of a specification.
Note 5 to entry: What things of the same kind have in common can be specified.
Note 6 to entry: “Class” and “type” are possible synonyms for kind. “Class” is used in ISO 15926-2:2003, 3.1.1 with a
meaning that is close to “set” in mathematics. The uses of these terms in ontologies or data modelling languages is not
necessarily consistent with the less formal use here.
Note 7 to entry: ISO 10303 mostly uses the term “class”. The usage of this term is defined in ISO/TS 10303-1114:2019,
4.3.1 defines the entity Classification_assignment to be “the assignment of a Class to product or activity data for their
classification”.
Within ISO 10303, a “part” can be a kind of thing. ISO/TS 10303-1022:2014, 3.1.2.2 defines a part to be “discrete object
that can come into existence as a consequence of a manufacturing process”.
Within ISO 10303, a “concept” is a kind of thing. ISO/TS 10303-1060:2004, 4.1.2 defines the entity Product_concept to
be “an identification of a set of similar products that were, are or will be proposed to customers”.
Within ISO 10303 the term “type” is used in some circumstances. ISO/TS 10303-1240:2004, 4.2.2 defines the entity
Organization_type to be a “recognized kind of organization”. ISO/TS 10303-1245:2004, 4.3.1 defines the entity Type_
of_person to be a “type of person”.
3.3 Terms related to artefact, product and material object
3.3.1
artefact
thing that is a result of human activity
EXAMPLE 1 The noise of vented steam from plant UGE-1 on 2020-03-17 is an artefact.
EXAMPLE 2 The footprints of Neil Armstrong on the moon are artefacts.
3.3.2
material object
thing that occupies space and possesses rest mass
EXAMPLE 1 A washer is stamped from a sheet of steel. The sheet of steel is a material object and a product (3.3.3).
The stamping process creates two new material objects and products:
— the washer;
— a disc of waste steel that is removed to make the hole in the washer.
The original sheet of steel continues to exist but now has a hole in it. The washer is a product intended for sale or use,
whilst the disc of waste steel and the steel sheet with hole in it may be waste products.
EXAMPLE 2 The batch of liquid B-101 is stored in tank A. The batch B-101 is a material object. The contents of tank
A are then divided so that some goes into tank B and some into tank C. The contents of tanks B and C are two different
material objects. We can say that the contents of tanks B and C came from batch B-101 for traceability, but it is an
administrative decision whether the material objects in tanks B and C are regarded as parts of material object B-101
which continues but now as two separate parts, or whether the material object B-101 ceased to exist when it was
transferred out of tank A and divided.
Note 1 to entry: A material object can be a discrete solid quantity of material, or a part of a larger quantity of solid
material. A material object can be a quantity of fluid material, or a part of a large quantity of fluid material.
Note 2 to entry: The beginning or end of the life or existence of a material object can be an arbitrary administrative
decision. A material object can be deemed to come into existence at a stage of a manufacturing process. A material
object can be deemed to have ended its life at a stage of a dismantling or recycling process.
Note 3 to entry: The matter that a material object consists of can exist before the material object begins. This matter is
other material objects. Similarly, the matter a material object consists of can continue to exist after the material object
ends. This matter is also another material object.

3.3.3
product
thing that is intended to be either sold, or delivered, or used as input to another human activity, or transferred
to the environment as waste
Note 1 to entry: This definition encompasses the following:
— sales product: This is something produced or extracted for sale. It is not necessarily an artefact (3.3.1), because
it can be raw material or agricultural produce. It is not necessarily a material object (3.3.2), because it can be
software.
— intermediate product: This is something that has been produced and that is intended for further processing before
end use.
— waste product: This is something that has been produced, but is unwanted by its producer. It can be input to other
processes or transferred to the environment.
Note 2 to entry: A product is distinguished from a service (3.11.2) in this document. The term “product and service” is
used for things that are a combination of the two.
Note 3 to entry: A product can be raw material extracted from the ground, timber from a forest, or agricultural
produce.
Note 4 to entry: A product can be intangible, such as software or a product design.
Note 5 to entry: A product can be energy, such as a supply of electricity or heat.
3.3.4
material product
product (3.3.3) that is a material object (3.3.2)
Note 1 to entry: A material product can be an unfinished product that is produced by a materials supplier, and that is
input to other manufacturing processes (3.11.1).
3.4 Terms related to part and component
3.4.1
part
thing that is a part of a whole
EXAMPLE 1 The front offside wheel of the vehicle with registration “DV 58 HUK” is a part of the vehicle. It is not
arbitrary, but an assembly element (3.5.3). It is also a material object (3.3.2). The material that is the front offside wheel
can change from time to time during the life of the vehicle.
EXAMPLE 2 The compartment “P-13” of the ship Arctic Queen is a part of the ship. It is not arbitrary, but a breakdown
element (3.7.4) of a spatial breakdown of the ship.
Note 1 to entry: Each thing is always a part of many other things. Therefore, calling a thing a “part” conveys no
information other than that there is a part-whole relationship of interest.
Note 2 to entry: A part can be an arbitrary division of the whole. A part can also be not arbitrary. A part that is not
arbitrary can be an assembly element, a system element (3.5.8), a network element (3.5.12), or a breakdown element.
Note 3 to entry: If the whole is a material object, then each part is also a material object. However, a part can be different
material at different times.
Note 4 to entry: A part can be identified solely by the place where it is. A part is not necessarily a serial numbered
material product (3.3.4).
Note 5 to entry: If a part is a material object which can be replaced, then the identity of the part is derived from its
relationship with the whole that it is part of.
Note 6 to entry: A part can be a shape feature (3.4.2).
Note 7 to entry: A part can be empty space. In a process plant, an access route can be an important and identified part.

3.4.2
shape feature
part (3.4.1) that is distinguished from a whole by its shape
Note 1 to entry: A shape feature is not usually a component (3.4.2) for an assembly (3.5.2). A shape feature is not usually
separable from the whole.
Note 2 to entry: A shape feature can be formed by the addition or removal of material. A shape feature can be a hole.
Note 3 to entry: A shape feature can be classified according to its shape. Such classifications include thread, groove,
slot, and stud.
Note 4 to entry: A shape feature can be classified according to its engineering purpose. Such classifications include
lifting lug and drain hole.
Note 5 to entry: The boundary of a shape feature can be incompletely defined. Hence the boundary between a lifting
lug and the material object (3.3.4) to which it is fixed can be vague. It can be somewhere in the region of the weld.
3.4.3
component
product (3.3.3) that was created with the intention that it be part of an assembly (3.5.2), system (3.5.6) or
network (3.5.11)
EXAMPLE 1 Nut is a generic kind (3.2.2) of component.
EXAMPLE 2 Flange nut is a generic kind of component.
EXAMPLE 3 “Flange nut to specification N-DEF” is a specific kind of component.
Note 1 to entry: A component is usually a material object (3.3.2), but can be a non-material thing such as software.
Note 2 to entry: A component can be an assembly.
Note 3 to entry: A component can have different statuses during its life, such as:
— not assembled: available for use in an assembly;
— assembled and replaceable: can be removed from its assembly and replaced by a component with similar form, fit
or function;
— assembled and not replaceable: cannot be removed from its assembly.
In a factory that makes circuit boards, a bare board is a component, which initially has the status of not assembled.
Once it is part of a completed circuit board, it has the status of assembled and not replaceable. A completed circuit
board is itself a component. In a distribution centre, a complete circuit board has the status of not assembled.
Note 4 to entry: In ISO/TS 10303-4000:2023 and in the Application Reference Model of ISO 10303-242:2022, the term
“product” is replaced by “part”. With this usage, it can be a component that is being referred to.
3.5 Terms related to things that are aggregations of parts
3.5.1
collection
aggregation
two or more particular (3.2.1) things together as a whole, where the relationships between the things are
unimportant
EXAMPLE 1 The load of bricks delivered to site UGE-1 on 2020-03-17 is a particular collection of bricks. The load of
bricks is also an artefact (3.3.1), material object (3.3.2) and product (3.3.3).
EXAMPLE 2 The paintings in the UK National Gallery are a collection. The paintings in the collection change from
time to time.
Note 1 to entry: A collection is not a set. If the things in a collection are material objects, then the collection is itself also
a material object.
Note 2 to entry: A collection can be arbitrary, non-contiguous or both.
Note 3 to entry: The parts (3.4.1) of a collection can change during the life of the collection.
3.5.2
assembly
two or more things, where each is a material object (3.3.2), assembled together into a contiguous whole
Note 1 to entry: A distinct part (3.4.1) within an assembly is an assembly element (3.4.3).
3.5.3
assembly element
material object (3.3.2) that is assembled with others to create an assembly (3.5.2)
EXAMPLE 1 The building with site identifier “B-101” is a particular (3.2.1) assembly. Some of its assembly elements,
such as doors and windows, are components (3.4.3) which are brought to the site. Other assembly elements, such as the
walls, are made in-place.
Each wall of building “B-101” is a particular assembly. A wall has bricks as assembly elements. The bricks are components.
EXAMPLE 2 The motor car with registration number “DV 58 HUK” is a particular assembly. All of its assembly
elements are components, such as the body shell, engine, and transmission. The engine is usually regarded as
replaceable, whilst the body shell is not.
EXAMPLE 3 The engine design “E-ABC” is or defines (according to ontological view) a kind (3.2.2) of assembly. The
arrangement of the head nuts for the engine design “E-ABC” is shown in Figure 2.

Figure 2 — Head nut arrangement for engine design “E-ABC”
EXAMPLE 4 The material of the cylinder head directly under head nut 27 of the engine with serial number
“98/12345” is a particular part. This is not a particular assembly element but an arbitrary particular part (3.4.1). The
material could change if that material were ground out and new material welded in.
EXAMPLE 5 The material of the cylinder head directly under head nut 27 of the kind of engine to design E-ABC is a
kind of part. This is not a kind of assembly element but an arbitrary kind of part.

Note 1 to entry: An assembly element exists only as a part of an assembly. Its identity depends upon the assembly so that
when an assembly ceases to exist, so necessarily do all of its assembly elements. A component that has been used as an
assembly element can continue to exist and may be refurbished and re-used elsewhere.
Note 2 to entry: An assembly element can be made in-place, or can be a component which has been brought from
elsewhere.
Note 3 to entry: An assembly element can be replaceable. In a design, some assembly elements can be flagged as
replaceable parts.
Note 4 to entry: An assembly element can be joined by welding, and therefore cannot be replaced easily. An assembly
element can be joined by nuts and bolts, and therefore can be replaced more easily.
Note 5 to entry: A part of an assembly can be an arbitrarily defined part, which is not an assembly element.
3.5.4
component in an assembly
occurrence
assembly element (3.5.3) that is a component (3.4.3)
EXAMPLE 1 Head nut is a generic kind (3.3.2) of component in an assembly.
EXAMPLE 2 The “head nut labelled 27 within engine design E-ABC” is a specific kind of component in an assembly.
EXAMPLE 3 The “head nut labelled 27 of the engine with serial number 98/12345” is a particular (3.3.1) component
in an assembly. During the life of the engine with serial number “98/12345”, different particular components can be
installed as this particular component in an assembly.
Note 1 to entry: An assembly element, such as a wall of a building, can be built in-place and is not a component. An
assembly element, such as a window frame, can exist before being part (3.4.1) of an assembly (3.5.2), and is a component.
Note 2 to entry: During the life of a particular assembly, a particular component in an assembly can be replaced.
Note 3 to entry: ISO/TS 10303-1026:2023 defines an approach to the design for manufacture, the actual manufacture
and maintenance of parts, that are assemblies. The following are defined:
— promissory usage: the relationship between an assembly and a component, regardless of the number of
intermediate levels between them, which supports the representation of a bill of material;
— next assembly usage: the relationship between a component and its immediate parent assembly in a product
structure.
These structures are used during design relating kinds of product (“parts” in ISO 10303 terminology) and during
operation and maintenance relating particular products (“individual parts” in ISO 10303 terminology). At the
design stage, the relationships are between “parts” or “occurrences of parts”. An “occurrence of a part” is a “part” or
“configured part” that is in an identified role. An “occurrence of a part” can have specific properties or need specific
maintenance.
Note 4 to entry: The term replaceable part is a near synonym. However, a component in an assembly need not be
practically replaceable.
3.5.5
sub-assembly
assembly element (3.5.3) that is an assembly (3.5.2)
EXAMPLE The building with site identifier “B-101” is a particular (3.2.1) assembly. Each wall of building “B-101” is
a particular sub-assembly. A wall has bricks as assembly elements (3.5.3). The bricks are components (3.4.3).
Note 1 to entry: Usually a sub-assembly is a component. It is possible that some sub-assemblies can only exist when part
(3.4.1) of a whole, and therefore are not components even though they are assembled from components.
Note 2 to entry: During the life of a particular assembly, a particular sub-assembly can be replaced.

3.5.6
system
two or more things with interactions between them, giving the whole a behaviour (3.8.1)
Note 1 to entry: A interacting part of a system is a system element (3.5.8).
Note 2 to entry: A system has a breakdown (3.7.1) into its system elements. A system can have other breakdowns into
parts (3.4.1) that are not system elements.
Note 3 to entry: A system can have parts which are not system elements. A part of a system can be all that is within a
particular area or compartment. This part can be without a function (3.8.3) as a whole, and can be neither a sub-system
(3.5.10) nor a component (3.4.3).
3.5.7
engineered system
system (3.5.6) that is an artefact (3.3.1) created for a purpose
Note 1 to entry: An engineered system is intended to have capabilities (3.8.2).
Note 2 to entry: An engineered system can have system elements (3.5.8) in the natural world that are not artefacts.
3.5.8
system element
thing that is one of the interacting parts that together form a system (3.5.6)
Note 1 to entry: A system element of a engineered system (3.5.7) has a function (3.8.3).
Note 2 to entry: A system element can be a sub-system (3.5.10), a component (3.4.3) or both. A circuit board can be a sub-
system, but if it is replaced as a whole when anything goes wrong it is also a component.
3.5.9
component in a system
system element (3.5.8) that is a component (3.4.3)
EXAMPLE The relationship between a component and a system (3.5.6) can be complicated. Consider a circuit
board that has some parts (3.4.1) that interact with “system A” and some parts that interact with “system B”. The
circuit board is a component, but not a system element (3.5.8) of either “system A” or “system B”.
The circuit board is a component in an assembly within the assembly (3.5.2) that is the rack of circuit boards. The
circuit board can be a component in a system of the system has both “system A” and “system B” as sub-systems (3.5.10).
Note 1 to entry: During the life of a particular (3.2.1) system, a particular component in a system can be replaced.
Note 2 to entry: A component in a system is a functionally defined role within a particular system that exists for the life
of the system. A component is usually a product (3.3.3) which may be able fill that role. Because of the different identity
criteria and lifecycles of these things, component of a system is not a specialisation of component.
3.5.10
sub-system
system element (3.5.8) that is a system (3.5.6)
3.5.11
network
two or more things with discrete connections between them
EXAMPLE The South Eastern Railway is a transport network. The railway stations are network elements (3.5.12)
and the connections between them are train operations. There can be a flow of passengers between railway stations.
Note 1 to entry: A connected part (3.4.1) of a network is a network element.
Note 2 to entry: Things are connected if something can pass between them. If mechanical force can pass, then things
are physically connected. Things are also connected in energy or information can pass between them. Hence a satellite
can be a part of a network that is a communications system.

Note 3 to entry: A line of posts preventing the access of vehicles is an assembly (3.5.2), but not a network because the
parts are not connected.
Note 4 to entry: A network has a breakdown (3.7.1) into its network elements and into the connectors between elements
if these are regarded as objects. A network can have other breakdowns into parts that are not network elements or
connectors.
3.5.12
network element
one of the connected things that together form a network (3.5.11)
3.6 Terms related to activity and participation
3.6.1
activity
something that happens or is being done
EXAMPLE 1 The pumping of batch B-101 from tank A to tank B on 2019-10-09 is a particular (3.2.1) activity.
EXAMPLE 2 Pumping is a generic kind (3.2.2) of activity.
EXAMPLE 3 “Pumping from tank A to tank B” is a specific kind of activity.
Note 1 to entry: An activity causes a change in the world.
Note 2 to entry: Different industry sectors define kinds of activity and roles (3.6.3) useful to their businesses.
Note 3 to entry: The beginning and end of an activity can be an arbitrary administrative decision. At an instant in time,
one activity can end and another, which consists of the same people and material, can begin.
Note 4 to entry: An activity can be intended to take place in the future. The term “planned” can be used as a synonym
for “intended”, and can imply not only an intention, but the existence of a plan (3.13.2).
[33]
Note 5 to entry: The FRISCO (Framework of Information System Concepts) report defines kinds of activity and
kinds of role.
3.6.2
participant
thing that contributes to the performance of an activity (3.6.1) or that is affected by an activity
EXAMPLE 1 Pump P-101 is a particular (3.2.1) participant in the activity of pumping batch B-101 from tank A to
tank B on 2019-10-09. The fluid that is pumped is also a particular participant.
EXAMPLE 2 John Doe is a particular participant in project Refurb-101 during 2018. He is the particular participant
with the role (3.6.3) of project manager.
EXAMPLE 3 The ship Arctic Queen is a particular participant in the operation of platform UGE-1 during May 2019. It
is the particular participant with the role of support vessel.
3.6.3
role
kind of participant
kind (3.2.2) of participant3.6.2)
EXAMPLE 1 Performer of pumping is a generic role.
EXAMPLE 2 “Performer of pumping from tank A to B” is a specific role.
EXAMPLE 3 Project manager is a generic role.
EXAMPLE 4 Support vessel is a generic role.

3.7 Terms related to breakdown
3.7.1
breakdown
tree structure of whole-part relationships such that at each level of the tree structure the vertices of the tree
are disjoint
EXAMPLE ISO 14224:2016 defines kinds (3.2.2) of breakdown for maintenance. A kind of breakdown for a pump
taken from ISO 14224:2016, 8.1 is shown in Figure 3.
Note 1 to entry: This breakdown has top level parts: power transmission, pump unit, control and monitoring,
lubrication system, and miscellaneous. The inclusion of miscellaneous makes this a complete breakdown.
Note 2 to entry: There can be different breakdowns of the same thing for different purposes, such as procurement,
construction, and maintenance.
Note 3 to entry: A breakdown can be a complete breakdown (3.7.2) or a partial breakdown (3.7.3).
Figure 3 — Kind of breakdown for a pump
3.7.2
complete breakdown
breakdown (3.7.1) where the sum of the parts (3.4.1) at a level equals the whole
3.7.3
partial breakdown
breakdown (3.7.1) where the sum of the parts (3.4.1) at a level does not equal the whole
Note 1 to entry: If a breakdown omits parts that are not relevant to its purpose, then it is a partial breakdown. Such a
breakdown is often turned into a complete breakdown by a part called “other” or “miscellaneous”.

3.7.4
breakdown element
part (3.4.1) that is a vertex within a breakdown (3.7.1) tree structure
3.7.5
functional breakdown
breakdown (3.7.1) such that each breakdown element (3.7.4) performs a function (3.8.3)
EXAMPLE The breakdown of a pump shown in Figure 3 is a functional breakdown because each part (3.4.1) has a
function.
A zonal breakdown of a pump that has a part “things mounted above the pump unit” is probably not a functional
breakdown. A part of the control and monitoring system and a part of the lubrication system may be above the pump
unit. Therefore, there is no function that is performed by the things above the pump unit as an aggregation.
Note 1 to entry: A zonal breakdown has the equipment items within a particular zone as a part. Each equipment item
has a function, but there may be no function that is performed by the aggregation of the equipment items within a zone.
3.7.6
assembly breakdown
physical breakdown
breakdown (3.7.1) of an assembly (3.5.2) into parts (3.4.1), each of which is an assembly element (3.5.3)
3.7.7
system breakdown
breakdown (3.7.1) of a system (3.5.6) into parts (3.4.1), each of which is a system element (3.5.8)
3.7.8
activity breakdown
breakdown (3.7.1) of an activity (3.6.1) into parts (3.4.1), each of which is an activity
EXAMPLE In chemical engineering, a Process Flow Diagram, which represents an overall kind (3.2.2) of activity,
shows a breakdown into elementary kinds of activity or unit operations, such as heat transfer.
Note 1 to entry: In engineering there are many hybrid diagrams, in which some symbols represent kinds of activity and
other symbols represent equipment items and their functions.
3.8 Terms related to behaviour, capability and function
3.8.1
behaviour
way a thing acts, transforms or reacts to inputs in a given condition or environment
EXAMPLE Stable hovering whilst lifting a load of 1 tonne is a behaviour, which is possessed by helicopter H-1234.
Note 1 to entry: A thing can have many behaviours. The behaviours of a material object (3.3.2) can include stress-strain
behaviours at different temperatures and load rates, creep behaviour, thermal expansion behaviour, and magnetic
behaviour.
3.8.2
capability
what something is capable of doing or being
EXAMPLE 1 The pump with serial number 98-12345 is a product (3.3.3). It has the capability of pumping a sand-sea
3 -1
water mixture continuously at a rate of 0,1 m sec with a head of 20 m. It has other capabilities at different heads, and
other capabilities for short periods.
When installed within system (3.5.6) S-101 as pump P-101-A, the pump with serial number 98/12345 has the capability
3 -
of pumping a sand-sea water mixture from tank A to tank B continuously at reduced power with a rate of 0,05 m sec
, or at full power for short periods. The installed pump cannot be operated continuously at full power because the
driver overheats.
EXAMPLE 2 It is a capability, within its operational envelope, of an assault craft to rescue refugees.

EXAMPLE 3 Delivering fire pumps is a capability which is possessed by helicopter H-1234.
Note 1 to entry: A capability is a potential of something. It is what a thing might do or be. This potential may never be
fulfilled.
Note 2 to entry: Kinds of thing that can have capabilities include equipment item, system, person (3.10.2), and
organization (3.10.1).
Note 3 to entry: A number of capabilities can be referred to as an “operational envelope”.
Note 4 to entry: In some circumstances a capability can be referred to as a “capacity”.
Note 5 to entry: The capabilities of a thing can change during its life.
Note 6 to entry: A product (3.3.3) has
...