Audience Definition
- Primary Users: The operators responsible for coordinating the activities of unmanned vehicles in a response to a chemical or explosives disaster event. The program will generally be working from the Emergency Operations Center (EOC) which will be stationed at the perimeter established around the event. The operator will not necessarily have any knowledge of the terrain the robots are navigating over. The operators will be trained emergency response personnel with a specific training using the interface.
- Stakeholders: The Human-Machine Teaming Lab directing the development of this project. This project will be the basis of research into effective methods for heterogeneous ground and aerial multirobot control.
Requirement Types
- Robotic Interface — Hardware requirement
- Control — Operator control requirement
- Scenario — Requirement pertaining to the task being tested
- Data — Requirements for data from the environment to be presented to the operator
- Backend — Specific technology implementation requirements
Requirements
- Client specified requirements:
-
- Requirement ID: 1
- Requirement Type: Robotic Interface
- Description: Support at least 10 vehicles
- Rationale: Pushes the maximum number of vehicles controlled in current interfaces which maintaining plausibility of implementation.
- Validation Measurement: Ten robots being present in the interface when the program is started.
-
- Requirement ID: 2
- Requirement Type: Robotic Interface
- Description: Support mixed aerial and ground vehicles
- Rationale: Modern response teams potentially to include mixed vehicle types.
- Validation Measurement: Different icons in the interface will allow the user to distinguish between types of robots.
-
- Requirement ID: 3
- Requirement Type: Robotic Interface
- Description: Support two types of ground vehicles
- Rationale: Robots with different capabilities are used in disaster response.
- Validation Measurement: Different icons in the interface will allow the user to distinguish between types of robots.
-
- Requirement ID: 4
- Requirement Type: Control
- Description: Support ground vehicles providing victim assessment and chemical sensing
- Rationale: Victim assessment and chemical sensing are two common response needs.
- Validation Measurement: Different icons in the interface will allow the user to distinguish between types of robots.
-
- Requirement ID: 5
- Requirement Type: Control
- Description: Support teleoperation of robots
- Rationale: The state of the art sometimes requires detailed human intervention to perform certain tasks with a robot.
- Validation Measurement: The interface will show the video feed from a particular robot. The operator can then command the robot to perform a set of rudimentary actions.
-
- Requirement ID: 6
- Requirement Type: Data
- Description: Provide video from UV
- Rationale: One useful method for gaining an awareness of the state of a robot is to see its environment.
- Validation Measurement: The operator can select a robot and view its video feed.
-
- Requirement ID: 7
- Requirement Type: Control
- Description: Require only one operator
- Rationale: Trained individuals present at a response may be limited.
- Validation Measurement: All tasks required can be performed by a single person.
-
- Requirement ID: 8
- Requirement Type: Scenario
- Description: Focus on chemical and explosives disaster response
- Rationale: Chemical and explosives disaster response are a situation where robots can effectively augment the response capabilities of a human team.
- Validation Measurement: The interface will integrate sensor readings to provide an overview of known areas of contamination.
-
- Requirement ID: 9
- Requirement Type: Scenario
- Description: Support victim analysis
- Rationale: There will frequently be victims within to perimeter who potentially need medical treatment.
- Validation Measurement: The interface should support existing victim analysis guidelines for human teams.
-
- Requirement ID: 10
- Requirement Type: Backend
- Description: Must be capable of using simulation data from USARSim
- Rationale: Client specified simulator.
- Validation Measurement: Confirm interface can connect and work with USARSim.
-
- Requirement ID: 11
- Requirement Type: Robotic Interface
- Description: Simulation robots move up to 30mph
- Rationale: Predicted maximum speed of ground robots.
- Validation Measurement: Set speed of several ground robots to 30mph and confirm that the interface can maintain data rates.
-
- Requirement ID: 12
- Requirement Type: Control
- Description: Support at least 5 concurrent tasks
- Rationale: Client specified the interface must support at least 5 concurrent tasks.
- Validation Measurement: Add 5 tasks to a newly instantiated interface and confirm that the interface is still operational and the operator can change between all tasks.
- Developer Specified Requirements:
-
- Requirement ID: 13
- Requirement Type: Data
- Description: Operator is able to quickly assess the status of an individual robot
- Rationale: In order to effectively control large groups of mobile robots, the operator must be able to tightly monitor their operation.
- Validation Measurement: Add 10 robots to the interface and confirm that the operator can toggle between robots with minimal delay and effort.
-
- Requirement ID: 14
- Requirement Type: Data
- Description: Interface must assist the operator in maintaining appropriate situational awareness
- Rationale: High levels of situational awareness are required to perform this task.
- Validation Measurement: Due to design time constraints, a SAGAT test will not be performed, but testable responses will be used. Additionally, a subjective measures test will also be conducted, possibly a SART test.
-
- Requirement ID: 15
- Requirement Type: Data
- Description: Alert the operator of unexpected events that require attention
- Rationale: Controlling large groups of mobile robots is a challenging task because they are frequently situated in complex and highly dynamic environments. Additionally, mobile robots can themselves be complex and dynamic. This dynamic nature can cause frequent unexpected error conditions to occur which require immediate attention.
- Validation Measurement: Simulate several error conditions and confirm that the interface provides messaging of some form to the operator.
Non-Required Possible Program Characteristics
-
- Requirement ID: 16
- Requirement Type: Control
- Description: Provide an indicator to the operator as to how long he has been teleoperating a particular robot
- Rationale: The state of the art requires frequent monitoring of robots
- Validation Measurement: Set the interface to work with one robot and confirm that after some time period, the interface notifies the operator that it may be beneficial to look over the other robots in the system.