Last modified by Tjalling Haije on 2025/07/14 08:50

From version 1.1
edited by Tjalling Haije
on 2025/07/07 10:59
Change comment: There is no comment for this version
To version 3.1
edited by Mark Rinse van Koningsveld
on 2025/07/13 22:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -UC01.0: Health Sensors
1 +UC03.0: Wide area assessment
Parent
... ... @@ -1,1 +1,1 @@
1 -2\. Specification.b\. Use Cases.Usecase\: Health sensors (Firefighters).WebHome
1 +2\. Specification.b\. Use Cases.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.TjallingHaije
1 +XWiki.MarkVanKoningsveld
Content
... ... @@ -1,3 +1,57 @@
1 -{{toc/}}
1 +**Objective**
2 +[[OB01: Increase effectiveness through exploration, sensing and communication means>>path:#]]
3 +[[OB04: Improve safety by providing overviews and warnings of environment conditions>>path:#]]
2 2  
5 +Use RTK-enabled outdoor drones for wide area assessment before and during USAR operations. Drones hover near structures and provide high-resolution video, controlled manually by an operator. Teams and command staff use the footage to support planning, assess hazards, and make routing decisions.
6 +
7 +**TDP**
8 +TDP1, TDP4, TDP6
9 +
10 +**IDP**
11 +IDP1, IDP3
12 +
13 +**Actors**
14 +Drone Operator, USAR Rescuers, Command Center Staff, Camera Analyst (optional)
15 +
16 +**Pre-Condition**
17 +Drone is operational and connected; a need for external visual assessment is identified.
18 +
19 +**Post-Condition**
20 +Hazards and structures externally assessed; situational awareness increased across teams.
21 +
22 +----
23 +
24 +=== **Action Sequence** ===
25 +
26 +1. **Deployment and Initial Positioning**
27 + a. Command or team lead requests drone support for external area overview.
28 + b. Drone operator launches drone, checks connectivity and RTK accuracy.
29 + c. Live feed is shared with teams and command center.
30 +1. **Initial Area Assessment**
31 + a. Drone hovers and performs a wide pass along the operational area.
32 + b. Camera operator or analyst identifies terrain features and visible hazards.
33 + c. Findings are noted by command staff for initial planning and worksite layout.
34 +1. **Detailed Look Upon Request**
35 + a. A responder team or command staff requests specific inspection (e.g. rooftop stability, exit blockage).
36 + b. Operator manually moves drone and zooms in for closer inspection.
37 + c. Team uses footage for tactical decision-making or confirmation before approach.
38 +1. **Data Sharing and Coordination**
39 + a. Screenshots or annotated video are shared across teams.
40 + b. Visual information is added to digital maps or discussed in team briefings.
41 + c. Drone remains in overwatch or is redirected to the next location.
42 +
43 +----
44 +
45 +=== **Claims (title)** ===
46 +
47 +|=Claims (title)|=Function|=Effect(s)|=Action Sequence Step(s)
48 +|CL1 Improved external SA for teams|Live video from hovering drone|EFXX: Situation Awareness improved → Measured with SAGAT or questionnaire.
49 +(Teams operate with up-to-date visuals of surroundings.)|2a, 2b, 3a
50 +|CL2 Safer team movement planning|Visual confirmation of hazards|EFXX: Safety of responders improved → Measured with near-incident reporting or field logs.
51 +(Avoids unstable paths or collapse zones.)|3a, 3b, 3c
52 +|CL3 Increased planning speed|Area scan before deployment|EFXX: Operational tempo improved → Measured with time-to-plan or decision cycle.|2a, 2c, 4b
53 +|CL4 Lower workload for reconnaissance|Drone replaces physical scout|EFXX: Mental workload decreased → Measured with NASA TLX.
54 +(Removes need for physical recon of rooftops or hard-to-access zones.)|2b, 3b
55 +|CL5 Shared SA between field and base|Feed shared across all actors|EFXX: Coordination improved → Measured with mission replay or comms analysis.|1c, 4a, 4b
56 +
3 3