FPSADMIN.NMV_P_CLIENT_CARRIERS

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)

CARRIER

VARCHAR2(32)

RFID of the cassette or FOUP the lot is currently in. (* from FPSINPUT.MHS_CARRIERS)

CURR_LOCATION

VARCHAR2(32)

store the curr location of the lot (* from FPSAPP.SCH_W_H_S_LOTS)

CURR_LOC_BAY

VARCHAR2(12)

CURR_LOC_BLDG

VARCHAR2(12)

CURR_LOC_CAP_CAST

NUMBER

CURR_LOC_NUM_CAST

NUMBER

CURR_LOC_OUT_STKRS

VARCHAR2(300)

CURR_LOC_STATION

VARCHAR2(32)

CURR_TOOL

VARCHAR2(16)

CURR_TOOL_BAY

VARCHAR2(12)

CURR_TOOL_OUT_STKRS

VARCHAR2(300)

CURR_TOOL_PRI_STKRS

VARCHAR2(300)

CURR_TOOL_SEC_STKRS

VARCHAR2(300)

CURR_VEHICLE

VARCHAR2(24)

DESIRED_LOCATION

VARCHAR2(4000)

EFF_SCHED_START

DATE

LEAST_FULL_STKR

VARCHAR2(16)

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)

MODULE

VARCHAR2(12)

Modules are departments of people who manage certain areas of the fab. The modules are assigned ownership of a set of tools to operate and maintain as well as steps on the route that they are responsible for executing. Since many of our tables include tool and step information together, we must distinguish between the owner of the step (WIP_MODULE), the owner of the operation of the tool (EQP_MODULE), and the owner of the maintenance of the tool (MNT_MODULE). WIP_MODULE is used to credit moves and set goals. Each route-step is assigned to a process family and then its wip_module is defined by the process family. EQP_MODULE is used to group tools particularly for tool performance reporting. Similar to WIP, each tool is dynamically assigned to a process family based on its assignments and then its eqp_module is defined by the process family. MNT_MODULE is usually the same as EQP_MODULE but unlike EQP_MODULE is not dependent on assignments but only on the EQP hierarchy. Each tool is assigned to an eqp_type and each eqp_type is assigned to a mnt_family and each mnt_family is assigned to a mnt_module. (* from FPSINPUT.GEN_MODULES)

PROCESS_STATE

VARCHAR2(5)

Process state is the most commonly used level of our Enhanced Cycle Time hierarchy. This displays on Dashboard, Scheduler, Cycle Time Analyzer, and Finished Lot Cycle Time Reporter. Process state is the parent of ECT state, however, there is configuration for when to show the process state of Reserved in each application which is done in WIP_ECT_STATES. (* from FPSADMIN.WIP_PROCESS_STATES)

RESERVED_VEHICLE

VARCHAR2(14)

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)

SCHED_TOOL_BAY

VARCHAR2(12)

SCHED_TOOL_BLDG

VARCHAR2(12)

SCHED_TOOL_PRI_STKRS

VARCHAR2(300)

SCHED_TOOL_SEC_STKRS

VARCHAR2(300)

SHOULD_RESERVE

CHAR(1)