Nwave console provides the possibility of device management using a hierarchical structure. It consists of a few objects, each of them represent a single level of hierachy.
Resource group
Batch
Group
Place
Device
Resource group
The resource group is the highest level of the hierarchy. Often it used for definition of project in a particular area. For example, if all devices in 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 devices of the project. Also, resource group is able to be used for registering Nwave base stations and granting user permissions.
Related pages:
Operations with resource group.
Batch
Batch is the 2nd level of hierachy. Batches are very useful if there is a need to split devices in a project onto a few parts. 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”, “Multilievel 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 clien’t 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 HTTP route
Creating RabbitMQ route
Group
The group is the 3rd level of the hierarchy. Groups are used to split projects onto small parts. For example, if there is a need to analyze 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 a group
Creating HTTP route
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 location of device. It keeps location information with no matter if 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 devices. If there is a need to change device (upgrade, for example), the place keeps it’s IDs and client’s services still recognize it like before, with no matter of real device ID.
Related pages:
Creating place
Device binding
Device
The device is the object which represents a real device in Nwave console. It used to keep information about device ID, warranty, device firmware and device monitoring. Devices have to be bound to places for processing data from them. If Nwave cloud receives data from free (unbound) device, the data is ignored.
Related pages:
Binding device
Device monitoring