FPSINPUT.GP_C_FACILITY

FACILITY

VARCHAR2(6)

N

Name of the facility to which these settings apply.

COMMENTS

VARCHAR2(200)

A comment field allowing a user to document the reason of the values populated in the table. Defaults is noted for the default value

DRUM_COMP_HIST_ROLL_HOURS

NUMBER(3)

Number of rolling hours to check for completes that will be compared to the drum target to determine a delta to target and corresponding priority. This value only applies if the DRUM_COMP_HIST_TYPE is set to ROLLING.

DRUM_COMP_HIST_ROLL_HOURS_LONG

NUMBER(3)

This is the same as DRUM_COMP_HIST_ROLL_HOURS except for a longer period of time. Setting both values allows tracking of both a short and long period, such as shift and day drum or day and week drum. Use of this longer period is optional. Step priority is given based on the following hierarchy: 1) Missing both long and short periods, 2) Missing the long period, Missing the short period.

DRUM_COMP_HIST_TYPE

VARCHAR2(8)

The type of historical calculation that will be done for comparing completes to the drum target to determine a delta to target and corresponding priority. Allowed values are SHIFT, PLAN DAY, and ROLLING. SHIFT is from the start of the current shift to date. PLAN DAY is from the start of the current plan day to date. ROLLING is a rolling number of hours as defined in DRUM_COMP_HIST_ROLL_HOURS.

DRUM_GROUPING

VARCHAR2(24)

Allowed values are "ROUTE STEP", "ROUTE FAMILY COMMON STEP", "ROUTE GROUP COMMON STEP", "COMMON STEP", "ROUTE FAMILY PROCESS", "ROUTE GROUP PROCESS", and "PROCESS". This determines the level at which the drum is aggregated. ROUTE STEP means the drum calculation is evaluated within each route for each step. COMMON STEP means the drum calculation is evaluated across routes for each COMMON STEP, assuming common steps are shared across routes. PROCESS means the drum calculation is evaluated across routes for each PROCESS, assuming processes are shared across routes.

DRUM_NORMALIZATION_GROUPING

VARCHAR2(32)

See comments on LB_NORMALIZATION_GROUPING. This field does the same thing for drum scoring

DRUM_NORMALIZATION_METHOD

VARCHAR2(24)

See comments on LB_NORMALIZATION_METHOD. This field does the same thing for drum scoring

LB_FUT_WIP_DELTA_CALC_TYPE

VARCHAR2(8)

Determines how future step WIP deltas are aggregated. Options are "SUM" and "WAVG". SUM means the straight sum is taken of the future step WIP deltas. WAVG means the weighted average of the future step WIP deltas is used.

LB_GROUPING

VARCHAR2(48)

Allowed values are "ROUTE STEP", "ROUTE FAMILY COMMON STEP", "ROUTE GROUP COMMON STEP", "COMMON STEP", "ROUTE FAMILY PROCESS", "ROUTE GROUP PROCESS", "PROCESS", "ROUTE FAMILY PROCESS FAMILY", "ROUTE GROUP PROCESS FAMILY", and "PROCESS FAMILY". This determines the level at which line balance is aggregated. ROUTE STEP means the line balance calculation is evaluated within each route for each step. COMMON STEP means the line balance calculation is evaluated across routes for each COMMON STEP, assuming common steps are shared across routes. PROCESS means the line balance calculation is evaluated across routes for each PROCESS, assuming processes are shared across routes. PROCESS_FAMILY means the line balance calculation is evaluated for each process relative to the process_families that are ahead. Normally a target WIP ratio is calculated for each route/step or process looking ahead at future route/steps or processes. When PROCESS_FAMILY is specified, the current target WIP ratio for the process is compared against the target WIP ratios for the future process_families, which includes processes that may be in different parts of the process flow. This setting can be used to slowdown the feed of WIP to process_families but may not result in balanced WIP across processes in the process flow.

LB_HORIZON_DAYS

NUMBER(3,1)

Line Balance horizon in days of cycle time. Controls how far downstream from each step, expressed in days of cycle time, the line balance calculation includes. This is treated as an OR condition in conjunction with LBR_HORIZON_NUM_STEPS.

LB_HORIZON_NUM_BLOCKS

NUMBER(2)

Line Balance horizon in number of line balance group units. Controls how far downstream from each step, expressed in number of blocks of line balance group, the line balance calculation includes. This is treated as an OR condition in conjunction with LBR_HORIZON_DAYS.

LB_NORMALIZATION_GROUPING

VARCHAR2(32)

This determines the grouping used to calculate the normalized line balance score. If set to facility then normalization is done across the facility. If set to route section or any other value then the normalization is done within the group which means there may be multiple max or min scores that represent different effective WIP deltas across the facility.

LB_NORMALIZATION_METHOD

VARCHAR2(24)

This determines the method used for normalization, which is either linear or logistic S-curve. Logistic creates greater seperation of scores that are closer to 0.

LB_QMODEL_MAX_XFACTOR

NUMBER(4,1)

The max X-factor that is allowed to be used when using the queueing model method to calculate target cycle time and corresponding WIP

LB_QMODEL_MIN_XFACTOR

NUMBER(4,1)

The min X-factor that is allowed to be used when using the queueing model method to calculate target cycle time and corresponding WIP

LB_QTIMER_START_STEP_PCT

NUMBER(3)

The percentage of target WIP that should be reallocated from steps in queue timers to the start step. If multiple timers overlap the WIP will be reallocated to the earliest start step.

LB_ROUTE_MIN_NUM_LOTS

NUMBER(3)

Filter for number of lots within a route for it to be considered within the line balance logic, helps with efficiency of computation as well as considering only main runners

LB_STEP_MIN_SMP_PCT

NUMBER(3)

Sets the minimum required sample rate to be considered in the line balance normalization calculation. Useful when metrology steps are dominating the line balance score.

LB_TARGET_BASIS

VARCHAR2(36)

Basis of determining line balance target distribution. Default is 1x process time from CTM_SUMMARY historical data, but can updated with TCT to use TCT_SEC instead.

LB_TARGET_METHOD

VARCHAR2(14)

Method of calculating the cycle time used to determine the ideal WIP distribution for the line balance WIP targets. 1X FACTOR means distribute the WIP based on the process time only. QUEUEING MODEL means distribute the WIP based on a target cycle time that is calculated using a queueing model. Note that the QUEUEING MODEL method relies heavily on the VARIATION_FACTOR set in EQP_TYPES.

LB_WIP_DELTA_WEIGHT_PCT_CURR

NUMBER(3)

The percentage of weight given to the current step WIP delta. This can be used to change the weighting of the WIP delta for the current step relative to future steps.

LB_WIP_DELTA_WEIGHT_PCT_FUT

NUMBER(3)

The percentage of weight given to the future step WIP deltas. This can be used to change the weighting of the WIP delta for the future steps relative to the current step.

MAX_CURR_QTY_DELTA

NUMBER(5)

MAX_FUTURE_QTY_DELTA

NUMBER(5)

MIN_CURR_QTY_DELTA

NUMBER(5)

MIN_FUTURE_QTY_DELTA

NUMBER(5)

USE_DRUM_DATA_FOR_GOALS

CHAR(1)

Flag indicating whether to use drum target completes and score data in shift and plan day goals for display on the Dashboard and elsewhere. A value of Y will cause us to ignore what is defined in FPSINPUT for Completes and Moves targets. Note that this does not take into account the DRUM_GROUPING, the route_step value is always used.