FPSBASE.WIP_STEP_FUTURE_COMBINED

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)

NUM_SEQ_AWAY_W_DECIMAL

NUM_STEPS_TO_RETURN

NUM_SEQ_TO_RETURN

IS_NEXT_STEP

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)

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)

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)

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)

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)

IS_IN_PRTY_GANTT

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)

LINE_YIELD_PCT_TO_ARRV

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

CURR_COMP_TO_EXPECTED_COMP_SEC

EARLIEST_STEP_SEC

EXPECTED_STEP_SEC

FIRST_FUT_HOLD_STEP

FIRST_FUT_HOLD_NUM_STEPS_AWAY

FIRST_FUT_HOLD_TYPE

FIRST_FUT_HOLD_NOTE

FUT_HOLD_SEC_TO_ARRV

FUT_HOLD_SEC_AT_STEP

FUT_HOLD_TYPE_AT_STEP

FUT_HOLD_NOTE_AT_STEP

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)

SMP_RESULT

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

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)

SEQ_NUM

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

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)

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_START

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

IS_BANK

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)

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)

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

GOAL_BEGIN_INST

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

GOAL_COMP_INST

GOAL_COMMENT

UPDATE_LATER_WHEN_CAUGHT_UP

IS_STEP_AFTER_LOT_ASGN

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)

WAIT_SEC_TO_SCHED_QUEUE

WAIT_TO_SCHED_REASON_QUEUE

WSF_ACTION

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)

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)

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

SCHED_JOB_ID

SCHED_IS_RESERVED

SCHED_QTY_IN_JOB

SCHED_CARRIERS_IN_JOB

SCHED_EET_SEC

SCHED_SCORE

SCHED_SCORE_DETAILS

SCHED_SCORE_BEST

SCHED_COMMENT

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_RECIPE

SCHED_SETUP

SCHED_SETUP_START

SCHED_BATCH_CRITERIA

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

SCHED_ALLOWED_TOOL_LIST

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)

EXTL_TIME_TO_NEXT_MOVE

Time provided by an external system to override the carrier time to move for racks. (* 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)

SCHED_PRE_BATCH_ID

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)

EXTL_VEHICLE_SUB_ROUTE

IS_TIMER_STEP_TO_SCHED

The flag to indicate if this is the timer step to schedule (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)

SCHED_EARLY_START

This Column stores the estimated earliest sched start for a lot. To be used for NextMove or dispatching (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)

IS_IN_WSFS