data-dictionary
data-dictionary
Breadcrumbs

FPSAPP.EQP_SETUP_CHG_MANUAL

Data Dictionary

>

FPSAPP Tables

> FPSAPP.EQP_SETUP_CHG_MANUAL

Table FPSAPP.EQP_SETUP_CHG_MANUAL"

For users to manually input setup change times which will override calculated times.

  • Schema: FPSAPP

  • Tablespace: FPSDATA

  • Primary key: FACILITY, EQP_TYPE, FROM_RQD_SETUP, TO_RQD_SETUP

  • Foreign keys: EQP_SETUP_CHG_MANUAL_FK_ETYPE: FACILITY, EQP_TYPE REFERENCES FPSINPUT.EQP_TYPES (FACILITY, EQP_TYPE)


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)

EQP_TYPE

VARCHAR2(50)

N

Each tool is assigned an EQP_TYPE and all tools in the same type are identical meaning that they should run at the same throughput when running the same process with the same chamber type count. We also expect similar availability since these tools are identical. However tools in the same EQP_TYPE may have different chamber configurations and may run different groups of processes. (* from FPSINPUT.EQP_TYPES)

FROM_RQD_SETUP

VARCHAR2(100)

N

Setup that is changed from. This should match a value in rqd_setup in RTG_TOOL_ASSIGNMENTS.

TO_RQD_SETUP

VARCHAR2(100)

N

Setup that will be change to. This should match a value in rqd_setup in RTG_TOOL_ASSIGNMENTS.

IS_LONG_SETUP

CHAR(1)

Normally when rqd_setup from RTG_TOOL_ASSIGNMENTS does not match curr_setup from ETP_STATUS for the entity then the curr_rank is S for Setup. S is not blocked and lots are available to be scheduled using the appropriate setup penalty. If this is set to Y then the curr_rank is L for Long Setup. L is blocked and these lots are not available to be scheduled. This allows us to use the automatic functionality of ETP_STATUS for long setups without manual intervention.

SETUP_COST

NUMBER(9)

Cost associated with the setup change. Used by the scheduler to optimize setup change based on configuration.

SETUP_SEC

NUMBER(8)

Estimated time to do this setup change. This time will override the automatically calculated value.

VERIFIED_BY

VARCHAR2(64)

N

Person who verified the setup change.

VERIFIED_COMMENT

VARCHAR2(128)

N

Optional field to enter comment about this setup change.