FPSBASE.DASH_P_MHS_LOCATIONS

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)

LOCATION

Location of a carrier or lot or durable which comes directly from the tracking system used at the site. This could be a port or internal tool location or tool or rack or stocker or zero footprint storage or room or really anywhere. Many non-automated sites allow users to manually enter locations into their system. Therefore unless we know for sure that the source data implements a size limitation, it is recommended to always trim the value in the ETL to 32 characters to fit into the column size and avoid load errors. For ports, location is the full name of the port which is unique across the entire site and usually includes the tool name. Please see the comment in the port column which explains the difference between location and port. Rack locations are similar. (* inherited from FPSINPUT.MHS_RACK_LOCATIONS)

STATION

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

IS_AMHS

This field indicates if the stocker is part of the Automated Material Handling System. (* inherited from FPSINPUT.MHS_STOCKERS)

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)

CAST_CAPACITY

Maximum number of cassettes that can be stored. We define cassette as a carrier for a lot. (* inherited from FPSINPUT.MHS_RACK_LOCATIONS)

BARE_WFR_CAPACITY

Maximum number of bare wafers that can be stored. Bare wafers are lots which are not in a cassette. (* inherited from FPSINPUT.MHS_RACK_LOCATIONS)

POD_CAPACITY

Maximum number of pods that can be stored. We define pod as a carrier for a durable. (* inherited from FPSINPUT.MHS_RACK_LOCATIONS)

BARE_DRBL_CAPACITY

Maximum number of bare durables that can be stored. Bare durables are durables which are not in a pod. (* inherited from FPSINPUT.MHS_RACK_LOCATIONS)