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. 1 1 www.tekom.de www.tekom.de
Introduction Dr. Michael Fritz 2 2 www.tekom.de www.tekom.de
User expectations User expectations for communication products • Context sensitive • Individualized • Adaptable • Multi-channel delivery • User experience • … 3 3 3 www.tekom.de 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 4 4 www.tekom.de 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 5 5 www.tekom.de www.tekom.de
Agenda Requirements for iiRDS Semantic modeling as RDFS First version of the metadata Technical scenario and requirements Format description Further steps and open tasks 6 6 www.tekom.de www.tekom.de
Agenda Requirements for iiRDS Semantic modeling as RDFS First version of the metadata Technical scenario and requirements Format description Further steps and next tasks 7 7 www.tekom.de www.tekom.de
Requirements and semantic modeling Ulrike Parson 8 8 www.tekom.de 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 9 9 www.tekom.de www.tekom.de
Requirements for iiRDS: User stories Definition of requirements as user stories with prioritization according to MOSCOW As a service technician who needs to Must have remove a malfunction, I want to receive instructions related to the error message so that I can take the right actions. Who wants As a user/operator/service technician , Must have what why ... I want the technical information to adapt to changes in the software configuration or hardware components so that system and information always match. 10 areas with a total of 59 user stories 10 10 www.tekom.de www.tekom.de
Agenda Requirements for iiRDS Semantic modelling as RFDS First version of the metadata Technical scenario and requirements Format description Further steps and open tasks 11 11 www.tekom.de 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. 12 12 www.tekom.de 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 13 13 www.tekom.de www.tekom.de
Recourse to established technology • RDF/RDFS User interface and applications • Part of the Semantic Web Trust • Since 1999, RDF has been a W3C Proof recommendation. The current specification, RDF 1.1, was Unifying Logic released in 2014. Ontologies: Rules: Cryptography OWL RIF/SWRL • Also used in the reference model Querying: SPARQL for industry 4.0 (RAMI) Taxonomies: RDFS Data interchange: RDF Syntax: XML URI UNICODE Identifiers: Character Set: 14 14 www.tekom.de www.tekom.de
Agenda Requirements for iiRDS Semantic modelling as RDFS First version of the metadata Technical scenario and requirements Format description Further steps and open tasks 15 15 www.tekom.de www.tekom.de
Current state of the metadata 16 16 www.tekom.de www.tekom.de
Current state of the metadata 17 17 www.tekom.de 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. 18 18 www.tekom.de www.tekom.de
Technical aspects Sebastian Göttel, represented by Dr. Martin Kreutzer 19 19 www.tekom.de www.tekom.de
Agenda Requirements for iiRDS Semantic modeling ad RDFS First version of the metadata Technical scenario and requirements Format description Further steps and open tasks 20 20 www.tekom.de www.tekom.de
Technical scenario Manufacturer B Supplier documentation, legacy documents, bulletins, Content App ...… Delivery Control room Content Content CCMS Delivery Delivery Panel Content ERP, PLM Resources Delivery and other DB Manufacturer A Manufacturer C Operator 21 21 www.tekom.de www.tekom.de
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 22 22 www.tekom.de www.tekom.de
Agenda Requirements for iiRDS Semantic modelling as RDFS First version of the metadata Technical scenario and requirements Format description Further questions and open tasks 23 23 www.tekom.de www.tekom.de
Package format Package Metadata Content 24 24 www.tekom.de www.tekom.de
Package unzipped • Control file for PI - FAN. z i p pa c ka ge . r df metadata PI - FAN • Name (package.rdf) ht m l de and path (top level) ka pi t e l _1. ht m l fix ka pi t e l _2. ht m l • XML-serialized RDF ka pi t e l _3. ht m l a bbi l dung_1. j pg • Content files a bbi l dung_2. j pg e n • At the top level, c ha pt e r _1. ht m l only directories, c ha pt e r _2. ht m l otherwise c ha pt e r _3. ht m l i m a ge _1. j pg • Free organization i m a ge _2. j pg • Free name pdf de • Order by the control PI - FAN. pdf file e n PI - FAN. pdf 25 25 www.tekom.de www.tekom.de
Different levels Package (Level 2) Package (Level 1) Package (Level 3) Metadata Content Metadata Content Metadata Content • File • Structured file • File • Structured files (embedded metadata) • Structured files • File • File • Structured file • Structured files (embedded metadata • ... • ... • ... 26 26 www.tekom.de www.tekom.de
Level 1: Document-oriented view Package (Level 1) Metadata • InformationType = „Document“ • DocumentType = „Maintenance instructions“ • Product = „XYZ-0815“ • ProductLifeCycle = „Operation“ • Person = „Trained personnel“ 27 27 www.tekom.de www.tekom.de
Level 2: Module-oriented view Package (Level 2) 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 28 28 www.tekom.de www.tekom.de
Level 3: Sub-module view Package (Level 3) 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 29 29 www.tekom.de www.tekom.de
Opposing goals All metadata is provided for all formats. Ensure that target systems can process the content. 30 30 www.tekom.de www.tekom.de
Recommend
More recommend
