Pass-through integration for local government · records are never stored System status1-559-251-7767Sentra familySign in
SentraBridgeIntegration platform
Finance & paymentsConnector

AMI meter data integration (Neptune 360, Sensus)

Advanced metering infrastructure (AMI) systems such as Neptune 360 and Sensus FlexNet collect water meter reads by radio. Utilities use them for daily reads, leak and no-flow alarms, and the billing read file each cycle.

Pre-built connector

AMI meter data (Neptune 360, Sensus)

Tier
Pre-built connector
Category
Finance & payments
Sign-in
API token (Bearer)
Paging
page number
Sandbox
Yes: practice with made-up data
Status
Built from the vendor's public documentation; confirmed with your account during setup

Vendor documentation ↗

§ Overview

What connecting AMI meter data does.

SentraBridge reads AMI export files or API data, checks each read and sends good reads to the utility billing system. This connector is built from public documentation, such as Neptune's file layout, and is confirmed with the utility's own export and account during setup.

  • Daily reads: Meter number, radio (MIU) ID, account, read time, reading and use since last read.
  • Meters (endpoints): Meter and radio IDs, account, route, dials and last read.
  • Alarms: Leak, tamper and no-flow alarms with raised and cleared times.
  • Export files: Neptune 360 pipe-separated export files read from SFTP with the Read files step.
What SentraBridge can do with AMI meter data (Neptune 360, Sensus)
resourcereadwritechanges onlyfields
Daily readslist—yesRead ID, Meter number, MIU (radio) ID, Account number, Read at, Reading…
Meters (endpoints)list, read one——Meter number, MIU (radio) ID, Account number, Route, Dials, Unit…
Alarms (leak, tamper, no flow)list—yesAlarm ID, Meter, Type, Raised, Cleared
§ Use cases

What cities connect AMI meter data for.

Daily reads to utility billing

Each morning the Neptune 360 export is read from the SFTP folder and good reads are posted to the billing system's meter read import.

Zero-read and error check

Reads with 35 days of no flow, a skipped read or a read error go to the meter team as a list, not into billing.

Leak alerts to customer service

Leak alarms create a service order in utility billing or a ticket in Zendesk, so staff can call the customer.

Meter list against billing

Meters reported by AMI are compared with meters in billing to find radio IDs that don't match an account.

§ How it works

How to connect AMI meter data

  1. 01Get accessAsk the AMI vendor for the daily export file or the utility's API license.
  2. 02Add the connectionSet up an SFTP folder where the AMI system drops its export.
  3. 03Preview real recordsAdd the SFTP connection, plus an API key if the utility has API access.
  4. 04Turn it onPreview one day's file and check meter numbers against billing.
§ Often connected with

AMI meter data and the rest of city hall.

Systems cities commonly connect with AMI meter data, each with its own connector page.

§ FAQ

AMI meter data integration questions

Does Neptune 360 have an API?

Neptune and Sensus license their APIs per utility. Most utilities use the daily export file instead, which SentraBridge reads over SFTP. The Neptune 360 file layout is publicly documented.

How do I get AMI reads into utility billing?

Read the export file, check each read for errors and zero flow, map fields to the billing system's read import layout, then post the reads or write the import file.

Is this connector verified with Neptune or Sensus?

It is built from public documentation and tested on a SentraBridge sandbox. Paths and file columns are confirmed with your own export and account before anything runs.

Connect AMI meter data (Neptune 360,… to the rest.

We'll set up a workspace with your systems in a sandbox and build your first flow with you.