Data Dictionary
>
FPSAPP Views
> FPSAPP.WIP_WAFER_HIST_LOOP
View FPSAPP.SCH_P_CURR_THREAD_ASSIGNMENTS
this view is used to indicate the possible threading tools that the scheduler should consider. 1. for the lot already entered into the threading, the scheduler should only schedule the future_thread_step to the allowed thread_group 2. for the lot that at not yet entered into the threading, then the scheduelr should schedule the start step first and according to the tool it is scheduled, then the the scheduler should only schedule the future_thread_step to the allowed thread_group
|
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) |
|
LOT |
A lot is a group of units that process together. Usually lot_id or lot_number in MES. All units in a lot are in the same carrier but there may be multiple lots in a carrier. (* inherited from FPSINPUT.WIP_LOTS_STATIC) |
|
ROUTE |
Route that has threading requirements (* inherited from FPSINPUT.RTG_STEP_THREADING) |
|
STEP_START |
|
|
NUM_STEPS_AWAY_START |
|
|
SCHED_GROUP_START |
|
|
STEP_END |
|
|
NUM_STEPS_AWAY_END |
|
|
SCHED_GROUP_END |
|
|
THREAD_GROUP |
This is an optional field for thread grouping. If populated then all possible tools will be the thread_tool. If not then it will be the tool where the lot ran on at the start thread step. (* inherited from FPSINPUT.RTG_STEP_THREADING) |
|
THREAD_TOOL |
Tool that the lot will be forced to run on at the future thread step if the tool processes the lot at the start step (* inherited from FPSINPUT.RTG_STEP_THREADING) |
|
THREAD_GROUP_START |
|
|
SCHED_TOOL_START |
|
|
THREAD_GROUP_END |
|
|
SCHED_TOOL_END |
|
|
THREAD_TOOL_RANK |
|
|
NON_THREAD_TOOL_RANK |
Rank for other tools at the End Step for the lot that processed on the thread tool at the start step (* inherited from FPSINPUT.RTG_STEP_THREADING) |