Maintaining Utilization and Job History Records on the Utilization Tab

The Utilization tab allows data in the Util_History and Job_History tables to be maintained. The Job_Hour_History table is also affected, as it is periodically updated with new data from the Util_History and Job_History tables. The Utilization tab is only available if MES Performance is licensed and the user has the May edit utilization data Data Editor user privilege.

The Util_History table captures utilization data and a chronological sequence of utilization events for each entity that can capture utilization data. This data includes entity utilization states, utilization reasons, number of occurrences, and the timestamps when an entity's utilization state or reason changes (that is, when a new event occurs).

The Job_Hour_History table, which is used in the calculation of equipment performance statistics, is updated every hour as necessary to reflect Util_History table changes, including those made from the Utilization tab. However, because recently entered job statistical data is considered volatile with a possibility of changing frequently, a predefined cut-off period is used to determine when equipment performance statistical data is based on data in the Job_Hour_History table or generated dynamically. The default cut-off period is 2 hours prior to the current hour. When the Job_Hour_History table is updated every hour, only event data that occurred prior to the pre-defined cut-off period is updated.

Deleting a utilization history record increments or decrements the value in the runtime, downtime, or idletime fields of the corresponding Job_Hour_History record, depending on the reason code of the deleted record (the reason code determines the time category). Similarly, inserting a new utilization history record increments or decrements the runtime, downtime, or idletime field of the corresponding Job_Hour_History record (or creates a new Job_Hour_History record, if no record with a key corresponding to the newly inserted utilization history record exists).

The Job_History table captures the jobs that are run on each entity that can run jobs. Also captured are the position on which the job was running and when the job started and ended. Updates to utilization event history records do not have any impact on the Job_History table. In the Utilization tab, Job_History records are shown listed below the utilization history record to which they correspond; that is, under the following conditions:

• The job start time of the Job_History record is greater than or equal to the start time of the utilization event for the related entity

• The job end time of the Job_History record ends before the end time of the utilization event for the related entity

When the start time or the end time of a Job_History record is modified, the corresponding runtime, downtime, and idletime of the job in the Job_Hour_History table is updated. Similarly, the good and reject production counts for the affected period are also updated in the Job_Hour_History table.

The following topics describe:

• The data by which the utilization history data records can be filtered

• The data that can be entered or edited for utilization history data records

• The data that can be entered or edited for job history records that are associated with utilization history data records