Afaqy Knowledge Base

1. Introduction

This page introduces Afaqy's AVL system, outlining its purpose in real-time asset tracking and fleet management. It highlights key features such as GPS integration, sensor connectivity, and industry use cases. It also gives background on Afaqy’s history, technical expertise, and the scalability of the AVL Pro platform across multiple sectors.

A. Technical Requirements

Here, users are guided through the minimum system specifications and supported browsers needed to run AVL Pro smoothly. It includes hardware and internet prerequisites, ensuring optimal system performance and compatibility for both individual and enterprise deployments.

B. Quick Start

This guide helps new users get started quickly with the AVL system. It covers how to log in, reset passwords, and navigate the interface, and includes a glossary of key terms like Unit, Sensor, and Geofence—making it a perfect orientation for first-time users.

C. Map

This section explains the AVL map interface and its interactive tools. It walks users through navigating the map, switching between views (like satellite or road maps), interpreting motion states via unit icons, and using map utilities such as measuring distance or setting routes.

2. Monitoring

The Monitoring page details how users can observe the live status of their fleet. It covers real-time data on unit movement, engine status, location, and driver behavior, allowing users to take immediate action based on current operational insights.

3. Dashboard

The Dashboard provides a centralized, high-level view of fleet performance and system activity. It aggregates key metrics, visual analytics, and operational summaries into configurable widgets that help users monitor trends, exceptions, and overall fleet health at a glance.

A. Statistics

This section presents numerical KPIs related to units, statuses, and activities. Users can filter, segment, and export statistical data to support operational analysis and reporting needs.

B. Charts

Charts transform raw data into visual insights. This section explains available chart types, how to create custom charts, and how to interact with chart tools for trend analysis and decision-making.

C. Geofences

This dashboard-focused geofencing view summarizes zone activity and unit presence. It explains how geofences are displayed, how unit counts are calculated, and how users can act on geofence-related insights.

4. Reports

The Reports section enables historical analysis and compliance reporting. It allows users to generate, schedule, and export structured reports based on fleet activity, performance, and events over selected time ranges.

A. Summary Reports

The Summary Reports section provides high-level overviews of unit performance over time, including metrics like mileage, idle time, driving duration, and fuel consumption. These reports help users evaluate operational efficiency, compare activity across periods, and quickly identify performance trends.

B. Vehicle Activity Reports

This section dives deeper into detailed vehicle-level activity. It covers reports such as trips, stops, idle periods, engine on/off states, and distance traveled. These reports are essential for understanding how each vehicle is utilized throughout the day and for validating operational timelines.

C. Driving Quality Reports

Driving Quality Reports focus on driver behavior and safety metrics. They include events like harsh braking, rapid acceleration, sharp turns, and overspeeding. These insights support driver performance evaluation, safety improvement programs, and compliance with internal or regulatory driving standards.

D. Zones Activity Reports

This section highlights how units interact with predefined geofenced zones. Reports show entries, exits, dwell time, and visit frequency per zone, enabling users to analyze site visits, depot utilization, service coverage, and adherence to planned routes.

E. Sensors Activity Reports

Sensor Activity Reports provide visibility into connected sensor data such as fuel levels, temperature, door status, or other IoT inputs. These reports help monitor asset conditions, detect anomalies, and support preventive maintenance and loss prevention use cases.

F. Other Reports

The Other Reports category includes specialized or auxiliary reports that don’t fall under standard activity or behavior classifications. These may support niche operational needs, custom analytics, or legacy workflows depending on the deployment configuration.

G. Deprecated Reports

This section lists older reports that are no longer actively maintained. While still accessible for reference or backward compatibility, users are encouraged to transition to newer report alternatives for improved accuracy, performance, and feature support.

5. Units

This section explains how tracked assets (units) are managed within the system. It covers unit creation, configuration, sensors, commands, and common operational questions.

A. Units Management

Units Management focuses on organizing and administering large fleets. It includes importing units, grouping, sharing, exporting data, and safely deleting units when required.

6. Messages

This section details how raw device messages are accessed and analyzed. It helps advanced users and support teams trace communications, inspect payloads, and troubleshoot device-level issues.

7. Second By Second

Second By Second provides high-resolution tracking data for detailed investigations. It explains when and how to use second-level logs, their limitations, and how to analyze movement precisely over short intervals.

8. Tracking

This section explains how to generate and analyze historical tracks for individual units. It covers tracking fields, replaying routes, and using tracking tools to understand movement patterns and behavior.

9. Multi-Unit Follow

Multi-Unit Follow allows users to monitor multiple units simultaneously on a single map. It is designed for live operations where situational awareness across several assets is required.

10. Users

This section explains how user accounts are created, managed, and governed. It covers roles, permissions, visibility rules, and auditing to ensure secure and controlled system access.

11. Geofences

This area focuses on creating and managing geographic zones and markers. It explains how geofences are structured, grouped, imported, and exported for operational and alerting purposes.

A. Geofences Management

Geofences Management focuses on the administration and lifecycle of geographic zones beyond dashboard visualization. It enables structured control over large numbers of geofences used for operations, alerts, and reporting.

12. Customers

The Customer's section is used to manage client entities within multi-tenant environments. It covers customer creation, data organization, and administrative management.

13. Resources

Resources define shared reference data used across the system. This includes drivers, trailers, events, statuses, administrative divisions, and custom fields that standardize operations.

A. Trailers

This page manages trailer entities that can be linked to units for extended asset tracking. It allows users to create, assign, and maintain trailer records to support logistics, utilization tracking, and reporting accuracy.

B. Drivers

The Drivers page centralizes driver profiles used across tracking, reports, and events. It supports associating drivers with units, enabling driver-based analytics, accountability, and operational visibility.

C. Events

This section defines system and device-generated events such as speeding, ignition changes, or geofence violations. Events serve as the foundation for alerts, reporting, and behavioral analysis.

D. Status

The Status page manages standardized operational states for units and assets. These statuses are used consistently across monitoring, reports, and dashboards to reflect real-time and historical conditions.

E. Administrative Division

This page structures geographic or organizational hierarchies such as regions, cities, or branches. Administrative divisions enable better filtering, segmentation, and reporting across large deployments.

F. Custom Fields

Custom Fields allow organizations to extend the data model with additional attributes. These fields can be attached to units, drivers, or other resources to capture business-specific metadata without system customization.

14. Settings

The Settings section centralizes system-level configuration that governs device behavior, feature availability, and access control. Changes made here affect how AVL Pro operates across the tenant and should typically be handled by administrators.

A. Protocols

This page defines the communication protocols used between tracking devices and the AVL platform. It allows administrators to manage supported protocol types, ensure device compatibility, and maintain reliable data ingestion across different hardware models.

B. Packages

The Packages page controls feature entitlements and service limits assigned to units or customers. It enables administrators to configure what functionality is available per package, supporting commercial plans, scalability, and controlled feature rollout.

C. Roles & Permissions

This section manages user roles and fine-grained access permissions across the system. It defines what actions users can perform and which data they can access, ensuring secure operation, segregation of duties, and compliance with internal governance policies.

15. Audit Log

The Audit Log provides a complete, immutable record of user and system actions. It supports security, compliance, and forensic analysis by detailing events, access controls, exports, and retention policies.