System for managing an air mission plan intended to be run by a plurality of platforms performing a plurality of tasks and associated method

Abstract

The system includes at least one display (42, 43) and a display management unit (44) on the display (42, 43), suitable for displaying, on the display (42, 43), at least one summary window containing information representative of tasks from a mission plan established on the basis of a current mission context; It includes an input interface (54) and / or an acquisition interface (56) suitable for being activated to define at least one new mission context comprising at least one objective, constraint, operational state and / or tactical environment different respectively from an objective, constraint, operational state and / or tactical environment of the current mission context and a mission calculation engine (58) suitable for being activated to determine a new mission plan based on the new mission context defined by the input interface (54) and / or by the acquisition interface (56).

Description

[0001] The present invention relates to a system for managing an aerial mission plan, intended to be executed by a plurality of platforms having to carry out a plurality of tasks, according to the preamble of claim 1.

[0002] Such a management system is intended in particular to be integrated into a ground control station of an aircraft fleet, in parallel with a flight control system ("Flight Management System" or "FMS" in English), to allow a ground crew to manage the mission plan and its developments.

[0003] Alternatively, the management system is embedded in an aircraft, particularly in the cockpit of the aircraft.

[0004] Such a system is intended to be used in particular to plan and monitor complex reconnaissance and / or combat missions in potentially hostile airspace.

[0005] Platforms are, for example, military aircraft, in particular reconnaissance and / or combat planes or drones.

[0006] The mission generally includes a plurality of objectives to be achieved, which are defined by a user, following constraints which exist in the environment.

[0007] The objectives to be achieved include, for example, destroying a target, neutralizing an air defense system, or eliminating a threat, such as a hostile combat system. Each objective to be achieved involves a plurality of tasks to be performed by at least one platform.

[0008] Constraints on the mission include, for example, geographical areas to avoid, time constraints, weather constraints, rules of engagement (e.g., need for visual identification before firing), etc.

[0009] To successfully carry out the mission, avoiding material or human losses, the tasks to be carried out must be planned very precisely in time and space, and must take into account the available platforms, their capabilities and their operational status.

[0010] Mission planning therefore requires the establishment of a very precise mission plan including, for each platform, the list of tasks to be carried out, as well as the location and time at which each task must be carried out. The individual mission plans of the different platforms must also be coordinated with each other.

[0011] The mission plan is then implemented by the various platforms which carry out the different tasks, under the supervision of the crew of each platform.

[0012] For the determination of the mission plan, powerful algorithmic calculation engines exist, allowing the automation of the definition of tasks based on the objectives, and their allocation to the different platforms intended to carry out the mission.

[0013] However, such systems are not entirely satisfactory. Indeed, the context of the mission often changes over time. In particular, the user of the management system may sometimes wish to modify the objectives of the mission, or the constraints applying to the mission.

[0014] Similarly, events external to the mission can disrupt its progress, such as the failure or neutralization of a platform, or a change in the tactical environment, notably the appearance of a new threat.

[0015] US2017 / 0254664 describes a mission management system for a platform in which a plurality of alternative mission plans are determined before the start of the mission, an update of the times spent at the different waypoints of the mission plans being carried out during the mission.

[0016] US2016 / 216711A1 describes a method of planning an unmanned aerial vehicle (UAV), e.g., aircraft for mission execution, comprising providing mission plan instructions to the UAV to enable the UAV to move from a first geographic location to a second geographic location.

[0017] US2016 / 146622A1 describes a threat assessment system, i.e., avionics system, for use in a military vehicle, having a processor for assessing the impact of a threat moving outside the boundaries if the processor determines that the location of the moving threat is moved outside the boundaries.

[0018] US7194353B1 describes a method of determining a flight path for an aircraft, comprising adjusting the flight path to provide a modified flight path, such that each grid cell intersected by a modified path has a cumulative threat risk value less than the defined value.

[0019] An aim of the invention is therefore to provide an air mission plan management system which is simple to use, and which nevertheless allows adaptation to changes in the mission context, in particular during the mission.

[0020] For this purpose, the invention relates to a system according to claim 1.

[0021] The system according to the invention may comprise one or more of the characteristics of claims 2 to 11 or one of the following characteristics, taken in isolation or in any technically possible combination: the mission calculation engine is capable of transforming each mission objective into a list of tasks to be performed to achieve the objective; the mission calculation engine is capable of distributing the mission tasks of each mission objective between the platforms intended to perform the mission, depending on the platforms available to perform the mission, the operational state of each platform and the tactical environment around the platforms; the mission calculation engine is capable of generating a mission plan for each platform comprising the ordered list of tasks to be performed, the time at which the task must be performed, the resources to be used at a waypoint on an application point, the mode of use of the resources at the waypoint, the geographical coordinates of the waypoint, and the trajectory to be taken from the waypoint to perform this task;the mission plan further comprises, for each platform, a flight plan comprising all the waypoints of the mission, and task trajectories, the tasks being linked by joining trajectories; the mission calculation engine is capable of calculating the ordered list of tasks to be carried out and the flight plan according to the constraints defined for the mission, in particular spatial, temporal, logical, or resource constraints, and / or an indicator of importance and / or priority of the constraint; the display management assembly is capable of displaying information representative of a previewed mission plan or of a mission plan proposed automatically superimposed on the information representative of the current mission plan, advantageously including modified waypoints and / or a modified trajectory proposed for the previewed mission plan or for the mission plan proposed automatically;the display management assembly is capable of displaying the display of a validation window of the previewed mission plan or the automatically proposed mission plan comprising a validation button capable of being selected by the user if he is satisfied by the previewed mission plan or the automatically proposed mission plan, to replace the current mission plan with the previewed mission plan or with the automatically proposed mission plan which becomes the new current mission plan.;

[0022] The invention also relates to a method for managing an air mission plan according to claim 12.

[0023] The method according to the invention may comprise one or more of the characteristics of claims 13 or 14, taken in isolation or in any technically possible combination.

[0024] The invention will be better understood by reading the following description, given solely by way of example, and made with reference to the appended drawings, in which: [ Fig 1 ] there figure 1 is a block diagram illustrating the components of a first mission plan management system according to the invention; [ Fig 2 ] there figure 2 is a schematic view illustrating a potential display arrangement in the first management system according to the invention; [ Fig 3 ] there figure 3 is a block diagram illustrating the logic of use of the management system according to the invention; [ Fig 4 ] there figure 4 is a view of a first mission summary window, including information representative of the tasks of a current mission in the tactical environment; [ Fig 5 ] there figure 5 is a view analogous to the figure 4 illustrating a step of modification by a user of a mission objective; [ Fig 6 ] there figure 6 is a view analogous to the figure 4 illustrating a step of displaying the modifications made by the user, before calculation by the calculation engine; [ Fig 7 ] there figure 7 is a view analogous to the figure 4 illustrating a step of displaying a previewed mission plan, before validation by the user; [ Fig 8 ] there figure 8 is a view analogous to the figure 4 illustrating a new current mission plan, after validation by the user of the previewed mission plan of the figure 7 ; [ Fig 9 ] there figure 9 is a view of a second mission summary window including mission objectives and information representative of the tasks of a current mission; [ Fig 10 ] there figure 10 is a view analogous to the figure 9 , when inserting a new mission objective by the user; [ Fig 11 ] there figure 11 is a view analogous to the figure 9 , after calculation of the new mission plan previewed by the calculation engine; and [ Fig 12 ] there figure 12 is a detail view of the display of the figure 4 , during a modification of the mission context, resulting from an event occurring on a platform intended to execute the mission.

[0025] In the figures, the views represent actual display windows of aeronautical displays, containing information in English, which is the language used in displays in this field. Where appropriate, and if necessary, the information is translated into French in the description that follows.

[0026] On the figure 1 A first system 10 for managing a mission plan according to the invention is schematically illustrated. In this example, the management system 10 is integrated into an infrastructure 12 for controlling a fleet of platforms 14 intended to carry out the mission.

[0027] The management system 10 is for example integrated into a ground mission control infrastructure, and / or into a portable electronic device (for example a tablet), or into a PC-type computer.

[0028] Alternatively, the management system 10 is integrated into the cockpit of a platform 14.

[0029] The fleet's 14 platforms are advantageously aircraft, particularly military aircraft. Aircraft are, for example, military fighter or reconnaissance aircraft, and / or drones.

[0030] In a known manner, the control infrastructure 12 is intended to control all of the systems of each platform 14, during the mission.

[0031] The control infrastructure 12 comprises in particular, in addition to the mission plan management system 10, a system 16 for conducting and executing the mission of each platform 14 of the fleet, and a system 18 for managing and monitoring the aircraft systems of each platform 14 of the fleet. It further comprises a system 19 for managing payloads, in particular sensors and weapons of each platform 14 and a system 21 for monitoring the tactical environment around each platform 14.

[0032] The mission control and execution system 16 is intended to assist the pilot of the platform 14 in navigating the platform 14 during the mission. It is capable of providing information in particular on the route followed by the platform 14, and on parameters of the evolution of the platform 14 such as fuel consumption.

[0033] It is also capable of guiding the platform 14 to follow a predetermined trajectory for the mission and carry out the tasks planned in the current mission plan.

[0034] The aircraft systems management and monitoring system 18 is intended in particular to allow the crew to monitor and possibly control all aircraft systems. The aircraft systems include in particular the hydraulic, electrical and conditioning systems of platform 14.

[0035] Similarly, the payload management system 19 is intended in particular to allow the crew to monitor and possibly control all payloads, in particular the weapons and associated sensors.

[0036] The systems 18, 19 are particularly suitable for determining an operating state of the platform 14 and its payloads, in particular the presence of faults and breakdowns present on the platform 14 and on its payloads on the ground and / or in flight.

[0037] The management system 10 according to the invention is connected to the systems 18, 19 of each platform 14 to take into account the state of the platform and its payloads in the mission plan calculations.

[0038] The tactical environment monitoring system 21 is capable of providing real-time information on the tactical environment in which each platform 14 operates.

[0039] The tactical environment includes, among other things, potential targets and threats, allied equipment and positions, and hostile or friendly areas. Information includes, among other things, the position and possible movement of each component of the tactical environment.

[0040] In reference to the figure 10 , the mission includes at least one objective 20 to be achieved (see figure 9 ), following a mission plan respecting at least one mission constraint.

[0041] Objective 20 is, for example, reconnaissance of an area, destruction of a target, neutralization of an air defense system, suppression of a threat, such as a hostile combat platform, air-to-air surveillance, support of ground troops ("close air support" in English), etc.

[0042] Each objective 20 is broken down into a plurality of elementary tasks 22 to be carried out by one or more platforms 14 of the mission, while respecting the constraints of the mission.

[0043] The elementary tasks 22 are for example navigation tasks, such as going to a waypoint, trajectories to be carried out from this waypoint, resources to be used at this waypoint on the point of application of the task, and possibly the activation of a mode of use of the resources to be used, for example a mode of taking a map by a radar.

[0044] The mission plan includes, for each platform 14 of the fleet, the ordered list of mission tasks 22 to be carried out by this platform 14, associated with a flight plan for this platform 14.

[0045] The mission plan is, for example, materialized by one or more computer files containing the ordered list data and the flight plan data.

[0046] The flight plan includes all 24 waypoints of the mission (visible in the form of pictograms on the figure 4 ), the set of trajectories 26 to be carried out for each task of the mission from a waypoint 24, and the joining trajectories 28 between the successive tasks of the mission, each joining trajectory 28 connecting the final end of the trajectory 26 to be carried out for a task of the mission and the waypoint 24 associated with the following task of the mission.

[0047] Mission constraints include spatial constraints, for example 30 zones or prohibited flight levels, 32 air routes or imposed flight levels, or more generally free flight zones and / or zones of flight imposed by airways.

[0048] Mission constraints also include time constraints, in particular a mission departure time and / or a required arrival time at each mission waypoint.

[0049] Mission constraints also include logical constraints, for example, impossibilities of performing a given task after another given task or, conversely, necessities of performing a given task after another given task.

[0050] Mission constraints also include resource constraints, associated with each platform, resulting from the platform's capabilities and its operational status in terms of faults and / or failures on one or more systems of the platform 14.

[0051] For example, the capabilities and / or operational state of the platform 14 may impose a maximum speed achievable by the platform 14, a defined autonomy of the platform 14, or even the impossibility of performing certain tasks such as firing or reconnaissance.

[0052] For example, if a weapon system is defective, platform 14 is unable to fire a weapon using that weapon system. Similarly, if a sensor is defective, platform 14 is unable to perform a reconnaissance task.

[0053] Mission constraints are advantageously associated with at least one indicator of the importance and / or priority of the constraint. The indicator is, for example, an indicator of compliance or non-compliance with a constraint or a numerical indicator reflecting a gradation between a strong constraint and a weak constraint.

[0054] In reference to the figure 1 and to the figure 2 , the management system 10 comprises at least one mission plan calculator 40, at least one display 42, 43 and at least one display management assembly 44 on the display 42, 43 suitable for displaying, on the display 42, 43, at least one summary window 46, 48 comprising information representative of tasks of a current mission plan.

[0055] The management system 10 further advantageously comprises an input tool 49, for example a keyboard, a mouse and / or a touch screen, intended to enable interactions with a user.

[0056] In this example, the mission plan calculator 40 comprises at least one processor 50 and at least one memory 52 containing software modules suitable for being executed by the processor 50.

[0057] The memory 52 contains at least one software module 54 for an interface for inputting, by a user, objectives and constraints of the mission, at least one software module 56 for an interface for acquiring operational states of platforms 14 which are to carry out the tasks of the mission and for acquiring tactical environment data around the platforms 14.

[0058] The memory 52 further contains a mission calculation engine 58, capable of determining a mission plan comprising a list of tasks to be carried out to fulfill the mission objectives while respecting the constraints, and an allocation of the tasks between the platforms 14, taking into account the capabilities and / or the operational state of the platforms 14.

[0059] The memory 52 further contains a mission plan cycle management module 59, intended to control the input interface 54, the acquisition interface 56 and the calculation engine 58 to implement a mission plan establishment cycle.

[0060] The input interface 54 is intended to be activated by a user to enter mission objectives and / or constraints defining a mission context.

[0061] The input interface 54 is for example implemented in the form of at least one input window 60 (see figure 5 ) intended to be displayed on a display 42, 43 by the display management assembly 44.

[0062] The input window 60 allows the user to define a new mission context comprising at least one objective and / or one constraint different from the objectives and constraints of the current mission plan.

[0063] The input interface 54 is capable of collecting user input by means of the input window, to define at least one new mission objective, for example a new reconnaissance, a new shot, and / or a new mission constraint, for example a schedule of different passages or at an imposed passage point.

[0064] The input interface 54 preferably comprises at least one input activation button 62 capable of being activated by the user to validate the input and to enable information representative of the modifications to the mission context to be displayed on the display 42, 43.

[0065] The input interface 54 also includes a preview button 64 (see figure 6 ), suitable for enabling the activation of the mission calculation engine 58 and the display of information representative of the tasks of a previewed mission plan obtained after activation of the calculation engine 58.

[0066] It also includes a button 66 for validating the previewed mission plan (see figure 7 ), suitable for activation by the user to replace the current mission plan with the previewed mission plan, as will be seen below.

[0067] The acquisition interface 56 is capable of punctually or periodically interrogating the aircraft systems management and monitoring system 18 and / or the payload management system 19 to determine a modification of an operational state of at least one platform 14 or its payloads. It is capable of punctually or periodically interrogating the mission control and execution system 16 of each platform to determine the position of the platform 14 and to determine whether a new constraint, for example meteorological, applies.

[0068] The acquisition interface 56 is also capable of punctually or periodically interrogating the tactical environment monitoring system 21 to determine a change in the tactical environment, for example the appearance of a new threat.

[0069] The modification of operational state, constraint or tactical environment determined by the acquisition interface 56 creates a new mission context having at least one operational state and / or a tactical environment different from the operational state and / or the tactical environment of the current mission context.

[0070] When the acquisition interface 56 detects a new mission context, the mission engine 58 is able to activate without a request from a user to calculate an automatically proposed mission plan, information representative of the tasks of the automatically proposed mission plan being displayed on the display 42, 43, after activation of the calculation engine 58.

[0071] The acquisition interface 56 also includes a validation button 68 for the automatically proposed mission plan (see figure 12 ), suitable for being activated by the user to replace the current mission plan with the automatically proposed mission plan.

[0072] The calculation engine 58 comprises an application 70 for managing objectives, an application 72 for allocating tasks, and an application 74 for generating a mission plan taking into account the mission constraints, the mission plan being obtained for each platform 14.

[0073] The management application 70 is capable of transforming each objective of the mission into a list of tasks to be carried out to achieve the objective. The application 70 is thus capable of identifying an objective entered by the user, and depending on the type of objective entered by the user, of defining the list of tasks, advantageously using a mission task database (not shown).

[0074] For example, if the objective is to neutralize a target, mission tasks include, for example, approaching the target, measuring the target's position, preparing to fire, and firing.

[0075] The allocation application 72 is capable of distributing the mission tasks of each mission objective between the platforms 14 intended to carry out the mission, depending on the platforms 14 available to carry out the mission, the operational state of each platform 14 and the tactical environment around the platforms 14.

[0076] The generation application 74 is capable of generating a mission plan for each platform 14 comprising the ordered list of tasks to be performed, the time at which the task must be performed, the resources to be used at a waypoint 24 on an application point, the mode of use of the resources at the waypoint 24, the geographical coordinates of the waypoint 24, and the trajectory 26 to be taken from the waypoint 24 to perform this task.

[0077] The mission plan further comprises, for each platform 14, a flight plan comprising all the waypoints 24 of the mission, and task trajectories 26, the tasks being linked by joining trajectories 28.

[0078] The ordered list of tasks to be performed and the flight plan are calculated based on the constraints defined for the mission, including spatial, temporal, logical, or resource constraints, as defined above. The generation of the mission plan also takes into account the importance and / or priority indicator of the constraint.

[0079] The mission plan is for example provided by the mission engine 58 in the form of at least one computer file comprising the list of tasks to be carried out and the associated flight plan.

[0080] The cycle management module 59 is intended to control the input interface 54, the acquisition interface 56 and the calculation engine 58 to implement a mission plan establishment cycle, represented on the figure 3 .

[0081] Initially, before the mission or at the start of the mission, the cycle management module 59 is capable of enabling the definition of the objectives and constraints of a current mission plan 80, on the basis of a desired mission context 82 loaded into the system 10 or defined from the input interface 54 and of activating this current mission plan 80 to enable the mission to be carried out.

[0082] As indicated above, the desired mission context 82 includes at least the mission objectives, the constraints applied to the mission, the operational state of each platform 14 and the tactical environment around the platforms 14.

[0083] Then, when the user wishes to modify the objectives or constraints of the mission by means of the input interface 54, the cycle management module 59 is able to activate the display management assembly 44 to display it on the display 42, 43 an input window 60. The cycle management module 59 is able to collect the input of a new objective and / or a new constraint made by the user, once the activation button 62 has been activated by the user. This defines a modified mission context 84.

[0084] The cycle management module 59 is then able to initiate the display on the display 42, 43, by the display management assembly 44, of information representative of the modifications 86 of objectives and constraints of the mission, superimposed on the information representative of the current mission plan, without calculating a flight plan with the mission engine 58 at this stage. The cycle management module 59 is then able to initiate the display of a calculation activation window 88 (visible on the figure 6 ) including the preview button 64.

[0085] Amendments 86 include, for example, one or more additional application points 89.

[0086] The cycle management module 59 is capable, after activation of the preview button 64 by the user, of activating the calculation engine 58 to generate a previewed mission plan 90 taking into account the modifications 86 present in the modified mission context 84. It is then capable of initiating the display on the display 42, 43, by the display management assembly 44, of information representative of the previewed mission plan 90 superimposed on the information representative of the current mission plan 80 and of launching the display, on the display 42, 43, of a window 92 for validating the previewed mission plan (see figure 7 ) including the validation button 66.

[0087] Like the current mission plan 80, the previewed mission plan 90 includes the ordered list of tasks to be performed, the time at which the task must be performed, the resources to be used at a waypoint 24 on an application point, the mode of use of the resources at the waypoint 24, the geographical coordinates of the waypoint 24, and the trajectory 26 to be carried out from the waypoint 24 to carry out this task. It includes a flight plan including all the waypoints 24 of the mission, all the trajectories 26 to be carried out for each task of the mission from a waypoint 24, and the joining trajectories 28 between the successive tasks of the mission, each joining trajectory 28 connecting the final end of the trajectory 26 to be carried out for a task of the mission and the waypoint 24 associated with the next task of the mission.

[0088] Upon validation of the validation button 66 by the user, the cycle management module 59 is able to replace the current mission plan 80 with the previewed mission plan 90 which becomes the new current mission plan.

[0089] On the display 42, 43, the information representative of the current mission plan 80 is then replaced by the information representative of the previewed mission plan 90.

[0090] In parallel, the acquisition interface 56 is capable of being activated punctually or periodically to determine a possible change in operational state, constraint or tactical environment of a platform 14, modifying the mission context 82 and defining a modified mission context 84 and activating the cycle management module 59 in the event of a change in the mission context 82.

[0091] In this case, the cycle management module 59 is capable of automatically activating the calculation engine 58 to generate an automatically proposed mission plan 94 and to launch the display, on the display 42, 43, of a validation window 96 of the automatically proposed mission plan (see figure 12 ) including the validation button 68.

[0092] Like the current mission plan, the automatically proposed mission plan 94 includes the ordered list of tasks to be performed, the time at which the task must be performed, the resources to be used at a waypoint 24 on an application point, the mode of use of the resources at the waypoint 24, the geographical coordinates of the waypoint 24, and the trajectory 26 to be carried out from the waypoint 24 to perform this task. It includes a flight plan comprising all the waypoints 24 of the mission, and task trajectories 26, the successive tasks being connected by joining trajectories 28.

[0093] Upon validation of the validation button 68 by the user, the cycle management module 59 is able to replace the current mission plan 80 with the automatically proposed mission plan 94 which becomes the new current mission plan.

[0094] On the display 42, 43, the information representative of the current mission plan 80 is then replaced by the information representative of the automatically proposed mission plan 94.

[0095] The display management assembly 44 comprises a graphics processor and a memory containing software modules capable of being executed by the graphics processor to display on each respective display 42, 43, summary windows of the mission plan 46, 48, the dialog windows 62, 88, 92, 96 and the information representative of the mission plans.

[0096] In the example shown on the figures 2 And 4 à 8, at least one display 42 is intended for displaying a summary window 46 comprising a geographical view 100 of the terrain in which the mission must be carried out, also designated by the term “tactical image”. The geographical view 100 comprises in particular a representation of the prohibited zones 30, and / or of the friendly 102 or hostile 104 terrains and advantageously of a separation line 105 between the terrains 102, 104.

[0097] The information representing the mission tasks is then representations of the waypoints 24, the mission trajectories 26, the joining trajectories 28, and possibly data relating to the tasks to be carried out.

[0098] Optionally, the display management assembly 44 is capable of displaying, superimposed on the summary window 46, a time tracking window 106 listing, for the current mission plan, the successive tasks 108 of an individual platform 14, or of a group of platforms 14, on a timeline 110.

[0099] In the example shown on the figures 9 à 11 , at least one display 43 is intended for displaying a summary window 48 comprising a table of successive tasks 22 planned in the current mission plan.

[0100] The representative information is then a designation of the planned task 22 to be carried out (here “Task A1”, “Task A2”, “Task B”, etc.), the mention of the platform 14 intended to carry out the task (“UCAV”), and indications relating to the execution of the task, such as the waypoint (“Waypoint”) at which the task must be carried out, and the time at which the task must be carried out (“Time”).

[0101] The summary window also advantageously includes a table of defined objectives (“Mission goals”) and a breakdown into tasks to be planned 22A (“Tasks to plan”), each associated with an application point 89A of the task (“Task application point”).

[0102] A goal modification button 107 is further displayed to enable activation of the input interface 54 and the addition of a new goal.

[0103] Each task to be planned 22A in the defined objectives table is broken down into one or more planned tasks 22 in the planned tasks table. Similarly, each planned task 22 results from one or more tasks to be planned 22A.

[0104] The operation of the Mission Plan Management System 10 will now be described.

[0105] Initially, the user defines or loads a mission context 82 comprising the mission objectives and the mission constraints, in particular using the input interface 54. The acquisition interface 56 loads the operational state of the platforms 14 and the tactical environment around the platforms.

[0106] The user activates the mission calculation engine 58 to define a current mission plan 80.

[0107] When the mission begins, the current mission plan 80 is activated for the completion of the mission. The information representative of the current mission plan 80 is displayed on each summary window 46, 48 as illustrated in the figures 4 And 9 .

[0108] Then, when the user wishes to modify the current mission plan 80, he activates the input interface 54, for example by clicking on the point 89 of the geographic view 100 on which a new objective must be achieved.

[0109] The cycle management module 59 then activates the display management assembly 44 which displays an input window 60 superimposed on the summary window 46. The input window 60 is here a circular menu.

[0110] The user enters a new objective and / or a new constraint, and activates the activation button 62 to define a modified mission context 84.

[0111] The cycle management module 59 then integrates the input made by the user and initiates the display on the summary window 46 of information representative of the modifications 86, superimposed on the information representative of the current mission plan 80.

[0112] The information representing the modifications 86 is for example displayed in a different color from that of the current mission plan or with a different graphic. Since no flight plan has been calculated at this stage for these modifications, only application points 89 are displayed in addition to the information representing the current mission plan. No trajectory associated with the modifications 86 is therefore visible on the summary window 46 at this stage.

[0113] In reference to the figure 10 , information representative of the modifications 86 is also displayed on the summary window 48 in the form of a new line of objectives and tasks to be planned 22A in the table of the summary window 48, creating a modified mission context.

[0114] The display management assembly 44 also displays a calculation activation window 88 (visible on the figure 6 ) including the preview button 64 and a cancel button.

[0115] The user then selects the preview button 64. The cycle management module 59 activates the calculation engine 58 to generate a previewed mission plan 90 taking into account the modified mission context 84.

[0116] As illustrated in the figure 7 , the display management assembly 44 then displays information representative of a previewed mission plan 90 superimposed on the information representative of the current mission plan, including the modified waypoints 91, and the modified trajectory 91A proposed for the previewed flight plan 90.

[0117] The information representative of the previewed mission plan 90 is for example displayed in a different color from that of the current mission plan or with a different graphic.

[0118] Furthermore, the information representative of the previewed mission plan 90 is also displayed on the time tracking window 106, in the form of a derivation 111 of the time line 110, placed parallel to the time line 110, with time synchronization with the time line 110.

[0119] In reference to the figure 11 , the planned tasks 22 to be executed are then updated in the table of planned tasks of the window 48, adding the information representative of the previewed mission plan 90 to that of the current mission plan 80.

[0120] The display management assembly 44 also launches the display of a window 92 for validating the previewed mission plan (see figure 7 ) comprising the validation button 66 and advantageously a cancellation button.

[0121] If satisfied with the previewed mission plan 90, the user selects the validation button 66 visible on the figure 7 .

[0122] In reference to the figure 8 , the cycle management module 59 replaces the current mission plan 80 with the previewed mission plan 90 which becomes the new current mission plan. The information representative of the current mission plan 80 is then replaced on the summary windows 46, 48 by the information representative of the previewed mission plan 90. Similarly, the derivation 111 of the timeline 110 replaces the timeline 110 on the time tracking window 106.

[0123] In parallel, the acquisition interface 56 is activated punctually or periodically, to determine a possible change in constraint, operational state of a platform 14 and / or tactical environment, modifying the mission context 82 and defining a modified mission context 84.

[0124] In this case, the cycle management module 59 automatically activates the calculation engine 58 to generate an automatically proposed mission plan 94.

[0125] The display management assembly 44 launches the display on the summary window 46 of information representative of the automatically proposed mission plan 94.

[0126] In reference to the figure 12 , this information includes for example a modified trajectory 130 which is displayed in a different color or with different graphics, superimposed on the information representative of the current mission plan 80.

[0127] The display management assembly 44 simultaneously displays a validation window 96 of the automatically proposed mission plan (see figure 12 ) including the validation button 68 and advantageously a cancellation button.

[0128] Upon validation of the validation button 68 by the user, the cycle management module 59 replaces the current mission plan 80 with the automatically proposed mission plan 94 which becomes the new current mission plan.

[0129] The information representative of the current mission plan 80 is then replaced by the information representative of the automatically proposed mission plan 94 on windows 46, 48 and 106.

[0130] The management system 10 is therefore particularly useful for conducting and monitoring complex missions involving multiple platforms and numerous objectives to be achieved. The management system 10 is very effective when changes to the mission occur, either due to the user or due to unexpected events affecting the platforms 14 conducting the mission.

[0131] The management system 10 allows the user to easily define a new mission context, by proposing an alternative mission plan. Similarly, in the event of the occurrence of unexpected events, the management system 10 proposes to the user at least one alternative mission plan to implement.

[0132] In a variant (not shown), the calculation engine 58 calculates several previewed mission plans 90 or several automatically proposed mission plans 94, leaving a choice to the user. The information representative of the different mission plans is for example presented simultaneously, in particular on the window 46 or successively by activating a scroll button (not shown), in particular on the window 48.

Claims

1. A system (10) for managing an air mission plan intended to be run by a plurality of platforms (14) performing a plurality of tasks, the system (10) comprising: - an input interface (54), for users, of the objectives and constraints of the mission; - an acquisition interface (56) of operational states of the platforms (14) performing the mission tasks and acquiring tactical environment data around the platforms (14); - a mission computation engine (58), suitable for determining a mission plan comprising a list of tasks to be performed in order to fulfill the mission objectives while respecting the constraints thereof; - at least one display (42, 43) and one display management assembly (44) on the display (42, 43), suitable for displaying, on the display (42, 43), at least one summary window (46, 48) comprising information representative of tasks of a mission plan established on the basis of a current mission context; the input interface (54) and / or the acquisition interface (56) is able to be activated to define at least one new mission context comprising at least one objective, a constraint, an operational state and / or a tactical environment different from an objective, a constraint, an operational state and / or a tactical environment, respectively, of the current mission context, characterized in that the mission computation engine (58) is able to determine a mission plan comprising an allocation of tasks between the platforms (14) by taking account of the operational state of the platforms (14) and the tactical environment around the platforms (14), the mission plan computed by the mission computation engine (58) comprising, for each platform (14), a sequenced list of tasks which the platform (14) must perform, associated with a flight plan for the platform (14); the mission computation engine (58) being able to be activated to determine a new mission plan based on the new mission context defined by the input interface (54) and / or by the acquisition interface (56), the display management assembly (44) being able to display, on the summary window (46, 48), information representative of tasks of at least one new mission plan obtained by the computation engine (58) based on the new mission context defined by the input interface (54) and / or by the acquisition interface (56).

2. The system (10) according to claim 1, wherein, after determining the new mission plan, the display management assembly (44) is able to display, on the summary window (46, 48), at least one validation button (68) for the new mission plan, able to be selected by the user to activate the new mission plan and replace the current mission plan.

3. The system (10) according to any one of claims 1 or 2, wherein the mission computation engine (58) is adapted to determine a plurality of new alternative mission plans based on the same new mission context defined by the input interface (54) and / or by the acquisition interface (56), the display management assembly (44) being able to display, successively or simultaneously on the display (42, 43), the information representative of each new mission plan determined by the mission computation engine (58) based on the same new mission context defined by the input interface (54) and / or by the acquisition interface (56).

4. The system (10) according to any one of the preceding claims, wherein the input interface (54) is suitable for being activated by the user to input a new objective or a new constraint of the mission and to define the new mission context, the new mission plan defined by the computation engine (58) being a previewed mission plan (90) taking into account the new objective and / or the new constraint of the mission entered by the user.

5. The system (10) according to claim 4, wherein, after entering the new objective and / or the new constraint, the display management assembly (44) is able to display information representative of the modifications (86) of the mission objective and / or constraint, before the activation of the mission computation engine (58), and a preview button (64) able to be selected by the user to activate the mission computation engine (58) and define the previewed mission plan (90).

6. The system (10) according to any one of the preceding claims, wherein the acquisition interface (56) able to detect an event modifying the constraints of the mission, of the operational state of the platforms (14), and / or of the tactical environment and to transmit, to the mission computation engine (58), at least one new constraint, a new operational state of the platforms (14), and / or a new tactical environment, the new mission plan computed by the mission computation engine (58) being an automatically proposed mission plan (94) taking into account at least one modification of the constraints of the mission, the operational state of the platforms (14) and / or the tactical environment having been generated by the event, the mission computation engine (58) possibly being able to compute the proposed mission plan automatically (94) without a request from a user.

7. The system (10) according to any one of the preceding claims, wherein the sequenced list of tasks to be performed comprises, for each task, at least one resource to be used for the task, a usage mode of the or each resource, a waypoint defining the start of the task and / or a trajectory to be taken for this task.

8. The system (10) according to any one of the preceding claims, wherein the flight plan comprises all the waypoints corresponding to each task to be performed by the platform (14), the trajectories to be performed for the task and / or the trajectories of junctions between the waypoints.

9. The system (10) according to any one of the preceding claims, wherein the summary window (46) of a current mission plan comprises a geographical view (100) of the terrain in which the mission is carried out, the information representative of the current mission plan (80) being represented on the geographical view (100), the information representative of the new mission plan being able to be represented in superposition or in substitution of the information representative of the current mission plan (80) on the geographical view.

10. The system (10) according to any one of the preceding claims, wherein the summary window (48) of the current mission plan comprises a table of successive tasks of the current mission plan, the table of successive tasks being able to be modified by the display management assembly (44) for displaying, in addition or in substitution, the specific tasks of the new mission plan.

11. The system (10) according to any one of the preceding claims, wherein the display management assembly (44) is adapted to display a time tracking window (106) listing, for the current mission plan, the successive tasks (108) of an individual platform (14), or of a group of platforms (14), on a timeline (110).

12. A method of managing an air mission plan comprising the following steps: - providing a management system (10) according to any one of the preceding claims; - inputting mission objectives and constraints by a user using the input interface (54); - acquiring, via the acquisition interface (56), operational states of the platforms (14) performing the mission tasks and / or tactical environment data around the platforms (14); - determining, via the mission computation engine (58), a mission plan comprising a list of tasks to be carried out to fulfill the mission objectives while respecting the constraints thereof; - displaying, on the display (42, 43) via the display management assembly (44), at least one summary window (46, 48) comprising information representative of tasks of a mission plan established based on a current mission context; - defining, via the input interface (54) and / or the interface of at least one new mission context comprising at least one objective, a constraint, an operational state and / or a tactical environment different from an objective, a constraint, an operational state and / or a tactical environment, respectively, of the current mission context; characterized by the following steps: - determining, via the mission computation engine (58), the mission plan comprising allocating tasks between the platforms (14) while taking account of the operational state (14) and the tactical environment around the platforms (14), the mission plan computed by the mission computation engine (58) comprising, for each platform (14), a sequenced list of tasks which the platform (14) must perform, associated with a flight plan for the platform (14); - activating the mission computation engine (58) to determine a new mission plan based on the new mission context defined by the input interface (54) and / or by the acquisition interface (56); - displaying, via the display management assembly (44), on the summary window (46, 48), information representative of tasks of at least one new mission plan obtained by the computation engine (58) based on the new mission context defined by the input interface (54) and / or by the acquisition interface (56).

13. The method according to claim 12, comprising activating the user input interface (54) to enter a new mission objective or constraint and define the new mission context, the new mission plan defined by the computation engine (58) being a previewed mission plan (90) taking into account the new objective and / or the new constraint of the mission entered by the user.

14. The method according to claim 12 or 13, comprising the following steps: - detecting, via the acquisition interface (56), an event modifying the constraints of the mission, the operational state of the platforms (14), and / or the tactical environment; and - transmitting, to the mission computation engine (58), at least one new constraint, a new operational state of the platforms (14), and / or a new tactical environment; the new mission plan computed by the mission computation engine (58) being an automatically proposed mission plan (94) taking into account at least one modification of the constraints of the mission, of the operational state of the platforms (14) and / or of the tactical environment having been generated by the event, the automatically proposed mission plan (94) being advantageously computed by the mission computation engine (58) without a request from a user.

Images