
Fieldman is the agile platform your organization needs to seamlessly integrate meter readings with your billing system and upgrade smart meter infrastructure during AMI installation and maintenance. Every project is unique, with its own challenges — and Fieldman guides you through them.
Start with a small field service project, confident that the Fieldman platform will adapt and upgrade alongside your project.








AMI deployment software runs the field work of a smart meter program: every account in a territory is visited once, on a schedule, and each visit produces an asset record the utility can audit. It handles routes and install cycles, meter exchanges and retrofits, field data capture with photos and serial scans, quality review, and inventory — the work between the contract award and the closeout report.
Field service management is built for service calls: a technician drives to an address, fixes something, closes the ticket, and the cycle repeats. A deployment is finite. You are working through a fixed list of addresses in a planned sequence, with a completion rate the utility tracks, and every visit that doesn't close has to come back around. A platform built for deployments already knows what an exchange, a retrofit, an RTU, and an unable-to-read are.
Three answers matter more than the feature list. What happens to the field app after a full day with no signal. Whether data reaches the utility's head-end system through an integration or an exported file. And how the price behaves when the crew doubles for a push — per-endpoint pricing and per-user pricing look similar in a pilot and very different at scale. Our AMI deployment guide walks through the rest.
Technicians keep working with no connection: their assigned work, workflows, photos, and readings are stored on the device and sync automatically once service returns. Nothing depends on a live connection in the field, which matters in basements, on rural routes, and in inside-set meter work.
Yes. Residents book, reschedule, and cancel their own appointments online, and dynamic scheduling keeps the open slots matched to the number of technicians actually available that day. Call center agents book on the same calendar, so a slot filled by either path is visible to dispatch the moment it's created.
Five days. A typical project starts on Monday with data import and workflow configuration and is running in the field by Friday. Each project is configured on its own, so a new contract doesn't disturb the ones already running.
Yes — Fieldman has a native integration with Sensus FieldLogic, so installed meters are registered without a file hand-off. Other utility systems connect by API or SFTP, depending on what the utility supports.


Read our free guide