OntoNaviERP: Ontology-supported Navigation in ERP Software Documentation

Transcription

1 OntoNaviERP: Ontology-supported Navigation in ERP Software Documentation 1,2 and Andreas Wechselberger 1 1 E-Business and Web Science Research Group, Bundeswehr University Munich, Germany 2 STI Innsbruck, Austria { andreas.wechselberger@unibw.de} 1

2 ERP: Enterprise Resource Planning MRP: Material Requirements Planning MRP-II: Manufacturing Resource Planning CIM: Computer Integrated Manufacturing Comprehensive --> Complex 2

3 SAP Help Files 3

4 Search is important, because... Users must align their mental models of processes and data with those underlying the ERP software Function Document Role? Event Intensive usage Function More efficient usage of ERP documentation means more efficient business operations. 4

5 Search is difficult, because... 5

6 Search is difficult, because... 5

7 Search is difficult, because... Textbook Business Terminology SAP Business Terminology SAP IT/System Terminology Industry Domain Terminology 5

8 In other words: An ideal showcase for semantic technology... 6

9 Requirements Cost-efficient Ontology Construction Cost-efficient Annotation Speed User Interface 7

10 Competency Question 8

11 Overview: OntoNaviERP 9

12 Which Terms Are Most Valuable - The Most Popular, the Frequent, or the Rare? Frequency vs. Information Value vs. Likelihood of Relevance Web-wide Number of Occurrences + Likelihood of relevant documents + Likelihood of usage in queries - limited information value balance between frequency and specificity + higher information value + highest information value if needed - likelihood of occurrence in query low - likelihood of relevant documents low Term 1..N (similar pattern for: Tags, Ontology Elements) 10

13 Approach: Conceptual Model 11

14 Approach: Conceptual Model Semi-automatically derived from term lists Traditional ontology engineering 11

15 Approach: Ontology Construction (1) Script Protégé WordNet Plug-In OWL Annotation Property.NT Generator 12

16 Approach: Ontology Construction (2) 13

17 Approach: Ontology Construction (3) 5 * 127 = * 257 = 32,382 14

18 Approach: Annotation (1) 15

19 Approach: Annotation (2) 16

20 Approach: User Interface and System 17

21 Evaluation Methodology 18

22 Results (1) Median of retrieved documents Term-based: 0 >=50% of the action-topic pairs yield no result OntoNaviERP: % of of the action-topic pairs return at least 5 result pages, of which 2 are relevant 19

23 Results (2) 20

24 Findings and Lessons Learned Understanding of ontology engineering and annotation under economic constraints In our setting, consolidation of synonyms and lexical variants does a great deal of the job 21

25 Future Extensions Task and Context Annotate individual sections of resources Skills / Users Competencies vs. Target Audience of a Resource Hybrid Search: Combining term-based and conceptual search E.g. see Bhagdev/Chapman/Ciravegna, Vitaveska Lanfranchi, Daniela Petrelli: Hybrid Search: Effectively Combining Keywords and Semantic Searches, ESWC

26 Reference and Links Hepp, Martin and Wechselberger, Andreas: OntoNaviERP: Ontologysupported Navigation in ERP Software Documentation, in: A. Sheth et al. (eds.): ISWC Proceedings of the 7th International Semantic Web Conference, Germany, October 26-30, 2008, Karlsruhe, Germany, Springer LNCS, Vol. 5318, pp This paper and other papers are available at The.NT Generator for KIM/GATE Gazetteer Lists is at: 23

27 Thank you! and Andreas Wechselberger { andreas.wechselberger@unibw.de} 24