data-dictionary

FPSAPP.MHS_STOCKERS_PLUS

Data Dictionary

>

FPSAPP Views

> FPSAPP.WIP_WAFER_HIST_LOOP

View FPSBASE.MHS_STOCKERS_PLUS

A view to show all information about stockers. This view is more complex and slower than MHS_STOCKERS which is why we have both.

Column

Comment

MNT_FACILITY

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. (* inherited from FPSINPUT.MHS_STOCKERS)

STOCKER

Stocker is effectively similar to a rack except that it stores carriers internally and has input and output ports. (* inherited from FPSINPUT.MHS_STOCKERS)

DESCRIPTION

Tool desciption. This value is only used to display in the Dashboard. (* 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)

IS_AMHS

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

MNT_FAMILY

MNT_FAMILY is assigned to each EQP_TYPE. Tools in the same MNT_FAMILY are similar and share the same maintenance schedule. (* inherited from FPSINPUT.EQP_MNT_FAMILIES)

MNT_MODULE

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. (* inherited from FPSINPUT.EQP_MNT_FAMILIES)

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)

NUM_CASTS

CAST_PCT_FULL

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)

NUM_BARE_WFRS

BARE_WFR_PCT_FULL

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)

NUM_PODS

POD_PCT_FULL

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)

NUM_BARE_DRBLS

BARE_DRBL_PCT_FULL

EQP_STATE

Client equipment state taken directly from their MES or from their existing tool state model. For EQP_MNT_FUTURE, this is the state that we estimate the entity will be in during the maintenance which is often set to a generic PM state if we do not have detailed information. (* inherited from FPSINPUT.EQP_L6_DETAILED_STATES)

EQP_STATE_CHG_EVENT

Event that last changed the eqp_state. (* inherited from FPSBASE.ETP_STATUS)

EQP_STATE_CHG_INST

Time when the eqp_state changed for this particular entity. If another entity on the same main tool changes state, eqp_inst will change for all entities on the tool even those whose state does not change. Therefore if eqp_inst is after state_chg_inst that means another entity changed state at eqp_inst but this entity has not changed since state_chg_inst. (* inherited from FPSBASE.ETP_STATUS)

EQP_STATE_CHG_OPERATOR

Operator who logged the event that last changed the eqp_state. (* inherited from FPSBASE.ETP_STATUS)

EQP_STATE_CHG_COMMENT

Comment with the event that last changed the eqp_state. (* inherited from FPSBASE.ETP_STATUS)

AVAILABILITY

AVAIL_INST

Time when the availability last changed, either came up or went down. (* inherited from FPSBASE.ETP_STATUS)

MFG_GROUP

MFG_GROUP_INST

Time when the mfg_group last changed. (* inherited from FPSBASE.ETP_STATUS)

E10_STATE

E10_INST

DOWN_REASON

A value from a reasonably short list of user-defined reasons why the entity went down. (* inherited from FPSINPUT.EQP_EVENT_HIST)

REPAIR_REASON

These are the values that can be found in EQP_EVENT_HIST REPAIR_REASON. A value from a reasonably short list of user-defined explanations of how the entity will be repaired or what caused it to go down. (* inherited from FPSINPUT.EQP_REPAIR_REASONS)

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)

STOCKER_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_STOCKERS)

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)