Digital Thread Data Element Mapping for Physical Components

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for designing and manufacturing physical components fail to digitize information effectively, leading to inefficiencies and human errors due to the high percentage of non-digital and unstructured data, which hinders the improvement of the component lifecycle.

Innovation Solution

A system utilizing a computer processor and storage medium to access and manipulate data element instance objects, creating digital threads by connecting data elements across different functions and data vessels, allowing for efficient data flow, removal of unnecessary data, and addition of needed data elements, thereby improving the design, testing, and manufacturing processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If information is stored in non-digital and unstructured formats, then data storage flexibility is maintained, but data accessibility and transmission efficiency deteriorate

Engineering Contradiction:
Improvedata accessibilityVSAvoiddata structure complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments information into standardized data elements with defined schemas, allowing each element to be independently structured and managed. This segmentation enables systematic organization of previously unstructured data while maintaining flexibility through modular data element definitions that can be customized for different component types.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transforms data from unstructured formats into structured digital formats by changing the state of data representation. This parameter change from unstructured to structured format enables automated processing, efficient transmission, and improved accessibility while maintaining adaptability through configurable data element schemas.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If data transmission between lifecycle functions is increased, then component improvement is enhanced, but process complexity increases

Engineering Contradiction:
Improvecomponent improvement efficiencyVSAvoiddata transmission complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent creates a universal data element framework that serves multiple functions across different lifecycle stages. The same structured data element schema is used for design, manufacturing, testing, and maintenance functions, enabling seamless data transmission without requiring function-specific data formats. This universality reduces transmission complexity while improving productivity.

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

Solution Approach 2:

The patent introduces a data element mapping and analysis system that acts as an intermediary between different lifecycle functions. This intermediary automatically transforms and translates data between functions, reducing the complexity of direct point-to-point data transmission while enabling comprehensive information flow across all lifecycle stages.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If digital data connection is implemented, then data transmission speed is improved, but implementation complexity increases

Engineering Contradiction:
Improvedata transmission speedVSAvoiddigitization complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent performs preliminary structuring of data elements before transmission occurs. By pre-defining data schemas and structures during the design phase, the system eliminates the need for complex real-time data transformation during transmission. This preliminary action simplifies the digitization process while maintaining high transmission speeds.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates standardized digital copies of component information that can be replicated and transmitted across the lifecycle. These standardized data element copies maintain fidelity to the original information while enabling efficient digital transmission. The copying approach reduces implementation complexity by using consistent templates rather than customizing data structures for each transmission.

Inventive Principle:
Principle #26Copying

4Reliability

If human examination of lifecycle is used, then data accuracy is maintained, but time consumption increases

Engineering Contradiction:
Improvedata accuracyVSAvoidexamination time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements automated feedback mechanisms through data element validation rules and consistency checks that verify data accuracy without human intervention. The system automatically detects errors, validates data integrity, and provides feedback for corrections, maintaining high reliability while eliminating time-consuming manual examination. The feedback loop ensures data accuracy through systematic automated verification.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12131134B1Physical components using data element mapping and analysis
Publication Date: 2024.10.29 AUBURN UNIVERSITY
  • US12131134B1 patent drawing
  • US12131134B1 patent drawing
  • US12131134B1 patent drawing

AI summary

A system for improving a physical component may include a processor configured to (1) access a first data storage that may include a plurality of function data objects or a plurality of data vessel data objects that may include references to each other; (2) iterate over the plurality of data vessel data objects, and for each data vessel data object, generate one or more data element instance data objects; (3) select a subset of the plurality of data element instance data objects that include the same data element identifier; (4) order the subset of the data element instance data objects based their respective one or more references to one or more other data element instance data objects; and (5) store the ordered subset of the data element instance data objects in a second data storage as a digital thread.