data-dictionary

FPSINPUT.BLD_VS_PROC_CT_BY_STEP

Data Dictionary

>

FPSINPUT Views

> FPSINPUT.WIP_WAFER_HIST_LOOP

View FPSADMIN.BLD_VS_PROC_CT_BY_STEP

This view is a drilldown of BLD_VS_PROC_CT_BY_ROUTE for each step. It compares the cycle time from the old WIP_STEP_HIST -> WIP_END_SHIFT_HIST -> CTM_SUMMARY method against the new ECT_HIST -> ECT_xxx_7D_2D_CW -> ECT_SUMMARY method. It is critical to choose a set of filters that return only one set of records from CTM_SUMMARY. By one set, I mean an entire prd but just one record for each step. In other words, this should filter by the primary key except for step. To use this, just find/replace for FFF, PPP, and GGG plus 'Prod' if your production lot_group is not Prod.

Column

Comment

SEQ_NUM

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

PROCESS

Process defines what occurs at a step. Different steps can share the same process if they are identical. Process should normally determine allowed tools and recipe although it can be overridden by step, route, prd, lot, and experiment for exceptions. Each process is dynamically assigned to one or more eqp_type-process_family combinations with use_pct. One process_family is determined to be primary. If grouping is done correctly, a process should only be one eqp_group with no crossover. (* inherited from FPSINPUT.RTG_PROCESSES)

TCT_HRS

PROC_HRS_D

PROC_HRS_ECT

3600

DELTA_HRS_TO_TCT

3600

DELTA_HRS_TO_ECT

TOTAL_D_HRS

TOTAL_ECT_HRS

TOTAL_TCT_HRS

TOTAL_DELTA_ECT_HRS

QTY_COMP_2D_D

QTY_COMP_2D_ECT

D_DATA_INST

ECT_DATA_INST

STEP

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