Reusable Business Transaction Integration for Fleet Assets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional fleet management systems are inflexible and costly to modify, requiring redevelopment of system interfaces for new integration needs and lacking domain-specific knowledge optimization, which hinders efficient adaptation to changing operational requirements.
Innovation Solution
A computer-implemented method and system that integrates multiple applications using reusable business transactions, allowing for the insertion and removal of applications without redevelopment, facilitated by an integration manager, gateway, application adapters, and intelligent transaction management, enabling seamless data packaging and distribution across a networked environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional point-to-point architecture is used to integrate domain-specific sustainment applications, then system integration is achieved, but any new integration needs require redevelopment of system interfaces, resulting in increased development costs and reduced flexibility
Solution Approach 1:
The patent implements a universal service-oriented architecture where standardized services can fulfill multiple integration needs across different domains. Instead of creating custom point-to-point interfaces for each integration scenario, the system provides a set of reusable services that can be universally applied to various sustainment applications, eliminating the need for repeated interface redevelopment
Solution Approach 2:
The patent introduces a service layer as an intermediary between applications and integration needs. This service layer acts as a mediator that handles all integration logic, allowing applications to communicate through standardized service interfaces rather than requiring direct point-to-point connections. This intermediary layer absorbs the complexity of integration, making the system adaptable to new needs without modifying application interfaces
2Productivity
If legacy applications are integrated with new applications in conventional systems, then fleet management capabilities are expanded, but the underlying suite of applications cannot be easily modified, requiring time-consuming and costly redevelopment
Solution Approach 1:
The patent segments the fleet management system into independent service components that can be individually developed, deployed, and modified. Each service is encapsulated with well-defined interfaces, allowing legacy and new applications to be integrated through service composition rather than tight coupling. This segmentation enables modifications to individual services without affecting the entire system, dramatically reducing modification time
Solution Approach 2:
The patent implements a dynamic service-oriented architecture where the system configuration can be changed at runtime. Services can be added, removed, or modified without requiring system shutdown or redevelopment of integrated applications. This dynamic approach allows the fleet management system to adapt to changing operational needs rapidly, eliminating the time-consuming redevelopment process inherent in conventional static architectures
3Adaptability or versatility
If conventional systems are designed to accommodate multiple distinct fleets of assets, then system versatility is improved, but the systems lack flexibility for easy modification of the underlying suite of applications
Solution Approach 1:
The patent implements universal services that can serve multiple distinct fleets of assets through a common infrastructure. The service-oriented architecture allows the same set of services to be configured and deployed for different fleet types (vehicles, aircraft, etc.) without requiring separate application suites. This universality maintains versatility while enabling easy modification through service configuration rather than application redevelopment
Data Source
AI summary
Methods, systems, and computer program products sustain a fleet of configuration-controlled assets. The method involves integrating a plurality of previously separate systems with reusable business transactions associated with managing a fleet of vehicles. The method also involves receiving operational data associated with a vehicle of the fleet, integrating the operational data per customer requirements, packaging and distributing the operational data to the plurality of systems, and installing and distributing the operational data to one or more applications of the plurality of systems utilizing reusable business transactions. The system utilizes a plurality of applications and a plurality of logical subsystems, which are connected to each other through gateways. The logical subsystems use a common format defined by a set of messages. However, the applications can use a plurality of different formats. The gateways, which are the connecting blocks, convert the data flow between the logical subsystems and the applications.