ERP Equipment Taxonomy for Failure Reporting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional ERP systems for managing enterprise equipment assets face challenges in data architecture and methodology, leading to ineffective equipment failure reporting and maintenance, which hinders optimal operational performance and increases safety and environmental risks.

Innovation Solution

An ERP/EAM system employing an equipment taxonomy that maps physical objects to functional locations within a hierarchical structure, enabling comprehensive and relational data collection and analysis for enterprise-wide equipment failure reporting and preventive maintenance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional ERP systems are used for enterprise asset management, then basic equipment tracking is possible, but data architecture complexity and ineffective failure reporting hinder operational performance

Engineering Contradiction:
Improveequipment reliability data qualityVSAvoiddata architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments equipment data into hierarchical categories (equipment, facilities, functional locations) with standardized attributes. This segmentation organizes complex data into manageable, structured units that can be efficiently queried and analyzed, resolving the contradiction between data quality and architectural complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter structure of equipment data by implementing standardized data fields and relational schemas. This transformation converts unstructured or semi-structured data into standardized parameters that can be consistently tracked and analyzed across the enterprise, improving reliability without proportionally increasing complexity.

Inventive Principle:
Principle #35Parameter changes

2Loss of information

If comprehensive equipment data collection is implemented, then better failure analysis is possible, but data merging and assessment become inefficient data mining exercises

Engineering Contradiction:
Improveequipment failure information completenessVSAvoiddata analysis time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent implements feedback mechanisms where equipment data is continuously collected, analyzed, and used to improve maintenance decisions. The system provides feedback loops that connect failure data collection with preventive maintenance scheduling, enabling efficient utilization of comprehensive data without manual data mining.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary data layer with standardized schemas and relational structures that mediates between raw equipment data and analysis processes. This intermediary layer organizes comprehensive data into accessible formats, eliminating the need for time-consuming manual data mining while preserving information completeness.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If ERP systems integrate multiple corporate data repositories, then enterprise-wide equipment view is achieved, but effectiveness diminishes due to data architecture issues

Engineering Contradiction:
Improveenterprise-wide data integration capabilityVSAvoidsystem usability
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent creates a universal equipment data schema that can accommodate multiple data sources and types within a single standardized framework. This universal structure enables the system to integrate diverse corporate data repositories while maintaining ease of operation through consistent data access methods across all integrated sources.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Quantity of substance

If traditional equipment management approaches are used, then actual repair costs are tracked, but production loss and safety consequences are not accounted for

Engineering Contradiction:
Improvefailure consequence measurement completenessVSAvoidoperational performance
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent implements preliminary action by using collected equipment data to predict potential failures and schedule preventive maintenance before actual failures occur. This proactive approach accounts for all failure consequences including production loss and safety risks, while maintaining productivity by preventing disruptions before they happen.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11157519B2System and method for enterprise asset management and failure reporting
Publication Date: 2021.10.26 CILIBERTI III VITO ANTHONY
  • US11157519B2 patent drawing
  • US11157519B2 patent drawing
  • US11157519B2 patent drawing

AI summary

An information (ERP/EAM) system and equipment taxonomy for representing and managing of equipment, equipment subunits and component parts thereof across an enterprise that maps materialized physical objects to functional physical objects within a hierarchy of functional locations within the enterprise for all enterprise assets in accordance with applicable industry standards. The ERP/EAM system and the equipment taxonomy also provide multi-leveled failure reporting.