Case study · Product development
Every variable from every machine, in more than 50 countries, live.
Lineomatic builds book making machines and installs them at customer sites in more than 50 countries. All the machine data stayed inside the PLC on the shop floor. We built the platform that got it out.
What it changes: Lineomatic supports a customer remotely instead of flying an engineer out. Their customers get a portal of their own, which now helps sell the machine.
- Client
- Lineomatic, machine manufacturing
- Client type
- OEM with customers in 50+ countries
- Sector
- Industrial IoT, machine monitoring
- Engagement
- 2020 to 2023
- Platform
- LMMS
- Delivered
- Edge gateway, cloud backend, web app, mobile app
- Golang
- NATS
- MQTT
- Node.js
- Express
- React
- React Native
- PostgreSQL
- Time series DB
- OPC UA
- Modbus
50+
Countries with machines installed
380+
Gateways deployed
60K+
Metrics a second at peak
< 200ms
Gateway to dashboard
The ask
Every machine carries motors, mechanical parts and sensors. Lineomatic also sets its own variables in the PLC for production counts, shift details and raw material use. All of it stayed inside the PLC. Checking a problem meant calling the site or flying an engineer out, and there was no history, no alarms and nothing on mobile.
They wanted one thing. Every variable, from every machine, live on desktop and on mobile, with their own customers seeing their own machines too.
What we built
Edge gateway
A gateway written in Golang, running on a Raspberry Pi or any small Windows or Ubuntu box on the PLC network. It reads every configured variable as often as once a second, over OPC UA or Modbus. Rules run locally, so basic logic holds up without the cloud.
OEM admin panel
Lineomatic’s control room. Create customers and machines, set the protocol and fetch frequency, build device templates, then map the addresses. Configure a machine model once and roll it out to the next hundred in minutes.
Customer panel and mobile app
Each customer logs in to their own machines only. Dashboards, reports, maintenance tracking, live alarms and full alarm history. The same views run in the React Native app, so a plant head checks production from anywhere.
How the data flows
- 01The PLC holds every variable the machine writes while it runs.
- 02The edge gateway reads them over OPC UA or Modbus, as often as once a second.
- 03Readings go to the NATS and MQTT broker.
- 04Node.js services write configuration to PostgreSQL and readings to a time series database.
- 05The React web app and the React Native app read from there.
What it gave each side
Lineomatic
- Machine data live within seconds, anywhere in the world
- Remote support in place of an engineer on a plane
- A new machine live without anyone writing code
- New machine types added by their own team
- Every reading stored, so trends and reports are always there
Their customers
- A portal showing only their own machines
- Dashboards and reports assigned to them
- Maintenance tracking and full alarm history
- Alarms by email, WhatsApp or SMS before downtime
- The same views on the mobile app
The job transfers
Any OEM with machines in the field
Packaging and printing machinery
Food and process equipment
Energy and utilities hardware
Anyone with data stuck in a PLC
Plant operators
Contract manufacturers
Any factory that still phones the site to ask
More product development work
Product development · Proptech · Australia
Rebuilt in under four months, live to millions the whole time
view.com.au is the number three real estate portal in Australia. We have engineered with them since 2019, starting with one data integration and ending up inside the platform, the mobile apps and the analytics.
- 2019 to today, ongoing
- Engagement
- ColdFusion to React, monolith to services, native apps
- Rebuilt
Next
Tell us which part of this looks like your problem.
We will walk you through how it was built, who built it, and what it took to keep it running afterwards.