FPSBASE.SCH_P_ALL_DURABLES

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)

DURABLE

Durables are either reticles for Litho or probe cards for Wet or Sort. A durable can either be in a carrier or at a location without a carrier. (* inherited from FPSINPUT.RTG_DURABLES)

DURABLE_FAMILY

Durable_family indicates what durable is required by the process. When multiple durables are in a family any of them can be used. Typically there is only one reticle per family and therefore the durable and durable_family are the same. The exception would be a high running product with backup reticles. However for probe cards it is common to have several cards for each product so we have several durables with the same family. (* inherited from FPSINPUT.RTG_DURABLE_FAMILIES)

CARRIER

RFID of the cassette or FOUP the lot is currently in. (* inherited from FPSINPUT.MHS_CARRIERS)

CARRIER_CLASS

Carrier class indicates what the carrier is able to carry. It is also an important field in EQP_PORTS but each port has a single defined carrier class and only carriers of this class should go to the port. The value must be one of those defined by FPS in FPSADMIN.MHS_CARRIER_CLASSES which include POD or CAST or BOX. This would be used as a filter on what carriers could be selected when a carrier is needed. For example, when a lot is split we need to find another carrier for the split lot and we select the best carrier in the carrier_class of CAST. But if we need to unload a reticle then we select the best carrier in the carrier_class of POD. (* inherited from FPSINPUT.MHS_CARRIERS)

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)

LAST_KNOWN_LOCATION

Often when a carrier is in transit we do not know exactly where it is but we only know where it came from. In this case we might set the location to something generic like TRANSIT and the last known location to where it came from. (* inherited from FPSINPUT.MHS_CARRIERS)

DURABLE_STATE

Durable state indicates the current state of the durable The value must be one of those defined by FPS in FPSADMIN.MHS_CARRIER_STATES. This is a short list of simple states like OK or WARN or DOWN in contrast to the complex options available for equipment states. This would be used as a filter/sort on what durables could be used for scheduling. For example, if there are two durables in the durable_family and one is OK and the other is DOWN then we schedule using the OK durable. But if there is only one durable in the family then we cannot schedule any lots which require this family if that lone durable is DOWN. (* inherited from FPSINPUT.RTG_DURABLES)

DURABLE_STATE_DISPLAY

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

HOME_STATION

The optional home station of the vehicle or carrier is generally where it should be stored when not in use or the area in which it operates. (* inherited from FPSINPUT.RTG_DURABLES)

HOME_TOOL

The optional home tool of the durable is generally where it should return after maintenance or inspection or where we prefer to schedule its use (* inherited from FPSINPUT.RTG_DURABLES)

POD_FAMILY_RQD

Certain durables must be stored in a specific group of pods and this is designated with this column. (* inherited from FPSINPUT.RTG_DURABLES)

SLOT_NUM

The slot number the durable is occupying in its pod. This applies when a durable is stored in a pod that can hold multiple durables. (* inherited from FPSINPUT.RTG_DURABLES)