data-dictionary

FPSBASE.MHS_STATION_ASSIGNMENTS

Data Dictionary

>

FPSBASE Tables

> FPSBASE.MHS_STATION_ASSIGNMENTS

Table FPSBASE.MHS_STATION_ASSIGNMENTS"

Contains the stations assigned to each tool for staging, input, and output as well as other stations which are acceptable if the carriers happen to be there already.

  • Schema: FPSBASE

  • Tablespace: FPSDATA

  • Foreign keys: MHS_STATION_ASSIGNMENT_FK_TOOL: FACILITY, TOOL REFERENCES FPSINPUT.EQP_TOOLS (FACILITY, TOOL)


Column

Type

Nullable

Comment

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)

TOOL

VARCHAR2(16)

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

STATION

VARCHAR2(32)

The rack, bay, building, tool, cart, or stocker which has alternately acceptable stations (* from FPSINPUT.MHS_STATION_ALTERNATES)

INPUT_RANK

NUMBER(1)

Preference where we want to send carriers which are reserved to this tool. These are typically input racks/stockers for the bay. This is a non-unique numeric rank from 1 to 9 where 1 is first choice and 9 is last choice.

IS_ALSO_ACCEPTABLE_IF_CURRLOC

CHAR(1)

This means that we would not send reserved carriers from elsewhere in the site to this location but if the carrier is already here that is not worth moving an assigned input location. Typically this is Y for location which are in adjacent bays.

OUTPUT_RANK

NUMBER(1)

Preference where we want to send carriers which have recently completed processing on this tool. These are typically input racks/stockers for the bay. This is a non-unique numeric rank from 1 to 9 where 1 is first choice and 9 is last choice.

OVR_CAST_EXPEDITE_TRANSIT_SEC

NUMBER(5)

Estimated expedite transit time to move a cassette between bays.

OVR_CAST_TRANSIT_SEC

NUMBER(5)

If populated, Scheduler and NextMove will use this value in place of any other logic for determining the transit time for a lot from this station to the associated tool.

OVR_POD_TRANSIT_SEC

NUMBER(5)

If populated, Scheduler and NextMove will use this value in place of any other logic for determining the transit time for a pod/durable from this station to the associated tool.

STAGING_RANK

NUMBER(1)

Preference where we want to stage reserved carriers immediately before loading on tool. This is a non-unique numeric rank from 1 to 9 where 1 is first choice and 9 is last choice.