Data Dictionary
>
FPSADMIN Views
> FPSADMIN.WIP_WAFER_HIST_LOOP
View FPSAPP.SCH_P_ADMIN_CHK_SCHED_GROUPS
This is to check what could tbe the potential reasons the scheduler won't run it will check 1. ON/OFF of sched_group 2. if SCH_C_FACILITIES is set properly 3. if it has data to schedule, lots, tools and tool assignments 4. if it has good configuration on SCH_C_CFG_XXX tables 5. if it has good SERVICE_HOST and SERVICE_WEB
|
Column |
Comment |
|---|---|
|
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) |
|
REASONS_NOT_RUN |
|
|
SCHED_GROUP_STATE |
State is constrained to one of three values. ON: Running for production. DEV: Schedule is visible for authorized users only (Q-Mgr and Scheduler run as if ON). OFF: Rarely used except when setting up a new sched_group. (* inherited from FPSINPUT.RTG_SCHED_GROUPS) |
|
WAIT_SEC_TO_TIME_OUT |
|
|
MAX_CAL_SEC |
This is used to set how many seconds allowed to run the single-looping calculation. This includes all time taken for parallel calculation in AVG_CAL_SEC. As an example, if AVG_CAL_SEC is 300 and MAX_CAL_SEC is 360 then the first 300 seconds will be done with parallel calculation and the remaining 60 with serial/single-loop calculations. If scheduler takes more than this time to complete, it will be tagged as SLOW. This value should be greater than or equal to AVG_CAL_SEC. If equal to AVG_CAL_SEC, all calculations will be done via parallel calculations. (* inherited from FPSINPUT.RTG_SCHED_GROUPS) |
|
DAYS_TO_KEEP_HIST |
This is used to determine how long to keep the historical data (* inherited from FPSINPUT.RTG_SCHED_GROUPS) |
|
NUM_LOTS |
|
|
NUM_ASGNS |
|
|
NUM_TOOLS |
|
|
CONFIG_ID |
This is used to tell which configuration the current sched-group is using (* inherited from FPSINPUT.RTG_SCHED_GROUPS) |
|
CFG_EVL_COUNT |
|
|
CFG_KPI_COUNT |
|
|
HOST_WEB |
|
|
HOST_SERVICE |
|
|
CFG_GBL_SORT |
|
|
CFG_LOT_PRIORITY |
|
|
CFG_PERM_RANK |