Asset Event Visualization for Unique and Repeat Fault Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing condition monitoring systems overwhelm operators with unnecessary event logs due to fluctuating operating parameters and lack of integrated data visualization, making it difficult to identify unique events causing asset performance deviations, especially in time-sensitive situations.
Innovation Solution
An asset management system with a historian and event analyzer that generates a graphical user interface (GUI) for hierarchical asset listing, classifying events as unique or repeat, and displaying detailed data and recommendations, allowing for efficient event analysis across multiple sites within a fleet.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If condition monitoring systems log all events when operating parameters fluctuate about a set point, then complete event records are maintained, but event logs become filled with unnecessary events that overwhelm operators
Solution Approach 1:
The system changes the parameter of event logging from recording all parameter fluctuations to recording only significant events based on classification criteria. Events are classified as unique or repeat based on their characteristics, and only unique events are logged in the main event log, while repeat events are tracked separately. This parameter change filters out noise while preserving important information.
Solution Approach 2:
The system applies different quality standards to different types of events. Unique events receive full logging and detailed analysis, while repeat events are handled with simplified tracking and aggregation. This local quality approach ensures that operator attention is focused on novel, potentially critical events rather than routine fluctuations.
2Device complexity
If condition monitoring systems present events as a simple list, then event data is easy to store, but it becomes difficult to find unique events responsible for triggering alerts
Solution Approach 1:
The event list is segmented into distinct categories: unique events, repeat events, and aggregated events. Each segment is presented with different levels of detail and organization. Unique events are highlighted separately from repeat events, and repeat events can be aggregated to show patterns. This segmentation makes it easy to identify which events are truly novel and require immediate attention.
Solution Approach 2:
The system adds dimensional organization to the event list by incorporating temporal dimension (showing event frequency and patterns), categorical dimension (grouping by event type or source), and hierarchical dimension (organizing from general to specific). This multi-dimensional presentation transforms a flat list into an organized structure that reveals patterns and makes unique events easily identifiable.
3Device complexity
If condition monitoring platforms do not combine events with supporting data, then system architecture is simpler, but operators must navigate between different applications to compare event details
Solution Approach 1:
The system merges event data with supporting diagnostic information into a unified event record. Each event entry includes not only the basic event parameters but also associated supporting data such as trend information, contextual asset data, and diagnostic recommendations. This merging eliminates the need for operators to switch between applications while maintaining system architecture simplicity through integrated data structures.
Solution Approach 2:
The event data structure is designed to be universal, accommodating multiple types of information in a single integrated format. The same event record can contain basic event parameters, temporal patterns, supporting diagnostic data, and actionable recommendations. This multi-functional event structure serves multiple purposes simultaneously, reducing navigation time while keeping the system architecture unified rather than fragmented across multiple specialized applications.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
Systems and methods for asset management are provided. Event data characterizing events experienced by assets distributed among different sites of a fleet is maintained. The event data includes an asset location within an asset hierarchy of the fleet and an event parameter corresponding to the event. A graphical user interface (GUI) is generated that displays a first window including a hierarchical list of assets organized according to their position within the asset hierarchy. When the GUI receives a selection of a level within the hierarchical list, events associated with the selected level can be identified. Identified events can be classified based upon their event data as a unique event having a single occurrence or a repeat event having multiple occurrences. In response to receipt of the selection, the GUI is updated to display a second window listing single entries for respective unique events and single entries for respective repeat events.