Adding OEE Configuration Objects

A number of OEE related configurations are not asset specific but apply to multiple equipments, areas or even plants. Therefore these configurations are centralized in objects of types which are dedicated to different configuration topics. These Configuration Objects are referenced by all the individual OEE Equipment Monitor Objects, to be taken into account when calculating their OEE indices, thus sharing these central configurations.

To create the connection between Sites in the ISA-95 Model and Timezone Availability Tracker objects in the I/O Model, which is mandatory for several of the following Configuration Objects, the TPM Site configuration is used.

Work shifts, including their respective local start and end times and their applicability with respect to certain times of the year, are configured using TPM Shift Configuration objects.

Special configurations regarding the fiscal year of an enterprise -as well as the calendar year- are set up in TPM Year configuration objects.

To inform the OEE Equipment Monitor object about when and why an equipment is not scheduled for production and therefore isn’t to be taken into account for OEE calculations, TPM Not Scheduled objects are used.

If an equipment, which had been scheduled for production before, had to be unscheduled again, TPM Unscheduled Configuration objects are used to inform the OEE Equipment Monitor object about the times and reasons.

By default, all equipment stops affect the OEE calculations. The TPM Stop Reason Configuration object allows to overwrite this behavior for each individual Stop Reason. Custom Stop Reasons can also be added and configured there.

If OEE Data is to be aggregated, also at least one TPM Preset Configuration object needs to be configured.