Data Dictionary
>
FPSINPUT Views
> FPSINPUT.WIP_WAFER_HIST_LOOP
View FPSBASE.CHK_PROC_CARRIER_LOCATIONS
This view identifies problems with consistency or synchronization between two fundamental components of our real-time ETL: FPSINPUT.WIP_EVENT_HIST: single-source-of-truth for what LOTs (and, optionally DURABLEs) are processing on what TOOLs at DATA_DATE FPSINPUT.MHS_CARRIERS: single-source-of-truth for the current physical location of LOTs and, in conjunction with FPSINPUT.RTG_DURABLES, DURABLEs In FPS location terminology, if a (LOT|DURABLE) is currently processing on a TOOL, then the CARRIER holding that (LOT|DURABLE) must have a STATION matching the TOOL: MHS_CARRIERS.LOCATION -> MHS_LOCATIONS.LOCATION select .STATION == WIP_LOT_PLUS.TOOL If these are mismatched, it indicates a lack of consistency or synchronization in the ETL. Some degree of lag is unavoidable, because: (a) There may be a lag in the underlying factory systems (b) We (currently) load WIP_EVENT_HIST in a batched stream on a finite interval, while MHS_CARRIERS and RTG_DURABLES refresh on a finite interval. Due to (a) and/or (b) we may, for example, load a begin-processing event for some (TOOL, LOT, DURABLE) before we load the updated locations of the lot-carrier or durable-carrier. In the interim, we will have a logical inconsistency insofar as we believe that the (LOT, DURABLE) are processing on TOOL -- but physically located elsewhere. ---------------------------------------- This view attempts to describe such inconsistencies for currently-processing WIP. When the STATION of a (LOT|DURABLE)-carrier's LOCATION does not match the TOOL where that (LOT|DURABLE) is currently processing: (LOT|DUR)_CARRIER_LOCATION_PROBLEM: describes the problem qualitatively (LOT|DUR)_CARRIER_LOCATION_LAG_MIN: the lag, in minutes, between the UPDATED_INST of the CARRIER's LOCATION and the BEG_PROC_INST on the TOOL. When this value is small and positive, e.g.: 0 < lag_min < 3 * GREATEST(WEH_update_interval, carrier_location_update_interval), then the lag may be due to one of the "unavoidable" reasons above. However, if the value is >>0 or <<0, it indicates a more serious problem. ----------------------------------------
|
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) |
|
TOOL |
Tool is generally just the main tool. The exception is when different entities on the tool run completely independently and it is physically impossible to run wafers of the same lot across multiple entities. In this exception case, we may want to assign the entities to different eqp_types and therefore we should define each entity as a tool. Please note that when we do this there is no indication whatsoever that these different entities are on the same tool. (* inherited from FPSINPUT.EQP_TOOLS) |
|
LOT_CARRIER_LOC_BEHIND_WEH_MIN |
|
|
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) |
|
LOT_CARRIER |
|
|
LOT_CARRIER_STATION |
|
|
DUR_CARRIER_LOC_BEHIND_WEH_MIN |
|
|
DURABLE |
Durables are either reticles for Litho or probe cards for Wet or Sort. A durable can either be in a carrier or at a location without a carrier. (* inherited from FPSINPUT.RTG_DURABLES) |
|
DURABLE_CARRIER |
The durable carrier ID of the durable required for this carrier to process. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT) |
|
DURABLE_CARRIER_STATION |
|
|
LOT_CARRIER_LOC_PROBLEM |
|
|
DUR_CARRIER_LOC_PROBLEM |
|
|
ROUTE |
Route that has threading requirements (* inherited from FPSINPUT.RTG_STEP_THREADING) |
|
STEP |
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. (* inherited from FPSINPUT.RTG_ROUTE_STEPS) |
|
STEP_ENT_INST |
Time when the lot entered the step. (* inherited from FPSBASE.WIP_LOT_HIST) |
|
LOT_CARRIER_LOCATION |
|
|
LOT_CARRIER_LOC_INST |
|
|
LOT_CARRIER_CLASS |
|
|
DURABLE_CARRIER_LOCATION |
|
|
DURABLE_CARRIER_LOC_INST |
|
|
DURABLE_CARRIER_CLASS |
|
|
DURABLE_POD_FAMILY |