2 STANDARDIZATION ROADMAP. Published by VDE ASSOCIATION FOR ELECTRICAL, ELECTRONIC & INFORMATION TECHNOLOGIES

Published by

VDE ASSOCIATION FOR ELECTRICAL, ELECTRONIC & INFORMATION TECHNOLOGIES as the umbrella organization of DKE German Commission for Electrical,

Electronic & Information Technologies of DIN and VDE Stresemannallee 15 D-60596 Frankfurt Phone: +49 69 6308-0 Fax: +49 69 6308-9863 Email: [email protected] Internet: www.dke.de Issue date: 04.2013

6

Recommendations for action in the standardization of Industrie 4.0

6.1 General recommendations (AE). . . 29

6.2 Recommendations on standardization strategy (NoS) . . . 31

6.3 Recommendations on the area of system architecture (SA) . . . 33

6.4 Recommendations on the area of use cases (UC) . . . 34

6.5 Recommendations on the area of fundamentals (GL). . . 35

6.6 Recommendations on the area of non-functional properties (NE) . . . 36

6.7 Recommendations on the area of reference models (RM) . . . 42

6.8 Recommendations on the area of development and engineering (RE) . . . 44

6.9 Recommendations on the area of technologies and solutions (TL) . . . 45

7

Links

8

Relevant standards and specifications

8.1 ISO / CEN / DIN . . . 47

8.2 IEC / CENELEC / DKE . . . 52

8.3 VDI/VDE . . . 54

8.4 Consortium specifications . . . 54

9

Abbreviations

10

Working group ”Standardization concept for industrie 4.0“

in division 9 of the DKE

Image directory

Figure 2 The four life cycles in industrial manufacturing (Source: ARC, with additions by Fraunhofer IPA) . . . 10

Figure 3 Innovation from standardization . . . 13

2.1 Future project Industrie 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 techno-logies and the management of complex industrial processes.” These introductory sentences from the implementation recommendations of the “Industrie 4.0” working group formed by the Industry and Science Research Union (see chapter 7) 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. It is necessary to defend and build upon that position within the context of international competition.

The future project Industrie 4.0 presented by the German Federal Government is intended to reflect the importance of manufacturing technology and the ICT sector which supports 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 Industrie 4.0 platform established by the associations ZVEI, VDMA and BITKOM, and the Scientific Advisory Board.

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 Industrie 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.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 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 concepts of automation, human beings are not to be “optimized out” of the production proces-ses, but rather to be given an increasingly important role: The CPPSs are to supply them with compressed 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. Figure 1 shows an example of a situation with various contributions between (partly) autonomous CPSs (mechatronic and human) which are to be controlled by the system as a whole in real time by the application of rules.

Figure 1 – Communication between CPSs (Source: Fraunhofer IAO)

I’ll top up the magazine.

Switch me off!

I can work this Saturday.

Booked up to capacity until Friday!

I’ve got to be in the shipping area

in 2 hours!

Sorry, I can’t work on Saturday.

Magazine empty. Please fill it!

Customer order: 50 gearboxes by Monday

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 rule-based and situation-controlled cooperation between machines and human beings is orga-nized.

Research l a ir t s u d n I support Standardization Innovation Functionality Practical relevance Marke t Methodology Stability Security of investment

4 THE CURRENT STANDARDIZATION

ENVIRONMENT

4.1 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 project Industrie 4.0. Industrie 4.0 requires an unprecedented degree of system integration across domain borders, 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 innovation: methodical soundness and functionality, stability and security of investments, practicability and market relevance.

Figure 3 –

Innovation from standardization

A prompt firming-up of concepts by a standardization process based on consensus and accom-panying research is also essential for rapid implementation in industrial practice.

The alternative routes are shown in figure 4. 90 % of national standards in the field of electrical engineering are now based on international standards from IEC. IEC standards are agreed in pa-rallel during the compilation process on the European level (CENELEC5_{) and on the international}

level, and then adopted nationally in Germany as DIN standards (Dresden Agreement6_{). There is}

a comparable procedure at ISO and CEN7 _{under the terms of the Vienna Agreement}8_.

It has become apparent in recent years that the development and elaboration of proposals for and contents of standards by the responsible standardization committees themselves is increa-singly meeting its limits. In many cases, the time available to the voluntary members of the com-mittees is insufficient. For that reason, the alternative route of extensive preparation of standards by consortiums and professional associations has become established in many areas.

As a result, the committees responsible for standardization are more and more taking on the functions of reviewing, facilitation, support, consultation and integration. They ensure that the interested groups are informed of the contents and the planned procedures, and that the standardization process is based on consensus. Together with these functions and the day to day administrative and editorial tasks, standardization committees are increasingly taking on an important role in analysing the existing standardization landscape and initiating and coordinating standardization projects in strategically important areas.

Figure 4 – From the need for standardization to the standard

Consensus-based standardization (Associations) Consortium standardization (Consortiums) l a n o it a n r e t n I standardization IEC , ISO, ITU (DKE, DIN) European adoption CEN, CENELEC I S T E l a n o it a N adoption DIN , DKE l a n o it a N standard N E standards Consortium standard ISO , IEC standards DIN standards Development of products and services Application in practice Need for standardization l a c i g o l o n h c e T development , h c r a e s e R strategic projects Technological development Environment (e.g. laws)

5 CENELEC – Comité Européen de Normalisation Électrotechnique, European Committee for electronic Standardization

6 Dresden Agreement: See CENELEC Guide 13,

http://www.cenelec.eu/membersandexperts/referencematerial/cenelecguides.html 7 CEN – Comité Européen de Normalisation, European Committee for Standardization

4.3 The national standardization landscape in automation

■

■ VDI/VDE guidelines (GMA)

■

■ NAMUR recommendations (NAMUR)

■

■ VDMA standard sheets (VDMA)

■

■ Preliminary DIN standards (DIN and DKE) ■

■ Technical reports (DIN and DKE)

In addition, the standardization organizations VDE/DKE and DIN provide opportunities to make specifications available to the market rapidly in the form of a DIN SPEC or VDE code of practice. For questions of procedure and organizational arrangements, guidelines such as

■

■ BITKOM guidelines (BITKOM)

■

■ ZVEI guidelines (ZVEI)

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.

GMY: VDI/VDE Society for Measurement and Automatic Control NAMUR: International User Association in Process Industries VDMA: German Engineering Federation

DIN: German Institute for Standardization

DKE: German Comission for Electrical, Electronic and Information Technologies of DIN and VDE BITKOM: Federal Association for Information Technology, Telecommunications and New Media ZVEI: Central Association of the Electrical and Electronics Industry

4.5 Standardization in information technology

In the IT world, specifications are typically developed and pursued by open communities which act internationally. One example is the W3C Consortium. In spite of their worldwide acceptance and importance, these specifications are not always adopted as de jure standards. When they are, this is often done by the ISO/IEC Joint Technical Committee JTC 1, “Information Technolo-gy”. That committee deals with a large number of standardization topics in information technolo-gy:

ISO/IEC JTC 1 “Information Technology” ■

■ JTC 1/WG 7 “Sensor networks” ■

■ JTC 1/SWG 5 “Internet of Things (IoT)” ■

■ JTC 1/WG 8 “Governance of IT” ■

■ JTC 1/SC 2 “Coded character sets” ■

■ JTC 1/SC 6 “Telecommunications and information exchange between systems” ■

■ JTC 1/SC 7 “Software and systems engineering” ■

■ JTC 1/SC 17 “Cards and personal identification” ■

■ JTC 1/SC 22 “Programming languages, their environments and system software interfaces”

■

■ JTC 1/SC 23 “Digitally Recorded Media for Information Interchange and Storage” ■

■ JTC 1/SC 24 “Computer graphics, image processing and environmental data representation”

■

■ JTC 1/ SC 25 “Interconnection of information technology equipment” ■

■ JTC 1/ SC 27 “IT security techniques” ■

■ JTC 1/ SC 28 “Office equipment” ■

■ JTC 1/ SC 29 “Coding of audio, picture, multimedia and hypermedia information” ■

■ JTC 1/ SC 31 “Automatic identification and data capture techniques” ■

■ JTC 1/ SC 32 “Data management and interchange” ■

■ JTC 1/ SC 34 “Document description and processing languages” ■

■ JTC 1/ SC 35 “User interfaces” ■

■ JTC 1/ SC 36 “Information technology for learning, education and training” ■

■ JTC 1/ SC 37 “Biometrics” ■

■ JTC 1/ SC 38 “Distributed application platforms and services (DAPS)” ■

5.1 Subject area SA: System architecture

Overall architecture

As discussed above, the relevant models of classical architecture are to be integrated and roun-ded off for Industrie 4.0. A reference model for the overall architecture is first to be developed. Architecture models to date, where developed in partial areas, are mostly function and techno-logy-driven. An architecture which is neutral in terms of technology is however required for such an extensive concept as Industrie 4.0. With today’s highly advanced state of the art, it can be assumed that the necessary technologies for implementation of the architecture concept are available. The new architectural approach focuses on service-orientation, autonomy, adaptivity and cooperativity. As standardization has also up to now been extensively technology-driven, the standardization processes themselves are also to be adapted to take account of this new procedure.

Owing to its fundamental importance, system architecture is to be regarded as a subject area in its own right with a special need for standardization.

5.2 Subject area UC: Use cases

Use cases

For clarification of the domain-specific need for development and standardization, Use cases from which the characteristic demands of the fourth stage of industry on the existing system landscape are to be identified. Consensus among all those involved on the relevance and representativeness of the identified use cases is of decisive importance. For that reason, the use cases themselves should be developed and published in the course of a consensus-based standardization process.

Industrial automation is characterized by the endeavour to achieve commercially justifiable quantities of automation components by covering as much of the various industries as possible. On the one hand, this requires compromises, and on the other hand variable options, which, however, often lead to a number of adjustable or changeable parameters which customers find overwhelming. With regard to the hardware of such components, the customer requirements range from the greatest possible degree of robustness (“military quality”) and the lowest possible price (“consumer price”). At the development stage it is often difficult to combine the two, but this is made easier by the application of standards. The use cases are to be compiled against this background. For the reasons stated, there also cannot be any closed collection of use cases, as the variety of sectors precludes any blanket automation of industry. The use cases therefore have to be limited to generic types, but can form the basis of implementation for speci-fic technologies and specispeci-fic projects.

5 OBJECT AREAS WITH A NEED FOR

STANDARDIZATION FOR INDUSTRIE 4.0

5.4 Subject area NE: Non-functional properties

The target systems of Industrie 4.0 are industrial production systems. In addition to their actual 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 me-thods 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 Industrie 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 (subject area SA), which has to be aligned with the concepts of the non-functional properties. This is an essential condition for implementation in operational practice.

9 Each functional unit not only has the capability of performing its primary useful function (functional properties), but also other administrative and workflow-related properties. In automation technology, these are termed non-functional properties.

5.6 Subject area RL: Reference models of

the instrumentation and control functions

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.7 Subject area RB: Reference models of

the technical and organizational processes

■ Diagnosis ■

■ Maintenance ■

■ Life cycle management ■

■ System migration ■

■ Optimization ■

■ Coexistence management of wireless applications ■

■ Security management ■

■ …

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. Accompany-ing the procedures stipulated by the tools, the user organizations and enterprises have develo-ped codes, regulations and best practice rules, etc., to make these processes efficient. In order to secure this knowledge and make it available to users in a concentrated form for integration in the general business processes, it appears appropriate to group the essential elements of the technical and organizational business processes together in standards.

5.11 Subject area SB: Standard libraries

The detailed stipulation of terminology and syntax is a basic requirement for interoperability. The success of Industrie 4.0 will essentially depend on the availability of standardized characteristic libraries, element libraries or descriptive languages for equipment and functional modules, and services libraries.

5.12 Subject area TL: Technologies and solutions

On fundamental aspect of standardization is the stipulation of the actual mapping of the individu-al concepts to the available technologies. This is the basis of products and industriindividu-al solutions. These standards require constant further development and adaptation to reflect the technical background conditions. Many of the existing standards combine the conceptual findings with the mapping to technological solutions (OPC-UA, SOA, PROFIBUS, FDI ...).

In the field of industrial automation, there are a large number of existing standards which have proven their worth in practice. The new requirements of the Industrie 4.0 landscape are however expected to make extensions and upgrading necessary. In many cases, substantive reorga-nization 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.

Recommendation AE-3:

Support for the established standardization committees by additional experts

If they are to be familiar with and influence the relevant core standards in IEC and ISO, 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 in that way 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 to facilitate participation by its experts in national and inter-national 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.

Recommendation AE-4: Training

The contents of the existing standards cannot be grasped intuitively. Training courses are an appropriate method of providing an efficient introduction to the existing concepts and solutions, especially for young people in research, industry and the committees. A first step would be the compilation of training documents on the individual standards. The overviews produced, for ex-ample, on IEC 62264, “Enterprise-control system integration” are a good example to be followed in that respect.

Recommendation AE-5:

Research and development requirements for emergent systems

The fundamental drafting of system standards which, for example, describe the development of procedures and specifically their chronological dynamics, should be prepared for and supported by research and development projects.

Recommendation NoS-4:

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 Industrie 4.0, the relevant core models are to be explicitly described and published as standards.

Recommendation NoS-5:

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 apt as descriptions of the matter at hand.

Recommendation NoS-6:

Functions and roles of human beings in Industrie 4.0

Starting with the new functions and roles of human beings in Industrie 4.0, the need for technical support, especially in the area of human-machine interfaces, is to be described.10

Recommendation NoS-7:

Separate description of the conceptual and technological stipulations

A sustainable, long-term development of Industrie 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.

6.4 Recommendations on the area of use cases (UC)

Recommendation UC-1:

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 an at least partially formalized description of the content. The descriptive template is to be standardized. Stipulations in the Smart Grid field can be drawn upon for that purpose. Generic fundamentals 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 62559)11_{. Application for Industrie 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.

Recommendation UC-2:

Reference list of important use cases for characterization of the term “Industrie 4.0”

Use cases can be compiled for a wide range of purposes. It is recommended that a set of repre-sentative use cases be compiled, in which typical tasks and scenarios in the Industrie 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 Industrie 4.0.

Recommendation UC-3:

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 develo-ped for each non-functional property.

6.6 Recommendations on the area of

non-functional properties (NE)

Recommendation NE-1:

Define terminology for the non-functional properties

The concept of non-functional properties is increasingly gaining in importance even beyond the field of automation technology. The underlying terminology is to be reviewed and new terminolo-gy developed where required (see also Recommendation GL-1).

Recommendation NE-2:

Clear addressing of the non-functional properties in separate 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 be to describe each non-functional property in its own standard (or several standards). The basic safe-ty standards for description of functional safesafe-ty 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.

Recommendation GL-3:

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 descrip-tion of technical systems, there is a great need to standardize descriptive languages which can then be drawn upon. These descriptive languages should be concise and not overly expressive, lend themselves to correct intuitive use, and follow the existing solutions both in their structure and in their notation.

18 BSI, the German Federal Office for Information Security 19 ISO/IEC JTC 1/SC 27, “IT Security Techniques” 20 DKE/UK 931.1, “IT security in automation technology”

21 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”

Recommendation NE-5: Information security

Protection of information as a valuable asset from loss and misuse, ensurance of its timely pro-vision to entitled users, and maintenance of its integrity and confidentiality are an indispensable 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 chal-lenges for information security arise. Statements, requirements, stipulations and recommenda-tions for information security are currently being produced at many locarecommenda-tions. The contacts for these are the regional data protection officers, the BSI18_{, and national and international}

standar-dization organizations (e.g. ISO/IEC19_{, DKE}20 _{and DIN}21_{) 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.

Recommendation NE-6: 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 account of this aspect 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.

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 pro-perties of individual components, but must rather define a functionality docked onto the system as a whole.

23 See EN 300328, “Electromagnetic compatibility and Radio spectrum Matters (ERM) - Wideband transmission systems - Data transmission equipment operating in the 2,4 GHz ISM band and using wide band modulation techniques”; series of standards 

24 See EN 300440, “Electromagnetic compatibility and Radio spectrum Matters (ERM) - Short range devices - Ra-dio equipment to be used in the 1 GHz to 40 GHz frequency range”; series of standards

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.

It is to be noted that wireless communications systems are telecommunications products whose marketing and operation are subject to legal restrictions. The European R&TTE (Radio and Tele-communications Terminal Equipment) Directive 1999/5/EC, which has been adopted in German national law, requires it to be demonstrated that the equipment fulfils the fundamental requi-rements 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 supplied 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 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 30032823

and EN 300440 (ETSI).24

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.

Regulations on the efficient use of frequencies, harmonized throughout Europe, are developed by the Electronic Communications Committee (ECC) of the CEPT (European Conference of Postal and Telecommunications Administrations. For that purpose, ECC Decisions and ECC Recommendations in particular are compiled and put into force. CEPT comprises administ-rations from 48 countries. The cooperation between CEPT/ECC and ETSI, and that with the

6.7 Recommendations on the area of reference models (RM)

6.7.1 Reference models in general

Recommendation RM-1-1:

Description of the reference models in separate standards

Like core models, reference models are also used in a wide variety of solution models. For harmonization, avoidance of unintentional deviations and for a better understanding, reference models should be described separately as independent standards.

Recommendation RM-1-2:

Primary and secondary objectives of reference model standardization

The primary objective of a reference model is the clear and unequivocal description of a model or a relevant situation. A reference model which satisfies these criteria is a standardizable refe-rence model. A second objective is to have only one referefe-rence 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.

Recommendation RM-1-3:

Standardized structure for the description of reference models

The structure of the description of reference models is to be as uniform as possible. If possible, the design patterns or templates for the core models should be used as the basis.

6.8 Recommendations on the area of development and

engi-neering (RE)

Recommendation RE-1:

Structuring and review of the distribution of functions in the field of the “digital factory”

One of the central ideas of Industrie 4.0 is integrated product and process development. Terms such as “digital factory”, “reverse engineering”, “model-based development” and “automated synthesis”, etc., show that this issue has already been discussed in the past. Examined in detail, the various tasks and functions exhibit decisive differences. The development of a mechatro-nic 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 dynamics (for simulation and design of control systems, etc.) play an important role in all cases. It appears appropriate to deal with this topic in separate working groups. There are already working groups dealing with standardization on this topic in professional associations and standardization organizations. The work of these groups is to be supported.

Recommendation RE-2:

Synthesis of automation systems is to become a focal topic

One special area is the development and engineering of the automation systems. This is only a small part of the subject, but an especially important one for automation technology. Co-deve-lopment with the IT functions, verification of the software developed, model-driven deveCo-deve-lopment, automated synthesis, adaptation during production and autonomous self-x technologies are only a few of the keywords which characterize the issue.

In this area, it appears imperative to establish a special group to analyze and order the need for standardization in close contact with the operational standardization committees on the one hand and with the research projects on the other.

7 LINKS

[1] DKE, Division 9, Process measurement and control technologies: http://www.dke.de/de/ Wirueberuns/DieDKE-Struktur/Organisationsstruktur/Seiten/Bereichs%c3%bcbersicht. aspx?Fachbereich=9

[2] IAO “The Potential of Human-Machine Interaction for the Efficient and Networked Produc-tion of Tomorrow”: http://www.iao.fraunhofer.de/images/iao-news/studie_future_hmi-en. pdf

[3] GMA: Thesen und Handlungsfelder “Cyber-Physical Systems: Chancen und Nutzen aus Sicht der Automation” (Cyber-Physical Systems: Opportunities and benefits from the point of view of automation): http://www.vdi.de/uploads/media/Stellungnahme_Cyber-Physical_ Systems.pdf

[4] Industrie 4.0 Platform: http://www.plattform-i40.de/

[5] Implementation recommendations (April 2013): http://www.plattform-i40.de/finalreport2013 [6] Autonomics research projects: http://www.autonomik.de/en/index.php

[7] Autonomics for Industrie 4.0: http://www.autonomik.de/de/1003.php [8] IEC/TC 65: http://www.iec.ch/dyn/www/f?p=103:7:0::::FSP_ORG_ID:1250

8.1.2 From ISO/TC 184 SC 2

Standard Title

ISO 8373:2012 Robots and robotic devices – Vocabulary

ISO 9283:1998 Manipulating industrial robots – Performance criteria and related test methods

ISO 9409:2004 Manipulating industrial robots – Mechanical interfaces

ISO 9787:2013 Robots and robotic devices – Coordinate systems and motion no-menclatures

ISO 9946:1999 Manipulating industrial robots – Presentation of characteristics ISO 10218:2011 Robots and robotic devices – Safety requirements for industrial

robots –

ISO 11593:1996 Manipulating industrial robots – Automatic end effector exchange systems – Vocabulary and presentation of characteristics

ISO/TR 13309:1995 Manipulating industrial robots – Informative guide on test equipment and metrology methods of operation for robot performance evaluati-on in accordance with ISO 9283

ISO/FDIS 13482 Robots and robotic devices – Safety requirements for personal care robots

ISO 14539:2000 Manipulating industrial robots – Object handling with grasp-type grippers – Vocabulary and presentation of characteristics

ISO/AWI 18646-1 Robots and robotic devices – Performance criteria and related test methods for service robot

8.1.4 From ISO/TC 184 SC 5

Standard Title

ISO 9506-1:2003 Industrial automation systems – Manufacturing Message Specifica-tion

ISO/TR 10314:1990 Industrial automation – Shop floor production ISO/TR 11065:1992 Industrial automation glossary

ISO 11354:2011 Advanced automation technologies and their applications – Require-ments for establishing manufacturing enterprise process interopera-bility

ISO 13281:1997 Industrial automation systems – Manufacturing Automation Program-ming Environment (MAPLE) – Functional architecture

ISO/TR 13283:1998 Industrial automation – Time-critical communications architectu-res – User requirements and network management for time-critical communications systems

ISO 14258:1998 Industrial automation systems – Concepts and rules for enterprise models

ISO 15704:2000 Industrial automation systems – Requirements for enterprise-refe-rence architectures and methodologies

ISO 15745:2003 Industrial automation systems and integration – Open systems appli-cation integration framework

ISO/CD 15746 Automation systems and integration – Integration of advanced pro-cess control and optimization for manufacturing systems

ISO 16100:2009 Industrial automation systems and integration – Manufacturing soft-ware capability profiling for interoperability

ISO/TR 18161 Automation systems and integration – Applications integration approach using information exchange requirements modelling and software capability profiling

ISO 18435:2009 Industrial automation systems and integration – Diagnostics, capabili-ty assessment and maintenance applications integration

8.2 IEC / CENELEC / DKE

Standard Title

Architecture

IEC 62264:2013 Enterprise-control system integration Communication

IEC 61158 Digital data communication for measurement and control – Fieldbus for use in industrial control systems

IEC 61784 Industrial communication networks – Profiles

IEC 62026 Low-voltage switchgear and controlgear – Controller-device interfaces (CDIs)

ISO/IEC 14543-3 Information technology – Home electronic system (HES) architecture IEC 62591 Industrial communication networks – Wireless communication

net-work and communication profiles – WirelessHARTTM

IEC 62601 Industrial communication networks – Fieldbus specifications – WIA-PA communication network and communication profile

Service oriented Architecture

IEC 62541 OPC UA

Security

8.3 VDI/VDE

Standard Title

VDI/VDE 2182 series IT security for industrial automation

VDI/VDE 2185 series Radio based communication in industrial automation

VDI/VDE 2651 Plant Asset Management (PAM) in the process industry – Definition, model, task, benefit

VDI/VDE 2657 Middleware in industrial automation – Fundamentals

VDI 2884 Purchase, operating and maintenance of production equipment using Life Cycle Costing (LCC)

VDI 2885 Standardized data for maintenance planning and determination of maintenance costs – Data and data determination

VDI 3385 GDX interface – Consistent data format from development to produc-tion (working title)

VDI 3633 series Simulation of systems in materials handling, logistics and production VDI/VDE 3699 series Process control using display screens

VDI/VDE 3850 series Development of usable user interfaces for technical plants VDI 4464 Operation of industrial trucks with RFID components VDI 4499 series Digital factory

VDI 4472 series Requirements to be met by transponder systems for use in the supply chain

VDI 5600 series Manufacturing execution systems (MES)

8.4 Consortium specifications

Abbreviation/acronym Meaning

DKE Deutsche Kommission Elektrotechnik Elektronik Informationstechnik

im DIN und VDE (German Commission for Electrical, Electronic & Information Technologies of DIN and VDE)

EDDL Electronic Device Description Language

EN European standard

ERP Enterprise Resource Planning

ETSI European Telecommunications Standards Institute

EU European Union

FB Fachbereich (Division)

FDI Field Data Integration

Designation of the IEC 62719 series of standards

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

INS Innovation with Norms and Standards (a project sponsored by the

German Ministry of Economic Affairs and Technology)

IPA Fraunhofer-Institut für Produktionstechnik und Automatisierung (Fraun-hofer Institute for Manufacturing Engineering and Automation)

ISA International Sociological Association

Abbreviation/acronym Meaning

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

SPC Stored Program Controller

TC Technical Committee

TL Technologien und Lösungen (Technologies and Solutions)

TR Technical Report

TS Technical Specification

UA Unified Architecture

10 WORKING GROUP “STANDARDIZATION CONCEPT

FOR INDUSTRIE 4.0” IN DIVISION 9 OF THE DKE

Volker Bautz, BGHM, Mainz

Dr. Heinz Bedenbender, VDI, Düsseldorf Prof. Dr. Christian Diedrich, IFAK, Magdeburg Udo Döbrich, Siemens, Karlsruhe

Prof. Dr. Ulrich Epple, RWTH Aachen, Aachen Heiko Frank, Wittenstein, Igersheim

Dieter Gödicke, VDMA, Frankfurt am Main Roland Heidel, Siemens, Karlsruhe Klaus Hemberger, BNetzA, Mainz

Dr. Günter Hörcher, Fraunhofer IPA, Stuttgart Haimo Huhle, ZVEI, Frankfurt am Main

Dr. Christian Kellermann, ZVEI, Frankfurt am Main Eckehardt Klemm, Phoenix Contact, Bad Pyrmont Prof. Peter Bernard Ladkin, Universität Bielefeld, Bielefeld Klaus-Peter Lindner, Endress+Hauser, Reinach

Dr. Wolfgang Mahnke, ABB, Mannheim

Dr. Stephan Middelkamp, HARTING, Espelkamp Reinhold Pichler, DKE, Frankfurt am Main

Dr. Thorsten Pötter, Bayer Technology Services, Leverkusen Dr. Lutz Rauchhaupt, ifak, Magdeburg

Ingo Rolle, DKE, Frankfurt am Main Martin Schwibach, BASF, Ludwigshafen Dr. Gerhard Steiger, VDMA, Frankfurt am Main Johannes Stein, DKE, Frankfurt am Main Ingo Weber, Siemens, Karlsruhe Ludwig Winkel, Siemens, Karlsruhe

VDE ASSOCIATION FOR ELECTRICAL, ELECTRONIC & INFORMATION TECHNOLOGIES DKE German Commission for Electrical,

Electronic & Information Technologies of DIN and VDE Stresemannallee 15 D-60596 Frankfurt Phone: +49 69 6308-0 Fax: +49 69 6308-9863 Email: [email protected] Internet: www.dke.de