FPSBASE.NMV_P_TOOL_SUMMARY

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)

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)

PROCESS_FAMILY

See https://help.inficonims.com/display/DW/Guide+to+Process+Families. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

TIME_TO_NEXT_MOVE

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)

IS_FULLY_LOADED

NUM_JOBS_LOADED

NUM_CARRIERS_RESERVED

NUM_CARRIERS_SCHEDULED

NUM_CARRIERS_COMPLETE

EST_NEXT_JOB_BEG_INST

NEXT_LOAD_LOT

NEXT_LOAD_CARRIER

IS_NEXT_LOAD_HIGHLIGHTED_PRTY

NEXT_LOAD_CURR_LOCATION

NEXT_LOAD_CURR_BAY

NEXT_LOAD_TIME

NEXT_UNLOAD_LOT

NEXT_UNLOAD_CARRIER

IS_NEXT_UNLOAD_HIGHLIGHT_PRTY

NEXT_UNLOAD_TIME

IS_NEXT_UNLOAD_READY

TIME_TO_EARLIEST_MOVE

STATE

STATE_COLOR

IS_AVAILABLE

TOOL_ID_COLOR

DECODE

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_FINISH

NEXT_LOT_TO_FINISH_CARRIER

NEXT_LOT_TO_FINISH_BEG_INST

NEXT_LOT_TO_FINISH_END_INST

NEXT_LOT_TO_FINISH_STATUS

NEXT_LOT_TO_FINISH_IS_COMPLETE

COORD_X

This is the x coordinate position of the location within its station, in other words horizontal position. The maximum coord_x is the width of the station. This is optional and is often used for racks and sometimes for carts so we can determine the exact position of the carrier to make it easier to find. (* inherited from FPSINPUT.MHS_RACK_LOCATIONS)

COORD_Y

This is the y coordinate position of the location within its station, in other words vertical position or shelf number. The maximum coord_y is the height of the station. This is optional and is often used for racks and sometimes for carts so we can determine the exact position of the carrier to make it easier to find. (* inherited from FPSINPUT.MHS_RACK_LOCATIONS)

IS_CRITICAL_IN_NMV

Used by NextMove to highlight critical tools in BayView. Ideally the client would update this column via ETL (* inherited from FPSINPUT.EQP_TOOLS)