Asset Tree¶
Asset tree is a key function of the Asset Management service of the EnOS. Asset tree is mainly for asset owners who understand the enterprise asset management business and can quickly create the asset topology to manage assets.
The asset tree management is decoupled from device provisioning, which means that the device provisioning operation is independent from the asset tree. Therefore, you can complete device provisioning first and then bind the connected devices to the asset tree. You can also create an asset tree and then connect the devices. Generally, a connected device is bound to a node of the asset tree.
Concepts¶
Asset Tree
An asset tree is the hierarchical organization of assets. An asset can be added to multiple asset trees so that the assets can be managed from different dimensions for different business scenarios. An asset can only appear once in an asset tree. Scenarios for multiple asset trees include:
- Management based on geographical location: country, state, city, district.
- Management based on domain: wind power, photovoltaic, energy storage.
- Management based on device type: fan, inverter, combiner box. For the scenarios above, you can create three asset trees for the same group of assets.
Node¶
A location on an asset tree to which you can bind an asset. Assets are bound on the nodes of the asset tree to form the topological relationship.
Asset¶
The entities that can be directly bound on the asset tree and can be managed. They are the asset tree nodes. When a user creates an asset tree, the node generated by EnOS is the root node. You can continue to bind sub-nodes under the root node, and bind nodes under each sub-node.
Classification¶
Assets can be divided into device assets and logical assets.
- Device asset: A physical device, such as a photovoltaic inverter, a wind turbine, etc.
- Logical asset: Can be a place to contain devices or a collection of devices, such as a site, an area, a floor, etc.
Limitations and Impacts¶
Each asset on an asset tree has a unique identifier. An asset can be bound to different asset tree nodes but must be unique on one asset tree. The relationship between asset trees, assets, and devices is shown in the following figure.
If a user deletes a device or logical asset in Device Management, the corresponding node on the asset tree will become an invalid node. You cannot bind assets under an invalid node.
You can bind assets to sub-nodes under every valid node on an asset tree. The maximum layers that an asset tree can have is 7, including the root node layer. On each layer, a maximum of 10,000 peer nodes are allowed.