Project homeWiki source code of UC04.4: Detailed indoor exploration without ANYMAL (USAR)
Last modified by Tjalling Haije on 2026/04/20 10:31
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
27.10 | 1 | |=**Objective**|= |
| |
10.3 | 2 | |=Description|=((( |
| |
27.10 | 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. |
| |
10.3 | 4 | ))) |
| |
30.2 | 5 | |**TDP**| |
| 6 | |**IDP**|[[IDP1 — Role-Based, Context-Specific Information Distribution>>2\. Specification.Requirements.IDP1 — Role-Based, Context-Specific Information Distribution.WebHome]] | ||
| 7 | |**Actors**|Squad leader, Safety officer (at HQ), Entry Team (FRs), structural expert (FR), shoring 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/]]) | ||
| |
10.3 | 8 | |**Pre-Condition**|((( |
| |
30.2 | 9 | * Structural integrity of building and whether **human entry is safe is unknown;** sector/ worksite allocated. Viable entrance identified. |
| |
10.3 | 10 | ))) |
| |
10.4 | 11 | |**Post-Condition**|((( |
| 12 | * Health alerts handled; intervention performed if needed. | ||
| 13 | ))) | ||
| |
8.1 | 14 | |**Status**|Hazards marked and/or victims detected; team proceeds with increased safety. |
| |
1.1 | 15 | |
| 16 | === **Action Sequence** === | ||
| 17 | |||
| |
30.2 | 18 | ===== 1. Deployment, Startup, and decision making ===== |
| |
1.1 | 19 | |
| |
30.2 | 20 | * ((( |
| 21 | ===== a. **Squad leader **and **Entry Team **arrive at building in allocated worksite. ===== | ||
| 22 | ))) | ||
| 23 | * b. **Structural expert (FR) **inspects building from outside. Decides with squad leader if **safe entry possible or shoring needed**. | ||
| 24 | * c. Shoring team does shoring of the building to enable safe entry. | ||
| 25 | * 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.** | ||
| 26 | * d. **First responders** do a comms and equipment check with **squad leader**. **Squad leader **informs **BoO **of mission start**.** | ||
| |
1.1 | 27 | |
| |
30.2 | 28 | 2. Indoor Exploration with two **first responders** |
| |
14.1 | 29 | |
| |
30.2 | 30 | * a. **First responders** enter as pair via the safest viable opening; walky-talkies are used for **status updates** (location + vitals). |
| 31 | * 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.** | ||
| 32 | * c. **Squad leader **monitors state of mission, and communicates progress back to the **BoO. ** | ||
| 33 | * d. **Someone **notes the encountered dangers (in a form?) from inside the building. | ||
| |
17.1 | 34 | |
| |
30.2 | 35 | 3. Decision making on victim extraction |
| |
27.12 | 36 | |
| |
30.2 | 37 | * a. **First responders **exit the building, and discuss results with **squad leader. Squad leader **does **decision making** on priorities for victim extraction, route, etc. |
| |
28.2 | 38 | |
| |
30.1 | 39 | ===== 4. Remote Monitoring, Alerts, and Coordinated Escalation ===== |
| |
17.1 | 40 | |
| |
30.2 | 41 | * a. Squad leader monitors his own team and receives health/location updates from BoO via walky-talky. |
| 42 | * b. **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 | * c. 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. | ||
| |
17.1 | 44 | |
| 45 | |||
| |
28.2 | 46 | |
| |
27.7 | 47 | (% class="box warningmessage" %) |
| 48 | ((( | ||
| |
27.8 | 49 | The above action sequence needs to be checked by a domain expert for validity |
| |
27.7 | 50 | ))) |
| |
14.1 | 51 | |
| |
6.1 | 52 | |=Claims (title)|=Function|=Effect(s)|=Action Sequence Step(s) |
| |
27.9 | 53 | |=(% colspan="4" scope="col" %)No seperate claims for this usecase. Instead focus on doing questionnaires etc to compare with the ANYMAL version. |