Today, Adam DeJans Jr. wrote: “Every business operates with tolerance: delivery delays, budget overruns, staffing gaps. Good models price those instead of eliminating them.” Two weeks ago, I posted the related article “Decision Model Tolerance” on LinkedIn.
Most experts and practitioners had agreed long ago that decision models should be declarative, meaning a user specifies WHAT the decision problem is and provides test cases with the desired outcome, and then the underlying decision engine or system automatically determines HOW to find the solution. Rule Engines and Constraint Solvers were specifically designed to support the declarativity.
Continue readingDMCommunity has already received five solutions for its Oct-2025 Challenge “Decision with two objectives” which is looking for decision models that help a web designer to select certain features while satisfying budget and value constraints. It is quite a simple problem for most linear or constraint solvers, so it is no wonder that the first 3 solutions utilized different solvers: Seeker, Pymoo, and OPL CPLEX. What makes this problem more interesting is that it involves two conflicting objectives: total value and total cost. Our decision models are supposed to devise a rational way to trade them against each other.
Continue reading
OpenRules - Decision Intelligence Platform 