FPSINPUT.MHS_POD_FAMILY_ASSIGNMENTS

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)

TOOL

VARCHAR2(16)

Tool is generally just the main tool. The exception is when different entities on the tool run completely independently and it is physically impossible to run wafers of the same lot across multiple entities. In this exception case, we may want to assign the entities to different eqp_types and therefore we should define each entity as a tool. Please note that when we do this there is no indication whatsoever that these different entities are on the same tool. (* from FPSINPUT.EQP_TOOLS)

POD_FAMILY

VARCHAR2(64)

This column is optional and only applies to pods/durables and not cassettes/lots. Certain durables must be stored in a specific group of pods and this is designated with this column. (* from FPSINPUT.MHS_CARRIERS)

CONSIDER_IN_POD_AS_ON_TOOL

CHAR(1)

When set to Y, the location of a durable in this pod will be considered to be the same as the tool for the pod family assignment, but only if the pod family is allowed for only one tool (i.e. dedicated pod family to tool.

EXTL_RANK

VARCHAR2(1)

Allowed values are P, F, W. For details on all EXTL columns please see Help Site page at https://help.finalphasesystems.com/display/SCHED/Scheduler+and+External+Model+Status. (* from FPSINPUT.RTG_TOOL_ASSIGNMENTS)

PERM_RANK

VARCHAR2(1)

N

Permanent rank is typically loaded by ETL from a combination of the MES, recipe management system, and existing preference logic already used at the site. Possible values are in FPSADMIN.RTG_PERM_RANKS. (* from FPSINPUT.RTG_TOOL_ASSIGNMENTS)

TEMP_RANK

VARCHAR2(1)

Temporary rank should only be set manually by a human user, never loaded automatically by ETL. Possible values are in FPSADMIN.RTG_PERM_RANKS. (* from FPSINPUT.RTG_TOOL_ASSIGNMENTS)