FPSADMIN.CTM_SUMMARY_TOTALS

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)

PRD

VARCHAR2(64)

N

Prd determines the route which is used to process the lot in the facility and what tools, recipes, durables, etc. can be used at each step. Prd also determines the next facility for the lot when it finishes its route. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* from FPSINPUT.RTG_PRDS)

BANK

VARCHAR2(36)

N

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

ROUTE

VARCHAR2(256)

N

Route that has threading requirements (* from FPSINPUT.RTG_STEP_THREADING)

PLANPRD

VARCHAR2(64)

N

Planning product used for all planning purposes. All lots with the same planprd are interchangeable to ship to the customer regardless of their prd, route, technology, wafer size, etc. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* from FPSINPUT.RTG_PLANPRDS)

PRTY_CTM_GROUP

VARCHAR2(7)

N

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

LOT_GROUP

VARCHAR2(8)

N

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

IS_NONSTD

CHAR(1)

N

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. (* from FPSBASE.WIP_LOT_HIST)

GROSS_DIE_PER_WFR

NUMBER(6)

Expected gross die per wafer for the product. This is a critical field for planning die shipments. Note this is gross so we multiply by line yield and by sort yield for remaining steps of remaining products. (* from FPSINPUT.RTG_PRDS)

INCLUDE_IN_PRD_AVG

CHAR(1)

IS_INCLUDED_WIP_FLUSH

CHAR(1)

If yes, then multi-facility WIP flush should include this LOT_GROUP when calculating weighted-average cycle time for future routes. (* from FPSINPUT.WIP_LOT_GROUPS)

IS_MAIN_ROUTE

CHAR(1)

Y indicates the route is the main processing route for PRD. N indicates it is a rework or alternate route. (* from FPSBASE.RTG_ACTIVE_PRD_ROUTES_BASE)

LOT_GROUP_SORT_ORDER

NUMBER(4)

N

MAIN_ROUTE_OF_PRD

VARCHAR2(256)

ROUTE_FAMILY

VARCHAR2(36)

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

ROUTE_GROUP

VARCHAR2(36)

Route_group is the parent of route_family. Route_group is used on the Dashboard and other applications as a large grouping for filtering. At many sites this is referred to as technology. (* from FPSINPUT.RTG_ROUTE_GROUPS)

TOTAL_AVG_WIP_FULL

NUMBER(12,3)

N

TOTAL_COMMIT_STEP_SEC

NUMBER(11)

N

TOTAL_FIFO_STEP_SEC

NUMBER(11)

N

TOTAL_LINE_YIELD_RATE

NUMBER(6,5)

N

TOTAL_QTY_COMP_FULL

NUMBER(12)

N

TOTAL_QTY_MOVED_2D

NUMBER(12)

N

TOTAL_QTY_MOVED_7D

NUMBER(12)

N

TOTAL_QTY_MOVED_FULL

NUMBER(12)

N

TOTAL_QTY_MOVED_LONG

NUMBER(12)

N

TOTAL_SORT_YIELD_RATE

NUMBER(6,5)

N

TOTAL_STEP_SEC_2D_WAVG

NUMBER(11)

N

TOTAL_STEP_SEC_7D_MED

NUMBER(11)

N

TOTAL_STEP_SEC_7D_WAVG

NUMBER(11)

N

TOTAL_STEP_SEC_FULL_WAVG

NUMBER(11)

N

TOTAL_STEP_SEC_LONG_WAVG

NUMBER(11)

N

TOTAL_STEP_SEC_NOHOLD_FOR_WSF

NUMBER(11)

N

TOTAL_TARGET_STEP_SEC

NUMBER(11)

N

WAFER_SIZE

VARCHAR2(8)

If the facility only has one wafer size then this column should be null in both RTG_PRDS and EQP_TYPES. If the facility has more than one wafer size then a value of null in EQP_TYPES means that those tools can run all wafer sizes. See column IS_ANY_WAFER_SIZE for details. (* from FPSINPUT.GEN_WAFER_SIZES)