System VS Locational Data Hierarchies
The structure of our asset data affects all levels of an organization, from operators to planning and scheduling to the C-suite. Setting up an asset hierarchy structure that enables insightful data analytics is key to effective decision making. So what exactly is an asset hierarchy and why are they rarely set up in the best way possible.
An asset hierarchy is a logical organization of physical structures, equipment, and spare parts, and how they work together. Most organizations have some level of an informal data hierarchy, though the best way to streamline decision making is to create a structured data hierarchy.
There is no one correct asset hierarchy structure; it really depends on the data needs of the organization itself. However, there are two common foundational hierarchies: Locational and System.
Asset-Locational Data Hierarchy: Spatial relationships to organize assets based on their physical location. Locations are organized hierarchically, and assets are associated into specific locations. This structure allows for spatial visualization and asset management based on physical location.
Asset-System Data Hierarchy: Parent-Child relationships to organize assets based on their function and relationships to other assets within a system. Systems are organized by function as systems stream into one another and assets are connected into one or more systems. This structure allows for operational flow visualization and dependencies within and between different systems.
In comparing the two hierarchies, we see distinct benefits. Below are several examples that highlight the benefits:
Asset-System
Provides insights about system performance by aggregating connected asset performance data.
Allows users to evaluate operational efficiency by searching for assets on upstream or downstream systems.
Asset-Location
Allows prioritization of specific areas on campus based on assigned criticality of assets within a location.
Helps to reduce time waste from searching for assets because of the clearly assigned location.
Best utilized when asset locations correspond to business function. For instance, Building B is responsible for packaging, so assets in Building B will support packaging.
There are benefits to each type of data hierarchy . When choosing the type of asset hierarchy system, ensure the choice is focused on your organization’s information needs.
While both structures provide valuable insights that will aid maintenance, operations, and digital transformation, these structures are not mutually exclusive. However, it’s not commonplace to have a combined system mainly due to different CMMS requirements. That said, a combined approach can be possible with the correct system and tools. By combining the locational and system asset data structures, organizations will reap the greatest possible benefits from both structures.
Comprehensive asset management: Both hierarchies provide valuable insights into different aspects of assets. Combining them offers a holistic view of each asset, incorporating a full picture of the assets’ purpose for existence.
Improved data integration: Identifying patterns and correlations between system functionality and physical location can improve asset management strategies for specific systems or locations.
Enhanced visualization: Combining system and locational data facilitates the creation of interactive models, maps and dashboards. These visualizations are powerful tools for visualizing asset performance, identifying trends, and managing assets more effectively.
Understanding both system and locational data hierarchies is crucial for effective asset management. By discerning the unique differences and advantages of each approach, organizations can craft a streamlined, yet comprehensive data strategy tailored to maximize information accessibility based on their specific needs.