Currently evaluation-strategies in solara.mp support the function of substrategies. However, these substrategies are always applied to all characteristics of the part.
We are currently lacking the possibility to apply different strategies within one part and this circumstance is causing us a lot of extra work and it very prone to human error. In our internal requirements, capability limits can differ based on characteristics-type, characteristics-class or even characteristics-specification.
The solution already in place within qs-stat for “specified requirements”, could be a great function also for solara.mp and with the extension to add the specification as a criteria (K2152) it could fulfill the requirement and would really contribute in reducing the number of evaluation-strategies.
