Method for determining a statistical fatigue level relating to a population of operators and associated determination system

Abstract

Method for determining a statistical fatigue level relating to a population of operators and associated determination system The present invention relates to a method for determining a statistical fatigue level, comprising the following steps: - acquisition (110) of a plurality of operator evaluation data determined from physiological data of the operators; - acquisition (120) of a plurality of general context data; - acquisition (130) of a plurality of particular context data; - preprocessing (150) of all the acquired data; - acquisition (170) of a time range for determining the statistical fatigue level and acquisition (170) of a filtering criterion, the filtering criterion being based on the general context data and / or the particular context data;- determination (190) from the set of preprocessed data of a statistical fatigue level according to the filtering criterion acquired over the acquired time range. Figure for the abstract: Figure 2;

Description

Title of the invention: Method for determining a statistical fatigue level relating to a population of operators and associated determination system

[0001] The present invention relates to a method for determining a level of statistical fatigue relating to a population of operators.

[0002] The present invention also relates to a determination system making it possible to implement such a method.

[0003] The invention lies in the technical field of evaluating operator fatigue, particularly in the aeronautical field. In this field, the invention makes it possible to improve flight safety.

[0004] The invention can, however, still be used in all other fields where managing operator fatigue is an important issue. These fields include in particular those where operational performance is necessary, such as, for example, the transport sector, nuclear power or medicine.

[0005] In the state of the art, operator fatigue is generally analyzed during temporary campaigns on the basis of questionnaires allowing subjective fatigue to be captured or on the basis of individual fatigue declarations.

[0006] There are also objective assessments based on biomathematical models and intended to raise specific and individual alerts when necessary.

[0007] These two modes of capturing fatigue only allow the deduction of subjective fatigue, which may be biased by cultural or corporate pressure. In particular, operators reporting their fatigue tend to underestimate it.

[0008] On the other hand, existing solutions do not allow for obtaining objective and structural statistics offering perspectives for analyzing fatigue according to defined criteria.

[0009] The aim of the present invention is to propose a means of evaluating fatigue objectively and this while making it possible to synthesize the overall view of fatigue in order to plan the operators' missions.

[0010] To this end, the invention relates to a method for determining a level of statistical fatigue relating to a population of operators, comprising the following steps:

[0011] - acquisition of a plurality of operator evaluation data determined at from physiological data of operators;

[0012] - acquisition of a plurality of general context data relating to the context general operator evaluation;

[0013] - acquisition of a plurality of particular context data relating to the context particular operator evaluation;

[0014] - preprocessing of all acquired data;

[0015] - acquisition of a time range for determination of the level of fatigue sta tistics and acquisition of a filtering criterion, the filtering criterion being based on general context data and / or particular context data;

[0016] - determination from all the preprocessed data of a fatigue level statistics according to the filtering criterion acquired over the acquired time range.

[0017] According to other advantageous aspects of the invention, the method comprises one or more of the following characteristics, taken individually or in combination according to all technically possible combinations:

[0018] - a step of transmitting the determined statistical fatigue level for display by a display interface;

[0019] - a step of validating the evaluation data and the context data general according to one or more predetermined validation criteria;

[0020] - the or each validation criterion is chosen from the group comprising:

[0021] - the acquired data relates to a validated evaluation;

[0022] - the acquired data relating to an identified operator;

[0023] - the acquired data respects a minimum duration of the evaluation;

[0024] - the acquired data respects a collection phase, each collection phase being chosen from an initial collection phase implemented before the mission, an intermediate collection phase implemented during the mission and a final collection phase implemented after the mission;

[0025] - the general context data comprises at least one chosen data type in the group including:

[0026] - data relating to the operator's environment;

[0027] - physiological data of the operator;

[0028] - the preprocessing of general context data includes the implementation of at least less one of the elements chosen from the group comprising:

[0029] - definition of the location of the evaluation;

[0030] - definition of local time;

[0031] - identification of a morning, normal or late session;

[0032] - identification of the position occupied by the operator;

[0033] - extrapolation of information relating to the operator's sleep;

[0034] - the evaluation data comprises at least one type of data chosen from the group including:

[0035] - objective fatigue level of the operator;

[0036] - subjective fatigue level of the operator;

[0037] - the preprocessing of the evaluation data comprises the implementation of at least one of the elements chosen from the group comprising:

[0038] - normalization of the objective fatigue level;

[0039] - normalization of the subjective fatigue level;

[0040] - identification of an objective fatigue class according to the objective fatigue level;

[0041] - identification of a subjective fatigue class according to the subjective fatigue level;

[0042] - the particular context data comprises at least one data type chosen from the group including:

[0043] - data relating to the mission to be carried out by the operator;

[0044] - data relating to the mission(s) carried out by the operator;

[0045] - operational data relating to activities carried out by the operator other than a mission;

[0046] - the preprocessing of the particular context data includes the determination of at least less one of the elements chosen from the group comprising:

[0047] - flight(s) operated;

[0048] - data specific to training sessions;

[0049] - period of the day of the mission;

[0050] - type of aircraft;

[0051] - workload;

[0052] - degree of disturbance in activity;

[0053] - activities in the days preceding the assessment;

[0054] - delays or disruptions during mission(s);

[0055] - routes operated;

[0056] - a step of correlating data acquired / determined during different phases collection relating to the same operator, each collection phase being chosen from an initial collection phase implemented before the mission, an intermediate collection phase implemented during the mission and a final collection phase implemented after the mission;

[0057] advantageously, the correlation step comprising the identification of the same operator identifier for at least two session identifiers associated with said acquired / determined data, corresponding to different collection phases.

[0058] - a step of determining a number of operators and / or a number of routes and / or a number of assessments corresponding to the acquired data usable to determine the level of statistical fatigue according to this filtering criterion;

[0059] - the step of determining the level of statistical fatigue further comprises the determination mination of a confidence indicator associated with the determined level of statistical fatigue, the confidence indicator being determined based on said number of operators and / or routes and / or evaluations.

[0060] The invention also relates to a system for determining a level of statistical fatigue relating to a population of operators, comprising technical means configured to implement the method as defined previously.

[0061] These advantages and characteristics of the invention will be better understood on reading the description which follows, given solely by way of non-limiting example, and made with reference to the appended drawings in which: - [Fig.l] [Fig.l] is a schematic view of a determination system according to the invention; - [Fig.2] [Fig.2] is a flowchart of a determination method according to the invention, the method being implemented by the system of [Fig.l]; - [Fig.3][Fig.4][Fig.5] Figures 3 to 5 are schematic views illustrating the implementation of the method of [Fig.2].

[0062] [Fig.l] in fact illustrates a system 10 for determining a level of statistical fatigue relative to a population of operators.

[0063] The operator population includes more than two operators performing similar tasks during missions of similar natures. For example, the operator population includes a few dozen operators. In some examples, the operator population includes a few hundred operators or more. The operator population may vary based on filtering criteria that will be explained in more detail later.

[0064] Advantageously, the determination system 10 can be used in the aeronautical field. In such a case, each operator is part of the flight crew, in particular the commercial flight crew. According to other examples, each operator is part of the flight planning operators or the maintenance operators or the aircraft control operators or the air traffic controllers.

[0065] Advantageously, each operator is a pilot capable of piloting an aircraft.

[0066] By aircraft is meant any flying machine that can be controlled from its cockpit, as is the case for example with an airplane or a helicopter, or remotely from it, as is the case for example with a drone.

[0067] Generally speaking, the concept of operator can apply to any other person carrying out a critical mission, for example in the field of transport (rail or heavy goods vehicles for example) or in the nuclear or space field, or in medicine.

[0068] As indicated previously, each operator carries out a mission which is determined by the field of his activity.

[0069] In particular, the operator's mission includes a plurality of tasks defined according to the operator's skills.

[0070] When the operator is an aircraft pilot, his mission generally consists of piloting the aircraft from a departure point to a destination point.

[0071] With reference to [Fig.l], the determination system 10 comprises an input module 21, a processing module 22 and an output module 23.

[0072] Each of these modules 21 to 23 is presented for example at least partially in the form of software and / or a programmable logic circuit such as an FPGA circuit (“Field Programmable Gate Array”).

[0073] When these modules are at least partially in the form of software, the determination system 10 further comprises a processor for implementing this software and a RAM for storing at least temporarily the data to be processed or the data processed by these different modules. The determination system 10 may also comprise a non-volatile memory for storing at least certain input data or output data, at least temporarily.

[0074] The input module 21 is configured to receive data from external systems.

[0075] In the example of [Fig.l], the external systems notably comprise a plurality of transportable fatigue assessment systems 28 as well as one or more databases 30.

[0076] Each transportable fatigue assessment system 28 makes it possible to generate pluralities of assessment data relating to the fatigue of the different operators.

[0077] In particular, each of the transportable evaluation systems 28 makes it possible to generate the evaluation data of the operators from the physiological data of these operators.

[0078] The physiological data of the operator presents any type of data making it possible to characterize the physical state of the operator. These physiological data are advantageously acquired just before the mission during an initial collection phase, or during the mission during an intermediate collection phase, or just after the mission during a final collection phase.

[0079] Advantageously, the physiological data of the operator comprise at least one type of data chosen from the group comprising:

[0080] - images or videos of the operator;

[0081] - a heart rate;

[0082] - blood pressure;

[0083] - an inspiration of oxygen;

[0084] - a breathing frequency;

[0085] - an amplitude of breathing;

[0086] - sweating;

[0087] - oxygen saturation;

[0088] - a dehydration rate.

[0089] To acquire the physiological data, each transportable evaluation system 28 comprises a plurality of sensors. Alternatively or advantageously, each transportable evaluation system 28 is connected directly or indirectly to a plurality of sensors arranged for example in the operator's workstation. For example, these sensors are arranged in a fixed and / or removable manner in the cockpit of the aircraft piloted by the operator.

[0090] In particular, the plurality of sensors comprises any sensor making it possible to acquire the physiological data of the operator.

[0091] For example, the plurality of sensors includes a camera configured to acquire images of the operator and a heart rate sensor for measuring the operator's heart rate.

[0092] The camera is for example oriented towards the operator or has means allowing it to be oriented according to the position of the operator.

[0093] The operator's heart rate sensor is configured, for example, to be positioned around a wrist of the operator.

[0094] For this purpose, the heart rate sensor has, for example, a connected watch or a bracelet capable of being fixed on the wrist of the operator and a sensitive part which is intended to measure the heart rate of the operator when the bracelet is fixed on his wrist.

[0095] The measurement of the heart rate is carried out for example by the sensitive part, by the technique called photoplethysmography, called PPG. Alternatively, the sensitive part is configured to carry out the measurement of the heart rate from an analysis of electrical response by the operator's wrist or by analysis of radar signals propagating in the operator's wrist.

[0096] In some examples, the heart rate sensor is configured to measure other physiological parameters of the operator such as (non-exhaustive list) blood pressure, oxygen inspiration, respiration rate, respiration amplitude, sweating, dehydration rate.

[0097] For oxygen saturation, the heart rate sensor is for example configured to emit towards the operator's skin and receive a light signal comprising at least two wavelengths. A first wavelength corresponding to a wavelength absorbed by saturated red blood cells, a second wavelength corresponding to a wavelength absorbed by unsaturated red blood cells. To determine oxygen saturation, the heart rate sensor is then configured to compare the light intensity received in response to each of the two wavelengths.

[0098] Generally speaking, the heart rate sensor can be in the form of a connected watch to, for example, measure your heart rate.

[0099] Of course, the aforementioned functionalities of the heart rate sensor can form separate sensors.

[0100] The evaluation data transmitted by the transportable evaluation systems 28 advantageously include objective fatigue levels of the operators having used these systems 28.

[0101] Preferably, this evaluation data further includes subjective fatigue levels of these operators.

[0102] In particular, each objective fatigue level is determined at least partially by the transportable evaluation system 28 from the physiological data of the operator and possibly contextual data. In certain examples, the objective fatigue levels are determined by one or more remote systems of the transportable evaluation systems 28 from, for example, the physiological data of the operators transmitted by these systems 28. This or these remote systems can form servers.

[0103] Each subjective fatigue level of the operator is entered by the operator himself via, for example, an interface of the corresponding transportable evaluation system 28.

[0104] Advantageously, the transportable systems 28 are further capable of providing general context data relating to the general context of evaluation of the operators.

[0105] This general context data includes at least one type of data chosen from the group comprising: - data relating to the operator's environment; - the operator's physiological data.

[0106] The data relating to the operator's environment are, for example, data describing the environment in which the operator's evaluation was made.

[0107] The physiological data of the operator relates to the operator himself and includes, for example, data determined by the various sensors as explained previously.

[0108] In some cases, this physiological data also includes physiological data entered by the operator via the communication interface of the corresponding transportable evaluation system 28. This data is entered, for example, by the operator following various questions relating to his general physiological state such as, for example, the duration of his sleep, the amount of naps taken, the hours of rest period(s), etc.

[0109] The general context data are for example linked to the evaluation data transmitted by the corresponding transportable evaluation system 28 by a unique session identifier.

[0110] In other words, this unique session identifier makes it possible to associate the evaluation data determined by this system 28 with the general context data which correspond to this evaluation data.

[0111] This unique session identifier may, for example, be associated with an identifier of the operator whose evaluation data is used. To do this, the general context data may include the identifier of this operator. The operator identifier may optionally be anonymized.

[0112] The database(s) 30 make it possible to provide particular context data. This particular context data comprises at least one type of data chosen from the group comprising: - data relating to the mission to be carried out by the operator; - data relating to the mission(s) carried out by the operator; - operational data relating to activities carried out by the operator other than a mission.

[0113] This particular context data corresponds for example to the flight planning carried out or to be carried out by different operators.

[0114] Data on activities other than a mission carried out by the operators includes, for example, data on their physical activities. This data comes, for example, from a sports tracking application of the operator or any other organization dealing with the operators' activities.

[0115] The activities carried out by the operator may further include, for example, in-flight or ground activities such as training, on-call duty, illness, etc.

[0116] The database(s) 30 may then belong to the airline or to any other third party organization which stores the particular context data as defined above.

[0117] The processing module 22 makes it possible to process the data acquired by the input module 21 as will be explained in more detail later.

[0118] The processing module 22 further makes it possible to generate output data which are transmitted to the output module 23.

[0119] The output module 23 makes it possible to send the data generated by the processing module 22 to any interested external system. This external system is for example connected to this output module 23 via a global or local computer network 35.

[0120] In the example of [Fig.l], such an external system comprises for example a communication interface 38 with a user such as a manager (i.e. for example Safety Manager in English) or any other superior of the operators.

[0121] This communication interface 38 comprises for example a display means such as a screen and an input means.

[0122] This input means allows, for example, the user to enter a display criterion which can also be transmitted to the input module 21 to be taken into account in the output data transmitted by the output module 23.

[0123] The determination system 10 makes it possible to implement a method 10 for determining a fatigue level and will now be described with reference to [Fig.2] presenting a flowchart of its steps.

[0124] It is initially considered that the transportable evaluation systems 28 have generated physiological data relating to a population of operators. This physiological data is used by the transportable systems 28 and / or other remote systems to generate evaluation data.

[0125] The evaluation data includes in particular the objective / subjective fatigue levels of these operators.

[0126] Advantageously, the evaluation data has been generated following one or more collection phases.

[0127] As indicated previously, each collection phase is chosen from an initial collection phase implemented before the mission, an intermediate collection phase implemented during the mission and a final collection phase implemented after the mission.

[0128] The initial collection phase, also called check-in, includes the acquisition of physiological data and mission data relating to the corresponding operator and generates an objective fatigue level from this data.

[0129] The intermediate collection phase, also called on-duty, includes a collection of different types of data such as the physiological data of the operator and data relating to the current mission. This collection, for example, is carried out by a device remote from the transportable evaluation device. Such a remote device may include a connected watch or any other mobile device worn by the operator during the mission.

[0130] The final collection phase, also called check-out, includes the collection of data generated during the mission as well as the physiological data of the operator acquired by the transportable evaluation system 28 following the mission.

[0131] In some embodiments, the intermediate collection phase is optional. In such a case, only the initial and final collection phases are implemented.

[0132] It is also considered that initially the transportable evaluation systems 28 generate the general context data associated with the evaluation data of the operators. This general context data is for example linked to the evaluation data of the corresponding operator by a unique session identifier as defined previously.

[0133] Finally, it is also considered that the database(s) 30 contain the specific context data relating to the specific context of operator evaluation.

[0134] During steps 110, 120, 130 the input module 21 acquires respectively the evaluation data from the transportable evaluation systems 28, the general context data also from these transportable evaluation systems 28 and the particular context data from the database(s) 30.

[0135] These steps 110, 120, 130 can be implemented by the input module 21 in parallel. Alternatively, at least some of these steps are implemented consecutively.

[0136] At the end of these steps, the input module 21 transmits the acquired data to the processing module 22.

[0137] During the following step 140, the processing module 22 implements the validation of the evaluation data and the general context data by applying one or more predetermined validation criteria.

[0138] These validation criteria are for example predetermined according to the nature of the data whose validity is studied. The or each validation criterion is chosen from the group comprising: - the acquired data which relate to a validated evaluation (i.e. the evaluation is validated by the transportable evaluation device 28 having collected the corresponding data); - the acquired data which relate to an identified operator (i.e. the operator has been identified by the transportable evaluation system 28 having transmitted the corresponding data and a possibly anonymized identifier is associated with the operator); - the acquired data which respect a minimum duration of the evaluation (the minimum duration of the evaluation may be set by the transportable evaluation system which transmitted the corresponding data and may include, for example, a few minutes), associated with this data; - acquired data which respects a collection phase.

[0139] In particular, with regard to compliance with the collection phase, the processing module 22 verifies that the data received correspond to those to be collected / generated during the corresponding collection phase.

[0140] To do this, the processing module 22 can, for example, verify that the natures of data transmitted correspond to those expected according to the corresponding collection phase.

[0141] As regards the minimum evaluation duration, this duration may also depend on the corresponding collection phase.

[0142] For example, this duration may be less for the initial collection phase than for the final collection phase.

[0143] When the acquired data are not validated according to one of the aforementioned criteria, the processing module 22 rejects, for example, this data from future consideration.

[0144] During the following step 150, the processing module 22 implements a pre-processing of all the acquired data. The pre-processing is for example chosen according to the nature of the acquired data.

[0145] Thus, for example, the preprocessing of the general context data comprises the implementation of at least one of the elements chosen from the group comprising: - the definition of the location of the evaluation (for example from the configuration or from the geographical coordinates of the evaluation); - the definition of the local time (calculated for example according to the location of the evaluation); - identification of a morning, normal or late session; - identification of the position occupied by the operator during his mission (for example pilot or co-pilot when the operator's mission is a flight); - extrapolation of information relating to the operator's sleep (e.g. sleep duration, bedtimes, wake-up times, nap duration, chronotype, etc.).

[0146] In particular, with regard to the identification of the morning, normal or late session, early morning or late flights are defined by the regulations (for example ORO.FTL.105, (i) and ARO.OPS.230). For the sessions, a margin of two hours before the departure of the flight is added (since the pilot arrives well before the flight) and one hour after the arrival of the flight. Therefore, the early morning slot is for example between 03:00 and 05:59, and the late slot is between 23:00 and 02:59 in local time of the operator's location.

[0147] The preprocessing of the evaluation data comprises, for example, the implementation of at least one of the elements chosen from the group comprising: - normalization of the level of fatigue (for example on the KSS scale (“Karolinska Sleepiness Scale”) ranging from 1 to 9); - normalization of the subjective fatigue level (for example according to the same KSS scale); - the identification of an objective fatigue class according to the objective fatigue level; - the identification of a subjective fatigue class according to the subjective fatigue level (for example, according to the same classes as those relating to the objective fatigue level).

[0148] The classification of the fatigue level into different classes can be carried out, for example, according to the value of the objective or subjective fatigue level. The number

[0149]

[0150]

[0151]

[0152]

[0153]

[0154]

[0155]

[0156]

[0157] of classes has for example a predetermined value which can for example be chosen between 2 and 10. Thus, for example, it is possible to choose only two fatigue classes (satisfactory and unsatisfactory) or three fatigue classes (intermediate, high, very high). For this purpose, the processing module 22 can, for example, compare the determined and possibly standardized subjective objective fatigue level with predetermined thresholds. Preprocessing of data from the particular context includes, for example, determining at least one of the elements chosen from the group comprising: - the flight operated (flight identifier, departure airport, arrival airport); - data specific to training sessions (type of mission, duration of the flight, landing time, night flight); - the period of the day of the mission (the exact hours and duration of the mission); - the type of aircraft or any other instrument / equipment used during the assignment ; - workload (e.g. degree of disruption during the mission); - activities in the days preceding the assessment; - delay or disruption during the mission; - the routes operated. Some of this data can be extracted or deduced from the databases 30 as defined previously. For example, aircraft type can be extracted from data on planned or operated commercial flights. Delays or disruptions can be extracted from data on commercial flights operated as well as weather data relating to these flights. Operated flights can be extracted from the crew schedule associated with the corresponding operator. Some of this data can be used to construct more sophisticated data, such as: - the routes operated which can be derived from the analysis of commercial flights operated; - induced delays which may arise from the analysis of data on planned and completed commercial flights. In the next step 160, the processing module 22 correlates the data acquired / determined during different collection phases relating to the same operator. For example, in some cases there is data that is acquired or de completed only during the initial collection phase and some other data which are acquired / determined only during the final collection phase.

[0158] In such a case, the processing module 22 will associate these data using the unique session identifier associated with each type of data and the operator identifier. For example, when the processing module 22 identifies the same operator identifier for two unique session identifiers corresponding respectively to an initial collection phase and a final collection phase, it can make a correlation between the data collected during these different phases.

[0159] The same applies to the intermediate collection phase.

[0160] In addition, it is possible to correlate data from several initial collection phases and several final collection phases relating to the same operator.

[0161] During the following step 170, the input module 21 acquires a time range for determining the fatigue level as well as a filtering criterion.

[0162] These data are acquired by the input module 21 following the user's interaction with the interface 38.

[0163] This interaction is carried out for example following the authentication of the user via the interface 38 and the transmission of this data to the input module 21 via the network 35.

[0164] The default time range covers, for example, all sessions. Advantageously, the user has the possibility of selecting a sub-range from this range covering all sessions, which will then be transmitted to the input module 21. This range may, for example, include specific dates or a predefined period (previous week, previous month, previous quarter, previous half-year, previous year, etc.).

[0165] The filtering criterion is for example based on general context data and / or particular context data.

[0166] This filtering criterion may comprise simple filtering (for example by mission type or aircraft type) or composite filtering (i.e. several superimposed filters such as the age of the operator and the aircraft type).

[0167] At the end of this step 170, the input module 21 transmits all of the acquired data to the processing module 22.

[0168] During the following step 190, the processing module 22 determines from all of the preprocessed data a statistical fatigue level according to the filtering criterion acquired over the acquired time range.

[0169] This level of statistical fatigue can then be presented in the form of a graph or diagram varying along the time range or representing different values ​​depending on the filtering criterion.

[0170] According to certain embodiments, the method may also comprise a step 192 which includes determining a number of operators and / or a number of routes and / or a number of evaluations corresponding to the acquired data which can be used to determine the level of statistical fatigue according to the chosen filtering criterion.

[0171] In other words, during this step, the processing module 22 analyzes the usability of the acquired data for the corresponding filtering criterion and then deduces a representative number of these usable data.

[0172] This representative number can then designate the number of operators who were evaluated to acquire this data or the number of routes carried out by these operators or the number of evaluations generated by these operators by the transportable evaluation systems 28.

[0173] In certain embodiments, the processing module 22 can also determine a confidence indicator associated with the level of statistical fatigue determined as a function of said number of operators and / or routes and / or evaluations.

[0174] Finally, during step 200, the output module 23 transmits the determined statistics level with possibly the associated confidence indicator to the interface 38 to be displayed in an appropriate form.

[0175] This appropriate form can be chosen by the user depending for example on the nature of the filtering criterion.

[0176] Some examples of application of the method according to the invention will be described below as a function of different filtering criteria.

[0177] According to a first example of application of the method, the filtering criterion consists of filtering the statistical objective / subjective fatigue level after the initial collection phase (check-in) and after the final collection phase (check-out).

[0178] In such an example, the processing module 22 calculates the following values ​​during the steps 190 and 192 described previously: - the number of sessions: this is the number of sessions over the acquired time range; - the number of operators: this is the number of different operators having carried out sessions over the acquired time range; - the number of routes: this is the number of different routes operated during the sessions over the acquired time range. This is, for example, an optional parameter calculated during said steps; - the objective fatigue levels during the initial collection phase (check-in): the fatigue levels calculated by the transportable evaluation systems 28 are, for example, classified into several classes (for example, into three classes as defined previously); - objective fatigue levels during the final collection phase (check-out): similarly, this concerns the classification of fatigue levels objectives calculated in several classes (for example in three classes); - subjective fatigue levels during the initial collection phase (check-in): idem, classification into several classes (for example into three classes); - subjective fatigue levels during the final evaluation phase (check-out): same here classification into several classes (for example into three classes).

[0179] [Fig.3] illustrates an example of a display obtained following the implementation of this example.

[0180] Thus, as shown in [Fig.3], the display firstly comprises the display of three values ​​NI, N2 and N3 which correspond respectively to the number of operators, the number of sessions and the number of routes calculated by the processing module 22.

[0181] The display further includes four diagrams D1, D2, D3 and D4. Diagram DI shows the classification of the statistical objective fatigue level of the operators during the initial collection phase (check-in).

[0182] Diagram D2 shows the classification of the statistical objective fatigue level during the final collection phase (check-out).

[0183] Diagram D3 shows the classification of the statistical subjective fatigue level of operators during the initial collection phase (check-in).

[0184] Finally, diagram D4 presents the classification of the subjective fatigue level during the final collection phase (check-out).

[0185] As illustrated in this [Fig.3], the shape and type of diagram may vary depending on the filtering criterion chosen.

[0186] Furthermore, the user also has the possibility to choose the type of diagram desired.

[0187] Finally, it is also possible to apply an additional filtering criterion to the diagrams already displayed.

[0188] Thus, for example, it is possible to refine these values ​​for example by type of aircraft, by role of the operator during the mission, by type of mission, etc.

[0189] According to a second example of application, the filtering criterion may further comprise the classification of the level of statistical fatigue during the operators' mission.

[0190] To do this, the processing module 22 can, for example, divide the mission into a plurality of sections and then determine the level of statistical fatigue for each of the sections.

[0191] Thus, for example, when the operator is a pilot or a co-pilot, it is possible to divide his mission (i.e. flight) into three sections of identical lengths or into sections based on characteristic points of the mission such as for example the end of ascent, cruise, after the start of the descent.

[0192] In such a case, the information on the level of fatigue in each of the sections presents an average value of the level of fatigue calculated continuously in these sections.

[0193] According to a third example of application, the level of statistical fatigue is calculated for different categories of operators.

[0194] These categories are determined for example according to the gender of the operator, the function of the operator during his mission, his age group, etc.

[0195] [Fig.4] illustrates an example of such a display for the different categories of operators.

[0196] In this example, the operator categories are formed by age group.

[0197] Thus, for example, the processing module 22 in this case calculates five categories of operators by age group. These categories include a first group ranging from 20 to 29 years, a second group for ages ranging from 30 to 39 years, a third group for ages ranging from 40 to 49 years, a fourth group for ages ranging from 50 to 59 years, and a fifth group for ages over 60 years.

[0198] In addition, the different categories can be calculated for the different types of fatigue level and for the different collection phases.

[0199] Thus, [Fig.4] illustrates the DI to D4 diagrams calculated for said age groups.

[0200] Diagram DI corresponds to the statistical objective fatigue level calculated by age group during the initial evaluation phase, diagram D2 corresponds to the statistical objective fatigue level by age group calculated during the final evaluation phase, diagram D3 corresponds to the statistical subjective fatigue level by age group calculated during the initial collection phase and diagram D4 corresponds to the subjective collection fatigue level by age group calculated during the final collection phase.

[0201] Each of these diagrams includes on the horizontal axis the corresponding age group and on the vertical axis the corresponding statistical fatigue level calculated on a scale varying for example from 1 to 9.

[0202] According to a fourth example of application, the statistical fatigue level is calculated by mission category.

[0203] Such a mission category may for example include the number of consecutive days of mission.

[0204] [Fig.5] illustrates an example of displaying such a statistical fatigue level.

[0205] According to this example, the categorization is done according to eight categories corresponding to the number of consecutive days of mission.

[0206] Thus, [Fig.5] illustrates the DI diagram and the corresponding D2 diagram respec tively to the statistical objective fatigue level and to the statistical subjective fatigue level depending on the number of consecutive days of mission.

[0207] Of course, many other examples of filtering criteria and superposition of different filters are also possible.

[0208] It is therefore understood that the present invention has a certain number of advantages.

[0209] First of all, the proposed solution consists of implementing a method for representing objective or subjective fatigue statistically over a time range, from different points of view.

[0210] Indeed, the solution makes it possible to present fatigue by focusing on certain points of the context captured during the evaluations.

[0211] The proposed solution has the advantage of relying on an objective or subjective state of fatigue that is contextualized and required for a population over a wide time range and not on a subjective or punctual state of fatigue that is often decorrelated from its context.

[0212] Thus, the invention makes it possible to have a global synthetic view of the statistical fatigue of the operators and thus makes it possible to plan the missions by effectively taking this fatigue into account.

Claims

Claims

1. Method for determining a statistical fatigue level relating to a population of operators, comprising the following steps: - acquisition (110) of a plurality of operator evaluation data determined from physiological data of the operators; - acquisition (120) of a plurality of general context data relating to the general context of evaluation of the operators; - acquisition (130) of a plurality of particular context data relating to the particular context of evaluation of the operators; - preprocessing (150) of all the acquired data; - acquisition (170) of a time range for determining the statistical fatigue level and acquisition (170) of a filtering criterion, the filtering criterion being based on the general context data and / or the particular context data;- determination (190) from all the preprocessed data of a statistical fatigue level according to the filtering criterion acquired over the acquired time range;

2. The method of claim 1, further comprising a step (200) of transmitting the determined statistical fatigue level for display by a display interface (38).

3. Method according to claim 1 or 2, further comprising a step (140) of validating the evaluation data and the general context data according to one or more predetermined validation criteria.

4. Method according to claim 3, in which the or each validation criterion is chosen from the group comprising: - the acquired data relates to a validated evaluation; - the acquired data relates to an identified operator; - the acquired data respects a minimum duration of the evaluation; - the acquired data respects a collection phase, each collection phase being chosen from an initial collection phase implemented before the mission, an intermediate collection phase implemented during the mission and a final collection phase implemented after the mission.

5. A method according to any preceding claim, wherein the general context data comprises at least one data type selected from the group comprising: - data relating to the operator's environment; - physiological data of the operator.

6. Method according to claim 5, in which the preprocessing of the general context data comprises the implementation of at least one of the elements chosen from the group comprising: - definition of the location of the evaluation; - definition of the local time; - identification of a morning, normal or late session; - identification of the position occupied by the operator; - extrapolation of the information relating to the sleep of the operator.

7. Method according to any one of the preceding claims, wherein the evaluation data comprises at least one type of data chosen from the group comprising: - objective fatigue level of the operator; - subjective fatigue level of the operator.

8. Method according to claim 7, wherein the preprocessing of the evaluation data comprises the implementation of at least one of the elements chosen from the group comprising: - normalization of the objective fatigue level; - normalization of the subjective fatigue level; - identification of an objective fatigue class according to the objective fatigue level; - identification of a subjective fatigue class according to the subjective fatigue level.

9. Method according to any one of the preceding claims, in which the particular context data comprises at least one type of data chosen from the group comprising: - data relating to the mission to be carried out by the operator; - data relating to the mission(s) carried out by the operator; - operational data relating to activities carried out by the operator other than a mission.

10. Method according to claim 9, in which the preprocessing of the particular context data comprises the determination of at least one of the elements chosen from the group comprising: - flight(s) operated; - data specific to the training sessions; - period of the day of the mission; - type of aircraft; - workload; - degree of disruption to activity; - activities in the days preceding the assessment; - delays or disruptions during mission(s); - routes operated.

11. Method according to any one of the preceding claims, further comprising a step of correlating (160) data acquired / determined during different collection phases relating to the same operator, each collection phase being chosen from an initial collection phase implemented before the mission, an intermediate collection phase implemented during the mission and a final collection phase implemented after the mission; advantageously, the correlation step (160) comprising the identification of the same operator identifier for at least two session identifiers associated with said acquired / determined data, corresponding to different collection phases.

12. Method according to any one of the preceding claims, further comprising for the acquired filtering criterion, a step (192) of determining a number of operators and / or a number of routes and / or a number of evaluations corresponding to the acquired data usable for determining the level of statistical fatigue according to this filtering criterion.

13. The method of claim 12, wherein the step of determining (190) the statistical fatigue level further comprises determining a confidence indicator associated with the determined statistical fatigue level, the confidence indicator being determined as a function of said number of operators and / or routes and / or evaluations.

Images