OPC data integration

This page explains how an integration with OPC will work and be set up for RS Production.

OPC UA

Newer version of OPC where it’s more flexible where integration client can be installed.

No need to open ports for incoming data

All data traffic to the RS Production cloud service is initiated from the local clients.

There is never any traffic that is initiated from the RS Production Service on the Azure cloud.

Traffic is on port 443 (or 80 with http)

Principles for OPC-data to RS Production

Principles for capture of cycles, produced and scrapped amounts

OPC update rate is about 0.1 seconds, which is slow in a real time context. To avoid missing cycles and pulses, RS Production uses an increasing counter. If you want it is possible to set a reset point where the counter restarts at 0.

Exemple with a reset point at 9 999

Principles for capture of machine uptime signals

RS Production reads operating signals (uptime/downtime) every second.

Every reading cycle, RS Production reads (samples) the current value of a specified field. This means that the system does not log any information about the exact time (in milliseconds) since the field changed.

Principles for collecting automatic reason encoding and station encoding of downtime

RS Production can automatically capture and categorize stops with both reason code and station code.

Each reason code and station code needs a specific OPC field that reflects its status.

Principles for machine alarm signals

RS Production can capture machine alarms and store them in a table available in Office tools.

Machine alarms in RS Production has one of two possible statuses in the table to the right.

Each alarm needs to have its own OPC-field and RS Production timestamps the status changes.