data-dictionary
data-dictionary
Breadcrumbs

FPSBASE.NMV_W_BAYMONITOR_ROTATION

Data Dictionary

>

FPSBASE Tables

> FPSBASE.NMV_W_BAYMONITOR_ROTATION

Table FPSBASE.NMV_W_BAYMONITOR_ROTATION"

A table that contains the list of bays that are paired for baymonitor rotation

  • Schema: FPSBASE

  • Tablespace: FPSDATA

  • Primary key: FACILITY, BAY, BAY_ROTATION

  • Foreign keys: NMV_W_BAYMONITOR_ROTATI_FK_FAC: FACILITY REFERENCES FPSINPUT.GEN_FACILITIES (FACILITY)


Column

Type

Nullable

Comment

FACILITY

VARCHAR2(6)

N

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)

BAY

VARCHAR2(12)

N

A bay is a physical area within the building. The bay is important for estimating travel time for a carrier to reach its destination as we usually store these estimates as a matrix of bay-to-bay and assume that the estimated time from any location within one bay to any location within another bay is approximately the same. (* from FPSINPUT.MHS_BAYS)