FPSBASE.SCH_P_RPT_DURABLES_TO_INSPECT

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_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)

DURABLE_UNAVAILABLE_TIME

DURABLE_REQUESTED_TIME

INSPECT_INFO

OTHER_INSPECT_INFO

CARRIER

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

DURABLE_CURR_LOCATION

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)

COUNTER_LEFT

the current available amount left of this counter (* inherited from FPSINPUT.RTG_PROCESS_COUNTERS)

NUM_REQUESTS

# of lots request to use this durable to process in the next 12 hours, based on step enter time (* inherited from FPSAPP.SCH_W_SCHED_DURABLE_INSPECT)

NUM_REQUESTS_PRTY

# of priority lots request to use this durable to process in the next 12 hours, based on step enter time (* inherited from FPSAPP.SCH_W_SCHED_DURABLE_INSPECT)

REQUEST_SUMMARY

SUGGESTED_INSPECTION_TIME

EARLIEST_REQUEST_TIME

EARLIEST_SCHED_START_TIME