FPSAPP.NMV_P_CARRIER_SUMMARY

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)

CARRIER

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

CARRIER_DISPLAY

CARRIER_CLASS

Carrier class indicates what the carrier is able to carry. It is also an important field in EQP_PORTS but each port has a single defined carrier class and only carriers of this class should go to the port. The value must be one of those defined by FPS in FPSADMIN.MHS_CARRIER_CLASSES which include POD or CAST or BOX. This would be used as a filter on what carriers could be selected when a carrier is needed. For example, when a lot is split we need to find another carrier for the split lot and we select the best carrier in the carrier_class of CAST. But if we need to unload a reticle then we select the best carrier in the carrier_class of POD. (* inherited from FPSINPUT.MHS_CARRIERS)

LOT_LIST

ASSIGNED_CARRIER

This column is needed for lot/carrier association for NextMove. When a lot is removed from its carrier to process on a tool, the now empty carrier can be moved independently of the lot. At this time the carrier field in WIP_LOTS_STATIC will be blank as the lot is no longer in the carrier however this column will keep track of the carrier to which the lot is assigned. This enables the ability to scan empty carriers on racks while the lot is processing on the tool. This column is strictly optional. All applications including NextMove will work as normal if this column is left blank. It should only be populated for sites using NextMove where empty carriers are allowed to leave the load port and remain assigned to lot(s) which are processing. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

NUM_LOTS_IN_CARRIER

HAS_LOT_ON_HOLD

IS_ALLOWED_FOR_SCHED

Lots on hold are only scheduled if this flag for the hold type is set to Y. By default this is N which means that lots on hold are not scheduled. (* inherited from FPSINPUT.WIP_HOLD_TYPES)

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)

TW_USE_PURPOSE

Brief definition of the use of test wafers at this step (ex: Etch Rate or Nitride Dum). (* inherited from FPSINPUT.RTG_ROUTE_STEPS)

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)

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)

PROCESS_DISPLAY

The name of the process displayed on all dashboards and reports. We allow a longer more descriptive name here although often this will be the same as the process. (* inherited from FPSINPUT.RTG_PROCESSES)

RECIPE_DISPLAY

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)

IS_MOVE

CARRIERS_IN_JOB

Set to the number of carriers in the job. The value in WIP_EVENT_HIST represents the number of carriers which have started processing in this job *so far*, while the value in WIP_STEP_HIST (written after the job completes processing) represents the total number of carriers in the job. (* inherited from FPSBASE.WIP_LOT_HIST)

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)

FIRST_LOT_IN_JOB

The first lot in the job determined by the order of events. When this first lot logs the first tool event which is usually a reserve or dispatch then the job_id is created with only this lot. Then subsequent lots join this job. While we use job_id to identify lots that will process or are processing or processed together, first_lot_in_job is still a useful field. (* inherited from FPSBASE.WIP_LOT_HIST)

CURR_LOCATION

store the curr location of the lot (* inherited from FPSAPP.SCH_W_H_S_LOTS)

CURR_STATION

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

CURR_STATION_DISPLAY

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_BUILDING

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

CURR_PROCESS_FAMILY

CURR_STATION_TYPE

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

CURR_LOCATION_TYPE

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_BUILDING

LAST_KNOWN_BAY

LAST_KNOWN_STATION

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)

DEST_STATION

The final destination the lot is required to move. Typically the reserved tool but also can be the scheduled tool if the client wants too, but this should be with caution as the scheduled tool can change (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

DEST_STATION_DISPLAY

DEST_BAY

DEST_PROCESS_FAMILY

DEST_STATION_TYPE

TOOL_FOR_NEXT_STEP

NEXT_STATION

NEXT_STATION_TYPE

NEXT_BAY

NEXT_STATION_DISPLAY

DIRECT_DELIVERY_BAY

DO_NOT_MOVE

SHOW_EXACT_DEST

REQ_EXACT_DEST

RESERVED_TOOL

IS_RESERVED

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

TIME_TO_START

TIME_TO_NEXT_MOVE

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)

TIME_TO_NEXT_MOVE_OVR

This column allows for sites to control the NextMove countdown timers. Normally we do not populate this but for certain use cases clients may want to change this value based on certain criteria. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

PREP_SEC

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

USE_DISP_INST

TRANSPORT_METHOD

VEHICLE_TYPE

VEHICLE_SUB_ROUTE

Sub route associated to a cart or carts within a vehicle route. (* inherited from FPSINPUT.MHS_VEHICLE_SUB_ROUTES)

CLAIMED_VEHICLE

IS_ON_VEHICLE

CLAIMED_USER

TRANSIT_START_INST

TRANSIT_EST_SEC

CURR_PROCESS_STATE

CURR_PROCESS_STATE_DISPLAY

CURR_PROCESS_STATE_DETAILS

NEEDS_UNLOAD

PRIORITY

This is the priority value as it is stored in the MES for each lot. It might be a number or a letter or word depending on the MES and the facility. (* inherited from FPSINPUT.WIP_PRIORITIES)

PRIORITY_DISPLAY

The name of the priority displayed on all dashboards and reports. Typically priority is short like P1, P2 so we allow a longer more descriptive name here that should be more familiar to the users. (* inherited from FPSINPUT.WIP_PRIORITIES)

5

PRIORITY_HTML_BG_COLOR

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)

CURR_PRIORITY_SORT

NMV_ADDL_BADGE_LABEL

By default, NextMove displays a badge next to the carrier indicating that it is a priority lot but this column allows us to show an additional badge indicating anything that we wish to highlight. (* inherited from FPSINPUT.MHS_CARRIERS)

NMV_ADDL_BADGE_COLOR

This is the color of the additional badge on NextMove. See comment on NMV_ADDL_BADGE_LABEL for details. (* inherited from FPSINPUT.MHS_CARRIERS)

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)

IS_QUEUE_TIMER

Flag to display queue timer icon in NextMove if lot is in queue time loop. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

IS_N2

Flag to display N2 icon in NextMove if lot requires N2 (nitrogen purged) storage. In a future version we will allow more generic AMHS-related flags but this is specific to N2 for now. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

DURABLE_CARRIER

The durable carrier ID of the durable required for this carrier to process. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

DURABLE_LOCATION

The location of the durable. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

LAST_KNOWN_DURABLE_LOC

The previous location of the durable. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

IS_DURABLE_REQUIRED

NextMove flag indicating if the carrier requires a durable to process. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

IS_DURABLE_AT_DESTINATION

NextMove flag indicating if the durable location is the same as the tool the carrier needs to process on. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

HIDE_ON_TOOLS

TO_SETUP_TEXT_COLOR_HTML