Skip to Content

Changes for page Roles

Last modified by Tjalling Haije on 2025/09/15 14:25
From version 6.1
edited by Tjalling Haije
on 2025/09/08 12:23
Change comment: There is no comment for this version
To version 9.1
edited by Tjalling Haije
on 2025/09/08 12:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,7 +2,7 @@
2 2  
3 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 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. 
... ... @@ -33,7 +33,7 @@
33 33  == General insights from interviews with stakeholders ==
34 34  
35 35  
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.
36 +**Split control & analysis.** Robots 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 37  
38 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 39