FPSBASE.WIP_REF_LOTS_COLS_NO_DD_PRTN

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)

ACTIVE_ABORT_INST

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)

OVR_BANK_FROM_CONSIDER_FLAG

BEG_PROC_INST_NOT_ABORTED

BLOCK_OR_DOWN_REASON

CARRIERS_IN_JOB_WCJ

CARRIER_DISPLAY

CARRIER_FOR_MHS_TRG

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_PORT

CURR_PORT_MODE

CURR_PRIORITY_BG_COLOR

CURR_PRIORITY_DISPLAY

CURR_PRIORITY_SORT

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)

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)

DEMAND_INST

Start of period when this qty of this planprd needs to finish. We automatically spread demand across each plan week in WIP_DEMAND_BY_WEEK which feeds WIP_FLUSH therefore this column can be the start of any time period less than or equal to plan week. It could be the demand for each shift or for each day or for each plan week but if the site has no preference then the easiest way to set this up is to write one row per plan week and let us spread across that week. It is important to note that we always spread across the plan week with our custom logic so even if this table is by day we might adjust it to another day within the same plan week. (* inherited from FPSINPUT.WIP_DEMAND)

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)

DIRECT_DELIVERY_BAY

DISP_PROC_ENDED_SEC

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)

EET_SEC_WCJ

EET_SEC_BATCH_FOR_TTS

EET_SEC_LOT_FOR_TTS

EST_BEG_INST_TOOL

EST_DISP_INST_TOOL

EST_END_INST_FROM_BEG

EST_NEXT_BEG_INST_FROM_BEG

EST_SEC_TO_COMP_SLOW

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_NEXT_STATION

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)

EXTL_RESERVE_INST

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_START

Time by when the external system recommends that the job will begin processing. (* inherited from FPSBASE.WIP_STEP_FUTURE_SCHED)

EXTL_STATION_FOR_NEXT_STEP

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)

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_TRANS_MODE_FOR_NEXT_STEP

EXTL_VEHICLE_SUB_ROUTE

EXTL_VEH_SUB_RT_FOR_NEXT_STEP

FACILITY_FOR_MHS_TRG

FACILITY_OF_BANK

FIRST_LOT_IN_JOB_WCJ

FUT_HOLD_SEC_ADD_TO_EST_COMP

FUT_HOLD_TYPE

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)

HIDE_LOTS_IN_DASH

This flag is similar to CONSIDER_IN_BANK but even more extreme. This flag will completely hide all lots and moves on this route from the Dashboard. Honestly we discourage anyone from using this flag (and strongly discourage it for anything but test wafers) but it is here at least for Dashboard only if a particular site really wants it. (* inherited from FPSINPUT.RTG_ROUTES)

HOLD_FOR_DISPLAY

HOLD_MODULE

HOLD_PRTY_GROUP

This field determines the grouping of hold lots displayed on the Dashboard hold page. Typically the highlighted priorities will each be in their own group and all others will be in a group named OTHERS. We might want to separate low priority lots too. (* inherited from FPSINPUT.WIP_PRIORITIES)

HOLD_TYPE_DISPLAY

IGNORE_BANK_TW_ON_DASH

The Dashboard spotlight shows a number of Test Wafers in the facility. Usually we want this to include test wafers in a bank so we would set this to N. To ignore test wafers in a bank then set this to Y. (* inherited from FPSINPUT.GEN_FACILITIES)

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_COMPLETE_FROM_OVR

IS_COUNT_PRIORITY_PCT

This flag determines which priorities to include in our overall percentage of priority lots in the Dashboard spotlight. This is similar to is_highlighted_prty but it is possible that we might want to highlight a priority but not include it in the percentage. (* inherited from FPSINPUT.WIP_PRIORITIES)

IS_CURR_PRTY_HIGHLIGHTED

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)

IS_DURABLE_REQUIRED

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

IS_HOLD_DISPLAY

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)

IS_NEXT_MOVE_NEXT_STEP

IS_NMV_PRIORITY

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

IS_PLAN_PRTY_HIGHLIGHTED

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_RESERVED

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

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

LAST_KNOWN_BAY

LAST_KNOWN_BUILDING

LAST_KNOWN_DURABLE_LOC

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

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)

LINE_SECTION_NOT_NULL

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)

LOCATION_TYPE

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_SORT_ORDER

LOTS_IN_JOB_WCJ

MAIN_RT_PROC_STATE

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)

NEXT_STATION

NMV_USE_DISP_INST

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

OVR_CARRIER_DISPLAY

The ID of the carrier for application display purposes. For example, the internal/referential carrier ID might be a zero-padded hexidecimal number, while the human-readable labels on the carriers might be an unpadded decimal equivalent (e.g. CARRIER=A1B2, OVR_CARRIER_DISPLAY=41394). (* inherited from FPSINPUT.MHS_CARRIERS)

PLAN_PRIORITY_BG_COLOR

PLAN_PRIORITY_DISPLAY

PLAN_PRIORITY_SORT

PREP_SEC

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

PROCESS_MODULE_DISPLAY

OVR_EST_END_INST

Estimated time when the lot will end processing on the tool. (* inherited from FPSINPUT.WIP_LOTS_OVR_EST_END_INST)

OVR_EST_NEXT_BEG_INST

Estimated time when the next job must start processing on the tool in order to maintain full cascading and not lose productivity. (* inherited from FPSINPUT.WIP_LOTS_OVR_EST_END_INST)

PROC_STATE_DASH

TOOL

Tool is generally just the main tool. The exception is when different entities on the tool run completely independently and it is physically impossible to run wafers of the same lot across multiple entities. In this exception case, we may want to assign the entities to different eqp_types and therefore we should define each entity as a tool. Please note that when we do this there is no indication whatsoever that these different entities are on the same tool. (* inherited from FPSINPUT.EQP_TOOLS)