FPSINPUT.SCH_C_TMP_SCHED_GROUPS_EVL

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)

TEMPLATE_ID

VARCHAR2(50)

EVALUATION_ID

VARCHAR2(50)

CURR_WEIGHTS

NUMBER

EVALUATION_METHOD

VARCHAR2(8)

Used to define how the scheduler will evaluate each lot for scheduling if it has multiple steps to schedule once, for example for the timer lot. The available options: FIRST: it will take the first step of the sequence of steps to calcualte the lot score CURRENT: it will take the current step (the next step to schedule) of the sequence of steps to calcualte the lot score LAST: it will take the last step of the sequence of steps to calcualte the lot score AVERAGE: it will take the average score from each step in this sequence for the lot score MAX: it will take the maximum score from each step in this sequence for the lot score MIN: it will take the minimum score from each step in this sequence for the lot score for example, lot A has step 1, 2 3 to schedule, and currently the first lot to be scheduled is 2: FIRST: 1 CURRENT: 2 LAST: 3 AVERAGE: avg(1, 2, 3) MAX: max(1, 2, 3) MIN: min(1, 2, 3) (* from FPSAPP.SCH_C_CFG_SCHED_GROUPS_EVL)

FOR_LOT_SCORE

CHAR(1)

FOR_TOOL_SCORE

CHAR(1)

INPUT_DESC

NVARCHAR2(2000)

used to set a slider description display that will stay constant within the sched_group (* from FPSAPP.SCH_C_EVALUATIONS)

INPUT_DISPLAY

VARCHAR2(500)

IS_ACTIVE

CHAR(1)

Flag to enable or disable the tag condition. (* from FPSBASE.MSO_TAG_CONDITIONS)

NORMALIZATION_RATIO

NUMBER