FPSINPUT.DASH_P_QUEUE_TIMER_HIST

Data Dictionary

FPSINPUT Views

> FPSINPUT.WIP_WAFER_HIST_LOOP

View FPSAPP.DASH_P_QUEUE_TIMER_HIST

Summary view of queue timer history information for completed timers. One row for each facility, route, start step, and end step combination, along with relavent timer information. It is possible for a lot to restart and be brought back to the beginning of a timer loop. This would show as a separate record with the same lot and timer id. You will only see one instance for each route, start step, end step, timer id combination. Sometimes a route will be updated or a step renamed. The timer id will get deleted and a new timer id will be generated in the ETL

Column	Comment
TIMER_START_INST
TIMER_END_INST
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)
ROUTE	Route that has threading requirements (* inherited from FPSINPUT.RTG_STEP_THREADING)
START_STEP	Start step that will impact the future thread step rank in RTG_TOOL_ASSIGNMENT_LOT (* inherited from FPSINPUT.RTG_STEP_THREADING)
END_STEP	The step upon move out where the WIP balance limit is no longer applied (* inherited from FPSINPUT.RTG_STEP_BALANCE)
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)
TIMER_ID	Unique number representing the queue timer to index with other tables. Automatically populated with RTG_QUEUE_TIMERS_ID_SEQ sequence. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)
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)
DEFINED_TIMER_LENGTH_HRS
ACTUAL_TIMER_LENGTH_HRS
TIME_OVER_UNDER
DID_EXPIRE
COUNT_EXPIRED_TIMERS
COUNT_TOTAL_TIMERS
PROCESS_MODULE_START
PROCESS_MODULE_END
PROCESS_FAMILY_START
PROCESS_FAMILY_END
OPERATION_START
OPERATION_END
ROUTE_FAMILY	Route_family indicates that all routes within the family have similar or even identical steps and have the same segments. At facilities where various prds share the same route it is likely that the route will be the route_family. This is sometimes referred to as the main process flow. It is used on Segment Summary and Line Viewer to group similar routes. (* inherited from FPSINPUT.RTG_ROUTE_FAMILIES)
ROUTE_GROUP	Route_group is the parent of route_family. Route_group is used on the Dashboard and other applications as a large grouping for filtering. At many sites this is referred to as technology. (* inherited from FPSINPUT.RTG_ROUTE_GROUPS)
SCHED_GROUP_START
SCHED_GROUP_END
WORK_WEEK	Name of work week must be unique and can be in any format as long as it is display friendly since this is what we show everywhere. (* inherited from FPSINPUT.CAL_WORK_WEEKS)
START_PLAN_DAY	Plan days must be 24 hours in length and the start of the plan day must be the start of one of the shifts. Contrast this to plan day which is independent of shift. (* inherited from FPSINPUT.CAL_PLAN_DAYS)