Data Dictionary
>
FPSBASE Views
> FPSBASE.WIP_WAFER_HIST_LOOP
View FPSBASE.ECT_APD_STATE_WEEK_HIST
ECT_STATE_WEEK_HIST is a weekly history table with the ect_state column added to the standard primary key of facility, prd, planprd, route, step, bank, prty_ctm_group, lot_group. This means that instead of having separate columns for total_proc_sec, total_hold_sec, total_wait_sec, etc. that we have separate rows for each ect_state and a single column named total_unit_seconds. This total_unit_seconds column can be divided by the total seconds in the week to get the average WIP in that ect_state. It can also be divided by the total moves for the standard primary key in the week to get the cycle time. For example, if one 25 wafer lot spends 2 days in the ect_state and another 5 wafer lot spends 3 days in the ect_state then the total_unit_seconds for that ect_state will be 25*2*86400 + 5*3*86400 = 5616000 unit-seconds. To get average WIP, divide this by the total seconds in the week so 234000/604800 = 9.29 wafers in this ect_state on average. To get cycle time, divide by the total moves for the standard primary key of facility, prd, planprd, route, step, bank, prty_ctm_group, lot_group which we will get from the CTM_WEEK_HIST table which has the primary key of just these standard columns without ect_state. If these two lots were the only two lots of this key for the week and both moved then we would have 30 moves so 234000/30 = 7600 seconds = 2.16 hours. If there was another 20 wafer lot that moved which did not spend any time in this ect_state then we would have 50 moves and the cycle time would go down: 234000/50 = 4680 seconds = 1.3 hours. On the other hand, if no other lots moved and the 5 wafer lot remained in the WIP at the end of the WIP then we would have just 20 moves and the cycle time would go up: 234000/25 = 9360 seconds = 2.6 hours.
|
Column |
Comment |
|---|---|
|
START_WEEK |
Work weeks must be 7 days in duration and the start of the work week must be the start of one of the work days. (* inherited from FPSINPUT.CAL_WORK_WEEKS) |
|
END_WEEK |
It is critical that this field equal the start_week of the next work work. (* inherited from FPSINPUT.CAL_WORK_WEEKS) |
|
ECT_STATE |
ECT state is the lowest level state of our Enhanced Cycle Time hierarchy and the value which is stored in WIP_LOTS_REALTIME and ECT_HIST. We can lookup all information about the ECT state including process state in ECT_STATE_DIAGRAM. (* inherited from FPSADMIN.WIP_ECT_STATES) |
|
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) |
|
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) |
|
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) |
|
TOTAL_UNIT_SECONDS |
|
|
NUM_LOTS_STARTWIP |
|
|
QTY_STARTWIP |
|
|
NUM_LOTS_ENDWIP |
|
|
QTY_ENDWIP |