Changes for page a. Operational Demands
Last modified by Mark Rinse van Koningsveld on 2025/09/08 09:58
From version 4.1
edited by Tjalling Haije
on 2025/09/08 09:52
on 2025/09/08 09:52
Change comment:
There is no comment for this version
To version 2.1
edited by Rosa Van Tuijn
on 2025/08/25 11:40
on 2025/08/25 11:40
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. TjallingHaije1 +XWiki.RosaVanTuijn - Content
-
... ... @@ -1,16 +1,1 @@ 1 -Urban Search and Rescue (USAR) operations take place in challenging conditions that impose specific **operational demands** on responders and technology. This section of the SYNERGISE USAR project wiki outlines the real-world context in which USAR teams work across Europe, ensuring our system design is grounded in actual field needs. It is informed by practitioner interviews, **INSARAG** guidelines, and field observations. The following subpages detail key aspects of the operational environment and how they influence requirements: 2 - 3 -* ((( 4 -**[[1. Environment>>Main.sdf.Environments.WebHome]] **– Describes the physical and operational conditions of disaster sites (e.g. collapsed structures, hazards, weather). 5 -))) 6 -* ((( 7 -**[[2. FR Organisation>>Main.sdf.FR Organisation.WebHome]] **– Explains USAR team hierarchy, interagency coordination, and how structures vary across European countries. 8 -))) 9 -* ((( 10 -**[[Task division in USAR missions>>Main.sdf.FR Organisation.Task division in USAR missions.WebHome]] **– Illustrates how tasks are split among team members at a rescue site and how work is coordinated on the ground. 11 -))) 12 -* ((( 13 -**[[ASR levels>>Main.sdf.FR Organisation.ASR levels.WebHome]] **– Defines the five sequential **Assessment, Search and Rescue (ASR) levels** (ASR1–ASR5) and clarifies which teams perform which phases of operation. 14 -))) 15 - 16 -Each page highlights implications for system design and provides links to related topics (e.g. **Stakeholders**, **Personas**, **Use Cases**, **Human Factors**). This modular guide allows engineers, human-factors experts, and stakeholders to navigate the complex USAR context and align the SYNERGISE system with operational reality. 1 +The operational demands describe the current practice as it is, i.e. without the envisioned technology. For the operational demands, SCE prescribes as main components the stakeholders and their characteristics (including their values), and the problem description and analysis thereof. A //problem scenario// provides a short storyline to illustrate the way in which stakeholders experience the problem. To obtain a clear overview of the problem, it needs to be analysed: what are the causes of the problem? Can the problem be broken down into smaller problems? And what type of problems are related to this problem yet beyond the scope of the current problem description?