|
|
Currently, in Info360 Plant, when creating a common analytic or workspace for the same type of asset (e.g., a pump or a set of pumps), it is necessary to manually create the analytic or workspace for each asset. This process is facilitated through the use of "Save As" and templates.
However, after creating multiple workspaces or analytics for each asset, if modifications are required across all assets, changes must be applied manually to each workspace or analytic, which can become burdensome.
To address this, Info360 Plant should offer the capability to create Classes. A class will allow the creation of multiple identical workspaces or analytics for the same type of asset. If an asset requires customization, its workspace or analytic can be declassified from the class. When modifications are applied to the class, all instances (workspaces or analytics) associated with that class will be uniformly updated.
For example:
- Our customer has defined two Key Performance Indicators (KPIs) to monitor energy performance within a hierarchical structure.
- The hierarchy spans from assets (e.g., pumps) to sites or stations (e.g., groups of pumps), culminating at the plant level for plant-wide monitoring.
- To simplify the creation of this monitoring structure for multiple assets (more than 60), a common Asset Analytic Class should be created to define all assets identically.
- Although the number of sites is significantly smaller (approximately four), a common workspace structure (Workspace Analytic Class) is also necessary to facilitate ease of monitoring and operational familiarization.
By implementing Classes in Info360 Plant, users will be able to efficiently manage and modify analytics and workspaces across similar assets, significantly reducing manual effort and enhancing operational consistency.
