FPSBASE.DASH_P_TOOL_WIP_METRICS

Data Dictionary

FPSBASE Tables

> FPSBASE.DASH_P_TOOL_WIP_METRICS

Table FPSBASE.DASH_P_TOOL_WIP_METRICS"

See comments in DASH_REF_P_TOOL_WIP_METRICS view.

Schema: FPSBASE
Tablespace: FPSDATA
Primary key: FACILITY, TOOL

Column	Type	Nullable	Comment
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)
TOOL	VARCHAR2(16)	N	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)
BAY	VARCHAR2(12)		A bay is a physical area within the building. The bay is important for estimating travel time for a carrier to reach its destination as we usually store these estimates as a matrix of bay-to-bay and assume that the estimated time from any location within one bay to any location within another bay is approximately the same. (* from FPSINPUT.MHS_BAYS)
DAY_ASSIGNED_WIP	NUMBER
DAY_ASSIGNED_WIP_BAY	NUMBER
DAY_COMP_BAY_PACE	NUMBER
DAY_COMP_PACE	NUMBER
DAY_CURR_COMP	NUMBER
DAY_CURR_COMP_BAY	NUMBER
DAY_CURR_WIP	NUMBER
DAY_CURR_WIP_BAY	NUMBER
DAY_PCT_COMPLIANCE	NUMBER
DAY_PCT_COMPLIANCE_BAY	NUMBER
DAY_TGT_COMP	NUMBER
DAY_TGT_COMP_BAY	NUMBER
DAY_TGT_WIP	NUMBER
DAY_TGT_WIP_BAY	NUMBER
GOAL_WIP_PCT_TO_TGT_BAY_PERF	NUMBER(2)		The plus / minus percentage of target WIP that is considered acceptable in the Bay Performance NMV pages. EG 20% gives acceptable WIP range of 80 to 120 on a target of 100. (* from FPSINPUT.GEN_SITE)
SHIFT_ASSIGNED_WIP	NUMBER
SHIFT_ASSIGNED_WIP_BAY	NUMBER
SHIFT_COMP_BAY_PACE	NUMBER
SHIFT_COMP_PACE	NUMBER
SHIFT_CURR_COMP	NUMBER
SHIFT_CURR_COMP_BAY	NUMBER
SHIFT_CURR_WIP	NUMBER
SHIFT_CURR_WIP_BAY	NUMBER
SHIFT_PCT_COMPLIANCE	NUMBER
SHIFT_PCT_COMPLIANCE_BAY	NUMBER
SHIFT_TGT_COMP	NUMBER
SHIFT_TGT_COMP_BAY	NUMBER
SHIFT_TGT_WIP	NUMBER