data-dictionary

FPSBASE.ADM_SPEED_HIST

Data Dictionary

>

FPSBASE Tables

> FPSBASE.ADM_SPEED_HIST

Table FPSBASE.ADM_SPEED_HIST"

A table to store results of speed tests written by the ADM_SPEED_HIST_INSERT procedure.

  • Schema: FPSBASE

  • Tablespace: FPSDATAHIST


Column

Type

Nullable

Comment

CHAR_VALUE1

VARCHAR2(4000)

CHAR_VALUE2

VARCHAR2(4000)

FACILITY

VARCHAR2(6)

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)

INST

DATE

Time when the event occurred. (* from FPSINPUT.WIP_EVENT_HIST)

INST_VALUE1

DATE

INST_VALUE2

DATE

LOT

VARCHAR2(128)

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)

LOT_SEQ_WITHIN_SEC

NUMBER(6,2)

For rows with identical timestamps, sequence records to get proper sequence (* from FPSINPUT.WIP_EVENT_HIST)

NUM_VALUE1

NUMBER

NUM_VALUE2

NUMBER

SECONDS

NUMBER(11,6)

N

SPEED_CLASS

VARCHAR2(36)

N

SPEED_GROUP

VARCHAR2(36)

N

START_TS

TIMESTAMP(6)

N

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)

TS

TIMESTAMP(6)

N