# 11.4 Providing of GUI *The jury has observed in recent years that not all teams have prioritized a user-friendly and informative GUI. A clear and intuitive interface is essential for the jury to understand what the ASV sees, detects, and decides during the tasks. A well-designed GUI makes it possible to evaluate the system’s situational awareness, decision-making, and overall usability during the competition.* During the tasks a graphical user interface (GUI) is expected to be shown to the jury. This GUI should provide more information and insight to how your ASV is solving the task. **The GUI should be easy to operate by someone with no background in programming/software.** Njord will provide a big screen on which you can show your GUI. The GUI should provide situational awareness and transparency for what the vessel is doing. The user should be able to safely supervise the system, and know when to intervene. It should also let the user know the state of the current mission; what it is doing and why it is doing it. Ideas for this are camera or LIDAR feed with object detection; a map with location, heading and path; a graph with speed, energy consumption, and battery percentage. You could add any parameters that you want and deem necessary/useful for the jury to understand your ASV better. The components together can show how your ASV makes decisions during its run. This can be based on showing which objects are detected and based on this how the path is further planned. This can be a combination of changing heading, speed and power consumption. It can also show how it searches for AR-tags to find the correct dock for example. This section requires teams to demonstrate transparency and unbiased assessment of their vessel's performance. To ensure this, one jury member should be able to understand your GUI and its displays without additional explanation during the task. Therefore, it’s essential that the GUI is user-friendly and understandable to someone with limited technical knowledge of the vessel. Here simplicity is key. During the team presentation, you will have the opportunity to explain to the jury how your GUI functions and how it aligns with your approach to solving the tasks. The data to be provided in your GUI are as follows: * Camera feed/LIDAR * Latitude * Longitude * Heading * Course over ground (COG) with trail, vs plot of ideal route given by GNSS points to compare. * Speed over ground. * Battery life in % left * Status Indicator: Displays whether the ASV is in autonomous mode, remote control, standby, or out of control. Nice to have: * Distance between ASV and next waypoint * Battery life in Wh left * Other parameters you would wish to include --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://njord.gitbook.io/2026/11-evaluation/11.4-providing-of-gui.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.