FPSAPP.ECT_FOR_ROUTE_STEPS

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)

ROUTE

VARCHAR2(256)

N

Route that has threading requirements (* from FPSINPUT.RTG_STEP_THREADING)

STEP

VARCHAR2(256)

N

A single processing step within a route representing a single tool visit. Step is often a very complex string and should rarely be displayed. Instead we should use process_display. (* from FPSINPUT.RTG_ROUTE_STEPS)

COMMIT_STEP_SEC

NUMBER(7)

COMMIT_STEP_SEC_TO_EOL

NUMBER(11)

ENDED_SEC_COMP_FULL_WAVG

NUMBER(7)

EST_SMP_PCT

NUMBER(5,2)

Smp_pct tells you what percentage of the lots complete on a tool. Some sites skip steps by jumping over them so we see the lot move from step 3 to step 5 and we only know that it jumped step 4 because step 4 is on the route between 3 and 5. Other sites skip steps by moving lots into them and then moving them out a second later so we see a move from 3 to 4 at 11:11:11 and a move from 4 to 5 at 11:11:12. We do not care how it is done but just that the lot did not process at step 4 -- and to be more specific that no tool capacity is required to process this lot at step 4 and no cycle time is accumulated at step 4. (* from FPSBASE.WIP_GOAL_LOT_SHIFT)

EST_TRANSIT_SEC

NUMBER(5)

FIFO_STEP_SEC

NUMBER(7)

FIFO_STEP_SEC_TO_EOL

NUMBER(11)

This can be used for critical ratio to avoid the following situation. Lot A of prd A and lot B of prd B are both at the same step on the same route. Plan CT for A is 40 plan CT for B is 60. Due date for A is in 41 days. Due date for B is in 59 days. Normal CR says A is one day ahead and B is one day behind so run B first. But this is insane because both are on the same route with exactly the same steps coming up and B is only "behind" because of a lower expectation. We should run A first. If we use FIFO then both are something like 50 days CT and A is 9 days behind and B is 9 days ahead. However there is a problem with this strategy because we would basically let B sit around and do nothing for 20 days until it was also 40 days and then have to run it at the same rate. So this is not perfect either. (* from FPSBASE.CTM_SUMMARY)

HOLD_SEC_FOR_WSF

NUMBER(7)

HOLD_SEC_FOR_WSF_TO_EOL

NUMBER(11)

LINE_YIELD_PCT_TO_EOL

NUMBER(6,3)

Line yield percentage to end of line is the percentage of units expected to successfully complete the remaining steps on the route. Normally we multiply the line yield of all remaining steps for the Capacity Model but entering a value in this OVR table manually overrides that calculated number. (* from FPSINPUT.RTG_ROUTE_STEP_EQPTYPE_OVR)

PROC_SEC_COMP_FULL_WAVG

NUMBER(7)

STEP_SEC_LONG_WAVG_TO_EOL

NUMBER(11)

STEP_SEC_NOHLD_RT_WSF

NUMBER(7)

STEP_SEC_NOHLD_RT_WSF_TO_EOL

NUMBER(11)

TARGET_STEP_SEC

NUMBER(7)

TARGET_STEP_SEC_TO_EOL

NUMBER(11)

TCT_SEC

NUMBER(7)

Theoretical cycle time in seconds (* from FPSBASE.WIP_LOT_HIST)

TCT_SEC_TO_EOL

NUMBER(11)

TOTAL_COMMIT_CT_DAYS

NUMBER(7,3)

TOTAL_TARGET_CT_DAYS

NUMBER(7,3)