Using Special Rules to Create Configurable Matrices
Special rules apply when you create rate matrices and salary increase guidelines matrices, and specific result ID values must exist in each type of matrix in order for the system to be able to process the matrix. Special rules are required because the components where these matrices are invoked will look for and process specific result IDs. If the correct result IDs do not exist, then the calling component will not know how to process the output.
Rate Matrix
This table lists the result IDs that must exist in a rate matrix that you plan to associate with a rate code. The list of expected result IDs is based on the rate code type:
Note: You do not need every result ID for each rate code type. You only need one of these result IDs for each.
|
Rate Code Type |
Result ID |
|---|---|
|
Flat Rate |
|
|
Hourly Rate + Flat Amount |
|
|
Hourly Rate |
|
|
Percent |
INCREMENT_PERCENT |
|
Points |
NEW_POINTS |
If you create a rate matrix that uses calculations, such as result IDs with the type of PERCENT_TO_APPLY, INCREMENT_PERCENT, and so on, you must select the Do not return Results check box for all other result IDs. This selection is necessary because the system requires that a rate matrix attached to a rate code can have only one result ID returned.
Salary Increase Matrix Attached to a Group Budget
The result IDs in the matrix must match the rate code type. This table illustrates the result IDs that are allowed based on rate code type:
|
Rate Code Type |
Allowed Combinations of Result IDs |
|---|---|
|
Flat, Hourly, or Flat + Hourly |
The matrix must have one of the following three combinations of result IDs:
|
|
Percent |
The matrix must have one of the following two combinations of result IDs:
|
|
Points |
The matrix must have one of the following two combinations of result IDs:
|
When the salary increase matrix is attached to a group budget, the system always looks for the DEFAULT_PERCENTAGE, DEFAULT_AMOUNT, or DEFAULT_POINTS result ID, and it will use that result ID to calculate the budget or assign increases.
However, the system performs special processing when the matrix includes both DEFAULT_PERCENTAGE and AMOUNT result IDs. In this case, the AMOUNT result ID is treated like a lump sum increase amount. Since every row will have both a default percentage and an amount result, the system will first check to see if the value for AMOUNT is greater than 0. If the value is greater than 0, the system uses that value as a lump sum increase amount in the group budget. If the AMOUNT value is 0, then the system uses the value for DEFAULT_PERCENTAGE as a change percentage. This selection allows you to create a salary increase matrix that handles the cases for which a worker's compa-ratio or percent-in-range values are outside the standard guidelines.
This example illustrates a salary increase matrix that includes percent-in-range values that are outside the standard guidelines:
|
Perf Ra- ting |
0 |
50 |
100 |
1000 |
||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Min Pct |
Dflt Pct |
Max Pct |
Lump Sum |
Min Pct |
Dflt Pct |
Max Pct |
Lump Sum |
Min Pct |
Dflt Pct |
Max Pct |
Lump Sum |
Min Pct |
Dflt Pct |
Max Pct |
Lump Sum |
|
|
1 |
0.00 |
0.00 |
0.00 |
20.00 |
6.00 |
6.50 |
7.00 |
0.00 |
5.00 |
5.50 |
7.00 |
0.00 |
0.00 |
0.00 |
0.00 |
6.00 |
|
2 |
0.00 |
0.00 |
0.00 |
18.00 |
5.00 |
5.50 |
6.00 |
0.00 |
4.00 |
5.00 |
6.00 |
0.00 |
0.00 |
0.00 |
0.00 |
4.00 |
|
3 |
0.00 |
0.00 |
0.00 |
16.00 |
4.50 |
5.00 |
5.50 |
0.00 |
4.50 |
4.50 |
5.00 |
0.00 |
0.00 |
0.00 |
0.00 |
2.00 |
|
4 |
0.00 |
0.00 |
0.00 |
6.00 |
3.00 |
3.50 |
4.00 |
0.00 |
3.00 |
3.50 |
4.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
Note that the matrix includes an explicit breakpoint with a Percent in Range (PIR) value of 0. This breakpoint is required to handle all workers whose PIR is negative, as compared to their salary range. A breakpoint with a value of 1000 also exists. This breakpoint is required to handle all workers whose PIR is greater than 100. The value 1000 is an arbitrarily high value chosen to ensure that all possible PIR values greater than 100 are captured.
Note how the LumpSum values are non-zero only for breakpoints 0 and 1000. All other breakpoints have LumpSum=0. This setting means that a worker whose PIR is between 0 and 100 will get increases based on the DEFAULT_PERCENTAGE guideline, while those whose PIR is outside the standard range (less than 0 or greater than 100) will get a flat amount increase based on the LumpSum AMOUNT guideline.