Intelligent Information for Smart Users · information items or other information objects (e.g....
Transcript of Intelligent Information for Smart Users · information items or other information objects (e.g....
1www.tekom.de 1www.tekom.de
Intelligent Information for Smart UsersDr Michael Fritz, tekom
2www.tekom.de 2www.tekom.de
Digital Transformation„Everything is smart“
WHAT MAKESINFORMATION
SMART?
3www.tekom.de 3www.tekom.de
Prof. Key Pousttchi
1) Value Creation ModelThe first dimension of the digital transformation comprises the influence on the creation of products and services, including necessary support processes and the organization of the company.
DIGITAL TRANSFORMATION
Three Dimensions
4www.tekom.de 4www.tekom.de
Characteristics
Sensors Software Controlled Connected Storage Capacity
DIGITAL TRANSFORMATION
Smart Products
5www.tekom.de 5www.tekom.de
Industry 4.0 / Industrial Internet /Made in China 2025
Self‐organizing and –optimizing “Cyber Physical Systems” Machine‐to‐Machine Communication, everything is connected Individualization of products (“Batch Size Zero”)
DIGITAL TRANSFORMATION
Smart Production
6www.tekom.de 6www.tekom.de
SEMANTIC TRIANGLE
DIGITAL TRANSFORMATION
Smart Production
„Industrial Internet / Industry 4.0 / Made in China 2025“
Engineering and IT merge IT works with digital models of the real products
„ASSET“OBJECT
CONCEPT MODEL
„SMART SIBLING“
7www.tekom.de 7www.tekom.de
How can information for use bedelivered to users in the future?
DIGITAL TRANSFORMATION
Smart Production
a) Embedded in the objectb) Linked with the IoT
OBJECT
CONCEPT MODEL
IoTa) Embedded
8www.tekom.de 8www.tekom.de
Prof. Key Pousttchi
2) Value Proposition ModelThe second dimension of the digital transformation comprises the influence on the company’s products, services, and revenue models.Hereby, the direct and indirect effect of applying digital technologies and techniques for improving existing products and services, offering new or even novel products and services, as well as changes of respective revenue models, is in focus.
DIGITAL TRANSFORMATION
Three Dimensions
9www.tekom.de 9www.tekom.de
Characteristics
Sensors Software Controlled Connected Storage Capacity
DIGITAL TRANSFORMATION
Smart Products
10www.tekom.de 10www.tekom.de
PRODUCTS
Cars
Homes
Watches
Fridges
SERVICE
Mobility
smartLiving
eHealth
smartShopping
DIGITAL TRANSFORMATION
Smart Services
11www.tekom.de 11www.tekom.de
Big Data Large‐scale Data Analytics
Controlling, Predictive Maintenance and Improvement of Smart Products and Services Sales Forecasts eHealth …
DIGITAL TRANSFORMATION
Ubiquitous Data
12www.tekom.de 12www.tekom.de
ECONOMICWINNERS
DIGITAL TRANSFORMATION
Platform Economy
Data‐driven business models
13www.tekom.de 13www.tekom.de
Prof. Key Pousttchi
3) Customer Interaction ModelThe third dimension of the digital transformation comprises the influence on type and content of customer interaction. Substantial indicators are a cross‐channel and holistic approach within customer relations as well as including automatized communication and modern forms of data analysis.
DIGITAL TRANSFORMATION
Three Dimensions
14www.tekom.de 14www.tekom.de
All things are connected with the Internet (Auto‐ID) by sensors or actors
Barcodes Smart LabelsBiometryOCRRFID Speech Recognitio…
DIGITAL TRANSFORMATION
Ubiquitous Data
IoTInternet of Things
15www.tekom.de 15www.tekom.de
Access from everywhere
DIGITAL TRANSFORMATION
Ubiquitous Data
16www.tekom.de 16www.tekom.de
Everybody uses mobile devices
DIGITAL TRANSFORMATION
Mobile Devices
17www.tekom.de 17www.tekom.de
What smart users want:
The right information For the right person At the right place On the Most Suitable Device In real time
INTELLIGENTINFORMATION
DIGITAL TRANSFORMATION
Smart Users
18www.tekom.de 18www.tekom.de
What is Intelligent Information (my definition)?
„Information that enables human‐machine‐communication in a nearlynatural way …“
Therefore it is: User centric Use case oriented Event driven Dynamic
METADATADRIVEN
DIGITAL TRANSFORMATION
Smart Users
19www.tekom.de 19www.tekom.de
Conclusions for Technical Communication
20www.tekom.de 20www.tekom.de
My main conclusion …
CONTEXTIS KING
21www.tekom.de 21www.tekom.de
1) Smart Users Information available everywhere / online / on all devices
2) Smart Products Information for use OR links to the information embedded in the product
3) Smart Services Information for use part of the service chain
4) Ubiquitous Data Information formats adaptive / responsive
5) Internet of Things Identifiers / connectors / actors to link products to information for use on the web / in the cloud
INTELLIGENT INFORMATION
Context Rules
22www.tekom.de 22www.tekom.de
6) „Industrial Internet / Industry 4.0 / Made in China 2025“Challenge How can smart information / links to smart information become a part of the “Administration Shell” of the product?
Paper is obsolete, dynamic delivery of electronic information needed Depending on the identification of the product Depending on the configuration of the product and its operating state Depending on individual factors of the user
INTELLIGENT INFORMATION
Context Rules
23www.tekom.de 23www.tekom.de
INTELLIGENT INFORMATION
Conclusions for Technical Communication
Paradigm Change 1:
Use CasesIn which situations do my users need information?
24www.tekom.de 24www.tekom.de
INTELLIGENT INFORMATION
Conclusions for Technical Communication
Paradigm Change 2:
User centricityWhat do my users want?
IntelligentInformation
25www.tekom.de 25www.tekom.de
Paradigm Change 3:
From Documents to Information The formal context of documents which was
constituted by their structure dissolves …
Intelligent Information uses smaller information items or other information objects (e.g. video)
The context information for Intelligent Information is constituted by … META‐
DATA
INTELLIGENT INFORMATION
Conclusions for Technical Communication
26www.tekom.de 26www.tekom.de
INTELLIGENT INFORMATION
Conclusions for Technical Communication
Paradigm Change 4:
MetadataHow do I describe theuse cases with metadata?
27www.tekom.de 27www.tekom.de
Metadata Systems …
Virtual model of the object‘s context
INTELLIGENT INFORMATION
Conclusions for Technical Communication
OBJECT
CONCEPT MODEL
Context
Metadata
28www.tekom.de 28www.tekom.de
Technical ScenarioDeveloped by tekom’s Working Group “Information 4.0”
29www.tekom.de 29www.tekom.de
Challenges Individual metadataProprietary delivery formats
TECHNICAL SCENARIO
Information Request and Delivery
Christoph Attila Kun, VDI 2770
STANDARD‐IZATION
REQUIRED!
30www.tekom.de 30www.tekom.de
The solution …
TECHNICAL SCENARIO
Information Request and Delivery
Christoph Attila Kun, VDI 2770
Win‐Win
iiRDS
31www.tekom.de 31www.tekom.de
TECHNICAL SCENARIO
Information Request and Delivery
DELIVERY
REQUEST
EVENT
Enterprise Search
Delivery Sever
CCMSEnterprise
CMSERP …
iiRDS
iiRDS
32www.tekom.de 32www.tekom.de
TECHNICAL SCENARIO
Information Request and Delivery
DELIVERY
XML:iiRDS Operator
Enterprise Search
Delivery Sever
CCMSEnterprise
CMSERP …
OEM
33www.tekom.de 33www.tekom.de
TECHNICAL SCENARIO
Information Request and Delivery
DELIVERY
XML:VDI 2770 Operator
Enterprise Search
Delivery Sever
CCMSEnterprise
CMSERP …
OEM
34www.tekom.de 34www.tekom.de
Information RequestSemantic Modelling
35www.tekom.de 35www.tekom.de
Which metadata must information have to give optimal support to users and systems?
Dynamic adaption to persons, their roles, their tasks and to work scenarios
Specialized information covering regular operation, maintenance and trouble shooting
Matching with the delivered system
Support of information curation
Dynamic integration of support information and operation related parameters
Support of a wide range of search and filter functions
Adaptability to different display devices
Extendable by the user
Support of security mechanisms
TECHNICAL SCENARIO
Information Request
36www.tekom.de 36www.tekom.de
PI‐Classification
Classification methodology widely used by CCMS which was developed by Prof. Dr. Wolfgang Ziegler (Karlsruhe) for the purpose of defining metadata for modular contents (see: www.pi‐class.de) describing Product components and information types (intrinsic) Discrete products and information products (extrinsic) Functional mechanisms (e.g. for maintenance plans or for complex
management of variants)
Compare the reference model www.pi‐fan.de
TECHNICAL SCENARIO
Information Request
37www.tekom.de 37www.tekom.de
Semantic modelling in RDF (Semantic Web Standard, W3C)
RDFS = Resource Description Framework Schema Metadata‐Data‐Model Definition of vocabulary, taxonomy and rules for the application of the defines resources within concrete domains Displaying of relationships and structure of knowledge Modelling of ontologies Can use different formats, mostly XML
TECHNICAL SCENARIO
Information Request
38www.tekom.de 38www.tekom.de
TECHNICAL SCENARIO
Information Request
39www.tekom.de 39www.tekom.de
VDI 2770Schublade 04
Schublade 03Schublade 02
Schublade 01
TECHNICAL SCENARIO
Information Request
40www.tekom.de 40www.tekom.de
TECHNICAL SCENARIO
Information Request
Specimen, not related with other figures
41www.tekom.de 41www.tekom.de
Information DeliveryiiRDS “Container Format”
42www.tekom.de 42www.tekom.de
Metadata Information Object(s)
TECHNICAL SCENARIO
Information Delivery
+
Container
43www.tekom.de 43www.tekom.de
PI-FAN.zip
package.rdf
PI-FAN
html
de
kapitel_1.html
kapitel_2.html
kapitel_3.html
abbildung_1.jpg
abbildung_2.jpg
en
chapter_1.html
chapter_2.html
chapter_3.html
image_1.jpg
image_2.jpg
de
PI-FAN.pdf
en
PI-FAN.pdf
Metadata File Name (package.rdf)and path (top level) are fix XML serial RDF
Content data On top level onlydirectories, besides this … Free organization Free naming Organization by the main file
TECHNICAL SCENARIO
Information Delivery
44www.tekom.de 44www.tekom.de
Packet (Level 1)
Metadata• File
Contents• File• ...
Packet (Level 2)
Metadata• File
Contents• Structured content
• Structured content
• Structured content
• ...
Packet (Level 3)
Metadata• File
Contents• Structured contentwithembeddedmeta data
• Structured contentwithembeddedmeta data
• ...
TECHNICAL SCENARIO
Information Delivery
45www.tekom.de 45www.tekom.de
Container (Level 1)
Metadata
Information Type = „Document“ Document Kind = „Maintenance Instuction“ Product = „XYZ‐0815“ Product Life Cycle = „Operation“ Person = „Trained Staff“
TECHNICAL SCENARIO
Information Delivery
46www.tekom.de 46www.tekom.de
Container (Level 2)
Metadata
[Module 1] Information Type = „Topic“ [Module 1] Topic Type = „Task“ [Module 1] Information Kind = „Trouble Shooting“ [Module 1] Product = „XYZ‐0815“ [Module 1] Product Life Cycle = „Operation“ [Module 1] Person = „Trained Staff“
TECHNICAL SCENARIO
Information Delivery
COULD ALSO WORK WITH
XHTML
47www.tekom.de 47www.tekom.de
Metadata
[Module #1A] Information Type = „Fragment“ [Module #1A] Information Kind = „Warning Message“ [Module #1A] Product = „XYZ‐0815“ [Module #1A] Product Life Cycle = „Operation“ [Module #1A] Person = „All“ [Module #1A] Data Model = “Dita”
TECHNICAL SCENARIO
Information Delivery
Container (Level 3)
COULD ALSO WORK WITH
XHTML
48www.tekom.de 48www.tekom.de
Any Format, enriched with Metadata
Make sure that devices can display the content
Consideration to be made …
TECHNICAL SCENARIO
Information Delivery
49www.tekom.de 49www.tekom.de
Level 3
Level 2
Level 1Any File Format
Structured Formats (e.g. XML/HTML5) [DEFAULT] plus Files with any format
[OPTIONAL]
Highly structured, semantic format [DEFAULT] plus Files with any format [OPTIONAL]
PDF/A‐2
Defined XML‐Subset of HTML5 with the following
formats: PNG, JPG, SVG, PDF, MPEG2, MP3
Highly structured, semantic format plus the following
formats: PNG, JPG, SVG, PDF, MPEG, MP3
„FREE“ VARIANT RELIABLE VARIANT A/
TECHNICAL SCENARIO
Information Delivery
50www.tekom.de 50www.tekom.de
User StoriesThe future is smart …
51www.tekom.de 51www.tekom.de
Definition of Requirements in User Stories with Prioritization (according to MOSCOW)
1) As a service technician, in a case of malfunction I want instructions to be displayed context sensitive so that I can act in an adequate way
USER STORIES
General Language
2) As a user / operator / service technician I want that, in case of changes of the software configuration or of hardware components also the information for use will be adjusted, so that system and information are congruent at any time
OBLIGATORY
10 thematic fields with 59 User Stories all over …
OBLIGATORY
WHO WANTSWHAT, WHY?
52www.tekom.de 52www.tekom.de
Event: Malfunction of a system
USER STORIES
“Trouble Shooting”
Foto: Fotolia
53www.tekom.de 53www.tekom.de
„As a service technician, in a case of malfunction I want instructions to be displayed context sensitive so that I can act in an adequate way”
USER STORIES
“Trouble Shooting”
54www.tekom.de 54www.tekom.de
CUSTOMER
Asset
Management
USER STORIES
“Integrating several deliveries”
Content Delivery
Panel
MANUFACTURER A
Third party documents,Legacy documents,Bulletins, …
CCMS
ERP, PLM
& other DB
MANUFACTURER C
Content
Delivery
MANUFACTURER B
Content
DeliveryApp
Res‐sources
Op display
55www.tekom.de 55www.tekom.de
SummaryiiRDS is …
56www.tekom.de 56www.tekom.de
Summary
iiRDS is a … standardized Metadata‐Ontology, plus a standardized Container‐Formatwhich together enable (dynamic) informationrequest‐ and delivery‐processes between usersand the (information‐)system
57www.tekom.de 57www.tekom.de
Disclaimer
58www.tekom.de 58www.tekom.de
… for content creation No one needs to know RDF No one needs to manually create level n/A‐formats
… a display format It will need at least one more step to be able to display iiRDS‐Content „nicely“
… a format for storing Even if you use iiRDS as a exchange format it makes no sense to use it as a content storing format
Foto: Pixabay
(Pub
licDo
main)
iiRDS is not …
59www.tekom.de 59www.tekom.de
HOW COMPANIES CAN
Be prepared
• Competent TechWriters• Established process (Hackos, Level 3)• Semantic structuring• Component Content Management
System (XML)• Single source capability• Cross media capability
PRE‐REQUISITES
WHAT DO I NEED?
OBLIGATORY
• Semantic metadata• Ontology / Taxonomy• Delivery concept• Content delivery system (CDS)
60www.tekom.de 60www.tekom.de
HOW COMPANIES CAN
Be prepared
WHAT DO I NEED?
• My CCMS‐Vendor must implement iiRDS asan interface
• My consultant must help me with themetadata system
61www.tekom.de 61www.tekom.de
The tekom‐Working GroupSmart people working hard
62www.tekom.de 62www.tekom.de
Industry Experts Machine Building and Systems Engineering Power Plants Electronics / Electrotechnical Industries Software
Software Vendors CCMS Content Delivery Systems Enterprise Search Semantic Graphics Database
Consulting and Academia Universities Consulting Service Providers
WG INFO 4.0
Members of the Working Group
63www.tekom.de 63www.tekom.de
Goal: Elaborate tekom Guidelines for a request‐ and deliver‐standard for intelligent information for use
Working mode: Open Data ProjectKick‐off: 2016‐03‐27Results First draft of iiRDS presented at the tekom / tcworld conference on November 2016 in Stuttgart / Germany Sneak Preview for Developers in Spring 2017 Request for Comments (RFC) starting October 20, 2017 Presentations at the tekom / tcworld conference 2017
Publishing of first draft End of 2017
WG INFO 4.0
Work in Progress
64www.tekom.de 64www.tekom.de
Liasing with VDI 2770, to reach full compatibility Platform Industry 4.0, and become official partial model of industry 4.0 eCl@ss, and submit the iiRDS‐vocabulary to international standardization
Publishing of first draft End of 2017
WG INFO 4.0
Work in Progress
65www.tekom.de 65www.tekom.de
Liasing with Platform Industry 4.0, and become official partial model of industry 4.0 eCl@ss, and submit the iiRDS‐vocabulary to international standardization
WG INFO 4.0
Work in Progress
66www.tekom.de 66www.tekom.de
Establishing the iiRDS‐Consortium, starting January 2018 Stable organizational structure within tekom as consortium leader Open to all interested parties (system vendors, consultants, academics and industry managers) from all over the world Support companies that are interested in implementing iiRDS International standardization of the core metadata Further development of the standard
WG INFO 4.0
A Glimpse into FutureBECOME
AMEMBER!
67www.tekom.de 67www.tekom.de
Gesellschaft für Technische Kommunikation –tekom Deutschland e.V.
Judith HallwachsRotebühlstraße 6470178 Stuttgart
[email protected]@tekom.de (for China)
WG INFO 4.0
How to contact us
Follow us on: