Use the Utilization control

The Utilization control displays entity utilization data (for example, downtime, idle time and running time), allows the current utilization reason to be changed, and allows pending reasons to be set.

Fields are added to the text box section under the grid where OEE data is displayed for showing the good and scrap quantities. If OEE is being displayed by shift, the quantities should be displayed by shift. If OEE is being displayed by job, the quantities would be displayed by job. As with other fields on the control, the visibility of these fields will be configurable at run time.

The Utilization control provides for four types of filtering: time-based, event state, minimum duration, and status. Time-based filtering limits data based on a specified period of time or number of events. Event State filtering limits data based on whether the event was acknowledged, unacknowledged or it can be set to both to not filter by event state. Minimum duration filtering limits data based on a duration by only showing those events that lasted as least as long as the minimum duration. Status filtering limits data based on the utilization status (that is, run time or downtime). Any combination of these four types of filters may be employed. A description of the current filter will be displayed in the control, so the user will always know what filter criteria are being used. For further detail on filtering, see Configure the filters.

The Multiple Selection for Reason Entry function is provided to allow the user to select multiple grid rows in the Utilization control which have a reason pending and set the final reason for a series of pending rows, or allow the user to select multiple grid rows in the Utilization which are non-pending and edit the final reason. For more information, see Multiple selection for reason entry/editing.

The comments of a selected reason or multiple selected reasons can be changed without changing anything else about the reason by use the EditComments() method or the Edit Comment button on the button bar. Both calling the method and pushing the button will bring up a dialog allowing the editing of the comments associated with one or more reasons. For more information, see Utilization control methods and Buttons.

Good or rejected production can be added for a selected reason using the AddProduction() method or the AddProduction button of the button bar if the AddProduction button is enabled. Both will open a dialog box that allows the user to enter the amount of production to be added. For more information, see Utilization control methods and Buttons.