FPSAPP.DASH_P_PROCESS_SUBFAMILIES

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)

PROCESS_SUBFAMILY

VARCHAR2(100)

N

Route step family is used for the Dashboard to separate processes in a process family based on shared but limited assignments. It is also the base for GP subfamily. (* from FPSBASE.RTG_ROUTE_STEPS_PLUS)

PROCESS_FAMILY

VARCHAR2(50)

N

See https://help.inficonims.com/display/DW/Guide+to+Process+Families. (* from FPSINPUT.RTG_PROCESS_FAMILIES)

AVG_UPH

NUMBER

AVG_UPH_DAY

NUMBER

BOTTLENECK_SCORE

NUMBER

BOTTLENECK_SCORE_HOVER_MSG

VARCHAR2(3999)

DAY_BOTTLENECK_SCORE

NUMBER

DAY_BOTTLENECK_SCORE_HOVER_MSG

VARCHAR2(3999)

EST_COMPLETES

NUMBER

EST_COMPLETES_DAY

NUMBER

GOAL_COMPLETES

NUMBER

Completes goal for the current shift. Typically we calculate either completes or moves goal depending on the site logic and then either multiply moves by est_smp_pct to get completes or divide completes by est_smp_pct to get moves. (* from FPSINPUT.WIP_GOALS_PER_SHIFT)

GOAL_COMPLETES_DAY

NUMBER

GOAL_REM

NUMBER

GOAL_REM_DAY

NUMBER

GOAL_WILL_NOT_ARRIVE

NUMBER

GOAL_WILL_NOT_ARRIVE_DAY

NUMBER

MODULE

VARCHAR2(12)

N

Modules are departments of people who manage certain areas of the fab. The modules are assigned ownership of a set of tools to operate and maintain as well as steps on the route that they are responsible for executing. Since many of our tables include tool and step information together, we must distinguish between the owner of the step (WIP_MODULE), the owner of the operation of the tool (EQP_MODULE), and the owner of the maintenance of the tool (MNT_MODULE). WIP_MODULE is used to credit moves and set goals. Each route-step is assigned to a process family and then its wip_module is defined by the process family. EQP_MODULE is used to group tools particularly for tool performance reporting. Similar to WIP, each tool is dynamically assigned to a process family based on its assignments and then its eqp_module is defined by the process family. MNT_MODULE is usually the same as EQP_MODULE but unlike EQP_MODULE is not dependent on assignments but only on the EQP hierarchy. Each tool is assigned to an eqp_type and each eqp_type is assigned to a mnt_family and each mnt_family is assigned to a mnt_module. (* from FPSINPUT.GEN_MODULES)

MODULE_DISPLAY

VARCHAR2(20)

N

The name of the module displayed on all dashboards and reports. We allow a longer more descriptive name here although often this will be the same as the module. (* from FPSINPUT.GEN_MODULES)

NUM_TOOLS_DOWN

NUMBER

NUM_TOOLS_UP

NUMBER

NUM_TOOLS_UP_ADDL_DAY

NUMBER

NUM_TOOLS_UP_ADDL_SHIFT

NUMBER

PROCESS_GROUP

VARCHAR2(36)

N

Process group is the critical field where tools and processes come together for the purposes of Scheduler. Process group is in both EQP_TOOLS for the tools and in RTG_PROCESSES for processes. Ideally all tools that run the same set of processes with no crossover including back-up and emergency tools would be in the same process group but it is important to note that this is not technically required for Scheduler as long as all process groups are in the same sched group. (* from FPSINPUT.RTG_PROCESS_GROUPS)

QTY_COMP

NUMBER

QTY_COMP_DAY

NUMBER

SORT_ORDER

NUMBER

This is used to sort within the grouping. SORT_ORDER always has a deferrable unique key to ensure uniqueness while allowing the user to make changes without erroring until the commit is attempted. Because of this you must be careful to not violate the unique key otherwise you will lose all of your edits. (* from FPSINPUT.GEN_FACILITIES)

TOOLS

VARCHAR2(1000)

UTIL_OF_AVAIL

NUMBER

WIP_OR_COMING

NUMBER