business ontology - integrate knowledge 1/3 an overview
DESCRIPTION
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.TRANSCRIPT
© 2
011
Tie
to C
orpo
ratio
n
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
© 2
011
Tie
to C
orpo
ratio
n
Business ontology 1/3 -
Overview
Business ontology – approach to integrate knowledge for applications
heimo hanninen
Tieto,[email protected]
© 2011 Tieto Corporation
What is ontology in IT system scope?
Enterprise Architect Dmitry Bogachev – Topic Maps 2007
-metadata
© 2
011
Tie
to C
orpo
ratio
n
Why ontology matters
© 2011 Tieto Corporation
Why should we care about organising information?
5 2011-02-09
A CHALLENGE
Our brain will not get any bigger – amount of information will.
© 2011 Tieto Corporation
Corporate information in silos – how to integrate the data?
6 2011-05-11
Local optimization
Global need, but
A CHALLENGE
Partners R&D Production ICT Sales &Marketing
HR
© 2011 Tieto Corporation
Information is Constantly in Motion –- a need for better management
30% of people’s time is spent searching for
relevant information
Only one-third of CFOs believe that the information is easy to
use, tailored, cost-effective or integrated
17% of IT budgets for storage hardware and storage management software and people
More than 60% of CEOs believe their business needs toaccess and understand information faster to make swift decisions
30–50% of design time is copy management
85% of information is unstructured
Documents
Transactions
Customers
Partners
Employees
OrganizationsFinancials
Products
E-mails
Databases
Media
Webcontent
Reports
37% growth of disk storage in 2005
40% of IT budgets may be spent on integrationSource: IBM
A CHALLENGE
Heimo Hänninen
© 2011 Tieto Corporation
Information with metadata
• Data about the content• Suitable metadata for each usage
• Computer likes identifiers
• Human likes descriptions
© 2011 Tieto Corporation Heimo Hänninen / 14.11.2007
Information without metadata
• Have to open all containers to know the content…
A CHALLENGE
© 2
011
Tie
to C
orpo
ratio
n
Some jada jada on ontologySemantic web approach
© 2011 Tieto Corporation
Triangle of meaning: the way we think and communicate with symbols
11 2011-06-17
• “referent”Real world object
• “symbol”Names we give
http://psi.tieto.com/taxonomy/resource/car
<label xml:lang=“se” > bil</label>
• “concept”Subjective understanding of object
CAR
Heimo
<label xml:lang=“fi” > auto</label>
© 2011 Tieto Corporation
Triangle of meaning: different context different meaning
12 2011-06-17
• “referent”Real world object
• “symbol”Names we give
• “concept”Subjective understanding of object
CAR
Nico Rosberg
http://psi.tieto.com/taxonomy/resource/car
<label xml:lang=“en” > racing car</label>
<label xml:lang=“fi” > kilpaauto</label>
© 2011 Tieto Corporation
Levels of Conceptual Interoperability Model
Ref. Virginia Modeling Analysis & Simulation Center:T
OD
AY
© 2011 Tieto Corporation
Towards subject centric computing (semantic web)• PSI: http://psi.ontopedia.net/Subject-centric_computing • 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-03-04
A GO
AL
© 2011 Tieto Corporation
Semantic Web Stack
15 2011-03-04
Learn more from: wikipediaOr DBpedia http://dbpedia.org/page/Semantic_Web_Stack
© 2011 Tieto Corporation
Semantic web today: Linked open data (http://linkeddata.org/ )
16 2011-03-04
READ MO
RE
http://www.w3.org/wiki/DataSetRDFDumps
Try APIs: http://airports.dataincubator.org/airports/EFHK.html
© 2
011
Tie
to C
orpo
ratio
n
Ontology in IT businessApproach to build IM system
© 2011 Tieto Corporation
System development with semantic 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 Maps
4. Analyze and build adapters to sources (mapping)5. Analyze biz app interface and provide methods and6. Create ontology queries and package results for methods
18 2011-03-04
© 2011 Tieto Corporation
Finding critical information assets and mapping them to business objects
Cat1
Cat2
Cat6 Cat5
Cat3
Cat4
1.Biz Process Walk through
2. Describe biz entities, properties and relations in common biz language
3. Identify sources. Understand local glossaries
4. Create mapping from local to global glossary
R&D LogisticsManufac-
turing Marketing Sales
Distri-bution
CustomerSupport
ProductDesign
Cat1
Cat2
Cat6Cat5
Cat3
Cat4
19
Luottamuksellinen
PDM, ERP CMS BI Sales &Marketing
Partner’sdata
CRM
Cat1
Cat2
Cat5
Cat4
Business ontology
Heimo Hänninen
© 2011 Tieto Corporation
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 integrate
documents to BI system 20 2011-03-04
© 2011 Tieto Corporation
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 (it's 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 tools
• Stick to standards and evaluate tools and services. 21 2011-03-04
© 2
011
Tie
to C
orpo
ratio
n
Architectural view
knowledge map layer between sources and business applications
Apps
Ontology service
Sources
Bus
© 2011 Tieto Corporation
Knowledge Map abstraction layer
Enterprise Architect Dmitry Bogachev – Topic Maps 2007
© 2011 Tieto Corporation
Three Layers of Information Architecture
Business Applications
Structures
ERP
projectproductsservice
doc report
staff
IntraEmailsfeeds
User Experience&
Business Processes
IA layers
Conceptual
Logical
Implementation CMS
customer
Semantics
Content Viewers
Contentand Data
Knowledge Map:-business objects
-info in context-across silos
User in situations, a task
at hand
InformationManagement
-metadata
BIG PICTURE
network
community
solution
Heimo Hänninen
© 2011 Tieto Corporation
IM Layers
25 2011-05-03
projecttechnology
service
document
staff
solutioncustomer Business Ontology/Domain model:
-Business entities-With associations and
-Properties-Across domains
Doc type
plans
project
business
risk
process
guide
quality
customer
agreement
report
Technology
Platform
application
communication
Process
business
application
Application
user
developer
management
information
application
Taxonomy:-Categorize
-Hierarchical-Domain specific
Information:-with metadata
-identified-content and data
Direct link
Indirect link
Phase 1 Phase 2 Phase 3 Phase nValue chain:
-Processes
© 2011 Tieto Corporation
Connecting user to biz ontology and information to ontology
Heimo Hänninen26
Start Phase Phase Phase End
Standard structuresLow level semantics
Customer in situations,
Info in context
EventsRules
Targeting Business
logic
ProfileImplicit
Explicit
Content and data
Knowledge map
Publication process
Use context
News
advertisementchannel
editor
sourcematerial
profilecustomer
Advertiser
interest
ERPIntraEmailsfeeds CMS
Extracted metadataLink to resource
Categorization,Ontology
High level semantics