Intelligent Part Numbering System Metadata Framework

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Prior art information systems are inefficient in storing and retrieving part numbers due to their requirement for a unique character string indexed in a database, leading to limited storage of part number instances and lengthy data entry processes for new part series, making it difficult for engineers or purchasers to find and order specialty parts.

Innovation Solution

A database design and associated tools that store part number attributes as metadata, allowing for rapid storage and retrieval of attributes and co-dependent attributes, enabling the generation of part numbers based on user inputs without a hierarchical indexed list of part numbers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If prior art information systems store part numbers as indexed unique character strings in a database, then part numbers can be uniquely identified and retrieved, but the storage capacity is limited and data entry for new part series is time-consuming

Engineering Contradiction:
Improvenumber of part number instances storedVSAvoidtime for data entry of new part series
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent segments part numbers into hierarchical components (family code, series code, attribute codes) stored as separate metadata fields in the database. Instead of storing complete part numbers as single indexed strings, the system breaks them down into constituent elements that can be independently managed and recombined, enabling rapid storage and retrieval without full indexing of every possible part number combination.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary action by pre-defining part number templates, attribute codes, and family/series structures in the metadata before actual part numbers need to be generated. This preliminary setup allows the system to automatically generate valid part numbers on-demand without requiring manual data entry or pre-population of every possible part number instance into the database.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If online parts distributors include only top selling items (5%-10% of possible part number instances) in their database, then storage requirements are reduced, but specialty parts cannot be found by engineers or purchasers

Engineering Contradiction:
Improvenumber of part number instances in databaseVSAvoidability to find and order specialty parts
Core Design Contradiction:
Quantity of substanceVSEase of operation

Solution Approach 1:

The patent creates a universal metadata framework that can represent any part number from any family or series without requiring pre-storation in the database. The system functions both as a storage mechanism for defined attributes and as a generation engine for on-demand part numbers, enabling users to find and order any specialty part by selecting from attribute options rather than searching through pre-loaded part number lists.

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

Solution Approach 2:

The metadata structure acts as an intermediary between the user's part requirements and the actual part number generation. Instead of directly storing or searching complete part numbers, the system uses metadata attributes as an intermediate layer that translates user selections into valid part numbers, enabling comprehensive part coverage without database bloat.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If a new part series is offered for sale through a distributor's existing online information system, then several weeks of coding and data entry are required, representing significant cost to the distributor

Engineering Contradiction:
Improveability to offer new part seriesVSAvoidtime for coding and data entry
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by establishing a reusable metadata template structure that defines families, series, and attribute hierarchies once. When a new part series needs to be added, distributors can simply configure new entries within the existing metadata framework rather than performing extensive coding and data entry, reducing setup time from several weeks to a fraction of that time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables rapid adaptation to new part series through parameter changes in the metadata configuration. By modifying attributes such as family codes, series codes, and attribute definitions in the metadata structure, the system can accommodate new part series without requiring structural changes or extensive programming, allowing distributors to quickly adapt to new product lines.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11755992B2Intelligent part numbering system and method
Publication Date: 2023.09.12 PONCHER KENNETH IAN
  • US11755992B2 patent drawing
  • US11755992B2 patent drawing
  • US11755992B2 patent drawing

AI summary

A database design and associated support tools for storing Intelligent Part Numbering System (IPNS) metadata for the purpose of interfacing with information systems in a more efficient way, thereby reducing maintenance requirement and improving information technology (IT) searching options. Embodiments of the present invention are directed to a method, system, and computer-readable medium for storing one or more attributes of a part number family in a database as metadata. The method includes associating a part number code with each attribute in the database; receiving one or more user inputs, each user input indicating a selection of one of the attributes; determining the part number codes associated with each of the selected attributes; and generating a part number based on the part number codes associated with each of the selected attributes.