FPSINPUT.EQP_MNT_COUNTER_CURR

Data Dictionary

>

FPSINPUT Tables

> FPSINPUT.EQP_MNT_COUNTER_CURR

Table FPSINPUT.EQP_MNT_COUNTER_CURR"

Current information on counter-based PMs based on information from EQP_MNT_COUNTER_HIST.

Schema: FPSINPUT
Tablespace: FPSDATA
Primary key: FACILITY, EVENT_ID

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_CHG_PER_DAY	NUMBER(13,4)	N	Average change in the counter per day calculated by linear regression and used to estimate the time for a counter-based maintenance
COUNTER_CHG_STD_DEV	NUMBER(13,4)	N	Standard deviation is a measure of fit to the line. A lower value means a better fit.
COUNTER_CURR	NUMBER(12,3)	N	Current counter value read at counter_read_inst
COUNTER_DIRECTION	VARCHAR2(4)	N
COUNTER_PRE_RESET_INST	DATE		The inst the last time the counter value was reset.
COUNTER_PRE_RESET_VALUE	NUMBER(12,3)		If a counter has been reset recently then this will be the min or max value depending on the counter direction before the counter was reset. A null value means that there were no resets within the min_used_counter_read_inst
COUNTER_READ_INST	DATE	N	Time when the current counter value was reported.
LAST_READ_COMMENT	VARCHAR2(512)
LAST_READ_OPERATOR	VARCHAR2(64)
MIN_USED_COUNTER_READ_INST	DATE	N
NUM_COUNTER_RESETS	NUMBER(3)		How many times the counter has been reset since min_used_counter_read_inst. This is used as a data quality as a data quality check.