• Like
A Goal-oriented Approach for Business Process Improvement Using Process Warehouse Data.
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

A Goal-oriented Approach for Business Process Improvement Using Process Warehouse Data.

  • 2,884 views
Published

 

Published in Education , Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,884
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
66
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Khurram Shahzad, Jelena Zdravkovic Department of Computer and Systems Sciences, Royal Institute of Technology(KTH) & Stockholm University(SU), Stockholm, Sweden. A Goal-Oriented Approach for Business Process Improvement using Process Warehouse Data 2 nd IFIP Working Conference on The Practice of Enterprise Modeling. (PoEM’09) Stockholm, Sweden 18-19 November, 2009
  • 2. Agenda
    • Background
    • Process Design Framework
    • The Decision Relationship Model (DRM)
    • Using DRM for Process Improvement
    • Healthcare Case Study
    • Conclusion
  • 3. Background
    • Process Analysis is a feedback phase that is
      • Used to evaluate process execution
      • Identification of bottlenecks
      • Improve efficiency
      • Increase productivity of execution
      • Optimize business processes
    • Resources, activities and actors optimization is achieved
    >Background Process Design Framework Decision Relationship Model On Using DRM Healthcare casestudy Conclusion
  • 4. Background
    • Traditional DW is used for analysis and decision making
    • Traditional DW don’t provide necessary information for process analysis
      • Data from OLTP is loaded in DW
      • Execution of activities is missing
      • Utilized resources data is missing
      • Control flow data is missing
    • Consequently, DW cannot be used for analysis and decision making on processes
    • DW is large and analysis requires small data as compare to DW size
    >Background Process Design Framework Decision Relationship Model On Using DRM Healthcare casestudy Conclusion
  • 5. Background
    • Identification of information for analysis & decision making is a complex task
    • Process warehouse (PW) is used for analysis & decision making
    • Business experts depend on IT personnel for extracting information
    • Structured way of making decisions for process improvement is missing
    >Background Process Design Framework Decision Relationship Model On Using DRM Healthcare casestudy Conclusion
  • 6. The Study
    • In this study, we
      • Present a goal based Decision Relationship Model (DRM) for process analysis and improvement
      • Explore DRM based on data from process warehouse
      • A semi-automated procedure for using DRM
        • Guidelines for managing analysis
    >Background Process Design Framework Decision Relationship Model On Using DRM Healthcare casestudy Conclusion
  • 7. Process Design Framework
    • Business process has been identified in various ways.
      • Core: set of activities that executed in an ordered
    • Processes are designed from four perspectives *
      • Functional perspective (what activities)
      • Informational perspective (manipulated resources)
      • Organizational perspective (notation of actors)
      • Behavioral perspective (data flow, activities)
      • Time – additional for analysis
    Background > Process Design Framework Decision Relationship Model On Using DRM Healthcare casestudy Conclusion * Curtis, B., Kellner, M.I., Over. J.: Process Modeling. Communications of ACM 35(9), 75-90 (1992).
  • 8. DRM users
    • Users involved in process analysis and decision making
      • Business experts , define goals of process analysis
      • Decision makers, take improvement decision
      • Technical experts , interact with warehouse
    • DRM reduces the gap between users
      • By providing structured way of decision making
    Background Process Design Framework > Decision Relationship Model On Using DRM Healthcare casestudy Conclusion
  • 9. Design Relationship Model
    • Elements of Decision Relationship Model
    Background Process Design Framework > Decision Relationship Model On Using DRM Healthcare casestudy Conclusion Leaf Goal Business Process Action Decision Decision Associated Information Process Warehouse trace fulfills on leads to requires total information acquired from The Decision Relationship Model
  • 10. Design Relationship Model
    • Leaf Goal
      • A desired state on any of the four process elements (Resources, Actors, Activities, Flow)
      • (Condition on process element)
      • Condition is the desired state
      • Defined by business experts
    • Decision
      • A directive of course of action on resource, actor, activity or flow
      • Result of decision making activity *
      • (Directive on element)
    Background Process Design Framework > Decision Relationship Model On Using DRM Healthcare casestudy Conclusion * Parkash, N. et. al. Information Scenarios for Data Warehouse Requirements Elicitation. Proceedings of ER’04, Springer LNCS Vol. 3288, pp. 205-216.
  • 11. Design Relationship Model
    • Decision Associated Information
      • PW has large amount of data **
      • Information that must be consulted to take a decision
      • Can be used for evaluation of alternative decisions
    • Action
      • Realization or implementation of a decision
      • As a result of action a goal is achieved
    Background Process Design Framework > Decision Relationship Model On Using DRM Healthcare casestudy Conclusion ** more to come
  • 12. On Using the DRM
    • Four step method for using DRM
      • Step 1: Define a goal model
      • Step 2: Identifying DAI
      • Step 3: Decision Elicitation
      • Step 4: Realization of a decision
    Background Process Design Framework Decision Relationship Model > On Using DRM Healthcare casestudy Conclusion DRM Use Cases
  • 13. Step 1: Define Goal model
    • A goal is broken down into sub-goals
    • Sub-goal can be broken further
    • Continue until leaf goals
    • Goals at the same level can have AND, OR or XOR.
    • Goal model is used to
      • Identify target elements
      • Identify a desired state of an element
    Background Process Design Framework Decision Relationship Model > On Using DRM Healthcare casestudy Conclusion Metamodel for Goal Model
  • 14. Step 2: Identify DAI
    • Leaf goals are input
    • DAI is the output
    • PW is a non-volatile DB with large amount of data
    • Analysis requires small amount of data
    • Therefore guidelines are developed
    Background Process Design Framework Decision Relationship Model > On Using DRM Healthcare casestudy Conclusion
  • 15. Step 2: Identify DAI (Guidelines)
      • G1: If goal is a condition on actor, the DAI is organizational and functional information
      • G2: If goal is a condition on resource, the DAI is resource and functional information
      • G3: If goal is a condition on flow, the DAI is control and functional information
      • G4: If goal is a condition on activities, the DAI is organizational, functional, resource and control information
    Background Process Design Framework Decision Relationship Model > On Using DRM Healthcare casestudy Conclusion
  • 16. Step 3: Decision Elicitation
    • Goal and DAI are input
    • Directive of course of action is output
    • Decision maker may not have substantial know to interact with PW
    • Three phase process
      • Identification of alternatives
      • Evaluation of alternatives
      • Selection of alternative
    Background Process Design Framework Decision Relationship Model > On Using DRM Healthcare casestudy Conclusion
  • 17. Step 4: Realization of Decision
    • Directives are realized to achieve goals
    • Directives are realized at two levels
      • Business level
        • From organizational perspective
      • Process level
        • From process modeling perspectives
    Background Process Design Framework Decision Relationship Model > On Using DRM Healthcare casestudy Conclusion
  • 18. Healthcare Case Study Background Process Design Framework Decision Relationship Model On Using DRM > Healthcare casestudy Conclusion Healthcare Process (in BPMN)
  • 19. Healthcare Case Study Background Process Design Framework Decision Relationship Model On Using DRM > Healthcare casestudy Conclusion Healthcare Goal Model Healthcare Process (in BPMN)
  • 20. Healthcare Case Study
    • Goal definition
    • Leaf goal = ‘optimal utilization of doctors availability’
    • Target element = Doctor (actor)
    • Desired State = Optimal use
    • Goal becomes ( optimal use of doctor )
    • DAI identification (using guideline 1)
      • Organizational information
        • Workload, tasks performed, completed & failed tasks, temporal information etc.
      • Functional Information
        • Activities, output, deadlock, cycle-time, failed due to doctor unavailability etc.
    Background Process Design Framework Decision Relationship Model On Using DRM > Healthcare casestudy Conclusion
  • 21. Healthcare Case Study
    • Decision Elicitation
      • Identify alternatives
        • Reschedule doctors’ timing
        • Involve Doctors in diagnosis activities only
      • Evaluation of alternatives
      • Selection of decision
      • “ doctor should not check blood pressure”
    • Realization of Decision
      • Business level
      • Process level
    Background Process Design Framework Decision Relationship Model On Using DRM > Healthcare casestudy Conclusion
  • 22. Conclusion & Future Research
    • Process models are important for designing & structuring activities of an enterprise
    • A model-based approach for analyzing enterprise processes, using the information from a PW
    • Perspectives of process design are used for developing guidelines
      • Are used for identifying relevant information from bulky warehouse
    • Future work
      • Decisions for high level goals
      • Identification of DAI for high level goals
      • Using DAI for complex decisions
      • Semi-automatic way of making decisions
    Background Process Design Framework Decision Relationship Model On Using DRM Healthcare casestudy > Conclusion
  • 23. Questions??