đ Afaqy Knowledge Base / AVL / Reports / Summary Reports
Summary reports provide an essential overview of operations either by unit or by driver, offering high-level analytics across defined time intervals. These reports are ideal for performance benchmarking, operational summaries, and executive-level insights.
Report Types
- Summary Report
- Summary by Driver
- Summary CAN BUS
- No Connections
- Last Update
1. Summary Report
Description
Provides a time-based overview of each unit's performance, highlighting operational metrics such as mileage, idle time, engine activity, and sensor readings if available. Additional configuration options enhance the relevance and readability of the report output.
Key Insights
- Mileage driven per day, week, or month
- Driving time vs. idle time analysis
- Mileage vs. Fuel consumption
- Number of trips and stops
- Speed profiles and maximum speed reached
- Total movement time and engine runtime comparison
Report Input
- Units
- Fields (Mileage, Idle time, Driving time, Trips, Max Speed, etc.)
- Summary by (Days, Weeks, Months)
- Report Duration
- Duration format (Days or Hours)
- Draw Track in PDF: Adds a visual route to the exported PDF if only one unit is selected (optional)
- Chart to HTML: Adds a visual chart (e.g., Mileage vs. Fuel consumption chart) to the exported HTML (optional)
Data Filters
- Min/Max Mileage: Focus on specific trip lengths.
- Time Limitation: Exclude specific periods. When enabled, this feature excludes specific timeframes from the report based on selected hours, weekdays, calendar days, and months.
- Define a time range (e.g., 09:00 to 16:00).
- Choose specific weekdays (e.g., Sunday).
- Include only certain days of the month, or use quick filters like Odd/Even.
- Select specific months of the year.
- Click on the Inverse button to treat the selected time ranges as excluded periods instead of included ones.
Users can:
Use Time Limitation to narrow report data to relevant operating hours or to exclude non-working periods.
- Hide Empty Records: Removes rows with no detected data or offline during the reporting period.
- Hide Summary Records: Hides summary totals of each selected unit in the Excel export for a more granular look.
- Mileage from Sensor: Calculates mileage using the installed 'Mileage' sensor instead of GPS if available.
How the report is calculated
- Mileage is taken from the mileage sensor (if available). If not, it is calculated using GPS coordinates (distance between track points).
- Idle time is derived from engine on + no motion.
- Movement time is computed from motion events.
- Trips and stops are calculated based on ignition and speed thresholds.
- Time is grouped based on the selected interval (daily/weekly/monthly).
Required Sensors
- GPS Module (mandatory)
- Odometer Sensor (optional, for enhanced mileage precision)
- Engine Status Sensor (optional, for working/idle time accuracy)
2. Summary by Driver
Description
Provides a breakdown of each driver's operational performance, independent of the vehicles utilized, with the aim of analyzing driving behaviors and managing individual workload levels.
Key Insights
- Total distance and time driven per driver
- Idle vs. active driving breakdown
- Driver workload and trip distribution
Data Filters
- Time Limitation
How the report is calculated
- Aggregates data based on driver-unit associations (manual or automated).
- Totals are computed per driver across all used units.
- Mileage uses sensor or GPS fallback depending on availability.
Report Input
- Drivers
- Fields (Driving Time, Idle Time, Trips, Stops, Fuel Efficiency, Engine Move Duration, etc.)
- Report Duration
- Duration format (Days or Hours)
- Summary By (Days, Weeks, Months)
Required Sensors
- GPS Module (mandatory)
- Driver ID Sensor (mandatory â via iButton or RFID)
- Odometer Sensor (optional)
3. No Connections
Description
Highlights units that failed to communicate with the server during a selected timeframe, helping identify communication issues.
Key Insights
- Units with prolonged disconnection
- Duration since last message
- Impacted geofences or locations
Data Filters
- Status (e.g., Offline, No Signal)
Report Input
- Units
- Geofences
- Fields (Last Update, Disconnection Duration, Location, etc.)
Required Sensor
- GPS Module (mandatory)
How the report is calculated
- Compares the last message timestamp against the current system time.
- Flags units that exceed the user-defined offline threshold.
4. Last Update
Description
Displays the timestamp of the most recent update received from each unit to track responsiveness and spot inactive devices.
Key Insights
- When each unit was last heard from
- Operational status at last check-in
- Location and motion state if available
Data Filters
- Status (e.g., Offline, No Signal)
How the report is calculated
- Pulls the most recent server entry per unit.
- Includes location and motion status from that message.
Report Input
- Units
- Geofences
- Fields (Last Update, Location, Total Weight, Temperature, Humidity, Driver, etc.)
Required Sensors
- GPS Module (mandatory)
No operational or telemetry sensors are required beyond base modules.
5. Summary CAN BUS
Description
Focused on vehicles equipped with CAN BUS integration. Provides highly accurate metrics derived from internal vehicle systems.
Key Insights
- Actual fuel consumption
- Engine RPM and temperature behavior
- Accurate odometer and engine hours from vehicle ECU
How the report is calculated
- All data is pulled directly from the CAN BUS interface.
- Raw binary values are converted using decoding algorithms specific to each vehicle model.
- Units without CAN will be excluded from calculations.
Cross-check reported mileage and fuel usage with the raw CAN logs to catch calibration issues early.
Report Input
- Units
- Fields (Route Length, Engine Work Duration, Fuel Consumption, etc.)
- Report Duration
- Duration format (Days or Hours)
Required Sensors
- CAN Bus Interface (mandatory; serves as the single source of truth for vehicle diagnostics and consumption data):
- Engine Hours: for calculating runtime and operational timelines
- Mileage: distance traveled directly from the ECU
- Actual Fuel Consumption: real-time fuel usage pulled from the CAN system
- Engine Status: to differentiate between active, idle, and off states
- Total Fuel: cumulative fuel monitoring used for consumption calculations
- RPM: engine revolutions per minute, useful for detecting idling patterns and mechanical stress
