Data Dictionary
>
FPSBASE Views
> FPSBASE.WIP_WAFER_HIST_LOOP
View FPSBASE.WIP_REF_FLUSH_ADD_SHUTD
See comments in WIP_REF_FLUSH view for the entire WIP_FLUSH series. The logic in this particular view is pretty crazy but mostly mechanical. In the future, could potentially be replaced by a recursive program but for now we just do the same logic for each of the next n upcoming shutdowns at the site. We must react to the first shutdown and adjust all times for all facilities and then move on the second shutdown using the adjusted information. And so on for each of the n shutdowns. So what is n? Honestly it is because Oracle hung and would not compile this view if we tried too many loops. At one site, seven was fine but it hung at eight. At another site, three was fine, six barely succeeded but took 90 seconds to create the view, and seven hung. At sites that normally run 24x7 three is plenty (in fact one or rarely two would be enough) but at sites with a standard weekly shutdowns (i.e. facility does not work weekends) then more loops are needed. Seven is the max but that still means that only the next seven weeks are perfectly accurate. If we even get a site with nightly shutdowns (i.e. facility only operates during daytime) then we will need to review a whole bunch of logic in DWH including this.
|
Column |
Comment |
|---|---|
|
LOT |
A lot is a group of units that process together. Usually lot_id or lot_number in MES. All units in a lot are in the same carrier but there may be multiple lots in a carrier. (* inherited from FPSINPUT.WIP_LOTS_STATIC) |
|
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) |
|
PRD |
Prd determines the route which is used to process the lot in the facility and what tools, recipes, durables, etc. can be used at each step. Prd also determines the next facility for the lot when it finishes its route. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* inherited from FPSINPUT.RTG_PRDS) |
|
BANK |
Lots which are not on a route are considered in a bank and the bank name indicates why the lot is off route. Bank must be NA for lots which are on a route. Our standard filter for active lots is bank = NA. (* inherited from FPSINPUT.RTG_BANKS) |
|
START_INST_NOHOLD_FOR_WSF |
|
|
EOL_INST_NOHOLD_FOR_WSF |
|
|
START_INST_FULL_WAVG |
Date/time when the lot is estimated to start the specified route/bank using weighted average cycle time from the Full period. For the current route/bank this is the date/time when it started. (* inherited from FPSBASE.WIP_FLUSH) |
|
EOL_INST_FULL_WAVG |
Date/time when the lot is estimated to finish the specified route/bank using weighted average cycle time from the Full period. (* inherited from FPSBASE.WIP_FLUSH) |
|
START_INST_LONG_WAVG |
Date/time when the lot is estimated to start the specified route/bank using weighted average cycle time from the Long period. For the current route/bank this is the date/time when it started. (* inherited from FPSBASE.WIP_FLUSH) |
|
EOL_INST_LONG_WAVG |
Date/time when the lot is estimated to finish the specified route/bank using weighted average cycle time from the Long period. (* inherited from FPSBASE.WIP_FLUSH) |
|
START_INST_7D_WAVG |
Date/time when the lot is estimated to start the specified route/bank using weighted average cycle time from the last 7 days. For the current route/bank this is the date/time when it started. (* inherited from FPSBASE.WIP_FLUSH) |
|
EOL_INST_7D_WAVG |
Date/time when the lot is estimated to finish the specified route/bank using weighted average cycle time from the last 7 days. (* inherited from FPSBASE.WIP_FLUSH) |
|
START_INST_7D_MED |
Date/time when the lot is estimated to start the specified route/bank using median cycle time from the last 7 days. For the current route/bank this is the date/time when it started. (* inherited from FPSBASE.WIP_FLUSH) |
|
EOL_INST_7D_MED |
Date/time when the lot is estimated to finish the specified route/bank using median cycle time from the last 7 days. (* inherited from FPSBASE.WIP_FLUSH) |
|
START_INST_2D_WAVG |
Date/time when the lot is estimated to start the specified route/bank using weighted average cycle time from the last 2 days. For the current route/bank this is the date/time when it started. (* inherited from FPSBASE.WIP_FLUSH) |
|
EOL_INST_2D_WAVG |
Date/time when the lot is estimated to finish the specified route/bank using weighted average cycle time from the last 2 days. (* inherited from FPSBASE.WIP_FLUSH) |
|
START_INST_FIFO |
Date/time when the lot is estimated to start the specified route/bank using FIFO cycle time. For the current route/bank this is the date/time when it started. (* inherited from FPSBASE.WIP_FLUSH) |
|
EOL_INST_FIFO |
Date/time when the lot is estimated to finish the specified route/bank using FIFO cycle time. (* inherited from FPSBASE.WIP_FLUSH) |
|
START_INST_TARGET |
Date/time when the lot is estimated to start the specified route/bank using Target cycle time. For the current route/bank this is the date/time when it started. (* inherited from FPSBASE.WIP_FLUSH) |
|
EOL_INST_TARGET |
Date/time when the lot is estimated to finish the specified route/bank using Target cycle time. (* inherited from FPSBASE.WIP_FLUSH) |
|
START_INST_COMMIT |
Date/time when the lot is estimated to start the specified route/bank using Commit cycle time. For the current route/bank this is the date/time when it started. (* inherited from FPSBASE.WIP_FLUSH) |
|
EOL_INST_COMMIT |
Date/time when the lot is estimated to finish the specified route/bank using Commit cycle time. (* inherited from FPSBASE.WIP_FLUSH) |
|
DAYS |