Automated run-time context data collection

Each piece of equipment can have several OEE data property tags assigned to it. Each of these tags can drive the setting of a property value for a specific OEE data property.

• The tag is mapped to a specific OEE data property name in the efficiency model configuration. During run time, the tag’s value is written as the OEE data property value.

• To be processed, the tag value must be a string.

• The second/millisecond portion of the tag’s value, time, and quality (VTQ) indicator are removed when writing the property value. Only one update can be received in a given minute; other updates within that time are ignored.

• OEE data properties are not meant to be changed more frequently than several times a day. Exceeding this expected frequency can cause performance problems.

• When possible, tag values should be current and sent in chronological order. However, support for store-and-forward scenarios does exist.

  You cannot update an existing OEE data property value by passing a new value with an existing timestamp. However, you can add older, missing data properties (that is, using store-and-forward).

• It is recommended that OEE data property tag updates be sent before production counter tag updates. This recommendation mainly applies when the updates are in your control, such as when uploading a CSV or JSON file of tags.

• VTQs with bad quality are ignored.