Data Dictionary
>
FPSADMIN Views
> FPSADMIN.WIP_WAFER_HIST_LOOP
View FPSBASE.EQP_TOOL_PLAN_DAY_HIST_NOW
Unions EQP_TOOL_PLAN_DAY_HIST table with the realtime data for all days not yet in the history. The previous day is never in the history since we do not load until one day has past to allow for post-updates of the eqp_state. This view includes the partial data for the current shift. IMPORTANT NOTE: This view uses DASH_B_H_ETP_7D table for speed but that table only has data for either EQP or ETP whichever one is active on the Dashboard. Therefore this view will return data for the previous and current shift only if ETP is active! This works perfectly for the Dashboard as long as we are still using the flag. In a future version, we will show both EQP and ETP together and at that time we will have to populate two different DASH_B_H_xxx_7D tables and modify this view accordingly.
|
Column |
Comment |
|---|---|
|
START_PLAN_DAY |
Plan days must be 24 hours in length and the start of the plan day must be the start of one of the shifts. Contrast this to plan day which is independent of shift. (* inherited from FPSINPUT.CAL_PLAN_DAYS) |
|
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) |
|
TOOL |
Tool is generally just the main tool. The exception is when different entities on the tool run completely independently and it is physically impossible to run wafers of the same lot across multiple entities. In this exception case, we may want to assign the entities to different eqp_types and therefore we should define each entity as a tool. Please note that when we do this there is no indication whatsoever that these different entities are on the same tool. (* inherited from FPSINPUT.EQP_TOOLS) |
|
EQP_STATE |
Client equipment state taken directly from their MES or from their existing tool state model. For EQP_MNT_FUTURE, this is the state that we estimate the entity will be in during the maintenance which is often set to a generic PM state if we do not have detailed information. (* inherited from FPSINPUT.EQP_L6_DETAILED_STATES) |
|
SECONDS |
|
|
IS_CURR_PLAN_DAY |