## 6 Practical Application and Results
### Design Conceptualization
\begin{table}
\begin{tabular}{c c l l} \hline \hline
**Theoretical** & **Area** & **N\({}^{\circ}\)** & **Design Guidelines** \\ \hline \multirow{8}{*}{Core principles} & \multirow{8}{*}{Core} & 1 & Organize information around goals \\  & & 2 & Present level 2 information directly (support comprehension) \\  & & 3 & Provide assistance for level 3 SA projections \\  & & 4 & Support trade-offs between goal-driven and data-driven processing: top-down and bottom-up processing \\  & & 5 & Make critical cues for schema activation salient \\  & & 6 & Use information filtering carefully \\ \cline{2-3}  & \multirow{2}{*}{To address uncertainty} & 7 & Explicitly identify missing information \\  & & 8 & Support sensor reliability assessment \\ \cline{2-3}  & \multirow{8}{*}{To taming complexity} & 9 & Just say no to feature creep-buck the trend \\  & & 10 & Manage rampant featurism through prioritization and flexibility \\  & & 11 & Insure logical consistency across modes and features \\  & & 12 & Minimize logic branches \\  & & 13 & Map system functions to the goals and mental models of users \\  & & 14 & Group information based on level 2/3 SA requirements and goals \\  & & 15 & Reduce display density, but do not sacrifice coherence \\  & & 16 & Provide consistency and standardization on controls across different \\  & & 16 & displays and systems \\  & & 17 & Minimize task complexity \\ \hline \multirow{8}{*}{To design automated systems} & \multirow{8}{*}{18} & 18 & Automate only if necessary \\  & & 19 & Use automation for assistance in carrying out routine actions rather than \\  & & 19 & higher level cognitive tasks \\ \cline{1-1}  & & 20 & Provide SA support rather than decisions \\ \cline{1-1}  & & 21 & Keep the operator in control and in the loop \\ \cline{1-1}  & & 22 & Make modes and system states salient \\ \cline{1-1}  & & 23 & Use methods of decision support that create human/system symbiosis \\ \hline \multirow{8}{*}{Immersive analytics (IA) [2]} & \multirow{8}{*}{Situated analytics [34]} & \multirow{8}{*}{Consider the size and visibility of the referents and environments with which the system will be used} \\  & & 25 & Consider how easy is to distinguish, track, and connect physical referents with related data \\ \cline{1-1}  & & 26 & Ensure that visual augmentations do not distract user’s attention away from the environment \\ \cline{1-1}  & & 27 & Ensure the alignment between virtual presentations and physical referents \\ \cline{1-1}  & & 28 & Emphasize the use of real-time data \\ \cline{1-1}  & & 29 & Choose visual encodings that ensure the system informs but does not hinder the user’s actions \\ \hline \hline \end{tabular}
\end{table} 
Table 4: SA and IA design guidelines employed in the method application. _AR interaction._ Handsets, specifically smartphones, were employed for AR interaction, using tactile gestures as the interaction mode (Table 4, guideline 37). Proposed interaction tasks included tap for selecting and body-based physical movement for exploring/navigating within the immersive environment. The AR interaction flow begins with selecting the option/button for goal 1.1.1. Once selected, if all constraints were removed, a colored message appears in the center of the screen to notify the user (guidelines 31 and 36). If not, the interface displays only the colored virtual building elements with tasks with constraints not removed (guideline 31). In this state, the field manager can navigate the immersive environment by physically moving while holding and gazing at the handset to inspect the work area (guidelines 32 and 38). 6. _MR interaction._ The Trimble XR10 headset was employed for MR interaction, using multimodal interaction such as eye/head gaze and hand gesture as the interaction modes (Table 4, guideline 37). The interaction tasks included head gaze and eye gaze for tracking; air-tap, point and commit with hands, and eye gaze and pinch for selecting; and body-based physical movement for exploring/navigating.