Skip to main content
LIOMO
Request a demo

Technology · Systems Integration

New data, working inside the systems you already run

We connect devices and new platforms to your existing business and building systems, so information reaches the place where decisions are already made.

Talk to an engineerExplore our solutions

Overview

Value appears when systems share data

A new sensor network or platform rarely stands alone. Fuel costs belong in accounting, stock levels belong in the warehouse system, and alarms from a plant room belong where the facilities team already works. When data stays on a separate screen, people copy it by hand or stop looking.

Integration is where we connect these pieces: devices and new platforms on one side; ERP, accounting, warehouse management, CRM, and building or process control systems on the other. We map what each system knows, agree which one is the source of truth for each record, and choose a method of exchange that both sides can support reliably.

We prefer to start with one data flow that matters, prove it with real data, and add the next once the first is stable.

Integration map · typical connections

Principles

How we approach integration

  • 01

    One source of truth

    For each piece of data we agree which system owns it, so two systems never quietly disagree about the same customer, vehicle or stock level.

  • 02

    Use what systems support

    We work with the interfaces your systems already offer, whether that is a modern API, a message queue, a nightly file or an industrial protocol.

  • 03

    Your data stays yours

    Data is kept in formats and places you control, with exports and documented interfaces, so changing supplier later, including away from us, stays possible.

  • 04

    Failures are visible

    Each integration records what it sent and received, retries when a system is unavailable and raises an alert when it cannot recover on its own.

Building blocks

Integration methods

These are options, not a fixed recipe. The right choice depends on what each system supports and how fresh the data needs to be.
  1. 01

    APIs and webhooks

    Direct, near-real-time exchange between systems that offer modern web interfaces.

    • REST APIs
    • Webhooks
    • JSON
    • OAuth 2.0 and API keys
  2. 02

    Messaging

    Queues and brokers that pass events between systems, even when one side is briefly unavailable.

    • MQTT
    • Message queues
    • Event streams
    • Retries and dead-letter handling
  3. 03

    File exchange

    Scheduled transfers for systems that work in batches or have no live interface.

    • CSV and spreadsheet files
    • XML
    • SFTP
    • Scheduled imports and exports
  4. 04

    Industrial and building protocols

    Open standards for reading from, and where agreed writing to, plant, building and process equipment.

    • OPC UA
    • Modbus RTU and Modbus TCP
    • BACnet
    • Read-only access by default
  5. 05

    Business systems

    The categories of system an integration project typically connects to.

    • ERP
    • Accounting
    • Warehouse management (WMS)
    • CRM
    • Building management (BMS)
    • SCADA

Engineering practices

Engineering practices

Map before building
Each data flow is written down, with source, destination, fields, frequency and owner, and agreed with your team before any code is written.
Read before write
New connections start read-only. Writing back to a business or control system is added only once the data has been checked and the change agreed.
Safe to repeat
Messages carry identifiers, so a retry or a duplicate file does not create a second invoice, order or record.
Every exchange logged
Each exchange is logged with its result, so a missing record can be traced to the step where it stopped.
Test away from live data
Integrations are tested against test or sandbox copies of the target system where they exist, before they touch live records.

Applied in

Solutions

FAQ

Questions buyers ask

Can you integrate with our ERP or accounting system?

Usually, if the system offers an API, supports file import and export, or has a database we are permitted to read. We review the interfaces available and agree the data flows before choosing an approach. Each integration is built and tested for your system rather than taken off the shelf.

What if our system has no API?

Many older systems can still exchange scheduled files, such as CSV or XML, or expose data through a reporting database. These are slower than an API but are often reliable enough for daily figures such as costs or stock levels.

Will integration affect our building or plant control systems?

Connections to building management or SCADA systems start read-only. Any write access, such as changing a setpoint, is agreed with the people responsible for the equipment, limited to specific points and logged.

Who owns the data that flows through an integration?

Our approach is that your operational data belongs to you. We design integrations so it is stored in systems and formats you control, can be exported, and is described in documentation another team could follow.

Technology areas

Discuss the technical side of your project

Bring your engineers. We are happy to go into protocols, data models, security and integration details.

Request a demoContact us