FPSADMIN.SCH_W_SCHED_SUMMARY

RUN_ID

VARCHAR2(50)

N

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

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)

CONFIG_ID

VARCHAR2(50)

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

CREATE_INST

DATE

EST_START_INST

DATE

Best guess at when the mnt event started. If actual_start_inst is provided it will be that value otherwise it will be the inst - est_mnt_duration_sec (* from FPSBASE.EQP_MNT_HIST)

HOURS_TO_SCHEDULE

NUMBER

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

NUM_LOT_NOT_SCHEDULED

NUMBER

NUM_LOT_SCHEDULED

NUMBER

PCT_LOTSTEPS_PLACED

NUMBER

RUN_BY

VARCHAR2(256)

RUN_COMMENTS

VARCHAR2(1024)

RUN_END_INST

DATE

RUN_LOCATION

VARCHAR2(500)

RUN_METHOD

VARCHAR2(24)

RUN_START_INST

DATE

RUN_STATE

VARCHAR2(500)

SAVE_START_INST

DATE

SCHED_VERSION

VARCHAR2(50)

SEC_CALCULATE

NUMBER

SEC_LOAD_CONFIG

NUMBER

SEC_LOAD_DATA

NUMBER

SEC_SAVE

NUMBER

STEPS_TO_SCHEDULE

NUMBER

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

UPDATE_INST

DATE