1. Can you explain that so I can understand it?! Helping business connect with process modelling & the value of BPMN! IIBAO&awa-OutaouaisChapter January2013 Michael Lachapelle! Business Model Fulcrum!

2. 1 Objectives! Capturing the business story to be modelled! Understanding that business, unlike programming, is often neither logical nor linear! Traits of BPMN that are 'business' friendly! 2 3 3. Nd and Sr isotopic data back for some Larvik Plutonic complex rocks indicates a Bulk Silicate Earth mantle source! 4. It was a good start for Gul, full ball angled in on middle that swerved in late. Kohli dabs it to mid-off.! 5. The analysts view schema-based! Is it a complete process?! Is it a sub-process?! What are the activities and decisions?! What are the inputs and outputs?! Its what I do! The business view experience-based! The challenge is more than language! 6. Our Project! 7. The problems:! 1!ThedepartmentalITsolu4onforcontract solicita4on&managementneedstobereplaced. 2! Theprocessesacrossalargedepartmentare fractured,inconsistent,andoutofsynchwith managementsunderstandingandclientsneeds 8. Hurdle #1! Who! 9. Focus on operational perspective real time experience! Needed to change the approach! 10. Hurdle #2! Connecting experience and modeling schemas ! 11. Usinganarra4veasan anchortolinkdecisions andac4onsineveryday business 12. Facilitator Business Analysts Wri4ng wall Working space structure! Recorders 13. The Story Structure! Pre-meeting work! Requirements Procurement Strategy Bid Solicita4on File Close-out Bid Selec4on Contract Award Contract Administra4on 14. so what did we learn! 15. Event driven not always linear! Can occur at an unspecied / unexpected time, or can put a process on hold! Can trigger a separate process! Can interrupt or terminate a process ! 16. how did BPMN help! 17. 5 Core components of BPMN! Ac4vi4es(7) Gates(5) Flows(4) Events(11) Ar4facts(4) 18. ! 1stLawofSimplicity Thesimplestwaytoachieve simplicityisthroughthoughAul reducCon JohnMaeda-Thelawsofsimplicity To engage the business people we needed to simplify our jargon! 19. ACTIVITIES! Ac4vity Collapsed Subprocess Loop Theworkperformed Brokendowninto componentac4vi4eson anothermap Mustbecompletedbefore movingon 20. Ac4vity Complete or correct before moving on! Complete yes no Loop 21. Where are the bottlenecks?! 22. EVENTS! Thingsthathappenwhile theworkisperformed During Start End message 4me error link 23. Interruptions and limitations! 24. GATEWAYS! Howaowsplitsandjoins Parallelac4vi4esonall pathsmustbecompleted Inclusiveac4vi4esonany pathmustbecompleted 25. Mapping multiple options! yes no no no yesyes Op4on1 Op4on2 Op4on3 D1 D3D2 26. Splitting, joining paths! 27. FLOWS! Connec4ngobjectsandac4vi4es Op4onalmayhappenas choiceorwithacondi4on Defaulttobefollowed unlesscondi4onapplies Messageowwhenyouhave externalpoolorswimlane 28. Following the ow of work! 29. ARTIFACTS! Objects,data,informa4onandgrouping Text Annota4on DataObjects Groupingof items Informa4on aboutthe modeloran aspect 30. Grouping around a time frame! 31. Grouping around a time frame! 32. Recap! Engagement of business people is often about the story (narrative) linking activities and decisions! Business doesnt always ow sequentially or in logical steps, sometimes its messy ! BPMN has added approaches and notation that make documenting the business experience more effective ! 1 2 3 33. Business Model Fulcrum Thanks. MichaelLachapelle m-613-447-3948 e-michael@businessmodelfulcrum.com t-@mike_lach s-michael_lachapelle l- hcp://ca.linkedin.com/in/michaellachapelle If you wish to use material from this presentation please observe the rules of creative commons licensing.