Wiki source code of h. Test SFT1: System baseline test
Version 1.19 by Tjalling Haije on 2026/03/24 09:19
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | **Experiment title** | ||
| 2 | System baseline test | ||
| 3 | |||
| 4 | |||
| 5 | **2. Objective / Research Question** | ||
| 6 | Do the SYNERGISE technologies together improve the SYNERGISE [[Objectives>>2\. Specification.Objectives.WebHome]] (stated below) without negative effects? | ||
| 7 | |||
| 8 | 1. Mission effectiveness | ||
| 9 | 1. Mission efficiency | ||
| 10 | 1. FR Health | ||
| 11 | 1. FR and victim safety | ||
| 12 | |||
| 13 | **3. Hypotheses / Expectations (optional)** | ||
| 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 | |||
| 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 | |||
| 24 | **4. Scenario / Context** | ||
| 25 | ASR3: Detailed indoor exploration | ||
| 26 | |||
| 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 | |||
| 35 | **5. Participants** | ||
| 36 | |||
| 37 | * FR team ROBOT: | ||
| 38 | ** 1x Squad leaders | ||
| 39 | ** 1x Robot operator | ||
| 40 | ** 1x Robot analyst | ||
| 41 | ** 2x First responder | ||
| 42 | * FR team HUMAN: | ||
| 43 | ** 1x Squad leaders | ||
| 44 | ** 2x First reponder | ||
| 45 | * Base of Operations: | ||
| 46 | ** 1x Safety officer / medical specialist | ||
| 47 | ** Team lead | ||
| 48 | |||
| 49 | Number of participants: 9 | ||
| 50 | |||
| 51 | |||
| 52 | **6. System(s) Under Test** | ||
| 53 | |||
| 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 | ))) | ||
| 80 | |||
| 81 | |||
| 82 | |||
| 83 | **7. Tasks** | ||
| 84 | |||
| 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 | |||
| 90 | **8. Experimental Conditions / Variants** | ||
| 91 | |||
| 92 | Two buildings: | ||
| 93 | |||
| 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). | ||
| 96 | |||
| 97 | Trial 1: | ||
| 98 | |||
| 99 | * FR Team ROBOT does Building A | ||
| 100 | * FR team HUMAN does Building B | ||
| 101 | |||
| 102 | Trial 2: | ||
| 103 | |||
| 104 | * FR Team ROBOT does Building B | ||
| 105 | * FR team HUMAN does Building A | ||
| 106 | |||
| 107 | **9. Measurements** | ||
| 108 | |||
| 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]] | ||
| 110 | |||
| 111 | |||
| 112 | **10. Procedure (Step-by-Step)** | ||
| 113 | |||
| 114 | 1. __Team preparation__: | ||
| 115 | 11. FR team ROBOT is trained in operating the robot, analysing the camera stream, and pinning information on C3I | ||
| 116 | 11. Squad leader and BoO are trained for both teams in interpreting the health and location sensor data. | ||
| 117 | 11. Experiment leader knows where hazards and victims are in both buildings. | ||
| 118 | 11. Anymal robot is tested with network in target buildings for experiment (without FR themselves seeing building!) | ||
| 119 | 1. __Experiment preparation:__ | ||
| 120 | 11. Building is prepped with victims, hazards, etc. | ||
| 121 | 1. __Briefing:__ | ||
| 122 | 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. | ||
| 123 | 11. One person is notified that their health sensor will be triggered during the Building B (difficult building) situation. | ||
| 124 | 1. __Execution:__ | ||
| 125 | 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]] | ||
| 126 | 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]] | ||
| 127 | 11. During execution of both teams, performance will be measured by experiment leader: | ||
| 128 | 111. Mission completion time | ||
| 129 | 111. Health indicators stay within acceptable range | ||
| 130 | 111. Time for tackling any health alerts | ||
| 131 | 111. Track FR path | ||
| 132 | 1. __Hotwash__: | ||
| 133 | 11. Questions (specified per role) on: | ||
| 134 | 111. Near-incident report | ||
| 135 | 111. Path inside | ||
| 136 | 111. FR location and status of hazards, victims, and layout | ||
| 137 | 111. Mission effectiveness ? Decision Making effectiveness? | ||
| 138 | 111. Self-reported workload | ||
| 139 | 111. Trust survey | ||
| 140 | 11. Group discussion with feedback | ||
| 141 | |||
| 142 | **~11. Planning:** | ||
| 143 | |||
| 144 | * Team preparation: Day before. 1 hour. | ||
| 145 | * Trial 1: | ||
| 146 | ** Setup usecase: Test day 1. 09:00 - 09:30 | ||
| 147 | ** Setup tech and perform checks: Test day 1. 09:00 - 09:30 | ||
| 148 | ** Briefing of each team individually (outside building): Test day 1: 09:00 - 09:30 | ||
| 149 | ** Mission execution: Test day 1. 09:30 - 10:30 | ||
| 150 | ** Hot wash: Test day 1. 10:30-11:00 | ||
| 151 | ** Usecase reset: test day 1. 10:30-11:00 | ||
| 152 | * Teams switch location: Test day 1. 11:00-11:15 | ||
| 153 | * Trial 2: | ||
| 154 | ** Setup usecase: Test day 1. 12:30 - 13:00 | ||
| 155 | ** Setup tech and perform checks: Test day 1. 12:30 - 13:00 | ||
| 156 | ** Briefing of each team individually (outside building): Test day 1: 12:30 - 13:00 | ||
| 157 | ** Mission execution: Test day 1. 13:00 - 14:00 | ||
| 158 | ** Hot wash: Test day 1. 14:00-14:30 | ||
| 159 | ** Cleanup area and store tech. 14:00-14:30 | ||
| 160 | |||
| 161 | |||
| 162 | |||
| 163 | **12. Materials** | ||
| 164 | |||
| 165 | * For FRs: | ||
| 166 | ** 1x Anymal with teleop setup and networking | ||
| 167 | ** 2x Tablet with C3I for squad leader (one spare) | ||
| 168 | ** 1x Base of Operations with computer with C3I | ||
| 169 | ** 4x Health sensors | ||
| 170 | ** 4x Location sensors | ||
| 171 | ** 8x walky talky with two channels (?) (for FR team and BoO). | ||
| 172 | * For usecase: | ||
| 173 | ** 2x training building (~~100m2?) | ||
| 174 | ** Enviromental challenges: smoke machine, obstacles, etc. | ||
| 175 | ** ~~8x Actors or dummies for victims. | ||
| 176 | * 8x Clipboards with papers and pens for hotwash and questionnaires | ||
| 177 | |||
| 178 | **13. Dependencies** | ||
| 179 | |||
| 180 | * Availability of materials | ||
| 181 | * Availability and functioning of ANYmal robot with teleoperation and network in target buildings | ||
| 182 | * Availability of functioning network between robot, FRs, and BoO. | ||
| 183 | * Availability of: | ||
| 184 | ** Experiment participants | ||
| 185 | ** People willing to play victim | ||
| 186 | ** Experiment leaders | ||
| 187 | |||
| 188 | **14. Success Criteria** | ||
| 189 | When mission(s) completed by both teams, and we can compare their performance using the metrics. | ||
| 190 | |||
| 191 | |||
| 192 |