FPSAPP.WIP_STEP_FUTURE_SCHED

LOT

VARCHAR2(128)

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. (* from FPSINPUT.WIP_LOTS_STATIC)

STEP

VARCHAR2(256)

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. (* from FPSINPUT.RTG_ROUTE_STEPS)

ROUTE

VARCHAR2(256)

Route that has threading requirements (* from FPSINPUT.RTG_STEP_THREADING)

FACILITY

VARCHAR2(6)

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. (* from FPSINPUT.GEN_FACILITIES)

BATCH_CRITERIA

VARCHAR2(140)

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. (* from FPSINPUT.RTG_TOOL_ASSIGNMENTS)

DURABLE_LAST_SCHED_END

DATE

DURABLE_LAST_SCHED_TOOL

VARCHAR2(16)

EST_MACHINE_RECIPE

VARCHAR2(100)

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. (* from FPSINPUT.RTG_TOOL_ASSIGNMENTS)

EXTL_ADDL_INFO

VARCHAR2(256)

This will have any additional lot info needed by the external system

EXTL_DEST_LOCATION

VARCHAR2(32)

This column will have the destination location for the lot

EXTL_DISP_INST

DATE

Time by when the external system recommends that the job must be dispatched.

EXTL_DO_NOT_MOVE

CHAR(1)

This column will decided whether NextMove will highlight to move or override it

EXTL_END

DATE

Time by when the external system recommends that the job will end processing.

EXTL_IS_RESERVED

CHAR(1)

Flag indicated whether the external system has reserved the lot to the tool. If not we still move to the destination.

EXTL_RECIPE

VARCHAR2(100)

EXTL_REQ_EXACT_DEST

CHAR(1)

This column will decided whether NextMove use alternates and station assignments or ignore them.

EXTL_RESERVE_CH_TO_USE

VARCHAR2(24)

EXTL_RESERVE_INST

DATE

EXTL_RESERVE_JOB_ID

VARCHAR2(64)

EXTL_RESERVE_QTY_IN_JOB

NUMBER(7)

EXTL_RESERVE_TOOL

VARCHAR2(16)

EXTL_RESERVE_USERNAME

VARCHAR2(64)

EXTL_SETUP

VARCHAR2(100)

EXTL_SHOW_EXACT_DEST

CHAR(1)

This column will decided whether NextMove will show the destination Bay or the exact destination.

EXTL_START

DATE

Time by when the external system recommends that the job will begin processing.

EXTL_TIME_TO_NEXT_MOVE

DATE

Time provided by an external system to override the carrier time to move for racks.

EXTL_TRANSPORT_MODE

VARCHAR2(16)

Name of the site transport mode which represents how material is moved from one location to another. (* from FPSINPUT.MHS_EXTERNAL_TRANSPORT_MODES)

EXTL_UNRESERVE_INST

DATE

EXTL_VEHICLE_SUB_ROUTE

VARCHAR2(36)

IS_RESERVED

CHAR(1)

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

IS_TIMER_STEP_TO_SCHED

CHAR(1)

The flag to indicate if this is the timer step to schedule

JOB_ID

VARCHAR2(64)

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

MANL_RESERVE_CH_TO_USE

VARCHAR2(24)

List of chambers to use for processing set by NextMove when lot is reserved.

MANL_RESERVE_INST

DATE

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.

MANL_RESERVE_JOB_ID

VARCHAR2(64)

MANL_RESERVE_QTY_IN_JOB

NUMBER(7)

MANL_RESERVE_TOOL

VARCHAR2(16)

Stores tool reserved by NextMove

MANL_RESERVE_USERNAME

VARCHAR2(64)

MANL_UNRESERVE_INST

DATE

NO_SCHED_TOOL_REASON

VARCHAR2(512)

PROCESS

VARCHAR2(50)

N

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. (* from FPSINPUT.RTG_PROCESSES)

RQD_SETUP

VARCHAR2(100)

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. (* from FPSBASE.WIP_LOT_HIST)

SCHED_ALLOWED_TOOL_LIST

VARCHAR2(512)

SCHED_BACKLOAD_INST

DATE

to indicate the the scheduled early start time, if it was possible. This should only be updated backload was possible

SCHED_BATCH_CRITERIA

VARCHAR2(140)

Scheduler will populate the batch criteria data here when it has info

SCHED_CARRIER

VARCHAR2(32)

SCHED_CARRIERS_IN_JOB

NUMBER(2)

SCHED_CH_TO_USE

VARCHAR2(24)

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.

SCHED_COMMENT

VARCHAR2(4000)

SCHED_COMP_INST

DATE

SCHED_DISP_INST

DATE

SCHED_DURABLE

VARCHAR2(129)

SCHED_EARLY_START

DATE

This Column stores the estimated earliest sched start for a lot. To be used for NextMove or dispatching

SCHED_EET_SEC

NUMBER(7)

SCHED_END

DATE

SCHED_EXTL_MODEL_ID

VARCHAR2(128)

to indicate the external model id of the tool that this lot is scheduled to

SCHED_EXTL_MODEL_STATE

VARCHAR2(128)

to indicate the external model state of the tool that this lot is scheduled to

SCHED_GROUP

VARCHAR2(36)

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. (* from FPSINPUT.RTG_PROCESS_GROUPS)

SCHED_IS_EXCLUSIVE_CHAMBER

CHAR(1)

to indicate if the chamber is exclusive on the tool where this lot scheduled to

SCHED_IS_RESERVED

CHAR(1)

SCHED_JOB_ID

VARCHAR2(64)

SCHED_LOT_TRANSIT_SEC

NUMBER(6)

to indicate the transit time needed to move the lot to the scheduled tool

SCHED_POD_FIRST_DISP_INST

DATE

SCHED_POD_KIT_READY_INST

DATE

SCHED_POD_KIT_START_INST

DATE

SCHED_PRE_BATCH_ID

VARCHAR2(64)

SCHED_PROCESS_CHANGE_SEC

NUMBER(6)

to indicate the process change time needed to run this lot

SCHED_QTY_IN_JOB

NUMBER(7)

SCHED_QUEUE_START_DELAY_INST

DATE

to indicate the earliest time that to start to process the queue-start-step

SCHED_RECIPE

VARCHAR2(100)

SCHED_RESERVE_INST

DATE

The actual time the lot was reserved by the scheduler will be helpful for compliance and debugging.

SCHED_RQD_PORT_GROUP

VARCHAR2(12)

to indicate the required port group information of the tool that this lot scheduled to

SCHED_SCORE

NUMBER(20,4)

SCHED_SCORE_BEST

VARCHAR2(4000)

SCHED_SCORE_DETAILS

VARCHAR2(4000)

SCHED_SETUP

VARCHAR2(100)

SCHED_SETUP_START

DATE

SCHED_SORT_ON_DURABLE

NUMBER(4)

SCHED_SORT_ON_TOOL

NUMBER(4)

SCHED_START

DATE

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

SCHED_STEP_BEG_BAY

VARCHAR2(24)

SCHED_STEP_BEG_INST

DATE

SCHED_STEP_BEG_STATION

VARCHAR2(32)

SCHED_STEP_ENT_INST

DATE

SCHED_TOOL

VARCHAR2(16)

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

SCHED_UNRESERVE_INST

DATE

SCHED_WAIT_ETP_STATE

VARCHAR2(48)

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.

SCHED_ZONE_TO_USE

VARCHAR2(1)

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.

TOOL_FOR_TTS

VARCHAR2(16)

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.

TRG_TIME

TIMESTAMP(6)

TTS_BAY

VARCHAR2(12)

Bay of the tool where this carrier is reserved or scheduled. (* from FPSINPUT.MHS_DELIVERY_NEXT)

TTS_PROCESS_FAMILY

VARCHAR2(50)

TTS_SOURCE

VARCHAR2(5)

UPDATED_INST

DATE

N

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. (* from FPSINPUT.GEN_FACILITIES)

WEH_END_PROC_INST

DATE

WEH_RESERVE_ACTUAL_CH_USED

VARCHAR2(24)

WEH_RESERVE_ACTUAL_MACH_RCP

VARCHAR2(100)

WEH_RESERVE_FIRST_LOT_IN_JOB

VARCHAR2(32)

WEH_RESERVE_INST

DATE

WEH_RESERVE_JOB_ID

VARCHAR2(64)

WEH_RESERVE_OPERATOR

VARCHAR2(64)

WEH_RESERVE_QTY_IN_JOB

NUMBER(7)

WEH_RESERVE_TOOL

VARCHAR2(16)