Smart meter field operations platform for AMISPs and DISCOMs

What smart meter field operations actually covers

People talk about a smart meter "rollout" as if it were one job. On the ground it is six, run by different people and often by different companies. Each stage leaves behind data that the next stage depends on, and most of the pain in a rollout comes from that hand-off.

1. Survey and consumer indexing. Before a meter goes up, someone walks the area and ties every consumer account to a pole, a distribution transformer (DT) and a feeder. If the indexing is wrong, DT-level energy accounting never balances, and nobody finds out until months later. See consumer indexing.
2. Installation. The old meter comes off and its final reading is recorded. The smart meter goes in and the seals go on. This is the volume stage, where a crew's day is counted in meters. See smart meter installation.
3. Verification. Someone other than the installer confirms the job happened where the record says it did, with the meter the record names. See installation verification.
4. Commissioning. The new meter has to appear in the head-end system (HES) and start reporting. A meter that is installed but silent is a cost, not an asset. See HES and MDM integration.
5. O&M and NCM. Some meters stop communicating. Each non-communicating meter (NCM) needs a field visit to find out why: a SIM problem, a weak signal in a meter room, a tampered or damaged unit. See NCM resolution.
6. Disconnection and reconnection. Prepaid meters handle most of this remotely, but a share of cases still ends with a technician at the premises. See disconnection and reconnection.

The diagram above shows the order. Most tools on the market are built for one or two of these stages. A platform for smart meter field operations has to carry a single service point through all six without someone re-typing it in a spreadsheet in between.

Who does the work

AMISPs (Advanced Metering Infrastructure Service Providers) hold the contract with the DISCOM. Under India's RDSS programme they handle metering end to end, which means they answer for every installed meter, whether or not their own staff installed it. Read more on the AMISP page.

Installation agencies are the crews. One AMISP often works through several agencies across districts, each with its own supervisors, phones and habits. They need something their technicians will actually use with gloves on, in the sun, on a cheap Android phone.

DISCOM project teams oversee the work, sign off progress and deal with the consumer complaints when a job goes wrong. They need to see what was done without chasing three companies for a status update. Read more on the DISCOM page.

The same platform has to serve all three, and each should only see what belongs to them. PIEBENCH is multi-tenant, and inside each organisation access is controlled by seven roles, with an audit trail on every action.

Where rollouts go wrong in the field

Most rollouts don't fail on the meter. They fail on the paperwork around it.

The spreadsheet relay. Crews send photos and readings over WhatsApp. A supervisor copies them into Excel at night. The AMISP merges a dozen of those sheets at the end of the week. Every copy is a chance to mistype a meter serial, and a wrong serial means the meter never commissions properly in the HES.

Installs nobody can prove. When an installation is disputed, the question is simple: was the technician at that premises, with that meter, on that day? Without a timestamped photo, a GPS fix and a scanned serial attached to the job, nobody can answer it.

Bad news arrives late. A crew that is slow, or skipping steps, shows up in the monthly numbers. By then the rework is already sitting in the next month's plan.

Rework. A blurred seal photo, a missing final reading on the old meter, a serial typed with one digit swapped. Each one sends a technician back to a premises they already visited.

No network where the meters are. Meter rooms in basements, rural feeders, hill districts. An app that needs a live connection to save a job will lose work in exactly the places where rollouts are hardest.

How PIEBENCH runs it

1. Load your service points. Import consumers and premises from a CSV, or pull them from your billing system. In PIEBENCH each service point is a location, so every job, photo and reading hangs off a place on the map.
2. Choose a template or build your own form. Meter Installation and Consumer Indexing come ready to use. You can change them, or build a new form with text, number, dropdown, checkbox, checklist, barcode, photo, GPS and counter fields. Adding or removing a step is the AMISP's decision, not a developer's.
3. Assign the work. Work orders go to teams, and teams can sit under a named contractor, so you can follow each installation agency separately. Crews on duty can also pick up jobs on the move.
4. Capture in the field, offline. Technicians complete jobs in Scout, the Android app. Photos are compressed on the phone, and everything is stored locally until the signal comes back, then it syncs.
5. Approve or reject. Supervisors review each submission. A rejection carries a note, so the crew knows exactly what to fix. A meter serial that already exists in the project is refused. On the Pro plan, rules can auto-approve the jobs that meet your criteria.
6. Send it on. Approved data goes to your HES, MDM or billing system through Connectorly, the integration module. Progress by crew, team and agency is visible the same day, with attendance alongside it.

What runs underneath every stage

Four pieces support all six stages:

• An offline field app. Scout saves everything on the phone first and syncs when there is signal, on Android 7.0 and later.
• A no-code workflow builder. Forms for each stage, built and changed by your own admin.
• Integrations. Connectorly links PIEBENCH to HES, MDM and billing systems such as SAP IS-U and Oracle CC&B.
• Field attendance. Selfie and GPS check-in, duty hours and stationary-agent alerts.

What to look for in a smart meter field operations platform

This is the checklist we would use if we were buying. It works for comparing any vendor, not just PIEBENCH.

If a vendor cannot show you the first three working on a low-end Android phone in airplane mode, the rest of the list doesn't matter much.

Getting started

Most teams start small: one project, one agency, a few hundred service points. You can be running in about 10 minutes on the free trial, with no card. When the pilot holds up, add the integration and the rest of the crews. Paid plans start at $199/month; see pricing.

Outside India

Nothing in the workflow above is specific to RDSS. A utility or metering contractor in the Gulf replacing electromechanical meters runs the same sequence: survey, install, verify, commission, maintain. The vocabulary changes (a "utility" rather than a DISCOM, a "metering contractor" rather than an AMISP), but the field problems are the same. Working outside India? Get in touch.