Anticipatory Data Caching for Supply Chain Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current supply chain management systems face challenges in real-time monitoring and data access, particularly in managing shortages, which can lead to disruptions and inefficiencies due to outdated information and the complexity of handling large volumes of data across multiple databases.

Innovation Solution

A method and system for real-time data access from one or more databases, involving the presentation of a first record set and the fetching of a second record set before a data request, allowing for immediate display of updated information, including parts, locations, and suppliers, to facilitate efficient shortage monitoring and management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If data is fetched from databases in real-time to ensure up-to-date information, then monitoring accuracy and response time improve, but system complexity and data processing overhead increase

Engineering Contradiction:
Improvemonitoring accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by fetching and caching data records before they are actually requested. When a user requests data, the system checks if the data has already been fetched and cached, returning it immediately if available. This anticipatory approach ensures up-to-date information is available without adding complexity to the real-time request handling process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary layer (cache memory) between the databases and the user interface. This cache acts as a buffer that stores frequently accessed data, allowing the system to serve requests quickly without directly querying the databases each time. This intermediary structure reduces system complexity while maintaining real-time monitoring accuracy.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If large volumes of data are accessed across multiple databases to provide comprehensive monitoring, then information completeness improves, but data access time and system resource consumption increase

Engineering Contradiction:
Improveinformation completenessVSAvoiddata access time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system extracts and caches only the specific data records that are likely to be requested, rather than accessing entire databases each time. By identifying and storing relevant subsets of data in advance, the system provides comprehensive monitoring information while significantly reducing data access time and resource consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary data fetching for records that are anticipated to be needed for monitoring. This allows comprehensive information to be prepared in advance, so when users request data, it is already available in the cache, eliminating the time delay associated with querying multiple databases in real-time.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If data is cached before requests to improve response time, then system responsiveness improves, but data freshness and accuracy may deteriorate

Engineering Contradiction:
Improvesystem responsivenessVSAvoiddata freshness
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The caching system is designed to be dynamic rather than static. It automatically manages cache contents by adding newly fetched records and removing or updating older records based on usage patterns and recency. This dynamic approach ensures that cached data remains fresh and accurate while still providing quick response times for commonly requested information.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system incorporates feedback mechanisms that monitor data usage patterns and cache performance. Based on this feedback, the system adjusts which records to cache, when to refresh cached data, and how long to retain records. This feedback-driven approach maintains data freshness and accuracy while optimizing system responsiveness.

Inventive Principle:
Principle #23Feedback

4Reliability

If real-time data access is implemented to prevent supply chain disruptions, then operational reliability improves, but computational overhead and energy consumption increase

Engineering Contradiction:
Improveoperational reliabilityVSAvoidcomputational overhead
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

Instead of continuously accessing all databases in real-time, the system performs partial actions by caching only the specific records that are likely to be needed for monitoring supply chain status. This selective caching approach maintains operational reliability by ensuring critical data is available while significantly reducing computational overhead and energy consumption compared to comprehensive real-time database queries.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS7844586B2Methods and systems in monitoring tools for effective data retrieval
Publication Date: 2010.11.30 SAP SE
  • US7844586B2 patent drawing
  • US7844586B2 patent drawing
  • US7844586B2 patent drawing

AI summary

Systems and methods are provided for accessing and presenting data in real-time. In one exemplary embodiment, the systems and methods may include presenting a first record set, fetching a second record set before a data request, and presenting the second record set in response to the data request. The first record set may be associated with at least one of a first part monitored by the monitoring system, a first location of the first part, and a first supplier of the first part. The second record set may be associated with at least one of a second part monitored by the monitoring system, a second location, and a second supplier.