TripsAnalyzer
Main analyzer
Central console: rides chart, per-vehicle stats, idle vs driving time breakdown.
The trip analytics engine: automatic ride detection, visited sites, routes traveled, driver scoring.
15 IRequest controllers, each exposing one atomic server-side function.
Central console: rides chart, per-vehicle stats, idle vs driving time breakdown.
Define points of interest (depots, customers, stations). Auto-arrival detection via geofence.
Classification (depot, customer, station, garage, no-go). Behavior per type.
Standard itineraries (Douala-Yaoundé, Yaoundé-Bafoussam). Actual vs expected comparison.
Automatic detection of most-traveled routes through GPS clustering. Suggests optimal itineraries.
Split routes into segments (toll, urban, highway) with per-section stats.
Top destinations per vehicle/driver. Heatmap of frequently visited points.
Administrative breakdown (region, department, city) for reporting.
Forecast planning (planned departure/arrival) vs actual auto-detection.
Mark weekends, holidays and non-working days. Excluded from stats.
Create virtual fleets (tankers, executive cars, etc.) for reporting.
Customizable time slicing for reporting (day, week, fiscal month).
Retroactive ride recomputation over a given period (useful after adding a site).
API endpoint: hierarchical site structure for external widgets.
API endpoint: vehicles + groups structure for BI integrations.
The TripsAnalyzer plugin exposes its functions through the /Helper servlet. Each controller is called over HTTP using the pattern:
/Helper?package=tripsanalyzer&plug=<Controller>&task=<action>Responses follow the ExtJS-compatible JSON format:
{
"success": true,
"total": 42,
"rows": [...]
}| Java package | com.malambi.fleetman.plug.tripsanalyzer |
| Controllers | 15 |
| URL pattern | /Helper?package=tripsanalyzer |
| Multi-tenant | yes (userid scope) |
| Audit logs | enabled |
| FleetMan version | 7.0.1+ |
The plugin ships standard with FleetMan. Activation is instant — contact your account manager or start a free trial.