FPSBASE.SCH_P_CURR_PROCESS_GROUPS

FACILITY

Facility is included in almost every join in the DWH so this represents a definitive split. A route must have all steps on tools in the same facility. A tool must process all lots in the same facility. If your site has multiple buildings where lots run on routes using tools in multiple buildings then everything should be one facility. For example, multiple Fab buildings. But if your site has independent facilities like Fab and Test and Assembly where lot may progress from one to the next but on different routes then these should be different facilities. Since this column is in virtually every table it is critical that the value here is exactly matches what is in the MES if the MES has facility. Use facility_display for the display friendly name displayed in applications. See site_name comment for client/site/facility example. (* inherited from FPSINPUT.GEN_FACILITIES)

SCHED_GROUP

This is the grouping of tools and processes which the FPS Scheduler schedules together. Since this is a parent of tool via tool->process_group and a parent of process via process->process_group, by definition each tool and each process can only be in one sched group. We need all related tools and processes to be in the same sched group for efficient scheduling. One example is sinks and furnaces because of queue times and batching. Another example is for smaller facilities like Assembly or Test where we might schedule the entire facility together. (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)

PROCESS_GROUP

Process group is the critical field where tools and processes come together for the purposes of Scheduler. Process group is in both EQP_TOOLS for the tools and in RTG_PROCESSES for processes. Ideally all tools that run the same set of processes with no crossover including back-up and emergency tools would be in the same process group but it is important to note that this is not technically required for Scheduler as long as all process groups are in the same sched group. (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)

SCHED_GROUP_STATE

State is constrained to one of three values. ON: Running for production. DEV: Schedule is visible for authorized users only (Q-Mgr and Scheduler run as if ON). OFF: Rarely used except when setting up a new sched_group. (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

DEFAULT_INPUT_ID

WAIT_SEC_TO_ALLOW_DOWN_RESERVE

This column is part of the Area Scheduler configuration. Please see Area Scheduler documentation for details. (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)

MAX_WAIT_TIME_PCT

to indicate how much time this priority is willing to wait for the coming lots to batch, this need to work with max_wait_time_extra_lots_rqd; if value is 0, then it means not going to wait at all. (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)

MAX_WAIT_TIME_EXTRA_LOTS_RQD

to indicate how many more lots this priority is willing to wait to batch, this need to work with max_wait_time_pct; by default, 999 meaning not going to way, but the minimum is 1, additional lot required to wait. (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)

CRITICAL_TOOL_HOURS

to determine how many hours to calculate the critical tool score; when set to 6 ours, then the scheduler will only look into how many tool are available within 6 hours and how many lots will be able to run within 6 hours (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)

SHOULD_RESERVE_BACK_TO_BACK

to determine if need to schedule back-to-back steps (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)

SHOULD_USE_EXTL_RSRV_TOOL

This flag determines if the scheduler should use the column extl_reserve_tool or not (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)

WAIT_FOR_LARGER_BATCH

This flag determines if the scheduler should always wait for an eligible larger batch for tools under this process group (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)

PREFER_TO_JOIN_BATCH

When set to Y, the scheduler will prefer to add a lot to an already started batch over starting a new batch, even if the score for starting a new batch would be higher (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)