Analytics

The Analytics page provides insights into the performance and activity of sensors, specifically how they receive and process incoming data from the field.

It includes multiple sections for monitoring sensor efficiency and drone detection patterns:

  • Processing Time
  • Sensor Diff
  • Drones with Pilot/Home
  • Drones with DJI Multicopter
  • Drones Per Asset
For all Analytics section graphs:
  • Users can zoom in/out using the mouse scroll function.
  • Users can toggle individual data lines by clicking on items in the legend, allowing for custom visualization of datasets.
 
eplasp.io_(High res) (17) 1
Processing Time

When the Analytics page is accessed, users begin in the Processing Time section. This section presents graphs that illustrate how long updates take to process and how many aircraft are handled per update. 
Displayed Graphs Include:

  • Past Sensor Updates Sampled – Shows duration types over selected time periods.
  • Detailed Updates – Tracks how long various processes take (e.g., elevation calculation, flight ID retrieval).
  • Aircraft Per Update – Displays the number of aircraft processed in each update over time.
  • Median Crewed Processing Speed vs Number of Aircraft – Compares recent and past data based on aircraft count.
Available Parameters:

Users can adjust the data displayed in the graphs using the following parameters:

  • Time Period – Choose between 1, 3, 6, 12, or 24 hours.
  • Update Category – Select the type of update to analyze: All, Crewed, Drone, Line of Bearing, Radar, or Ship.
  • Duration Type – Switch between Total Time to Process Update and Time Per Aircraft.
These parameters help tailor the visualizations to provide focused insight into sensor processing behavior across different conditions.
Sensor Diff

Sensor Diff is defined as the difference between the timestamp reported by the sensor for an update and the time at which the UNIFY.C2 backend received and began processing that update. This metric helps assess data latency and transmission performance across environments.
This section allows users to select an asset from a dropdown and visualize the Sensor Diff Over Time graph, which includes:

  • Sandbox Sensor Diff (seconds)
  • Production Sensor Diff (seconds)
Both are plotted over a selected time range, enabling users to evaluate and compare the timing consistency of sensor updates between sandbox and production environments.
eplasp.io_(High res) (18) 1
Flight History Table

Beneath the graph, users will find a Flight History-style table that lists flight logs captured by the selected asset. This table includes key fields such as:

  • Flight ID
  • Detection Time
  • Aircraft Type
  • Max Altitude
  • Flight Duration
  • Distance Between Pilot and UAS
  • Violation
  • Flight Profile – Includes a “VIEW” button to open the detailed flight violation and replay interface.
  • View Time Machine – Includes a button that directs users to the COP map, automatically inputting the detection time for playback in the Time Machine (see more on Time Machine ).
 
The table layout is consistent with the Flight History section (see more on
Flight History), enabling users to quickly identify, review, and analyze relevant flight activity associated with sensor performance over time.

Drones With Pilot/Home

The Drones With Pilot/Home section displays the percentage of detected drone flights that include either a home position or pilot position over time. This metric helps users assess how frequently location-based metadata is captured during detections, providing insight into sensor effectiveness and flight transparency.

eplasp.io_(High res) (19) 1
Drones With DJI Multicopter

The Drones With DJI Multicopter section displays the percentage of detected drone flights identified as DJI multicopters over time. This provides visibility into the prevalence of DJI-manufactured drones within detected activity, offering insights into manufacturer trends and potential operational risks.

Note: A high percentage in this metric may indicate that UNIFY.C2 is unable to accurately determine the type of many detected drones, defaulting to DJI as a fallback classification. This could suggest:

  • An outdated Remote ID database, or
  • Issues with the drone sensors or data parsing that require review.
A low percentage is typically a positive indicator, meaning the system is correctly identifying a broader variety of drone types, improving situational clarity and threat assessment.

eplasp.io_(High res) (20) 1
Drones Per Asset

The Drones Per Asset section displays the number of drones detected per asset over a selected time range. Users can customize the view using two dropdowns:

  • Asset Class – Choose between Cooperative-RF or Remote-ID.
  • Time Range – Select either 7 days or 30 days. (based on GMT)

eplasp.io_(High res) (24) 1 eplasp.io_(High res) (23) 1
Graph View

A line graph is shown at the top of the section, where each line represents an individual asset. This visualizes how drone detections fluctuate over time for each asset.

Data Table

Below the graph is a detailed table that breaks down the detection counts per day. The table includes:

  • Asset Name – The name of the sensor or system that detected drones.
  • Date Columns – Each additional column represents one day within the selected time range (either the past 7 or 30 days).(based on GMT)
  • Daily Detection Counts – Each cell shows the number of drone detections by that asset on that specific day.