FPSADMIN.RTG_QUEUE_TIMERS_LOT_HIST

ACTION

VARCHAR2(1)

For CHGLOG and automatic HIST tables, this is I for insert or U for updated or D for delete. (* from FPSINPUT.EQP_PORT_HIST)

BEG_PROC_INST_OF_END_STEP

DATE

BEG_PROC_INST_OF_START_STEP

DATE

Time when the lot started processing on the tool at the step which starts the queue timer. (* from FPSINPUT.RTG_QUEUE_TIMERS_LOT_MANUAL)

COMP_INST_OF_END_STEP

DATE

COMP_INST_OF_START_STEP

DATE

Time when the lot completed (also referred to as moved out of) the step which starts the queue timer. (* from FPSINPUT.RTG_QUEUE_TIMERS_LOT_MANUAL)

DESCRIPTION

VARCHAR2(256)

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

DISPATCH_INST_OF_END_STEP

DATE

DISPATCH_INST_OF_START_STEP

DATE

Time when the lot was dispatched to the tool at the step which starts the queue timer. (* from FPSINPUT.RTG_QUEUE_TIMERS_LOT_MANUAL)

END_PROC_INST_OF_END_STEP

DATE

END_PROC_INST_OF_START_STEP

DATE

Time when the lot ended processing on the tool at the step which starts the queue timer. (* from FPSINPUT.RTG_QUEUE_TIMERS_LOT_MANUAL)

END_ROUTE_IF_DIFF

VARCHAR2(256)

Most normal queue timers start and end on the same route and for these we leave this column blank. However some timers start on a rework route and ending on the main route so this column allows us to support this. We would populate the route column with the rework route (the start step would be on this rework route) and this end_route_if_diff column with the main route (the end step would be on this main route). (* from FPSINPUT.RTG_QUEUE_TIMERS)

END_STEP

VARCHAR2(256)

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

EVENT

VARCHAR2(48)

N

Event that was logged, effectively removing or stopping the timer.

EVENT_TYPE

VARCHAR2(12)

Event_type that was logged, effectively removing or stopping the timer. This corresponds to the timer_end_event defined in RTG_QUEUE_TIMERS.

EXPIRED_SEC

NUMBER(7)

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

FACILITY

VARCHAR2(6)

N

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)

FEED_IF_LESS_THAN_SEC

NUMBER(6)

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

HIST_COMMENT

VARCHAR2(256)

LOT

VARCHAR2(32)

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

MIN_WAIT_SEC

NUMBER(7)

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

NON_TIMER_WIP_PCT

NUMBER(3)

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

OPERATION_END

VARCHAR2(50)

OPERATION_START

VARCHAR2(50)

OVR_IS_QUEUE_STOPPED

CHAR(1)

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

PROCESS_FAMILY_END

VARCHAR2(50)

PROCESS_FAMILY_START

VARCHAR2(50)

PROCESS_MODULE_END

VARCHAR2(12)

PROCESS_MODULE_START

VARCHAR2(12)

ROUTE

VARCHAR2(256)

N

Route the lot was on at the time the timer was removed.

ROUTE_FAMILY

VARCHAR2(36)

Route_family indicates that all routes within the family have similar or even identical steps and have the same segments. At facilities where various prds share the same route it is likely that the route will be the route_family. This is sometimes referred to as the main process flow. It is used on Segment Summary and Line Viewer to group similar routes. (* from FPSINPUT.RTG_ROUTE_FAMILIES)

ROUTE_GROUP

VARCHAR2(36)

Route_group is the parent of route_family. Route_group is used on the Dashboard and other applications as a large grouping for filtering. At many sites this is referred to as technology. (* from FPSINPUT.RTG_ROUTE_GROUPS)

RWK_IF_EXPIRED

CHAR(1)

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

RWK_ROUTE

VARCHAR2(256)

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

RWK_START_STEP

VARCHAR2(256)

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

SCHED_GROUP_END

VARCHAR2(36)

SCHED_GROUP_START

VARCHAR2(36)

SOURCE

VARCHAR2(12)

STARTED_ON_RWK_ROUTE

CHAR(1)

START_STEP

VARCHAR2(256)

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

STEP

VARCHAR2(256)

N

Step the lot was on at the time the timer was removed.

TIMER_END_EVENT

VARCHAR2(12)

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

TIMER_ID

NUMBER(9)

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

TIMER_ROUTE

VARCHAR2(256)

TIMER_START_EVENT

VARCHAR2(12)

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

UPDATED_INST

DATE

Time when the record was updated according to the source data. Note this is not the time when the record was actually updated in this table - it will almost always be earlier. (* from FPSINPUT.GEN_FACILITIES)

WAIT_SEC_TO_SCHED

NUMBER(7)

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

WAIT_SEC_UPDATED_INST

DATE

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