Data Dictionary
>
FPSAPP Views
> FPSAPP.WIP_WAFER_HIST_LOOP
View FPSAPP.NMV_P_BAY_SUMMARY
Time-to-Start (TTS) data by tool for NextMove for all bays. If at least one lot is loaded on the tool then TTS is the time when the next lot needs to start after the most recently loaded lot in order to maintain the cascade. If no lots are loaded then TTS is data_date.
|
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) |
|
BAY |
A bay is a physical area within the building. The bay is important for estimating travel time for a carrier to reach its destination as we usually store these estimates as a matrix of bay-to-bay and assume that the estimated time from any location within one bay to any location within another bay is approximately the same. (* inherited from FPSINPUT.MHS_BAYS) |
|
BUILDING |
Building is the top of our MHS hierarchy at each site. It is independent of facility which is at the top of our EQP/RTG hierarchy. It is possible for a building to include multiple facilities and for a facility to include multiple buildings but we do not even need to define these relationships because EQP_TOOLS determines this by the combination of the facility and bay columns (since bay points to building). (* inherited from FPSINPUT.MHS_BUILDINGS) |
|
NEXT_LOT_TO_START_BEG_INST |
|
|
NEXT_LOT_TO_START |
|
|
NEXT_LOT_TO_START_CARRIER |
|
|
NEXT_LOT_TO_START_LOCATION |
|
|
NEXT_LOT_TO_START_BAY |
|
|
NEXT_LOT_TO_START_TOOL |
|
|
TIME_TO_NEXT_MOVE_INCOMING |
|
|
NEXT_LOT_TO_FINISH |
|
|
NEXT_LOT_TO_FINISH_CARRIER |
|
|
NEXT_LOT_TO_FINISH_BEG_INST |
|
|
NEXT_LOT_TO_FINISH_TOOL |
|
|
NEXT_LOT_TO_FINISH_END_INST |
|
|
NEXT_LOT_TO_FINISH_STATUS |
|
|
NEXT_LOT_TO_FINISH_IS_COMPLETE |
|
|
TIME_TO_NEXT_MOVE_OUTGOING |
|
|
NEXT_LOT_TO_MOVE |
|
|
NEXT_LOT_TO_MOVE_CARRIER |
|
|
NEXT_LOT_TO_MOVE_BEG_INST |
|
|
NEXT_LOT_TO_MOVE_TOOL |
|
|
NEXT_LOT_TO_MOVE_END_INST |
|
|
NEXT_LOT_TO_MOVE_STATUS |
|
|
NEXT_LOT_TO_MOVE_IS_COMPLETE |
|
|
TIME_TO_NEXT_MOVE_INTERNAL |
|
|
IS_HIGHLIGHTED_PRTY |
This flag indicates if this priority should be highlighted on the dashboard. When we sort all priorities by priority_sort all Y should be first followed by all N. (* inherited from FPSINPUT.WIP_PRIORITIES) |
|
NUM_CARRIERS_RESERVED |
|
|
NUM_CARRIERS_COMPLETE |
|
|
NUM_NEXT_MOVES |