Changes for page Direct Stakeholders

Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -1,68 +1,174 @@
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.
	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. //
2	2
3		-== Main Stakeholders SYNERGISE technologies ==
	3	+== General Stakeholders ==
4	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.
	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.
6	6
7	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" %)(((
	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 **|(((
12	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	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	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.
	13	+== Summary roles ==
	14	+
	15	+|Who?|Values (taak, verantwoordelijkheden)
	16	+| |
	17	+| |
	18	+
	19	+== Detailed roles - First Responders ==
	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	+
	23	+[[image:hierarchical overview.png]]
	24	+
	25	+
	26	+(% class="table-striped" %)
	27	+|=(% scope="row" %)**Stakeholder**|=**Description **
	28	+|[[image:Asset 26\@4x.png]]|(((
	29	+**USAR Coordination Cell**
	30	+
	31	+Manages the (international) coordination between all stakeholders involved in an incident
23	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.
	33	+|[[image:Asset 25\@4x.png||alt="Asset 26@4x.png"]]|(((
	34	+**Team Leader (TL) - USAR**
	35	+
	36	+Responsible for the whole USAR team. Communication with UCC
	37	+
	38	+Participates at the team leader meetings to get tasks assigned
37	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	+|[[image:Asset 22\@4x.png]]|(((
	41	+**Deputy Team leader - USAR**
40	40
41		-**Firefighting Exclusive Stakeholders SYNERGISE technologies**
	43	+Responsible for all staff at the Base of Operations (BOO)
	44	+)))
	45	+|[[image:Asset 23\@4x.png]]|(((
	46	+**Staff - USAR**
42	42
43		-|**Firefighter / Rescue Technician**|Tasks: fire attack, interior search, ventilation, extrication. Needs: go/no-go cues, simple wayfinding, hazard alerts that don’t drown out radio discipline. Decisions: continue, withdraw, change tactic or access path. Tech: PPE/BA, FR gear, Worksite forms, Radio to crew and to command.
44		-//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.
45		-|**Crew Officer (Worksite)**|Tasks: route/entry choice, team tasking, safety checks, on-scene deconfliction. Needs: live incident map (hydrants, hazards, team status), quick comms, ability to mute non-critical feeds during critical phases. Decisions: offensive vs. defensive mode, entry vs. exterior ops, ventilation timing. Tech: Tablet/MDT with worksite forms, FR gear, Radio to crew and to command, C3I.
46		-//Notes//: Wants answers, not raw feeds. Mark-verify-notify loops must be fast. Prefers just-in-time sensor fitting at the worksite.
47		-|**Incident Commander (Field or HQ)**|(((
48		-Tasks: prioritize sectors/sites, assign companies, align with LEMA/OSOCC. Needs: rolled-up picture, change feed (“what changed since last brief”), escalation options. Decisions: strategy selection, resource escalation, evacuation orders. Tech: Command unit kit, FR gear, Radio to divisions & dispatch, C3I.
49		-//Notes//: Treat setup time as investment. Accepts minor startup cost if it clearly shortens later operations or reduces risk.
	48	+Located at the BOO. Includes: Information, Staff, Media, ICT,  and Hazmat
	49	+)))|
	50	+|[[image:Asset 21\@4x.png]]|(((
	51	+**Logistics - USAR**
	52	+
	53	+Located at the BOO. Responsible for logistics of an incident
50	50	)))
	55	+|[[image:Asset 20\@4x.png]]|(((
	56	+**Medical - USAR**
51	51
52		-== General insights from interviews with stakeholders ==
	58	+Located at the BOO. Medical professionals.
53	53
	60	+Provides more in-depth assessment of victim health and can perform emergency treatments
54	54
55		-**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.
	62	+Tracks the health of first responders
56	56
57		-**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.
	64	+Assesses medical equipment for extraction
	65	+)))
	66	+|[[image:Asset 19\@4x.png]]|(((
	67	+**Liaison - USAR**
58	58
59		-**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.
	69	+Located at the BOO. Responsible for the communication with third-party organisations during an incident
	70	+)))
	71	+|[[image:Asset 18\@4x.png]]|(((
	72	+**Chief of Operations - USAR**
60	60
61		-**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.”
	74	+Responsible for all rescue operations at all assigned worksites; usually at a worksite during setup and during critical phases
	75	+)))
	76	+|[[image:1724250237332-368.png]]|(((
	77	+**Chief Search and Rescue - USAR**
62	62
63		-**Graceful degradation.** Networks fail; work continues. Design implication: offline-first, store-and-forward, mesh hints, on-device caching; visible confidence and data age.
	79	+Responsible for all staff at one worksite
64	64
65		-**Role-based privacy.** Health and video data need scoped visibility. Design implication: strict role views, consent/ack flows, redaction by default on exports.
66		-
	81	+Contact to Local Emergency Management Ageny (LEMA) at the worksite
67	67
68		-
	83	+Using INSARAG Coordination Management System (ICMS) Survey 123 forms
	84	+
	85	+Communication/ contact to BoO (Base of operation)
	86	+
	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	+)))
	89	+|[[image:Asset 16\@4x.png]]|(((
	90	+**Squad Leader - USAR**
	91	+
	92	+Located in the field. Leads the technical rescue operation
	93	+
	94	+In depth analysis of the situation and solution proposal
	95	+
	96	+Close communication with CSAR, structural engineer, paramedic, maintenance and his team
	97	+
	98	+In need of all the detailed information, search results, measurements, data etc
	99	+
	100	+Decides and guides search techniques, routes inside the worksite and breaking/ breaching as well as rope rescue
	101	+)))
	102	+|[[image:Asset 15\@4x.png]]|(((
	103	+**Structural Engineer - USAR**
	104	+
	105	+Located in the field. Analyses structural integrity of buildings to assess risks of collapse and stabilises buildings where necessary
	106	+)))
	107	+|[[image:Asset 14\@4x.png]]|(((
	108	+**Paramedic - USAR**
	109	+
	110	+Located in the field. Assesses victim health and performs emergency treatment for victim stabilisation where necessary
	111	+)))
	112	+|[[image:Asset 13\@4x.png]]|(((
	113	+**Maintenance - USAR**
	114	+
	115	+Located in the field. Responsible for maintenance during an incident
	116	+)))
	117	+|[[image:Asset 12\@4x.png]]|(((
	118	+**Rescue Expert - USAR**
	119	+
	120	+Located in the field. Expertise in rescuing victims
	121	+)))
	122	+|[[image:Asset 11\@4x.png]]|(((
	123	+**Search Tech - USAR**
	124	+
	125	+Located in the field. Expertise in searching for victims
	126	+)))
	127	+|[[image:Asset 10\@4x.png]]|(((
	128	+**Dog + Handler - USAR**
	129	+
	130	+Located in the field. Searches for (entrapped) victims with the help of scent
	131	+)))
	132	+|[[image:Asset 24\@4x.png]]|(((
	133	+**Fire Chief - FD**
	134	+
	135	+Responsible for all staff at a fire department
	136	+)))
	137	+|[[image:Asset 9\@4x.png]]|(((
	138	+**Incident Commander (IC) - FD**
	139	+
	140	+Responsible for the incident as a whole
	141	+
	142	+Communication with the Fire Chief and TLs
	143	+
	144	+Chair of the team leader meetings
	145	+)))
	146	+|[[image:Asset 8\@4x.png]]|(((
	147	+**Team Leader - FD**
	148	+
	149	+Participate at the team leader meetings to get tasks assigned
	150	+
	151	+Responsible for the whole team
	152	+
	153	+Communication with "her/his" IC
	154	+)))
	155	+|[[image:Asset 7\@4x.png]]|(((
	156	+**Chauffeur - FD**
	157	+
	158	+Drives the firefighters to and around the incident
	159	+)))
	160	+|[[image:Asset 6\@4x.png]]|(((
	161	+**Firefighter - FD**
	162	+
	163	+Responsible for mitigating hazards such as fires and gas leaks
	164	+)))
	165	+(% class="warning" %)|//[[image:Asset 2\@4x.png]]//|(((
	166	+//**Tactical Operator - NEW**//
	167	+
	168	+//Located in the BOO. Responsible for controlling robots remotely. //
	169	+)))
	170	+(% class="warning" %)|//[[image:Asset 1\@4x.png]]//|(((
	171	+//**Operational Operator (Field Operator) - NEW**//
	172	+
	173	+//Located in the field. Responsible for controlling robots on-site. //
	174	+)))