Data Dictionary
>
FPSAPP Tables
> FPSAPP.MHS_STOCKERS
Table FPSAPP.MHS_STOCKERS"
List of stockers where carriers can be stored.
-
Schema: FPSAPP
-
Tablespace: FPSDATA
-
Referenced by: FPSINPUT.MHS_STOCKER_PORTS (STOCKER)
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
STOCKER |
VARCHAR2(16) |
Stocker is effectively similar to a rack except that it stores carriers internally and has input and output ports. |
|
|
BARE_DRBL_CAPACITY |
NUMBER(4) |
Maximum number of bare durables that can be stored. Bare durables are durables which are not in a pod. (* from FPSINPUT.MHS_RACK_LOCATIONS) |
|
|
BARE_WFR_CAPACITY |
NUMBER(4) |
Maximum number of bare wafers that can be stored. Bare wafers are lots which are not in a cassette. (* from FPSINPUT.MHS_RACK_LOCATIONS) |
|
|
BAY |
VARCHAR2(12) |
N |
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. (* from FPSINPUT.MHS_BAYS) |
|
CAST_CAPACITY |
NUMBER(3) |
Maximum number of cassettes that can be stored. We define cassette as a carrier for a lot. (* from FPSINPUT.MHS_RACK_LOCATIONS) |
|
|
DESCRIPTION |
VARCHAR2(256) |
Tool desciption. This value is only used to display in the Dashboard. (* from FPSINPUT.EQP_TOOLS) |
|
|
IS_AMHS |
CHAR(1) |
This field indicates if the stocker is part of the Automated Material Handling System. |
|
|
IS_OUTPUT_FOR_BAY |
CHAR(1) |
This flag indicates if this rack qualifies as an output rack for the bay for NextMove. (* from FPSINPUT.MHS_RACKS) |
|
|
MNT_FACILITY |
VARCHAR2(6) |
Stockers and vehicles are locations but they are also maintenance entities. Location is independent of facility so the mnt_facility is not relevant as far as location. But maintenance entities needed a facility and this mnt_facility column is used exclusively for that purpose. |
|
|
MNT_FAMILY |
VARCHAR2(50) |
MNT_FAMILY is assigned to each EQP_TYPE. Tools in the same MNT_FAMILY are similar and share the same maintenance schedule. (* from FPSINPUT.EQP_MNT_FAMILIES) |
|
|
MNT_MODULE |
VARCHAR2(12) |
MNT_MODULE is the module responsible for maintaining the tool and is a property of MNT_FAMILY. See comments on the module column in GEN_MODULES for how it relates to eqp_module and mnt_module. (* from FPSINPUT.EQP_MNT_FAMILIES) |
|
|
POD_CAPACITY |
NUMBER(3) |
Maximum number of pods that can be stored. We define pod as a carrier for a durable. (* from FPSINPUT.MHS_RACK_LOCATIONS) |
|
|
STOCKER_DISPLAY |
VARCHAR2(32) |
N |
Optional column to show a user friendly station name on the NextMove GUI which is different that the station name on the barcode. |
|
UNBLOCK_AFTER_ABORT |
CHAR(1) |
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. |