How it works
Three people, one chain of record.
The resident is billed monthly. The operator runs the sequence. The municipality is paid first. Everyone quotes the same rows.
Ward sequencePostGIS · ward sequencing
Plan
Wards and crew-drawn service points become the unit of work. Geometry is stored as PostGIS points — not street addresses that do not exist.
EVENT · Zone 3 sequence locked · 14 stopscycling
Console inspect14 stops · 21.4 km · assisted
- 01Depot
- 02North 1
- 03North 4next
- 04Market kerb
- 05Landfill
Simulated sample city. Click a node to inspect the desk.
Resident or commercial client
Pay and be picked up
On the city host — never on metrocir.com
01A monthly batch invoice is issued against your tier — not a charge per collection.
02Payment goes through the city portal or mobile money rails; sandbox today, production cutover pending.
03Confirmations and reminders arrive in the city's languages — Swahili first in Tanzania.
04A missed pickup is reported on the city host and closed out on the same record.
Operator
Run the concession
On the city operator host
01Dispatch sequences ward runs and assigns crews and vehicles.
02Drivers work the run in-cab and capture proof of service offline if needed.
03Loads are weighed in; the ticket is sealed into the append-only ledger.
04Vendor payout and billing read that ledger — no parallel spreadsheet.
Municipality
Verify and be paid
Reporting from the city host
01Scheduled versus served per ward, with exceptions listed.
02Concession fee computed on verified tonnage and settled first.
03SLA events and civic close-outs available as evidence.
04Period statements reconcile to the weight ledger, row by row.