Centralized Fuel Management System Eliminates Local Server Sync Conflicts

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Decentralized fuel management systems with local servers at each airport become unreliable and complex as the number of airports grows, leading to frequent downtime due to data discrepancies and communication conflicts.

Innovation Solution

A centralized fuel management system where hand-held devices at each airport forward data to a central data center, which then aggregates and forwards it to the fleet operator's central computer system, eliminating the need for local servers and reducing synchronization issues.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a decentralized fuel management system with local servers is used at each airport, then fuel management can be performed locally, but the system becomes unreliable and complex as the number of airports grows

Engineering Contradiction:
Improvelocal fuel management capabilityVSAvoidsystem reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent merges multiple decentralized local servers into a single centralized server that handles fuel management for all airports. This consolidation eliminates the reliability issues of multiple synchronized databases while maintaining local operational capability through a unified system that all airports access.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The centralized server performs multiple functions: it serves as the database for all airports, handles fuel management calculations, communicates with ACARS systems, and manages data synchronization across all locations. This single universal system replaces multiple specialized local servers.

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

2Speed

If a local server maintains a local database at each airport, then local fueling decisions can be made quickly, but frequent synchronization with the airline's database is required

Engineering Contradiction:
Improvelocal fueling decision speedVSAvoidsynchronization complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent extracts the database functionality from multiple local servers and consolidates it into a single centralized database. This eliminates the synchronization complexity while maintaining fast local decision-making capability by having all airports access the same unified data source.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If hundreds of servers are connected to the airline computer system for synchronization, then each airport can operate independently, but data discrepancies and communication conflicts cause frequent downtime

Engineering Contradiction:
Improveindependent airport operationVSAvoidsystem uptime
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent combines hundreds of independent server operations into a single centralized server that all airports access. This maintains the ability for each airport to operate independently while eliminating the data discrepancy and communication conflict issues that arise from having multiple synchronized systems.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8666586B2Enterprise fuel management system
Publication Date: 2014.03.04 QT TECHNOLOGIES LLC
  • US8666586B2 patent drawing
  • US8666586B2 patent drawing
  • US8666586B2 patent drawing

AI summary

An enterprise fuel management system for managing fueling operations of an aircraft fleet operated by a fleet operator having a central computer system at a data center and operating aircraft at multiple airports avoids reliability problems associated with synchronizing a central database with local databases. Data collection units communicate collected fueling information wirelessly to a central data center, and the data collection units are not in direct communication with the fleet operator's central computer system. Moreover, the central data center gathers fueling information from the various data collection units and communicates the gathered fueling information to the fleet operator's central computer system as data messages for subsequent processing and action. In this way, the fleet operator's central computer system can maintain the only database of fueling information and flight information, obviating the need to synchronize the data in the fleet operator's computer system with data in some other computer system.