1. Trips
2. Weights Trips
3. Battery Unplugged
4. Services
5. Over Speed
6. Stops
7. Stops Enhanced
8. Over Speed Enhanced
9. Idle

10. Trailer History
11. Dozer Report
12. Tampering Report
13. Fuel Theft Report
14. Engine Hours
15. Fuel Filling Report
16. Fuel Summary
17. Movement
18. Connection Loss

• Trip start and end locations/times
• Route length per trip
• Duration, idle vs. driving time

• Maximum speed during each trip
• Fuel usage per trip
• Count of trips made per unit

• Units
• Geofences (Optional)
• Fields (Start Time, Route Length, Duration, etc.)
• Report duration (e.g. for the previous 5 days; check Include Current to include today)

• Time Limitation: Exclude specific periods. When enabled, this feature excludes specific timeframes from the report based on selected hours, weekdays, calendar days, and months.

Users can:

1. Define a time range (e.g., 09:00 to 16:00).
2. Choose specific weekdays (e.g., Sunday).
3. Include only certain days of the month, or use quick filters like Odd/Even.
4. Select specific months of the year.
5. Click on the Inverse button to treat the selected time ranges as excluded periods instead of included ones.

Use Time Limitation to narrow report data to relevant operating hours or to exclude non-working periods.

• Duration Filters (Min/Max): Filter trips by duration.
• Mileage Filters (Min/Max): Focus on specific trip lengths.
• Speed Limitation (Min/Max): Focus on safe or risky trips.
• Hide Empty Records: Removes rows with no valid data or inactive units during the period.
• Hide Summary Records: Hides unit-level summary rows in Excel.

Sensor Requirements

To accurately generate this report, the following sensors must be configured:

• GPS Sensor (mandatory)
• Ignition Sensor (to detect start/end)
• Mileage Sensor (optional, prioritizes accuracy over GPS distance)
• CAN Bus Interface (recommended for fuel consumption and advanced diagnostics)

• Trip detection is based on the Accuracy tab in the unit profile (motion sensitivity, minimum trip time/distance, minimum park time, minimum speed).
• Trip Start

(This refers to the time when the unit starts moving within the selected report interval.)

1. GPS + ACC units:
• Speed exceeds the Minimum Speed threshold with ACC ON and ≥ 6 km/h, and
• The unit keeps moving for ≥ Minimum Trip Time (default: 60 s) or covers ≥ Minimum Trip Distance (default: 100 m).
2. GPS‑only units:
• Speed exceeds the Minimum Speed threshold, and
• The unit keeps moving for ≥ Minimum Trip Time (default: 60 s) or covers ≥ Minimum Trip Distance (default: 100 m).
• Trip End

(This refers to the time when the unit is considered to have stopped moving.)

1. GPS + ACC units:
• Speed falls below Minimum Speed (ACC ON or OFF), and
• The unit remains stationary for ≥ Minimum Park Time (default: 300 s).
2. GPS‑only units:
• Speed falls below Minimum Speed, and
• The unit remains stationary for ≥ Minimum Park Time (default: 300 s).

• No Movement
• Defined as speed below the Minimum Speed threshold (as configured in the unit profile).
• Trip Start = Ignition On + Movement
• Trip End = Motion stops or Ignition Off
• Route Length = GPS Distance (or Mileage Sensor if enabled)
• Idle Time = Engine On + Speed less than threshold
• Fuel Consumed = Calculated or retrieved from CAN
• Duration is calculated from trip start to end timestamps.
• Grouped by unit per selected interval

Key Insights

• Loading and unloading locations and times
• Duration and amount of material handled per event
• Route and trip durations during weighted operations
• Full cycle view of logistics workflows

Data Filters

• Driver: Filter operations based on assigned personnel(s) or driver group(s).
• Trailer: Filter by units with/without linked trailers.

How the report is calculated

• Weight = Delta from load/unload readings
• Duration = Time between load/unload triggers
• Loading and unloading points are determined based on changes in sensor values.
• Timestamps are calculated from the moment a change is detected until it ends.
• Load and unload amounts are recorded directly from the connected sensors.

Report Input

• Units
• Fields (Loading Location, Start Time, Duration, Amount, Unloading Location, etc.)
• Report duration (e.g. for the previous 3 months; check Include Current to include current month)

Sensor Requirements

To accurately generate this report, the following sensors must be configured:

• GPS Sensor (mandatory)
• Ignition Sensor (to detect start/end)
• Mileage Sensor (optional, prioritizes accuracy over GPS distance)
• CAN Bus Interface (recommended for fuel consumption and advanced diagnostics)

Key Insights

• Detection of battery disconnection periods
• Start and end timestamps and locations of unplug events
• Duration of each unplugged session
• Frequency of disconnection across the fleet

Data Filters

• Time Limitation: When enabled, this feature excludes specific timeframes from the report based on selected hours, weekdays, calendar days, and months.

Users can:

1. Define a time range (e.g., 09:00 to 16:00)
2. Choose specific weekdays (e.g., Sunday)
3. Include only certain days of the month, or use quick filters like Odd/Even
4. Select specific months of the year
5. Click on the Inverse button to treat the selected time ranges as excluded periods instead of included ones
• Duration Filters (Min/Max): Display only unplug events within a specific time threshold

Report Input

• Units
• Fields (Start Date, End Date, Start Location, End Location, Duration, Driver)
• Report duration (e.g. for the previous 1 week; choose from minutes, hours, days, weeks, or months via dropdown and check Include Current to include the current period)

Sensor Requirements

• Power Status Sensor (to detect battery disconnect)
• GPS Sensor (to log location)

How the report is calculated

• Battery unplug events are detected when the system receives a power disconnection signal from the vehicle’s main power line.
• Start timestamp and location are captured at the moment of disconnection.
• End timestamp and location are recorded upon reconnection.
• Duration is calculated from the time difference between unplug and restore events.
• Route length (if vehicle was moving during this time on the device battery) is calculated from the location difference between unplug and restore events.
• All events are grouped by vehicle and sorted by the selected report duration.

Key Insights

• List of configured service types (e.g., oil change, inspection)
• Status of each service (Active / Expired)
• Odometer or engine hour thresholds and actual values
• Service messages and grouping by category

How the report is calculated

• The system checks configured service schedules, which may be based on odometer readings, engine hours, or elapsed time.
• When the threshold value is reached or exceeded, the service is marked as "Expired"; otherwise, it remains "Active".
• Odometer and engine hour values are pulled from the latest readings at the time of report generation.
• Grouping and status presentation follow the configuration defined in the maintenance setup.
• Optional trailer and driver information is linked where available for traceability.

Report Input

• Units
• Fields (Service Name, Service Message, Service Status, Odometer, Engine Hours, Status)

Sensor Requirements

• Odometer Sensor
• Engine Hours Sensor
• CAN Bus Interface (required if pulling service triggers from ECU)

Data Filters

• Status
• Service Status (All, Active, Expired)
• Driver: Filter operations based on assigned personnel(s) or driver group(s)
• Trailer: Filter by units with/without linked trailers

Key Insights

• Frequency and duration of speeding events
• Start and end location of each violation
• Maximum speed reached per incident
• Duration of each violation
• Driver-level visibility into speed behavior

Data Filters

• Time Limitation: When enabled, this feature excludes specific timeframes from the report based on selected hours, weekdays, calendar days, and months.

Users can:

1. Define a time range (e.g., 09:00 to 16:00)
2. Choose specific weekdays (e.g., Sunday)
3. Include only certain days of the month, or use quick filters like Odd/Even
4. Select specific months of the year
5. Click on the Inverse button to treat the selected time ranges as excluded periods instead of included ones
• Duration Filters (Min/Max): Filter events by their duration
• Speed Filters (Max): Only include violations that exceed a defined max speed
• Mileage Filters (Min/Max): Narrow reports to incidents within a specific mileage range
• Driver: Filter operations based on assigned personnel(s) or driver group(s)
• Trailer: Filter by units with/without linked trailers
• Hide Summary Records: Hides the summary line for each selected resource in Excel exports

Report Input

• Units
• Geofences
• Fields (Start Time, Start/End Location, Max Speed, Duration, Route Length, Driver)
• Report duration (define custom intervals as needed)
• Speed Threshold: Define the maximum speed that constitutes a violation.

Sensor Requirements

• Speed Sensor / GPS
• Driver Assignment Module (optional)
• CAN Bus (preferred for accurate speed)

How the report is calculated

• A violation is recorded when the unit's speed exceeds the threshold set in its configuration.
• Start and end times are derived from the first moment the limit is exceeded until it returns below the threshold.
• Max speed is the highest recorded value within the violation.
• Duration reflects the time spent above the speed threshold.
• Each record is grouped by unit, with optional filters for driver and trailer if configured.

Key Insights

• Stop address and timing details
• Duration spent stopped, idling, or with engine off
• Personal points and unidentified stop durations
• Driver-based accountability for stop behavior

Data Filters

• Time Limitation: When enabled, this feature excludes specific timeframes from the report based on selected hours, weekdays, calendar days, and months.

Users can:

1. Define a time range (e.g., 09:00 to 16:00)
2. Choose specific weekdays (e.g., Sunday)
3. Include only certain days of the month, or use quick filters like Odd/Even
4. Select specific months of the year
5. Click on the Inverse button to treat the selected time ranges as excluded periods instead of included ones
• Duration Filters (Min/Max): Focus the report on stops above or below a certain threshold
• Driver: Filter stops based on assigned drivers or driver groups
• Trailer: Filter based on trailer linkage
• Hide Summary Records: Hides the summary line for each selected resource in Excel exports

Report Input

• Units
• Geofences
• Fields (Start Time, End Time, Address, Idle Duration, Driver)
• Report duration (e.g. for the previous 4 weeks; check Include Current to include current week)

Sensor Requirements

• GPS Sensor
• Ignition Sensor
• Motion Sensor
• CAN Bus (optional for RPM and engine state)

How the report is calculated

• A stop is detected when the unit has zero movement for a configured threshold (e.g., based on ignition state and motion sensor).
• Idle time is tracked when the engine is on, but the vehicle is stationary.
• Engine-off duration reflects time the unit is stopped with ignition off.
• Personal points and Duration N/A are system-detected annotations based on location tagging or data inconsistencies.
• Each record is grouped per unit and segmented within the selected interval.

Key Insights

• Complete stop details: address, timing, and duration
• Breakdown of idle and engine-off durations
• Weight data before and after the stop (if available)
• Trailer linkage and group classification
• Driver responsibility for extended or frequent stops

Data Filters

• Time Limitation: When enabled, this feature excludes specific timeframes from the report based on selected hours, weekdays, calendar days, and months.

Users can:

1. Define a time range (e.g., 09:00 to 16:00)
2. Choose specific weekdays (e.g., Sunday)
3. Include only certain days of the month, or use quick filters like Odd/Even
4. Select specific months of the year
5. Click on the Inverse button to treat the selected time ranges as excluded periods instead of included ones
• Duration Filters (Min/Max): Filter based on stop duration
• Driver: Filter stop events by assigned driver(s) or driver group(s)
• Trailer: Filter stop events by trailer linkage
• Hide Empty Records: Removes rows with no detected data or offline status during the selected timeframe
• Hide Summary Records: Hides the summary totals of each selected resource in Excel exports

Report Input

• Units
• Geofences
• Fields (Start Time, End Time, Address, Idle Duration, Start/End Weight, Driver, Trailer)
• Report duration (e.g. from 2025-07-29 00:00:00 to 2025-07-29 18:13:28 or define custom intervals as needed)

Sensor Requirements

• All sensors in Stops Report
• Weight Sensor (Start/End Weight)
• Trailer Linkage Detection Sensor

How the report is calculated

• Stops are recorded when the unit registers zero motion for a duration exceeding the unit-configured threshold.
• Trailer associations are pulled from system linkage logs.
• Idle time is calculated when the engine is on but the vehicle remains stationary.
• Engine-off duration is the time the unit remains stopped with ignition off.
• Weight fields (Start Weight, End Weight) are pulled from the associated sensors.
• Personal point stops and N/A durations are derived from location tags or data inconsistencies.
• Each record is grouped by unit and segmented according to the defined report interval.

Key Insights

• Start and end times of each over-speeding event
• Maximum speed and duration of speeding
• Route and location of the incident
• Driver involved and unit-specific patterns

Data Filters

• Time Limitation: When enabled, this feature excludes specific timeframes from the report based on selected hours, weekdays, calendar days, and months.

Users can:

1. Define a time range (e.g., 09:00 to 16:00)
2. Choose specific weekdays (e.g., Sunday)
3. Include only certain days of the month, or use quick filters like Odd/Even
4. Select specific months of the year
5. Click on the Inverse button to treat the selected time ranges as excluded periods instead of included ones
• Duration Filters (Min/Max): Focus on speeding events that lasted longer or shorter than expected
• Speed Filters (Max): Identify violations of defined speed thresholds
• Mileage Filters (Min/Max): Restrict to specific trip lengths where speeding occurred
• Driver: Filter events based on specific drivers or groups
• Trailer: Filter incidents by trailer association
• Hide Empty Records: Removes rows with no detected data or offline status during the selected timeframe
• Hide Summary Records: Hides the summary totals of each selected resource in Excel exports

Report Input

• Units
• Geofences
• Fields (Start Time, Max Speed, Route Length, Driver, etc.)
• Report duration (e.g. from 2025-07-29 00:00:00 to 2025-07-29 18:51:15 or define custom intervals as needed)

Sensor Requirements

• Same as Over Speed Report
• Trailer Linkage Sensor
• Driver Assignment (iButton or Manual)

How the report is calculated

• Over-speeding is determined when a vehicle's speed exceeds the threshold configured in the system.
• Each event logs the timestamp, location, duration, and top speed.
• Duration is calculated between the start and end of the over-speed condition.
• Max speed is pulled from sensor readings during the violation.
• Route length is calculated based on the segment in which the violation occurred.
• Driver and trailer linkage (if available) are included for detailed tracking.
• Records are grouped by unit and time interval.

Key Insights

• Start and end times of each idling period
• Location and address of idling events
• Total idle duration per vehicle
• Personal or system-marked idling points

Data Filters

• Time Limitation: When enabled, this feature excludes specific timeframes from the report based on selected hours, weekdays, calendar days, and months.

Users can:

1. Define a time range (e.g., 09:00 to 16:00)
2. Choose specific weekdays (e.g., Sunday)
3. Include only certain days of the month, or use quick filters like Odd/Even
4. Select specific months of the year
5. Click on the Inverse button to treat the selected time ranges as excluded periods instead of included ones
• Duration Filters (Min/Max): Highlight excessively short or long idle events
• Driver: Filter idle events by driver or driver group
• Trailer: Filter idle events by trailer usage
• Event Status: Filter idle events based on system-recognized status

Report Input

• Units
• Fields (Idle Location, Duration, Driver, Personal Point, etc.)
• Duration format (Days or Hours)
• Report duration (e.g. from 2025-07-29 00:00:00 to 2025-07-29 21:27:09 or define custom intervals as needed)

Sensor Requirements

• Ignition Sensor
• GPS Sensor
• Motion Sensor
• CAN Bus (optional, for RPM confirmation)

How the report is calculated

• An idle event is logged when the ignition is on, but the vehicle remains stationary for a defined period.
• Start and end timestamps are taken from the system’s movement detection algorithm.
• Address is generated based on the GPS location of idling.
• Duration is calculated from the first detected idle moment to movement resumption.
• Driver assignment is pulled from system configuration.
• Events may be marked as personal points for manual tagging and analysis.

Key Insights

• Start and end times of trailer connections
• RFID and iButton records for trailer authentication
• Historical linkage records across vehicles
• Monitoring of trailer swap frequency and duration

How the report is calculated

• Trailer connection is logged when the system detects a change in trailer status based on RFID, iButton, or system settings.
• Start Time = moment of connection
• End Time = moment of disconnection
• iButton and RFID fields are captured when available to validate the trailer-user association.
• Records are grouped by vehicle and trailer combination for reporting clarity.

Report Input

• Units
• Fields (Trailer, iButton, RFID, Start Date, End Date)
• Report duration (e.g. from 2025-07-30 00:00:00 to 2025-07-30 20:26:14 or define custom intervals as needed)

Sensor Requirements

• Trailer ID via iButton / RFID (mandatory)
• Connection Detection Sensor (wired or wireless)
• CAN Bus Interface (optional, if trailer data is available)

Key Insights

• Start and end times of engine activity
• Start and end times of dozer operations
• Engine vs. operation duration comparison
• Utilization percentage and operational workload
• Trip level identifiers for tracking sessions

How the report is calculated

• Engine Start/End are captured when the engine is turned on and off.
• Engine Duration = Engine End – Engine Start
• Operation Duration = Dozer Operation End – Operation Start
• Utilization % = (Operation Duration / Engine Duration) × 100
• Operation Start/End mark the beginning and end of physical operation activity.

Report Input

• Units
• Fields (Engine Start/End Date, Operation Start/End Date, Engine Duration, Operation Duration, Utilization, Trip Level, Location)
• Report duration (e.g. from 2025-07-15 00:00:00 to 2025-07-30 21:01:37 or define custom intervals as needed)

Sensor Requirements

• Engine Signal Sensor
• Dozer Operation Sensor (plow/blade activation)
• CAN Bus Interface (recommended for precise engine data)

Key Insights

• Start time of suspected tampering event
• Location where the tampering was detected
• Speed reading during the incident
• Involved driver name if applicable

How the report is calculated

• Triggered by patterns like signal jamming, repeated GPS errors, or sudden disconnection.
• Start Time is recorded at the onset of detected tampering behavior.
• Location is logged using GPS coordinates at the time of the event.
• Speed is registered from the vehicle at the moment of tampering.
• Driver Name is included if driver assignment was active during the event.

Report Input

• Units
• Fields (Start Time, Start Location, Speed, Driver Name)
• Report duration (e.g. from 2025-05-10 00:10:00 to 2025-07-30 22:36:40 or define custom intervals as needed)

Sensor Requirements

• GPS Module (mandatory to detect signal loss or distortion)
• Device Connectivity Status Sensor
• Ignition Sensor (optional to contextualize tampering)

Key Insights

• Time and address of the suspected theft
• Fuel levels before and after the incident
• Total fuel volume suspected to be stolen
• Assigned driver during the incident

Data Filters

• Theft Rate Volume (Liters): Threshold volume change to consider theft
• Theft Rate Time (Minutes): Duration threshold for the drop to be valid
• Hide Empty Records: Removes records where no fuel theft was detected

How the report is calculated

• Theft Volume = Fuel Level Before – Fuel Level After
• Fuel theft detection is triggered when a rapid decrease in fuel level is observed within a short duration, surpassing configured volume and time thresholds, or if the vehicle is operating below the minimum speed limit.
• Start Time and End Time are derived from when the fuel drop starts and stabilizes.
• Driver Name is displayed if assigned to the unit at the time of the theft.
• Zones and addresses are identified based on GPS location at the theft time.

Report Input

• Units
• Drivers
• Fields (Start Time, End Time, Zone, Address, Fuel Level Before, Fuel Level After, Theft Volume, Driver Name)
• Report duration (e.g. from 2025-01-00 00:00:00 to 2025-07-30 22:47:55 or define custom intervals as needed)
• Consumption Rate (configured in the Unit’s profile) is not required, as it does not factor into fuel theft detection logic.
• Theft Rate: Set a threshold rate in liters per minute to flag potential theft cases (suggested theft rate: 5 liters in 7 minutes)

Sensor Requirements

• Fuel Level Sensor (mandatory; CAN Bus recommended)
• CAN Bus Interface (required for accurate real-time fuel readings)
• GPS Sensor (to pinpoint location of theft)

Key Insights

• Engine start and end times and locations
• Total duration of engine activity
• Time spent moving vs. idling vs. stopped
• Inefficiencies due to idle time or unnecessary engine usage
• Route length and max speed per entry
• Initial and final odometer readings

Data Filters

• Time Limitation: When enabled, this feature excludes specific timeframes from the report based on selected hours, weekdays, calendar days, and months.

Users can:

1. Define a time range (e.g., 09:00 to 16:00)
2. Choose specific weekdays (e.g., Monday & Friday)
3. Include only certain days of the month, or use quick filters like Odd/Even
4. Select specific months of the year
5. Click on the Inverse button to treat the selected time ranges as excluded periods instead of included ones
• Duration Filters (Min/Max): Focus on long or short engine sessions
• Mileage Filters (Min/Max): Focus on movement vs. idle sessions
• Driver / Trailer Filters: Filter data by assigned driver or trailer
• Hide Empty Records: Removes rows with no engine activity during the selected period
• Hide Summary Records: Hides summary totals per vehicle in Excel output

Report Input

• Units
• Geofences
• Fields (Start Time, Engine Work Duration, Engine Move Duration, Driver Name, etc.)
• Duration format (Days or Hours)
• Report duration (e.g. from 2025-04-31 00:00:00 to 2025-07-31 01:16:53 or define a custom interval)
• Chart to HTML: Adds a visual chart (e.g., Mileage vs. Fuel consumption chart) to the exported HTML (optional)

Sensor Requirements

• Ignition Sensor (mandatory to determine engine state)
• Motion Sensor / GPS (to classify idle vs. moving)
• Odometer Sensor (optional, for movement distance)
• CAN Bus Interface (recommended for precision)

How the report is calculated

• Engine Work Duration = Engine End Time – Engine Start Time
• Idle Duration = Engine On + No Motion
• Move Duration = Engine On + Motion
• Route Length = Distance between GPS points or via Odometer

Key Insights

• Refueling start and end timestamps
• Fueling location and associated zone
• Fuel levels before and after the event
• Duration and total volume of each filling session
• Filling rate per unit of time

Data Filters

• Volume (Liters): Define a threshold to classify significant fuel filling events
• Time (Minutes): Minimum duration to consider a valid filling operation
• Hide Empty Records: Optionally exclude records with no filling data

How the report is calculated

• Fuel Filling Duration = End Filling Time – Start Filling Time
• Fuel Filling Volume = Fuel Level After – Fuel Level Before
• Filling Rate = Fuel Filling Volume / Fuel Filling Duration (in minutes)
• Fuel Filling Cost = Fuel Filling Volume × Fuel Price (if price field is enabled)
• Fuel Efficiency = (optional, if odometer available): Distance Covered / Fuel Used

Report Input

• Units
• Drivers
• Fields (Driver Name, Zone, Address, Start/End Filling Time, Fuel Filling Duration, Fuel Type, Fuel Level Before/After, Fuel Filling Volume, Fuel Price, Fuel Cost)
• Report duration (e.g., from 2025-02-31 00:00:00 to 2025-07-31 03:29:53 or custom intervals)
• Filling Rate Filters (Required):
• Volume (Liters)
• Time (Minutes)
• Recommended filling rate threshold: 5 liters within 7 minutes (used to help distinguish legitimate refueling from potential anomalies)

Sensor Requirements

To accurately generate this report, the following sensors must be configured:

• Fuel Level Sensor (mandatory; CAN Bus recommended for accuracy)
• Fuel Price Input (if cost analysis is required; mainly retrieved via CAN Bus)
• Optional Sensors:
• Odometer Sensor (for fuel efficiency calculation)
• CAN Bus Interface (recommended for all fuel-related values to ensure precision and real-time updates)

Key Insights

• Actual vs. target consumption rates
• Fuel used and filled over time
• Total fuel volume and cost indicators
• Consumption difference per driver or vehicle
• Summary view by day, week, or month

How the report is calculated

• Actual Consumption (Liters/100 KM) = (Fuel Used × 100) / Distance Covered
• Actual Consumption Ratio (KM/Liter) = Distance Covered / Actual Fuel Consumed (Liters)
• Difference in Consumption = Target Consumption Ratio – Actual Consumption Ratio
• Target Total Liters = Distance × Target Consumption Ratio (converted to liters)
• Actual Total Liters = Total Fuel (CAN) at end signal – Total Fuel (CAN) at first signal
• Difference (Total Liters) = Actual Total Liters – Target Total Liters
• Distance may be calculated via GPS or sensor depending on configuration.

Report Input

• Units
• Fields (Final Fuel Level, Fuel Filling Volume, Mileage, Actual/Target Consumption Ratio, Actual/Target Total Liters, Driver)
• Report duration (e.g., from 2025-05-01 00:00:00 to 2025-08-01 04:42:08 or define custom intervals)
• Summary By: Choose whether to group data by Days, Weeks, or Months
• Mileage Source: Toggle Mileage from sensor if you want to calculate distance using mileage sensor readings instead of GPS.

Sensor Requirements

To ensure accurate reporting, the following sensors are required:

• Fuel Level Sensor (mandatory)
• Mileage Sensor (optional but recommended for high-precision consumption figures)
• CAN Bus Interface (required to fetch actual fuel consumption and odometer readings)

Key Insights

• Movement start and end times and locations
• Duration of movement
• Distance covered and max speed
• Movement type classification (e.g., Idle, Stop, Move, Engine Off)

Data Filters

• Time Limitation: Exclude or include results based on defined weekdays, hours, calendar days, or months
• Duration Filters (Min/Max): Focus on movements that fall within a certain duration range
• Mileage Filters (Min/Max): Filter based on distance traveled
• Speed Limitation (Min/Max): Report movements based on minimum or maximum speed
• Driver: Filter events by driver or driver group
• Trailer: Filter events based on trailer linkage
• Vehicle Status Type: Select one or more movement states: Idle, Stop, Move, Engine Off
• Hide Empty Records: Removes rows with no valid data or inactive units during the period.
• Hide Summary Records: Hides unit-level summary rows in Excel.

Report Input

• Units
• Geofences (optional, for segmenting by zones)
• Fields (Type, Duration, Route Length, Start/End Time and Location, Max Speed, and Average Speed)
• Report duration (e.g., from 2025-03-01 00:00:00 to 2025-09-01 05:06:51 or define custom intervals)

Sensor Requirements

To ensure accurate reporting, the following sensors are recommended:

• GPS Module (mandatory for tracking movement and calculating distance)
• Speed Sensor (optional if CAN bus is unavailable)
• CAN Bus Interface (optional, enhances speed and distance accuracy when integrated)

How the report is calculated

• Movement segments are identified based on GPS data and the unit's vehicle status
• Start and end times are defined by status transitions (e.g., from idle to moving)
• Distance is calculated using GPS tracking
• Max speed is the highest speed recorded during the movement
• Movement type (e.g., Move, Stop, Idle) is determined by internal system classification per time interval

Key Insights

• Start and end times of each disconnection
• Location of disconnection and reconnection
• Total offline duration
• Connection status classification

Data Filters

• Time Limitation: Refine the report to specific hours, days, or months
• Duration Filters (Min/Max): Focus on losses longer or shorter than defined thresholds
• Driver: Filter records by driver or group (if linked)
• Trailer: Filter records based on trailer attachment

How the report is calculated

• A connection loss event is recorded when the platform receives no signal from the unit for a duration exceeding the configured offline threshold
• Start time and location are captured from the last known point before loss
• End time and location are captured upon reconnection
• Duration is calculated as the difference between loss and recovery
• Connection status events are included to help interpret anomalies:
• Disconnected: Indicates a deliberate or system-triggered shutdown of the tracking device (e.g., manual power-off, device removal).
• Connection Loss: Refers to an unexpected interruption in communication, typically due to poor signal, network issues, or hardware malfunction.
• Records are grouped by unit and optionally filtered based on context.

Report Input

• Units
• Fields (Start Time, End Time, Start/End Location, Duration, Connection Status)
• Report duration (e.g., from 2025-01-01 00:00:00 to 2025-08-03 00:46:15 or define custom intervals)
• Maximum Allowed Offline Duration (e.g., 60 minutes) — this defines what qualifies as a “connection loss”

Sensor Requirements

To track connection losses, the following are required:

• Tracking Device with Cellular/GSM Module (mandatory)
• Stable GPS Module (optional, enhances location tracking before/after loss)
• CAN Bus or digital input for ignition state (optional, for verifying whether disconnection is linked to ignition off)