Intelligent Information Request andDeliveryStandard · Intelligent Information Request...

transcript

1www.tekom.de 1www.tekom.de

Intelligent Information Request and Delivery StandardThe 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.

IntroductionDr. Michael Fritz

User expectations

User expectations for communication products• Context sensitive• Individualized• Adaptable• Multi-channel delivery• User experience• …

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

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

Requirements for iiRDS

Semantic modeling as RDFS

Agenda

First version of the metadata

Technical scenario and requirements

Further steps and open tasks

Format description

Agenda

Further steps and next tasks

Format description

Requirements and semantic modeling

Ulrike Parson

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

Requirements for iiRDS: User stories

Definition of requirements as user stories with prioritization according to MOSCOW

Who wantswhat 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 or hardware components so that system and information always match.

Must have

10 areas with a total of 59 user stories

Semantic modelling as RFDS

Agenda

Format description

Methodological basis: PI classification

The method of PI classification (designed by Prof. Dr. Ziegler I4ICM & HS Karlsruhe) defines metadata formodular 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.

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

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

Cryptography

Unifying Logic

Querying:SPARQL

Ontologies:OWL

Rules:RIF/SWRL

Taxonomies: RDFS

Data interchange: RDF

Syntax: XML

Identifiers: URI Character Set: UNICODE

Semantic modelling as RDFS

Agenda

Format description

Current state of the metadata

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.

Technical aspectsSebastian Göttel, represented by Dr. Martin Kreutzer

Semantic modeling ad RDFS

Agenda

Format description

Technical scenario

Content DeliveryCCMS

Supplierdocumentation, legacydocuments, bulletins, ...…

ERP, PLM and other

Content Delivery

Manufacturer A Manufacturer C Operator

Control room

Resources

Manufacturer B

Technical requirements

An operator wants to intelligently aggregate and select information for his machine park. For this purpose, the operator 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

Semantic modelling as RDFS

Agenda

Further questions and open tasks

Format description

Package format

Package

Metadata Content

PI-FAN.zip

package.rdf

PI-FAN

kapitel_1.html

kapitel_2.html

kapitel_3.html

abbildung_1.jpg

abbildung_2.jpg

chapter_1.html

chapter_2.html

chapter_3.html

image_1.jpg

image_2.jpg

PI-FAN.pdf

• Control file for metadata• Name (package.rdf)

and path (top level) fix

• XML-serialized RDF• Content files

• At the top level, only directories, otherwise

• Free organization• Free name• Order by the control

Package unzipped

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• ...

Package (Level 1)

Level 1: Document-oriented view

Metadata

• InformationType = „Document“• DocumentType =

„Maintenance instructions“• Product = „XYZ-0815“• ProductLifeCycle = „Operation“• Person = „Trained personnel“

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

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

Opposing goals

All metadata is provided for all

formats.

Ensure that target systems can process the

content.

Level 3

Level 2

Level 1

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,

Defined XML/serialized subset of HTML5 with

the following file formats: PNG, JPG, SVG, PDF, MPEG2,

Double track solutionFree variant Reliable

/A-variant

• 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 …

Agenda

Format description

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

• Intelligent information requires metadata

• Metadata is created by editorial work

• Sophisticated metadata concepts require preparation and time

Why are we informing you now?

• 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?

• 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

Gesellschaft für Technische Kommunikation – tekom Deutschland e.V. Rotebühlstraße 6470178 Stuttgart

+49 711 65704-0Fax +49 711 65704-99

www.tekom.de/iirds info@tekom.de

Our contact information

Intelligent Information Request andDeliveryStandard · Intelligent Information Request...

Documents