1. What is Location based calculation using KPI Datapoint?
Location can be used as a high level container which can have a KPI datapoint that provides an overall metrics for all the asset datapoints monitored under that location.
Consider there are 5 DGs in a location, the user wants to know the overall energy generated by all the DGs under that location. To achieve this, you can create a KPI datapoint for the location and do the required calculation.
2. What is the limit of levels in the Location allowed?
Though the parent can have as many children as required (based on license). The parent - child relationships are limited to 10 levels.
3. When to model as a location, and when as an asset?
For better understanding, let us consider a datacenter location at Chennai, in which you want to monitor temperature, humidity, and O2 readings.
In IoT setups, a Data Center can be added either as a location or as an asset, depending on the requirements.
As a Location: If the Data Center contains multiple devices and assets associated with it, and acts as a container, it is recommended to add it as a Location. Here you have the benefit of viewing the DC in the hierarchy with Chennai as the parent node.
The devices can be added as a lookup fields using custom field option and so can be added as the hierarchy because it has Located At and Parent Location.
As an Asset: If the Data Center does not contain any other devices and assets, and it has sensors attached for data collection, it can be added as an asset. You can directly monitor the parameters temperature, humidity, and O2, by creating it as datapoints of the sensors at DC.
If you want to monitor other assets along with the DC, you can have it as a child asset of the DC.
Choosing between the two depends on whether you want to focus on the Data Center's role in the physical layout (location) or its operational and functional contributions to the IoT system (asset).
The devices can be added as a lookup fields using custom field option and so can be added as the hierarchy because it has Located At and Parent Location.
Note: Refer to the Understanding Assets document for more details.4. When must you avoid creating a location as a managed entity?
When there are too many managed entities to be associated with a location then it is not advisable to add the location as a managed entity.
5. Why is the status propagated to a certain level in the hierarchy in some cases and not updated to the parent location?
The status propagation feature must be enabled in the parent to be updated with the status of the child. For example, consider a scenario where you want to propagate status to the city level Chennai and not up to the root level India; you need to select Chennai and select Disable Status Propagation in Actions.
To enable status propagation,
Click on the name of the node up to which you want to enable Status Propagation.

Click on Actions > Enable Status Propagation in the resultant screen.
