An Augmented Reality Command and Control Sand Table Visualization of the User Interface Prototyping Toolkit (UIPT)

Author(s):  
Bryan Croft ◽  
Jeffrey D. Clarkson ◽  
Eric Voncolln ◽  
Alex Campos ◽  
Scott Patten ◽  
...  



2012 ◽  
Vol 12 (3) ◽  
pp. 555-573 ◽  
Author(s):  
M. Hammitzsch ◽  
M. Lendholt ◽  
M. Á. Esbrí

Abstract. The command and control unit's graphical user interface (GUI) is a central part of early warning systems (EWS) for man-made and natural hazards. The GUI combines and concentrates the relevant information of the system and offers it to human operators. It has to support operators successfully performing their tasks in complex workflows. Most notably in critical situations when operators make important decisions in a limited amount of time, the command and control unit's GUI has to work reliably and stably, providing the relevant information and functionality with the required quality and in time. The design of the GUI application is essential in the development of any EWS to manage hazards effectively. The design and development of such GUI is performed repeatedly for each EWS by various software architects and developers. Implementations differ based on their application in different domains. But similarities designing and equal approaches implementing GUIs of EWS are not quite harmonized enough with related activities and do not exploit possible synergy effects. Thus, the GUI's implementation of an EWS for tsunamis is successively introduced, providing a generic approach to be applied in each EWS for man-made and natural hazards.





2001 ◽  
Author(s):  
John S. Bay ◽  
Louise E. Borrelli ◽  
Kevin L. Chapman ◽  
Thomas R. Harrold




Author(s):  
Mark Johnxys ◽  
Heather M. Oonk ◽  
Glenn A. Osga

Supervision of command and control tasks requires monitoring and maintaining situation awareness of multiple on-going tasks performed by other agents and systems. Automation may aid the user, but realistic automation is often not totally reliable. Sophisticated users may learn to use even unreliable automation to their advantage if 1) they employ a strategy such as “trust-but-verify”, and 2) the user interface supports this strategy by integrating information about the situation with the display of what the automation is doing. The trust-but-verify strategy can be broken into two parts: 1.1) conditional trust and 1.2) qualitative verification. Conditional trust involves knowing when the situation is conducive to trusting the automation. Qualitative verification involves using the automation as a guide or input into manual decision making.



Sign in / Sign up

Export Citation Format

Share Document