FPSBASE.CM_W_ROUTE_STEP_EQPS_USE

Data Dictionary

>

FPSBASE Tables

> FPSBASE.CM_W_ROUTE_STEP_EQPS_USE

Table FPSBASE.CM_W_ROUTE_STEP_EQPS_USE"

Table contains override for use percentage in the Capacity Model. This table is populated by upload from the CM website.

Schema: FPSBASE
Tablespace: FPSDATA
Primary key: FACILITY, EQP_TYPE, ROUTE, STEP, WORKWEEK, SCENARIO
Foreign keys: CM_W_ROUTE_STEP_EQPS_US_FK_FAC: FACILITY REFERENCES FPSINPUT.GEN_FACILITIES (FACILITY)

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)
EQP_TYPE	VARCHAR2(50)	N	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)
ROUTE	VARCHAR2(256)	N	Route that has threading requirements (* from FPSINPUT.RTG_STEP_THREADING)
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)
WORKWEEK	VARCHAR2(7)	N
SCENARIO	VARCHAR2(16)	N
EST_USE_PCT	NUMBER(5		Estimated use percentage is the percentage of units of this route-step that we expect to run on this eqp_type. Normally we use historical data to calculate this for the Capacity Model but entering a value in the OVR table manually overrides that historical number. (* from FPSINPUT.RTG_ROUTE_STEP_EQPTYPE_OVR)