Skip to Content

Wiki source code of Direct Stakeholders

Version 11.1 by Tjalling Haije on 2025/09/08 12:37
Hide last authors
Tjalling Haije 6.1 1 USAR and firefighting operations are carried out by a mix of professionals and trained volunteers who work long shifts under high risk and high tempo. Structures differ across Europe (national fire services, civil protection agencies like THW, mixed volunteer/pro units), but field reality is consistent: clear command, sector/task discipline, and pragmatic “get it done” culture. In SYNERGISE we focus first on people who directly touch the technology or whose decisions depend on it. That includes emerging roles (drone pilot, sensor/video analyst, C4I home base operator, information analyst) alongside classic USAR roles (team lead, squad lead, paramedic, search/rescue tech). Interviews repeatedly stressed: don’t make the same person both “set up” and “go in”; treat setup time as an investment only if it clearly pays back in safety, speed, or certainty later; and keep prep at BoO** **with just-in-time activation at the worksite. New tech must fit rhythms already in use (USAR vs. Fire tempo), respect national certification (e.g., drone licensing), and be configurable to local doctrine while sharing a common core.
Tjalling Haije 1.1 2
Tjalling Haije 4.1 3 == Main Stakeholders SYNERGISE technologies ==
Tjalling Haije 1.1 4
Tjalling Haije 8.1 5 Below are a number of stakeholders that will interact directly with the proposed technologies in SYNERGISE. The term 'First Responder' is an umbrella term for different types of stakeholders. These stakeholders are further identified in the stakeholders this table.
Tjalling Haije 1.1 6
7 (% class="table-striped" %)
Mark Rinse van Koningsveld 3.1 8 |(% style="width:162px" %)**First Responder (FR)**|(% style="width:794px" %)Form the first response to incidents. INSARAG distinguishes between three First Response organisations: Civil Defence/Protection (police), Local Emergency Services (firefighters and emergency medical technician//, //EMTs), and Community First Responders. First responders can be //local //or //international//,// //if international help is requested for large incidents. 
9 \\Tasks: breaching, shoring, extrication, interior search. Needs: go/no-go cues, simple wayfinding, hazard alerts that don’t drown out radio discipline. Decisions: continue, withdraw, change access path. Tech: rugged handheld/wearable, glanceable alerts, offline maps.
10 //Notes~:// Avoid alert fatigue; if an alert matters, it must be rare, explainable, and immediately actionable. Setup “on the apron” is fine; strapped-on sensors too early are just dead weight until entry.
11 |(% style="width:162px" %)**Victim **|(% style="width:794px" %)(((
Tjalling Haije 1.1 12 Victims can be direct stakeholders, when they have to interact directly with technologies. For example, if victims have to communicate with robot actors, they are directly affected by how these robot actors function.
13 )))
Mark Rinse van Koningsveld 3.1 14 |(% style="width:162px" %)(((
15 **Squad Leader (worksite)**
16 )))|(% style="width:794px" %)Tasks: route choice, team tasking, safety checks, on-site deconfliction. Needs: live worksite map (markers, hazards, team status), quick comms, ability to mute non-critical feeds during critical phases. Tech: role-based dashboard; add/confirm markers; radio + data in one glance.
17 //Notes~:// Wants answers, not raw feeds. Mark-verify-notify loops must be fast. Prefers just-in-time sensor fitting at the worksite.
18 |(% style="width:162px" %)**Team Leader (field or HQ)**|(% style="width:794px" %)Tasks: prioritize sectors/sites, assign teams, align with LEMA/OSOCC. Needs: rolled-up picture, change feed (“what changed since last brief”), escalation options. Tech: COP with filters, status roll-ups, one-click briefing.
19 //Notes~:// Treat setup time as //investment//. Accepts minor startup cost if it clearly shortens later operations or reduces risk.
20 |(% style="width:162px" %)**Drone/Robot Pilot**|(% style="width:794px" %)Tasks: launch, supervise autonomous scans, manual inspection, safe recovery. Needs: stable link, people/drone separation cues, battery/health, quick handover to/from analyst. Tech: low-latency video/controls; airspace & ground-proximity cues.
21 //Notes~:// Split pilot/analyst by default; don’t ask one person to fly //and// interpret. Fire contexts are truck-based with pilot + observer; USAR can accommodate more pre-entry setup.
22 |(% style="width:162px" %)**Sensor & Video Analyst**|(% style="width:794px" %)Tasks: interpret feeds, confirm detections, place map markers, advise routes. Needs: synchronized video/thermal/3D, annotation tools, confidence + “why”, provenance. Tech: layered overlays; flag→mark→notify workflow.
23 //Notes~:// Analysts prefer to push //decisions// and //routes//, not heatmaps; they want re-task buttons (“re-scan this door void”).
24 |(% style="width:162px" %)**Information Analyst (field or HQ)**|(% style="width:794px" %)Tasks: curate sector/worksite status, maintain “one source of truth,” produce reports. Needs: versioning, role-based visibility, audit trail. Tech: C3I forms, bulk updates, snapshots.
25 //Notes~:// Fights duplication and drift; wants structured fields but fast capture in the field (short forms, later enrich).
26 |(% style="width:162px" %)**Paramedic (worksite)**|(% style="width:794px" %)Tasks: triage/treat victims; monitor responder vitals; escalate alerts. Needs: traffic-light for non-medics; drill-down for medics; location-to-patient path. Tech: personal baselines, thresholds, confirm/ack flow.
27 //Notes~:// Keep responders’ privacy by default; show only what a role needs. Escalation should route to medic first, then TL.
28 |(% style="width:162px" %)**Structural Engineer**|(% style="width:794px" %)Tasks: assess stability, advise shoring, approve entry. Needs: quick 3D slices of interior paths, hazard overlays, decision log.
29 //Notes~:// Values simple, trustworthy measurements over fancy visuals; wants to annotate “do not cut here / brace here.”
Tjalling Haije 1.1 30
31
Rosa Van Tuijn 2.1 32
Mark Rinse van Koningsveld 3.1 33 == General insights from interviews with stakeholders ==
Rosa Van Tuijn 2.1 34
Mark Rinse van Koningsveld 3.1 35
Tjalling Haije 10.1 36 **Split control & analysis.** Robots work best with a distinct **Pilot** and **Analyst**; and a specific **Overview** role when multiple robots run. Design implication: default to separate UI profiles and explicit handovers; shared annotations sync by default.
Mark Rinse van Koningsveld 3.1 37
38 **Set up or go in.** Frontline shouldn’t run complex tech during entry. Design implication: shift setup to BoO or staging; enable just-in-time activation at the worksite; minimize attach/remove steps.
39
40 **Investment, not sacrifice.** Startup costs must pay back in later speed/safety. Design implication: show expected payoff (e.g., saved search time) and keep setup under a known ceiling.
41
42 **Answers over feeds.** Leaders want decisions and routes, not raw sensor firehoses. Design implication: analyst tools publish //recommendations// with provenance; commanders get roll-ups and “what changed.”
43
44 **Graceful degradation.** Networks fail; work continues. Design implication: offline-first, store-and-forward, mesh hints, on-device caching; visible confidence and data age.
45
46 **Role-based privacy.** Health and video data need scoped visibility. Design implication: strict role views, consent/ack flows, redaction by default on exports.
47
48
49 == All roles within USAR operation ==
50
Tjalling Haije 10.2 51 In SYNERGISE, we distinguish between two First Responder departments: Urban Search and Rescue (USAR) and Fire Department (FD). These two departments work closely together during an incident. At the end of the overview, some new actors are identified that do not currently exist, but that will need to be included when new technologies are introduced.
Tjalling Haije 1.1 52
53 [[image:hierarchical overview.png]]
54
55
Mark Rinse van Koningsveld 3.1 56 (% class="table-striped" style="width:641.656px" %)
57 |=(% scope="row" %)**Stakeholder**|=(% style="width: 468.656px;" %)**Description **
58 |[[image:Asset 26\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 59 **USAR Coordination Cell**
60
Mark Rinse van Koningsveld 3.1 61 Manages the (international) coordination between all stakeholders involved in an incident.
Tjalling Haije 1.1 62 )))
Mark Rinse van Koningsveld 3.1 63 |[[image:Asset 25\@4x.png||alt="Asset 26@4x.png"]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 64 **Team Leader (TL) - USAR**
65
66 Responsible for the whole USAR team. Communication with UCC
67
68 Participates at the team leader meetings to get tasks assigned
69 )))
Mark Rinse van Koningsveld 3.1 70 |[[image:Asset 22\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 71 **Deputy Team leader - USAR**
72
73 Responsible for all staff at the Base of Operations (BOO)
74 )))
Mark Rinse van Koningsveld 3.1 75 |[[image:Asset 23\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 76 **Staff - USAR**
77
78 Located at the BOO. Includes: Information, Staff, Media, ICT,  and Hazmat
Mark Rinse van Koningsveld 3.1 79 )))|(% style="width:1px" %)
80 |[[image:Asset 21\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 81 **Logistics - USAR**
82
83 Located at the BOO. Responsible for logistics of an incident
84 )))
Mark Rinse van Koningsveld 3.1 85 |[[image:Asset 20\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 86 **Medical - USAR**
87
88 Located at the BOO. Medical professionals.
89
90 Provides more in-depth assessment of victim health and can perform emergency treatments
91
92 Tracks the health of first responders
93
94 Assesses medical equipment for extraction
95 )))
Mark Rinse van Koningsveld 3.1 96 |[[image:Asset 19\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 97 **Liaison - USAR**
98
99 Located at the BOO. Responsible for the communication with third-party organisations during an incident
100 )))
Mark Rinse van Koningsveld 3.1 101 |[[image:Asset 18\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 102 **Chief of Operations - USAR**
103
104 Responsible for all rescue operations at all assigned worksites; usually at a worksite during setup and during critical phases
105 )))
Mark Rinse van Koningsveld 3.1 106 |[[image:1724250237332-368.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 107 **Chief Search and Rescue - USAR**
108
109 Responsible for all staff at one worksite
110
111 Contact to Local Emergency Management Ageny (LEMA) at the worksite
112
113 Using INSARAG Coordination Management System (ICMS) Survey 123 forms
114
115 Communication/ contact to BoO (Base of operation)
116
117 Overall strategy and safety in line with guidance by CoO and advice of paramedic, structural engineer and squad leader after initial overview/ survey
118 )))
Mark Rinse van Koningsveld 3.1 119 |[[image:Asset 16\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 120 **Squad Leader - USAR**
121
122 Located in the field. Leads the technical rescue operation
123
124 In depth analysis of the situation and solution proposal
125
126 Close communication with CSAR, structural engineer, paramedic, maintenance and his team
127
128 In need of all the detailed information, search results, measurements, data etc
129
130 Decides and guides search techniques, routes inside the worksite and breaking/ breaching as well as rope rescue
131 )))
Mark Rinse van Koningsveld 3.1 132 |[[image:Asset 15\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 133 **Structural Engineer - USAR**
134
135 Located in the field. Analyses structural integrity of buildings to assess risks of collapse and stabilises buildings where necessary
136 )))
Mark Rinse van Koningsveld 3.1 137 |[[image:Asset 14\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 138 **Paramedic - USAR**
139
140 Located in the field. Assesses victim health and performs emergency treatment for victim stabilisation where necessary
141 )))
Mark Rinse van Koningsveld 3.1 142 |[[image:Asset 13\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 143 **Maintenance - USAR**
144
145 Located in the field. Responsible for maintenance during an incident
146 )))
Mark Rinse van Koningsveld 3.1 147 |[[image:Asset 12\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 148 **Rescue Expert - USAR**
149
150 Located in the field. Expertise in rescuing victims
151 )))
Mark Rinse van Koningsveld 3.1 152 |[[image:Asset 11\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 153 **Search Tech - USAR**
154
155 Located in the field. Expertise in searching for victims
156 )))
Mark Rinse van Koningsveld 3.1 157 |[[image:Asset 10\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 158 **Dog + Handler - USAR**
159
160 Located in the field. Searches for (entrapped) victims with the help of scent
161 )))
Mark Rinse van Koningsveld 3.1 162 |[[image:Asset 24\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 163 **Fire Chief - FD**
164
165 Responsible for all staff at a fire department
166 )))
Mark Rinse van Koningsveld 3.1 167 |[[image:Asset 9\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 168 **Incident Commander (IC) - FD**
169
170 Responsible for the incident as a whole
171
172 Communication with the Fire Chief and TLs
173
174 Chair of the team leader meetings
175 )))
Mark Rinse van Koningsveld 3.1 176 |[[image:Asset 8\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 177 **Team Leader - FD**
178
179 Participate at the team leader meetings to get tasks assigned
180
181 Responsible for the whole team
182
183 Communication with "her/his" IC
184 )))
Mark Rinse van Koningsveld 3.1 185 |[[image:Asset 7\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 186 **Chauffeur - FD**
187
188 Drives the firefighters to and around the incident
189 )))
Mark Rinse van Koningsveld 3.1 190 |[[image:Asset 6\@4x.png]]|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 191 **Firefighter - FD**
192
193 Responsible for mitigating hazards such as fires and gas leaks
194 )))
Mark Rinse van Koningsveld 3.1 195 (% class="warning" %)|//[[image:Asset 2\@4x.png]]//|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 196 //**Tactical Operator - NEW**//
197
198 //Located in the BOO. Responsible for controlling robots remotely. //
199 )))
Mark Rinse van Koningsveld 3.1 200 (% class="warning" %)|//[[image:Asset 1\@4x.png]]//|(% style="width:468.656px" %)(((
Tjalling Haije 1.1 201 //**Operational Operator (Field Operator) - NEW**//
202
203 //Located in the field. Responsible for controlling robots on-site. //
204 )))