📘 Resource Overview & Documentation Details

You are viewing the technical directory listing for Supervisory Control for Unmanned Vehicles: CaSHMI. This engineering resource is curated under our Human Machine Interface division to support automation specialists, control systems engineers, and manufacturing technicians looking for verified reference materials.

🔍 Contextual Abstract & Technical Scope

Share Summary:LinkedInEmail

Supervisory control for unmanned vehicles requires a different approach from remotely piloting one vehicle at a time. As missions involve multiple unmanned vehicles (UxVs), operators need to manage tasks and respond to changing events without continuously controlling each platform. The Control Station Human Machine Interface (CaSHMI) effort addresses this challenge with human-machine interface (HMI) concepts intended to support mission-level management across UxV platforms.

CaSHMI was framed as a Navy-focused effort to develop prototype interfaces and a concept of employment for supervisory control. Its central idea is to let operators engage vehicles through mission tasks, while software and automation support the interaction. The goal was not simply to put more vehicle controls on one screen, but to rethink how people, interfaces and unmanned systems work together.

Why multi-vehicle control calls for a different interface

In the approach described as current practice, teams of multiple operators control a single unmanned vehicle, and managing several vehicles follows a sequential pattern. This can make personnel and operator attention significant constraints as missions grow more complex.

CaSHMI identifies a related design limitation: the remote-piloting interface model is manpower intensive and often tied to separate, “stove-piped” vehicle control systems with disparate HMIs. A flight-control interface designed around one vehicle may not translate well to managing several UxVs, particularly as autonomy capabilities emerge. Mission management calls for a view of tasks and vehicle activity that can support oversight without requiring continuous, individual attention to each platform.

CaSHMI’s supervisory control for unmanned vehicles concept

Rather than treating each vehicle primarily as something an operator pilots, CaSHMI proposes an integrated, mission-management approach in which vehicles act as service providers. An operator can request that a vehicle engage in a specific task, instead of giving it sequential attention through direct control. This shifts the interface focus from vehicle-by-vehicle piloting toward coordinating mission activity.

The proposed model recognizes that operators have finite capacity and should engage with the system at appropriate points, rather than remain continuously vigilant over every vehicle. Interfaces would be designed for intermittent warfighter engagement, using automation aligned with expected technology capabilities. The effort also sought to support dynamic mission events, where task management may need to adapt as operational needs change.

One intended outcome was to enable a single operator to manage two or more UxVs for one mission. This was a target for the concept and prototype work, not a claim that the capability had already been demonstrated or fielded.

Modular software and platform integration

CaSHMI’s HMI concepts were planned as modular software operating through a service-oriented architecture. The software would work with UxV controller software and Navy mission-planning software, with the aim of making the interface approach usable across multiple UxV platforms.

Cross-platform use does not mean every vehicle presents identical information or functions. The research plan called for identifying both common and platform-specific information requirements. A scalable interface would need to communicate the information operators share across platforms while accounting for the requirements of individual vehicles and mission contexts.

Control could also pass between operators as the mission moved through different phases. Prototype HMI designs were intended to reflect the information requirements of the operator responsible at each phase. This handoff concept makes operator roles and the timing of engagement important parts of interface design, alongside the display itself.

Human factors and evaluation priorities

Developing a useful supervisory interface involves more than connecting software components. CaSHMI’s research challenges included applying human-factors and cognitive-engineering principles to display design. The aim was to develop design options around identified information needs, helping operators understand what requires attention and what tasks are being managed.

The effort also proposed a suite of measures of effectiveness to evaluate supervisory control. These measures were to consider both operator state and task performance. In combination, those evaluation areas could help assess whether an interface supports mission work while respecting human capacity. The source material does not specify particular measures or report evaluation results.

Key design questions for this kind of system include:

  • Which information is essential across all supported platforms, and which depends on a specific vehicle?
  • How should task requests and changing mission events be presented to the operator?
  • When should control or responsibility pass to another operator?
  • How can evaluation account for both operator state and successful task performance?

Planned transition and operational relevance

The effort identified alignment with the Navy’s Common Control System (CCS) Build III and the AN/BYG-1 combat system as part of its transition rationale. Prototype software was intended for delivery to the submarine community for integration into BYG-1 and to the Naval Air Systems Command Common Control System. The stated intent was to provide concepts and prototypes for integration and future development; the material does not establish that integration was completed.

For system integrators and technical decision-makers, the broader lesson is that multi-vehicle operation is an architecture and human-systems challenge as well as a control-software challenge. Common interface concepts, service-oriented software, mission-planning connections and clearly defined operator handoffs all contribute to a coherent approach. The design must also preserve room for platform-specific information and requirements.

Conclusion

CaSHMI sets out a mission-centered alternative to sequential remote piloting: operators request and oversee tasks across multiple UxVs, with modular software and automation supporting the interaction. Its intended benefits included reduced manning, dynamic task management and common controls across Navy platforms. For organizations planning supervisory systems, the practical implication is to design around mission tasks, operator capacity, platform differences and measurable human-system performance—not merely to combine separate vehicle-control screens.

Access Official Technical PDF