Data Dictionary
>
FPSINPUT Views
> FPSINPUT.WIP_WAFER_HIST_LOOP
View FPSAPP.DASH_REF_P_PROCESS_SUBFAMILIES
Information on process_subfamilies plus the Bottleneck Score. Bottleneck Score is the percentage of the goal expected to be achieved by the end of the shift assuming that all tools in the family which are currently up remain up and tools which are currently down remain down. A score under 100% means we do not expect to meet the goal while a score over 100% means that we expect to exceed the goal. Since a tool can be in more than one process_submfamily, we use the use percent optimizer linear program to determine how much of each process_subfamily goal remaining should be done by each tool. Note that we group by process_subfamily rather than by the full GP grouping so this will work even with est goals.
|
Column |
Comment |
|---|---|
|
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) |
|
PROCESS_SUBFAMILY |
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. (* inherited from FPSBASE.RTG_ROUTE_STEPS_PLUS) |
|
PROCESS_FAMILY |
See https://help.inficonims.com/display/DW/Guide+to+Process+Families. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES) |
|
PROCESS_GROUP |
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. (* inherited from FPSINPUT.RTG_PROCESS_GROUPS) |
|
MODULE |
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. (* inherited from FPSINPUT.GEN_MODULES) |
|
MODULE_DISPLAY |
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. (* inherited from FPSINPUT.GEN_MODULES) |
|
TOOLS |
|
|
SORT_ORDER |
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. (* inherited from FPSINPUT.GEN_FACILITIES) |
|
GOAL_COMPLETES |
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. (* inherited from FPSINPUT.WIP_GOALS_PER_SHIFT) |
|
QTY_COMP |
|
|
WIP_OR_COMING |
|
|
GOAL_WILL_NOT_ARRIVE |
|
|
GOAL_REM |
|
|
GOAL_COMPLETES_DAY |
|
|
QTY_COMP_DAY |
|
|
WIP_OR_COMING_DAY |
|
|
GOAL_WILL_NOT_ARRIVE_DAY |
|
|
GOAL_REM_DAY |
|
|
NUM_TOOLS_UP |
|
|
NUM_TOOLS_DOWN |
|
|
NUM_TOOLS_UP_ADDL_SHIFT |
|
|
NUM_TOOLS_UP_ADDL_DAY |
|
|
UTIL_OF_AVAIL |
|
|
AVG_UPH |
|
|
AVG_UPH_DAY |
|
|
EST_COMPLETES |
|
|
EST_COMPLETES_DAY |
|
|
BOTTLENECK_SCORE |
|
|
DAY_BOTTLENECK_SCORE |
|
|
BOTTLENECK_SCORE_HOVER_MSG |
|
|
DAY_BOTTLENECK_SCORE_HOVER_MSG |