You build a machine, it leaves the factory, and from then on you learn about it from complaints. A controller fitted on the line reports what the machine is doing from wherever it ends up, to you, to your dealer and to the customer, each seeing only their own units.
The controller and the cloud are the same in every case. What changes is which signals are worth reading on that machine.
Hardware you fit, a cloud you put your name on, and nothing to build in between.
Four ports that each take any supported sensor protocol, set from the dashboard, so one part number covers every model in your range. It reads your own controller over Modbus as well.
Accounts for you, your dealers and their customers, with permissions that stop at each boundary. This is the part that takes longest to build and it exists today.
The dashboard is served on your domain with your name, logo and colours, and the apps are listed under your company in the stores. What the customer sees is your connected product.
One machine reporting is a gadget. Every machine you have shipped reporting to the same place is a service business.
Each machine reports to the same cloud. Your service desk sees which units are running, which are in alarm and which have gone quiet, before the customer calls.
Accounts nest: you sit above your dealers, and each dealer above its customers. A parent account cannot grant more than it holds, and a unit can be shared with a service company without handing over a login.
Readings and events are stored with their time and export to Excel, for a warranty claim, a service report or a disagreement about what happened and when.
A REST API with scoped tokens covers what the dashboard covers, so fleet data can feed your service system, your ERP or your customer portal directly.
The controller takes 6 to 32 V DC, so it runs from a 12 or 24 V supply already on the machine. Its internal rechargeable battery keeps it reporting after the machine loses power, which is when the reading matters most.
It connects over 4G-LTE from wherever the machine is installed. There are no Wi-Fi credentials to collect and no IT department to convince at each customer.
If the machine already has a controller with an RS485 Modbus RTU port, give us its register map and we add it as a supported device. Its values and alarms then arrive alongside the sensor readings.
The web dashboard is served on your domain with your name, logo and colours, and the iOS and Android apps are published under your own developer accounts. Your customers log in to your product.
Readings are held on the device while the network is down and sent in order when it returns, so the record has no gap where the incident was.
It does not have to be. Fitting a standard controller to your machine and giving your customers access under your name needs no custom hardware. Where the product does need its own enclosure, firmware or board, the custom hardware and ODM pages describe that route.
Yes. Over fifty sensor types are supported today and more are added on request. If a sensor speaks one of the supported protocols, it is a candidate.
Either. Every controller comes with OmniCloud included, and the REST API does what the dashboard does if you would rather build your own front end on top of it.
The supply voltage available on the machine, the signals you want reported, the register map if the machine has a Modbus controller, and how your dealers and customers should be separated. A first batch on machines already in the field is the usual way to begin.
Over the air, by cellular. Where there is no network at all, the unit raises its own Wi-Fi access point and takes the update from a phone or laptop beside it.
What it is, what you want it to report, and who needs to see which units. We come back with how the controller wires in and how the accounts would be laid out.
Talk to us →