data-dictionary

FPSAPP.RTG_QUEUE_MULTI_AREA_WIP

Data Dictionary

>

FPSAPP Tables

> FPSAPP.RTG_QUEUE_MULTI_AREA_WIP

Table FPSAPP.RTG_QUEUE_MULTI_AREA_WIP"

See comments in RTG_REF_QUEUE_MULTI_AREA_WIP view.

  • Schema: FPSAPP

  • Tablespace: FPSDATA

  • Primary key: LOT, FACILITY, ROUTE, START_STEP, RN_FOR_LOT_ROUTE_STEP


Column

Type

Nullable

Comment

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)

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)

ROUTE

VARCHAR2(256)

N

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

START_STEP

VARCHAR2(256)

N

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

RN_FOR_LOT_ROUTE_STEP

NUMBER(2)

N

AVG_SMP_RATE

NUMBER(5,4)

AVG_UPH

NUMBER(9,3)

CUM_LOT_FOR_TIMER

NUMBER(4)

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)

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)

FREE_SEC_FOR_TIMER

NUMBER(7)

FREE_SEC_FOR_TIMER_SUBF_ALLOW

NUMBER(7)

HRS_BEF_Q

NUMBER(5,1)

HRS_BEF_Q_SUBF_ALLOW

NUMBER(5,1)

IS_QUEUE_STOPPED

CHAR(1)

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)

NUM_TOOLS_DOWN

NUMBER(6,2)

NUM_TOOLS_DOWN_SUBF_ALLOW

NUMBER(6,2)

NUM_TOOLS_UP

NUMBER(6,2)

NUM_TOOLS_UP_SUBF_ALLOW

NUMBER(6,2)

PROCESS_FAMILY

VARCHAR2(50)

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

PROCESS_SUBFAMILY

VARCHAR2(100)

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. (* from FPSBASE.RTG_ROUTE_STEPS_PLUS)

QTY_CURR_STEP

NUMBER(9)

QTY_CURR_STEP_PRTY

NUMBER(9)

QTY_IN_TIMER

NUMBER(9)

QUEUE_CALCULATION

VARCHAR2(1000)

QUEUE_CALC_SUBF_ALLOW

VARCHAR2(1000)

QUEUE_EXPLANATION

VARCHAR2(1000)

RN_FOR_ROUTE_STEP

NUMBER(4)

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_GROUP_LIST

VARCHAR2(1000)

START_NUM_STEPS_AWAY

NUMBER(4)

SUBFAM_USED_OR_NULL

VARCHAR2(100)

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)

USE_UP

CHAR(1)

UTIL_OF_AVAIL

NUMBER(5,2)

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)