Createch Yazılım Danışmanlık ve Bilgi Teknolojileri San. Tic. Ltd. Şti.
Fleet · Telemetry

Vehicle tracking systems and fleet management

Knowing where the vehicle is only the beginning. What matters is knowing what it is doing: engine speed, real fuel consumption, door status, cargo temperature, driver behaviour and delivery confirmation become manageable once they meet in the same data model.

We design and manufacture the telemetry hardware at our own R&D centre. Vehicle tracking here is therefore not software wrapped around an off-the-shelf device; it is a layer where we can change which vehicle data is read and how, per sector. Tanker compartments, concrete drums and refrigerated cargo are monitored on one platform under different rules.

  • GPS Position
  • CAN-bus
  • Fuel Consumption
  • Geofence
  • Driver Scoring
  • In-vehicle Tablet
  • Trip Management
  • Sensor Interfaces
  • Idle Analysis
  • Fault Codes
  • Instant Alerts
  • Central Reporting
01 DEFINITION

Vehicle tracking:
not position, operational data

The dot on the map is a starting point; what drives decisions is the data behind it.

A vehicle tracking system uses a telemetry device fitted to the vehicle to send position and vehicle data continuously to a central platform, making the current state of the fleet observable. The common perception limits this to showing vehicle position on a map; but position alone does not produce an operational decision.

What produces decisions is data coming together: engine and fuel data over CAN-bus, temperature and door status from sensors, delivery confirmation entered by the driver on a tablet and geofence events meeting on the same timeline. Then the question changes from "where is the vehicle" to "is the trip going as planned".

01 · POSITION

Where

GPS position is displayed on the map in real time; historical trace, stop durations and route deviations are recorded.

02 · STATE

What it is doing

Engine speed, road speed, fuel consumption, idle time and fault codes are read from the vehicle computer; cargo and equipment data come from sensors.

03 · EVENT

What happened

Geofence violation, harsh braking, speeding, door opening or temperature deviation is raised as an event and reported to the right person immediately.

02 DATA FROM THE VEHICLE

CAN-bus telemetry:
reading, not estimating

Calculating fuel consumption from distance and reading it from the vehicle computer are not the same thing.

  • Engine and driving data: Engine speed, road speed, throttle and braking behaviour and idle time are read over CAN-bus; driving analysis rests on vehicle data rather than estimation.
  • Real fuel consumption: Consumption is read from the vehicle, not estimated from distance. Fuel loss, abnormal consumption and fuel burned at idle become separately visible.
  • Fault codes: Error codes produced by the vehicle computer reach the centre; a fault enters the maintenance plan before it is noticed in the field.
  • Sensor interfaces: Vehicle-specific equipment data is collected through boards supporting digital I/O, temperature sensors, RS232, RS485 and TTL.
  • Cargo and equipment state: Tanker compartment, concrete drum rotation direction, refrigerated cargo temperature or door open/closed status are defined per sector.
  • Time-stamped records: All data is stored with a time stamp, making post-event review and evidence-based reporting possible.

We design and manufacture the telemetry boards, driving safety modules and sensor interfaces at our own R&D centre. Product models, port layouts and technical specifications are published in our technical documentation centre.

Telemetry Product Family — Createch Wiki

Telemetry data path from vehicle to report The diagram shows a four-stage flow. On the left are the data sources on the vehicle: the CAN-bus line, the GPS receiver, sensor inputs and door and temperature contacts. These connect to the telemetry board fitted to the vehicle, chosen from the CRE-FMB and CRE-FMC families; because the board has multi-protocol inputs it can read from vehicles of different makes and models at the same time. The board transfers what it collects to the cloud over GSM in encrypted form. On the right is the platform layer, where the data becomes a live map, fleet reports, alarms and alerts, and the tablet inside the vehicle. Fuel and engine values are read directly from the vehicle, so no estimation is involved. ONE BOARD · MANY PROTOCOLS VEHICLE DATA SOURCES CAN-BUS GPS POSITION SENSOR INPUT DOOR · TEMPERATURE TELEMETRY BOARD CRE-FMB · CRE-FMC MULTI-PROTOCOL INPUT OUR OWN MANUFACTURE GSM · CLOUD ENCRYPTED TRANSFER PLATFORM OUTPUTS LIVE MAP FLEET REPORT ALARM · ALERT IN-VEHICLE TABLET DATA IS READ FROM THE VEHICLE, NOT ESTIMATED
DIAGRAM · DATA PATH FROM VEHICLE TO REPORT Every link in the chain runs on hardware we manufacture ourselves: the telemetry board, the sensor interfaces and the in-vehicle tablet share one data model, so no integration layer sits between them. The product codes in the diagram correspond to real model families published on the Createch Wiki; the number and type of sources vary with the hardware fitted to the vehicle.
03 IN-VEHICLE TABLET

A two-way link
with the driver

Telemetry carries data from vehicle to centre; the tablet carries tasks from centre to vehicle.

01

Tasks and delivery sequence

The driver receives the daily task list, delivery sequence and customer details on the tablet; paper lists and confirmation by phone disappear.

02

Delivery confirmation

When a delivery is completed, confirmation, waybill details and any deviation reason reach the centre instantly; trip status updates in real time.

03

Intra-day updates

When a cancellation, delay or new order arrives, the updated sequence appears on the tablet; the driver sees the change on screen rather than over the phone.

04

Field instructions and alerts

Route deviation, geofence violation or a safety warning is raised in the cab with sound and visuals; the event is reported to the centre automatically.

04 GEOFENCE

Knowing what happens
outside the defined zone

A geofence is not a drawing on a map; it is an operational rule.

Operational zones defined on the map enter the system as rules. When a vehicle enters or leaves a defined zone an event is raised; a delivery, discharge or unloading attempt outside the zone is detected immediately. An audible and visual alert is raised in the cab and the management centre is notified automatically.

What the rule means changes by sector. Loading and discharge happening inside an authorised zone in fuel distribution, a pour taking place at the correct site in concrete, and a refrigerated vehicle not opening its door outside the cold store are all checked by the same mechanism.

01 · DEFINE

Zone definition

A site, station, warehouse or restricted area is marked on the map once; the system remembers those boundaries permanently.

02 · MONITOR

Entry and exit monitoring

An event is raised when the vehicle crosses a boundary; an out-of-zone operation attempt is detected and recorded immediately.

03 · ALERT

Two-way alerting

An audible and visual alert is raised in the cab while an automatic notification reaches the management centre at the same moment.

Geofence definitions and automatic event generation The diagram shows two authorised zones defined on the map: the depot on the left and the filling terminal on the right. The vehicle track follows the route from the depot to the terminal. Three events are marked along the track. The first is the vehicle crossing the depot boundary at 08:12, recorded as an exit event. The second is an eighteen-minute stop beginning at 10:25 at a point between the two zones that is not defined as authorised; because it is a stop outside any zone it is marked in the warning colour and the control centre is notified automatically. The third is the vehicle entering the filling terminal boundary at 11:40. Zone entry and exit are not reported by hand; once the boundary is drawn on the map the events are generated on their own. GEOFENCE · EVENT GENERATION DEPOT / AUTHORISED ZONE FILLING TERMINAL DEPOT TERMINAL EXIT EVENT 08:12 · LEFT THE ZONE UNAUTHORISED STOP 10:25 · 18 MINUTES ENTRY EVENT 11:40 · INSIDE AUTHORISED ZONE EVERY BOUNDARY CROSSING IS RECORDED WITH A TIMESTAMP
DIAGRAM · GEOFENCE AND EVENT GENERATION Zones are drawn on the map once; after that entry, exit and out-of-zone stop events are generated automatically. In fuel and LPG transport this is how filling and discharge are verified to happen only at the authorised terminal. The times and durations in the diagram are illustrative examples; the number of zones and the alarm thresholds are defined per operation.
05 DRIVER BEHAVIOUR

Telemetry and camera
score together

Part of driving behaviour shows up in vehicle data; part of it only in the cab image.

  • Read from telemetry: Harsh acceleration and braking, cornering, speed violations, idle time and abnormal fuel consumption.
  • Read from the camera: Phone use, seatbelt status, smoking and fatigue indicators such as eye closure.
  • Instant alerting: When a violation is detected the driver is warned in the cab and the event is reported to the centre at the same moment.
  • Safety score: Violation history and a safety score are kept per driver in the central panel, with instant access to driver-level reports.
  • Training input: Scores can be used as an objective measure in individual training and bonus processes.
  • Evidence-based review: Because event footage and telemetry are stored together, dispute and damage processes move faster.

In-cab AI cameras, blind spot radar, 360 degree coverage and event-based recording are covered in detail on a separate page.

Vehicle Camera Systems

07 FREQUENTLY ASKED QUESTIONS

Common questions about
vehicle tracking systems

The questions we meet most often in project discussions.

01

What is a vehicle tracking system?

A telemetry device fitted to the vehicle sends position and vehicle data continuously to a central platform, making the current state of the fleet observable. Engine, speed and fuel data over CAN-bus, temperature and door status from sensors, and delivery confirmation entered on a tablet all meet in the same data model.

02

What is the difference between CAN-bus telemetry and GPS tracking?

GPS tracking tells you where the vehicle is; CAN-bus telemetry tells you what it is doing. Engine speed, real fuel consumption, road speed, braking and fault codes are read from the vehicle computer. Reading consumption from the vehicle rather than estimating it from distance gives a different level of accuracy.

03

What is a geofence used for?

Geofences are operational zones defined on the map. When a vehicle enters or leaves a zone the system raises an event; a delivery, discharge or unloading attempt outside the zone is detected immediately, an alert is raised in the cab and the management centre is notified automatically.

04

How is driver behaviour measured and scored?

Acceleration, harsh braking, cornering, idle time and speed violations come from telemetry; phone use, seatbelt status and fatigue indicators come from the in-cab AI camera. Violation history and a safety score are kept per driver in the central panel.

05

What does the in-vehicle tablet do?

The driver receives the task list, the current delivery sequence and field instructions on the tablet, and sends delivery confirmation, waybill details and any deviation reason back instantly. When the route changes during the day, the updated sequence appears on the tablet.

06

Do you manufacture the hardware as well?

Yes. Telemetry boards, driving safety modules and sensor interfaces are designed and produced at our own R&D centre in Seferihisar, İzmir. Product models and technical specifications are published on Createch Wiki.

08 CONTACT

Make your fleet visible

We define your vehicle types, the data that needs to be read and your operational rules together. Deployment can start with a single vehicle and spread across the fleet; existing vehicles are retrofitted with additional hardware.

Contact us for detailed information, project consultancy and demo requests. Our technical team is ready to plan the deployment scope around your fleet size and vehicle types.