Data Dictionary
>
FPSINPUT Tables
> FPSINPUT.EQP_L6_DETAILED_STATES
Table FPSINPUT.EQP_L6_DETAILED_STATES"
These are the detailed states used by the client. See comments in EQP_L5_TRANSITION_STATES for more details
-
Schema: FPSINPUT
-
Tablespace: FPSDATA
-
Primary key: EQP_STATE
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
EQP_STATE |
VARCHAR2(48) |
N |
Client equipment state taken directly from their MES or from their existing tool state model. For EQP_MNT_FUTURE, this is the state that we estimate the entity will be in during the maintenance which is often set to a generic PM state if we do not have detailed information. |
|
E58_SUBSTATE |
VARCHAR2(24) |
Substate for SEMI E58 categorization. This is for reference and reporting only and can be left balnk |
|
|
EQP_STATE_DISPLAY |
VARCHAR2(48) |
N |
Display name for the equipment state which will be displayed on all Dashboards and reports. |
|
EQP_STATE_OWNER |
VARCHAR2(48) |
Person or department who owns each state. This is for reference and reporting only and can be left blank |
|
|
LONG_DESCRIPTION |
VARCHAR2(1000) |
||
|
LOT_GROUP_TO_SCHED_LIST |
VARCHAR2(64) |
By default we will schedule all lots when a tool is in a state where mfg_state is MFG (PRD and SBY but not ENG). For NONMFG states use this column to schedule lots of certain lot_groups, most likely test wafers. |
|
|
MINUTES_UNTIL_SCHED |
NUMBER(7) |
This value should be set only for NONMFG states and represents the number of minutes from the time when the eqp state changed until we will schedule lots to a tool in this state as long as that time is no earlier than remaining_mins_until_sched from now. The default value in EQP_L6_DETAILED_STATES can be overridden by an entry in EQP_OVR_MINS_UNTIL_SCHED for a specific eqp_type and eqp_state. If the value is EQP_L6_DETAILED_STATES is null then we will not schedule. For example, the current time is 10:00, the current state is SCH-SERVICE, state changed at 02:00, minutes_until_sched is 600, and remaining_mins_until_sched is 90. 02:00 + 600 minutes is 10:00 which is more than 90 minutes away therefore we schedule lots to this tool starting at 10:00. But once the clock passes 08:30 then the original estimate of 10:00 is less than 90 minutes away then we perpetually estimate that the tool will be up in 90 minutes. So at 08:35 we schedule starting at 10:05 then at 08:40 we schedule starting at 10:10 and so on. |
|
|
OVR_BG_COLOR |
VARCHAR2(24) |
This column defines the color used in the reports for displaying WIP qtys by ECT state. Since hold groups are an ECT state this color will be the color used in the Dashboard reports for the associated hold group. (* from FPSINPUT.WIP_HOLD_GROUPS) |
|
|
OVR_EQP_STATE_SHORT_DISPLAY |
VARCHAR2(12) |
For several applications including NextMove BayView we need to show the state in 12 characters or less. By default we will use the first 12 characters of the eqp_state but if you have longer state names then you can improve the display by overriding with 12 or fewer clearer characters in this column. |
|
|
PENDING_SDT_OR_QUAL_OR_ENG |
VARCHAR2(4) |
When this is populated with either SDT or QUAL or ENG this means that the tool is processing but will stop when all jobs which are currently processing complete. When in this pending state, the process state of lots which are qualified to run on this tool will be DOWN just as if the tool was already SDT or QUAL or ENG. This pending state does not affect ETP logic during efficient processing but after the tool misses cascade then goes to standby then it will be pending maintenance rather than the normal standby state. |
|
|
REMAINING_MINS_UNTIL_SCHED |
NUMBER(7) |
See comment for MINUTES_UNTIL_SCHED column. |
|
|
SHOW_IN_DIAGRAM |
CHAR(1) |
Some sites have eqp states that are rarely if ever used. We want to keep all eqp states from the MES in this table in case that a state is used but setting this flag to N prevents these states from showing in the Eqp State Diagram. Technically this flag sets the existing is_active flag in both EQP_STATE_DIAGRAM and ETP_STATE_DIAGRAM which was previously always Y for states from the MES. |
|
|
SORT_WITHIN_TRANSITION |
NUMBER(3) |
N |
Unique sort order within the transition_state. This is not particularly critical but the idea is that 1 is worse (i.e. closer to NST) and the highest number is best (i.e. closer to PRD). |
|
TECHNICAL_DETAILS |
VARCHAR2(1000) |
Technical description of how ETP works to cause an entity to enter this L6 state. (* from FPSADMIN.ETP_L6_DETAILED_STATES) |