CONTROL AND MONITORING DEVICE FOR A VEHICLE

Abstract

A control and monitoring device for a vehicle, and, more particularly, to a control and monitoring device for a vehicle with a controllable device, whereby the vehicle is operated by a vehicle operator wearing a personalized wearable device. The control and monitoring device may include a vehicle management system that is adapted to send alert information to and to receive status information from the personalized wearable device via a wireless radio transmitter and receiver unit. The status information may include at least one of preferred workspace settings of the vehicle operator or health-related information about the vehicle operator. The vehicle management system may control the controllable device based on the at least one of the preferred workspace settings or the health-related information.

Claims

1. A control and monitoring device for a vehicle with a controllable device, wherein the vehicle is operated by a vehicle operator wearing a personalized wearable device, wherein the monitoring device comprises: a wireless radio transmitter and receiver unit that is adapted for communicating with the personalized wearable device of the vehicle operator; and a vehicle management system that is adapted to send alert information to the personalized wearable device via the wireless radio transmitter and receiver unit and to receive status information from the personalized wearable device via the wireless radio transmitter and receiver unit, wherein the status information comprises at least one of preferred workspace settings of the vehicle operator or health-related information about the vehicle operator, and wherein the vehicle management system controls the controllable device based on the at least one of the preferred workspace settings or the health-related information; wherein the control and monitoring device further comprises a usage monitoring system that monitors a current usage of the vehicle and communicates the current usage to the vehicle management system, wherein the vehicle management system, compares the current usage from the usage monitoring system with a planned usage and a safe domain of usage of the vehicle, and, upon a detection of a deviation of the current usage from the planned usage or upon a detection of an exceedance of the current usage beyond the safe domain of usage of the vehicle directs the wireless radio transmitter and receiver unit to send the alert information to the personalized wearable device.

2. The control and monitoring device of claim 1, wherein the controllable device comprises an adjustable workspace for the vehicle operator, wherein the status information comprises the preferred workspace settings, and wherein the vehicle management system directs adjustment of the adjustable workspace based on the preferred workspace settings.

3. The control and monitoring device of claim 2, wherein the adjustable workspace comprises a pedal, a seat, and at least one motor, and wherein the vehicle management system directs the at least one motor to adjust a position of the pedals relative to the seat based on the preferred workspace settings.

4. The control and monitoring device of claim 2, wherein the adjustable workspace comprises at least one display, and wherein the vehicle management system directs configuration of the at least one display and selects the information displayed on the at least one display based on the preferred workspace settings.

5. The control and monitoring device of claim 1, wherein the status information further comprises identifying information about the vehicle operator, and wherein the vehicle management system directs the controllable device to grant or deny the vehicle operator access to the vehicle based on the identifying information about the vehicle operator.

6. The control and monitoring device of claim 1, wherein the vehicle management system directs at least one of a vehicle operating system, a flight control computer, an automatic flight control system, or an autopilot to either accept and execute or refuse and ignore flight control inputs from the vehicle operator based on the status information from the personalized wearable device.

7. The control and monitoring device of claim 1, further comprising: a vehicle monitoring system that monitors the vehicle and sends associated monitored information about the vehicle to the vehicle management system, wherein the vehicle management system, assesses the associated monitored information from the vehicle monitoring system, and, upon a detection of a safety-critical event, directs the wireless radio transmitter and receiver unit to send the alert information to the personalized wearable device.

8. The control and monitoring device of claim 7, wherein the alert information causes the personalized wearable device to create cues in order to alert the vehicle operator about the deviation of the current usage from the planned usage or about the detection of the exceedance of the current usage beyond the safe domain of usage of the vehicle.

9. The control and monitoring device of claim 1, wherein the status information about the vehicle operator comprises the health-related information, and wherein the control and monitoring device is further adapted to determine whether the vehicle operator is unfit for safely operating the vehicle based on at least one of the health-related information or a current workload of the vehicle operator.

10. The control and monitoring device of claim 9, wherein the vehicle management system directs a vehicle operating system to initiate autonomous operation of the vehicle in response to determining that the vehicle operator is unfit for safely operating the vehicle.

11. The control and monitoring device of claim 10, further comprising: a communication device, wherein the vehicle management system informs a remote surveillance station via the communication device that autonomous operation of the vehicle has been initiated in response to determining that the vehicle operator is unfit for safely operating the vehicle.

12. The control and monitoring device of claim 9, wherein the vehicle is further operated by an additional vehicle operator wearing an additional personalized wearable device, and wherein the control and monitoring device further comprises: first and second radio frequency identification or wireless near field communication units, wherein the first radio frequency identification or wireless near field communication unit is adapted for identifying and communicating with the personalized wearable device of the vehicle operator, and wherein the second radio frequency identification or wireless near field communication unit is adapted for identifying and communicating with the additional personalized wearable device of the additional vehicle operator.

13. The control and monitoring device of claim 12, wherein the vehicle management system, in response to determining that the vehicle operator is unfit for safely operating the vehicle, directs the second radio frequency identification or wireless near field communication unit to send additional alert information to the additional personalized wearable device that causes the additional personalized wearable device to create cues in order to alert the additional vehicle operator to the fact that the vehicle operator is unfit for safely operating the vehicle.

14. A vehicle comprising the control and monitoring device of claim 1.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Embodiments are outlined by way of example in the following description with reference to the attached drawings. In these attached drawings, identical or identically functioning components and elements are labeled with identical reference numbers and characters and are, consequently, only described once in the following description.

[0054] FIG. 1 is a diagram of an illustrative control and monitoring device for a vehicle with a controllable device and a vehicle operator who is approaching the vehicle and wearing a personalized wearable device in accordance with some embodiments,

[0055] FIG. 2 is a diagram of an illustrative control and monitoring device with a vehicle management system for a vehicle that receives information including preferred workspace settings from a personalized wearable device and directs adjustment of an adjustable workspace in the vehicle based on the preferred workspace settings in accordance with some embodiments,

[0056] FIG. 3 is a diagram of an illustrative portion of an adjustable workspace of a vehicle and two illustrative personalized wearable devices that communicate with respective radio frequency identification (RFID) or wireless near field communication (NFC) units in accordance with some embodiments,

[0057] FIG. 4 is a diagram of an illustrative control and monitoring device for a vehicle that directs a vehicle management system to create cues for the vehicle operator in accordance with some embodiments,

[0058] FIG. 5 is a diagram of an illustrative control and monitoring device for a vehicle that initiates autonomous operation of the vehicle and informs a remote surveillance station that autonomous operation of the vehicle has been initiated in response to determining that the vehicle operator is unfit for safely operating the vehicle in accordance with some embodiments,

[0059] FIG. 6 is a flowchart showing illustrative operations that a control and monitoring device performs based on status information from a personalized wearable device in accordance with some embodiments,

[0060] FIG. 7A is a flowchart showing illustrative operations that a control and monitoring device performs based on identifying information from a personalized wearable device in accordance with some embodiments,

[0061] FIG. 7B is a flowchart showing illustrative operations that a control and monitoring device performs based on preferred workspace settings from a personalized wearable device in accordance with some embodiments, and

[0062] FIG. 7C is a flowchart showing illustrative operations that a control and monitoring device performs based on health-related information about a vehicle operator from a personalized wearable device in accordance with some embodiments.

DETAILED DESCRIPTION OF THE INVENTION

[0063] FIG. 1 is a diagram of an illustrative control and monitoring device 120 for a vehicle 100 with a controllable device and a vehicle operator 110 who is approaching the vehicle 100 and wearing a personalized wearable device 111.

[0064] Vehicle 100 is exemplarily illustrated as an aircraft, in particular as a rotorcraft and, more particularly, as a helicopter. Thus, for purposes of simplicity and clarity, the vehicle 100 may be hereinafter referred to as the “helicopter” 100. The control and monitoring device 120 is, however, not limited for the use with helicopters and can likewise be used with any other vehicle, independent of a particular configuration thereof.

[0065] Vehicle 100 may be operated by a vehicle operator 110. If vehicle 100 is a helicopter or any other aircraft then vehicle operator 110 may be a pilot. Thus, for purposes of simplicity and clarity, the vehicle operator 110 may be hereinafter referred to as the “pilot” 110 if the vehicle is a helicopter or any other type of aircraft.

[0066] Pilot 110 may wear a personalized wearable device 111. In the scenario in which helicopter 100 has more than one pilot 110, each pilot 110 may have a personalized wearable device 111, if desired. The personalized wearable device 111 may include a processing unit 112, an identification unit 113, and a wireless communication unit 114.

[0067] The identification unit 113 is used to identify the vehicle driver 110 to the personalized wearable device 111 by individual or biometric characteristics. For instance, the identification unit may include a fingerprint sensor to identify the vehicle driver by his finger print.

[0068] By way of example, personalized wearable device 111 may include a data storage unit (e.g., data storage unit 116 of FIGS. 4 and 5). The data storage unit may store status information. If desired, personalized wearable device 111 may be associated with an external data storage unit (e.g., data storage unit 109 of the control and monitoring device of the vehicle).

[0069] By way of example, personalized wearable device 111 may include a cue generation unit 118, e.g., the cue generation unit 118 of FIG. 4.

[0070] By way of example, personalized wearable device 111 may include a display 404 according to FIG. 4. The display 404 may be a touch screen to enable input from the vehicle driver to the wearable device.

[0071] By way of example, personalized wearable device 111 may include a health and workload sensor unit 500 according to FIG. 5.

[0072] As an example, the status information may include preferred workspace settings of the vehicle operator 110. As another example, the status information may include health-related information about the vehicle operator 110. As yet another example, the status information may include preferred workspace settings of the vehicle operator 110 and health-related information about the vehicle operator 110.

[0073] Illustratively, the helicopter 100 comprises a fuselage 101 with a cabin 102 and a tail boom 103, which may comprise a vertical tail plane, a suitable counter-torque device, such as a tail rotor, which is configured to provide counter-torque during operation in order to balance the helicopter 100 in terms of yaw, a horizontal stabilizer, a bumper and so on.

[0074] As shown in FIG. 1, helicopter 100 may have a main rotor 104 with rotor blades that are mounted to a rotor mast. While the main rotor 104 may be controlled by the vehicle operator 110 with his hands via cyclic and collective sticks, the tail rotor may be controlled with his feet via pedals as shown in FIGS. 2 and 4. Helicopter 100 may include a landing gear 105 that is illustratively shown to be a wheel-type landing gear. However, any other type of landing gear such as a skid type landing gear may be used instead.

[0075] By way of example, vehicle 100 may include a controllable device 130. Controllable device 130 may be any device that is installed in vehicle 100 and that can be controlled to execute specific tasks. As an example, controllable device 130 may be an electric motor that may be controlled to adjust a workspace for the vehicle operator 110 as shown in FIG. 2. As another example, controllable device 130 may be a display that may be configured for the vehicle operator 110 as shown in FIG. 3.

[0076] Illustratively, control and monitoring device 120 may include a wireless radio transmitter and receiver unit 106. The wireless radio transmitter and receiver unit 106 may be adapted for communicating with the personalized wearable device 111 of the vehicle operator 110. For example, wireless radio transmitter and receiver unit 106 may be adapted for communicating with the wireless communication unit 114 of the personalized wearable device 111.

[0077] By way of example, control and monitoring device 120 may include a data storage unit 109. Data storage unit 109 may store data indicative of a safe operation of the vehicle 100.

[0078] Illustratively, control and monitoring device 120 may include a usage monitoring system 108. Usage monitoring system 108 may monitor a current usage of the vehicle 100.

[0079] Control and monitoring device 120 may include a vehicle management system 200. Vehicle management system (VMS) 200 may include any onboard system that manages the vehicle's internal capabilities to accomplish mission goals. Thus, vehicle management system 200 may provide several functions.

[0080] As an example, vehicle management system 200 may monitor sensors and collect general information about the vehicle 100. If desired, vehicle management system 200 may retrieve the data indicative of a safe operation of the vehicle 100 from the data storage unit 109 and compare the data with the associated general information about the vehicle 100 to detect any safety-critical event. Vehicle management system 200 may generate alert information based on a detected safety-critical event, if desired.

[0081] As another example, usage monitoring system 108 may communicate the current usage of the vehicle 100 to the vehicle management system 200. The vehicle management system 200 may compare the current usage from the usage monitoring system 108 with a planned usage and a safe domain of usage of the vehicle 100, e.g., the certified flight domain including attitude, altitude, air speed, etc. for given outside air temperature (OAT), air density, loading condition, etc.

[0082] Upon a detection of a deviation of the current usage from the planned usage or upon a detection of an exceedance of the current usage beyond the safe domain of usage, the vehicle management system 200 may generate alert information based on the deviation of the current usage from the planned usage or based on the exceedance of the current usage beyond the safe domain of usage of the vehicle 100, if desired.

[0083] Vehicle management system 200 may be adapted to send the alert information via the wireless radio transmitter and receiver unit 106 to the personalized wearable device 111. In other words, vehicle management system 200 may direct the wireless radio transmitter and receiver unit 106 to send a signal 115 that includes the alert information to the personalized wearable device 111.

[0084] In response to receiving the alert information from the vehicle management system 200, the personalized wearable device 111 may create cues for the vehicle operator 110. The cues may be based on the alert information with the goal of quickly informing the vehicle operator 110 of the nature of the problem for which the alert information was issued. For example, each problem may be associated with a different cue.

[0085] The personalized wearable device 111 may create different types of cues by means of different cue generation units 118. As an example, the personalized wearable device 111 may create haptic cues such as vibrations, i.e., mechanical oscillations. The vibrations may be a sequence of vibrations of different lengths, frequency and/or intensity/amplitude such that every problem for which the alert information was issued is associated with a different characteristic sequence of vibrations.

[0086] As another example, the personalized wearable device 111 may create haptic cues based on mechanical stimulation like vibrations or local mechanical pressure on the skin, electrical stimulation of the skin, or thermal stimulation of the skin of the vehicle operator 110.

[0087] As another example, the personalized wearable device 111 may create visual cues such as flashes on a screen, blinking lights, or any other visual cues. The visual cues may be a sequence of flashes of different lengths and/or color such that every problem for which the alert information was issued is associated with a different visual cue. If desired, the visual cues may be a message on a display.

[0088] As yet another example, the personalized wearable device 111 may create aural cues such as alarms sounds, beeps, or clear voice announcements. The aural cues may be a sequence of alarm sounds or beeps of different lengths, frequency, and/or loudness/volume such that every problem for which the alert information was issued is associated with a different aural cue.

[0089] If desired, the personalized wearable device 111 may create any combination of haptic cues and/or visual cues and/or aural cues.

[0090] Illustratively, vehicle management system 200 may be adapted to receive status information from the personalized wearable device 111 via the wireless radio transmitter and receiver unit 106. For example, personalized wearable device 111 may send a signal 115 that includes status information of the vehicle operator 110 via wireless communication unit 114 and wireless radio transmitter and receiver unit 106 to vehicle management system 200.

[0091] By way of example, the status information may include identifying information about the vehicle operator 110. If desired, the vehicle management system 200 may direct the controllable device 130 to grant or deny the vehicle operator 110 access to the vehicle 100 based on the identifying information about the vehicle operator 110. For example, the controllable device 130 may direct electric motors to unlock or lock the doors of vehicle 100 to grant or deny physical access to the vehicle 110.

[0092] Illustratively, vehicle management system 200 may grant or deny access to operational commands of the vehicle. In the scenario in which the vehicle 100 is an aircraft, vehicle management system 200 may grant or deny access to the avionics system and/or allow to operate the aircraft by command inputs and/or perform a pre-flight check of the aircraft.

[0093] Illustratively, vehicle management system 200 may grant or deny access to data 109 stored in the vehicle 100.

[0094] Vehicle 100 may be operated by different types of vehicle operators 110. For example, in case of an aircraft, vehicle 100 may be operated by maintenance personnel, by cabin crew, or by one or more pilots, just to name a few. If desired, the vehicle management system 200 may grant or deny access to certain data of data 109 based on the type of vehicle operator 110.

[0095] Illustratively, different identifying information may be associated with different types of vehicle operators 110. For example, the vehicle management system 200 may accept or ignore operational command inputs and grant or deny the vehicle operator 110 different types of access rights to data stored in the vehicle, e.g., read only access, write access, etc.

[0096] Illustratively, based on the identifying information of a vehicle operator 110 who is registered as maintenance personnel but not as a pilot cleared for flight, the vehicle management system 200 may grant read access to data 109 stored in the vehicle 100 for maintenance purposes but ignore operational command inputs and deny write access to any data 109 stored in the vehicle 100 that is relevant during flight.

[0097] Consider the scenario in which the status information includes at least one of preferred workspace settings of the vehicle operator 110 or health-related information about the vehicle operator 110. In this scenario, the vehicle management system 200 may control the controllable device 130 based on the at least one of the preferred workspace settings or the health-related information.

[0098] FIG. 2 is a diagram of an illustrative control and monitoring device 120 with a vehicle management system 200 for a vehicle 100. Vehicle 100 may have a controllable device 130 that includes an adjustable workspace 210.

[0099] Vehicle management system 200 may receive status information from a personalized wearable device 111. For example, the personalized wearable device 111 may include a data storage unit 116. Data storage unit 116 may store status information of the vehicle operator 110.

[0100] Personalized wearable device 111 may be associated with a vehicle operator 110. Illustratively, the status information may include preferred workspace settings of the vehicle operator 110. In response to receiving the preferred workspace settings, vehicle management system 200 may direct adjustment of the adjustable workspace 210 in the vehicle 100 based on the preferred workspace settings.

[0101] If desired, vehicle management system 200 may direct adjustment of the adjustable workspace 210 as soon as the vehicle operator 110 has been identified and/or has registered with the vehicle management system 200 based on the status information.

[0102] Illustratively, the adjustable workspace 210 may include pedals 204 or any other device that the vehicle operator controls with the feet when operating the vehicle, a seat 203 or a stool or a back rest or an arm rest as part of the seat 203 or any other device that the vehicle operator rests on when operating the vehicle 100, at least one display, one or more rearview mirrors, or any other device that the vehicle operator 110 observes when operating the vehicle 100, speakers, headsets, or any other device that the vehicle operator 110 listens to when operating the vehicle, handles, cyclic center stick or side sticks and collective sticks, or any other device that the vehicle operator controls with the hands when operating the vehicle, etc.

[0103] By way of example, pedals 204, handles, displays, or any other device within the adjustable workspace 210 may be associated with seat 203 or any other device that the vehicle operator rests on when operating the vehicle.

[0104] At least some devices of the adjustable workspace 210 may be adjustable. For example, pedals 204 and/or seat 203 may be adjustable. Pedals 204 and/or seat 203 may have one or more adjustable setting.

[0105] As an example, the adjustable settings of the seat 203 may include the inclination of the back rest of the seat 203, the height of the back rest of the seat 203, the height and/or advancement of an optional head rest of the seat 203, the inclination of the seat surface of the seat 203, the height of the seat surface of the seat 203, the advancement of the seat 203 relative to any controls, the height and/or advancement of an optional arm rest of the seat 203, etc.

[0106] Illustratively, the height of the seat surface of seat 203 (e.g., from the floor) may be adjusted for a correct line of sight of the vehicle operator 110 by accommodating and adapting to the height of the vehicle operator's 110 upper body. Illustratively, the height of the seat surface of seat 203 may be adjusted such that the vehicle operator 110 has a desired view at the instrument panel and through the windows of the vehicle 100.

[0107] By way of example, the position of the seat surface of seat 203 in flight direction or the inclination of the back rest of seat 203 may be adjusted such that the vehicle operator 110 may easily reach all the instruments and commands (e.g., instrument panels, switch buttons, knobs, touchscreens, etc.) by accommodating and adapting to the length of the vehicle operator's 110 arms.

[0108] As another example, the adjustable settings of the pedals 204 may include the position of the pedals 204 relative to the seat 203 in order to accommodate the length of the legs of the vehicle operator 110, the distance of the pedals 204 from each other, the protrusion of the individual pedals 204 from the floor, etc.

[0109] Pedals 204 and/or seat 203 may be adjustable by a motor 201. Motor 201 may be an electric motor. A separate motor 201 may be associated with each different adjustable setting. If desired, one motor 201 may perform more than one adjustable setting (e.g., via a gearbox or screw-nut mechanism).

[0110] Vehicle management system 200 may direct the motor 201 to adjust a position of the pedals 204 relative to the seat 203 based on the preferred workspace settings. For example, vehicle management system 200 may direct motor 201 to perform a movement 205 of the pedals 204, thereby adjusting the protrusion of the pedals 204 from the floor, i.e., the vertical distance of the pedals 204 from seat 203, and/or the advancement of the pedals 204, i.e., the horizontal distance of the pedals 294 from the seat 203 in order to accommodate the length of the legs of the vehicle operator.

[0111] Vehicle management system 200 may direct the motor 201 to adjust a position of the seat 203 based on the preferred workspace settings. For example, vehicle management system 200 may direct motor 201 to perform a movement 202 of the seat 203, thereby adjusting the back rest, the head rest, and/or the seat surface of the seat 203.

[0112] Illustratively, adjustable workspace 210 may include adjustable handles or grips 431 and vehicle management system 200 may direct motor 201 to adjust a position of the handles. For example, motor 210 may adjust the position of the handles relative to the seat 203.

[0113] Illustratively, adjustable workspace 210 may include adjustable arm rests and vehicle management system 200 may direct motor 201 to adjust a position of the arm rest. For example, motor 210 may adjust the position of the arm rest relative to the seat 203 and/or cyclic center stick or side sticks and collective stick that the vehicle operator uses to operate the vehicle in order to accommodate the size of the body, length of the arms, the hand and fingers of the vehicle operator.

[0114] In case of more than one vehicle operator: individual settings for each vehicle operator, i.e., for each vehicle operator the individual settings can be adjusted independently based on the preferred settings stored in the corresponding personalized wearable device of each individual vehicle operator.

[0115] If desired, adjustable workspace 210 may include at least one display. FIG. 3 is a diagram of an illustrative portion of an adjustable workspace 210 of a vehicle (e.g., helicopter 100 of FIG. 1).

[0116] As shown, the vehicle may provide at least two workspaces, a first workspace for vehicle operator 110 and a second workspace for vehicle operator 300. Each vehicle operator 110, 300 may have a personalized wearable device 111, 301. For example, vehicle operator 110 may have personalized wearable device 111, and vehicle operator 300 may have personalized wearable device 301.

[0117] If desired, the vehicle may provide only one workspace or more than two workspaces. A vehicle operator may be associated with each workspace, and each vehicle operator may be associated with a personalized wearable device.

[0118] Each workspace may include a radio frequency identification (RFID) or wireless near field communication (NFC) unit 304, 305. For example, the first workspace may have RFID or wireless NFC unit 304 that is used to identify the personalized wearable device 111 of the vehicle operator 110, and the second workspace may have RFID or wireless NFC unit 305 that is used to identify the personalized wearable device 301 of the second vehicle operator 300.

[0119] As a preferred embodiment, the respective RFID or wireless NFC unit 304, 305 may have a range that is limited to the respective first and second workspaces. In other words, RFID or wireless NFC unit 304 cannot communicate with personalized wearable device 301 that is located in the second workspace, and the RFID or wireless NFC unit 305 cannot communicate with personalized wearable device 111 that is located in the first workspace. By limiting the range of the first and second RFID or wireless NFC unit 304, 305 to the corresponding first and second workspace dedicated to the first and second vehicle operator, it is assured that the personalized wearable devices 111, 301 of the first and second vehicle operators 110, 300 can be safely distinguished without ambiguity or the risk of confusion.

[0120] Illustratively, the RFID or wireless NFC unit 304 may receive status information that includes preferred workspace settings of vehicle operator 110 from personalized wearable device 111, and RFID or wireless NFC unit 305 may receive status information that includes preferred workspace settings of vehicle operator 300 from personalized wearable device 301.

[0121] As an alternative, the wireless radio transmitter and receiver unit 106 may receive status information that includes preferred workspace settings of both vehicle operator 110 from personalized wearable device 111, and of vehicle operator 300 from personalized wearable device 301 after the individualized wearable devices have each been initially identified by RFID/NFC.

[0122] As shown in FIG. 3, the portion of the adjustable workspace may include displays 302, 303, 306, 307, and 308. If desired, the displays 302, 303, 306, 307, 308 may be arranged on at least two different instrument panels or consoles 309, 310. For example, displays 302, 303, and 308 may be arranged on the main instrument panel 309, while displays 306 and 307 are arranged on the center console 310. In a preferred embodiment, the at least two different instrument panels or consoles 309, 310 could have different size, position, spatial orientation and accessibility towards the vehicle operator.

[0123] However, it should be noted that any number of displays can be arranged on any number of screens if desired for a certain vehicle configuration. As an example, each display may be arranged on a separate screen. As another example, all displays may be arranged on a single screen.

[0124] Illustratively, vehicle management system 200 may be adapted to receive status information from the respective personalized wearable devices 111, 301 via the respective RFID or wireless Near Field Communication (NFC) unit 304, 305. Vehicle management system 200 may distinguish between first status information received from personalized wearable device 111 via RFID or wireless Near Field Communication (NFC) unit 304 and second status information received from personalized wearable device 301 via RFID or wireless Near Field Communication (NFC) unit 305.

[0125] First status information may include first preferred workspace settings of vehicle operator 110, while second status information may include second preferred workspace settings of vehicle operator 300.

[0126] Vehicle management system 200 may include a display controller 107. Vehicle management system may, through display controller 107, direct configuration of the displays that are associated with the first workspace of vehicle operator 110 (e.g., displays 302, 306, 308) according to the first preferred workspace settings and configuration of the displays that are associated with the second workspace of vehicle operator 300 (e.g., displays 303, 307) according to the second preferred workspace settings.

[0127] As an example, vehicle management system 200 may determine the visual design of the different displays by selecting the brightness, contrast, luminance, color, and/or size of the different displays based on the preferred workspace settings. As another example, vehicle management system 200 may select the information displayed on the respective displays based on the preferred workspace settings, e.g., navigation map data, vehicle configuration or information dedicated to different systems like fuel system, hydraulic system, external cameras etc. As yet another example, vehicle management system 200 may determine the arrangement of the information on the respective displays based on the preferred workspace settings.

[0128] FIG. 4 is a diagram of an illustrative control and monitoring device 120 for a vehicle 100 that directs a vehicle management system 200 to create cues 400 for the vehicle operator 110 in accordance with some embodiments.

[0129] Illustratively, control and monitoring device 120 may include a vehicle monitoring system 410. Vehicle monitoring system 410 may monitor the vehicle 100. For example, the vehicle monitoring system 410 may include at least one sensor 402, 403.

[0130] Illustratively, the vehicle monitoring system 410 may monitor installed equipment in vehicle 100 and the use of the equipment. For example, if vehicle 100 is an aircraft, vehicle monitoring system 410 may monitor engines 413, gearbox limitations, limits of structural loads, fuel level, the status of the landing gear, hydraulics, avionics, air data (e.g., speed, altitude, etc.), navigational data (e.g., position, course, etc.), operation of the aircraft (e.g., air speed with landing gear extended or external installations such as loads in place), or the environment of the aircraft (e.g., other air traffic, etc.), just to name a few.

[0131] Consider the scenario in which sensor 403 monitors the engine of vehicle 100. For example, sensor 403 may monitor the temperature of the engine 413, the oil pressure, or the revolutions per minute of the engine, just to name a few. In this scenario, sensor 403 may send the associated monitored information about the engine to engine control unit 401, which may process and/or forward the information to vehicle management system 200.

[0132] Vehicle management system 200 may assess the associated monitored information from the vehicle monitoring system 410. For example, the control and monitoring device 120 may include a data storage unit 109 that stores data indicative of a safe operation of the vehicle 100 (e.g., a safe engine temperature, or a safe oil pressure, sufficient fuel reserve, just to name a few).

[0133] Vehicle management system 200 may retrieve the data indicative of a safe operation of the vehicle 100 from the data storage unit 109 and compare the retrieved data with the associated information from the engine control unit 401 to detect any safety-critical event.

[0134] Illustratively, the control and monitoring device 120 may include a usage monitoring system (e.g., usage monitoring system 108 of FIG. 1). The usage monitoring system may monitor a current usage of the vehicle 100 and communicate the current usage to the vehicle management system 200. The vehicle management system 200 may compare the current usage from the usage monitoring system with a planned usage and a safe domain of usage of the vehicle 100 to detect a deviation of the current usage from the planned usage or to detect an exceedance of the current usage beyond the safe domain of usage of the vehicle 100.

[0135] Upon a detection of a safety-critical event, upon a detection of a deviation of the current usage from the planned usage, or upon a detection of an exceedance of the current usage beyond the safe domain of usage of the vehicle, vehicle management system 200 may generate associated alert information.

[0136] If desired, vehicle management system 200 may register all alert information in a log book. The log book may be stored in data storage unit 109 as part of the vehicle 100 and/or in data storage unit 116 as part of the personalized wearable device 111.

[0137] Vehicle management system 200 may alert the vehicle operator 110 of the occurrence of the event that triggered the generation of the alert information. For example, vehicle management system 200 may via a vehicle operating system 501 direct a vibrating device 430 to provide tactile cues 430 (e.g., via flight control interceptors, handles or the grip of the cyclic or collective sticks 431), via a channel selector 460 direct a display 440 or other visual instruments to provide visual cues 406 (e.g., in the form of alert information or flashing or blinking lights or messages), and/or via the channel selector 460 direct one or more speakers 450 or headphones to provide aural cues 407 (e.g., in the form of alert messages or sounds) to the vehicle operator 110.

[0138] Illustratively, vehicle management system 200 may via the channel selector 460 direct the wireless radio transmitter and receiver unit 106 to send the alert information to the personalized wearable device 111 of vehicle operator 110. By way of example, personalized wearable device 111 may include or be associated with data storage unit 116. Data storage unit 116 may store all received alert information in data storage unit 116, if desired.

[0139] Personalized wearable device 111 may provide cues 400 to the vehicle operator 110. For example, based on the alert information that the vehicle management system 200 sends to the personalized wearable device 111 via the channel selector 460 and the wireless radio transmitter and receiver unit 106, the personalized wearable device 111 may provide cues 400 in form of tactile cues (e.g., mechanical stimulation like vibrations or local mechanical pressure on the skin, electric stimulation of the skin, thermal stimulation of the skin, etc.), visual cues (e.g., flashing of display 404, a text message on the display, etc.) and/or aural cues (e.g., sounding of an alarm, announcement of the safety-critical event, etc.), or any combination thereof.

[0140] Generating cues with the personalized wearable device 111 in addition to the cues provided by the vehicle 100 increases the number of communication channels between the vehicle 100 and the vehicle operator 110 and improves the situational awareness of the vehicle operator 110.

[0141] A different characteristic cue may be provided for each associated different problem for which an alert information was issued. Thereby, ambiguity between cues and different problems may be avoided and the vehicle operator 110 may easily identify the source of the problem based on the cue characteristics.

[0142] In particular, different channels of perception can be used to distinguish between messages of different criticality, e.g., “nice to have” information may be separated from safety related alerts that require immediate action of the vehicle operator 110 to ensure the safety or integrity of the vehicle 100 based on the channel of perception used by the cue characteristics.

[0143] Illustratively, the vehicle management system 200 may communicate alerts related to flight control inputs of the vehicle operator via tactile cue device 430 linked to a flight control inceptor of the vehicle 431, e.g., cyclic, collective sticks or pedals. As an example, the tactile cue device 430 may create soft or hard stops of the pilot force feel on short or long pole sticks, sidesticks, pedals or throttle levers 431.

[0144] In a preferred embodiment, alerts not related to flight control inputs could be communicated to the vehicle operator via cues of the personalized wearable device 111 in order to avoid interference with flight control inputs.

[0145] Illustratively, personalized wearable device 111 may monitor the health status and workload of vehicle operator 110. If desired, personalized wearable device 111 may capture health-related information about the vehicle operator 110 and store the health-related information in data storage unit 116.

[0146] For example, personalized wearable device 111 may be able to assess physiological and/or bio indicators of the vehicle operator 110 such as the vehicle operator's heart rate, electrocardiogram, sweating/electrical conductivity of the skin, body/skin temperature, blood oxygen saturation, blood pressure, etc.

[0147] Personalized wearable device 111 may send health-related information about the vehicle operator 110 together with other status information to the control and monitoring device 120. If desired, personalized wearable device 111 may only send health-related information about the vehicle operator 110 to the control and monitoring device 120 when the vehicle operator 110 is unfit for operating vehicle 100.

[0148] The assessment whether the vehicle operator 110 is unfit for operating vehicle 100 may be made by the personalized wearable device 111 and/or the control and monitoring device 120 based on the health-related information. In response to determining that the vehicle operator 110 is unfit for operating vehicle 100, control and monitoring device 120 may initiate autonomous operation of the vehicle 100.

[0149] FIG. 5 is a diagram of an illustrative control and monitoring device 120 for a vehicle 100 that initiates autonomous operation of the vehicle 100. For example, personalized wearable device 111 may include a workload and health sensor 500. Personalized wearable device 111 may send signals 115 with status information via wireless radio transmitter and receiver unit 106 to vehicle management system 200 of control and monitoring device 120.

[0150] Illustratively, the status information that the vehicle management system 200 of the control and monitoring device 120 receives via the wireless radio transmitter and receiver unit 106 from the personalized wearable device 111 may include health-related information and/or a current workload of the vehicle operator 110.

[0151] If desired, the control and monitoring device 120 may be adapted to determine whether the vehicle operator 110 is unfit for safely operating the vehicle 100 based on at least one of the health-related information or the current workload of the vehicle operator 110. In response to determining that the vehicle operator 110 is unfit for safely operating vehicle 100, the vehicle management system 200 may direct a vehicle operating system 501 to initiate autonomous operation of the vehicle 100.

[0152] If desired, vehicle management system 200 may ignore command inputs from the vehicle operator 110 and refuse any modifications of avionics data or changes in settings initiated by the vehicle operator 110 in response to determining that the vehicle operator 110 is unfit for safely operating vehicle 100.

[0153] Control and monitoring device 120 may inform a remote surveillance station 504, 505 that autonomous operation of the vehicle 100 has been initiated. As an example, consider the scenario in which the vehicle 100 is an aircraft and the vehicle operating system an automatic flight control system (AFCS). In this scenario, control and monitoring device 120 may include a communication device 502, and the vehicle management system 200 may inform a control tower 504 and/or an air traffic control 505 on the ground 503 via the communication device 502 that the automatic flight control system (AFCS) 501 of the aircraft 100 has taken over control of the aircraft 100 in response to determining that the vehicle operator 110 is unfit for safely operating the vehicle 100.

[0154] As another example, consider the scenario in which the vehicle 100 is operated by vehicle operator 110 and an additional vehicle operator (e.g., additional vehicle operator 300 of FIG. 3) wearing an additional personalized wearable device (e.g., additional personalized wearable device 301 of FIG. 3) is on-board vehicle 100. Consider further that the control and monitoring device 120 includes first and second wireless NFC units (e.g., RFID or wireless NFC units 304, 305 of FIG. 3). The first RFID or wireless NFC unit may be adapted for identifying and communicating with the personalized wearable device 111 of the vehicle operator 110, and the second RFID or wireless NFC unit may be adapted for identifying and communicating with the additional personalized wearable device of the additional vehicle operator.

[0155] For the purpose of identification, RFID or wireless NFC need to correctly identify the respective wearable devices 111, 301 of the respective vehicle operators 110, 300 without ambiguity. RFID or wireless NFC units 304, 305 may, thanks to the limited range of the wireless communication, correctly allocate the respective wearable devices 111, 301 to the right and left seat.

[0156] In this scenario, the vehicle management system 200, in response to determining that the vehicle operator 110 is unfit for safely operating the vehicle 100, may direct the second wireless limited range communication unit to send additional alert information to the additional personalized wearable device. The additional alert information may cause the additional personalized wearable device to create cues in order to alert the additional vehicle operator to the fact that the vehicle operator 110 is unfit for safely operating the vehicle 100.

[0157] For example, the additional wearable device may vibrate to draw the attention of the additional vehicle operator 300 to the fact that the vehicle operator 110 is unfit for safely operating the vehicle 100.

[0158] In case of two vehicle operators 110, 300, the vehicle management system 200 may ignore the command inputs by the vehicle operator who is unfit to operate the vehicle 100 and only consider and follow command inputs by the other vehicle operator as long as the other vehicle operator remains healthy and fit to operate the vehicle 100.

[0159] FIG. 6 is a flowchart 600 showing illustrative operations that a control and monitoring device may perform based on status information from a personalized wearable device in accordance with some embodiments.

[0160] During operation 610, the control and monitoring device may, with a vehicle management system, receive a status signal from a personalized wearable device via a wireless radio transmitter and receiver unit, wherein the status signal comprises status information about a vehicle operator.

[0161] For example, vehicle management system 200 of FIG. 2 may receive signals 115 with status information about vehicle operator 110 from the personalized wearable device 111 via the wireless radio transmitter and receiver unit 106. If desired, the status information may include at least one of preferred workspace settings of the vehicle operator 110 or health-related information about the vehicle operator 110.

[0162] During operation 620, the control and monitoring device may, with the vehicle management system, control a controllable device based on the status information.

[0163] For example, the status information may include preferred workspace settings of the vehicle operator 110 of FIG. 2 and the vehicle management system 200 may control a controllable device 130 (e.g., motor 201) based on the preferred workspace settings to adjust a position of pedals 204.

[0164] FIG. 7A is a flowchart 710 showing illustrative operations that a control and monitoring device may perform based on identifying information from a personalized wearable device in accordance with some embodiments.

[0165] During operation 720, the control and monitoring device may use a vehicle management system to receive a status signal from a personalized wearable device that comprises identifying information of a vehicle operator.

[0166] For example, control and monitoring device 120 of FIG. 1 may use vehicle management system 200 to receive a status signal via wireless radio transmitter and receiver unit 106 from personalized wearable device 111. The status signal may include identifying information of vehicle operator 110.

[0167] During operation 730, the control and monitoring device may use the vehicle management system to grant or deny the vehicle operator access to the vehicle based on the identifying information.

[0168] Illustratively, during operation 730, the control and monitoring device may use the vehicle management system to grant or deny the vehicle operator physical access to the vehicle.

[0169] For example, control and monitoring device 120 of Figure may use vehicle management system 200 to grant or deny the vehicle operator 110 physical access to vehicle 100 (e.g., by locking or unlocking vehicle doors) based on the identifying information that the vehicle management system 200 has received from personalized wearable device 111.

[0170] Illustratively, during operation 730, the control and monitoring device may use the vehicle management system to grant or deny the vehicle operator access to the vehicle systems such as avionics system, maintenance system, health and usage monitoring system (HUMS), flight management system (FMS) or flight control system (FCS) based on the identifying information.

[0171] Illustratively, based on the identifying information of the vehicle operator, the control and monitoring device may use the vehicle management system to grant or deny the vehicle operator the right to read data, in particular to read vehicle settings, to read maintenance data, and/or to read usage data from the HUMS.

[0172] For example, if the vehicle operator based on his identifying information is correctly identified as maintenance personnel, he could be granted access to read data.

[0173] In addition, based on the identifying information of vehicle operator, the control and monitoring device may use the vehicle management system to accept or refuse command inputs from the vehicle operator.

[0174] As an example, the control and monitoring device may use the vehicle management system to command the avionics system to accept or refuse that the vehicle operator changes vehicle settings.

[0175] As another example, the control and monitoring device may use the vehicle management system to command the flight management system (FMS) to accept or refuse that the vehicle operator changes flight management data, flight planning data, or navigation data.

[0176] As yet another example, the control and monitoring device may use the vehicle management system to command the flight control computer (FCC), the automatic flight control system (AFCS), the autopilot (AP), and the engine control system to refuse and ignore any flight control inputs by the vehicle operator.

[0177] Illustratively, flight control computers (FCC) are employed to compute the flight laws and control the flight control servos and actuators of fly-by-wire (FbW) aircraft.

[0178] By way of example, the automatic flight control system (AFCS), autopilot (AP), and engine control system compute the flight laws and control the flight control servos and actuators of the aircraft via classical mechanical flight control kinematics.

[0179] Illustratively, if the vehicle operator based on his identifying information is correctly identified as an authorized vehicle operator, he would be granted access to enter command inputs, in particular to change vehicle settings in the avionics system, to change flight management data, flight planning data or navigation data in the flight management system (FMS), and to accept and execute all flight control inputs by the pilot in the flight control computer (FCC), the automatic flight control system (AFCS), the autopilot (AP), and the engine control system.

[0180] If desired, in addition to the correct identifying information of the vehicle operator, the vehicle operator's command inputs could still be refused and ignored during if the vehicle operator is considered unfit for safely operating the vehicle based on the health-related information received from the personalized wearable device 301.

[0181] FIG. 7B is a flowchart 715 showing illustrative operations that a control and monitoring device may perform based on preferred workspace settings from a personalized wearable device in accordance with some embodiments.

[0182] During operation 740, the control and monitoring device may use a vehicle management system to receive a status signal from a personalized wearable device that comprises preferred workspace settings of a vehicle operator.

[0183] For example, control and monitoring device 120 of FIG. 2 may use vehicle management system 200 to receive a status signal 115 from personalized wearable device 111 via wireless radio transmitter and receiver unit 106. If desired, the status signal 115 may include status information, whereby the status information comprises preferred workspace settings of vehicle operator 110.

[0184] During operation 750, the control and monitoring device may use the vehicle management system to adjust at least a pedal position relative to a seat based on the preferred workspace settings.

[0185] For example, control and monitoring device 120 of FIG. 2 may use vehicle management system 200 to adjust the position of pedals 204 by moving the pedals 205 with motor 201 relative to seat 203 based on the preferred workspace settings. For example, motor 201 may adjust the protrusion of the pedals 204 from the floor and/or the advancement of the pedals 204 relative to the seat 203.

[0186] During operation 760, the control and monitoring device may use the vehicle management system to direct configuration of a display based on the preferred workspace settings.

[0187] For example, control and monitoring device 120 of FIG. 3 may use vehicle management system 200, and more particularly, display controller 107 in vehicle management system 200 to direct configuration of displays 302, 303, 306, 307, 308 based on the preferred workspace settings.

[0188] As an example, vehicle management system 200 may determine the visual design of the different displays by selecting the brightness, contrast, color, and/or size of the different displays based on the preferred workspace settings. As another example, vehicle management system 200 may select the information displayed on the respective displays based on the preferred workspace settings. As yet another example, vehicle management system 200 may determine the arrangement of the information on the respective displays based on the preferred workspace settings.

[0189] FIG. 7C is a flowchart 718 showing illustrative operations that a control and monitoring device may perform based on health-related information about a vehicle operator from a personalized wearable device in accordance with some embodiments.

[0190] During operation 770, the control and monitoring device may use the vehicle management system to receive a status signal from a personalized wearable device that comprises health-related information of a vehicle operator.

[0191] For example, control and monitoring device 120 of FIG. 5 may use vehicle management system 200 to receive a status signal 115 from personalized wearable device 111. If desired, the status signal may include health-related information of vehicle operator 110.

[0192] During operation 772, the control and monitoring device may evaluate whether the vehicle operator is unfit for safely operating the vehicle based on the health-related information.

[0193] For example, control and monitoring device 120 of FIG. 5 may evaluate whether vehicle operator 110 is unfit for safely operating vehicle 100 based on the health-related information received from personalized wearable device 111.

[0194] In response to determining that the vehicle operator is not unfit for safely operating the vehicle based on the health-related information, the control and monitoring device may return to performing operation 770.

[0195] In response to determining that the vehicle operator is unfit for safely operating the vehicle based on the health-related information, the control and monitoring device may evaluate during operation 774 whether there is another vehicle operator on-board the vehicle who is fit for safely operating the vehicle.

[0196] For example, control and monitoring device 120 of FIG. 5 may evaluate whether there is another vehicle operator such as vehicle operator 300 of FIG. 3 on-board vehicle 100 and whether the other vehicle operator 300 is fit for safely operating vehicle 100.

[0197] For example, operation 774 may similar to operation 772 evaluate whether vehicle operator 300 of FIG. 3 is unfit for safely operating vehicle 100 based on the health-related information received from personalized wearable device 301 of FIG. 3.

[0198] In response to determining during operation 774 that there is another vehicle operator on-board the vehicle who is fit for safely operating the vehicle, the control and monitoring device may inform the other vehicle operator on-board the vehicle that the vehicle operator is unfit for safely operating the vehicle during operation 790.

[0199] For example, control and monitoring device 120 of FIG. 3 may use wireless NFC unit 305 or wireless radio transmitter and receiver unit 106 to inform the other vehicle operator 300 on-board vehicle 100 via his wearable device 301 that vehicle operator 110 is unfit for safely operating vehicle 100.

[0200] In response to determining during operation 774 that there is no other vehicle operator on-board the vehicle or that the other vehicle operator is also unfit for safely operating the vehicle, the control and monitoring device may re-evaluate whether the vehicle operator is unfit for safely operating the vehicle based on the health-related information during operation 775.

[0201] In response to determining during operation 775 that the vehicle operator is unfit for safely operating the vehicle based on the health-related information, the control and monitoring device may use the vehicle management system to direct a vehicle operating system to initiate autonomous operation of the vehicle during operation 780.

[0202] For example, control and monitoring device 120 of FIG. 5 may use vehicle management system 200 to direct vehicle operating system 501 to initiate autonomous operation of vehicle 100.

[0203] In case that vehicle operator 110 is unfit for safely operating the vehicle, a vehicle management system and/or a flight control computer (FCC) and/or an automatic flight control system (AFCS) may ignore the command inputs by the unfit vehicle operator 110 during operation 783. If present, the same may apply for an unfit vehicle operator 300.

[0204] For example, the vehicle management system 200 and/or the flight control computer (FCC) and/or the automatic flight control system (AFCS) 501 of FIG. 5 may deny a change to the vehicle settings, a change to the flight management, flight planning, and/or the navigation data, and/or ignore any flight control inputs of the unfit vehicle operator 110 or 300.

[0205] During operation 785, the control and monitoring device may use a communication device to inform a remote surveillance station that autonomous operation of the vehicle has been initiated.

[0206] For example, control and monitoring device 120 of FIG. 5 may use communication device 502 to inform remote surveillance station 504, 505 that autonomous operation of vehicle 100 has been initiated.

[0207] For example, the surveillance station may be any competent authority. As an example, consider the scenario in which the vehicle is an aircraft. In this scenario, the surveillance station may be a control tower 504 of a controlled airspace/airport or any air traffic control (ATC) 505 for the airspace in which the vehicle is currently operating or intends to operate during autonomous operation.

[0208] For example, the information exchanged with the remote surveillance station 504, 505 about the autonomous operation may concern the callsign of the aircraft, the type of aircraft, the number of passengers, the current position and altitude when switching to autonomous operation, a change of flight plan and change of flight rules, the intended route, waypoints and altitude, etc. In exchange the remote surveillance station may grant access rights to restricted or controlled airspaces, clear desired routes, flight speeds, headings and altitudes or advise changes of routes, flight speeds, headings and altitudes.

[0209] It should be noted that modifications to the above described embodiments are within the common knowledge of the person skilled in the art and, thus, also considered as being part of the present invention. It should further be noted that the drawings are only intended for schematically representing embodiments of the present invention and not for showing detailed constructions thereof.

[0210] For example, with reference to FIG. 5, vehicle management system 200 may refuse and ignore command inputs from the vehicle operator 110 and refuse any modifications of avionics data or changes in settings initiated by the vehicle operator 110 in response to determining that the vehicle operator 110 is unfit for safely operating vehicle 100. However, vehicle management system 200 may provide for a manual override by the vehicle operator 110 in case of a wrongful detection that the vehicle operator 110 is unfit for operating the vehicle 100. For example, vehicle management system 200 may be overridden by vehicle operator 110 if the latter enters a predetermined code or presses a dedicated button, etc. that indicates that he or she is able to safely operate vehicle 100.

[0211] For example, vehicle management system 200 may be overridden by vehicle operator 110 if the latter enters a predetermined code, presses a dedicated button, or draws a predetermined pattern on the touchscreen etc. on the personalized wearable device 111.

[0212] As another example, personalized wearable device 111 of FIG. 5 may be able to assess physiological and/or bio indicators of the vehicle operator 110 such as the vehicle operator's heart rate, electrocardiogram, sweating/electrical conductivity of the skin, body/skin temperature, blood oxygen saturation, blood pressure, etc. However, personalized wearable device 111 may also provide means to the vehicle operator 110 to declare himself or herself unfit for safely operating vehicle 100. For example, vehicle operator 110 may enter a predetermined code, press a dedicated button, or draw a predetermined pattern on the touchscreen etc. on personalized wearable device 111 that indicates that he or she is unable to safely operate vehicle 100.

[0213] Moreover, vehicle management system 200 of FIG. 5 is shown to inform a control tower 504 and/or an air traffic control 505 on the ground 503 via the communication device 502 that the automatic flight control system (AFCS) 501 of the aircraft 100 has taken over control of the aircraft 100 in response to determining that the vehicle operator 110 is unfit for safely operating the vehicle 100. However, vehicle management system 200 may inform any other surveillance station that may be in the air (e.g., another aircraft or a balloon), in space (e.g., a satellite), or on water (e.g., a ship).

REFERENCE LIST

[0214] 100 vehicle, aircraft, helicopter [0215] 101 fuselage [0216] 102 cabin [0217] 103 tail boom [0218] 104 main rotor [0219] 105 landing gear [0220] 106 wireless radio transmitter and receiver unit [0221] 107 display controller [0222] 108 usage monitoring system [0223] 109 data storage unit [0224] 110 vehicle operator [0225] 111 personalized wearable device [0226] 112 processing unit [0227] 113 identification unit [0228] 114 wireless communication unit [0229] 115 signal [0230] 116 data storage unit [0231] 118 cue generation unit [0232] 120 control and monitoring device [0233] 130 controllable device [0234] 200 vehicle management system (VMS) [0235] 201 motor [0236] 202 movement of the seat [0237] 203 seat [0238] 204 pedal [0239] 205 movement of the pedal [0240] 210 adjustable workspace [0241] 300 vehicle operator [0242] 301 personalized wearable device [0243] 302, 303 display [0244] 304, 305 radio frequency identification (RFID)/wireless near field communication (NFC) unit [0245] 306, 307, 308 display [0246] 309, 310 instrument panel, console [0247] 400 cues [0248] 401 engine control unit [0249] 402 sensor [0250] 403 sensor [0251] 404 display [0252] 405 tactile cues [0253] 406 visual cues [0254] 407 aural cues [0255] 410 vehicle monitoring system [0256] 413 engines [0257] 420 flight control [0258] 430 vibrating device, tactile cue device of flight control inceptor [0259] 431 flight control inceptor, grip of collective or cyclic stick, handle [0260] 440 display [0261] 450 speaker [0262] 460 channel selector [0263] 500 workload and health sensor [0264] 501 vehicle operating system, flight control computer (FCC), automatic flight control system (AFCS), autopilot (AP) [0265] 502 communication device [0266] 503 ground [0267] 504 control tower [0268] 505 remote surveillance station, air traffic control (ATC) [0269] 600 flowchart [0270] 610, 620 operation [0271] 710, 715, 718 flowchart [0272] 720, 730, 731, 740, 750, 760, 770, 772, 774, 775, 780, 783, 785, [0273] 790 operation