How systems connect

The wiring layer

The Integration Hub creates and maintains live, structured connections between the Singularity and every external system already in place.

It does not replace existing systems. It makes the data inside them usable. It reads from each source, normalizes what that source produces, makes the result available to every other module, and handles writes back to source where a workflow needs them.

What it connects to

• The main business software for orders, inventory, and finance (ERP)
• The system that monitors and controls equipment across a plant (SCADA)
• The small computers that control individual machines (PLCs)
• Internet-connected sensors and devices
• Quality platforms, scheduling tools, and third-party cloud apps

The integrations page covers the same ground for someone deciding whether to buy, and the Integration Hub reference has the full module detail.

Moving data by hand

Data exists in every system an operation runs. It just does not move between them without someone doing it by hand.

A production order lives in the ERP. Machine telemetry sits on the PLC. Quality results live in a spreadsheet. Nobody has a current picture, because assembling one means pulling from five systems by hand. Operators export, paste, and reconcile. Fragile point-to-point integrations get built by someone who has since left. Shift-end reconciliation becomes a standing meeting, and decisions get made on data that is already hours old.

Protocols

The Integration Hub speaks the common technical languages systems use to talk to each other:

• REST
• SOAP
• OPC UA
• MQTT
• File-based protocols

These terms are not needed to understand what the Hub does. They matter when a specific connection gets scoped, because the protocol a source system already speaks decides how that connection is built.

Connection health

Every signal that flows through the Integration Hub is schema-normalized and source-tagged, so every module downstream works from the same values and can trace where each one came from.

Connection health monitoring watches each connection continuously. When one drops, it is flagged before it causes a downstream error, so a module never works from stale or missing data without anyone knowing.

Integration work already done

Custom integrations built in-house stay in place. The Integration Hub is the wiring layer going forward, and what it connects to, in what order, is a scoping conversation rather than an all-or-nothing rebuild.

The Developers section covers the same material for a technical reader, alongside what your own team configures inside the platform.