FPSINPUT.ECTFL_P_H_FINISHED_PROC_STATE

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)

LOT

A lot is a group of units that process together. Usually lot_id or lot_number in MES. All units in a lot are in the same carrier but there may be multiple lots in a carrier. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

QTY

Quantity of units in the lot according the qty_unit defined for the facility. It is required for all lots in each facility to have their qty defined in the same units therefore the change in the unit is critical to defining the facility. For example, a pretest facility might have a sort step in the middle where we learn the qty of die. Prior to this step we know only the wafer qty but after this step we know both wafer and die. Since wafer is the only qty we know throughput the flow then wafer must be defined as the qty unit for this facility. Die can then be populated as sec_qty when it is known. Similarly the wafer saw facility might have a step in the middle where we cut the wafers into die. After this step we no longer know the number of wafers which means that die must be the qty unit for this facility and wafers can be the sec_qty prior to the saw step. Please note that a lot with qty of 0 is allowed but only if the sec_qty is greater than 0. This is unusual but one case is where we know the wafers will be scrapped but cannot be scrapped quite yet. (* inherited from FPSINPUT.WIP_EVENT_HIST)

START_INST

Time when the lot started. (* inherited from FPSINPUT.WIP_STARTS)

FINISHED_INST

FIRST_STEP_ENT_INST

SECONDS

PROCESS_STATE

Process state is the most commonly used level of our Enhanced Cycle Time hierarchy. This displays on Dashboard, Scheduler, Cycle Time Analyzer, and Finished Lot Cycle Time Reporter. Process state is the parent of ECT state, however, there is configuration for when to show the process state of Reserved in each application which is done in WIP_ECT_STATES. (* inherited from FPSADMIN.WIP_PROCESS_STATES)

PROCESS_STATE_DISPLAY

BG_HTML_COLOR

SORT_ORDER

This is used to sort within the grouping. SORT_ORDER always has a deferrable unique key to ensure uniqueness while allowing the user to make changes without erroring until the commit is attempted. Because of this you must be careful to not violate the unique key otherwise you will lose all of your edits. (* inherited from FPSINPUT.GEN_FACILITIES)

QTY_UNIT

Defines the unit used to measure number of quantity. The key here is that this quantity must be known throughout the entire route through the facility. For example in a sort facility where lots enter in wafers and are broken into die but the number of wafers is still known when the lot completes the facility then the qty_unit must be wafer. It cannot be die because die is not known when the lot enters so die will be the sec_qty_unit. Similarly at a final test facility where the lots enter with both wafers and die known but only die are known when the lot completes the facility then the qty_unit must be die. It cannot be wafer because wafer is not known when the lot completes so wafer will be the sec_qty_unit. Please note the entire process from only wafers to only die must be split into at least two facilities because of this requirement. (* inherited from FPSINPUT.GEN_FACILITIES)

QTY_UNIT_PLURAL

Plural form of the quantity unit. For example if qty_unit is defined as wafer then the plural form would be wafers. (* inherited from FPSINPUT.GEN_FACILITIES)

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)

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)

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)

ROUTE_FAMILY

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

ROUTE_GROUP

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

COMMIT_CT_DAYS

Number of days of cycle time committed to the customer for the prd or bank. This commit is published externally. This should be greater than or equal to the target. (* inherited from FPSINPUT.RTG_BANKS)

TARGET_CT_DAYS

Number of days of cycle time targeted for the prd or bank. This target is only published internally which often means it is not even published to corporate planning. This should be less than or equal to the commit. (* inherited from FPSINPUT.RTG_BANKS)

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)

NUM_STEPS_COMP

PERIOD_SORT_ORDER

This column is only to sort the periods in the FLCT application. Normally this will match the period_start_inst but when sites has multiple period types like months and years then it is nice to be able to control the sort order. (* inherited from FPSINPUT.WIP_CTM_FORECAST)

FINISHED_PERIOD

PERIOD_TYPE

START_PERIOD

END_PERIOD

NUM_PHOTO_LAYERS

SEC_WAVG