“BPM Standards Landscape”. Keynote presentation by Mike Marin at the BPM Korea Forum at Seoul, Korea. Describe the importance of standards and the Workflow and BPM standards landscape in 2005.

1. BPM Standards Landscape
Mike Marin
WfMC Technical Committee Vice Chairman (Americas)
Software Architect, FileNet Corporation

2. Agenda
• Why standards?
• Some vertical process organizations
• BPM standards history
• Some standards and organizations
• Putting all together
2

3. Why Standards?
• Reduce risk for
• Customers
• Vendors
• Define and consolidates a market
• Creates common understanding
• Defines a minimum functionality set
3

4. Standards Reduce Risk for Customers
• Gives customer options
• Avoid vendor lockup
• Improve tool interoperability
• Define a minimum functionality set
4

5. Standards Reduce Risk for Vendors
• Reduce research and development
• Define the market needs and requirements
• Provide an opportunity to influence the market
5

6. BPM Space
XML
Proprietary Process Process Process
Files Versioning Repository Repository Discovery
Process Definition
Very Lifecycle
Long
Average Workflow
Process IT Business
Developer User
BPM
Duration
EAI Process
Component
Very
Short Assembly
Process Analysis
Auditing Monitoring Business Forecasting Simulation
Measurements
6

7. Process Templates by Vertical Groups
• Groups using BPM technology to create process
templates for a market
• Fully designed and documented process templates
• Good starting point
• Avoid designing process from scratch
• Decrease process project time to deployment
• Provide interoperability
• Examples
• RosettaNet
• OAGI
• HL7
7

8. RosettaNet
• Supply chain process templates for
• Information technology (IT)
• Electronic components (EC)
• Predefined partner interface process (PIP)
8

9. Open Applications Group (OAGI)
• EDI integration process templates
• For B2B and A2A
• Examples
• Customer Relationship Management
• Logistics
9

10. Health Level Seven (HL7)
• Processes templates for health care
• Examples
• HIPAA
• Patient Administration
• Laboratory Automation
10

11. BPM Standards
• XML is the language of standardization
• Explosion of XML standards
• It takes time for standards to converge
• But it is happening
• BPML, XLang, WSFL replaced by WS-BPEL
• Process Standards start converging
• Modeling
• BPMN
• XPDL
• Execution
• WS-BPEL
• Foundation
• Simple Object Access Protocol (SOAP)
• Web Services (WSDL)
• Universal Description, Discovery, and Integration (UDDI)
11

12. BPM and Workflow Standards History
SGML Open
1993 OASIS
1998 1999
ebXML, WS-BPEL & ASAP
WfMC WAPI, IF4-Mime Binding, WPDL, XPDL, wf-XML
1993
Workflow Facility, BPDM, BPRI, BPMN
BPMI BPMN
WS-CDL
BPM Standards 2000
OMG
1989 1997 2005
W3C
1994 2003
12

13. WfMC -- Workflow Management Coalition
• Founded in 1993
• Non-profit – open to all
• Mission Statement
• Increase the value of customer’s investment on workflow
and process technology
• Decrease the risk of using process products
• Expand the workflow and process market through
increasing awareness of the technology
www.wfmc.org
13

14. The WfMC Reference Model
Process Definition
& Modelling Tools
Specification 1 Process Definition
Specification 5 Specification 4
Process Management Other
Audit Data Process Process
Engine
Interoperability Management
Systems
Specification 2 Performer Application
Specification 3
Interface Interface
Invoked
Clients
Applications
14

15. WfMC Specifications
• Glossary (1994, 1996, 1999)
• Reference Model (1995)
• Workflow APIs
• “C” (1995, 1997)
• Interoperability Protocol & Bindings
• MIME (Email) (1995)
• Wf-XML (2000, 2001)
• Audit specification (1997, 1999)
• Process Definition Import/Export Specification
• WPDL (1999)
• XPDL (2002, 2005)
• OMG Submission
• Workflow Management (1999)
15

16. XML Process Definition Language (XPDL)
• A modeling language for Process Definition
• A Process Definition Meta-model
• Reference Model Interface 1 – Process definition
• Goals
• Process Definition Model interchange between tool
16

17. Workflow Interoperability (wf-XML)
• Interaction between requesters and providers of process
services
• For managing interactions with long running services
• Standardized minimum set of operations
• Reference Model Interface 4 – Process Interoperability
17

18. OMG -- Object Management Group
• founded in April 1989 by 11 companies
• Non-profit software consortium
• To create a component-based software marketplace
• Created
• CORBA, UML, MDA, …
www.omg.org
18

19. Business Process Modeling Notation (BPMN)
• By the Business Process Management Initiative (BPMI)
• Now part of OMG
• Graphical business notation to
• Describe processes
• Describe interaction between processes
• Design to be used by business analysts
19

20. Business Process Definition Meta-model (BPDM)
• OMG current work on Process Definition
• Not completed
• Encompassing meta-model for all BPM languages and
models, including
• WS-BPEL
• BPMN
• XPDL
• Etc.
• Based on UML
• MOF compliant
20

21. Business Process Runtime Interface (BPRI)
• OMG current work on BPM runtime interface
• Not completed
• API for workflow and process engines
• Access to executing processes
21

22. OASIS Organization for the Advancement of
Structured Information Standards
• Founded in 1998
• Emerged from SGML open
• Founded in 1993
• Non-profit consortium
• The goal is to drive the development, convergence,
and adoption of e-business standards
www.oasis-open.org
22

23. Business Process Execution Language (WS-BPEL)
• Based on BPEL4WS specification (2002)
• Web services composition
• Encapsulate services into higher level services
• Handle exception cases
• Web services orchestration
• Support for long term services with state
• Some choreography elements
• Abstract/opaque processes
• Just enough to describe the external process behavior without
disclosing the actual process
• Minimalist approach
23

24. Electronic Business using XML (ebXML)
• Created in November 1999
• It was a joint initiative of
• UN/CEFACT
• OASIS
• Goal is to enable electronic commerce
• Business Process Specification Schema (BPSS)
• ebXML Choreography language
• For binary choreographies
24

25. W3C -- World Wide Web Consortium
• Created in October 1994
• MIT, DARPA, CERN, & INRIA
• Leads the technical evolution of the web
• More than 35 specifications
• Including HTML, XML, CSS
www.w3c.org
25

26. Choreography Description Language (WS-CDL)
• Process Choreography specification
• Not complete
Get
Credit
Organization Good Organization
Credit
or or
Process process
Rejected
end
26

27. Putting all together
• BPMN
• For process modeling BPMN
Pool 1 Pool 2
• XPDL UDDI
• For BPM functionality
• BPEL
one way bidirectional
• For web services composition
• UDDI
• For process discovery BPEL XPDL
BPEL Engine Web Services BPM Engine
27