Skip to Content
Last modified by Tjalling Haije on 2026/03/23 12:13
From version 1.1
edited by Mark Rinse van Koningsveld
on 2025/09/13 15:35
Change comment: There is no comment for this version
To version 1.3
edited by Tjalling Haije
on 2026/03/23 12:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.MarkVanKoningsveld
1 +XWiki.TjallingHaije
Content
... ... @@ -1,17 +1,18 @@
1 -Route the right info to the right person at the right time; hide the rest by default. For now focussing on local robot information for squad leads, alerts for BoO and medical status information for squad leads, team leads, medical staff and BoO
2 -
3 -**Intent.** Minimize distraction and missed signals with role- and phase-aware routing.
4 -
5 -**Context.** Multi-role teams; shifting phases; heterogeneous devices.
6 -
7 -**Problem.** Undifferentiated feeds overload users and bury critical cues.
8 -
9 -**Solution.**
10 -
11 -* **Role Profiles** (Operator, Analyst, Squad Lead, Sector Lead, BoO) with default subscriptions and alert levels.
1 +| |**IDP1 Role-Based, Context-Specific Information Distribution**
2 +|**Visual**|[[image:1774262282868-737.png]]
3 +|**Description**|Route the right info to the right person at the right time; hide the rest by default. For now, focusing on local team information for squad leads, sector related alerts for BoO and detailed medical status information for the medical staff. Every role should get the information deliverd so that they can act upon it within the tasks of their role. The squad leader should have status indicators that are simple and readable, because they do not have the time to look into details. The BoO should have a collapsable overview of all teams, with alerts when there are a lot of status changes at once. Medical teams should have detailed information like heart rate, blood oxygen levels, and other relevant information. This same buildup holds for location, comm status and environmental sensor status information.
4 +|**Intent**|Minimize distraction and missed signals with role- and phase-aware routing.
5 +|**Context**|Multi-role teams; shifting phases; heterogeneous devices.
6 +|**Problem**|Undifferentiated feeds overload users and bury critical cues.
7 +|**Solution**|(((
8 +* **Role Profiles** (Operator, Analyst, Squad Lead, Sector Lead, BoO) with default subscriptions and alert levels.
12 12  * **Progressive disclosure**; “break-glass” broadcast for emergencies.
13 -* **Targeted alerts** based on role like medical staff including medics but also doctors at BoO
14 -
15 -**UI/Modalities.** Role dashboards, , contextual banners;
16 -
17 -**Related.** All TDPs; especially TDP1, TDP5.
10 +* **Targeted alerts** based on role like field medics but also doctors at BoO
11 +)))
12 +|**UI/Modalities**|Role dashboards
13 +|**Advantages**|(((
14 +* Mission efficiency improved (due to user finding and interpreting relevant information more quickly).
15 +* Workload acceptable (due to tailoring dashboard to needs of the user).
16 +)))
17 +|**Disadvantages**|
18 +|**Related TDPs/IDPs**|TDP1, TDP5.
1774262282868-737.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.TjallingHaije
Size
... ... @@ -1,0 +1,1 @@
1 +19.4 KB
Content