FPSADMIN.SCH_W_H_S_QUEUE_TIMERS

COMMENT_RWK_START

VARCHAR2(512)

COMMENT_START

VARCHAR2(512)

CREATE_INST

DATE

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)

IS_TIMER_STARTED

CHAR(1)

LOT

VARCHAR2(128)

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)

NUM_SEQ_AWAY_END

NUMBER(4)

NUM_SEQ_AWAY_RWK_START

NUMBER(4)

NUM_SEQ_AWAY_START

NUMBER(4)

NUM_STEPS_AWAY

NUMBER(4)

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

NUM_STEPS_AWAY_END

NUMBER(4)

NUM_STEPS_AWAY_RWK_START

NUMBER(4)

NUM_STEPS_AWAY_START

NUMBER(4)

PROCESS

VARCHAR2(50)

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

PROCESS_END

VARCHAR2(50)

the process for the timer end step

PROCESS_GROUP

VARCHAR2(36)

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

PROCESS_GROUP_END

VARCHAR2(36)

the process group for the timer end step

PROCESS_GROUP_RWK_START

VARCHAR2(36)

PROCESS_GROUP_START

VARCHAR2(36)

the process group for the timer start step

PROCESS_GROUP_STEP_0

VARCHAR2(36)

PROCESS_MODULE_END

VARCHAR2(12)

PROCESS_MODULE_RWK_START

VARCHAR2(12)

PROCESS_MODULE_START

VARCHAR2(12)

PROCESS_RWK_START

VARCHAR2(50)

PROCESS_START

VARCHAR2(50)

the process for the timer start step

PROCESS_STEP_0

VARCHAR2(50)

QUEUE_TCT_SEC

NUMBER

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)

ROUTE

VARCHAR2(256)

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

ROUTE_END

VARCHAR2(256)

ROUTE_RWK_START

VARCHAR2(256)

ROUTE_START

VARCHAR2(256)

RUN_ID

VARCHAR2(50)

N

the run id from the last successful scheduler (* from FPSAPP.SCH_W_SCHED_GROUP_STATUS)

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

VARCHAR2(36)

N

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

SCHED_GROUP_END

VARCHAR2(36)

SCHED_GROUP_RWK_START

VARCHAR2(36)

SCHED_GROUP_START

VARCHAR2(36)

SCHED_GROUP_STEP_0

VARCHAR2(36)

SCHED_STATE_STEP_0

VARCHAR2(7)

SCH_IGNORE_ON_EXPIRY

CHAR(1)

The flag which indicates to stop scheduling upon expiration of the timer

SCH_RESET_SCORE_ON_EXPIRY

CHAR(1)

The flag which indicates queue timer score should be set to zero upon expiration of the timer

SCH_WEIGHT_PER_HOUR_ON_EXPIRY

NUMBER(7,2)

The value which indicates the points per hour added to the timer score upon expiration of the timer

SEQ_NUM

NUMBER(7,2)

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

SEQ_NUM_END

NUMBER(7,2)

SEQ_NUM_RWK_START

NUMBER(7,2)

SEQ_NUM_START

NUMBER(7,2)

SHOULD_USE

CHAR(1)

This flag determines if the scheduler should use this data or not

STEP

VARCHAR2(256)

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

STEP_END

VARCHAR2(256)

STEP_RWK_START

VARCHAR2(256)

STEP_START

VARCHAR2(256)

TCT_SEC

NUMBER(7)

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

TCT_SEC_TO_END_OF_QUEUE

NUMBER(11)

TIMER_CT_PCT_TO_EOT

NUMBER(7,2)

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_EXPIRED_PULL_SEC

NUMBER(7)

TIMER_EXPIRED_SEC

NUMBER(7)

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_STARTED_INST_RWK_START

DATE

TIMER_STARTED_INST_START

DATE

TIMER_START_EVENT

VARCHAR2(12)

To indicate what is the event, DISP, BEGIN, END, or COMP to trigger timer start from the start-step

TIMER_TCT_PCT_TO_EOT

NUMBER(7,2)

TIMER_WAIT_SEC

NUMBER(7)

TIMER_WARNING_SEC

NUMBER(7)