Domain model
Shipments, legs, vehicles, drivers, fuel events and incidents as tables with real keys and constraints. Most spreadsheet chaos is a modelling problem; once a leg is an entity, many reconciliation questions answer themselves.
Replace a web of spreadsheets with one operational view, without stopping the business.
Reference engagements illustrate how Elicon would approach a project of this kind — the problem, the architecture and the decisions. They are examples, not accounts of past client work.
THE SITUATION
A logistics operator running the business from interlinked spreadsheets and a telematics portal nobody in dispatch opens. The engagement models the real operation in Postgres, ingests live vehicle positions, and gives dispatchers, drivers and owners each their own view — migrating the spreadsheets rather than abandoning them.
Every question about a shipment takes several tabs and a phone call, and month-end reconciliation produces numbers nobody fully trusts.
APPROACH
ARCHITECTURE
Shipments, legs, vehicles, drivers, fuel events and incidents as tables with real keys and constraints. Most spreadsheet chaos is a modelling problem; once a leg is an entity, many reconciliation questions answer themselves.
Repeatable importers per sheet with validation reports listing every failed row and why, run nightly against the live sheets so the database is never stale during transition.
Driver screens cache the day's assignments and queue updates locally, syncing when signal returns. A yard with no signal is the normal case, not an edge case.
DECISIONS
A hard cutover on a business that cannot stop invites a rollback. Nightly re-imports let the new system be wrong for a day without losing a shipment.
TRADE-OFFA period of double entry for some fields, and importer maintenance during it.
It is installed, paid for and working. Replacing it adds cost and an installation schedule to a software project.
TRADE-OFFThe vendor's API limits and gaps are inherited and smoothed over rather than fixed.
Mixed devices and no device management make native distribution more expensive than the feature itself.
TRADE-OFFNo background location and a weaker offline story, both mitigated with caching and queued writes.
STACK
Work of this shape usually runs as Agent Ops Sprint →
SIMILAR PROBLEM?
One conversation with an engineer is usually enough to tell whether this is a few weeks of work, a few months, or something you shouldn't build at all.
Talk to an engineer →