• Smart-Data: A modern approach to robotic data capture that enables scenario-driven data collection through deployed software agents. Characterized by remote management, Over-the-Air (OTA) updates, selective signal recording, automated event tagging with metadata for searchability, and robotic data democratization.

​
Physical Entities

  • System: Physical devices (robot, computer, drone, vehicle, etc.) where Agents are installed to collect Smart-Data.
  • Agent: An executable program deployed on Systems that monitors data streams and initiates custom data recording based on predefined scenarios. Agents can receive Over-The-Air (OTA) updates.

​
Data Sources

  • Data Source: Device or file (e.g., ROSbag) that exposes one or many data streams.
  • Signal: A single data stream from a Data Source which can be monitored and/or recorded.

​
Monitoring & Recording

  • Trigger: A set of Signals to monitor, conditions, and recording strategies that define data capture scenarios for generating Smart-Data.
  • Monitor: Custom component within an Agent that tracks specific data points or system metrics.
  • Conditions: Logical rules that determine when data recording should occur (i.e. robot is stopped)
  • Recorder: Custom component within an Agent responsible for capturing, tagging and transferring specified data streams.
  • Implementation: An executable binary developed from the Heex SDK, which implements monitors and/or recorders and deployed in Agents to monitor or record given Signal.

​
Events & Recordings

  • Event: Generated when all conditions of a given trigger are met, and which results in a notification and tagged data capture from Recorders.
  • Recording: A custom format digital document/file captured by the Recorder Implementations in response to a specific Event, containing relevant data and tags for searchability.

​
Organization & Classification

  • Label: Key-value pairs used to classify and efficiently search resources.
  • Group: A special Label used to group similar or different Systems together for bulk monitoring and management.
  • Status: Automatically updated to reflect the current state of Systems, Triggers, Implementations, and other components (e.g., requested, to be deployed, ready).