26th Annual INCOSE International Symposium (IS 2016)

Edinburgh, Scotland, UK, July 18-21, 2016

The Reference Designation System (RDS)

A common naming convention
for systems and their elements

Henrik Balslev
Systems Engineering A/S
www.syseng.dk
+45 21 68 48 67
hb@syseng.dk

Copyright © 2016 by Henrik Balslev. Published and used by INCOSE with permission.

Abstract. This paper introduces the Reference Designation System (RDS) as defined in the
ISO/IEC 81346 standard series. The 81346 standard is a horizontal standard within ISO and
IEC, and thereby a reference document for all other international standards. RDS identifies
systems and their elements. A reference designation (a TAG number) is the output of RDS. The
TAG numbers act as labels for the system and the system elements, and are used for instant and
unambiguous recognition across different kinds of documentation and labelling of tangible
products as well as non- tangible products such as different models in a software tool. RDS is
an international “naming convention” designed for systems and their elements and a practical
technique to underpin a common understanding among different disciplines. The use of RDS
as a fundamental system naming convention is not widely known within the INCOSE
environment. By this paper, the author wishes to reach out to INCOSE and systems
engineering in general, so the principles of RDS is to be better understood and recognized as a
basic part of systems engineering tool box. RDS provides generic principles and are applicable
in more or less all technical disciplines; among these are civil engineering, mechanical
engineering, electrical engineering and software engineering. Application examples are
provided and a case example showing the economic benefit is presented.

Introduction
In the design of systems there is a need for identification of the systems and their elements.
This may be done simply by naming the systems, but as complexity grows there is a need for
specific identifiers of systems and their elements. The identification ensures that the elements
of system of interest can be recognised across various models and documents by both
stakeholders and IT systems.
Very often, system and system elements and their related models are not labelled at all or a
given some kind of TAG number created to carry a range of information in addition to the main
purpose; identification. Such TAG numbers seldom comply with international rules, but are
instead company specific.
The only international standard for creating unambiguous identifiers for systems and their
elements is the ISO/IEC 81346 standard series, which has a very clear scope. It defines the
rules for reference designation systems (RDS), where the output is reference designations (RD).
An RD is an identifier, designed to unambiguously identify systems and their elements by a
combination of well-defined relations (part-of and type-of relations) and different aspects
(function, product, location and type). The RD is a clear, sharp and easy-to-learn international
naming convention.
The RD is also a TAG, whereas a TAG is not necessarily a RD. The main difference between
any random TAG and an RD is, that the RD by default determines system types and element
relations, whereas there is no guarantee for this when TAG’s are created without the rules from
81346 applied.
An important mechanism of RDS is, that RDS handles flexible system structures by multiple
views, recognized as “tree-like structures” in 81346. This means that the output RD has no
fixed format, but is to be read and understood as an unlimited navigation in system structures.
In contrast to RD, any random TAG often has a fixed notation, which may lead to limitations in
the design of system structures.
RDS is not linked to any specific domain, but acts as a neutral provider. This means that RDS
has potential applications in a wide range of industries.
The RD creates a link among various models of the system(s) which are designed and
engineered by a wide range of actors, and thereby creates both a common language among
humans and among various computer systems.

Background – The standard for designations

The basic for RDS was defined by IEC 60113-2 in 1971. After this came 3 successors: IEC
60750 (1983), IEC 61346 (1996) and lately ISO/IEC 81346 (2009).
With the revision in 1996, the use of item/reference designations became further extended. It
was recognised that reference designations could be used as a powerful tool for information
management and systems thinking became an integral part of the standard.
Information was not necessarily contained in ready-made documents, but could be fragmented,
existing in different data bases, from which documents could be put together as needed
(including graphical presentations). In such an environmen , it was required to use the
reference designation system as a "navigation tool".
Instead of "smart" economising with computing power it had become more essential to
describe things logically and straightforward in order to enhance functionality, exchangeability
and communication. One of the important requirements was that the reference designations
should be possible to use over the entire life cycle of the objects.
In the latest edition, ISO/IEC 81346-1:2009, the rules established in the successors are
maintained, but more emphasis is put on the description of the concepts in order to enhance the
understanding and applicability of the standard, including systems thinking.
Although it can be argued about where exactly the boundaries should be, it is possible to
illustrate roughly the ambitions and the scope of the revisions as in figure below:
 Application domain

Common ISO/IEC IEC 81346-1:2009

Technical IEC 61346-1:1996
information in
general

Technical
documentation in
IEC 60750:1983
general

Diagrams with IEC 60113-2:1971

supplementary
documents

Life cycle
Design Manufacturing Operation Phase out /
recycle
Engineering Installation Maintenance /
improvements

Figure 1. Scope of reference designation standards

The Reference Designation System

The introduction of ISO/IEC 81346-1:2009 defines the following (extract in italics):
By applying the structuring principles, even very large sets of information in a complex
installation can be handled efficiently.
The structuring principles and the rules for reference designations provide a system that is
easy to navigate within and easy to maintain. This system provides an excellent overview on a
technical system(*) since composite structures are simple to establish and understand.
The structuring principles and the rules for reference designations allow, by accepting more
than one aspect, that more than one coding principle can be applied. This technique also
allows ‘old structures’ (that means existing structures) to be handled together with ‘new
structures’ by using multiple unambiguous identifiers.
The structuring principles and the rules for reference designations support individual
management for the establishment of reference designations, and enable subsequent
integration of modules into larger constructs. They also support the establishment of reusable
modules, either as functional specifications or as physical deliverables.
(*) Systems and systems thinking is an integral part of the standard.
 Overview of the 81346 standard series
The ISO/IEC 81346 standard series consist of the following parts:

Title
Content:

IEC 81346-1 (2009) The fundamental rules:

Industrial systems, Installations and Equipment and
Industrial Products – Structuring Principles and
Reference Designations – - Objects
- Systems
Part 1: Basic rules.
- Structuring
- Aspects
- Designations
(TAG’s)

IEC 81346-2 (2009 – under revision 2016) Letter codes for

Industrial systems, Installations and Equipment and classification:
Industrial Products – Structuring Principles and
Reference Designations –
Part 2: Classification of Objects and Codes for - Systems
- Elements
Classes.
- Components
- Spaces

ISO/TS 81346-3 (2012) Technical Specification A technical specification

Industrial systems, Installations and Equipment and used for special domains.
Industrial Products – Structuring Principles and
Reference Designations –
Part 3: Application rules for a reference designation
Contains limitations to the
system.
rules provided in part 1.

ISO/TS 81346-10 (2015) Technical Specification The industry related part of

Industrial systems, Installations and Equipment and 81346 applicable for power
Industrial Products – Structuring Principles and plants.
Reference Designations –
Part 10: Power plants.
“RDS-PP” Letter codes for systems in a
power plant.
 ISO/DIS 81346-12 (2016 – Draft International The industry related part of
Standard) 81346 applicable for the
Industrial systems, Installations and Equipment and building industry.
Industrial Products – Structuring Principles and
Reference Designations –
Part 12: Construction works and building services.
Letter codes for systems in a
“RDS-CW” construction complex /
a building.

Core elements of RDS

The 81346 standard series concerns the designation of technical objects – of any given kind,
but mostly recognized as systems – in structures in a well-defined manner.
Basically 81346 uses relations to handle complexity:

used for structuring of objects

part-of relations
determining system and
(partitive relations)
elements in 81346-1

and

used for classification

type-of relations
of systems and components
(generic relations)
in 81346-2 (the letter codes)
According to 81346, a reference designation system consists of:

1 A single level or multi-level structure Single level:

This is used to structure objects (systems),

based on part-of relations:

Multi-level:

2 One or more aspects of the structures

%
This is used to clear the content of the structure,
that is to filter out information and only see
specific aspects of a system in specific part-of -
relation.

Aspects are: +

% Type
- Product =
+ Location
= Function
#
# (user defined)

3 Numbers 01
02
This is used to separate objects from one
03
another.
04
 Note: Preceded zeros may be used (like here)
but shall have no specific meaning. 05

It may in addition (often) also have:

4 Classes in form of letter codes A

BT
This is used to recognize the class of object and
QQC
to identify objects with similar properties.
…

The reference designation of a system and system elements are made by combining:

or

ASPECT
with at least one

and often a LETTER CODE

and a 123

The reference designation identifies systems and their elements unambiguously across all
disciplines and documents, it systems etc. A reference designation is therefore a code or an
"address". It indicates where in the reference designation system an object belongs, so that any
object of interest can be retrieved.

Examples are provided in the following chapter.

Syntax of RDS
The syntax of the reference designation is as shown in figure below:
Single-level
reference designation

P AA NN . AA NN . AA NN ... . AA NN

Prefix
=/+/-/#/%

Prefix, space or

Class letter code

See Appendix A
Number

Figure 2. Reference designation syntax [Figure from ISO 81346-12]

NB! Reference designations are read from right to left, as the rightmost part of the code string
is the object of interest which is designated!
Examples of reference designations are:

Object (system) Reference designation

Door no. 5 (QQC5) -QQC5

Wall construction no. 1 (AD1)

part of
-B1.AD1
Wall system no. 1 (B1)

Door no. 2 (QQC2)

part of
Wall construction no. 3 (AD3)
-B1.AD3.QQC2
part of
Wall system no. 1 (B1)

Ventilation plant no. 4 (HF4)

part of
=J1.HF4
Ventilation system no. 1 (J1)
 Switch no. 6 (SFA6)
part of
Lighting system no. 2 (HH2)
part of =K2.HG1.HH2.SFA6
Power supply system no. 1 (HG1)
part of
Electrical system no. 2 (K2)

The reference designation is considered to be an attribute (metadata) to any system or system

element, which identifies the system unambiguously. Therefore, the reference designation
shall be shown next to (or nearby / as a part of) the system or the element in the system
documentation or system model representation, and thereby creating the common
understanding of different views of systems and their elements - along with a common
understanding of which system (or element of the system) are viewed.

Sub-suppliers and RDS

A fundamental technique of RDS is to allow sub-suppliers to enable an RDS system which fit
their system design. As a logical consequence of this, sub-contractors are not to follow an
overall RDS “number” principle from clients, but more to be implemented as a part of a larger
whole.
Therefor rule 5 in 81346-1 says “The object represented by the top node shall not be assigned a
single-level reference designation”. This ensures that sub-suppliers can maintain a stable
system design, and keep supplier identification within documentation without adopting
different TAG systems from a range of clients.

Figure 3. Adaption of a system from sub-supplier into system of interest

 Application of reference designations (RDS)
The appliance and knowledge of reference designations varies significantly among different
domains. Because the technique originates from the electrotechnical domain, where safe
recognition and a reliable link between real-world and documentation is fundamental (for
safety reasons), the RDS is widely implemented in IT software tools for electrical
diagramming.
As the application area of the 81346 standard was expanded in 2009, more and more software
tools implements the principles, for example tools for process diagramming and modelling
tools for Information Modelling. Whether an IT system adopts the RDS technique or not is a
question of how well it can handle part-of relations in documentation and modelling and
multiple structures.
The RDS mechanism is generic and not linked to any specific domain. As an example of the
expansion of the application of RDS, the RDS system has lately formed the basis for labelling
of systems in the Danish building industry (wall system, roof system, HVAC system etc.),
where a “common language” by means of a reliable interdisciplinary naming convention was
required as a safe identifier for exchange of information across disciplines and across very
different IT tools used for modelling and simulations.
Other application areas are emerging such as oil & gas industry (off-shore), wind turbine
industry. Various plants (cement, mining, water distribution etc.) are also examples of
industries where the RDS gains favour.

The economic benefit of RDS

ISO has published international case studies “Economic benefits of standards vol. 1 & 2”1
providing cases for economic aspects of working with international standards in a broad sense.
Because RDS is based on a system mind-set, a decision to apply RDS automatically leads to
system awareness, and thereby the door is open to apply systems engineering.
In INCOSE it is recognized, that systems engineering is a point of synchronization for
knowledge and any other related subject of design. What RDS offers in this point of
synchronization is a description of the core structures, and an unambiguous naming convention
for the systems and system elements to be used across disciplines and tools.

1
See references.
 RDS
81346

Figure 4. RDS as the naming convention of systems in the point of synchronization

Case
RDS has been applied for a client acting as EPC within the construction area of large and
complex transformer platforms for off-shore use. A design concept based on elements of
systems engineering was implemented, as the previous designs had grown dramatically in
complexity with loss of time, quality and money as a consequence.
The result was to introduce a concept based on system architecture, describing the system and
system elements, and label this structure in accordance with RDS. The RDS now ensures a
stability of labels so navigation in the complex system structures are unambiguous in the full
life cycle, from tender to design over construction and commissioning and maintenance.
Real figures for the project show the dramatic impact of a clear architecture and designation
with RDS. The economic benefit becomes clear for the 2nd project and continues to increase in
the 3rd project as shown in figure 5 (below):
 Figure 5: Figures from a project, implementing system engineering and RDS
(reproduced by permission from Semco Maritime A/S).

Summary
Systems engineering has a need for a common language, which RDS can provide. Since the
basic mechanism of the common language originates from industrial systems, installations and
equipment as given in the ISO/IEC 81346 standard series (RDS), the principles can be adopted
in most technical industries. A few application examples are given in appendix A.
The output from RDS is the reference designation (RD). The RD is designed to create links
among various models of the systems which are designed and engineered by a wide range of
actors, and thereby creating both a common language among humans and among various
computer systems.
The RDS can be seen as simple yet very strong and flexible: The simplicity is based on
recognition of systems (objects) organized in type-of relations in the classification system from
which they are redrawn. Classes from the classification system can subsequently be combined
in any way needed in part-of relations, equivalent to organization of systems and system
elements.
RDS provides a lifecycle stable code based on classification. This enables pre-coding of
objects in software object libraries, easy letter coding which is recognizable for humans and
computer systems, and an object oriented approach to the complexity of systems organized in
part-of relations.
RDS acts as the spine for the common language among all disciplines. It is creating an
inter-disciplinary understanding of systems and their constituents across actors and
IT-platforms.
Application of RDS in a real world case example demonstrates a significant positive impact in
consumption of hours, with up to 50% reduction by the third project.
 Appendix A - Examples of application
This appendix shows different applications of RDS in different domains.

EXAMPLE 1:
RDS has been used to address the complexity of a roof (system) and its elements by means of
the product aspect (-), determining how the system is constructed.

Figure 6: Example of RDS application in the building construction domain

EXAMPLE 2:
A manufacture of bearings has organized objects with common properties and designate these
types by means of the type aspect (%) in RDS.

Figure 7: Example of RDS appliance for types of bearings

EXAMPLE 3:
A quantity surveyor has organized windows with common properties and designate these types
by means of the type aspect (%) in RDS.

Figure 8: Example of RDS appliance for types of windows

EXAMPLE 4:
Functions in a diagram of a ventilation plant (G1) designated by means of the function aspect
(=) in RDS:

=BPA6
=BPA3

PT
PT

=BTB3
=BTB1

TT
TT

=BTA3
=BTA1

TS
TS

=GQA2
=BPA5
PT
=QMB1

=EQB1
M

=BTA2

TS
=HNC1
=BPA2

=EPB1
PT

=BTB2
TT
=EGB1
=GQA1

=HNC2
=BPA1

=BPA4
PT

PT
=QMB2
M
=G1

Figure 9: Example of RDS function aspect applied in a functional diagram

EXAMPLE 5:
Spaces on a plan of level 2 in a building are designated by means of the location
aspect (+) in RDS:

Figure 10: Example of RDS location aspect applied in a building

 References
ISO/IEC 81346-1: (2009): “Industrial systems, installations and equipment and industrial
products - structuring principles and reference designations -
Part 1: Basic rules”

ISO/IEC 81346-2 (2009): “Industrial systems, installations and equipment and industrial
products - structuring principles and reference designations -
Part 2: Classifications of objects and code for classes”.
NOTE: Under revision. CDV version is to be launched in May 2016.

ISO 704 (2009): “Terminology work - Principles and methods”

ISO 22274 (2013): “Systems to manage terminology, knowledge and content –

Concept-related aspects for developing and internationalizing classification systems”

Balslev, Henrik (2014): “Reference Designation System for Coding System Objects”,
INCOSE Insight Volume 17, April 2014. Article.

Economic benefits of standards. International case studies. Volume 1 & 2.

International Organization for Standardization 2011-2012.
ISBN 978-92-67-10556-7 & ISBN 978-92-67-10580-2.

Video introduction on YouTube:

RDS / 81346 - It’s all about creating a common language (12 minutes’ video)
https://www.youtube.com/watch?v=QO4cX4oNpmc
 Biography

Henrik Balslev, CEO and founder of Systems Engineering A/S (DK) has a
Bachelor of Science in Electrical Engineering, Technical University of
Denmark, Copenhagen (1988). Today he is acting as a specialist in
bridging between practical engineering disciplines and the theory and rules
anchored in ISO & IEC Standards, some of them of which he acts as the
convenor. He is recognized as an international expert in Reference
Designation Systems (RDS) in accordance with ISO/IEC 81346 standard
series, which supports SE. Furthermore, he is holding the position of trust
as president of INCOSE Denmark. See www.syseng.dk and
www.81346.com for more information and free downloads.