Lecture 2 Business Process Architecture
Lecture 2 Business Process Architecture
Process
Weeks 10-11 monitoring and
Gover- Process Weeks 5-6
Strategy nance analysis
controlling
Culture
2
Chapter 2: Process Identification
Contents
1. The Context of Process Identification
2. Definition of the Process Architecture
1. Process Categories
2. Relationships Between Processes
3. Reuse of Reference Models
4. Process Landscape Model
5. The Example of SAP’s Process Architecture
3. Process Selection
1. Selection Criteria
2. Process Performance Measures
3. Process Portfolio
4. Recap
SEITE 3
Process Identification in the BPM Lifecycle
Management Processes
Examples for BPM lifecycle and process mining identification Core Processes
A E
D
5m 3m 5m 10m 30m 2h 10m
15m
C
1.5h 10min
Conformance and Process As-is process
performance discovery model
insights
A B C D E
Process Process
monitoring analysis
Executable Insights on
process weaknesses and
model their impact
Process Process
implementation To-be process redesign
model
Chapter Overview
SLIDE 5
Definition of Business Strategy
SLIDE 6
Balanced Scorecard (Kaplan & Norton)
Learning and
Financial Customer Internal
Growth
Perspective Perspective Perspective
Perspective
Product/Service Operations Management
Attributes Processes
Improve Cost
Culture
Structure Price Supply Distribution
Production Risk Mgmt.
Quality
SLIDE 7
Enterprise Architecture according to TOGAF*
▪ Organizational perspective:
actors, roles, and organizational structure.
▪ Product perspective:
products and services along with their relationships.
▪ Business process perspective:
process architecture.
▪ Data perspective:
informational entities and their relationships.
▪ Application perspective:
different pieces of software with their dependencies.
▪ Technical infrastructure:
computer hardware and communication networks.
*TOGAF: The Open Group Architecture Framework- the most used framework for enterprise architecture today that
provides an approach for designing, planning, implementing, and governing an enterprise information technology
architecture
SLIDE 8
The Process Checklist
It may not be easy to decide on what to consider as a business process. A chunk of work
that is frequently repeated might not be a business process on its own. To prevent poor
scoping decisions, it is useful to consider the following process checklist:
▪ Is it a process at all? ▪ Is the process important enough to manage?
▪ It must be possible to identify main action, which is ▪ There is customer who is willing to pay for outcomes,
applied to a category of cases. ▪ Organization that carries out the process would be
▪ Name is of form verb + noun. willing to pay another party for taking over, or
▪ Can the process be controlled? ▪ Legal, mandatory framework compels an
▪ Repetitive series of events and activities to organization to execute it.
execute individually observable cases. ▪ Is the scope of the process not too big?
▪ Without a clear case notion, process management ▪ 1:1 relation between initial event and activities.
is not feasible. ▪ Is the scope of the process not too small?
▪ Also, without any sense of repetition, a group of ▪ Rule of thumb: there should be at least three
business activities may better qualify as a project different actors – excluding the customer – involved.
than as a business process.
▪ If there are no handoffs between multiple actors or
systems, there is little that can be improved using
BPM methods.
SLIDE 9
Process identification
What?
1. Identify an organization’s business processes
2. Prioritize their management based on certain criteria
Why?
1. Understand the organization
2. Maximize value of BPM projects
Process identification steps
1. Designation step
Process
Enumerate main processes
Architecture
Determine process scope
Geary Rummler
Porter: Types of processes
Management
Processes
Customers / Stakeholders
Suppliers / Partners
Core Processes
Support Processes
Support processes
Indirect procurement (parts replenishment, operational resources replenishment…)
HR (policies update, recruitment, induction, probation…)
…
Management processes
Suppliers management (suppliers planning, suppliers acquisition…)
Logistics management (logistics planning, logistics controlling…)
…
Relations between core, support, mgt processes
Core processes
Fill Order Process
generate value as they
are directly linked to Receive Approve Deliver
Fill Order
external customers Order Order Order
Reorder
Supplies
Support processes provide
Stock Process Order
resources to be used by other Supplies Supplies
processes
Receive
Supplies
Relationships between Processes
Sequence
Manage
Procure Procure Market Deliver
Customer
Materials Products Products Products
Service
Decomposition Specialization
SLIDE 16
Example: process architecture
Wholesaler
Strategic
Management
Logistics Suppliers
Management Management
Warehouse Demand
Management Management
Process
Management processes group
Direct
Sales Distribution
procurement
Marketing Service
Core processes
Indirect
Finance IT HR
procurement
Support processes
Example: process architecture
Insurance company
Strategic
Management
Corporate Market Investor
Development Development Relations
Management processes
Strategic Teaching
Management award courses
IP
Marketing
Management
Course Additional
Management services mgt
Language Admission IT
training
1. Clarify terminology:
▪ Define key terms.
▪ Use organizational glossary.
▪ Use reference models.
▪ Ensure that stakeholders have a consistent understanding of process landscape model.
2. Identify end-to-end processes:
▪ Those processes interface with customers and suppliers.
▪ Goods and services that organization provides are good starting point.
▪ Properties help to distinguish processes, including: Product type, Service type, Channel, Customer type.
3. For each end-to-end process, identify its sequential processes:
▪ Identify the internal, intermediate outcomes of end-to-end process.
▪ Perspectives help set boundaries: Product lifecycle, Customer relationship, Supply chain, Transaction
stages, Change of business objects, Separation.
4. For each business process, identify its major management and support processes:
▪ What is required to execute the previously identified processes.
▪ Typical support processes are management of personnel, financials, information, and materials.
▪ However, these can be core processes if they are integral part of business model.
▪ Management processes are usually generic.
SLIDE 22
How to define Process Landscape Model
SLIDE 23
Process scoping
Process architecture
Value chain modeling
Chain of processes an organization performs to deliver value to customers and stakeholders
More generally, a mechanism to group high-level business processes according to an order
relation (can be applied to core, support and management processes)
business
process
Procure-to-service
order
relation
Guidelines to identify horizontal boundaries
in value chains
1. Change of key business object in the process
2. Change of granularity of main business object
3. Change in frequency/time
4. Change in intermediate outcome/resolution/objective
Example: value chain
Wholesaler
Core processes
Building up a value chain (for core processes)
Think around three main steps:
IMAGINE IT (DESIGN NEW
Example: Producer PRODUCT/SERVICE)
BUILD IT (SOURCE, ASSEMBLE,
DELIVER PRODUCT/SERVICE)
SELL IT (MARKET, SELL, SERVICE
PRODUCT/SERVICE)
Stocked
products:
Specializations
MTO
products:
ETO
products:
Example: value chains for service provider
IT service provider
Systems Integration
Outsourcing
Network Services
HR:
Accounting:
Management processes
Suppliers
management:
Risk
management:
Example: process architecture & value chains
Wholesaler
Strategic
Management
Warehouse Logistics
Management Management
Suppliers Demand
Management Management
Management processes
Chevron: Direct Box:
Sales Distribution
collapsed procurement
groups
Procure-to-Service
value chain processes/
Marketing Service
Core processes value chains
Indirect
Finance IT HR
procurement
Support processes
Alternative: process architecture – groups
Consultancy Firm
Manage Firm
1.1 1.2 1.3 1.4 1.5
Management Plan the Govern the (Re)design Develop Methods Change the
processes Business Business Processes & Standards Business
Expanded
Relate to Clients
Core 2.1 2.2 2.3 2.12 process
Optimize Develop Raise Awareness Evaluate Client
processes Stakeholder
Relationships
Service Offerings of Services Solution Delivery group
Optimize Solutions
2.9
Operate 2.10 2.11
Infrastructure & Retire Solutions Support Users
Business Systems
Support Firm
3.1 3.2 3.4 3.6
Support 3.3 3.5
Provide Expert Provide HR Acquire Goods & Provide Working
Provide IT Tools Obtain Financial
processes Advice & Capabilities Services Facilities
Services
Knowledge
Typical artifacts for vertical scoping
Value chains
Chains of processes. Stay at a high level. Rule of thumb: 3-7 processes
Procure-to-service, Risk management
(Root/Main) Processes
Build up value chains and affect each other. They are abstract
Lead-to-quote, Quote-to-order, Order-to-cash
Subprocesses
Typical focus of Process enumeration
Build up processes. They are detailed, involve multiple activities and can be layered on different levels of
abstraction (i.e. sub-subprocesses)
Order shipment, invoicing
Process tasks
Build up processes and sub-processes. They are atomic and performed by human beings, IT systems or
equipment
Approve invoice
Process architecture: hierarchical view
Level 1
Process
Landscape
Process hierarchy
Level 2
Main
Processes
(e.g. BPMN)
Level 3+
Subprocesses, Tasks
(e.g. BPMN)
How many levels in the process architecture?
35
Example: process hierarchy
Insurance company
Level 1
Strategic
Management
Corporate Market Investor
Development Development Relations
Management processes
Develop
Define pricing
Build Process
Manage
business investor subgroup
knowledge strategy
strategy relations
Manage Communicate
partners with stakeholders
Manage
investments &
divestments
Management processes
Example: process hierarchy
Management processes
Example: process hierarchy
Insurance company
Level 4
Formulate Subprocess
mission
Communicate
mission
Management processes
Designation via reference models
A reference model is used as a template to design the process architecture
Examples:
Information Technology Infrastructure Library (ITIL)
Supply Chain Operations Reference Model (SCOR)
Process Classification Framework (PCF)
Control Objectives for Information Technology (COBIT)
Value Reference Model (VRM)
Voluntary Interindustry Commerce Solutions (VICS)
eTOM Business Process Framework
Performance Framework
Example:
APQC Process Classification Framework (PCF)
Category
APQC Classification Framework
Group
Activity
Process
APQC Classification Framework
Short-term action
High Feasibility
Loan Rating
Low
controlling Contract
preparation Medium
Loan
decision Loan market High
evaluation
Handling of
payments Loan
planning
Loan
application
Low
Poor Health Good
Possible Strategic fit?
Prioritisation
1. Importance
Which processes have greatest impact on the organization‘s strategic objectives?
2. Health (or Dysfunction)
Which processes are in deepest trouble?
3. Feasibility
Which processes are most susceptible to successful process management?
Short-term action
High Feasibility
Loan Rating
Low
controlling Contract
preparation Medium
Loan
decision Loan market High
evaluation
Handling of
payments Loan
planning
Loan
application
Low
Poor Health Good
Possible Strategic fit?
Process Performance Measures
SLIDE 49
Example 2.3: Restaurant
▪ A restaurant has recently lost many customers due ▪ In this scenario, most relevant performance
to poor customer service. The management team dimension is serving time.
has decided to address this issue first of all by ▪ One objective is to completely avoid waiting times
focusing on the delivery of meals. above 30 min.
▪ The team gathered data by asking customers about ▪ Percentage of customers served in less than 30 min
how quickly they liked to receive their meals and should be close to 100%.
what they considered as an acceptable wait.
▪ Thus, the percentage of customers served in less
▪ The data suggested that half of the customers would than 30 minutes is relevant performance measure.
prefer their meals to be served in 15 min or less. All
customers agreed that a waiting time of 30 min or ▪ Threshold mentioned in scenario is 15 min.
more is unacceptable ▪ Choice between two performance measures:
average meal delivery time or percentage of
customers served in 15 min.
SLIDE 50
Balanced scorecards with cascading
process performance measures
SLIDE 51
Process Portfolio
Handling
High
Payments
Loan
Loan Planning
Application
Low
SLIDE 52
Recap
SLIDE 53
Questions ?