BPM Deep Dive
BPM Deep Dive
Introductions
Presenters:
Wali Haidri Technical Lead
James McClure Process Architect
Organization:
AD Global Shared Services (Megan Clark)
Process & Tools (Mike Zomermaand)
Ford Proprietary 2
Topics
Discussion
BPM Use
Cases
Learn BPM
Key
BPM Concepts
Architecture
BPM
History
Ford Proprietary 3
History - Major Software Releases
IBM acquires
Lombardi
Lombardi Software
Lombardi
Teamworks Teamworks IBM BPM
5.57 6.2 7.5
Lombardi IBM
Teamworks Websphere
6.01 Lombardi
Edition 7.2
Ford Proprietary 4
BPM Application Architecture
Ford Proprietary 5
BPM Production Infrastructure
Intranet
BPM Users
Ford Global Client
Windows 7/Vista/XP
IE 8.x
HTTP/80
GSS/ACE
www.bpm.ford.com
HTTP/80
JDBC/1521
BPM Database
Annex HP DL380
FUSE 4.1.0 (SLES 10 64 bit)
Oracle 11G
Intranet ECCDB923
Ford Proprietary 6
Key Concepts
Process
Instance
Tracking
Metrics Task
Coach Routing
Ford Proprietary 7
Key Concepts - Process
BPD
(Business Process Process Instance
Diagram)
A Process Instance
Model of a created when a
Business Process BPD is executed at
run time
Unique Instance
Executable
Id is assigned
Ford Proprietary 8
Key Concepts - Task
- at runtime To user(s)
A step within a
- Identified by based upon
process
a Task Id Routing
Assigned to a
user or
Role/Group
Ford Proprietary 9
Key Concepts - Routing
Dynamic List
Role Based
of Users
TW Internal
Customizable
Security
APS Security
Ford Proprietary 10
Key Concepts - Coach
Basic
Web User Customization
WYSIWG editor
Interface Simple CSS / Simple
AJAX
Full
Customization:
Teamworks Web API
Ford Proprietary 11
Key Concepts Tracking Metrics
Number of exceptions
(e.g. escalations)
Ford Proprietary 12
Example Database Change Request Process
Ford Proprietary 13
Example User Submits Request
Request
SDA Submits Assigned to
Request Data
(Coach/UI) Architect
Role
New Task created and as
to Data Architect Role
Ford Proprietary 14
Example Designer Approves Request
Data Architect Request
opens the Assigned to
Request Data Model
(Coach/UI) Team
Ford Proprietary 15
Use Cases
Ford Proprietary 16
Use Cases
SOA Process
Standalone
Integrated Enabled J2EE
Application
Application Application
Ford Proprietary 17
UC 1: Standalone Application
Client Tier
Low budget
Process / business
Application Tier
Short Timeframe logic in BPM
Resource Tier
No upstream/downstream systems
Any Application
data persistence
in BPM DB.
Ford Proprietary 18
UC 2: SOA Integrated Application
Ford Proprietary 19
UC 2: SOA Integrated Application
BPM Infrastructure
Pros & Cons:
Client Tier
Large projects BPM User Interface
in BPM
Application Tier
High Complexity
Resource Tier
Upfront Analysis
SOA Integration Layer and Design required
Process / business
logic in BPM
High Collaboration required
BPM interacts with
SOA Integration Layer External System via
Web Services
Other components
External System(s)
Ford Proprietary 20
UC 3: Process Enabled Client Application
J2EE Application
Pros & Cons: User Interface in
Client Tier
Highest return on investment J2EE Application
SOA Integration Layer
Lightweight
External System Process Business Logic in
J2EE App
Application Tier
Any size Java Application can use
Resource Tier Business data stored
Web Services skills required by J2EE in J2EE App
app
No business logic in BPM J2EE Application can
invoke Process calls
No data persistence
Application Tier in BPM
Process logic in BPM
SOA Integration Layer
BPM Infrastructure
Ford Proprietary 21
Discussion
Q&A
Email
[email protected],
[email protected]
Ford Proprietary 22