FPSADMIN.SCH_B_DURABLE_COUNTERS

FACILITY

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. (* inherited from FPSINPUT.GEN_FACILITIES)

DURABLE

Durables are either reticles for Litho or probe cards for Wet or Sort. A durable can either be in a carrier or at a location without a carrier. (* inherited from FPSINPUT.RTG_DURABLES)

COUNTER_CURR

Current counter value read at counter_read_inst (* inherited from FPSBASE.EQP_MNT_COUNTER_CURR)

COUNTER_UNIT_TYPE

the counter unit, can be wafer, lot, second, job (* inherited from FPSINPUT.RTG_PROCESS_COUNTERS)

COUNTER_UNIT_WEIGHTS

the weights will consume per each unit (* inherited from FPSINPUT.RTG_PROCESS_COUNTERS)

COUNTER_LATE

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. (* inherited from FPSINPUT.EQP_MNT_FUTURE)

MNT_NAME

Name identifying the scheduled maintenance event which is unique for the `logged_entity`. For example, daily qual or weekly PM. (* inherited from FPSINPUT.EQP_MNT_FUTURE)

EVENT_ID

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. (* inherited from FPSINPUT.EQP_MNT_FUTURE)

COUNTER_MAX

the maximum usage of this counter (* inherited from FPSINPUT.RTG_PROCESS_COUNTERS)

COUNTER_LEFT

the current available amount left of this counter (* inherited from FPSINPUT.RTG_PROCESS_COUNTERS)

COUNTER_MSG

the counter message on the durable (* inherited from FPSAPP.SCH_W_SCHED_DURABLE_INSPECT)