FPSBASE.MHS_ALL_POSSIBLE_RACKS

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)

RACK

Rack is the parent of location and is where we ask to send the carrier. (* inherited from FPSINPUT.MHS_RACKS)

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)

CLEANUP_IF_FREE_LESS_THAN

If the free space at the rack (measured by total capacity of all locations minus carriers at all locations) is less than this number then we will move carriers away from this station to another storage location with more free space. If this value is 0 then we will never do this. (* inherited from FPSINPUT.MHS_RACKS)

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)

RACK_DISPLAY

Optional column to show a user friendly station name on the NextMove GUI which is different that the station name on the barcode. (* inherited from FPSINPUT.MHS_RACKS)

UNBLOCK_AFTER_ABORT

After a lot aborts processing it has the process state BLOCK and cannot be scheduled. This allows the operator to put on hold or send to rework or otherwise take the appropriate action. Normally this lasts for the period specified in wait_sec_to_sch_after_abort in GEN_FACILITIES. But at many sites if a lot arrives back in a stocker or on certain storage racks then it should no longer be blocked. This flag enables this behavior. It is set for each stocker or rack but most likely will be set to Y for all stockers and/or all input racks if this behavior is desired at the site. Any lot at a location with this flag set to Y will no longer be blocked after abort. Instead it will have process state of WAIT and will be available to schedule on any tool. (* inherited from FPSINPUT.MHS_STOCKERS)