Configure a schedule generation strategy

• In the Engine Will drop-down, select one of the following contexts:
  • Generate Open Shifts Only — Does not assign any shifts to employees, but it can assign breaks if break rules are configured and Ignore Break Placement Rules is not selected.
  • Assign Open Shifts Only — Assigns all available, open shifts to employees, but does not create shifts
  • Generate and Assign Shifts — Generates open shifts and employee shifts. Assigns any previously existing open shifts to employees
  • Optimize Shift Contents — Optimizes job assignments within shifts, but does not change employees, shift start or end times, or durations.
  • Generate Employee Shifts Only — Employee shifts are generated as shifts that are assigned to employees, but does not create open shifts.
  • If business needs change, this context quickly assigns scheduled employees to transfer jobs without changing the scheduled shifts in any other way. You can change job assignments for whole shifts or parts of shifts. Example: Normally, a team of manufacturing employees works on Line 1. However to complete a new order, these employees need to work on Line 2 for half a day. Load the new workload. Select Optimize Shift Contents. Regenerate the schedule. Then re-post the schedule.
• In the Workload drop-down, select one of the following:
  • Baseline — For locations that use schedule zone sets and shift sets, the baseline number of hours comes from the workload plan.
  • If Forecast Manager is installed and the locations use forecast labor, the baseline number of hours comes from the forecast workload.
  • Plan — For locations that use zone sets and shift sets, the planned workload is the adjusted number of hours from the workload plan. If the planned workload is not defined, schedule generation uses Baseline.
  • If Forecasting is configured and the locations use forecast labor, the planned workload is the labor forecast.
  • Budget — If Forecasting is configured and labor constraints have been applied to the labor forecast, select Budget to use the system-adjusted labor forecast.
• In the Shift Template Profile To Use drop-down, select one of the following:
  • Current User's Shift Template Profile (Default) — Limit the number of shift templates to only the shift templates for the current user of schedule generation.
  • If the user does not have a default shift template profile in their data access profile, schedule generation does not generate shifts. You see a message only when you run schedule generation, not from the setup workspace. Select one shift template profile.
  • All Shift Templates — Use all available shift templates in the data access profile.
  Uwaga: This option can require more processing time for large numbers of shift templates.
  • Ignore and Use Shift Profile Sets — Use shift profile sets rather than shift template profiles. The available shift template profiles are defined by the data access profile.
• In the Shift Profile Sets for Open Shifts area, select the shift profile sets from the Available box and click the right arrow. Alternatively, click the double right arrow to select all items. To remove shift profile sets, select the items from Selected and click the left arrow.
• Schedule generation can use shift profile sets that define start times, end times, and shift durations when it generates open shifts. The number in parentheses is the Relative Part that represents a soft minimum on the proportion of open shifts that satisfies the corresponding shift profile set. A higher number indicates that the shift profile set gets proportionally more open shifts than a shift profile set with a lower number. Schedule generation balances soft rules and relative part values. If the schedule generation strategy does not overwrite the current schedule, existing open shifts remain and count towards the relative part.
• Select Shift Segment Tags that the engine can build around when it generates shifts. Example: Shift segments that are tagged for Training. From Available, select the shift segment tags and click the right arrow.

Select or clear the following check boxes as necessary:

• Overwrite Current Schedule — Select to remove unlocked or open shifts in the current schedule before schedule generation generates a new schedule. Schedule generation never affects locked shifts, shifts during locked days, or pay codes; it can override only the shifts that it can regenerate
• Allow Break in Segment Tags — Select to allow breaks in shifts that are built around segment tags. Example: Allow a break during a long meeting.
• Ignore Break Placement Rules — Select to not assign breaks within the generated shifts.
• Treat Manually Created Shifts as Locked — Select to prevent changes to existing assigned shifts that were created manually. Clear to allow schedule generation to remove unlocked shifts even if they are assigned to employees.
• This setting has no effect if Overwrite Current Schedule is not selected.
• Regardless of this setting, schedule generation can assign any open shifts no matter how these were created.
• Allow Multi-Job Shifts — Select to allow shifts to contain multiple segments for different jobs. You should define the shortest length of shift segments in Minimum Job Segment Length.
• This setting has no effect if Assign Shifts to Primary Job Only is selected.
• Allow Shifts when Availability is Undefined — Select to generate or assign shifts that overlap unknown availability periods.
• This setting has no effect if the relevant availability employee rule is not active, or if the severity of the rule is Not Considered.
• Overwrite Open Shift Breaks — Select to modify breaks according to the employee's break rules when schedule generation assigns existing open shifts.
• Allow Overlap with Unavailability — Select to generate or assign shifts that overlap periods when an employee is not available.
• This setting has no effect if the relevant availability employee rule is not active, or if the severity of the rule is Not Considered.
• Assign Shifts to Primary Job Only — Select to generate shifts only for the primary job of employees. Selecting this check box disables the Allow Multi-Job Shifts setting.

Provide values as necessary in the following fields:

• Minimize Overcoverage — Enter a value as follows:
• High value = Minimizing over-coverage is more important.
• Low value = Minimizing over-coverage is less important.
• To ignore over-coverage, enter 0.
• Minimize Undercoverage — Enter a value as follows:
Uwaga: If the site.scheduling.schedGen.business.protocol.AllowWorkloadUnderCoverage system setting is false, this setting has no effect.
• High value = Minimizing under-coverage is more important.
• Low value = Minimizing under-coverage is less important.
• To ignore under-coverage, enter 0.
• Minimize Open Shift Creation — Enter a value to minimize coverage by open shifts as follows:
Uwaga: For the Generate Open Shifts Only context, this setting is redundant with Minimize Overcoverage. This setting is also redundant with the site.scheduling.schedGen.business.protocol.SprayOverCoverage system setting.
• Any value higher than 0 (zero) penalizes generation of open shifts.
• High value = Minimizing coverage by open shifts is more important.
• Low value = Minimizing coverage by open shifts is less important.
• To not penalize coverage by open shifts, enter 0.
• Match Shift Profile Set Distribution — Only if shift profiles are configured for open shifts, define how closely the profiles of open shifts match the relative parts that are defined in shift profile sets in this field.
• Relative parts define a minimum percentage of generated, open shifts that conform to a shift profile set. This is a soft constraint; schedule generation can try to generate more open shifts for this shift profile set, but not fewer.
• High value = Closely matching the relative parts is more important.
• Low value = Closely matching the relative parts is less important.
• To not penalize relative parts matching, enter 0.
• Minimize Zero Coverage — Define the penalty for gaps in coverage when workload is required but no employee is scheduled.
• Example: Set this penalty to avoid scheduling all employees to take breaks at the same time.
• High value = Minimizing gaps in coverage is more important.
• Low value = Minimizing gaps in coverage is less important.
• To ignore gaps in coverage, enter 0.
• Skill and Certification Undercoverage Weight — Enter a relative value to minimize under-coverage of the skill and certification workload as follows:
• High value = Minimizing under-coverage is more important.
• Low value = Minimizing under-coverage is less important.
• Range = Integers from 0—1,000,000,000, but use a reasonable value.
• To ignore under-coverage, enter 0.
• Minimum Job Segment Length (hh:mm)
Uwaga: Segment Length (hh:mm) to set the minimum length of a shift segment for a job. This setting ignores segments, such as breaks, that are not associated with jobs.
• Default = 0:00.
• This setting has no effect if Allow Multi-Job Shifts is not selected.
• Satisfy Minimum Hours — Set a penalty for scheduling fewer than the minimum number of hours each period of time for any employee. This applies to both minimum hours per week rules and minimum period hours rules.
• High value = Scheduling fewer than the minimum hours is more penalized.
• Low value = Scheduling fewer than the minimum hours is less penalized.
• To ignore the minimum number of hours each week, enter 0.
• Satisfy Minimum Days per Week — Set a penalty for scheduling fewer than the minimum number of days each week for any employee.
• High value = Scheduling fewer than the minimum days is more penalized.
• Low value = Scheduling fewer than the minimum days is less penalized.
• To ignore the minimum number of days each week, enter 0.
• Satisfy Minimum Weekend Off — Set a penalty for scheduling fewer than the minimum number of weekends off for any employee.
• High value = Scheduling fewer than the minimum weekends off is more penalized.
• Low value = Scheduling fewer than the minimum weekends off is less penalized.
• To ignore the minimum number of weekends off, enter 0.
• Overall Employee Preferences Weight — Enter a value to set the penalty for not accounting for employee preferences in a schedule.
• High value = The employee preferences are more important.
• Low value = The employee preferences are less important.
• To ignore employee preferences, enter 0.

Enter the relative importance of each type of employee preference:

Uwaga: If the sum of percentages exceeds 100%, schedule generation normalizes the sum to 100%. Example: If the percentage of Preferred Availability, Job, Hours per Week, Day Off, and Most Hours per Week is each 80%, schedule generation interprets the value of each to be 20%.
• Preferred Availability (%) — Enter a percentage to set the relative importance of scheduling employees during their preferred availability.
• High value = The preference is more important.
• Low value = The preference is less important.
• To ignore preferred availability, enter 0.
• Employee Preferred Job (%) — Enter a percentage to set the relative importance of scheduling employees to their preferred job.
• High value = The preference is more important.
• Low value = The preference is less important.
• To ignore preferred jobs, enter 0.
• Preferred Hours per Week (%) — Enter a percentage to set the relative importance of scheduling employees to their preferred number of hours each week.
• High value = The preference is more important.
• Low value = The preference is less important.
• To ignore preferred hours each week, enter 0.
• Preferred Day Off (%) — Enter a percentage to set the relative importance of not scheduling employees during their preferred days off.
• High value = The preference is more important.
• Low value = The preference is less important.
• To ignore preferred days off, enter 0.
• Most Hours per Week (%) — Enter a percentage to set the relative importance of scheduling employees to their preferred maximum number of hours each week.
• High value = The preference is more important.
• Low value = The preference is less important.
• To ignore the most hours each week, enter 0.
• Earliest Shift (%) — Enter a percentage to set the relative importance of scheduling employees to work the earliest shifts in the day.
• High value = The preference is more important.
• Low value = The preference is less important.
• To ignore a preference for the earliest shifts, enter 0.
• Longest Shift (%) — Enter a percentage to set the relative importance of scheduling employees to work the longest shifts that are available.
• High value = The preference is more important.
• Low value = The preference is less important.
• To ignore a preference for the longest shifts, enter 0.
• Low Job Priority/High Job Priority — To set the relative importance of covering specific jobs, select job groups for each field.

  Uwaga: If the number of organizational sets is too large to display in the drop-down list, the system displays an informational message instructing you to search for more results.

• Group Employee Days Off Together — Enter a value to minimize the number of non-consecutive days off that are scheduled for any employee.
• High value = Scheduling days off consecutively is more important.
• Low value = Scheduling days off consecutively is less important.
• To not prioritize consecutive days off, enter 0.
• Minimize the Number of Generated Shifts — Enter a value to minimize the number of generated shifts as follows:
• High value = Scheduling fewer shifts is more important.
• Low value = Scheduling fewer shifts is less important.
• To not penalize scheduling more and shorter shifts, enter 0.
• Priority-based hours balancing (%) — Enter a value to control how hours are distributed amongst employees relative to their seniority as follows:
• High value = Distributing hours to the more senior employees is less important; encourages fairness between senior and junior employees
• Low value = Distributing hours to the more senior employees is more important; favors senior employees by to the detriment of junior employees

When this setting has a value of 100%, employees should receive — as much as possible — the same number of hours worked during the week. Several factors may impact this objective:

• under- and over-coverage of demand, which is typically the dominant goal
• minimum and maximum number of hours worked per week, defined per employee
• shift-length restrictions
• other factors, such as the employee availability

For more information, see Configure Hours Distribution for Employee Priority Groups.

• Employee Priority Group — Select the employee priority groups in the priority order that you want from top (most important) to bottom (least important).

Employee priority groups are configured in Schedule Groups and for each person in the People Editor.

An employee priority group is a set of employees that are ranked based on certain attributes typically reflecting their seniority. The Schedule Generation engine assigns each employee to only one employee priority group. Based on the ordered list of employee priority groups selected in the strategy and the schedule group assignment for each employee, the first schedule group assigned to the employee that is applicable during the optimization horizon is the priority group assigned to the employee.

For more information, see Configure Hours Distribution for Employee Priority Groups.

• Grouped Arrival Weight — The grouped arrival setting attempts to group employees by their arrival times. The grouping is a soft constraint and can be applied in combination with other scheduling schemes. Enter a value to minimize the number of different start times for employees who are in the same schedule group or team. Example: When employees who work similar jobs arrive together, managers can provide shift information more efficiently.
Uwaga: To show different group starting times, use a Dataview instead of the Scheduler.
• High value = Scheduling groups together is more important.
• Low value = Scheduling groups together is less important.
• To ignore arrival times, enter 0.
• Stable Schedule Penalty — Consistency in shift start times is between one day off and the next weekly day off. Schedule stability applies to all shifts that are scheduled between these two weekly rest or off days, and does not carry over from one week to the next. Consistency resets after off periods.
• Set the importance of consistent shift start times:
• High value = Schedule stability is more important.
• Low value = Schedule stability is less important.
• To ignore the consistency of shift start times and durations, enter 0.

Schedule generation can schedule groups of employees by priority and, within those groups, equalize assignments by employee preferences, weekly scheduled hours, or both. Without equalization, prioritizing by worker type acts similarly to ranking by custom field.

Provide the following information:

• Custom Field for Employee Priority — Select a custom field to set the priority of employees. This custom field comes from People Information > Person tab > Additional Information. Use this priority to improve employee satisfaction.
• Example: Select Seniority.
• High value = Setting the priority of employees by this custom field is more important.
• Low value = Setting the priority of employees by this custom field is less important.
• Default = blank.
• To treat all employees with the same priority, enter 0.
• In the Worker Type Priority area, select the worker types in the priority order that you need from top (most important) to bottom (least important). The order sets the priority of satisfying employee preferences, worked hours, or both. Click the right arrow.
• Worker types are defined in Common Setup and for each person in the People Editor. Examples: Full Time, Part Time, Per Diem
• Worker Type Equalization smooths the differences between employee hours or preferences. Select one of the following:
  • Equalize Hours: Schedule employees from the same worker-type group the same number of worked hours each week. This setting overrides the Custom Field for Employee Priority for the selected groups.
  • Equalize Preferences: Schedule employees from the same worker-type group the same level of employee preferences each week. This setting overrides the Custom Field for Employee Priority for the selected groups.
  • Equalize Hours & Preferences: Schedule employees from the same worker-type group for the same number of worked hours and the same level of employee preferences each week. This setting overrides the Custom Field for Employee Priority for the selected groups.
  • None = Ignore equalization but prioritize first by Worker Type Priority, then by Custom Field for Employee Priority as a tie-breaker if needed and defined for the employees.
• Work Type Hour Equalization Weight sets the importance of the Worker Type Equalization setting in relation to workload coverage and employee preferences. Enter a value:
  •  High value = Equalization of employee hours or preferences is more important.
  •  Low value = Equalization of employee hours or preferences is less important.
  •  To ignore equalization, enter 0.

Configure schedule generation to use cost or hours budgets to limit the number of generated shifts.

• For cost, the budget is calculated from shift lengths multiplied by wages.
• For hours, the budget is calculated from shift lengths.

For schedule generation, the budget applies to all contexts. Otherwise, the budget applies only to the Generate Open Shifts context. Also, employee wages and currency must be configured, and open-shift wages and currency must be configured in Location Settings

1. In the Budget Type field, select one of the following:
   • Budget Cost From Strategy — Also define the Budget Limit Per Week, Budget Tolerance Percentage, Weekly Budget Weight, and Budget Currency.
   • Budget Hours From Strategy — Also define the Budget Limit Per Week, Budget Tolerance Percentage, and Weekly Budget Weight.
   • Imported Budget Cost — The imported budget cost value from Forecasting. Also define the Budget Tolerance Percentage and Weekly Budget Weight.
   • Imported Budget Hours — The imported budget hours value from Forecasting. Also define the Budget Tolerance Percentage and Weekly Budget Weight.

   For budget types Imported Budget Cost or Imported Budget Hours, the budget limit comes from Forecasting.

   • Possible values: integers greater than or equal to —100%
   • Negative values penalize schedules that go below the budget.
   • Positive values penalize schedules that exceed the budget.
   • None — Ignore budget limits.
2. If you selected Budget Cost From Strategy or Budget Hours From Strategy budget types, define a limit to the budget amount in the Budget Limit Per Week field. Enter a positive value for cost or number of hours.
3. The budget limit is a lower or upper limit or both depending on the Budget Tolerance Percentage.
   • High value = A soft constraint, penalize generation of shifts that exceed weekly budgets less strictly.
   • Low value = A hard constraint, penalize generation of shifts that exceed weekly budgets more strictly.
   • To generate no shifts, enter 0. Regardless, schedule generation can assign shifts.
2. In the Budget Tolerance Percentage field, enter a value to define how much the schedule cost can go above or below the budget.
3. If the budget type is Budget Cost From Strategy or Budget Hours From Strategy, the budget limit is defined by the Budget Limit Per Week setting.
3. If the budget type is Imported Budget Cost or Imported Budget Hours, the budget limit comes from Forecasting.
   • Possible values: integers greater than or equal to —100%
   • Negative values penalize schedules that go below the budget.
   • Positive values penalize schedules that exceed the budget.
   • High value = A soft constraint, penalize generation of shifts that exceed weekly budgets less strictly.
   • Low value = A hard constraint, penalize generation of shifts that exceed weekly budgets more strictly.
   • To ignore variations from the budget, enter 0.
4. Enter a Weekly Budget Weight to define the penalty for schedule costs that exceed the weekly Budget Tolerance Percentage setting.
5. Important: For this setting to have effect, the Budget Tolerance Percentage setting cannot be 0.
6. Use this penalty to resolve any tradeoff between exceeding a budget limit and other objectives such as minimization of under-coverage or maximization of employee preferences.
   • High value = Generation of shifts that exceed weekly budgets is penalized more.
   • Low value = Generation of shifts that exceed weekly budgets is penalized less.
   • To ignore shifts that exceed weekly budgets, enter 0.
5. If you selected the Budget Cost From Strategy budget type, you can select a currency in the Budget Limit per Week Currency field.
6. Select the currency of the employee or open shift wage costs. To use the default currency settings from the system configuration, select None.
Uwaga: The open shift wages for a job are defined in the location settings that are assigned to the business structure. If you select a different currency from the default, make sure that the currency is also defined in the location settings; otherwise only the default currency is used.

To prevent scheduling employees to be transferred to different physical locations on the same day, (for example, to not have an employee spending time traveling between locations), you can configure schedule generation to define the location type inside which an employee can be scheduled during their work day and cannot be transferred to another location of the same or higher level location type on the same day.

The Single-Location Type setting is used to identify under which Type of physical location (as defined in the Business Structure) employees can be transferred during the same shift on the same day, taking into account their Job assignments and qualifications defined within People Information.

When a Single-Location Type is specified, an employee cannot be transferred on the same day to different locations of the specified type. However, they can be transferred on the same day to other jobs within the same physical location, and they can be transferred to a different physical location on a different day.

In Single-Location Type, do one of the following:

• Select the Location Type at which level transfers are allowed.
• Select None to have no restriction on employee transfers taken into account.

• site.scheduling.schedGen.settings.employeeHolidayCredit
• Enter the number of hours to account for holidays.
• Default = 0

• site.scheduling.schedGen.business.protocol.AllowWorkloadUnderCoverage
  • True = Allow under-coverage.
  • False (default) = Prevent under-coverage.
• site.scheduling.schedGen.business.protocol.SprayOverCoverage
• This setting is redundant with the Open Shifts Distribution Penalty.
  • True = Distribute shifts to avoid peaks of under- or over-coverage in the schedule.
  • False (default) = Do not distribute shifts to avoid peaks of under- or over-coverage.
• site.scheduling.schedGen.business.protocol.AllowWorkloadAtZeroToBeCovered
• Example: A workload of zero corresponds to periods when a location is closed.
  • True (default) = Allow coverage during any time period that has a workload of zero.
  • False = Prevent coverage during time periods when the workload is zero, and the time period is greater than or equal to the minimum time period that is defined in ThresholdSpanForWorkloadAtZeroAnalysis.
• site.scheduling.schedGen.business.protocol.ThresholdSpanForWorkloadAtZeroAnalysis
• Sets the maximum time period when workload is zero that cannot be covered. Enter a value in minutes.
  • High value = More shifts can be created during periods when workload is zero.
  • Low value = Few or no shifts are created during periods when workload is zero. Example: Allow coverage only of gaps that are 30 minutes or shorter.
  • Default = 1440 minutes (24 hours)
• This setting has no effect if AllowWorkloadAtZeroToBeCovered is true.
• site.scheduling.schedGen.business.modules.shiftenumerator.Resolution
• Sets the resolution of when shifts start and end. Possible values:
• 1 (default) minute = Shifts can start and end on any minute.
• 5 minutes = Shifts start and end only at 5-minute intervals.
• 10 minutes = Shifts start and end at 10-minute intervals.
• 15 minutes = Shifts start and end on the quarter hour.
• 30 minutes = Shifts start and end on the half hour.
• 60 minutes = Shifts start and end on the hour.

• site.scheduling.schedGen.CalculateOpenShifts.threshold
  • Enter a percentage of coverage that a non-standard shift can provide to a workload that is based on shift sets.
  • Default = 15%
• site.scheduling.schedGen.CalculateOpenShifts.UseNonStandShifts
  • True = Allow schedule generation to use non-standard shifts when it calculates open shifts.
  • False (default) = Use only standard shifts.
• site.scheduling.schedGen.CalculateOpenShifts.UseShiftTemplates
  • True = Allow schedule generation to use shift templates when it calculates open shifts.
  • False (default) = Do not use shift templates.

Przestroga :Only qualified personnel who are trained to configure schedule generation and who understand schedule optimization should be allowed to modify these advanced system settings.

The default values of these advanced system settings are the most appropriate in almost all situations. However if schedule generation cannot find appropriate solutions, you can adjust these settings to change the balance of schedule quality against system performance. Then, test the results. If needed, change the settings and test again.

Because schedule problems can involve many constraints and variables, schedule generation balances processing time against the quality of the solution. It breaks the schedule problem into smaller problems, generates sub-schedules, and combines results to generate an entire schedule. The main tradeoffs occur between performance and quality:

• If you shorten processing time, you reduce solution quality.
• If you improve solution quality, you increase processing time.

• site.scheduling.schedGen.LpSolver.RelOptimalityGapPerMil
• The relative optimality gap measures the quality of the solution that corresponds to a sub-schedule. This setting defines the maximum quality gap to accept a solution relative to the best schedule solution. The gap is measured in per mil (a tenth of a percent or one part per thousand).
• Enter the optimality gap.
• Must be greater than or equal to 0
• High value = Reduce the solution quality and shorten the processing time.
• Low value = Improve the solution quality but lengthen the processing time.
• Default = 30

• site.scheduling.schedGen.CtrWorkloadDivider.MaxSize
• Enter the maximum number of jobs to process in each iteration of the calculation process.
• Default = 1

• site.scheduling.schedGen.LpSolver.GapDurationPerMilisec
• Enter the time limit to process sub-problems.
• Default = 6,000,000 ms (1 minute)

• site.scheduling.schedGen.business.solver.schedulegeneration.MaximumReoptimizationLimit
• Enter the maximum number of macro-iterations as the engine decomposes the calculations.
• Default = 1,000,000

• site.scheduling.schedGen.business.solver.schedulegeneration.SolveAsynchronously
• True = Allow schedule generation to process asynchronously.
• False (default) = Schedule generation processes only synchronously.

• site.scheduling.schedGen.EmployeeDivider.MaxSize
• Enter the maximum number of employees to process for each sub-schedule.
• Must be greater than or equal to 1
• Default = 30
• Increase the value only to process many employees who have the same qualifications.

• site.scheduling.schedGen.solver.ClusteringStrategy

Specifies the clustering strategy to regroup employees and jobs. A clustering strategy is a way to regroup employees and jobs for the engine to generate the schedule efficiently.

• Compact (default) = Employees and jobs are divided into subgroups considering their rules and qualifications.
• Global = All the employees and jobs are considered together as a whole group.

Uwaga: The Global strategy can significantly impact the performance of the engine.

The following settings control how schedule generation prioritizes employee assignments. Example: These settings control how employees are sorted by seniority.

• site.scheduling.schedGen.EmployeeDivider.MaxLevelSize
  • Enter the maximum number of priority levels.
  • Default = 2
• site.scheduling.schedGen.rules.controlledaccount.ExponentialFactor
  • True (default) = Temporarily create virtual employees for the calculations.
  • False = Do not use virtual employees.
• site.scheduling.schedGen.rules.emphasizeMinHours
  • None (default) = Setting is not enabled.
  • Weekly Hours = Emphasize the minimum hours per week rules.
  • Period Hours = Emphasize the minimum period hours rules.
  • All = Emphasize minimum hours per week and minimum period hours rules.
• site.scheduling.schedGen.business.ShowAllLocationStrategies
  • True = In the Schedule Planner, all Schedule Generation Engine strategies that are assigned to at least one of the selected locations or jobs are available to use. Only the jobs that are assigned to the strategy are considered when the Schedule Engine is run.
    • The Skills & Certifications requirement is only considered if all assigned locations and jobs are selected within the Schedule Planner, even if not all of them are assigned to the selected Schedule Generation strategy.

    • Existing shifts within the Schedule Planner are always considered regarding workload and Skills & Certifications coverage.

    • When the system setting site.scheduling.schedGen.engine.ExcludeExternalEmployees is set to False, all qualified employees shown in the Schedule Planner will be considered during the schedule generation.
    • When the site.scheduling.schedGen.engine.ExcludeExternalEmployees is set to True, only employees having their primary job assigned to the selected Schedule Generation Strategy will be considered during the schedule generation.
  • False (default) = In the Schedule Planner, only Schedule Generation Engine strategies that are assigned to the entire selected locations and jobs are available to use.
    • The Skills & Certifications requirement is only considered if all assigned locations and jobs are selected within the Schedule Planner.

  Uwaga: This setting has no impact on the batch processing behavior.

• site.scheduling.schedGen.rules.controlledaccount.PriorityLevelFactor
• Enter the level of discrimination between two consecutive priority levels.
• Default = 1
• site.scheduling.schedGen.EmployeeDivider.ExponentialBasis - Enter the discrimination ratio in percent between two consecutive levels (1-99)
  Default = 95
• site.scheduling.schedGen.EmployeeDivider.UseVirtualEmployees
  • True (default) = Temporarily create virtual employees for the calculations.
  • False = Do not use virtual employees.
• site.scheduling.schedGen.solver.EmployeePreferenceHandlingStrategy

  Determines how schedules of prioritized employees are compared with respect to the configured preferences. Employee priorities are configured using one or both of the Custom Field for Employee Priority and Worker Type Priority options. Preferences are configured using the percentages from the schedule generation engine strategy or employee setup.

  • Combined Preferences (default) = When this option is selected, the existing schedule generation strategy for handling employee preferences is used, as follows:

  The combined satisfaction of all the configured preferences of a given employee should not be lower than those of less senior employees. The preference percentages are used as multiplication factors when combining preference satisfactions. As a result, it is possible that schedules with high satisfaction regarding a given preference and poor satisfaction regarding other preferences may be generated, inducing satisfaction imbalances across preference types.

  • Individual Preferences = When this option is selected, the individual satisfaction over any configured preference of a given employee should not be lower than those of less senior employees. The preference percentages are used as ranking criteria between preference types when there is inversion tradeoff to handle.
  • When possible:
  • The satisfactions are balanced to avoid any inversion.
  • The most senior employees receive the longest shift, the earliest shift, or the most hours per week than less senior employees. The most hours preference remains implicitly an important criterion.

  Satisfaction refers to how the overall quality of an employee's schedule is measured based on configured preferences. Inversions occur when a less senior employee is given a shift that would have been attributed to a more senior employee.

  Schedule generation evaluates seniority order between employees who have the same primary job and are scheduled to work the same job. Some employees may still be scheduled out of seniority order due to coverage needed, employee availability, and schedule rules. In that case, the preferences with the higher percentage are the last to be inverted.

The horizon is the time interval of the entire schedule. schedule generation decomposes the horizon into sub-horizons that each represent the time interval of a sub-schedule. Control the horizon-decomposition scheme with the following system settings:

• site.scheduling.schedGen.HorizonDivider.Reference
  • Select the first day of the week.
  • This value must match the definition of the week that is used by the organization.
  • In North America, the typical value is Sunday.
  • In Europe, the typical value is Monday.
• site.scheduling.schedGen.HorizonDivider.Step
  • Enter the number of days to separate the start of two consecutive sub-horizons.
  • Must be greater than or equal to 1, and never greater than the value of HorizonDivider.Length
  • Default = 7 days
• site.scheduling.schedGen.HorizonDivider.Length
  • Enter the maximum length of each sub-horizon, in days.
  • Must be greater than or equal to 1
  • Default = 7 days
  • Lengthen the sub-horizon to improve the solution quality, but you reduce the system performance.
• site.scheduling.schedGen.engine.ExcludeExternalEmployees

Controls the scheduling of eligible external employees

• True = The engine schedules only employees whose primary jobs are in the optimization scope, meaning the jobs that are selected in the Schedule Planner or those jobs specified in the parameter string of the batch task, if the engine is run via batch.
• False = The engine considers:
• Employees whose primary jobs are within the optimization scope, and
• Employees whose primary jobs are outside the optimization scope (external employees), but have been scheduled to work at least one of the jobs in the scope during the loaded period, 2 weeks before the loaded period, or 2 weeks after the loaded period.

Example: If the schedule is loading the current schedule period for a location selection that includes Job X, an employee whose primary job is different from Job X but was transferred to Job X in the previous schedule period will be considered by the schedule generation engine strategy.

Uwaga: When this setting is False, the behavior is in line with the default behavior of the Schedule Planner when the View transfer set employees setting is not selected in the Schedule Planner configuration.

This behavior limits clashes when the Schedule Generation engine is run in parallel for multiple locations, either manually or via batch.

• site.scheduling.schedGen.shiftenumerator.EnumeratedShiftLimit
• Limit the number of shifts that schedule generation analyzes for each day. The shifts are based on shift profile sets.
• Enter a value of 5 or more.
• High value = A high quality of coverage but long processing time.
• Low value = A low quality of coverage but fast processing time.
• The default value of 5000 effectively turns off this limit.
• site.scheduling.schedGen.business.protocol.ExcludePayCodesFromBudgetBalance
• True = Exclude pay codes from the initial budget balance. This setting also enables the Budget Adjusted indicator to compare produced results with expected results more accurately.
• False (default) = Include pay codes from the initial budget balance.

• site.scheduling.schedGen.business.protocol.StabilityTolerance
•  Enter a threshold value, in minutes, that defines the maximum, acceptable deviation between shift start times.
  • High value = Accept a wider variation in start times.
  • Low value = Reduce the variation in start times.
  • Default = 30 minutes.
• site.scheduling.schedGen.business.protocol.StabilityRelativeWeight
•  Set the relative weight (%) of unstable shift start times and durations.
  • High value = Schedule stability is more important.
  • Low value = Schedule stability is less important.
  • Default = 50%
• site.scheduling.schedGen.business.protocol.SprayDeviation
•  Select whether to minimize variations in shift start times.
  • True = Distribute shift start times to avoid differences between days.
  • False (default) = Do not distribute shift start times to avoid differences between days.

    Example: If this setting is false, shifts on Monday to Thursday start at the same time (have zero variation), but the shift on Friday starts 5 hours later. If this setting is true, the variation is only 1 hour each day.