FPSAPP.SCH_C_GROUP_LOT_GBL_SORTS

FACILITY

VARCHAR2(6)

N

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)

N

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)

GBL_SORT

NUMBER

N

Sorting used for dispatching or allocation systems to sort future start lots based on priority, critical ratio, etc. (* from FPSINPUT.WIP_STARTS)

ENABLE_DISPATCH

CHAR(1)

Enable/Disable Dispatch by Global Sort

EXPEDITE_DELIVERY

CHAR(1)

RESERVE_AHEAD

CHAR(1)

RESERVE_ALWAYS

CHAR(1)

RESERVE_DOWN_TOOL

CHAR(1)

SCHED_RANK

NUMBER

SCHED_WEIGHTS

NUMBER(4

is used to determine the sched weights on this gbl-sort in the sched-group