Changes for page Direct Stakeholders

Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.RosaVanTuijn
	1	+XWiki.TjallingHaije

Content

...	...	@@ -1,36 +1,66 @@
1		-Direct stakeholders interact directly with developed technologies. The tables below shows relevant stakeholders in Synergise, divided in general stakeholders and first responders. When we describe how these stakeholders collaborate with technologies, we may also refer to them as //actors. //
	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.
2	2
3		-== General Stakeholders ==
	3	+== Main Stakeholders SYNERGISE technologies ==
4	4
5		-Generally, there are two types 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 First Responders subsection.
	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	6
7	7	(% class="table-striped" %)
8		-|**First Responder (FR)**|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		-|**Victim **|(((
	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" %)(((
10	10	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.
11	11	)))
	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.”
12	12
13		-== Summary roles ==
14	14
15		-|Who?|Values (taak, verantwoordelijkheden)
16		-| |
17		-| |
18	18
19		-== Detailed roles - First Responders ==
	33	+== General insights from interviews with stakeholders ==
20	20
21		-In Synergise, we distinguish between two First Responder departments: Urban Search and Rescue (USAR) and Fire Department (FD). These two department 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.
22	22
	36	+**Split control & analysis.** Robotics work best with distinct **Pilot** and **Analyst**; add an **Overview** role when multiple robots run. Design implication: default to separate UI profiles and explicit handovers; shared annotations sync by default.
	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	+
	51	+In SYNERGISE, we distinguish between two First Responder departments: Urban Search and Rescue (USAR) and Fire Department (FD). These two department 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.
	52	+
23	23	[[image:hierarchical overview.png]]
24	24
25	25
26		-(% class="table-striped" %)
27		-|=(% scope="row" %)**Stakeholder**|=**Description **
28		-|[[image:Asset 26\@4x.png]]|(((
	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" %)(((
29	29	**USAR Coordination Cell**
30	30
31		-Manages the (international) coordination between all stakeholders involved in an incident
	61	+Manages the (international) coordination between all stakeholders involved in an incident.
32	32	)))
33		-|[[image:Asset 25\@4x.png||alt="Asset 26@4x.png"]]|(((
	63	+|[[image:Asset 25\@4x.png||alt="Asset 26@4x.png"]]|(% style="width:468.656px" %)(((
34	34	**Team Leader (TL) - USAR**
35	35
36	36	Responsible for the whole USAR team. Communication with UCC
...	...	@@ -37,22 +37,22 @@
37	37
38	38	Participates at the team leader meetings to get tasks assigned
39	39	)))
40		-|[[image:Asset 22\@4x.png]]|(((
	70	+|[[image:Asset 22\@4x.png]]|(% style="width:468.656px" %)(((
41	41	**Deputy Team leader - USAR**
42	42
43	43	Responsible for all staff at the Base of Operations (BOO)
44	44	)))
45		-|[[image:Asset 23\@4x.png]]|(((
	75	+|[[image:Asset 23\@4x.png]]|(% style="width:468.656px" %)(((
46	46	**Staff - USAR**
47	47
48	48	Located at the BOO. Includes: Information, Staff, Media, ICT,  and Hazmat
49		-)))|
50		-|[[image:Asset 21\@4x.png]]|(((
	79	+)))|(% style="width:1px" %)
	80	+|[[image:Asset 21\@4x.png]]|(% style="width:468.656px" %)(((
51	51	**Logistics - USAR**
52	52
53	53	Located at the BOO. Responsible for logistics of an incident
54	54	)))
55		-|[[image:Asset 20\@4x.png]]|(((
	85	+|[[image:Asset 20\@4x.png]]|(% style="width:468.656px" %)(((
56	56	**Medical - USAR**
57	57
58	58	Located at the BOO. Medical professionals.
...	...	@@ -63,17 +63,17 @@
63	63
64	64	Assesses medical equipment for extraction
65	65	)))
66		-|[[image:Asset 19\@4x.png]]|(((
	96	+|[[image:Asset 19\@4x.png]]|(% style="width:468.656px" %)(((
67	67	**Liaison - USAR**
68	68
69	69	Located at the BOO. Responsible for the communication with third-party organisations during an incident
70	70	)))
71		-|[[image:Asset 18\@4x.png]]|(((
	101	+|[[image:Asset 18\@4x.png]]|(% style="width:468.656px" %)(((
72	72	**Chief of Operations - USAR**
73	73
74	74	Responsible for all rescue operations at all assigned worksites; usually at a worksite during setup and during critical phases
75	75	)))
76		-|[[image:1724250237332-368.png]]|(((
	106	+|[[image:1724250237332-368.png]]|(% style="width:468.656px" %)(((
77	77	**Chief Search and Rescue - USAR**
78	78
79	79	Responsible for all staff at one worksite
...	...	@@ -86,7 +86,7 @@
86	86
87	87	Overall strategy and safety in line with guidance by CoO and advice of paramedic, structural engineer and squad leader after initial overview/ survey
88	88	)))
89		-|[[image:Asset 16\@4x.png]]|(((
	119	+|[[image:Asset 16\@4x.png]]|(% style="width:468.656px" %)(((
90	90	**Squad Leader - USAR**
91	91
92	92	Located in the field. Leads the technical rescue operation
...	...	@@ -99,42 +99,42 @@
99	99
100	100	Decides and guides search techniques, routes inside the worksite and breaking/ breaching as well as rope rescue
101	101	)))
102		-|[[image:Asset 15\@4x.png]]|(((
	132	+|[[image:Asset 15\@4x.png]]|(% style="width:468.656px" %)(((
103	103	**Structural Engineer - USAR**
104	104
105	105	Located in the field. Analyses structural integrity of buildings to assess risks of collapse and stabilises buildings where necessary
106	106	)))
107		-|[[image:Asset 14\@4x.png]]|(((
	137	+|[[image:Asset 14\@4x.png]]|(% style="width:468.656px" %)(((
108	108	**Paramedic - USAR**
109	109
110	110	Located in the field. Assesses victim health and performs emergency treatment for victim stabilisation where necessary
111	111	)))
112		-|[[image:Asset 13\@4x.png]]|(((
	142	+|[[image:Asset 13\@4x.png]]|(% style="width:468.656px" %)(((
113	113	**Maintenance - USAR**
114	114
115	115	Located in the field. Responsible for maintenance during an incident
116	116	)))
117		-|[[image:Asset 12\@4x.png]]|(((
	147	+|[[image:Asset 12\@4x.png]]|(% style="width:468.656px" %)(((
118	118	**Rescue Expert - USAR**
119	119
120	120	Located in the field. Expertise in rescuing victims
121	121	)))
122		-|[[image:Asset 11\@4x.png]]|(((
	152	+|[[image:Asset 11\@4x.png]]|(% style="width:468.656px" %)(((
123	123	**Search Tech - USAR**
124	124
125	125	Located in the field. Expertise in searching for victims
126	126	)))
127		-|[[image:Asset 10\@4x.png]]|(((
	157	+|[[image:Asset 10\@4x.png]]|(% style="width:468.656px" %)(((
128	128	**Dog + Handler - USAR**
129	129
130	130	Located in the field. Searches for (entrapped) victims with the help of scent
131	131	)))
132		-|[[image:Asset 24\@4x.png]]|(((
	162	+|[[image:Asset 24\@4x.png]]|(% style="width:468.656px" %)(((
133	133	**Fire Chief - FD**
134	134
135	135	Responsible for all staff at a fire department
136	136	)))
137		-|[[image:Asset 9\@4x.png]]|(((
	167	+|[[image:Asset 9\@4x.png]]|(% style="width:468.656px" %)(((
138	138	**Incident Commander (IC) - FD**
139	139
140	140	Responsible for the incident as a whole
...	...	@@ -143,7 +143,7 @@
143	143
144	144	Chair of the team leader meetings
145	145	)))
146		-|[[image:Asset 8\@4x.png]]|(((
	176	+|[[image:Asset 8\@4x.png]]|(% style="width:468.656px" %)(((
147	147	**Team Leader - FD**
148	148
149	149	Participate at the team leader meetings to get tasks assigned
...	...	@@ -152,22 +152,22 @@
152	152
153	153	Communication with "her/his" IC
154	154	)))
155		-|[[image:Asset 7\@4x.png]]|(((
	185	+|[[image:Asset 7\@4x.png]]|(% style="width:468.656px" %)(((
156	156	**Chauffeur - FD**
157	157
158	158	Drives the firefighters to and around the incident
159	159	)))
160		-|[[image:Asset 6\@4x.png]]|(((
	190	+|[[image:Asset 6\@4x.png]]|(% style="width:468.656px" %)(((
161	161	**Firefighter - FD**
162	162
163	163	Responsible for mitigating hazards such as fires and gas leaks
164	164	)))
165		-(% class="warning" %)|//[[image:Asset 2\@4x.png]]//|(((
	195	+(% class="warning" %)|//[[image:Asset 2\@4x.png]]//|(% style="width:468.656px" %)(((
166	166	//**Tactical Operator - NEW**//
167	167
168	168	//Located in the BOO. Responsible for controlling robots remotely. //
169	169	)))
170		-(% class="warning" %)|//[[image:Asset 1\@4x.png]]//|(((
	200	+(% class="warning" %)|//[[image:Asset 1\@4x.png]]//|(% style="width:468.656px" %)(((
171	171	//**Operational Operator (Field Operator) - NEW**//
172	172
173	173	//Located in the field. Responsible for controlling robots on-site. //