Sustaining a fleet of configuration-controlled assets

• US 10,248,914 B2
• Filed: 11/14/2006
• Issued: 04/02/2019
• Est. Priority Date: 11/29/2005
• Status: Active Grant

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: Stoughton, Chris, Thompson, Jenny B., Gould, Peter M., Bacon, Alan J., Hooks, Dean C., White, Robert W., Fox, Barry R., Oakes, Janet E., Beggs, Robert M., Bonin, Kim, Burke, Terence M.
• Primary Examiner(s): Santos-Diaz, Maria C
• Application Number:
  US11/559,492
• Publication Number:
  US 20070124189A1
• Time in Patent Office: 4,522 Days
• Field of Search: 705 8
• CPC Class Codes: G05B 2219/31348 Gateway
• CPC Class Codes: G05B 2219/31396 Business management, production, document, asset, regulatory management, high level
• CPC Class Codes: G05B 2219/32024 Remote ordering, electronic selection article and fitting to form of client
• CPC Class Codes: G05B 2219/32234 Maintenance planning
• CPC Class Codes: G05B 2219/36542 Cryptography, encrypt, access, authorize with key, code, password
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management
• CPC Class Codes: G06Q 10/08 Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
• CPC Class Codes: G06Q 10/20 Administration of product repair or maintenance
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

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.

Claims

1. A computer-implemented method for sustaining a fleet of configuration-controlled assets, the method implemented using a sustainment data system (SDS) server including a processor in communication with a memory, the method comprising:

integrating a plurality of previously separate computer applications each including specific reusable business transactions associated with managing a fleet of assets, wherein functional capabilities of individual computer applications of the plurality of previously separate computer applications are defined by one or more of the specific reusable business transactions executable therein, wherein the plurality of previously separate computer applications are separate from the assets of the fleet of assets, and wherein a first computer application of the plurality of previously separate computer applications communicates via a first communication format to a first gateway, where the first gateway communicates with the SDS server via a second communication format;

receiving, by the SDS server from an engineering data system, technical data associated with one asset of the fleet of assets, wherein the engineering data system is separate from the one asset of the fleet of assets;

translating, by the SDS server, the received technical data from a third communication format associated with the engineering data system to the second communication format associated with the SDS server;

transmitting, from the SDS server to the first gateway associated with the first computer application, the translated technical data;

converting, by the first gateway, the translated technical data from the second communication format to the first communication format;

transmitting, from the first gateway to the first computer application, the converted technical data, wherein the first computer application is configured to utilize at least one of the specific reusable business transactions, wherein the first computer application is further configured to install the converted technical data, and wherein the first computer application is separate from one asset of the fleet of assets;

receiving, by the SDS server from the at least one asset, sensor data associated with a first mission completed by the at least one asset;

determining, by the SDS server, a work order and a schedule to perform the work order, based on the received sensor data for the at least one asset, an availability of a trained resource to perform the work order, and the technical data;

transmitting, from the SDS server to a computer system associated with a user, the work order and the schedule for display to the user;

planning, by the SDS server, using one or more of the previously separate computer applications, a second mission for the at least one asset; and

transmitting, from the SDS server to the computer system associated with the user, the second mission for display to the user.

2. The method of claim 1, further comprising:

determining whether parts are available to fulfill the work order.

3. The method of claim 2, further comprising receiving performance of the work order and recording the work performed.

4. The method of claim 2, further comprising tracking and reporting one or more anomalies detectable via one or more of the plurality of previously separate computer applications.

5. The method of claim 2, further comprising:

aggregating metrics data associated with sustaining the fleet of assets; and

calculating one or more key performance indicators (KPIs) based on the metrics data collected wherein the one or more KPIs are identified by a customer.

6. The method of claim 5, further comprising:

forwarding at least one of the metrics data or the KPIs for engineering system analysis and feedback; and

analyzing the metrics data or KPIs for reliability, maintainability, and performance trends related to the fleet of assets and the assets.

7. The method of claim 6, further comprising:

forwarding at least one of the metrics data or the KPIs for logistical system analysis and feedback; and

analyzing the metrics data or KPIs for logistical reliability, logistical maintainability, and logistical performance trends related to the fleet of assets and the assets.

8. The method of claim 1, further comprising managing users of the plurality of separate computer applications via a central authoritative logon for the plurality of previously separate computer applications.

9. The method of claim 8, wherein managing users via the central authoritative logon comprises:

receiving logon inputs from one or more users;

identifying and authenticating the one or more users; and

issuing a role-based credential for each of the one or more users to be used during a user session accessing one or more of the plurality of previously separate computer applications.

10. The method of claim 1, wherein the plurality of previously separate computer applications comprise at least two of a vehicle mission planning system, a supply chain management system, a training management system, a vehicle configuration state database, an optimized resource planning service, a technical publications system, a maintenance management system, and an integrated vehicle health management system.

19. The method of claim 1 further comprising:

determining that the first computer application is replaced with a second computer application, wherein the second computer application communicates via a fourth communication format; and

generating a second gateway associated with the second computer application, wherein the second gateway is configured to communicate between the second computer application and the SDS server, and wherein the second gateway is configured to convert communications between the second communication format and the fourth communication format.

20. The method of claim 19 further comprising:

transmitting, from the SDS server to the second gateway associated with the second computer application, the translated technical data;

converting, by the second gateway, the translated technical data from the second communication format to the fourth communication format; and

transmitting, from the second gateway to the second computer application, the converted technical data, wherein the second computer application is further configured to install the converted technical data, and wherein the second computer application is separate from the at least one asset of the fleet of assets.

11. A computer-readable non-volatile medium having control logic stored therein for causing a sustainment data system (SDS) server to sustain a fleet of configuration-controlled assets, the SDS server including a processor in communication with a memory, the control logic comprising computer-readable program code for causing the SDS server to:

integrate a plurality of previously separate computer applications each including specific reusable business transactions associated with managing a fleet of assets, wherein functional capabilities of individual computer applications of the plurality of previously separate computer applications are defined by one or more of the specific reusable transactions executable therein, wherein the plurality of previously separate computer applications are separate from the fleet of assets, and wherein a first computer application of the plurality of previously separate computer applications communicates via a first communication format to a first gateway, where the first gateway communicates with the SDS server via a second communication format;

receive technical data associated with at least one asset of the fleet of assets from a second computer application of the plurality of previously separate computer applications that is separate from the fleet of assets;

integrate the received technical data per customer requirements;

translate the received technical data from a third communication format associated with the at least one asset of the fleet of assets to a second format associated with the SDS server;

transmit, to the first gateway associated with the first computer application, the translated technical data;

convert, by the first gateway, the translated technical data from the second communication format to the first communication format;

transmit, from the first gateway to the first computer application, the converted technical data, wherein the first computer application is configured to utilize at least one of the specific reusable business transactions, and wherein the first computer application is further configured to install the converted technical data, and wherein the first computer application is separate from the at least one asset of the fleet of assets;

receive sensor data associated with a mission completed by the at least one asset, the sensor data received from at least one of the plurality of previously separate computer applications;

determine, based on execution of the plurality of previously separate computer applications, a work order and a schedule to perform the work order, based on the received sensor data for the at least one asset, an availability of a trained resource to perform the work order, and the technical data;

transmit, to a computer system associated with a user, the work order and the schedule for display to the user;

plan, using at least one of the plurality of previously separate computer applications, a second mission for the at least one asset; and

transmit, to the computer system associated with the user, the second mission for display to the user.

12. A method for sustaining a fleet of vehicles, the method implemented using a sustainment data system (SDS) server including a processor in communication with a memory, the method comprising:

integrating and executing, within the SDS server, a plurality of modules associated with the management of a fleet of mobile platforms, the plurality of modules including a mission planning system for planning the missions for individual platforms within the fleet of mobile platforms, an integrated vehicle health management system (IVHMS), and a resource planning service for determining schedules for performing work orders on the individual platforms, wherein the plurality of modules are separate from the fleet of mobile platforms, and wherein a first module of the plurality of modules communicates via a first communication format to a first gateway, where the first gateway communicates with the SDS server via the second communication format;

creating, by the SDS server, a predetermined set of messages for allowing the plurality of the modules, including the mission planning system, the IVHMS, and the resource planning service to communicate with each other;

receiving, by the SDS server, technical data associated with at least one individual platform of the fleet of mobile platforms from a second module of the plurality of modules;

translating, by the SDS server, the received technical data from a third format associated with the at least one individual platform of the fleet of mobile platforms to a second format associated the SDS server;

transmitting, from the SDS server to the first gateway associated with the first module, the translated technical data;

converting, by the first gateway, the translated technical data from the second communication format to the first communication format;

transmitting, from the first gateway to the first module, the converted technical data, wherein the first module is configured to utilize at least one reusable business transaction, and wherein the first module is further configured to install the converted technical data;

determining a schedule to perform a work order using results from execution of the resource planning service that are based at least in part on data provided by execution of the mission planning system, an availability of a trained resource to perform the work order, the technical data, and the IVHMS, wherein data provided by the IVHMS includes sensor data associated with missions completed by the individual platforms;

transmitting, to a computer system associated with a user, the work order and the schedule for display to the user;

determining a second mission for the individual platforms using the mission planning system and the resource planning service; and

transmitting, to the computer system associated with the user, the second mission for display to the user.

13. The method of claim 12, further comprising the step of monitoring a performance of the plurality of modules.

14. The method of claim 12, further comprising the step of monitoring anomalies detected by the plurality of modules.

15. The method of claim 12, further comprising the steps of analyzing anomalies detected by the plurality of modules and providing a recommendation.

16. A method for managing the insertion and removal of previously separate domain applications that have been integrated with one another, the method implemented using a sustainment data system (SDS) server including a processor in communication with a memory, said method comprising:

configuring an extended application interface to connect the previously separate domain applications together, each previously separate domain associated with an aspect of management of a fleet of assets, wherein the previously separate domain applications are separate from the fleet of assets, wherein a first domain application of the plurality of previously separate domain applications communicates via a first communication format to a first gateway, wherein a second domain application of the plurality of previously separate domain applications communicates via a second communication format to a second gateway, and wherein the first gateway and the second gateway communicate with the SDS server via a third communication format;

receiving, at the first gateway, data from the first domain application for the second domain application, wherein the first domain application and the second domain application are separate from the fleet of assets;

translating, by the first gateway, the received data from the first communication format associated with the first domain application into the third communication format associated with the SDS server;

receiving, at the SDS server, the translated data from the first gateway;

transmitting, from the SDS server, the translated data to the second gateway;

converting, by the second gateway, the translated technical data from the third communication format to the second communication format;

transmitting, from the second gateway to the second domain application, the converted technical data;

operating, by the SDS server, a transaction manager to extract and install one or more reusable transactions;

implementing, in the SDS server, an application adapter for each new domain application to be added, with the application adapter configured to interface the new domain application to the extended application interface;

receiving a plurality of data from the previously separate domain applications, wherein the plurality of data received is associated with the fleet of assets and is one of technical data and sensor data for each of the assets in the fleet of assets, the plurality of data received from a domain application associated with an engineering data system and configured to update at least one of stored engineering data and stored logistics analysis data of at least one asset, the sensor data associated with a mission completed by the at least one asset, the sensor data received from the previously separate domain applications;

aggregating, by the SDS server, data received from the previously separate domain applications; and

determining a reliability trend, using the aggregated data, for one or more assets of the fleet of assets.

17. The method of claim 16 wherein configuring the extended application interface to connect the previously separate domain applications together comprises combining message-oriented middleware and service oriented architecture with modular application gateway adapters and standard formatted messages.

18. The method of claim 16 further comprising connecting existing systems with logic contained in modular application gateway connectors through verified transactions with anti-spoofing capabilities.