Skip to Content

Changes for page 3. Evaluation

Last modified by Tjalling Haije on 2025/09/15 08:03
From version 6.1
edited by Rosa Van Tuijn
on 2025/08/25 12:34
Change comment: There is no comment for this version
To version 3.1
edited by Rosa Van Tuijn
on 2025/08/25 09:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,24 +1,5 @@
1 -The design evaluation process is intended to assess and validate the system’s architecture, or to differentiate between various design alternatives, thereby facilitating incremental improvements in successive development cycles. The SCE methodology outlines two key components pertinent to system evaluation: (1) the prototype and/or simulation, and (2) the evaluation, which details the assessment approach and findings.
1 +The design evaluation aims to test and validate the system’s design, or to discriminate between multiple design options, such that the current design can be improved upon in incremental development cycles. The SCE method describes two parts that are relevant with respect to the system evaluation: (1) the prototype and/or simulation, and (2) the evaluation that describes the evaluation method and results.
2 2  
3 -Within the SYNERGISE project, initial assessments were conducted through CFTs (Component Field Tests), followed by comprehensive SFTs (System Field Tests). The CFTs involved only selected technologies, whereas the SFTs integrated all developed technologies for thorough testing.
4 4  
5 -This evaluation chapter will present all prototypes created for the HMT framework, accompanied by their corresponding CFT tests. Prototype documentation illustrates the concepts and principles of HMT, while test reports detail interactions with users and summarize the results obtained.
6 6  
7 -
8 -=== CFT1: Data visualisation ===
9 -
10 -This first CFT evaluated how sensor data - specifically health, location, and communication data - can support decision-making in USAR operations at tactical and operational levels. Questionnaires were used to determine users' data needs and preferences for [[visualization formats>>doc:.a\. Prototype.WebHome]]. The [[study found>>doc:.b\. Test.WebHome]] that different roles require different types and levels of data detail: tactical users prefer aggregated overviews, while operational users need real-time, detailed information.
11 -
12 -=== CFT2: Concept of Operations ===
13 -
14 -During the second CFT the Concept of Operations (ConOps) was evaluated. Through[[ structured sessions>>doc:.d\. Test.WebHome]] involving presentations of multiple[[ use cases>>doc:.c\. Prototype .WebHome]] and participant feedback, the study explored operational feasibility, safetly, and team dynamics. [[Key findings>>doc:.d\. Test.WebHome]] highlighted the importance of context in technology deployment, the need for rapid and logical task distribution, and the critical role of human oversight.
15 -
16 -=== CFT3: Two Detailed Use Cases ===
17 -
18 -The third CFT, evaluated [[two use cases>>doc:.e\. Prototype .WebHome]]: autonomous indoor drones for victim detection and physiological/ environmental sensors for monitoring first responder health. The study assessed usability, trust, and itegration into emergency workflows through structured sessions with firefighters, USAR personnel, and drone pilots. [[Key findings highlight>>doc:.f\. Test.WebHome]] that while both technologies show promise, their success depends on seamless integration into operational proces, respecting roles, protocols, and situational constraints to become trusted tools in the field.
19 -
20 -=== CFT4: Human-Machine Teaming ===
21 -
22 -....
23 -
24 24