{"id":1418,"date":"2015-02-25T15:35:50","date_gmt":"2015-02-25T21:35:50","guid":{"rendered":"http:\/\/garysamuelson.com\/blog\/?p=1418"},"modified":"2018-05-28T09:39:46","modified_gmt":"2018-05-28T15:39:46","slug":"process-management-case-cmmn-and-bpm-bpmn-together","status":"publish","type":"post","link":"http:\/\/garysamuelson.com\/blog\/?p=1418","title":{"rendered":"Process Management: Case (CMMN) and BPM (BPMN) Together?"},"content":{"rendered":"<p>Do I pursue a more holistic approach by purchasing a process-management system that includes both case (CMMN) and BPM (BPMN) capabilities?<\/p>\n<h3>\u00a0Argument for the inclusive (case+BPM) system approach:<\/h3>\n<p>1) Assuming we&#8217;re heading towards an integrated Case+BPM system (typically the situation when looking at artifact-centric applications). A stand-alone case system tends to increase integration complexity. A combined solution, for example a BPMS that does case-management, presents an almost seamless coupling between BPM and CMMN models. From an artifact-centric view, such as document management (insurance, finance, health), a combined system approach offers significant savings and reduced operations\/maintenance overhead.<\/p>\n<p>2) Reduction in analysis and development costs via reuse of task\/activity services between BPMN and CMMN models &#8211; this includes application (process-aware) run-times. In terms of the UI (UX), rules, and general SOA services, we&#8217;re looking at a considerable savings. HOWEVER&#8230; it&#8217;s best to avoid any sort of reusability goals during early adoption!\u00a0\u00a0 Focus on process 1st and reuse later. In-other-words, let the SOA team worry about reuse while the process-management people focus on core business-value.<\/p>\n<p>3) Shorter distance to market with case solutions versus BPMN models. This approach cuts BPMN analysis-paralysis from the project by focusing on &#8220;tasks\/activities&#8221; early. By allowing for ad hoc execution within a case model (though acknowledging rules-based entry\/exit constraints) we avoid potential delays induced by early attempts at a fully-wired BPMN model. Noting that a BPMN model with a big ad hoc set of tasks IS NOT &#8220;process management&#8221;. An inclusive process-management platform (does both CMMN and BPMN), then provides the evolutionary path for migrating matured tasks\/activities into formalized BPMN workflows. Noting that we undertake this last step, from CMMN to BPMN, as an on-demand evolution of process requirements (e.g. &#8220;case&#8221; is BPMN-agile).<\/p>\n<p>&nbsp;<\/p>\n<h3>Arguments for a stand-alone case management solution:<\/h3>\n<p>1) BPM and case are very, very different in their support of object-centric requirements (e.g. ECM). Case is document oriented (object-centric). Attempting a BPM-practice against a case-oriented set of requirements demands additional focus on the risks associated with long-running business transactions implied with BPMN models.<\/p>\n<p>2) BPM practitioners tend to build context-tunneling as a matter of course during the construction of BPMN workflows. This is a given feature provided by the relationship between BPMN &#8220;lane&#8221; and &#8220;participant&#8221; within workflow models. The problem here is that case-management avoids this rut completely via its inclusive approach (with a focus on user and object centric requirements). In-other-words, case and BPM methodologies just don&#8217;t mix very well&#8230; from a general practice\/methodology perspective.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Do I pursue a more holistic approach by purchasing a process-management system that includes both case (CMMN) and BPM (BPMN) capabilities? \u00a0Argument for the inclusive (case+BPM) system approach: 1) Assuming we&#8217;re heading towards an integrated<a class=\"moretag\" href=\"http:\/\/garysamuelson.com\/blog\/?p=1418\"> Read more&hellip;<\/a><\/p>\n","protected":false},"author":1,"featured_media":1581,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,11,21],"tags":[],"class_list":["post-1418","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business-process-management-best-practices","category-bpm-methodology","category-case"],"_links":{"self":[{"href":"http:\/\/garysamuelson.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1418","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/garysamuelson.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/garysamuelson.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/garysamuelson.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/garysamuelson.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1418"}],"version-history":[{"count":6,"href":"http:\/\/garysamuelson.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1418\/revisions"}],"predecessor-version":[{"id":1424,"href":"http:\/\/garysamuelson.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1418\/revisions\/1424"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/garysamuelson.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/1581"}],"wp:attachment":[{"href":"http:\/\/garysamuelson.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1418"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/garysamuelson.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1418"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/garysamuelson.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1418"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}