Changes for page Roles

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Objects (0 modified, 1 added, 0 removed)
  • XWiki.XWikiComments[0]

Details

Page properties

Content

...	...	@@ -1,3 +1,70 @@
	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	+**Firefighting Exclusive Stakeholders SYNERGISE technologies**
	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.
	50	+)))
	51	+
	52	+== General insights from interviews with stakeholders ==
	53	+
	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.
	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.
	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.
	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.”
	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.
	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	+
	67	+
1	1	== All roles within USAR operation ==
2	2
3	3	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.

XWiki.XWikiComments[0]

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.IvanaAkrum

Comment

...	...	@@ -1,0 +1,1 @@
	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,0 +1,1 @@
	1	+2024-07-12 14:12:45.284