BPM & Workflow in the New Enterprise Architecture
Upcoming SlideShare
Loading in...5
×
 

BPM & Workflow in the New Enterprise Architecture

on

  • 8,004 views

 

Statistics

Views

Total Views
8,004
Slideshare-icon Views on SlideShare
7,922
Embed Views
82

Actions

Likes
5
Downloads
609
Comments
1

3 Embeds 82

http://www.actionsoft.com.cn 66
http://www.slideshare.net 15
http://cache.baidu.com 1

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Great overview...
    Some updated version would be nice as landscape probably evolved in terms of maturity and standards in the last few weeks.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    BPM & Workflow in the New Enterprise Architecture BPM & Workflow in the New Enterprise Architecture Presentation Transcript

    • Keith D Swenson Technical Committee Chairman Workflow Management Coalition Vice President of R&D Fujitsu Computer Systems Corporation Workflow, BPM, & New Enterprise Architecture
    • Fujitsu : Leadership in Software
      • Fujitsu’s Strengths:
      • Strong presence in the BPM area and a comprehensive product line in SOA and BPM
      • Significantly expanded consulting and engineering resources in the U.S. — it has won U.S./U.K. customers and gained significant growth ratio outside Japan
      • Strong presence in human-to-human BPM area that offers strong capability in orchestration
      • Deep understanding of back-end integration requirements, with a long history of supporting the mainframe environment
      • Strong capability in composing, sequencing and managing services with Interstage Service Integrator/Fujitsu enterprise service bus (ESB) accompanied by service registry and repository (CentraSite)
    • Customers Media/ IT IT Healthcare
    • Overview / Agenda
      • Definitions of Terms & Motivation
      • The Evolution of Workflow / BPM
        • How the technology has developed over time
        • Human BPM and EAI Convergence
      • A New Enterprise Architecture for Agility
      • Five Key Standards
        • BPMN, XPDL, BPEL, Wf-XML, BPAF
      • What is the Ultimate Goal?
        • Business Level Agility
    • Terms is defined in a is managed by a composed of which may be Process Definition Representation of what is intended to happen Business Process What is intended to happen Workflow Management System ( BPMS ) Activities Manual Activities Automated Activities Work Items Invoked Applications Process Instance used to create & manage composed of Representation of what is actually happening Controls the automated Aspects of the process. includes one or more Not managed by BPMS during execution are represented by Tasks allocated to a Workflow Participant. Services called as part of process Activity Instances subprocess
    • Motivation Drivers for Business Process Management (BPM) Performance Business Process Improvement Engineering of Process-aware IS Compliance Mandated compliance (e.g. SOX) Desired compliance (e.g. ISO, ITIL)
    • 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
    • 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
    • The Evolution of Workflow and BPM
    • 1990  Workflow in the Brain Enterprise Application A “ Account Management” Background Check Conformance Guidelines Application Logic in Monolithic Program UI “ Screens” list Accts new Acct update Acct delete Acct
    • 1993  Assist Work Sequence Enterprise Application A “ Account Management” Background Check Conformance Rules Application Logic in Monolithic Program UI “ Screens” list Accts new Acct update Acct delete Acct background check create account check guidelines Launches UI User accesses original UI directly Human BPM/Workflow:
    • 1996  Distribute Work Enterprise Application A “ Account Management” Background Check Conformance Rules Application Logic in Monolithic Program UI “ Screens” list Accts new Acct update Acct delete Acct background check create account check guidelines Launches
    • 2002  Backend Web Services Enterprise Application A “ Account Management” Background Check Conformance Rules Application Logic Service Oriented Architecture Exposed Web Services list Accts new Acct update Acct delete Acct enter info create account bg check rules Review UI connects user to process engine, not the back-end applications
    • 2005  Composite Services Give IT Agility Old Rules Enterprise Application A “ Account Management” Background New Rules list Accts new Acct update Acct delete Acct enter info create account call 1 Review ESB / BPEL Application Logic Exposed Web Services Composite Service
    • 2005  Composite Services Give IT Agility Old Rules Background New Rules list Accts new Acct update Acct delete Acct enter info create account call 1 Review ESB / BPEL Application Logic Exposed Web Services Composite Services
    • Human Activities: 3 Phases Review Automated phase before to prepare for the task Wait phase for Human to do the work, includes timers and escalation logic Automated phase after to take care of results of the task User Interface (while waiting) Note: this notation is not standard!
    • Future  Simplify as “Human Steps” Enterprise Application A “ Account Management” Background Conformance Rules Application Logic Exposed Web Services list Accts new Acct update Acct delete Acct call 1 Review ESB / BPEL enter info Composite Service To People: Looks like two steps! Much simpler.
    • Separation of Responsibility
      • 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
      Enterprise Application A “ Account Management” Background Rules list Accts new Acct update Acct delete Acct ESB / BPEL call 1 Review enter info
    • Separation of Development
      • 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
      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 Who? When? What? How?
    • Human Process Management vs. Enterprise Application Integration
    • 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
    • Human BPM/Workflow
      • Mainly Human Centric Activities
      • Collaboration between participants
        • May be supported by BPM system
        • May occur outside automated system (direct human interaction)
        • Long process duration
      • Projects tend to be driven by Business
      • Almost always require integration with applications or technologies
      • Integration capabilities usually not as rich as products with origins in EAI
    • 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
    • Human BPM has Management
      • Time management
        • Delegate, alarm, overdue, delay, vacation
      • Supervision
        • Team management, Process supervision, exception
    • Human BPM Represents Users
      • User management
        • Rights, assignment, skills, Organizational structure
      • Task assignment
        • Self-service, workload, distribution, dynamic assignment
    • 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
    • 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
    • Standards Overview
    • BPM Standards Summary
      • BPMN – Business Process Modelling Notation
      • is widely accepted as standard for the look of a process
      • XPDL – XML Process Definition Language
      • promotes 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 Collaboration
      • provides runtime integration between process services
      • BPAF - Business Process Analytics Format
      • Standard event format for Process Intelligence Tools
    • Standards Landscape Collaboration Agreement Process Model Diagram UML Activity Diagrams BPMN 1.0 Repository & Discovery UDDI Assurance WS-Security SAML Process Model Definition/Storage Formats ebXML BPSS ebXML CPA/CPP Transport Reliability ebXML-RM WS-RM ... Transport Layer HTTP JMS ... Encoding SOAP / Attachments WS-Addressing Data Definition XML-Schema Service End Point Definition WSDL Service Orchestration Choreography Definition WS-CDL BPEL Monitoring & Audit WfMC IF5 1.0 (CWAD) Runtime Interaction Wf-XML 1.0 WfMC WAPI Presentation XForms Service/ Human Interaction BPEL4People Near Completion Stable Under Development Ideation Stage BPMN 1.1 Process 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
    • Standards Landscape discuss today XPDL 2.1 BPEL Wf-XML 1.0 Wf-XML 2.0 BPMN 1.0 BPMN 1.1
    • Workflow / BPM Reference Model
    • Workflow / BPM Reference Model BPMN XPDL SOAP BPEL Wf-XML BPAF REST
    • 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
    • XPDL: XML Process Definition Language
      • The FILE FORMAT for a process definition
      • Exchange 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
    • 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
    • Process Design Ecosystem Vendor F Vendor E SOA Design Workflow Design Vendor C Vendor D Vendor B Vendor 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 People Integration Limited Portability BPMN BPMN BPMN BPMN
    • Wf-XML: Runtime Integration
      • Sales Process on Server A
      Legal Review Process on Server B Draft Aprove Legal Review Close Contract Specialist Tort Specialist Exec Analyst Wf-XML based on SOAP or REST Standard Protocol between process engines allows one process to reuse another across technologies.
      • Standardized Event Format
        • XML Syntax
        • Defined Attribute Semantics
      • Process State Model
      • Activity State Model
      BPAF: Business Process Analytics Format Business Process Intelligence Warehouse Business Process Management System Servers
    • Standards Timeline - Releases WfMC OASIS BPMI OMG WPDL XML BPMN 1.0 XPDL 2.0 XPDL 2.1 1994 1998 2000 2001 2008 2010 2007 2006 2009 2004 2005 2002 2003 XPDL 1.0 BPMN 1.0 BPMN 1.2 BPMN 1.1 BPMN 2.0 Ref Model Wf-XML-R Wf-XML 1.0 Wf-XML 1.1 BPEL4People BPEL XPDL 3.0 BPAF
    • Goal: Business Level Agility
    • Agility = Business Driven Change w/o Programming Enterprise Application A “ Account Management” Background Rules list Accts new Acct update Acct delete Acct call 1 Review ESB / BPEL enter info News Flash! Some other bank sued! Need to respond quickly to avoid risk!
    • Agility = Business Driven Change w/o Programming Background Rules call 1 Review ESB / BPEL enter info Immediate Response: Handle the problem manually with a specialist team -- the next day . Enterprise Application A “ Account Management” list Accts new Acct update Acct delete Acct legal check
    • Agility = Business Driven Change w/o Programming Background Rules call 1 Review ESB / BPEL enter info Eventually: Automate the step with a service, and eliminate the manual review team a few weeks or months later. Enterprise Application A “ Account Management” list Accts new Acct update Acct delete Acct Legal Check
    • 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 start
      • Key Benefits:
        • Business Level Control & Agility
      • Standards 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
    • 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
    • Questions? Interstage BPM Studio available free at http://www.fsw.fujitsu.com/support/ibpm_studio/ WfMC: Process Thought Leadership.
    • Thank You!
      • Keith D Swenson
      • Technical Committee Chairman
      • Workflow Management Coalition
      • Vice President of R&D
      • Fujitsu Computer Systems Corporation
      • Contact Information:
      • +1 408 859-1005
      • [email_address]