FleetMonitoring Platform Features

 

Your Own GPS Tracking Server and Management Platform

FleetMonitoring is a server-based GPS tracking and telematics platform being developed for businesses that want to run their own tracking service or monitor their vehicles within their own infrastructure.

The platform brings together device communication, data storage, mapping, reporting and administration tools. Integration is focused exclusively on Teltonika trackers.

The sections below describe the platform’s intended scope. Features included in a deployment are defined in the proposal and depend on the installed modules, server configuration and connected devices.

 

Platform Architecture

A FleetMonitoring deployment brings together four main components.

Component Purpose
Device communication server Receives and processes data from compatible Teltonika trackers
Database Stores vehicle positions, events and telemetry records
User panel Provides access to maps, journey history and reports
Administration panel Provides tools for managing accounts, users, vehicles and permissions

Trackers must be configured to communicate with the server. Mobile connectivity, mapping, address lookup and messaging services are separate parts of the deployment and may involve third-party providers.

 

Customer Accounts and Fleet Administration

Manage Multiple Customers

For GPS tracking providers, account management is central to operating the service.

The administration tools are intended to support creating customer accounts, assigning devices and vehicles, adding users and controlling access to fleet information.

Customers access the vehicles assigned to their accounts, while the system administrator manages the wider platform.

 

Organise Your Own Fleet

A deployment can also serve a single organisation. Vehicle groups help organise different branches, departments or operational teams.

User permissions determine which vehicles and functions each member of staff can access.

 

Administration Tools

The platform’s administration scope includes:

  • Customer account creation and management.
  • User accounts and password management.
  • Tracker and vehicle assignment.
  • Vehicle groups and fleet organisation.
  • Geofence management.
  • Access controls and user roles.
  • Configurable event descriptions.
  • System information and device identification tools.

Advanced administration features depend on the modules included in the deployment.

 

Vehicle Maps and Location Information

Map views provide access to the latest received vehicle positions and recorded events.

The mapping scope includes:

  • Individual vehicle and fleet views.
  • Selected vehicle groups.
  • Automatic position refresh.
  • Vehicle names and configurable markers.
  • Direction-of-travel indicators.
  • Position details, including time, coordinates and speed.
  • Date and time range selection.
  • Geofence display.

A displayed position represents the latest location received by the server. Its age depends on the tracker’s reporting settings and connectivity.

Mapping providers and available map layers depend on the integrations configured for the deployment.

 

Journey History and Route Playback

Recorded positions allow users to review where a vehicle travelled during a selected period.

Journey history can help verify routes, identify stops and investigate unexpected vehicle activity. Route playback provides a way to follow recorded movements in sequence.

The available detail depends on how frequently the tracker records and transmits positions.

Distance may be calculated from GPS points or obtained from supported vehicle data. These measurements can differ because they use different methods.

 

Geofences and Site Visits

Geofences define areas such as depots, customer premises, warehouses or construction sites.

The platform’s scope includes circular and polygon geofences, with names and colours to distinguish locations on the map.

Geofence analysis can identify:

  • Arrival and departure times.
  • Time spent within an area.
  • Repeated visits to a location.
  • Travel time between defined areas.

Arrival and departure events may be calculated by the server from received GPS positions. Detection accuracy depends on position quality and reporting intervals.

 

Reports and Data Export

Reports organise vehicle and fleet records into information that users can review and share.

Vehicle Activity Reports

The reporting scope includes:

  • Detailed event history.
  • Journey start and end times and locations.
  • Driving and stopped time.
  • Distance travelled.
  • Events exceeding a configured speed threshold.
  • Last known vehicle locations.

Geofence Reports

Additional reports can show arrivals, departures, time within geofences and journeys between defined locations.

Equipment-Dependent Reports

With compatible equipment and server-side processing, reporting can be extended to include:

  • Ignition activity.
  • Digital input changes.
  • Temperature measurements and graphs.
  • Fuel level and consumption.
  • Engine operating time and idling.
  • Diagnostic information and fault codes.
  • Maintenance information.

Ignition-on time does not necessarily represent engine running time. Report interpretation depends on the signal being recorded.

Fleet and Administration Reports

Extended reporting may include grouped vehicle activity, driver-related records, user login audits, account login information, communication statistics and devices contacting the server without an account assignment.

 

Output Formats

Depending on the installed modules, reports may be viewed in the browser, sorted by column, exported as CSV, XML or XLS, and delivered by email.

KML support can provide vehicle event data for use in compatible geographic applications.

 

Event Rules and Notifications

The notification module evaluates incoming events against configured conditions.

Its intended scope includes rules for:

  • Exceeding a defined speed threshold.
  • Entering or leaving a geofence.
  • Ignition state changes.
  • Digital input activation.
  • Alarm button events.
  • Sensor readings outside configured limits.
  • Selected device event codes.

An extended rules module can add browser-based rule management, notification queues, callbacks to other applications and map markers selected by event type.

Further options may include maintenance alerts, diagnostic alerts and route corridor monitoring.

Email notifications require a configured mail service. SMS delivery requires a compatible gateway or another implemented messaging service.

Alerts based on a road’s posted speed limit require suitable road-speed data and a corresponding integration.

 

CAN Bus and Vehicle Telemetry

Compatible Teltonika equipment can extend GPS tracking with data obtained from the vehicle.

Depending on the vehicle and installation, available parameters may include:

  • Vehicle odometer.
  • Engine speed.
  • Fuel level.
  • Total fuel used.
  • Engine operating hours.
  • Selected diagnostic information.

CAN or J1939 integration requires compatible hardware, the correct connection and support for the relevant data fields on the server.

Connecting a tracker to an OBD socket does not automatically provide access to all vehicle parameters.

 

Temperature, Inputs and Driver Identification

 

Temperature Monitoring

Compatible sensors can provide temperature records for applications such as refrigerated transport.

The deployment may include measurement history, graphs and threshold-based notifications.

Digital and Analogue Inputs

Supported inputs allow the tracker to record signals from connected equipment.

The meaning of each input depends on the installation. Both the tracker configuration and server processing must match the intended use.

RFID and iButton Identification

Compatible RFID or iButton accessories can provide identification records.

Associating these identifiers with drivers and journeys requires configuration and appropriate reporting. Receiving an identifier alone does not provide a complete driver management function.

 

Teltonika Device Integration

FleetMonitoring development is focused exclusively on Teltonika devices.

The communication server receives packets, interprets supported records, associates them with the correct tracker and sends acknowledgements where required by the protocol.

Device Compatibility

Compatibility is checked for each deployment based on the exact Teltonika model, firmware version, communication protocol and required data fields. Send us your device list so we can confirm the supported functions before installation.

Integration Capabilities

Depending on the device and implemented server integration, supported functions may include:

  • TCP/UDP data reception.
  • Digital and analogue input data.
  • CAN bus data fields.
  • RFID/iButton identifiers.
  • Multiple recorded events within a data packet.
  • Acceleration and temperature data.
  • Server-generated geofence arrival and departure events.
  • Events derived from input states.
  • Estimated distance calculation.
  • SMS commands through a configured SMS gateway.

The available functions are confirmed individually for each deployment.

Remote Commands

Remote command support depends on the tracker, its firmware, the communication channel and the server integration.

SMS commands require a suitable messaging service. Commands over a data connection require corresponding support on both the device and server.

Functions such as starter enable/disable also require appropriate installation and hardware. They are not included automatically with basic GPS tracking.

Additional Modules and Integrations

The platform can be extended for specific operational requirements.

Area Potential extension
Route corridors Detect deviations from a defined route corridor or prolonged stops
Geographic boundaries Record boundary crossings and distance within defined areas
Trailers Detect attachment and detachment using suitable hardware
Vehicle maintenance Reports and alerts based on supported maintenance criteria
External applications Exchange positions, events, reports or telemetry through implemented interfaces
Branding Adjust supported interface elements to the operator’s identity

Geographic boundary analysis requires suitable boundary data. Each hardware-dependent extension requires compatibility checks and server-side implementation.

 

Server Deployment and Operation

Deployment planning covers the application, database and device communication services.

Depending on the agreed scope, configuration can include HTTPS access, service startup after a restart, scheduled tasks, administrative tools and external service connections.

The operating system, server requirements, backup arrangements and data retention policy are defined for the intended installation.

Managing your own platform also involves maintaining the server environment, database and connected services. Responsibility for these tasks should be specified in the deployment and support agreement.

 

How Deployment Works

Whether you want to monitor your own fleet or offer GPS tracking to your customers, here’s how we get your FleetMonitoring platform up and running.

1. Tell us what you need

Use the form below to tell us whether you want to monitor your own fleet or offer GPS tracking to your customers.

2. Agree on the setup

We check device compatibility and agree on the server setup, user access and features you need. Before we start, we confirm what we’ll configure and what you’ll need to provide.

3. Start using your platform

We set up the agreed environment, test the device connections and give you access to the administration panel. From there, you can manage your vehicles and users or set up accounts for your customers.

Define Your Deployment

Use the form below to tell us about your project. If you already know the details, please include:

  • The expected number of connected devices.
  • The Teltonika models you intend to use.
  • The number of customer accounts and users.
  • Required reports, alerts and telemetry data.
  • Your preferred hosting environment.
  • Branding and integration requirements.

The proposal will specify licence terms, installation scope, included modules, any applicable limits, updates and support.

FleetMonitoring is currently under development. Contact us to discuss your planned GPS tracking platform.

Please include your expected number of vehicles, Teltonika tracker models and the features you need.