FPSBASE.WIP_STEP_FUTURE_PLUS

UPDATED_INST

Time when the record was updated according to the source data. Note this is not the time when the record was actually updated in this table - it will almost always be earlier. (* inherited from FPSINPUT.GEN_FACILITIES)

TRG_TIME

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)

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)

NUM_SEQ_AWAY

Number of steps away including all steps which will or might be skipped. We name this column seq because it is just the delta in seq_num between the current step and the future step. (* inherited from FPSBASE.WIP_STEP_FUTURE)

SEQ_NUM

Sequence number of step in route (* inherited from FPSINPUT.RTG_ROUTE_STEPS)

PROCESS

Process defines what occurs at a step. Different steps can share the same process if they are identical. Process should normally determine allowed tools and recipe although it can be overridden by step, route, prd, lot, and experiment for exceptions. Each process is dynamically assigned to one or more eqp_type-process_family combinations with use_pct. One process_family is determined to be primary. If grouping is done correctly, a process should only be one eqp_group with no crossover. (* inherited from FPSINPUT.RTG_PROCESSES)

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)

EARLIEST_STEP_ENT_INST

EXPECTED_STEP_ENT_INST

EARLIEST_COMP_INST

EXPECTED_COMP_INST

EST_DISP_INST_TOOL_FOR_TTS

EST_BEG_INST_TOOL_FOR_TTS

EST_END_INST_TOOL_FOR_TTS

END

END

END

NEXT_BEG_INST_TOOL_FOR_TTS

ABORT_INST

When a lot has begun processing on a tool and an event with event_type of ABORT is logged, abort_inst captures the time of the abort. If multiple aborts happen to the same lot, the last abort_inst is used. See description of ABORT ect_state for more details. (* inherited from FPSBASE.WIP_STEP_HIST)

ACTUAL_CH_USED

Here is where we can log the actual_ch_used directly if we know it. We have three ways to determine actual_ch_used in WIP_LOTS_REALTIME which populates WIP_STEP_HIST: 1) Log it directly in this colum for an event where the logged_entity is the main tool. 2) Log events to each of the chambers used in WIP_EVENT_HIST. 3) Log events to each of the chambers used in WIP_WAFER_HIST. (* inherited from FPSINPUT.WIP_EVENT_HIST)

ACTUAL_DURABLE_USED

Actual durable used as logged by the tool during processing of the lot. This can be a comma delimited string if multiple durables are used. (* inherited from FPSINPUT.WIP_EVENT_HIST)

ACTUAL_MACHINE_RECIPE

Machine recipe used to process the lot as logged during processing by the tool. (* inherited from FPSINPUT.WIP_EVENT_HIST)

AMHS_DESTINATION

The destination of a carrier when in transit or when a move is requested. This is an optional input value that comes from the AMHS. It is not where the carrier needs to go which we decide in MHS_DELIVERY_NEXT but rather where it is already going in the AMHS. If this value is blank then we know the carrier has no move requested. (* inherited from FPSINPUT.MHS_CARRIERS)

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)

BUNCH_ID

Chain lots together for Goal Planner (* inherited from FPSINPUT.WIP_LOTS_STATIC)

CANCEL_INST

Time when tool reservation or dispatch or perhaps even load or ready for the lot at the current step was cancelled. After cancel_inst the lot is available to any qualified tool immediately. (* inherited from FPSBASE.WIP_STEP_HIST)

CARRIER

RFID of the cassette or FOUP the lot is currently in. (* inherited from FPSINPUT.MHS_CARRIERS)

CARRIER_DISPLAY

CRITICAL_RATIO

The critical ratio (days until due / days of CT left) for the lot (* inherited from FPSAPP.SCH_W_H_S_LOTS)

CURR_BANK

CURR_BAY

Current bay of carrier. See column comment on BAY in FPSINPUT.MHS_BAYS for more information. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

CURR_BEG_PROC_INST

CURR_BUILDING

Current building of carrier. See column comment on BUILDING in FPSINPUT.MHS_BUILDINGS for more information. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

CURR_CARRIERS_IN_JOB

CURR_COMMON_STEP

CURR_COMP_TO_EARLIEST_ARRV_SEC

The comment on CURR_COMP_TO_EXPECTED_ARRV_SEC applies here too. The only difference is that this column is what we consider the earliest possible arrival rather than the expected arrival. (* inherited from FPSBASE.WIP_STEP_FUTURE)

CURR_COMP_TO_EARLIEST_COMP_SEC

CURR_COMP_TO_EXPECTED_ARRV_SEC

We use this numeric field rather than the date field EXPECTED_ARRV_INST but the date field depends on the estimated complete of the current step which depends on the current time. Therefore in order for EXPECTED_ARRV_INST to be accurate we would have to change it every second! Instead we use this field to store the seconds from the complete of the current step to the arrival which only needs to be updated when the lot changes steps. Then we do the calculations to get EXPECTED_ARRV_INST using the current time in the WIP_STEP_FUTURE_PLUS view. For all steps which are one step away, this value is always 0 which makes sense because the complete of the current step is the same as the arrival of the next step. (* inherited from FPSBASE.WIP_STEP_FUTURE)

CURR_COMP_TO_EXPECTED_COMP_SEC

CURR_END_PROC_INST

CURR_EST_CH_USED

CURR_EST_DURABLE_USED

CURR_EST_MACHINE_RECIPE

CURR_FIRST_LOT_IN_JOB

CURR_HOLD_NOTE

CURR_HOLD_TYPE

CURR_IS_STAGING_STEP

CURR_JOB_ID

CURR_LOGICAL_RECIPE

CURR_PRIORITY

The priority at the current step. As the lot moves along the route after LAST_STEP_CURR_PRTY it will revert to PLAN_PRIORITY. For example, timelink or sendahead priority is only temporary. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

CURR_PRIORITY_BG_COLOR

CURR_PRIORITY_DISPLAY

CURR_PRIORITY_REASON

An optional description of why the priority is set as it is. This is typically shown as additional information on pages related to priority lots. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

CURR_PRIORITY_SORT

CURR_PROCESS

CURR_PROC_STATE_DASH

CURR_PROC_STATE_DASH_DETAILS

CURR_PROC_STATE_DASH_DISPLAY

CURR_PROC_STATE_DASH_SORT_ORD

CURR_PROC_STATE_EVENT_ONLY

CURR_PROC_STATE_SCH

CURR_PROC_STATE_SCH_DETAILS

CURR_PROC_STATE_SCH_DISPLAY

CURR_PROC_STATE_SCH_SORT_ORDER

CURR_QTY

Current qty of the lot using quantity unit of the current facility. (* inherited from FPSBASE.WIP_FLUSH)

CURR_QTY_IN_JOB

CURR_QUEUE_STATUS

CURR_RECIPE_VERSION

CURR_ROUTE

CURR_RT_STEP_BANK_ENT_INST

CURR_STATION

See column comment on STATION in FPSINPUT.MHS_STATION_ALTERNATES for more information. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

CURR_STATION_TYPE

Current station type of carrier. See view MHS_LOCATIONS for more information. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

CURR_STEP

CURR_STEP_EARLIEST_COMP_INST

CURR_STEP_ENT_INST

CURR_STEP_EST_COMP_INST

CURR_TOOL

CUSTOMER

Customer who will accept shipment of the lot. Currently this only used for grouping and filtering but in the future we might want to allow a customer to view a Dashboard only including their products. (* inherited from FPSINPUT.GEN_CUSTOMERS)

DAYS_BEHIND

DISPATCHED_BY

DISPATCH_INST

Time when the lot indicated in the MES that it will process on the tool. As opposed to reserve, dispatch cannot be automatically undone. (* inherited from FPSBASE.WIP_STEP_HIST)

DUE_INST

To indicate the due date for this futuer start lot (* inherited from FPSINPUT.WIP_STARTS)

DURABLE_LAST_SCHED_END

DURABLE_LAST_SCHED_TOOL

EARLIEST_STEP_SEC

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)

EST_QTY_AT_ARRV

This column degrades the current qty by the estimated line yield at steps between the current step and future step so this represents the expected qty of the lot when it arrives to the future step. This is unlikely to be different than the current qty in a Fab but is quite important for Test/Sort/Assembly. (* inherited from FPSBASE.WIP_STEP_FUTURE)

EST_SEC_QTY_AT_ARRV

EST_SMP_PCT

Smp_pct tells you what percentage of the lots complete on a tool. Some sites skip steps by jumping over them so we see the lot move from step 3 to step 5 and we only know that it jumped step 4 because step 4 is on the route between 3 and 5. Other sites skip steps by moving lots into them and then moving them out a second later so we see a move from 3 to 4 at 11:11:11 and a move from 4 to 5 at 11:11:12. We do not care how it is done but just that the lot did not process at step 4 -- and to be more specific that no tool capacity is required to process this lot at step 4 and no cycle time is accumulated at step 4. (* inherited from FPSBASE.WIP_GOAL_LOT_SHIFT)

EXPECTED_STEP_SEC

EXPT_ID

Experiment identifier which indicates the lot will process differently that normal for its product on at least one step of the route. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

EXPT_VARIATION

Assigned to sibling lots to indicate which variation of the experiment will be performed on the lot. For example, variation 0 might get the normal recipe while variation 1 might get a different recipe then we can compare the different wafers in each split at a following measurement or test step. (* inherited from FPSINPUT.RTG_TOOL_ASSIGNMENTS_LOT)

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_DO_NOT_MOVE

This column will decided whether NextMove will highlight to move or override it (* 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)

EXTL_NEXT_STATION

EXTL_RESERVE_CH_TO_USE

EXTL_RESERVE_INST

EXTL_RESERVE_JOB_ID

EXTL_RESERVE_QTY_IN_JOB

EXTL_RESERVE_TOOL

EXTL_RESERVE_USERNAME

EXTL_START

Time by when the external system recommends that the job will begin processing. (* 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_UNRESERVE_INST

FIRST_FUT_HOLD_NOTE

FIRST_FUT_HOLD_NUM_STEPS_AWAY

FIRST_FUT_HOLD_STEP

FIRST_FUT_HOLD_TYPE

FUT_HOLD_NOTE_AT_STEP

FUT_HOLD_SEC_AT_STEP

FUT_HOLD_SEC_TO_ARRV

FUT_HOLD_TYPE_AT_STEP

GBL_SORT

Sorting used for dispatching or allocation systems to sort future start lots based on priority, critical ratio, etc. (* inherited from FPSINPUT.WIP_STARTS)

GOAL_BEGIN_INST

Time when the lot has to complete the current step to remain on schedule. (* inherited from FPSBASE.WIP_STEP_HIST)

GOAL_COMMENT

GOAL_COMP_INST

IS_BANK

IS_CURR

Boolean flag where Y indicates this row is for the current main route or product. Same as flush_seq_num = 1. (* inherited from FPSBASE.WIP_FLUSH)

IS_CURR_PRTY_HIGHLIGHTED

IS_FUTURE

This should be set to Y if the state does not apply immediately. Production runoff and alarms are two examples where we do not want to set this state in ETP until the tool misses the cascade and starts to lose productivity. (* inherited from FPSINPUT.EQP_L5_TRANSITION_STATES)

IS_HIGHLIGHTED_PRTY

This flag indicates if this priority should be highlighted on the dashboard. When we sort all priorities by priority_sort all Y should be first followed by all N. (* inherited from FPSINPUT.WIP_PRIORITIES)

IS_HOLD_CURR

IS_HOLD_UPCOMING

IS_IN_NMV_PICK_LIST

Set to Y if lot-step is within range to be displayed in NextMove Pick List according to hours/steps_to_schedule fields in GEN_FACILITIES (* inherited from FPSBASE.WIP_STEP_FUTURE)

IS_IN_PRTY_GANTT

IS_LOADED

IS_NEXT_STEP

IS_NMV_PRIORITY

This flag indicates if this priority should be emphasized in NextMove (* inherited from FPSINPUT.WIP_PRIORITIES)

IS_NONSTD

Our column to indicate non-standard processing at the step. For example, an experiment or a chain that is only active at a particular step or set of steps and then goes back to being normal for the route. If an experiment is severe enough that it affects the final product and has to be planned separately then it will be its own prd or planprd. (* inherited from FPSBASE.WIP_LOT_HIST)

IS_RESERVED

This flag indicates if the carrier has been reserved to a tool. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

IS_REWORK

Y indicates the lot is on a rework route after the event is logged. If a lot is reworked then returns to the main route and repeats some steps, is_rework will be N but we will count those steps as repeats. (* inherited from FPSINPUT.WIP_EVENT_HIST)

IS_REWORK_CURR

IS_SCHED

This flag indicates that lots in this group should be scheduled. This flag additionally causes TW groups to be included in WIP_STEP_FUTURE which they are normally not. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

IS_STAGING_STEP

We expect large amounts of WIP and long cycle times at staging steps. We still calculate cycle time like any other step but the important difference is that lots currently at a staging step are not counted as normal coming lots to future steps. Instead we show them in a special column labeled From Staging. (* inherited from FPSINPUT.RTG_ROUTE_STEPS)

IS_START

Boolean flag where Y indicates the lot is an upcoming start and not an existing lot. (* inherited from FPSBASE.WIP_FLUSH)

IS_STEP_AFTER_LOT_ASGN

IS_TW

Our standard filter to exclude test wafers is is_tw = N but what we really mean with this filter is to exclude any lots that do not add value for the facility. Lots which add value including sellable, development, and engineering and these lot groups should have is_tw set to N. Lots which do not add value are commonly grouped together and named "test wafers" which is why this flag is named is_tw. These include true test wafers like monitors and quals and dummies but also could include virtual lots used for training or testing, bare wafers, or really anything else including in the MES as a lot which does not add value. All of these lot groups should have is_tw set to Y. You could argue that the is_tw field might be more accurately named is_value or is_valuable or is_prod_eng_dev but is_tw is generally clear to most people. Plus it has the advantage that it is short which is nice given how frequently we use the is_tw = N filter. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

IS_TW_USE

Applicable to TW routes only. If N (default), then this step is part of the process of building the test wafer. If Y, then this step is one at which the TW is used for process characterization by the owning module. (* inherited from FPSINPUT.RTG_ROUTE_STEPS)

JOB_ID

Automatically set by trigger when the first lot of a job logs an event to the tool. (* inherited from FPSBASE.WIP_LOT_HIST)

LAST_HOLD_INST

Time when the lot was last placed on hold. (* inherited from FPSBASE.WIP_FLUSH)

LAST_KNOWN_LOCATION

Often when a carrier is in transit we do not know exactly where it is but we only know where it came from. In this case we might set the location to something generic like TRANSIT and the last known location to where it came from. (* inherited from FPSINPUT.MHS_CARRIERS)

LAST_KNOWN_LOCATION_INST

Time when the last_known_location was originally updated as the location of this carrier. This column and last_known_location are both updated by trigger. (* inherited from FPSINPUT.MHS_CARRIERS)

LAST_TOOL

For rework and scrap events we automatically look up the last tool where the lot processed including metrology tools. (* inherited from FPSBASE.WIP_LOT_HIST)

LAST_TOOL_BEG_INST

Time of the last event on the previous tool (including metrology) for the lot occurred. (* inherited from FPSBASE.WIP_LOT_HIST)

LINE_YIELD_PCT_TO_ARRV

LOCATION

Location of a carrier or lot or durable which comes directly from the tracking system used at the site. This could be a port or internal tool location or tool or rack or stocker or zero footprint storage or room or really anywhere. Many non-automated sites allow users to manually enter locations into their system. Therefore unless we know for sure that the source data implements a size limitation, it is recommended to always trim the value in the ETL to 32 characters to fit into the column size and avoid load errors. For ports, location is the full name of the port which is unique across the entire site and usually includes the tool name. Please see the comment in the port column which explains the difference between location and port. Rack locations are similar. (* inherited from FPSINPUT.MHS_RACK_LOCATIONS)

LOCATION_INST

Time when the carrier arrived at the location. (* inherited from FPSINPUT.MHS_CARRIERS)

LOT_FAMILY

Lot_family is a grouping of lot_type which is mainly use for goal planning. We set goals by family and are allowed to switch goals for different lots of different types within the family. We also report goal performance by family. (* inherited from FPSINPUT.WIP_LOT_FAMILIES)

LOT_GROUP

Lot_group is a grouping of lot_family and is the highest grouping in the lot type hierarchy. There should be only a few values for lot_group, i.e. Prod, Dev, TW. We group WIP and moves by lot_group on the dashboard and we group cycle time calculations by lot_group so this is an important field. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

LOT_TYPE

Lot_type is the base of the hierarchy that determines lot_family then lot_group. Ideally lot_type will come straight from the MES with little modification. (* inherited from FPSINPUT.WIP_LOT_TYPES)

LOT_TYPE_SORT_ORDER

MAIN_ROUTE

Primary route used by the prd. Excludes rework and alternate routing. We allow this column to be null in WIP_LOTS_VERIFY because we may not be certain what the main route is when we fix for missed events. In that event we trust the WIP_EVENT_HIST triggers has loaded the correct information into WIP_EVENTS_CURR_STEP. (* inherited from FPSINPUT.WIP_EVENT_HIST)

MAIN_ROUTE_FAMILY

Route family of the main route for the prd of the lot. (* inherited from FPSINPUT.WIP_OVR_OPER_MOVES_HIST)

MAIN_ROUTE_GROUP

Route group of main route. Often referred to as technology. (* inherited from FPSBASE.WIP_FLUSH)

MAIN_RT_OPER_ENT_INST

MAIN_RT_STEP

When lot is on a rework or alternate route, this is the step where it will return to the main route. We use this for planning purposes so we can calculate remaining steps. We allow this column to be null in WIP_LOTS_VERIFY because we may not be certain what the main route step is when we fix for missed events. In that event we trust the WIP_EVENT_HIST triggers has loaded the correct information into WIP_EVENTS_CURR_STEP. (* inherited from FPSINPUT.WIP_EVENT_HIST)

MAIN_RT_SEQ_NUM

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_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_JOB_ID

MANL_RESERVE_QTY_IN_JOB

MANL_RESERVE_TOOL

Stores tool reserved by NextMove (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)

MANL_RESERVE_USERNAME

MANL_UNRESERVE_INST

MEAS_RESULT

Result of measurement. For facilities not using FPS Sampling this value is for display purposes only and can be pass/fail or a number or anything. For facilities using FPS Sampling this field is used to dynamically adjust the sampling rules and must be a letter grade A-F. (* inherited from FPSINPUT.WIP_EVENT_HIST)

NMV_USE_DISP_INST

A flag that will help decided whether to use the start time or dispatch time. (* inherited from FPSINPUT.EQP_TYPES)

NO_SCHED_TOOL_REASON

NUM_SEQ_AWAY_W_DECIMAL

NUM_SEQ_TO_RETURN

NUM_SIBLING_LOTS

A count of other lots that were also split from the same parent. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

NUM_STEPS_TO_RETURN

OPER_ENT_INST

ORIG_DUE_INST

Original Due Date of this lot (* inherited from FPSINPUT.WIP_STARTS)

OVR_IS_QUEUE_ALLOWED

We stop lots from starting the first step in a queue timer when WIP is too high but this flag allows this specific lot to start despite this. Use for priority lots or sendahead lots or when we want to trickle lots into the timer. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

PARENT_LOT

The parent lot should ideally be the original parent but it could be the most recent parent if multiple splits have occurred. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

PLANPRD

Planning product used for all planning purposes. All lots with the same planprd are interchangeable to ship to the customer regardless of their prd, route, technology, wafer size, etc. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* inherited from FPSINPUT.RTG_PLANPRDS)

PLAN_PRIORITY

Permanent priority of the lot set in the MES generally by planning. (* inherited from FPSINPUT.WIP_EVENT_HIST)

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)

PREP_SEC

The time in seconds required to prepare the lot before track in. (* inherited from FPSINPUT.EQP_TYPES)

PROCESS_FAMILY

See https://help.inficonims.com/display/DW/Guide+to+Process+Families. (* inherited from FPSINPUT.RTG_PROCESS_FAMILIES)

PROCESS_GROUP

Process group is the critical field where tools and processes come together for the purposes of Scheduler. Process group is in both EQP_TOOLS for the tools and in RTG_PROCESSES for processes. Ideally all tools that run the same set of processes with no crossover including back-up and emergency tools would be in the same process group but it is important to note that this is not technically required for Scheduler as long as all process groups are in the same sched group. (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)

PROC_PORT_MODE

PRTY_CTM_GROUP

This is one of the primary keys of our CTM tables. We use this group rather than the priority because we often have several different priorities which are close and are expected to have the same cycle time. (* inherited from FPSINPUT.WIP_PRIORITIES)

PRTY_SCHED_SORT

READY_INST

Time when the lot was ready to be processed (e.g. after recipe downloaded). (* inherited from FPSBASE.WIP_STEP_HIST)

RESERVE_INST

Time when the lot was reserved to the tool either by Scheduler or external or manual reservation. As opposed to dispatch, reserve is only in the FPS DWH and therefore can be automatically undone. (* inherited from FPSBASE.WIP_STEP_HIST)

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)

SAH_CHAMBERS

Send ahead chambers (* inherited from FPSINPUT.WIP_LOTS_STATIC)

SAH_TOOL

Send ahead tool (* inherited from FPSINPUT.WIP_LOTS_STATIC)

SAH_TYPE

Send ahead type is primarily used to set lot_priority. We often want to prioritize a sendahead lot only to the metrology tool so we can get metrology as soon as possible and start processing more lots. (* inherited from FPSINPUT.WIP_SAH_TYPES)

SCHED_ALLOWED_TOOL_LIST

SCHED_BACKLOAD_INST

to indicate the the scheduled early start time, if it was possible. This should only be updated backload was possible (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)

SCHED_BATCH_CRITERIA

Scheduler will populate the batch criteria data here when it has info (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)

SCHED_CARRIER

SCHED_CARRIERS_IN_JOB

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_COMMENT

SCHED_COMP_INST

SCHED_DISP_INST

SCHED_DURABLE

SCHED_EET_SEC

SCHED_END

SCHED_GROUP

This is the grouping of tools and processes which the FPS Scheduler schedules together. Since this is a parent of tool via tool->process_group and a parent of process via process->process_group, by definition each tool and each process can only be in one sched group. We need all related tools and processes to be in the same sched group for efficient scheduling. One example is sinks and furnaces because of queue times and batching. Another example is for smaller facilities like Assembly or Test where we might schedule the entire facility together. (* inherited from FPSINPUT.RTG_PROCESS_GROUPS)

SCHED_IS_RESERVED

SCHED_JOB_ID

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_POD_FIRST_DISP_INST

SCHED_POD_KIT_READY_INST

SCHED_POD_KIT_START_INST

SCHED_PRE_BATCH_ID

SCHED_QTY_IN_JOB

SCHED_RECIPE

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_SCORE

SCHED_SCORE_BEST

SCHED_SCORE_DETAILS

SCHED_SETUP

SCHED_SETUP_START

SCHED_SORT_ON_DURABLE

SCHED_SORT_ON_TOOL

SCHED_START

The first start time for the durable to be used (* inherited from FPSBASE.RTG_DURABLE_FUTURE_SCHED)

SCHED_STEP_BEG_BAY

SCHED_STEP_BEG_INST

SCHED_STEP_BEG_STATION

SCHED_STEP_ENT_INST

SCHED_TOOL

the tool from the first lot that scheduled (* inherited from FPSAPP.SCH_W_SCHED_DURABLE_INSPECT)

SCHED_UNRESERVE_INST

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)

SCHED_ZONE_TO_USE

While zone restricted batch scheduling is enabled, this column will be populated with the zone assignment corresponding to the ZONE in EQP_ZONES for the scheduled tool. (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)

SCH_CRITICAL_RATIO_OVR

This column allows for a user defined CRITICAL RATIO to be used by the scheduler. If this value is populated, it will be used by the scheduler instead of any value of CRITICAL RATIO that would be calculated by the FPS sytems. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

SCH_DAYS_LATE_OVR

Our normal days late calculation uses due_inst and changes over time as that date approaches. This value overrides that normal calculation with a fixed number of days late that does not change over time. A positive value means the lot is behind schedule. This only applies to the Scheduler. The normal use case is for important development lots where we do not really have a due date but we just want them to always count as two days late putting them ahead of normal lots that are less than two days late but behind normal lots that are more than two days late. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

SMP_RESULT

Either TAKE or SKIP (* inherited from FPSINPUT.WIP_SMP_FUTURE)

START_INST

Time when the lot started. (* inherited from FPSINPUT.WIP_STARTS)

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)

TARGET_CARRIER

This is the carrier that the future start lots planned to be assigned. (* inherited from FPSINPUT.WIP_STARTS)

TIMER_ID_END_STEP

This indicates that this step is in the middle of a queue timer. Inner join with RTG_QUEUE_TIMERS using timer_id as there is no foreign key because the timer_id record might get deleted from RTG_QUEUE_TIMERS. (* inherited from FPSBASE.WIP_STEP_FUTURE)

TIMER_ID_MID_STEP

This indicates that this step is the end of a queue timer. Inner join with RTG_QUEUE_TIMERS using timer_id as there is no foreign key because the timer_id record might get deleted from RTG_QUEUE_TIMERS. (* inherited from FPSBASE.WIP_STEP_FUTURE)

TIMER_ID_START_STEP

This indicates that this step is the start of a queue timer. Inner join with RTG_QUEUE_TIMERS using timer_id as there is no foreign key because the timer_id record might get deleted from RTG_QUEUE_TIMERS. (* inherited from FPSBASE.WIP_STEP_FUTURE)

TOOL_FOR_TTS

TTS for tool is greatest(last start plus EET of last start, data_date). TTS for first lot not started is the same as the TTS for tool but we need to store TTS for tool because tool might not have any reserved lots. TTS for subsequent lots cums the EET of each lot after the first lot. (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)

UPDATE_LATER_WHEN_CAUGHT_UP

WAIT_SEC_TO_SCHED

The lot may be scheduled but must not be allowed to dispatch or start until this number of seconds has elapsed. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

WAIT_SEC_TO_SCHED_QUEUE

WAIT_TO_SCHED_REASON

WAIT_TO_SCHED_REASON_QUEUE

WEH_END_PROC_INST

WEH_RESERVE_ACTUAL_CH_USED

WEH_RESERVE_ACTUAL_MACH_RCP

WEH_RESERVE_FIRST_LOT_IN_JOB

WEH_RESERVE_INST

WEH_RESERVE_JOB_ID

WEH_RESERVE_OPERATOR

WEH_RESERVE_QTY_IN_JOB

WEH_RESERVE_TOOL