FPSINPUT.SCH_P_CURR_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)

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)

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)

PROCESS

Process defines what occurs at a step. Different steps can share the same process if they are identical. Process should normally determine allowed tools and recipe although it can be overridden by step, route, prd, lot, and experiment for exceptions. Each process is dynamically assigned to one or more eqp_type-process_family combinations with use_pct. One process_family is determined to be primary. If grouping is done correctly, a process should only be one eqp_group with no crossover. (* inherited from FPSINPUT.RTG_PROCESSES)

PROCESS_GROUP

Process group is the critical field where tools and processes come together for the purposes of Scheduler. Process group is in both EQP_TOOLS for the tools and in RTG_PROCESSES for processes. Ideally all tools that run the same set of processes with no crossover including back-up and emergency tools would be in the same process group but it is important to note that this is not technically required for Scheduler as long as all process groups are in the same sched group. (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)

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)

SEQ_NUM

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

NUM_STEPS_AWAY

Number of steps away not including steps which we know will be skipped nor those which we estimate will be skipped at least x pct of the time. This x value is configurable in GEN_FACILITIES using the smp_pct_for_num_steps_away column. (* inherited from FPSBASE.WIP_STEP_FUTURE)

TCT_SEC

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

TCT_SEC_TO_EOL

TCT_SEC_TO_END_OF_QUEUE

CT_SEC

CT_SEC_TO_EOL

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)

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)

STARTED_ON_RWK_ROUTE

100

TIMER_TCT_PCT_TO_EOT

TIMER_CT_PCT_TO_EOT

TIMER_WARNING_SEC

TIMER_EXPIRED_SEC

TIMER_WAIT_SEC

TIMER_EXPIRED_PULL_SEC

QUEUE_TCT_SEC

The total process time (TCT_SEC) between the start step and the end step, but not include the step that is est_smp_pct < 50 (defined on sched-group level) (* inherited from FPSAPP.SCH_W_H_S_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)

IS_TIMER_STARTED

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)

SCHED_GROUP_START

PROCESS_MODULE_START

PROCESS_GROUP_START

the process group for the timer start step (* inherited from FPSAPP.SCH_W_H_S_QUEUE_TIMERS)

PROCESS_START

the process for the timer start step (* inherited from FPSAPP.SCH_W_H_S_QUEUE_TIMERS)

ROUTE_START

STEP_START

SEQ_NUM_START

NUM_STEPS_AWAY_START

NUM_SEQ_AWAY_START

TIMER_STARTED_INST_START

TCT_SEC_TO_EOL_START

CT_SEC_TO_EOL_START

COMMENT_START

SCHED_GROUP_RWK_START

PROCESS_MODULE_RWK_START

PROCESS_GROUP_RWK_START

PROCESS_RWK_START

ROUTE_RWK_START

STEP_RWK_START

SEQ_NUM_RWK_START

NUM_STEPS_AWAY_RWK_START

NUM_SEQ_AWAY_RWK_START

TIMER_STARTED_INST_RWK_START

TCT_SEC_TO_EOL_RWK_START

CT_SEC_TO_EOL_RWK_START

COMMENT_RWK_START

SCHED_GROUP_END

PROCESS_MODULE_END

PROCESS_GROUP_END

the process group for the timer end step (* inherited from FPSAPP.SCH_W_H_S_QUEUE_TIMERS)

PROCESS_END

the process for the timer end step (* inherited from FPSAPP.SCH_W_H_S_QUEUE_TIMERS)

ROUTE_END

STEP_END

SEQ_NUM_END

NUM_STEPS_AWAY_END

NUM_SEQ_AWAY_END

TCT_SEC_TO_EOL_END

CT_SEC_TO_EOL_END

SCHED_GROUP_STEP_0

PROCESS_GROUP_STEP_0

PROCESS_STEP_0

NUM_STEPS_AWAY_STEP_0

NUM_SEQ_AWAY_STEP_0

SCHED_STATE_STEP_0

WIP_TIMER_PCT_SCALE