FPSADMIN.SCH_P_CURR_SCHED_GROUPS

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)

SCHED_GROUP_DESC

Longer description of sched_group (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

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)

IS_DEFAULT

This is used to land the first sched group on the scheduler/web by default (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

SERVICE_URL

HOURS_TO_SCHEDULE

This column is used to determine how many hours to look ahead and schedule the lots that might come into this area/SCHED-GROUP even it is still several steps away. (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

STEPS_TO_SCHEDULE

This column is used to determine how many steps to look ahead and schedule the lots that might come into this area/SCHED-GROUP even it is still several hours away. Between HOURS_TO_SCHEDULE and STEPS_TO_SCHEDULE, the Scheduler will try to schedule all the lots either will arrive within X hours OR within Y steps away. (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

HOURS_TO_DISPLAY

WILL REMOVE SOON (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

CURR_RUN_MODE

WILL REMOVE SOON (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

CURR_NUM_RUNS_FAIL

WILL REMOVE SOON (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

CURR_NUM_RUNS_SUCCESS

WILL REMOVE SOON (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

DEFAULT_NUM_RUNS_FAIL

WILL REMOVE SOON (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

DEFAULT_NUM_RUNS_SUCCESS

WILL REMOVE SOON (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

SORT_ORDER

This is used to sort within the grouping. SORT_ORDER always has a deferrable unique key to ensure uniqueness while allowing the user to make changes without erroring until the commit is attempted. Because of this you must be careful to not violate the unique key otherwise you will lose all of your edits. (* inherited from FPSINPUT.GEN_FACILITIES)

INT_SEC_TO_RUN_SCHEDULER

This column is used to determine how often to run the scheduler for this SCHED-GROUP. For example, if it sets 60 seconds in this column, it means it will wait for at least 60 seconds before initializing a new scheduler run from the end time of previous run. (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

INT_SEC_TO_REFRESH_WEB_DATA

Interval where Scheduler will refresh cached web data after this many seconds have elapsed since last refresh (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

WAIT_SEC_TO_TIME_OUT

UPDATED_INST

Time when the record was updated according to the source data. Note this is not the time when the record was actually updated in this table - it will almost always be earlier. (* inherited from FPSINPUT.GEN_FACILITIES)

SHOULD_SCHEDULE_HOLD_LOTS

This is used to indicate if the scheduler should schedule the hold lot or not (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

SHOULD_SCHEDULE_BLOCK_LOTS

WILL REMOVE SOON (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

SHOULD_SHOW_SETUP_ON_LEGEND

To indicate if it is going to display the setup on the legends on the Scheduler/Web (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

RESCHED_MAX_CAP_SEC

WILL REMOVE SOON (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

DEFAULT_BAY

for each sched group it will have default bay. this is really for the durable location issue (* inherited from FPSINPUT.RTG_SCHED_GROUPS)

RUN_ID

the run id from the last successful scheduler (* inherited from FPSAPP.SCH_W_SCHED_GROUP_STATUS)