Automation coupling, or joint cognitive systems is a concept in which human cognition and machine cognition are performed in conjugation, rather than with agency.
This concept is one that is highly favored in the automation industry but has yet to be effectively implemented into any complex system. Cognitive coupling is gradually increasing in automobile-human relationships with blind spot detection, automatic braking, back up sensors, self-parking, self-breaking, and self-driving features. However, the human-machine relationship in these examples is still dominated by the human, there is no team-like performance that equates to a joint cognitive system. As system complexity increases engineers lean towards designating either the human or the machine to lead the decision-making process. Current autonomous coordination designs are limited by the idea that machines and humans must operate in agency. For complete human-automation coupling and total efficacy in artificial intelligence - AI (intelligence carried out by computational power rather than the human mind) to occur, there must be an equal amount of directive and control from each interface.
Avengers (Iron Man) Conceptual Design Applied to the Real World
When I initially learned about the concept of cognitive coupling, I started to get the feeling that something sounded familiar about Human-Automation Cognitive Coupling, like I’d already seen it incorporated into a system. I couldn’t quite put my finger on what it was until the last Avengers movie trailer was brought to my attention. Tony Stark’s (Iron Man) armored suit and its software, J.A.R.V.I.S. (Just a Rather Very Intelligent System) is a perfect concept of a joint cognitive system. J.A.R.V.I.S. is the user interface for Tony Stark’s Iron Man suit that informs him about mission plans, the suit’s system status, atmospheric and environmental conditions, and details about enemies during combat. J.A.R.V.I.S. is also able to study Stark’s personal notes and aid him with technological experiments for the improvement of itself. J.A.R.V.I.S. also can take control when Stark is in danger, or unconscious, and react in a timely manner when it calculates Stark will be unable to react appropriately. Unlike most autonomous systems, J.A.R.V.I.S. is an adaptive system that can form a conversational communication structure, which enables “him” to operate as Stark’s partner, they work as a team rather than in agency. J.A.R.V.I.S. is literally the suit that encompasses Stark, once the two combine they become one system which is Iron Man. Stark needs J.A.R.V.I.S. to save the world, and J.A.R.V.I.S. needs Stark to fulfill its purpose, they need each other to become the Iron Man.
I can see the concept of J.A.R.V.I.S being most efficiently applied to the aerospace industry, considering J.A.R.V.I.S. is an aerial system when in flight. How would such an advanced aerial system operate? It wouldn't be the mechanical system we think of when picturing an autonomous aircraft like Black Panther's Royal Talon. It would be an operational system that includes both human intel and artificial intel, inexistent without the presence of both parties. This concept would be an aircraft that only requires one pilot. The aircraft would, just like J.A.R.V.I.S, adjust to the pilot’s anthropometrics upon being seated, meaning it would have adjustable seats.
Upon entrance, the aircraft’s AI system would ask initial questions to gauge the mental condition of the pilot to predict his/her cognitive presence, situational awareness, stress, and fatigue, and communicate any concerns to the pilot while adjusting accordingly. This system would also be programmed to listen and abide by the pilot's commands, but at the same time communicate the most efficient action/reaction and the possible consequences of the pilot ignoring the recommendations. This conceptual aircraft would also have the ability to detect maintenance issues within itself as well as the knowledge of maintenance solutions. Just like J.A.R.V.I.S., this aircraft would be its own “self,” and require the cognitive aid of a pilot to operate.
Design Principles for Interface Agent Modeling
In designing this concept, one must follow two crucial interface design principles in order for such a complex system to run efficiently. The first one is the principle of, “Keep it Simple.” “Keep it simple” centers around the designer making sure the automation interfaces represent the simplest design consistent with the functions and tasks of the users. Machine and software agents must communicate its “thoughts” and calculations in a way that the human agent can comprehend and react to in a timely manner, and vice versa. The Human-agent must also communicate in a way that the machine will understand. Poor communication within the human-machine interaction could cause an inappropriate action or response from one of the interfaces. This design concept also requires achieving compatibility between the design and the human perceptual, physical, cognitive, and dynamic motor response capabilities.
For these, requirements, I go back to the Marvel super suit, J.A.R.V.I.S. J.A.R.V.I.S. is a perfect example of meeting every aspect of this design principle. J.A.R.V.I.S. has the capability to predict Iron Man’s actions, and reactions, mold to his anthropometrics, help make decisions, and react to impending harm autonomously in the event that Stark is unable to. It is also important for such a complex system to follow the design principle of “presenting dynamic information in real-time” Dynamic information (information that changes over time) should be presented in real-time and on-demand to ensure accurate and timely decision-making.
Comments