data-dictionary

FPSADMIN.MHS_ALL_POSSIBLE_VEHICLES

Data Dictionary

>

FPSADMIN Views

> FPSADMIN.WIP_WAFER_HIST_LOOP

View FPSBASE.MHS_ALL_POSSIBLE_VEHICLES

This view adds the appropriate facilities to MHS_VEHICLES for all uses where we want to filter on facility including Scheduler and 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)

VEHICLE

Field that uniquely identifies a vehicle. (* inherited from FPSINPUT.MHS_VEHICLES_TRACKING)

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)

HOME_BAY

Assign vehicle to a home bay for the normal place where the cart resides. If you assign a home bay, then the transit times for lots on the vehicle will be determined using the bay to bay matrix with the home bay as the from bay. (* inherited from FPSINPUT.MHS_VEHICLES)

IS_AMHS

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

IS_AUTO_SLOT_ASSIGNMENT

Y means automatically assign lot locations on carts. N means let the user assign the slot by scanning the lot then scanning the location. (* inherited from FPSINPUT.MHS_VEHICLES)

IS_LAST_LOC_UNLOAD

Y means the last activity for the vehicle was a load. N means it was an unload. (* inherited from FPSINPUT.MHS_VEHICLES_TRACKING)

LAST_LOCATION

Last location of vehicle is set by trigger based on the previous location of the carrier most recently loaded from/to the vehicle. (* inherited from FPSINPUT.MHS_VEHICLES_TRACKING)

LAST_LOCATION_INST

Time when the vehicle last loaded or unloaded a carrier. (* inherited from FPSINPUT.MHS_VEHICLES_TRACKING)

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)

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)

VEHICLE_DISPLAY

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

VEHICLE_ROUTE

A route that vehicles (carts) can take to pick up and drop off carriers around the site. (* inherited from FPSINPUT.MHS_VEHICLE_ROUTES)

VEHICLE_STATE

The state of the vehicle, which is typically used for determining whether it can be used or not. (* inherited from FPSINPUT.MHS_VEHICLES)

VEHICLE_STATE_DISPLAY

The name of the vehicle state displayed on all dashboards and reports. Vehicle_state must match the FPS list defined in MHS_VEHICLE_STATES but this display field might be formatted in a more familiar way to the users. (* inherited from FPSINPUT.MHS_VEHICLES)

VEHICLE_TYPE