Hardware-Software-Cloud AaS Conversion via Real-Time Data Mesh

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional ERP systems face inefficiencies in data integration, data fragmentation, and lack of real-time visibility, leading to operational delays, errors, and uninformed decision-making in complex distribution and supply chain environments, with inadequate security and compliance features.

Innovation Solution

An automated 'As a Service' (AaS) model integrating hardware, software, and cloud services into a subscription-based model, utilizing a Real-Time Data Mesh (RTDM) and Single Pane of Glass (SPoG) UI, with advanced algorithms for dynamic pricing and subscription management, ensuring data security and compliance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If traditional ERP systems are used for managing distribution and supply chain, then comprehensive data storage is achieved, but data fragmentation and lack of real-time visibility occur

Engineering Contradiction:
Improvedata storage capacityVSAvoidreal-time visibility
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The system segments data into structured categories (product data, customer data, order data, inventory data) and implements a multi-tenant architecture where each tenant can access only their relevant data segments. This segmentation enables comprehensive data storage while preventing information loss through organized data silos that maintain real-time accessibility for authorized users.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimensional layer above traditional ERP systems through the distribution management system, which adds real-time data capture and analytics capabilities. This dimensional addition transforms static stored data into dynamic real-time information without replacing the underlying comprehensive storage infrastructure.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Device complexity

If traditional ERP systems are used, then centralized data management is achieved, but data integration capabilities with external systems are insufficient

Engineering Contradiction:
Improvecentralized management structureVSAvoiddata integration capability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary layer in the form of a distribution management system that sits between traditional ERP systems and external systems. This intermediary handles data integration, transformation, and exchange, enabling centralized ERPs to communicate effectively with external partners, carriers, and marketplaces without compromising their core centralized management architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Manufacturing precision

If manual data transformation processes are used, then data standardization is achieved, but operational delays and errors increase

Engineering Contradiction:
Improvedata standardizationVSAvoidoperational efficiency
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The patent replaces manual mechanical data transformation processes with automated electronic data interchange (EDI) systems, API integrations, and automated validation rules. This substitution maintains data standardization through systematic transformation while eliminating human error and accelerating processing speeds, thereby improving operational efficiency.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Adaptability or versatility

If traditional subscription processes are used, then service selection is achieved, but efficiency and flexibility in subscription management are reduced

Engineering Contradiction:
Improveservice selection capabilityVSAvoidsubscription processing efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements self-service capabilities that allow customers to autonomously select services, configure subscription parameters, and manage their own subscriptions through intuitive interfaces. This self-service approach maintains service selection flexibility while dramatically improving processing efficiency by eliminating manual intervention for routine subscription operations.

Inventive Principle:
Principle #25Self-service

5Reliability

If traditional ERP security features are used, then basic data protection is achieved, but robust security and compliance features are inadequate

Engineering Contradiction:
Improvebasic data protectionVSAvoidsecurity and compliance adaptability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic security features that automatically adapt to changing compliance requirements and threat landscapes. Role-based access control, data encryption, and audit logging mechanisms dynamically adjust based on user roles, data sensitivity, and regulatory requirements, maintaining basic protection while providing robust adaptability to evolving security and compliance demands.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP4621691A1Systems and methods for converting hardware-software-cloud to as-a-service (AAS)
Publication Date: 2025.09.24 INGRAM MICRO INC
  • EP4621691A1 patent drawingFigure 1
  • EP4621691A1 patent drawingFigure 2
  • EP4621691A1 patent drawingFigure 3

AI summary

Computerized systems and methods are described for converting traditional technology products into an "As a Service" (AaS) model, facilitating the transition from capital expenses (CapEx) to operational expenses (OpEx). Methods include receiving user inputs for technology product selections and accessing a Real-Time Data Mesh (RTDM) to retrieve data. An Advanced Analytics and Machine Learning (AAML) Module analyzes user inputs and market data, optimizing the conversion into subscription-based services. Process results are displayed to the user through a Single Pane of Glass User Interface (SPoG UI). An AaS Conversion Module performs transition of products into customizable subscription packages. This method emphasizes dynamic pricing based on usage, flexibility, and/or scalability of services. Methods are provided for real-time reporting, subscription management, and vendor system integration, enabling a comprehensive AaS conversion process suitable for modern technology products and services.