1 / 50

INTEGRATING KNOWLEDGE MODELING IN BUSINESS PROCESS MANAGEMENT

INTEGRATING KNOWLEDGE MODELING IN BUSINESS PROCESS MANAGEMENT. 組別：第六組 組員： M9301407 容怡平 M9401203 李日春 M9401206 吳仁鈞 M9401302 吳啟宏. ABSTRACT. A new approach for integrating Business Process Management and Knowledge Management, focus on the modeling of

tilden
Download Presentation

INTEGRATING KNOWLEDGE MODELING IN BUSINESS PROCESS MANAGEMENT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. INTEGRATING KNOWLEDGE MODELING IN BUSINESS PROCESS MANAGEMENT 組別：第六組 組員：M9301407 容怡平 M9401203 李日春 M9401206 吳仁鈞 M9401302 吳啟宏

  2. ABSTRACT A new approach for integrating Business Process Management and Knowledge Management, focus on the modeling of weakly-structured and knowledge- intensive business process.

  3. OUTLINE 1. INTRODUCTION. 2. MODELLING KNOWLEDGE IN BUSINESS RPOCESS. 3. INTEGRATING KNOWLEDGE TASKS AND KNOWLEDGE OBJECTS IN BUSINESS PROCESSES. 4. AN APPLICATION EXAMPLE. 5. REALTED WORK. 6. CONCLUSIONS AND FURTHER WORK.

  4. 1.INTRODUCTION(1/4) • BPM and BPR have been predominant business trends and are now becoming “serious tools”. • The focus of BPR is typically on studying and changing a variety of factors.

  5. 1. INTRODUCTION (2/4) • Most BPR efforts have not focused much on knowledge, if at all. This is indeed critical, considering that knowledge is treated more and more as a principal success factor – or the major driving force behind business success.

  6. 1. INTRODUCTION (3/4)Knowledge Management efforts • An emphasis is given to the strategic application of knowledge-related initiatives and a focus on creating the right culture and organizational structure that facilitates knowledge sharing and enables knowledge leveraging.

  7. INTRODUCTION (4/4)Integrating consistently knowledge within business processes • The present paper attempts to fill this gap by proposing a new framework and workflow meta-model that treats in an explicit manner knowledge management tasks and knowledge objects.

  8. 2. MODELING KNOWLEDGE IN BUSINESS PROCESSES (1/3) • An analysis of knowledge work shows that knowledge-intensive processes tend to be characterized by dynamic changes of goals, information environment, constraints, and highly individual and ad-hoc communication and collaboration patterns.

  9. 2. MODELING KNOWLEDGE IN BUSINESS PROCESSES (2/3) • Conventional workflow approaches providing a strong structuring mechanism for specification of workflow control are not suited to deal with the ad-hoc effects, frequent exceptions, and common changes in knowledge-intensive work activities.

  10. 2. MODELING KNOWLEDGE IN BUSINESS PROCESSES (3/3) There are several reasons for this: ‧ The knowledge needed for executing the process is not explicitly described in the workflow model. ‧ Current workflow approaches are not flexible enough to adapt on the fly to changing processes.

  11. Business processes can be described as follows ‧Knowledge-intensive: The processes considered are often complex in general, with many, but conceptually simple, document-centred activities. ‧Weakly-Structured: The processes under consideration normally consist of many steps performed by many people in different roles, often several departments are involved, sometimes at different location, etc.

  12. Four core tasks of knowledge management • knowledge generation • Knowledge storage • Knowledge distribution • Knowledge application

  13. Knowledge assets canbe • Human • Structural • Market

  14. The relation between knowledge assets and knowledge objects • Define “knowledge objects” as the means of representing knowledge; then the following statement outlines the relation between knowledge assets and knowledge objects: “A knowledge asset creates, stores and disseminates knowledge objects”.

  15. A knowledge object has characteristics • Is created and maintained by a knowledge management task. • Is used to search, organize and disseminate knowledge content. • Acts as a catalyst, enabling the fusion of knowledge flows between people, with knowledge content discovery and retrieval, through technology. • Facilitates the knowledge transfer from person to person, or from information to person.

  16. 3. INTEGRATING KNOWLEDGE TASKS AND KNOWLEDGE OBJECTS IN BUSINESS PROCESSES (1/3) • Model knowledge-related tasks and knowledge objects • A workflow meta-model • Tasks can be composed into (sub)tasks

  17. 3. INTEGRATING KNOWLEDGE TASKS AND KNOWLEDGE OBJECTS IN BUSINESS PROCESSES (2/3) • Distinguish two types of tasks in the workflow model: • Normal tasks (Tasks). • Knowledge Management tasks (KM tasks). • Each of these role has a set of permissions associated regarding usage of the organization’s resources. • The workflow instance consists of the instances of the Tasks and KM Tasks. • Modeling modifications can be made to a running Task-instance.

  18. 3. INTEGRATING KNOWLEDGE TASKS AND KNOWLEDGE OBJECTS IN BUSINESS PROCESSES (3/3) • The proposed workflow model is an extension of the reference workflow model proposed by the Workflow Management Coalition. • Captures the fundamental elements of the workflow paradigm and their relationships: • Task specification perspective • Organizational perspective • Data perspective • Process logic perspective • Captures the tasks in the process that are associated with the generation, storage, application and distribution of knowledge. • Knowledge perspective

  19. 3.1 Task specification perspective • The task specification perspective deals with the static dimension of workflow modeling. • A workflow task can consist of several (sub)tasks. • Each (sub)task in turn can be further decomposed. • This recursively can result into an arbitrary deep decomposition hierarchy.

  20. 3.2 Organizational perspective • It provides specification constructs for the definition of an organization structure. • Users can be registered and described in more detail by user attributes. • It deals with the assignment of users to workflows at runtime. • Assigning specific persons or resources to a workflow task denotes that this task should be performed by these actors.

  21. 3.3 Data perspective • This perspective focuses on what data objects are used within the workflow models. • A Knowledge object can be seen as a Data object with more attributes necessary for its manipulation by KM Tasks.

  22. 3.4 Process logic perspective (1/2) • It ties together the first three perspectives describing the control and data flow between the workflow tasks. • Active nodes (tasks) and passive nodes (events) are linked to form an Event-driven Process Chain (EPC). • EPCs are extended by links to other relevant entities contributed by the other perspectives. • Tasks can be connected to input and output data that are located in the data perspective to model the data flow between different tasks.

  23. 3.4 Process logic perspective (2/2) • Model the control flow of the business process in the EPC model. • Sequences — link two activities sequentially. • splitters — split into multiple parallel branches. • joiners — parallel branches all have to be executed at the same time (and-split), that only one (xor-split) or some (or-split). • more complex branching (loops) — allows one or more tasks to be repeated until a condition is met.

  24. 3.5 Knowledge perspective • Stress the link between business processes and knowledge management. • It ties together the task specification, the organizational and the data perspective: KM Tasks performed by persons or software agents handling knowledge objects. • Describes the content of knowledge objects by reference to (ontological) concepts. • Different concepts are connected by links and are grouped into views.

  25. 4. An application example • In order to demonstrate the practicality of our approach we have developed a modeling tool that incorporates the theoretical aspects of our framework. • We developed the tool as an integration of the commercial tool MS Visio 2000 and CognoVision. • We tested our approach in an organisation from the social security sector: the Greek Social Security Institute (IKA), which is the largest insurance institution in Greece.

  26. 4.1 Description of the business process(1/1) • The business process that was examined and modeled with our tool is the granting of full old age pension. • The pension granting process requires a deep knowledge of the relevant legislation; first for making the decision whether the insured person is entitled to receive a pension; and second for calculating the amount of pension.

  27. 4.1 Description of the business process(1/1) • The process begins with the submission of the application form by the insured person and the collection of all the supplementary documentation, which constitutes the retirement folder.

  28. 4.1 Description of the business process(1/2) • The pension folder is being checked at the department of pensions or the department of payments. • The decision regarding the entitlement to a pension is made on the basis of the employment and personal data of the insured person. • This decision is based also on the current legal regulations, which are differentiated according to the pension type, the category of the insured person and other factors.

  29. 4.2 Task specification • The first thing to do when developing the workflow model for the selected business process is to define which tasks are involved in the business process and decompose them into subtasks. • Starting from some generic tasks that roughly describe the business process, the workflow developer defines the decomposition into more detailed subtasks which in turn can represent a whole workflow. • This decomposition continuous until the desired level of details is obtained.

  30. 4.3 Process logic • Having specified the tasks involved in the business process as well as their decomposition into more detailed subtasks, the next thing to do is to connect these tasks using control flow elements (sequence,and, or, xor, etc) forming the process chain.

  31. 5.RELATED WORK • To the best of our knowledge ,in the area of Knowledge Management only few approaches have explicitly acknowledged the relation between knowledge management and business processes. • And even fewer approaches have tired to develop a systematic method to integrate knowledge management activities into the business processes .

  32. CommonKADS methodology Schreiber et al (1999)

  33. meta-level activity consists of a cyclic exertion of three main activities: • Conceptualise • Reflect • Act

  34. The knowledge object level is defined by three objects • agents as persons or software that possess • knowledge assets • business processes

  35. knowledge management cycle • Identify • plan • develop • distribute • foster the application • control and maintain • dispose

  36. Knowledge value chain Weggeman (1998)

  37. six knowledge management taskson the operational level: • identify the required knowledge • document the available knowledge • develop • share • apply and evaluate knowledge

  38. Eight building blocks to manage knowledge Probst et al. (1998)

  39. Eight building blocks • knowledge goals • knowledge identification • acquisition • development • sharing • utilization • retention • assessment

  40. The model-based knowledge management approach Allweyer (1998)

  41. The approach aims to the description of required and used knowledge as well as generated and documented knowledge. • The approach claims to support the structuring of knowledge into categories and the construction of a knowledge map to locate who knows what inside the organization.

  42. advantage： • easy-to understand pictograms are proposed to help users describe the use of documented and tacit knowledge within their business processes. shortcoming ： • It does not make explicit how to integrate the knowledge management activities into business processes. • It does not provide any criteria to analyse and improve the knowledge processing within the business process.

  43. model-based design of knowledge-oriented processes Warnecke et al (1998).

  44. Five basic knowledge management activities • identify • make explicit • distribute • apply • store

  45. The lack of emphasis on the importance of the sequencing of the basic knowledge management activities overlooks the fact that one important weakness in existing business processes is the lack of connectivity between these basic activities. • A possible barrier for the application of the reference model is the translation of real world tasks into the specific notation of the model. This might lead to additional effort and misunderstandings between the modelling expert and the process owner.

  46. Business Process orientedKnowledge Management Karagiannis et al (2000)

  47. Five steps • Strategic Decisions • Knowledge Management Process (KMP) Analysis • KMP and Oranisation Memory (OM) Modelling • Specification • Implementation

  48. CONCLUSIONS • Describes a novel approach for integrating knowledge tasks and knowledge objects within business process models. This integration is achieved by explicitly incorporating knowledge tasks and knowledge objects into the business process model. • The knowledge tasks deal with the creation, storage, distribution and application of knowledge required for achieving the goal of the business process.

  49. 報告結束謝謝

More Related