FPSBASE.WIP_RESERVE_HIST

DISPATCH_OPERATOR

VARCHAR2(64)

DISP_TOOL

VARCHAR2(16)

EQP_TYPE

VARCHAR2(50)

Each tool is assigned an EQP_TYPE and all tools in the same type are identical meaning that they should run at the same throughput when running the same process with the same chamber type count. We also expect similar availability since these tools are identical. However tools in the same EQP_TYPE may have different chamber configurations and may run different groups of processes. (* from FPSINPUT.EQP_TYPES)

EST_MACHINE_RECIPE

VARCHAR2(100)

Estimated machine recipe what we estimate will be the machine recipe based on information from the Recipe Management System. It is used in combination with process for throughput calculations and setup change penalty calculations. It is not necessary to estimate for all processes since this is always used in combination however it needs to be NA rather than blank since it is part of the primary key of most THP tables. Hopefully when this is not NA it should match the actual machine recipe logged for each lot during processing. (* from FPSINPUT.RTG_TOOL_ASSIGNMENTS)

EXTL_RESERVE_TOOL

VARCHAR2(16)

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)

LOT

VARCHAR2(32)

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)

MANL_RESERVE_TOOL

VARCHAR2(16)

Stores tool reserved by NextMove (* from FPSBASE.WIP_STEP_FUTURE_SCHED)

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)

PREV_EXTL_RESERVE_TOOL

VARCHAR2(16)

PREV_MANL_RESERVE_TOOL

VARCHAR2(16)

PREV_RECIPE

VARCHAR2(100)

Recipe of the previous job on the tool before the job including this lot. Used in combination with prev_process to determine if this job cascaded and if it required a setup change. (* from FPSBASE.WIP_LOT_HIST)

PREV_SCHED_TOOL

VARCHAR2(16)

ROUTE

VARCHAR2(256)

N

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

SCHED_COMMENT

VARCHAR2(4000)

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)

SCHED_GROUP_STATE

VARCHAR2(5)

State is constrained to one of three values. ON: Running for production. DEV: Schedule is visible for authorized users only (Q-Mgr and Scheduler run as if ON). OFF: Rarely used except when setting up a new sched_group. (* from FPSINPUT.RTG_SCHED_GROUPS)

SCHED_IS_RESERVED

CHAR(1)

SCHED_SCORE

NUMBER(20,4)

SCHED_SCORE_DETAILS

VARCHAR2(4000)

SCHED_START

DATE

The first start time for the durable to be used (* from FPSBASE.RTG_DURABLE_FUTURE_SCHED)

SCHED_TOOL

VARCHAR2(16)

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

START_SHIFT

DATE

Shifts can be of any length and it is important that all queries get the shift length based on start_shift and end_shift rather than assuming a set number of hours. (* from FPSINPUT.CAL_SHIFTS)

STEP

VARCHAR2(256)

N

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)