FPSAPP.CM_P_SCENARIOS_EQPTYPES

SCENARIO

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)

EQP_TYPE

Each tool is assigned an EQP_TYPE and all tools in the same type are identical meaning that they should run at the same throughput when running the same process with the same chamber type count. We also expect similar availability since these tools are identical. However tools in the same EQP_TYPE may have different chamber configurations and may run different groups of processes. (* inherited from FPSINPUT.EQP_TYPES)

NUM_CAP_ENTS

PLAN_UTIL

Planned utilization used in goal planner and capacity model. Must be less than plan_avail. (* inherited from FPSINPUT.EQP_TYPES)

WORK_WEEK

Name of work week must be unique and can be in any format as long as it is display friendly since this is what we show everywhere. (* inherited from FPSINPUT.CAL_WORK_WEEKS)