Ontology Ontology-based Methodology for based Methodology for - - PowerPoint PPT Presentation

▶
ontology ontology based methodology for based methodology
SMART_READER_LITE
LIVE PREVIEW

Ontology Ontology-based Methodology for based Methodology for - - PowerPoint PPT Presentation

Nov 29, 2023 293 likes •538 views

Ontology Ontology-based Methodology for based Methodology for Collaborative Process Definition of Collaborative Process Definition of Enterprise Networks Enterprise Networks V. Rajsiri, JP. Lorr EBM WebSourcing, Ramonville St-Agne,

slide-1
SLIDE 1
  • 1-

Ontology Ontology-based Methodology for based Methodology for Collaborative Process Definition of Collaborative Process Definition of Enterprise Networks Enterprise Networks

  • V. Rajsiri, JP. Lorré

EBM WebSourcing, Ramonville St-Agne, 31520,France

  • F. Bénaben, H. Pingaud

Ecole des Mines d’Albi-Carmaux, Centre de Génie Industriel, Albi, 81000, France

IFAC World Congress - Seoul – Korea – July 10, 2008

slide-2
SLIDE 2
  • 2-

Outline

  • Scope of the study
  • Collaborative Ontology
  • Collaborative Process Ontology
  • Design rules for the collaborative process generation
  • Conclusions and perspectives
slide-3
SLIDE 3
  • 3-

Physical Layout Logical layer Business Layer (requirements)

Knowle ledge about colla laborati tion ne netw tworks Specific ic ne netw twork colla laborati tion mod model BPM BPMN model l of a colla laborati tive pro rocess (CP (CP) UML me mediati tion inf nformati tion sys syste tem model l (M (MIS model) l) Co Config igurati tion model for r the MIS layout usi using an n ESB so solution n

Scope of our presentation in the MISE project

MIS

Rajsiri PhD (2006-2009) Touzi PhD (2004-2007) Touzi Post Doc (2007-2008)

slide-4
SLIDE 4
  • 4-

The expected result

slide-5
SLIDE 5
  • 5-

Collaborative Network Ontology (CNO)

  • « Ontology is a formal explicit specification of a shared conceptualization

for a domain of interest. It contains a set of concepts relevant in a given domain, their definitions and relationships » (Gruber, 1993)

  • Concepts
  • Features of collaborative network
  • Features of collaborative process
  • Deduction rules
  • Process instances come from an OWLized version of the MIT Process

Handbook http://www.ifi.uzh.ch/ddis/ph/2006/08/

Collaborative process ontology Collaboration ontology

Rules

CNO

slide-6
SLIDE 6
  • 6-

Outline

  • Scope of the presentation
  • Collaborative Ontology
  • Collaborative Process Ontology
  • Design rules for the collaborative process generation
  • Conclusions and perspectives
slide-7
SLIDE 7
  • 7-
  • Relationship of collaboration (Fombrun and al., 1982)
  • Vertical (supply-chain), horizontal (concurrence), group
  • f interest
  • Components of network (Poulin and al., 1984)
  • Network, node (participant), link, relationship, flow
  • Network topologies (Katzy & Löh, 2003)
  • Star, Peer-to-peer, Chain
  • Configuration factors of network (Zaidat, 2005)
  • Objective, duration, relationship, partner, role,

connectivity, organizational structure, …

  • On reference models for collaborative networked
  • rganizations (CAMARINHA-MATOS and al.,International

Journal of Production Research,,Vol. 46, No. 9, 1 May 2008, 2453–2469)

  • Enterprise modelling for networked organisations

Litterature references on Enterprise Collaboration

Collaborative process ontology Collaboration

  • ntology

Rules

Collaboration Ontology (1)

slide-8
SLIDE 8
  • 8-
  • Participant can be an individual or an enterprise.
  • Collaborative network is a set of participants who would like to work together

in respond to one or multiple common goals and a set of relationships between the participants.

  • Role defines the responsibility of participant in the network.
  • Common goal describes the reason why the network does exist.
  • Abstract service is a high level service that explains the competencies or the

know-how of the participant.

  • Relationship defines the existing of interaction between two participants.
  • Topology describes the relationships between partners at high level.
  • Power describes the behavior and the orientation of decision-making in the

network.

  • Duration describes the frequency of interactions occurred during the

collaboration in the network.

Collaboration Ontology (2)

Collaborative process ontology Collaboration

  • ntology

Rules

slide-9
SLIDE 9
  • 9-

Collaboration ontology

  • Deduction Rules:
  • Role ↔ Abstract service
  • Power & Duration → Topology Type

Collaborative network contain Common Goal participant Abstract services topology role relationship power duration has has play achieve perform Is performed by provide has has P1 has

A Purchase materials & supplies Acquire resources… Buyer

central equal hierarchic continuous discontinuous chain P2P star kindOf chain hierarchic continuous P2

Collaborative process ontology Collaboration

  • ntology

Rules

Collaboration Ontology (3)

slide-10
SLIDE 10
  • 10-

Outline

  • Scope of the presentation
  • Collaborative Ontology
  • Collaborative Process Ontology
  • Design rules for the collaborative process generation
  • Conclusions and perspectives
slide-11
SLIDE 11
  • 11-

Some references on collaborative process

  • Modelling of collaborative or cross organisational processes (Touzi, 2007) 

Target Model

  • definition and components of collaborative process oriented
  • MIT Process Handbook
  • developed over 10 years at the MIT
  • includes over 5,000 entries:
  • MIT business activity model (buy, make, sell…)
  • Coordination processes (manage by market with bidding…)
  • Case examples (supply chain, e-business…)
  • Activity categories (produce, deploy, provide, modify…)
  • Dependencies (flow of information…)
  • Resources (human agent, software agent, location…)
  • http://ccs.mit.edu/ph
  • OWL MIT Process Handbook
  • developed at the University of Zurich to test their Semantic Web applications
  • an OWLized version of the MIT Process Handbook containing:
  • an ontology schema file (ProcessHandbook.owl)
  • approximately 8000 business processes which are stored in their own files.
  • http://www.ifi.unizh.ch/ddis/ph-owl.html

Collaborative Process Ontology (1)

Collaborative process ontology Collaboration

  • ntology

Rules

slide-12
SLIDE 12
  • 12-

Abstract Service Business Service

Rule: Abstract → Business services

Category of the Abstract Service

Collaborative Process Ontology (2)

Collaborative process ontology Collaboration

  • ntology

Rules

slide-13
SLIDE 13
  • 13-
  • Business service explains task at a functional level. An abstract service is

composed of some business services.

  • Coordination service is in charge of coordinate the dependency by managing its

resource.

  • MIS service is considered as a coordination service.
  • Resource can be machine, software, tool or material used or produced by

business service.

  • Dependency between business services (message flow) is a flow from a business

service to another when they have a resource in common. The two business services linked by this kind of flow do belong to different participants.

  • Dependency between CIS services (sequence flow) is a flow from a MIS service to

another when they have a resource in common. It is like the movement of resource between MIS services.

Collaborative Process Ontology (3)

Collaborative process ontology Collaboration

  • ntology

Rules

slide-14
SLIDE 14
  • 14-

Collaborative process ontology

  • Deduction Rules:
  • Abstract service ↔ Business service
  • Resource (P1.B.input = P2.B.output) → Dependency
  • Dependency → Coordination service → MIS service

Abstract services Dependency b/w services

  • f different participants

(message flow) Dependency b/w CIS services (sequence flow) Coordination service Business service MISservice * generic specific resource Is composed of has input has output manage is a from to coordinate is coordinated by from to

Identify needs Place order Select supplier Receive Pay Purchase materials & supplies Acquire resources… Place order (output = PO) Obtain order (input = PO) Manage flow of document Manage flow of document

coordinate is coordinated by

A B Place order Obtain order PO Manage flow

  • f document

Collaborative Process Ontology (4)

Collaborative process ontology Collaboration

  • ntology

Rules

slide-15
SLIDE 15
  • 15-

Outline

  • Scope of the presentation
  • Collaborative Ontology
  • Collaborative Process Ontology
  • Design rules for the collaborative process generation
  • Conclusions and perspectives
slide-16
SLIDE 16
  • 16-
  • 5 groups of rules:
  • role and abstract service (Petersen, 2005)(Fox et al., ???)

Participant(?x) ^ playRole(?x, ?y) ^ performAService(?y, ?z) → provideAService(?x, ?z)

  • links between role and abstract service
  • abstract and business service (Process Handbook online)

Participant(?x) ^ provideAService(?x, ?y) ^ hasBusinessService(?y, ?a) → provideBusinessService(?x, ?a)

  • Links between abstract and business service
  • dependency, coordination service and CIS service (Malone et al., Chapter

3: A Taxonomy of Organizational Dependencies and Coordination Mechanisms)

CNetwork(?a) ^ hasRelationship(?a, ?z) ^ P1(?z, ?y) ^ provideBusinessService(?y, ?c) ^ hasOutput(?c, ?d) ^ P2(?z, ?x) ^ provideBusinessService(?x, ?b) ^ hasInput(?b, ?d) ^ CoordinationService(?f) ^ manageResource(?f, ?d) ^ Dependency (?e) → fromBusinessService(?e, ?c) ^ toBusinessService(?e, ?b) ^ containResource(?e, ?d) ^ isCoordinatedBy(?e, ?f) ^ hasCISservice(?a, ?f) ^ CISservice(?f)

  • links between input of a business service and output of another business service belonging to the different participants
  • links between resource managed by a coordination service and the common resource

Collaborative process ontology Collaboration

  • ntology

Rules

Design rules for CP generation (1)

slide-17
SLIDE 17
  • 17-
  • 5 groups of rules (cont.):
  • common goal (not implemented)

CommonGoal(?x) ^ description(?x, ?a) ^ swrlb:substringBefore(?y, ?a, " ") ^ AbstractService(?b) ^ name(?b, ?c) ^ swrlb:containsIgnoreCase(?c, ?y) → composedAService(?x, ?b)

  • links between the description of goal and the name of abstract service.
  • topology

Topology(?x) ^ hasPower(?x, central) ^ hasDuration(?x, continuous) → hasType(?x, star)

  • Deduction of the type of topology from the characteristics of decision-making power and duration of collaboration

Collaborative process ontology Collaboration

  • ntology

Rules

Design rules for CP generation (2)

slide-18
SLIDE 18
  • 18-

Network characterization BPMN collaborative process model Collaborative process ontology Collaboration ontology

Rules

CNO Collaboration pattern knowledge

XSL

ATL

SPARQL Network Editor Collaborative Process Editor Instances Deduction rules Specific collaboration patterns (XML) BPMN Editor 2) Collaboration pattern deduction 1) Knowledge gathering 4) BPMN construction 3) Specific collaborative process extraction

manuel and automatic complements

SWRL Editor and Jess engine (plug-in Protégé) XSL

An open source based prototype (1)

slide-19
SLIDE 19
  • 19-

An open source based prototype (2)

slide-20
SLIDE 20
  • 20-

An open source based prototype (3)

slide-21
SLIDE 21
  • 21-

Outline

  • Scope of the presentation
  • Collaborative Ontology
  • Collaborative Process Ontology
  • Design rules for the collaborative process generation
  • Conclusions and perspectives
slide-22
SLIDE 22
  • 22-

Model driven engineering

  • f MIS

A multifold view of Model Driven Interoperability