Aircraft Refueling Control Architecture for Remote Upgrades

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing aircraft refueling systems lack efficient methods for modifying and upgrading controllers, data transmission, and analysis to improve system performance.

Innovation Solution

An aircraft refueling system incorporating a master controller, fleet controller, platform controller, and fuel control system with components like a primary pressure controller, secondary pressure controller, programmable logic controller, and data logger controller, enabling remote data analysis and software upgrades to enhance system performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If refueling systems use standalone controllers without remote communication capabilities, then device complexity is reduced, but adaptability for receiving data, transmitting data to remote locations, and analyzing data from multiple systems is limited

Engineering Contradiction:
Improvedata transmission and analysis capabilityVSAvoidcontroller complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system divides the refueling control into multiple independent controllers (master controller, fleet controller, platform controller, fuel control system with primary and secondary pressure controllers). Each controller handles specific functions and can operate semi-independently, allowing data transmission capabilities to be added to specific controllers without requiring all controllers to be complex. This segmentation enables adaptability improvements while keeping individual device complexities manageable.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The master controller is designed with multi-functional capabilities including receiving data from multiple sources (fleet controller, platform controller, fuel control system), analyzing this data, modifying operational parameters, and performing remote software upgrades. This universal design allows a single controller to handle diverse functions that would otherwise require multiple specialized devices, improving adaptability without proportionally increasing overall system complexity.

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

2Loss of time

If controllers are upgraded remotely, then downtime is reduced, but reliability of the refueling process may be affected during updates

Engineering Contradiction:
Improvecontroller upgrade timeVSAvoidrefueling process reliability
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system performs data analysis and operational parameter modifications before executing remote software upgrades. The master controller receives and analyzes operational data, determines necessary modifications, and prepares upgrade packages in advance. This preliminary action ensures that controllers are upgraded based on actual performance needs rather than arbitrary schedules, minimizing unnecessary downtime while maintaining reliability through data-driven decision-making.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system continuously monitors refueling operations and controller performance, using this feedback to determine when upgrades are necessary and to verify that upgrades maintain system reliability. The master controller receives data from all subordinate controllers, analyzes their performance, and only initiates upgrades when beneficial. This feedback mechanism ensures that reliability is maintained by upgrading based on actual performance degradation rather than predetermined schedules.

Inventive Principle:
Principle #23Feedback

3Productivity

If data is collected and analyzed from multiple controllers to improve system performance, then productivity is enhanced, but device complexity increases due to additional communication and analysis requirements

Engineering Contradiction:
Improvesystem performance optimizationVSAvoiddata communication and analysis complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments data collection and analysis functions across multiple controllers with clear divisions of labor. The fuel control system collects data from pressure sensors and fuel flow meters, the platform controller collects data from refueling operations, the fleet controller aggregates data from multiple platforms, and the master controller performs comprehensive analysis. This segmentation allows each controller to handle data collection and analysis at its appropriate level without requiring all controllers to have full data processing capabilities, thus improving productivity while managing complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system merges data from multiple sources (fuel control system, platform controller, fleet controller) at the master controller level for comprehensive analysis. By combining data streams and analysis capabilities at a centralized master controller rather than distributing full analysis capabilities to all controllers, the system achieves improved productivity through holistic data analysis while avoiding the complexity of replicating full analysis functionality across all devices.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP3853129B1Aircraft refueling system
Publication Date: 2025.07.02 EATON INTELLIGENT POWER LTD
  • EP3853129B1 patent drawingFigure 1
  • EP3853129B1 patent drawingFigure 2
  • EP3853129B1 patent drawingFigure 3

AI summary

An aircraft refueling system (10) includes a master controller (12), a fleet controller (14) in communication with the master controller, a platform controller (18) in communication with the fleet controller, and a fuel control system (16) in communication with the platform controller. Embodiments of an aircraft refueling system may include a primary pressure controller (20), a secondary pressure controller (22), a programmable logic controller (24), and a data logger controller (26). The master controller may be configured to receive and analyze data from at least one of the fleet controller, the platform controller, and the fuel control system; and to modify operational parameters or upgrade the fuel control system based at least in part on the analysis of received data.