Release 3.6

Asset Class

Cloud Server now supports an additional layer in the asset representation that allows group Asset Types into Asset Classes. This makes easier to filter assets that have different types but belong to the same class. As an example, for asset class we can have Pump and for type we can have Rotary Pump and Hydraulic Pump.

E.g.:

 Pump (Class)
 ├── Rotary (Type)
 │   ├── pump 1 (Asset)
 │   └── pump 2 (Asset)
 └── Hydraulic (Type)
     └── pump 3 (Asset)

Asset Model Hierarchy

The Asset Model Hierarchy brings a relationship between assets that is very common, which is the parent <-> child relationship between assets. With this feature, the Platform supports configuring each asset parent with no limitation on how many levels, efficiently representing the most complex systems. As an example, a centrifugal pump is usually composed by Volute Casing, Closed Impellers, Wear Ring, Packaging, Shaft, Bearing House, Bearing Cover and Coupling. In Cloud Server now, it's possible to represent this in a tree view structure without limiting how many levels. Also, we provide a comprehensive management tool where the user can manage the tree structure by simply drag n drop the assets in the tree.

E.g.:

Pump
├── Volute Casing
├── Closed Impellers
├── Wear Ring
├── Packaging
├── Shaft
├── Bearing House
├── Bearing Cover
│   └── Bearing
├── Coupling

Kelvin Manager Dashboard

Kelvin Manager now has a dashboard section where the user can see how many nodes are down, how many assets are not receiving data, and visualize the system's entire tree view. In the tree view, the user can see the details of the asset like the last read values, properties, locations and the time-series data in the chart.