Carasik BPM ECM
Download as PPT, PDF1 like369 views
This document summarizes a three-part course on business process modeling and enterprise content management. Day 1 covers why and how to model business processes using the BPMN language. Day 2 focuses on the lifecycle of electronic information and content management systems. Day 3 is a survey of process modeling and content management tools with case study presentations.
Carasik BPM ECM
- 1. Business Process Management and ECM, session 1 Presented to China University of Geosciences Bob Carasik, guest lecturer
- 2. 欢 迎！上 课！ Our schedule: Three ½ day sessions. 15 minute break, 10:15 to 10:30 Homework both nights, some team assignments Quiz on Friday morning Exchange of contact information
- 3. Course Outline Day 1, Business Process Modeling Why do want to Model a Business Process? The BPMN Language, and other languages How to build a Business Process Model Bring the Model to Life with Business Process Management Day 2, Enterprise Content Management The life cycle of electronic information Capture, store, search, retrieve, retain/destroy Components of Content Management systems Day 3, Survey of BPM and ECM tools, case study presentations
- 4. What is Process Modeling? What is a business process? How people and Information systems work together to meet a demand on their organization There is a starting event, activity and defined output or outputs What is a model? Formalize the knowledge and rules from IT and workers Abstract representations of what, and who, makes the process happen. Uses of a Process model Analysis Simulation (out of scope for this course) Process automation with BPEL (day 2)
- 5. Process Modeling, Why? Why create a model of a business Can we learn something about the business? Can we CHANGE something about the business? Competition forces changes Update products Improve organization Provide new services Regulation and compliance requirements How can we use our resources better?
- 6. Goals of Process Modeling Enabling change First, fully understand what the business does Use one design language for business and technical staff Trials of alternative ways of doing things Create workflows from the design Identify process measurements and evaluate progress Supporting regulatory compliance Demonstrate adherence to quality standards
- 7. Making a process model The “work itself” plus Description of information systems Equals A model
- 8. Three levels of detail Process Map: simple flowchart Process Description: add information to the map Process Model: supports analysis, simulation, and execution
- 9. If we’ve done it right, then … Changing processes is easier: “agility” Spotting problems is easier: “transparency” People are freed up for other work. What else might work better if we have a model?
- 10. A Reference model, from the Workflow Management Coalition
- 11. Definition of “workflow” The defined series of tasks within an organization to produce a final outcome. Workgroup applications allow you to define different workflows for different types of jobs. So, for example, in a publishing setting, a document might be automatically routed from writer to editor to proofreader to production. At each stage in the workflow, one individual or group is responsible for a specific task. Once the task is complete, the workflow software ensures that the individuals responsible for the next task are notified and receive the data they need to execute their stage of the process.
- 12. Workflow model and screen shot
- 13. A workflow task list from http://www.skelta.com/products/screenshot-gallery/screens.aspx#TaskList
- 14. What do we express in a modeling language? The goal: graphic representation with formal precision Business processes Functions Flow of control Flow of information Probability
- 15. Business Process Modeling Language (BPMN) Why BPMN? Based on past languages (UML, WSFL, XLANG) Now standard, many vendors have implementations Components Events Activities Sequence Flows Gateways
- 16. Summary of BPMN diagram elements
- 17. A simple insurance process (From Havey book, p. 147)
- 18. Events “Occurrence that triggers a business process” Have beginning, intermediate, end states Types: Basic, message, timer, rule, exception, cancellation, compensation, link, multiple, termination
- 19. Activities A step in a process that performs work. Atomic (task) or compound (contains process) Simple Compensated Ad Hoc Looping Multiple instances Examples: Call a Web service, Receive a message (wait for input from field representative) Send a message (update customer contacts) Manual task (call customer at home) Script reference to another task
- 20. Sequence Flows Normal flow Default flow; depends on conditions “Guarded”, depends on rule evaluation
- 21. Gateways Splits and joins of control flow
- 28. BPMN Modeling constructs There are 52 graphic objects, 6 connecting objects, 2 grouping objects But only these few are really common: Normal Flow Task End Event Start Event Pool Data-Based XOR Start Message Text Annotation Message Flow Parallel Fork / Join Lanes (subdivides Pool) Gateway Data-Based XOR Sub Process Association Data Object Intermediate Timer Intermediate Message End/Terminate
- 29. An example: auto insurance claim
- 30. Our goal: running a BPM model with BPEL BPEL language XML-based scripting language Includes WSDL for system interface definitions Tools can generate it from BPMN models
- 31. Retailer process, from OnJava
- 32. BPEL code, 1 1 <process name="Retailer" 2 targetNamespace="http://acm.org/samples" suppressJoinFailure="yes" 3 xmlns:tns="http://acm.org/samples" 4 xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" 5 xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/ business-process/"> 6 7 <!-- some code omitted - -> 8 9 <!-- Mainline process code starts here --> 10 <sequence name="main"> 11 12 <!-- Step 1: Consumer sends PO --> 13 <receive name="receiveInput" partnerLink="consumer" portType="tns:Retailer" 14 createInstance="yes" operation="sendPO" variable="po"> 15 <!-- Use the inbound PO message as the basis for correlation --> 16 <correlations> 17 <correlation set="poset" initiate="yes"/> 18 </correlations> 19 </receive> 20
- 33. BPEL code, 2 21 <!-- Step 2: Send receipt ack to consumer --> 22 <invoke name="callbackClient" partnerLink="consumer" 23 portType="tns:RetailerCallback" operation="poReceipt" 24 inputVariable="po"/> 25 26 <!-- Step 3: create PO record in internal database --> 27 <invoke name="writePOToDB" partnerLink="retailerDB" portType="tns:RetailerDB" 28 operation="createPO" inputVariable="po"/> 29 30 <!-- Step 4: send PO to warehouse --> 31 <invoke name="sendPOToWH" partnerLink="warehouse" portType="tns:Warehouse" 32 operation="sendPO" inputVariable="po"/> 33 34 <!-- Step 5: wait for warehouse response --> 35 <receive createInstance="no" name="receiveWHResponse" partnerLink="warehouse" 36 portType="tns:WarehouseCallback" operation="onResult" 37 variable="poResponse"> 38 <!-- correlate on identifiers in initial PO --> 39 <correlations> 40 <correlation set="poset" initiate="no"/> </correlations> </receive>
Editor's Notes
- #3: Welcome! Start course! 欢 迎！上 课！