An assistance system for the implementation of aircraft procedures comprising a chain of operations to carry out is provided. The system includes a procedure database receiving the specifications of a plurality of procedures to be performed and a display and/or validation module which is able to collect the specifications of the procedure, to display a piece of characteristic information at least one operation of the procedure on the basis of the collected specifications, and/or to receive validation of the performance of at least one operation of the procedure. The system includes a conflict determination module which is able to generate for at least one operation of the procedure, feasibility information for the operation of the procedure during the course of the procedure, depending on the current operating states of the functional systems of the aircraft.
|
1. An assistance system for implementation of aircraft procedures comprising a chain of operations to be performed, the system comprising:
a procedure database hosting specifications of a plurality of procedures to be performed depending on given operating states of functional systems of the aircraft;
a displayer and/or validator configured to collect the specifications of a procedure from the procedure database and to display at least a piece of information which is characteristic of at least one operation of the procedure based on the collected specifications, and/or to receive a validation of performance of at least one operation of the procedure;
a conflict determiner configured to generate, for at least one operation of the procedure, a piece of feasibility information of the operation of the procedure during course of the procedure, based on current operating states of the functional systems of the aircraft, the conflict determiner being configured to transmit the generated piece of feasibility information to the displayer and/or validator.
2. The system as recited in
3. The system as recited in
4. The system as recited in
5. The system as recited in
6. The system as recited in
7. The system as recited in
8. The system as recited in
9. The system as recited in
10. The system as recited in
11. The system as recited in
12. The system as recited in
13. The system as recited in
14. The system as recited in
15. The system as recited in
16. An assistance method during a given aircraft procedure comprising a chain of operations to be performed, the method comprising:
enabling the system as recited in
displaying by the displayer and/or validator of at least one piece of characteristic information of at least one operation of the procedure on the basis of the collected specifications;
generating for at least one operation of the procedure, a piece of feasibility information for the operation of the procedure during the course of the procedure by the conflict determiner, based on information which is representative of the current operating states of the functional systems of the aircraft; and
transmitting the generated piece of feasibility information to the displayer and/or validator.
17. The method as recited in
automatically generating by the automatic executer a command to perform at least one operation to be performed of the procedure;
transmitting by the conflict determiner the command to perform generated by the automatic executer when the generated piece of feasibility information is a piece of compatibility information; and
blocking by the conflict determiner the command of the operation to be performed when the generated piece of feasibility information is a piece of conflict information.
|
|||||||||||||||||||||||||
The present invention relates to an assistance system for the implementation of aircraft procedures comprising a chain of operations, the system including:
Such a system is intended for use in a cockpit of an aircraft, in order to lighten the workload of the crew during the performance of the procedures required during the movement of the aircraft. In some cases, the system may overcome the lack of a crew member. On the ground, it may also be implemented by a maintenance operator from the cockpit or remotely from the aircraft.
The procedures are, for example, procedures to be carried out before a flight, to check proper operation of the various systems of the aircraft, navigation procedures to be implemented during flight, for example when changing a flight phase, or malfunction procedures to be implemented in the event of failures of one or more pieces of aircraft equipment.
Generally each procedure involves a series of operations defined by the manufacturer and/or the operator, and which are generally validated by certification authorities. These procedures are linked in the form of lists.
The operations are, for example, actions to be performed, such as commands intended for an airplane system, with acknowledgement of their application, questions to the crew requiring a simple response, or requests for crew actions. Other operations are purely for information, such as sending messages and/or information to the crew without a response being expected.
When a procedure is implemented during flight, the crew performs the actions required by actuating the controls positioned in the cockpit, either directly by means of switches or through computers and software controlled by the crew.
In traditional flight with a crew of two, the first member of the crew takes care of the short-term flight and a second crew member successively performs the various actions of the procedure under the control of the first crew member for major or irreversible actions, such as an engine failure, extinction of a fire . . . .
The procedures are generally listed in one or more aircraft operating manuals which are available in paper form or electronically. A large number of procedures are certified and must be strictly applied by the crew, especially in the event of malfunctions.
On modern aircraft, the procedures are stored as computer files in a database and may be displayed on a screen in the cockpit when they have to be implemented.
Generally, the operations of the procedure are successively displayed by a display and validation module, wherein the crew must validate the actions as they are gradually performed.
In some cases, especially in the event of multiple malfunctions on the aircraft, several different procedures must be implemented one after the other.
Generally, the crew determines the order of performing of the procedures by determining which are the most critical. Then, the crew successively executes the various procedures to be implemented by carrying out the provided actions of each procedure one by one.
Furthermore, for safety reasons, particularly in the context of multiple malfunctions, the crew must continually analyze whether the action to be performed of a specific procedure is appropriate with respect to the current operational state of the aircraft. In particular, if the action to be performed might result in a change of state of a piece of equipment of the aircraft, this change of state might affect the appropriate flying of the aircraft, or even the safety of the flight depending on the elements affected by other procedures or by other malfunctions.
By the term <<change of state>> of a piece of equipment, is meant the change from a state of power on to a state of power off or vice versa, the change from an operational state to a state of malfunction, the change of an equipment control mode, or even any change in the positioning of a piece of equipment to a state which is distinctly different from the previous state (e.g. a slat or flap position, or raising/lowering the landing gear).
The crew workload is thus very high, insofar that the crew has to keep the aircraft in flight while carrying out a large number of actions relating to procedures, determining the preferential order for performing the procedures, and the impact of each action of a procedure on the course of the flight.
An object of the invention is thus to provide an assistance system for the implementation of aircraft procedures comprising a chain of operations to be performed, wherein the system simplifies the work of the crew and reduces their workload, while ensuring the safety of the flight.
To this end, the invention provides a system of the aforementioned type, characterized in that the system includes a conflict determination module which is able to generate, for at least one operation of the procedure, a piece of feasibility information of the operation of the procedure during the course of the procedure, on the basis of current operating states of the functional systems of the aircraft, the conflict determination module being able to transmit the determined piece of feasibility information to the display and/or validation module.
The system according to the invention may comprise one or more of the following features individually or in any technically possible combination:
The invention also provides an assistance method during at least one given aircraft procedure comprising a chain of operations to be performed, the method comprising the following steps:
The method of the invention may comprise one or more of the following features individually or in any technically possible combination:
the system comprises an automatic execution module of at least one operation of the procedure,
the method comprising the following steps:
The invention will be better understood on reading the description which follows and which is given by way of example with reference to the appended drawings, wherein:
A first system 10 for assisting the crew of an aircraft 12 according to an embodiment of the invention is schematically illustrated in
The system 10 is intended to help the crew implement procedures including a chain of operations to be performed, relating to functional systems 14 of the aircraft 12.
The functional systems 14 comprise, for example, one or more hydraulic systems 16, one or more electrical systems 18, and one or more propellant systems 20 of the aircraft 12 and/or one or more conditioning systems 22 of the cabin. This list may be extended to cover all the controlled systems of the aircraft.
Each functional system 14 includes equipment and components able to perform hydraulic, electrical, propulsion, or conditioning functions of the aircraft 12.
Conventionally an aircraft 12 includes a cockpit 24 occupied by the crew 12 of the aircraft. The cockpit 24 includes at least one panel provided with physical control elements or a control screen 26 for the functional systems 14 of the aircraft 12, which is able to implement controls of the functional systems 14 through physical switches or pieces of software operated by the crew, or through computers and pieces of software controlled by the crew.
A procedure consists of a chain of operations intended to be carried out depending on given operating states of the functional systems 14 of the aircraft 12.
Each procedure is, for example, implemented on the occurrence of a particular operational phase of the aircraft, such as taxiing, takeoff, passing through a given altitude, transition to cruise.
Other procedures are implemented on the occurrence of a malfunction or failure of a functional system 14 of the aircraft 12.
In this case, the procedure generally corresponds to a configuration or reconfiguration of one or more pieces of equipment of one or more functional systems 14 of the aircraft 12, by carrying out operations or a sequence of operations, according to the observed operating states of the functional systems 14.
The operations to be carried out advantageously comprise actions to perform such as an analysis of a state of a piece of equipment, a command intended for an aircraft system with confirmation of the execution of the command, a question to the crew, a request for crew action, monitoring of the actions of the crew, a selection from among several possible sequences of operations, acknowledgement of a piece of information by the user. Some operations of the procedure are informative for the crew without acknowledgement such as an informative display to the crew, for example the sending of an informative message to the crew or the display of one or more parameters relating to the procedure.
A command is able to be transmitted to an aircraft system. Examples of commands are the opening or closing of a valve, the control of electric switches . . . .
A command is generally followed in the procedure by a verification of its application.
A question to the crew is generally followed by awaiting a simple answer, for example, <<yes>> or <<no>>
A request for crew action is generally followed by awaiting action, which is determined by the effects of the action through sensors in the functional systems 14.
Monitoring a pilot action is sometimes followed by a confirmation when this action is likely to have significant consequences on the continuation of the flight.
The selection from among several possible sequences of operations is determined depending on value of representative information of operating states of the functional systems 14, for example, the state of a valve, the electrical voltages observed, or else the presence of a malfunction message.
The selection is expressed in the transition to a series of operations selected from among several possible sequences of operations provided in the procedure, depending on the current operating states of the aircraft, i.e. the operating states having just been measured.
A simple display to the crew is informative. It is not generally followed by any action.
Procedures are generally specified by detailing the sequential list of operations to be performed in the procedure. As previously mentioned, the procedure may comprise bifurcations, to allow different sequences of operations to be followed depending on current operating states of the functional systems 14, or on answers of the crew to questions posed through a displayer and/or validator in the form of a display and validation module 32.
The assistance system 10 according to an embodiment of the invention is implemented on one or more computers comprising at least a processor and a memory hosting the databases, as well as specific software modules able to be performed by the processor.
Referring to
The system 10 further includes data acquirer in the form of a module 33 for acquiring representative information of current operating states, and a procedure monitor in the form of a monitoring module 34 able to determine the procedures associated with the current operating states and/or follow the course of procedures implemented, depending on the current operating states.
The system 10 also includes an automatic executer in the form of a module 36 for automatic execution of at least part of the operations of the procedure, and a conflict determiner in the form of a conflict determination and safety module 38 able to generate, for each successive operation of the procedure, a piece of feasibility information of the operation of the procedure in the current operating states of the functional systems 14 of the aircraft 12.
The procedure database 30 comprises the description of the procedures in the form of characteristics of each of the operations which it contains, and the sequential order for performing such operations.
It further comprises, for procedures including a plurality of alternative sequences of operations, a definition of the operating states conditioning the passage to one or other of the sequences of operations.
The procedure database 30 further comprises a priority table allowing the definition of an order for performing the procedures when several procedures are to be performed simultaneously, depending on observed operating states of the functional systems 14 of the aircraft 12.
For example, the table comprises a list of possible sets of operating states likely to be observed, and for each set of operating states which may be observed, a list of associated procedures to be performed for this set of operating states. In addition, the table includes, for each procedure in the list of associated procedures, an indicator of the order for performing the procedures for all the procedures to be performed.
The display and validation module 32 is able to collect the specifications of a procedure given in the procedure database 30, to successively display a piece of information characteristic of each operation of the procedure obtained from the collected specifications on at least a control panel screen 26, and to receive, if necessary, an execution validation of the operation of the procedure by the crew or the automatic execution module 36.
The characteristic piece of information comprises, for example, a description of the operation to be performed, for example, an action to be performed, possibly accompanied by an indication of the degree of completion of the operation. Alternatively, the characteristic piece of information may comprise a warning message or a measured parameter, when the operation having taken place is purely informative.
Advantageously, the characteristic piece of information of a subsequent operation in the course of a procedure is only displayed when the execution validation of the previous operation in the procedure has been performed. Alternatively, the characteristic piece of information of a plurality of operations of the procedure to be performed are displayed simultaneously, and the display of each operation is changed depending on the state of performance of the operation.
The data acquisition module 33 is able to measure information which is representative of the current operating states of the various systems or functional equipment 14 of the aircraft, and to provide this information of operating states to the monitoring module 34, to the automatic execution module 36 and to the conflict determination module 38.
This representative information is, for example, sensor data available on the equipment and components of the functional systems. The data are representative of physical parameters such as temperature, position and/or equipment configurations such as the switching state of a valve, the voltage on a power grid, or a declared state of equipment malfunction.
Conventionally, the data acquisition module 33 is able to obtain data from redundant sensors, and to operate in a multi-instantiated manner, with outputs polled to guarantee data reliability.
The monitoring module 34 is able to receive continuous data from the data acquisition module 33, which are representative of the current operating states of the various functional systems of the aircraft 14.
It is able to query the priority table of the procedure database 30, in order to determine whether the current operating states correspond to a set of possible operating states in the list of sets of possible operating states, to extract the procedure(s) associated with these possible operating states and, where appropriate, the order for performing the associated procedures.
The monitoring module 34 is thus able to establish and transmit to the display and validation module 32 the list of the procedure(s) to be launched when current operating states are measured by the module 33, and to provide the crew, where appropriate, with the preferential order for performing the procedures, depending on the data available in the priority table of the procedure database 30.
The monitoring module 34 is further able to enable the automatic execution module 36, on the basis of acknowledgement of consent by the crew received from the control panel 26, so as to successively perform the operations of each procedure in the list of procedures to be launched.
The monitoring module 34 is able to transmit information on the ongoing procedure to the conflict determination module 38.
For each procedure performed, the automatic execution module 36 is able to load into the database 30, the list of the operations of the procedure to be performed and to receive data from the data acquisition module 33 in order to determine the current operating states of the various functional systems 14 of the aircraft 12.
The automatic execution module 36 is able to automatically determine the commands to be performed depending on the current operating states from the data acquisition module 33.
It is able to send, via the conflict determination module 38, the commands to be performed on the functional systems 14, and optionally measure the effects of commands sent on the observed operating states.
The automatic execution module 36 is able to switch from an already performed operation to the next operation to be performed in the procedure depending on the observed operating conditions and on optional intervention by the crew following a question or an override.
For certain operations, predefined as <<without validation>> in the procedure, the automatic execution module 36 is able to send commands to the functional systems 14 via the conflict determination module 38 without validation by the crew.
For other operations, predefined as <<with validation>> in the procedure, the conflict determination module 38, is able to query the crew via the monitoring module 34 in order to obtain an order for performing the operation, and then, once the order for performing the operation is obtained, to send commands to the functional systems 14.
The automatic execution module 36 may be disabled from the control panel 26 by the crew at any time in order to prevent the automatic execution of a command by the automatic execution module 36 or, conversely, to force the performance of an operation specifically blocked by the conflict determination module 38.
When the procedure comprises alternative sequences of operations, the automatic execution module 36 is able to compare the current operating states coming from the data acquisition module 33 against predefined operating states for each of the following alternative operations in the procedure database 30 in order to determine the specific sequence of operations to be performed with the current operating states from among all possible sequences of operations.
The automatic execution module 36 is possibly able to query the crew in order to obtain a validation of the sequence of alternative operations selected depending on the current operating states.
The conflict determination module 38 is able to generate, for each successive performance of an ongoing procedure, a piece of feasibility information for the operation to be performed in the procedure depending on the current operating states of the functional systems 14 of the aircraft 12, and for the completion of the ongoing procedure provided by the module 34. The module 38 is then able to transmit the determined piece of feasibility information to the display and validation module 32 and, advantageously, to the monitoring module 34 and the automatic execution module 36 and, if necessary, to block the command transmitted by the automatic execution module 36.
The piece of feasibility information is either a piece of compatibility information, giving the possibility of performing the operation of the procedure, or a piece of conflict information capable of blocking the performance of the operation of the procedure.
If the piece of feasibility information is a piece of compatibility information, the conflict determination module 38 is able to transmit the command from the automatic execution module 36 to the systems 14 of the aircraft, with or without validation by the pilot.
An operation may be regarded as generating conflict if it involves, for example, non-compliance with a safety requirement with respect to the operation of the aircraft 12 or non-compliance with a constraint related to the mission such as, for example, a comfort criterion, a restriction on the usage of the aircraft 12 in order to limit damage or the following of a flight plan.
To this end, the conflict determination module 38 includes a conflict identification database 50.
The conflict identification database 50 includes at least one incompatibility table defining a list of conflicting operations in the presence of a set of predefined operating states of the functional systems 14 of the aircraft 12.
For example, the incompatibility table includes a list of possible sets of operating conditions, likely to be observed and for each set of possible operating states, an associated list of incompatible conflicting operations for this set of operating states.
Advantageously, the list of conflicting operations comprises at least one operation causing a change of state of a first piece of aircraft equipment which is incompatible with the current operating and/or malfunctioning states of at least one second piece of equipment redundant with said first piece of equipment.
For example, in the case of a twin-engine aircraft, a stop command operation of the second engine of the aircraft 12 is identified as a conflicting operation when the observed operating states indicate a malfunction and/or the stopping of the first engine of the aircraft. Similarly, the shutting down of a pump supplying a hydraulic network is identified as a conflicting operation when another hydraulic network is already shut down.
For each operation to be performed in a procedure, the conflict determination module 38 is thus able to receive representative information of the current operating states, coming from the data acquisition module 33, and to identify the conflicting operations corresponding to the observed operating states from the incompatibility table of the conflict identification database 50.
The conflict determination module 38 is able to generate the piece of feasibility information of the operation of the procedure during the course of the procedure, based on current operating states of the functional systems 14 of the aircraft 12.
This piece of feasibility information is a piece of conflict information if the operation to be performed in the procedure is a conflicting operation in the current operating states. However, the piece of feasibility information is a piece of compatibility information if the operation to be performed in the procedure is not a conflicting operation in the current operating states.
When a piece of conflict information is transmitted to the display and validation module 32, the module 32 is able to warn the crew, for example by identifying on the display of the control panel 26, that the operation to be performed is conflicting by a specific marking.
This particular display consists, for example, of displaying the conflicting operation to be performed differently from a compatible operation to be performed, for example with a different colour, and/or a special background band, and/or with a display effect, such as a flashing display. Alternatively or additionally, a sound message or an alarm is triggered by the display and validation module 32.
When a piece of conflict information is detected by the conflict determination module 38, the latter is able to prevent the automatic performance of the operation to be performed, and the crew must then take control in order to either perform the operation or not.
The databases 30 and 50 are parameterizable in order to define and update the data of the operations to be performed in each procedure, and also to define and update the priority table and/or incompatibility table. The parameterization may be carried out from the ground facilities, especially during a maintenance operation on the aircraft 12.
An example of a assistance method for the crew using the system 10, will now be described in the context of the performance of three successive procedures as illustrated in
Initially, the twin-engine aircraft 12 takes off. The assistance system 10 is enabled by the crew. The data acquisition module 33 continuously queries the sensors present in the various functional systems 14 of the aircraft in order to obtain information representative of the operating states of the functional systems 14.
The information representative of the operating states is continuously transmitted to the monitoring module 34.
The monitoring module 34 continuously queries the procedure database 30 in order to determine whether the current operating states received from the data acquisition module 33 are predefined operating states corresponding to one or more procedures listed in the priority table.
When the current operating states correspond to at least one procedure listed in the priority table, the monitoring module 34 transmits the piece of information to the display and validation module 32, which suggests to the crew the implementation of the procedure(s) corresponding to the current operating states in the order defined in the priority table.
For example, when the data acquisition module 33 detects that the flight level 100, corresponding to passing to an altitude of 10,000 feet is reached, and no malfunction has been observed on the functional systems 14, the monitoring module 34 determines that the normal procedure “CLIMB” may be enabled. It thus transmits this piece of information to the display and validation module 32 which suggests to the crew performing the operations of this procedure.
Upon crew acknowledgement, the display and validation module 32 retrieves the information relating to the operations to be performed in the procedure from the procedure database 30, and displays it on a screen of the control panel 26, as shown in
The monitoring module 34 then enables the automatic execution module 36 to allow subsequent automatic performance of the various operations in the procedure.
The automatic execution module 36 then loads into the database 30, the list of operations to be performed for the procedure.
For each successive operation, the automatic execution module 36 determines whether the operation should be performed depending on the operating states of the functional systems 14 received from the data acquisition module 33.
The automatic execution module 36 moreover determines whether the operation is an operation without validation by the crew (marked “A” in
In the case of an operation without any validation, or after having obtained consent of the crew in the case of an operation with validation, the automatic execution module 34 sends a command to perform the operation. When this is done, the module 34 verifies the effects of the command on the basis of the operating states of the functional systems 14, following execution of the command.
In the case of the procedure described in
The automatic execution module 36 then verifies that the lights have been switched off and then passes on to the next operation.
The following operation is to keep on or switch off the <<no smoking>> sign (<<no smoking>> in
If the crew chooses to switch off the sign, the automatic execution module 36 sends a command to switch off the sign, and checks that the command has been performed before proceeding to the following operation, which is similar by keeping on or switching off the sign <<fasten your seatbelts>> in the cabin (<<fasten belts>> in
Then the automatic execution module 36 detects that the following operation is to check the cabin pressurization (<<pressurization>> in
The automatic execution module 36 analyzes the information representative of the operating states of the functional systems 14, especially the pressure in the cabin air conditioning system, and automatically determines whether the pressurization is adequate by comparing the pressure observed with a range of predefined normal pressures. If the pressure is adequate, the automatic execution module 36 performs the following operations defined in the procedure until the end of the procedure.
For each operation to be performed, the conflict determination module 38 generates a piece of feasibility information for the operation, depending on the current operating states of the functional systems 14 received from the data acquisition module 33. This piece of information is either a piece of compatibility information which allows the operation to be performed, or a piece of conflict information which blocks the performance of the operation.
The monitoring module 34 also continuously checks that the current operating states of the functional systems 14 do not require the implementation of another procedure in place of the one currently being executed.
In this example, at a given moment during the course of the <<CLIMB>> procedure, the <<full authority>> digital control system of the first engine of the aircraft triggers an automatic shutdown of the engine.
The monitoring module 34 detects the shutdown of the first engine from among the current operating states raised by the data acquisition module 33.
It queries the database 30 and determines from the priority table that the procedure <<ENG1: AUTO SHUTDOWN>> corresponding to the automatic shutdown of the first engine must be implemented, in priority with respect to the <<CLIMB>> procedure which must be interrupted.
The monitoring module 34 thus stops the performance of the <<CLIMB>> “CLIMB” by the automatic execution module 36. Upon the command from the crew, it then enables the automatic execution module 36 to perform the procedure <<ENG1: AUTO SHUTDOWN>> whose successive operations are shown in
This procedure begins with a pilot operation request (<<power lever Idle>>) in order to bring the corresponding power lever to the engine idle position.
The automatic execution module 36 checks that the pilot has done this before proceeding to the following operation which is to warn the pilot not to attempt to restart the engine (<<Do not attempt to restart the engine>>).
Then the automatic execution module 36 performs the various successive operations of the procedure, some of which may be performed automatically, while others require validation by the crew, as described above.
During the course of this procedure, the data acquisition module 33 delivers information about a low level of pressure on the fuel supply line of the second engine.
The monitoring module 34 queries the database 30, and determines from the priority table that the procedure <<FUEL: ENG2 LO PRESS>> must be performed after the end of the procedure <<ENG1: AUTO SHUTDOWN>>.
When the procedure <<ENG1: AUTO SHUTDOWN>> is over, and following validation by the crew, the automatic execution module 36 begins the procedure <<FUEL: ENG2 LO PRESS>>, whose operations are shown in
The first operation of the procedure is a fuel pump enabling command <<BOOST2 ST-BY>> (power on) that is effected automatically by the automatic execution module 36, which checks that it has indeed been performed after sending the command.
Then two possible sequences of operations may be carried out, depending on the operating states of the functional systems 14 of the aircraft, especially with respect to stopping or maintaining an indication of low pressure (FUEL: ENG2 LO PRESS) on the second engine fuel supply line, following performance of the previous operation.
The automatic execution module 36 determines what sequence of operations has to be performed depending on the current operating states raised by the data acquisition module 33.
In this case, as the indication of low pressure in the second engine remains present, the automatic execution module 36 determines that the second sequence of operations has to be performed.
The automatic execution module 36 determines the quantity of fuel in the second tank (<<Tank 2 fuel quantity: Monitor>>) and compares this quantity with a quantity calculated to identify a potential fuel leak.
Based on this calculation, the automatic execution module 36 confirms the occurrence of a fuel leak. In this case, the next operation to be performed in the procedure normally involves shutting down the second engine.
However, the conflict determination module 38 determines from the current operating states of the functional systems 14 that the first engine has already been shut down. From the compatibility table, the conflict determination module 38 develops a piece of conflict information indicating that the operation of shutting down the second engine is incompatible with the current operating states.
The module 38 therefore blocks the performance of the command to shut down the second engine.
The piece of conflict information is transmitted to the display and validation module 32 to inform the crew of this incompatibility, for example by a particular indication, by displaying the operation to be performed with a different color or with a special background band, or with a visual cue, such as flashing. An audible or visual alarm may be triggered if necessary.
The piece of conflict information is also transmitted to the monitoring module 34 which disables the automatic execution module 36.
The crew takes over manual control of the performance of the procedures depending on the operational situation.
The crew assistance system 10 thus greatly simplifies the task of the crew by serving as a second pilot thanks to the presence of a monitoring module 34 which continuously determines the appropriate procedures to be performed at any moment, and prioritizes these procedures based on the current functioning states of the functional systems 14 of the aircraft 12.
For each procedure, the crew assistance system 10 is able to display in a synthetic manner the various operations to be performed, and the state of performance of each operation through a display and validation module 32.
The automatic execution module 36 of the crew assistance system 10 is further able to enable the automatic or semi-automatic performance of successive operations of a procedure, especially directly generating commands, without the intervention of the crew, or, in some cases, after validation by the crew. The automatic execution module 36 is able to verify that these commands have been carried out, based on the current operating states of the functional systems 14.
The conflict determination module 38 of the crew assistance system 10 is able to signal to the crew at any time whether an operation to be performed, particularly coming from the automatic execution module 36, is incompatible with the current operating states of the functional systems 14 and if necessary block the command for performing this operation. This guides the crew when it is manually running the procedures and ensures safety in the case where the procedures are automatically or semi-automatically run by the automatic execution module 36.
The system 10 greatly simplifies the conduct of the flight and gives the possibility, in some cases, of overcoming the lack of a crew member. In addition, the safety of the conduct of the flight is maintained, since the crew operations are monitored and validated continuously by the crew assistance system 10, especially when these operations are inalienable or irreversible.
However, the crew remains master of the assistance system 10 at all times, and can take over the commands of the system 10 through traditional commands at the control panel 26.
Alternatively, the assistance system 10 may be implemented by a maintenance operator to perform at least one procedure. The implementation takes place either in the aircraft, especially the cockpit, or on the ground at a distance from the aircraft.
Alternatively, the module 32 may be simply a display module able to receive a piece of acknowledgement information of the performance of the validation.
Nevertheless, the conflict determination module 38 remains enabled and passes on the piece of feasibility information to the display module 32.
Constant, Gilles, Ramirez, Bruno, Bramoullé, Gaëtan
| Patent | Priority | Assignee | Title |
| Patent | Priority | Assignee | Title |
| 8698653, | Feb 17 2012 | Honeywell International Inc. | Display system and method for generating a display |
| 20060028012, | |||
| 20100161157, | |||
| 20140200747, | |||
| 20160107763, | |||
| WO9526012, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Mar 04 2016 | DASSAULT AVIATION | (assignment on the face of the patent) | / | |||
| Apr 18 2016 | CONSTANT, GILLES | DASSAULT AVIATION | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 038744 | /0922 | |
| Apr 20 2016 | RAMERIZ, BRUNO | DASSAULT AVIATION | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 038744 | /0922 | |
| Apr 25 2016 | BRAMOULLÉ, GAËTAN | DASSAULT AVIATION | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 038744 | /0922 |
| Date | Maintenance Fee Events |
| Mar 01 2021 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
| Date | Maintenance Schedule |
| Sep 05 2020 | 4 years fee payment window open |
| Mar 05 2021 | 6 months grace period start (w surcharge) |
| Sep 05 2021 | patent expiry (for year 4) |
| Sep 05 2023 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Sep 05 2024 | 8 years fee payment window open |
| Mar 05 2025 | 6 months grace period start (w surcharge) |
| Sep 05 2025 | patent expiry (for year 8) |
| Sep 05 2027 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Sep 05 2028 | 12 years fee payment window open |
| Mar 05 2029 | 6 months grace period start (w surcharge) |
| Sep 05 2029 | patent expiry (for year 12) |
| Sep 05 2031 | 2 years to revive unintentionally abandoned end. (for year 12) |