FPSBASE.EQP_MNT_EVENTS_OVR

Data Dictionary

>

FPSBASE Tables

> FPSBASE.EQP_MNT_EVENTS_OVR

Table FPSBASE.EQP_MNT_EVENTS_OVR"

Optional list of maintenance events including but not limited PMs, quals, automated, inline or adhoc.

Schema: FPSBASE
Tablespace: FPSDATA
Primary key: FACILITY, EVENT_ID
Foreign keys: EQP_MNT_EVENTS_OVR_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)
EVENT_ID	VARCHAR2(64)	N	Field that uniquely identifies the maintenance task definition in the facility. `Event_id` is usually a number or code from the maintenance system, but it could also be defined as `logged_entity` concatenated with `mnt_name`, since that combination also uniquely represents an event. It is important to ensure that our definition of `event_id` represents repeated instances of the same maintenance event with the same `event_id`. For example, if we have a monthly PM on tool T1, there will be instances of this event each month. The field used as `event_id` could be something like T1 monthly PM; it should not be something like T1 monthly PM Jan, T1 monthly PM Feb, etc., since this would cause the `event_id` to change every month. (* from FPSINPUT.EQP_MNT_FUTURE)
COUNTER_INST_PERCENTILE	NUMBER(6,5)		Tolerance for use in prediction when counter based events will come do. Higher number means that a larger range of values will be included. Smaller values mean that the prediction will be more strict on the values to include in the estimation.
COUNTER_VALUE_PERCENTILE	NUMBER(6,5)		See comment on COUNTER_INST_PERCENTILE, same idea but for the value.
EVALUATE_FTR	CHAR(1)		This flag will determine if we should evaluate First Time Right (FTR) for these events, Y means we will report FTR, N means we will not report FTR.