FPSAPP.SCH_W_H_S_DURABLES

ASSIGNED_CARRIER_FAMILY

VARCHAR2(32)

CLAIMED_BY

VARCHAR2(64)

CLAIMED_CARRIER

VARCHAR2(32)

CLAIMED_END

DATE

CLAIMED_SLOT_NUM

NUMBER

CLAIMED_START

DATE

CLAIMED_TOOL

VARCHAR2(16)

CREATE_INST

DATE

CURR_BAY

VARCHAR2(12)

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

CURR_CARRIER

VARCHAR2(32)

CURR_LOCATION

VARCHAR2(32)

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

CURR_SLOT_NUM

NUMBER(2)

CURR_STATION

VARCHAR2(32)

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

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

DURABLE_AVAILABILITY

VARCHAR2(12)

DURABLE_FAMILY

VARCHAR2(64)

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_STATE_DISPLAY

VARCHAR2(128)

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

DURABLE_TYPE

VARCHAR2(72)

FACILITY

VARCHAR2(6)

N

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)

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

IS_CLAIMED

CHAR(1)

RUN_ID

VARCHAR2(50)

N

the run id from the last successful scheduler (* from FPSAPP.SCH_W_SCHED_GROUP_STATUS)

SCHED_CARRIER

VARCHAR2(32)

SCHED_GROUP

VARCHAR2(36)

N

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

SCHED_IS_RESERVED

CHAR(1)

SCHED_TOOL

VARCHAR2(16)

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

SHOULD_USE

CHAR(1)

This flag determines if the scheduler should use this data or not

WAIT_SEC_TO_SCHED

NUMBER

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