Skip to Content
Version 29.1 by Rosa Van Tuijn on 2026/03/25 10:37
Show last authors
1 |=**Objective**|=
2 |=Description|=(((
3 Baseline usecase with current way of working for entering a building and extraction victims, augmented with health and location sensors of first-responders for BoO.
4 )))
5 |**TDP**|2c: IDP "role-based, context-specific views",
6 |**IDP**|
7 |**Actors**|Team leader, 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/]])
8 |**Pre-Condition**|(((
9 * Structure is flagged as (relatively?) **safe for direct human entry**; sector/ worksite allocated. Viable entrance identified.
10 * **FRs wearables** distributed, connected, and calibrated.
11 )))
12 |**Post-Condition**|(((
13 * Health alerts handled; intervention performed if needed.
14 )))
15 |**Status**|Hazards marked and/or victims detected; team proceeds with increased safety.
16
17 === **Action Sequence** ===
18
19 ===== 1. Deployment, Startup and decision making =====
20
21 *  a. **Squad leader **receives building status (safe enough for human entry) + safe viable openings.
22 * b. **Comms/network check**: verify stable uplink for wearable streams between worksite and base of operations via walky-talky.
23 * c. Squad leader selects an **entry decision** (go / no-go / partial entry) and makes decisions regarding: entry team composition, route, objectives, time limits, and abort criteria. The decision is communicated with the **BoO.**
24 *  d. **First responders** check and calibrate wearable sensors (health + localization); the squad leader confirms **team baseline status** are “green/ready” on the squad dashboard; **base of operations** sees the same status across all teams.
25
26 ===== 2. Indoor Exploration with two **first responders** =====
27
28 *  a. **First responders** enter as pair via the safest viable opening; wearables are used for **continuous tracking** (location + vitals) and display their status and location on the C3I of the **BoO**.
29 * b. **First responders** explores building and provide updates to **squad leader** via walky-talky, locating **blocked corridors, collapse risk, gas/smoke pockets, heat zones, viable routes, possible victims.**
30 * c. **Squad leader **monitors state of mission, and communicates progress back to the **BoO. **
31 * d. **Someone **notes the encountered dangers (in a form?) from inside the building?
32
33 4. Victim extraction
34
35 * a. **Squad leader** decides when to transition to victim extraction and in what order, route, etc.
36 * b. **First responders **extract the victims.
37
38 ===== 3. Remote Monitoring, Alerts, and Coordinated Escalation =====
39
40 *  a. **Base of operations** monitors the squads active in the operation via C3I and health monitoring and location; squad leader monitors his own team and receives health/location updates from BoO via walky-talky.
41 *  b. If a responder crosses a threshold (e.g., heart rate spike, heat stress indicator, immobility, rapid elevation change, loss of signal), an **alert** is generated simultaneously: Base of operations receives the same alert in the multi-team view (for cross-team support decisions), and communicates this via walky-talky to the **squad leader**.
42 *  c. **Escalation policy (two-level response)**: 1) **Squad leader action**: immediate check-in (voice), buddy-check instruction, micro-reroute to nearest safe point / egress, or pause task. 2) **Base of operations action**: dispatch medical support / reallocate teams / request additional sensing (robot reposition, drone overwatch), and initiate comms contingency if signal degradation persists.
43 *  d. If readings normalize, event is closed with a short note; if abnormal readings persist, the squad leader executes abort criteria (partial withdrawal / full extraction) while base coordinates site-level support and deconfliction with other teams.
44
45
46
47 (% class="box warningmessage" %)
48 (((
49 The above action sequence needs to be checked by a domain expert for validity
50 )))
51
52 |=Claims (title)|=Function|=Effect(s)|=Action Sequence Step(s)
53 |=(% colspan="4" scope="col" %)No seperate claims for this usecase. Instead focus on doing questionnaires etc to compare with the ANYMAL version.