FPSAPP.SCH_W_H_S_TOOL_EVENTS

ACTUAL_START_INST

DATE

to store the actual start time of the tool event

CH

VARCHAR2(1)

to store the chamber that this event is associated to

CH_TYPE

VARCHAR2(6)

to store the chamber type that this event is associated to

CREATE_INST

DATE

EARLY_DUE_INST

DATE

to store the early due time of the floating PM tool event, i.e., the early start time of the floating PM could be calculated via substracting the EST_DURATION_SEC value (* from FPSAPP.SCH_W_TOOL_SCHED_EVENTS)

END_INST

DATE

N

The time the even is scheduled to end (* from FPSINPUT.EQP_SCHED_EVENTS_MANUAL)

ENTITY

VARCHAR2(19)

to store the entity to which the tool event is associated

EST_DURATION_SEC

NUMBER(8)

to store the est duration of the tool event

EVENT

VARCHAR2(48)

N

This is the event registered in the MES. This is for the historical record and display only. Each event is mapped to an FPS event_type and the event_type is what is used by FPS applications. (* from FPSINPUT.WIP_EVENTS)

EVENT_CATEGORY

VARCHAR2(40)

to store the event_category, e.g., NOT_TO_SCHEDULE, NOT_TO_START etc.

EVENT_DESC

VARCHAR2(500)

Event Description (* from FPSINPUT.EQP_SCHED_EVENTS_MANUAL)

EVENT_TYPE

VARCHAR2(12)

N

Event Type (* from FPSINPUT.EQP_SCHED_EVENTS_MANUAL)

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)

LATE_DUE_INST

DATE

to store the late due time of the floating PM tool event, i.e., the late start time of the floating PM could be calculated via substracting the EST_DURATION_SEC value (* from FPSAPP.SCH_W_TOOL_SCHED_EVENTS)

OTHER_NOTE

VARCHAR2(500)

Some description for this scheduler (* from FPSINPUT.RTG_SCHED_GROUPS)

RUN_ID

VARCHAR2(50)

N

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

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)

SHOULD_USE

CHAR(1)

This flag determines if the scheduler should use this data or not

START_INST

DATE

N

Time when the lot started. (* from FPSINPUT.WIP_STARTS)