FPSBASE.RTG_REF_PROCESS_FAMILIES_PLUS

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)

PROCESS_FAMILY

See https://help.inficonims.com/display/DW/Guide+to+Process+Families. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

MODULE

Modules are departments of people who manage certain areas of the fab. The modules are assigned ownership of a set of tools to operate and maintain as well as steps on the route that they are responsible for executing. Since many of our tables include tool and step information together, we must distinguish between the owner of the step (WIP_MODULE), the owner of the operation of the tool (EQP_MODULE), and the owner of the maintenance of the tool (MNT_MODULE). WIP_MODULE is used to credit moves and set goals. Each route-step is assigned to a process family and then its wip_module is defined by the process family. EQP_MODULE is used to group tools particularly for tool performance reporting. Similar to WIP, each tool is dynamically assigned to a process family based on its assignments and then its eqp_module is defined by the process family. MNT_MODULE is usually the same as EQP_MODULE but unlike EQP_MODULE is not dependent on assignments but only on the EQP hierarchy. Each tool is assigned to an eqp_type and each eqp_type is assigned to a mnt_family and each mnt_family is assigned to a mnt_module. (* inherited from FPSINPUT.GEN_MODULES)

MODULE_DISPLAY

The name of the module displayed on all dashboards and reports. We allow a longer more descriptive name here although often this will be the same as the module. (* inherited from FPSINPUT.GEN_MODULES)

PROCESS_CLASS

Top-level grouping of process groups with same general purpose (i.e. Process or Metrology or Nonwafer). Allowed values are defined by FPS and are listed in FPSADMIN.RTG_PROCESS_CLASSES. This field can also be defined in EQP_TOOLS using the ovr_process_class field if we do not know it for the process group. (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)

NUM_TOOLS_UP

NUM_TOOLS_DOWN

NUM_TOOLS_NST

NUM_TOOLS_UP_MAQT

NUM_TOOLS_DOWN_MAQT

OVR_UTIL_OF_AVAIL_FOR_MAQT

This is the override value used in the multi area queue timer wip ETL (RTG_REF_QUEUE_MULTI_AREA_WIP) for the utilization of availability used in determining the % of the available tools in the timer to process the WIP. If left null, the ETL will use the plan avail * plan util. This was created as the plan avail and plan util columns are used for the Dashboard targets on the tool state history charts and some clients want to use non target values for the queue timer evaluation. (* inherited from FPSINPUT.EQP_TYPES)

UTIL_OF_AVAIL

AVG_SECONDS_UNTIL_UP

DEFAULT_QTY_MEAS

Default number of wafers measured in a lot on the tool in the family. This is used if the number of wafers measured is not specified for a particular lot. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

IS_CTM_CALC_BY_PROCESS

Flag indicating whether we calculate planned queue cycle time by process instead of by eqp_family (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

OVR_ADD_TO_GP_CUTOFF_MINS

Override the default Goal Planner add to cutoff minutes from GEN_FACILITIES (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

MIN_STEP_SEC

See MAX_STEP_SEC comment. This minimum limit should rarely be used. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

MAX_STEP_SEC

This is a cap on the cycle time for steps in this process family. The most common use is for a process family which has historically been bad but we do not want the cycle time to show that. We hesitated on capping the historical numbers and prefer to only cap commit and target but we somewhat reluctantly agreed to cap history too. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

DEFAULT_STEP_SEC

This is used as the default for the process family in the fillin logic in CTM_SUMMARY. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

IGNORE_BNS

If set to Y the bottleneck score will always be 999 so it will be a the bottom of the list. Note that we normally use pace for families with no tools therefore this should generally be set only for families which we do not care about whatsoever. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

USE_SETUP_AS_SUBFAMILY

USE_DUR_FAM_AS_SUBFAMILY

Using durable family is the third of three ways to set process_subfamily. If set to Y then the durable_family from RTG_DURABLE_ASSIGNMENTS will be the process_subfamily as long as ovr_process_subfamily is not populated. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

MIN_PROC_TIME_SEC

Normally we ignore process times less than 60 seconds when calculating throughput to avoid the dreaded case when the operator logs begin and end together. However some tools actually process jobs in less than 60 seconds so we need to override this with a smaller number. If desired we could also override with a larger number. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

MAX_PROC_TIME_SEC

We typically have decent logic to ignore certain cases and only take 10-50% but this is another way to eliminate bad data. We do not recommend setting this unless you investigate certain cases of throughput oddities and decide there is no other method. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

MIN_QTY_FOR_BNS

Minimum current WIP quantity required for a bottleneck score to be calculated. If the current WIP quantity is below this number then the bottleneck score will be set to 999. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

USE_COMING_HOLD_WIP_IN_BNS

Column controls if HOLD wip not at the current operation will be included in the BNS. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

USE_CURR_HOLD_WIP_IN_BNS

Column controls if HOLD wip at the current operation will be included in the BNS. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

OVR_MIN_GOAL_COMP_FOR_BNS

Override the default minimum goal completes when calculating bottleneck score. An adjusted goal less than this number will show a BNS = 100. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

IS_KEY_ON_FACILITY_DASH

Should be set for less than 5 of the most critical process families in the facility to keep them always displayed on the facility page in the Key Process Families section. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

IS_KEY_ON_MODULE_DASH

Should be set for less than 5 of the most critical process families in the module to keep them always displayed on the module page in the Key Process Families section. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

IS_EXEMPT_FROM_TOP_ON_DASH

Normally we sort process familiies by Bottleneck Score or WIP but there are some facilities, usually logistics or sometimes metrology, that we do not want to show on the top even when the Score indicates they should be. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

SORT_ORDER

This is used to sort within the grouping. SORT_ORDER always has a deferrable unique key to ensure uniqueness while allowing the user to make changes without erroring until the commit is attempted. Because of this you must be careful to not violate the unique key otherwise you will lose all of your edits. (* inherited from FPSINPUT.GEN_FACILITIES)

AVG_UPH

AVG_UPH_DAY

HOURS_TO_DRAIN_WIP

BOTTLENECK_SCORE

BOTTLENECK_SCORE_HOVER_MSG

DAY_BNS

DAY_BNS_HOVER_MSG