FPSINPUT.EQP_MNT_FAMILIES

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)

MNT_FAMILY

VARCHAR2(50)

N

MNT_FAMILY is assigned to each EQP_TYPE. Tools in the same MNT_FAMILY are similar and share the same maintenance schedule.

DAYS_TO_SHOW_EVENTS_IN_DASH

NUMBER(3)

Default 7 days to show the future events in Dashboard for this MNT_FAMILY, and users can define how many days to show this in Dashboard

FILTER_FROM_EQP_SUMMARIES

CHAR(1)

If this is Y then tools in this MNT_FAMILY will not be included in the EQP/ETP state summary bar charts on the facility and module level. This applies to bar charts on the Operations, Equipment, and Performance tabs of the Dashboard. EQP/ETP state summaries will still be available for these tools on the process family and tool level.

MNT_MODULE

VARCHAR2(12)

N

MNT_MODULE is the module responsible for maintaining the tool and is a property of MNT_FAMILY. See comments on the module column in GEN_MODULES for how it relates to eqp_module and mnt_module.

MNT_WORK_AREA

VARCHAR2(50)

This field is only used for custom reporting but it gives us one more field to assign each mnt_family to a work area which is more specific that the mnt_module.