Job Allocation Pass Field Description

General

*Denotes a required field.

IMPORTANT: The word ‘job’ when using Blueprints means a blueprint position.

Items listed in menu boxes may be different than labeled in the table below due to terminology modifications. For example, organizational levels such as Units could be Lines, Stations could be Areas, Plants, Cells... a Rank could be Job Title, a work status could be a work code, blueprint positions could be jobs... when in doubt go to the Terminology page: Setup > General > Terminology

General Area: Criteria used to return a group of people.

Field Name	Description
*Name	The name of this pass.
List	Optional - An additional filter used to exclude people, and further narrow the list of candidates returned by the List associated in the Job Allocation Strategy. These are the people that will be assigned specifically for that pass (for example, unallocated only and sorted by seniority order). Note: If left blank the system will use the List as is from the Job Allocation Strategy. The main purpose of the List is to disqualify certain users, qualify candidates, and then sort the candidates in some order, such as seniority.
Exclude fully allocated people and positions	Select to exclude candidates that are already allocated to blueprint positions; and exclude blueprint positions that are fully allocated from going through this pass process.

Changing Times/Locations

Changing Times/Locations requires prior knowledge of Flexible Times and Shift Adjustment work code configurations and behaviors. This area handles shift assignment hours. The end result is to change the person's working times, and there are two options to do that: Flexible Times, or adding work codes to compensate for time-on or time-off gaps:

Change a person's schedule using the Flexible Times feature.
Change a person's schedule by adding corresponding working and non-working codes to reflect working and non-working periods of time.

The Job Allocation Pass determines whether to use Flexible Times or the Scheduled and Unscheduled work codes when processing the person’s staffing record or records. Both options are configurable in the selected Job Allocation Pass setup area, but when a person's time is changed, only one option is used, Flexible Times, or the Scheduled and Unscheduled work code option.

Field Name	Description
Use Flexible Times	Used to allow the Job Allocation tool to respect Flexible Times if set on the shift assignment work code. If this check box is cleared, the job allocation tool will ignore the Flexible Times setting on the shift assignment work code. For more information review Flexible Times topics.
Assign to Full Shift	Applicable when moving a person across distinct shifts. This option removes the original or previous shift record. If a person is moved to a shift that has a partial vacancy, the person will be scheduled for the entire duration of the new shift, and partially allocated for the job that is being filled. The staffing record will denote the duration of the job’s parent shift. For example, suppose that person X is scheduled on Shift 2, then moved to work a partial vacancy on Shift 3, the staffing record will show person X working Shift 3. Also see Previous Allocations field description below.
Scheduled Work Code	Shows a list of Regular Duty and Working type work codes. Select one for the Job Allocation Pass to apply if there is a working period of time not covered by the Shift Assignment.
Unscheduled Work Code	Shows a list of Nonworking type work codes. Select one for the Job Allocation Pass to apply if there is a non-working period of time not covered by the Shift Assignment.
Previous Allocations	Used to handle partially allocated scenarios when moving people across shifts. Options are: Ignore - the person will remain in any of their previously allocated jobs. Remove - the person will be removed from any job they were previously allocated

Bumping Options

IMPORTANT: To configure Bumping, the user must have in-depth knowledge of the applications Rules engine, meaning base rule type behaviors and components of a List Plan, in addition to Job Allocation Pass Rules, and Blueprints. It is very important to start the configuration with a small subset of people and tight limits when using the bumping feature for the first time. Jobs with multiple people allocated will not be considered in the bumping process.

Bumping is very complex and can very quickly result in a bumping loop. We recommend setting as many limits as possible, and don’t turn all of the bumping settings in the table below at once, but rather one or two at a time, check the results, and slowly increase the limits as needed. Moreover, because bumping is complex to troubleshoot start with a simple job allocation pass as well.

Field Name	Description
Bumping Pass Status	Enables Bumping.
Consider Unallocated Jobs	Runs Job Allocation Pass rules, and factors unallocated jobs for a person that is already allocated (the Holder). Select the check box to consider unallocated jobs in this pass.This setting affects ALL of the Holder filters that enable when Bumping is turned on. Consider Unallocated Jobs is available as of version 6.6.1. The default behavior does not consider unallocated jobs.
Only Bump if Qualified for Job	Runs Pass rules, and factors jobs for a person that is already allocated (the Holder); this person (the Holder) can only be bumped by the ‘target person in the List’ - if the Pass returns another job the Holder is qualified to work. When checked, the Qualified for Job Filter menu enables.
Qualified for Job Filter	Enables if Only Bump if Qualified for job is selected. Used to indicate which Pass (rules) to execute when returning jobs for the person. Options are: Use this Pass - Utilizes the rules (filters and sorts) in this Pass to identify jobs this person is qualified to work. Select another Pass - Utilizes the rules of another Pass to identify jobs for the person.
Last Bumped Person	Defines how to process the person who was bumped. Options are: Process in List- Places the bumped person on the list of candidates derived from the current List. The person would then be sorted according to the rules in the List. For example, if the sort is based on seniority the bumped person is placed on the list by order of seniority; this means somewhere on the list depending on the person’s seniority placement relative to others on the same List. Process Next- Select to process the bumped person immediately after they are bumped. Simply put, Process Next makes the last bumped person the #1 person on the List to be processed next regardless of how the list is sorted. When selected this option enables the Last Bumped Filter to define which List to use for the bumped person. Note: If the Pass contains a List the application attempts to place the person on this List, if the Pass does not contain a List, then the application will attempt to place the person on the List of the Job Strategy. The word attempt is used here because it is possible depending on the rules within the List that the person fails the job criteria of the selected List.
Last Bumped Person Filter	Enables when Process Next is used in Last Bumped Person. Indicates which Pass (rules) to execute when returning jobs for the person who bumped last. Options are: Use this Pass - Utilizes the rules (filters and sorts) in this Pass to identify jobs this person is qualified to work. Select another Pass - Utilizes the Rules of another Pass to identify jobs for the person.
Person Bump Limit	Indicates the maximum amount of times a person may be bumped within a Job Allocation Strategy. Once the person meets this number they can no longer be bumped. This means same shift, same blueprint position, and same Job Allocation Strategy. Note: Using a different Job Allocation Strategy the person could be bumped again. This setting ensures that the person is not bumped X many times using this Job Allocation Strategy.
*Bump Break Limit	REQUIRED: A threshold used to limit the number of bump attempts to be taken before the bumping process comes to an end. Designed to avoid complications with infinite bumping loops.
Prevent Recurring Bumps	Prevents a person from bumping a person that bumped them from the same job. This means, the same blueprint, same shift, same blueprint position. Two people can bump each other more than once from different blueprint positions. The following two scenarios are possible using Prevent Recurring Bumps: Example 1: John bumps James from Job 1, Shift A, Position 2A. This means James cannot bump John from Job 1, Shift A, Position 2A using Prevent Recurring Bumps Example 2: John bumps James from Job 1, Shift A, Position 2A. James gets allocated to Job 1, Shift A, Position 3A. Tom bumps John from Job 1, Shift A, Position 2A. John bumps James from Job 1, Shift A, Position 3A

Pass Definition

FILTER: Criteria used to filter blueprint positions.

Field Name	Description
Rank	The filter targets the candidate’s profile and the rank associated with the blueprint position. Active - The job title associated with the blueprint position must match the job title of the candidate’s active profile. Can Act As - The job title associated with the blueprint position must match the Can Act As job title of the candidate’s active profile. Equivalent - The job title associated with the blueprint position must match an equivalent job title in the candidate’s active profile. Any - The job title associated with the blueprint position must match one of these types (Active, Can Act As, Equivalent) in the candidate’s profile.
Organizational Level	The filter targets the organizational level of the blueprint position and the candidate’s active assignment. Limits include: Institution, Agency, Region, Station, Unit
Specialties	The filter targets the specialty associated with the blueprint position. All - The candidate’s active profile must match all of the specialties associated with the blueprint position. Any - The candidate’s active profile must match any of the blueprint position’s specialties. Exact - The candidate’s active profile must match the exact same set of specialties associated with the blueprint position. For example, if the blueprint position specialties are X,Y and the candidate has X,Y, Z - the person would be disqualified. None - Blueprint position has no specialties.
Groups	The filter targets the group associated with the blueprint position. All - The candidate’s active profile must match all of the groups associated with the blueprint position. Any - The candidate’s active profile must match any of the blueprint position’s groups. Exact - The candidate’s active profile must match the exact same set of groups associated with the blueprint position. For example, if the blueprint position groups are (X,Y), and the candidate has (X,Y, Z), the person would be disqualified. None - Blueprint position has no groups.
Position Allocation	The filter targets the blueprint position’s state. Unallocated - The blueprint position is entirely vacant. Fully allocated - The blueprint position has a resource or resources allocated for the entire duration. Partially allocated - The blueprint position has a resource or resources allocated for a segment or segments of the entire duration.
Position Times	The filter targets the blueprint’s position times; this means the entire From and Though range of the shift associated with the blueprint position. Exact - The blueprint’s position time must match the candidate’s scheduled time precisely. Within - The blueprint’s position time must be within the candidate’s scheduled times. Matches Start - The blueprint’s position start time must match the candidate’s scheduled start time. Matches End - The blueprint’s position end time must match the candidate’s scheduled end time.
Vacancy Times	The filter targets the unallocated segment or segments of a blueprint position; this means either the entire unallocated duration of the shift associated with the blueprint position, or the remaining segment of a partially allocated blueprint position. Exact - The blueprint’s position time must match the candidate’s scheduled time precisely. Within - The blueprint’s position time must be within the candidate’s scheduled times.
Vacancy Status	The filter targets the allocated and unallocated segments of a blueprint position. Unallocated - Returns blueprint positions with an unallocated segment or segments. Allocated - Returns the allocated segment or segments of a blueprint position.
Shift	The filter targets blueprint positions assigned the same shift as the shift associated with the target person’s staffing record. Options are: Matches Does not match The person's shift is either the shift applied on the person’s Assignment, or the shift applied by an exception record. If the person's regular shift assignment was moved, the filter returns the exception's new working location. A blueprint position’s shift is determined by the Shift applied on the parent Blueprint.
Shift Selection	Displays a list of shifts. A Shift filter set to ‘Matches’ returns blueprint positions that match any of the Shifts selected. The inverse outcome is true when ‘Does not match’ is selected in Shifts.
Shift Group	The filter targets blueprint positions with shifts that belong to the same shift group as the shift associated with the target person’s staffing record. Options are: Matches Does not match A person’s shift group is determined by the shift on the person’s Assignment, or the shift applied by an exception record. A blueprint position’s shift group is determined by the Shift applied on the parent Blueprint.
	For example: Shift Group 1 contains Shift A, Shift B, Shift X. Shift Group 2 contains Shift A, Shift C, Shift X The target person’s shift assignment contains Shift A Shift Group > Selections is Shift Group 1 Shift Group > Criteria is Matches This means return blueprint positions containing Shift A, Shift B, Shift X because the target person’s shift is associated with Shift Group 1, and Shift Group 1 is the limit. No selections in Shift Group Selections, returns all shift groups, which includes all of the blueprint positions containing a shift group association with Shift A which includes Shift Group 1, and Shift Group 2.
Shift Group Selections	Displays a list of shift groups as configured in Setup > Shifts> Shift Groups. When shift group is set to ‘Matches’ the filter returns blueprint positions associated with a shift that is included in the shift group selection. The inverse outcome is true when ‘Does not match’ is selected in Shift Group.
Duration	Returns blueprint positions that match the duration of the person's assigned Shift. The duration of the blueprint position refers to the unallocated portion of the blueprint position; any allocated portion of the blueprint position will not be considered. Options are: Matches, Greater Than, Less Than, Does not match
Duration Value	Returns blueprint positions with a duration that matches a specified value; for example 8 hours. The duration of the job refers to the unallocated portion of the job; any allocated portion of the job will not be considered. Options are: Minutes, Hours, Days
Allocated to Another Shift	Determines the next path for the application to take when a person is scheduled and allocated to a portion of a shift. Options are: Within same shift only - Returns blueprint positions that match the Shift the target person is already allocated, and returns blueprint positions for periods outside the already working time period. The purpose is to prevent people from getting allocated to two distinct shifts. If the person is not allocated, then this pass returns zero blueprint positions. Allow allocation to other shifts - This option returns blueprint positions outside the already allocated shift.
Preferences	The filter returns blueprint positions that match both the target person’s preference and the selected preference in the job allocation pass, and -satisfy the comparison operator’s value. Comparison operator: Equal Less Than or Equal Less Than Greater Than or Equal Greater Than
	For example, suppose that the planning board has 1 vacant Operator blueprint position in Unit 1. The target person has Preference X set, this person’s Preference X contains two preferences within and in this order: #1 - Operator in Unit 2 #2 - Operator in Unit 1 In Filters, Preference X is selected in the job allocation pass with a comparison value of = 1. Result: The Operator blueprint position in Unit 1 on the planning board is NOT returned because the comparison value is set to =1, meaning the target person’s first preference which points to Operator in Unit 2. To extend this example, if the comparison operator value was set to =2, or >1, or >=1, then the Operator blueprint position in Unit 1 on the planning board would be returned.
	Simply put, the application returns the highest matching preference, your number #1 choice then it evaluates your number one choice against the rule or job allocation criteria. If the rule or pass is set to >=2 and a job matches Preference 1,2, and 3, the application returns 1 your number 1 choice, which is not >=2 so it will fail the criteria.
	A single preference number will be returned from all rule or job allocation checks against preferences. The application will always return the highest matching preference number. If a vacancy matches preference 1,2, and 3. 1 will be returned for further processing, after the 1 is returned, the result is compared to the WHERE condition (or filter modifier for job allocation). So if the where is >=2, a 1 will fail. If the where is set >=1 a 1 will pass.
Job Title Selection	Returns jobs that match any of the selected job titles.
Job Level	Returns blueprint position’s that satisfy the person’s job title level located in Setup > General > Rank. Comparative values: >,<,<=,>=,=
Organization Selections	Returns jobs that match any of the selected organizational levels. If more than one organizational level is selected then any of the selected organizational levels will be returned.
Specialty Selections	Returns blueprint positions that match any of the selected specialties.
Group Selections	Returns blueprint positions that match any of the selected groups.
Person Assignment Locations	Targets the person’s Assignment record for the day, not a staffing record. Rather than returning where a person is actually working, this will only return the person's assignment on a particular day. Criteria: Matches or Does Not Match \| Target: Organizational Level
Person Profile Wage	Returns blueprint positions that match the person’s Wage (pay rate) located on the person’s Profile. For example, if the option is set to Equal to, then only the jobs with pay that are equal to the person’s profile pay are returned. Comparative values: >,<,<=,>=,=
Previous Job Allocation	Returns and sorts blueprint positions that match other positions or jobs that the target person has been allocated to. Generally, used to sort previously worked positions, at units, at stations and so on to the top of the list followed by and in addition to other jobs the person is qualified to work. Target options include: Target Day Last Day Worked Next Day Worked Same Day Previous Sunday Previous Saturday Previous Friday Previous Thursday Previous Wednesday Previous Tuesday Previous Monday Compare Property Institution Agency Region Station Unit Rank Job Group Job Specialties Criteria: Matches or Does Not Match

Additional Filters visible when Bumping is turned ON. Bumping pass filters are used to target jobs based on the current Holder’s attributes, the ‘Holder’ is the person who is allocated to the job. For these filters, the ‘Target Person’ means the person from the active List that is being considered in the Job Allocation.

Field Name	Description
Holder’s Special Date	The Holder’s Special Date relative to the Target person’s Special Date. Comparative values: >,<,<=,>=,=
Holder’s Promotion Date	The Holder’s Promotion Date relative to the Target person’s Promotion Date. Comparative values: >,<,<=,>=,=
Holder’s Opportunity Number	The Holder’s Opportunity Number relative to the Target person’s Opportunity Number. Comparative values: >,<,<=,>=,=
Holder User Defined Field	The Holder’s UDF value in relation to the Target person’s UDF value. Comparative values: >,<,<=,>=,=
Holder’s Assignment Location	Holder Assignment organizational or staffing record location. Options are Matches or Does Not Match the Organizational level selection.

Sort: Criteria for blueprint position sorting. Applied after filtering above is completed. Sorts are mutually exclusive; each Sort can be either ascending or descending. If any of the sorts result in a tie (and cannot be broken by another sort in the configuration of the pass, then the results will be random.

Field Name	Description
Blueprint Name	Sort by Blueprint Name. Options are: Ascending Descending
Blueprint Start Date-Time	Sort by Blueprint Start Date-Time. Options are: Ascending Descending
Rank Ordinal	Sort by the job title’s ordinal number in Setup > General > Rank. Rank Ordinal means the order number in which the selected rank is placed to set that rank’s hierarchy amongst other ranks.
Rank Level	Sort by the job title’s (rank) Level in Setup > General > Rank...
Rank Boolean	This sorting will take one or more job titles and sorts all of those job titles to the top (in an arbitrary order if more than one is included), all others will be after.
Unit Ordinal	Sort by the Unit’s ordinal number in Setup > Organizations
Unit Boolean	This sorting will take one or more units and will sort all of those units to the top (in an arbitrary order if more than one is included), all others will be after.
Station Ordinal	Sort by the Station’s ordinal number in Setup > Organizations
Station Boolean	This sorting will take one or more stations and will sort all of those stations to the top (in an arbitrary order if more than one is included), all others will be after.S
Specialty Count	Sort by the total number of specialties assigned to a blueprint position. Used to get the blueprint position with the most specialty requirements filled as quickly as possible.
Group Count	Sort by the total number of groups assigned to a blueprint position. Used to get the blueprint position with the most group requirements filled as quickly as possible.
Position Time Duration	Sort by the position's duration length.
Previous Job Allocations	Returns blueprint positions that match other positions, or jobs that the target person has been allocated to. Target options include: Target Day Last Day Worked Next Day Worked Same Day Previous Sunday Previous Saturday Previous Friday Previous Thursday Previous Wednesday Previous Tuesday Previous Monday Compare Property Organizational Levels Job Title Job Group Job Specialty Shift Shift Group
Vacancy Time Duration	Sort by a vacancy's duration length. A vacancy would be a vacant or filled segment of a blueprint position.
Shift	Sort by Shift. Used to target the Shift associated with the blueprint position, and the target person’s shift. Options are: Matches Does not match A blueprint position’s shift is determined by the Shift applied on the parent Blueprint. A person’s shift is determined by the shift on the person’s Assignment, or the shift applied by an exception record.
	For example, suppose that no Shift limits were applied in the Filters section of the job allocation pass. This means the blueprint positions being considered include blueprint positions across all shifts that ‘Match’, and ‘Does not match’ the target person's shift. If ‘Match’ is used in ascending order, then all of the blueprint positions that match the person’s shift sort to the top of the list. If the ‘Does not match’ is used in ascending order, then all of the blueprint positions that do not match the person's shift sort to the top of the list. Shifts could sort in random order when equal.
Shift Selection	Shows a list of shifts as configured in Setup > Shifts> Shift. When Shift is set to ‘Matches’ the filter returns blueprint positions that match any of the Shifts selected. The inverse outcome is true when ‘Does not match’ is selected in Shifts.
Shift Group	Sorts by Shift Group. Used to target the Shift Group associated with the blueprint position’s shift, and the shift group of the target person’s shift. Options are: Matches Does not match A person’s shift group is determined by the shift on the person’s Assignment, or the shift applied by an exception record. A blueprint position’s shift group is determined by the Shift applied on the parent Blueprint.
Shift Group Selections	Displays a list of shift groups as configured in Setup > Shifts> Shift Group. When Shift Group is set to ‘Matches’ the filter returns blueprint positions that contain a shift that match any of the Shift Groups selected. The inverse outcome is true when ‘Does not match’ is selected in Shift Groups.
Preference	Shows a list of preferences as configured in Setup > Preferences. The sort targets blueprint positions based on the person’s preference settings. Multiple preferences may be distinctly applied, and ordered as desired in a single job allocation pass.
	For example, in Filters, Preference X is selected in the job allocation pass with a comparison value of >= 1. In Sort, Preference X is selected in ascending order. The target person has Preference X set, this person’s Preference X contains two preferences within and in this order: #1 - Operator blueprint positions #2 - Machinist blueprint positions Result: All Operator and Machinist blueprint positions are returned because the comparison operator is >=1 which means return all preferences. Ten Operator blueprint positions and 5 machinist blueprint positions are found and sorted in this order: Ten Operator blueprint positions show at the top of the list (Preference #1), followed by 5 Machinist blueprint positions (Preference #2).
	Another example, suppose that Preference X targets the Units of the organizational structure. The job allocation pass contains the following: Filter targets the organizational level of Unit. This means blueprint positions associated with the target Unit relative to the person’s assigned Unit. No Preferences are set in Filters. In Sort, Preference X is selected in ascending order. Result: All blueprint positions matching the person's unit are returned, and blueprint positions that do not match any of the person's preferences are sorted to the bottom. The blueprint positions that match the person's preferences are sorted to the top - using the order defined on that person's preferences.
Job Title	Sorts blueprint positions that match the person’s Job Title located on the active profile AND in addition to these options: Active Can Act As Equivalent Any
Job Allocation	Sorts blueprint positions based on their allocation status. Options are: Not Allocated: If true returns jobs that are not allocated. Partially: If true returns jobs that are partially allocated. Fully Allocated: If true returns jobs that are fully allocated.
Job Name	Sorts by the blueprint’s Job Override Name field, if a job override name does not exist then the application sorts by the Job name on the blueprint. Options are: Ascending Descending
Job Pay	Sorts blueprint positions based on the Wage or Pay on the blueprint.
Job Span (Before, During, After)	Sorts in job run order of Before, During, and After.
Job Start Date-Time	Sorts by job start date-time and irrespective of the job span before, during, and after.
Person Assignment Location	Sorts by the location of the person’s assignment for the day; not necessarily the shift assignment although it could be the end result if the person is on their shift assignment that day.
Specialty	Sorts blueprint positions with specialties that match the person’s specialty located on their active profile AND in addition to these options: Any All None Exact
Specialty Selection	Sorts jobs based on the selected specialties.
Group	Sorts blueprint positions with Groups that match the person’s Groups located on their active profile AND in addition to these options: Any All None Exact
Group Selection	Sorts jobs based on the selected groups.

Additional Sorts visible when Bumping is turned ON. Bumping pass sorts are used to sort jobs based on the current Holder’s attributes, the ‘Holder’ is the person who is allocated to the job. The Match sorts jobs based on the Holder’s attributes.

Field Name	Description
Holder’s Special Date	The Holder’s Special Date.
Holder’s Promotion Date	The Holder’s Promotion Date.
Holder’s Opportunity Number	The Holder’s Opportunity Number.
Holder User Defined Field	The Holder’s UDF value.
Holder’s Assignment Location	Holder Assignment organizational or staffing record location.