OPC Router is bidirectional communication software between IT and OT from a single center. It connects to SAP systems, SQL and NoSQL databases, printers, barcode readers, email and messaging systems, and more. With its visual drag-and-drop configuration, it saves time and money in projects.

SAPRFC integration
SQL / NoSQLDatabases
OPC UAMQTT · REST · ODBC
No codeDrag & drop

Next-Generation Industrial Connectivity

Innovative, simple, effective. OPC Router is a central integration platform that automates and optimizes data exchange in your networked production processes. No programming knowledge required: model your data flows visually — OPC Router handles the rest.

Key Features

Drag & Drop Configuration

Model data flows visually — no programming knowledge required; maintenance and changes are done in minutes.

Condition & Event-Based Data

Trigger data exchange on conditions and events: notification, logging or actions when a value threshold is exceeded.

Broad Protocol Support

OPC UA, OPC DA, MQTT, REST/JSON, ODBC, Modbus, Siemens S7, Beckhoff ADS and more.

Bidirectional Data Flow

From OT to IT systems and back — for example production orders from SAP to PLCs, consumption records from PLCs to SAP.

Plugin and Driver Support

OPC Router has a large plugin collection for the following systems:

  • Databases: SQL Server, Oracle, MySQL, PostgreSQL, NoSQL (MongoDB, InfluxDB), ODBC
  • Enterprise systems: SAP (RFC), MES systems, REST/JSON APIs
  • Messaging: Email, SMS, Telegram, Slack notifications
  • Office & production: Excel, CSV, printers, barcode readers
  • Industrial: OPC UA, OPC DA, MQTT, Modbus, Siemens S7, Beckhoff ADS
  • Cloud: Azure, AWS and generic MQTT brokers

How a data flow is built

In OPC Router every integration is a flow: it starts with a trigger, reads from a source, transforms the data and writes to a target. When the structure of the flow is clear from the start, error handling can be designed from the start too.

  1. Source and targetWhich system to read from and which to write to? Connections (plugins) are defined for both directions.
  2. TriggerWhen should the flow run: a timer, a value change, a signal or an event.
  3. Mapping and transformationFields are mapped; values are transformed while type, unit and timestamp are preserved.
  4. Writing to the targetThe database, SAP, MES, MQTT or file target is updated.
  5. Error behaviourRetry, logging and the alert path are defined in advance for when a connection drops.
  6. Acceptance testThe flow is tested end to end with real data and the results are recorded.
The anatomy of a data flowA flow starts with a trigger, reads from a source, transforms the data, writes to a target and logs the result; on error a retry or alert path takes over.failedTriggerTime, change,condition1Read sourceOPC UA, PLC,SQL, SAP2TransformType, unit,mapping,validation3Write targetSQL, MQTT,MES/ERP, PLC4LogResult,duration,id5Error pathRetry, back-off, alert; without losingdata
Every flow should have one purpose, one trigger and a defined error behaviour.

OPC Router and Kepware Server Together

In a typical architecture, field controllers connect to Kepware Server; OPC Router receives this data and distributes it to enterprise systems — SAP, databases, MES, reporting, printer/barcode lines and the cloud. Together, the two products form an end-to-end, bidirectional and traceable data backbone from production to the enterprise.

The data path from the field to target systemsKepware Server collects data from PLCs, meters and legacy devices; OPC Router moves it to SQL, MES/ERP and MQTT targets using triggers and transformation rules.FieldAcquisitionIntegrationTarget systemsPLCsSiemens, Rockwell,Mitsubishi, ABBMeters /analysersModbus and similarLegacy devicesSerial, proprietaryKepware ServerDrivers, tags, OPCUA and DA serverOPC RouterTriggers, mapping,transformation,routingSQL databaseTables, recordsMES / ERPOrders, recipes,resultsMQTT / cloudPublish,analyticsReading and writing are designed together: orders and recipes flow down, measurements and results flow up
Acquisition, integration and delivery are separate layers; type, unit, timestamp and quality are preserved at every step.

Frequently asked questions

Is OPC Router a SCADA or a historian?

No. OPC Router is an integration layer: it moves and transforms data between systems. SCADA or a historian is still used for visualisation or long-term archiving; OPC Router can exchange data with them too.

Does it connect to field devices directly?

It can connect over OPC UA, Modbus, Siemens S7 and similar protocols. With many controllers of different brands, Kepware Server is usually used as the acquisition layer and OPC Router takes the data from that server.

How does data exchange with SAP work?

A plugin based on RFC is used for SAP; data such as production orders can flow to the PLC and data such as consumption records to SAP, in both directions. For scenarios like recipe transfer we have a separate checklist on controlled writing.

Is data lost if the connection drops?

That depends on how the flow is designed: retry, buffering and error logging are defined inside the flow. We cover the topic in detail in our article on redundancy and buffering.

Next step

Plugin listThe systems it can connect toDesigning data flowsTriggers, transformation and error handlingPLC data to SQLFive design decisionsIntegration acceptance testsWhat to test once the connection worksKnowledge baseFrequently asked questions and solutionsDemo and project discussionWe will prepare a scenario for your architecture

OPC Router Product Site

All up-to-date OPC Router information — product features, plugin list, solutions, pricing and the demo version — is published at opcrouter.com.tr.

opcrouter.com.tr ↗ Plugins Pricing Demo Version

You can use the demo form to request an OPC Router demonstration.