Data Dictionary
>
FPSADMIN Views
> FPSADMIN.WIP_WAFER_HIST_LOOP
View FPSBASE.ECT_REF_SUMMARY
This table stores the base table for all non-trend Cycle Time Analyzer data using the ECT logic. Here we get all of the steps for routes where we have data for at least one step and we include all steps with avg WIP so that the avg WIP totals will be correct. This logic uses CTM_SUMMARY for fill-in logic, target/commit/fifo, sampling percentage and more which obviously means that it does not replace CTM_SUMMARY. If we are going to continue down the path of replacing it with ECT logic then we would have to include the logic for all of those columns here. First and foremost would be better fill-in logic. Please note that the ECTA queries must filter module, process family, and process at the very end in order to weight properly by route. This means that there is no reason to have indexes on any of these columns.
|
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) |
|
PRD |
Prd determines the route which is used to process the lot in the facility and what tools, recipes, durables, etc. can be used at each step. Prd also determines the next facility for the lot when it finishes its route. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* inherited from FPSINPUT.RTG_PRDS) |
|
PLANPRD |
Planning product used for all planning purposes. All lots with the same planprd are interchangeable to ship to the customer regardless of their prd, route, technology, wafer size, etc. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* inherited from FPSINPUT.RTG_PLANPRDS) |
|
ROUTE |
Route that has threading requirements (* inherited from FPSINPUT.RTG_STEP_THREADING) |
|
STEP |
A single processing step within a route representing a single tool visit. Step is often a very complex string and should rarely be displayed. Instead we should use process_display. (* inherited from FPSINPUT.RTG_ROUTE_STEPS) |
|
BANK |
Lots which are not on a route are considered in a bank and the bank name indicates why the lot is off route. Bank must be NA for lots which are on a route. Our standard filter for active lots is bank = NA. (* inherited from FPSINPUT.RTG_BANKS) |
|
PRTY_CTM_GROUP |
This is one of the primary keys of our CTM tables. We use this group rather than the priority because we often have several different priorities which are close and are expected to have the same cycle time. (* inherited from FPSINPUT.WIP_PRIORITIES) |
|
LOT_GROUP |
Lot_group is a grouping of lot_family and is the highest grouping in the lot type hierarchy. There should be only a few values for lot_group, i.e. Prod, Dev, TW. We group WIP and moves by lot_group on the dashboard and we group cycle time calculations by lot_group so this is an important field. (* inherited from FPSINPUT.WIP_LOT_GROUPS) |
|
IS_NONSTD |
Our column to indicate non-standard processing at the step. For example, an experiment or a chain that is only active at a particular step or set of steps and then goes back to being normal for the route. If an experiment is severe enough that it affects the final product and has to be planned separately then it will be its own prd or planprd. (* inherited from FPSBASE.WIP_LOT_HIST) |
|
QTY_COMP_FULL |
|
|
QTY_MOVED_FULL |
|
|
NUM_LOTS_MOVED_FULL |
|
|
AVG_WIP_FULL |
|
|
WHY_PROC_FULL |
|
|
WHY_OTHERS_FULL |
|
|
WHY_SKIP_FULL |
|
|
ABORT_SEC_FULL_WAVG |
|
|
BLOCK_SEC_FULL_WAVG |
|
|
DISP_SEC_FULL_WAVG |
|
|
DOWN_SEC_FULL_WAVG |
|
|
ENDED_SEC_FULL_WAVG |
|
|
HOLD_SEC_FULL_WAVG |
|
|
LONGH_SEC_FULL_WAVG |
|
|
PROC_SEC_FULL_WAVG |
|
|
RESRV_SEC_FULL_WAVG |
|
|
SHUTD_SEC_FULL_WAVG |
|
|
STG_SEC_FULL_WAVG |
|
|
WAIT1_SEC_FULL_WAVG |
|
|
WAIT2_SEC_FULL_WAVG |
|
|
WAIT3_SEC_FULL_WAVG |
|
|
STEP_SEC_FULL_WAVG |
|
|
QTY_COMP_LONG |
|
|
QTY_MOVED_LONG |
|
|
NUM_LOTS_MOVED_LONG |
|
|
AVG_WIP_LONG |
|
|
WHY_PROC_LONG |
|
|
WHY_OTHERS_LONG |
|
|
WHY_SKIP_LONG |
|
|
ABORT_SEC_LONG_WAVG |
|
|
BLOCK_SEC_LONG_WAVG |
|
|
DISP_SEC_LONG_WAVG |
|
|
DOWN_SEC_LONG_WAVG |
|
|
ENDED_SEC_LONG_WAVG |
|
|
HOLD_SEC_LONG_WAVG |
|
|
LONGH_SEC_LONG_WAVG |
|
|
PROC_SEC_LONG_WAVG |
|
|
RESRV_SEC_LONG_WAVG |
|
|
SHUTD_SEC_LONG_WAVG |
|
|
STG_SEC_LONG_WAVG |
|
|
WAIT1_SEC_LONG_WAVG |
|
|
WAIT2_SEC_LONG_WAVG |
|
|
WAIT3_SEC_LONG_WAVG |
|
|
STEP_SEC_LONG_WAVG |
|
|
QTY_COMP_7D |
|
|
QTY_MOVED_7D |
|
|
NUM_LOTS_MOVED_7D |
|
|
AVG_WIP_7D |
|
|
WHY_PROC_7D |
|
|
WHY_OTHERS_7D |
|
|
WHY_SKIP_7D |
|
|
ABORT_SEC_7D_WAVG |
|
|
BLOCK_SEC_7D_WAVG |
|
|
DISP_SEC_7D_WAVG |
|
|
DOWN_SEC_7D_WAVG |
|
|
ENDED_SEC_7D_WAVG |
|
|
HOLD_SEC_7D_WAVG |
|
|
LONGH_SEC_7D_WAVG |
|
|
PROC_SEC_7D_WAVG |
|
|
RESRV_SEC_7D_WAVG |
|
|
SHUTD_SEC_7D_WAVG |
|
|
STG_SEC_7D_WAVG |
|
|
WAIT1_SEC_7D_WAVG |
|
|
WAIT2_SEC_7D_WAVG |
|
|
WAIT3_SEC_7D_WAVG |
|
|
STEP_SEC_7D_WAVG |
|
|
QTY_COMP_2D |
|
|
QTY_MOVED_2D |
|
|
NUM_LOTS_MOVED_2D |
|
|
AVG_WIP_2D |
|
|
WHY_PROC_2D |
|
|
WHY_OTHERS_2D |
|
|
WHY_SKIP_2D |
|
|
ABORT_SEC_2D_WAVG |
|
|
BLOCK_SEC_2D_WAVG |
|
|
DISP_SEC_2D_WAVG |
|
|
DOWN_SEC_2D_WAVG |
|
|
ENDED_SEC_2D_WAVG |
|
|
HOLD_SEC_2D_WAVG |
|
|
LONGH_SEC_2D_WAVG |
|
|
PROC_SEC_2D_WAVG |
|
|
RESRV_SEC_2D_WAVG |
|
|
SHUTD_SEC_2D_WAVG |
|
|
STG_SEC_2D_WAVG |
|
|
WAIT1_SEC_2D_WAVG |
|
|
WAIT2_SEC_2D_WAVG |
|
|
WAIT3_SEC_2D_WAVG |
|
|
STEP_SEC_2D_WAVG |
|
|
STEP_SEC_NOHOLD_FOR_WSF |
The FOR_WSF columns are used in populating WIP_STEP_FUTURE. This is based on the CTM_COLUMN_FOR_WIP_STEP_FUT column in GEN_FACILITIES. For example, if the value of that column is 7D_WAVG then we use the 7D_WAVG cycle times for WSF. (* inherited from FPSBASE.CTM_SUMMARY) |
|
HOLD_SEC_FOR_WSF |
|
|
EST_LINE_YIELD_PCT |
Estimated line yield percent for the route-step. Leave blank for the default of no loss expected. A value of 99.5 means we expected 1 unit out of 200 to be lost. (* inherited from FPSINPUT.RTG_ROUTE_STEPS) |
|
EST_SMP_PCT |
Smp_pct tells you what percentage of the lots complete on a tool. Some sites skip steps by jumping over them so we see the lot move from step 3 to step 5 and we only know that it jumped step 4 because step 4 is on the route between 3 and 5. Other sites skip steps by moving lots into them and then moving them out a second later so we see a move from 3 to 4 at 11:11:11 and a move from 4 to 5 at 11:11:12. We do not care how it is done but just that the lot did not process at step 4 -- and to be more specific that no tool capacity is required to process this lot at step 4 and no cycle time is accumulated at step 4. (* inherited from FPSBASE.WIP_GOAL_LOT_SHIFT) |
|
SMP_RATE_FULL |
|
|
TCT_SEC |
Theoretical cycle time in seconds (* inherited from FPSBASE.WIP_LOT_HIST) |
|
FIFO_STEP_SEC |
|
|
TARGET_STEP_SEC |
|
|
COMMIT_STEP_SEC |
|
|
EST_TRANSIT_SEC |
|
|
ESTIMATED |