7.3 UV-Robotics: Execution Monitoring Issues

The initial monitoring issues apparent within the UV-Robotics domain can be divided into the following four categories:

• Monitoring the completion of, or progress toward, a basic action (e.g., go to a waypoint)

• Monitoring the satisfaction or completion of the multiple tasks to which the robot is currently committed (e.g., pursue evader, patrol area, photograph target every 2 hours)

• Monitoring the activity of unknown or adversarial entities

• Monitoring the state of the communication network, the robot, and other team members (e.g., communication network quality or integrity, robot mobility, or battery level)

Comparing these to our ontology in Section 4, the first two categories involve the general alert types plan constraint violated and constraint violation projected. However, they exist at different levels of abstraction and often have different temporal impact and associated monitoring requirements. The third category cleanly fits the adversarial activity detected alert type and triggers alerts for both autonomous control and user reporting. The fourth category is essential both to team-based automated operation and effective user interaction, and involves policy constraint violated alerts, reporting requirement alerts, and system problem detected alerts.