
14.10.2026, 10:44:39
Source: LinkedIn Org Feed (DNA Evolutions)
Rules like "customers with a given keyword in their id should each ideally be the first node of their route" are too specific to be built into a generic optimizer. With the Open Assessor, you write such a rule in Java, and the optimizer evaluates it with every solution candidate.
A rule can look at one node in its route, for example at the node before it, or at the route as a whole. When the rule is broken, it adds cost and reports a violation for that node, with a message you define.
The rules steer by cost; a hard limit belongs in a native constraint.
Our node-level and route-level examples:
https://lnkd.in/eGGYGCqa
#JOpt #JOptTourOptimizer #Java #RouteOptimization
lnkd.in) may only resolve reliably when opened from the original LinkedIn post. 





































