FPSAPP.DASH_P_WIP_STEP_FUTURE_SCHED

Data Dictionary

FPSAPP Views

> FPSAPP.WIP_WAFER_HIST_LOOP

View FPSAPP.DASH_P_WIP_STEP_FUTURE_SCHED

This view adds all Scheduler and NextMove information from WIP_STEP_FUTURE_SCHED for use in Dashboard lot views when necessary. This information must be filtered or joined on lot+facility+route+step like this: select * from dash_p_wip_lots w left join dash_p_wip_step_future_sched s on s.lot = w.lot and s.route = w.route and s.step = w.step and s.facility = w.facility; Please note that this view breaks the normal rule of only including columns necessary for the Dashboard and instead includes all columns from WIP_STEP_FUTURE_SCHED except for process, tool_for_tts, and job_id which are already in DASH_P_WIP_LOTS and three long details columns. However please only query the columns which are currently needed in the Dashboard query so that we can drop columns which are not used in the future as necessary.

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)
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)
ROUTE	Route that has threading requirements (* inherited from FPSINPUT.RTG_STEP_THREADING)
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)
NUM_STEPS_AWAY	Number of steps away not including steps which we know will be skipped nor those which we estimate will be skipped at least x pct of the time. This x value is configurable in GEN_FACILITIES using the smp_pct_for_num_steps_away column. (* inherited from FPSBASE.WIP_STEP_FUTURE)
PROCESS_FAMILY	See https://help.inficonims.com/display/DW/Guide+to+Process+Families. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)
PROCESS_MODULE	WIP_MODULE is used to credit moves and set goals. See comments on the module column in GEN_MODULES for info on this column and how it relates to eqp_module and mnt_module. (* inherited from FPSBASE.RTG_ROUTE_STEPS_PLUS)
WSF_ACTION
IS_RESERVED	This flag indicates if the carrier has been reserved to a tool. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)
SCHED_TOOL	the tool from the first lot that scheduled (* inherited from FPSAPP.SCH_W_SCHED_DURABLE_INSPECT)
NO_SCHED_TOOL_REASON
SCHED_POD_KIT_START_INST
SCHED_POD_KIT_READY_INST
SCHED_POD_FIRST_DISP_INST
SCHED_STEP_BEG_INST
SCHED_DISP_INST
SCHED_START	The first start time for the durable to be used (* inherited from FPSBASE.RTG_DURABLE_FUTURE_SCHED)
SCHED_END
SCHED_COMP_INST
SCHED_DURABLE
SCHED_CARRIER
SCHED_CH_TO_USE	Please note that the Scheduler often populates this with M which indicates the main tool therefore we often should filter out a value of M when using this value since that it not a valid chamber combination. When this is populated with any value other than M then we use this as est_ch_used rather than calculating with GET_CH_ALLOWED_STATUS or GET_CH_PATH_STATUS. (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
SCHED_JOB_ID
SCHED_IS_RESERVED
SCHED_QTY_IN_JOB
SCHED_CARRIERS_IN_JOB
SCHED_EET_SEC
SCHED_SCORE
SCHED_RESERVE_INST	The actual time the lot was reserved by the scheduler will be helpful for compliance and debugging. (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
SCHED_UNRESERVE_INST
SCHED_ALLOWED_TOOL_LIST
SCHED_RECIPE
SCHED_SETUP
SCHED_BATCH_CRITERIA	Scheduler will populate the batch criteria data here when it has info (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
SCHED_SORT_ON_TOOL
SCHED_SORT_ON_DURABLE
DURABLE_LAST_SCHED_END
DURABLE_LAST_SCHED_TOOL
SCHED_STEP_ENT_INST
SCHED_STEP_BEG_STATION
SCHED_STEP_BEG_BAY
SCHED_EXTL_MODEL_ID	to indicate the external model id of the tool that this lot is scheduled to (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
SCHED_EXTL_MODEL_STATE	to indicate the external model state of the tool that this lot is scheduled to (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
SCHED_IS_EXCLUSIVE_CHAMBER	to indicate if the chamber is exclusive on the tool where this lot scheduled to (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
SCHED_RQD_PORT_GROUP	to indicate the required port group information of the tool that this lot scheduled to (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
MANL_RESERVE_INST	The actual time the lot was manually reserved by NextMove will be helpful especially for compliance and debugging to have these columns. In the absence of the Scheduler this will also determine the order to run the reserved lots. (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
MANL_RESERVE_TOOL	Stores tool reserved by NextMove (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
MANL_RESERVE_QTY_IN_JOB
MANL_RESERVE_JOB_ID
MANL_RESERVE_USERNAME
MANL_RESERVE_CH_TO_USE	List of chambers to use for processing set by NextMove when lot is reserved. (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
MANL_UNRESERVE_INST
EXTL_RESERVE_INST
EXTL_RESERVE_TOOL
EXTL_RESERVE_QTY_IN_JOB
EXTL_RESERVE_JOB_ID
EXTL_RESERVE_USERNAME
EXTL_RESERVE_CH_TO_USE
EXTL_UNRESERVE_INST
EXTL_DEST_LOCATION	This column will have the destination location for the lot (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
EXTL_TRANSPORT_MODE	Name of the site transport mode which represents how material is moved from one location to another. (* inherited from FPSINPUT.MHS_EXTERNAL_TRANSPORT_MODES)
EXTL_RECIPE
EXTL_SETUP
EXTL_ADDL_INFO	This will have any additional lot info needed by the external system (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
EXTL_DISP_INST	Time by when the external system recommends that the job must be dispatched. (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
EXTL_START	Time by when the external system recommends that the job will begin processing. (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
EXTL_END	Time by when the external system recommends that the job will end processing. (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
EXTL_IS_RESERVED	Flag indicated whether the external system has reserved the lot to the tool. If not we still move to the destination. (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
WEH_RESERVE_INST
WEH_RESERVE_TOOL
WEH_RESERVE_QTY_IN_JOB
WEH_RESERVE_JOB_ID
WEH_RESERVE_FIRST_LOT_IN_JOB
WEH_RESERVE_OPERATOR
WEH_RESERVE_ACTUAL_CH_USED
WEH_RESERVE_ACTUAL_MACH_RCP
WEH_END_PROC_INST
EST_MACHINE_RECIPE	Estimated machine recipe what we estimate will be the machine recipe based on information from the Recipe Management System. It is used in combination with process for throughput calculations and setup change penalty calculations. It is not necessary to estimate for all processes since this is always used in combination however it needs to be NA rather than blank since it is part of the primary key of most THP tables. Hopefully when this is not NA it should match the actual machine recipe logged for each lot during processing. (* inherited from FPSINPUT.RTG_TOOL_ASSIGNMENTS)
RQD_SETUP	Rqd_setup is determined by ovr_rqd_setup in RTG_TOOL_ASSIGNMENTS and use_process_as_rqd_setup and use_est_mach_rcp_as_rqd_setup from EQP_TYPES. The latter two columns allow us to easily specify for an eqp_type that setup times should be calculated by process or est_machine_recipe. For traditional setups that are a group of recipes we use ovr_rqd_setup. (* inherited from FPSBASE.WIP_LOT_HIST)
BATCH_CRITERIA	Lots that can run on the same batch TOOL and have the same value of BATCH_CRITERIA can run together in a batch. Therefore this is a critical column for scheduling on batch tools. If BATCH_CRITERIA is not populated, Scheduler defaults to the assumption that any WIP with the same EST_MACHINE_RECIPE can be batched together. Keep in mind that many MESs have additional constraints on batching (for example, that all WIP in a batch has the same SCRIPT_ID) and these must be incorporated into BATCH_CRITERIA to ensure that the batches are allowed by the MES. (* inherited from FPSINPUT.RTG_TOOL_ASSIGNMENTS)
TTS_SOURCE
TTS_BAY	Bay of the tool where this carrier is reserved or scheduled. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)
TTS_PROCESS_FAMILY
EXTL_DO_NOT_MOVE	This column will decided whether NextMove will highlight to move or override it (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
EXTL_SHOW_EXACT_DEST	This column will decided whether NextMove will show the destination Bay or the exact destination. (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
EXTL_REQ_EXACT_DEST	This column will decided whether NextMove use alternates and station assignments or ignore them. (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
SCHED_LOT_TRANSIT_SEC	to indicate the transit time needed to move the lot to the scheduled tool (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
SCHED_PROCESS_CHANGE_SEC	to indicate the process change time needed to run this lot (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
SCHED_QUEUE_START_DELAY_INST	to indicate the earliest time that to start to process the queue-start-step (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)
SCHED_WAIT_ETP_STATE	The only way for ETP to know that the Scheduler is asking to wait is for the Scheduler to populate this column indicating that the lot is scheduled but waiting for a particular reason. This column must be an exact etp_state value starting with SBY-IW so it has a check constraint and a foreign key on ETP_STATE_DIAGRAM. (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)