FPSAPP.RTG_PROCESS_COUNTERS

SCHED_GROUP

VARCHAR2(36)

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)

COUNTER_INFO

VARCHAR2(512)

the unique identifier for the counter

FACILITY

VARCHAR2(6)

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)

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

COUNTER_LEFT

NUMBER(5)

the current available amount left of this counter

COUNTER_MAX

NUMBER(5)

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

COUNTER_UNIT_WEIGHTS

NUMBER(3)

the weights will consume per each unit

TIME_PERIOD

VARCHAR2(32)

the period (cycle) for each period. can be work_week, work_day, work_shift

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)

this is used to delay the schedule for the normal lots if it chooses delay_schedule as the wait_to_sched_method

WAIT_SEC_TO_SCHED_PRTY

NUMBER(7)

this is used to delay the schedule for the priority lots if it chooses delay_schedule as the wait_to_sched_method