Wiki source code of h. Test SFT1: System baseline test
Version 2.4 by Rosa Van Tuijn on 2026/03/24 16:16
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
| |
1.6 | 1 | **Experiment title** |
| |
1.16 | 2 | System baseline test |
| |
1.2 | 3 | |
| |
1.6 | 4 | |
| |
1.2 | 5 | **2. Objective / Research Question** |
| |
1.14 | 6 | Do the SYNERGISE technologies together improve the SYNERGISE [[Objectives>>2\. Specification.Objectives.WebHome]] (stated below) without negative effects? |
| |
1.2 | 7 | |
| |
1.6 | 8 | 1. Mission effectiveness |
| 9 | 1. Mission efficiency | ||
| 10 | 1. FR Health | ||
| 11 | 1. FR and victim safety | ||
| 12 | |||
| |
1.2 | 13 | **3. Hypotheses / Expectations (optional)** |
| |
1.6 | 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: |
| |
1.2 | 15 | |
| |
1.6 | 16 | * CL01: Improve safety for responders |
| 17 | * CL02: Increased SA | ||
| 18 | * CL03: Improved mission effectiveness | ||
| 19 | * CL04: acceptable workload | ||
| 20 | * CL05: trustworthy SA | ||
| 21 | * CL06: improved FR health | ||
| 22 | * CL07: degraded mission efficiency | ||
| 23 | |||
| |
1.2 | 24 | **4. Scenario / Context** |
| |
1.7 | 25 | ASR3: Detailed indoor exploration |
| |
1.2 | 26 | |
| |
1.7 | 27 | Preconditions 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]] : |
| 28 | |||
| 29 | * Structure is flagged as (relatively?) **safe for direct human entry**; sector/ worksite allocated. | ||
| 30 | * **FRs wearables** distributed, connected, and calibrated. | ||
| 31 | * Specific to scenario with ANYmal: | ||
| 32 | ** **ANYmal **is mission-ready (battery, controls, and payload checked). | ||
| 33 | ** **C3I is online**, role-based views are configurated (Operator/ Analyst/ Team leader/ Safety officer); **5G pods** are installed for connection. | ||
| 34 | |||
| |
1.2 | 35 | **5. Participants** |
| 36 | |||
| |
1.7 | 37 | * FR team ROBOT: |
| |
1.3 | 38 | ** 1x Squad leaders |
| 39 | ** 1x Robot operator | ||
| 40 | ** 1x Robot analyst | ||
| 41 | ** 2x First responder | ||
| |
1.7 | 42 | * FR team HUMAN: |
| |
1.3 | 43 | ** 1x Squad leaders |
| 44 | ** 2x First reponder | ||
| 45 | * Base of Operations: | ||
| |
1.6 | 46 | ** 1x Safety officer / medical specialist |
| |
1.3 | 47 | ** Team lead |
| |
1.2 | 48 | |
| |
1.6 | 49 | Number of participants: 9 |
| 50 | |||
| |
1.5 | 51 | |
| |
1.2 | 52 | **6. System(s) Under Test** |
| 53 | |||
| |
1.7 | 54 | |(% style="width:267px" %)Technology|(% style="width:1250px" %)Description |
| 55 | |(% style="width:267px" %)ANYmal|(% style="width:1250px" %)((( | ||
| 56 | * Robust mobility over uneven terrain (stairs, debris, slopes). | ||
| 57 | * Multi-sensor payload (video, LIDAR, thermal??) | ||
| 58 | * Reliable wireless communication/ connection in degraded environments. | ||
| 59 | * Support for tele‑operation with clear operator feedback. | ||
| 60 | * Link with C3I, such as adding victims as pin on map. | ||
| 61 | * NO autonomy. | ||
| 62 | ))) | ||
| 63 | |(% style="width:267px" %)C3I (BoO and tablet version)|(% style="width:1250px" %)((( | ||
| 64 | * Interoperability with health and location sensors. | ||
| 65 | * Robust operation under limited connectivity (sync when possible). | ||
| 66 | * Usable tablet interface for field conditions (gloves, stress, time pressure). | ||
| 67 | ))) | ||
| 68 | |(% style="width:267px" %)Health sensors|(% style="width:1250px" %)((( | ||
| 69 | * Accurate and reliable physiological sensing (e.g. heart rate, exertion proxies). | ||
| 70 | * Comfortable, non‑intrusive form factor suitable for long missions. | ||
| 71 | * Secure wireless data transmission to C3I systems. | ||
| 72 | * Real‑time alerting and trend monitoring. | ||
| 73 | ))) | ||
| 74 | |(% style="width:267px" %)Location sensors|(% style="width:1250px" %)((( | ||
| 75 | * Indoor and outdoor localisation capability. | ||
| 76 | * Sufficient accuracy and update rate for safety‑critical use. | ||
| 77 | * Integration with C3I and mapping systems. | ||
| 78 | * Robustness to environmental interference (dust, debris, structures, height differences). | ||
| 79 | ))) | ||
| |
1.2 | 80 | |
| |
1.7 | 81 | |
| 82 | |||
| |
1.2 | 83 | **7. Tasks** |
| 84 | |||
| |
1.6 | 85 | [[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]] |
| 86 | |||
| 87 | [[UC04.4: Detailed indoor exploration without ANYMAL (USAR)>>2\. Specification.b\. Use Cases.UC04\.0\: Detailed indoor exploration.UC04\.3\: Detailed indoor exploration with ANYmal (USAR).WebHome]] | ||
| 88 | |||
| 89 | |||
| |
1.2 | 90 | **8. Experimental Conditions / Variants** |
| |
1.7 | 91 | |
| 92 | Two buildings: | ||
| 93 | |||
| |
1.8 | 94 | * Building A: Easier location, obstacles and environmental conditions. (clear visibility, ..) |
| 95 | * Building B: Challenging location, obstacles and environmental conditions for humans and robots (e.g. smoke and obstacles). | ||
| |
1.7 | 96 | |
| |
1.8 | 97 | Trial 1: |
| |
1.7 | 98 | |
| |
1.8 | 99 | * FR Team ROBOT does Building A |
| 100 | * FR team HUMAN does Building B | ||
| |
1.7 | 101 | |
| |
1.8 | 102 | Trial 2: |
| |
1.7 | 103 | |
| |
1.8 | 104 | * FR Team ROBOT does Building B |
| 105 | * FR team HUMAN does Building A | ||
| |
1.7 | 106 | |
| |
1.2 | 107 | **9. Measurements** |
| 108 | |||
| |
2.2 | 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]]. Compare outcomes between the two conditions teams if applicable. |
| |
1.2 | 110 | |
| |
2.2 | 111 | |**Claim: Safety**|**Measurment(s)**|**How to test ** |
| |
2.1 | 112 | |Safer decision before entry|Safe path chosen|((( |
| 113 | * Define ground-truth safe path(s) beforehand so that they can be compared to chosen entry path during the trial | ||
| 114 | * Score paths beforehand: safe/ suboptimal/ unsafe | ||
| 115 | ))) | ||
| 116 | |Better decision overall|"How good were you decisions looking back?"|((( | ||
| 117 | * Hotwash reflection question (likert + open) | ||
| |
2.2 | 118 | * Observations of errors (e.g. near-incidents, unsafe choices) |
| |
2.1 | 119 | ))) |
| |
2.2 | 120 | |Fewer dangerous situations|Near-incident reports|((( |
| 121 | * Define hazards in buildings beforehand and check (with observations of during hotwash) if these hazards are avoided or not | ||
| 122 | ))) | ||
| |
1.6 | 123 | |
| |
2.2 | 124 | |**Claim: Efficiency**|**Measurment(s)**|**How to test ** |
| 125 | |Faster mission execution|Total mission completion time|((( | ||
| 126 | * Timestamp of start (after briefing) till all located victims have been extracted | ||
| 127 | ))) | ||
| 128 | |Faster inside performance|First responder time inside|((( | ||
| 129 | * Timestamp of entry building till exist building (last located victim is exstracted) | ||
| 130 | ))) | ||
| |
2.1 | 131 | |
| |
2.2 | 132 | |**Claim: Situation Awareness**|**Measurment(s)**|**How to test ** |
| 133 | |Before entry |((( | ||
| 134 | Correctness of reported hazards, victims, layout | ||
| 135 | )))|((( | ||
| |
2.3 | 136 | * Before entry let squad leader and entry team (seperatly) sketch/map or describe inside of building (harzards, victims, layout) > compare these with the ground-truth |
| 137 | |||
| 138 | ((( | ||
| |
2.2 | 139 | |
| 140 | ))) | ||
| |
2.3 | 141 | ))) |
| |
2.2 | 142 | |During entry|((( |
| 143 | FR path logs | ||
| 144 | )))|((( | ||
| |
2.3 | 145 | * Compare plannend vs. executed path (how many or how big were the deviations? and were they acceptable?) and identify detours caused by misjudgment or new information |
| 146 | |||
| 147 | ((( | ||
| |
2.2 | 148 | |
| 149 | ))) | ||
| |
2.3 | 150 | ))) |
| |
2.2 | 151 | |After mission|((( |
| 152 | Correctness of reported hazards, victims, layout | ||
| |
2.3 | 153 | )))|((( |
| 154 | * Repeat sketching/mapping or descriptive task and compare the outcomes (improvement/ deterioration vs pre-entry) | ||
| 155 | ))) | ||
| 156 | |||
| |
2.4 | 157 | |**Claim: Health**|**Measurment(s)**|**How to test ** |
| 158 | |((( | ||
| 159 | Health remains acceptable | ||
| |
2.3 | 160 | )))|((( |
| |
2.4 | 161 | |
| 162 | |||
| 163 | Health indicators | ||
| 164 | )))|((( | ||
| 165 | * Define acceptable ranges (e.g. HR, temperature, etc.) beforehand and log these parapeter ranges | ||
| |
2.3 | 166 | ))) |
| |
2.4 | 167 | |((( |
| 168 | Issues handled in time | ||
| |
2.3 | 169 | )))|((( |
| |
2.4 | 170 | |
| 171 | |||
| 172 | Health issues tackled in acceptable time | ||
| 173 | )))|((( | ||
| 174 | * Log when | ||
| |
2.3 | 175 | ))) |
| |
2.1 | 176 | |
| |
2.2 | 177 | |
| 178 | |||
| |
1.2 | 179 | **10. Procedure (Step-by-Step)** |
| 180 | |||
| |
1.15 | 181 | 1. __Team preparation__: |
| |
1.8 | 182 | 11. FR team ROBOT is trained in operating the robot, analysing the camera stream, and pinning information on C3I |
| 183 | 11. Squad leader and BoO are trained for both teams in interpreting the health and location sensor data. | ||
| 184 | 11. Experiment leader knows where hazards and victims are in both buildings. | ||
| |
1.13 | 185 | 11. Anymal robot is tested with network in target buildings for experiment (without FR themselves seeing building!) |
| |
1.15 | 186 | 1. __Experiment preparation:__ |
| |
1.11 | 187 | 11. Building is prepped with victims, hazards, etc. |
| |
1.15 | 188 | 1. __Briefing:__ |
| |
1.8 | 189 | 11. Same for both teams for both building types: Building has been inspected from outside and is estimated safe for entry. Situation inside unknown. Victims possibly present. Goal: find, assess, and extract victims while avoiding and mapping hazards. |
| 190 | 11. One person is notified that their health sensor will be triggered during the Building B (difficult building) situation. | ||
| |
1.15 | 191 | 1. __Execution:__ |
| |
1.8 | 192 | 11. For FR team ROBOT, see: [[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]] |
| 193 | 11. For FR team HUMAN, see: [[UC04.4: Detailed indoor exploration without ANYMAL (USAR)>>2\. Specification.b\. Use Cases.UC04\.0\: Detailed indoor exploration.UC04\.3\: Detailed indoor exploration with ANYmal (USAR).WebHome]] | ||
| 194 | 11. During execution of both teams, performance will be measured by experiment leader: | ||
| 195 | 111. Mission completion time | ||
| 196 | 111. Health indicators stay within acceptable range | ||
| 197 | 111. Time for tackling any health alerts | ||
| 198 | 111. Track FR path | ||
| |
1.15 | 199 | 1. __Hotwash__: |
| |
1.21 | 200 | 11. Questions (specified per role, couple questions per topic) on: |
| |
1.8 | 201 | 111. Near-incident report |
| 202 | 111. Path inside | ||
| 203 | 111. FR location and status of hazards, victims, and layout | ||
| |
1.25 | 204 | 111. Mission effectiveness: e.g. self reported effectiveness of decisions |
| |
1.8 | 205 | 111. Self-reported workload |
| 206 | 111. Trust survey | ||
| |
1.18 | 207 | 11. Group discussion with feedback |
| |
1.2 | 208 | |
| |
1.15 | 209 | **~11. Planning:** |
| |
1.6 | 210 | |
| |
1.13 | 211 | * Team preparation: Day before. 1 hour. |
| |
1.11 | 212 | * Trial 1: |
| |
1.22 | 213 | ** Setup scenario: Test day 1. 09:00 - 09:30 |
| |
1.11 | 214 | ** Setup tech and perform checks: Test day 1. 09:00 - 09:30 |
| 215 | ** Briefing of each team individually (outside building): Test day 1: 09:00 - 09:30 | ||
| 216 | ** Mission execution: Test day 1. 09:30 - 10:30 | ||
| 217 | ** Hot wash: Test day 1. 10:30-11:00 | ||
| |
1.22 | 218 | ** Scenario reset: test day 1. 10:30-11:00 |
| |
1.11 | 219 | * Teams switch location: Test day 1. 11:00-11:15 |
| 220 | * Trial 2: | ||
| |
1.23 | 221 | ** (Setup scenario: Test day 1. 12:30 - 13:00) |
| |
1.11 | 222 | ** Setup tech and perform checks: Test day 1. 12:30 - 13:00 |
| 223 | ** Briefing of each team individually (outside building): Test day 1: 12:30 - 13:00 | ||
| 224 | ** Mission execution: Test day 1. 13:00 - 14:00 | ||
| 225 | ** Hot wash: Test day 1. 14:00-14:30 | ||
| |
1.23 | 226 | * Cleanup area and store tech. 14:00-14:30 |
| |
1.2 | 227 | |
| |
1.6 | 228 | |
| |
1.2 | 229 | |
| |
1.15 | 230 | **12. Materials** |
| |
1.2 | 231 | |
| |
1.12 | 232 | * For FRs: |
| 233 | ** 1x Anymal with teleop setup and networking | ||
| 234 | ** 2x Tablet with C3I for squad leader (one spare) | ||
| 235 | ** 1x Base of Operations with computer with C3I | ||
| 236 | ** 4x Health sensors | ||
| 237 | ** 4x Location sensors | ||
| 238 | ** 8x walky talky with two channels (?) (for FR team and BoO). | ||
| 239 | * For usecase: | ||
| 240 | ** 2x training building (~~100m2?) | ||
| 241 | ** Enviromental challenges: smoke machine, obstacles, etc. | ||
| 242 | ** ~~8x Actors or dummies for victims. | ||
| 243 | * 8x Clipboards with papers and pens for hotwash and questionnaires | ||
| |
1.6 | 244 | |
| |
1.15 | 245 | **13. Dependencies** |
| |
1.2 | 246 | |
| |
1.13 | 247 | * Availability of materials |
| |
1.15 | 248 | * Availability and functioning of ANYmal robot with teleoperation and network in target buildings |
| |
1.13 | 249 | * Availability of functioning network between robot, FRs, and BoO. |
| 250 | * Availability of: | ||
| 251 | ** Experiment participants | ||
| 252 | ** People willing to play victim | ||
| 253 | ** Experiment leaders | ||
| |
1.6 | 254 | |
| |
1.15 | 255 | **14. Success Criteria** |
| 256 | When mission(s) completed by both teams, and we can compare their performance using the metrics. | ||
| |
1.2 | 257 | |
| 258 | |||
| 259 |