Don’t Program a System, Educate It!

Modern decision management techniques enable business decisions by supporting a path from data to decisions and actions. Wherever people use stand-alone Business Rules, Complex Event Processing, Predictive Analytics, Optimization systems or their combinations, they prefer to put in charge subject matter experts and not software developers.  Actually, all these systems tend to be declarative and allow customers to feed their systems with externally maintained business knowledge, e.g. historical data and/or already known business rules. Nowadays people in a way want to educate a general purpose system with their domain-specific knowledge avoiding traditional programming. Continue reading

Posted in Decision Management, Predictive Analytics, Tools and Technologies, DMN | Leave a comment

OpenRules Dialog Questions in Multiple Tables

If you have too many questions in your OpenRules Dialog project, you may want to split a large table “questions” into several tables. Continue reading

Posted in OpenRules Specific, Tools and Technologies | Leave a comment

OpenRules Business Glossary in Multiple Tables

By default OpenRules provides a glossary template that allows our customers to create their own business glossary in one table. Below I will explain how to split a glossary between multiple tables. Continue reading

Posted in DMN, OpenRules Specific | Leave a comment

Presentation at BBC-2015: Good Old UServ Product Derby in the Brave New World of Decision Management

James Taylor and I are giving a session at this year’s Building Business Capability conference on “Good Old UServ Product Derby in the Brave New World of Decision Management“at 4:50pm on the Wednesday of the show. Continue reading

Posted in Events, Decision Management, DMN | Leave a comment

Decision “Make a Good Burger” published an interesting June-2015 Challenge called “Make a Good Burger“. Below I describe an OpenRules-based decision model that provides various solutions for this problem.  Continue reading

Posted in Constraint Programming, Decision Management, Use Cases | 2 Comments

DMN 1.1 Issues: Aggregation

DMN defines “aggregation” in the following way:

“Multiple hits must be aggregated into a single result. DMN 1.0 specifies six aggregation indicators, namely: collect, sum, min, max, average. Optionally, the aggregation indicator may be included in the table. The default is collect.”

Below is a list of my issues with this DMN 1.0 approach. Continue reading

Posted in Decision Management, Discussions, DMN | Leave a comment

DMN 1.1 Issues: Multi-Hit Decision Tables

In an ideal world we would limit ourselves to Single-Hit decision tables that cover all possible combinations of the involved decision variables. However, DMN rightfully introduced so called “multiple hit” (or “multi-hit”) decision tables to stay closer to the decision modeling reality. Continue reading

Posted in Decision Management, DMN | 1 Comment