FPSAPP.SCH_C_GROUP_LOT_PRIORITIES

FACILITY

VARCHAR2(6)

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. (* from FPSINPUT.GEN_FACILITIES)

SCHED_GROUP

VARCHAR2(36)

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. (* from FPSINPUT.RTG_PROCESS_GROUPS)

PRIORITY

VARCHAR2(7)

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. (* from FPSINPUT.WIP_PRIORITIES)

ENABLE_DISPATCH

CHAR(1)

Enable/Disable Dispatch by Lot Priorities

EXPEDITE_DELIVERY

CHAR(1)

HTML_STYLE

VARCHAR2(500)

used to configure how to display this lot priority on kitting/scheduler web page

LATE_DAYS_LOGISTIC_SLOPE

NUMBER(4,2)

The steepness of the S-curve function for lot days late. Larger numbers mean steeper curves - i.e. closer to a step function change.

MAX_WAIT_TIME_EXTRA_LOTS_RQD

NUMBER(3)

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

MAX_WAIT_TIME_PCT

NUMBER(3)

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

PROC_TIME_LOOK_AHEAD_PCT

NUMBER

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. (* from FPSINPUT.WIP_PRIORITIES)

RESERVE_AHEAD

CHAR(1)

RESERVE_ALWAYS

CHAR(1)

RESERVE_DOWN_TOOL

CHAR(1)

SCHED_END_TIME_WAIT_PCT

NUMBER(4)

used to determine if this priority will allow late sched-end time for batching

SCHED_RANK

NUMBER

SCHED_WEIGHTS

NUMBER(4,1)

is used to determine the sched weights on this lot priority in the sched-group

STEP_ENTER_LOGISTIC_MID_HRS

NUMBER(3,1)

The midpoint of the S-curve function for step enter time. After this many hours, the raw sore will equal 5 for the function.

STEP_ENTER_LOGISTIC_SLOPE

NUMBER(3

The steepness of the S-curve function for step enter time. Larger numbers mean steeper curves - i.e. closer to a step function change.