FPSAPP.RTG_REF_QUEUE_TIMER_STEP_PCT

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)

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)

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)

SEQ_NUM

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

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)

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)

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)

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)

CT_SEC_TOTAL

CT_SEC_AT_STEP

CT_PCT_AT_STEP

COMMIT_SEC_TOTAL

COMMIT_SEC_AT_STEP

COMMIT_PCT_AT_STEP

TCT_SEC_TOTAL

TCT_SEC_AT_STEP

COMMIT_STEP_SEC_CURR

COMMIT_STEP_SEC_TO_EOL_CURR

STEP_SEC_CURR

STEP_SEC_TO_EOL_CURR

TCT_SEC_CURR

TCT_SEC_TO_EOL_CURR

PROC_SEC_CURR

SEQ_NUM_START

COMMIT_STEP_SEC_START

COMMIT_STEP_SEC_TO_EOL_START

STEP_SEC_START

STEP_SEC_TO_EOL_START

TCT_SEC_START

TCT_SEC_TO_EOL_START

PROC_SEC_START

SEQ_NUM_END

COMMIT_STEP_SEC_END

COMMIT_STEP_SEC_TO_EOL_END

STEP_SEC_END

STEP_SEC_TO_EOL_END

TCT_SEC_END

TCT_SEC_TO_EOL_END

PROC_SEC_END