FOR DIGITIZING STANDARDIZATION AND STANDARDS - WHITEPAPER - DKE
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
WHITEPAPER SCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
AUTHORS/CONTACTS
Introduction
Damian A. Czarny, DKE of DIN and VDE
Johannes Diemer, Diemer Consulting 4.0 UG
Dr.-Ing. Mario Schacht, DIN e.V.
Scenario Level 2
Dr.-Ing. Gilles Bülow,DKE of DIN and VDE
Michael Noll, Open Grid Europe GmbH
Scenario Level 3
Dietmar Lochner, Schaeffler Technologies AG & Co. KG
Dr.-Ing. Mario Schacht, DIN e.V.
Scenario Level 4
Damian A. Czarny, DKE of DIN and VDE
Dr.-Ing. Jens Gayko, SCI 4.0
Jui Nahid Pervin, SCI 4.0
Peter Rauh, DIN e.V.
Scenario Level 5
Prof. Dr.-Ing. Christian Diedrich, Otto von Guericke University of Magdeburg
Johannes Diemer, Diemer Consulting 4.0 UG
Outlook and conclusions
Johannes Diemer, Diemer Consulting 4.0 UG
This Document is a translation of the German original version.
The German version is nationally aligned within the IDiS community.
PUBLISHED BY
DIN e. V. DKE Deutsche Kommission Elektrotechnik
Elektronik Informationstechnik in DIN und VDE
Burggrafenstraße 6 Stresemannallee 15
10787 Berlin 60596 Frankfurt am Main
Germany Germany
Phone: +49 30 2601-0 Phone: +49 69 6308-0
Email: presse@din.de Fax: +49 69 08-9863
Email: standardisierung@vde.com
Photo credit cover picture: Rymden / stock.adobe.com
June 2021
CONTENTS
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1 Basis for the scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.1 Utility model SMART Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 Extending the utility model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3 Scenarios as substantiation of the utility model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 Scenario level 2 – machine-readable standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 Content creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Content management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Content delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.4 Content usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3 Scenario level 3 – machine-readable and -executable content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1 Content creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2 Content management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3 Content delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.4 Content usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4 Scenario level 4 – machine-interpretable content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1 Content creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2 Content management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3 Content delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4 Content usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5 Scenario level 5 – self-executing and optimizing content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.1 Content creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.2 Content management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.3 Content delivery und usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6 Conclusion and outlook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Annex A Distinctive features of the scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I
Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . III
FIGURES
Fig. 1 – Phases in the value creation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Fig. 2 – The extended utility model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Fig. 3 – Phases in the value creation process: from content creation to content usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Fig. 4 – Level 3 processes and main questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Fig. 5 – Integrated value adding process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Fig. 6 – Moving towards information-centered content management (level 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Fig. 7 – Consolidate knowledge of AGI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Fig. 8 – Positioning activities of existing and future solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Fig. 9 – Positioning of the IDiS working groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
WHITEPAPER - 3
Left:
Michael Teigeler
DKE Managing Director
PREFACE
Right:
Christoph Winterhalter
Chairman of the
Executive Board, DIN
Dear Readers,
The standards of tomorrow will be digital, and there are good At this point we would like to express our gratitude to all
reasons for this: they must continue to provide all relevant authors and other contributors from industry, research and
information in a way that is appropriate for the application. the associations for their great commitment in supporting the
As applications are being increasingly digitized, standards digital standards Initiative (IDiS) with great motivation and
must follow suit. Welcome to digital Standards! Welcome to well-substantiated contributions.
IDiS: the digital Standards Initiative.
We hope all readers enjoy reading the Whitepaper and ask for
Current standardization and standard application will have your active support in the further elaboration of the digital
to go through comprehensive further development and standards of tomorrow.
digital transformation in order to become digital standards.
This new approach offers the potential of further significant
increases in the sum of 17 billion Euro currently saved every
year by standards in Germany.
With this Whitepaper, Germany is the first country to present
a description of the possible changes for standardization and
standard application in the next ten years. The conceivable Michael Teigeler Christoph Winterhalter
scenarios were elaborated in IDiS, giving explicit consid- DKE Managing Director Chairman of the
eration to the different perspectives of the value creation Executive Board, DIN
process involved in standardization. IDiS thus makes an im-
portant contribution to German, European and international
development of standardization in a digital world.
4 - WHITEPAPER
INTRODUCTION
INTRODUCTION
Digital Standard1 comprises all relevant information
for a standardization task and provides this in a met-
hod and scope that is suitable for specific applications.
Digital Standards can be initiated, created, processed,
implemented and adapted by both humans and machi-
nes.
“
That is the vision of IDiS (Digital Standards Initiative /IDiS-21/) The description of possible scenarios for Digital Standards is a
for the future of standards and specifications. But exactly first step towards establishing a common understanding. The
what does it mean? What will Digital Standards look like and White Paper thus provides a basis for discussing the digital
how can they be used? How will they differ from traditional future and transformation of standardization and standards
document-based standards, and how will this influence the begun on a national level by the IDiS in 2019 and which will
standardization processes? What will be done automatically, continue in future. Section 6 gives an overview of the planned
what influence does artificial intelligence have, what influ- further activities.
ence do people have? This Whitepaper takes four scenario
descriptions for a closer look at the possible answers to
these questions. The scenarios also include the two extreme
positions: „Nothing‘s really changed“ and „General artificial
intelligence has replaced the human expert knowledge“. The
scenarios depict the varying status in terms of the maturity
and readability of standards and the degree to which they
can be implemented and interpreted, looking at possible
automatic compilation by machines. They thus describe the
related different autonomy attributes in the compilation and
use of standards and specifications (utility levels 2 to 5, see
1.1). Theoretically, all described scenarios or corresponding
manifestations are possible in 10 years. The scenarios that
actually occur will depend essentially on the possible step-
by-step developments to the next maturity level in each case.
1 In the German version of this document the term“Digitale Norm”has been introduced. The direct translation of this expression would be“digital
norm”.Since the term“norm”is not very common in English language we use the term“Digital Standard”instead. Currently no approved defi-
nition for the term“digital standard”exists so that the provided definition describes the common understanding within the IDiS community. It
is not intended to replace the internationally known term“SMART Standard”which is also already used in the literature and the standardization
community.“SMART”stands for:“Standard whose contents are applicable and readable for machines, software or other automated systems, and
furthermore can be provided digitally in an application/user-specific manner (transferable)”/SCM-20/. Nevertheless, the Digital Standard and
the“SMART Standard”can be regarded as synonymous. There are still discussions within the international standardization community about the
appropriate term.
WHITEPAPER - 5
SCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
1 BASIS FOR THE SCENARIOS
Content Creation Content Management Content Delivery Content Usage
standardization hosting repository Content-as-a-Service Use of standards content
Fig. 1: Phases in the value creation process
The scenarios describe various levels for Digital Standards.
Level 0: Paper format. Not suitable for direct automatic
The descriptions are based on the workflow currently used
processing or usage.
by known standardization organizations such as DIN and
DKE, which can be broken down into the four essential value
Level 1: Digital document. Automatic management
creation process phases Content Creation, Management,
and display of the document is possible
Delivery and Usage /SCM-20/ (see Fig. 1). However, Digital
(WORD, PDF).
Standards as defined by the IDiS present new challenges
for both standardization organizations and standards users.
Level 2: Machine-readable document. The structure
There will have to be fundamental changes within the indi-
of the document can be digitized and certain
vidual process phases, to the stakeholders in each specific
granular content4 can be exported (chapters,
process, the respective objectives and the workflow itself for
graphics, definitions etc.). Content and presen-
the vision of Digital Standards to become reality.
tation are separated.
Level 3: Machine-readable content. All essential granu-
1.1 Utility model SMART Standards lar information units can be clearly identified,
their reciprocal relationships recorded and
The actual manifestation of Digital Standards has a direct made available for further processing or partial
impact on how fundamental and comprehensive the changes implementation.
will be. The step model or classification and utility model
used by the IEC2 to describe the analyzability of digital Level 4: Machine-interpretable content. The infor-
standards can be taken as an initial starting point /CZS-19/. mation in a standard is linked with implementa-
The model describes characteristics of Digital Standards, tion and usage information in such a way
assigning them to different levels that define the digitization that it is implemented by machines directly
degree3 of a standard. The model distinguishes between or interpreted and combined with other infor-
the following five levels: mation sources so that complex actions and
decision-making processes take place automat-
ically.
2 This model was drawn up in the IEC SG12 and is currently going through further development in the various ISO and IEC working groups.
3 The digitization degree of Digital Standards is called maturity, or also automation degree or autonomy level, in accordance with /PLT-20-2/.
4 Granularity as per /ISO-05/ means“the boundary where an object functions as a self-contained, stand-alone unit to support a common vision
or goal”.Accordingly, granular information refers to the smallest information units of a standard that fulfill a purpose. Fragment is meanwhile
also being used for granularity.
6 - WHITEPAPER
SCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
Level 5
Level 4 Machine-
controllable
content
Machine-
The content of a
interpretable standard is be amended
content automatically and
Level 3 adopted by automated
Information models decision-making
describing and explaining processes.
the content and Digital standards
Machine- the relationships between are based on a system
readable and items of information of artificial general
Level 2 -executable Self-learning analysis intelligence with
cognitive capabilities.
content together with
automatic validation Digital standards
Content completely and optimization adapt constantly
Machine- (semantically) discovered to the current state
Level 1 Value-adding services
readable Semantic search possible e.g. of the art of technical
and regulatory
document and selective access conformity check,
framework conditions.
on content level question answering,
Structured predictive content supply
Digital document format
Earmarked
document information Fully integrated
Software processing with delivery across digital value chain
Digital representation high manual workload several documents is possible
Fig. 2: The extended utility model
As shown in Fig. 2. the levels are connected with certain Level 5: Machine-controllable content. The content of a
developments so that the corresponding level target can be standard can be amended by machines working
achieved. Furthermore, the individual levels can be seen as unassisted, and adopted by automated (distrib-
development steps that build on each other. Each level builds uted) decision-making processes. The content
on what was achieved in the previous level, thus forging adopted in this way is automatically reviewed
ahead with digitization. The model makes it possible to take and published via the publication channels of the
stock of the current status with regard to machine inter- standardization organizations.
pretability respectively digitization of standardization and
standards
Level 5 is a consistent continuation of the growing influence
of AI in the previous levels that extends selectively across the
1.2 Extending the utility model individual process phases and develops in level 5 into cohe-
sive artificial general intelligence (AGI)5 /GOE-07/. Artificial
In order to describe a visionary target scenario, an addition- general intelligence has cognitive capabilities and is capable
al level is defined that comes above level 4 in the IEC utility of making cross-process and cross-phase optimizations and
model (see Fig. 2): decisions. The content of Digital Standards can thus be com-
5 Artificial general intelligence describes a software program capable of solving many complex problems in many different areas that controls itself
automatically, with its own thoughts, concerns, emotions, strengths, weaknesses and inclinations /GOE-07/.
WHITEPAPER - 7SCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
piled and amended automatically or triggered by machines, The following descriptions of the scenarios for levels 2 to 5
achieving a further level of maturity: in addition to machine aim to close this gap. There is no need to consider a scenar-
interpretability, this also allows machine control of the stan- io for level 1, as the corresponding value creation process
dardization process based on machine knowledge, possibly already corresponds to present-day practice (see Fig. 9 in
even without human intervention. section 6). Each scenario describes a possible future picture
of standardization and standards by presuming that the
The standardization process in level 4 is characterized by the corresponding target level is fulfilled within a period of 10
fact that information and knowledge from the delivery and years. Each scenario describes the level of achievement in
usage phases flow into the content creation phase in the the context of the current value adding process phases of the
sense of an overarching life cycle. Furthermore, the content standardization organizations (creation, management, deliv-
is amended and renewed all the time. The process therefore ery and usage). The table in Annex A summarizes the essen-
takes place in continuously repeating cycles and not in a suc- tial distinctive features of the individual scenarios, comparing
cessive time sequence. Every digital standard is thus capable them in condensed form.
of adapting constantly (and intrinsically) to the new knowl-
edge. This process is also automated in level 5.
1.3 Scenarios as substantiation
of the utility model
The utility model describes the main distinctive features
between the levels for assessing the degree to which Digital
Standards can be evaluated and automated. Examples are
provided of what seems possible on which level and which
aspects may be involved. However, the main changes within
a level are not given a cohesive description and put in se-
quence (in the sense of a road map). This makes it harder to
estimate the consequences or necessary realization activities
for each level.
8 - WHITEPAPERSCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
2 SCENARIO LEVEL 2 – MACHINE-READABLE STANDARDS
In 10 years, there has been no essential change in standardization.
Comprehensive electronic delivery of national/European/ implemented to shorten the process with the aim of reducing
international standards is still mainly carried out using PDF- the processing times to less than 12 months for most consen-
based standards management processes organized by means sus-based standards. Content reviews usually take place after
of meta data /SCM-12/. 5 years, initiated by system-assisted deadline tracking on the
part of the standards body. as in the past, every standard-
In technological terms and seen from the user’s point of ization request (new/change) needs an individual initiative
view, the situation is in a mature, reliable status, given that “new
( work item proposal”).
this refers to very broad-based information provision in terms
of the number of verified regulations and indexing depth. Adopting the finished standard as a consensus document
still produces top quality results (human benchmarks of the
The workflow that has been in place for decades (see Fig. 3) experts involved) while also avoiding high complexity (for
works successfully and is well-balanced due to conventions example by not considering manufacturer-specific aspects).
agreed between the various process partners involved. The basic Diversity and substantiation can be described in the form of
principles have been carefully coordinated in compliance with supplementary standards or accompanying documents, for
standardization and legislation, and guarantee reliable man- example as a consortium standard, a SPEC or a guideline.
agement of the standardization results in customer-oriented
systems. Amendments to the standardization system are made The standard document itself has an XML document struc-
conscientiously and with the consensus of all stakeholders, tak- ture that makes it machine-readable. The structure is based
ing due account of the rules valid in each case /DIN-20, ISO-04, on separating content and presentation, making it possible
ISO-18/. to identify and research typical document elements such
as chapters, graphics, definitions and bibliography entries,
but not meaningful elements. Standard creation is thus still
2.1 Content creation primarily geared to developing standards that can be read
by machines and interpreted by people. New (collaborative)
The consultation process (in virtual or physical sessions) can tools for creating standards have been successfully estab-
still take several years in some cases. Measures have been lished.
Fig. 3: Phases in the value creation process: from content creation to content usage
DIN EN 12345-6
ICS 12.4356.30.89
Index
orem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula
eget dolor. Aenean massa.
Cum sociis natoque penatibus
et magnis dis parturient
montes, nascetur ridiculus mus. Donec quam
felis, ultricies nec, pellentesque eu, pretium quis, sem.
Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec,
vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo.
Nullam dictum felis eu pede mollis pretium. Integer tincidunt.
Cras dapibus. Vivamus elementum semper nisi. Aenean vulputate eleifend tellus.
Aenean leo ligula, porttitor eu, consequat vitae, eleifend ac, enim.
Aliquam lorem ante, dapibus in, viverra quis, feugiat a, tellus.
Phasellus viverra nulla ut metus varius laoreet. Quisque rutrum.
Aenean imperdiet. Etiam ultricies nisi vel augue.
DIN EN 12345-6 DIN EN 12345-6
ICS 12.4356.30.89
ICS 12.4356.30.89 DIN EN 12345-6
DKE Deutsche Kommission Elektrotechnik Elektronik Informationstechnik im DIN und VDE
DIN EN 12345-6 orem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula
orem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa.
eget dolor. Aenean massa.
Cum sociis natoque penatibus ICS 12.4356.30.89 Cum sociis natoque penatibus
et magnis dis parturient
et magnis dis parturient
montes, EN
DIN 12345-6 montes, nascetur ridiculus mus. Donec quam
nascetur ridiculus mus. Donec quam
felis, ultricies nec, pellentesque eu, pretium quis, sem.
felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec,
Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo.
ICS
vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis 12.4356.30.89
vitae, justo.
orem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula
eget dolor. Aenean massa. Nullam dictum felis eu pede mollis pretium. Integer tincidunt.
Nullam dictum felis eu pede mollis pretium. Integer tincidunt. Cum sociis natoque penatibus Cras dapibus. Vivamus elementum semper nisi. Aenean vulputate eleifend tellus.
Cras dapibus. Vivamus elementum semper nisi. Aenean vulputate eleifend tellus. et magnis dis parturient Aenean leo ligula, porttitor eu, consequat vitae, eleifend ac, enim.
ICS 12.4356.30.89 Aenean leo ligula, porttitor eu, consequat vitae, eleifend ac, enim. montes, nascetur ridiculus mus. Donec quam Aliquam lorem ante, dapibus in, viverra quis, feugiat a, tellus.
Aliquam lorem ante, dapibus in, viverra quis, feugiat a, tellus. Phasellus viverra nulla ut metus varius laoreet. Quisque rutrum.
Phasellus viverra nulla ut metus varius laoreet. Quisque rutrum. felis, ultricies nec, pellentesque eu, pretium
orem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligulaquis, sem. Aenean imperdiet. Etiam ultricies nisi vel augue.
Aenean imperdiet. Etiam ultricies nisi vel augue. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec,
eget dolor. Aenean massa.
Cum sociis natoque penatibus vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo.
et magnis dis parturient
montes, nascetur ridiculus mus. Donec quam
Nullam dictum felis eu pede mollis pretium. Integer tincidunt.
orem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula
eget dolor. Aenean massa. felis, ultricies nec, pellentesque eu,Cras dapibus.
pretium quis, Vivamus
sem. elementum semper nisi. Aenean vulputate eleifend tellus.
Nulla consequat massa quis enim. DonecAeneanpedeleo ligula, porttitorvel,
justo, fringilla eu,aliquet
consequatnec,vitae, eleifend ac, enim.
Cum sociis natoque penatibus
Aliquam ut,
vulputate eget, arcu. In enim justo, rhoncus lorem ante, dapibus
imperdiet in, viverra
a, venenatis vitae,quis,
justo.feugiat a, tellus.
et magnis dis parturient
Phasellus viverra nulla ut metus varius laoreet. Quisque rutrum.
montes, nascetur ridiculus mus. Donec quam
Aenean imperdiet. Etiam ultricies nisi vel augue.
felis, ultricies nec, pellentesque eu, pretium quis, sem. Nullam dictum felis eu pede mollis pretium. Integer tincidunt.
Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, Cras dapibus. Vivamus elementum semper nisi. Aenean vulputate eleifend tellus.
deliver document-
vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo. Aenean leo ligula, porttitor eu, consequat vitae, eleifend ac, enim.
Aliquam lorem ante, dapibus in, viverra quis, feugiat a, tellus.
Phasellus viverra nulla ut metus varius laoreet. Quisque rutrum. DKE Deutsche Kommission Elektrotechnik Elektronik Informationstechnik im DIN und VDE
DKE Deutsche Kommission Elektrotechnik Elektronik Informationstechnik im DIN und VDE
Nullam dictum felis eu pede mollis pretium. Integer tincidunt. Aenean imperdiet. Etiam ultricies nisi vel augue.
Cras dapibus. Vivamus elementum semper nisi. Aenean vulputate eleifend tellus.
Aenean leo ligula, porttitor eu, consequat vitae, eleifend ac, enim.
provide
Aliquam lorem ante, dapibus in, viverra quis, feugiat a, tellus.
Phasellus viverra nulla ut metus varius laoreet. Quisque rutrum.
Aenean imperdiet. Etiam ultricies nisi vel augue.
provide
DKE Deutsche Kommission Elektrotechnik Elektronik Informationstechnik im DIN und VDE
DKE Deutsche Kommission Elektrotechnik Elektronik Informationstechnik im DIN und VDE
centric standards
DKE Deutsche Kommission Elektrotechnik Elektronik Informationstechnik im DIN und VDE
Experts DIN Software / DKE Beuth Verlag / VDE Verlag
Content Creation Content Management Content Delivery Content Usage
WHITEPAPER - 9SCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
The following prerequisites are fulfilled for using the new 2.3 Content delivery
tools:
Standards are available as one-off sales or subscriptions in
→ The standard structure as (XML) document is extensively printed or digital form (PDF, XML or as HTML fragments in
harmonized. standards websites). All output formats are produced directly
→ Complete templates for standards exist and are used by or indirectly from the content management systems (single
the major standardization organizations. source publishing).
→ Standardization organizations can share and combine
standards when the need arises, as facilitated for exam- By using meta data and additional information, standards
ple by the NISO-STS shell model /NISO-17/. websites and standards management systems can be up-
→ Creation tools are offered as a service. graded with Digital Standards to allow for detailed searches
for standards (e.g. according to various facets) or language/
version comparisons.
2.2 Content management
Beside the“traditional”standards websites, possibilities are
The standard publisher is responsible for content man- being created for alternative access to standards with CaaS
agement. The content management systems used by the (Content-as-a-Service) interfaces /GZL-20/.
standardization institutions are mainly proprietary solutions.
Data and meta information are shared in the form of XML-
based document formats, although there is no warranty that 2.4 Content usage
all relevant information will be shared throughout the entire
process. Standards are still read, understood, reviewed, selected and
implemented by people on the basis of the standards made
Standards are created and managed in editor systems. Editor available by content delivery and the supporting help func-
systems are supported by interfaces to other tools used in tions (search, favourites lists, document comparisons etc.).
standard production, e.g. translation management systems
or tools for creating factory standards. There is no integrating Digital access makes it significantly easier to handle and pro-
system that can be used by all processes and stakeholders cess standards. Standards management systems help with
involved in standard production. Depending on the process (internal) licensing, administration and distribution of the
step, there is a possibility of media disruption which demands documents. Standards websites offer various research and
manual data input in other tools to warrant data consistency. convenience functions that make it easier to understand and
work with standards.
The meta data describing the standard or standardization
projects are kept in databases or ideally in the content
management system for standards management and made
available for various usage purposes (most of which are not
integrated).
10 - WHITEPAPERSCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
3 SCENARIO LEVEL 3 – MACHINE-READABLE
AND -EXECUTABLE CONTENT
In 10 years, some of the processes involved in standardization have changed
The process for level 3, like level 1 and 2, is characterized use in editor systems or other usage environments. Further-
by distinct areas of responsibility. Although this simplifies more, digital objects defined in the standard (e.g. tables, for-
the implementation of solutions in terms of organization, it mulae, graphics) are stipulated for direct usage in customer
prevents the integrated overarching approach that will be systems. The requirement for semantic granularity of stan-
vitally necessary for the Digital Standard in level 4. Focusing dards down to the smallest meaningful information elements
on IT-assisted processes and their further development in and their marking is one of the core tasks characteristic of
content management and content delivery makes it possible level 3. In level 3, this refers initially to standardized facts that
to swiftly achieve specific machine-readable solutions. Fig. 4 are required and necessary in the content usage phase of the
shows the main questions to be answered, with explanations value adding process.
provided below.
Rules for describing granular information in standards
together with systematic stipulation of the usage context
3.1 Content creation (e.g. standardization function, sites of action, see /LMN-19,
SCM-20/) are available for technology-based usage with
A document is created with a data structure according to the considerable improvements in the usage quality of IT-assist-
current creation framework conditions for standardization, ed application processes. Stipulations of a corresponding
but with the whole content delivered in XML, e.g. for further information model are established and standardized on an
Fig. 4: Level 3 processes and main questions
Content Creation Content Management Content Delivery Content Usage
CMS /
XSCoRe
provide provide deliver content-
centric standards
Experts DIN Software / DKE Beuth Verlag / VDE Verlag
standardization tagging XML/metadata repository Content-as-a-Service Use of standards content
Which additional How is granular information
tagging expands processed and delivered?
content access?
What are the rules
Which granular information
for structuring and How is granular is needed
marking individual contents? information managed? in the customer process?
WHITEPAPER - 11SCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
international scale /WHR-19, CZO-20, RUH-20/, together with → Further development of digital search and delivery plat-
corresponding ontology for standards documents and highly forms based on semantic (additional) information which
granular information elements.6 e.g. can describe the relationships between granular
content, which in turn can be included in a relevance
Examples of highly granular information elements and their appraisal.
usage are as follows: → Provision and further development of interfaces to assist
the content management processes in the XML work-
→ Stipulations (requirements, recommendations, etc.) can flows.
be clearly identified in the XML structure and exported to
the standard user’s requirement management systems. The“Semantic Standards Information Framework (SNIF)”
Definitions in the standards content are marked with TBX is used for semantic indexing of standards /SCW-14/. In
(TermBase eXchange)-compatible tags for cross-platform level 3, this semantic indexing closes the gap that emerges
terminology management with rough cross-linking of the when there is no 100% semantic indexing of the content of a
content. standard. SNIF links the intellectually elaborated meta data
→ Formulae are described by data formats such as Math- with the semantic indexed standards texts to provide better
Lab, MathML, etc. and made available to the user in a quality information to systems involved in further processing.
machine-executable form.
→ Images are embedded unchanged as raster graphics and
exported with connected information (caption, legend, 3.3 Content delivery
etc.)
New digital solutions for standards usage based on XML
technology have emerged or been developed /GZL-20/. The
3.2 Content management solutions made possible by structured, highly granular infor-
mation are mainly developed by solution providers and made
Database processing and export of content takes place in a available for the content usage phase in the value adding
suitable system. All existing German, European and interna- process.
tional standards are available as XML and managed in XML
databases /WHK-16, EKW-17/ with the following attributes: The XML versions of the standards documents permit
specific access to all possible information units within the
→ Central provision and management of meta data and documents, as well as linking these to other information
standards content for digital information and knowledge sources, such as document meta data or further additional
products, also in usage-relevant, partially granular form, information. Suitable digital search and delivery platforms
as corresponding content and purposes are identifiable have uniform access to this information and safeguard shared
and classified (→ content creation requirement). exporting. The semantic enrichment of information allows
→ The management process for granular content considers access to highly granular information and the reciprocal
life-cycle information that can be coupled to the total relationships.
document.
6 In 2020, the NISO Working Group began corresponding work on a Standards Specific Ontology Standard (SSOS) /NISO-19/. On the national level,
the NAGLN (DIN Standards Committee Principles of Standardization) has expanded the rules for standardization work.t.
12 - WHITEPAPERSCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
3.4 Content usage repository for structured standards data acts already in level
3 as the basis for company-specific AI applications, devel-
Standards users are provided with highly granular informa- oped initially for the main part in innovative companies with
tion and semantic enrichment of standards and specifica- high investment potential, possibly in cooperation with the
tions. These can be integrated, although still by hand, in the standards bodies.
company processes and taken into account in the develop-
ment and production process (PEP). Possible applications
include e.g.:
→ Construction: support in product development by linking
product requirements with requirements from standards.
This is possible because the requirements are identified
or marked in the content of a standard. Cross-linking al-
lows for traceability, providing specific information when
there are changes to the granular standards information.
This allows swift assessment of the impacts on the prod-
uct.
→ Automation: existing highly granular standards infor-
mation is used in production processes in the form of a
management shell (Industry 4.0). Standards information
is brought together with the user information (the asset)
in a shared place, which is the management shell, and
processed together.
→ After sales: standards information is available in the
usage context of after sales (e.g. commissioning, mainte-
nance, servicing).
Besides“traditional”ICT-assisted usage methods (e.g. da-
tabase applications, standards management) from solution
providers, a future usage scenario reveals far greater usage
benefit for Digital Standards with the possibility of deriving
rules for formalizing and modelling the content of standards
and specifications for AI-based applications. The resulting
quality improvements in the basic data are indispensable for
optimum functionality of AI systems /WTH-19/. The intended
development by DIN/DKE and other standards bodies of a
WHITEPAPER - 13SCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
4 SCENARIO LEVEL 4 – MACHINE-INTERPRETABLE CONTENT
In 10 years, standardization has changed.
Significant improvements in the information basis will be The increased demand for information results in the introduc-
necessary, in terms of both quantity and quality, for the con- tion of specialized tools and management systems together
tent of standards to be machine-interpretable. The identified with further merging of classical areas of responsibility. On
information units resulting from level 3 are broken down into the IT and process level, this leads to the establishment of a
their semantic components and supplemented with informa- distributed overall system for standardization.
tion about the application context and execution behaviour
(execution semantics). Interpreting, embedding and exe-
cuting the granular content is still up to the standards user 4.1 Content creation
respectively the systems he uses. However, these are able to
transfer for information units relevant for a specific usage to The standardization process must be able to provide the
the user domains and interpret them according to the execu- required granularity of information in each case, which is
tion semantics in its own decision-making and automation necessary for interpretation in the respective application
processes. context. The creation tool used in the process plays a central
role, because not only the content of a standard but also its
Fig. 5 /DKI-20/ shows the direction in which a future work- semantic structure has to be created and then maintained.
flow should develop in 10 years. Crucial importance will be For standards creation conforming with level 4, the document
attributed above all to greater integration of the previously creation tools introduced in levels 2 and 3 (XML Online Au-
mainly autonomous, sequential process phases. The concept thoring Tools /ISO-20/) are supplemented by a large number
of semantic interoperability, as implemented for example in of (plug-in) creation modules. These modules are used for
Industry 4.0, eliminates media disruption and the need for native creation of domain-specific content which is then
data conversion at the transition points in the value adding integrated in the context of the standard. For the creation
process. tool and underlying content management system to create
Fig. 5: Integrated value adding process
DIGITAL STANDARDS
APIs PLM
Future 2030
ERP
CAD
Beuth Verlag / VDE Verlag
Experts and other solution provider deliver solutions
provide provide
standardization Content-as-a-Service
Digital Standards use
Content Repository
14 - WHITEPAPERSCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
User
GUIDES
PROPERTIES
MODELS
(SysML)
DOCUMENTS FIGURES
Broker Broker
Level 2&3 Level 4 TEST
ONTOLOGIES CASES
create &
METADATA transform transform TERMS
search & search & TAGS
codeliver combine
Fig. 6: Moving towards information-centered content management (level 4)
and process the domain-specific elements (often present in 4.2 Content management
varying formats), there is urgent need for a uniform semantic
description of all elements according to an information mod- The level 4 scenario adds the challenge of interpretation to
el (see 3.1) and new standardized rules. the identification and export of information units in level
2 and 3. These are supplemented by additional definition
Compared to level 3, this not only increases the depth of de- aspects and execution descriptions /execution semantics) for
tail (granularity level) and the number of supported formats: continuous interpretation of all information units in the specif-
above all, new semantic concepts are developed and stan- ic application context (see 4.1). This extended information
dardized for format-independent execution and behaviour cannot be (repeatedly) present completely in every standards
description of standards content (execution semantics). Sim- document. To a certain extent, this is still possible in level 3 as
ilar developments can already be seen today in the context of here it refers primarily to simple annotations with relatively
Industry 4.0 /PLT-18, PLT-20-1/. fixed vocabulary, managed in the form of lists or simple struc-
tures. The scope and complexity of the annotations increases
For certain content types, the content life cycle introduced in level, thus making it increasingly necessary to use special-
in level 3 is now decoupled from the actual document with ized database systems or repositories for certain types with
regard to process (content creation) and IT (content manage- corresponding references made in the standards documents.
ment). Information quantity and complexity together with One example of this consists of property repositories such as
the overarching network of relationships require specialized the Common Data Dictionary (CDD) /IEC-17/, which assume
standardization and management of the information units the role played previously by definitions of terms, and also
detached from the actual standards document. offer the possibility of adding further information. These
property definitions are so complex that the standards have
Level 4 sees a dramatic change in the requirements profile for to refer directly to the property definitions (or certain aspects)
standardization experts. A level 4 standardization expert must in the property repositories. Fig. 6 shows the transition from a
write in a way that people can understand, that is formalized central document repository (levels 2 and 3, on the left of the
and modelled appropriately for the machine/domain, while picture) to a number of specialized information repositories
producing a semantic description of the elements according (level 4, on the right of the picture).
to the standardization domain. As a rule, this wide range
of skills cannot be covered by one expert alone, so that the This large number of individual repositories, which may pos-
committees increasingly consist of technical, methodical and sibly be managed by different organizations and in different
system experts. ways, are merged to a uniform overall system. The overall
WHITEPAPER - 15SCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
system, which Tannenbaum also calls“Distributed System” across several standards. Initial export possibilities handle
/TAN-07/, appears to the user to be one single system, despite the data in general formats or directly in common industrial
its distributed sub-systems, thanks to harmonized user man- formats, e.g. ReqIF (Requirements Interchange Format) for
agement (usability, rights, personal data) and information requirements or RDF (Resource Description Framework)
management (data security, licensing, etc.). In addition to for semantic meta data. Level 3 thus permits a kind of raw
system fusion, the main property of the distributed sys- information provision in various formats with initial minor
tem consists in data fusion and quality control. Data fusion convenience functions. It is still up to the individual user to
consists of merging information from individual repositories know which formats or information components are relevant
that use different data structures, on one and the same meta for the specific use case or how these have to be combined
level (see 5.1). This allows for semantic searching, exporting or processed. Level 3 only makes it possible for the user to
and data optimization across repository borders (consistency, obtain this information.
dead references, duplications etc. Optimization increasingly
uses AI-based methods with on-going analysis of the stan- In the level 4 scenario, execution and interpretation infor-
dards stock, also generating recommendations for content mation is added to the provision of raw data. However, the
creation for example, or ascertaining the need for harmoniza- biggest change in this area consists of the growing content-re-
tion in the data stocks and suggesting solutions at the same lated integration of standardization and user information.
time. On the one hand, initial user information (experience, user
descriptions, etc.) is fed back into the content management
In the level 3 scenario, the content management systems systems and linked with normative content. On the other
form the link between content creation and content delivery, hand, the content delivery systems develop an improved
but the systems tend to be rather in the background of the understanding for user-related information, e.g. when search-
individual organizations. In the level 4 scenario, the distribut- ing for relevant normative information or when it comes to
ed system is more in the foreground and partially accessible providing information. Asset or requirement descriptions of
for both authors (content creation, for definitions, searches products can be used directly for searches by analyzing such
and editing) and for standard users (content delivery for data and comparing it with the meta models of the standards
definitions, explanations, comments, etc.). However, for information.
most users, access is primarily indirect from intermediary
applications from other areas, e.g. the tools used for content As far as actual delivery is concerned, the raw data services
creation. Even so, there is an increasing number of direct have developed into use case-related service packages.
users alongside the IT process owners who are responsible For common use cases such as simulations, evaluations or
for instance for normative and overarching data and methods conformity statements, the content delivery systems take the
maintenance. user information to ascertain which combined information
needs to be provided, which formats used, which notification
functions should be adjusted and which user information is
4.3 Content delivery still missing.
Content delivery in level 3 is still basically document-cen- It is still up to the user to proceed with execution or informa-
tered provision of information supplemented by access and tion, but the content delivery system is increasingly respon-
search methods to consider any information units within and sible in the case of common use cases for which information
16 - WHITEPAPERSCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
packages or service settings help the user to obtain and In level 4, internal digitization and automation within a com-
interpret the data. pany is joined increasingly by the need for cross-company
digitization. This mainly happens by making the normative
information part of the larger digitization platforms, rather
4.4 Content usage than giving all standards users access to the same content de-
livery systems with corresponding synchronization. Systems
The introduction of level 3 systems already gave users access such as the management shell of the Industry 4.0 platform
to individual highly granular information from standards for act as a central point for digitizing whole chains of compa-
corresponding integration in their own development and nies by defining and providing the data and mechanisms for
production processes (PEP). In turn, this acted as the driving interoperability between different instances. Standards and
force behind their own internal digitization, for instance by specifications are an integral part of these platforms to offer
automating decision-making processes based on normative standards users the corresponding normative information
information or making normative information an integral part and services at the point where sharing and interaction with
of their own engineering. other companies takes place.
Experience gained in this way was fed back in turn to the use
case oriented provision that was developing in level 4 content
delivery (see 4.3). In this process, the individual and in some
cases special experience of level 3 users was generalized and
mapped for the broadest possible range of appropriate use
cases. This is beneficial not just for new users who profit from
the experience of former users, but also for the level 3 pio-
neers who thus successively simplify or refine their informa-
tion procurement with the sheer general growth in size of the
systems. Content usage users can generally be broken down
into two groups:
→ Use case oriented users who are satisfied with tried-and-
tested procedures and delivery forms.
→ Users needing a highly customized approach who require
specialized, highly granular standards access including
extended control and configurability.
The second group includes, above all, the content solution
providers (see 3.3), who take this data and service basis to de-
velop further solutions and offer them to specialized groups
of standards users.
WHITEPAPER - 17SCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
5 SCENARIO LEVEL 5 – SELF-EXECUTING
AND OPTIMIZING CONTENT
In 10 years, standardization has changed fundamentally.
Development processes in the industrial setting have become description for a new technology, and to decide whether the
highly agile, closely integrating the specification, prototype current Digital Standards can be used or have to be extended,
implementation and validation of compliance with standards, proceeding in the latter case automatically with the process
specifications and directives or, if necessary, their amend- of adaptation.
ment or formulation. Consensus-based standardization pro-
cesses are replaced by automated AI-assisted decision-mak- This automatic knowledge-based decision-making process
ing processes. Standards and specifications are no longer replaces historical consensus-based standardization.
static documents. Instead, as Digital Standards they describe
the optimum current state of the art of technical and regula- Besides automatic review and adaptation of the Digital
tory framework conditions that are necessary for sustainable Standards, it is also possible to proceed with planning and
functionality in a global ecosystem. implementation of the whole systems engineering process.
The human contribution in this scenario then consists of
describing the new product as a SCRUM story line with the re-
5.1 Content creation quired functionalities and characteristics (appearance, shape,
size, material), with allowance being made for incomplete de-
Digital Standards adapt constantly to the new knowledge scriptions. Similarly, when drawing up a new digital standard
acquired from the installed products, production systems it is also possible to proceed with an ecological assessment,
and environmental influences as these change in the course formulating the requirements and required conditions for the
of time. The system of artificial general intelligence behind 7
new standard. Here again, all other Digital Standards are then
the Digital Standards is capable not only of reactive learning: reviewed in terms of compatibility and adjusted accordingly
it also takes a proactive approach in a smart, flexible manner where necessary.
comparable with human cognitive skills. Its characteristics in-
clude among others knowledge-based presentation, commu- Given that basic artificial general intelligence merges various
nication in natural languages, an understanding of syntax and types of knowledge with different learning methods (cog-
semantics, use of strategies as well as handling and assessing nitive synergy), this means that the types and granularity
irregularities. of content creation also differ and can come from various
sources. The creation of new content for Digital Standards is
Furthermore, it has methods for identifying important past triggered by
events and saving these with their context. These events can
then be downloaded as associative knowledge (in the sense → people formulating an idea (e.g. for a product or specifi-
of a remembered memory). These capabilities allow the sys- cation), or
tem to automatically and constantly expand its expert knowl- → AI systems automatically detecting the need for adapta-
edge as the basis for creating a RAMI 4.0-compliant model
8
tion or formulation.
7 One basic characteristic of this AI system consists in the ability to merge the different kinds of limited knowledge (including declarative, procedu-
ral, sensitive knowledge) obtained with different learning methods, like human brains do. This capability is also called cognitive synergy and was
described in software terms for the first time with the project /GOE-14/. Working on the basis of this merged knowledge, the system then reacts
rationally.
8 RAMI – Reference Architecture Model Industry 4.0 /DIN-16/.
18 - WHITEPAPERSCENARIOS FOR DIGITIZING STANDARDIZATION AND STANDARDS
Artificial
Cognitive Synergy
General
All relevant information
Intelligence (AGI) is used and provided
in a continuous learning process
DIGITAL
STANDARD APIs
Tools and Open Standards
IT-Systems DIGITAL
STANDARD Applications DIGITAL
DIGITAL
STANDARD
Standard
STANDARD Online App Store
Repositories Standard Plattform Authoring
Robotics Cyber security Planning & Requirements Product Interoperability
Market exploration Operation…
development analysis development
Production & Control Communication Installation Operation…
implementation
Occupational
Big Data Digital supply chain Monitoring & IoT communication
Metrics Risk management Maintenance … health
controlling
Service & Documentation Hotline On-site service …
support www
Fig. 7: Consolidated knowledge of AGI
The AI systems use both current and historical data and 5.2 Content management
information and are learning all the time. Among others, the
following sources can be used to generate knowledge: The cognitive synergy mentioned above has access to a
distributed network of differing knowledge. This requires con-
→ Data from installed machines and production lines tent management to link the knowledge in a meta represen-
→ Ambient data (room climate, weather, ...) tation, for example as a semantic (neural) network that builds
→ Databases up a semantic memory in the course of time. It contains links
→ Social networks to external knowledge or how to obtain knowledge with
→ Any unstructured data (including documents with texts external methods.
and figures (laws, regulations, ...))
→ Dialogue with experts, with the system using natural At the moment, the actual content is described using a meta
language processing to communicate and debate directly data architecture that distinguishes several abstraction
with the experts (e.g. on the basis of a future version of levels. According to the Meta Object Facility Specification /
the Watson Project Debater /IBM-21/) OMG-16/, the meta data architecture of UML 2.0 for instance
consists of the four levels:
WHITEPAPER - 19You can also read
