Wiki source code of UC04.3: Detailed indoor exploration with ANYmal (USAR)
Version 11.1 by Tjalling Haije on 2026/02/16 08:19
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | |=**Objective**|=[[OB01: Increase effectiveness through exploration, sensing and communication means>>path:#]] | ||
| 2 | [[OB04: Improve safety by providing overviews and warnings of environment conditions>>path:#]] | ||
| 3 | |=Description|=((( | ||
| 4 | Enable safe, data‑driven interior reconnaissance and victim triage **before** human entry, with continuous **FR health/location monitoring** informing decisions, rotations, and evacuation. | ||
| 5 | ))) | ||
| 6 | |**TDP**|1a: Pattern: “Robots first, then humans.”, 2c: IDP "role-based, context-specific views", | ||
| 7 | |**IDP**| | ||
| 8 | |**Actors**|Team leader, Robot operator, Analyst, Safety officer (at HQ), Entry Team (FRs) (described at [[4. Personas & Problem Scenarios>>path:/bin/view/Main/sdf/4.%20Scenarios%20%26%20Personas/]] and [[Direct Stakeholders>>path:/bin/view/Main/sdf/Stakeholders/Direct/]]) | ||
| 9 | |**Pre-Condition**|((( | ||
| 10 | * Structure is flagged as **unsafe for direct human entry**; sector/ worksite allocated. | ||
| 11 | * **ANYmal **is mission-ready (battery, controls, and payload checked). | ||
| 12 | * **FRs wearables** distributed, connected, and calibrated. | ||
| 13 | * **C3I is online**, role-based views are configurated (Operator/ Analyst/ Team leader/ Safety officer); **5G pods** are installed for connection. | ||
| 14 | ))) | ||
| 15 | |**Post-Condition**|((( | ||
| 16 | * | ||
| 17 | * Health alerts handled; intervention performed if needed. | ||
| 18 | ))) | ||
| 19 | |**Status**|Hazards marked and/or victims detected; team proceeds with increased safety. | ||
| 20 | |||
| 21 | === **Action Sequence** === | ||
| 22 | |||
| 23 | 1. **Deployment and Startup** | ||
| 24 | a. Team leader labels the buildings interior as **robot-first** (no human entry). | ||
| 25 | b. Robot Operator positions ANYmal at the threshold of the building while Analyst opens the control/analyst workspace of ANYmal in C3I. | ||
| 26 | c. Wearables; Entry team confirms connection and baseline vitals. Safety officer sees green 'ready' status on the health/ location dashboard in C3I. | ||
| 27 | d. Comms/ network connection check; confirms connection is stable for robot video/ LiDAR and wearable streams between worksite and HQ. | ||
| 28 | 1. **Exploration and navigation** | ||
| 29 | a. ANYmal enters through the safest/ big enough opening with remote Operator tele-operating the tight passage. | ||
| 30 | b. ANYmal builds a live 3D map (LiDAR) with XX sensors (only camera?) for victim detection; Analyst interprets layers of information. | ||
| 31 | c. Real-time feed (video/ LiDAR/ thermal?) streams to C3I (to HQ); Analyst places markers (doors, unstable zones, possible victims). | ||
| 32 | 1. **Victim detection and Robot/Operator control** | ||
| 33 | a. A candidate victim is detected on the LiDAR map/ camera view (with a confidence score?) by the Analyst; the Robot operator manually controls ANYmal to verify. | ||
| 34 | b. If equipped, ANYmal's arm can nudge light debris or open door to approach the possible victim detection for verification. | ||
| 35 | c. Victim locations are confirmed, tagged, and prioritized with access contraints (blocked corridor, gas risk, etc.) for Team leader's plan. | ||
| 36 | 1. **Team coordination and decision support** | ||
| 37 | a. An updated worksite map (victims, no-go areas, suggested routs?) is visable on the Team leader's tablet; and addional information is communicated with the Team leader by the Analyst. | ||
| 38 | b. Team leader refines the plan (who enters, route, tools) and briefs Entry team. Decision rationale is logged in C3I for HQ. | ||
| 39 | c. .. | ||
| 40 | 1. **Remote monitoring and escalation** | ||
| 41 | a. Part of the entry team is now inside of the building; while safety officer at HQ verfies continious FR vitals and positioning. | ||
| 42 | b. If critical threshold is crossed (e.g. high heart rate/ temperature spike), Team leader recieves an on-dashboard critical alert while the affected FR (or/and buddy?) sees a local alarm (LED/ audio/ haptic). | ||
| 43 | c. Escallation policy: alarms . | ||
| 44 | |||
| 45 | === === | ||
| 46 | |||
| 47 | |=Claims (title)|=Function|=Effect(s)|=Action Sequence Step(s) | ||
| 48 | |CL1 Improve safety for responders|Robot enters unsafe or blocked zones|EFXX: Improves safety of responder by having robot explore unsafe or blocked zones instead | ||
| 49 | → Measured with FR path logs or near-incident reports.|2a | ||
| 50 | |CL2 Improved FR SA |SNAKE camera visual confirmation|EFXX: Improves SA of FR by inspecting small spaces | ||
| 51 | → Measure with NASA TLX? |4b | ||
| 52 | |CL2 Improved victim detection rate in small spaces|SNAKE camera visual confirmation|EFXX: Victim discovery rate increased | ||
| 53 | → Measured with number of victims detected & time to victim detection, compared to manual entry.|2b, 2c | ||
| 54 | |CL3 Safer responder routing|Hazard identification via robot|EFXX: First responder safety increased | ||
| 55 | → Measured with map updates and avoided hazards.|2c, 3a | ||
| 56 | |CL4 Trustworthy SA|Operator-validated visuals|EFXX: Trust in robot findings increased by operator confirmation | ||
| 57 | → Measured with trust survey or follow-up interviews.|4a | ||
| 58 | |CL5 Operational speed improved|Robot scouts ahead of team|EFXX: Operational speed improved | ||
| 59 | → Measured with time-per-room metrics.|2a, 3c |