The core concepts in Sift build on its telemetry data model of Assets, Channels, and Runs. The terms below describe the key objects used to analyze and review telemetry in Sift, workflow and analysis terms, and data ingestion methods.
A physical or virtual system that produces telemetry data in Sift. Assets organize data sources such as vehicles, test rigs, robots, or spacecraft so that telemetry can be associated with the correct system and analyzed consistently across Runs. See Assets.
An individual telemetry signal recorded from an Asset, typically represented as a time-series measurement such as temperature, voltage, or pressure. Channels are the fundamental data streams that users visualize and analyze. See Channels.
A derived signal created from one or more Channels using mathematical or logical expressions. Calculated Channels let users generate new signals and insights without changing the original telemetry data. See Calculated Channels.
A defined time period during which telemetry is recorded from an Asset, such as a test, experiment, or operational session. Runs provide the primary time context for organizing and analyzing telemetry. See Runs.
A note attached to telemetry data to record observations, findings, or issues discovered during analysis. Annotations help teams capture insights directly alongside the data. See Annotations.
A workspace that groups related Reports and Annotations into a coordinated review process. Campaigns help teams organize large analysis efforts and track progress across Runs or systems. See Campaigns.
The main Sift workspace used to visualize and analyze telemetry data. Users plot Channels, compare Runs, and investigate behavior over time. See Explore.
A visualization container within Explore that displays telemetry data using a chart or table. Multiple panels allow users to compare signals or views side by side. See Panels.
A defined condition that evaluates telemetry data to detect patterns, anomalies, or events automatically. Rules help teams identify important behavior in telemetry without manually scanning signals. See Rules.
Custom logic written by users to transform or analyze telemetry data. UDFs allow teams to reuse calculations across Rules, Calculated Channels, or other analysis workflows. See User-Defined Functions.
A feature that exports telemetry data from Runs or Channels for use outside Sift. This allows teams to move data into other analysis tools or archives. See Advanced Export.
A method for importing data either programmatically or directly through the UI. Supported formats include CSV, Parquet, TDMS, Chapter 10, and Rosbags. See Import data files.
A method for streaming telemetry data into Sift using Protocol Buffers (Protobuf) messages. This format enables efficient, structured transmission of telemetry data from external systems into Sift’s ingestion pipeline. See Protobuf Ingestion.
A configuration that defines how telemetry data is streamed into Sift for a specific Asset. It specifies how incoming data is associated with the Asset and processed during ingestion. See Ingestion Config Based Streaming.
