Changes for page f. Test CFT3: Two Detailed Use Cases

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-b. Test
	1	+f. Test CFT3: Two Detailed Use Cases

Content

...	...	@@ -1,33 +1,74 @@
1	1	= 1. Introduction =
2	2
3		-//<include a short summary of the claims to be tested, i.e., the effects of the functions in a specfic use case>//
	3	+This study evaluates the operational impact and user acceptance of two technological interventions in emergency response: (1) autonomous indoor drones for victim detection and (2) physiological and environmental sensor systems for monitoring first responder health. The primary claims tested are whether these technologies can enhance situational awareness, improve safety, and integrate seamlessly into existing workflows without overburdening personnel. The analysis focuses on stakeholder feedback from first responders, drone operators, and medics, emphasizing usability, trust, and coordination in high-stress environments.
4	4
5		-
6	6	= 2. Method =
7	7
8	8
9	9	== 2.1 Participants ==
10	10
	10	+Three evaluation sessions were conducted. The first session focused on Use Case 2 (physiological and environmental sensors) and included 10 participants, including: firefighters, USAR personnel, and team leaders. The second and third sessions addressed Use Case 1 (autonomous indoor drones). The second session involved 6 participants, primarily general first responders, while the third session included 2 experienced drone pilots who provided technical and operational insights into drone deployment and navigation.
11	11
12	12	== 2.2 Experimental design ==
13	13
	14	+Each use case was presented through a structured action sequence, simulating realistic operational steps. For every step in the sequence, participants were asked targeted questions using polls. Each sequence included between 2 to 5 questions, designed to elicit feedback on usability, trust, and integration of the proposed technologies. After each participant submitted their poll response, the aggregated results were displayed on screen, prompting open discussion. While not every question led to extended dialogue, many sparked valuable exchanges that clarified user expectations and concerns. At the end of each session, participants were asked two closing questions: (1) their overall impression of the use case, and (2) their expectations for how such technologies might evolve over the next 10 years. These questions helped contextualize the feedback within both current and future operational realities.
14	14
15	15	== 2.3 Tasks ==
16	16
	18	+Participants evaluated the deployment, operation, and integration of the drone and sensor systems in simulated mission phases. Tasks included assessing drone startup, autonomous navigation, victim detection, and the use of health monitoring dashboards during live operations.
17	17
18	18	== 2.4 Measures ==
19	19
	22	+Feedback was captured through qualitative observations, direct quotes, and Likert-scale agreement ratings on key usability and trust dimensions. Measures focused on perceived usefulness, cognitive load, trust in automation, and integration with team workflows.
20	20
21	21	== 2.5 Procedure ==
22	22
	26	+Each session began with a scenario briefing and a walkthrough of the proposed technology in action. Participants were guided through a detailed action sequence representing a typical mission phase. At each step, they responded to poll questions, which were then visualized and discussed in real time. This format allowed for both quantitative and qualitative feedback. The sessions concluded with reflective questions about the overall use case and long-term expectations, encouraging participants to think beyond the immediate implementation and consider future developments.
23	23
24	24	== 2.6 Material ==
25	25
	30	+Materials included scenario descriptions, interface mockups (e.g., traffic-light health dashboards), and conceptual visualisations Use case flows. They were shown in the program Mentimeter, to create an interactive session. These were used to prompt discussion and elicit targeted feedback on system behavior and user interaction.
26	26
27	27	= 3. Results =
28	28
	34	+Across the three sessions, participants expressed strong interest in the potential of both technologies, while also identifying critical usability and integration challenges.
29	29
	36	+**Use Case 1 (Autonomous indoor drones):**
	37	+
	38	+* Feedback centered on the need for **rapid drone deployment**, **minimal interference with human responders**, and **reliable victim detection**. First responders highlighted the importance of **parallel deployment protocols** and **geofencing** to avoid human-drone conflicts. Drone pilots emphasized the value of having **dedicated operators and analysts**, and supported the integration of **friend-or-foe identification** to improve AI recognition.
	39	+* Participants agreed that drones are a valuable **additional tool**, but (currently) not a replacement for dogs or human responders. Deployment timing depends on the situation: in urgent cases, responders may enter without waiting for a drone; in international USAR missions, there may be more time to prepare and deploy drones.
	40	+* Regulations is also something to take into consideration—drones are not allowed to fly near personnel, requiring coordination and certification.
	41	+* Participants noted that **drone teams are often separate from firefighting teams** and may not fit into standard vehicle deployments. In USAR, drone operation could be an **additional role** for technical search specialists. There was consensus that drones should **continue scanning after detecting a victim**, unless they can provide direct aid.
	42	+* Drone pilots highlighted technical preferences, such as combining **RGB and LIDAR feeds**, and noted that **indoor noise and sensor interference** are real concerns.
	43	+* Trust in the drone team varied, especially among participants unfamiliar with previous CFTs or without experience with these technologies in the field. Some responders were initially skeptical but acknowledged that **standard operating procedures (SOPs)** could help integrate drone teams more effectively.
	44	+* Participants also emphasized the need for **flexible information filtering**, allowing HQ to suppress irrelevant data and team leaders to focus on their operational area.
	45	+
	46	+**Use Case 2 (Physiological and environmental sensors):**
	47	+
	48	+* Participants emphasized the importance of **minimal setup time**, especially for firefighters who need to deploy immediately. USAR personnel, operating in longer shifts, were more tolerant of a 10–15 minute setup window.
	49	+* There was strong support for **default configurations**, **discreet personal alerts**, and **role-based interfaces**. Firefighters preferred simple, glanceable indicators (e.g., traffic-light status), while USAR medics wanted access to more detailed data.
	50	+* Participants stressed that **not everyone needs to see everything**—information should be filtered based on role and task. For example, a smoke director or safety officer might monitor vitals instead of the team leader. The system should provide **yes/no answers** to task-relevant questions rather than raw data.
	51	+* There was consensus that **team leaders must retain control**, including the ability to mute alerts when needed to maintain situational awareness.
	52	+* Views on escalation varied: some participants preferred **automatic escalation to HQ**, while others particpants favored **team leader confirmation first**.
	53	+* Participants also supported the idea of a **dedicated tech or medic role** to manage sensor readiness and monitoring.
	54	+* The system was seen as a way to **increase resilience**, but participants warned against over-reliance or information overload.
	55	+
30	30	= 4. Discussion =
31	31
	58	+The evaluation sessions highlighted the importance of aligning technological innovation with the operational logic and tempo of emergency response teams. Rather than focusing solely on functionality, participants repeatedly emphasized the need for systems to respect the **division of roles**, (**national) protocols**, and **mission-specific constraints**.
32	32
	60	+One key insight was the **diversity of expectations across countries and roles**. For example, Dutch and Polish participants had different views on escalation authority—some preferring centralized confirmation, others favoring automatic escalation. Similarly, firefighters and USAR personnel differed in their tolerance for setup time and information density. These differences underscore that **designing a solution that satisfies everyone is inherently difficult**. Different roles (Firefighters, USAR teams, medics, drone pilots, and team leaders) each brought distinct expectations shaped by their mission profiles, team sizes, and regulatory environments.
	61	+
	62	+Another recurring theme was the **importance of trust—not just in the technology, but in the people operating it**. For drones, this meant that responders were more likely to accept the system if they had worked with the same drone operator before, because when first responders know the operator’s style and competence, they are more likely to trust the drone’s data and integrate it into their decision-making without hesitation. For sensors, trust was tied to the system’s ability to deliver relevant alerts without overwhelming users or bypassing human judgment, because a subtle vibration or visual cue, paired with a clear explanation visible to the team leader or medic, was seen as more trustworthy. In both cases, participants valued **human-in-the-loop designs** that preserved decision-making authority while leveraging automation for speed and coverage.
	63	+
	64	+The sessions also revealed subtle but important tensions: between **autonomy and oversight**, **data richness and cognitive load**, and **technical capability and field practicality**. For example, while drone pilots advocated for layered sensor views and AI-enhanced detection, responders were more concerned with whether the drone could be deployed quickly and without disrupting operations. Similarly, while medics appreciated detailed vitals, team leaders wanted only the most essential alerts—preferably in a format that could be understood at a glance, even in low-light or high-stress conditions.
	65	+
33	33	= 5. Conclusions =
	67	+
	68	+The stakeholder evaluations confirmed that both the autonomous drone and health sensor systems have strong potential to enhance emergency response—but only if they are **deeply embedded in the operational culture** of the teams that use them.
	69	+
	70	+For the **sensor system**, success depends on delivering **relevant, role-specific insights** with minimal friction. Systems must be **plug-and-play**, with clear escalation logic and the ability to adapt to different team structures. The value lies not in showing more data, but in showing the **right data to the right person at the right time**.
	71	+
	72	+For the **drone system**, the challenge is to balance **technical sophistication with field usability**. Drones must be fast to deploy, easy to coordinate with human teams, and capable of operating independently without becoming a burden. Their integration into standard operating procedures—and the trust placed in their operators—will be critical to their acceptance.
	73	+
	74	+Ultimately, both systems must be designed not just for functionality, but for **fit**: fit with the mission, the team, the environment, and the moment. When that fit is achieved, these technologies can move from being experimental tools to **trusted tools **in the field.