Parent Topic |
The Sorting Rules button displays a screen to configure how to rank employees who qualify for each of the passes. Employees are displayed on the results listing in the order of the points ranking. If the employees are contacted in the order of the listing, those at the top of the list are most likely to be called off.
For each pass, select the rules to be used in sorting. Only Selected Rules are used in sorting qualified employees.
The following Sorting Rules are available for selection with the Schedule Assistant Call Off Feature:
Determines if qualified employees are to be sorted based on their date of hire.
Additional fields determine if points are awarded based on years, months, days or hours and whether the sorting order is most recent hire or earliest hire date.
The following fields display when configuring the Hire Date sorting rule:
|
Determines how specifically the sorting of employees is to be conducted, by years, months, days or hours. For example:
|
|
The number of Units (years, months, days) to be bundled together for one Increment. For example, every 6 months could be one increment. If an increment is 1 point, employees would get 1 point for every six months they have been employed. |
|
Determines whether to award employee rule-points for each value, or to combine values in groups (e.g. 5, 10, 30, etc.). For example if the sorting rule is on seniority hours, the increment can be set up for 10. Employees would get 1 point for every 10 hours of seniority they have. In this example, the value of 1 point is determined by the Value Per Increment entered. |
|
Determines if the employees are sorted in ascending or descending order based on the rule points earned.
|
The Hide When Run check box determines whether these fields are visible and editable when running the wizard. More about the Hide When Run check box.
The Hide When Run check box option determines whether these fields are available for configuration while the wizard is being run.
This rule ranks the employees based on the number of hours they are scheduled above their approved weekly or pay period hours, and is used with the Call Off wizard.
Employees can be sorted in ascending or descending order, by incremental value.
The following fields display when configuring the sorting rule:
|
Indicates the number of "points" that the employee earns for each increment unit they qualify for. For example, if the employee is scheduled 10 hours above their approved hours, and the table is set up to award 1 value point for every 5 units (minutes), the employee would earn 2 points. If more than one sorting rule is used, higher value can be given to rules that carry more weight. For example if employees are given points for Over Overtime Hours and also for Seniority, determine which rule should carry more weight. If you want employees under their approved hours to be more important, you could give that rule a value of 100 for each increment. Then seniority value would be a "tie breaker" between employees with more seniority. |
|
Determines whether to award employee rule-points for each value, or to combine values in groups (e.g. 5, 10, 30, etc.). For example if the sorting rule is on seniority hours, the increment can be set up for 10. Employees would get 1 point for every 10 hours of seniority they have. In this example, the value of 1 point is determined by the Value Per Increment entered. |
|
Determines if the employees are sorted in ascending or descending order based on the rule points earned.
|
The Hide When Run check box determines whether these fields are visible and editable when running the wizard. More about the Hide When Run check box.
The Hide When Run check box option determines whether these fields are available for configuration while the wizard is being run.
This rule ranks the employees based on the number of hours they are scheduled above their overtime weekly or pay period hours, and is used with the Call Off wizard.
Employees can be sorted in ascending or descending order, by incremental value.
The following fields display when configuring the sorting rule:
|
Indicates the number of "points" that the employee earns for each increment unit they qualify for. For example, if the employee has 10 overtime hours, and the table is set up to award 1 value point for every 5 units (hours), the employee would earn 2 points. If more than one sorting rule is used, higher value can be given to rules that carry more weight. For example if employees are given points for Over Overtime Hours and also for Seniority, determine which rule should carry more weight. If you want employees under their approved hours to be more important, you could give that rule a value of 100 for each increment. Then seniority value would be a "tie breaker" between employees with more seniority. |
|
Determines whether to award employee rule-points for each value, or to combine values in groups (e.g. 5, 10, 30, etc.). For example if the sorting rule is on seniority hours, the increment can be set up for 10. Employees would get 1 point for every 10 hours of seniority they have. In this example, the value of 1 point is determined by the Value Per Increment entered. |
|
Determines if the employees are sorted in ascending or descending order based on the rule points earned.
|
The Hide When Run check box determines whether these fields are visible and editable when running the wizard. More about the Hide When Run check box.
The Hide When Run check box option determines whether these fields are available for configuration while the wizard is being run.
Sorts the employees based on their seniority tracking date. If no value is entered in the employees' Seniority Date field in the employee record, seniority is determined by the Hire Date.
The following fields display when configuring the Seniority Date sorting rule:
|
Determines how specifically the sorting of employees is to be conducted, by years, months, days or hours. For example:
|
|
The number of Units (years, months, days) to be bundled together for one Increment. For example, every 6 months could be one increment. If an increment is 1 point, employees would get 1 point for every six months they have been employed. |
|
Determines whether to award employee rule-points for each value, or to combine values in groups (e.g. 5, 10, 30, etc.). For example if the sorting rule is on seniority hours, the increment can be set up for 10. Employees would get 1 point for every 10 hours of seniority they have. In this example, the value of 1 point is determined by the Value Per Increment entered. |
|
Determines if the employees are sorted in ascending or descending order based on the rule points earned.
|
The Hide When Run check box determines whether these fields are visible and editable when running the wizard. More about the Hide When Run check box.
The Hide When Run check box option determines whether these fields are available for configuration while the wizard is being run.
The seniority hours rule is used with organizations that track employee seniority by earned hours rather than hire date or seniority date.
The following fields display when configuring the Seniority Hours sorting rule:
|
The number of minutes to be bundled together for one Increment. For example, 60 minutes could be one increment. If an increment is 1 point, employees would get 1 point for every 60 minutes of Seniority Hours they have earned. |
|
Determines whether to award employee rule-points for each value, or to combine values in groups (e.g. 5, 10, 30, etc.). For example if the sorting rule is on seniority hours, the increment can be set up for 10. Employees would get 1 point for every 10 hours of seniority they have. In this example, the value of 1 point is determined by the Value Per Increment entered. |
|
Determines if the employees are sorted in ascending or descending order based on the rule points earned.
|
The Hide When Run check box determines whether these fields are visible and editable when running the wizard. More about the Hide When Run check box.
The Hide When Run check box option determines whether these fields are available for configuration while the wizard is being run.
Sorts employees based on the awarded skill level of the employees' position.
Employees can be sorted in ascending or descending order, by incremental value.
The following fields display when configuring the Skill Value sorting rule:
|
Indicates the number of "points" that the employee earns for each increment unit they qualify for. For example, if the employee has seniority months of 50, and the table is set up to award 1 value point for every 5 units (months), the employee would earn 10 points. If more than one sorting rule is used, higher value can be given to rules that carry more weight. For example if employees are given points for Under Approved Hours and also for Seniority, determine which rule should carry more weight. If you want employees under their approved hours to be more important, you could give that rule a value of 100 for each increment. Then seniority value would be a "tie breaker" between employees with more seniority. |
|
Determines whether to award employee rule-points for each value, or to combine values in groups (e.g. 5, 10, 30, etc.). For example if the sorting rule is on seniority hours, the increment can be set up for 10. Employees would get 1 point for every 10 hours of seniority they have. In this example, the value of 1 point is determined by the Value Per Increment entered. |
|
Determines if the employees are sorted in ascending or descending order based on the rule points earned.
|
The Hide When Run check box determines whether these fields are visible and editable when running the wizard. More about the Hide When Run check box.
The Hide When Run check box option determines whether these fields are available for configuration while the wizard is being run.
This rule ranks employees by the most recent date they were assigned a certain activity code or pay code. This rule can be used to sort employees by codes associated with low census, so that employees who were sent home the most recently are now the last employees on the list to send home.
The following fields display when configuring the sorting rule:
|
Indicates a specific activity code assigned to employee schedules that should be used to sort employees. Note: To include several activity codes in the same sort sequence, use the Activity Group option. |
|
Indicates an activity group which groups together multiple activity codes that should be used to sort employees. For example, an activity group can be set up to group together all the Low Census activity codes. Employees can then be sorted by the last time they were assigned any of the low census activity codes. |
|
Indicates a specific pay code associated with employee schedules that should be used to sort employees. (To include several pay codes in the same sort sequence, use the Pay Code Group option). |
|
Indicates a pay code group which groups together multiple pay codes that should be used to sort employees. For example, a pay code group can be set up to group together all the Low Census pay codes. Employees can then be sorted by the last time they were assigned any of the low census pay codes. |
|
Determines the number of days previous to the highlighted date that the system will search. For example, if this value is set to 365, the system will search the previous 365 days for the indicated activity code/pay code. |
|
Determines whether the last occurrence of an activity code/pay code should be ranked by number of years, days, or months. |
|
Indicates the number of "points" that the employee earns for each increment unit they qualify for. For example, if the employee has a matching pay code or activity code 30 days previous to the highlighted date, and the Units field is set to Days and the Units per Increment value is set to 5, the employee would get 1 point for every 5 days. Therefore, the employee would get 6 points for 5 days (30/5 = 6) |
|
Determines whether to combine rule point units in groups (e.g. 5, 10, 30, etc.). For example, if this increment is set to 10, employees get 1 point for every 10 days since they were last awarded a qualifying activity/pay code. If this increment is set to 1, employees get 1 point for every day they were last awarded a qualifying activity/pay code. |
|
Determines if the employees are sorted in ascending or descending order based on the rule points earned.
|
The Hide When Run check box determines whether these fields are visible and editable when running the wizard. More about the Hide When Run check box.
The Hide When Run check box option determines whether these fields are available for configuration while the wizard is being run.
Determines whether the employees are sorted in ascending or descending direction based on the total points they have earned for the Sorting Rules.
The Hide When Run check box determines whether these fields are visible and editable when running the wizard. More about the Hide When Run check box.
The Hide When Run check box option determines whether these fields are available for configuration while the wizard is being run.
The following additional section options are available in the left pane: Adding a Call Off Selection Style |