How do mutual, shared, and team situational awareness differ in multi-robot systems?

Two axes separate the three awareness terms

The paper's core move is to stop treating MA, SSA, and TSA as loose synonyms and instead place them on a two-dimensional taxonomy. The first axis is the object of awareness: what an agent must hold a representation of, such as a peer's planned trajectory, a survivor's location and status, or platform-specific airspace conditions. The second axis is awareness distribution: whether that representation stays individualized per agent or must be uniform across the team.

Positioning each term on both axes is what produces the hierarchy claim. MA sits at the individualized end, SSA at the uniform end, and TSA occupies a mixed position because it combines shared mission-critical elements with role-specific knowledge. The taxonomy is a conceptual framework, not a measured system property, so its value is in specifying coordination requirements rather than reporting performance numbers.

Mutual awareness is directional and individualized

Mutual Awareness is defined in the paper as the awareness each agent holds of its teammates' internal states, including their intentions, beliefs, goals, and plans, where each agent forms an individualized understanding shaped by its own perspective and role. The object of awareness is the peer's internal state; the distribution is individualized.

The paper stresses that MA is inherently directional and may be asymmetric. Citing Villa et al., it distinguishes a watching awareness, where member A can observe B but B cannot observe A, from a watched awareness, where A knows B is observing them but cannot reciprocate. In the Search and Rescue scenario, MA governs how two UGVs track each other's planned trajectories during reconnaissance: UGV A plans a path in its local occupancy grid, and UGV B integrates that path into its own costmap. B's representation need not match A's internal encoding, only capture the same spatial intent in B's own terms.

Shared situational awareness requires uniform interpretation

Shared Situational Awareness is defined as the awareness all agents must maintain of the environmental and mission elements that fall within every agent's requirements, specifically their intersection, such that all agents reach an aligned interpretation of the information essential for coordinated action. The object of awareness is the shared subset of mission-critical elements; the distribution is shared.

The paper's Search and Rescue illustration makes the requirement concrete. When a UAV detects a survivor and broadcasts their location and assessed status, every agent must integrate the same conclusion regardless of its internal representation: a survivor is present at a specific location with a given urgency. No agent may hold a divergent interpretation of this element without risking conflicting rescue priorities. The paper also notes that the information to be shared should be defined by examining where each team member's SA requirements overlap, so that sharing does not become excessive communication overload.

Team situational awareness mixes shared and role-specific knowledge

Team Situational Awareness is defined as the complete awareness a robotic team must maintain, encompassing both the shared understanding of mission-critical elements common to all agents (SSA) and elements of the environment that are relevant to the mission yet specific to certain roles, for which divergent, role-shaped understanding is appropriate. The object of awareness spans both shared and role-specific elements; the distribution is mixed.

In the Search and Rescue scenario, all robots share awareness of survivor locations and mission progress, while UAVs additionally maintain their own role-specific assessments of airspace conditions and safe landing zones, and UGVs track debris properties and terrain traversability. The paper states that TSA encompasses all three layers: peer-state awareness, shared mission-critical awareness, and role-specific environmental knowledge. This partial alignment is presented as enabling flexibility and task specialization while still supporting cohesive team behavior.

Why the hierarchy matters for coordination requirements

The paper's argument is that conflating the three terms is consequential because each imposes different requirements on a robotic system. MA requires agents to maintain awareness of each other's beliefs, plans, and states to enable basic coordination. SSA builds on MA by demanding shared semantic understanding of mission-critical environmental elements, ensuring aligned interpretation across the team. TSA integrates both shared awareness and role-specific knowledge, enabling specialized coordination while maintaining collective coherence.

Because the requirements differ, the paper argues that treating the terms as interchangeable obscures what a system must actually implement. The taxonomy is offered as a conceptual foundation for principled specification, design, and comparison of collective awareness in multi-robot systems, rather than as an empirical claim about coordination performance.

The Search and Rescue case study grounds each position

The illustrative example concerns a heterogeneous robotic team cooperating in a Search and Rescue operation: aerial robots (UAVs) equipped with cameras and image analysis capabilities, and ground robots (UGVs) equipped with manipulation capabilities. The mission unfolds across four interdependent phases: deployment, reconnaissance, rescuing, and monitoring. The paper notes these phases are not strictly sequential and often overlap, requiring the team to maintain awareness at multiple levels simultaneously under conditions of unreliable communication, dynamic environmental changes, and role-based task specialization.

The case study is used to ground each abstract taxonomy position in concrete coordination requirements. During reconnaissance, UGVs must navigate debris-filled corridors without interfering with each other; UAVs detect and localize survivors and broadcast their location and assessed status to the whole team; and UAVs identify safe landing zones using aerodynamic models specific to aerial platforms and share these assessments with other UAVs for mission replanning. The paper states that each mission phase demands different combinations of awareness types.

What the taxonomy does not yet establish

The paper is explicit that the taxonomy is conceptual. It does not report deployed-system measurements, and the Search and Rescue scenario is an illustrative case study rather than an experimental evaluation. The authors state that future work should formalize the requirements identified by the taxonomy as verifiable system specifications, develop architectural components that instantiate these requirements, and empirically evaluate their effect on coordination performance in deployed systems.

This matters for how readers should use the framework. The hierarchy and the three definitions are the paper's contribution; whether systems built to these specifications coordinate better remains an open empirical question that the paper itself flags rather than answers.

The practical priority is specifying which elements must align

The most decision-relevant output of this paper is not a single metric but a specification question: for each element a team must know, is individualized understanding sufficient, must all agents converge on the same interpretation, or is the element role-specific and appropriately divergent? The taxonomy's two axes give that question a structure, and the Search and Rescue phases show it changing across a mission rather than being fixed once.

The paper's own priority is therefore to push multi-robot coordination work toward principled specification and meaningful comparison, instead of using MA, SSA, and TSA as interchangeable labels. Readers evaluating a coordination approach can use the containment hierarchy to ask which layer the approach actually implements, and whether the elements it shares are the mission-critical intersection or an over-broad broadcast that risks communication overload.

Sources used in this answer