> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/dashboards/technical-conditions-dashboard.md).
# Technical conditions dashboard
The **Technical Conditions Dashboard** is the third tab of the Dashboard app. Where the **Fleet Live Status Dashboard** answers "what is the fleet doing right now?" and the **Trips Dashboard** answers "what did the fleet do over the past week?", the Technical Conditions Dashboard answers "how well is the fleet's hardware performing, and what needs attention?". It pulls GPS quality, power supply, mileage, fault codes, engine RPM, and safety events into a single view, so you can spot deteriorating devices and vehicles before they cause downtime.
{% hint style="info" %}
The Technical Conditions Dashboard is currently in beta (v1.0.0). It's an early version released so we can shape it based on real feedback. If something is missing, confusing, or could be more useful, please tell us through the **Send Feedback** button at the top of the tab. The three dashboards version independently, so the Fleet Live Status, Trips, and Technical Conditions tabs may show different version numbers.
{% endhint %}
Want more customization and detail? [Dashboard Studio](/docs/analytics/dashboard-studio.md) lets you build fleet analytics tailored to your own KPIs using IoT Query data. Recommended template to start with: [Fleet Anomaly Monitor](https://github.com/Navixy/navixy-iot-query-dashboard/blob/main/schemas/01-fleet-anomaly-monitor.md).
## How the dashboard defines fleet health
Several panels share the same status indicators, so it's worth reading the rules once before scanning the page.
An object counts as **active** if it has at least one hourly statistics record on file, meaning the device has communicated with the platform at some point in the stored history. Active does not mean active right now — an object that last reported a week ago still counts. An **inactive** object exists in your account catalog but has never produced an hourly record at all.
GPS quality combines two values reported by the device: the number of visible satellites and HDOP (Horizontal Dilution of Precision, a dimensionless measure of GPS geometry where lower is better).
| Status | Condition |
| ------------ | ----------------------------------------- |
| ⚫ No GPS Fix | HDOP is negative (unavailable or invalid) |
| 🔴 Critical | HDOP > 5, or satellite count ≤ 3 |
| 🟡 Warning | HDOP > 2, or satellite count < 6 |
| 🟢 Normal | HDOP ≤ 2 and satellite count ≥ 6 |
Battery and onboard (board) voltages are judged differently: each object's most recent reading is compared against that object's own historical average, rather than against a fixed threshold. This catches gradual deterioration that absolute limits would miss, and accommodates fleets with mixed 12 V and 24 V vehicles.
| Status | Condition |
| ----------- | ------------------------------------------------------------- |
| 🔴 Critical | Current voltage is more than 20% below the historical average |
| 🟡 Warning | Current voltage is 10–20% below the historical average |
| 🟢 Normal | Current voltage is within 10% of the historical average |
## Data window and refresh
The dashboard reads from the full hourly statistics history available for your account. There is no date picker, and the window cannot be changed. In practice this covers roughly the last 7 days of hourly aggregates, which is the typical retention horizon for the underlying store.
The "latest" values shown in the health monitor tables and in **Latest Diagnostics** always come from each object's most recent hourly record, regardless of how recent that record is. An object that last reported three days ago will still appear with its three-day-old values rather than being excluded.
The dashboard refreshes itself every **90 seconds** while the browser tab is in focus, and the **Update** button in the top-right corner forces an immediate refresh.
## Fleet summary
The top row of three KPI tiles frames the overall size and activity of your fleet.
| Tile | What it shows |
| -------------------- | ---------------------------------------------------------------------------------- |
| **Total Objects** | Every device registered in your account, whether or not it has ever reported data. |
| **Active Objects** | Devices that have produced at least one hourly statistics record. |
| **Inactive Objects** | Total Objects minus Active Objects. |
When to investigate
A non-zero Inactive count is worth a look at your object catalog: newly installed devices that haven't started reporting, decommissioned hardware that's still listed, or trackers with configuration problems. The gap between Total and Active also affects how other panels read: a large inactive share doesn't mean your active fleet is performing badly.
## Safety and diagnostics event counts
The second row of four KPI tiles counts how many hourly periods recorded a given type of event across the fleet. Each tile counts hours, not individual events: an hour with five SOS activations and an hour with one both add one to the count. The exception is **Amount of DTC Events**, which sums raw event counts and so reflects cumulative OBD activity rather than the number of affected hours.
| Tile | What it counts |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------- |
| **GPS Degraded Events** | Hours in which a device had fewer than 3 visible satellites. |
| **SOS Events** | Hours in which at least one SOS alarm was triggered anywhere in the fleet. |
| **Seatbelt Events** | Hours with at least one seatbelt violation — belt unfastened while the object was travelling faster than 5 km/h. |
| **Amount of DTC Events** | Total count of diagnostic trouble code events across every hourly period. |
## GPS quality
Two panels work together to surface devices with positioning problems. The bar chart tells you who has the most degraded hours; the health monitor tells you whose situation is getting worse.
| Panel | What it shows |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Top 10 Objects by GPS Degraded Events** (bar chart) | The 10 objects with the most hours of poor GPS quality. An hour counts as degraded when satellites ≤ 3, HDOP > 5, or HDOP is unavailable. |
| **GPS Health Monitor** (table) | One row per object. Current HDOP and satellite count alongside each object's historical averages, with trend arrows (▲ rising, ▼ falling, ► flat) and a Require Attention status using the thresholds above. |
The GPS Health Monitor sorts No Fix first, then Critical, Warning, and Normal; within each group, the worst readings sit at the top.
When to investigate
Objects at the top of the bar chart often have antenna damage, obstructions on the device, or mounting problems. The health monitor adds context: an object with a Critical status but a stable trend has a known long-running issue, while a Warning status with a falling trend is a situation that's actively deteriorating and worth catching early.
## Battery and power supply
This section covers two distinct power supplies, each with its own trend chart and health monitor. **Battery voltage** is the tracker's internal backup battery, used when the vehicle is off or disconnected. **Board voltage** is the vehicle's main electrical system, typically 12 V for cars and light vehicles or 24 V for trucks and heavy equipment.
| Panel | What it shows |
| --------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Battery Voltage Trend for Top 10 Objects** (line chart) | Backup battery voltage over time for the 10 objects with the lowest current battery charge percentage. |
| **Battery Power Supply Health Monitor** (table) | Current voltage vs. historical average per object, with trend arrow, absolute difference, and relative change as a percentage. Sorted with the largest relative drop first. |
| **Board Voltage Trend for Top 10 Objects** (line chart) | Onboard supply voltage over time for the 10 objects with the lowest current board voltage. |
| **Board Power Supply Health Monitor** (table) | Same structure as the battery monitor, applied to the vehicle's onboard supply. |
Both health monitors use the Critical / Warning / Normal voltage thresholds described earlier.
When to investigate
A downward voltage trend combined with a low charge percentage is the strongest signal that a tracker's backup battery is approaching failure.
Board voltage that drops while the engine is off is usually normal; a sustained drop while the engine is running indicates a charging or wiring problem. Comparing the board and battery monitors side by side is the quickest way to tell a tracker-side issue (battery degrading, board stable) from a vehicle-side issue (board degrading, battery may follow).
{% hint style="info" %}
Both health monitors only include voltage readings between 1 V and 50 V to filter out invalid sensor values. Objects whose readings all fall outside this range — typically because the sensor isn't fitted or isn't reporting — are excluded from the table entirely.
{% endhint %}
## Mileage
Two panels track odometer activity across the fleet, both using the hardware odometer reported by the device.
| Panel | What it shows |
| ------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **Top 10 Objects by Mileage** (table) | The 10 objects with the highest current odometer readings, plus the timestamp of the message that produced each value. |
| **Mileage Trend for Top 10 Objects** (line chart) | Odometer readings over time for those same 10 objects. |
Objects without a hardware odometer sensor do not appear in either panel, even if they have other telemetry.
When to investigate
A line that stays flat indicates a vehicle that has been parked or whose sensor has stopped reporting. A sharp vertical jump usually means a manual odometer correction or a sensor replacement, both of which are worth verifying against your maintenance records.
## Fault codes
The **Objects with Active Fault Codes** table lists every hourly record in which one or more active diagnostic trouble codes (DTCs) were reported by the vehicle's OBD interface. Each row is one hourly record, not one object — the same vehicle may appear multiple times if it reported fault codes in different hours.
Columns include the object label, the message timestamp, the array of active fault codes (in standard formats such as `P0300`), and the number of distinct codes active during that hour. When the table is empty, it shows "No DTC events found for the last 7 days".
When to investigate
A vehicle that appears many times with the same codes has a persistent fault that hasn't been cleared. A vehicle that appears once with many codes may have had a communication burst or a severe single event. Either case is worth a workshop visit.
## Engine and speed
Two panels cover engine behavior and peak speeds.
| Panel | What it shows |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Top 10 Events by RPM** (table) | The 10 individual hourly periods with the highest engine RPM readings recorded anywhere in the fleet, sourced from the vehicle CAN bus. Each row is one hour, and the value shown is the peak RPM during that hour. |
| **Speed Trend for Top 10 Objects** (line chart) | Peak hourly speed over time for the 10 objects with the lowest current maximum speed — designed to surface vehicles whose top speed has been consistently low. |
When the RPM table is empty, it shows "No rpm values found for the last 7 days".
When to investigate
RPM values above 10,000 are unusual for road vehicles and typically indicate either a genuine over-rev event or a sensor fault.
Consistently low top speeds in the Speed Trend chart can point to route-constrained assets, speed-limited equipment, or vehicles that have been parked for most of the data window.
## Latest diagnostics
The **Latest Diagnostics** table at the bottom of the dashboard is the single-row-per-object summary of fleet health. It shows the most recent value of every metric the dashboard tracks for every object in your account: last update timestamp, battery level and voltage, board voltage, HDOP, satellite count, mileage, active DTC codes and event count, peak RPM and speed, SOS and seatbelt events, and peak acceleration. Every column is sortable.
How to use this table during an investigation
Sort by **Last Update** to find objects that have stopped reporting — this is the first thing to check when a vehicle appears stale in other panels. Sort by **Battery Voltage** or **Board Voltage** to find the lowest current readings without waiting for the health monitors to flag them. Sort by **DTC Events** or **SOS Events** to bring objects with current incidents to the top.
{% hint style="info" %}
The table shows up to 600 objects, ordered by most recently updated first. If your account has more than 600 objects, the least recently updated ones will not appear here; use the other panels to investigate them.
{% endhint %}
## Exporting panel data
Every panel on the Technical Conditions Dashboard, both charts and tables, has a download icon in its top-right corner. Click it to export the panel's current data as a CSV file. The export reflects the state of the panel at the moment you click, which is useful for capturing a snapshot for a handover, a maintenance report, or further analysis in a spreadsheet.
Like the other Dashboard tabs, the Technical Conditions Dashboard does not currently support global filters, custom time ranges, or shared links.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://navixy.com/docs/user/guide/dashboards/technical-conditions-dashboard.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.