FPSADMIN.CTR_B_FINISHED_BY_PERIOD

START_PERIOD

DATE

N

FACILITY

VARCHAR2(6)

N

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

PRD

VARCHAR2(64)

N

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

PLANPRD

VARCHAR2(64)

N

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

LOT_GROUP

VARCHAR2(8)

N

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

BANK1_SEC

NUMBER

BANK1_STDDEV

NUMBER

BANK2_SEC

NUMBER

BANK2_STDDEV

NUMBER

BANK3_SEC

NUMBER

BANK3_STDDEV

NUMBER

BANK4_SEC

NUMBER

BANK4_STDDEV

NUMBER

BANK5_SEC

NUMBER

BANK5_STDDEV

NUMBER

COMMIT_CT_DAYS

NUMBER

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

CTR_BANK1

VARCHAR2(36)

In Finished Lot Cycle Time we divide the time within a facility by process state like PROC, HOLD, etc. but for banks we can use these columns to have specific common banks be their own process state for this grouping. So rather than just seeing the average time in bank if we populate this with FAB-OUT then we can see the average time in the FAB-OUT bank separately. (* from FPSINPUT.GEN_FACILITIES)

CTR_BANK2

VARCHAR2(36)

See comment for CTR_BANK1. (* from FPSINPUT.GEN_FACILITIES)

CTR_BANK3

VARCHAR2(36)

See comment for CTR_BANK1. (* from FPSINPUT.GEN_FACILITIES)

CTR_BANK4

VARCHAR2(36)

See comment for CTR_BANK1. (* from FPSINPUT.GEN_FACILITIES)

CTR_BANK5

VARCHAR2(36)

See comment for CTR_BANK1. (* from FPSINPUT.GEN_FACILITIES)

END_PERIOD

DATE

FACILITY_COLOR

VARCHAR2(24)

FACILITY_DISPLAY

VARCHAR2(20)

The name of the facility displayed on all dashboards and reports. Facility is a short field since it is used in every join so we allow a longer more descriptive name here although often this will be the same as the facility. (* from FPSINPUT.GEN_FACILITIES)

FACILITY_HTML_COLOR

VARCHAR2(7)

FACILITY_SORT_ORDER

NUMBER(4)

FAC_INCL_BANK_SEC

NUMBER

FAC_INCL_BANK_STDDEV

NUMBER

FINISHED_PERIOD

VARCHAR2(7)

NUM_LOTS

NUMBER

NUM_PHOTO_LAYERS

NUMBER(3)

OTH_BANK_SEC

NUMBER

OTH_BANK_STDDEV

NUMBER

OVR_PROC_CT_DAYS_FOR_FLCT_XF

NUMBER(5,1)

Some sites prefer to use a fixed number for the processing time of each prd in the denominator of their X-Factor calculation. The FLCT app will use this value if populated in the X-Factor calculation instead of the calculation processing time. For sites which combine prd in the same facility to report a sequence of prds in FLCT, this value must be populated for the last prd in the same sequence but it should have the value of the total processing time for all prds in the sequence. (* from FPSINPUT.RTG_PRDS)

PERIOD_SORT_ORDER

NUMBER

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

PERIOD_TYPE

VARCHAR2(12)

PRD_MAX_SERIES_SEQ

NUMBER(1)

QTY

NUMBER

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

QTY_UNIT

VARCHAR2(12)

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

QTY_UNIT_PLURAL

VARCHAR2(12)

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

ROUTE

VARCHAR2(256)

N

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

ROUTE_FAMILY

VARCHAR2(36)

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

ROUTE_GROUP

VARCHAR2(36)

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

STEP_BLOCK_SEC

NUMBER

STEP_BLOCK_STDDEV

NUMBER

STEP_DISP_SEC

NUMBER

STEP_DISP_STDDEV

NUMBER

STEP_DOWN_SEC

NUMBER

STEP_DOWN_STDDEV

NUMBER

STEP_ENDED_SEC

NUMBER

STEP_ENDED_STDDEV

NUMBER

STEP_HOLD_SEC

NUMBER

STEP_HOLD_STDDEV

NUMBER

STEP_PROC_SEC

NUMBER

STEP_PROC_STDDEV

NUMBER

STEP_SHUTD_SEC

NUMBER

STEP_SHUTD_STDDEV

NUMBER

STEP_WAIT_SEC

NUMBER

STEP_WAIT_STDDEV

NUMBER

TARGET_CT_DAYS

NUMBER

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

WAFER_SIZE

VARCHAR2(8)

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