## 6 Practical Application and Results
### Design Conceptualization  
The design conceptualization for each design parameter is exemplified using the first SA requirement from Table 2: \"Current status of the constraints of the weekly/immediate work plan\", as explained below. 1. _Description._ This is a level 2 SA requirement, as it involves comprehending the current situation of constraints for planned tasks based on perceived information. This cognitive outcome represents the field manager's mental picture of whether planned tasks have their constraints removed or not, being most important in the latter as they need to be addressed. 2. _Type._ This is a mental construct about the constraints' situation. 3. _Spatial association._ This mental construct cannot be directly associated with elements in the environment. However, it can be formed by associating information about tasks and their constraints with related virtual elements. For this, the digital building model should be overlaid onto its physical twin version to present and access information on demand. 4. _Visualization._ Following the guidelines in Table 4, the interface should \"present level 2 information directly\" (guideline 2) to support the comprehension of the task constraints situation. This involves visualizing if tasks have their constraints removed or not within the immersive environment. For this, the interface should use a visual encoding that informs without hindering the user's actions (guideline 29). One approach is to use colors on virtual building elements associated with tasks with \begin{table}
\begin{tabular}{l l l} \hline \hline
**Type of Requirement** & **Operational Requirements** \\ \hline Technical environment & \(\bullet\) & The system can work sufficiently with lower-level interaction tasks. \\ \hline \multirow{8}{*}{System integration} & \(\bullet\) & The system shall be able to retrieve data from different sources, including Excel spreadsheets, PDF files, and Word documents. \\  & \(\bullet\) & The system shall support building information modeling (BIM) models. \\  & \(\bullet\) & The system shall require the user to employ BIM models with sufficient granularity to associate required information with specific building elements. \\  & \(\bullet\) & The system shall be able to maintain information updated. \\ \hline \multirow{2}{*}{Portability} & \(\bullet\) & The system can run on handset or headset devices on the construction site. \\ \hline Maintainability & \(\bullet\) & The system shall support scalability for goals, information, and data sources. \\ \hline \hline \end{tabular}
\end{table} 
Table 3: _Cont._constraints not removed (guidelines 39 and 40). For tasks with constraints removed, their associated elements should be hidden to focus the field manager's attention on the constraints not removed (guidelines 15 and 26). If all tasks have their constraints removed, i.e., no colored building elements are visible, the interface should display a notification to inform the field manager. This design concept highlights the critical cues that activate the mental schema of the situation (guideline 5) and minimizes task complexity (guideline 17), enabling the field manager to recognize, at a glance, planned tasks with constraints to be addressed.