Meter Reading Route Planner

Field guide: Meter Reading Route Planner

Manual reads survive everywhere AMI hasn't reached — and paradoxically, AMI created a new routing problem: the monthly exception list (silent endpoints, tamper flags, high-low checks) scatters single visits across the whole service territory, the worst possible geography for gut-feel ordering. Paste the exception list or the book's stops, and let the solver turn scatter into a sane loop.

Defaults fit mixed walk/drive reading: 20 km/h effective speed and 2 minutes per meter (find it, read it, key it, photograph if disputed). Off-cycle final reads and re-reads — the other scattered-visit workload — fit the same pattern. The CSV export is your read sheet: order, premise, coordinates, ETA. Reads themselves go in your billing system; this just makes the boots efficient.

Field tips

• Run exception lists through the optimizer the morning they're generated — scattered singles benefit most from ordering, often 30%+.
• Bump service time to 5+ minutes for known dog/locked-gate/deep-pit premises so the day's ETAs survive contact with reality.
• GPS-capture problem meters as you visit them (wrong coordinates in the CIS are common) — next month's route improves itself.

Records are stored only in this browser (localStorage) — export regularly. This tool aids field documentation; it does not replace your agency's official inspection procedures or engineering judgment.