FPSBASE.EQP_L5_TRANSITION_STATES

Data Dictionary

FPSBASE Tables

> FPSBASE.EQP_L5_TRANSITION_STATES

Table FPSBASE.EQP_L5_TRANSITION_STATES"

This table is how we join the client states with our ETP hierarchy. Transition_state is the parent of eqp_state which comes directly from the client input data. ETP_group is the FPS ETP Level 4 group where the values are defined by FPS as an enhancement of the industry SEMI standard. From the ETP_group we get the SEMI standard E10 and availability and other information. Therefore we can determine the E10 and availability for each client eqp_state through this table.

Schema: FPSBASE
Tablespace: FPSDATA
Foreign keys: EQP_L5_TRANSITION_FK_L4_GRP: OPPORTUNITY_STATE REFERENCES FPSADMIN.ETP_L4_OPPORTUNITY_STATES (OPPORTUNITY_STATE)

Column	Type	Nullable	Comment
TRANSITION_STATE	VARCHAR2(48)		We name this transition_state because ideally this state would be determine what states are allowed to follow but really this is just a grouping which is the parent of eqp_state and child of etp_group
CONSIDER_NONMFG_AS_UP_FOR_MAQT	CHAR(1)		There are some NONMFG states like QUAL and ALARM that we want to consider as up for the purposes of the Multi Area Queue Timer logic because we expect the entity to come up in the near future.
IS_ALARM	CHAR(1)		This should be set to Y if the state should count as an alarm event. (This is typically a downtime event automatically triggered by the equipment.)
IS_EQP_RELATED	CHAR(1)		This should be set to Y for UDT or SDT states where the equipment is solely responsible for the entity being down and is actively being diagnosed or repaired. (Does not include Wait-times or alarms, can include Quals). Should only be Set to Y for Downtime (UDT or SDT) states
IS_FUTURE	CHAR(1)		This should be set to Y if the state does not apply immediately. Production runoff and alarms are two examples where we do not want to set this state in ETP until the tool misses the cascade and starts to lose productivity.
IS_NST_HIDDEN_ON_HIST	CHAR(1)		If yes then do not include time in this NST state in the history. Most NST states should be Y unless there is a specific reason why the client wants it to be part of the total. An example calculation here is if a tool is PRD for 1 day, SBY for 1 day, SDT for 1 day, UDT for 1 day, and NST for 3 days then the totals for the week are 25% each for PRD, SBY, UDT, SBY because the NST is ignored.
IS_PM	CHAR(1)		This should be set to Y if the state should count as a Preventative Maintenance, PM, event. This should only be Y on Scheduled (SDT) States. This is used in the Mean time to (perform) PM, MTTPM metric. (Does not include Wait-times. Can include Qualifications or Verification tests)
IS_QUAL	CHAR(1)		This should be set to Y if the state should count as a qual event and time spent in this state should count as qual time. The EQP_L5_QUAL_CHECK constraint ensures that this must be set to Y when mnt_group is QUAL. The is_qual column is critical for NMV_P_TOOL_QUAL_SUMMARY and this constraint is not perfect but it prevents the most obvious wrong case.
IS_SCHED_QUAL	CHAR(1)		This should be set to Y if the state should count as a scheduled qual event. (This is typically a qual run by the equipment operator rather than by the maintenance group.)
IS_SDT_SETUP	CHAR(1)		Boolean column indicating if the eqp_state is Scheduled Down due to setup conversion. We will note this in ETP_MNT_EPISODE_HIST to differentiate from regular PMs.
LONG_DESCRIPTION	VARCHAR2(1000)
MNT_GROUP	VARCHAR2(36)		Grouping field for upcoming maintenance on Dashboard and Mnt Viewer. This can be any value and should be formatted for display.
OPPORTUNITY_STATE	VARCHAR2(12)	N	FPS Enhanced Tool Performance group assigned to each transition_state and to each etp_family. This assignment determines the default grouping on all Tool Performance charts and determines the color on all views including Dashboard and Gantt charts.
SORT_WITHIN_OPP	NUMBER(3)	N	Unique sort order within the ETP_group. 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).