IndustrialBridge
Move plant data, both ways, without losing a row.
The foundation tier of TA Factory. IndustrialBridge replaces the fragile in-house scripts, VBA bridges, and per-tag historians your plant has been getting by with — a single OPC ↔ SQL engine that finally makes plant data reliable, bi-directional, and queryable.
SET oee = (good_units / planned_units) * 100
IF oee < 65 THEN flag = "WARN"
Most plants run on fragile glue code
Every plant has them — VBA macros, in-house Python scripts, per-tag historian connectors, the engineer-who-left's spreadsheet bridge. They break in monsoon, they break on patch Tuesday, they break the moment that one engineer takes leave. IndustrialBridge is the engine that finally replaces them.
Modern PLCs + legacy servers, same project
Modern OPC UA PLCs and decade-old OPC DA servers (Matrikon, RSLinx, classic KEPServerEX) coexist in most plants. Most bridges handle one or the other — IndustrialBridge handles both, in the same configuration.
Bi-directional, with handshake
Reading tags into a database is the easy half. Pushing recipes, setpoints and commands back to the PLC with confirmation and handshake — that's where in-house bridges fall over. IndustrialBridge does it as a first-class capability.
Outages can't lose rows
When the database goes down or the network blinks, an in-house bridge silently drops data and nobody knows until the audit. IndustrialBridge caches every row to a crash-safe local store and replays when connectivity returns.
Browser-managed configuration
Drag tags from the OPC browser into transaction groups. Auto-create database tables. Test, deploy and version — all from a browser, no Windows tooling.
Six capabilities that turn fragile glue into a platform
OPC UA + OPC DA, both native
Connect modern OPC UA PLCs (Siemens, Allen-Bradley, Rockwell) and legacy OPC DA servers (Matrikon, RSLinx, classic KEPServerEX) in a single project. Drag tags from the browser into transaction groups.
Bi-directional with handshake
Auto-create database tables. Push recipes, setpoints and commands from the database back to the PLC with confirmation handshake. Real two-way integration, not just data logging.
47-function Logic Tag library
Math, string, conditional, date, type conversion, bitwise. Plus inline SQL queries. Scale 4–20 mA signals, decode PLC status words, compute OEE, build batch IDs — without writing PLC code or custom .NET.
Store-and-forward caching
When the database goes down, every row is cached to a crash-safe local SQLite store and replayed when the network recovers. Your operators never know there was an outage.
Visual Report Designer
Generate banded PDF and HTML reports with multi-level grouping, calculated fields, and parameterised SQL. No Crystal Reports, no SSRS, no third-party BI tool needed.
Seven supported databases
SQL Server, PostgreSQL, MySQL, MariaDB, Oracle, SQLite, TimescaleDB. Pick what your IT team already runs — IndustrialBridge speaks all of them.
What changes when IndustrialBridge goes in
Foundation tier — built to power the next two
IndustrialBridge is the data layer that SyncPlant and TruAdaptiv Copilot build on. Deploying it well means the next tier is already ready to receive everything you build.
Portable config
Configuration lives in one portable file. Move it between environments, version-control it, ship it to another plant with one copy.
Managed in-browser
OPC browse, tag selection, transaction-group design and deploy — all from a browser. No Windows tooling, no thick client.
Plant-LAN deploy
Runs on your plant LAN. No data leaves the perimeter. Pairs naturally with the next two tiers, which also stay on-prem.
Powers Tier 2 & 3
The clean, normalised data IndustrialBridge produces is exactly what SyncPlant and TruAdaptiv Copilot were designed to consume. No re-platforming required.
Start at the foundation — and know the next two tiers are ready
IndustrialBridge is ready to deploy as the foundation of your TA Factory journey. Book a discovery call to walk through the engine and scope a deployment.
Common questions
- Does IndustrialBridge replace a plant historian?
- Not usually. A historian is built to compress and retain high-frequency time-series data; IndustrialBridge moves plant data into a relational SQL database where it can be joined, reported on and consumed by other systems. Plants whose real need is structured reporting often run it instead of a historian. Plants that need long-horizon trend storage run it alongside one.
- Can IndustrialBridge write back to the PLC, or is it read-only?
- It is bi-directional. As well as reading tags from OPC UA and OPC DA servers, it can write values back, so setpoints, recipe parameters and targets can flow from SQL down to the control layer. Write access is configured per tag rather than granted wholesale.
- What happens to data if the network or the SQL server goes down?
- Readings are buffered locally by the store-and-forward cache and replayed in order once the link returns. This is the difference between a gap in your dataset and a delay in it — the sequence and timestamps survive the outage.
- Does it support OPC DA, or only OPC UA?
- Both. Many Indian plants still run older OPC DA servers alongside newer OPC UA equipment, so IndustrialBridge speaks both and can bridge between them rather than forcing a control-system upgrade first.
- What are Logic Tags?
- A library of 47 functions for computing derived values inside the bridge — aggregates, unit conversions, conditional logic, rate calculations. It means calculated tags are configured where the data already is, instead of needing a separate scripting layer or a downstream ETL job.
- Does IndustrialBridge need internet access?
- No. It runs entirely on the plant network and has no cloud dependency, which is what makes it deployable in segmented or air-gapped plant environments.