System and method for situational control of mobile platform maintenance and operation

• US 20080114507A1
• Filed: 11/10/2006
• Published: 05/15/2008
• Est. Priority Date: 11/10/2006
• Status: Abandoned Application

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: Ruth, Robert S., Knudson, Richard T.
• Application Number:
  US11/558,806
• Publication Number:
  US 20080114507A1
• Time in Patent Office: Days
• US Class Current: 701/29
• CPC Class Codes: G05B 23/0283 Predictive maintenance, e.g. involving the monitoring of a system and, based on the monitoring results, taking decisions on the maintenance schedule of the monitored system; Estimating remaining useful life [RUL] preventive maintenance, i.e. planning maintenance according to the available resources without monitoring the system G06Q10/06
• CPC Class Codes: G06Q 10/00 Administration; Management

Abstract

A system for managing situational events associated with a mobile platform (such as a train, ship, aircraft or automobile) is provided. The system includes an operational events module that determines if a situation regarding the mobile platform has occurred based on event input. The event input is generated by a log book, a maintenance system, a materials management system, a diagnostic system or an operations system for example. The system also includes a situational manager module that determines at least one alert based on the situation if the situation exists. The system further includes a graphical user interface module that displays the event input, the situation and the alert data to enable an operator to view the events relating to the mobile platform and determine a response to the situation if a situation exists.

Claims

1. A system for managing situational events associated with a mobile platform comprising:

an operational events module that determines if a situation regarding the mobile platform has occurred based on event input;

a situational manager module that determines at least one alert based on the situation if a situation exists; and

a graphical user interface module that displays the event input, the situation and the alert data to enable an operator to view the events relating to the mobile platform and to determine a response to the situation if a situation exists.

2. The system of claim 1, wherein the operational events module further comprises:

an integration broker that receives the event input and transforms the event input into event data;

an operational event handler module that receives the event data; and

an operational event database receives the event data from the operational event handler module and that stores the event data to provide stored event data regarding the operation of the mobile platform.

3. The system of claim 2, wherein the operational events module further comprises:

a knowledge fusion agent that determines if the event data is a situation based on the event data and the stored event data from the operational event database, and if the event data is a situation, stores the event data as situation data in the operational event database.

4. The system of claim 3, wherein the knowledge fusion agent is invoked by the operational event handler based on the type of event data received.

5. The system of claim 3 wherein the situation manager module further comprises:

a situation manager that determines an alert based on the situation data, and that determines a workflow to manage the situation data.

6. The system of claim 5, wherein the alert is selected from the group comprising:

a text notification, a visual notification, an audible notification or combinations thereof.

7. The system of claim 3 further comprising a post situation analysis module that analyzes the event data and the situation data received from the operational events module and includes:

a data mart that stores the event input and situation event received from the operational event database; and

a data miner module that determines trend data and anomaly data based on the data stored in the data mart.

8. The system of claim 1, further comprising at least one of a log book that generates the event input, a maintenance system that generates the event input, a materials management system that generates the event input, a diagnostic system that generates the event input, an operations system that generates the event input and combinations thereof.

13. The method of claim 7, further comprising:

transferring the data stored in the operational event database to a data mart;

analyzing the data in the data mart for at least one of historical data, trend data and anomaly data; and

outputting at least one of the historical data, the trend data and anomaly data.

9. A method of managing the maintenance and operation of a mobile platform in response to an operational event comprising:

receiving at least one event input regarding the mobile platform relating to at least one of a required maintenance event and an operation event;

determining if a situation exists that is associated with performing the required maintenance event or operation event, based on the received event input; and

alerting at least one operator if the situation exists.

10. The method of claim 9, further comprising:

storing the event input in an operational event database to provide stored event data associated with the operation of the mobile platform; and

determining if the received event input is a situation based on a combination of the received event input and the stored event data.

11. The method of claim 10, wherein determining if the event input is a situation further comprises:

comparing the combination of event input and stored event data to known event data patterns that result in situations;

determining that a situation exists if the event input and stored event data match a known event data pattern; and

storing the situation in the operational event database.

12. The method of claim 9, wherein alerting at least one operator if a situation exists further comprises:

transmitting at least one of a text message, audible message or visual message including data regarding the situation;

awaiting a response; and

transmitting at least one of a second text message, audible message or visual message if there is no response.

14. The method of claim 12, wherein alerting at least one operator further comprises:

initiating a workflow operation to manage the situation.

15. The method of claim 9, wherein receiving at least one event input further comprises at least one of:

receiving an event input from a log book indicative of at least one of a pilot reported error, an actual departure time of the mobile platform, and an actual arrival time of the mobile platform;

receiving an event input from a maintenance system indicative of a scheduled maintenance event;

receiving an event input from a materials management system indicative of a time to receive a component required for the scheduled maintenance event;

receiving an event input from a diagnostic system indicative of a sensed condition of the mobile platform requiring maintenance; and

receiving an event input from an operations system indicative of a scheduled route plan for the mobile platform.

16. A method of managing the maintenance and operation of at least one aircraft in response to an operational event comprising:

receiving an event input relating to at least one of a required maintenance event and an operation event for the aircraft;

storing the event input into an operational events database;

gathering from the operational events database stored event inputs that match the received event input;

matching the received event input and stored event inputs to predefined event inputs that result in situations; and

determining that a situation exists based on the matched combination of the received event input and the stored event inputs.

17. The method of claim 16, further comprising:

storing the situation event in the operational events database.

18. The method of claim 16, further comprising:

transmitting at least one of a text message, audible message or visual message including data regarding the situation;

awaiting a response; and

transmitting at least one of a second text message, audible message or visual message if there is no response.

19. The method of claim 17, further comprising:

transferring the data stored in the operational events database to a data warehouse;

analyzing the data in the data warehouse for at least one of historical data, trend data and anomaly data; and

outputting at least one of the historical data, trend data, and the anomaly data.

20. The method of claim 16, wherein receiving the plurality of event inputs further comprises at least one of:

receiving an event input from a log book indicative of at least one of a pilot reported error, an actual departure time of the aircraft, and an actual arrival time of the aircraft;

receiving an event input from a maintenance system indicative of a scheduled maintenance event;

receiving an event input from a materials management system indicative of a time to receive a component required for the scheduled maintenance event;

receiving an event input from an aircraft diagnostic system indicative of a sensed condition of the aircraft requiring maintenance; and

receiving an event input from an operations system indicative of a scheduled route plan for the mobile platform.