Configuring the System Calendar

On This Page:

Total system date range
Auto Scheduling date range
Operative day boundaries

Related Pages:

FRU Process

The following entries in Database sp083_system_parameters need to be configured in consultation with the business. They all relate to the FRU Process.

Total system date range

The FRU process needs to build up a calendar in memory that gives the available working time for each employee for booking jobs. This calendar cannot be endless, therefore it is necessary for the business to decide on the date range over which the system is to run. This date range will then be the complete range of dates that the business can book into, and the complete range of dates that can be seen on the ServiceGANTT client.

Parameter	Description	Considerations
`glob_days_before`	Number of days before today at which the Memory Horizon is to start.	this is the visible history for data. The business needs to consider what is the purpose of this data - what business processes require it? If the value here is large then it might affect the performance of the system. In general it is assumed that ServiceOptimizer is NOT the system of record for data, and hence any mining of historic data should be done from elsewhere.
`glob_days_after`	Number of days after today at which the Memory Horizon is to end.	this is the visible forwards horizon for data. No jobs may be booked further out into the future, so the business needs to be sure that their processes do not require later dates. Again, performance is a driving factor here - the larger the value, the more impact on performance.

Auto Scheduling date range

Parameter	Description	Considerations
`glob_sched_horizon`	Number of days in the scheduling window.	Depending on the specific set up for optimization within the FRU, there could be an optimization process run for each date within the horizon. Since optimization is very heavy on processor usage, it is wise to restrict the number of days being optimized to those within the nearer horizon. The minimum value for this should be the number of days that the system dispatches at any one time.

Operative day boundaries

Parameter	Description	Considerations
`fru_day_rounding_val`	Automatically calculated operative day boundaries are snapped to multiples of this value (in hours). Should be set to be consistent with `glob_min_wd_len`.	Where employees work different shifts, and particularly over midnight shifts, it is necessary for the system to have a standard way to determine when one day should end and another begin.