Experience: DMN was developed by people having decades of experience with Decision Management.As rules (leading to decisions) change much more often that processes or entities, being agile in changing rules is absolutely necessary for being future ready! Given appropriate tooling it might even be realistic that business people can directly edit concrete rules within a given structure (more on this later). This allows to use business analysis results as “code” making changes to the rules behind the decision really easy. Business-IT-Alignment: Decisions can be modeled and executed using the same notation.The standard is supported by many software products you are less dependent on any particular vendor’s products. Standard: DMN is not owned by a certain enterprise but by an institution (OMG), which is already established through other world-wide standards, e.g., BPMN or UML.Who (which employee) should handle a new filed claim? The example is straight forward but very real for a lot insurance companies which currently transform their processes from manual/paper-based work into partly automated/digital form. The example: Task Assignment/Routing of new claims So high time to give an introduction into DMN and present some learnings we had so far. Over the last months we discussed a lot of Business Rules use cases with clients and sketched solutions in DMN. It is currently on the home stretch of standardization and camunda will release camunda BPM 7.4 including DMN in November. DMN defines an XML format and is executable on Decision/Business Rules Engines. DMN is a brand new standard of the OMG, it stands for Decision Model and Notation and is clearly related to BPMN and CMMN.
0 kommentar(er)
