Intelligent Information

Size: px

Start display at page:

Download "Intelligent Information"

Mervyn Nicholson
5 years ago
Views:

1 Intelligent Information for Smart Users Dr Michael Fritz, tekom 1

2 Digital Transformation Everything is smart WHAT MAKES INFORMATION SMART? 2

3 DIGITAL TRANSFORMATION Three Dimensions Prof. Key Pousttchi 1) Value Creation Model The 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. 3

4 DIGITAL TRANSFORMATION Smart Products Characteristics Sensors Software Controlled Connected Storage Capacity 4

5 DIGITAL TRANSFORMATION Smart Production 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 ) 5

6 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 OBJECT ASSET CONCEPT MODEL SMART SIBLING SEMANTIC TRIANGLE 6

7 DIGITAL TRANSFORMATION Smart Production How can information for use be delivered to users in the future? a) Embedded in the object b) Linked with the IoT OBJECT a) Embedded IoT CONCEPT MODEL 7

8 DIGITAL TRANSFORMATION Three Dimensions Prof. Key Pousttchi 2) Value Proposition Model The 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. 8

9 DIGITAL TRANSFORMATION Smart Products Characteristics Sensors Software Controlled Connected Storage Capacity 9

10 DIGITAL TRANSFORMATION Smart Services PRODUCTS Cars Homes Watches Fridges SERVICE Mobility smartliving ehealth smartshopping 10

11 DIGITAL TRANSFORMATION Ubiquitous Data Big Data Large scale Data Analytics Controlling, Predictive Maintenance and Improvement of Smart Products and Services Sales Forecasts ehealth 11

12 DIGITAL TRANSFORMATION Platform Economy Data driven business models ECONOMIC WINNERS 12

13 DIGITAL TRANSFORMATION Three Dimensions Prof. Key Pousttchi 3) Customer Interaction Model The 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. 13

14 DIGITAL TRANSFORMATION Ubiquitous Data All things are connected with the Internet (Auto ID) by sensors or actors Barcodes Smart Labels Biometry OCR RFID Speech Recognitio IoT Internet of Things 14

15 DIGITAL TRANSFORMATION Ubiquitous Data Access from everywhere 15

16 DIGITAL TRANSFORMATION Mobile Devices Everybody uses mobile devices 16

17 DIGITAL TRANSFORMATION Smart Users What smart users want: The right information For the right person At the right place On the Most Suitable Device In real time INTELLIGENT INFORMATION 17

18 DIGITAL TRANSFORMATION Smart Users What is Intelligent Information (my definition)? Information that enables humanmachine communication in a nearly natural way Therefore it is: User centric Use case oriented Event driven Dynamic METADATA DRIVEN 18

19 Conclusions for Technical Communication 19

20 My main conclusion CONTEXT IS KING 20

21 INTELLIGENT INFORMATION Context Rules 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 21

22 INTELLIGENT INFORMATION Context Rules 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 22

23 INTELLIGENT INFORMATION Conclusions for Technical Communication Paradigm Change 1: Use Cases In which situations do my users need information? 23

24 INTELLIGENT INFORMATION Conclusions for Technical Communication Paradigm Change 2: User centricity What do my users want? Intelligent Information 24

INTELLIGENT INFORMATION Conclusions for Technical Communication Paradigm Change 3: From Documents to Information The formal context of documents which was constituted by their structure

25 INTELLIGENT INFORMATION Conclusions for Technical Communication 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 25

26 INTELLIGENT INFORMATION Conclusions for Technical Communication Paradigm Change 4: Metadata How do I describe the use cases with metadata? 26

27 INTELLIGENT INFORMATION Conclusions for Technical Communication Metadata Systems Virtual model of the object s context OBJECT Context Metadata CONCEPT MODEL 27

28 Technical Scenario Developed by tekom s Working Group Information

29 TECHNICAL SCENARIO Information Request and Delivery Challenges Individual metadata Proprietary delivery formats STANDARD IZATION REQUIRED! Christoph Attila Kun, VDI

30 TECHNICAL SCENARIO Information Request and Delivery The solution Win Win iirds Christoph Attila Kun, VDI

31 TECHNICAL SCENARIO Information Request and Delivery iirds REQUEST Delivery Sever Enterprise Search CCMS Enterprise CMS ERP iirds DELIVER Y EVENT 31

32 TECHNICAL SCENARIO Information Request and Delivery Delivery Sever Enterprise Search CCMS Enterprise CMS ERP OEM XML: iirds DELIVER Y Operator 32

33 TECHNICAL SCENARIO Information Request and Delivery Delivery Sever Enterprise Search CCMS Enterprise CMS ERP OEM DELIVER Y XML: VDI 2770 Operator 33

34 Information Request Semantic Modelling 34

35 TECHNICAL SCENARIO Information Request 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 35

36 TECHNICAL SCENARIO Information Request 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: 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 fan.de 36

TECHNICAL SCENARIO Information Request Semantic modelling in RDF (Semantic Web Standard, W3C) RDFS = Resource Description Framework Schema Metadata Data Model Definition of vocabulary, taxonomy

37 TECHNICAL SCENARIO Information Request 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 37

38 TECHNICAL SCENARIO Information Request 38

39 TECHNICAL SCENARIO Information Request VDI 2770 Schublade 04 Schublade 03 Schublade 02 Schublade 01 39

40 TECHNICAL SCENARIO Information Request Specimen, not related with other figures 40

41 Information Delivery iirds Container Format 41

42 TECHNICAL SCENARIO Information Delivery Container Metadata + Information Object(s) 42

43 TECHNICAL SCENARIO Information Delivery Metadata File Name (package.rdf) and path (top level) are fix XML serial RDF Content data On top level only directories, besides this Free organization Free naming Organization by the main file PI-FAN.zip package.rdf PI-FAN html pdf de en de 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 en PI-FAN.pdf 43

44 TECHNICAL SCENARIO Information Delivery Packet (Level 1) Packet (Level 2) Packet (Level 3) Metadata Contents Metadata Contents Metadata Contents File File... File Structured content Structured content Structured content... File Structured content with embedded meta data Structured content with embedded meta data... 44

Document Kind = Maintenance Instuction Product = XYZ

45 TECHNICAL SCENARIO Information Delivery Container (Level 1) Metadata Information Type = Document Document Kind = Maintenance Instuction Product = XYZ 0815 Product Life Cycle = Operation Person = Trained Staff 45

TECHNICAL SCENARIO Information Delivery Container (Level 2) Metadata [Module 1] Information Type = Topic [Module 1] Topic Type = Task [Module 1] Information

46 TECHNICAL SCENARIO Information Delivery 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 COULD ALSO WORK WITH XHTML 46

Fragment [Module #1A] Information Kind = Warning

Product Life Cycle = Operation [Module #1A] Person =

47 TECHNICAL SCENARIO Information Delivery Container (Level 3) 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 COULD ALSO WORK WITH XHTML 47

48 TECHNICAL SCENARIO Information Delivery Consideration to be made Any Format, enriched with Metadata Make sure that devices can display the content 48

49 TECHNICAL SCENARIO Information Delivery FREE VARIANT RELIABLE VARIANT A/ Level 1 Any File Format PDF/A 2 Level 2 Structured Formats (e.g. XML/HTML5) [DEFAULT] plus Files with any format [OPTIONAL] Defined XML Subset of HTML5 with the following formats: PNG, JPG, SVG, PDF, MPEG2, MP3 Level 3 Highly structured, semantic format [DEFAULT] plus Files with any format [OPTIONAL] Highly structured, semantic format plus the following formats: PNG, JPG, SVG, PDF, MPEG, MP3 49

50 User Stories The future is smart 50

51 USER STORIES General Language 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 OBLIGATORY WHO WANTS WHAT, WHY? 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 51

52 USER STORIES Trouble Shooting Event: Malfunction of a system Foto: Fotolia 52

53 USER STORIES Trouble Shooting 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 53

54 USER STORIES Integrating several deliveries Third party documents, Legacy documents, Bulletins, MANUFACTURER B Content Delivery App Content Delivery Op display CCMS Asset Management Panel ERP, PLM & other DB Content Delivery Ressources MANUFACTURER A MANUFACTURER C CUSTOMER 54

55 Summary iirds is 55

56 Summary iirds is a standardized Metadata Ontology, plus a standardized Container Format which together enable (dynamic) information request and delivery processes between users and the (information )system 56

57 Disclaimer 57

iirds is not 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

58 iirds is not 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 (PublicDomain) 58

59 HOW COMPANIES CAN Be prepared WHAT DO I NEED? Competent TechWriters Established process (Hackos, Level 3) Semantic structuring Component Content Management System (XML) Single sourcecapability Cross media capability Semantic metadata Ontology / Taxonomy Delivery concept Content delivery system (CDS) PRE REQUISITES OBLIGATORY 59

60 HOW COMPANIES CAN Be prepared My CCMS Vendor must implement iirds as an interface My consultant must help me with the metadata system WHAT DO I NEED? 60

61 The tekom Working Group Smart people working hard 61

62 WG INFO 4.0 Members of the Working Group 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 62

63 WG INFO 4.0 Work in Progress Goal: Elaborate tekom Guidelines for a request and deliver standard for intelligent information for use Working mode: Open Data Project Kick off: Results 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

64 WG INFO 4.0 Work in Progress Liasing with VDI 2770, to reach full compatibility Platform Industry 4.0, and become official partial model of industry 4.0 and submit the iirds vocabulary to international standardization Publishing of first draft End of

65 WG INFO 4.0 Work in Progress Liasing with Platform Industry 4.0, and become official partial model of industry 4.0 and submit the iirds vocabulary to international standardization 65

66 WG INFO 4.0 A Glimpse into Future 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 BECOME A MEMBER! 66

67 WG INFO 4.0 How to contact us Gesellschaft für Technische Kommunikation tekom Deutschland e.v. Judith Hallwachs Rotebühlstraße Stuttgart iirds.tekom.de (forchina) Follow us on: 67

Intelligent Information Request and Delivery Standard

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