FPSINPUT.SMMS_B_EVENT_DEFINITIONS_CNTR

Data Dictionary

FPSINPUT Tables

> FPSINPUT.SMMS_B_EVENT_DEFINITIONS_CNTR

Table FPSINPUT.SMMS_B_EVENT_DEFINITIONS_CNTR"

Counter (CNTR) based Maintenance definitions define a group of events to be performed on many entities. These counters could be based on lots, wafers, or any time of consumable material. This table includes attributes that exist in MNT_EVENTS if they exist in MNT_EVENTS they will override the values at the family level.

Schema: FPSINPUT
Tablespace: FPSDATA
Primary key: EVENT_GROUP, EVENT_DEFINITION

Column	Type	Nullable	Comment
EVENT_GROUP	VARCHAR2(128)	N	Event group is the second highest level in the maintenance event hierarchy it could be used to denote the group even maintenance definitions such as PMs, Adhoc tasks, OCAPS, Quals, or inspections. This grouping will be a collection of maintenance definitions. (* from FPSAPP.SMMS_B_EVENT_GROUPS)
EVENT_DEFINITION	VARCHAR2(200)	N
COUNTER_DUE	NUMBER(12,3)	N	Counter value when the maintenance event will be due or expected. See `counter_early` and `counter_late` for the window of values in which the maintenance can be performed. (* from FPSINPUT.EQP_MNT_FUTURE)
COUNTER_EARLY	NUMBER(12,3)	N	Counter value when the maintenance event will be early (* from FPSINPUT.EQP_MNT_FUTURE)
COUNTER_INTERVAL	NUMBER(12,3)	N	Indicates the frequency of future occurrences of this maintenance. For example, a qual required every 250 wafers will be listed once with counter_due set to the next occurrence and `counter_interval` set to 250 so we know to plan for it to occur again 250, 500, 750, etc. wafers after the counter_due. (* from FPSINPUT.EQP_MNT_FUTURE)
COUNTER_LATE	NUMBER(12,3)	N	Counter value when the maintenance event will be late. In most systems, the entity in question will be mandatorily logged down if the maintenance is not started before the counter reaches this value. (* from FPSINPUT.EQP_MNT_FUTURE)
COUNTER_NAME	VARCHAR2(64)	N	Name of the counter used for this maintenance event. (* from FPSINPUT.EQP_MNT_FUTURE)
COUNTER_UNITS	VARCHAR2(18)	N	Unit for the maintenance counter. Common examples include wafers or hours or kWh. (* from FPSINPUT.EQP_MNT_FUTURE)
CREATED_INST	DATE		Time when the lot was created, either lot start or split. (* from FPSINPUT.WIP_LOTS_STATIC)
DESCRIPTION	VARCHAR2(256)	N	Tool desciption. This value is only used to display in the Dashboard. (* from FPSINPUT.EQP_TOOLS)
ENT_OR_CARR_OR_DUR	VARCHAR2(1)	N	Upcoming maintenance for entities, carriers, and durables is included together in this table. An E here indicates that the `logged_entity` field in this table is an entity, C for carrier, and D for durable. (* from FPSINPUT.EQP_MNT_FUTURE)
EST_MNT_DURATION_SEC	NUMBER(8)	N	Est_mnt_duration_sec is the estimate of the total duration of the maintenance in seconds including work time, wait time, and qual time. Est_mnt_duration_sec is required then if desired, this total can be broken down into est_mnt_work_sec, est_mnt_wait_sec, and est_mnt_qual_sec. These three breakdown columns are optional but if any of those three columns are populated then they must sum to the value of est_mnt_duration_sec. Only est_mnt_duration_sec is used in FPS applications. The other three are available for informational purposes and to use for custom reporting but are not currently used in any FPS application. (* from FPSINPUT.EQP_MNT_FUTURE)
IS_HIDDEN_BY_DEFAULT	CHAR(1)		If this flag is set then this event is hidden by default on the Maintenance Dashboard to avoid clutter. There is an option to show hidden events. (* from FPSINPUT.EQP_MNT_FUTURE)
NUM_TECHS_RQD	NUMBER(1)		We assume that each maintenance event requires one technician but this column allows us to indicate that more than one person is required to complete the event. (* from FPSINPUT.EQP_MNT_FUTURE)