UC04.4: Detailed indoor exploration without ANYMAL (USAR)

|=**Objective**|=

|=Description|=(((

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 and Startup =====

20

21

a. **Squad leader **receives building status (safe enough for human entry) + safe viable openings.

22

b. 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.**

23

c. **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.

24

d. **Comms/network check**: verify stable uplink for wearable streams between worksite and base of operations via walky-talky.

25

26

===== 2. Interior 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

a. **Squad leader** decides when to transition to victim extraction and in what order, route, etc.

35

b. **First responders **extract the victims.

36

37

===== 3. Remote Monitoring, Alerts, and Coordinated Escalation =====

38

39

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.

40

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:

41

• 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)**:

43

1) **Squad leader action**: immediate check-in (voice), buddy-check instruction, micro-reroute to nearest safe point / egress, or pause task.

44

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.

45

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.

46

47

48

(% class="box warningmessage" %)

49

(((

50

The above action sequence needs to be checked by a domain expert for validity

51

)))

52

53