- Ikemefuna Allen
When we created our Business Flows reference model and set of best practice methodology over three years ago, our objective was to provide a simple process repository for everybody. The challenge we saw, was finding the right balance of being specific as well as being relevant for a wide range of customers.
The use cases and feedback from customers show that we accomplished this job well, but also let us think about what we can do developing it further.
Since the beginning of the year we have been working on upgrading model contents, conventions and methodologies and are now happy to announce the new release. version 3, of Business Flows.
The main points we have changed or added for the current release are
Additional Content (Domains, Scenarios)
We now cover several additional domains:
Lead to Opportunity (L2O)
After Sales and Services (ASS),
Forecast to Plan (F2Pl) and
Master Data Management (MDM)
Especially ASS and MDM are hot topics as many industrial companies strategically want to transform their business model more towards offering services and solutions rather than just products. This in combination with ever shorter product-innovation-cycle-times and growing markets has a massive impact on master data processes.
They need to become better integrated, faster and more reliable in order to facilitate the core processes.
Simplified role model
We have decided to discontinue the roles on BPMN level and just provide the department role on process level.
The feedback on the value of roles associated with individual processes and process steps was ambivalent as most customers have very individual organizations and corresponding role definition and naming. The added value of having an example was diminished by the discussions on how best to adapt to the actual situation.
Also, frequently - depending on size of departments and organization the role model has to be more differentiated or sometimes less differentiated.
Use case related content in detailed process charters in BPMN
We encounter two main types of use cases for the most detailed process level modeled in BPMN:
Act as a modeling template to be copy/adjusted rather than starting on a white modeling canvas.
Provide content on the main activities, the degrees of automation, inputs/outputs etc in order to facilitate process workshops and business requirements sessions.
We think the latter use case is of greater value to Business Flows users for which we provide the BPMN processes and have decided to focus on accumulating relevant information into dedicated sections. We call this the process charter.
The models still comply with the BPMN notation but are now structured according to the fixed scheme shown below.