data-dictionary

FPSAPP.EQP_MNT_CHAMBER_ALARM_HIST

Data Dictionary

>

FPSAPP Tables

> FPSAPP.EQP_MNT_CHAMBER_ALARM_HIST

Table FPSAPP.EQP_MNT_CHAMBER_ALARM_HIST"

This table stores the historical values of the chamber alarms being tracked by an FDC system.

  • Schema: FPSAPP

  • Tablespace: FPSDATAHIST

  • Primary key: INST, FACILITY, ENTITY


Column

Type

Nullable

Comment

INST

DATE

N

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

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)

ENTITY

VARCHAR2(19)

N

The lowest level of the equipment hierarchy that an event can be logged against. Tools, subtools, shared parent tools, chambers, ports are all entities. Load locks are also included although we consider them as ports. (* from FPSINPUT.EQP_STATUS_VERIFY)

ALARM_TEXT

VARCHAR2(48)

The actual alarm text for the fault.

ANALYSIS_DETAIL

VARCHAR2(48)

The detail of the analysis being sent.

ANALYSIS_NAME

VARCHAR2(48)

The name of the analysis being sent.

INSERTED_TIME

TIMESTAMP(6)

Timestamp field set by trigger storing SYSTIMESTAMP when record was inserted in the table. (* from FPSINPUT.WIP_EVENT_HIST)