data-dictionary

FPSINPUT.NMV_P_STATIONS

Data Dictionary

>

FPSINPUT Views

> FPSINPUT.WIP_WAFER_HIST_LOOP

View FPSAPP.NMV_P_STATIONS

Stockers and racks data for NextMove.

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)

STATION

The rack, bay, building, tool, cart, or stocker which has alternately acceptable stations (* inherited from FPSINPUT.MHS_STATION_ALTERNATES)

STATION_TYPE

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)

DESCRIPTION

Tool desciption. This value is only used to display in the Dashboard. (* inherited from FPSINPUT.EQP_TOOLS)

IS_OUTPUT_FOR_BAY

This flag indicates if this rack qualifies as an output rack for the bay for NextMove. (* inherited from FPSINPUT.MHS_RACKS)

STATION_DISPLAY

REQUIRE_LOCATION_SCAN

This flag indicates if the rack requires a location scan (* inherited from FPSINPUT.MHS_RACKS)