Measured on the road. Posted in your ERP.
Kilometres, hours, fuel and alerts become the numbers your ERP invoices, your accountant reconciles and your regulator expects: shaped by formulas you write, delivered to any system, with proof.
Integration Hub
The Integration Hub reads the same event stream every other component reads and turns it into outputs for systems outside EaglesEye. You write formulas over trips, idle time, alerts and fuel (a rate per kilometre, a surcharge after hours, a rounding rule), shape the result to the target's schema, and connect it: Odoo invoice lines and analytic accounts, a webhook to your own software, a scheduled file to a government tracking portal. Every delivery is logged and can be replayed. Nothing about your fleet is locked inside our screens.
| Description | Qty | Rate | EGP |
|---|---|---|---|
| Kilometres, measured | 14,220 km | 3.20 | 45,504 |
| Waiting hours, engine on | 61.5 h | 45.00 | 2,768 |
| After-hours kilometres | 412 km | 4.00 | 1,648 |
| Total | 49,920 | ||
Building blocks of the hub
- 1
Event stream
trips · alerts · summary · positionsEvery trip with its measured distance and engine-on idle, every alert, every day's totals, per vehicle and per tenant, as they happen or in batches. The REST API serves the same data today.
- 2
Formulas
Roadmapformula · per tenant · versionedYour arithmetic over the stream: billable_km = distance_km × 1.05, after_hours_fee = km_after_hours × 2.5, waiting = idle_h > 1 ? idle_h − 1 : 0. Units, rounding and thresholds you control, tested against yesterday before going live.
- 3
Output shaping
Roadmaptemplate · json · csv · xmlMap fields to the target's schema with a template: an Odoo invoice line, a CSV a ministry accepts, the JSON your dispatcher app expects. Preview the exact payload before switching it on.
- 4
Connectors
Roadmapodoo · webhook · mqtt · sftp · emailOdoo through its standard XML-RPC API: invoice lines, fleet odometers, analytic accounts. Signed webhooks to any URL. MQTT for control rooms. Files by SFTP or email on a schedule.
- 5
Government feed
Roadmapscheduled · signed · auditableWhere an authority requires vehicle tracking data, a scheduled, signed feed in its format, per vehicle, with proof of delivery. One connector per authority, maintained once for every customer.
- 6
Audit & replay
Roadmapdeliveries · retries · replayEvery delivery recorded with payload, response and time; failures retried with backoff; any window replayable after a target outage or a formula fix.
The hub in action
Invoices from what actually happened
A transport company bills per kilometre and per waiting hour. Measured km and engine-on idle per vehicle and contract post into Odoo invoice lines. The invoice is built from the road, not from driver sheets.
Fuel cost in the books
Fuel and idle cost per vehicle, per day, land as analytic entries against each vehicle's cost centre. Finance sees the fleet in the same ledger as everything else.
The regulator's feed
A ministry mandates tracking data for licensed fleets. A connector formats and delivers it on schedule, with stored proof, and nobody exports a spreadsheet again.
Who uses it
Odoo first; SAP B1 and Dynamics on demand.
Cost per vehicle, in the ledger.
Authority feeds that prove delivery.
Webhooks and REST for everything else.
Questions
Your fleet data, in the systems that run your business