FPSBASE.RTG_QUEUE_MULTI_AREA_PRTY

LOT

VARCHAR2(32)

N

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)

CURR_PRIORITY_REASON

VARCHAR2(128)

An optional description of why the priority is set as it is. This is typically shown as additional information on pages related to priority lots. (* from FPSINPUT.WIP_LOTS_STATIC)

CURR_STEP

VARCHAR2(256)

N

END_STEP

VARCHAR2(256)

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

END_STEPS_AWAY

NUMBER(4)

END_STEP_COMP_INST_IF_TCT

DATE

EXPIRED_INST

DATE

EXPIRED_INST_PLUS_TCT

DATE

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)

PRIORITY_SORT

NUMBER(3)

N

Unique sort of priority. Sort ascending gives the order from highest to lowest priority. Therefore the smallest number in priority_sort is the highest priority. (* from FPSINPUT.WIP_PRIORITIES)

QUEUE_PRIORITY

VARCHAR2(7)

QUEUE_START_INST

DATE

ROUTE_OF_END_STEP

VARCHAR2(256)

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)

SCHED_SORT

NUMBER(3)

N

The sorting used by the scheduler to prioritize lots. This is more generic than priority_sort as different priorities may have the same sched_sort. (* from FPSINPUT.WIP_PRIORITIES)

SEQ_NUM_OF_END_STEP

NUMBER(7,2)

START_STEP

VARCHAR2(256)

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

TIMER_ID

NUMBER(9)

N

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_PRTY_XFACTOR

NUMBER(2,1)

This allows us to give a curr_priority value to lots in a queue timer if the X-Factor required to finish the timer before it expires is less than this threshold. For example, QUEUE2X priority is configured to have a threshold of 2x processing time and QUEUE3X priority is configured at 3x. We have a lot which is 3 steps from the end of the queue timer and those three steps have 1, 2, and 2 hours of processing time, respectively. The queue timer will expire in 20 hours but all timers end when the lot begins processing at the end step. In order to calculate our X-Factor we need to add the 3 hours processing at the end step. So we get (10 + 2) / (1 + 2 + 2) = 12 / 5 = 2.4. This X-Factor of 2.4 is not less than the threshold for QUEUE2X so it does not get that highest priority but it is less than the threshold for QUEUE3X so it gets that priority. This priority of QUEUE3X is fed to the Dashboard for display and to the Scheduler for calculation and is used by all components of the DWH. (* from FPSINPUT.WIP_PRIORITIES)

XFACTOR_RQD

NUMBER(4