data-dictionary

FPSBASE.RTG_DURABLES

Data Dictionary

>

FPSBASE Tables

> FPSBASE.RTG_DURABLES

Table FPSBASE.RTG_DURABLES"

Detailed information about each 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.

  • Schema: FPSBASE

  • Tablespace: FPSDATA


Column

Type

Nullable

Comment

FACILITY

VARCHAR2(6)

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

DURABLE

VARCHAR2(64)

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.

CARRIER

VARCHAR2(32)

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

CARR_CATEGORY_RQD

VARCHAR2(17)

Required carrier category which if set must match carr_category in MHS_CARRIERS

DURABLE_FAMILY

VARCHAR2(64)

N

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

DURABLE_PARM1

VARCHAR2(128)

User-defined parameter which can store any value relevant to the durable. Description of use should be noted in the RTG_DURABLES ETL.

DURABLE_STATE

VARCHAR2(36)

N

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.

DURABLE_STATE_DISPLAY

VARCHAR2(128)

N

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.

HOME_STATION

VARCHAR2(32)

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.

HOME_TOOL

VARCHAR2(16)

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

POD_FAMILY_RQD

VARCHAR2(64)

Certain durables must be stored in a specific group of pods and this is designated with this column.

SLOT_NUM

NUMBER(2)

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.