Real-time tracking
The position of mobile assets — shipments, fleets, field teams — on the map and in history, with the route travelled and the stops, not just the last point.
Maps that sit inside the workflow, not beside it
Most applications with a map show where something is. The hard part starts afterwards: what happens when the vehicle leaves the permitted corridor, how the amount due is computed from the distance travelled, who receives the alert at 3 a.m. and what the next morning’s report says.
We build that part — the geographic rules tied to the institution’s process — not just the map. We worked on the national system for tracking sealed shipments and on road-charging platforms where position turns directly into money.
- PostGIS
- Leaflet
- Geofencing
- Tarifare pe zone
- Spring Boot
- Angular
01
What we build
Components that drop into an existing system or form a new one.
Geofencing and alerts
Zones drawn on the map and rules attached to them: leaving a corridor, stopping for too long, entering a restricted area. The alert goes out by email, SMS or in-app.
Zone and segment tariffs
Turning distance travelled into an amount due: segments, vehicle categories, time periods. With auditable rules, because invoices come out of them.
Maps inside the working screen
The map as part of the screen people already use, with its filters and actions, not a separate page you have to go to on purpose.
Territorial reports
Analysis by administrative unit, coverage area or route: where activity concentrates, where nobody gets to, what changed since last month.
Device integration
Taking data from smart seals, GPS devices or field apps, with position validation before it enters the process.
02
What you get
Rules, not just dots on a map
Position triggers something in the process: an alert, a charge, a task for someone. Otherwise the map is decoration.
History that survives scrutiny
The route is kept and can be reconstructed, with a timestamp on every point. In a dispute, the answer comes out of the data.
Calculations you can defend
When money follows from position, the calculation rule is written and tested separately, so it can be explained and checked piece by piece.
Works on a bad connection
Field apps store locally and send when the network returns. Data is not lost because someone drove through a tunnel.
03
How it runs
The geographic part is verified in the field, not in the office.
- 01
Rules on the map
We settle which zones matter, which rules apply in each and what happens when they are broken. We draw the zones together, on the map, rather than describing them in text.
- 02
Prototype on real data
We take real routes, not generated ones, and check what the rules produce: how many alerts, which are false, how much would have been charged. Rules are adjusted now, not after launch.
- 03
Going live
The component goes into the existing system with its alerts and reports. We stay on monitoring — geographic rules do change.
Questions about this service
Which maps do you work with?
Open maps (OpenStreetMap and derivatives) wherever possible, because they add no per-view cost, and commercial providers where the institution already has a contract. The geographic data lives with us, in PostGIS; it does not depend on the map provider.
How often is the position updated?
It depends on the device and on what you pay for data traffic. In practice, for intercity transport a point every 30–60 seconds is enough for routes and alerts; for urban fleets it comes down to 10–15 seconds.
Can you add a map to an application we already have?
Yes, that is the most common case. We first read how data flows through the existing application, then put the geographic component where decisions are already made, not in a new screen nobody opens.
What happens to old positions?
They are kept as long as the process requires, then archived or aggregated. Positions are personal data when they identify a person, so the retention period is settled at the start, not at the first audit.
Can you compute charges from recorded positions?
Yes, and we have: segments, vehicle categories, time periods. The tariff rule is written separately from the rest of the application and tested on real routes, because a mistake there means wrong invoices, not just a broken screen.
Contact
Have a map that does nothing?
Tell us what decisions should come out of the positions you already collect. We start there.
Office: Barajul Dunării 3, District 3, Bucharest