The signs get lost.
Pressure dropping little by little, a failing voltage or starts that don’t catch. Nobody sees them until the machine stops.
We fit gauges and a control unit to the machine. The data goes straight into a program that analyses it, cross-references it and shows you how each one is doing and what has happened. It alerts you if something goes outside its limits, generates reports and lets you export them. We build both parts: what goes on the machine and the software.
Read pressures, voltages, starts and whatever you need on the machine.
Receives the signals, processes and stores them.
Over the network with coverage. If not, downloaded in person.
The data goes straight in. It analyses it, cross-references it and keeps the history.
Shows how each machine is doing and what has happened.
Compares with the limits and alerts your phone or email.
Before it breaks, a machine gives signs. It monitors many of them itself, but usually doesn’t store them or tell you. Everything else is scattered across paper job sheets, an Excel file, the site manager’s WhatsApp and the mechanic’s memory.
Pressure dropping little by little, a failing voltage or starts that don’t catch. Nobody sees them until the machine stops.
They depend on someone checking the counter. If nobody does, the machine keeps working.
What the engine shows, what goes on the job sheet and what gets invoiced are three different numbers.
Without hours, fuel and repairs together, you can’t tell which one pays off and which doesn’t.
A lot can be measured, in different ways. What’s measured and how depends heavily on the machine, its model and where it works: on some you can measure more and on others less. If the machine gives the signal, it gets read. If it doesn’t, a sensor can be fitted. These are examples, not a limit.
This is a very simple example. It’s nothing like what can be done: real dashboards are far more complete, with charts, comparisons and everything you need to see.
Today, 10:32Machine 2: oil pressure has dropped below the manufacturer’s minimum.
Made-up values. Each company decides which machines and which data it wants to see, and how.
They’re fully configurable to your liking: per machine and per reading, with the limits the manufacturer recommends or the ones you decide, choosing who gets alerted and how. When a limit is passed, or something gets gradually worse, you get an alert saying what happened and when. For example:
Oil pressure dropped below the manufacturer’s recommended minimum.
Still above the recommended temperature. If it continues, it may deteriorate.
Several failed start attempts in a row. Battery voltage is falling.
Few hours left until the service. It’s recorded that the alert was sent.
Each reading is stored with its date and time, off the machine. So you can find out what happened weeks later, even if no trace of it remains on the machine.
Whether it was worked beyond its limits, when and for how long. Useful if you sell with a warranty, if you rent out and if you use it yourself.
How they’ve been used and what state they come back in, with real hours.
There’s a record that the service was flagged and of when it was done.
Voltage spikes and drops that damage electronics and that, with no record, can’t be proved.
By machine, by site or by date. Compare machines and see how each reading changes over time.
A report of what has happened to a machine, ready to review or export.
The machine stops when you decide, not when it breaks.
Services by real hours or by date, breakdowns and parts. It connects to your maintenance software.
Fuel, repairs and hours cross-checked: you know which is profitable and what to charge. Try it with the cost-per-hour calculator.
The operator adds hours and incidents from a phone, also with no coverage.
If the machine already sends data through the manufacturer’s telematics, we bring it into your system and you stop checking one portal per brand. We explain when the manufacturer’s is enough and when it isn’t.
If it’s old, another brand or works where nothing reaches, we design, assemble and test the gauges and control unit. With no coverage the data stays stored on the machine: it’s sent when the network returns or downloaded in person.
It’s a parallel system fitted to the machine. The machine keeps working exactly the same: nothing of its own is changed.
It only reads signals. It doesn’t change the machine’s programming or how it works.
It doesn’t allow the machine to be operated or acted upon.
A project can be planned where the gauge is sealed and has the certifications required for the conditions of the mine or site.
It can be hidden, so that only certain staff can find, open or handle it.
It adapts to the operators, what they need and how they have to use it.
All of this depends heavily on the machine, the model and the installation. That’s why each case is studied before anything is fitted.
When the data is sent or downloaded, it goes straight into the program. It’s not just a database: it’s a complete program that analyses everything.
It reviews all the data from each machine: what happened, when and for how long.
Hours, fuel, breakdowns, machines and sites against each other, to see what one reading alone doesn’t show.
Charts, comparisons and summaries by machine, by site or by date.
Reports and data can be exported to use wherever you want.
The data is yours and only the people you authorise get in.
Where we have most experience: several brands, demanding environments and no coverage. We cover it in machinery in tunnels and mines.
Hours per contract, condition on delivery and return, and the cost of each machine on each site.
Production machinery, compressors, generators or pumps. We adapt it to what you have.
No. We don’t do remote operation. We monitor: you see its status, location, hours and fuel in real time and get alerts. The machine is operated by its operator.
Yes. We integrate manufacturers’ telematics where it exists and, on machines that don’t provide data, we fit the necessary hardware. It all ends up in one system.
It’s designed in: the control unit stores the data and sends it when there’s a connection. It can also be extracted on site.
No. It’s a complete program. The data goes straight in and the program analyses it, cross-references it, generates reports and lets you export them.
Because the way you work isn’t standard. A generic package makes you adapt to it; a custom one adapts to you, your machines and what you need to see.
It depends on the number of machines, whether hardware is needed and what has to be integrated. We start at €4,000 and give you a fixed price after the diagnosis.
Yes. By machine and by variable, with the manufacturer’s limits or yours. They tell you what happened, when and who to notify.
No. It only reads the signals. It writes nothing and doesn’t allow remote operation.
Yes. We have most experience in civil works, tunnelling and mining, but it adapts to factories and other equipment.
You do. Code, data and documentation. If one day you want to continue with another team, you can.
With that, in a 15 to 30 minute call we’ll see what can be measured and where to start.
Tell us about your fleet↗Then a diagnosis and a fixed price. From €4,000, VAT included. Code, data and documentation are yours. No lock-in.