Asset Setup

It allows the user to create an asset hierarchy structure and configure the individual asset by configuring sensors and KPIs at the asset and component level.
Recommendations to create an Asset Hierarchy
The following image provides the basic idea of creating assets at different hierarchies:
Asset Hierarchy
NOTE:
This above image is the intended flexibility to be provided in hierarchy creation.
Key points around the Asset Hierarchy figure:
  • From the Enterprise level, the user can create a Product, Region, or Site. Note that defining the structure from Enterprise to Asset, once defined, the user needs to repeat for the rest of the hierarchy. Additional flexibility is planned for future releases. For example
    • If the user decides to use Enterprise > Site1 > Asset1, then every other asset needs to follow the same structure (Enterprise > Site1 > Asset2 or Enterprise > Site2 > Asset3) would work without issue. If the user follows other structures (Enterprise > Region > Site3 > Asset4), it does not work.
  • Under Product, the user can define Region (If not defined before) or Site.
  • Under Region, the user can define Product (If not defined before) or Site.
  • Under Site, the user can define Area or Asset.
  • Under Area, the user can define Sub-Area or Asset.
  • Under Asset, the user can define Component.
NOTE:
  1. Users are restricted to perform the following combination in the hierarchy list:
    • Enterprise > Product > Region > Product
    • Enterprise > Region > Product > Region
    • Enterprise > Asset
    • Enterprise > Area
  2. If the user defined the structure as Enterprise > Product > Region, then the user cannot define the structure as Enterprise > Region or Enterprise > Product > Site. Users can only build out the structure as Enterprise > Product > Region > Site.
  3. Under Site, the user can define any one of the following structures:
    • Site1 > Area > Asset
    • Site2 > Asset
    • Site3 > Area > Sub-Area > Asset
NOTE:
To edit a node at Asset Setup, the user needs to update the configuration status from Active to non-active status. For example, if the user changes the status from Active to Draft, then error toast message is displayed as “
Weightage must be set to 0 before changing the configuration status from Active to other
.” The user needs to change the weightage to zero to change the status of the node.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.