Fleet Monitoring
Real-Time Telemetry
Section titled “Real-Time Telemetry”The MDM platform ingests telemetry from all connected devices and presents it through multiple views.
Telemetry Data Points
Section titled “Telemetry Data Points”RC500 devices report the following metrics at configurable intervals:
| Category | Metrics |
|---|---|
| System | CPU usage, memory usage, uptime, temperature |
| Network | WAN type, throughput, latency, failover state |
| Cellular | RSRP, RSRQ, SINR, band, technology, operator |
| WiFi | Client count, channel utilization |
| GPS | Latitude, longitude, speed, heading, satellites |
| VPN | Tunnel status, bytes transferred |
Reporting Intervals
Section titled “Reporting Intervals”| Parameter | Default | Range |
|---|---|---|
| Heartbeat | 60s | 10s – 3600s |
| Telemetry | 60s | 10s – 3600s |
| GPS (moving) | 30s | 5s – 300s |
| GPS (stationary) | 300s | 60s – 3600s |
Intervals are configurable per-device or per-fleet through configuration profiles.
GPS Fleet Map
Section titled “GPS Fleet Map”The fleet map provides a real-time view of all GPS-equipped devices.
Features
Section titled “Features”- Live positions — Updated every 30 seconds
- Track history — View historical routes for any time range
- Track playback — Animated replay of device movement
- Geofences — Visual overlay of defined zones
- Clustering — Automatic marker clustering at zoom levels
- Layers — Map, satellite, and terrain views
Track Playback
Section titled “Track Playback”To replay a device’s route:
- Click a device on the map or device list
- Select Track History
- Choose a date/time range
- Click Play to animate the route
- Use speed controls (1x, 2x, 5x, 10x) to adjust playback
Geofences
Section titled “Geofences”Define geographic zones for monitoring:
- Navigate to Geofences
- Click Create Geofence
- Draw a polygon on the map
- Name the geofence and set alert rules
- Assign devices to monitor
Alert triggers:
- Enter — Device enters the geofenced area
- Exit — Device leaves the geofenced area
- Dwell — Device remains in zone longer than threshold
Device Health Monitoring
Section titled “Device Health Monitoring”Online/Offline Detection
Section titled “Online/Offline Detection”A device is considered offline when:
- No heartbeat received for 3x the configured heartbeat interval
- Example: 60s interval → offline after 180s of silence
Health Indicators
Section titled “Health Indicators”| Indicator | Healthy | Warning | Critical |
|---|---|---|---|
| Signal (RSRP) | > -90 dBm | -90 to -110 | < -110 dBm |
| Memory | < 70% | 70-90% | > 90% |
| Uptime | > 24h | < 1h (recent reboot) | — |
| Firmware | Current | 1 version behind | 2+ versions behind |
Trip Detection
Section titled “Trip Detection”For GPS devices, the platform automatically detects trips:
| Event | Trigger |
|---|---|
| Trip Start | Ignition ON or speed > threshold |
| Trip End | Ignition OFF for > 5 minutes |
| Idle | Ignition ON, speed = 0 for > 2 minutes |
Trip Metrics
Section titled “Trip Metrics”Each completed trip records:
- Start/end time and location
- Total distance (km)
- Maximum and average speed
- Idle time
- Number of GPS points
Alerts
Section titled “Alerts”Alert Types
Section titled “Alert Types”| Type | Description |
|---|---|
device_offline | Device hasn’t reported within threshold |
signal_low | Cellular signal below threshold |
geofence_enter | Device entered a geofenced zone |
geofence_exit | Device left a geofenced zone |
speeding | Speed exceeded configured limit |
firmware_outdated | Device running old firmware |
Alert Lifecycle
Section titled “Alert Lifecycle”Triggered → Pending → Acknowledged → Resolved- Pending — Alert fired, awaiting attention
- Acknowledged — Someone is looking at it
- Resolved — Issue fixed or condition cleared
Notification Channels
Section titled “Notification Channels”Alerts can be delivered via:
- Portal notification (in-app)
- Email (configurable recipients)
- Webhook (for integration with external systems)
Data Retention
Section titled “Data Retention”Telemetry data retention depends on your plan:
| Plan | Retention |
|---|---|
| Starter | 30 days |
| Pro | 90 days |
| Enterprise | 365 days |
After retention period:
- Raw telemetry is compressed then deleted
- Aggregated trip data is retained longer
- Device state snapshots are kept indefinitely