Business ontology - integrate knowledge 1/3 An overview


Published on

Introduction to business ontology. I tried to explain in simple terms how conceptual data model above your information sources can ease the management. Also, having a knowledge mapped on information allows you to do more interesting processing and targeting of information. Information discovery - "see also" or "surprise me" becomes a trivial task.

Published in: Education, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Brain will not get bigger – amount of information will
  • semantic interoperability into contextUseful framework for discussing solutions
  • Development of Ontology driven system is like any other dev, except perhaps one thing: focus is on subject centric computing. = system development with semtect approach
  • Top down – bottom up
  • Biz case requires a large understanding or business needs, application landscape, integration challenges, data sources and interfacesLack of risk taking in times when you should innovate and generate new type of business?
  • Ref. Forrester: Simplifying Information Architecture Creating An IA Program That Works,7211,37385,00.html
  • Business ontology - integrate knowledge 1/3 An overview

    1. 1. Business ontology – approach to integrate knowledge for applications. Set of presentations: 1. Overview (why, what, how) 2. Creating a business ontology (data modeling case study) 3. Semantic technology & Reference cases© 2011 Tieto Corporation
    2. 2. Business ontology 1/3 - Overview Business ontology – approach to integrate knowledge for applications© 2011 Tieto Corporation heimo hanninen Tieto,
    3. 3. What is ontology in IT systemscope? -metadataEnterprise Architect Dmitry Bogachev – Topic Maps 2007 © 2011 Tieto Corporation
    4. 4. © 2011 Tieto Corporation matters Why ontology
    5. 5. Why should we care aboutorganising information? Our brain will not get any bigger – amount of information will.5 © 2011 Tieto Corporation 2011-02-09
    6. 6. Corporate information in silos –how to integrate the data?Partners R&D Production ICT HR Sales & Marketing6 © 2011 Tieto Corporation 2011-05-11
    7. 7. Information is Constantly in Motion –- a need for better managementMore than 60% of CEOs Only one-third of CFOsbelieve their business needs to believe that the informationaccess and understand information is easy to use, tailored,faster to make swift decisions cost-effective or integrated Transactions Employees Customers85% of information 30–50% of design timeis unstructured Products Partners is copy management Databases Organizations 17% of IT budgets E-mails Financials Web 30% of people’s time for storage hardware content is spent searching for and storage management Documents relevant information software and people Reports Media 40% of IT budgets 37% growth of disk storage may be spent on integration in 2005 Source: IBM Corporation Hänninen © 2011 Tieto Heimo
    8. 8. Information with metadata • Human likes descriptions• Data about the content• Suitable metadata for each usage • Computer likes identifiers © 2011 Tieto Corporation
    9. 9. Information without metadata • Have to open all containers to know the content… © 2011 Tieto Corporation Heimo Hänninen / 14.11.2007
    10. 10. Some jada jada on ontology Semantic web approach© 2011 Tieto Corporation
    11. 11. Triangle of meaning: the way we thinkand communicate with symbols CAR • “concept” Subjective understanding of object Heimo resource/car <label xml:lang=“se” > bil</label> <label xml:lang=“fi” > • “referent” • “symbol” auto</label> Real world object Names we give11 © 2011 Tieto Corporation 2011-06-17
    12. 12. Triangle of meaning: different context different meaning CAR • “concept” Subjective understanding of object Nico Rosberg resource/car <label xml:lang=“en” > racing car</label> <label xml:lang=“fi” > • “referent” • “symbol” kilpaauto</label> Real world object Names we give12 © 2011 Tieto Corporation 2011-06-17
    13. 13. Levels of ConceptualInteroperability Model Ref. Virginia Modeling Analysis & Simulation Center: TODAY © 2011 Tieto Corporation
    14. 14. Towards subject centriccomputing (semantic web)• PSI:• PSD: Subject-centric computing is a branch of computing theory and practices which emphasizes the primacy of subjects (and their interrelationships) in all forms of information and knowledge management, human-computer interaction, and operating system design. Its proponents claim to be realizing Vannevar Bush’s 1945 vision of computing “as we may think”.• (Every)Thing has • published subject identity (PSI) and • published subject descriptor (PSD) attached• Information about a Thing can be then found, ”understood” and merged etc.14 © 2011 Tieto Corporation 2011-03-04
    15. 15. Semantic Web StackLearn more from: wikipediaOr DBpedia © 2011 Tieto Corporation 2011-03-04
    16. 16. Semantic web today: Linked opendata ( )Try APIs: © 2011 Tieto Corporation 2011-03-04
    17. 17. Ontology in IT business Approach to build IM system© 2011 Tieto Corporation
    18. 18. System development withsemantic technology approachUnderstanding semantics of biz entities and taking good care of managing identities of entities and information related.1. Understand business process2. Extract info objects needed in process: • Entities, • their relationship, • properties and • info resources (links to docs)3. Model the formal ontology in W3C: RDF/OWL or ISO: Topic Maps4. Analyze and build adapters to sources (mapping)5. Analyze biz app interface and provide methods and6. Create ontology queries and package results for methods18 © 2011 Tieto Corporation 2011-03-04
    19. 19. Finding critical information assets and mapping them to business objects1.Biz Process Product Manufac- Distri- Customer Walk through R&D Design Logistics turing Marketing Sales bution Support2. Describe biz entities, properties and relations Cat1 Cat1 Cat4 Cat4 Cat2 in common biz Cat3 Cat6 Cat2 Cat5 Cat4 Cat1 Cat5 language Cat2 Cat3 Cat5 Cat6 Business ontology4. Create mapping from local to global glossary3. Identify sources. PDM, ERP CMS CRM BI Sales & Partner’s Marketing data Understand local glossaries Heimo Hänninen Luottamuks ellinen © 2011 Tieto Corporation 19
    20. 20. Why ontology in IM?• one stop shopping for "knowledge intense" logic  consistent and holistic view for users• Add metadata and semantics  findability, reuse of info• biz logic in service component,  reuse of logic• layered architecture, decoupling sources and biz apps  secure investments• extendable, flexible information integration • mapping local glossaries to common, virtually any domain can be integrated (vs. MDM thinking) • more and more external data sources available (open linked data)  secure investments and evolution friendly• powerful query languages covering local ontology plus external sources (end points) discovers “hidden knowledge”• knowledge in std format,  safe to own and share• unstructured information gets metadata  integrate20 documents to BI system © 2011 Tieto Corporation 2011-03-04
    21. 21. Faced problems in the real world• Poor data quality of sources • Bad or missing metadata, no identifiers, ad hoc field naming etc.• Security mgt. • do you have to copy ACL or request it while user runs a query?• Performance • if running complex queries, if carrying on access management• Governance • difficult to define, who owns centralized knowledge service (its not CMS, nor DW, nor CRM, nor PDM but can benefit from those all). • Usage: everyone want to ride on a bus but nobody wants to run the bus company.• Ontology is redundant metadata about data in other systems. • Not good for real time critical systems. Virtual ontology engine which reads data directly from source is not here yet.• Ontology may get out-dated, out of synch of business pulse • World around evolves, so does business and information  evolve your ontology • Based on evolution theory, a mechanism of mutations and natural selection should be built in • Difficult to calculate the business case, often no quick wins on table• Not in the ICT main stream • Educate and lobby managers, train developers to use semantic technologies• Limited number or mature tools21 • Stick to standards © 2011 Tieto Corporation and evaluate tools and services. 2011-03-04
    22. 22. Apps Architectural Bus Ontology service view Sources knowledge map layer between sources and business applications© 2011 Tieto Corporation
    23. 23. Knowledge Map abstraction layerEnterprise Architect Dmitry Bogachev – Topic Maps 2007 © 2011 Tieto Corporation
    24. 24. Three Layers of Information Architecture User in situations, a task User Experience at hand & Business Applications Content ViewersBusiness Processes customer community network solution Knowledge Map: service products -business objects Conceptual staff project -info in context doc report -across silos Information Logical Structures Semantics Management -metadata Content Implementation feeds Emails Intra ERP CMS and Data IA layers Heimo Hänninen © 2011 Tieto Corporation
    25. 25. IM Layers Value chain: Phase 1 Phase 2 Phase 3 Phase n -Processes customer solution Business Ontology/Domain model: -Business entities service technology -With associations and staff project -Properties document Indirect link -Across domains Doc type Technology Direct link plans process customer Taxonomy: Platform Process Application management -Categorize project guide agreemen t -Hierarchical application business user information -Domain specific business quality report communication application developer application risk Information: -with metadata -identified -content and data © 2011 Tieto Corporation 25 2011-05-03
    26. 26. Connecting user to biz ontology and information to ontology Customer in situations, Profile Use context Implicit Info in context Explicit Events Publication process Start Phase Phase Phase End Rules interest Targeting Business customer profile Categorization, Knowledge map logic advertisement Ontology channel High level semantics News editor Advertiser material source Standard structures Link to resource Extracted metadata Low level semantics Content and data feeds Emails Intra ERP CMS26 © 2011 Tieto Corporation Heimo Hänninen