FPSADMIN.SCH_P_CURR_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)

SCHED_GROUP

This is the grouping of tools and processes which the FPS Scheduler schedules together. Since this is a parent of tool via tool->process_group and a parent of process via process->process_group, by definition each tool and each process can only be in one sched group. We need all related tools and processes to be in the same sched group for efficient scheduling. One example is sinks and furnaces because of queue times and batching. Another example is for smaller facilities like Assembly or Test where we might schedule the entire facility together. (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)

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)

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_AVAILABILITY

WAIT_SEC_TO_SCHED

The lot may be scheduled but must not be allowed to dispatch or start until this number of seconds has elapsed. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

WAIT_SEC_TO_SCHED_PRTY

this is used to delay the schedule for the priority lots if it chooses delay_schedule as the wait_to_sched_method (* inherited from FPSINPUT.RTG_PROCESS_COUNTERS)

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)

CURR_CARRIER

CURR_SLOT_NUM

CURR_LOCATION

store the curr location of the lot (* inherited from FPSAPP.SCH_W_H_S_LOTS)

CURR_STATION

See column comment on STATION in FPSINPUT.MHS_STATION_ALTERNATES for more information. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

CURR_BAY

Current bay of carrier. See column comment on BAY in FPSINPUT.MHS_BAYS for more information. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

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)

ASSIGNED_CARRIER_FAMILY

DURABLE_TYPE

SCHED_TOOL

the tool from the first lot that scheduled (* inherited from FPSAPP.SCH_W_SCHED_DURABLE_INSPECT)

SCHED_CARRIER

SCHED_IS_RESERVED

CLAIMED_START

CLAIMED_END

CLAIMED_CARRIER

CLAIMED_SLOT_NUM

CLAIMED_TOOL

CLAIMED_BY

IS_CLAIMED