din/dke – roadmap - home - 3c creative communication … · 2017-10-06 · this standardization...

GERMAN STANDARDIZAT ION ROADMAP

Industry 4.0

Vers ion 2

D I N / D K E – R o a d m a p

2 STANDARDIZATION ROADMAP

Published by

DIN e. V.

Am DIN-Platz

Burggrafenstraße 6

10787 Berlin

Tel.: +49 30 2601-0

e-mail: [email protected]

Internet: www.din.de

Issue date: January 2016

Cover photo: Fraunhofer IPA

DKE Deutsche Kommission Elektrotechnik

Elektronik Informationstechnik in DIN und VDE

Stresemannallee 15

60596 Frankfurt

Tel.: +49 69 6308-0

Fax: +49 69 08-9863


Internet: www.dke.de

www.dke.de

THE GERMAN STANDARDIZATION ROADMAP FOR INDUSTRY 4.0 – VERSION 2 3

1 Executive Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

2.1 Future-oriented project Industry 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

2.2 Objectives of Industry 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

2.3 The system of systems – Challenges for technology and standardization . . . . . . . . . . . . . . . . . . . . . . . . . . .9

2.4 Aspects of implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

2.5 Standardization as a driving force for innovation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.6 The route to standards and specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.7 Development phase standardization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 Objectives of the Standardization Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4 The current environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.1 Cooperation between the standardization committees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.1.1 DIN/DKE Steering Group Industry 4.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.1.2 Platform Industry 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.1.3 Cooperation at international level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.2 Standardization of automation systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.3 Standardization in information technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.4 Frequency ranges for radio communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5 Subject areas and requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5.1 Standardization requirements for Industry 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5.2 Reference models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5.2.1 Reference models in general . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5.2.1.1 Description and use of reference models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5.2.1.2 Recommendation: Description of the reference models in dedicated standards . . . . . . . . . . . . . . . . . . . . . . 32

5.2.1.3 Recommendation: Standardized structure for the description of reference models . . . . . . . . . . . . . . . . . . . . 32

5.2.1.4 Recommendation: Widespread use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32


5.2.2 System architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5.2.2.1 Reference Architecture Model for Industry 4.0 (RAMI4.0). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5.2.2.2 Recommendation: Integration of existing standards and specifications

and standardization activities in the RAMI4.0 general model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

5.2.2.3 Recommendation: Compilation of a list of existing models, and integration of existing models

in the RAMI4.0 general model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

5.2.2.4 Recommendation: Integration of new models in the RAMI4.0 general model . . . . . . . . . . . . . . . . . . . . . . . . 34

5.2.2.5 Recommendation: Characteristics, semantics and ontologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

5.2.3 Reference models of instrumentation and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.2.3.1 Initial situation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.2.3.2 Areas of application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.2.3.3 Recommendation: Standardized functionality across all levels of automation . . . . . . . . . . . . . . . . . . . . . . . 37

5.2.4 Reference models of the technical and organizational processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37


5.2.4.2 Areas of application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.2.4.3 Recommendation: Development of a framework for uniform description of the

technical and organizational processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.2.4.4 Recommendation: Creation of standards on technical and organizational processes . . . . . . . . . . . . . . . . . . 38

5.2.5 Reference models of life cycle processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38


5.2.5.2 Recommendation: Description of life cycle processes in flexible, adaptive systems . . . . . . . . . . . . . . . . . . . . 39

5.3 Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.3.1 Initial situation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.3.2 Recommendation: Standardized description template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.3.3 Recommendation: Reference list of important use cases for characterization of the term “Industry 4.0”. . . . . . . 41

5.3.4 Recommendation: Use cases to illustrate the need for standardization

in the area of non-functional properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.4 Fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42


5.4.2 Recommendation: Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42


5.4.3 Recommendation: Relate terms of automation technology and IT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.4.4 Recommendation: Describe core models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.4.5 Recommendation: Specification of the modelling languages to be used in standards . . . . . . . . . . . . . . . . . . 44

5.5 Non-functional properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44


5.5.2 Recommendation: Define terminology for non-functional properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

5.5.3 Recommendation: Clearly addressing non-functional properties in standards . . . . . . . . . . . . . . . . . . . . . . . 45

5.5.4 Recommendation: Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

5.5.5 Recommendation: Security and IT-Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

5.5.6 Recommendation: Information security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5.5.7 Recommendation: Reliability and robustness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5.5.8 Recommendation: Maintainability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

5.5.9 Recommendation: Real time: Stipulation of the concepts and terminology in a standard . . . . . . . . . . . . . . . . 49

5.5.10 Recommendation: Interoperability between systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.6 Development and engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49


5.6.2 Areas of application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

5.6.3 Recommendation: Transparent and seamless database and development tools for the entire product life cycle . 50

5.6.4 Recommendation: Early support for professional IT developments through standardization in automation . . . . . 50

5.6.5 Recommendation: Need for research and development in cooperating systems . . . . . . . . . . . . . . . . . . . . . 51

5.6.6 Recommendation: Industrial location management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.7 Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.7.1 Initial situation of line-based communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.7.2 Initial situation of radio-based communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

5.7.3 Recommendation: Network management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5.7.4 Recommendation: Infrastructure components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5.7.5 Recommendation: Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5.7.6 Recommendation: EMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5.7.7 Recommendation: Work to achieve exclusive frequency ranges for industrial automation . . . . . . . . . . . . . . . . 54


5.7.8 Recommendation: Coexistence of radio applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5.7.9 Recommendation: Radio technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5.7.10 Recommendation: Integration of radio communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.8 Additive manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.9 Human beings in Industry 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58


5.9.2 Recommendation: Further develop standards and specifications

for people-friendly work design in Industry 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

5.9.3 Recommendation: Technology design – Adaptive design of work systems in Industry 4.0. . . . . . . . . . . . . . . . 61

5.9.4 Recommendation: Concepts for a functional division of work between human beings and machines . . . . . . . . 61

5.9.5 Recommendation: Design of the interaction between human beings and technical systems . . . . . . . . . . . . . . 62

5.9.6 Recommendation: Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5.10 Standardization processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64


5.10.2 Recommendation: Open Source development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5.10.3 Recommendation: Modularization of stipulations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5.10.4 Recommendation: Formalization of stipulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.10.5 Recommendation: Categorization of standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.10.6 Recommendation: Explicit standardization of the core models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.10.7 Recommendation: Formally correct and complete description of the reference models . . . . . . . . . . . . . . . . . 66

5.10.8 Recommendation: Separate description of the conceptual and technological stipulations . . . . . . . . . . . . . . . 67

5.10.9 Recommendation: Exchange of documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.10.10 Recommendation: Qualifications, teaching materials, initial and further training

on the application of the standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

6 Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

7 Relevant standards and specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

8 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

9 The authors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

1 EXECUTIVE SUMMARY

With digitization of industrial production, it is essential for extremely divergent systems from

various manufacturers to interact reliably and efficiently. The users, operating globally, expect to

be able to source their accustomed products and systems everywhere in the world. In order to

ensure this global usability and cross-system consistency, international standardization in indus-

trial automation has always been regarded as especially important and pursued as a matter of

priority. Nowadays, standards are available or at least being drafted to cover important issues

in industrial automation, but new technologies and new requirements repeatedly create a new

demand for standardization. The aim of the future-oriented initiative Industry 4.0 is to exploit the

potential resulting from

■■ the extensive use of the internet,

■■ the integration of technical processes and business processes,

■■ the digital mapping and virtualization of the real world, and

■■ the opportunity to create “smart” products and means of production.

This requires the development of a host of new concepts and technologies. It will, however, only

be possible to implement these new concepts and technologies in industrial practice if they are

backed up by standards based on consensus, as only such standards are able to create the

necessary security for investments and confidence among manufacturers and users. In order to

address the standardization issues at an early stage, the DIN/DKE Steering Group Industry 4.0

was founded. The fundamental task of the Steering Group is to develop the strategic, con-

ceptual and organizational aspects of the topic of Industry 4.0 from the point of view of stand-

ardization. The Steering Group identifies concrete needs for standardization, coordinates their

implementation and advances the development of fundamental concepts.

The Working Group “Standardization Roadmap” was established under the DIN/DKE Steering

Group to develop and update the first version of the standardization roadmap on Industry 4.0.

This standardization roadmap is the central medium of the DIN/DKE Steering Group for com-

munication with standardization committees, industry, associations, research institutions and

ministries. It is a guide showing the way for individuals and organizations active in various sec-

tors of technology, and thus supports the acceptance by the market of new technologies and

processes from the research and development stage onwards.

The aim of this standardization roadmap is to provide all actors with an overview of the relevant

standards in the area of Industry 4.0 and shed a light on the current standardization environ-

ment. Over and above this, it contains recommendations for action and sketches out the

requirements for standardization in the topics which make up Industry 4.0.

The standardization roadmap is a medium for communication between all parties involved. Any

comments or additional information will be welcomed.


2.1 Future-oriented project Industry 4.0

“Germany has one of the most competitive manufacturing industries in the world and is a global

leader in the manufacturing equipment sector. This is in no small measure due to Germany’s

specialization in research, development and production of innovative manufacturing technolo-

gies and the management of complex industrial processes.” These introductory sentences from

the implementation recommendations of the “Industry 4.0” working group formed by the Indus-

try and Science Research Union accurately reflect the importance of this field of industry to the

Federal Republic. They apply equally to many other industrial regions in Europe. The outstanding

quality of manufacturing industry is also essentially based on high-quality production technology.

The future-oriented project Industry 4.0 presented by the German Federal Government is

intended to reflect the importance of manufacturing technology and the ICT sector which sup-

ports it. The Federal Ministries of Education and Research (BMBF) and Economic Affairs and

Energy (BMWi) are coordinating their funding activities in this regard. These are supported and

monitored by the Industry 4.0 platform, the leadership of which was taken over by the BMWi and

BMBF at the start of 2015. The work of the original Industry 4.0 platform, established by the as-

sociations ZVEI, VDMA and BITKOM, has thus been translated to a higher level and placed on a

broader political and social basis.

From the point of view of manufacturing, i.e. of the users of the new technologies, it is still by

no means sure whether this will be a further revolution or rather an evolution of the existing

concepts. It is however generally recognized that the introduction of the new technologies and

corresponding new concepts is necessary if the increasing complexity and granularity with rising

demands for quality and flexibility are to be mastered in the environment of volatile markets.

2.2 Objectives of Industry 4.0

The fundamental objective is to utilize the progress achieved in information and communications

technologies and that expected in the near future for the benefit of manufacturing enterprises.

Preparation therefore has to be made for the increasing and consistent embedding of those

technologies in production systems – and that in ever smaller partial systems and components.

Additional communications capability and (partial) autonomy in reactions to external influences

and internally stored specifications are transforming mechatronic systems into Cyber-Physical

Systems (CPS). The objectives derived from that transformation are developments and adjust-

ments in ICT for manufacturing applications: robustness, resilience, information security and real

time capability.


2 INTRODUCTION

In addition, it is aimed to achieve an increasing improvement in energy and resource efficiency,

and the adjustment of industry to accommodate the social demands arising from demographic

change.

2.3 The system of systems – Challenges for technology

and standardization

Industry 4.0 describes a new, emerging structure in which manufacturing and logistics systems

in the form of Cyber-Physical Production Systems (CPPS) intensively use the globally available

information and communications network for an extensively automated exchange of information

and in which production and business processes are matched. In such a broad environment, a

large number of models, systems and concepts from an extremely wide range of domains play

an important part in shaping that structure. They are not however the heart of the Industry 4.0

concept itself. Industry 4.0 can be regarded as an additional level of integration on the basis of

the existing structures, which is itself the basis of the newly emerging structure and thus creates

the new quality. Furthermore, increasing networking of previously extensively autonomous sys-

tems, for instance in the fields of production, logistics, power supply1 and building management,

is expected in the course of Industry 4.0. What is being created is a system of systems.

A special difficulty arises here for terminology and standardization. Basically, it would be suf-

ficient only to define the additional level of integration and its emergent behaviour. But to do that,

the existing system landscape would first have to be coherently and completely defined in a

globally standardized manner. This is not always the case. Against this background, the relevant

models of the classical architecture require integration and rounding off in addition to Indus-

try 4.0 itself.

2.4 Aspects of implementation

The semi-finished products and parts involved in the manufacturing process are to possess “ar-

tificial intelligence”, or at least information on themselves and suitable means of communication,

and therefore themselves constitute cyber-physical systems. These “smart products” are to be

embedded in the process as a whole and in extreme cases control not only their own logistical

path through production, but rather the entire production workflow that concerns them.

Decentralization of the digitally stored information will consequently be followed by a decentrali-

zation of control systems. Today’s bit by bit programming will no longer be practicable with the

further increase in complexity. Current production systems are already pushing against the limits

1 For instance IEC/TC 65/WG 17, “System interface between industrial facilities and the smart grid”.


of programmability. The taking into account of sensor information, available in increasing quanti-

ties and resolutions, and the reliable coordination of several actuators in real time can no longer

be tested in all function sequences. The variety of tests can be further increased in simulations,

but it has already become necessary to abandon absolute control. Programming will in future be

replaced by a system of rules which the partial systems will follow flexibly within the limits speci-

fied for them and the current situations signalled by the other partial systems.

As a further highly important aspect, it is to be remembered that, in contrast to the early con-

cepts of automation, human beings are not to be “optimized out” of the production processes,

but rather to be given an increasingly important role: The CPPSs are to supply them with com-

pressed information suitably derived from the complex interrelationships and communicated in

a personalized manner as the basis for their intervention in the process. In this way, not only a

new form of cooperation between machines and parts of machines, but also one of cooperation

between machines and human beings arises.

Not only on the factory floor, though, but also in the added value networks, the CPSs and

CPPSs will contribute to an automation of the partial processes. This will support both short-

term flexibility and medium-term transformability in the reaction to the increasingly shorter and

more severe external influences, and thus improve the resilience of production.

According to the implementation recommendations of the “Industry 4.0” working group of the

Industry and Science Research Union2, Industry 4.0 is to be implemented in a dual strategy:

Existing basic technologies and experience are to be adapted to meet the special requirements

of manufacturing technology, and research and development work is to be conducted into

solutions for new production locations and new markets. In that context, attention is to focus on

three characteristics:

■■ Horizontal integration: Ad-hoc added-value networks optimized in real time

■■ Vertical integration: Business processes and technical processes

■■ Continuity of engineering throughout the life cycle

As a result of the large number of IT solutions now available, many sectors of industry have

experienced a serious problem of constantly rising costs, often difficult to justify in commercial

terms, for maintenance, updating, modifications and new implementations. Tools with a wide

range of data models, countless interface protocols and versions necessarily lead to a lack of

transparency and thus to greater and greater problems with the stability of the systems as a

whole. It cannot of course be the solution to prescribe a uniform global data model or harmo-

nized interfaces. A solution has to be developed which on the one hand ensures the greatest

possible room for development and on the other hand alleviates the problems described above.

One promising concept for this is service-oriented architecture, in which the above-mentioned

2 Umsetzungsstrategie Industrie 4.0 – Ergebnisbericht der Plattform Industrie 4.0, April 2015.


rule-based and situation-controlled cooperation between machines and human beings is

organized.

2.5 Standardization as a driving force for innovation

Standards create a secure basis for technical procurement, ensure interoperability in applica-

tions, protect the environment, plant and equipment and consumers by means of uniform safety

rules, provide a future-proof foundation for product development and assist in communication

between all those involved by means of standardized terms and definitions.

Standardization is of central importance for the success of the future-oriented project Indus-

try 4.0. Industry 4.0 requires an unprecedented degree of system integration across domain bor-

ders, hierarchy borders and life cycle phases. This is only possible if it proceeds from standards

and specifications based on consensus. Close cooperation between researchers, industry and

the standardization bodies is required to create the necessary conditions for sweeping innova-

tion: methodical soundness and functionality, stability and security of investments, practicability

and market relevance.

Standardization work is a joint function which is fulfilled by the groups involved (users, occupa-

tional health and safety organizations, trade unions, government, regulatory institutions, other

non-governmental organizations, conservationists, consumer associations, industry, scientists

and researchers), their experts and the members of DIN and DKE, on their own responsibility.

The application of standards is voluntary, unless their use is required by law.

The starting point is demand from the ranks of stakeholders. Those stakeholders are at liberty to

take part in the drafting process or to submit comments during the public enquiry phase. Drafts

of standards are therefore freely available.

As global trade increases, standards are predominantly drafted on the international or European

levels. Various contracts have been concluded between the standardization organizations on

the different levels for that purpose. When new topics arise, a review is conducted to ascertain

whether the subject is suitable for European or international standardization.

Standardization is a consensus-based process in which a generally accepted document is

developed, containing requirements for general and recurrent application. Distinctions can be

made between the various documents compiled at DIN and DKE on the basis of the degree of

consensus. A standard (DIN, DIN EN, DIN EN ISO, DIN ISO, DIN EN IEC) is developed by the

principle of consensus, involving all stakeholders. A specification (DIN SPEC, CWA, PAS, VDE

Application Guide), in contrast does not necessarily require full consensus and the involvement

of all stakeholders. A DIN SPEC or VDE Application Guide can therefore be easily developed in


small working groups within only a few months. Such documents promote the exchange of infor-

mation with other market players and ensure that no conflicts with existing standards occur.

The development of a normative document (a standard) takes place in working committees,

each of which is responsible for the handling of a defined standardization project. Within the

working committee a draft standard is drawn up, which is made available for two months

(or up to four months, for DIN Standards) online at the Draft Standards portal3 or as a draft

standard to purchase from the publisher Beuth Verlag4, and can be commented upon. This

ensures the involvement of a broad public in the process. At the end of the commenting period,

the objections are discussed by the working committee, the manuscript amended accordingly

where appropriate, and the standard adopted. The standard is then included in the body of

German Standards and published.

The development of standards takes place on various levels (national, European and international).

For better understanding, an overview of the standardization organizations and their interactions

is presented below (see Figure 1).

In Germany, DIN, the German Institute for Standardization, has been named in contract as

the responsible national standards body for the Federal Republic of Germany, and represents

German interests as a member of CEN (Comité Européen de Normalisation – European Stand-

ardization Committee) and ISO (International Organization for Standardization) on matters of

European and international standardization.

3 See www.din.de/de/mitwirken/norm-entwurfs-portal.

4 See www.beuth.de and www.vde-verlag.de.

ISO: International Organization for Standardization

IEC: International Electrotechnical Commission

ITU: International Telecommunication Union

CEN: European Committee for Standardization

CENELEC: European Committee for Electrotechnical Standardization

ETSI: European Telecommunications Standards Institute

DIN: German Institute for Standardization

DKE: German Commission for Electrical, Electronic & Informa-tion Technologies of DIN and VDE

DIN and DKE represent German interests in European and international standardization.

© 2013 DIN German Institute for Standardization

Mechanical engineering

Building/civil engineering

Services

Information technology

Aerospace

Medical technology

Precision engineering

63 futher fi elds of activity

Electrotechnology

Telecommunications

…

INTERNATIONAL

NATIONAL

EUROPEAN

National representation of interests

Figure 1:

National, European and

international standardization

levels


DKE represents the interests of the electrical engineering, electronics and information technol-

ogy industries in the field of international and regional electrotechnical standardization work, and

is funded by VDE. It therefore represents German interests within both CENELEC and IEC.

Nowadays, almost 90 % of standardization work is oriented towards the European and interna-

tional levels, with DIN and DKE organizing the entire process of standardization on the national

level and ensuring German involvement in the European and international processes through the

corresponding national committees.

Apart from the internationally recognized standardization institutes, there are other organizations

throughout the world which deal with standards or recommendations, some of whose products

are designated as quasi-standards. These may serve as the preliminary stage or basis of a

DIN SPEC, and in that way make a contribution to standardization.

2.6 The route to standards and specifications

Consensus-based standards can be established in different ways. The starting point is the

identification of a particular need for standardization. This results from feedback from practical

applications, from the creation of new technologies, from the results of research or from new

regulations.

Considering the path leading to an international standard (ISO, IEC), distinctions can be made

between three typical routes:

1. Direct stipulation within the responsible standardization committees. In this case, the

stipulations to be standardized are compiled and developed within the responsible interna-

tional committee and its national mirror committees. One example is the development of

IEC 61131-3, “Programmable controllers” in IEC/SC 65B/WG 7 and in Germany in the

Working Group DKE/AK 962.0.3, “SPC languages”.

2. Direct adoption of consortial specifications. In this case, the specification is drawn up

within a consortium and then adopted essentially unchanged as a DIN SPEC or standard.

Examples include the adoption of the batch control specification ISA S 88 (ISA) in

IEC 61512, the OPC UA specification in IEC 62541, the Prolist specification in IEC 61987,

and RAMI4.0 in DIN SPEC 91345.

3. Consensus-based development in national organizations with subsequent further

development in the responsible standardization committees. In this case, the fundamental

requirements are prepared within professional associations or DIN committees and pub-

lished as guidelines or national specifications (DIN SPEC, VDE Application Guide) and then,

in a second step, developed into international standards by the responsible standardization

committees.


It has become apparent in recent years that the development and elaboration of proposals for

and contents of standards are increasingly taking place within the professional associations and

DIN SPEC committees. The results of this preliminary work then flow into the work of the re-

sponsible standardization committees for further development. These committees ensure that all

stakeholders are informed of the contents and the planned procedures, and that the standardi-

zation process takes place on the basis of consensus. In addition, the standardization commit-

tees play an important role in analyzing the existing standardization landscape and initiating and

coordinating standardization projects in strategically important areas.

Within Germany, there are a number of relevant professional associations which publish cor-

responding stipulations and consortial specifications. In many cases, the associations are so

broadly based and organized internally to reach and reflect a consensus that their publications

can be regarded as the common opinion of the relevant professional community and thus

constitute a particularly stable and reliable basis both for the further standardization process and

for immediate industrial use. A procedure may be termed consensus-based in this context when

the following conditions are fulfilled:

■■ The specifications are drawn up in committees which any professional can join.

Membership in an organization is not required. If the number of members has to be limited,

selection is made by a transparent and non-discriminatory procedure.

■■ The results of the committee’s work are published at an early stage as a draft for comment-

ing. They can be obtained and commented on by anyone, irrespective of membership in an

organization.

■■ Prior to publication as a specification, there is public enquiry procedure in which anyone

can raise an objection. The committee decides in open discussion on acceptance of the

objection.

■■ When adopted, the specification is published and is available to all those interested,

irrespective of membership in any organization.

With consensus-based specifications, a sound standardization foundation can be created in the

short term for the development processes within companies. These specifications then provide

a good point of departure for consensus-based standards.

Further information on standardization can be found at the DIN website.5

5 http://www.din.de/en/about-standards.


2.7 Development phase standardization

The consecutive nature of scientific findings and industrial applications is now becoming more of

a parallel process, as technology and service suppliers have to react to requirements from prac-

tice even while development is in progress. In order to take account of this economic develop-

ment, development phase standardization has been adopted at DIN and DKE.6

Standards and specifications represent an effective instrument for putting the results of research

into practice in a rapid and user-friendly manner, and by doing so promoting rapid access to

the market for innovations. They thus secure a broad acceptance for the implementation of new

concepts and technologies in industrial practice, create confidence and trust among manufac-

turers and users, and provide the necessary security for investment.

Development phase standardization therefore makes a fundamental contribution to the utiliza-

tion of research results. It plays a decisive part in making the traditional standardization process

more dynamic, and comprises all activities which are aimed at detecting the standardization

potential of strategic, fundamentally innovative products and services, systems and basic tech-

nologies, at as early a stage as possible.

6 http://www.din.de/en/innovation-and-research/research-projects and http://www.vde.com/en/dke/Pages/DKE.aspx.


Figure 2:

Innovation from

standardization

In this way, innovative topics and research results can be publicized and made useful on a

broad basis. The transfer of knowledge and technology, especially in fields with a high degree

of innovation, is promoted and accelerated in this way.

In research projects, especially when these are subsidized with public funds, the focus is in-

creasingly on the effective commercial usability of the results. Research projects therefore have

to be holistic in their approach. In order to provide optimum support to transfer into the market

and the propagation of innovative results from research and development, standardization activi-

ties should already be taken into account in the commissioning phase of research projects.

Funding bodies are therefore recommended to include standardization aspects in their tendering

texts, and so provide an incentive to initiate standardization work during the course of research

projects.

DIN and DKE can be involved as project partners in national, European and international re-

search projects. With the involvement of DIN and DKE in consortiums, it is ensured that attention

is paid to standardization issues and thus the utilization of the research results at an early stage.

National research funding

Within the context of national research funding, DIN7 and DKE8 are already engaged in numer-

ous projects and tendering processes which are funded by government, for example the Federal

Ministry of Education and Research (BMBF) and the Federal Ministry for Economic Affairs and

Energy (BMWi). The following examples are worthy of note in the context of Industry 4.0:

ProSense:

The objective of the “ProSense” project, sponsored by the BMBF, is the development of produc-

tion control to meet the requirements of manufacturers and the market, on the basis of cyber-

netic support systems and smart sensors. In order to enable reactions to dynamic market pro-

cesses and at the same time ensure robust production processes, there is a need for a modular

IT structure which can process and condition high-resolution data from the production process

with real time capability, so as to assist in decision-making by individual employees. These high

resolution data from the production process coupled with intelligent graphical representation

provide optimum support to humans for planning and control of production. The results of the

research are contributed to standardization in the form of DIN SPEC 91329, “Extension of the

EPCIS event model by aggregated production events for use in corporate application systems”.

7 http://www.din.de/en/innovation-and-research/research-projects/industry-4-0.

8 http://www.vde.com/de/Technik/Industrie40/Seiten/default.aspx.


APPsist:

The objective of the “APPsist” project, supported by the BMWi, is the development, validation

and example implementation of a holistic software package integrated in cyber-physical produc-

tion systems, taking account of the socio-technical design perspectives. The APPsist solution is

intended to facilitate smart, cooperative and self-organized interaction between staff and techni-

cal operation systems along the value chain and make that interaction transparent. The results of

the research are channelled into standardization.

POLAR:

The objective of the “POLAR” project, sponsored by the BMBF, is the development of standard-

ized communication between production facilities and energy and load management systems in

manufacturing industry. Industrial load management is to be made possible by combining data

exchange systems with corresponding energy management software. In order to assist in the

dissemination and transfer of the project results, the findings from the project are channelled into

DIN SPEC 91327, “Reference architecture for a recommendation-based demand side manage-

ment system for industry“.

Interoperability for I4.0 systems based on automation standards:

The main objective of this INS project is to set the solutions arrived at in the context of the

Industry 4.0 initiative on the foundation of the existing standards and specifications in the field of

automation, and to develop them in such a way that security of investment can be established

for the stakeholders in evolutionary steps. The fundamental focal areas are as follows:

■■ Creation of integration capability between industrial communications systems and the

IP-based internet of things and services Ú interoperability on the level of communication

protocols and services with the focus on “Definition of Quality of Service (QoS)”

■■ Continuous flow of information between the devices and components, manufacturing sys-

tems and actors Ú interoperability by means of semantic models and methods with the

focus on definition of the semantics on the basis of characteristics systems

■■ With the gradual implementation of the Industry 4.0 strategy, the life cycle of the means of

production will develop in the direction of more flexibility and variability Ú interoperability

between devices and components throughout the life cycle from planning to operation and

maintenance, with the focus on definition of the semantics on the basis of characteristics

systems.

AUTONOMIK for Industry 4.0:

The intention behind the technology programme AUTONOMIK for Industry 4.0 is to exploit the

potential for innovation in meshing the latest I&C technologies with industrial manufacturing

and accelerating the development of innovative products and services. For that purpose,

standardization has been introduced as a cross-cutting topic within the research accompanying

the AUTONOMIK for Industry 4.0 programme. In the course of the services accompanying the

programme, the topic of standardization is to be explored more deeply, so as to ensure rapid

implementation in industrial practice.


In order to keep the legal risks of digital manufacturing as low as possible, a description of the

legal background for Industry 4.0 has been compiled as part of the accompanying research for

the technology programme. This model is intended to enable non-lawyers to classify concrete

areas of legal risk, damages and hazards throughout the networked value adding process9.

BZKI for Industry 4.0:

In the future industrial world which is being discussed under the concept “Industry 4.0”, wireless

communication between distributed systems is indispensable. If closed loop control of complex

processes is to be made possible, an extremely low latency with low jitter has to be achieved.

At the same time, a high level of reliability in communication with a simultaneously high device

density is to be ensured. In order to ensure high data transfer rates with extremely low latency,

it will only be possible to implement future applications such as the haptic human-machine

interface or “augmented reality” with a new wireless technology. The research project ZDKI

(Reliable Wireless Communication in Industry), also entitled INDUSTRIALRADIO.DE, addresses

the present limits and will ensure real time use by means of innovative radio technologies. Eight

independent research consortiums comprising industry and academic institutions are dealing

with this problem and examining various use cases from industrial practice. The eight projects

are coordinated by the BZKI background research team, so as to bundle the findings made in

the projects for standardization purposes.

European research funding

In the world of research and development, standardization is not only increasing in importance

on the national level. The European Commission has also recognized this, and is therefore

increasingly integrating requirements for standardization in its tendering documents. In conse-

quence, DIN is also just as much at home in the diverse group of topics which make up Horizon

2020, the European Union’s framework programme for the promotion of research and innovation

as it was in the previous European research framework programmes. The following examples

are worthy of note:

EASE-R3:

The European research project EASE-R3 (Integrated framework for a cost-effective and easy

repair, renovation and re-use of machine tools within a modern factory) is developing a new,

integrated reference system for cost-effective and easy maintenance of manufacturing machin-

ery. The reference system developed takes account of the entire life cycle of the machine tool

(from design to use in operation), and maps both conversion and re-use of machine tools in the

modern factory. The innovative reference system supports users in matters such as how to draw

up the best and most cost-effective customized maintenance strategy for a series of machine

components or machines in the factory. The results of the research are currently being contrib-

uted to the standardization process at international level.

9 www.ju-rami.com.


The aim behind this document was to draw up a strategic, technically oriented roadmap which,

taking special account of the recommendations from the Industry and Science Research Union

and the corresponding assistance from the BMWi and BMBF, presents the requirements for

standards and specifications for Industry 4.0, identifies areas where action is necessary and

gives corresponding recommendations. In addition, it provides an overview of the existing stand-

ards and specifications in this context, in cooperation with Platform Industry 4.0.

In the German Standardization Strategy10, standardization is understood as being the fully

consensual establishment, by a recognized organization, of rules, guidelines and criteria for

activities for general or recurrent application. The de jure standards produced in this way are

accompanied by specifications in various forms, such as DIN SPEC (DIN Specifications),

VDE Application Guides, PAS (Publicly Available Specifications), TS (Technical Specifications),

CWA (CEN Workshop Agreements), IWA (International Workshop Agreements), ITA (Industry

Technical Agreements) or TR (Technical Reports).

This standardization roadmap is intended as a stock-taking and a means of communication

between the parties involved from various technological sectors such as automation, information

and communications technology and manufacturing technology. The following chapters build

upon each other and present a description of the current status in standardization for Indus-

try 4.0, an analysis of the currently identifiable need for standardization and detailed recommen-

dations for action in the development of further standards in the individual fields.

It has been a conscious decision not to set any priorities in the standardization roadmap. The

implementing committees are requested to incorporate the recommendations in their pro-

grammes of work.

This standardization roadmap will be regularly revised and amended on the basis of

new findings – for example from research projects and the work in the standardization

committees. Even after its publication, therefore, there is still an opportunity to take part

in this process by submitting comments and working on standards.11

10 The German Standardization Strategy: http://www.din.de/en/din-and-our-partners/din-e-v/german-stand-ardization-strategy.

11 You can find the contact for the standardization roadmap and for all questions concerning standardization at www.din.de/go/industrie4-0 and www.dke.de/de/std/Industrie40/Seiten/default.aspx.


3 OBJECTIVES OF THE STANDARDIZATION ROADMAP

http://www.din.de/en/din-and-our-partners/din-e-v/german-standardization-strategy

http://www.din.de/en/din-and-our-partners/din-e-v/german-standardization-strategy

4.1 Cooperation between the standardization committees

The future-oriented project Industry 4.0 was launched in Germany as early as 2013. The impor-

tance of standardization in the context of Industry 4.0 rapidly became clear. As a result, the first

issue of the standardization roadmap for Industry 4.0 was already published in November 2013.

Together with the early identification of future needs for standardization, a further central task is

the organization of cooperation between the various stakeholders.

4.1.1 DIN/DKE Steering Group Industry 4.0

With the foundation of the DIN/DKE Steering Group, an important foundation stone was laid,

supporting industry and the academic community and making an efficient and holistic ap-

proach to the topic of Industry 4.0 possible. The fundamental function of the Steering Group is to

advance the strategic, conceptual and organizational treatment of the topic of Industry 4.0 from

the point of view of standardization. The Steering Group identifies concrete needs for stand-

ardization, coordinates their fulfilment and provides impetus to the examination of fundamental

concepts. It currently encompasses three subordinate working groups, dedicated to specific

cross-committee aspects of Industry 4.0 (see figure). DIN and DKE communicate the results of

the Steering Group’s work to Platform Industry 4.0.


DIN/DKE Steering Group Industry 4.0

German Standardization Roadmap

Radio I4.0

4 THE CURRENT ENVIRONMENT

Figure 3:

The DIN/DKE Steering Group

and its Working Groups

Use Cases

4.1.2 Platform Industry 4.0

The Federal Ministries for Economic Affairs and Energy (BMWi) and Education and Research

(BMBF) announced the foundation of Platform Industry 4.0 at the Hanover Fair in 2015 and took

on the management of that platform. The work of the Industry 4.0 platform previously run by the

associations VDMA, ZVEI and BITKOM was transferred to Platform Industry 4.0 and the topic

thus placed on a broader political and social foundation.

Platform Industry 4.0 focuses its work in five working groups: Reference Architecture and

Standardization, Research and Innovation, Security of Networked Systems, Legal Framework,

and Work and Training. DIN and DKE are represented in the working group on Reference

Architecture and Standardization, making an active contribution to discussions on standardiza-

tion topics there. Initial results from the work of the association platform on Industry 4.0 have

already flowed into standardization activities at DIN. Examples worthy of mention here include

the reference architecture model for Industry 4.0 (RAMI4.0), which is expected to be published

as DIN SPEC 91345 in German and English, and in that form serve as input for international

standardization.

4.1.3 Cooperation at international level

The central importance of standardization in the digitization of industrial manufacturing is now

becoming apparent outside Germany in a large number of activities. There are for example

standardization initiatives at ISO, IEC, ISO/IEC JTC 1 (ISO/IEC Joint Technical Committee

for Information Technology), W3C (World Wide Web Consortium), ITU-T and IEEE (Institute of

Electrical and Electronics Engineers), and also initiatives such as the Industrial Internet Consor-

tium (IIC).

For German industry with its global operations and export orientation, the stipulation of technical

requirements in globally valid standardization systems is of special importance. Various profes-

sional groups have repeatedly emphasized the importance of international, consensus-based

standardization. The aim must be to anchor all stipulations essential for a uniform technical

function and usability in international standards step by step. Only a consistently coordinated

European and international standardization system can bring about a breakthrough for the new

concepts and technologies of Industry 4.0. German industry and businesses have access to and

influence on European and international standardization through DIN and DKE.

There is great interest on the international scene, especially in countries such as China, the USA,

Korea and Japan. On that basis, a new working group for Industry 4.0 (Intelligent Manufacturing)

was founded at the meeting of the Chinese-German Standardization Cooperation Commission

in May 2015.



ISO Strategic Advisory Group on Industry 4.0

In order to support the vision of Industry 4.0 as well as possible at ISO and to deal with the topic

of standardization in a concerted and all-encompassing manner, DIN has initiated a strategic

advisory group at ISO on Industry 4.0 (ISO/SAG Industry 4.0/Smart Manufacturing) under Ger-

man chairmanship.12

The aim is to organize the contribution to be made by ISO and in that way support a common

procedure, especially together with IEC and ITU-T. The focus of the strategic advisory group is

on the following tasks:

■■ Strategic and conceptual development of Industry 4.0 at ISO

■■ Identification of lacking standards and specifications

■■ Establishment of implementation strategies and recommendations for Industry 4.0

■■ Coordination of the standardization activities on the international level

■■ Establishment of early coordination across the various committees and organizations

■■ Cooperation with further organizations on the national, European and international levels,

with great importance attached to cooperation with IEC and ITU-T.

The report to the Technical Management Board is planned for September 2016.

SMB Strategic Group 8, Industry 4.0 – Smart Manufacturing

In order to support the vision of Industry 4.0 as well as possible at IEC and to deal with the topic

of standardization in a concerted and all-encompassing manner, IEC’s Standardization Manage-

ment Board (SMB) initiated a strategic group, SG8 Industry 4.0 – Smart Manufacturing, in May

2014 (see SMB/5332/R).

The objective of IEC SG 8 is to recommend to the IEC SMB by June 2016 the means by which

the topic of Industry 4.0 can best be supported by standardization. The basis of the work within

IEC SG8 is the results from Platform Industry 4.0 and the contents of the Standardization Road-

map on Industry 4.0. DIN SPEC 91345 “Reference Architecture Model for Industry 4.0 (RAMI4.0)”

and the I4.0 components are also particularly important in setting the course for recommenda-

tions to the IEC SMB.

To date, IEC SG 8 has achieved the following:

■■ Formation of SG 8 with broad participation by national committees, some of which sent

experts from major companies in industrial automation.

■■ Liaison with

■z ISO/IEC JTC 1 WG 10

■z IEEE P2413

■z ISO SAG Industry 4.0/Smart manufacturing

■z ISO TC 184

12 Further information can be found at http://www.din.de/en/innovation-and-research/industry-4-0/working-groups.

http://www.din.de/en/innovation-and-research/industry-4-0/working-groups

http://www.din.de/en/innovation-and-research/industry-4-0/working-groups


■■ Initial report to the IEC SMB (see SMB/5584/R) with the following decisions:

■z Recommendation to define a standardization map for Industry 4.0/Smart manufacturing

electronically. The standardization map will constitute an equivalent electronic tool to the

Smart Grid Mapping Tool (http://smartgridstandardsmap.com).

■z Enquiry by IEC to ITU/R concerning the radio frequency range for Industry 4.0/Smart

manufacturing.

■z Long-term financing of servicing of the characteristics classification database “common

data dictionary (CDD)” and the corresponding software (PARCEL MAKER™ for

IEC 62656).

■z Recommendation to the TCs to increasingly populate and use the CDD in accordance

with IEC 61360. In this way, characteristic classifications can be described in a stand-

ardized manner in the administration shells of the I4.0 components.

In general, the first report to the IEC SMB pursues the aim of making Industry 4.0 manage-

able from the point of view of standardization. The recommendation on the Industry 4.0/Smart

Manufacturing standardization map constitutes the central tool. The liaisons mentioned above

with the standardization organizations ISO and IEEE are important achievements allowing this to

be projected beyond the bounds of IEC. Only in this way will it be possible to establish a broad

basis for acceptance of Industry 4.0.

4.2 Standardization of automation systems

The important associations and standardization bodies involved in the development of standards

in the national German environment include the following:

■■ DIN (DIN Standard, DIN SPEC, DIN Technical Report, DIN Preliminary Standard)

■■ DKE (DIN Technical Report and DIN Preliminary Standard)

■■ VDI-GMA (VDI/VDE Guideline)

■■ VDMA (VDMA Standard Sheet)

■■ NAMUR (NAMUR Recommendation)

For questions of procedure and organizational arrangements, guidelines such as

■■ BITKOM guidelines (BITKOM)13

■■ ZVEI guidelines (ZVEI)14

are also of assistance.

13 https://www.bitkom.org/Themen/Branchen/Industrie-40/index.jsp.

14 http://www.zvei.org/Verband/Publikationen/Seiten/ZVEI-Leitfaden-Industrie-Services.aspx.


The professional groups behind these bodies are staffed with experienced teams of experts who

ensure rapid development of high-quality specifications and standards. Typically, the amount of

free time available to the experienced experts who work voluntarily on the committees is limited.

The projects should therefore be prioritized and organized up to the time at which they go for-

ward for international standardization.

The topics of automation technology are extensively covered by the fields of activity of the inter-

national standardization committees. The following committees are involved with the especially

interesting system topics of Industry 4.0:

■■ IEC/TC 65 “Industrial process, measurement, control and automation”, with its subcommit-

tees

■z SC 65A “System Aspects”

■z SC 65B “Measurement and control devices”

■z SC 65C “Industrial networks”

■z SC 65E “Devices and integration in enterprise systems”

■■ ISO/TC 184 “Automation Systems and Integration”, with its subcommittees

■z SC 1 “Physical device control”

■z SC 2 “Robots and robot devices”

■z SC 4 “Industrial data”

■z SC 5 “Interoperability, integration, and architectures for enterprise systems and

automation applications”

IEC/TC 65 is mirrored nationally in Germany by the DKE in the Process measurement and

control technologies division (FB 9), and ISO/TC 184 by DIN Standards Committee Mechanical

Engineering (NAM). In addition, there are a number of other committees in ISO and IEC which

deal with related and adjacent matters. Practically all the important topics of system-oriented

automation technology from the field level through the process control and production control

levels to the MES level and the interface with the ERP level are however covered by the fields of

activity of IEC/TC 65 and ISO/TC 184. The extensive series of standards created in recent years

have already achieved a high degree of maturity and are being further extended step by step.

All in all, the structure required to organize the additions resulting from the Industry 4.0 initiative

is in place. One essential challenge will be to ensure interoperability above and beyond domain

boundaries, i.e. between the systems and concepts of process technology, manufacturing

technology, logistics, mechanical engineering and information technology. This will require close

cooperation between the standardization committees.


4.3 Standardization in information technology

In information technology, consensus-based standards and specifications are developed and

continuously updated by the subcommittees of the DIN Standards Committee on Information

Technology and Applications (NIA) and its international counterpart, the ISO/IEC Joint Technical

Committee (ISO/IEC JTC 1). A variety of standardization topics in information technology have

been dealt with there for many years, constituting a good basis for the work on Industry 4.0.

In this context, the quality assurance of software for manufacturing systems, for example, is an

especially relevant topic which is a fundamental requirement for reliable, fail-safe Industry 4.0

systems and is ensured by ISO/IEC 29119 among other standards. Communication between

machines is also without a doubt in the focus of Industry 4.0. This requires appropriate networks

which facilitate rapid and secure communication. The ISO/IEC 8802 series of standards deals

with this subject and lays the foundation stone for further action. As regards identification and

data exchange in the context of Industry 4.0, furthermore, contactless chip card technology

(ISO/IEC 14443) and NFC (Near Field Communication, ISO/IEC 13157) are also used.

The topic of the Internet of Things is also one of the focal areas which are closely connected to

Industry 4.0. Work is already in progress on projects on both the national and international levels.

In the field of automatic identification and data collection (AIDC) in particular, there are close con-

nections with the Internet of Things. ISO/IEC 15459 and ISO/IEC 29161 are worthy of mention

in that connection. On the national level, preparations are being made for an IoT light project, in

which an automatic mechanism establishes a connection between an object and the internet.

In addition, in the form of DIN 66277, there is a standard which makes it possible to control

processes automatically.

A further, relatively new, area for standardization is that of Big Data. In JTC 1/WG 9, fundamental

principles are being established on the evaluation of data collected in an unstructured form for

optimization of production and logistics processes (ISO/IEC 20547).

The cloud as a new storage technology is also playing an increasingly important role for In-

dustry 4.0. The standards established in JTC 1/SC 38 (ISO/IEC 19944) enable the use of cloud

technologies for organization of information management, storage and communication between

machines and human beings.

IT security represents what is surely the most critical success factor in Industry 4.0. Information

technology networking must not lead to a situation in which sensitive production data fall into the

wrong hands (industrial espionage) or in which data are manipulated and production processes

sabotaged. The application of existing standards and solutions for IT security alone will not be

sufficient, as the field of manufacturing technology presents special challenges for the imple-

mentation of IT security measures. Those worthy of mention here are the requirement for real

time capability, direct communication between machines without the opportunity for operators


to intervene, security during transmission of sensitive manufacturing data and, last but not least,

aspects of data protection. With the declared aim of Industry 4.0 to make a batch size of

1 equivalent in cost to mass production, production data will in future also be linked to customer

data, and therefore the requirements of national data protection laws and in future the EU data

protection regulations will have to be complied with in production areas. Securing information

systems will thus not only be in the interests of the enterprise itself, but will also be required by

legislation. This complex environment requires a system-oriented procedure which must be

supported by standards so that the implementation of Industry 4.0 concepts can be successfully

mastered by means of standardized interfaces and best practice procedures.

The development of consensus-based standards and specifications in the IT security environ-

ment is essentially taking place in the following committees:

Organization Committee designation Committee title Field of work

DIN NA 043-01-27 AA IT Security Techniques Mirror committee to ISO/IEC JTC 1/SC 27

DKE DKE/GK 914 Functional safety of electrical,

electronic and programmable electronic

systems (E, E, PES) for the protection

of persons and the environment

Mirror committee to

IEC TC 65/SC 65A/WG 14

DKE UK 931.1 IT security in automation systems Mirror committee to IEC TC 65/WG 10

CEN TC 251 Health Informatics Medical information technology

ISO/IEC JTC 1/SC 27 IT Security Techniques Generic IT security/information security

management systems

IEC TC 65/WG 10 Industrial process measurement,

control and automation

IT security in automation systems

ETSI TC Cyber Technical Committee (TC)

Cyber Security ETSI

Cyber Security

ISA ISA 99 Industrial Automation and

Control Systems Security

IT security of production control systems in

cooperation with IEC TC 65


In addition, consortium standards from the IT environment are, for example, published by the

following organizations:

■■ W3C

■■ IEEE

■■ OASIS

■■ OMG

■■ IETF

The German Standardization Roadmap on IT Security deals with the standardization of security

aspects. It provides an overview of the focal areas of IT security standardization which are cur-

rently at the forefront of discussions, and presents prospects and recommendations for action

on the basis of the present discussions.

The standardization roadmap is compiled and regularly updated by the IT Security Coordina-

tion Office at DIN in cooperation with DKE. The current version (in German) can be downloaded

from www.din.de/go/kits or www.dke.de/de/std/Seiten/NormungsRoadmaps.aspx. An English

version is also available.

4.4 Frequency ranges for radio communication

The International Telecommunication Union – Radiocommunication Sector (ITU-R) compiles

Radio Regulations. These are revised at approximately 4-year intervals for presentation at the

World Radio Conference (WRC). The next dates are November 2015 and the year 2019. The

Radio Regulations (RR) only distinguish between primary and secondary services, and these are

assigned to the various frequency bands.

In the view of the ITU, industrial automation applications are industrial, scientific and medical

(ISM) applications. These applications are defined and treated without reference to services. The

ISM applications themselves are not named in the frequency tables of the Radio Regulations,

but can rather be found in two footnotes presented at appropriate locations in the RR. The appli-

cations of industrial automation are therefore not assigned to any “radiocommunication service”

as defined by the ITU, and consequently cannot claim any protection from interference caused

by a primary or secondary service.

The requirements for a radio link in an industrial environment do however indicate that a certain

level of protection from interference which can be caused by other radio systems is desirable.

This can be effected in various ways: on the one hand by planning for the use of radio in the

industrial facility by the operator of that facility, and on the other hand by the use of a radiocom-

munication service assigned under the auspices of the ITU. Obtaining the assignment of an

exclusive range as a primary service is a time-consuming process, in which a variety of groups


are involved worldwide. Together with the aim of an exclusively usable frequency range, the

possibility of joint use should also be considered. This may be possible with either a primary or a

secondary service.

Electromagnetic waves are suitable for the wireless transmission of signals within a limited fre-

quency range. International harmonization agreements have been concluded in order to ensure

efficient use of this finite resource. On the national level, allocations are made to various radio

services by the German frequency regulations. Frequencies may be allocated to the public, by

way of a general assignment. On the one hand, this creates the greatest possible flexibility for

the use of the frequencies. On the other hand, however, the possibility of interference on joint

use of a frequency by other users has to be taken into account.

In many frequency ranges, the frequencies are allocated to a single user or wireless network

operator (an individual assignment) in order to protect the applications. The Federal Network

Agency has set down its procedures in administrative regulations in order to ensure that the

authorities act in a uniform manner. In addition, the German Telecommunications Act (TKG)

contains legal stipulations which regulate the frequency assignments.

The international harmonization agreements mentioned above are concluded on two levels.

Firstly, there is the level of the European Conference of Postal and Telecommunications Ad-

ministrations (CEPT). These agreements are arrived at by consensus. CEPT groups together

48 administrations in the field of post and telecommunications regulation, including those of all

member states of the European Union. Within CEPT, industry and interested associations can

take part on the working group level. CEPT compiles joint European proposals for submission to

ITU-R. These proposals comprise changes to the allocations of frequency ranges to the various

services (e.g. mobile radiocommunication service or fixed radiocommunication service). CEPT

stipulates on an international level which applications are assigned to a radiocommunication

service on which frequency.

Secondly, international harmonization agreements are reached on the level of the ITU. For

that purpose, the world is divided into three regions, in which Europe together with the former

Soviet Union, parts of the Russian Federation and the African continent comprise Region 1,

North and South America Region 2, and Asia, the Pacific area, Australia and parts of the

Russian Federation Region 3. The various services are assigned to the different frequency

ranges for each region. Within ITU, the aim is to reach consensus between the countries

concerned.

Independently of joint European contributions to ITU-R, each country may also submit its own

proposals. Possible channels are as follows:

■■ ZVEI Ú BMVI/BNetzA (AK1/AK2) Ú CEPT Ú ITU

■■ IEC Ú national authorities Ú CEPT Ú ITU

■■ IEC Ú national authorities Ú ITU


There is no doubt that the implementation of a recommendation requires great commitment

by businesses and politicians, with a correspondingly high level of motivation and economic

justification. It is also clear that such a process is time-consuming, but has to be initiated with all

necessary emphasis when it appears necessary.

The ZVEI Working Group “Wireless in Automation” in cooperation with the accompanying re-

search team at BZKI has established a “German industry initiative for WRC-15 preparation”.


5.1 Standardization requirements for Industry 4.0

With Industry 4.0, the focus has shifted to new subject areas and in particular to a system-

oriented procedure. Cross-level and cross-domain strategies have to be developed and stand-

ardized. It is not sufficient in this context merely to include a higher level; on the contrary, an

all-encompassing approach is required. If development work is to be efficiently supported by

specifications and standards, efforts which go beyond the normal work of the committees will

be required.

One of the central requirements of Industry 4.0 is the broad support of technical and organiza-

tional processes in process engineering, manufacturing and logistical environments, accom-

panying the entire life cycle of systems, products and series in units distributed both spatially

and organizationally. This is only possible with consensus-based standardization, involving the

professional groups and stakeholders concerned.

Integration includes on the one hand use of the existing standardization landscape as a stable,

tried and tested basis for further development, and on the other hand active contribution of the

concepts newly established or further developed in the context of the Industry 4.0 strategy to

the international standardization process, preferably in existing standardization committees with

which an intensive exchange of information is already practised.

In the field of industrial automation, for example, there are a large number of existing standards

which have proven their worth in practice. The new requirements of the Industry 4.0 landscape

are, however, expected to make extensions and upgrading necessary. In many cases, substan-

tive reorganization may also be required to make the standards landscape more compact, more

robust and freer from overlaps. In any case, the existing international standards will form the

central reference point for development.

If they are to be familiar with the development of the relevant core standards in IEC and ISO

and influence further international standardization organizations in that connection, the existing

technical committees and national mirror committees in DKE and DIN must be staffed by the

leading experts and be endowed with sufficient resources. Only then will it also be possible

for the German experts, manufacturers and users to contribute their knowledge and raise their

concerns in the international standardization work of ISO and IEC. An appeal is therefore made

to German industry and other groups interested in standardization to facilitate participation by

their experts in national and international committees, to support them and to document their

requirements for standards. The standardization committees should also be used to provide

support for the implementation of the standards and specifications in practice across industry

and internationally.

5 SUBJECT AREAS AND REQUIREMENTS


5.2 Reference models

5.2.1 Reference models in general

5.2.1.1 Description and use of reference models

A reference model is a model which coherently describes an aspect which plays an important

role in the systems of an area of application. Reference models take into account organizational

and technological circumstances, and observe the system to be modelled from a particular point

of view. They are therefore not without alternatives, but do, in the opinion of the professional

experts, accurately describe the situation. Different groups of experts may of course arrive at

different reference models. This is undesirable, but in many cases unavoidable. Reference

models are metamodels. They are the basis of common understanding in the expert groups,

they describe the structure of the models in a use case, and are the point of departure for the

tools developed from them. The availability of standardized reference models in all areas is a

decisive precondition for Industry 4.0. The cross-domain view gives additional importance to an

explicit, unambiguous and clear presentation of the situations in reference models. The existing

domain-specific models are to be added to, extended and harmonized to achieve this aim.

A further challenge consists in the fact that the reference models are often not explicit and

delimited, but are rather described in a variety of technical standards. This leads to a repeated,

unclear, inconsistent and unreferenceable description, and to difficulties in the integration of

components in an overall system.

The primary objective of a reference model is the clear and unequivocal description of a model

of a relevant situation. A reference model which satisfies these criteria is a standardizable refer-

ence model. A second objective is to have only one reference model for a particular situation

wherever possible, and to manage that model globally as the only standard. This, however, can-

not always be done. Reference models are never the only true models. Depending on the point

of view, the user’s own history, or for reasons of technical or corporate policy, several competing

reference models may be created for the same situation and then also lead to different solutions.

In this undesirable case, it can be better to permit several standards or specifications to exist in

parallel in the consensus-based framework rather than to promote the creation of consortium

specifications. Then, of course, the aim should be to establish a reference model which spans

various domains.


5.2.1.2 Recommendation: Description of the reference models

in dedicated standards

As with core models, reference models are also used in a wide variety of model solutions.

Reference models should be defined separately as independent standards for the purposes of

simplification and avoidance of unintentional deviations, and for better understanding.

5.2.1.3 Recommendation: Standardized structure

for the description of reference models

The structure of the description of reference models is to be as uniform as possible.

5.2.1.4 Recommendation: Widespread use

Widespread use of reference models should be promoted. Technical systems and processes in

Industry 4.0 should be described on the basis of those reference models.

5.2.2 System architecture

5.2.2.1 Reference Architecture Model

for Industry 4.0 (RAMI4.0)

As explained above, the relevant models of the classical architecture are to be integrated and

rounded out for Industry 4.0. The Smart Grid Architecture Model (SGAM), developed for compa-

rable purposes in connection with the smart grid has been adapted and expanded to meet the

requirements of Industry 4.0 as the Reference Architecture Model for Industry 4.0 (RAMI4.0). To

accompany the “Asset Layer”, which represents the real, physical world, an “Integration Layer”

has been added (y axis), containing a virtual map of the physical installation of a system. The x

axis, which in the SGAM focused primarily on the value chain for power distribution, has been

made more general. The distinction between the “type” and “instance” of an object along the

value chain is particularly important. As long as an idea, a concept, a thing, etc., remains a plan

and is not yet available as a real, usable object, it is termed a “type”. When the plan is imple-

mented as a real product, the type becomes one or many instances, which may also include

objects which are not directly tangible, e.g. software, archives, etc.


Finally, the z axis is labelled in accordance with the terminology from the IEC 62264 and

IEC 61512 standards, with additions representing the networking between enterprises

(“Connected World”) and, at the other end of the scale, the “Product”, taking account of the

demand for active involvement of the product in, for example, a self-configuring production

line. RAMI4.015, presented during the 2015 Hanover Fair, is currently being enshrined in

DIN SPEC 91345, and will be published in both German and English in early 2016 and contrib-

uted to the international standardization process. From the point of view of standardization, the

question arises as to how an assignment of standards and specifications to processes and

means of production can be effected by means of RAMI4.0.

Source: Platform Industrie 4.0

5.2.2.2 Recommendation: Integration of existing standards

and specifications and standardization activities in the

RAMI4.0 general model

In accordance with the positioning set out above, it is recommended that all relevant standards,

specifications and use cases should be incorporated within RAMI4.0.

15 See www.bmwi.de/BMWi/Redaktion/PDF/I/industrie-40-verbaendeplattform-bericht,property= pdf,bereich=bmwi2012,sprache=de,rwb=true.pdf.

Figure 4

The Reference Architecture

Model for Industry 4.0

(RAMI4.0)

http://www.bmwi.de/BMWi/Redaktion/PDF/I/industrie-40-verbaendeplattform-bericht,property=pdf,bereich=bmwi2012,sprache=de,rwb=true.pdf

http://www.bmwi.de/BMWi/Redaktion/PDF/I/industrie-40-verbaendeplattform-bericht,property=pdf,bereich=bmwi2012,sprache=de,rwb=true.pdf


5.2.2.3 Recommendation: Compilation of a list of existing

models, and integration of existing models in the

RAMI4.0 general model

The existing standardization landscape already contains a large number of individual architecture

models. Important examples may, for instance, be found in the following:

■■ IEC TR 62832-1 Digital Factory Framework

■■ IEC 61804-1 Function Blocks for Process Control

■■ IEC 62264 Enterprise Control System Integration (enterprise model, system model and func-

tion model)

■■ IEC 61512 Batch Control (system model and process model)

■■ IEC 62769 FDI (device model)

■■ IEC 61508-6 Redundancy models

■■ IEC 61508-1 and IEC 61784-3 Safety-oriented communication model

■■ IEC 62443 Zones and conduits (architecture model for evaluation of IT security)

The general parts of many series of standards also describe models and relationship which are

architectural in character. The most important of these models are included in reference lists16, 17.

Their interrelationships are to be analysed and the importance of the individual models for the

overall context is to be explained.

5.2.2.4 Recommendation: Integration of new models

in the RAMI4.0 general model

With the present state of knowledge and on the basis of work performed to date, models are to

be selected or created, taking account of IT technologies, for the following subject areas:

■■ Quality of Services for the underlying, cross-domain communications

■■ Identification of objects and their characteristics

■■ Structure of the administration shell of the I4.0 components

■■ Generic services on the basis of the service-oriented architecture (SOA)

■■ Formal description of application functions and application services

In detail, this means the following:

16 Bitkom/VDMA/ZVEI, “Umsetzungsstrategie Industrie 4.0 – Ergebnisbericht der Plattform Industrie 4.0”, April 2015.

17 VDI/ZVEI, “Status report Reference Architecture Model Industrie 4.0 (RAMI4.0)”, April 2015.


The quality of communication required across the borders between enterprises must satisfy

certain criteria. Objects must be unequivocally addressable by means of unique identifiers. Each

object is to possess at least one administration shell, which contains all the relevant information

on the object itself and its use. On the basis of the SOA, general services which facilitate an ex-

change of information between autonomous objects which goes far beyond the previous scope

of data exchange must be defined. Finally, the application functions of data processing, classi-

cally only described to date in text or graphic form, are to be made available in the form of formal

machine-processable descriptions, adding a further part to the semantics in addition to the

characteristics and links between characteristics. In order to ensure comprehensive protection,

security considerations must be included in the conceptual design and the links to the organiza-

tional tasks clarified.

5.2.2.5 Recommendation: Characteristics,

semantics and ontologies

The method and depth of description of the metadata are particularly important in the context of

Industry 4.0. Generally applicable, simple concepts are required here.

The characteristics models are of central importance both for interoperability and for a wide-

ranging comparison of technological statements, as characteristics are a central part of the

future Industry 4.0 semantics.

In IEC 61360-1/2 and ISO 13584-42, comprehensive rules for the stipulation of characteristics

are described. Both standards have been harmonized in terms of content, with the result that

characteristics established in ISO or IEC in accordance with those documents are identically

structured.

In IEC, furthermore, there is a complete infrastructure for the creation, modification and provision

of characteristics in the form of the Common Data Dictionary (CDD).

In ISO and IEC, there are a series of characteristics projects which are as yet uncoordinated. The

classification project by eCl@ss e. V., originally founded for purchasing purposes, has developed

significantly in recent years, especially with Version 9.0, in the direction of characteristics with

very good tool support. The results of work by the now defunct PROLIST e. V. have been taken

over in full. All the characteristics of the around 30 fields of business in eCl@ss are specified in

accordance with IEC 61360.

In Germany, however, it is not only eCl@ss which is dealing with questions of semantics. The

objective must be a “semantic alliance” of all the institutions involved with this topic, aimed at

contributing the results to the international standardization at IEC and ISO.


This alliance should also take account of technologies such as Linked Data as an additional

representation format, without giving up existing semantic models, e.g. on the basis of XML.

Use cases are of tremendous importance for the work in this connection. They are developed

not only at DKE, but also at ZVEI, Bitkom and VDMA, and will be available on a harmonized

basis.18

5.2.3 Reference models of instrumentation and

control functions

5.2.3.1 Initial situation

The I&C functions are a core area of automation technology. The corresponding terms are

standardized in the IEV. They are elaborated by the manufacturers of the control systems who

supply the I&C functions as system services. They are therefore only partly standardized, as

this was not necessary in the context of practical use of the control systems. In an extended

consideration of the systems, the I&C functions are, however, not only interesting on the process

control level, but can be made available in a generalized form to all participants on all levels as

uniform system functions. For that purpose, they are to be explicitly described as reference

models and standardized.

5.2.3.2 Areas of application

■■ Control

■■ Signalling

■■ Alarms

■■ Archiving

■■ Monitoring

18 Alexander Fay, Christian Diedrich, Mario Thron, André Scholz, Philipp Puntel Schmidt, Jan Ladiges, Thom-as Holm: Wie bekommt Industrie 4.0 Bedeutung? Beiträge von Normen und Standards zu einer seman-tischen Basis (How is Industry 4.0 to achieve significance? Contributiions from standards and specifications to a semantic basis). atp (57) Vol. 7-8, pp. 30 – 43. Deutscher Industrieverlag DIV; Diedrich, Ch., Riedl, M.: Semantik durch Merkmale für I40 (Semantics from characteristics for I40). in Handbuch Industrie 4.0, 2nd edition. Ed.: Birgit Vogel-Heuser, Thomas Bauernhansl and Michael ten Hompel. Springer Verlag 2015.


5.2.3.3 Recommendation: Standardized functionality

across all levels of automation

In the past, the I&C functions were assigned to the process control level. The I&C functions are

however general functions; they apply on all levels and in many different domains. Two series

of standards supply the essential basis for description of the reference models with general ap-

plicability in the closed-loop and communication based automation of Industry 4.0:

■■ IEC 61512 (ISA S88) – Batch Control (batch-oriented operation)

■■ IEC 62264 (ISA S95) – Enterprise-control system integration

The IEC 61512 series has its roots in batch process engineering, but in terms of methodology it

is so generally structured that there is a large amount of potential, as yet relatively untapped, for

application to discrete manufacturing, continuous production processes and even to logistics.

The fundamental methodological concepts of Industry 4.0 with material flow models and indi-

vidual “assembly formulas” are similar to those of batch processing.

The models of IEC 62264 combine the aspects of IEC 61512, which are highly oriented towards

the production process itself, with the business-oriented aspects of enterprises.

The two together facilitate the description of consistent, uniform, service-oriented functionalities.

For safety and security aspects, the following standards, for example, are also to be included in

the considerations:

■■ IEC 61508 (ISA S84) – Functional safety of electrical/electronic/programmable electronic

safety-related systems

■■ IEC 62443 (ISA S99) – Industrial communication networks – Network and system security

5.2.4 Reference models of the technical and

organizational processes


The structuring and organization of the technical and organizational business processes has

up to now been the domain of the users, application suppliers and tool manufacturers. Ac-

companying the procedures stipulated by the tools, the user organizations and enterprises have

developed codes, regulations and best practice rules, etc., to make these processes efficient.

For integration of the new rule-based workflows in the general business processes, this practical

know-how has to be secured and made available in a concentrated form.


5.2.4.2 Areas of application

■■ Diagnosis

■■ Maintenance

■■ Life cycle management

■■ System migration

■■ Optimization

■■ Coexistence management of wireless applications

■■ Security management

5.2.4.3 Recommendation: Development of a framework for

uniform description of the technical and organizational

processes

Technical and organizational processes are in some cases performed by machines, and in some

cases by human beings. It is to be ascertained what a general but uniform description of such a

process could look like.

5.2.4.4 Recommendation: Creation of standards on technical

and organizational processes

The essential elements of the technical and organizational processes are to be grouped together

in standards.

5.2.5 Reference models of life cycle processes


There are concepts and standards available on the description of life cycle processes in

classical systems. With Industry 4.0, however, the systems will become more flexible, smarter

and self-adaptive. They will also adapt their structures to conform to changing environments.


5.2.5.2 Recommendation: Description of life cycle processes

in flexible, adaptive systems

A concept is to be developed to identify, describe and document life cycles in such systems.

5.3 Use Cases

5.3.1 Initial situation

For clarification of the domain-specific need for development and standardization, use cases

from which the characteristic demands of Industry 4.0 on the existing system landscape

can be deduced are to be identified. Consensus among all those involved on the relevance and

representativeness of the identified use cases is of utmost importance. For that reason, the

use cases themselves should be developed and published in the course of a consensus-based

standardization process.

Consequently, there is no complete collection of use cases, because, with the variety of indus-

tries involved, there is no single form of industrial automation. The use cases must therefore

necessarily be limited to generic types, but can be the basis of technology or project-related

implementations.

With the current topic of Industry 4.0, a method is required which meets the growing demand for

cross-system interoperability and IT security.

We are being confronted by new requirements. With the appearance of new, cross-system is-

sues, experts with different vocabularies and views of the system are coming together and need

a common methodology for their approach to Industry 4.0.

It has become apparent that the use case method can help to create a common understand-

ing of the technologies. In this approach, user stories form the basis, and the use cases derived

from these are the starting point for the definition of the requirements. By means of the use

cases, actors, data exchange and conditions are identified from the point of view of the applica-

tion, and technical details are abstracted (see Figure 5).

In order to represent the interplay between the functional actors in an abstract manner, there is a

need for a reference architecture which can be used for the implementation and visualization of

the cross-system interoperability and IT security aspects. An initial presentation of the reference

architecture for Industry 4.0 (RAMI4.0) has been developed in DIN SPEC 91345.

Figure 5:

The use case process

at DKE


The technical requirements relevant to interoperability and IT security are then enshrined in

standards and specifications in the fields concerned. Use cases therefore map processes and

implementation plans at an early stage of standardization, requiring only systematic implementa-

tion to follow.

DKE has developed a Use Case Management Repository (UCMR) to store and ensure the

consistency of the processed use cases. This is a database which facilitates standardized

compilation, collection and administration of the use cases. The uniform presentation improves

comparability. The UCMR is a freely accessible, web-based tool which allows registered

users to collaborate at any time irrespective of their location. It assists in the management and

quality assurance of the stored use cases. The detailed and generically derived use cases are

available for further standardization work, projects and as the basis of new business models

(see Figure 6).

Figure 6:

DKE Use Case

Management Repository


5.3.2 Recommendation: Standardized description template

Use cases should be described on the basis of a standardized template. This serves to improve

comprehension, comparability and the uniform usability of the use cases. The description must

contain the objectives of the use case, the background conditions on which it is based and at

least partially formalized description of the content. The descriptive template is to be standard-

ized. Stipulations in the Smart Grid field can be drawn upon for that purpose. Generic funda-

mentals for the description of use cases in templates and their export to UML are currently being

defined in IEC/TC 8 WG 5, “Methodology and Tools” (IEC 6255919). Application for Industry 4.0

should be investigated.

For the work of the standardization organizations, use cases are in particular to be used in

developing a common viewpoint across committees and organizations for the examination of

complex system topics. This will then serve as the basis for further standardization projects.

Some use cases may also be included in standards, if, for example, they support interoperability

and testability.

5.3.3 Recommendation: Reference list of important use cases

for characterization of the term “Industry 4.0”

Use cases can be compiled for a wide range of purposes. It is recommended that a set of rep-

resentative use cases be compiled, in which typical tasks and scenarios in the Industry 4.0 envi-

ronment are described. That set of use cases should be standardized as a reference basis. The

selected use cases should be coordinated in terms of breadth, depth and degree of abstraction,

and shed light on the entire field of Industry 4.0.

5.3.4 Recommendation: Use cases to illustrate the need

for standardization in the area of non-functional

properties

In practice, there are many misunderstandings and domain-specific interpretations of the non-

functional properties. In order to clarify the importance of the terminology and to explain the

specific need for standardization, it is recommended that a set of specific use cases be devel-

oped for each non-functional property.

19 IEC 62559, “Use case methodology”, in preparation.


5.4 Fundamentals


One essential aid in the development of a consistent standardization landscape is the use of

common terms and basic concepts. A common terminological basis is available in the form of

the IEV (IEC 60050 series). This will have to be expanded and supplemented for the new topics

raised by Industry 4.0.

Core models describe important basic concepts which are capable of receiving general consen-

sus and are regarded in the long term as neutral in terms of technology, stable and immutable.

These have been relatively neglected in the past as a result of the solution orientation of the

standards, but will attain considerable importance in the environment of Industry 4.0.

A further important basis is the use of common modelling and description techniques. A range

of existing modelling methods and language conventions is available from the application

domains and information science, but these do not meet the new requirements in many cases.

There is in particular a lack of concepts for mitigation of the omnipresent interface problem, and

of solutions for the formal description of product characteristics and for mastery of the variety of

versions. Descriptive languages are too specific (i.e. software-oriented) and too detailed.

5.4.2 Recommendation: Terms

Expansion of the IEV and support to DKE/UK 921.1, “Terminology in I&C systems”

The IEV (International Electrotechnical Vocabulary, IEC 60050)20 contains a section 351, “Control

technology”, which has just been updated and reflects the state of the art. The terms defined are

coherent and consolidated, and there is no current need for action in this respect. It is however

to be noted that the section in its present form fundamentally contains terms related to open

loop and closed loop control systems. The subject areas of industrial automation and informa-

tion-oriented instrumentation and control systems are not sufficiently covered by this section to

date. It appears expedient to append one or more additional sections and to structure the entire

terminological field of Industry 4.0.

Comparable standardization on terminology and ontology is supported by DIN Standards

Committee Terminology. The DIN-TERMinology Portal21, for example, provides not only the

standardized designations from current standards and their standardized translations, but

20 DKE-IEV: http://www.dke.de/de/Online-Service/DKE-IEV/Seiten/IEV-Woerterbuch.aspx, IEV: http://www.electropedia.org/, IEC Glossary: http://std.iec.ch/glossary.

21 See http://www.din.de/en/services/terminology.


also the corresponding definitions, notes, examples, etc., and, above and beyond that, also

definitions of terms from draft standards and specifications with an indication of the relevant

source document. There, the user can either search systematically for designations or view

the complete list of terms or the terms from a single standardization committee sorted in alpha-

betical order.

The determination of an Industry 4.0 terminology is to be supported.

The terms are published in the guideline VDI/VDE 2192 Part 1 and adopted in international

standardization when the period for objections has expired.

5.4.3 Recommendation: Relate terms of automation

technology and IT

The standardization of Industry 4.0 frequently draws upon terminology which is unknown in the

IT world – and vice versa. It is recommended that the terminology in the field of Industry 4.0 be

set in relation to the terminology from the field of IT, and that this terminology work be performed

on a continuous basis so that access for each group to the other’s field is facilitated.

5.4.4 Recommendation: Describe core models

Core models describe general basic terms, providing a basis for standards and model descrip-

tions. In the individual stipulations, they are either explicitly defined or implicitly assumed to be

familiar and simply used. Frequently, the models are not unequivocal even though they are actu-

ally assumed to be familiar.

There is currently no dedicated location at which these core models are explicitly defined. It

is therefore recommended that standardization documents be compiled, containing the core

models ordered by subject area.

Core models are to be described on the basis of a standardized template. This serves to

improve understanding, comparability and uniform usability. The description has to define the

core model briefly, comprehensibly and clearly. In the individual case, it has to contain formally

verifiable statements.

The relevant core models have been developed and described in DKE/WG 931.0.4 and pub-

lished by DIN as DIN SPEC 40912.


5.4.5 Recommendation: Specification of the modelling

languages to be used in standards

Languages for model description are familiar and widespread in information technology and

automation. In many cases, however, they are oriented towards software systems and cannot

be applied on a 1:1 basis to the modelling of technical problems. Nevertheless, they are popular

in practice and applied intuitively. One typical example is the singling out of various constructs

from the UML class diagram for the description of technical metamodels. For the normative

description of technical systems, there is a great need to standardize descriptive language which

can then be drawn upon. This descriptive language should be concise and unequivocal, lend

itself to correct intuitive use, and follow the existing solutions both in their structure and in their

notation.

5.5 Non-functional properties22


The target systems of Industry 4.0 are industrial manufacturing systems. In addition to their ac-

tual function, these have to possess a series of non-functional properties to fulfil the operational

requirements for efficient, safe and robust production. Non-functional properties are typically

cross-cutting properties. Both the individual elements and the nature of their interaction in the

interconnected system as a whole contribute to their fulfilment. The non-functional properties

are already an important area for standardization. This concerns the definition and demarcation

of the property itself, and the stipulation of quantitative limits for uniform classification and of

methods to ensure that those limits are actually maintained. It is a necessity and an objective for

the systemic and systematic consideration of the non-functional properties also to be applied to

the new concepts of Industry 4.0. The integral involvement of the worldwide information network,

the cross-domain consideration of production chains and the inclusion of the business process

level in that consideration result in a new system architecture, which has to be aligned with the

concepts of the non-functional properties. This is an essential condition for implementation in

operational practice.

22 Each functional unit not only has the capability of performing its primary useful function (functional proper-ties), but also other administrative and workflow-related properties. In automation technology, these are termed non-functional properties.


5.5.2 Recommendation: Define terminology

for non-functional properties

The concept of non-functional properties is increasingly gaining in importance even beyond the

field of automation technology. Non-functional properties are to be designated explicitly in stand-

ards and defined as characteristics. The term “non-functional property” is defined as opposed to

functional properties as follows: Functional properties refer, as the term indicates, to the function

of a system. The function describes the relationship between the input and output variables of a

system in general, i.e. what the user of a system expects from it. Functional properties then refer

to the input and output variables, such as available values or value range, and to properties of

the input and output variables such as the steadiness or opportunities for continuous or discrete

change of the variables. These functions are implemented by real physical systems, i.e. devices

and components. These also have properties which influence the way in which the functions are

performed. These properties of the devices and components, which often entail restrictions in

the provision and execution of the functions, are termed non-functional properties. This applies

both to hardware and to software.

The underlying terminology is to be reviewed and new terminology developed where required.

5.5.3 Recommendation: Clearly addressing

non-functional properties in standards

The description of the non-functional properties, their objectives and the resulting requirements

for regulation, the equipment manufacturers, the integrators, the operators and the users is a

demanding task and should be formulated in detail and unambiguously. The objective is to

describe each non-functional property in a standard. The basic safety standards for description

of functional safety are a very good approach in this regard, as they consider the aspect of

functional safety independently of context and can therefore in principle be generally applied.

5.5.4 Recommendation: Safety

The aim of functional safety is the protection of the surroundings from serious damage caused

by the technical system under consideration. This includes protection of human beings, protec-

tion of the environment and protection of valuable assets from serious damage. The standards


IEC 6150823, IEC 6151124 and ISO 1384925 supply not only models for analysis and assessment

of the hazards, but also detailed procedural models for determination of the necessary protec-

tive measures, handling and implementation in terms of equipment. The standards contain

methods and indicators for quantitative determination and reduction of the risk. They have

proven successful, and must also be stringently applied in future systems. It should not be at-

tempted to reduce the requirements of the relevant standards on functional safety in order to

qualify IT systems designed for general purposes as safety-related systems.

New areas of application define further requirements for safe systems and the corresponding

methods for assessment of functional safety. They should be reviewed to ascertain whether they

can also become relevant to the objectives of Industry 4.0.

5.5.5 Recommendation: Security and IT-Security

Security describes the protection of a system from impermissible external influences. The

concepts are general and can, for example, serve as basic standards for concrete solutions

or as a basis for product standards (e.g. “security by design”26). Security as a concept applies

both to physical influences, e.g. entry into a room by unauthorized persons, and to impermis-

sible influencing of an IT system via its communications interfaces. With the intensive use of the

internet for control functions in automation systems, with virtualization and cloud computing, and

also with the self-x technologies (self-configuration, self-healing and self-optimization) and the

networking of smart functions as agents, IT security is of special importance in Industry 4.0.

IT security is an essential condition for information security, and is closely connected to it.

IEC 62443 builds upon the ISO/IEC 27000 series of standards, in order to stipulate the additional

requirements for critical infrastructures.

The German Standardization Roadmap on IT Security deals with the standardization of security

aspects. It provides an overview of the focal areas of IT security standardization which are cur-

rently at the forefront of discussions, and presents prospects and recommendations for action

on the basis of the present discussions.

23 See DIN EN 61508 (VDE 0803), “Functional safety of electrical/electronic/programmable electronic safety-related systems”, series of standards.

24 See DIN EN 61511 (VDE 0810), “Functional safety – Safety instrumented systems for the process industry sector”; series of standards.

25 DIN EN ISO 13849, “Safety of machinery – Safety-related parts of control systems”; series of standards.

26 See also the implementation recommendations of the Industry 4.0 Working Group, page 46, point 1, “Security by Design”.


The standardization roadmap is compiled and regularly updated by the IT Security

Coordination Office at DIN in cooperation with DKE. The current version can be downloaded

from www.din.de/go/kits and www.dke.de/de/std/Seiten/Normungsroadmaps.aspx.

5.5.6 Recommendation: Information security

Protection of information as a valuable asset from loss and misuse, ensurance of its timely

availability to entitled users, and maintenance of its integrity and confidentiality are an indis-

pensable basis of every IT system. With the virtualization, flexibilization and coupling of internal

corporate management, production and field networks with the worldwide web, a multitude

of new challenges for information security arise. Statements, requirements, stipulations and

recommendations for information security are currently being produced at many locations. The

contacts for these are the regional data protection officers, the BSI27, and national and inter-

national standardization organizations (e.g. ISO/IEC28, DKE29 and DIN30) with active assistance

from the relevant associations (BITKOM, VDE, VDI and GMA).

Information security now also plays a central role in other areas of the CPSs, e.g. in the automo-

tive, AAL or Smart Grid fields. There are a large number of activities with more or less relevance

to the issues of cyber-physical production systems. In order to ensure that the requirements of

industrial production are fulfilled, it appears absolutely essential for a map to be created of the

CPPS environment, representing and structuring the fields, requirements and solutions offered

for information security in the industrial production environment.

5.5.7 Recommendation: Reliability and robustness

The objective of production safety is the robustness and reliability of the production systems.

Irrespective of the question of serious damage to the plant or the environment or injury to human

beings, failure of a production system is rarely tolerated today. Failures significantly reduce the

performance of a system and impair competitiveness. Modern production systems take these

facts into account and are correspondingly designed to be robust and reliable. In the CPPS field,

new concepts have to be developed to ensure failure safety even in a virtualized IT environment

without significant additional costs.

27 BSI, the German Federal Office for Information Security.

28 ISO/IEC JTC 1/SC 27, “IT Security Techniques”.

29 DKE/UK 931.1, “IT security in automation technology”.

30 DIN/NIA: NA 043-01-27, Working Committee on “IT Security Techniques”. NIA also manages the secretariat of ISO/IEC JTC 1/SC 27, “IT Security Techniques”.


However, in CPPS/Internet of Things systems, which are in some cases highly dynamically

networked, system robustness is of special importance. It must not only take account of the

properties of individual components, but must rather define a functionality docked onto the

system as a whole.

From the standardization point of view, the identified solution concepts are to be classified and

indicators defined which permit an unequivocal description of their characteristic properties.

5.5.8 Recommendation: Maintainability

In this connection, maintainability is also of significance. This is the ability of a production system

to be maintained rapidly and easily. The resulting requirements such as the opportunity for

troubleshooting, replaceability, modularity, preventive maintenance, etc., are already to be taken

into account during the planning and conceptual design of a CPPS. After all, the maintainability

of a system has a significant influence on the future workflow and cost of maintenance, and

thus on the costs and cost-effectiveness of the system. The acceptance by customers of new

Industry 4.0 solutions will therefore be influenced to a great extent by the maintainability of those

solutions.

Fundamental aspects of maintainability have already been described in

DIN EN 60300-3-10:2015-01. The specific features of Industry 4.0 solutions, which result in

particular from the vertical and horizontal integration of the systems, nevertheless require these

aspects to be accompanied by further requirements on maintainability which are inherent in

Industry 4.0: With the vertical integration of the business processes and systems, the various IT

systems also have to be integrated for maintenance purposes in such a way that information on

the current condition of the system is made available simply and rapidly to all relevant levels of

the enterprise.

Standards on integrated solutions must, however, also take account of aspects of modularity

and interchangeability, so that they, as open systems, continue to enable the operators to pro-

cure the necessary services such as repairs, maintenance or condition monitoring independently

from a variety of suppliers. In this context, particular attention is to be paid to the free exchange-

ability of condition data for condition monitoring. On the basis of VDMA Standard Sheet 24582,

DKE Working Group 931.0.13 has compiled a standardization proposal on condition monitoring

functions for uniform treatment of condition monitoring data.

The standardization proposal “UNIFORM REPRESENTATION OF CONDITION MONITORING

FUNCTIONS” has been submitted to IEC/SC 65E.

Furthermore, standards on integrated systems must take into account the usually different life

cycles of parts of those systems. The obsolescence of one part of the system must not lead to


obsolescence of the integrated system as a whole. Thus, standards for integrated Industry 4.0

solutions are to be drafted with attention to this aspect.

5.5.9 Recommendation: Real time: Stipulation of the con-

cepts and terminology in a standard

Real time is a fundamental property of all CPS systems. For the expected discussion of this topic

in widely networked, flexible, adaptive and autonomous systems, it is imperative for the relevant

concepts and properties (characteristics) of industrial real-time systems to be comprehensively

and uniformly stipulated in a standard.

5.5.10 Recommendation: Interoperability between systems

Cross-component and cross-system communications and interaction schemata are of central

importance in Industry 4.0. The systems involved have to be designed interoperably and also

behave in that way during operation.

Interoperability is the ability of equipment and components to perform a function jointly on the

basis of interactions and exchange of information. Interoperability comprises both functional

and non-functional properties. For the purpose of interoperability, it has to be determined on the

basis of those properties whether they are compatible and can work together.

5.6 Development and engineering


A highly diverse range of components and systems are developed in the environment of Indus-

try 4.0. The extent to which development processes and indicators can be standardized (and the

extent to which this would be useful at all) is not currently foreseeable.

The digital factory is an important topic within Industry 4.0. In that context, development, engi-

neering and construction are especially worthy of mention as difficult synthetic processes which

require a multitude of auxiliary and ancillary processes (artificial intelligence, simulation, verifica-

tion, etc.). The resulting requirements for system architecture have to be taken into account in

the Industry 4.0 concepts.


5.6.2 Areas of application

■■ Development of products

■■ Development of functional elements (functional, software-based, mechatronic ...)

■■ Modelling and simulation in the course of development

■■ Consistency of development in product families and variant management

■■ Verification and quality assurance for the components developed

■■ Service engineering

■■ Product development and system planning in the digital factory

■■ Simulation in advance of physical implementation, and virtual commissioning

■■ Simulation during operation for optimization planning and adaptability

■■ Consistency of development and engineering throughout the life cycle (of both the products

and the production systems and factories)

■■ Construction and commissioning

5.6.3 Recommendation: Transparent and seamless database

and development tools for the entire product life cycle

One of the central ideas of Industry 4.0 is integrated product and process development. Terms

such as “digital factory”, “reverse engineering”, “model-based development”, “concurrent engi-

neering” and “automated synthesis”, etc., show that this issue has already been discussed in the

past. Examined in detail, however, the various tasks and functions exhibit decisive differences.

The development of a mechatronic component, for example, is fundamentally different from

the development of a new vaccine and the development of a new type of plant. Nevertheless,

product descriptions, descriptions of requirements and descriptions of the process steps and

process dynamics (for simulation and production automation, etc.) play an important role in all

cases. There are already working groups dealing with standardization on this topic in profes-

sional associations and standardization organizations. These groups must be supported by

providing fundamental data structures and architectures, within which the various requirements

of the various industries can be mapped in as uniform a manner as possible.

5.6.4 Recommendation: Early support for professional IT

developments through standardization in automation

There are a large number of established standards in the field of technologies and solutions

which ensure interoperable and future-proof interaction between components in heterogeneous

networks. To that extent, there is no acute need to make changes to the tried and tested pro-

cesses. The procedure is in general conservative. The standards are only defined on an existing


and generally available technological basis. In the future, individual checks will be required to

ascertain whether or not a more rapid implementation of discernible IT developments in stand-

ardization would be appropriate. One condition is a critical analysis of the extent to which a new

IT development has the potential to be successful on a broad basis in industrial automation.

5.6.5 Recommendation: Need for research and development

in cooperating systems

The fundamental creation of system standards which describe, for example, the development

of procedures and, specifically, their dynamics relative to time, should be prepared for and sup-

ported by research and development projects.

5.6.6 Recommendation: Industrial location management

Industrial location management is the systematic detection, management and representation of

the geographical position of distributed and networked components of an automation system.

There are highly diverse approaches to the performance of this function. Uniform standards on

the following aspects are however lacking:

■■ Technologies for detection of location data

■■ Formats for location data

■■ Agreements on data storage (centralized/decentralized)

■■ Protocols for data transmission

■■ Applications and visualization tools

As, with wireless networking in particular, where the reference to a particular location is lost,

work in this field is considered advisable. Existing standards should be taken into account and

applied where appropriate. Relevant organizations for this field are the OGC (Open Geospatial

Consortium) and W3C (the working group on “Spatial Data on the Web”).

5.7 Communication

5.7.1 Initial situation of line-based communication

Industrial communication systems, also known as field buses, already provide established

solutions for line-bound communication which meets stringent requirements, on the basis of

IEEE 802.3 (Ethernet). With Industry 4.0 networks, which cover not only the shop floor but also

the office floor, however, the previous requirements are joined by further requirements concern-


ing modularization and the flexible addition, removal and rearrangement of modules. In addition

to the non-hierarchical networking of the components, the increasing number of sensors and

actuators and extended network connections for equipment, for instance for diagnosis pur-

poses, result not only in increasing data traffic but also in changing needs with regard to the

topology of the networks.

5.7.2 Initial situation of radio-based communication

Wireless communications systems are telecommunications products whose marketing and

operation are subject to legal restrictions. The European R&TTE (Radio and Telecommunica-

tions Terminal Equipment) Directive 1999/5/EC31, which has been adopted in German national

law, requires it to be demonstrated that the equipment fulfils the fundamental requirements of

the R&TTE Directive. If equipment is manufactured in accordance with the relevant harmonized

standards, the assumption is that the equipment complies with the fundamental requirements of

the Directive. The manufacturer declares this in the declaration of conformity which is to be sup-

plied with the equipment, and by affixing the CE marking.

The harmonized standards are developed on application or in response to a mandate from the

European Commission. They come into force when their references are published in the Official

Journal of the European Union (OJEU). For the R&TTE Directive, harmonized standards are

predominantly developed by the European Telecommunications Standards Institute (ETSI). In the

future, the requirements and conditions of industrial wireless communication are to be taken into

account to a greater extent in that work, as for example in the relevant standards EN 300328

and EN 300440.

Apart from the standardization committees, the requirements of industrial automation also have

to be positioned with the Commission committees such as the Telecommunications Conformity

Assessment and Market Surveillance Committee (TCAM) and the Administration Coordination

Group (ADCO), etc. This can be achieved, for example, by submitting comments on the revised

R&TTE Directive, risk assessment and so on.

The standardization of radio communication for industrial automation applications covers three

different areas:

■■ Conditions for use of the radio frequencies

■■ Technologies for radio transmission

■■ Technologies for industrial communications

31 To be replaced on 12 June 2016 by the Radio Equipment Directive (RED).


All these areas have a significant impact on the use of radio communications for Industry 4.0,

and have to be taken into account. Consequently, a standardization concept which both facili-

tates consistent solutions and sets down defined interfaces is required. The recommendations

presented in this document are aimed at establishing such a concept. The recommendations in

sections 5.7.6 to 5.7.8 concern the necessary involvement of the application experts in shaping

the conditions of use for the frequency range. The recommendation in section 5.7.9 expresses

the necessity of involving industrial automation in formulating the requirements for future devel-

opments in radio transmission.

5.7.3 Recommendation: Network management

The amount of management work for Industry 4.0 networks increases with the complexity of

the solutions. It should be investigated whether software-supported network management

on the basis of the standards and solutions for Automated Infrastructure Management (AIM)

which are already in existence or being created for other areas of application is also suitable

for Industry 4.0 or has to be upgraded with the addition of further stipulations.

5.7.4 Recommendation: Infrastructure components

In order to implement diagnosis and monitoring functions in an Industry 4.0 network, the infra-

structure components of the line-based communications systems, both active (routers, switches,

repeaters, etc.) and passive (cables and plugs), require virtual representation. The characteristics

(data describing products and data related to their application) and the condition information of

the infrastructure components are to be standardized in order to facilitate a uniform view. The

special requirements of Industry 4.0 for plug connectors are being examined in the DKE Working

Group 651.03, “Plug connectors with additional functions”.

5.7.5 Recommendation: Topology

With regard to topology, we have two different worlds at present. On the one hand, the active,

linear topology which is standard in industrial automation, in which every station has a switch

which connects both incoming and outgoing lines and the internal link to the device. On the

other hand, structured building cabling involves a star topology with the three hierarchical stages

of campus, building and floor. Investigations should be performed to ascertain what an ideal

network structure for Industry 4.0 looks like, and radio-based communication should also be

included in those considerations. This covers communication within I4.0 components and

networking between the various, in some cases mobile, I4.0 components, communication with

the higher level automation devices and links with the commercial data processing systems,


up to the cloud for data storage and cloud-based services. The solutions found are to be

standardized.

5.7.6 Recommendation: EMC

Increasing data traffic will necessitate increased bandwidth. This requirement can already be

covered with 4-pair cabling to Cat 6A, suitable for up to 10 gigabits per second. As a result of

the small voltage differences in signal encoding, this will require a very good screen quality if

EMC problems in the industrial environment are to be avoided. In this context, investigations

should be performed to ascertain whether the standard screen qualities can cope with the EMC

stresses encountered in industry, and to set out an appropriate solution. Where new stipulations

are to be made, these are to be standardized.

5.7.7 Recommendation: Work to achieve exclusive frequency

ranges for industrial automation

The flexible networking which characterizes Industry 4.0 scenarios will require more frequency

bands than are currently available. Especially for applications with high demands for real time

capability, determinism and availability, a frequency range which is available worldwide without

serious concessions to other applications in the vicinity of industrial systems will be required.

Preparatory measures are to be initiated so that such a frequency range can be obtained for

industrial automation. These measures are to include determination of the demand, identification

of a requirement package for the applications, identification of suitable radio frequencies and

mapping of the industrial automation services suitable for the ITU.

5.7.8 Recommendation: Coexistence of radio applications

A fundamental aspect of the implementation of Industry 4.0 is the communication between

spatially and organizationally distributed units, which often has to take place by radio either for

reasons of flexibility or because the units are mobile. The requirements of the various applica-

tions differ greatly, and therefore cannot be fulfilled by any single wireless technology. Radio

communication today uses frequency ranges which are not as a rule exclusively available for a

single application. A prioritization of wireless applications only takes place at present in the al-

location of frequencies by the regulatory authorities.

If high availability of the rapidly growing number of wireless applications in the industrial sector

is to be ensured, in-company coexistence management independent of the frequency range,


which takes account of the communications requirements of the technical processes and the

business processes, is required. It is necessary to define concepts which add the coexistence

aspect both to the life cycle of an industrial radio product and to the life cycle of an industrial

wireless communications system. It is to be noted that influences of the application are also of

importance in such a coexistence management process. These influences and other relevant

information, can only be made available centrally, and therefore a system with a central coordi-

nator is necessary.

The IEC/EN 6265732 standard describes a coexistence management system which is independ-

ent of frequency and can be implemented in manual or automatic forms. This represents an

important step in the right direction.

The developments in Software Defined Radio (SDR) and Cognitive Radio (CR) have potential

for automated coexistence management across the boundaries of radio technologies. This still

requires a reference model for use of the medium, libraries for various radio technologies and the

specification of standardized services for the implementation of an extensively automated ex-

change of information between the wireless applications and between the wireless applications

and the technical process or business process. Cooperation is to be sought with other relevant

consortiums and standardization organizations for this work.

5.7.9 Recommendation: Radio technologies

Some of the radio technologies developed for home and office communications also cover

the requirements of industrial automation applications. There are, however, some which are not

suitable for these IT solutions. Special stipulations have therefore been made for automation

technology in the standards IEC 61784-2, IEC 62591 (WirelessHART) and IEC 62601 (WIA-PA).

For developments such as Near Field Communication (NFC) or Software Defined and Cognitive

Radio (SDR/CR), and also for new mobile telephony standards, it will have to be ascertained

whether and for which applications they can be used without changes, or whether, for example,

profiles have to be established for their application in the industrial field. Aspects of industrial

applications are being dealt with by 3GPP and ETSI. Cooperation should be sought with these

consortiums and standardization organizations.

In the course of the implementation of Industry 4.0, a special radio standard will also become

necessary for communication in the manufacturing cell or in the vicinity of the manufacturing

machine. Standardization work on this topic is already in progress. Sensors, for example, will

play an increasingly important role in the identification of workpieces, in the control of machines

and manufacturing cells, and in the documentation of the manufacturing process. They are the

32 IEC 62657-2, “Industrial communication networks – Wireless communication network – Part 2: Coexistence management”, to be published soon in Germany as DIN EN 62657.


source of a process image which is exact as possible. On the other side, more and more actua-

tors are involved in the production process. The wiring between the growing numbers of sensors

and actuators in mechanical engineering is complex, and in some cases technically difficult to

implement. Wireless incorporation of sensors and actuators will therefore gain in importance.

The variety of suppliers of sensors and actuators, in some cases highly specialized, requires

standardization of radio communications. The properties of simple sensors (endpoint devices)

with regard to overall size, performance and price, are to be taken into account. Different ap-

proaches, where present, are to be harmonized, as diversity is not commercially viable in this

field.

5.7.10 Recommendation: Integration of radio communications

The requirements for (uniform) management of radio communications systems with a wide range

of technologies within the life cycle of manufacturing systems also have an effect on the role of

those radio systems. They are not merely a means to an end (i.e. communication), but also an

integral part of the production system. As such, the radio equipment should also be developed

as Industry 4.0 components as defined within the reference architecture model for Industry 4.0.

Corresponding actions are to be taken for integration of the radio communications and manage-

ment systems in the world of industrial automation.

Harmonized stipulations on configuration of the radio equipment and on diagnosis and fault

analysis are conceivable. This applies in particular to IT solutions in which other concepts and

strategies are pursued than those in the industrial field. In any case, action is necessary to take

account of radio applications based on new technologies in the life cycle of the production sys-

tems and specifically in the coexistence management process.

5.8 Additive manufacturing

The field of additive manufacturing is known to the public by the term “3D printing”, and is

considered there from the point of view of its benefit for individual end-users (or of the resulting

dangers, for instance the “gun from the printer”). The large, and already highly developed,

market for the application of these technologies (for there are many different technologies,

not just one, and others are coming onto the market in rapid succession), is however that of

industrial application, for example in the fields of aerospace, automotive, power engineering

and, in addition, in the fields of medical and dental technology.

Status quo:

In 2011, ISO/TC 261 “Additive Manufacturing” was founded, with a scope covering international

standardization for all processes and applications in additive manufacturing. In order to avoid


competitive situations or overlaps which would be disruptive to industry, a partnership between

ASTM and ISO was entered into only a short time later. An ASTM Committee, ASTM F42 had

shortly before commenced its standardization work on additive manufacturing with a claim to

global validity. This partnership, which has further crystallized into a highly reliable cooperative

venture in recent years, means that a common set of standards for additive manufacturing is

now being compiled by the two organizations, ISO and ASTM, with a common orientation and

the joint aim of avoiding double standardization and controlling strategically important aspects

within the framework of the available capacities. The standards are published with a joint ISO/

ASTM number, and the drafting and revision (including copyright issues) are regulated by a spe-

cial partner standards development organization agreement between the two organizations.

The standards which have been published to date concern the following:

■■ Coordinate systems and test methodologies

■■ Standard specification for additive manufacturing file format (AMF) Version 1.1

■■ Overview of process categories and feedstock

■■ Main characteristics and corresponding test methods

■■ Overview of data processing

Projects which are currently in progress (at various stages of completion) comprise the following:

■■ Terminology

■■ Guide for Design for Additive Manufacturing

■■ Requirements for purchased AM parts

■■ Standard test artifacts

■■ Standard Specification for Material Extrusion Based Additive Manufacturing of Plastic

Materials

■■ Standard Practice for Metal Powder Bed Fusion to Meet Rigid Quality Requirements

■■ Specific design guidelines on powder bed fusion

■■ Qualification, quality assurance and post processing of powder bed fusion metallic parts

■■ NDT for AM parts

On the national German level, there is close cooperation with VDI, as standardization had

already commenced there at an earlier date, and a number of the standards published by

ISO/TC 261 and also the standards currently being compiled in cooperation with ASTM F42 are

based on guidelines established by VDI FA 105.

On the European level, CEN/TC 438 “Additive Manufacturing”, founded in 2015, clarified at its

constitutive meeting that it does not intend to perform any standardization work of its own above

that of ASTM F42 and ISO/TC 261, but rather sees its function as adopting those standards in

the European environment.


The issue of a generally used data format was to have been resolved with the AMF format,

although its acceptance is not yet sufficiently widespread. With the new 3mf format, put on the

market by a consortium to which Microsoft belongs, it can be expected that there will now be a

highly widespread format as a result of that market dominance.

5.9 Human beings in Industry 4.0


The world of work in Industry 4.0 will still be inconceivable without human beings. Seen as

socio-technical work systems, flexible and adaptable production facilities provide numerous

opportunities to design work better and more compatibly with humans. With this objective, it is

appropriate to take into account established principles of the design of people-friendly working

conditions (Table 1).

One fundamental requirement is that for practicability; i.e., account must be taken of physical

and mental capabilities in the design of a work system. Tasks must always be doable. Over and

above that, it must be ensured that activities are safe, and that the design avoids accidents

and harm to health. Furthermore, the extent to which an activity is free from impairment or can

reasonably be expected of people is to be considered. This means that in the best case an

optimum of stress can be achieved: people are neither overtaxed mentally and physically, nor

are they undertaxed. New technologies also offer a variety of opportunities to organize work in

a way which promotes learning and the development of personality. Adaptive systems, for ex-

ample, can support employees individually, promote learning processes and even compensate

for physical limitations. Work systems which offer these options can have a favourable effect on

health and develop employees’ skills. When successfully implemented, such systems improve

satisfaction, motivation and efficiency.

Table 1: Criteria and principles of a people-friendly design of work, following Hacker (2005)

Assessment levels Core characteristics

Practicability Compliance with anthropometric and

neurophysiological norms

Safety Preclusion of harm to health

Freedom from impairment Work without experience of impairment;

no reduction in well-being

Personality-building Development of learning and skills


Together with these opportunities, new technologies also entail risks with regard to the

implementation of criteria for people-friendly work. In the worst-case scenario, characteristics

of automation can lead to a situation in which tasks to be performed by the employees consist

of residual activities, leading to monotony and loss of skill. The complexity and dynamism of

the cyber physical systems and their processes may, under some circumstances, also not be

sufficiently understood. This can lead indirectly to stress and safety risks.

The job to be performed is the heart of the socio-technical system, and therefore in the focus of

the people-friendly design of work. It links the organizational part of the system with the techni-

cal part, and at the same time with the human beings. By considering the world of work as a

socio-technical system, the interactions between technology, organization and personnel can be

described.

For people-friendly design of work and jobs, this leads to the “TOP principle” (Technology,

Organization, Personnel). The abbreviation is not a matter of chance, but is intended to express

the ergonomic approach that, if good, safe and healthy work is to be established, the extent

to which work can be designed as well as possible from a technical point of view, e.g. with

the objective of achieving an optimum level of stress or minimizing the risk of accidents, is first

to be ascertained. Where this is not possible, regulatory organizational measures are to be

taken, e.g. by limiting the time of exposure to stress. Only when the technical and organizational

opportunities to optimize the design of work have been exhausted should behavioural or

personnel-oriented measures be deployed, which can then compensate for the deficiencies in

the design of the work process. Such measures are, however, not to be confused with funda-

mentally skill-expanding approaches or the development of expertise. For highly capable people,

the mastering of complex challenges may represent an optimum of stress which contributes to

learning and to further development. However, this does not take place with constant efforts to

compensate for deficiencies in technology or working conditions.

The three core elements of a socio-technical system (technology, organization and personnel)

can each be influenced from three levels of action: the micro, meso and macro levels of organi-

zations. The micro level represents the individual workplace or possibly also a specific piece of

equipment. The meso level deals with complete work systems and processes between struc-

tural units of an enterprise. The macro level comprises entire enterprises and processes which

span enterprises.

The three elements of technology, organization and personnel, together with the various levels,

open up a matrix (Table 2) which can be used to systematize fields of action for people-friendly

design of work in Industry 4.0.


In the following, recommendations are derived from these fields, and are intended to contribute

to the successful introduction and implementation of Industry 4.0. The recommendations for ac-

tion cannot all be set down in standards and specifications, but in some cases also address

economic and social background conditions which are to be further developed in various ways.33

5.9.2 Recommendation: Further develop standards

and specifications for people-friendly work design in

Industry 4.0

The role of standardization in people-friendly work design has been very clear at least since

the New Approach, and is readily understandable, for example, in the field of machine safety.

By laying out the framework for the design of products, and therefore also of the means of

production, it quite literally sets standards. Here, the standards now to be developed for the

33 Hacker, W. (2005). Allgemeine Arbeitspsychologie. Psychische Regulation von Wissens-, Denk- und körper-licher Arbeit. Bern: Verlag Hans Huber (2nd, completely revised edition).

Table 2: Fields of action for people-friendly work design in Industry 4.0

Technology Organization Personnel

■z Assistance systems

■z Human-robot collaboration

■z Human-machine interface design

■z Usability

■z Room for action and

decision-making

■z Design and variety of jobs

■z Information requirement and provision

■z Qualification and expertise

■z Capability and responsibility

■z Prospective design of products and

production processes

■z Design of technology to promote

learning

■z Organization of authority and

responsibility

■z Positioning of decision-making

functions

■z Introduction of the systems

■z Process design to promote learning

■z Technology and innovation-dependent

development of expertise, and personnel

development

■z Interpersonal processes and communi-

cation

■z Works and enterprise spanning busi-

ness processes and value chains

■z Flexibility of technological resources

■z Personal data protection and

personal rights

■z Arrangement and flexibility of

working hours

■z Personnel strategy and management

■z Availability of skilled staff

■z Demographic change

■z Adaptation of initial and further training

curriculums


products of Industry 4.0 can both draw upon existing standards, for instance on machine safety

or ergonomics, and also identify new fields of work for these issues. It is therefore recommended

that, in the development of new standards, the extent to which there are existing standards for

the issues of safety and ergonomics that these be investigated and those standards then cited

and/or applied. In addition, gaps which become apparent should be defined and then filled,

where appropriate in cooperation with existing committees (e.g. the standardization committee

on ergonomics).

5.9.3 Recommendation: Technology design –

Adaptive design of work systems in Industry 4.0

The purpose of assistance systems is to support workers in the performance of their jobs. This

means that it is not people who have to adapt to machines, but machines to people. With the

objective of people-friendly design, elements conducive to learning can be implemented in this

way. Safe conditions which promote acceptance will have to be created for collaborative sce-

narios in which machines adapt autonomously within a work system.

The human-machine and machine-machine interfaces considered separately in standardiza-

tion to date will have to be combined. The scenarios arrived at in developments of Industry 4.0

indicate that machines, especially in industrial production, are deployed so flexibly that they can

interact as required with a human being or another machine to perform their tasks. Appropriate

design of overarching, flexible interoperability for a human-machine interface is to be ensured.

The complexity and dynamics of system components which reconfigure themselves place great

demands on the design of the human-machine interface (control of multiple machines). Stand-

ards for ergonomic design and for the usability of the software are becoming more and more

important.

5.9.4 Recommendation: Concepts for a functional division of

work between human beings and machines

The work of human beings in Industry 4.0 with and on machines should change in such a way

that sustainable relief from physical and mental stresses (movement of heavy loads; repetitive,

monotonous and tiring activities) can be achieved. As a result, human beings will be able to

make a greater contribution with their creative, innovative and improvisational skills, and will play

a part in motivating and conveying a sense of fulfilment.

The aim must be for human beings to regard themselves, as before, as a central and important

part of the working environment, with corresponding dignity and respect. The role of people as

the driving force behind change in Industry 4.0 should continue to be in the foreground, even if


classical interpersonal communication is now accompanied by interaction with networked and

digitized machines. The risk of humans being downgraded and/or set on the same level as pure

means of production such as plant and machinery must be taken seriously in this context.

In the design of work, the fundamental issue for human beings will be the support provided for

the relevant activity by the existing technology, in tune with the situation and the requirements.

This requires suitable assistance systems which process the available data into understandable

and useful information and by doing so put the human beings in a position to make the right

decisions.

5.9.5 Recommendation: Design of the interaction between

human beings and technical systems

Jobs are to be safely and harmlessly performed with interaction between human beings and

technical systems. The fundamental basis of interaction, the mutual exchange of information,

can be dynamic and variable in both timing and content (digitization, networking, dynamization)

and also take on direct and indirect forms. Processes of human information processing (cf. also

physical stress) are fundamental to that interaction, and should be incorporated in standardiza-

tion more frequently and to a greater extent. Possible variants of interactions with technical sys-

tems should be taken into account as varying processes. Standardization should also take into

account that jobs and allocations of functions, once made, will change in future work systems

in which interacting partners (e.g. human beings, equipment and working environments) are

extensively networked and exchange (digitized) information. Meaningful changes are those “in

the course of time”, “in terms of content” and “in their method of processing”, and combinations

of these. Changes are to be taken into account on the levels of personnel (changes in qualifica-

tions), organization (changes in information, coordination and decision-making processes with

flexible assignment of functions) and technology (usable human-machine interfaces for adaptive

and adaptable allocation of functions; local – remote or distributed). Human beings can be flex-

ibly assisted in their interaction with a technical system (tool), partially supplemented (prosthesis)

or temporarily represented (agent).34

The need for action arising from digitization results from the quantity and quality of information

to be processed for the job in hand. Networking and dynamization demand action to determine,

disseminate and coordinate the extensive and varying information held both by the human being

and the technical system. Standardization should also provide approaches for overcoming the

following challenges of people-friendly design of the human-system interaction (Lee & Seppelt,

2012; Miller et al. 2012):

34 Fraunhofer: http://www.iao.fraunhofer.de/images/iao-news/studie_future_hmi.pdf.


■■ Changes in feedback (out-of-the loop unfamiliarity, surprising mode transitions, inadequate

training and skill loss): High degrees of automation provide human beings with insufficient

information for reasonable participation. People then find changes and errors in automation

difficult to identify and impossible to compensate for.

■■ Changes in the job structure (clumsy automation, automation task errors, behavioural adap-

tation): Functions are taken away from human beings by automation, and their work is con-

sequently impaired or even hindered.

■■ Changes in the relationship structure (mismatched expectations and eutactic behav-

iour, inappropriate trust (misuse, disuse, and complacency), job satisfaction and health):

Technology-centred design of automation leads to unintended uses by people.35

5.9.6 Recommendation: Maintenance

In Industry 4.0 in general, and specifically in the factory of the future – the smart factory – main-

tenance will play a central role as the guarantor of the availability and reliability of machines and

systems. Above all against the background of increasing complexity, the growing number of

objects to be maintained and the increased use of a wide variety of technologies, maintenance

has to be prepared for these changes. The vision of smart maintenance regards it as an enabler

of Industry 4.0, keeping the cyber-physical systems (CPSs) which are notable for their high de-

gree of networking, digitization, decentralization and autonomy, efficient and available. Together

with the understanding of different technologies and the control, processing and interpretation

of big data, great importance is attached to the involvement of human beings (the maintenance

technicians) in this new working environment. Complete automation of maintenance activities

is precluded by the prevailing requirement profile of maintenance (unique nature of the work,

creativity and flexibility in finding solutions, etc.). It is therefore necessary to prepare people for

the changing requirements of work by systematic, individual training and qualification in the fields

of electronics, mechatronics, condition monitoring, system engineering, information science and

analytics. Furthermore, suitable assistance systems have to be developed to put the mainte-

nance technicians in a position to understand complex interrelationships, to select and prepare

data, to interact and communicate with machines and systems and to make the right deci-

sions. Without systematic development of maintenance into smart maintenance, the successful

implementation of Industry 4.0 will be put at risk. Initial efforts by industrial companies, research

institutes and industrial associations have already been made under the auspices of the Fraun-

hofer Institute for Material Flow and Logistics (IML) with the compilation of an acatech position

paper. Behind the initiative “Smart Maintenance for Smart Factories”36, recommendations for

35 Lee, J.D. & Seppelt, B.D. (2012). Human factors and ergonomics in automation design. In G. Sal-vendy (Ed.), Handbook of human factors and ergonomics (1615-1642). Hoboken: Wiley.

Miller, C.; Nickel, P.; Di Nocera, F.; Mulder, B.; Neerincx, M.; Parasuraman, R.; Whiteley, I. (2012). Psychology and Human-Machine Systems. In Hockey, G.R.J. (Ed.), THESEUS Towards Human Exploration of Space: a European Strategy (22-38, 54). Strasbourg: Indigo.

36 http://www.acatech.de/de/projekte/laufende-projekte/smart-maintenance.html.


action to politicians, businesses and society are being formulated, supporting these theses and

the importance of maintenance for Industry 4.0.

With regard to standards and specifications, maintenance is above all dependent on the area of

communications. Apart from establishing a formal legal framework, the aim must be to regulate

and harmonize the technical methods of communication within a CPS (human-human, human-

machine and machine-machine) and also the exchange of information, data and knowledge

beyond the bounds of individual enterprises.

5.10 Standardization processes


Industry 4.0 affects various sectors of industry, in part with traditionally different and historically

developed standardization worlds and cultures. Many new topics, including not only Industry 4.0

but also, for example, Smart Cities, Smart Grid, the energy turnaround or AAL (Ambient Assisted

Living), are characterized by the merging of different sectors. New functions which transcend the

traditional boundaries of particular industries do however require interoperability and a common

understanding of safety in the widest possible sense, and can be significantly supported by

standardization in those respects.

In advance of the actual development of standards and specifications, there is a need for estab-

lished fundamentals and a common understanding of the system which spans various sectors

of industry. As set out in greater detail elsewhere in this standardization roadmap, the following

elements have proven useful in this connection:

Use cases describe basic functionalities, actors and acting roles (IEC 62559-2), and assist in the

early development of a glossary, which is also important. On the basis of the use cases, gen-

eralized requirements for the system can be formulated, and these then described by models,

concepts and architectures, for instance the reference architecture model RAMI4.0 for Indus-

try 4.0 or DIN SPEC 91345 for I4.0 components. Standardization roadmaps serve to collate this

knowledge, to order it, to identify existing standards and specifications, to compare and contrast

the requirements and to identify the need for further development. All these elements – use

cases, reference architectures, models and standardization roadmaps – are intended to promote

a common understanding and cooperation between highly diverse professional groups. New

approaches, such as the graphically interactive Smart Grid Mapping Tool37 from IEC, combine

these elements. Further developments are impending and could also be decisively influenced by

the work on standardization of Industry 4.0.

37 http://smartgridstandardsmap.com/.


The development of standards and specifications has become a routine operation in the various

standardization organizations. Especially in the systems environment it would be appropriate to

ascertain whether other standardization results than international standards, which represent

a high level international consensus, would not be more suitable as a first step for many issues

– for instance because they would be available more rapidly or because the high degree of con-

sensus is not required. Such results may be, for example, DIN SPECs, VDE Application Guides

or VDI Guidelines on the national German level, or CEN Workshop Agreements (CWA), Technical

Specifications (TS) or Technical Reports (TR) on the international level.

While the elements listed above such as use cases or reference architectures are pre-stand-

ardization developments, it has been proposed by the Smart Grid Coordination Group38 that, if

fundamental interoperability is to be achieved, further measures must be applied after the clas-

sical standardization phase, some of which are already familiar from software engineering or in

the field of automation but can be deployed even more systematically for cross-industry system

development. For certain areas of application, the development of firm profiles which are based

on standards may be useful. Applied together with test cases/test beds – developed from the

earlier use cases in these areas of application – they can then ensure extensive interoperability.

5.10.2 Recommendation: Open Source development

In this connection, investigation of how open source developments and standardization can

complement each other is to continue.39

The recommendations presented below contain requirements which are in part a self-evident

basis of all standardization work. They are however explicitly listed once again here, as they

have taken on a new importance in the context of such a broadly based and dynamic venture as

Industry 4.0.

5.10.3 Recommendation: Modularization of stipulations

In order to stabilize the standardization process, the stipulations to be made are to be modu-

larized and categorized. The aim is the development of clearly organized individual standards

which each deal with one self-contained aspect and the stipulations of which each possess a

common degree of maturity, generality and long-term stability.

38 http://www.cencenelec.eu/standards/sectors/sustainableenergy/smartgrids/pages/default.aspx.

39 For examples see OPC UA http://open62541.org/ or http://opcfoundation.org/opc-connect/2015/06/open-shared-source-code-and-specifications-program/).

http://opcfoundation.org/opc-connect/2015/06/open-shared-source-code-and-specifications-program/

http://opcfoundation.org/opc-connect/2015/06/open-shared-source-code-and-specifications-program/


5.10.4 Recommendation: Formalization of stipulations

The contents of a standard should on the one hand be comprehensible to the reader. They

should, however, also have a formal part in which the stipulations are made in such a way that

compliance with them can be verified by formal methods in individual cases. Even if this will not

always be completely successful in every case, formalization is nevertheless to be sought as far

as possible.

5.10.5 Recommendation: Categorization of standards

Each standard should be assigned to one of the categories of “core model”, “reference model”,

“library” or “technical solution”.

■■ Core models (model universals) are models which are to be generally regarded as true, i.e.

their “correctness” and lack of alternatives are globally accepted.

■■ Reference models are suitable and accurate descriptions. However, there may be similarly

suitable alternatives to a reference model.

■■ Libraries contain classes of the various element types, specified in detail. There are there-

fore, for example, standardized libraries for characteristics, equipment types, functional

module types, service types and representation types, etc.

■■ Technical solutions describe solutions for specific technological platforms, with all the nec-

essary properties in each case. Many existing standards belong in this category.

5.10.6 Recommendation: Explicit standardization

of the core models

Core models (model universals), as models generally regarded as true, are really “laws” and not

stipulations requiring standardization. ( F = m · g does not, for example, require stipulation in a

standard.) In the field of information models, however, there are not so many of these laws. In

order to strengthen the common model base for Industry 4.0, the relevant core models are to be

explicitly described and published as standards.

5.10.7 Recommendation: Formally correct and complete

description of the reference models

The objective of standardization is the correct and complete description of the reference models.

Different concepts, strategic interests or histories can lead to different reference models. It is

to be ascertained in individual cases whether agreement on a single reference model can be


achieved. If not, the existence of several reference models is to be accepted, as long as they are

correctly formulated and suitable for describing the matter at hand.

5.10.8 Recommendation: Separate description of the

conceptual and technological stipulations

A sustainable, long-term development of Industry 4.0 can only be successful if it is based on

general, stable concepts which are extensively neutral in terms of technology. In reverse, no

innovation is possible if mapping to the currently available technologies is not stipulated by

standards. Against this background it appears expedient for the description of the conceptual

stipulations in the standards to be clearly separated from the technological stipulations. It must

be mentioned once again that both types of stipulation are necessary.

5.10.9 Recommendation: Exchange of documents

There are several consortiums and standardization organisations which are focusing on wireless

communications systems for industrial applications. These include 3GPP, Bluetooth SIG, ETSI,

IEC, IEEE, ISO, oneM2M, and PI. A coordinated roadmap on this subject requires an opportunity

for simple and unbureaucratic exchange of documents. In this way, potential for collaboration

and risks of duplicated work can be recognized at an early stage. At present, there are obstacles

to access to drafts or to standards which have been adopted but not yet published. Responsi-

bilities are to be identified so that corresponding action can be taken.

5.10.10 Recommendation: Qualifications, teaching materials,

initial and further training on the application of the

standards

The contents of the existing standards cannot always be grasped intuitively. In order to deepen

the knowledge of standards in general and in specific disciplines, and in particular to provide

the next generation in research, industry and the committees with an efficient way of taking the

first steps into the existing concepts and solutions, the publishing company Beuth Verlag offers

training courses as part of the DIN Academy.

In addition, the DIN Academy provides a variety of e-learning courses on current, practically

relevant topics. Especially for small and medium sized enterprises (SMEs), this range is a helpful

method of acquiring valuable knowledge rapidly and cost-effectively. Further information on the


learning and training materials and services on offer can be found at www.din.de/de/service-

fuer-anwender/din-akademie.

DKE organizes webinars on Industry 4.0. Together with introductory topics, the sessions devote

detailed attention to the current discussions in the area of standardization.40 More advanced

seminars are also offered by the seminar service of VDE.41

The compilation of training documents on individual standards is frequently also very helpful. The

overviews produced, for example, on IEC 62264, “Enterprise-control system integration” are a

good example to be followed in that respect.

Companies which apply standards will find useful information in a Beuth Verlag brochure tailored

especially to meet the needs of SMEs on the various ways of purchasing and viewing standards.

Those interested can obtain further information with the aid of the new e-learning tool. The con-

tents there include, for example, messages from companies which are already active in the field

of standardization. The contributions from these companies particularly emphasize the benefits

of standards for SMEs.

Furthermore, DIN offers a large variety of free information in multimedia form on the topic of

standardization at the DIN Mediathek.42

40 http://www.dke.de/de/Webinare/Seiten/Webinare.aspx.

41 https://www.vde-verlag.de/seminare.html.

42 Further information on training materials and services can be found at: http://www.din.de/de/din-und-seine-partner/presse/mediathek/mediathek-72666 http://www.din.de/de/ueber-normen-und-standards/basiswissen http://www.din.de/de/ueber-normen-und-standards/nutzen-fuer-die-wirtschaft/mittelstand/

normungswissen http://www.din.de/blob/69886/5bd30d4f89c483b829994f52f57d8ac2/kleines-1x1-der-normung-

neu-data.pdf.

http://www.din.de/de/service-fuer-anwender/din-akademie

http://www.din.de/de/service-fuer-anwender/din-akademie

http://www.din.de/de/ueber-normen-und-standards/nutzen-fuer-die-wirtschaft/mittelstand/normungswissen

http://www.din.de/de/ueber-normen-und-standards/nutzen-fuer-die-wirtschaft/mittelstand/normungswissen

http://www.din.de/blob/69886/5bd30d4f89c483b829994f52f57d8ac2/kleines-1x1-der-normung-neu-data.pdf

http://www.din.de/blob/69886/5bd30d4f89c483b829994f52f57d8ac2/kleines-1x1-der-normung-neu-data.pdf


Platform Industry 4.0

http://www.plattform-i40.de/

DIN on Industry 4.0

http://www.din.de/go/industry-4-0

Development stage standardization

http://www.din.de/en/innovation-and-research/research-projects

IT Security Coordination Office at DIN

www.din.de/go/kits

DKE on Industry 4.0

http://www.vde.com/en/dke/std/Pages/Industry40.aspx

Autonomik für Industrie 4.0

http://www.autonomik.de/en/index.php

Potentials of human-technology interaction for the efficient and networked production of

tomorrow – Fraunhofer IAO (German only)

http://www.iao.fraunhofer.de/images/iao-news/studie_future_hmi.pdf

VDI/VDE Society for Measurement and Automatic Control (GMA)

www.vdi.de/industrie40

6 FURTHER INFORMATION


The topic of Industry 4.0 touches upon a large number of professional disciplines. Fields with

great relevance to Industry 4.0 include, for example, mechanical engineering, automation,

information and communications technology, ergonomics, security, services, maintenance and

logistics. In order to provide an overview of existing standards and specifications which is inde-

pendent of committees and organizations, DIN and DKE have each established an accessible

database where the relevant standards and specifications are listed and regularly updated.

The standard and specification collection at DIN is accessible here:

www.din.de/go/industrie4-0

The standard and specification collection at DKE is accessible here:

http://dke.de/Normen-Industrie40

7 RELEVANT STANDARDS AND SPECIFICATIONS


3GPP 3rd Generation Partnership Project

AAL Active Assisted Living

acatech Deutsche Akademie der Technikwissenschaften (German National Academy of

Science and Engineering)

AE Allgemeine Empfehlungen (General Recommendations)

AK Arbeitskreis (Working Group)

BITKOM Bundesverband Informationswirtschaft, Telekommunikation und neue Medien e. V.

(Federal Association for Information Technology, Telecommunications and New

Media)

BMBF Bundesministerium für Bildung und Forschung

(Federal Ministry of Education and Research)

BMWi Bundesministerium für Wirtschaft und Technologie

(Federal Ministry for Economic Affairs and Technology)

BSI Bundesamt für Sicherheit in der Informationstechnik

(Federal Office for Information Security)

CAI Computer Assisted Instruction

CAx Computer Aided System

CDD Common Data Dictionary

CDIs Controller-device interfaces

CEN Comité Européen de Normalisation

CENELEC Comité Européen de Normalisation Électrotechnique

CPPS Cyber-physical Production System

CPS Cyber-physical System

CRM Customer Relationship Management

DIN Deutsches Institut für Normung e. V. (German Institute for Standardization)

DIN SPEC DIN Specification

DKE Deutsche Kommission Elektrotechnik Elektronik Informationstechnik im DIN und

VDE (German Commission for Electrical, Electronic & Information Technologies of

DIN and VDE)

8 ABBREVIATIONS


DL Dienstleistungen (Services)

EDDL Electronic Device Description Language

EN European standard

ERP Enterprise Resource Planning

ETSI European Telecommunications Standards Institute

EU European Union

EW Entwicklung (Research)

FB Fachbereich (Section)

FDI Field Data Integration

FDT Field Device Tool

GL Grundlagen (Fundamentals)

GMA VDI/VDE Gesellschaft Mess- und Automatisierungstechnik

(VDI/VDE Society for Measurement and Automatic Control)

ICT Information and Communications Technology

IEC International Electrotechnical Commission

IEEE Institute of Electrical and Electronics Engineers

IEV International Electrotechnical Vocabulary

IML Fraunhofer Institute for Material Flow and Logistics

INS Innovation with Norms and Standards

(a project sponsored by the German Ministry of Economic Affairs and Technology)

IPA Fraunhofer Institute for Manufacturing Engineering and Automation

ISA International Sociological Association

ISO International Organization for Standardization

IT Information Technology

ITA Industry Technical Agreement

ITG Informationstechnische Gesellschaft im VDE (VDE Information Technology Society)


ITU International Telecommunication Union

JTC Joint Technical Committee of IEC and ISO

M2M Machine-2-machine

MES Manufacturing Execution System

NAM Normenausschuss Maschinenbau

(DIN Standards Committee Mechanical Engineering)

NAMUR International User Association for Automation in Process Industries

NE Nichtfunktionale Eigenschaften (Non-functional properties)

NFC Near Field Communication

NIA Normenausschuss Informationstechnik und Anwendungen

(DIN Standards Committee Information Technology and selected IT Applications)

NS Normungsstrategie (Standardization strategy)

OASIS Organization for the Advancement of Structured Information Standards

OMG Object Management Group

OPC-UA Open Platform Communications – Unified Architecture

PAM Pluggable Authentication Module

PAS Publicly Available Specification

PDM Product Data Management

PLM Product Lifecycle Management

QMS/CRM Quality Management System program for control of production

RB Reference models of technical and organizational processes

RE Engineering

RL Reference models of instrumentation and control functions

RM Reference models

RT Reference models of technical systems and processes

SA System Architecture


SB Standardbibliotheken (Standard Libraries)

SCM Supply Chain Management

SDR/CR Software Defined Radio/Cognitive Radio

SMB Standardization Management Board (IEC)

SOA Service-oriented Architecture

SPS Stored Program Controller

TC Technical Committee

TL Technologien und Lösungen (Technologies and Solutions)

TR Technical Report

TS Technical Specification

UA Unified Architecture

UC Use Cases

UK Unterkomitee (Subcommittee)

UML Unified Modeling Language

UMTS Universal Mobile Telecommunications System

VDE Verband der Elektrotechnik, Elektronik und Informationstechnik e. V.

(Association for Electrical, Electronic & Information Technologies)

VDI Verein Deutscher Ingenieure e. V. (Association of German Engineers)

VDMA Verband Deutscher Maschinen- und Anlagenbau e. V.

(German Engineering Federation)

W3C World Wide Web Consortium

WG Working Group

XML Extensible Markup Language

ZVEI ZVEI Zentralverband Elektrotechnik- und Elektronikindustrie e. V.

(Central Association of the Electrical and Electronics Industry)


Prof. Dr. Lars Adolph, Bundesanstalt für Arbeitsschutz und Arbeitsmedizin (BAuA), Dortmund

Thomas Anlahr, Fraunhofer-Institut für Materialfluss und Logistik IML, Dortmund

Dr. Heinz Bedenbender, VDI, Düsseldorf

Alexander Bentkus, DKE, Frankfurt am Main

Prof. Dr. Lennart Brumby, Duale Hochschule Baden-Württemberg Mannheim, Eppelheim

Prof. Dr. Christian Diedrich, IFAK, Magdeburg

Dr. Dagmar Dirzus, VDI, Düsseldorf

Filiz Elmas, DIN, Berlin

Prof. Dr. Ulrich Epple, RWTH Aachen, Aachen

Dr. Jochen Friedrich, IBM, Mannheim

Jessica Fritz, DKE, Frankfurt am Main

Dr. Hansjürgen Gebhardt, Institut ASER e. V., Wuppertal

Jan Geilen, Bundesanstalt für Arbeitsschutz und Arbeitsmedizin (BAuA), Dortmund

Dr.-Ing. Christoph Hecker, Deutsche Gesetzliche Unfallversicherung (DGUV) e. V., Mainz

Roland Heidel, Kommunikationslösungen e.K., Kandel

Klaus Hemberger, BNetzA, Mainz

Stefan Hiensch, BNetzA, Mainz

Prof. Dr. Dr. Eric Hilgendorf, Universität Würzburg

Dr. Günter Hörcher, Fraunhofer IPA, Stuttgart

Eckehardt Klemm, Phoenix Contact, Bad Pyrmont

Jens Mehrfeld, Bundesamt für Sicherheit in der Informationstechnik (BSI), Bonn

9 THE AUTHORS


Theo Metzger, Bundesnetzagentur, Berlin

Dr. Stephan Middelkamp, HARTING, Espelkamp

Dr. Christian Mosch, VDMA, Frankfurt am Main

Dr. Peter Nickel, Deutsche Gesetzliche Unfallversicherung (IFA), Sankt Augustin

Reinhold Pichler, DKE, Frankfurt am Main

Christopher Prinz, Ruhr-Universität Bochum, Bochum

Dr. Lutz Rauchhaupt, ifak, Magdeburg

Ingo Rolle, DKE, Frankfurt am Main

Prof. Dr. Felix Sasaki, W3C/DFKI GmbH, Berlin

Uwe Seidel, VDI/VDE Innovation + Technik GmbH, Berlin

Johannes Stein, DKE, Frankfurt am Main

Daniela Tieves-Sander, KAN Kommission Arbeitsschutz und Normung, Sankt Augustin

Dr. Carsten Ullrich, DFKI GmbH, Berlin

Ingo Weber, Siemens, Karlsruhe

Wei Wei, IBM, Düsseldorf

Ludwig Winkel, Siemens, Karlsruhe

DIN e. V.

Am DIN-Platz · Burggrafenstraße 6

10787 Berlin · Tel.: +49 30 2601-0


Internet: www.din.de

DKE Deutsche Kommission Elektrotechnik

Elektronik Informationstechnik in DIN und VDE

Stresemannallee 15 · 60596 Frankfurt

Tel.: +49 69 6308-0 · Fax: +49 69 08-9863


Internet: www.dke.de

www.dke.de

din/dke – roadmap - home - 3c creative communication … · 2017-10-06 · this standardization...

Documents