Last modified by Rosa Van Tuijn on 2026/04/13 12:47

From version 1.24
edited by Tjalling Haije
on 2026/03/24 09:22
Change comment: There is no comment for this version
To version 1.17
edited by Tjalling Haije
on 2026/03/23 15:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -10,6 +10,7 @@
10 10  1. FR Health
11 11  1. FR and victim safety
12 12  
13 +
13 13  **3. Hypotheses / Expectations (optional)**
14 14  See the claims from [[UC04.3: Detailed indoor exploration with ANYMAL (USAR)>>2\. Specification.b\. Use Cases.UC04\.0\: Detailed indoor exploration.UC04\.3\: Detailed indoor exploration with ANYMAL (USAR).WebHome]], being:
15 15  
... ... @@ -21,6 +21,7 @@
21 21  * CL06: improved FR health
22 22  * CL07: degraded mission efficiency
23 23  
25 +
24 24  **4. Scenario / Context**
25 25  ASR3: Detailed indoor exploration
26 26  
... ... @@ -32,6 +32,7 @@
32 32  ** **ANYmal **is mission-ready (battery, controls, and payload checked).
33 33  ** **C3I is online**, role-based views are configurated (Operator/ Analyst/ Team leader/ Safety officer); **5G pods** are installed for connection.
34 34  
37 +
35 35  **5. Participants**
36 36  
37 37  * FR team ROBOT:
... ... @@ -104,6 +104,7 @@
104 104  * FR Team ROBOT does Building B
105 105  * FR team HUMAN does Building A
106 106  
110 +
107 107  **9. Measurements**
108 108  
109 109  See the measurements from [[UC04.3: Detailed indoor exploration with ANYMAL (USAR)>>2\. Specification.b\. Use Cases.UC04\.0\: Detailed indoor exploration.UC04\.3\: Detailed indoor exploration with ANYMAL (USAR).WebHome]]
... ... @@ -130,33 +130,32 @@
130 130  111. Time for tackling any health alerts
131 131  111. Track FR path
132 132  1. __Hotwash__:
133 -11. Questions (specified per role, couple questions per topic) on:
137 +11. Questions on:
134 134  111. Near-incident report
135 135  111. Path inside
136 136  111. FR location and status of hazards, victims, and layout
137 -111. Mission effectiveness ? Decision Making effectiveness?
141 +111. Mission effectiveness
138 138  111. Self-reported workload
139 139  111. Trust survey
140 -11. Group discussion with feedback
141 141  
142 142  **~11. Planning:**
143 143  
144 144  * Team preparation: Day before. 1 hour.
145 145  * Trial 1:
146 -** Setup scenario: Test day 1. 09:00 - 09:30
149 +** Setup usecase: Test day 1. 09:00 - 09:30
147 147  ** Setup tech and perform checks: Test day 1. 09:00 - 09:30
148 148  ** Briefing of each team individually (outside building): Test day 1: 09:00 - 09:30
149 149  ** Mission execution: Test day 1. 09:30 - 10:30
150 150  ** Hot wash: Test day 1. 10:30-11:00
151 -** Scenario reset: test day 1. 10:30-11:00
154 +** Usecase reset: test day 1. 10:30-11:00
152 152  * Teams switch location: Test day 1. 11:00-11:15
153 153  * Trial 2: 
154 -** (Setup scenario: Test day 1. 12:30 - 13:00)
157 +** Setup usecase: Test day 1. 12:30 - 13:00
155 155  ** Setup tech and perform checks: Test day 1. 12:30 - 13:00
156 156  ** Briefing of each team individually (outside building): Test day 1: 12:30 - 13:00
157 157  ** Mission execution: Test day 1. 13:00 - 14:00
158 158  ** Hot wash: Test day 1. 14:00-14:30
159 -* Cleanup area and store tech. 14:00-14:30
162 +** Cleanup area and store tech. 14:00-14:30
160 160  
161 161  
162 162  
... ... @@ -175,6 +175,7 @@
175 175  ** ~~8x Actors or dummies for victims.
176 176  * 8x Clipboards with papers and pens for hotwash and questionnaires
177 177  
181 +
178 178  **13. Dependencies**
179 179  
180 180  * Availability of materials
... ... @@ -185,6 +185,7 @@
185 185  ** People willing to play victim
186 186  ** Experiment leaders
187 187  
192 +
188 188  **14. Success Criteria**
189 189  When mission(s) completed by both teams, and we can compare their performance using the metrics.
190 190