Organize a Fleet the Way Your Operation Is
A few dozen devices can live in a list. A few hundred cannot, and by then the names people invented in the first month have stopped meaning anything. ioX-Pulse gives equipment two kinds of structure: sites, for where something physically is, and networks, for what belongs together.
They are not alternatives. A site is a place, arranged as a hierarchy you build to match the actual buildings. A network is a group, which may be a floor's worth of equipment or a logical cluster that has nothing to do with geography. Most operations end up using both, and the platform keeps them consistent with each other rather than leaving you to.
- A location hierarchy of campus, building and floor, built to match your estate rather than ours
- Groups you define, so a filter gets you a floor's equipment or a customer's cluster in one click
- Every reading records the site it was taken at, so history stays correct when equipment moves
- Equipment in a group takes its location from the group, so the two structures cannot drift apart
- Somebody can be restricted to a site and see their own location and below, never above it
- Attach equipment in bulk from a device list rather than one record at a time
Trusted by teams monitoring critical infrastructure
A group, not a radio network
Networks: What Belongs Together
A network here is a named group of your devices and gateways, not the LoRaWAN radio network itself. It is the label you put on equipment that belongs together.
- Filter a device or gateway list down to one group in a click, which is how most people use them day to day
- Each group counts its own devices and gateways, so it doubles as a rough roll-up for reporting
- A piece of equipment belongs to one group at a time, and adding it to another moves it rather than duplicating it
A group can also belong to a site, and when it does, everything inside it takes that site automatically. That is what stops the two structures contradicting each other.
The part that matters later
Readings Remember Where They Were Taken
Equipment moves. A sensor is pulled from one building and redeployed in another, a spare goes out to cover a failure, a whole rollout is reorganized. On most platforms the readings are attributed to wherever the device is now, so moving it quietly rewrites its history.
In ioX-Pulse each reading records the site the device was at when it arrived. Move the device and last year's data still says where it was measured.
The site appears alongside the reading itself, so anybody looking at a device's history can see the move rather than having to remember it.
Nobody asks about this during an evaluation. It is the sort of thing you discover eighteen months later, when a report covering two locations turns out to have been counting them as one.
The older readings keep the site they were measured at.
One site, not the whole fleet
Limiting Someone to Their Own Site
A site manager usually needs their own location and nothing else. Restrict a member to a site and that is what they get: their own site and anything beneath it in the hierarchy, never anything above it.
It follows through the rest of the product rather than stopping at a device list. A dashboard linked to a site is visible to the people at that site and at any site above it, and somebody restricted to a floor does not see a dashboard built for the campus.
The restriction narrows what a person can reach; it never widens it.
Their own site and everything beneath it. Never the level above.
