2. FR Organisation

USAR missions involve a structured First Responder organisation to manage complexity. Understanding the hierarchy and coordination of teams is crucial for integrating new technology. European countries have varied USAR setups, but common elements exist under international guidelines:

• Team Structure: A USAR team typically comprises five functional components – Management, Search, Rescue, Medical, and Logistics. The Team Leader oversees operations and liaises with the local incident command. Each function has a supervisor (e.g. Search Team Manager, Rescue Squad Leader) and specialists (search dog handlers, technical search operators, rescue technicians, medics, etc.).
• Hierarchy & ICS: Many operations use an Incident Command System or similar structure. On-site, a Local Emergency Management Authority (LEMA) or Incident Commander coordinates all agencies. The USAR Team Leader integrates into this structure, often through an On-Site Operations Coordination Center (OSOCC) in international responses. Clear roles (e.g. Safety Officer, Structural Engineer advisor) ensure accountability and communication flow.
• Interagency Coordination: USAR teams often work alongside firefighters, police, medical services, military units, and volunteers. In Europe, most USAR teams are part of fire and rescue services, though some countries use civil protection or military civil-defense units. Common procedures (like INSARAG marking systems) help different teams cooperate. However, terminology and rank structures can vary by country (e.g. a “Sector Commander” in one nation might be a “Site Manager” in another).
• European Institutions: Some nations maintain one national USAR task force (e.g. the Netherlands’ USAR.NL), while others have regional teams (e.g. Germany’s THW units or UK Fire & Rescue USAR teams). All INSARAG-certified teams meet minimum standards (rapid deployment, self-sufficiency, training) and can be mobilized through the EU Civil Protection Mechanism for international disasters. Language and cultural differences require flexibility in coordination.

Implications for System Design: The system must fit into existing command structures and augment, not disrupt, communication workflows. For example, information should be accessible according to role – a team leader needs an overview, while a search specialist might need detailed sensor data. Supporting multi-agency work means the system should enable easy information sharing between organizations (police, medics, etc.) while maintaining data security and role-based access. Variations across Europe imply the system should be configurable to different organisational models and languages. Recognizing key Stakeholders (incident commanders, team leaders, specialists) and their needs is critical, tying into our Personas and Use Cases to ensure technology adoption by all user groups.