Customer story · Logistics
A postal operator
Fleet analytics for a postal operator
Messy monthly fuel workbooks become a canonical fleet data model, with per-vehicle reporting against versioned norms and access that mirrors the organisation.
Executive summary
The situation
Monthly workbooks had messy headers and format variants. Vehicle data and consumption norms also change, so historical comparisons need the reference values effective at the time.
What was built
Nexus normalises uploads, prevents duplicate ingestion and versions reference data by date. Fuel, cost, deviation and trend reports respect organisational scope; an assistant uses guarded read-only queries.
Why it matters
Makes repeatable reporting easier to work with while preserving reference dates and access boundaries. Managers have a consistent basis for examining their area, through reports or questions.
- Primary users
- Fleet users and regional managers
- Core systems/data
- Fuel workbooks, vehicle data and dated norms
- Human control point
- Role scope and read-only queries
- Nexus role
- Normalisation, versioning and reporting
The challenge
Monthly workbooks that never look the same.
Monthly fuel workbooks arrived with messy headers and format variants. The ingestion process needed to recognise those differences and bring them into a common model without duplicating records on repeated uploads.
Vehicle data and consumption norms also change over time. Historical comparisons need the reference effective then, while managers need a view aligned with their organisational scope. Format handling, dates and access all belong in the reporting design.
What we built
A canonical fleet model with scoped reporting.
Workbook variants are normalised into a canonical model. Uploads are idempotent, so submitting a file again does not create duplicate records. Vehicle master data and norms carry effective dates: a historical comparison needs the relevant norm, not simply the latest one.
Per-vehicle reporting shows fuel, cost, deviation and historical trends. Access mirrors organisational hierarchy, such as a regional manager seeing their region. The assistant answers through guarded read-only queries under those boundaries. The interface can be bilingual while official reports use the required business language.
How the workflow runs
Step by step.
01
Upload
Monthly fuel workbooks are uploaded. Format variants are fused into the canonical data model.
02
De-duplicate
Idempotent uploads prevent duplicate records. Consumption is compared with the norm effective at the time.
03
Report
Per-vehicle reports show fuel, cost, deviation and trends. Users query fleet data through the read-only assistant.
What the business team sees
Reports scoped to each manager.
Managers examine consumption, costs and deviations for their part of the organisation, with trends and dated norms providing context. The assistant offers another route into the same data without write access. Interface language can support users while official reporting keeps its required business language.
- Per-vehicle fuel and cost
- Deviation against norms
- Historical trends
- Region-scoped access
- Read-only fleet assistant
How Nexus works underneath
Reference dates belong in the calculation.
Deterministic normalisation maps variants to one model; idempotent ingestion prevents repeated uploads from duplicating records. Effective-date versioning connects comparisons to their historical reference. Nexus applies access boundaries to reporting and assistant queries alike, keeping the assistant read-only within the user’s scope.
Architecture
How the layers fit together.
Business team
Fleet reports and assistant
Per-vehicle reports · trends · scoped access · questions
Nexus orchestration
- 01Workbook ingestion
- 02Normalisation
- 03Idempotent upload
- 04Versioned norms
- 05Reporting
- 06Guarded queries
Connected systems and data
- Monthly fuel workbooks
- Vehicle master data
- Consumption norms
Human control and audit
Access follows the organisation.
Role-scoped access means each manager sees only their area. The assistant respects the same boundaries and cannot change data.
What this changes
Repeatable handling of variants. Normalisation is designed to reduce repeated preparation across known formats.
Comparisons retain their dates. Reports use versioned norms rather than treating the latest reference as timeless.
Access reflects the organisation. Managers inspect their own scope, including through assistant queries.
Your process
Discuss a similar workflow
Tell us about the documents, systems and decisions involved. We will discuss where Nexus orchestration fits and where your team stays in control.