EP2158525A1 - Système informatique de maintenance d'un aéronef - Google Patents
Système informatique de maintenance d'un aéronefInfo
- Publication number
- EP2158525A1 EP2158525A1 EP08760549A EP08760549A EP2158525A1 EP 2158525 A1 EP2158525 A1 EP 2158525A1 EP 08760549 A EP08760549 A EP 08760549A EP 08760549 A EP08760549 A EP 08760549A EP 2158525 A1 EP2158525 A1 EP 2158525A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- module
- maintenance
- hosted
- documentation
- computer system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/105—Multiple levels of security
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0218—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults
- G05B23/0243—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults model based detection method, e.g. first-principles knowledge model
- G05B23/0245—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults model based detection method, e.g. first-principles knowledge model based on a qualitative model, e.g. rule based; if-then decisions
- G05B23/0248—Causal models, e.g. fault tree; digraphs; qualitative physics
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
- G05B23/0267—Fault communication, e.g. human machine interface [HMI]
- G05B23/0272—Presentation of monitored results, e.g. selection of status reports to be displayed; Filtering information to the user
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Definitions
- the present invention relates generally to the field of aeronautical maintenance.
- logbook is also in the form of an electronic document, called "eLogbook”.
- the aforementioned electronic documents are also linked together by means of hyperlinks, so that the operator can easily switch from one application to another.
- CMS Centralised Maintenance System
- BITE Built In Test Equipment
- the maintenance operator therefore has at his disposal a plurality of disparate computer tools that he must master to be able to diagnose and solve a possible failure.
- the on-board network is generally partitioned into two sub-networks, the first located in a so-called avionic zone, the second in a so-called open or non-secure zone.
- the links between the two sub-networks are necessarily unidirectional, directed from the avionics subnet to the open subnet.
- the links can be bidirectional.
- Hosting the maintenance tools in the open area would not guarantee their integrity, ie effectively guard against malicious access and / or corruption of the programs and data that constitute them. As a result, maintenance tools would not be eligible for certification.
- An object of the present invention is to propose a maintenance tool for an aircraft that does not have the aforementioned drawbacks, that is to say, on the one hand, that allows to guide the operator in a systematic way and to on the other hand, which offers an implementation compatible with the partition of the embedded network.
- the present invention is defined by a computer maintenance system for an aircraft equipped with a partitioned network in a secure area, called avionics, and an open area, said computer system comprising a first software module hosted in the avionics area and a second software module hosted in the open area, the first module being adapted to traverse a diagnostic tree, the second module being adapted to present an electronic maintenance documentation, the path of the diagnostics shaft by the first module inducing automatically and synchronously presenting by the second page module of said maintenance documentation respectively associated with these nodes.
- each node of said diagnostic tree corresponds to at least one maintenance task and the first module transmits to the second module a hyperlink pointing to a page of the maintenance documentation associated with this task when the first module reaches said node.
- the first module typically determines the next node based on the result of the execution of said maintenance task corresponding to that node.
- the diagnostic tree is determined for example from a fault identifier code, said code being itself obtained from an analysis of an entry of an electronic logbook hosted in the avionics zone. If the first module determines that a device of the aircraft is defective at the end of the path of the diagnostics tree, said system can be adapted to verify the presence of this equipment in a minimum list of aircraft equipment, called MEL list, hosted in the avionics area.
- the system is adapted to calculate the corresponding cost in terms of functional performance losses or safety margins of the aircraft.
- a third software module housed in the avionics zone, and a fourth software module, hosted in the open zone, may be provided, the third module being adapted to browse and select the elements of the MEL list, the fourth software module to be presented.
- documentation pages corresponding to said equipment the selecting an element by said third software module inducing automatically and synchronously a presentation by the fourth module of a documentation page relating to this element.
- the third module advantageously transmits to the fourth module, a hyperlink pointing to a URL containing said documentation page relating to this element.
- the first module and, if applicable, the third module can be hosted in a first computer of the avionics zone and the second module and, where appropriate, the fourth module can be hosted ( s) in a second computer of the open area, the second computer then being connected to the network portion of the avionic area by a unidirectional link to the open area and a wireless access point.
- the first module and, where appropriate, the third module can be hosted in a first computer of the avionics zone and the second module and, where appropriate, the fourth module can be hosted in a second computer of the open area, the inputs / outputs of the first and second computers being connected to a KVM switch, said switch being adapted to switch said inputs / outputs to a common input / output interface.
- Fig. 1 schematically illustrates a first embodiment of the maintenance system according to the invention
- Fig. 2 schematically illustrates an alternative embodiment of the maintenance system according to the invention
- Fig. 3 illustrates the operation of the maintenance system according to the invention
- Fig. 4 gives an example of a diagnostic tree
- Figs. 5A to 5G represent the contents of a first screen and a second screen of the maintenance system, during the progression of the diagnostic module along successive nodes of the diagnostic tree.
- the idea underlying the invention is to provide a maintenance system comprising a first software module hosted in the avionics area and a second software module hosted in the open area, the first being a diagnostic module adapted to perform a route in a diagnostic tree, the second being dedicated to the presentation of the maintenance documentation, the path of nodes of the diagnostic tree automatically and synchronously inducing a presentation of the documentation pages respectively associated with these nodes.
- Fig. 1 illustrates a maintenance computer system according to an embodiment of the invention.
- the system is composed of two parts 101 and 102 respectively included in the avionics zone AW and the open zone OW.
- Each of the parts of the system comprises a plurality of equipment interconnected by bidirectional links, for example virtual links of a switched Ethernet network.
- the two parts are connected to each other only by one or more unidirectional link (s) directed (s) from the AW zone to the OW zone, symbolized in the figure by diodes.
- the part of the avionic zone comprises a maintenance terminal 110 or OMT (Onboard Maintenance Terminal) hosting a centralized maintenance system (CMS), 113.
- This system comprises in particular a first software module, called diagnostic module, 115, adapted to traverse a predetermined diagnostic tree.
- the OMT terminal also hosts a software module 120, responsible for managing the logbook.
- the OMT terminal is also connected to integrated test modules, 130, implemented in some equipment to be tested, and to a unit 160 responsible for controlling all the circuit breakers relating to these devices. The activation of a circuit breaker makes it possible to cut off the power supply of one or more pieces of equipment in order to replace it safely.
- the OMT terminal has an input / output interface 150 including a display screen and a keyboard.
- the part of the system in the open area includes a terminal for consulting the maintenance documentation, hereinafter referred to as information terminal.
- This terminal may for example take the form of a laptop computer, 190, or an electronic slate (Tablet PC TM), 195.
- the maintenance documentation is housed either directly in the laptop 190 or the electronic slate 195 , if its memory size is sufficiently low, either in an embedded server 170, otherwise.
- the laptop or electronic slate can be connected via a wireless link to the wired network via an AP access point. If the access point is connected to the avionic part of the network, this connection is made by means of a unidirectional link 181, as shown in the figure.
- Frame switches denoted SW allow routing on the various links of the network.
- a common input / output interface 155 (keyboard, screen and, where appropriate, mouse) is shared between the computer 110 hosting the diagnostic module and the computer 191 hosting the maintenance documentation.
- the inputs / outputs of these computers are connected through the KVM (Keyboard Video Mouse) switch 185, to this common input / output interface, said switch to switch, manually or automatically, between the two computers.
- KVM Keyboard Video Mouse
- the maintenance operator can easily switch from the diagnostic screen to the documentation screen, as will be seen below. In case of failure, the system
- CMS is notified either directly by a message transmitted by the flight alarm system or FWS (Flight Warning System), or by a note of the driver recorded as entry in the logbook 120, or by both jointly .
- the CMS system can correlate different failures to look for the likely common cause (s). In all cases, the CMS system provides a probable fault identification code, associated with one or more replaceable equipment (s) or LRUs (Line Replaceable ⁇ nits).
- the diagnostic module, 115 receives a fault identification code and retrieves the diagnostics tree corresponding to this code.
- the module 115 is adapted to traverse this diagnostic tree according to the indications provided by the maintenance operator and / or the test modules integrated in the equipment to be tested.
- the diagnostic tree generally comprises a first part relating to the confirmation of the failure and a second part, relating to the actual resolution, in case the failure is actually confirmed.
- Each node of the diagnostic tree includes a task or a sequence of tasks to be performed, the result of which determines the choice of the next node.
- Each node of the diagnostics tree corresponds to a page of the maintenance documentation intended to be displayed on the information terminal 190 or 195.
- the path of the diagnosis tree induces simultaneously and automatically a navigation through the pages of the the documentation associated with the traversed nodes. More specifically, each time a node is visited by the diagnostic module, a hyperlink is transmitted by the terminal OMT to said terminal.
- the latter includes a navigation module that synchronizes automatically by searching for the URL pointed to by the hyperlink.
- the corresponding page can be retrieved locally in the information terminal if the documentation is stored there or if said page is available in the cache memory, or in the embedded server 170. Alternatively, the documentation page can be retrieved from a server on the ground.
- the maintenance operator is thus routinely guided through the diagnostic procedure while being able to consult the maintenance documentation for each step of the procedure.
- Storing maintenance documentation in the open area facilitates update operations.
- the latter can be performed for example by means of a data downloading method complying with the ARINC 615 protocol or simply by replacing a memory medium.
- the update usually leaves the diagnostic tree unchanged, which ensures the integrity of the maintenance system.
- the diagnostics tree can be extracted from the existing maintenance documentation, ie the aforementioned AMM and TSM manuals. More precisely, the diagnostic tree corresponds to the tree structure of the TSM manual.
- a step in the fault repair procedure corresponding to a tree node in the TSM manual, requires the completion of certain maintenance tasks in the AMM manual. In this case the tree constituting these tasks is grafted locally to the aforementioned node.
- the set of tree nodes in the TSM manual to which the trees of the maintenance tasks related to these nodes are thus grafted forms the diagnostic tree.
- the diagnostic tree will be obtained by removing the visual representation elements, for example layout elements, images, three-dimensional schemas , animation scripts. These elements are rejected in the documentation section. However, all the functional elements will be kept in the diagnostic tree, including hyperlinks to launch test applications, download software for a device, activate or deactivate a circuit breaker, etc.
- a diagnostic tree is obtained and on the other hand a purely documentary file, both being, for example, in XML or SGML format but having distinct DTDs.
- a hyperlink to a page of the document file.
- the diagnostic tree and the document file can also be developed in parallel, provided that they respect their
- Fig. 3 illustrates an example of operation of the maintenance computer system according to the invention.
- a fault identification code is transmitted to the diagnostic module, for example from a logbook setpoint.
- the diagnostics module searches for the diagnostics tree (indicated here by "Task N") corresponding to this code. This tree is divided into two parts noted (I) and (II) respectively corresponding to the procedure of confirmation of failure and the procedure of resolution of failure.
- the presentation of the maintenance documentation is synchronized as each node of the tree passes. For example, when the diagnostic module goes through node 5, the documentation page relating to sub-task 5 is displayed on the information terminal. It should be noted, however, that switching from one node to the next does not necessarily require a change of the page to be displayed.
- the maintenance operator can navigate freely through the documentation through hyperlinks. For example, the operator can click on the hyperlink "subtask 5- 2" to see the page related to this subtask. However, as soon as the diagnostic module passes to the next node (in this case node 8), the documentation page for this last node ("subtask 8") will automatically appear on the terminal screen. information.
- the fault is resolved or the fault remains and the corresponding mention is recorded in the logbook.
- the defective equipment is listed and compared with the contents of the Minimum Equipment List (MEL). This list, contrary to what its name indicates, gives the list of equipment whose operation is optional for the operation of the device. Thus, if equipment diagnosed as defective is not on the list, the flight must be canceled. On the other hand, if a device diagnosed as defective is in the MEL list, the system determines the constraints imposed by the malfunction of the equipment and the associated cost in terms of functional performance losses or safety margins.
- MEL Minimum Equipment List
- the malfunction of an equipment may impose a constraint on the amount of fuel that the aircraft will be able to embark, which will in turn result in a limit of its range of action.
- the aforementioned costs are stored in a file hosted in the avionics area.
- the computer system comprises a third software module, hosted in the avionic zone, for example in the diagnostic terminal, allowing the pilot or the maintenance operator to browse the MEL list and select any equipment from this list.
- the computer system also comprises a fourth software module, hosted in the open zone, for example in the information terminal, responsible for displaying the documentation relating to the elements of the MEL list.
- This documentation is housed in the open area, for example by the information terminal or the embedded server 170. Alternatively, this documentation may be hosted by a server on the ground.
- the MEL list is, meanwhile, hosted in the avionics area, for example in the diagnostic terminal.
- an element of the MEL list When an element of the MEL list is selected by means of the third software module, it transmits via the network to the fourth module a hyperlink pointing to a URL giving the documentation page relating to this element.
- the fourth software module retrieves this page and displays it on the information terminal screen. In this way, the path of the elements of the MEL list automatically and synchronously induces a presentation of the corresponding documentation pages by the information terminal.
- FIG. 4 gives an example of a diagnostics tree used by the diagnostic module 115, corresponding to a determined fault code, noted here TSM 31-50-810-982-A, corresponding to a failure of the software of a system of diagnosis.
- flight alarm FWS 2 Flight Warning System
- the part of the tree relating to the confirmation procedure and the part relating to the isolation procedure are separated by a horizontal dashed line.
- FIGS. 5A to 5G show the contents of the screens of the OMT terminal and the information terminal for an example of a path of the diagnostics shaft shown in FIG. 4.
- the root 410 of the diagnostics tree 400 is associated with a documentation page shown in the left-hand part of FIG. 5A. This page shows the main steps of the procedure for confirming and isolating the fault.
- the diagnostic module tests the failure indicated in the logbook. In this case, the status of the fault is confirmed (node 421) and therefore the diagnostic module proceeds to node 441.
- the node 441 is associated with the execution of an integrated test program (BITE) of a unit (LRU) of the FWS system called CPIOM-C2 (Core Processing Input / Output Module).
- BITE integrated test program
- CPIOM-C2 Core Processing Input / Output Module
- the screen of the terminal OMT indicates the degree of completion of the test program, and the information screen the details of the corresponding procedure.
- the program returns an error code as indicated on the screen of the OMT terminal in FIG. 5C.
- the failure of the CPIOM-C2 unit is therefore isolated (node 441 of the diagnostics tree).
- Node 451 corresponds to a procedure for replacing the CPIOM-C2 unit, as illustrated in FIG.
- the information terminal screen indicates the detail.
- the circuit breaker of the CPI0M-C2 power supply circuit is activated, that is, its power supply is cut off, and then in a second step (see Fig. 5E) a new unit is installed.
- the diagnostics module tests the FWS again, that is, returns to root 410 of the diagnostics tree.
- the test of the system proves this time satisfactory (absence of error code), as indicated in FIG. 4G.
- the documentation page is of course the same as that displayed during the first pass in the diagnostic tree.
- the maintenance operator therefore concludes that the fault has been repaired and bears the corresponding mention in the logbook.
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Human Computer Interaction (AREA)
- Debugging And Monitoring (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR0755789A FR2917521B1 (fr) | 2007-06-15 | 2007-06-15 | Systeme informatique de maintenance d'un aeronef |
PCT/EP2008/056970 WO2008155227A1 (fr) | 2007-06-15 | 2008-06-05 | Système informatique de maintenance d'un aéronef |
Publications (1)
Publication Number | Publication Date |
---|---|
EP2158525A1 true EP2158525A1 (fr) | 2010-03-03 |
Family
ID=38963227
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP08760549A Withdrawn EP2158525A1 (fr) | 2007-06-15 | 2008-06-05 | Système informatique de maintenance d'un aéronef |
Country Status (9)
Country | Link |
---|---|
US (1) | US8433475B2 (ja) |
EP (1) | EP2158525A1 (ja) |
JP (1) | JP5336477B2 (ja) |
CN (1) | CN101681160B (ja) |
BR (1) | BRPI0813340A2 (ja) |
CA (1) | CA2700933A1 (ja) |
FR (1) | FR2917521B1 (ja) |
RU (1) | RU2486566C2 (ja) |
WO (1) | WO2008155227A1 (ja) |
Families Citing this family (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8341298B2 (en) | 2005-12-02 | 2012-12-25 | The Boeing Company | Scalable on-board open data network architecture |
US9719799B2 (en) * | 2008-12-12 | 2017-08-01 | Honeywell International Inc. | Next generation electronic flight bag |
RU2488894C2 (ru) | 2009-04-13 | 2013-07-27 | Шарп Кабусики Кайся | Устройство отображения, жидкокристаллическое устройство отображения, способ возбуждения для устройства отображения и телевизионный приемник |
FR2950176B1 (fr) * | 2009-09-11 | 2012-12-14 | Airbus Operations Sas | Procede et dispositif d'acces a la documentation et performance d'un aeronef selon des alarmes generees dans ce dernier |
US20110179390A1 (en) * | 2010-01-18 | 2011-07-21 | Robert Paul Morris | Methods, systems, and computer program products for traversing nodes in path on a display device |
GB2492328A (en) * | 2011-06-24 | 2013-01-02 | Ge Aviat Systems Ltd | Updating troubleshooting procedures for aircraft maintenance |
FR2981446B1 (fr) * | 2011-10-14 | 2013-11-15 | Thales Sa | Procede de reinitialisation rapide pour dispositif de visualisation de planche de bord |
US9571181B2 (en) | 2012-03-01 | 2017-02-14 | Honeywell International Inc. | Programmable portable electronic device for airborne operational communications |
FR2989500B1 (fr) * | 2012-04-12 | 2014-05-23 | Airbus Operations Sas | Procede, dispositifs et programme d'ordinateur d'aide a l'analyse de la tolerance aux pannes d'un systeme d'un aeronef, utilisant des graphes d'evenements redoutes |
CN103455161A (zh) * | 2012-06-01 | 2013-12-18 | 南京神易网络科技有限公司 | 一种安全kvm切换器 |
US9334063B2 (en) * | 2012-09-10 | 2016-05-10 | Rosemount Aerospace, Inc. | Aircraft avionics tablet interface module |
US9563580B2 (en) | 2013-07-25 | 2017-02-07 | North Flight Data Systems, LLC | System, methodology, and process for wireless transmission of sensor data onboard an aircraft to a portable electronic device |
US9260182B2 (en) | 2013-10-30 | 2016-02-16 | Westjet Airlines Ltd. | Integrated communication and application system for aircraft |
EP3108615B1 (en) | 2014-02-21 | 2019-01-02 | Astronautics Corporation Of America | System for communicating avionics information through portable electronic devices |
US10375087B2 (en) * | 2014-07-21 | 2019-08-06 | Honeywell International Inc. | Security architecture for the connected aircraft |
FR3026882B1 (fr) * | 2014-10-02 | 2016-11-04 | Snecma | Procede de determination d'au moins un equipement defaillant d'un aeronef et systeme correspondant |
CN104318491B (zh) * | 2014-10-27 | 2017-05-10 | 国家电网公司 | 多源互联配电网检修防误操作验算方法 |
US9550583B2 (en) | 2015-03-03 | 2017-01-24 | Honeywell International Inc. | Aircraft LRU data collection and reliability prediction |
US9590718B1 (en) | 2015-09-22 | 2017-03-07 | Honeywell International Inc. | End-to-end wireless connectivity between vehicle and remote server using wireless radios of two mobile devices |
US10191479B2 (en) | 2015-09-29 | 2019-01-29 | General Electric Company | Methods and systems for network-based detection of component wear |
FR3047340B1 (fr) * | 2016-02-02 | 2019-10-18 | Dassault Aviation | Systeme d'aide a la decision d'autorisation a partir d'un aeronef, et procede associe |
FR3049415B1 (fr) * | 2016-03-25 | 2018-04-20 | Sagem Defense Securite | Procede de gestion et de maintenance d’un aeronef comportant une zone de haut degre de securite |
FR3050351B1 (fr) * | 2016-04-15 | 2018-05-11 | Thales | Procede de controle d'integrite de l'avionique d'un aeronef, dispositif et produit programme d'ordinateur associes |
US10067817B2 (en) | 2016-05-25 | 2018-09-04 | International Business Machines Corporation | Equipment failure risk detection and prediction in industrial process |
US11210434B2 (en) * | 2017-10-17 | 2021-12-28 | Textron Innovations Inc. | Fault isolation |
CN111504341B (zh) * | 2020-04-30 | 2023-09-19 | 中国直升机设计研究所 | 一种直升机飞行状态识别方法 |
CN111698288B (zh) * | 2020-05-11 | 2023-04-07 | 北京空间技术研制试验中心 | 一种基于以太网面向无连接的星上软件在轨维护方法 |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6115656A (en) * | 1997-06-17 | 2000-09-05 | Mcdonnell Douglas Corporation | Fault recording and reporting method |
US6208955B1 (en) * | 1998-06-12 | 2001-03-27 | Rockwell Science Center, Llc | Distributed maintenance system based on causal networks |
RU2163745C2 (ru) * | 1999-04-29 | 2001-02-27 | Щеглов Андрей Юрьевич | Система защиты виртуального канала корпоративной сети с аутентифицирующим маршрутизатором, построенной на каналах и средствах коммутации сети связи общего пользования |
TW498228B (en) * | 1999-11-24 | 2002-08-11 | Elegent Technologies Inc | Self-contained network browser with diagnostic abilities |
US6574537B2 (en) * | 2001-02-05 | 2003-06-03 | The Boeing Company | Diagnostic system and method |
RU2181334C1 (ru) * | 2001-06-08 | 2002-04-20 | Владимиров Игорь Михайлович | Способ оценки технического состояния агрегатов несущей системы вертолета для продления ресурса |
FR2838585B1 (fr) * | 2002-04-15 | 2004-12-10 | Airbus France | Procede et dispositif de transmission de donnees sur un aeronef |
FI113121B (fi) * | 2002-05-30 | 2004-02-27 | Metso Automation Oy | Järjestelmä, tietoliikenneverkko ja menetelmä tietojen lähettämiseksi |
US8510083B2 (en) * | 2003-07-31 | 2013-08-13 | The Boeing Company | Method, apparatus and computer program product for constructing a diagnostic network model |
US7149612B2 (en) * | 2004-01-05 | 2006-12-12 | Arinc Incorporated | System and method for monitoring and reporting aircraft quick access recorder data |
US7167788B2 (en) * | 2004-01-30 | 2007-01-23 | United Technologies Corporation | Dual-architecture microserver card |
RU2276466C1 (ru) * | 2004-11-10 | 2006-05-10 | Общество с ограниченной ответственностью Фирма "Анкад" | Способ создания защищенных виртуальных сетей |
US7668632B2 (en) * | 2004-11-22 | 2010-02-23 | The Boeing Company | System, method and computer program product for real-time event identification and course of action interpretation |
US7788002B2 (en) * | 2005-08-08 | 2010-08-31 | The Boeing Company | Fault data management |
US7756145B2 (en) * | 2005-12-02 | 2010-07-13 | The Boeing Company | Methods and apparatus providing an airborne e-enabled architecture as a system of systems |
US8341298B2 (en) * | 2005-12-02 | 2012-12-25 | The Boeing Company | Scalable on-board open data network architecture |
US7983809B2 (en) * | 2007-12-21 | 2011-07-19 | Sikorsky Aircraft Corporation | Aircraft integrated support system (ISS) |
US8306685B2 (en) * | 2008-04-17 | 2012-11-06 | The Boeing Company | Electronic logbook flight preparation system and method |
US9719799B2 (en) * | 2008-12-12 | 2017-08-01 | Honeywell International Inc. | Next generation electronic flight bag |
FR2949161B1 (fr) * | 2009-08-14 | 2011-09-09 | Thales Sa | Dispositif pour le diagnostic de systeme |
-
2007
- 2007-06-15 FR FR0755789A patent/FR2917521B1/fr not_active Expired - Fee Related
-
2008
- 2008-06-05 JP JP2010511584A patent/JP5336477B2/ja not_active Expired - Fee Related
- 2008-06-05 RU RU2010101065/08A patent/RU2486566C2/ru not_active IP Right Cessation
- 2008-06-05 WO PCT/EP2008/056970 patent/WO2008155227A1/fr active Application Filing
- 2008-06-05 CA CA2700933A patent/CA2700933A1/fr not_active Abandoned
- 2008-06-05 EP EP08760549A patent/EP2158525A1/fr not_active Withdrawn
- 2008-06-05 CN CN2008800200621A patent/CN101681160B/zh not_active Expired - Fee Related
- 2008-06-05 US US12/663,351 patent/US8433475B2/en not_active Expired - Fee Related
- 2008-06-05 BR BRPI0813340-9A2A patent/BRPI0813340A2/pt not_active IP Right Cessation
Non-Patent Citations (1)
Title |
---|
See references of WO2008155227A1 * |
Also Published As
Publication number | Publication date |
---|---|
WO2008155227A1 (fr) | 2008-12-24 |
US8433475B2 (en) | 2013-04-30 |
RU2010101065A (ru) | 2011-07-20 |
CA2700933A1 (fr) | 2008-12-24 |
US20100198431A1 (en) | 2010-08-05 |
FR2917521B1 (fr) | 2009-10-02 |
CN101681160A (zh) | 2010-03-24 |
JP2010529921A (ja) | 2010-09-02 |
BRPI0813340A2 (pt) | 2014-12-23 |
JP5336477B2 (ja) | 2013-11-06 |
FR2917521A1 (fr) | 2008-12-19 |
RU2486566C2 (ru) | 2013-06-27 |
CN101681160B (zh) | 2013-08-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2158525A1 (fr) | Système informatique de maintenance d'un aéronef | |
EP1846824B1 (fr) | Systeme et procede de traitements embarques d'essais en vol | |
CA2193540C (fr) | Dispositif de surveillance d'un systeme complexe, notamment d'un aeronef | |
CN104158910B (zh) | 一种云端Web应用自动化部署*** | |
US20100152962A1 (en) | System and Method for Performing Real-Time Data Analysis | |
FR2915292A1 (fr) | Procede et systeme de modification d'un contenu d'un message d'alerte a bord d'un aeronef. | |
WO2016034824A1 (fr) | Architecture bi-voies avec liaisons ccdl redondantes | |
FR2953954A1 (fr) | Dispositif d'elaboration des alertes d'un systeme d'aeronef | |
WO2007036462A1 (fr) | Procede et systeme de diagnostic des pannes pour aerodynes | |
EP2975363B1 (fr) | Traitement des messages d'alarmes et de maintenance d'un aeronef | |
BR102012015582A2 (pt) | Sistema, método e produto de programa de computador | |
CN101651669A (zh) | 业务箱集成服务器和业务箱集成方法 | |
EP2874106A1 (fr) | Système et procédé de diagnostic de panne aéronef | |
FR2978264A1 (fr) | Un procede de rechargement automatique de logiciel et un dispositif de rechargement automatique de logiciel | |
FR2950177A1 (fr) | Procede et dispositif de gestion d'informations dans un aeronef | |
FR3007000A1 (fr) | Systeme de surveillance d'une plateforme avionique a architecture trois tiers | |
FR2947650A1 (fr) | Procede et systeme de generation de documentation electronique pour la maintenance | |
FR2938675A1 (fr) | Dispositif permettant l'amelioration des procedures de maintenance d'equipements embarques | |
EP2629201A1 (fr) | Procédé et système de détection d'anomalies à solutionner dans un aéronef | |
FR3001065A1 (fr) | Dispositif centralise pour la gestion automatique de la configuration et de la reconfiguration de systemes multiples d'un aeronef. | |
WO2007036452A1 (fr) | Procede et systeme de validation des defaillances pour aerodynes | |
CN112882892B (zh) | 数据处理方法和装置、电子设备及存储介质 | |
FR3047340B1 (fr) | Systeme d'aide a la decision d'autorisation a partir d'un aeronef, et procede associe | |
FR3062846A1 (fr) | Passerelle de controle entre un composant avionique et un dispositif mobile | |
FR2999318A1 (fr) | Procede d'evaluation de la surete de fonctionnement d'un systeme complexe |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20091214 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL BA MK RS |
|
DAX | Request for extension of the european patent (deleted) | ||
17Q | First examination report despatched |
Effective date: 20110810 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20180103 |