Kai Garrels, Chair of the Working Group “Reference Architectures, Standards and Norms“

Kai Garrels, Chair of the Working Group “Reference Architectures, Standards and Norms“

© Andreas Henn

Question 1: Interoperability is indispensable when it comes to smart connections between installations and products. How can it be ensured that all components in a value chain are working together in harmony?

There are three essential aspects necessary for seamless interaction to take place. The first aspect is a joint communication structure, i.e. networks and protocols. At Plattform Industrie 4.0 we assume that the internet provides this joint network. This means that the Internet Protocol IP forms the lowest basis for communication.

Secondly, it takes a common language with symbols, vocabulary, grammar and semantics. The central building block here is the Industrie 4.0 component. This I4.0 component consists of a physical object – a machine, a component, etc. – and the object’s digital image, the so-called Administration Shell. The Administration Shell was designed by the Plattform and it provides for the exchange of features, process variables and desired values, as well as accessing objective functionalities. The following instructions, for instance: “drill a hole of 3.5mm in diameter and 4mm deep at position 4”.

Thirdly, there is a need for joint rules on cyber security and data protection. This topic is being addressed by our Working Group AG3, which we closely cooperate with. The central concept here is called data integrity.


Question 2: Different industries, IT and machinery – Industrie 4.0 brings together many different areas which at first glance appear to be quite separate from each other. What impact does this have when establishing standards?

First of all, it is important for providers and customers of industry components and machines to get together and to clarify what the most important pieces of information are that need to be exchanged, e.g. between providers and users of electric drives or other automation components. On this, software and hardware experts from Industrie 4.0, VDMA and ZVEI are working together in different Working Groups.

The term “industry” refers both to the areas of manufacturing industry and to process industry. Digitalisation however does not stop at the sectoral border of “industry”; a smart tractor for example is produced by “industry” but is then used in the area of “smart agriculture”. Our aim is for our suggestions to connect these sectoral borders, which is why we cannot simply rely on industry standards but also have to look at how we can integrate other sectors.

Of course, we don’t want our suggestions to be limited by national borders, which is why we are in close contact with other countries, such as France and China. At the end of the day, we hope to achieve international standardisation and in this endeavour, we enjoy support from the Standardization Council I4.0, which coordinates the German standardisation efforts at an international level.


Question 3: Many companies are hesitant when it comes to investing, since they do not want to bet on a standard which may end up not prevailing. What is your advice for companies when it comes to dealing with standards?

In my view there are two steps: first of all, companies should already be asking themselves strategic questions linked to digitalisation: How will my sector and my company be changing? Through which channels will our products be sold and how will customers be making decisions? Is the product the decisive factor, or do other aspects come into play? What will be the role of accompanying data or of digital functions, service offers or the perfect placement of the product in web shops or engineering tools which our customers are using? Anyone who has recently chosen and bought a new car for instance has perhaps already gained a first impression of these changes. These are questions that the SME 4.0 Competence Centre can provide support on.

When it comes to the next step and drawing conclusions, standards play an important role: What is the basis upon which I wish to build my internal automation landscape, for example? What interfaces are my customers expecting from me? How can I “supply” my product data? For which processes do I need to collect and provide additional information? Once there are appropriate standards that value chain partners have been able to agree on, cooperation will become easier. There already exist some clearly identified candidates, such as for instance OPC-UA for communication in manufacturing, or ecl@ss for the exchange of product features.

It seems to me that making a quick start, experimenting and taking those first steps is more important that simply waiting for the “perfect, accepted” standard to come along. By waiting, one runs the risk of missing the right moment and not leaving oneself enough time to practice and try things out.