FPSAPP.SCH_C_CFG_SCHED_GROUPS

FACILITY

VARCHAR2(6)

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)

SCHED_GROUP

VARCHAR2(36)

This is the grouping of tools and processes which the FPS Scheduler schedules together. Since this is a parent of tool via tool->process_group and a parent of process via process->process_group, by definition each tool and each process can only be in one sched group. We need all related tools and processes to be in the same sched group for efficient scheduling. One example is sinks and furnaces because of queue times and batching. Another example is for smaller facilities like Assembly or Test where we might schedule the entire facility together. (* from FPSINPUT.RTG_PROCESS_GROUPS)

CONFIG_ID

VARCHAR2(50)

This is used to tell which configuration the current sched-group is using (* from FPSINPUT.RTG_SCHED_GROUPS)

BATCH_SIZE_WEIGHTS_AT_OPER

NUMBER(7,2)

the batch score weight applied to the percent of lots that are at the batching operation

BATCH_SIZE_WEIGHTS_COMING

NUMBER(7,2)

the batch weights for the lots will arrive after the process starting

BATCH_SIZE_WEIGHTS_CURRENT

NUMBER(7,2)

the batch weights for the current batched lots

BATCH_SIZE_WEIGHTS_FULL

NUMBER(7,2)

the batch score bonus points for scheduling a full batch - either max size or all lots in scheduler window

BATCH_SIZE_WEIGHTS_FUTURE

NUMBER(7,2)

the batch weights for the lots will arrive before process starting

CONFIG_BY

VARCHAR2(50)

CONFIG_DESC

VARCHAR2(500)

CONFIG_SEQ_NUM

NUMBER

CREATE_INST

DATE

DISPATCH_RULES

VARCHAR2(36)

used to define the order of dispatching: 0. timer lots, the timer lot at least needs to be nearby and in-danger 1. lot on tool; durable on tool 2. lot on tool; durable near tool (on tool or stocker) 3. lot near tool; durable on tool 4. lot near tool; durable near tool 5. lot on tool; 6. lot near tool; 7. sched-rank-1 lot, currently at the operation; 8. enable dispatch based on lot priority; for example, (1):(3):(2):(4) -> will dispatch 1 first and followed by 3 and then 2 and then 4; for example, (1):(2|3):(4) -> will dispatch 1 first and followed by (2 or 3) and then 4;

ENABLE_SCHED_ONLY_LOT_AT_OP

CHAR(1)

EXPIRED_QUEUE_TIMER_WEIGHT

NUMBER(7,2)

how much weight to give lots with expired timers for example: A weight of 0 -> expired timers will all get the same score of 20. for example: A weight of 1 -> expired timers will get an additional point for every hour they are late

FEEDBACK_EMAIL

VARCHAR2(512)

HOURS_TO_DISPLAY

NUMBER

WILL REMOVE SOON (* from FPSINPUT.RTG_SCHED_GROUPS)

HOURS_TO_SCHEDULE

NUMBER

This column is used to determine how many hours to look ahead and schedule the lots that might come into this area/SCHED-GROUP even it is still several steps away. (* from FPSINPUT.RTG_SCHED_GROUPS)

HOURS_TO_SCHEDULE_FIRST_STEP

NUMBER

to set the max hours to sched for the first step of each lot

HOURS_TO_SCHEDULE_MIN_BATCH

NUMBER(2)

HOURS_TO_SCHEDULE_TOOL_EVENT

NUMBER

to indicate how far in the future to include a tool_event. Any event that starts within current time + this value will be considered

IS_ACTIVE

CHAR(1)

Flag to enable or disable the tag condition. (* from FPSBASE.MSO_TAG_CONDITIONS)

LOGIN_RQD_FOR_PREVIOUS_RUNS

CHAR(1)

MIN_EST_SMP_PCT_TO_SCHED

NUMBER(7,2)

NUM_LOTS_TO_SCHEDULE_PER_LOOP

NUMBER

NUM_TOP_TOOL_ASGNS_TO_EVL

NUMBER(3)

to indicate the number of top tool assignments will be evaluated in the scheduler on the SCHED-GROUP. Default to 999, it means it will most likely to evaluate on every tool assignment

OTHER_NOTE

VARCHAR2(500)

Some description for this scheduler (* from FPSINPUT.RTG_SCHED_GROUPS)

RQD_PCT_TO_UPDATE_WSFS

NUMBER(2)

When less than this percentage of lot steps are evaluated/placed before timeout, the scheduler will not update WIP_STEP_FUTURE_SCHED data for the run. Note that this is not the percent of scheduled lots - only the percent evaluated. If this parameter is set to 70 and in a run all lot/steps are evaluated by 31 percent cannot be scheduled (due to tool assignment or other), then the scheduler will still update WIP_STEP_FUTURE_SCHED. This flag is primarily to prevent SLOW scheduler runs from clearing WIP_STEP_FUTURE_SCHED.

RSV_WEIGHTS_ON_NEXT_RQD_STEP

NUMBER(7,2)

to assign the points to the next required step if the current step is reserved/dispatched

SCORING_TIME_BASE

VARCHAR2(16)

the scoring time base is used to allow scheduler to calculate the time related points based on HOUR or DAY

SHOULD_SCHEDULE_FUTURE_STARTS

CHAR(1)

When set to N, the scheduler will not include future WIP from WIP_STARTS in the scheduler.

SHOULD_UPDATE_WSFS

CHAR(1)

When this value is set to N, the scheduler will not write lot schedule results back to WIP_STEP_FUTURE_SCHED. Results will only be written to the snapshot tables (e.g. SCH_W_H_S_LOTS). This can be useful during an initial deployment of a new scheduler where you do not want the results from a scheduler to impact step enter times for other schedules

SHOW_CARRIER_ID

VARCHAR2(50)

to set the visibility of a carrier id within a lot block in the Gantt chart. SHOW: Show the carrier id. HIDE: Hide the carrier id. SHOW_IF_DIFFERENT: Only show the carrier if it is different from the lot id

STEPS_TO_SCHEDULE

NUMBER

This column is used to determine how many steps to look ahead and schedule the lots that might come into this area/SCHED-GROUP even it is still several hours away. Between HOURS_TO_SCHEDULE and STEPS_TO_SCHEDULE, the Scheduler will try to schedule all the lots either will arrive within X hours OR within Y steps away. (* from FPSINPUT.RTG_SCHED_GROUPS)

STEP_ENTER_LOGISTIC_MIDPOINT

NUMBER(3,1)

The midpoint of the S-curve function for step enter time. After this many hours, the raw sore will equal 5 for the function.

STEP_ENTER_LOGISTIC_SLOPE

NUMBER(3,1)

The steepness of the S-curve function for step enter time. Larger numbers mean steeper curves - i.e. closer to a step function change.

TIMER_CRITICAL_FACTOR

NUMBER(4,1)

TIMER_HURRY_IN_HOURS

NUMBER(5,1)

is used to determine when x hours left on the timer, the scheduler should start to prioritize the lot

TIMER_HURRY_IN_PCT

NUMBER(3)

is used to determine when x % left on the timer, the scheduler should start to prioritize the lot

TIMER_TIME_SCHED_PCT

NUMBER(3)

is used to determine how conservative the timer should be in schedulder

USE_MPCT_STATE

CHAR(1)

USE_NEXT_STEP_LOC_ON_LINK_STEP

CHAR(1)

to indicate if it needs to use the location from the next step as primary location for the current step, for the link step

USE_NEXT_STEP_LOC_ON_TIMER

CHAR(1)

to indicate if it needs to use the location from the next step as primary location for the current step, for the timer lot

WEIGHT_FOR_FIRST_DISP_INST

NUMBER(4)

WEIGHT_FOR_KIT_TIME_POINTS

NUMBER(4)

WEIGHT_FOR_NUM_DURABLES_KITTED

NUMBER(4)

WEIGHT_FOR_POD_SELECTION

NUMBER(4)