Otherwise you might end up in a situation like the one on the left there!Įnsure automation setup doesn’t put situational awareness at risk.
Or, as Mica would put it, users need to retain situational awareness. So how do we achieve this? Reading up on Mica Endsley, an aviation automation guru, led us to believe that the eTechLog8 users need to really know whats happening to really figure out what to do. For Conduce it’s imperative that we keep eTechLog8 users fully aware and in the loop. As the system becomes more reliable and automated, the users disengage because they trust the system will do everything for them.Īnd maybe buying whatever your fridge told you to get is okay (if you want to eat the same thing every week!), but a pilot in autopilot mode is definitely not okay. Ultimately, the consequences of this can be devastating.Īs Lisanne Bainbridge claimed, this is the irony of automation.
Extensive research has proven that too much automation has adverse effects because people lose attention or may not understand what is happening. This first one is the grounds for the repetitive inspection:Īnd there’s a good reason to be wary of too much automation. So how does it work? When eTechLog8 users mark a defect action for a repetitive inspection, the system automatically creates a secondary defect entry that falls under the scope of the original one. With this automation, we nailed one of the ultimate goals of eTechLog8: to reduce human errors. In fact, we implemented this feature after realising that many eTechLog8 users forgot to action and close the corresponding defect and defect action entries when recording repetitive inspections. Our brand-new repetitive defect inspection feature is the best example of this type of automation. The system performs a function as a result of a specific user action. We ensure a human has monitored and checked what the system will use automatically. However, this is an example of where we trust the automation because a human being has curated and checked the defect templates list before uploading it. We highly recommend using defect templates as it helps standardisation and speed. To make this happen, first we have to upload a list of defect templates to the eCentral8 website. Some of our customers choose to add defect templates for standardising or simplifying the process of entering a defect. The system pre-populates information for a specific field.ĭefect templates are a great example of this. On the eTechLog8 device, our customers mainly notice this automation in two ways: 1. This customisation extends from importing files or setting up statements to… You guessed it! Automating processes. While implementing eTechLog8 as the aircraft technical logbook, we dedicate a great deal of time and effort to customise the solution in line with customer procedures and applicable regulations. In the same trend, our eTechLog8 application offers plenty of automation possibilities to our customers. We won’t bore you with all the examples we found, but, as you see, the evidence is out there. Likewise, Robert Ropelewski demonstrated that embedding automation in the cockpit as part of the manufacturing process of a B767 improved the crew’s performance. For example, in 1996 Charles Billings proved ground proximity warning systems in transport aircraft significantly decreased terrain incidents. Since the 80s, scientists have proven that increased automation diminishes the likelihood of aircraft accidents and delays. Automation is everywhere! Especially in the aviation industry, where every second is precious, and pilots’ or engineers’ attention is a matter of life and death. Just think of that last bill that you set up an automatic payment for, or that fancy fridge that checks food in stock and makes a shopping list for you.
0 kommentar(er)
