data-dictionary
data-dictionary
Breadcrumbs

FPSINPUT.CTM_COMPARE

Data Dictionary

>

FPSINPUT Views

> FPSINPUT.WIP_WAFER_HIST_LOOP

View FPSBASE.CTM_COMPARE

Summary of CTM and related info over entire routes and banks with selected examples representing various CTM cases. This should give us a good representation of the data in CTM_SUMMARY in a reasonable format to compare. For example, use the query below to compare the new logic of CTM_SUMMARY in this instance to the old logic of CTM_SUMMARY in the database at yourdblink to confirm the differences are as expected: with new as (select * from fpsbase.ctm_compare) select 'new' as which, facility, why_compare, prd, planprd, route, bank, prty_ctm_group, lot_group, total_avg_wip_full, sum_target_step_days, sum_commit_step_days, sum_step_full_wavg_days, sum_step_7d_wavg_days, sum_step_7d_med_days, sum_hold_7d_wavg_days, sum_nohold_wsf_days, avg_smp_pct_full, num_steps, never_skipped, rarely_skipped, often_skipped, always_skipped, is_nonstd, is_bank, is_tw, is_main_route, is_mostly_fillin from new union all select 'old' as which, facility, new.why_compare, prd, planprd, route, bank, prty_ctm_group, lot_group, c.total_avg_wip_full, c.sum_target_step_days, c.sum_commit_step_days, c.sum_step_full_wavg_days, c.sum_step_7d_wavg_days, c.sum_step_7d_med_days, c.sum_hold_7d_wavg_days, c.sum_nohold_wsf_days, c.avg_smp_pct_full, c.num_steps, c.never_skipped, c.rarely_skipped, c.often_skipped, c.always_skipped, is_nonstd, c.is_bank, c.is_tw, c.is_main_route, c.is_mostly_fillin from fpsbase.ctm_compare@yourdblink c join new using (facility, prd, planprd, route, bank, prty_ctm_group, lot_group, is_nonstd) order by 2, 3, 4, 5, 6, 7, 8, 9, which desc;

Column

Comment

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)

WHY_COMPARE

PRD

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

PLANPRD

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

ROUTE

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

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)

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)

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)

TOTAL_AVG_WIP_FULL

SUM_TARGET_STEP_DAYS

SUM_COMMIT_STEP_DAYS

SUM_STEP_FULL_WAVG_DAYS

SUM_STEP_7D_WAVG_DAYS

SUM_STEP_7D_MED_DAYS

SUM_HOLD_7D_WAVG_DAYS

SUM_NOHOLD_WSF_DAYS

AVG_SMP_PCT_FULL

NUM_STEPS

NEVER_SKIPPED

RARELY_SKIPPED

OFTEN_SKIPPED

ALWAYS_SKIPPED

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)

IS_BANK

IS_TW

Our standard filter to exclude test wafers is is_tw = N but what we really mean with this filter is to exclude any lots that do not add value for the facility. Lots which add value including sellable, development, and engineering and these lot groups should have is_tw set to N. Lots which do not add value are commonly grouped together and named "test wafers" which is why this flag is named is_tw. These include true test wafers like monitors and quals and dummies but also could include virtual lots used for training or testing, bare wafers, or really anything else including in the MES as a lot which does not add value. All of these lot groups should have is_tw set to Y. You could argue that the is_tw field might be more accurately named is_value or is_valuable or is_prod_eng_dev but is_tw is generally clear to most people. Plus it has the advantage that it is short which is nice given how frequently we use the is_tw = N filter. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

IS_MAIN_ROUTE

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

IS_MOSTLY_FILLIN