Your fleet already generates data all day long. SASCAR, Autotrac, Omnilink, Onixsat, Cobli, Geotab — each device knows where the vehicle is, how fast it's going, how long the driver has been at the wheel and whether the reefer unit has drifted out of range. The problem is rarely a lack of data. It's data locked in six different portals, checked by hand, pasted into a spreadsheet. By then it arrives late, arrives wrong, or doesn't arrive at all.
We connect your fleet's telemetry directly to your TMS and BI. Position, driver hours, events and geofences become metrics your team uses every day — one source, in real time, with no spreadsheet in the middle. You stop operating by staring at a tracker portal and start operating by looking at your actual operation.
Which telemetry data enters the integration
Every provider exposes a similar set of data, with different names. We normalize it all into a single format — whether a vehicle is tracked by SASCAR or Geotab, the metric lands the same way in your dashboard. What we typically sync:
- Position and route: latitude/longitude, approximate address, heading and odometer. The foundation for maps, geofences and delivery SLAs.
- Speed: instantaneous speed and violations against the road limit or company policy.
- Driver hours: ignition, movement, stops, meals and rest — the input for driver-hours management (the Brazilian Driver Law).
- Events: harsh braking, aggressive acceleration, sharp cornering, RPM, panic button, geofence violation, signal loss and immobilization.
- Temperature and cargo body: reefer sensors, door opening and trailer coupling/uncoupling — critical for cold chain and anti-theft.
- Identification: license plate, driver (iButton/RFID), route and, when available, the link to the transport document.
If one of your providers isn't on this list, we usually integrate it too. The right question isn't "do you support brand X," it's "does brand X have an API or position feed" — and it almost always does.
Where the data goes: TMS, BI and customer portal
Telemetry on its own is a pretty map. Telemetry connected to the rest of the operation is management. We take the data to the three places where it turns into work:
- TMS (RODOPAR and others): position ties to the trip and the CT-e. A telemetry event becomes a transport event. The TMS no longer depends on someone opening the tracker portal to know where the cargo is.
- BI (Power BI and others): events become historical metrics — on-time performance, yard time, driver-hours usage, recurrence of risk events by driver and by route. Data that turns into decisions, not a report no one reads.
- Customer / shipper portal: your customer tracks their own delivery with real position and status, without calling the control room. Visibility that cuts down the ringing phone and improves service perception.
It's the end of re-keying: the event is born in the tracker and travels through TMS, BI and portal without anyone copying it over.
What this solves in practice
We don't sell dashboards. We solve three concrete pain points that show up at nearly every carrier:
- Driver-hours management: driving, waiting and rest hours come straight from telemetry, ready for review and closing. Less labor liability, less manual timekeeping spreadsheet, a real basis for overtime pay.
- Anti-fraud and security: route deviation, unplanned stop, geofence violation, cargo-body opening away from the delivery point and signal loss become alerts on the spot — not a discovery the next day. Telemetry cross-checked against the TMS trip is what separates a real incident from a false positive.
- Delivery SLA: position is checked against the promised window. You know a delivery will run late before the customer does, you measure on-time performance by route and by customer, and you have the history to renegotiate contracts with numbers, not opinions.
How the integration is done
The path depends on what each provider offers, and we pick the most stable one for your operation:
- API / webhook: when the provider exposes an API (as with Cobli, Geotab and most modern ones), we pull positions and events via scheduled requests or receive the push in real time.
- Position feed: SASCAR, Autotrac, Omnilink and Onixsat typically offer to send data to an endpoint of yours — we enable and handle the inbound flow.
- Normalization layer: between the provider and your TMS/BI sits a layer that standardizes names, units and time zones, deduplicates repeated positions and stores history. It's what makes six providers look like one.
The integration runs in parallel with your operation. We don't swap or shut down your tracker — we only read what it already produces. Technology that disappears so your business can show.
Why Meta Dados
We've been integrating transportation and logistics since 2000. We know SASCAR, RODOPAR, the CT-e and the day-to-day of fleet operators — we don't show up to learn your business during your project. We start by understanding the real operation, in the field, before proposing any architecture. And we deliver with governance and privacy by design, not as a patch: driver data is personal data, and we treat it that way from the very first position.
The first step is a free assessment in 48h: we map your telemetry providers, your TMS and where the spreadsheet lives today, and we show exactly what can be automated — with scope, order and timeline. No strings attached.
Frequently asked questions
How long does it take to integrate telemetry into my TMS?
A single-provider integration (for example, SASCAR into RODOPAR) with position and the main events is usually ready in a few weeks. The actual timeline depends on how many providers you use and how accessible each one's API is. The free 48h assessment returns a schedule with scope and order before any contract.
Do I have to stop the operation or switch trackers?
No. The integration reads the data your tracker already produces and runs in parallel with the operation — nothing is shut down or replaced. You keep SASCAR, Autotrac, Omnilink or whatever provider you already use; we simply connect that flow to the TMS and the BI.
Which telemetry data is synced?
Position and route, speed and violations, driver hours (ignition, stops, rest), risk events (braking, geofence violation, panic button, signal loss), reefer temperature and cargo-body opening, plus license plate, driver and route identification. We normalize it all into a single format, the same for every provider.
Can I integrate more than one tracking provider at once?
Yes, and it's the most common case. Fleets mix SASCAR, Autotrac, Omnilink, Onixsat, Cobli and Geotab depending on when the vehicles were acquired. A normalization layer unifies them all: the metric lands the same way in the dashboard, no matter which tracker the position came from.
Does the integration work for driver-hours management?
Yes. Driving, waiting and rest hours come straight from telemetry's ignition and movement events, ready for review and closing. This reduces manual timekeeping in spreadsheets and provides a real basis for the driver-hours calculation under the Brazilian Driver Law.
How does the anti-fraud and alerts side work?
We cross-check telemetry against the TMS trip. Route deviation, unplanned stop, geofence violation, cargo-body opening away from the delivery point and signal loss become real-time alerts. Cross-checking against the planned trip is what reduces false positives and focuses the control room on the incident that matters.