Skip to main content

⚙️ OPC UA Connections: Live Data From Your PLCs and SCADA

How OPC UA brings live values from your PLCs, SCADA systems, and historians onto your Production Entities — and what setup looks like.

Written by Alex Merkin

📌 What Is an OPC UA Connection?

If your factory floor has a PLC, a SCADA system, or a historian, there's a very good chance it already speaks OPC UA — the standard industrial protocol that almost every modern machine controller supports.

An OPC UA Connection in Next Plus is a bridge between that equipment and your Production Entities. Once it's set up, live values from the PLC — temperatures, pressures, cycle counts, statuses — appear on the same screen your team uses every day.

No more walking to the panel. No more screenshots of the SCADA. The values are there, updating in real time, attached to the right machine in Next Plus.


🏭 When Does OPC UA Fit?

OPC UA is the right choice when:

  • Your equipment is a PLC, SCADA, or historian — Siemens, Rockwell, Beckhoff, Ignition, AVEVA, iFix, and so on

  • You want to browse what's available on the machine and pick the variables you care about

  • You need near-real-time data — values arrive within about one second of changing

  • Your IT or controls team has security requirements that map to industrial standards (signed and encrypted sessions, named user accounts)

If your equipment doesn't speak OPC UA natively, a small gateway box (from companies like Kepware, Matrikon, or Inductive Automation) usually bridges older protocols like Modbus or OPC-DA into OPC UA — and then Next Plus reads it the same way.


🛠 How OPC UA Connections Work

In plain terms:

  1. You add the server — Next Plus opens a long-lived session to your PLC or SCADA endpoint

  2. You browse and pick — a tree view shows everything the server exposes; you tick the variables (NodeIds) you want on a specific Production Entity

  3. The server pushes updates — every time a value changes, the PLC sends it to Next Plus. Next Plus never asks; it just listens.

  4. The value lands on the PE — visible on dashboards, available for triggers, logged for history

Unlike a database (where Next Plus has to ask "what's the latest?" every few seconds), OPC UA is a push model. The PLC tells Next Plus the moment something changes. That's why it's the closest to real-time of the four connection types.


🔒 Security

Read-only, always. Next Plus reads from your PLC. It cannot write, cannot send commands, cannot change setpoints. Your controls engineers remain in charge of what the machine does.

OPC UA offers three security levels — your IT or controls team picks the one that fits your network:

  • None — quick to set up for lab and dev environments. Not recommended outside an isolated network.

  • Sign — messages are signed so they cannot be tampered with in transit

  • Sign & Encrypt — recommended for production. Messages are signed and encrypted end to end.

When you choose Sign or Sign & Encrypt, Next Plus connects with a dedicated username and password on the PLC — your controls team creates that user with browse-and-read permissions only on the specific variables you want exposed.


🏭 Common Scenarios

🔥 Furnace Temperature Live On The Floor

Before: The furnace's temperature lived on the SCADA screen in the control room. Operators on the line couldn't see it without walking over.

After: An OPC UA connection reads the temperature once a second straight onto the furnace's Production Entity. A trigger flips the PE to "Fault" if it drops below the setpoint.

Outcome: Faster reaction to drift, automatic status, no walking back and forth.


⚙️ CNC Cycle Counter

Before: Cycle counts for OEE were estimated from production logs at the end of the shift.

After: OPC UA pulls the cycle counter directly off the CNC's PLC. The number is live on the operator's screen and feeds the OEE calculation in real time.

Outcome: Real OEE, not estimated. Shift leads see performance live.


🛠 Press Line Status

Before: When the press stopped, the shift lead had to find out why from the operator.

After: OPC UA reads the press's run/stop state and fault code. Next Plus flips the PE status automatically and surfaces the fault code on the screen.

Outcome: Downtime root cause is captured the moment it happens.


💡 Real-Life Examples By Industry

See if any of these sound like your factory:

🏥 Medical Devices

Use Case 1: Autoclave Sterilization Cycle

Before: Chart recorders captured the cycle profile; someone had to attach it to the batch record.
Connection: OPC UA reads temperature, pressure, and door state directly off the autoclave PLC into the Production Entity.
Benefits:

  • ✅ Continuous validation evidence per batch

  • ✅ ISO 13485 audit-ready

  • ✅ Immediate alert if the cycle drifts

Use Case 2: Cleanroom Differential Pressure

Before: Cleanroom pressures were logged manually twice a shift.
Connection: OPC UA streams pressures from the building management PLC.
Benefits:

  • ✅ Continuous environmental monitoring

  • ✅ Automatic alerts on excursions

  • ✅ No paperwork on the floor

🧃 Food & Beverage

Use Case 1: Filling Line Throughput

Before: OEE was estimated end-of-shift from bottle counts and rough downtime notes.
Connection: OPC UA reads the filler's cycle counter and run state off the line PLC.
Benefits:

  • ✅ Real OEE numbers

  • ✅ Downtime captured at the second it happens

  • ✅ Performance visible live on the shift dashboard

Use Case 2: Pasteurizer Hold Temperature

Before: Pasteurization records were a chart-recorder strip stapled to the batch sheet.
Connection: OPC UA reads hold temperature continuously.
Benefits:

  • ✅ HACCP-compliant electronic records

  • ✅ Easy deviation investigation

  • ✅ Faster batch release

✈️ Aerospace & Defense

Use Case 1: Torque Test Bench

Before: Torque values were transcribed from the test bench screen into batch records.
Connection: OPC UA reads torque, angle, and pass/fail directly from the bench controller, tied to each serial number.
Benefits:

  • ✅ Zero transcription errors

  • ✅ Per-serial-number traceability

  • ✅ Audit evidence ready instantly

Use Case 2: CNC Tool Life Tracking

Before: Tool changes were scheduled on the calendar, not on actual use.
Connection: OPC UA reads tool-life counters from the CNC.
Benefits:

  • ✅ Tool changes based on real wear

  • ✅ Fewer scrapped parts

  • ✅ Predictable maintenance windows

🧪 Pharma / Cosmetics

Use Case 1: Mixer Cycle Profile

Before: Mixer speed and time were written into the batch record after the cycle.
Connection: OPC UA reads mixer RPM, motor load, and elapsed time live for the full batch.
Benefits:

  • ✅ Complete batch profile captured automatically

  • ✅ GMP-compliant electronic records

  • ✅ Deviations spotted live

Use Case 2: Reactor Temperature & Pressure

Before: Reactor data sat on the DCS; batch records pulled from a separate report.
Connection: OPC UA streams reactor parameters continuously.
Benefits:

  • ✅ Live batch oversight

  • ✅ Auto-attached process data per batch

  • ✅ Smoother release process

📱 Electronics Assembly

Use Case 1: Reflow Oven Profile

Before: Oven profiles were documented on paper attached to each tray.
Connection: OPC UA reads zone temperatures and conveyor speed live, tied to each batch.
Benefits:

  • ✅ Digital reflow profile per batch

  • ✅ Process control visibility

  • ✅ No paperwork on the line

Use Case 2: SMT Line Pick-And-Place Counters

Before: Production counts were reconciled at the end of the shift.
Connection: OPC UA reads component placement counters off the line.
Benefits:

  • ✅ Live throughput visibility

  • ✅ Component consumption tracking

  • ✅ Faster end-of-shift reporting


🚀 What Setup Looks Like

You don't do this alone. Your CS team and your controls / IT team work together. Here's the rough shape:

  • Step 1 – Make sure the PLC speaks OPC UA
    Most modern PLCs do. If yours doesn't, an OPC UA gateway box is the standard answer.

  • Step 2 – Get the endpoint URL and a dedicated user
    Your controls team creates a read-only user on the PLC and gives you a URL like opc.tcp://plc.factory.local:4840.

  • Step 3 – Add the connection in Next Plus
    From Modeling → Production Entity → OPC UA Servers, click the red +, paste the URL, pick a security level, enter the credentials, and hit Test Connection.

  • Step 4 – Bind variables to your Production Entities
    Open a PE, scroll to Parameters, and use the wizard to browse the PLC's address space. Tick the variables you want — they appear live on the PE.

Want help mapping it out? Contact us via chat and we'll walk through the network, security, and what variables to start with.

Did this answer your question?