FPSADMIN.SCH_W_H_S_PROCESS_COUNTERS

COUNTER_EFFECTIVE_EVENT

VARCHAR2(5)

used for scheduler to indicate the what was the event that the counter was counted only three options now: 1. disp, it means the counter was counted at the time the lot dispatched to the tool 2. proc, it means the counter was counted at the time the lot process started on the tool 3. ended, it means the counter was counted at the time the lot process ended on the tool, default value (* from FPSINPUT.RTG_PROCESS_COUNTERS)

COUNTER_INFO

VARCHAR2(512)

the unique identifier for the counter associated with this assignment (* from FPSINPUT.RTG_PROCESS_COUNTER_ASGNS)

COUNTER_LEFT

NUMBER

the current available amount left of this counter (* from FPSINPUT.RTG_PROCESS_COUNTERS)

COUNTER_MAX

NUMBER

the maximum usage of this counter

COUNTER_MSG

VARCHAR2(512)

the counter message on the durable (* from FPSAPP.SCH_W_SCHED_DURABLE_INSPECT)

COUNTER_UNIT_TYPE

VARCHAR2(32)

the counter unit, can be wafer, lot, second, job (* from FPSINPUT.RTG_PROCESS_COUNTERS)

COUNTER_UNIT_WEIGHTS

NUMBER(3)

the weights will consume per each unit (* from FPSINPUT.RTG_PROCESS_COUNTERS)

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)

RUN_ID

VARCHAR2(50)

N

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

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)

SHOULD_USE

CHAR(1)

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

TIME_PERIOD

VARCHAR2(32)

the period (cycle) for each period. can be work_week, work_day, work_shift (* from FPSINPUT.RTG_PROCESS_COUNTERS)

TIME_PERIOD_NEXT_START_INST

DATE

WAIT_SEC_TO_SCHED

NUMBER

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_TO_SCHED_PRTY

NUMBER

the wait sec delay on this resource counter for the priority lots