FPSAPP.RTG_QUEUE_TIMERS_ALL_STEPS

TIMER_ID

Unique number representing the queue timer to index with other tables. Automatically populated with RTG_QUEUE_TIMERS_ID_SEQ sequence. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

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)

ROUTE

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

START_STEP

Start step that will impact the future thread step rank in RTG_TOOL_ASSIGNMENT_LOT (* inherited from FPSINPUT.RTG_STEP_THREADING)

END_STEP

The step upon move out where the WIP balance limit is no longer applied (* inherited from FPSINPUT.RTG_STEP_BALANCE)

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)

WARN_SEC

Seconds from the start event until warning limit for queue time restriction. Lots that remain in the timer sequence longer than this warning limit should be prioritized to prevent them from expiring. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

EXPIRED_SEC

Seconds from the start event until queue time restriction is expired. After expiration, the lot must rework or scrap or otherwise be evaluated. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

EXPIRED_PULL_SEC

MIN_WAIT_SEC

All lots must wait at least this many seconds at the step before processing. This column is the opposite of the others and can only be populated if the others are null. Also start_step and end_step must be the same since this can only apply at a single step. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

FEED_IF_LESS_THAN_SEC

If WIP in the queue sequence as measured by total seconds of EET is below this number then we should prioritize lots entering the sequence. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

TIMER_START_EVENT

The WIP event type which starts the queue timer at the start step. The default and preferred choice is END since most timers should start when the lot ends processing at the start step but other choices are DISPATCH, BEGIN, and COMP. These four choices are a subset of list in WIP_EVENT_TYPES. This column would be more accurately named TIMER_START_EVENT_TYPE but this is in use everywhere and changing ETL makes upgrades significantly more difficult so we are leaving this slightly confusing column name. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

TIMER_END_EVENT

The WIP event type which ends the queue timer at the end step. Prior to Scheduler version 1.18.1, the only choice is BEGIN so all timers will end when the lot starts processing at the end step. For 1.18.1+, DISPATCH, BEGIN, END, and COMP are all available options. Please note that scheduling timers that end on COMP and END events is much more difficult, as many factors can introduce significant variability to the processing time of a lot. DISPATCH and BEGIN are the preferred event types to use here. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

RWK_IF_EXPIRED

Indicates whether rework is required after queue timer expires. If allowed, we need to specify the route and step that we expect the lot to move into for rework. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

RWK_ROUTE

If the queue timer is from a rework route to the main route then this is the name of the rework route and the route column is the name of the main route. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

RWK_START_STEP

If the queue timer moves to a rework route and step from the main route then this is the start step on the rework route. The timer handling is treated the same once it enters rework, with the rework step starting the timer like the normal start step. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

OVR_IS_QUEUE_STOPPED

This is Y if we know from the customer logic that lots cannot start the first step in the queue because their logic has determined that there is too much WIP already in the queue sequence. In the future, we will also use our own logic for this so we stop lots if this is Y or if our logic says to stop. In both cases, we can allow specific lots to go through using ovr_is_queue_allowed in WIP_LOTS_STATIC. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

WAIT_SEC_TO_SCHED

The lot may be scheduled but must not be allowed to dispatch or start until this number of seconds has elapsed. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

WAIT_SEC_UPDATED_INST

Time which may be used to adjust wait_sec_to_sched, usually based on how long a timer was been stopped. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

NON_TIMER_WIP_PCT

When calculating the time required to process WIP through a queue timer segment, we normally consider both WIP on queue timers, as well as non-queue-time-limited WIP in the same area, equally in terms of their impact on the available capacity of the tools required to run the segment. If this is set to <100%, then we under-weight the impact of the non-queue-time-limited WIP accordingly. We strongly recommend keeping it at 100%, because setting it to a low value can cause scheduler to prioritize excessive queue timer WIP, and delay running non-queue-time-limited WIP. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

HIDE_TIMER_IN_DASH

This configuration will remove WIP for this timer_id from the Dashboard Queue Timer report. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

EXCLUDE_HOLD_LOTS_IN_TIMER

This configuration will exclude any HOLD lots from queue timer consideration if set to Y. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

DESCRIPTION

Tool desciption. This value is only used to display in the Dashboard. (* inherited from FPSINPUT.EQP_TOOLS)

SCH_IGNORE_TIMER

When set to Y, this timer will not be loaded into the scheduler for consideration. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

SCH_IGNORE_ON_EXPIRY

THE FLAG WHICH INDICATES TO STOP SCHEDULING UPON EXPIRATION OF THE TIMER (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

SCH_WEIGHT_PER_HOUR_ON_EXPIRY

THE VALUE WHICH INDICATES THE POINTS PER HOUR ADDED TO THE TIMER SCORE UPON EXPIRATION OF THE TIMER (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

SCH_RESET_SCORE_ON_EXPIRY

THE FLAG WHICH INDICATES QUEUE TIMER SCORE SHOULD BE SET TO ZERO UPON EXPIRATION OF THE TIMER (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

TIMER_ID_START_STEP

This indicates that this step is the start of a queue timer. Inner join with RTG_QUEUE_TIMERS using timer_id as there is no foreign key because the timer_id record might get deleted from RTG_QUEUE_TIMERS. (* inherited from FPSBASE.WIP_STEP_FUTURE)

TIMER_ID_MID_STEP

This indicates that this step is the end of a queue timer. Inner join with RTG_QUEUE_TIMERS using timer_id as there is no foreign key because the timer_id record might get deleted from RTG_QUEUE_TIMERS. (* inherited from FPSBASE.WIP_STEP_FUTURE)

TIMER_ID_END_STEP

This indicates that this step is in the middle of a queue timer. Inner join with RTG_QUEUE_TIMERS using timer_id as there is no foreign key because the timer_id record might get deleted from RTG_QUEUE_TIMERS. (* inherited from FPSBASE.WIP_STEP_FUTURE)

WAIT_SEC_START_STEP

EXPIRED_SEC_START_STEP

EXPIRED_SEC_MID_STEP

EXPIRED_SEC_END_STEP

SEQ_NUM

Sequence number of step in route (* inherited from FPSINPUT.RTG_ROUTE_STEPS)

PROCESS_FAMILY

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

SCHED_GROUP

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

PROCESS_SUBFAMILY

Route step family is used for the Dashboard to separate processes in a process family based on shared but limited assignments. It is also the base for GP subfamily. (* inherited from FPSBASE.RTG_ROUTE_STEPS_PLUS)

MPU

MPU is a commonly used abbreviation which stands for minutes per unit. It is often referred to as MPW which for minutes per wafer but MPU is better because the unit is not always wafer. (* inherited from FPSBASE.WIP_LOT_HIST)

EST_SMP_PCT

Smp_pct tells you what percentage of the lots complete on a tool. Some sites skip steps by jumping over them so we see the lot move from step 3 to step 5 and we only know that it jumped step 4 because step 4 is on the route between 3 and 5. Other sites skip steps by moving lots into them and then moving them out a second later so we see a move from 3 to 4 at 11:11:11 and a move from 4 to 5 at 11:11:12. We do not care how it is done but just that the lot did not process at step 4 -- and to be more specific that no tool capacity is required to process this lot at step 4 and no cycle time is accumulated at step 4. (* inherited from FPSBASE.WIP_GOAL_LOT_SHIFT)

IS_STAGING_STEP

We expect large amounts of WIP and long cycle times at staging steps. We still calculate cycle time like any other step but the important difference is that lots currently at a staging step are not counted as normal coming lots to future steps. Instead we show them in a special column labeled From Staging. (* inherited from FPSINPUT.RTG_ROUTE_STEPS)

ALWAYS_ALLOW_Q_WHEN_DOWN

Normally we do not allow lots to start at the first step in a queue timer sequence if there is a step in the sequence that has no tools available. But if this flag is set to Y then we will allow lots to start even when all tools are down at this process. Typically this is used for a process that we know we can skip but the est_smp_pct might be above the smp_pct_to_allow_q_when_down threshold set for the facility in GEN_FACILITIES. (* inherited from FPSINPUT.RTG_PROCESSES)

COMMIT_STEP_SEC

COMMIT_STEP_SEC_TO_EOL

STEP_SEC_NOHLD_RT_WSF

STEP_SEC_NOHLD_RT_WSF_TO_EOL

TCT_SEC

Theoretical cycle time in seconds (* inherited from FPSBASE.WIP_LOT_HIST)

TCT_SEC_TO_EOL

PROC_SEC_COMP_FULL_WAVG

START_STEP_SEQ_NUM

START_STEP_SMP_PCT

START_STEP_SCHED_GROUP

START_STEP_PROCESS_MODULE

START_STEP_PROCESS_GROUP

START_STEP_PROCESS

START_STEP_TCT_SEC

START_STEP_TCT_SEC_TO_EOL

START_STEP_COMMIT_STEP_SEC

START_STEP_COMMIT_SEC_TO_EOL

START_STEP_SEC_NOHLD_RT_WSF

START_STEP_SEC_NH_R_WSF_TO_EOL

START_STEP_PROC_SEC_C_F_WAVG

END_STEP_SEQ_NUM

END_STEP_SMP_PCT

END_STEP_SCHED_GROUP

END_STEP_PROCESS_MODULE

END_STEP_PROCESS_GROUP

END_STEP_PROCESS

END_STEP_TCT_SEC

END_STEP_TCT_SEC_TO_EOL

END_STEP_COMMIT_STEP_SEC

END_STEP_COMMIT_SEC_TO_EOL

END_STEP_SEC_NOHLD_RT_WSF

END_STEP_SEC_NH_R_WSF_TO_EOL

END_STEP_PROC_SEC_C_F_WAVG