FPSINPUT.SCH_P_CFG_PROCESS_GROUPS_EVL

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)

CONFIG_ID

This is used to tell which configuration the current sched-group is using (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

TEMPLATE_ID

EVALUATION_ID

EVL_SORT_ORDER

CURR_WEIGHTS

NORMALIZATION_RATIO

EVALUATION_METHOD

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) (* inherited from FPSAPP.SCH_C_CFG_SCHED_GROUPS_EVL)

IS_EVALUATION_METHOD_EDITABLE

MIN_WEIGHTS

used to determine the minimum weight for each evaluation (* inherited from FPSAPP.SCH_G_EVALUATIONS)

MAX_WEIGHTS

used to determine the maximum weight for eachF evaluation (* inherited from FPSAPP.SCH_G_EVALUATIONS)

STEP_WEIGHTS

EVL_PREFIX_INPUT_ID

INPUT_DISPLAY

INPUT_DESC

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

CALCULATION_METHOD

SHOULD_APPLY_TO_STAGING_STEP

This is to indicate if this evaluation item should be applied to the staging step while the scheduler is compiling the lot score on the lot level. usually any evaluation releated to the tool should be set to N. (* inherited from FPSAPP.SCH_G_EVALUATIONS)

DIFFERENT