Skip to Content

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

Version 29.1 by Rosa Van Tuijn on 2026/03/25 10:37
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. 

TDP2c: IDP "role-based, context-specific views", 
IDP 
ActorsTeam leader, Safety officer (at HQ), Entry Team (FRs) (described at 4. Personas & Problem Scenarios and Direct Stakeholders)
Pre-Condition
  • Structure is flagged as (relatively?) safe for direct human entry; sector/ worksite allocated. Viable entrance identified. 
  • FRs wearables distributed, connected, and calibrated.
Post-Condition
  • Health alerts handled; intervention performed if needed.
StatusHazards marked and/or victims detected; team proceeds with increased safety.

Action Sequence

1. Deployment, Startup and decision making
  •  a. Squad leader receives building status (safe enough for human entry) + safe viable openings.
  •     b. Comms/network check: verify stable uplink for wearable streams between worksite and base of operations via walky-talky.
  •     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.
  •  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.
2. Indoor Exploration with two first responders
  •  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.
  •     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.
  •     c. Squad leader monitors state of mission, and communicates progress back to the BoO. 
  •     d. Someone notes the encountered dangers (in a form?) from inside the building?

4. Victim extraction

  •     a. Squad leader decides when to transition to victim extraction and in what order, route, etc. 
  •     b. First responders extract the victims.
3. Remote Monitoring, Alerts, and Coordinated Escalation
  •  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.
  •  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.
  •  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.
  •  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.

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

Claims (title)FunctionEffect(s)Action Sequence Step(s)
No seperate claims for this usecase. Instead focus on doing questionnaires etc to compare with the ANYMAL version.