Data Dictionary
>
FPSINPUT Views
> FPSINPUT.WIP_WAFER_HIST_LOOP
View FPSADMIN.RECENT_SPEED_HIST
Simple view to quickly get data from recent speed tests. For summarization and analysis of speed tests on the 3min/Realtime job please use RECENT_SPEED_TESTS which combines data from recent speed tests with inserted_time from three FPSINPUT history tables. Here is a query for summarizing speed tests specifically on the critical UPDATE_WIP_STEP_FUTURE procedure which is not quite useful enough to merit its own view: select round_ten_min, speed_group, count(*) as num_total, count(case when seconds > 0.5 and seconds < 1 then 1 end) as num_half_sec, count(case when seconds >= 1 and seconds < 2 then 1 end) as num_one_sec, count(case when seconds > 2 then 1 end) as num_two_plus_sec, round(count(case when seconds > .5 then 1 end) / count(*) * 100, 1) as pct_over_half_sec, sum(seconds) as total_sec, round(sum(case when seconds > .5 then seconds end) / sum(seconds) * 100, 1) as pct_of_total_sec_from_slow, round(sum(seconds) / count(*) * 1000) as avg_millisec, round(sum(case when seconds <= .5 then seconds end) / count(case when seconds <= .5 then 1 end) * 1000) as avg_millisec_under_half, round(sum(case when seconds > .5 then seconds end) / count(case when seconds > .5 then 1 end) * 1000) as avg_millisec_over_half from ( select trunc((cast(ts as date) - trunc(sysdate)) * 144) / 144 + trunc(sysdate) as round_ten_min, h.* from recent_speed_hist h where speed_class = 'UPDATE_WIP_STEP_FUTURE' and ts > trunc(sysdate, 'HH') - 1/24 ) group by round_ten_min, speed_group order by speed_group desc, round_ten_min desc;
|
Column |
Comment |
|---|---|
|
TS |
|
|
START_TS |
|
|
SECONDS |
|
|
SPEED_CLASS |
|
|
SPEED_GROUP |
|
|
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 |
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) |
|
INST |
Time when the event occurred. (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
LOT_SEQ_WITHIN_SEC |
For rows with identical timestamps, sequence records to get proper sequence (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
CHAR_VALUE1 |
|
|
CHAR_VALUE2 |
|
|
NUM_VALUE1 |
|
|
NUM_VALUE2 |
|
|
INST_VALUE1 |
|
|
INST_VALUE2 |
|
|
VALUE_DEFINITIONS |