BPM: is a comprehensive change management of business processes that results in continuous process improvement. BPM Goal: efficient business process with visibility. BPM System: manages People2People, System2System, and Person2System.  BPM Results: improve in financial, customer, and employee satisfaction.

1. IBM Business Process Management
(BPM 8.5)
Rafie Tarabay
eng_rafie@mans.edu.eg

2. Why we may need BPM

To computerized all documents work-flow in the
company, for example if the employee need
vacation he just fill a form then submit to take
manager approval and if approved goes
automatically to HR and if rejected back to
employee and send notification on his mail.

The implementation of work-flow will need no
coding in most cases!, just drug and drop the
sequence of the process.

3. BPM Final Screen Sample

4. BPM Architecture

5. Example of developing hiring
request

The user will use BPM to draw the
sequence process in the
Process Designer

Flow will divided to leans according
to who will apply the step
in this case we have 3 leans
(Hiring Manager, General Manager,
Human Resources)

7. What is BPM?

BPM: is a comprehensive change management of
business processes that results in continuous
process improvement.

BPM Goal: efficient business process with visibility.

BPM System: manages People2People,
System2System, and Person2System.

BPM Results: improve in financial, customer, and
employee satisfaction.

8. BPM Vision
BPM Vision: is to improve operations by using
internal business expertise,
business people directly engaging in Design, in
Definition, and in Creation of the process.
Design → Modeling → Execution → Optimization
BPM life cycle

9. BPM Modeling
Design → Modeling → Execution → Optimization
Modeling: capture the ordered sequence of the
business process tasks and the roles of doing
the activity.

10. Modeling approach
Describe → Analyze → Implement (Execute)
Describe: Vision, Goals, KPIs …
Analyze: Business requirement, Process
requirement, Function requirement.
Implement: Development requirement, Solution
implementation.

11. Processing Model
A graphical representation, or diagram, of the
business process.

12. BPM Teams Responsibilities
Sponsor: define Project Goal
Owner: success execution of the process, know the process E2E in high level.
PM: Project Success
Subject Matter Expert: selected by owner, know specific process.
Core Team Member: (Analysis, Developer, Architect)
Administrators: Install, Update, Configure BPM system.
Facilitators: manage the meetings.

13. IBM BPM 8.5
1) Process Center (Development)
(a) Process Designer Interface
(b) Process Center Console
(c) Process Servers
(d) Performance data warehouse (PDW)
2) Process Servers (Production)
(a) Process Servers
(b) Performance data warehouse (PDW)

15. (1)
Process Designer Interface

16. Process Designer Interface
Desktop application save its data to process center
Allow developer to create, manage, test and
optimize BPD( business process definition)
BPD: reusable shared model of the process,
define what is common in all runtime instance of
the process.

17. Process Designer Interface
Consists of
- Designer: allow create, modify, implement BP model
- Inspector: allow test process during modeling & implementation
- Optimizer: evaluate the business process model simulation scenarios

18. (2)
Process Center Console

19. Process Center Console
This tool is used to deploy process application to
the production servers.
Developer should create a Snap Shot first then
Process Center Console deploy this Snap Shot.

20. (3)
Process Center

21. Process Center
Central repository, where process application are
created and stored.
It consists of
- Process server (PS): run business process in
development and store history, versions of
development/deployment.
- Performance data warehouse (PDW) :
collect performance data during development.

22. (4)
Process Servers

23. Process Server
Application server run on webSphere.
Provide the workflow facilities, such as task
management, routing, and simulation.
Components:
- BPD engine
- Service engine
- Event manager

24. (5)
Performance data warehouse (PDW)

25. Performance data warehouse
(PDW)
It is application runs on webSphere to collect
performance data.

26. Working with BPM 8.5

27. How to start PBM 8.5

28. Another way to start BPM
We can start BPM on
two steps
- Start the deployment manager
- Start the node agent

31. Now BPM is start

32. How to get Business Process
Designer

34. Create new project
and create new BPD inside it

35. Open Process Designer

36. Create New Process App

38. Create new Business Process Definition (BPD)

40. Process Designer Elements

41. Process Designer Elements
Simple hire process

42. Start Event

43. End Event

44. Lean

45. Phase

46. Leans VS Phases
Lean : Group of users complete some tasks
Phases : Logical organization unit in the flowchart

47. Activity

48. Activity: Nested Process

49. Gateways

50. Intermediate & Boundary Events

51. Nested Process

52. Types of Nested Process
Subprocess: create a subprocess flow
Linked Process: linked to another reusable flow
Event Subprocess: not linked on the flow, it is fire
automatically when certain event is happened

53. Subprocess implementation
Define it as subprocess the double click on it to
set its implementation sequence

54. Linked Process Implementation

55. Gateways

56. Gateways
1) Exclusive Gateway (one nested IF condition)
2) Inclusive Split Gateway (many IF conditions)
3) Inclusive Join Gateway (OR condition) wait for any
4) Parallel Split Gateway (send to all)
5) Parallel Join Gateway (wait for all)

57. Control Gateway Behavior

58. Exclusive Gateway (IF condition)
One condition only are evaluated
if ()
else if ()
else
end if

59. Exclusive Gateway (IF condition)
Evaluate conditions one by one from top to bottom
if one are true cancel evaluate the other conditions

60. Inclusive Gateway
All conditions are evaluated
if ()
end if
if ()
end if
if ()
end if

61. Inclusive Join (OR condition)
Wait to any incoming tasks to continue

62. Parallel Join
Wait for all incoming
tasks to complete first
before continue.

63. Parallel gateway
Many steps must complete regardless of its
sequence, and these steps can run in parallel.

64. Boundary Event vs Intermediate event

65. Intermediate event
Pause the flow until event occurred

66. Boundary Event

68. Timer Intermediate event

70. Message Intermediate event

71. Content Intermediate event

72. Tracking Intermediate event

73. Error Boundary Event

74. Toolkits

75. Default toolkits
BPM has by default 5 toolkits
(1) Coaches
(2) System Data
(3) Content Management
(4) System Governance
(5) Dashboards
the 1st
two items are included by default in any
new project

78. Add new toolkit to exist project

79. Develop new BPM project steps

81. Development iterations
To develop any work flow, it is normal to have 6
iterations, from playback 0 to playback 5.
Playback 0 Iteration (Defined the process):
Capture →Document → Map → Refine
Playback (1-5) Iterations (Develop the process):
(Playback1 to Palyback5 steps):
Requirement →Design → Build → Test

82. Playbacks objectives
Playback 0: Describe the current state (as is) and how it should be
(to be).
Playback 1: Manage variables and dataflow and gateways and
routing.
Playback2: Business data flow, business objects
Playback3: create services for integration to get the real data for
web service/Databases …
Playback4: focus on the user screens to create a better user
interface
Playback5: focus on handle process errors, error handling

83. Playback 0
Draw Business flow

84. Playback 1
Focus on the next items:

86. Local Variables
Input, Output, and Private

87. Variable Namespace
All variables are java script objects
tw.system.org.findParticipantGroupByName("Loan Officers").users
tw.system.process.instanceId

88. Implement timers

89. Implement Gateways

90. Implement Routing Task

97. Playback 2
Focus on the next items:

98. Playback 3
Focus on the next items:

99. Playback 4
Focus on the next items:

100. Playback 5
Focus on the next items: