Data Dictionary
>
FPSINPUT Views
> FPSINPUT.WIP_WAFER_HIST_LOOP
View FPSBASE.EQP_WIP_COMP_TGTS
Base logic of wip and completes targets for NextMove Bay Performance pages. Targets are derived form wip_goal_est_shift by route step. Allowed tools (Rank P or A) are joined from RTAL where the route-step exists or from RTA where route-step does not exist in RTAL. Completes targets for the day are simply x2 that of the shift. WIP targets for day are equal to that of the shift. Customer override values are joined from Wip_metics_goal_ovr.
|
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) |
|
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) |
|
GOAL_WIP_PCT_TO_TGT_BAY_PERF |
The plus / minus percentage of target WIP that is considered acceptable in the Bay Performance NMV pages. EG 20% gives acceptable WIP range of 80 to 120 on a target of 100. (* inherited from FPSINPUT.GEN_SITE) |
|
SHIFT_TGT_COMP |
|
|
DAY_TGT_COMP |
|
|
SHIFT_TGT_WIP |
|
|
DAY_TGT_WIP |