Intelligent Information Request and Delivery Standard The - - PowerPoint PPT Presentation

intelligent information request and delivery standard
SMART_READER_LITE
LIVE PREVIEW

Intelligent Information Request and Delivery Standard The - - PowerPoint PPT Presentation

Intelligent Information Request and Delivery Standard The Information 4.0 Working Group presents Presentation at tcworld 2016. Download the German-language original. English translation by Kristen James Eberlein, Eberlein Consulting LLC, 27


slide-1
SLIDE 1

1

www.tekom.de

1

www.tekom.de

Intelligent Information Request and Delivery Standard

The Information 4.0 Working Group presents

Presentation at tcworld 2016. Download the German-language original. English translation by Kristen James Eberlein, Eberlein Consulting LLC, 27 November 2016. kris@eberleinconsulting,com Not reviewed or approved by tekom.

slide-2
SLIDE 2

2

www.tekom.de

2

www.tekom.de

Introduction

  • Dr. Michael Fritz
slide-3
SLIDE 3

3

www.tekom.de

3

www.tekom.de

User expectations

3

User expectations for communication products

  • Context sensitive
  • Individualized
  • Adaptable
  • Multi-channel delivery
  • User experience
slide-4
SLIDE 4

4

www.tekom.de

4

www.tekom.de

Information 4.0 working group

  • Goal: To develop a tekom guideline for a query and delivery

standard for Intelligent Information

  • Kick-off: 07.03.2016
slide-5
SLIDE 5

5

www.tekom.de

5

www.tekom.de

Members of the working group

Industry representatives

  • Machinery and plant engineering
  • Power plant engineering
  • Electronics, electrical engineering
  • Software

Manufacturers of content management systems

  • CCMS
  • Content delivery systems
  • Enterprise Search
  • Semantic Graph Database

Consulting and teaching

  • Universities
  • Service providers
slide-6
SLIDE 6

6

www.tekom.de

6

www.tekom.de

Requirements for iiRDS Semantic modeling as RDFS

Agenda

First version of the metadata Technical scenario and requirements Further steps and open tasks Format description

slide-7
SLIDE 7

7

www.tekom.de

7

www.tekom.de

Requirements for iiRDS Semantic modeling as RDFS

Agenda

First version of the metadata Technical scenario and requirements Further steps and next tasks Format description

slide-8
SLIDE 8

8

www.tekom.de

8

www.tekom.de

Requirements and semantic modeling

Ulrike Parson

slide-9
SLIDE 9

9

www.tekom.de

9

www.tekom.de

Requirements for iiRDS: Areas

What must intelligent information do to support users and systems?

  • Dynamically adjust to the person, role, task, and usage

context

  • Provide targeted information for standard operation, failure

and maintenance

  • Match the delivered system
  • Provide targeted content assembly
  • Dynamically integrate assistance information and operating

parameters

  • Versatile search and support for filtering information
  • Displayed on different devices
  • Can be extensible by the user
  • Safety mechanisms
slide-10
SLIDE 10

10

www.tekom.de

10

www.tekom.de

Requirements for iiRDS: User stories

Definition of requirements as user stories with prioritization according to MOSCOW

Who wants what why ... As a service technician who needs to remove a malfunction, I want to receive instructions related to the error message so that I can take the right actions. Must have As a user/operator/service technician, I want the technical information to adapt to changes in the software configuration

  • r hardware components so that system

and information always match. Must have

  • 10 areas with a total of 59 user stories
slide-11
SLIDE 11

11

www.tekom.de

11

www.tekom.de

Requirements for iiRDS Semantic modelling as RFDS

Agenda

First version of the metadata Technical scenario and requirements Further steps and open tasks Format description

slide-12
SLIDE 12

12

www.tekom.de

12

www.tekom.de

Methodological basis: PI classification

The method of PI classification (designed by Prof. Dr. Ziegler I4ICM & HS Karlsruhe) defines metadata for modular content (pi-class.de) and is used in many CCMSs:

  • For product components and information types (intrinsic)
  • For end products and information products (extrinsic)
  • For properties that are used for additional features (e.g. maintenance

plans) or for more complex variant control The PI-Fan content, which is already used in CCMS and Content Delivery systems (pi-fan.de), serves as the reference model for the initial implementation.

slide-13
SLIDE 13

13

www.tekom.de

13

www.tekom.de

Semantic modeling in RDF

  • RDFS = Resource Description Framework

Schema

  • Designed as a metadata data model
  • For defining vocabulary, taxonomy, and

rules for using the modeled resources for a particular domain

  • Models context and structures of

knowledge

  • Definition of simple ontologies
  • Can use different formats (syntax), but

mostly XML

slide-14
SLIDE 14

14

www.tekom.de

14

www.tekom.de

Recourse to established technology

  • RDF/RDFS
  • Part of the Semantic Web
  • Since 1999, RDF has been a W3C
  • recommendation. The current

specification, RDF 1.1, was released in 2014.

  • Also used in the reference model

for industry 4.0 (RAMI)

User interface and applications Trust Proof Cryptography Unifying Logic Querying: SPARQL Ontologies: OWL Rules: RIF/SWRL Taxonomies: RDFS Data interchange: RDF Syntax: XML

Identifiers: URI Character Set: UNICODE

slide-15
SLIDE 15

15

www.tekom.de

15

www.tekom.de

Requirements for iiRDS Semantic modelling as RDFS

Agenda

First version of the metadata Technical scenario and requirements Further steps and open tasks Format description

slide-16
SLIDE 16

16

www.tekom.de

16

www.tekom.de

Current state of the metadata

slide-17
SLIDE 17

17

www.tekom.de

17

www.tekom.de

Current state of the metadata

slide-18
SLIDE 18

18

www.tekom.de

18

www.tekom.de

Metadata und user stories

As a service technician who needs to remove a malfunction, I want to receive instructions related to the error message so that I can take the right actions.

slide-19
SLIDE 19

19

www.tekom.de

19

www.tekom.de

Technical aspects

Sebastian Göttel, represented by Dr. Martin Kreutzer

slide-20
SLIDE 20

20

www.tekom.de

20

www.tekom.de

Requirements for iiRDS Semantic modeling ad RDFS

Agenda

First version of the metadata Technical scenario and requirements Further steps and open tasks Format description

slide-21
SLIDE 21

21

www.tekom.de

21

www.tekom.de

Technical scenario

Content Delivery

CCMS

Supplier documentation, legacy documents, bulletins, ...…

ERP, PLM and other DB

Content Delivery Content Delivery

Content Delivery

Manufacturer A Manufacturer C Operator

App

Control room

Panel

Resources

Manufacturer B

slide-22
SLIDE 22

22

www.tekom.de

22

www.tekom.de

Technical requirements

An operator wants to intelligently aggregate and select information for his machine park. For this purpose, the

  • perator requires a delivery format that meets the following

requirements:

  • Manufacturer-independent
  • Able to process both fine-grained information and monolithic documents
  • Tag information with metadata
  • Standardized metadata for evaluating information from different sources
  • Standardized content formats to ensure processing (aggregation, device-

specific display)

  • Archivability
slide-23
SLIDE 23

23

www.tekom.de

23

www.tekom.de

Requirements for iiRDS Semantic modelling as RDFS

Agenda

First version of the metadata Technical scenario and requirements Further questions and open tasks Format description

slide-24
SLIDE 24

24

www.tekom.de

24

www.tekom.de

Package format

Package

Metadata Content

slide-25
SLIDE 25

25

www.tekom.de

25

www.tekom.de

PI - FAN. z i p pa c ka ge . r df PI - FAN ht m l de ka pi t e l _1. ht m l ka pi t e l _2. ht m l ka pi t e l _3. ht m l a bbi l dung_1. j pg a bbi l dung_2. j pg e n c ha pt e r _1. ht m l c ha pt e r _2. ht m l c ha pt e r _3. ht m l i m a ge _1. j pg i m a ge _2. j pg pdf de PI - FAN. pdf e n PI - FAN. pdf

  • Control file for

metadata

  • Name (package.rdf)

and path (top level) fix

  • XML-serialized RDF
  • Content files
  • At the top level,
  • nly directories,
  • therwise
  • Free organization
  • Free name
  • Order by the control

file

Package unzipped

slide-26
SLIDE 26

26

www.tekom.de

26

www.tekom.de

Different levels

Package (Level 1)

Metadata

  • File

Content

  • File
  • ...

Package (Level 2)

Metadata

  • File

Content

  • Structured files
  • Structured files
  • Structured files
  • ...

Package (Level 3)

Metadata

  • File

Content

  • Structured file

(embedded metadata)

  • Structured file

(embedded metadata

  • ...
slide-27
SLIDE 27

27

www.tekom.de

27

www.tekom.de

Package (Level 1)

Level 1: Document-oriented view

Metadata

  • InformationType = „Document“
  • DocumentType =

„Maintenance instructions“

  • Product = „XYZ-0815“
  • ProductLifeCycle = „Operation“
  • Person = „Trained personnel“
slide-28
SLIDE 28

28

www.tekom.de

28

www.tekom.de

Package (Level 2)

Level 2: Module-oriented view

Metadata

  • [Module 1] InformationType = „Topic“
  • [Module 1] TopicType = „Task“
  • [Module 1] InformationSubject =

„Troubleshooting“

  • [Module 1] Product = „XYZ-0815“
  • [Module 1] ProductLifeCycle = „Operation“
  • [Module 1] Person = „ Trained personnel“

This works (in principle) the same way in HTML

slide-29
SLIDE 29

29

www.tekom.de

29

www.tekom.de

Package (Level 3)

Level 3: Sub-module view

Metadata

  • [Module 1#A] InformationType = „Fragment“
  • [Module 1#A] InformationTheme = „Warnings“
  • [Module 1#A] Product = „XYZ-0815“
  • [Module 1#A] ProductLifeCycle = „Operation“
  • [Module 1#A] Person = „All “

This works (in principle) the same way in HTML

slide-30
SLIDE 30

30

www.tekom.de

30

www.tekom.de

Opposing goals

All metadata is provided for all formats. Ensure that target systems can process the content.

slide-31
SLIDE 31

31

www.tekom.de

31

www.tekom.de

Level 3 Level 2 Level 1 Head

All file formats Structured format (XML/HTML5/etc.) [MUST] plus any files [OPTIONAL] Strongly structured, semantic format [MUST] plus any files [OPTIONAL] PDF/A-2 Defined XML/serialized subset of HTML5 with the following file formats: PNG, JPG, SVG, PDF, MPEG2, MP3 Defined XML/serialized subset of HTML5 with the following file formats: PNG, JPG, SVG, PDF, MPEG2, MP3

Double track solution

Free variant Reliable /A-variant

slide-32
SLIDE 32

32

www.tekom.de

32

www.tekom.de

  • Authoring standard
  • No one needs to write RDF.
  • No one needs to manually

create the iiRDS metadata.

  • Presentation format
  • It will need a processing step

to display iiRDS content "nicely.“

  • Storage format in content

delivery systems

  • The exchange format does

not indicate how the information was originally authored and stored.

An exchange format is not a …

Bildnachweis: Pixabay (PublicDomain)

slide-33
SLIDE 33

33

www.tekom.de

33

www.tekom.de

Requirements for iiRDS Semantic modeling as RDFS

Agenda

First version of the metadata Technical scenario and requirements Further steps and open tasks Format description

slide-34
SLIDE 34

34

www.tekom.de

34

www.tekom.de

Further steps

  • Continue development of semantic model
  • Specify mandatory elements
  • Add navigation structures
  • Documentation
  • Use of Dublin Core
  • Develop architecture with iiRDS core + branch-specific domains
  • Validation by means of reference implementations and

show cases at tekom events

  • Comments by interested parties
  • Coordinate with other standardization initiatives such as

OPC UA, RAMI ...

  • Publication
slide-35
SLIDE 35

35

www.tekom.de

35

www.tekom.de

  • Intelligent information

requires metadata

  • Metadata is created by

editorial work

  • Sophisticated metadata

concepts require preparation and time

Why are we informing you now?

Bildnachweis: Pixabay (PublicDomain)

slide-36
SLIDE 36

36

www.tekom.de

36

www.tekom.de

  • Technical communication

becomes part of Industry 4.0/ the smart factory

  • Standardized metadata

makes data exchange and query easy

  • We can aggregate

contents from different sources in content delivery systems

What are the benefits of iiRDS?

Bildnachweis: Pixabay (PublicDomain)

slide-37
SLIDE 37

37

www.tekom.de

37

www.tekom.de

  • The iiRDS will be available as Open Resource, under

Creative Commons License

  • Target date for request for comments (RFC):

31 March 2017

  • Further information: www.tekom.de/iirds

Time line

slide-38
SLIDE 38

38

www.tekom.de

38

www.tekom.de

Gesellschaft für Technische Kommunikation – tekom Deutschland e.V. Rotebühlstraße 64 70178 Stuttgart +49 711 65704-0 Fax +49 711 65704-99 www.tekom.de/iirds info@tekom.de

Our contact information