Asset Event Cost Visualization for Condition Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing condition monitoring systems face challenges in prioritizing events due to limited numerical scales for event severity and asset criticality, leading to subjective operator judgments, especially as the number of events and monitored assets increases, making it difficult to efficiently manage and address asset performance deviations.

Innovation Solution

The implementation of a system that correlates events with costs, using reliability models like FMEA, to provide a graphical user interface displaying event data and corresponding costs, allowing operators to prioritize based on the magnitude of costs rather than numerical scales, thereby reducing subjectivity and improving decision-making efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If numerical scales (1-4) are used for event severity and asset criticality categorization, then the system structure remains simple, but operator subjectivity increases and prioritization accuracy deteriorates

Engineering Contradiction:
Improvesystem structureVSAvoidprioritization accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The patent transforms the prioritization parameter from abstract numerical scales (1-4) to concrete cost values (e.g., production loss amounts, repair costs). This parameter change provides a common quantitative basis for comparing events across different assets and severity levels, objectively resolving prioritization decisions while maintaining system simplicity.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If traditional numerical scales are used for event prioritization, then the system remains easy to operate, but decision-making speed decreases as the number of events and assets increases

Engineering Contradiction:
Improvesystem usabilityVSAvoiddecision-making speed
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent creates a cost representation model that copies real-world economic impacts (production loss, repair costs) into the monitoring system. This cost model serves as a simplified proxy for complex event assessments, allowing operators to quickly prioritize events by comparing cost values rather than analyzing multiple numerical scales across numerous assets.

Inventive Principle:
Principle #26Copying

3Loss of energy

If subjective operator judgment is relied upon for event prioritization, then the system requires minimal computational resources, but decision accuracy and consistency deteriorate

Engineering Contradiction:
Improvecomputational resourcesVSAvoiddecision consistency
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The patent performs preliminary calculation of cost values for each event based on pre-defined cost models and event parameters. By pre-computing these cost representations, the system eliminates the need for complex real-time computational analysis during operator decision-making, while ensuring consistent and objective prioritization across all events.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12093862B2Event cost visualization for asset condition monitoring
Publication Date: 2024.09.17 BAKER HUGHES CO
  • US12093862B2 patent drawing
  • US12093862B2 patent drawing
  • US12093862B2 patent drawing

AI summary

An asset management system is provided and includes a memory and an event analyzer. The memory maintains event data and at least one cost. The event data characterizes events experienced by assets distributed among sites of a fleet. The event data include an asset location within an asset hierarchy of the fleet and event parameters corresponding to the event. Costs can be correlated to respective events. The analyzer generates a GUI displaying a first window hierarchically listing of assets organized by their hierarchical position within the fleet. The analyzer receives, via the GUI, a user selection of a hierarchical level within the hierarchical list, and identifies events associated with the selected hierarchical level. The analyzer updates the GUI to display a second window in response to receipt of the user selection. The second window lists the identified events, with corresponding event data costs.