bpm & workflow in the new enterprise architecture
TRANSCRIPT
Welcome Keith D Swenson
Technical Committee ChairmanWorkflow Management Coalition
Vice President of R&DFujitsu Computer Systems Corporation
Workflow, BPM, & New Enterprise Architecture
2 April 21-23, 2008
Renaissance Washington, DC
Fujitsu : Leadership in Software
Fujitsu’s Strengths:Strong presence in the BPM area and a comprehensive product line in SOA and BPMSignificantly expanded consulting and engineering resources in the U.S. — it has won U.S./U.K. customers and gained significant growth ratio outside JapanStrong presence in human-to-human BPM area that offers strong capability in orchestrationDeep understanding of back-end integration requirements, with a long history of supporting the mainframe environmentStrong capability in composing, sequencing and managing services with Interstage Service Integrator/Fujitsu enterprise service bus (ESB) accompanied by service registry and repository (CentraSite)
3 April 21-23, 2008
Renaissance Washington, DC
Customers
Media/
IT
HealthcareIT
4 April 21-23, 2008
Renaissance Washington, DC
Overview / Agenda
Definitions of Terms & MotivationThe Evolution of Workflow / BPM
– How the technology has developed over time– Human BPM and EAI Convergence
A New Enterprise Architecture for AgilityFive Key Standards
– BPMN, XPDL, BPEL, Wf-XML, BPAF
What is the Ultimate Goal?– Business Level Agility
5 April 21-23, 2008
Renaissance Washington, DC
is defined in a is managed by a
composed of
which may be
Process DefinitionProcess DefinitionRepresentation of what is intended to happen
Business ProcessBusiness Process
What is intended to happen
Workflow Management System( BPMS )
Workflow Management System( BPMS )
ActivitiesActivities
ManualActivitiesManual
ActivitiesAutomatedActivities
AutomatedActivities
Work ItemsWork Items InvokedApplications
InvokedApplications
Process InstanceProcess Instanceused to create & manage
composed of
Representation of what is actually happening
Controls the automated Aspects of the process.
includes one or more
Not managedby BPMS
during execution arerepresented by
Tasks allocated to aWorkflow Participant. Services called as
part of process
Activity InstancesActivity Instances
subp
roce
ss
Terms
6 April 21-23, 2008
Renaissance Washington, DC
Motivation
Drivers for Business Process Management (BPM)
Drivers for Business Process Management (BPM)
PerformanceBusiness Process Improvement
Engineering of Process-aware IS
PerformanceBusiness Process Improvement
Engineering of Process-aware IS
ComplianceMandated compliance (e.g. SOX)
Desired compliance (e.g. ISO, ITIL)
ComplianceMandated compliance (e.g. SOX)
Desired compliance (e.g. ISO, ITIL)
7 April 21-23, 2008
Renaissance Washington, DC
You’re Hired !
Process: New Hire Integration– Background Check– Allocation of office space– Reservation of phone, pager– Creation of access rights in operational systems
Problem: Lost productivity due to late provisioning of work infrastructure
Automating the process coordination reduced cycle time from 2 week average to 2 days
BPM Goal: Performance
8 April 21-23, 2008
Renaissance Washington, DC
You’re Fired !
Process: Employee Termination– Removal of computer access rights– Collection of company-issued phone, pager, access
card– Removal from employee directory
Problem: Not all equipment is collected, access rights remain after an employee leaves
Automating the process coordination ensures that no step is forgotten
BPM Goal: Compliance
Welcome The Evolutionof Workflowand BPM
10 April 21-23, 2008
Renaissance Washington, DC
1990 Workflow in the Brain
Enterprise Application A “Account Management”
Backg
rou
nd
Ch
eck
Co
nfo
rma
nce G
uid
eline
s
ApplicationLogic
in MonolithicProgram
UI“Screens”
listAccts
newAcct
updateAcct
deleteAcct
11 April 21-23, 2008
Renaissance Washington, DC
1993 Assist Work Sequence
Enterprise Application A “Account Management”
Backg
rou
nd
Ch
eck
Co
nfo
rma
nce R
ules
ApplicationLogic
in MonolithicProgram
UI“Screens”
listAccts
newAcct
updateAcct
deleteAcct
backgroundcheck
createaccount
checkguidelines
LaunchesUI
User accessesoriginal UI directly
Human BPM/Workflow:
12 April 21-23, 2008
Renaissance Washington, DC
1996 Distribute Work
Enterprise Application A “Account Management”
Backg
rou
nd
Ch
eck
Co
nfo
rma
nce R
ules
ApplicationLogic
in MonolithicProgram
UI“Screens”
listAccts
newAcct
updateAcct
deleteAcct
backgroundcheck
createaccount
checkguidelines
Launches
13 April 21-23, 2008
Renaissance Washington, DC
2002 Backend Web Services
Enterprise Application A “Account Management”
Backg
rou
nd
Ch
eck
Co
nfo
rma
nce R
ules
ApplicationLogic
Service Oriented
Architecture
ExposedWeb
Serviceslist
AcctsnewAcct
updateAcct
deleteAcct
enterinfo
createaccount
bgcheck
rules Review
UI connects user to process engine, not
the back-end applications
14 April 21-23, 2008
Renaissance Washington, DC
Old
Ru
les
2005 Composite Services Give IT Agility
Enterprise Application A “Account Management”
Backg
rou
nd
New
Ru
les
listAccts
newAcct
updateAcct
deleteAcct
enterinfo
createaccount
call 1 Review
ESB / BPEL
ApplicationLogic
ExposedWeb
Services
CompositeService
15 April 21-23, 2008
Renaissance Washington, DC
Old
Ru
les
2005 Composite Services Give IT Agility
Backg
rou
nd
New
Ru
les
listAccts
newAcct
updateAcct
deleteAcct
enterinfo
createaccount
call 1 Review
ESB / BPEL
ApplicationLogic
ExposedWeb
Services
CompositeServices
16 April 21-23, 2008
Renaissance Washington, DC
Human Activities: 3 Phases
Review
Automated phase beforeto prepare for the task
Wait phase for Human to do the work,includes timers andescalation logic
Automated phase afterto take care of resultsof the task
User Interface(while waiting)
Note: this notation is not standard!
17 April 21-23, 2008
Renaissance Washington, DC
Future Simplify as “Human Steps”
Enterprise Application A “Account Management”
Backg
rou
nd
Co
nfo
rma
nce R
ules
ApplicationLogic
ExposedWeb
Services
listAccts
newAcct
updateAcct
deleteAcct
call 1 Review
ESB / BPEL
enterinfo
CompositeService
To People:Looks liketwo steps!
Much simpler.
18 April 21-23, 2008
Renaissance Washington, DC
Separation of Responsibility
Enterprise Application A “Account Management”
Backg
rou
nd
Ru
les
listAccts
newAcct
updateAcct
deleteAcct
ESB / BPEL
call 1 Reviewenterinfo
Business Retains Control of• Assignment of Responsibility• Groups, Roles, Skills• Deadlines• Alerts, Reminders, Escalations• Order of Tasks• Addition of Manual Tasks• User Interface
IT Retains Control of• Computational Logic• Data Representations• Scalability / Performance• Interoperability• Master Data Management
19 April 21-23, 2008
Renaissance Washington, DC
Who?
When?
What?
How?
Separation of DevelopmentBusiness Retains Control of• Assignment of Responsibility• Groups, Roles, Skills• Deadlines• Alerts, Reminders, Escalations• Order of Tasks• Addition of Manual Tasks• User Interface
IT Retains Control of• Computational Logic• Data Representations• Scalability / Performance• Interoperability• Master Data Management
Depends strongly on who is in each organization.
Changes on daily basis
Organizational Culture
Optimize for each team
Respond to market or legislation
Related to Training, Experience
Requires expensive technical capabilities
Very low or no dependence upon the organizational culture
Knowledge of infrastructure
Welcome Human Process Management vs.Enterprise Application Integration
21 April 21-23, 2008
Renaissance Washington, DC21
EAI BPM
Mainly integration or technology driven processes– Straight Through Processes– Short process duration
Projects tend to be driven by IT
Humans get involved when there are exceptions
Usually less sophisticated human support required
AverageProcessDuration
VeryLong
VeryShort
ComponentAssembly
EAIProcess
Workflow
Lifecycle
Components
Applications
Applicationsand
Participants
Processes
Technology Coordinate
22 April 21-23, 2008
Renaissance Washington, DC22
Human BPM/Workflow
Mainly Human Centric ActivitiesCollaboration between
participants– May be supported by BPM
system– May occur outside
automated system(direct human interaction)
– Long process durationProjects tend to be driven by
BusinessAlmost always require integration
with applications or technologies
Integration capabilities usually not as rich as products with origins in EAI
AverageProcessDuration
VeryLong
VeryShort
ComponentAssembly
EAIProcess
Workflow
Lifecycle
Components
Applications
Applicationsand
Participants
Processes
Technology Coordinate
23 April 21-23, 2008
Renaissance Washington, DC23
Human BPM Has UI
Workitems– To-do list, works to do (personal, role …)
Forms represent task – Step, workflow activity
Forms interaction– document attachments, comments
Many other interaction– Search, caseview …
Users need rich applications
24 April 21-23, 2008
Renaissance Washington, DC24
Human BPM has Management
Time management– Delegate, alarm,
overdue, delay, vacation
Supervision– Team management,
Process supervision, exception
25 April 21-23, 2008
Renaissance Washington, DC25
Human BPM Represents Users
User management– Rights, assignment, skills, Organizational structure
Task assignment– Self-service, workload, distribution, dynamic
assignment
26 April 21-23, 2008
Renaissance Washington, DC26
Human BPM has Integration, too
From a workflow perspective, a participant can be a human, an application, a machine, or another process or workflow engine
System integration mostly base on point to point connector technology (a participant = 1 application)
High document integration (EDMS/ECM) capability
27 April 21-23, 2008
Renaissance Washington, DC27
Convergence
• EAI specialists acquire Human BPM technology to increase Human capabilities
• Human BPM specialists integrate EAI technology to increase integration/transaction/connector capabilities
• Over time these are blending into a single category
Benefit to Customers:– Single product applicable for wide range of projects– Fewer pieces of technology to manage– More consistent integration– Fosters better collaboration between Business and IT
Welcome Standards Overview
29 April 21-23, 2008
Renaissance Washington, DC29
BPM Standards Summary
BPMN – Business Process Modelling Notationis widely accepted as standard for the look of a process
XPDL – XML Process Definition Languagepromotes the exchange of processes between vendors and tools:– Modelling and Simulation– Process Design and Implementation– Process Deployment– BAM and Historical Reporting
BPEL – Business Process Execution Language– Includes only the executable aspects of a process– Oriented toward orchestration of Web Services
Wf-XML - Inter Engine Collaborationprovides runtime integration between process services
BPAF - Business Process Analytics FormatStandard event format for Process Intelligence Tools
April 21-23, 2008
Renaissance Washington, DC
Standards Landscape
Collaboration AgreementCollaboration Agreement
Process Model DiagramProcess Model Diagram
UML Activity Diagrams
BPMN 1.0
Repository & DiscoveryRepository & Discovery
UDDI
AssuranceAssurance
WS-Security SAML
Process Model Definition/Storage FormatsProcess Model Definition/Storage Formats
ebXML BPSSebXML
CPA/CPP
Transport ReliabilityTransport Reliability
ebXML-RM WS-RM ...
Transport LayerTransport Layer
HTTP JMS ...
EncodingEncoding
SOAP / AttachmentsWS-Addressing
Data DefinitionData Definition
XML-Schema
Service End Point DefinitionService End Point Definition
WSDL
Service Orchestration
Service Orchestration
Choreography DefinitionChoreography Definition
WS-CDLBPEL
Monitoring & AuditMonitoring & Audit
WfMC IF5 1.0 (CWAD)
Runtime InteractionRuntime Interaction
Wf-XML 1.0 WfMCWAPI
PresentationPresentation
XForms
Service/Human
Interaction
Service/Human
Interaction
BPEL4People
Near Completion
Stable
Under Development
Ideation Stage
BPMN 1.1
Process Model SemanticsProcess Model Semantics
BPDM 1.0
Proprietary (e.g. MQSeries)
Wf-XML 2.0
WfMC IF5 2.0
(XWAD)BPRI
BPMN 2.0 (BPDM 2)
JSF WS-RP
XPDL 2.1
RosettaNet PIPs
April 21-23, 2008
Renaissance Washington, DC
Standards Landscape
discuss today XPDL 2.1
BPELWf-XML
1.0Wf-XML
2.0
BPMN1.0
BPMN 1.1
32 April 21-23, 2008
Renaissance Washington, DC
Workflow / BPM Reference Model
33 April 21-23, 2008
Renaissance Washington, DC
Workflow / BPM Reference Model
BPMN
XPDL
SOAP
BPEL Wf-XMLBPAF
REST
34 April 21-23, 2008
Renaissance Washington, DC
BPMN: Business Process Modeling Notation
Defines the way the process LOOKS
Provides a dictionary of standard shapes with particular meanings
Consistent use of shape/meaning benefits everyone:reduces the learning curve,training on shapes is useful for multiple products
35 April 21-23, 2008
Renaissance Washington, DC
XPDL: XML Process Definition Language
The FILE FORMAT for a process definitionExchange process definitions between
– Different BPM/Workflow Products– Process Modelling/ Simulation tools and
BPM/Workflow Products– Supported by more than 70 commercial BPA/ BPM
products and interoperability demonstrated; use of tools that support the standard ensures that you are not locked in to any particular vendor
Full support for BPMN
36 April 21-23, 2008
Renaissance Washington, DC
BPEL: Business Process Execution Language
Powerful programming language for Web service orchestration and XML manipulation
Oriented toward building composite applications, not necessarily BPM
Inflated expectations in media to be universal process language; now disillusioned
No support for human activities– Look to BPEL4People effort to add this
No sub-processes– Look to BPEL Subprocess effort to add this
No on-the-fly process modifications
37 April 21-23, 2008
Renaissance Washington, DC
Process Design Ecosystem
Vendor FVendor E
SOA DesignWorkflow Design
Vendor C Vendor DVendor BVendor A
Process Risk Mgmt Process Simulation
Process Execution
Process Modeling
Process Model Repository
Process Optimization
Process Execution
Executable Model Repository (e.g. XPDL)
Executable Model Repository (e.g. BPEL)
◄ Wf-XML ►
X
Risk/Control Ownership/Issue
Resources/Time
Goals/Strategies
Tool- specific Capabilities
User Needs
Process Structure is shared by all tools
Execution environments have different strengths, no model exchange at this level
PeopleIntegratio
n
Limited Portability
BPMN BPMN BPMN BPMN
38 April 21-23, 2008
Renaissance Washington, DC
Wf-XML: Runtime Integration
Sales Process on Server A
Draft AproveLegal
ReviewClose
ContractSpecialist
TortSpecialist
ExecAnalyst
Legal Review Process on Server B
Wf-XMLbased on SOAP or REST
Standard Protocol between process engines allows oneprocess to reuse anotheracross technologies.
39 April 21-23, 2008
Renaissance Washington, DC
• Standardized Event Format– XML Syntax– Defined Attribute Semantics
• Process State Model• Activity State Model
BPAF: Business Process Analytics Format
BusinessProcess
IntelligenceWarehouse
BusinessProcess
ManagementSystemServers
40 April 21-23, 2008
Renaissance Washington, DC
WfMC WfMC
OASISOASIS
BPMIBPMI
OMGOMG
Standards Timeline - Releases
WPDLWPDL
XMLXML
BPMN 1.0BPMN 1.0
XPDL 2.0XPDL 2.0 XPDL 2.1XPDL 2.1
1994 1998 2000 2001 2008 201020072006 20092004 20052002 2003
XPDL 1.0
XPDL 1.0
BPMN 1.0BPMN 1.0BPMN
1.2BPMN
1.1
BPMN 1.1
BPMN 2.0
RefModel
RefModel
Wf-XML-RWf-XML 1.0
Wf-XML 1.0
Wf-XML 1.1
Wf-XML 1.1
BPEL4PeopleBPELBPEL
XPDL 3.0
BPAF
Welcome Goal: Business Level Agility
42 April 21-23, 2008
Renaissance Washington, DC
Agility = Business Driven Change w/o Programming
Enterprise Application A “Account Management”
Backg
rou
nd
Ru
les
listAccts
newAcct
updateAcct
deleteAcct
call 1 Review
ESB / BPEL
enterinfo
News Flash!
Some otherbank sued!Need to respondquickly to avoid risk!
News Flash!
Some otherbank sued!Need to respondquickly to avoid risk!
43 April 21-23, 2008
Renaissance Washington, DC
Agility = Business Driven Change w/o Programming
Backg
rou
nd
Ru
les
call 1 Review
ESB / BPEL
enterinfo
legalcheck
ImmediateResponse:
Handle the problem manually with a specialist team -- the next day.
ImmediateResponse:
Handle the problem manually with a specialist team -- the next day.
Enterprise Application A “Account Management”
listAccts
newAcct
updateAcct
deleteAcct
44 April 21-23, 2008
Renaissance Washington, DC
Agility = Business Driven Change w/o Programming
Backg
rou
nd
Ru
les
call 1 Review
ESB / BPEL
enterinfo
Eventually:
Automate the step with a service, and eliminate the manual review team a few weeks or months later.
Eventually:
Automate the step with a service, and eliminate the manual review team a few weeks or months later.
Enterprise Application A “Account Management”
listAccts
newAcct
updateAcct
deleteAcct
Leg
al Ch
eck
45 April 21-23, 2008
Renaissance Washington, DC
Summary
New structure for enterprise applications– Separate “who” & “when” - controlled by business users– From “what” & “how” - controlled by IT developers– Purposefully segregate these aspects so that the right
group has the right flexibility from the startKey Benefits:
– Business Level Control & AgilityStandards are key to interoperability
– BPMN – the graphical notation– XPDL – the file format for design interchange– BPEL – the executable part of the process– Wf-XML – runtime integration of processes– BPAF – Analytics Format for Process Intelligence
46 April 21-23, 2008
Renaissance Washington, DC
BPM In Practice: A Primer for BPM & Workflow Standards
All of this and more is covered in this new book from Keith Swenson and Robert Shapiro available at:
http://www.lulu.com/content/2244958
See the related blog at:
http://kswenson.wordpress.com/books
47 April 21-23, 2008
Renaissance Washington, DC
Questions?
Interstage BPM Studio available free at
http://www.fsw.fujitsu.com/support/ibpm_studio/
WfMC: Process Thought Leadership.
48 April 21-23, 2008
Renaissance Washington, DC
Thank You!
Keith D SwensonTechnical Committee Chairman
Workflow Management CoalitionVice President of R&D
Fujitsu Computer Systems Corporation
Contact Information:+1 408 [email protected]