Data Dictionary
>
FPSINPUT Tables
> FPSINPUT.GEN_FACILITY_SHUTDOWNS
Table FPSINPUT.GEN_FACILITY_SHUTDOWNS"
Information about facility shutdowns past, present, and future.
-
Schema: FPSINPUT
-
Tablespace: FPSDATA
|
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) |
|
|
FROM_INST |
DATE |
Time from which this state was active. |
|
|
IS_NORMALLY_SCHEDULED |
CHAR(1) |
We show facility shutdowns on the progress chart on the Dashboard Lot page but for a facility that does not operate 24-7 then we do not want to show weeknights or nights when it is normally scheduled to be shutdown. |
|
|
OVR_SBY_W_NST_STATE |
VARCHAR2(48) |
This column is not yet used but the idea is that if this column is populated then ETP logic will override standby state with the NST state specified in this value for all tools in standby during the period of the shutdown. This should definitely be set for a full shutdown and could be set for a partial shutdown if desired. |
|
|
PLAN_UTIL_DEGRADE_PCT |
NUMBER(3) |
This is normally 100 when the facility is completely shutdown but this column allows for partial shutdowns where we expect that the facility will continue running but at a far lower output. Technically what we do with this value is we multiply the time at the step during the shutdown by this multiplier and assign that cycle time to the shutdown. For example, if this is 75 then we expect the output to degrade by 75%. So for a tool where we normally expect 60% utilization, we would expect 15% utilization during the shutdown period. If a lot waited for 8 hours then we count 2 hours to WAIT and 6 hours to SHUTDOWN in our cycle time calculations. |
|
|
SHUTDOWN_NOTE |
VARCHAR2(128) |
Note describing the reason for the shutdown. |
|
|
TO_INST |
DATE |
Time to which this state was active. |