FPSBASE.CTM_SUMMARY_WEEK_HIST

START_PLAN_WEEK

DATE

N

Plan weeks must be 7 days in duration and the start of the plan week must be the start of one of the plan days. (* from FPSINPUT.CAL_PLAN_WEEKS)

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)

ROUTE

VARCHAR2(256)

N

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

STEP

VARCHAR2(256)

N

A single processing step within a route representing a single tool visit. Step is often a very complex string and should rarely be displayed. Instead we should use process_display. (* from FPSINPUT.RTG_ROUTE_STEPS)

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)

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)

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)

COMMIT_QUEUE_SEC

NUMBER(7)

CTM_DATA_INST

DATE

EST_LINE_YIELD_PCT

NUMBER(6,3)

Estimated line yield percent for the route-step. Leave blank for the default of no loss expected. A value of 99.5 means we expected 1 unit out of 200 to be lost. (* from FPSINPUT.RTG_ROUTE_STEPS)

EST_SMP_PCT

NUMBER(5,2)

Smp_pct tells you what percentage of the lots complete on a tool. Some sites skip steps by jumping over them so we see the lot move from step 3 to step 5 and we only know that it jumped step 4 because step 4 is on the route between 3 and 5. Other sites skip steps by moving lots into them and then moving them out a second later so we see a move from 3 to 4 at 11:11:11 and a move from 4 to 5 at 11:11:12. We do not care how it is done but just that the lot did not process at step 4 -- and to be more specific that no tool capacity is required to process this lot at step 4 and no cycle time is accumulated at step 4. (* from FPSBASE.WIP_GOAL_LOT_SHIFT)

EXPECTED_Q_SEC_COMP

NUMBER(7)

FIFO_QUEUE_SEC

NUMBER(7)

HOLD_SEC_FOR_WSF

NUMBER(7)

IS_INACTIVE_STEP

CHAR(1)

Since we now use RTG_ROUTE_STEPS_INACTIVE table, we should only include the active steps on each route in RTG_ROUTE_STEPS. Therefore this value must be set to N in the RTG_ROUTE_STEPS table but will be set appropriately to Y for inactive steps in the RTG_ROUTE_STEPS_PLUS table. (* from FPSINPUT.RTG_ROUTE_STEPS)

PROC_SEC_FOR_EOL

NUMBER(7)

SEQ_NUM

NUMBER(7,2)

N

Sequence number of step in route (* from FPSINPUT.RTG_ROUTE_STEPS)

STEP_SEC_2D_WAVG

NUMBER(7)

STEP_SEC_7D_WAVG

NUMBER(7)

STEP_SEC_FULL_WAVG

NUMBER(7)

STEP_SEC_LONG_WAVG

NUMBER(7)

STEP_SEC_NOHOLD_FOR_WSF

NUMBER(7)

The FOR_WSF columns are used in populating WIP_STEP_FUTURE. This is based on the CTM_COLUMN_FOR_WIP_STEP_FUT column in GEN_FACILITIES. For example, if the value of that column is 7D_WAVG then we use the 7D_WAVG cycle times for WSF. (* from FPSBASE.CTM_SUMMARY)

TARGET_QUEUE_SEC

NUMBER(7)

TCT_SEC

NUMBER(7)

Theoretical cycle time in seconds (* from FPSBASE.WIP_LOT_HIST)

WHY_OTHERS_2D

NUMBER(3)

WHY_OTHERS_7D

NUMBER(3)

WHY_OTHERS_FULL

NUMBER(3)

WHY_OTHERS_LONG

NUMBER(3)

WHY_PROC_FULL

NUMBER(3)