On This Page:

Global parameters
Per FRU parameters

Related Pages:

14.1 FRU Process

An 14.1 FRU Process relies on Database sp083_system_parameters and Database sp213_scheduler_parameters to configure how the optimization processes work.

The business needs to determine how these parameters should be set to meet their business requirements. Ideally, the business users should update the parameters using the appropriate screens within the ServiceManager web application.

They are given below for information only.

Global parameters

Parameter

Mandatory/

Optional

Description

none

Per FRU parameters

Parameter Name	Mandatory/ Optional	Description
`opt_auto_alloc_horizon_after`	O	In conjunction with opt_auto_alloc_horizon_before gives the number of days considered when selecting intray jobs for optimizer pre/post process auto allocation. Only used when optimizer in single mode. Does not include optimizer start date, i.e. a setting of 0 means that the last date considered is the optimizer trigger start date.
`opt_auto_alloc_horizon_before`	O	In conjunction with opt_auto_alloc_horizon_after gives the number of days considered when selecting intray jobs for optimizer pre/post process auto allocation. Only used when optimizer in single mode. Does not include optimizer start date, i.e. a setting of 0 means that the first date considered is the optimizer trigger start date.
`opt_capability_horizon`	M	The number of days before and after the optimizer start date that the optimizer will consider for assigning jobs to other capable operatives. Only used when optimizer in single mode. Does not include optimizer start date, i.e. a setting of 0 means that the only date considered is the optimizer trigger start date.
`opt_discard_empty_days`	O	Should optimizer remove empty days from consideration for PM schedule?
`opt_max_no_opt_steps`	O	Used in PM mode to reduce the runtime of optimizers by stopping the optimization early if no further improvement can be found.
`opt_mode`	M	Denotes the running mode of the optimizer: 0 = multiple optimizers allowed; 1 = PM mode - single optimizer only.
`opt_region_selection_rule`	M	Indicates whether optimizer should use level 2 or level 3 region to group jobs together for mini-optimizer run in PM mode.
`opt_selection_horizon_after`	M	In conjunction with opt_selection_horizon_before gives the number of days considered for bringing together jobs in the same region. Only used when optimizer in single mode. Does not include optimizer start date, i.e. a setting of 0 means that the last date considered is the optimizer trigger start date.
`opt_selection_horizon_before`	M	In conjunction with opt_selection_horizon_after gives the number of days considered for bringing together jobs in the same region. Only used when optimizer in single mode. Does not include optimizer start date, i.e. a setting of 0 means that the first date considered is the optimizer trigger start date.
`WOOSH`	M	Cost per minute of job’s work time out of Service Hours (excluding Grace Period).

Browser not supported