OPC Router 5.7: Conditions, Functions, and Smarter Flows

What Is OPC Router?

Modern manufacturing depends on data moving between two very different worlds.

On the plant floor, PLCs, machines, sensors, and industrial systems generate the information needed to run production. At the business level, systems such as SAP, MES, databases, APIs, and cloud applications need that same information to make decisions, track production, manage inventory, and coordinate operations.

OPC Router is an industrial integration platform designed to connect those two worlds.

It allows manufacturers to move data between OT and IT systems using configurable connectors and visual workflows instead of building and maintaining a custom integration application for every connection.

That makes OPC Router particularly useful in industries such as automotive, food and beverage, pharmaceutical, consumer products, and other manufacturing environments where production data frequently needs to move between machines and enterprise systems.

Build Industrial Integrations Visually

The connectors are only part of the story.

What makes OPC Router especially useful for engineers is its visual workflow environment.

Instead of burying integration logic inside custom applications or scripts, engineers can build a Flow that shows where the data comes from, what should happen to it, and where it needs to go next.

A Flow might read production information from a PLC, transform the data, evaluate a condition, write the result into SAP or a database, and trigger another action.

Because the process is visible, another engineer can open the project later and understand how the integration works without first reverse-engineering a large amount of custom code.

How Manufacturers Use OPC Router

Build More of the Application Directly in the Flow

The most important changes in 5.7 give engineers better ways to make decisions, reuse logic, recover from errors, and manage application state.

01. Condition (IF): Put Decisions Directly in the Flow

Most integration projects eventually need branching logic.

Maybe a value should only be sent to the MES when it exceeds a limit. Maybe one production state should trigger an ERP update while another should only be logged. Maybe a response from an API determines what happens next.

In older project designs, logic like that could spread across several Flows or require scripting.

The new Condition (IF) object gives you a more direct approach. You can evaluate a condition and route the process accordingly without hiding that decision inside custom code.

The value here is not just fewer steps. It is visibility. Someone opening the project later can see the decision as part of the Flow itself.

Why this helps:

• Keeps related logic together
• Reduces the need for simple custom scripts
• Makes troubleshooting easier
• Makes projects easier for another engineer to understand

02. Function (FX): Stop Rebuilding the Same Logic

A common maintenance problem in integration projects is duplicated configuration.

If ten, twenty, or thirty machines all need the same data preparation sequence, it is tempting to copy that sequence into every Flow. That works until the process changes.

Then every copy has to be found, updated, and validated.

The new Function (FX) capability lets you define reusable logic once and call it wherever it is needed.

If the requirement changes later, the update happens in one place.

Why this helps:

• Reduces duplicated configuration
• Makes standards easier to enforce
• Lowers the risk of inconsistent changes
• Simplifies long-term maintenance

For larger projects, this may be one of the most valuable additions in the release.

03. Try/Catch: Build Recovery Into the Integration

Industrial integrations fail for plenty of reasons that have nothing to do with the original project design.

An ERP may be unavailable for a few seconds. A database may reject a transaction. A REST endpoint may time out. A network connection may briefly drop.

The new Try/Catch capability lets you decide how OPC Router should respond when those failures occur.

Rather than treating every error as the end of the process, the Flow can be designed to take a recovery path.

Imagine an order being sent from production to an ERP system. If the ERP does not respond, the Flow can attempt the transaction again before escalating the issue.

That moves error handling from a reactive troubleshooting task into the actual design of the integration.

Why this helps:

• Temporary failures can be handled automatically
• Operators do not need to intervene for every transient error
• Troubleshooting information can be captured closer to the problem
• Integrations can be designed with recovery in mind

04. Variables: More Useful Than Simple Storage

Variables in OPC Router 5.7 received a broader redesign.

In a large project, variables may be used for machine state, counters, configuration values, measurements, credentials, intermediate calculations, and many other tasks.

Once the number of variables grows, organization becomes important.

Version 5.7 adds a folder-based hierarchy, making it easier to group and navigate variables in larger applications.

Sensitive information can also be stored using a secret string type, helping keep credentials and other protected values out of plain view.

The bigger functional change is aggregation.

Variables can now calculate values such as:

• Minimum
• Maximum
• Average

That means some calculations that previously required dedicated helper logic can now happen directly at the variable level.

That reduces both the amount of data sent downstream and the amount of custom logic required to calculate it.

Why this helps:

• Better organization for large projects
• Safer storage of sensitive values
• Less calculation logic to maintain
• More flexibility for dynamic project designs

Make Certificate Management More Scalable

The larger the OPC UA environment, the more important centralized certificate administration becomes.

05. OPC UA GDS: Manage OPC UA Certificates More Centrally

Certificate management can become tedious quickly in larger OPC UA environments.

One OPC Router installation is manageable. Dozens of installations across multiple facilities are a different story.

Version 5.7 adds support for OPC UA Global Discovery Server (GDS) certificate management.

This allows OPC Router certificates to be managed through a centralized certificate infrastructure rather than handled individually on every installation.

Why this helps:

• Reduces manual certificate work
• Helps avoid issues caused by expired certificates
• Gives IT a more centralized management model
• Scales better across multi-site deployments

More Changes Worth Knowing About

Change Gate: Avoid Sending the Same Data Repeatedly

Many industrial systems generate values continuously even when those values are not changing.

The new Change Gate makes it possible to continue a Subflow only when a monitored value has changed in a meaningful way.

That can be useful when writing to databases, sending MQTT messages, calling APIs, writing files, or pushing information to cloud services.

Instead of repeatedly sending the same value, OPC Router can wait until there is actually something new to process.

For high-volume applications, that can reduce unnecessary transactions and load on downstream systems.

Database Log Table Transfer Object

The new Database Log Table transfer object helps reduce some of the setup work involved in building database logging applications.

OPC Router can inspect the target table structure and provide options for handling differences, simplifying the initial configuration for supported relational databases.

Plug-In Instance Management

Plug-in instances can now be disabled when they are not needed, including options for OPC Router to handle this automatically.

That can reduce unnecessary connections and make larger projects easier to manage.

Updated Terminology

You will also notice a few naming changes in version 5.7:

• Connections are now called Flows.
• Arrows are now called Item Links.

These changes better reflect the way OPC Router projects are structured visually.

Updated Platform

OPC Router 5.7 is built on .NET 10 and also introduces automatic logout after periods of inactivity.

Why OPC Router 5.7 Matters

The strongest part of this release is how the features work together.

Condition (IF) makes decisions easier to see.

Function (FX) reduces duplication.

Try/Catch makes recovery part of the project design.

The updated variable system gives projects a cleaner way to hold, organize, protect, and summarize information.

OPC UA GDS reduces certificate administration, while Change Gate helps cut unnecessary communication with downstream systems.

For teams supporting projects across multiple machines, production lines, or plants, that can be more valuable than simply adding another connector.