Workflow Management Kap. 1. Organizing Workflows

Slides:



Advertisements
Similar presentations
Workflow Management Kap. 5. Architecture of Workflows Wil van der Aalst has copyrights to almost all figures in the following slideshow made by Lars Frank.
Advertisements

Software and Systems Engineering Seminar Winter 2011 Domain-specific languages in model-driven software engineering 1 Speaker: Valentin ROBERT.
Workflow Management Kap. 3. Management of Workflows Wil van der Aalst has copyrights to almost all figures in the following slideshow made by Lars Frank.
Workflow Management Kap. 4. Analyzing Workflows Wil van der Aalst has copyrights to almost all figures in the following slideshow made by Lars Frank.
1 C H A P T E R CP3507 – MIS Course Introduction.
The Database Environment
Appendix A The Future of Workflows Wil van der Aalst has copyrights to almost all figures in the following slideshow made by Lars Frank.
McGraw-Hill/Irwin Copyright © 2008, The McGraw-Hill Companies, Inc. All rights reserved.
Principles and Learning Objectives
Information and Decision Support Systems
CHAPTER 10 & 13 IS within the Organization & Acquiring IS and Applications.
Well, Sort-of.
Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
McGraw-Hill/Irwin Copyright © 2008, The McGraw-Hill Companies, Inc. All rights reserved. Electronic Business Systems Chapter 7.
1 Review Topics 1.Basic understanding of a business process 2.The relationship of a business process with a work flow 3.The different types aspects and.
Supporting Managers and (other) Decision Makers
Information and Decision Support Systems
1 Chapter 7 IT Infrastructures Business-Driven Technology
© 2007 by Prentice Hall 1 Chapter 1: The Database Environment Modern Database Management 8 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden.
Principles of Information Systems, Sixth Edition Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
Chapter 1: The Database Environment and Development Process
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
Information and Decision Support Systems
Business Driven Technology Unit 3 Streamlining Business Operations Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution.
Chapter 1: The Database Environment
Mgt 20600: IT Management & Applications Decision Support Systems Tuesday April 18, 2006.
Acquiring Information Systems and Applications
Pinnacle Seven Technologies - Gateway to Solutions Pinnacle Seven Technologies - Gateway to Solutions.
Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
Business systems are computer-based information systems that provide organizations with valuable information in a timely and effective manner to allow.
7 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
New Product Development Management NPDM 11 Mohsen SADEGHI
CHAPTER 1: THE DATABASE ENVIRONMENT AND DEVELOPMENT PROCESS Modern Database Management 11 th Edition Jeffrey A. Hoffer, V. Ramesh, Heikki Topi © 2013 Pearson.
Principles of Information Systems, Sixth Edition Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
Fundamentals of Information Systems, Third Edition2 Principles and Learning Objectives Good decision-making and problem-solving skills are the key to.
Chapter Intranet Agents. Chapter Background Intranet: an internal corporate network based on Internet technology. Typically, an intranet can.
Effective IS Planning: Achieving a Balance Between Ideal and Executable June 25, 2003 NCC Bldg., Diliman Quezon City.
Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
Principles of Information Systems, Sixth Edition Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
7/5: Ch. 2 Fundamentals of IS What is a system? What is an information system?
Chapter 6 Organizational Information Systems
@ ?!.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
Workflow Management introduktion: Wil van der Aalst has copyrights to the slides conserning his book about Workflow Management. However, some of the slides.
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 1: The Database Environment Modern Database Management 9 th Edition Jeffrey A. Hoffer,
Why should a database transaction be atomic?. ABORT = Removal of the updates of a transaction An abort is implemented by a DBMS roll back recovery where.
7-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 7 IT Infrastructures.
BUSINESS DRIVEN TECHNOLOGY
CHAPTER 13 Acquiring Information Systems and Applications.
Chapter 1 Chapter 1: The Database Environment Modern Database Management 8 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden © 2007 by Prentice.
Chapter 10 McGraw-Hill/Irwin Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. Enterprise Resource Planning and Collaboration Systems.
Workflow Management Kap. 6. Roadmap for Workflows = Design of Workflow Systems Wil van der Aalst has copyrights to almost all figures in the following.
1 Database Systems Instructor: Nasir Minhas Assistant Professor UIIT PMAS-AAUR
IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.
Fundamentals of Information Systems, Second Edition 1 Information and Decision Support Systems.
Chapter7 TELECOMMUNICATIONS AND NETWORKS. Content e-Business Systems – Cross-Functional Enterprise Applications – Enterprise Application Integration –
IT and Network Organization Ecommerce. IT and Network Organization OPTIMIZING INTERNAL COLLABORATIONS IN NETWORK ORGANIZATIONS.
1 Slides used in class may be different from slides in student pack Managerial Briefing 13 Enterprise Resource Planning Systems  Enterprise Resource Planning.
Chapter1 FOUNDATIONS OF INFORMATION SYSTEMS IN BUSINESS.
1 BY CHANDRA S. AMARAVADI OVERVIEW OF IS. 2 DEFINITION OF IS A collection of computer systems to support information processing in organizations. A set.
Copyright © 2005 World Batch Forum1 How to use ISA95 part 3 for MES functional URS Jean Vieille
Elaboration popo.
Chapter 8 Environments, Alternatives, and Decisions.
Fundamentals of Information Systems, Sixth Edition
CHAPTER 1 FOUNDATIONS OF IS Subject Name: MANGEMENT INFORMATION SYSTEM
Building Information Systems
MANAGING DATA RESOURCES
IS Theories & Practices
Presentation transcript:

Workflow Management Kap. 1. Organizing Workflows Wil van der Aalst has copyrights to almost all figures in the following slideshow made by Lars Frank.

What are the relationships between KM, Workflows and ERP? Knowledge Management (KM): Provide the way to share and organize strategies, research and development of current systems Work Management: Assist in day-to-day production work, enhance productivity and quality of work Enterprise Resource Planning (ERP): Applications for traditional business activities like accounting, inventory, logistics, sales etc. Source: Martin Ader (2000) Technologies for the Virtual Enterprise

Which management levels can use WFMS?

Routing types example: Routing rules are used to integrate activities and places Routing types example: Settlement = skadesopgørelse. Proceeding = Gå videre. What routing types are missing in the dataflow diagram?

Workflows may be nested. If C is outsourced it is viewed as atomic and its parts are not interesting. Can an e-commerce system be viewed as an outsourced atomic activity?

Example of a Contract tree A principal can outsource a subprocess to a contractor.

Three types of processes/tokens Senere vises at support- og styringsprocesser undertiden kan styres med triggers. The managerial/support process is integrated in the primary process! In the following example you have a human token that manages the primary process. A database state record with the information ”compensatable”, ”pivot”, or ”retriable” is an example of a support process/state.

Petri net with one support/managerial resource: In the example you have a human token that manages the primary process in such a way that the primary process can only handle one token at a time! The managerial process is integrated in the primary process! How can the capacity be extended by using more human pay assistents? Who desides whether the claim is rejected or payed? (Correct the error).

Overview of Process modeling techniques:

Today´s situation (2003):

Activity Execution Activity description Process prog in out

Each workflow activity may use resources Workflow Technology Activity Synch 1 2 Business Process 3 4 5 Decision Does a workflow manage human ressources or can the human ressources manage the workflow?

Workflow versus groupware: Structured processes CSCW Unstructured processes

Grouping of “workflow” applications: High Volume Low Individual Processes Routine/Repeatable Software Development Collaborative Process Management Insurance Claims Production Static Structure Administrative Document Processing Non-critical Groupware Ad hoc Human Intervention Ad-hoc workflows do not have a well-defined process model to follow. The execution path is more or less determined at runtime, and is basically controlled by humans. These are generally not mission critical, and accomplish the flow of information among people within the organization. Production workflows are also predictable and repetitive. They have well defined process models. These usually involve a number of information systems that may be heterogeneous and distributed. Production workflow management systems are thus, more complex and critical than ad-hoc or administrative. Administrative workflows are based on simple, repetitive and predictable processes. The ordering and coordination of tasks can thus be automated. However, these too, like ad-hoc workflows, do not involve complex information processing systems, and are generally not mission critical. Collaborative workflows are characterized by high mission criticality. They are mostly controlled by humans, and lack a well-defined process model. Thus most of the task ordering and coordination is determined at runtime by the workflow participants.

Workflow and groupware products:

Groupware versus Transaction processing:

Aspects of workflow and workgroup computing:

WF Management subsystems: Workflow Management System Build Time Run Time Semantics Syntax Workflow Model Workflow Language Build Time Tools Editor Simulator Animator Debugger Work List EndUser Tools Monitor Analyser Administrator Configurator Functional Components Run Time Tools Implementation Architecture Implementation Model Processes Databases Communication Source: Jablonski and Bussler, 1996

Workflow Implementation Process Business Process Engineering Implementing WF Test System Project Pre-phase Workflow Conceptual Design Developing WF Interfaces Strategic Planning Implementing Production System Production Phase Maintenance Improvement Application Integration Workflow Test Run Source: Scheer, 2000

Workflows is not a new idea, why now? CPI = continuous process improuvement XML

End of session Thank you !!!

Factors and Technologies Workflow Management Email Special DB Communication Systems Video Conferencing Bulletin Board Shared Data spaces Distributed Hypertext Workgroup Computing Planning System Meeting Support Group Editor Coordination Collaboration

Business Activities Any (business) activity has 3 dimensions: Intelligence (< 20 % of total costs) market segmentation; competitive positioning; pricing strategy; service quality benchmarking; identifying potential customers, BI. Operational (~ 10 % of total costs) core business tasks; invoicing; sales transactions; accounting; purchasing; inventory control Production (Up to 85 % of total costs) Handling insurance claims; reviewing applications; meeting with potential customers; writing proposals; ordering goods and services  Knowledge Management  Enterprise Resource Planning  Workflow Management Source: Martin Ader (2000) Technologies for the Virtual Enterprise

Dataflow diagrams: In dataflow diagrams, routing rules that illustrate papallel executinon are missing. In the following the roting rules are described.

Workflow Routing Types B A Begin Sequence And Split E C D Fork And Join Or Split Synchronizer G F Choice Or Join S Merge Do L While Nesting End Synchronizer Iteration Termination