The OEE Equipment Monitor Setup
With the OEE Simulation prepared and a Timezone and Availability Tracker configured for the Connector where the simulation data is produced, the time has come to create the OEE Equipment Monitor as the central element of OEE calculation in system:inmation.
Go to the ISA-95 Equipment Model and select the asset, for which you want the OEE indices to be calculated. In our example this is 'The OEE Demo Cell'. Right click on this object and selectto open the Create Equipment Monitor wizard which we will now go through step by step.
In the Common section, give the new object a suitable name and, optionally, add a description of the object’s function. Leave the Processing Mode on 'Configuration'. When done, click Next to go to the next section.
|For initial setup and all later configuration changes, the Processing Mode should be set to 'Configuration'. Setting this to 'Production' to starts the OEE calculation.|
The Configuration Options can link to specific OEE Configuration Objects, which will be addressed later, when we are Adding Configuration Objects. For this basic example no Configuration Objects are needed, so you can skip this section by clicking Next once more.
In the Processing Options select a Trigger Source which indicates the start and end of a production cycle and trigger the OEE calculation. In this example, please select 'Quantity Dropped', then click Next.
The Measurement Options inform the OEE Equipment Monitor about how the product is measured. The Performance Measurment Type specifies if Discrete Units are to be counted or Volume or Mass to be measured. Depending on the selection here, individual options allow to specify the unit in which the product which is produced on this asset is measured. For the example, leave everything in it’s default setting and click Next to continue.
The Availability Options inform the OEE Equipment Monitor about the planned availability of the asset. Default value is 'Continuous Availability (24/7)' but it can also be set to 'Shift Regime', which means there is a more detailed availability configuration, defined in a specific TPM Shift Configuration Object. This object will be addressed later.
For this example, leave the Availability Type on its default value 'Continuous Availability (24/7)' and click Next to continue.
The Quantity Options link the OEE Equipment Monitor to the objects in the I/O Model which hold the current quantity data for the production. In other words, these fields tell the monitor how much was produced and possibly rejected.
Add the Total Quantity Input. To do this click the … icon for this property, expand the I/O Model tree and select the 'QuantityTotal' variable object from the OEE Simulator, then click OK to confirm your selection and close this dialog window.
Then add the Good Quantity information: Check the checkbox for Good Quantity Available and select the Good Quantity Input in the same way as the Total Quantity Input. Then click Next to continue.
In the Performance Options section the key values regarding the asset’s performance are configured. The 'Default …' values are asset specific.
In the Product Options section the ideal production outputs are defined. Product specific values can be entered in a table and default valued provided, if the product can not be found in this table.
Products are identified by their name, which has to be provided by an object in the I/O Model tree. To connect the OEE Equipment Monitor to this object, it again has to be selected as the Product Name Input, clicking on the … icon.
Then click on the 'table' icon for the Product Configuration property to open the Product Configuration table. For each product defined in the OEE Simulator script add a line, entering the values for 'Product Name' and 'Performance' from the 'Product Database' section of the script.
Click OK to close the table.
If configured, Default Performance, Default Quantity Multiplier, and Default OEE Target will be used as fallback values if the current product can’t be found in the Product Configuration Table.
To be able to consider the state of an equipment in the OEE calculation, the OEE Equipment Monitor needs to be linked to an object in the I/O Model which can be used as the Input for the current state of this equipment. This state has to codified according to the EquipmentStates Coding Group
Set the Equipment State Input to be linking to the 'Equipment State' object of the OEE Simulator, in the same way as the other Inputs before.
The system uses Equipment States according to the ISA-88 specification. To be useful for the OEE Monitor, these status codes need to be translated into the corresponding TPM Time Categories. This translation is configured in the State Time Assignment table.
Click on the table icon for State Time Assignment property.
In the table, add a line for each state which is to be mapped. In each line select the Equipment State and the corresponding Time Category from the respective drop-down lists.
For our example, set the State Time Assignment table to match the following configuration:
Then click OK to close the table display.
Failures can be signalled to the OEE Equipment Monitor object in four different ways: by an error flag, an error code, an error message or an OPC A&E message.
Since the OEE Simulator script sends out error codes in case of failure, we select its Error Code variable in the I/O Model as the Equipment Error Code Input property.
When all Performance Options are configured, click Next to continue.
Our example is running a batch production, so we provide a link to the BatchID Input by clicking on the … icon …
... selecting 'Batch ID' from the OEE Simulator in the I/O Model tree and clicking OK to confirm the selection and close the object picker window.
The Stop Reasons Filter Options are used to restrict the options which will be available in WebStudio when annotating stop records with stop-reason codes.
The system has a number of built-in reasons for equipment stops, which may be assigned to stops in the OEE Equipment Stops table. By default all stops affect the calculation of the OEE Indices. This behavior can be overridden in Stop Reason Configruation Objects. Also Custom Stop Reasons can be defined there.
NOTE: Micro stops don’t affect the Availability Index, but rather the performance metric.
In the Stop Reason Filter table ranges of Stop Reasons which will be made available in WebStudio can be specified.
|If no range is specified in this table, all defined Stop Reasons will be available in WebStudio. If at least one range is defined in this table, only the Stop Reasons which are included in the specified range(s) will be visible.|
To add a range of Stop Reasons, follow these steps:
In the Stop Reason Filter Options, click on the table icon for the Stop Reason Filter property to open the Table Property Grid.
In the Table Property Grid, click on the + icon to add a new line to the Stop Reason Filter table.
In this new line, select the first Stop Reason of such the range from the drop-down list in the
Stop Reason Fromcolumn.
Select the last Stop Reason of this range from the drop-down list in the
Stop Reason Tocolumn.Figure 19. Filtering Built-in Stop Reasons
Click OK to close the Table Property Grid.
Finally, Apply the changes to the properties.
The Custom Stop Reason Filter property is used to define filters on the attribute fields of custom stops reasons. When editing the stops reasons in WebStudio, all available reason codes and custom stop reasons are presented to operators for selection.
It may however be that some stop-reasons only apply to certain machines, which is indicated by setting one or more of their attributes to the machine type or model or make for example.
The set of custom stop reasons presented to users in WebStudio can be controlled by defining filter expressions. Each row in the configuration table is set to contain strings that should match with corresponding attributes. A reason is included if any of the row expressions match. For example, suppose we want to return all custom reason strings where (attribute1 == “X” and attribute2 == “Y”) or (attribute1 == “Z”). This would be accomplished with the following settings in the filter table:
|Custom Filter 1||Custom Filter 2||Custom Filter 3|
The 'Custom Filter' columns correspond to the Custom Attribute columns of TPM Stop Reason Configuration objects. If the defined Custom Attributes match the corresponding Custom Filters, the Stop Reason will be visible.
|Custom Stop Reasons Filters are additive to the Stop Reason Filters. This means that Custom Stop Reasons will be included in the list of visible Stop Reasons if they are included in the Custom Stop Reason Filter - even if they fall within a range which is NOT included in the Stop Reason Filter.|
Now all of the relevant configurations for the OEE Demo Equipment Monitor have been made, so click Create to create the monitor object.
The new OEE Equipment Monitor object will appear underneath the cell for which we created it.