FPSADMIN.ECT_SUMMARY_G4_FILLIN

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)

ROUTE_FAMILY

Route_family indicates that all routes within the family have similar or even identical steps and have the same segments. At facilities where various prds share the same route it is likely that the route will be the route_family. This is sometimes referred to as the main process flow. It is used on Segment Summary and Line Viewer to group similar routes. (* inherited from FPSINPUT.RTG_ROUTE_FAMILIES)

PROCESS_FAMILY

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

BANK

Lots which are not on a route are considered in a bank and the bank name indicates why the lot is off route. Bank must be NA for lots which are on a route. Our standard filter for active lots is bank = NA. (* inherited from FPSINPUT.RTG_BANKS)

LOT_GROUP

Lot_group is a grouping of lot_family and is the highest grouping in the lot type hierarchy. There should be only a few values for lot_group, i.e. Prod, Dev, TW. We group WIP and moves by lot_group on the dashboard and we group cycle time calculations by lot_group so this is an important field. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

PRTY_CTM_GROUP

This is one of the primary keys of our CTM tables. We use this group rather than the priority because we often have several different priorities which are close and are expected to have the same cycle time. (* inherited from FPSINPUT.WIP_PRIORITIES)

IS_NONSTD

Our column to indicate non-standard processing at the step. For example, an experiment or a chain that is only active at a particular step or set of steps and then goes back to being normal for the route. If an experiment is severe enough that it affects the final product and has to be planned separately then it will be its own prd or planprd. (* inherited from FPSBASE.WIP_LOT_HIST)

ABORT_WAVG_FULL_G4

BLOCK_WAVG_FULL_G4

DISP_WAVG_FULL_G4

LONGH_WAVG_FULL_G4

HOLD_WAVG_FULL_G4

ENDED_WAVG_FULL_G4

PROC_WAVG_FULL_G4

STG_WAVG_FULL_G4

WAIT1_WAVG_FULL_G4

WAIT2_WAVG_FULL_G4

WAIT3_WAVG_FULL_G4

RESRV_WAVG_FULL_G4

SHUTD_WAVG_FULL_G4

DOWN_WAVG_FULL_G4

ABORT_WAVG_LONG_G4

BLOCK_WAVG_LONG_G4

DISP_WAVG_LONG_G4

HOLD_WAVG_LONG_G4

LONGH_WAVG_LONG_G4

ENDED_WAVG_LONG_G4

PROC_WAVG_LONG_G4

STG_WAVG_LONG_G4

WAIT1_WAVG_LONG_G4

WAIT2_WAVG_LONG_G4

WAIT3_WAVG_LONG_G4

RESRV_WAVG_LONG_G4

SHUTD_WAVG_LONG_G4

DOWN_WAVG_LONG_G4

ABORT_WAVG_7D_G4

BLOCK_WAVG_7D_G4

DISP_WAVG_7D_G4

LONGH_WAVG_7D_G4

HOLD_WAVG_7D_G4

ENDED_WAVG_7D_G4

PROC_WAVG_7D_G4

STG_WAVG_7D_G4

WAIT1_WAVG_7D_G4

WAIT2_WAVG_7D_G4

WAIT3_WAVG_7D_G4

RESRV_WAVG_7D_G4

SHUTD_WAVG_7D_G4

DOWN_WAVG_7D_G4

ABORT_WAVG_2D_G4

BLOCK_WAVG_2D_G4

DISP_WAVG_2D_G4

LONGH_WAVG_2D_G4

HOLD_WAVG_2D_G4

ENDED_WAVG_2D_G4

PROC_WAVG_2D_G4

STG_WAVG_2D_G4

WAIT1_WAVG_2D_G4

WAIT2_WAVG_2D_G4

WAIT3_WAVG_2D_G4

RESRV_WAVG_2D_G4

SHUTD_WAVG_2D_G4

DOWN_WAVG_2D_G4

NUM_LOTS_MOVED_FULL

NUM_LOTS_MOVED_LONG

NUM_LOTS_MOVED_7D

NUM_LOTS_MOVED_2D