Nwave’s console provides the possibility of device management using a hierarchical structure. It consists of a few objects, each of them represent a single level in the hierarchy.
Resource group
The resource group is the highest level of the hierarchy. It is often used as a means for regional aggregation. For example, if all devices in a project are placed in the single city, it makes sense to create a resource group with the name of the city and use this resource group for registering all of the devices for that project. Also, resource groups can be used for registering Nwave’s base stations and granting user permissions.
Related pages:
Batch
Batch is the 2nd level of the hierarchy. Batches are very useful as means of typical aggregation (grouping by type of location). For example, if one project contains parking sensors on-street parking bays and on multilevel car parking, it makes sense to split them on batches “On-Street”, “Multilevel parking 1”, “Multilevel parking 2”, “parking lot near WallMart” and so on.
The most important feature of batches is the possibility of setting up data routing. Nwave is able to push data to client’s services using HTTP and RabbitMQ protocols. For setting up sending data using one of these ways you need to create a route specified to batch.
Related pages:
Creating RabbitMQ route
Group
The group is the 3rd level of the hierarchy. Groups are means of adjacency aggregation(adjoining spots or very close proximity). For example, if there is a need to analyse parking occupancy data of multilevel car parking by levels, you can register a group for each level and keep devices in them. Also, Nwave use groups for algorithms of calculation of realtime availability of parking bays. Groups also can be used for setting up HTTP and RabbitMQ routes.
Related pages:
Creating RabbitMQ route
Place
The place is the lowest hierarchy level. Place represents a physical point in the world. Places have a lot of properties. The place is used to keep information about device’s location. It preserves location information whether device is placed there or not. Users can choose the most successful locations for device placing on the map, and then go there and place their devices. If there is a need to change a device (upgrade, for example), the place will keep it’s IDs and client’s services will recognise it like before, irrespective of the real device ID.
Related pages:
Creating place
Device binding
Device
The device is the object which represents a real device in Nwave’s console. It is used to keep information about device ID, warranty, device firmware and device monitoring. Devices have to be bound to places for device messages to be processed. If Nwave cloud receives data from a free(unbound) device, the data is ignored.
Related pages:
Binding device
Device monitoring