data-dictionary

FPSINPUT.SCH_C_TMP_PROCESS_GROUPS_EVL

Data Dictionary

>

FPSINPUT Tables

> FPSINPUT.SCH_C_TMP_PROCESS_GROUPS_EVL

Table FPSINPUT.SCH_C_TMP_PROCESS_GROUPS_EVL"

This table is used to store the evaluation information for process group template.

  • Schema: FPSINPUT

  • Tablespace: FPSDATA

  • Primary key: FACILITY, SCHED_GROUP, PROCESS_GROUP, TEMPLATE_ID, EVALUATION_ID


Column

Type

Nullable

Comment

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)

PROCESS_GROUP

VARCHAR2(36)

N

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

TEMPLATE_ID

VARCHAR2(50)

N

EVALUATION_ID

VARCHAR2(50)

N

CURR_WEIGHTS

NUMBER

FOR_LOT_SCORE

CHAR(1)

FOR_TOOL_SCORE

CHAR(1)

IS_ACTIVE

CHAR(1)

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