FPSINPUT.SCH_W_H_S_EQP_PROCESS_USAGES

CHANGE_COST

NUMBER(9)

the cost it need to budget to have this change (* from FPSINPUT.EQP_PROCESS_USAGES)

CHANGE_FROM

VARCHAR2(100)

the value the process max usagess from (* from FPSINPUT.EQP_PROCESS_USAGES)

CHANGE_SEC

NUMBER(9)

the time it takes to have this change (* from FPSINPUT.EQP_PROCESS_USAGES)

CHANGE_TO

VARCHAR2(100)

the value the process max usagess to (* from FPSINPUT.EQP_PROCESS_USAGES)

CHANGE_TYPE

VARCHAR2(64)

the change for this process max usages. only allow setup, recipe, recipe_family, recipe_group (* from FPSINPUT.EQP_PROCESS_USAGES)

CREATE_INST

DATE

ENTITY_TYPE

VARCHAR2(12)

the entity type for this process max usages. only allow chamber, tool (* from FPSINPUT.EQP_PROCESS_USAGES)

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)

MAX_USAGE

NUMBER(9)

the max usage for change_from before it change to the new value (* from FPSINPUT.EQP_PROCESS_USAGES)

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

TOOL

VARCHAR2(16)

Tool is generally just the main tool. The exception is when different entities on the tool run completely independently and it is physically impossible to run wafers of the same lot across multiple entities. In this exception case, we may want to assign the entities to different eqp_types and therefore we should define each entity as a tool. Please note that when we do this there is no indication whatsoever that these different entities are on the same tool. (* from FPSINPUT.EQP_TOOLS)

TOOL_TYPE

VARCHAR2(50)

N

the tool type from the first lot that scheduled (* from FPSAPP.SCH_W_SCHED_DURABLE_INSPECT)