Library — Integration

No rip and replace

Every operation already runs on decades of systems that work. The fastest way to make them smarter is to leave them where they are.

How it holds up3 min read

01The problem

Replacing an operational estate is slow, risky and rarely delivers the understanding it promised.

Large operations are built in layers — an ERP from one era, a warehouse system from another, maintenance software chosen by a different team, and EDI links to partners that nobody wants to touch. A replacement programme takes years, and at the end of it the new system is still one system.

Theralon takes the opposite approach. It reads what those systems already produce and builds its understanding above them, so the value arrives without a migration and the systems of record stay exactly where they are.

The systems of record remain where they belong. The intelligence sits above them.

02How it lands

  1. 01

    Reads what already flows

    ERP, EAM, MES, WMS, TMS, CMMS, SCADA, industrial IoT, operational databases, cloud data platforms, streaming infrastructure, APIs and live telemetry.

  2. 02

    Real EDI, not a sample

    X12 and EDIFACT traffic parsed directly, with shipping notices reconciled against receipts automatically.

  3. 03

    Columns nobody predefined

    Unexpected fields are profiled, classified and used — not dropped for failing to match a known name.

  4. 04

    Incomplete feeds still count

    A source missing one field is graded on what it can drive rather than discarded, so partial data still contributes.

  5. 05

    A governed write path

    Operators can correct and extend the model directly, with every change validated, attributed to its source and versioned.

  6. 06

    A published schema

    An installable SDK and a self-describing schema give integrators typed access to the model, the risk register and model cards.

Six systems of record with lines rising into a single layer drawn above them.
Above the systems of record, not in place of them

03What changes

Value after the migration

Value without one

Data dropped for not fitting

Data used for what it can drive

Integration by tribal knowledge

Integration by published schema

04Under the hood

Both the automated derivation path and the manual write path validate against the same schema, so the published shape cannot drift from reality. A misspelled property or a relationship pointing the wrong way round is refused with an explanation — never stored as a fact indistinguishable from a real one.

Keep reading

See all

Ports and maritime

Ports, and the problem with handoffs 

Freight and logistics

Freight networks that see around corners 

Deployment and control

Sovereign by design 

If this is your operation, we would like to hear about it.

We reply personally. There is no sales queue.

Get in touch →