FPSBASE.SCH_W_H_S_CARRIERS

AVAILABILITY

VARCHAR2(4)

BG_COLOR_HTML

VARCHAR2(7)

CARRIER

VARCHAR2(32)

N

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

CARRIER_CLASS

VARCHAR2(13)

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

CARRIER_FAMILY

VARCHAR2(64)

N

CARRIER_STATE

VARCHAR2(18)

Carrier state indicates the current state of the carrier. The value must be one of those defined by FPS in FPSADMIN.MHS_CARRIER_STATES. This is a very 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 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 would prefer one with state of OK then WARN but we could not choose one which was DOWN. (* from FPSINPUT.MHS_CARRIERS)

CLAIMED_BY

VARCHAR2(64)

CLAIMED_END

DATE

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_LOCATION

VARCHAR2(32)

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

CURR_STATION

VARCHAR2(32)

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

DURABLE_CAPACITY

NUMBER

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

IS_CLAIMED

CHAR(1)

IS_LOCATION_ASSUMED

CHAR(1)

used to store if making the location assumption

LOCATION_INST

DATE

used to store when the location info modified

MAX_BUILD_SEC_AHEAD

NUMBER

MIN_BUILD_SEC_AHEAD

NUMBER

RUN_ID

VARCHAR2(50)

N

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

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_START

DATE

The first start time for the durable to be used (* from FPSBASE.RTG_DURABLE_FUTURE_SCHED)

SCHED_STATE

VARCHAR2(7)

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