Skip to Content
Version 14.4 by Tjalling Haije on 2026/02/16 08:49
Show last authors
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 the LiDAR and (depth) cameras while being tele-operated by the operator; Analyst interprets the camera feed and 3D map for victim and hazard detection.
31 c. Real-time feed (video/ 3D map / thermal?) streams to C3I (to HQ); Analyst places markers on C3I (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; on request of the Analyst the robot Operator moves the ANYmal closer 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 in C3I 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 in C3I; 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 == Open questions on technology capabilities ==
48
49 1. Anymal:
50 11. What sensors does the Anymal have? LiDAR, day-light camera, depth-camera, thermal camera, microphones, speakers?
51 11. How many of these sensors are available to the operator/analyst?
52 11. Is the operator UI connected with C3I?
53 11. Can the operator share information via the operator UI connected to C3I to the command center? If so, in what form? Photo with image and text? A short video? A livestream?
54 11. Can the operator place a marker on the C3I map with a detection (e.g. hazard or victim)? Can information be attached to that marker? Can that marker be confirmed / prioritized / further specified with constraints (e.g. access constraints)?
55 11. Can the robot do object detection for finding victims? If so, how are results presented to the operator/analyst?
56 1. C3I:
57 11. What information can be logged in C3I on the teamleaders tablet? Can suggested routes and no-go zones also be specified?
58
59 == Open questions on user needs ==
60
61 1. HQ
62 11. At what level of detail do they require Situation Awareness? Does this differ per situation?
63 11. Does HQ communicate always via the teamlead, or also directly with the robot operator/analyst? As in, does the teamleader "confirm" new markers etc in C3I before they become visible to HQ?
64 11. In what way does HQ want to maintain SA? Markers on C3I map with text description, with image and description, only image with category, multiple images, short video, livestream, live 3D map, live thermal camera stream, audio recordings.
65 11. What are the tasks of HQ
66 11. How many teams typically are coordinated by HQ?
67 11. How much time does HQ have available for maintaining SA and communicating with the teamlead etc on this part of the mission?
68 1. Teamlead
69 11. At what level of detail does the teamlead require Situation Awareness? Which info do they need? Does this differ per situation?
70 11. In what way does teamlead want to maintain SA? Should they have enough info from inspecting the C3I map, do they require talking with the analyst, or do they require looking along to inspect the robot sensors?
71 11. What other tasks does the teamlead have? How much time do they have available for maintaining SA on the mission / talking with the analyst / talking with HQ / making plans, etc.
72 11. How many teams does the teamlead have? Are they always close to the operator/analyst (shouting distance), or not?
73 11. How do the analyst and teamlead communicate? Via talking in person, or via radio?
74 1. Operator/Analyst
75 11. What tasks does the Analyst have: analysing the robot sensor streams, instructing operator for where to go, updating the teamlead, updating the C3I interface, other tasks?
76 11. How does the Analyst communicate with others, via speech in person, via radio, via C3I?
77
78
79
80 (% class="box warningmessage" %)
81 (((
82 Table below need to be updated
83 )))
84
85 |=Claims (title)|=Function|=Effect(s)|=Action Sequence Step(s)
86 |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 
87 → Measured with FR path logs or near-incident reports.|2a
88 |CL2 Improved FR SA |SNAKE camera visual confirmation|EFXX: Improves SA of FR by inspecting small spaces 
89 → Measure with NASA TLX? |4b
90 |CL2 Improved victim detection rate in small spaces|SNAKE camera visual confirmation|EFXX: Victim discovery rate increased
91 → Measured with number of victims detected & time to victim detection, compared to manual entry.|2b, 2c
92 |CL3 Safer responder routing|Hazard identification via robot|EFXX: First responder safety increased
93 → Measured with map updates and avoided hazards.|2c, 3a
94 |CL4 Trustworthy SA|Operator-validated visuals|EFXX: Trust in robot findings increased by operator confirmation
95 → Measured with trust survey or follow-up interviews.|4a
96 |CL5 Operational speed improved|Robot scouts ahead of team|EFXX: Operational speed improved
97 → Measured with time-per-room metrics.|2a, 3c