What goes on your network.
Two boxes. One outbound connection. Nothing to open.
Three places. One connection out.
A reading starts on the machine, passes through the receiver, and ends on the platform. Only the last hop leaves your site, and the receiver is the one that opens it.
- On the machineSensors
Battery-powered and mounted on the outside of the bearing housing. They talk to the receiver over licence-free sub-GHz radio, 902–928 MHz, so the sensor hop needs no plant Wi-Fi, new cable, or access points.
- On the wallReceiver
Mains powered through a supplied adapter. It collects every sensor on the floor and opens one outbound connection, MQTT with TLS, over Wi-Fi, Ethernet or LTE. A typical plant uses one to three, placed at scoping.
- Off the floorPlatform
The diagnosis is done here, not on the receiver. The platform runs in the cloud, or inside your own network on the Enterprise plan.
The questions IT will ask.
Short answers, so the network review can start before the first call. The security page lists what is live today and what is still to come.
- What do we open on the firewall?
- Nothing inbound. The receiver opens one outbound connection.
- Which protocols?
- MQTT with TLS from the receiver. The product API the platform uses is HTTPS.
- Do the sensors join our Wi-Fi?
- Not the sub-GHz sensors. They reach the receiver by radio and do not join the plant network. The Wi-Fi sensor models are separate parts.
- Does it touch the PLC or historian?
- No. Neither needs a connection.
- What if the internet drops?
- On the Gateway, the dashboard and local UI run on the device, so the wall display stays up.
- Can it stay inside our perimeter?
- Yes. An on-premise deployment is available on the Enterprise plan.