FPSBASE.SCH_P_GROUP_LOT_PRIORITIES

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)

PRIORITY

This is the priority value as it is stored in the MES for each lot. It might be a number or a letter or word depending on the MES and the facility. (* inherited from FPSINPUT.WIP_PRIORITIES)

SCHED_RANK

SCHED_WEIGHTS

This is how much weight to give the chamber path rank. When populated, this will override the weights for chamber path rank and tool assignment rank. If null, then Scheduler will take the value from the configuration table SCH_C_GROUP_PERM_RANKS. example 1: ovr_sched_weights is 40 -> the chamber path rank will have a weight of 40, regardless of what ovr_ch_path_rank is. example 2: ovr_sched_weights is null and ovr_ch_path_rank == "A" -> the chamber path rank will get the weight for "A" from SCH_C_GROUP_PERM_RANKS example 3: ovr_sched_weights is null and ovr_ch_path_rank is null-> the chamber path rank will use the tool assignment rank and get the weight from SCH_C_GROUP_PERM_RANKS (* inherited from FPSAPP.SCH_W_H_S_CH_PATH_ASSIGNMENTS)

PROC_TIME_LOOK_AHEAD_PCT

For batching logic in the Scheduler, the percentage of the processing time that we will wait for future lots to arrive to make a full batch. For example, high priorities might have 0 for this column meaning we will never wait for future lots. Standard priority default is 100 meaning if the batch processing time is 2 hours that we would wait for up to 2 hours for future lots to arrive. Low priority might be 200 meaning we will wait up to 4 hours. Of course Scheduler might choose to process an incomplete batch sooner based on other logic but this is upper bound. (* inherited from FPSINPUT.WIP_PRIORITIES)

SCHED_END_TIME_WAIT_PCT

used to determine if this priority will allow late sched-end time for batching (* inherited from FPSAPP.SCH_C_GROUP_LOT_PRIORITIES)

PRIORITY_DISPLAY

The name of the priority displayed on all dashboards and reports. Typically priority is short like P1, P2 so we allow a longer more descriptive name here that should be more familiar to the users. (* inherited from FPSINPUT.WIP_PRIORITIES)

PRIORITY_SORT

Unique sort of priority. Sort ascending gives the order from highest to lowest priority. Therefore the smallest number in priority_sort is the highest priority. (* inherited from FPSINPUT.WIP_PRIORITIES)

PRIORITY_DESC

IS_HIGHLIGHTED_PRTY

This flag indicates if this priority should be highlighted on the dashboard. When we sort all priorities by priority_sort all Y should be first followed by all N. (* inherited from FPSINPUT.WIP_PRIORITIES)

SCHED_RANK_DISPLAY

SCHED_RANK_DESC

EXPEDITE_DELIVERY

RESERVE_AHEAD

RESERVE_ALWAYS

RESERVE_DOWN_TOOL

ENABLE_DISPATCH

Enable/Disable Dispatch by Lot Priorities (* inherited from FPSAPP.SCH_C_GROUP_LOT_PRIORITIES)

LATE_DAYS_LOGISTIC_SLOPE

The steepness of the S-curve function for lot days late. Larger numbers mean steeper curves - i.e. closer to a step function change. (* inherited from FPSAPP.SCH_C_GROUP_LOT_PRIORITIES)

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)

STEP_ENTER_LOGISTIC_MID_HRS

The midpoint of the S-curve function for step enter time. After this many hours, the raw sore will equal 5 for the function. (* inherited from FPSAPP.SCH_C_GROUP_LOT_PRIORITIES)

STEP_ENTER_LOGISTIC_SLOPE

The steepness of the S-curve function for step enter time. Larger numbers mean steeper curves - i.e. closer to a step function change. (* inherited from FPSAPP.SCH_C_GROUP_LOT_PRIORITIES)

BG_COLOR_HTML

BRD_COLOR_HTML

TEXT_COLOR_HTML