Planning Optimal Assignment Rules
In general, the fewer assignment rules, the better. When you use fewer assignment rules, you achieve the following long-term gains:
Reduce maintenance. The assignment administrator (AA) has fewer rules to manage, thus reducing time spent on checking quality of assignment rules.
Scalability. When new organizations or divisions require Assignment Manager capability, there is no need to rewrite the existing rules to accommodate the new requirements.
Reduce system resources. Assignment Manager, like other processing applications, is resource intensive. By reducing the number of assignment rules, the amount of system resources required are minimized including database, Siebel Server, and the time window for territory alignments.
Enhance performance. Assignment processing and throughput is increased when there are fewer rules because the Assignment Manager engine has a limited dataset to work on.
For normalization purposes, use the following guidelines to optimize your assignment rules:
Avoid duplication of assignment rules across objects.
For example, an account rule and a professional rule might have the same position assigned (within the same ZIP Code, or other postal code). In this case, you can collapse these two assignment rules into a single rule.
For custom assignment criteria with similar values across multiple objects, build a single criteria so that you can consolidate assignment rules.
Consolidate positions across multiple assignment rules.
After assignment rules are created, determine the 10 most popular positions used in assignment rules. If one or more positions are used in more than 90% of the assignment rules, then you might want to consider alternate paths.