Patent Grant
8316225
The invention relates generally to the transfer of mobile platform metrics and fault data from logbooks utilized onboard the mobile platform to ground based systems during mobile platform operations or when the mobile platform reaches its destination. More particularly, the invention relates to transferring such data between an electronic logbook onboard the mobile platform and the ground based systems.
Airlines and other mobile platform providers, such as companies that provide passenger and/or cargo transportation by bus, train or ship, often maintain travel metrics and fault data during operation of the mobile platform. Metrics data generally include information and data regarding such things as origin and destination information for the mobile platform, passenger information and flight crew information, travel times, fueling information, etc. Fault data generally include data detailing problems with the mobile platform that were detected during the operation of the mobile platform. This fault data is used to determine whether the mobile platform meets regulatory and operational requirements and can be re-dispatched or redeployed.
Often, the metric and fault data are recorded by hand on preprinted forms during operation of the mobile platform and maintained in metrics and maintenance logbooks. The logbooks are generally carried off the mobile platform by crew of the mobile platform when the mobile platform reaches a mobile platform terminal at its destination. The metrics and fault data are then keyed into a ground based computer system to be stored in an electronic database. The ground based computer system may include a “master” logbook database, operational decision aid systems, e.g. mobile platform health management systems, and/or data repository systems, e.g. maintenance history systems. Often the forms can be multi-part forms where each part goes to a different department at the mobile platform terminal. Additionally, corrective maintenance actions taken to address the fault reports need to be recorded in the logbooks to be available to crew members of the mobile platform when the mobile platform departs from the terminal for another destination. Such data entry tasks are time consuming and provide data to using systems after significant time delay. Furthermore, this paper logbook process is labor intensive and has significant inefficiencies inherent in the process. Further yet, faults may occur during high workload periods on the mobile platform causing the mobile platform operators to delay recording or not record certain information, such as fault codes that allow direct correlation to system generated fault messages. Such delayed or non recording can inhibit timely clearing of the fault condition by the mobile platform maintenance crew.
Recently, some mobile platform providers have implemented electronic metrics and fault data recordation and maintenance systems where an electronic logbook is utilized. The electronic logbook includes electronic forms that are utilized by crew onboard the mobile platform during operation of the mobile platform. Although the electronic logbooks increase efficiency, they, too, generally need to be removed from the mobile platform to download the data to the ground based computer system and stored in electronic databases. The ground based systems can provide the capability to efficiently process metrics and fault information and can help prioritize which faults should be addressed and to identify the particular maintenance procedure needed to address the particular fault report. Since the clearing of a fault may be required to dispatch the mobile platform on another mission, this delay can affect the schedule of operation of the mobile platform.
With the prevalence of contemporary communication, downloading the metrics and fault data from the electronic logbooks to the ground based systems while the electronic logbooks remain on board the mobile platforms is possible. However, mobile platforms move throughout the country and the world with a variety of electronic communication connectivity options and availability en-route and at each mobile platform terminal. For example, connectivity at certain mobile platform terminals may employ IEEE 802.11 or global packet radio service (GPRS) wireless protocols, while other terminals may employ VHF and satellite networks. Yet other terminals may utilize broadband satellite networks and still other terminals may not have communication connectivity availability, but instead may use a direct wired connection. VHF and satellite communications are available for transfer of data while the mobile platform is en-route.
Therefore, there is a need to move mobile platform metrics and fault data and maintenance records between such electronic logbooks and the ground based mobile platform terminal systems in an efficient, repeatable and secure automated manner.
In various embodiments of the present invention a system and method are provided for establishing a communication link between an onboard computer system (OCS) of a mobile platform and a central computer system (CCS) located remotely from the mobile platform. The method includes sending a message containing data to be downloaded from the OCS to the CCS from a first portion of an electronic log book function (ELB1) of the OCS to a second portion of a communications management function (CMF2) of the OCS. Execution of the ELB1 and CMF2 configures the message into a transmittable data file that can be communicated to the CCS using any suitable Internet protocol and places the transmittable data file into an outgoing queue of the CMF2. The CMF2 automatically selects at least one desired communication channel from a plurality of available communication channels utilizing a configuration file of the CMF2. The configuration file includes a plurality of desired communication channels that the OCS can utilize to communicate with the CCS. Execution of the CMF2 further establishes a secure link between the OCS and the CCS utilizing the automatically selected communication channel. The CMF2 then sends the transmittable data file containing the data message to a first portion of a communications management function (CMF1) included in the CCS, via the secure established link over the automatically selected channel.
The features, functions, and advantages of the present invention can be achieved independently in various embodiments of the present inventions or may be combined in yet other embodiments.
The present invention will become more fully understood from the detailed description and accompanying drawings, wherein;
Corresponding reference numerals indicate corresponding parts throughout the several views of drawings.
The following descriptions of various embodiments are merely exemplary in nature and are in no way intended to limit the invention, its application or uses. Additionally, the advantages provided by the preferred embodiments, as described below, are exemplary in nature and not all preferred embodiments provide the same advantages or the same degree of advantages.
The OCS 14 can be a stand alone system or a subsystem of any other system, network or component onboard the mobile platform 18. For example, in various embodiments the OCS 14 is an electronic travel aid utilized by an operator of the mobile platform 18 to enhance ease and efficiency of many tasks the operator must perform during operation of the mobile platform 18. An exemplary electronic travel aid utilized by some airlines is referred to as an electronic flight bag (EFB). Alternatively, the OCS 14 can be a subsystem of an onboard local area network (LAN) or any other onboard mobile platform control system. Although the mobile platform 18 is illustrated as an aircraft, the invention is not limited to aircraft applications. That is, the mobile platform 18 could be any mobile platform such as an aircraft, bus, train or ship.
The OCS 14 includes a processor 22 for executing all functions of the OCS 14 and an electronic storage device (ESD) 26 for electronically storing a first portion 28A of an electronic logbook (ELB) software application 28, and other applications, data, information and algorithms. The first portion 28A of the ELB software application 28 will be referred to herein as simply the ELB128A. The OCS 14 additionally includes a database 30. The OCS database 30 is an electronic memory device, i.e. computer readable medium, for storing large quantities of data organized to be accessed and utilized during various operation of the DASS 10. For example, a plurality of look-up tables containing maintenance data, fault data, maintenance procedures and mobile platform metrics may be electronically stored on the OCS database 30 for access and use by the DASS 10 and users of the DASS 10. The OCS ESD 26 can be any computer readable medium device suitable for electronically storing such things as data, information, algorithms and/or software programs executable by the OCS processor 22. For example, the OCS ESD 26 can be a hard drive, a Zip drive, a CDRW drive, a thumb drive or any other electronic storage device. The OCS 14 additionally includes a display 32 for illustrating graphical and textual data, forms and other information, and an input device 34 such as a keyboard, mouse, stylus, touch screen or joy stick for inputting data and information to the OCS 14 to be stored on the OCS ESD 26. It should be understood that the OCS processor, ESD, display and input device 22, 26, 30 and 34 can be components of a stand alone computer based system, i.e. the OCS 14, or components of a larger system, such as an onboard LAN or an onboard mobile platform control system that collectively comprise the OCS 14. Alternatively, the OCS 14 can be a stand alone system that is connectable to a larger system, e.g. an onboard LAN, such that various ones of the OCS processor, ESD, display and input device 22, 26, 30 and 34 are included in the stand alone OCS 14 and others are included in the larger system.
The ELB128A is executed and utilized by mobile platform crew to enter mobile platform operation and technical log information and store the log information in the OCS ESD 26, as the mobile platform travels from its origination point to its destination. Operation and technical log information includes such things as mobile platform metrics and fault information regarding the itinerary, schedule and operational performance of the mobile platform. As described further below, the OCS 14 is adapted to communicate the log information to the CCS 20 as the mobile platform 18 is in transit or when the mobile platform reaches a terminal including the CCS 20 at a destination of the mobile platform 18.
Generally, the OCS processor 22 executes the ELB128A to communicate with other systems, such as one or more central maintenance computers (CMCs) 36, onboard the mobile platform 18 and generate electronic log forms that are displayed on the OCS display 32. In various embodiments, the log forms include interactive information and data fields for a crew member of the mobile platform to read and/or fill out, utilizing the OCS input device 34, regarding metrics and fault data for the mobile platform. Additionally, the CMC 36 can communicate detected faults to the ELB128A and the ELB128A will automatically complete various data fields in the log forms so that the crew member can verify, edit, accept or reject the particular logbook entry. A system and method for automatically completing the various data fields in the log forms is described in co-pending patent application titled, “Fault Data Management”, Ser. No. 11/199,399, and assigned to The Boeing Company, which is incorporated by reference herein in its entirety. The OCS processor 22 stores the metrics and/or fault data input or accepted by the crew member in the OCS ESD 26 to be downloaded to the CCS 20, as described below.
The CCS 20 includes at least one processor 38, at least one database 42, at least one display 46, at least one electronic storage device (ESD) 50 and at least one input device 54. The CCS display 46 can be any display suitable for visually presenting graphics, text and data to a user of the DASS 10. The CCS input device 54 can be any device adapted to input data and/or information into CCS 20, for example a keyboard, a mouse, a joystick, a stylus, a scanner, a video device and/or an audio device. The CCS ESD 50 can be any computer readable medium device suitable for electronically storing a second portion 28B of the ELB 28, and such other things as data, information and algorithms and/or software programs executable by the CCS processor 38. For example, the CCS ESD 50 can be a hard drive, a Zip drive, a CDRW drive, a thumb drive or any other electronic storage device. The second portion 28B of the ELB 28 will be referred to herein simply as the ELB228B.
The CCS database 42 is also an electronic memory device, i.e. computer readable medium, for storing large quantities of data organized to be accessed and utilized during various operation of the DASS 10. For example, a plurality of look-up tables containing maintenance data, fault data, maintenance procedures and mobile platform metrics may be electronically stored on the CCS database 42 for access and use by the DASS 10 and users of the DASS 10. The CCS processor 38 controls all operations of the CCS 20. For example, the CCS processor 38 controls communications, e.g. wired or wireless, and data transfers between the CCS 20 and the OCS 14, displaying graphics and data on the CCS display 46, interpreting and routing information and data input by the CCS input device 54 and the executing various algorithms stored on the CCS ESD 50. Additionally, the CCS processor 38 executes the ELB228B to store downloaded data in the CCS database 42.
In various embodiments, the DASS 10 further includes a portable electronic device (PED) 58, e.g. a laptop computer, PDA or any other such device, that communicates with the CCS 20 and/or OCS 14 via a wired or wireless connection. The PED 58 is adapted to access and utilize data stored in the CCS database 42 or the OCS database 30 and also to input data to the CCS 20 or OCS 14 to be stored in the CCS database 42 of OCS database 30 and uploaded to the OCS ESD 26 for utilization by the ELB128A, if desirable. The PED 58 displays logbook data in a format suitable for use as a work management tool utilized to return the mobile platform to service. The PED 58 can contain such information and data as lists of required work, e.g. work orders, deferred maintenance actions and unresolved fault reports and any other assigned work found in the CCS database 42 or the OCS database 30
The mobile platform metrics and fault data are downloaded to the CCS 20 so that the data can be shared with mobile platform performance monitoring and maintenance systems (not shown). The mobile platform performance monitoring and maintenance systems may be software applications stored on the CCS ESD 50 or may be separate computer based systems communicatively linked with the CCS 20 and/or the OCS 14. The mobile platform performance monitoring and maintenance systems ensure that regularly scheduled maintenance is performed and that the mobile platform 18 and all systems onboard are maintained in proper operational order. Additionally, the metrics and fault data stored in the CCS database 42 and/or the OCS database 30 can be accessed and utilized, via the PED 58, by maintenance personnel responsible for performing the maintenance and repairs to the mobile platform 18. The metrics and fault data stored in the CCS database 42 and/or the OCS database 30 are synchronized whenever connectivity is established between the OCS 14 and the CCS 20.
The CCS 20 further includes a first portion 62A of a communication management function (CMF) stored on the CCS ESD 50. A second portion 62B of the CMF is stored on the OCS ESD 26. The first and second portions 62A and 62B of the CMF will be respectively referred to herein as the CMF162A and the CMF262B and collectively referred to here in as the CMF 62. Generally, the CMF 62 provides application program interfaces (APIs) to allow the ELB128A and the ELB228B to communicate, as described further below.
More particularly, to initiate communication between the OCS 14 and the CCS 20, the OCS processor 22 executes the ELB128A and the CMF262B to register the ELB128A with the CMF262B, as indicated at 202. Once the ELB128A is registered with the CMF262B, the ELB128A sends a message, containing any metric and fault data to be ‘downloaded’ to the CCS 20, to the CMF262B, as indicated at 204. The CMF262B then parses the message, generates a unique message identification for the message, converts the message into an encoded data string, and then configures the encoded data string into a transmittable data file so that the metric and/or fault data can be communicated to the CCS 20 using any suitable Internet protocol, as indicated at 206. For example the CMF262B can create an extensible markup language (XML) file so that the metric and/or fault data can be communicated to the CCS 20 using any suitable Internet protocol.
The CMF262B then places the transmittable data file into a CMF outgoing queue, as indicated at 208. The CMF262B can send the message to the CCS 20 via any suitable communication means, e.g. any suitable wired or wireless communication channel. For example, the CMF262B can send the message containing the transmittable data file to the CCS 20 using general packet radio service (GPRS), wireless IEEE 802.11, VHF, satellite networks, broadband satellite networks, or a direct wired connection. More specifically, the CMF262 includes a configuration file identifying all the desired communication channels the OCS 14 can utilize to communicate with the CCS 20. The number and type of communication channels included in the CMF2 configuration file is application specific and selected by the particular mobile platform provider. For example, a first mobile platform provider may desire to utilize Gatelink IEEE 802.11 and VHF and satellite networks, while a second mobile platform provider may desire to utilize only broadband satellite networks for communication between the OCS 14 and the CCS 20.
More particularly, the CMF262B determines and keeps track of what communication channels are available for communication between the OCS 14 and the CCS 20, as indicated at 210. The CMF262B automatically selects an appropriate communication channel based on the communication means included in the CMF2 configuration file determined by the operator based on expense of the channel and the value of the message, as indicated at 212. Utilizing the automatically selected communication channel, the CMF262B establishes a secure link between the OCS 14 and the CCS 20 and sends the message containing the transmittable data file to CCS 20, via the secure link, as indicated at 214. The CMF262B may store more than one message in the CMF outgoing queue and send only those messages that the priority rules, as determined by expense of the channel and value of the message, dictate should be sent via the presently established secure link. The CMF262B can then establish another secure link, as described above, using another available channel to send other messages in the CMF outgoing queue that the priority rules deem should be sent by the newly established secure link. If the priority rules and the messages in the CMF outgoing queue do not match any of the available channels, the CMF262B will store the messages until the necessary available channels are available.
Furthermore, the CMF262B establishes the secure link using any suitable certificate exchange method. For example, the CMF262B can establish the secure link utilizing the security certificate management method described in the co-pending patent application titled “Security Certificate Management”, Ser. No. 11/191,622, and assigned to the Boeing Company, which is incorporated herein by reference. Once the CMF262B sends the message containing the transmittable data file to CCS 20 over the secure link, the CCS processor 38 executes the ELB228B and the CMF162A to send an ‘ACK’ message to the OCS 14 acknowledging receipt of the message containing the transmittable data file, as indicated at 216. The CMF162A receives a call-back from an offline client for the message received, and the ELB228B extracts the fault and metric data message from the transmittable data file and logs the ‘ACK’, as indicated at 218. Once the CMF162A sends the ‘ACK’ message to the OCS 14, the ELB228B reads the metric and fault data from the extracted message and stores the metric and fault data in the CCS database 42, as described at 224.
Next, the CMF162A sends the maintenance log message to the OCS 14, via the secure link, as indicated at 304. The CMF262B receives the message containing the transmittable data file including the maintenance log data and stores the message in a CMF incoming queue, as indicated at 306. The CMF262B reads the received message and sends an ‘ACK’ message to the CMF162A, as indicated at 308. Based on information in the received maintenance log message, the CMF262B determines an appropriate destination, e.g. an appropriate application executable by the OCS processor 22, and sends a notification message, as indicated at 310. The appropriate application retrieves the message and sends an ‘ACK’ to the CMF262A, as indicated at 312. Finally, the appropriate application additionally sends an ‘ACK’ to the CMF162A, as indicated at 314. The exchange of ‘ACKs’ indicated at 312 and 314 ensure the appropriate synchronization of data between the CCS database 42 and the OCS database 30.
The DASS 10 provides rapid and human intervention-less movement of data by use of communication channels, e.g. wired or wireless, and improved availability of logbook data, thereby improving operational efficiency and reducing labor costs and other operating costs, e.g. schedule delays, of moving the metric and fault data to mobile platform health maintenance systems, e.g. the CCS 20 or other network connected to the CCS 20, in a timely fashion. Additionally, the DASS 10 coordinates and synchronizes the metric and fault data between the OCS 14, the CCS 20 and the PED 58 and enables near real-time status on the health of a particular mobile platform while it is en route.
Those skilled in the art can now appreciate from the foregoing description that the broad teachings of the present invention can be implemented in a variety of forms. Therefore, while this invention has been described in connection with particular examples thereof, the true scope of the invention should not be so limited since other modifications will become apparent to the skilled practitioner upon a study of the drawings, specification and following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6148179 | Wright et al. | Nov 2000 | A |
| 6173159 | Wright et al. | Jan 2001 | B1 |
| 6201797 | Leuca et al. | Mar 2001 | B1 |
| 6253129 | Jenkins et al. | Jun 2001 | B1 |
| 6275497 | Varma et al. | Aug 2001 | B1 |
| 6353734 | Wright et al. | Mar 2002 | B1 |
| 6516192 | Spaur et al. | Feb 2003 | B1 |
| 6760778 | Nelson et al. | Jul 2004 | B1 |
| 6816728 | Igloi et al. | Nov 2004 | B2 |
| 7039510 | Gumpinger | May 2006 | B2 |
| 7149612 | Stefani et al. | Dec 2006 | B2 |
| 7177939 | Nelson et al. | Feb 2007 | B2 |
| 7260389 | Allen et al. | Aug 2007 | B2 |
| 7617029 | Loda | Nov 2009 | B2 |
| 7689329 | Avery et al. | Mar 2010 | B2 |
| 20030030581 | Roy | Feb 2003 | A1 |
| 20050003816 | Vardoulias et al. | Jan 2005 | A1 |
| 20050148327 | Perez et al. | Jul 2005 | A1 |
| 20050181787 | Judd et al. | Aug 2005 | A1 |
| Number | Date | Country |
|---|---|---|
| 203 19 116 | Aug 2004 | DE |
| WO 0150728 | Jul 2001 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20070028089 A1 | Feb 2007 | US |
