Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
+49 69 6308-9863
Email: standardisierung@vde.com
Internet: www.dke.de
Issue date: 04.2013
STANDARDIZATION ROADMAP
6.1
6.2
6.3
6.4
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
6.5
6.6
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
6.7
6.8
6.9
Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
8
Relevant
8.1
8.2
8.3 VDI/VDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
8.4
Consortium specifications .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54
9
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
53
10
58
Image directory
Figure 1 Communication between CPSs (Source: Fraunhofer IAO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 2 The four life cycles in industrial manufacturing (Source: ARC, with additions by Fraunhofer IPA) . . . . . . . . . . . . 10
Figure 3 Innovation from standardization
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STANDARDIZATION ROADMAP
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
15
2 INTRODUCTION
STANDARDIZATION ROADMAP
Figure 1 Communication
between CPSs (Source:
Fraunhofer IAO)
Customer order:
50 gearboxes by Monday
Sorry, I cant
work on Saturday.
Magazine
empty.
Please fill it!
Booked up to capacity
until Friday!
Switch me off!
I can work this
Saturday.
Ive got to be in
the shipping area
in 2 hours!
STANDARDIZATION ROADMAP
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 harmonized 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 organized.
10
STANDARDIZATION ROADMAP
Industrial
support
Figure 3
Innovation from standardization
Methodology
Practical
relevance
Market
Innovation
Research
Functionality
Stability
Security of
investment
Standardization
A prompt firming-up of concepts by a standardization process based on consensus and accompanying research is also essential for rapid implementation in industrial practice.
12
STANDARDIZATION ROADMAP
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 parallel 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 Agreement8.
Environment
(e.g. laws)
National
adoption
DIN , DKE
Technological
development
European
adoption
CEN, CENELEC
ETSI
International
standardization
IEC , ISO, ITU
(DKE, DIN)
Technological
development
Research,
strategic
projects
Consortium
standardization
(Consortiums)
Need for
standardization
Consensus-based
standardization
(Associations)
DIN
standards
EN
standards
ISO , IEC
standards
Development of
products and services
Application in practice
Consortium
standard
National
standard
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 increasingly meeting its limits. In many cases, the time available to the voluntary members of the committees 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.
14
STANDARDIZATION ROADMAP
VDI/VDE guidelines
(GMA)
NAMUR recommendations
(NAMUR)
(VDMA)
Technical reports
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 forward for international standardization.
DIN:
DKE:
German Comission for Electrical, Electronic and Information Technologies of DIN and VDE
BITKOM: Federal Association for Information Technology, Telecommunications and New Media
ZVEI:
16
STANDARDIZATION ROADMAP
18
STANDARDIZATION ROADMAP
JTC 1/WG 7
Sensor networks
JTC 1/SWG 5
JTC 1/WG 8
Governance of IT
JTC 1/SC 2
JTC 1/SC 6
JTC 1/SC 7
JTC 1/SC 17
JTC 1/SC 22
software interfaces
JTC 1/SC 23
JTC 1/SC 24
data representation
JTC 1/ SC 25
JTC 1/ SC 27
IT security techniques
JTC 1/ SC 28
Office equipment
JTC 1/ SC 29
JTC 1/ SC 31
JTC 1/ SC 32
JTC 1/ SC 34
JTC 1/ SC 35
User interfaces
JTC 1/ SC 36
JTC 1/ SC 37
Biometrics
JTC 1/ SC 38
JTC 1/ SC 39
20
STANDARDIZATION ROADMAP
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 nonfunctional properties.
22
STANDARDIZATION ROADMAP
Control
Signalling
Alarms
Archiving
Monitoring
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.
Diagnosis
Maintenance
System migration
Optimization
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. Accompanying 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. 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.
24
STANDARDIZATION ROADMAP
Characteristics
Element libraries
Services 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.
Communications platform
Service systems
Workflow systems
Programming languages
On fundamental aspect of standardization is the stipulation of the actual mapping of the individual concepts to the available technologies. This is the basis of products and industrial 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 ...).
26
STANDARDIZATION ROADMAP
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 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.
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 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.
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 example, 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.
28
STANDARDIZATION ROADMAP
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.
30
STANDARDIZATION ROADMAP
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 representative use cases be compiled, in which typical tasks and scenarios in the Industrie 4.0 environment 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 nonfunctional 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 developed for each non-functional property.
32
STANDARDIZATION ROADMAP
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 description 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.
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 terminology 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 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.
34
STANDARDIZATION ROADMAP
Recommendation NE-5:
Information security
Protection of information as a valuable asset from loss and misuse, ensurance of its timely provision 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 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 BSI 18, and national and international standardization organizations (e.g. ISO/IEC 19, 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 automotive, 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 properties of individual components, but must rather define a functionality docked onto the system
as a whole.
36
STANDARDIZATION ROADMAP
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 exchange 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 Telecommunications 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 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 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 300328 23
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 administrations from 48 countries. The cooperation between CEPT/ECC and ETSI, and that with the
23 See EN 300328, Electromagnetic compatibility and Radio spectrum Matters (ERM)- Wideband transmission
systems- Data transmission equipment operating in the 2,4GHzISM band and using wide band modulation
techniques; series of standards
24 See EN 300440, Electromagnetic compatibility and Radio spectrum Matters (ERM)- Short range devices- Radio equipment to be used in the 1GHz to 40GHz frequency range; series of standards
38
STANDARDIZATION ROADMAP
6.7
40
STANDARDIZATION ROADMAP
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-development with the IT functions, verification of the software developed, model-driven development,
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.
42
STANDARDIZATION ROADMAP
7 LINKS
[1]
[2]
IAO The Potential of Human-Machine Interaction for the Efficient and Networked Production 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
44
STANDARDIZATION ROADMAP
[4]
[5]
[6]
[7]
[8]
Title
ISO 8373:2012
ISO 9283:1998
ISO 9409:2004
ISO 9787:2013
ISO 9946:1999
ISO 10218:2011
ISO 11593:1996
ISO/TR 13309:1995
ISO/FDIS 13482
ISO 14539:2000
ISO/AWI 18646-1
46
STANDARDIZATION ROADMAP
Title
ISO 9506-1:2003
ISO/TR 10314:1990
ISO/TR 11065:1992
ISO 11354:2011
Advanced automation technologies and their applications Requirements for establishing manufacturing enterprise process interoperability
ISO 13281:1997
Industrial automation systems Manufacturing Automation Programming Environment (MAPLE) Functional architecture
ISO/TR 13283:1998
Industrial automation Time-critical communications architectures User requirements and network management for time-critical
communications systems
ISO 14258:1998
ISO 15704:2000
ISO 15745:2003
Industrial automation systems and integration Open systems application integration framework
ISO/CD 15746
Automation systems and integration Integration of advanced process control and optimization for manufacturing systems
ISO 16100:2009
Industrial automation systems and integration Manufacturing software capability profiling for interoperability
ISO/TR 18161
ISO 18435:2009
Industrial automation systems and integration Diagnostics, capability assessment and maintenance applications integration
48
STANDARDIZATION ROADMAP
Title
Architecture
IEC 62264:2013
Communication
IEC 61158
IEC 61784
IEC 62026
ISO/IEC 14543-3
IEC 62591
Industrial communication networks Wireless communication network and communication profiles WirelessHARTTM
IEC 62601
OPC UA
Security
IEC 62443
50
STANDARDIZATION ROADMAP
Security in Automation
8.3 VDI/VDE
Standard
Title
VDI/VDE 2651
VDI/VDE 2657
VDI 2884
VDI 2885
VDI 3385
GDX interface Consistent data format from development to production (working title)
VDI 4464
Digital factory
52
STANDARDIZATION ROADMAP
Abbreviation/acronym Meaning
DKE
EDDL
EN
European standard
ERP
ETSI
EU
European Union
FB
Fachbereich (Division)
FDI
FDT
GL
Grundlagen (Fundamentals)
GMA
ICT
IEC
IEEE
IEV
INS
IPA
Fraunhofer-Institut fr Produktionstechnik und Automatisierung (Fraunhofer Institute for Manufacturing Engineering and Automation)
ISA
54
STANDARDIZATION ROADMAP
Abbreviation/acronym Meaning
56
STANDARDIZATION ROADMAP
PDM
PLM
QMS/CRM
RB
RE
Engineering
RL
RM
Reference models
RT
SA
System Architecture
SB
SCM
SDR/CR
SMB
SOA
Service-oriented Architecture
SPC
TC
Technical Committee
TL
TR
Technical Report
TS
Technical Specification
UA
Unified Architecture
UC
Use Cases
58
STANDARDIZATION ROADMAP