Business Process Management (BPM) Lecture 1: Introduction Dr Adnan M. Albar IS Dept., FCIT King Abdulaziz University.

Slides:



Advertisements
Similar presentations
Welcome to the Montreal MIS Tutorial. MIS Tutorial What is an MIS What is the MIS role in JDF Introduction Gray Boxes MIS Requirements – Job Costing.
Advertisements

Business Process Modelling - 1.2/ Marcello La Rosa Queensland University of Technology Brisbane, 25 July 2013.
BUSINESS PLUG-IN B2 Business Process.
Integration-centric implementation of BPM in Financial Services.
MTAT Business Process Management Lecture 1 – Introduction
Systems Analysis. We we came from… Planning Analysis Design Implementation Identify Problem/Value. Feasibility Analysis. Project Management.
Business Process Reengineering & Innovation Chou-Hong Chen, Ph.D Professor of MIS School of Business Administration Gonzaga University Spokane, WA
Marlon Dumas marlon.dumas ät ut . ee
MIS 325 PSCJ. 2  Business processes can be quite complex  Process model: any abstract representation of a process  Process-modeling tools provide a.
Corporate Service Review DEPARTMENT OF BUSINESS AND EMPLOYMENT.
Marlon Dumas marlon.dumas ät ut . ee
Business Process Reengineering & Innovation Jason Chen School of Business Administration Gonzaga University Spokane, WA 99223
Industrial Revolution’s Model of Organization and Production
Chapter 14 Contemporary cost management. Cost management §Improvement of an organisation’s cost effectiveness through understanding and managing the real.
Unit Five – Transforming Organizations
Presentation Title: Utilizing Business Process Management (BPM) and Enterprise Architecture (EA) to Achieve and Maintain a Competitive Advantage Presented.
Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
Business Plug-In B2 Business Process.
Business process management (BPM) Petra Popovičová.
Business Process Management: The Third Wave The Next 50 Years of IT.
Information Technology Management
Business process modelling with process maps Study material for October 10th and 17th Dr. Mojca Indihar Štemberger, Associate Professor.
1 Reengineering Work: Don't Automate, Obliterate Michael Hammer Harvard Business Review, July-August, 1990, pp 授課老師 : 林娟娟 教授 報告學生 : 黃俊銘 學 號 :
Managing the development and purchase of information systems (Part 1)
Week 5: Business Processes and Process Modeling MIS 2101: Management Information Systems.
Marlon Dumas marlon.dumas ät ut . ee
MTAT Business Process Management (BPM) Lecture 1: Introduction
Marlon Dumas marlon.dumas ät ut . ee
Marlon Dumas marlon.dumas ät ut . ee
Marlon Dumas marlon.dumas ät ut . ee
Chapter 8 Business Processes.
CSS 496 Business Process Re-engineering for BS(CS)
We provide web based benchmarking, process diagnostics and operational performance measurement solutions to help public and private sector organisations.
The Implementation of BPR Pertemuan 9 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
ERP Implementation Lifecycle
MTAT Business Process Management (BPM) (for Masters of ETM) Lecture 2: Process Analysis & Re-Design Marlon Dumas marlon.dumas ät ut. ee.
Department of Computer Science 1 CSS 496 Business Process Re-engineering for BS(CS) Chapter 1: Introduction Khurram Shahzad Based.
Reengineering Work: Don’t Automate, Obliterate Jason C.H. Chen, Ph.D. Professor of MIS School of Business Administration Gonzaga University Spokane, WA.
MTAT Business Process Management Lecture 6 – Quantitative Process Analysis II Marlon Dumas marlon.dumas ät ut. ee 1.
Copyright © 2016 Curt Hill Enterprise Systems Doing the routine work.
MTAT Business Process Management Lecture 7 – Process Redesign 1 Marlon Dumas marlon.dumas ät ut. ee 1.
MTAT Business Process Management Lecture 1 – Introduction Marlon Dumas marlon.dumas ät ut. ee 1.
1 BIS 3106: Business Process Management (BPM) Lecture Eight: Quantitative Process Analysis (1) Makerere University School of Computing and Informatics.
Lecture 9: Business Process Modeling Notation Dr. Taysir Hassan December 17, 2015 INF411 Information Engineering Information Systems Dept. Faculty of Computers.
Information Systems in Organizations Running the Business: Enterprise Systems (ERP)
UNIT - II BUSINESS PROCESS REENGINEERING
Marlon Dumas marlon.dumas ät ut . ee
Information Technology Management
Business process management (BPM)
Request-to-Resolve Scenario Overview
BUSINESS PLUG-IN B2 Business Process.
Automate Does Not Always Mean Optimize
TECHNOLOGY PLUG-IN T12 BUSINESS PROCESS.
BUSINESS PLUG-IN B2 Business Process.
IS4440 Business Process Management (BPM) Lecture 1: Introduction
Владимир Гусаров Директор R&D, Dell Visual Studio ALM MVP ALM Ranger
Business process management (BPM)
MTAT Business Process Management Lecture 8 – Process Redesign 1
BUSINESS PLUG-IN B2 BUSINESS PROCESS.
Request-to-Resolve Scenario Overview
Business Process Redesign
MTAT Business Process Management Lecture 8 – Process Redesign 1
Customer Contract Management Scenario Overview
Order-to-Cash (Project-Based Services) Scenario Overview
Request-to-Resolve Scenario Overview
Fundamental Test Process
Customer Contract Management Scenario Overview
Order-to-Cash (Project-Based Services) Scenario Overview
Request-to-Resolve Scenario Overview
Presentation transcript:

Business Process Management (BPM) Lecture 1: Introduction Dr Adnan M. Albar IS Dept., FCIT King Abdulaziz University

About This Course Objective: –To introduce the principles and methods of Business Process Management and Enterprise Resource Planning Systems. The course relates to: –Enterprise System Integration Integrating applications to automate or support business processes –Data mining Mining business process execution logs –Software Economics Business case analysis: Benefit assessment of IT projects

Structure of the course 7 lectures covering: –Principles of BPM –Process Modeling Using BPMN –Process Analysis (Qualitative and Quantitative) –Process Automation –Process Monitoring and Mining 7 lectures covering: –Principles of ERP –ERP implementation lifecycle –ERP types –Business Processes and ERP Team Project with openERP and KAU BP.

What is a (Business) Process? Collection of related events, activities and decisions, that involve a number of actors and resources, and that collectively lead to an outcome that is of value to an organization or its customers. Examples: Order-to-Cash Procure-to-Pay Application-to-Approval Claim-to-Settlement Fault-to-Resolution (Issue-to-Resolution)

fault-report-to-resolution process “My washing machine won’t work!” VALUE Customer Warranty? Parts Store Service Dispatch Technician CustomerCall CentreCustomer © Michael Rosemann

Processes and Outcomes Every process leads to one or several outcomes, positive or negative –Positive outcomes deliver value –Negative outcomes reduce value Fault-to-resolution process –Fault repaired without technician intervention –Fault repaired with minor technician intervention –Fault repaired and fully covered by warranty –Fault repaired and partly covered by warranty –Fault repaired but not covered by warranty –Fault not repaired (customer withdrew request)

What is a Business Process: Recap

BPM: What is it? Body of principles, methods and tools to design, analyze, execute and monitor business processes In this course, we will focus on BPM based on process models.

Why BPM? “The first rule of any technology used in a business is that automation applied to an efficient operation will magnify the efficiency. The second is that automation applied to an inefficient operation will magnify the inefficiency.”

Why BPM? Information Technology Process Change Yields Business Value Index Group (1982) Enables

How to engage in BPM? Continuous Process Improvement (CPI) Does not put into question the current process structure Seeks to identify issues and resolve them incrementally, one step at a time and one fix at a time Business Process Re-Engineering (BPR) Puts into question the fundamental assumptions and principles of the existing process structure Aims to achieve breakthrough, for example by removing costly tasks that do not directly add value

The Ford Case Study (Hammer 1990) Ford needed to review its procurement process to: Do it cheaper (cut costs) Do it faster (reduce turnaround times) Do it better (reduce error rates) Accounts payable in North America alone employed > 500 people and turnaround times for processing POs and invoices was in the order of weeks

The Ford Case Study Automation would bring some improvement (20% improvement) But Ford decided not to do it… Why? a)Because at the time, the technology needed to automate the process was not yet available. b)Because nobody at Ford knew how to develop the technology needed to automate the process. c)Because there were not enough computers and computer-literate employees at Ford. d)None of the above

The correct answer is … Mazda’s Accounts Payable Department

How the process worked? (“as is”)

Reengineering Process (“to be”)

The result… 75% reduction in head count Material control is simpler and financial information is more accurate Purchase requisition is faster Less overdue payments  Why automate something we don’t need to do? Automate things that need to be done.

How to engage in BPM? 1.Process identification and opportunity assessment 2.Process discovery (as-is) 3. Process analysis 4. Process re-design (to-be) 5. Process implementation 6. Process monitoring/controlling Process Modeling Tools Process Management Systems

Process Identification Core processes Support processes Management processes Quote handling Product delivery Invoice handling Detailed quote handling process

Phase 1: Performance Measure Identification and Selection Cost per execution Resource utilization Waste Cost Cycle time Waiting time Non-value- adding time Time Error rates SLA violations Customer feedback Quality

Phase 2: Process Discovery

Phase 3: Analysis Qualitative analysis Root-cause analysis PICK charts Issue register Quantitative Analysis Flow analysis Queuing analysis Process simulation

Issue Register Issue No. Short Description Issue ExplanationBroad ConsequenceAssumptionsImpact 2 Information regarding units does not match Units in Relocation system do not match information provided by... Wrongly calculated entitlements cause manual calculation... 5% of cases go to the wrong queue, 5 minutes to sort queue and redirect. 5% recalculating on average 10 minutes per calculation. 28,000x0.05x1 5 = 21,000 minutes 350 hours/ hrs 9.5 working days 5 Protected/ Mandatory data entry fields Not all fields in data entry forms are relevant but mandatory. So "fuzzy" information is entered Resource intensive, incorrect data. Cases in Clarify need to physically be closed. 5% of cases taking 2 minutes to locate and close. 5% of relocations requiring entry that is not needed taking 30 minutes each. 28,000x0.05x3 2 = 44,800 minutes 477 hours/ hrs 20 working days 11 Information on posting orders Time consuming to sort through posting orders to identify relocations.... MBR does not get Info pack therefore cannot process move. More information could be provided which could be used later in process... Only 1/3 rd of postings and CIPC’s are entitled to relocation relocations then sorting through postings. 3 to 4 minutes on average to sort through each. 84,000x3.5 = 294,000 min/60/7.5 = 653 days /250 working days in year FTE © Michael Rosemann

Simulation / What-If Analysis 10 applications per hour Poisson arrival process (negative exponential) TaskRole Execution Time (mean, dev.) Receive applicationsystem00 Check completenessClerk30 mins10 mins Perform checksClerk2 hours1 hour Request infosystem1 min0 …………

Simulation output: KPIs

Costs Quality Time Flexibility Phase 4: Process Re-Design

Phases 5-6. When technology Kicks in..

Process Execution Engines BPMN-based –BizAgi –Activiti –Progress Savvion BPEL-based –Oracle SOA Suite –ActiveVOS BPM IBM BPM Microsoft –BizTalk –Windows Workflow Foundation

Next Week Introduction to Process Modeling