Changes for page Roles
Last modified by Tjalling Haije on 2025/09/15 14:25
From version 15.1
edited by Mark Rinse van Koningsveld
on 2025/09/08 13:41
on 2025/09/08 13:41
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. MarkVanKoningsveld1 +XWiki.TjallingHaije - Content
-
... ... @@ -1,81 +1,30 @@ 1 - USAR and firefighting operations arecarried outby a mix of professionals andtrained volunteers whoworklong shifts underhigh riskand hightempo. Structuresdifferacross Europe(nationalfireservices, civilprotectionagencieslikeTHW, mixedvolunteer/pro units),but fieldreality isconsistent:clear command,sector/taskdiscipline, and pragmatic “get it done” culture. In SYNERGISE we focus firstonpeople who directlytouch the technology orwhose decisionsdependonit. That includesemerging roles (dronepilot, sensor/videoanalyst, C4I home baseoperator, information analyst)alongsideclassic USARroles(teamlead,squad lead,paramedic, search/rescue tech).Interviewsrepeatedlystressed: don’t makethesame personboth “setup” and “goin”;treatsetuptimeas an investmentonly if it clearly paysback in safety, speed,or certaintylater;and keep prep atBoO** **(BaseOf Operations)withjust-in-timeactivation at the worksite.Newtechmust fit rhythmsalready in use (USAR vs. Fire tempo),respectnationalcertification (e.g.,drone licensing),and beconfigurabletolocal doctrine whilesharingacommoncore.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 StakeholdersSYNERGISE technologies==3 +== General Stakeholders == 4 4 5 - Beloware anumberof 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 stakeholdersthistable.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. 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.” 13 +== First Responders == 40 40 41 - **Specific FirefightingStakeholdersSYNERGISEtechnologies**15 +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. 42 42 43 -|=Firefighting Role|=Description 44 -|**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. **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 / Company 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. **Notes:** Wants answers, not raw feeds. Mark-verify-notify loops must be fast. Prefers just-in-time sensor fitting at the worksite. 46 -|**Incident Commander / Sector Supervisor (Field or HQ)**|**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. **Notes:** Treat setup time as investment. Accepts minor startup cost if it clearly shortens later operations or reduces risk. 47 - 48 -== General insights from interviews with stakeholders == 49 - 50 - 51 -**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. 52 - 53 -**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. 54 - 55 -**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. 56 - 57 -**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.” 58 - 59 -**Graceful degradation.** Networks fail; work continues. Design implication: offline-first, store-and-forward, mesh hints, on-device caching; visible confidence and data age. 60 - 61 -**Role-based privacy.** Health and video data need scoped visibility. Design implication: strict role views, consent/ack flows, redaction by default on exports. 62 - 63 - 64 -== All roles within USAR operation == 65 - 66 -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. 67 - 68 68 [[image:hierarchical overview.png]] 69 69 70 70 71 -(% class="table-striped" style="width:641.656px"%)72 -|=(% scope="row" %)**Stakeholder**|= (% style="width: 468.656px;" %)**Description **73 -|[[image:Asset 26\@4x.png]]|( % style="width:468.656px" %)(((20 +(% class="table-striped" %) 21 +|=(% scope="row" %)**Stakeholder**|=**Description ** 22 +|[[image:Asset 26\@4x.png]]|((( 74 74 **USAR Coordination Cell** 75 75 76 -Manages the (international) coordination between all stakeholders involved in an incident .25 +Manages the (international) coordination between all stakeholders involved in an incident 77 77 ))) 78 -|[[image:Asset 25\@4x.png||alt="Asset 26@4x.png"]]|( % style="width:468.656px" %)(((27 +|[[image:Asset 25\@4x.png||alt="Asset 26@4x.png"]]|((( 79 79 **Team Leader (TL) - USAR** 80 80 81 81 Responsible for the whole USAR team. Communication with UCC ... ... @@ -82,22 +82,22 @@ 82 82 83 83 Participates at the team leader meetings to get tasks assigned 84 84 ))) 85 -|[[image:Asset 22\@4x.png]]|( % style="width:468.656px" %)(((34 +|[[image:Asset 22\@4x.png]]|((( 86 86 **Deputy Team leader - USAR** 87 87 88 88 Responsible for all staff at the Base of Operations (BOO) 89 89 ))) 90 -|[[image:Asset 23\@4x.png]]|( % style="width:468.656px" %)(((39 +|[[image:Asset 23\@4x.png]]|((( 91 91 **Staff - USAR** 92 92 93 93 Located at the BOO. Includes: Information, Staff, Media, ICT, and Hazmat 94 -)))| (%style="width:1px" %)95 -|[[image:Asset 21\@4x.png]]|( % style="width:468.656px" %)(((43 +)))| 44 +|[[image:Asset 21\@4x.png]]|((( 96 96 **Logistics - USAR** 97 97 98 98 Located at the BOO. Responsible for logistics of an incident 99 99 ))) 100 -|[[image:Asset 20\@4x.png]]|( % style="width:468.656px" %)(((49 +|[[image:Asset 20\@4x.png]]|((( 101 101 **Medical - USAR** 102 102 103 103 Located at the BOO. Medical professionals. ... ... @@ -108,17 +108,17 @@ 108 108 109 109 Assesses medical equipment for extraction 110 110 ))) 111 -|[[image:Asset 19\@4x.png]]|( % style="width:468.656px" %)(((60 +|[[image:Asset 19\@4x.png]]|((( 112 112 **Liaison - USAR** 113 113 114 114 Located at the BOO. Responsible for the communication with third-party organisations during an incident 115 115 ))) 116 -|[[image:Asset 18\@4x.png]]|( % style="width:468.656px" %)(((65 +|[[image:Asset 18\@4x.png]]|((( 117 117 **Chief of Operations - USAR** 118 118 119 119 Responsible for all rescue operations at all assigned worksites; usually at a worksite during setup and during critical phases 120 120 ))) 121 -|[[image:1724250237332-368.png]]|( % style="width:468.656px" %)(((70 +|[[image:1724250237332-368.png]]|((( 122 122 **Chief Search and Rescue - USAR** 123 123 124 124 Responsible for all staff at one worksite ... ... @@ -131,7 +131,7 @@ 131 131 132 132 Overall strategy and safety in line with guidance by CoO and advice of paramedic, structural engineer and squad leader after initial overview/ survey 133 133 ))) 134 -|[[image:Asset 16\@4x.png]]|( % style="width:468.656px" %)(((83 +|[[image:Asset 16\@4x.png]]|((( 135 135 **Squad Leader - USAR** 136 136 137 137 Located in the field. Leads the technical rescue operation ... ... @@ -144,42 +144,42 @@ 144 144 145 145 Decides and guides search techniques, routes inside the worksite and breaking/ breaching as well as rope rescue 146 146 ))) 147 -|[[image:Asset 15\@4x.png]]|( % style="width:468.656px" %)(((96 +|[[image:Asset 15\@4x.png]]|((( 148 148 **Structural Engineer - USAR** 149 149 150 150 Located in the field. Analyses structural integrity of buildings to assess risks of collapse and stabilises buildings where necessary 151 151 ))) 152 -|[[image:Asset 14\@4x.png]]|( % style="width:468.656px" %)(((101 +|[[image:Asset 14\@4x.png]]|((( 153 153 **Paramedic - USAR** 154 154 155 155 Located in the field. Assesses victim health and performs emergency treatment for victim stabilisation where necessary 156 156 ))) 157 -|[[image:Asset 13\@4x.png]]|( % style="width:468.656px" %)(((106 +|[[image:Asset 13\@4x.png]]|((( 158 158 **Maintenance - USAR** 159 159 160 160 Located in the field. Responsible for maintenance during an incident 161 161 ))) 162 -|[[image:Asset 12\@4x.png]]|( % style="width:468.656px" %)(((111 +|[[image:Asset 12\@4x.png]]|((( 163 163 **Rescue Expert - USAR** 164 164 165 165 Located in the field. Expertise in rescuing victims 166 166 ))) 167 -|[[image:Asset 11\@4x.png]]|( % style="width:468.656px" %)(((116 +|[[image:Asset 11\@4x.png]]|((( 168 168 **Search Tech - USAR** 169 169 170 170 Located in the field. Expertise in searching for victims 171 171 ))) 172 -|[[image:Asset 10\@4x.png]]|( % style="width:468.656px" %)(((121 +|[[image:Asset 10\@4x.png]]|((( 173 173 **Dog + Handler - USAR** 174 174 175 175 Located in the field. Searches for (entrapped) victims with the help of scent 176 176 ))) 177 -|[[image:Asset 24\@4x.png]]|( % style="width:468.656px" %)(((126 +|[[image:Asset 24\@4x.png]]|((( 178 178 **Fire Chief - FD** 179 179 180 180 Responsible for all staff at a fire department 181 181 ))) 182 -|[[image:Asset 9\@4x.png]]|( % style="width:468.656px" %)(((131 +|[[image:Asset 9\@4x.png]]|((( 183 183 **Incident Commander (IC) - FD** 184 184 185 185 Responsible for the incident as a whole ... ... @@ -188,7 +188,7 @@ 188 188 189 189 Chair of the team leader meetings 190 190 ))) 191 -|[[image:Asset 8\@4x.png]]|( % style="width:468.656px" %)(((140 +|[[image:Asset 8\@4x.png]]|((( 192 192 **Team Leader - FD** 193 193 194 194 Participate at the team leader meetings to get tasks assigned ... ... @@ -197,22 +197,22 @@ 197 197 198 198 Communication with "her/his" IC 199 199 ))) 200 -|[[image:Asset 7\@4x.png]]|( % style="width:468.656px" %)(((149 +|[[image:Asset 7\@4x.png]]|((( 201 201 **Chauffeur - FD** 202 202 203 203 Drives the firefighters to and around the incident 204 204 ))) 205 -|[[image:Asset 6\@4x.png]]|( % style="width:468.656px" %)(((154 +|[[image:Asset 6\@4x.png]]|((( 206 206 **Firefighter - FD** 207 207 208 208 Responsible for mitigating hazards such as fires and gas leaks 209 209 ))) 210 -(% class="warning" %)|//[[image:Asset 2\@4x.png]]//|( % style="width:468.656px" %)(((159 +(% class="warning" %)|//[[image:Asset 2\@4x.png]]//|((( 211 211 //**Tactical Operator - NEW**// 212 212 213 213 //Located in the BOO. Responsible for controlling robots remotely. // 214 214 ))) 215 -(% class="warning" %)|//[[image:Asset 1\@4x.png]]//|( % style="width:468.656px" %)(((164 +(% class="warning" %)|//[[image:Asset 1\@4x.png]]//|((( 216 216 //**Operational Operator (Field Operator) - NEW**// 217 217 218 218 //Located in the field. Responsible for controlling robots on-site. //