IEC PAS 63088:2017

IEC PAS 63088 ®
Edition 1.0 2017-03
PUBLICLY AVAILABLE
SPECIFICATION
PRE-STANDARD
colour
inside
Smart manufacturing – Reference architecture model industry 4.0 (RAMI4.0)

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.

IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé Fax: +41 22 919 03 00
CH-1211 Geneva 20 info@iec.ch
Switzerland www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.

IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing 20 000 terms and definitions in
Technical Specifications, Technical Reports and other English and French, with equivalent terms in 16 additional
documents. Available for PC, Mac OS, Android Tablets and languages. Also known as the International Electrotechnical
iPad. Vocabulary (IEV) online.

IEC publications search - www.iec.ch/searchpub IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a 65 000 electrotechnical terminology entries in English and
variety of criteria (reference number, text, technical French extracted from the Terms and Definitions clause of
committee,…). It also gives information on projects, replaced IEC publications issued since 2002. Some entries have been
and withdrawn publications. collected from earlier publications of IEC TC 37, 77, 86 and

CISPR.
IEC Just Published - webstore.iec.ch/justpublished

Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: csc@iec.ch.
IEC PAS 63088 ®
Edition 1.0 2017-03
PUBLICLY AVAILABLE
SPECIFICATION
PRE-STANDARD
colour
inside
Smart manufacturing – Reference architecture model industry 4.0 (RAMI4.0)

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 25.040.01; 35.080; 35.240.50 ISBN 978-2-8322-4053-3

– 2 – IEC PAS 63088:2017  IEC 2017
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 9
2 Normative references . 9
3 Terms and definitions . 9
4 Assets in Industry 4.0 . 11
4.1 The object world . 11
4.2 Information carriers . 12
4.3 Assets and the information world . 12
4.4 Life (“vita”) and characterization of an asset . 13
4.5 Means by which an asset is actively presented, or made known, in the
information system . 14
4.5.1 General . 14
4.5.2 Unknown assets . 15
4.5.3 Anonymously known assets . 15
4.5.4 Individually known assets . 15
4.5.5 Assets administered as entities . 15
4.6 State in an asset’s lifetime (“vita”) . 16
4.6.1 General . 16
4.6.2 Type . 16
4.6.3 Instance . 16
4.7 Communication capability . 17
4.7.1 Communication capability of assets in the physical world . 17
4.7.2 Communication capability of assets in the information world . 18
4.8 Classification of assets in terms of presentation and communication
capability . 18
4.9 Representation by means of information and technical functionality . 19
5 Reference Architecture Model Industry 4.0 (RAMI4.0). 20
5.1 General . 20
5.2 Architecture axis (“Layers”) . 21
5.2.1 Overview . 21
5.2.2 Business layer . 21
5.2.3 Functional layer . 21
5.2.4 Information layer . 22
5.2.5 Communication layer . 22
5.2.6 Integration layer . 22
5.2.7 Asset layer . 23
5.3 Life cycle & value stream axis . 23
5.4 Hierarchy axis . 23
6 Industry 4.0 components. 24
6.1 General . 24
6.1.1 Overview . 24
6.1.2 Properties of I4.0 components . 25
6.1.3 Identifiability . 25
6.1.4 State in the lifetime (“vita”) . 25
6.1.5 Secure I4.0-compliant communication, services and quality of service . 26
6.1.6 Representation by information with I4.0-compliant semantics . 26

6.1.7 I4.0 system consisting of I4.0 components . 27
6.1.8 Nestability . 27
6.1.9 Encapsulability . 28
6.1.10 Domain specific functionality and state model . 29
6.2 Administration shell of I4.0 components . 29
6.2.1 General . 29
6.2.2 Basic structure of the administration shell . 30
6.2.3 DF header and DF body . 30
6.2.4 Partial models and views . 31
6.2.5 Properties . 32
6.2.6 Managing the administration shell . 34
6.2.7 Fundamental requirements for the administration shell . 36
6.3 Forms of I4.0 components . 36
6.3.1 Different assets with administration shells . 36
6.3.2 Asset with multiple administration shells . 37
6.3.3 Administration shell for multiple assets . 38
Bibliography . 39

Figure 1 – Structure of the object worlds with examples . 12
Figure 2 – Assets in the information world and their physical carriers . 12
Figure 3 – Life (“vita”) of an asset . 13
Figure 4 – Concepts of an asset . 14
Figure 5 – Component manager for administering entities . 16
Figure 6 – Active presentation of an asset in the information system and its
communication capability . 19
Figure 7 – CP notation system for classifying according to communication capability
and presentation (“publicity”) . 19
Figure 8 – Reference architecture model Industry 4.0 (RAMI4.0) . 20
Figure 9 – Hierarchical levels of RAMI4.0 . 24
Figure 10 – An I4.0 component as a necessary connection between the asset and the
administration shell . 25
Figure 11 – Nestability of I4.0 components . 28
Figure 12 – Encapsulability of I4.0-compliant and deterministic real-time
communication . 29
Figure 13 – Diagram of an I4.0 administration shell . 30
Figure 14 – Examples of domain specific models . 31
Figure 15 – Diagram of how views are created . 32
Figure 16 – Availability of administration shells via repository or directly via the
represented assets . 35
Figure 17 – Different assets that become I4.0 components by adding the administration
shell . 37
Figure 18 – Representation of an asset by means of multiple administration shells . 37
Figure 19 – Representation of multiple assets . 38

– 4 – IEC PAS 63088:2017  IEC 2017
Table 1 – Basic views of a partial model . 32
Table 2 – Property classes. 33

INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
SMART MANUFACTURING –
REFERENCE ARCHITECTURE MODEL INDUSTRY 4.0 (RAMI4.0)

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
A PAS is a technical specification not fulfilling the requirements for a standard, but made
available to the public.
– 6 – IEC PAS 63088:2017  IEC 2017
IEC PAS 63088 has been processed by IEC technical committee 65: Industrial-process
measurement, control and automation.
The text of this PAS is based on the This PAS was approved for publication
following document: by the P-members of the committee
concerned as indicated in the following
document
Draft PAS Report on voting
65/645/PAS 65/655/RVDPAS
Following publication of this PAS, which is a pre-standard publication, the technical committee
or subcommittee concerned may transform it into an International Standard.
This PAS shall remain valid for an initial maximum period of 3 years starting from the
publication date. The validity may be extended for a single period up to a maximum of
3 years, at the end of which it shall be published as another type of normative document, or
shall be withdrawn.
A bilingual version of this publication may be issued at a later date.

IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
INTRODUCTION
Background
Industry requires constant attention on optimization, cost efficiency, energy efficiency,
environmental concerns, quality, security, safety, time-to-market, inventory reduction,
simulation, ease of maintenance, etc. Customers also want to satisfy new requirements and
address new use cases now reachable given the availability of new technologies. Addressing
these challenges, several projects in different countries were issued with similar names and
aims, e.g. in Germany “Industrie 4.0”, in France “Industrie du Futur”, in China “Intelligent
Manufacturing”, in Japan etc.
Manufacturers, customers, service providers are working in a more and more global market.
The need of interoperability of products, open interfaces, etc. can only be achieved with
International Standards. To cover these needs, IEC and ISO have activities related to Smart
Manufacturing.
Objective
This specification defines a Reference Architecture Model to identify, structure, and illustrate
the different areas where standards exist or standards are required. It allows setting
standards in relation to different aspects, hierarchies and life cycles.
Life cycles are relevant to products, to assets in the factory or plant, to orders from planning
to cash and to the supply chain covering the process from source to delivery.
In addition, this specification defines term and definitions generally for Smart Manufacturing.
As Smart Manufacturing is covering different domains (batch, continuous, discrete, etc.),
terms need to be harmonized and globally accepted.
The fundamental purpose of Industry 4.0 is to facilitate cooperation and collaboration between
technical objects, which means they have to be virtually represented and connected. In this
context, a technical object is an object that is of value to an organization, which therefore not
only means physically tangible objects, but also intangible objects such as ideas, archives
and software. The concept of Industry 4.0 is intended to create digital description rules for a
technical object throughout its entire lifetime, and for the associated changes in value, in the
form of the Reference Architecture Model for Industry 4.0 “RAMI4.0”. The purpose of this
model is to represent the technical object and all aspects relevant to it, from its development,
production and use right through to its disposal. The Industry 4.0 component provides a digital
description of the object, making it possible to represent that object virtually.
Technical objects are intentionally manufactured in order to fulfil a specific purpose. They
possess common characteristics in terms of their lifetime and the associated changes in
value. Technical objects for which a “change in value” or an “owner” are important aspects are
also referred to as “technical assets”. Because this is almost always the case, the terms
“technical object” and “technical asset” can be regarded as synonymous. In this document,
the term “technical asset”, or simply “asset” is used.
This document describes two fundamental reference models for the Industry 4.0 concept:
– The reference architecture model RAMI4.0 is a reference model of Industry 4.0 reference
architecture and gives a structured description of fundamental ideas. See Clause 5.
– The I4.0 component reference model provides digital access to this description. See
Clause 6.
– 8 – IEC PAS 63088:2017  IEC 2017
The central concept of Industry 4.0 is that assets can be combined in any way, and these
assets are formally described in sufficient detail for use in the digital world. This methodology
not only enables sufficient generic descriptions of a configuration, but through an increasing
degree of detail also allows for very specific descriptions. This is a core concept regardless of
the way in which the asset is used.
To virtually represent configurations of assets and the connections between them, the
“principle of recursive description of assets” is used to characterize an asset as follows:
– the structural description is compliant with RAMI4.0;
– a configuration of two or more assets collectively forms a new asset, which is described
using RAMI4.0;
– components of an asset can themselves represent separate assets that are described with
RAMI4.0;
– the asset description is provided as structured information in the administration shell of
the I4.0 component that acts as a virtual representation of an asset.
This means that any configuration can be digitally represented to any degree of granularity by
describing structured assets, and combinations thereof, using RAMI4.0.

SMART MANUFACTURING –
REFERENCE ARCHITECTURE MODEL INDUSTRY 4.0 (RAMI4.0)

1 Scope
This document, which is a PAS, describes a reference architecture model in the form of a
cubic layer model, which shows technical objects (assets) in the form of layers, and allows
them to be described, tracked over their entire lifetime (or “vita”) and assigned to technical
and/or organizational hierarchies.
It also describes the structure and function of Industry 4.0 components as essential parts of
the virtual representation of assets.
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.
IEC 61360-1, Standard data element types with associated classification scheme for electric
components – Part 1: Definitions – Principles and methods
IEC 61360-2, Standard data element types with associated classification scheme for electric
components – Part 2: EXPRESS dictionary schema
IEC TR 62794 , Industrial-process measurement, control and automation – Reference model
for representation of production facilities (digital factory)
IEC TS 62832-1, Industrial-process measurement, control and automation – Digital factory
framework – Part 1: General principles
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.1
administration shell
virtual digital and active representation of an I4.0 component in the I4.0 system
Note 1 to entry: An administration shell contains the manifest and the component manager.
_____________
Withdrawn.
– 10 – IEC PAS 63088:2017  IEC 2017
3.2
architecture
fundamental concepts or properties of a system in its environment embodied in its elements,
relationships, and in the principles of its design and evolution
[SOURCE: ISO/IEC/IEEE 42010:2011, 3.2]
3.3
archive world
all the information in the digital world which is no longer valid or up-to-date and which
therefore can no longer be changed
Note 1 to entry: Information which is no longer valid or up-to-date is transferred to the archive world.
Note 2 to entry: No statement is made on when the information is transferred from the model world or state world
to the archive world.
3.4
asset
object which has a value for an organization
3.5
service
separate scope of functions offered by an entity or organization via interfaces
Note 1 to entry: This definition is not the same as the definition of services by the OASIS-RM (“Services are the
mechanism by which needs and capabilities are brought together”).
3.6
entity
uniquely identifiable object which is administered in the information world due to its
importance
3.7
information world
digital world or cyber world
ideas, concepts, algorithms, models and entirety of representations of physical objects and
people in the virtual environment
Note 1 to entry: The framework for considering each entirety needs to be defined.
Note 2 to entry: The elements of the information world can be semantically related to each other.
3.8
component manager
organizer of autonomous administration and access to resources of the relevant I4.0
component, such as the I4.0 component itself, object, technical functionality, virtual
representation
Note 1 to entry: In many documents, the component manager is referred to as the resource manager, but this
should be called the component manager in future.
3.9
manifest
externally accessible, defined set of meta-information on the functional and non-functional
properties of the relevant I4.0 component
Note 1 to entry: The manifest can be regarded as similar to the manifest in information technology.
3.10
physical world
all actually existing objects and people

Note 1 to entry: The real world is the same as the physical world.
Note 2 to entry: Loaded or stored software is part of the physical world.
Note 3 to entry: The framework for considering each entirety needs to be defined.
3.11
reference architecture
model for an architecture description (for I4.0) which is generally used and recognized as
being suitable (has reference character)
Note 1 to entry: A reference architecture can be defined on the basis of a reference model.
3.12
reference model
model that is generally used and recognized as being suitable (has recommendation
character) for deriving specific models
3.13
value-added chain
sequence of processes that add value (linear or hierarchical, which formally means acyclically
aligned)
Note 1 to entry: Company boundaries are not necessarily relevant for a value-added chain or value chain.
3.14
value-added system
network or system of value-added chains that can include connections and dependencies
between them
3.15
value-added process
process during which a commodity can be created which is valuable for a customer
Note 1 to entry: The commodity does not have to be tangible (such as a raw material or manufactured product),
but can also be intangible (such as knowledge, information or a service).
Note 2 to entry: The determination of the value or price is not considered here.
Note 3 to entry: Value-added processes are value activities according to Porter.
4 Assets in Industry 4.0
4.1 The object world
Figure 1 shows the structure of the object worlds. In the object world of Industry 4.0, assets
from the information world and the physical world are considered. Besides these assets,
people (the human world) also play an important part. The information world is divided into
the model world, the state world and the archive world. The model world contains objects
such as meta-documents, models, concepts, technical documentation, production plans and
procedural descriptions. The state world describes the current state. The archive world
contains the recorded state and life cycle information of processes that have taken place.
These can be production processes, development processes, maintenance processes and so
on.
The physical world includes all physical products, installations, resources, IT systems, loaded
programs, etc. When classifying software, it should be noted that the algorithm itself belongs
to the information world, but the executable program loaded to a system is part of the physical
world. People are part of the physical world and participate in the information world. Because
of their intelligence and freedom to make decisions, human beings have a special status.

– 12 – IEC PAS 63088:2017  IEC 2017
Human world
Human
Model world State world Archive world Physical world
- Meta-documents (standards, - Current - Life cycle - Products
directives) measurements documentation - Resources
- Technical documentation - Effective target - Events - Production systems (equipment items,
(functional diagrams, plant value - Status histories sensors, actuators)
diagrams, product descriptions, - Current - Project histories - IT systems, control systems (computer,
procedural descriptions) configuration - Processes programs, data carriers, cables)
- Operative plans (production parameters - Cabinets, paper
plans, project plans)
- Business process description
Information world Physical world

IEC
Figure 1 – Structure of the object worlds with examples
4.2 Information carriers
Figure 2 shows examples of various carriers of information. A plan, for example, can be
stored as an xml or pdf file on a computer. It can also be inside somebody’s head or printed
out on a piece of paper. In each case, the information asset “plan” is the same. The character
of the physical carrier does not alter the information asset. If the carrier is destroyed, so is all
the information stored on it. To prevent information from being lost, copies of it can be made
on multiple carriers. However, they are all still the same asset.
Assets in the
Information world
information world
USB Brain Paper
Physical world
stick
Carrier 1 Carrier 2 Carrier 3
IEC
Figure 2 – Assets in the information world and their physical carriers
4.3 Assets and the information world
Every asset has a value for an organization. It represents an artefact that is specifically
intended to perform a particular role in a particular system. Assets are intentionally
manufactured in order to fulfil a specific purpose. They possess a common “vita”, or lifetime,
and the associated change in value. See Figure 3. Assets for which a “change in value” or an
“owner” are important aspects are also referred to as “technical assets”.
The key task in Industry 4.0 is to take technical assets from the physical world and virtually
represent them in the information world. The physical world is to be understood to mean the
entirety of all real assets and people.

The following applies to every asset.
– The asset is designed, created, used and disposed of.
– The asset can be an idea, a software program, an archive, a service or any physical item
(in other words it does not have to exist in a physical form).
– The asset has a lifetime.
– The asset is clearly identifiable.
– The asset is represented in the virtual world by its administration shell.
– The asset can have multiple virtual representations specified according to the rules of
Industry 4.0 for different purposes.
– Assets can be combined to create new assets with different properties.
– The asset is characterized in a process by means of time, location and state.
– Each piece of information has a carrier.
– The asset’s characteristics are described using Industry 4.0 vocabulary that includes a
collection of terms which describe properties.
EXAMPLE: Assets in the context of Industry 4.0 are whole installations or parts thereof, electronic modules,
subsystems and systems, machinery, plants and networks, services, concepts and ideas, plans, archives and
programs.
3. Provision
2. Production
4. Usage
1. Commissioning
7. Disposal
6. Repair 5. Maintenance
IEC
Figure 3 – Life (“vita”) of an asset
4.4 Life (“vita”) and characterization of an asset
Each asset has a specific lifetime, during which it serves the purpose for which it was
specifically created (see Figure 3). The way it is created depends on the type of asset.
Creation can mean development (of a type), engineering (of a plant), measurement (of a
status), construction (of an installation) or production (of a product). In this context, these are
all creation processes. Once an asset is created, it exists, but it is not yet ready to use. The
provision phase includes all processes between the time the product is created and the time it
is ready and working at the place of use. Provision processes include shipping, transport,
warehousing, configuration and assembly, and for software assets, processes such as
release, downloading and installation. After provision, the asset is installed and ready to use
on site, in other words, it is ready to perform its intended role as a technical device. In the
subsequent phase, two different uses of the asset shall be taken into account: usage and
maintenance. When being used, the asset is part of the technical system for carrying out the
desired technical (production or usage) processes. During maintenance, the asset is still a
product whose functionality shall be maintained or restored. Maintenance can be carried out
by the user, by an external workshop or by the manufacturer. The work can take place on site,
by remote maintenance or (for example after it is removed) at a workshop. Certain
maintenance procedures can be regarded as a loop, involving a renewed manufacturing
phase and recommissioning, while others are simply a change of status of the asset in use.

– 14 – IEC PAS 63088:2017  IEC 2017
As regards the information world, an asset can be characterized as shown in Figure 4. It:
– is presented, or made known, in a certain way (i.e. is known or not known to a certain
degree);
– has a specific state within its life (at least a type or instance);
– has communication capability;
– is represented by means of information (data);
– has technical functionality.
(Technical) function
Representation by means of information
Communication capability
State within its lifetime
Presentation within the system
IEC
Figure 4 – Concepts of an asset
4.5 Means by which an asset is actively presented, or made known, in the information
system
4.5.1 General
An asset exists in itself and has a specific lifetime. This is true for all types of asset. Initially,
however, the existence of the physical asset, its identity, state and lifetime (“vita”) are not
known in the information system. One of the most important questions of system design is
whether and to what extent this information is made known to the information system, and
how much of that information is presented in the system.
An asset in the information world is at the very least known in its own information system. If
information on physical assets is contained within the information system, then the
administration objects that manage the asset need to be created and supplied with

information. An asset can be classified as follows, depending on the amount of information
available in the information system:
– unknown;
– anonymously known;
– individually known;
– administered as an entity.
4.5.2 Unknown assets
An unknown asset is one that is not known in the information world.
4.5.3 Anonymously known assets
An anonymously, not individually known asset is one which can only be recognized in the
information world as an asset of a particular type at a particular place.
EXAMPLE: A screw is in a box with other screws. Even if the number of screws in the box is known, no individual
properties can be assigned to any of the screws other than the general ones common to that type. If an asset that
is not individually identifiable is included in a system, then it can be indirectly identified by means of its location. If
a screw is installed in a plant, then it can be determined that precisely that screw installed at that particular
location is rusty and has to be replaced. However, this is only true as long as the screw is installed. Once it is
removed, it ends up in the scrap bucket and can no longer be identified. The same goes for products such as
punched parts. During the punching process, it is possible to identify which punched part is in which section of the
matrix. After it is discharged, the part is no longer individually identifiable, but the information system still knows
that this punched part exists and is in the discharge container.
4.5.4 Individually known assets
An individually known asset is unambiguously identifiable. It has a unique name that is known
in the information world. The system has an identification method with which the asset can be
identified in the physical world and assigned to the name object.
NOTE Here it is irrelevant which technology is used for identification: it can be an ID code physically attached to
the asset (nameplate with serial number, barcode, RFID, etc.), an analysis of characteristic physical properties
(fingerprint etc.) or a deterministic and systematic tracking strategy in the system (coil, batch, etc.). In each case,
the detected asset can be assigned unambiguously to the name object in the information world.
4.5.5 Assets administered as entities
An entity is an unambiguously identifiable asset which, due to its importance, is administered
in the information world.
Entities are assets that possess objects of their own so that they can be administered and
used, in other words they are represented by information.
Their representation by information means that data on the asset is kept. This data can be
kept either on or in the relevant I4.0 component (as described in Cause 6) and can be made
available to the outside world using I4.0-compliant communication. Alternatively, the data can
be kept on a (higher-level) IT system that makes it available to the outside world by means of
I4.0-compliant communication.
I4.0-compliant communication shall take place in such a way that it is possible to access the
information of a representation of the relevant I4.0 component either in the asset itself or in a
(higher-level) IT system.
The functionality thus available in the information system goes far beyond mere identification.
It includes functions for purposes such as tracking assets, recording lifetime data, operational
management of the company’s own production process, and automated monitoring and quality
assurance. If the administration functions are encapsulated in a functional unit and carry out
their tasks proactively, the functional unit is known as a component manager (see Figure 5).

– 16 – IEC PAS 63088:2017  IEC 2017
Whether or not an asset is regarded as an entity is a design decision in each individual case.
As shown in Figure 5, entities cannot only be assets in the physical world, but also assets in
the information world.
EXAMPLE: The lifetime of a radar probe is documented on the left of Figure 5. The radar probe is regarded as an
entity and is given its own component manager. The example on the right documents the lifetime (creation, release
and maintenance processes) of a diagram (P&ID). The P&ID becomes an entity and is also given its own
component manager. In the model used here, the asset itself is conceptually separate from its administration.

Component Component
manager of the manager of the
administration administration
Administered by
shell shell
P and ID
Intangible asset
Information world
Physical world
Administered
by
Tangible asset
IEC
Figure 5 – Component manager for administering entities
4.6 State in an asset’s lifetime (“vita”)
4.6.1 General
Throughout its lifetime, an asset has a particular state at a particular time at a particular
location. This state can be described more precisely using additional information. When
observing an asset, a distinction is made between type and instance. Depending on how the
asset is used in the value-added chain, the properties and state of its type or of its specific
instance are relevant. Both types and individual instances are subject to usage and
maintenance.
4.6.2 Type
The type of an asset defines the sum of the properties which are characteristic for all
instances of that particular asset. The type of an asset is unambiguously identifiable and
arises with the initial idea, in other words when it is created, e.g. during the development
phase. This means, for example, ordering, development and testing, right up to the initial
sample and prototype production. Once all tests required for validation are completed, the
type is released for series production, which means that instances of that type can be
produced.
4.6.3 Instance
An instance is a specific, unambiguously identifiable asset that is characterized by the
properties of a type. An instance always has an unambiguously relationship to its type.
For a physical asset, concrete assets are created in production on the basis of the type. Each
manufactured asset represents an instance of a type and can be utilized. The instances can
be sold, delivered to customers, used by customers and maintained.

For an asset in the information world, instances are created on the basis of the type, for
example by allocating and initialising data structures, which are used, modified and later
released again.
4.7 Communication capability
4.7.1 Communication capability of assets in the physical world
4.7.1.1 General
Assets in the physical world can have a physical application (e.g. a pipe, or a cable), can
function as inform
...