FPSAPP.THPT_P_SUMMARY_EQPTYPE

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)

EQP_TYPE

Each tool is assigned an EQP_TYPE and all tools in the same type are identical meaning that they should run at the same throughput when running the same process with the same chamber type count. We also expect similar availability since these tools are identical. However tools in the same EQP_TYPE may have different chamber configurations and may run different groups of processes. (* inherited from FPSINPUT.EQP_TYPES)

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)

EST_MACHINE_RECIPE

Estimated machine recipe what we estimate will be the machine recipe based on information from the Recipe Management System. It is used in combination with process for throughput calculations and setup change penalty calculations. It is not necessary to estimate for all processes since this is always used in combination however it needs to be NA rather than blank since it is part of the primary key of most THP tables. Hopefully when this is not NA it should match the actual machine recipe logged for each lot during processing. (* inherited from FPSINPUT.RTG_TOOL_ASSIGNMENTS)

CH_TYPE_CNT

This value is a summarizing of ch_used which we use for grouping of throughput. The assumption is that throughput will be the same if the same number of chambers of the same type are used. (* inherited from FPSINPUT.THP_EXTERNAL)

IS_PARALLEL_OTHER_CH

NOTE: Currently this is not set and is always N! This flag is for chamber tools where the job is running on some chambers while another job is running on entirely different chambers. For example, we expect a job on chambers AB to be faster running alone than when running in parallel with another job on chambers CD. (* inherited from FPSBASE.THP_TOOL_WEEK_HIST)

DURABLE_THP_VARIATION

When this column is populated that means that we have a choice of durable families and that processing time for the lot/recipe depends on which durable family is chosen. The most common use case is 8 pin and 16 pin probe cards. This will be blank for reticles and other cases where the throughput is not dependent on the durable. This is part of the primary key of our throughput logic where nulls are filled in as NA since PK columns cannot be null. In our first example, we have a recipe WAFER_TEST_1 that we use for a whole bunch of different prds. Each prd requires its own probe card but for throughput purposes we do not care about the prd. We just care about the recipe which is WAFER_TEST_1 and we would set duration_thp_variation to 8pin or 16pin. Then we would group all prds that use WAFER_TEST_1 and ran with an 8 pin probe card together in the same THP record. Our second example is similar to the first but for throughput purposes each prd will be different. We would set duration_thp_variation to the durable family for this case. In our third example, the recipe is different for each prd. In this case, we would set duration_thp_variation to either 8pin and 16pin or to the durable family and get the same result. (* inherited from FPSINPUT.RTG_DURABLE_FAMILIES)

IS_BATCH_THP

This is a critical value for throughput calculations. Throughput for batch tools is the same regardless of the qty in the batch. Throughput for non-batch tools varies based on the qty in the job. Usually this is Y when max_batch_size_carriers > 1 but not always. We can have tools who load multiple carriers together but whose throughput is calculated per unit. We can also have tools who load only single carriers but whose throughput is calculated per batch. (* inherited from FPSINPUT.EQP_TYPES)

WAFER_SIZE

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

WAFER_SIZE_DISPLAY

The name of the wafer_size displayed on all dashboards and reports. We allow a longer more descriptive name here although often this will be the same as the wafer_size. (* inherited from FPSINPUT.GEN_WAFER_SIZES)

NUM_JOBS

AVG_QTY_PER_JOB

IS_VALID

We consider a lot valid for our finished lot calculations when the lot moved through the first step and the last step on the main route for its product. There are some variations such as the lot moved through the first step on an older version of the route or finished with an event specifically marked as a ship event or the route did not have any steps. (* inherited from FPSBASE.ECT_FINISHED_LOT_HIST)

CALC_TYPE

CALC_TYPE_DISPLAY

INTERVAL_SEC_AUTO

INTERVAL_STD_DEV

IS_INTERVAL_VALID

NUM_WFR_INTERVALS

FIRST_UNIT_SEC_AUTO

FIRST_UNIT_STD_DEV

IS_FIRST_UNIT_VALID

ENDED_AVG_SEC

ENDED_STD_DEV

IS_ENDED_VALID

INTERVAL_SEC_TRUSTED

FIRST_UNIT_SEC_TRUSTED

USERNAME_TRUSTED

COMMENT_TRUSTED

RCP_BATCH_SHORT_MSG

RCP_BATCH_LONG_MSG

CASCADE_LENGTH_DISPLAY

CH_TYPE_FOR_THP_DISPLAY

EXP_CASCADE_BATCHES

Expected cascade batches is only for cascading batch tools. It is used in throughput calculations to determine how many batch_intervals to count after each first_unit_sec. If this is not populated we assume the batch tool does not cascade. This value could also be used in dispatching/scheduling to specify how many batches should be cascaded before a setup change is allowed. Historical data should be compared to this value regularly to verify it. (* inherited from FPSINPUT.EQP_TYPES)

MAX_BATCH_SIZE_CARRIERS

Maximum number of carriers which can be loaded together in a batch. This column must be populated and is used for ETP and for scheduling to determines whether the tool loads in batches. Non-batch tools will have a value of 1 and batch tools limited by units will be populated according to the comment in max_batch_size_units. This is not used for throughput calculation because we can have tools which load multiple carriers at once but whose throughput is calculated per unit. (* inherited from FPSINPUT.EQP_TYPES)

EXP_CASCADE_QTY

Expected number of wafers in a cascade is only for cascading tools which are not batch tools. It is used in throughput calculations to determine how many unit_intervals to count after each first_unit_sec. If this is not populated we use the exp_qty_per_carr_for_wph as the default meaning we cascade just one carrier. This value could also be used in dispatching/scheduling to specify how many wafers should be cascaded before a setup change is allowed. Historical data should be compared to this value regularly to verify it. (* inherited from FPSINPUT.EQP_TYPES)

FIXED_CARRIER_SEC

Seconds between units in two different carriers in additional to the normal unit interval. This time is added to the EET, MPU, and UPH. (* inherited from FPSINPUT.EQP_TYPES)

LOAD_SEC

For throughput purposes, we would like the begin event to be logged when the first wafer of the lot enters the tool so that we can accurately track theoretical cycle time (TCT) which starts at this point. If the tool logs as desired then this column will be 0 and it usually is. But some tools do not log the begin event until some amount of time later, for example after the pumping time. This column exists to account for this delay and it is the number of seconds from when the first wafer enters until the begin is logged. We simply add this time to the processing time to get the TCT. This is by eqp_type as we estimate that all recipes of all tools in the same eqp_type will be consistent in this behavior. Please note that unload_sec is similar for any time after the end event until the lot can be unloaded. (* inherited from FPSINPUT.EQP_TYPES)

UNLOAD_SEC

Seconds after the end is logged until the lot is available to be unloaded. This will often be 0. Unload_sec is added to the first_wafer_sec in throughput calculations. (* inherited from FPSINPUT.EQP_TYPES)

EXP_QTY_PER_JOB

If populated this value is used for the EET/TCT calculation for this eqp type instead of avg_qty_per_carr_for_wph which is the default for the facility. (* inherited from FPSINPUT.EQP_TYPES)

EXP_QTY_PER_BATCH

Expected wafers in a batch used in throughput calculations and for inc_batch_pct calculation. This value is required to be populated for batch tools. (* inherited from FPSINPUT.EQP_TYPES)

USE_ONLY_TRUSTED_FOR_THP_AVG

By default, the Auto MPU for each eqp_type shown on our Throughput Tracker is the weighted average of the automated calculated MPU for all processes. But the Auto-Trusted Delta compares the weighted average of the auto MPU only for processes where a trusted value is defined. Therefore if only selected processes have trusted values, we will show something confusing like Auto 7, Trusted 5, A-T Delta 1. If this flag is set then we will show the weighted average only for processes where a trusted value is defined to match the A-T Delta calculation. Then we will show Auto 6, Trusted 5, A-T Delta 1. (* inherited from FPSINPUT.GEN_FACILITIES)

HIDE_ON_THP_PAGE

Some eqp types we just simply do not care about their throughput so we can use this flag to hide them from our Throughput Tracker. (* inherited from FPSINPUT.EQP_TYPES)

ET_PRCS_EMR_CH_INT_CV

ET_PRCS_EMR_CH_FIRSTU_CV

ET_PRCS_EMR_CH_MPU_CV

ET_PRCS_NUM_JOBS

ET_PRCS_INT_CV

ET_PRCS_FIRSTU_CV

ET_PRCS_MPU_CV

ET_CV_NUM_JOBS_USED

ET_INT_CV

ET_FIRSTU_CV

ET_MPU_CV

MPU_AUTO

MPU_TRUSTED

MPU_LCL

Lower control limit for MPU used in our Throughput monitoring. Obviously this must be less than the manual MPU value. (* inherited from FPSINPUT.THP_MANUAL)

MPU_UCL

Upper control limit for MPU seconds used in our Throughput monitoring. Obviously this must be greater than the manual MPU value. (* inherited from FPSINPUT.THP_MANUAL)

UPH_AUTO

MPU_AUTO_FOR_TRUSTED

FIRST_UNIT_SEC_LCL

Lower control limit for first unit seconds used in our Throughput monitoring. Obviously this must be less than the manual first unit value. (* inherited from FPSINPUT.THP_MANUAL)

FIRST_UNIT_SEC_UCL

Upper control limit for first unit seconds used in our Throughput monitoring. Obviously this must be greater than the manual first unit value. (* inherited from FPSINPUT.THP_MANUAL)

INTERVAL_SEC_LCL

Lower control limit for interval seconds used in our Throughput monitoring. Obviously this must be less than the manual interval value. (* inherited from FPSINPUT.THP_MANUAL)

INTERVAL_SEC_UCL

Upper control limit for interval seconds used in our Throughput monitoring. Obviously this must be greater than the manual interval value. (* inherited from FPSINPUT.THP_MANUAL)

AUTO_TRUSTED_PCT_DIFF

IS_BEST_CTC_FOR_PRCS_RCP_ETYPE

WHY_INTERVAL

IS_AUTO_VALID

IS_MOST_COMMON_CH_TYPE_CNT

USE_FOR_PRCS_RCP_ETYPE