m (Scipediacontent moved page Draft Content 568122445 to Boy 2019a) |
|||
Line 2: | Line 2: | ||
== Abstract == | == Abstract == | ||
− | During the last three decades, aircraft cockpits have been highly automated and incrementally digitized to the point that we now talk about | + | During the last three decades, aircraft cockpits have been highly automated and incrementally digitized to the point that we now talk about âinteractive cockpitsâ, not because pilots interact with the mechanical part of the aircraft directly, but because they use a pointing device to interact with computer screens. More generally, computers invaded the airspace ranging from onboard aircraft to air traffic control (ATC) ground services. In terms of workflow, the elimination of the flight-engineer onboard commercial aircraft cockpits drastically transformed the way pilots flyâthis was done in the beginning of the 1980s. Pilotâs activity shifted from manual control to cognitive management of embedded systems (performing some of the tasks the flight engineer used to do). Aircraft automation considerably improved commercial aviation safety. Today, main issues come from the exponential increase of the number of aircraft in the sky. Air traffic complexity imposes drastic reengineering of air traffic workflow. ATC is shifting towards air traffic management (ATM). Same thing: moving from control to management, expanding cockpitâs single agent problems and solutions to air traffic multi-agent problems and solutions. The main emphasis is therefore social cognition. During the twentieth century, we automated physical systemsâwe now talk about cyber-physical systems (i.e., we shifted from hardware mechanical engineering issues to software cognitive problems). During the beginning of the twenty-first century, almost all systems are first ideated and designed as pieces of software, and they are transformed into tangible things. Consequently, workflow can be modeled and simulated very early during the design process and, unlike during the twentieth century, functions and therefore activities can be tested before anything is physically built. This provides great possibilities that should be operationalized and implemented. This chapter will show that the main issue has become tangibility, instead of automation. At the same time, these new possibilities provided by our emerging digital world enable a brand-new move towards more autonomous systems that need to be coordinated. We will illustrate this shift from automation towards autonomy, by providing salient examples and generic patterns of this evolution of workflow in the aviation domain. |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
Line 15: | Line 10: | ||
* [https://hal.archives-ouvertes.fr/hal-02424942/file/CHAPTER%207%20GAB%20v1r.pdf https://hal.archives-ouvertes.fr/hal-02424942/file/CHAPTER%207%20GAB%20v1r.pdf] | * [https://hal.archives-ouvertes.fr/hal-02424942/file/CHAPTER%207%20GAB%20v1r.pdf https://hal.archives-ouvertes.fr/hal-02424942/file/CHAPTER%207%20GAB%20v1r.pdf] | ||
+ | |||
+ | * [http://link.springer.com/content/pdf/10.1007/978-3-030-16916-9_5 http://link.springer.com/content/pdf/10.1007/978-3-030-16916-9_5], | ||
+ | : [http://dx.doi.org/10.1007/978-3-030-16916-9_5 http://dx.doi.org/10.1007/978-3-030-16916-9_5] under the license http://www.springer.com/tdm | ||
+ | |||
+ | * [https://hal.archives-ouvertes.fr/hal-02424942 https://hal.archives-ouvertes.fr/hal-02424942], | ||
+ | : [https://hal.archives-ouvertes.fr/hal-02424942/document https://hal.archives-ouvertes.fr/hal-02424942/document], | ||
+ | : [https://hal.archives-ouvertes.fr/hal-02424942/file/CHAPTER%207%20GAB%20v1r.pdf https://hal.archives-ouvertes.fr/hal-02424942/file/CHAPTER%207%20GAB%20v1r.pdf] | ||
+ | |||
+ | * [https://hal.archives-ouvertes.fr/hal-02956589 https://hal.archives-ouvertes.fr/hal-02956589], | ||
+ | : [https://hal.archives-ouvertes.fr/hal-02956589/document https://hal.archives-ouvertes.fr/hal-02956589/document], | ||
+ | : [https://hal.archives-ouvertes.fr/hal-02956589/file/CHAPTER%207%20GAB%20v1r.pdf https://hal.archives-ouvertes.fr/hal-02956589/file/CHAPTER%207%20GAB%20v1r.pdf] | ||
+ | |||
+ | * [https://link.springer.com/chapter/10.1007%2F978-3-030-16916-9_5 https://link.springer.com/chapter/10.1007%2F978-3-030-16916-9_5], | ||
+ | : [https://hal.archives-ouvertes.fr/hal-02424942 https://hal.archives-ouvertes.fr/hal-02424942], | ||
+ | : [https://academic.microsoft.com/#/detail/2963920429 https://academic.microsoft.com/#/detail/2963920429] |
During the last three decades, aircraft cockpits have been highly automated and incrementally digitized to the point that we now talk about âinteractive cockpitsâ, not because pilots interact with the mechanical part of the aircraft directly, but because they use a pointing device to interact with computer screens. More generally, computers invaded the airspace ranging from onboard aircraft to air traffic control (ATC) ground services. In terms of workflow, the elimination of the flight-engineer onboard commercial aircraft cockpits drastically transformed the way pilots flyâthis was done in the beginning of the 1980s. Pilotâs activity shifted from manual control to cognitive management of embedded systems (performing some of the tasks the flight engineer used to do). Aircraft automation considerably improved commercial aviation safety. Today, main issues come from the exponential increase of the number of aircraft in the sky. Air traffic complexity imposes drastic reengineering of air traffic workflow. ATC is shifting towards air traffic management (ATM). Same thing: moving from control to management, expanding cockpitâs single agent problems and solutions to air traffic multi-agent problems and solutions. The main emphasis is therefore social cognition. During the twentieth century, we automated physical systemsâwe now talk about cyber-physical systems (i.e., we shifted from hardware mechanical engineering issues to software cognitive problems). During the beginning of the twenty-first century, almost all systems are first ideated and designed as pieces of software, and they are transformed into tangible things. Consequently, workflow can be modeled and simulated very early during the design process and, unlike during the twentieth century, functions and therefore activities can be tested before anything is physically built. This provides great possibilities that should be operationalized and implemented. This chapter will show that the main issue has become tangibility, instead of automation. At the same time, these new possibilities provided by our emerging digital world enable a brand-new move towards more autonomous systems that need to be coordinated. We will illustrate this shift from automation towards autonomy, by providing salient examples and generic patterns of this evolution of workflow in the aviation domain.
The different versions of the original document can be found in:
Published on 01/01/2019
Volume 2019, 2019
DOI: 10.1007/978-3-030-16916-9_5
Licence: CC BY-NC-SA license
Are you one of the authors of this document?