The test reconstructed a posteriori
When the client disputes a ride, the response is constructed by asking the driver and looking at the tour sheets. It's a memory versus a complaint.
Sector — waste collection
Completing the collection round is one thing. Proving it is another.
Disputes arrive after the collection round: a missed location, an unrecorded pass or a challenged invoice. Zenit records location and time as the round happens, instead of forcing the team to reconstruct them later.
The point
A service that is judged on things that happened days before.
The collection is a repetitive and verifiable work, but the verification almost always comes later — and at that point what can be opposed is a memory.
Laps that change without leaving a trace
A detour, a missed point due to blocked access, a redone lap: it happens, and it's normal. Not having a trace of it is not.
Consumption that no one compares
On identical routes every week, a deviation is a strong signal, but remains invisible if the data is not compared over time.
Scheduled maintenance on different wears
Two vehicles on the same service accumulate very different wear in terms of number of stops and time with the engine running. A fixed date treats them equal.
Driving times to be monitored as elsewhere
If the fleet falls under the obligations, the same rules apply as for any heavy fleet, but the urban service makes them easier to lose sight of.
The main topic
Operational evidence, non-documentary compliance
The distinction is the heart of this page and it is worth keeping it clear, because confusing them is the quickest way to make a commitment that we cannot keep.
What Zenit records
Route history shows where the vehicle travelled and at what time. The data is recorded during the collection round, so it is ready to review when someone asks for it instead of having to be reconstructed.
What is it for
To respond to a dispute with a trace instead of with a memory, and to first recognize a ride that is going differently than usual - a longer route, an anomalous stop, a point not reached.
What it isn't
It is not the documentary traceability of waste, which follows its own discipline with its own systems and deadlines and is not part of the Zenit coverage. It's not even a certification: how much the evidence is worth in the relationship with the client depends on what the contract between you provides.
- The platform provides the data, not its legal qualification
- No statements about regulatory compliance on this page, on purpose
- If you need documentary coverage, the request must be made to the person who provides it
What do you use
The modules that govern a collection service
Three areas, all available today.
Location and history
Where the vehicle travelled and when, with each collection round reconstructable from route history.
Stops and dwell time
How long a vehicle remains stationary and where: on a fixed point service, this is the data that distinguishes a passage from a transit.
Consumption and vehicle data
Consumption, kilometres and time with engine running, comparable between identical laps.
Maintenance on use
Deadlines tied to actual mileage and usage rather than a fixed date.
tachograph
If the fleet is subject to tachograph rules, data downloads and deadlines are managed within the same framework.
Operational alerts
Rules that report the deviation as it happens, not as a final result.
What changes
From reconstruction to evidence recorded during the collection round.
No numbers declared: we have no verifiable data on collection fleets to cite.
Before
- 1
Test built later
The response to a complaint is gathered by asking who was in the vehicle.
- 2
Invisible deviations
A longer than usual turn is only noticeable if someone compares by hand.
- 3
Wear treated equal
Vehicles with different workloads follow the same maintenance calendar.
With Zenit
- 1
Test already registered
Position and time exist from the moment the vehicle passed.
- 2
Legible deviation
On repetitive routes the difference compared to usual is a strong signal.
- 3
Interventions on real use
The thresholds follow actual kilometres and use of the individual vehicle.
Operational coverage
Three boundaries to clarify before configuration
Contract, fleet and tachograph classification determine what data is available and how it can be used.
Contract
The contract with the client
What the client accepts as evidence of a passage is a clause, not a function. It should be read before promising that the data is enough.
The contract remains the source for establishing which evidence is accepted by the client.
Vehicle
The fleet of vehicles
Which data the on-board network displays changes depending on the brand, year and equipment of the heavy vehicle.
Signal availability is verified on the actual fleet before installation.
Compliance
Tachograph obligations
Whether the rules apply to the fleet depends on the type of transport and the maximum permissible mass.
The classification falls to those who follow the company's compliance.
Frequently asked questions
Frequently asked questions about waste collection
Bring the last complaint you received to the demo.
It is the quickest way to understand if the data we record would have been sufficient to respond. If that wasn't enough, it's better to know now.