Skip to Content

Changes for page Roles

Last modified by Tjalling Haije on 2025/09/15 14:25
From version 14.1
edited by Mark Rinse van Koningsveld
on 2025/09/08 13:34
Change comment: There is no comment for this version
To version 18.1
edited by Tjalling Haije
on 2025/09/15 14:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Direct Stakeholders
1 +Roles
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.sdf.Stakeholders.WebHome
1 +Main.sdf.FR Organisation.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.MarkVanKoningsveld
1 +XWiki.TjallingHaije
Content
... ... @@ -1,61 +59,3 @@
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** **(Base Of Operations) 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.
2 -
3 -== Main Stakeholders SYNERGISE technologies ==
4 -
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.
6 -
7 -(% class="table-striped" %)
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: Worksite forms, FR gear, Radio to squad and to base
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" %)(((
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 -)))
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: Worksite forms, FR gear, Radio to squad and to base,C3I 
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" %)(((
19 -Tasks: prioritize sectors/sites, assign teams, align with LEMA/OSOCC. Needs: rolled-up picture, change feed (“what changed since last brief”), escalation options.
20 -
21 -Tech: FR gear, Radio to squad and to base,C3I 
22 -//Notes~:// Treat setup time as //investment//. Accepts minor startup cost if it clearly shortens later operations or reduces risk.
23 -)))
24 -|(% 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.
25 -Tech: Drone and remote control, Radio to squad and to base.
26 -//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.
27 -|(% 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.
28 -Tech: Tablet for analysis, FR gear, Radio to squad and to base, C3I
29 -//Notes~:// Analysts prefer to push //decisions// and //routes//, not heatmaps; they want re-task buttons (“re-scan this door void”).
30 -|(% 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.
31 -Tech: C3I 
32 -//Notes~:// Fights duplication and drift; wants structured fields but fast capture in the field (short forms, later enrich).
33 -|(% style="width:162px" %)**Paramedic (worksite)**|(% style="width:794px" %)(((
34 -Tasks: triage/treat victims; monitor responder vitals; escalate alerts. Needs: traffic-light for non-medics; drill-down for medics; location-to-patient path.
35 -Tech: FR gear, Medical equipment, Radio to squad and base, C3I
36 -//Notes~:// Keep responders’ privacy by default; show only what a role needs. Escalation should route to medic first, then TL.
37 -)))
38 -|(% 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.
39 -//Notes~:// Values simple, trustworthy measurements over fancy visuals; wants to annotate “do not cut here / brace here.”
40 -
41 -
42 -
43 -== General insights from interviews with stakeholders ==
44 -
45 -
46 -**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.
47 -
48 -**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.
49 -
50 -**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.
51 -
52 -**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.”
53 -
54 -**Graceful degradation.** Networks fail; work continues. Design implication: offline-first, store-and-forward, mesh hints, on-device caching; visible confidence and data age.
55 -
56 -**Role-based privacy.** Health and video data need scoped visibility. Design implication: strict role views, consent/ack flows, redaction by default on exports.
57 -
58 -
59 59  == All roles within USAR operation ==
60 60  
61 61  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 may need to be included when new technologies are introduced.
... ... @@ -80,17 +80,17 @@
80 80  |[[image:Asset 22\@4x.png]]|(% style="width:468.656px" %)(((
81 81  **Deputy Team leader - USAR**
82 82  
83 -Responsible for all staff at the Base of Operations (BOO)
25 +Responsible for all staff at the Base of Operations (BOO).
84 84  )))
85 85  |[[image:Asset 23\@4x.png]]|(% style="width:468.656px" %)(((
86 86  **Staff - USAR**
87 87  
88 -Located at the BOO. Includes: Information, Staff, Media, ICT,  and Hazmat
30 +Located at the BOO. Includes: Information, Staff, Media, ICT,  and Hazmat.
89 89  )))|(% style="width:1px" %)
90 90  |[[image:Asset 21\@4x.png]]|(% style="width:468.656px" %)(((
91 91  **Logistics - USAR**
92 92  
93 -Located at the BOO. Responsible for logistics of an incident
35 +Located at the BOO. Responsible for logistics of an incident.
94 94  )))
95 95  |[[image:Asset 20\@4x.png]]|(% style="width:468.656px" %)(((
96 96  **Medical - USAR**
... ... @@ -97,52 +97,52 @@
97 97  
98 98  Located at the BOO. Medical professionals.
99 99  
100 -Provides more in-depth assessment of victim health and can perform emergency treatments
42 +Provides more in-depth assessment of victim health and can perform emergency treatments.
101 101  
102 -Tracks the health of first responders
44 +Tracks the health of first responders.
103 103  
104 -Assesses medical equipment for extraction
46 +Assesses medical equipment for extraction .
105 105  )))
106 106  |[[image:Asset 19\@4x.png]]|(% style="width:468.656px" %)(((
107 107  **Liaison - USAR**
108 108  
109 -Located at the BOO. Responsible for the communication with third-party organisations during an incident
51 +Located at the BOO. Responsible for the communication with third-party organisations during an incident.
110 110  )))
111 111  |[[image:Asset 18\@4x.png]]|(% style="width:468.656px" %)(((
112 112  **Chief of Operations - USAR**
113 113  
114 -Responsible for all rescue operations at all assigned worksites; usually at a worksite during setup and during critical phases
56 +Responsible for all rescue operations at all assigned worksites; usually at a worksite during setup and during critical phases.
115 115  )))
116 116  |[[image:1724250237332-368.png]]|(% style="width:468.656px" %)(((
117 117  **Chief Search and Rescue - USAR**
118 118  
119 -Responsible for all staff at one worksite
61 +Responsible for all staff at one worksite.
120 120  
121 -Contact to Local Emergency Management Ageny (LEMA) at the worksite
63 +Contact to Local Emergency Management Ageny (LEMA) at the worksite.
122 122  
123 -Using INSARAG Coordination Management System (ICMS) Survey 123 forms
65 +Using INSARAG Coordination Management System (ICMS) Survey.
124 124  
125 -Communication/ contact to BoO (Base of operation)
67 +Communication/ contact to BoO (Base of operation).
126 126  
127 -Overall strategy and safety in line with guidance by CoO and advice of paramedic, structural engineer and squad leader after initial overview/ survey
69 +Overall strategy and safety in line with guidance by CoO and advice of paramedic, structural engineer and squad leader after initial overview/ survey.
128 128  )))
129 129  |[[image:Asset 16\@4x.png]]|(% style="width:468.656px" %)(((
130 130  **Squad Leader - USAR**
131 131  
132 -Located in the field. Leads the technical rescue operation
74 +Located in the field. Leads the technical rescue operation.
133 133  
134 -In depth analysis of the situation and solution proposal
76 +In depth analysis of the situation and solution proposal.
135 135  
136 -Close communication with CSAR, structural engineer, paramedic, maintenance and his team
78 +Close communication with CSAR, structural engineer, paramedic, maintenance and his team.
137 137  
138 -In need of all the detailed information, search results, measurements, data etc
80 +In need of all the detailed information, search results, measurements, data etc.
139 139  
140 -Decides and guides search techniques, routes inside the worksite and breaking/ breaching as well as rope rescue
82 +Decides and guides search techniques, routes inside the worksite and breaking/ breaching as well as rope rescue.
141 141  )))
142 142  |[[image:Asset 15\@4x.png]]|(% style="width:468.656px" %)(((
143 143  **Structural Engineer - USAR**
144 144  
145 -Located in the field. Analyses structural integrity of buildings to assess risks of collapse and stabilises buildings where necessary
87 +Located in the field. Analyses structural integrity of buildings to assess risks of collapse and stabilises buildings where necessary.
146 146  )))
147 147  |[[image:Asset 14\@4x.png]]|(% style="width:468.656px" %)(((
148 148  **Paramedic - USAR**
... ... @@ -157,50 +157,50 @@
157 157  |[[image:Asset 12\@4x.png]]|(% style="width:468.656px" %)(((
158 158  **Rescue Expert - USAR**
159 159  
160 -Located in the field. Expertise in rescuing victims
102 +Located in the field. Expertise in rescuing victims.
161 161  )))
162 162  |[[image:Asset 11\@4x.png]]|(% style="width:468.656px" %)(((
163 163  **Search Tech - USAR**
164 164  
165 -Located in the field. Expertise in searching for victims
107 +Located in the field. Expertise in searching for victims.
166 166  )))
167 167  |[[image:Asset 10\@4x.png]]|(% style="width:468.656px" %)(((
168 168  **Dog + Handler - USAR**
169 169  
170 -Located in the field. Searches for (entrapped) victims with the help of scent
112 +Located in the field. Searches for (entrapped) victims with the help of scent.
171 171  )))
172 172  |[[image:Asset 24\@4x.png]]|(% style="width:468.656px" %)(((
173 173  **Fire Chief - FD**
174 174  
175 -Responsible for all staff at a fire department
117 +Responsible for all staff at a fire department.
176 176  )))
177 177  |[[image:Asset 9\@4x.png]]|(% style="width:468.656px" %)(((
178 178  **Incident Commander (IC) - FD**
179 179  
180 -Responsible for the incident as a whole
122 +Responsible for the incident as a whole.
181 181  
182 -Communication with the Fire Chief and TLs
124 +Communication with the Fire Chief and TLs.
183 183  
184 -Chair of the team leader meetings
126 +Chair of the team leader meetings.
185 185  )))
186 186  |[[image:Asset 8\@4x.png]]|(% style="width:468.656px" %)(((
187 187  **Team Leader - FD**
188 188  
189 -Participate at the team leader meetings to get tasks assigned
131 +Participate at the team leader meetings to get tasks assigned.
190 190  
191 -Responsible for the whole team
133 +Responsible for the whole team.
192 192  
193 -Communication with "her/his" IC
135 +Communication with "her/his" IC.
194 194  )))
195 195  |[[image:Asset 7\@4x.png]]|(% style="width:468.656px" %)(((
196 196  **Chauffeur - FD**
197 197  
198 -Drives the firefighters to and around the incident
140 +Drives the firefighters to and around the incident.
199 199  )))
200 200  |[[image:Asset 6\@4x.png]]|(% style="width:468.656px" %)(((
201 201  **Firefighter - FD**
202 202  
203 -Responsible for mitigating hazards such as fires and gas leaks
145 +Responsible for mitigating hazards such as fires and gas leaks.
204 204  )))
205 205  (% class="warning" %)|//[[image:Asset 2\@4x.png]]//|(% style="width:468.656px" %)(((
206 206  //**Tactical Operator - NEW**//
XWiki.XWikiComments[0]
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.IvanaAkrum
Comment
... ... @@ -1,1 +1,0 @@
1 -Rename "extraction operation" to the appropriate terminology as used in the use cases. The term refers to the use cases where the focus is on extracting useable equipment from hazard zones, like partially collapsed hospitals.
Date
... ... @@ -1,1 +1,0 @@
1 -2024-07-12 14:12:45.284