FPSAPP.WF_P_FLUSH

SHIFT

Name of shift must be unique and can be in any format as long as it is display friendly since this is what we show everywhere. We prefer that other tables should reference start_shift rather than shift in case we want to change the naming convention for the shift. (* inherited from FPSINPUT.CAL_SHIFTS)

START_SHIFT

Shifts can be of any length and it is important that all queries get the shift length based on start_shift and end_shift rather than assuming a set number of hours. (* inherited from FPSINPUT.CAL_SHIFTS)

START_PLAN_DAY

Plan days must be 24 hours in length and the start of the plan day must be the start of one of the shifts. Contrast this to plan day which is independent of shift. (* inherited from FPSINPUT.CAL_PLAN_DAYS)

CALENDAR_DAY

When we choose this day on a website calendar we will associate with work_days of this day. Typically this is the day of the start_day but not always. For example, start_day might be 17:00 and represent the following calendar_day. (* inherited from FPSINPUT.CAL_WORK_DAYS)

START_PLAN_WEEK

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

PLAN_WEEK

Name of plan week must be unique and can be in any format as long as it is display friendly since this is what we show everywhere. (* inherited from FPSINPUT.CAL_PLAN_WEEKS)

REPORT_INST

Date/time when the WIP Flush last updated. Obviously this is the same for all rows. (* inherited from FPSBASE.WIP_FLUSH)

LOT_ACTIVITY_INST

Date/time when the lot last had activity. (* inherited from FPSBASE.WIP_FLUSH)

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)

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)

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)

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)

FLUSH_SEQ_NUM

Flush sequence number is the order of main routes and banks for the lot from current to the final flushed product. 1 is always the current main route or bank. (* inherited from FPSBASE.WIP_FLUSH)

CURR_FACILITY

Current facility of the lot. (* inherited from FPSBASE.WIP_FLUSH)

CURR_FAC_BANK

Current bank of the lot (NA if lot is currently on a route). (* inherited from FPSBASE.WIP_FLUSH)

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)

EST_QTY_AT_EOL

The estimated quantity when the lot finishes the route/bank listed in units of the facility listed. The calculation is based on line yield from the current step to the end of the route/bank listed. So if the route/bank is in the future then the upcoming routes/banks starting with the current one are included since we expect those wafers to be lost between now and the end of the future route/bank listed. This does not include sort yield. (* inherited from FPSBASE.WIP_FLUSH)

CUSTOMER

Customer who will accept shipment of the lot. Currently this only used for grouping and filtering but in the future we might want to allow a customer to view a Dashboard only including their products. (* inherited from FPSINPUT.GEN_CUSTOMERS)

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)

PLANPRD_OUT

Planprd of final flushed product. See detailed comments and examples in table overview. (* inherited from FPSBASE.WIP_FLUSH)

ROUTE

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

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)

MAIN_ROUTE_GROUP

Route group of main route. Often referred to as technology. (* inherited from FPSBASE.WIP_FLUSH)

MAIN_ROUTE_FAMILY

Route family of the main route for the prd of the lot. (* inherited from FPSINPUT.WIP_OVR_OPER_MOVES_HIST)

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)

ENGR_COMMENT

Special comments made by engineering about this lot. These comments are about the lot in general and not about a specific step. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

PLAN_PRIORITY

Permanent priority of the lot set in the MES generally by planning. (* inherited from FPSINPUT.WIP_EVENT_HIST)

PRIORITY_DISPLAY

The name of the priority displayed on all dashboards and reports. Typically priority is short like P1, P2 so we allow a longer more descriptive name here that should be more familiar to the users. (* inherited from FPSINPUT.WIP_PRIORITIES)

PRIORITY_SORT

Unique sort of priority. Sort ascending gives the order from highest to lowest priority. Therefore the smallest number in priority_sort is the highest priority. (* inherited from FPSINPUT.WIP_PRIORITIES)

LOT_TYPE

Lot_type is the base of the hierarchy that determines lot_family then lot_group. Ideally lot_type will come straight from the MES with little modification. (* inherited from FPSINPUT.WIP_LOT_TYPES)

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)

LOT_GROUP_DISPLAY

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

ROUTE_SEGMENT

Route_segment allows for clear hierarchical segment organization for Segment Summary and Line Viewer on Dashboard. This is often referred to as stage and typically will come from the MES (as opposed to facility_segment which we will typically have to define for our purposes). We recommend that all routes in the same route family have the same route segments in the same order so that the Line Viewer by route family will be consistent but if this is not the case then we approximate the order as best we can. (* inherited from FPSINPUT.RTG_ROUTE_STEPS)

ROUTE_SEGMENT_SORT

FACILITY_SEGMENT

Facility segment is the parent of common step and is used as the highest level grouping when we show WIP for a route group or the entire facility where we cannot use route segment. We would prefer somewhere between 8 and 20 facility segments. Typically we will have to define these (as opposed to route_segment which we will typically come from the MES). There is no RTG_FACILITY_SEGMENTS table because sorting of facility segments is determined by common_step_sort. A trigger on RTG_COMMON_STEPS ensures that facility segments are contiguous when the entire facility is sorted by common step. (* inherited from FPSINPUT.RTG_COMMON_STEPS)

FACILITY_SEGMENT_SORT

ROUTE_SECTION

A large grouping of route steps used for line balance and should be set to contain at least a week of steps based on cycle time. Line balance uses this grouping instead of segment so that it can be configured independently from segment which is used in the Dashboard for display purposes, but they can also be set the same if desired. The section should be large in order to minimize the impact of short-term WIP distribution changes on step WIP targets because line balance calculates step WIP targets based on the WIP currently in each section. (* inherited from FPSINPUT.RTG_ROUTE_STEPS)

PROCESS_MODULE

WIP_MODULE is used to credit moves and set goals. See comments on the module column in GEN_MODULES for info on this column and how it relates to eqp_module and mnt_module. (* inherited from FPSBASE.RTG_ROUTE_STEPS_PLUS)

PROCESS_FAMILY

See https://help.inficonims.com/display/DW/Guide+to+Process+Families. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

NUM_STEPS_REMAINING

COMMON_STEP

A display-friendly field that groups similar steps together for purposes of viewing the entire line. Typically the only duplicates within a single route will be optional ordered steps in the same segment. But we will often have steps across routes that share the same common step even though exact step definition is not identical. (* inherited from FPSINPUT.RTG_COMMON_STEPS)

COMMON_STEP_SORT

How to sort common_step when displaying together for multiple routes in the same view. This must be unique for the entire facility so that we know how to order common_step when viewing the entire facility. (* inherited from FPSINPUT.RTG_COMMON_STEPS)

IS_HOLD

This field indicates the lot is on hold after the event is logged. In other words, this will always be Y if is_hold_start is Y and always N if is_hold_end is Y. (* inherited from FPSINPUT.WIP_EVENT_HIST)

STEP_ENT_INST

Time when the lot entered the step. (* inherited from FPSBASE.WIP_LOT_HIST)

CREATED_INST

Time when the lot was created, either lot start or split. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

CREATED_SORT

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

DUE_INST

To indicate the due date for this futuer start lot (* inherited from FPSINPUT.WIP_STARTS)

DAYS_TO_EOL_DUE

Days until the due date. This column is poorly named. (* inherited from FPSBASE.WIP_FLUSH)

START_PLAN_WK_DUE

Work week of due date according to CAL_WEEKS. (* inherited from FPSBASE.WIP_FLUSH)

PLAN_WEEK_DUE

EOL_INST_NOHOLD_FOR_WSF

DAYS_TO_EOL_NOHOLD_FOR_WSF

START_PLAN_WK_NOHOLD_FOR_WSF

PLAN_WEEK_NOHOLD_FOR_WSF

EOL_INST_FULL_WAVG

Date/time when the lot is estimated to finish the specified route/bank using weighted average cycle time from the Full period. (* inherited from FPSBASE.WIP_FLUSH)

DAYS_TO_EOL_FULL_WAVG

Days until the lot is estimated to finish the specified route/bank using weighted average cycle time from the Full period. (* inherited from FPSBASE.WIP_FLUSH)

START_PLAN_WK_FULL_WAVG

Work week when the lot is estimated to finish the specified route/bank using weighted average cycle time from the Full period according to CAL_WEEKS. (* inherited from FPSBASE.WIP_FLUSH)

PLAN_WEEK_FULL_WAVG

EOL_INST_LONG_WAVG

Date/time when the lot is estimated to finish the specified route/bank using weighted average cycle time from the Long period. (* inherited from FPSBASE.WIP_FLUSH)

DAYS_TO_EOL_LONG_WAVG

Days until the lot is estimated to finish the specified route/bank using weighted average cycle time from the Long period. (* inherited from FPSBASE.WIP_FLUSH)

START_PLAN_WK_LONG_WAVG

Work week when the lot is estimated to finish the specified route/bank using weighted average cycle time from the Long period according to CAL_WEEKS. (* inherited from FPSBASE.WIP_FLUSH)

PLAN_WEEK_LONG_WAVG

EOL_INST_7D_WAVG

Date/time when the lot is estimated to finish the specified route/bank using weighted average cycle time from the last 7 days. (* inherited from FPSBASE.WIP_FLUSH)

DAYS_TO_EOL_7D_WAVG

Days until the lot is estimated to finish the specified route/bank using weighted average cycle time from the last 7 days. (* inherited from FPSBASE.WIP_FLUSH)

START_PLAN_WK_7D_WAVG

Work week when the lot is estimated to finish the specified route/bank using weighted average cycle time from the last 7 days according to CAL_WEEKS. (* inherited from FPSBASE.WIP_FLUSH)

PLAN_WEEK_7D_WAVG

EOL_INST_7D_MED

Date/time when the lot is estimated to finish the specified route/bank using median cycle time from the last 7 days. (* inherited from FPSBASE.WIP_FLUSH)

DAYS_TO_EOL_7D_MED

Days until the lot is estimated to finish the specified route/bank using median cycle time from the last 7 days. (* inherited from FPSBASE.WIP_FLUSH)

START_PLAN_WK_7D_MED

Work week when the lot is estimated to finish the specified route/bank using median cycle time from the last 7 days according to CAL_WEEKS. (* inherited from FPSBASE.WIP_FLUSH)

PLAN_WEEK_7D_MED

EOL_INST_2D_WAVG

Date/time when the lot is estimated to finish the specified route/bank using weighted average cycle time from the last 2 days. (* inherited from FPSBASE.WIP_FLUSH)

DAYS_TO_EOL_2D_WAVG

Days until the lot is estimated to finish the specified route/bank using weighted average cycle time from the last 2 days. (* inherited from FPSBASE.WIP_FLUSH)

START_PLAN_WK_2D_WAVG

Work week when the lot is estimated to finish the specified route/bank using weighted average cycle time from the last 2 days according to CAL_WEEKS. (* inherited from FPSBASE.WIP_FLUSH)

PLAN_WEEK_2D_WAVG

EOL_INST_FIFO

Date/time when the lot is estimated to finish the specified route/bank using FIFO cycle time. (* inherited from FPSBASE.WIP_FLUSH)

DAYS_TO_EOL_FIFO

Days until the lot is estimated to finish the specified route/bank using FIFO cycle time. (* inherited from FPSBASE.WIP_FLUSH)

START_PLAN_WK_FIFO

Work week when the lot is estimated to finish the specified route/bank using FIFO cycle time according to CAL_WEEKS. (* inherited from FPSBASE.WIP_FLUSH)

PLAN_WEEK_FIFO

EOL_INST_TARGET

Date/time when the lot is estimated to finish the specified route/bank using Target cycle time. (* inherited from FPSBASE.WIP_FLUSH)

DAYS_TO_EOL_TARGET

Days until the lot is estimated to finish the specified route/bank using Target cycle time. (* inherited from FPSBASE.WIP_FLUSH)

START_PLAN_WK_TARGET

Work week when the lot is estimated to finish the specified route/bank using Target cycle time according to CAL_WEEKS. (* inherited from FPSBASE.WIP_FLUSH)

PLAN_WEEK_TARGET

EOL_INST_COMMIT

Date/time when the lot is estimated to finish the specified route/bank using Commit cycle time. (* inherited from FPSBASE.WIP_FLUSH)

DAYS_TO_EOL_COMMIT

Days until the lot is estimated to finish the specified route/bank using Commit cycle time. (* inherited from FPSBASE.WIP_FLUSH)

START_PLAN_WK_COMMIT

Work week when the lot is estimated to finish the specified route/bank using Commit cycle time according to CAL_WEEKS. (* inherited from FPSBASE.WIP_FLUSH)

PLAN_WEEK_COMMIT

PLAN_OUT_INST

Current planned out date for this lot in the current facility. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

DAYS_TO_EOL_PLAN_OUT

START_PLAN_WK_PLAN_OUT

PLAN_WEEK_PLAN_OUT

FAC_DEMAND_INST

DAYS_TO_FAC_DEMAND

START_PLAN_WK_FAC_DEMAND

PLAN_WEEK_FAC_DEMAND

OUT_DEMAND_INST

DAYS_TO_OUT_DEMAND

START_PLAN_WK_OUT_DEMAND

PLAN_WEEK_OUT_DEMAND