AMI Head-End System (HES) Communication Metrics
This dataset provides granular communication performance metrics for smart meters managed by an AMI head-end system, including read success rates, latency, signal strength, mesh network hop count, and firmware status. It enables utilities to monitor device health, optimize network performance, and manage firmware updates across geographically distributed assets.
Sample rows
preview · 8 of 200 rows · all 14 columns| record_idstring | network_typestring | signal_strength_rssi_dbmfloat | firmware_update_pendingboolean | device_statusstring | meter_idstring | collection_timestampdatetime | read_success_ratefloat | average_latency_msfloat | max_latency_msfloat | hop_countinteger | firmware_versionstring | location_latitudefloat | location_longitudefloat |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| rec-0001 | ethernet | -3.1 | false | active | MTR-1001 | 2024-05-01T09:04:21Z | 99.9 | 8.7 | 19.2 | 0 | 6.0.0 | 41.881832 | -87.623177 |
| rec-0002 | ethernet | -4.2 | false | active | MTR-1002 | 2024-05-01T09:14:55Z | 97.5 | 12.3 | 22.1 | 0 | 5.0.0 | 40.712776 | -74.005974 |
| rec-0003 | ethernet | -2.3 | false | active | MTR-1003 | 2024-05-01T09:29:32Z | 98.8 | 7.9 | 17 | 0 | 6.0.1-rc1 | 29.760427 | -95.369804 |
| rec-0004 | ethernet | 0 | false | active | MTR-1004 | 2024-05-01T09:35:17Z | 100 | 4.2 | 8.7 | 0 | 5.0.0 | 33.448376 | -112.074036 |
| rec-0005 | ethernet | -1.9 | false | active | MTR-1005 | 2024-05-01T09:40:12Z | 99.7 | 6 | 14.2 | 0 | 5.0.0 | 34.052235 | -118.243683 |
| rec-0006 | ethernet | -3.7 | false | active | MTR-1001 | 2024-05-02T09:04:21Z | 99.9 | 9.1 | 18.6 | 0 | 6.0.0 | 41.881832 | -87.623177 |
| rec-0007 | cellular | -94.2 | false | active | MTR-1006 | 2024-05-01T10:05:33Z | 86.1 | 33.7 | 76.2 | 5 | 2.7.9 | 39.952583 | -75.165222 |
| rec-0008 | cellular | -116.4 | false | active | MTR-1007 | 2024-05-01T10:11:21Z | 71.8 | 41.2 | 101.3 | 2 | 2.5.3 | 32.776665 | -96.796989 |
| rec-0009 | cellular | -98.7 | false | active | MTR-1008 | 2024-05-01T10:19:44Z | 77 | 49.5 | 113.1 | 3 | 2.5.3 | 37.774929 | -122.419418 |
| rec-0010 | cellular | -88.2 | true | maintenance | MTR-1009 | 2024-05-01T10:25:19Z | 81.3 | 65.7 | 158.8 | 6 | 2.5.3 | 29.424122 | -98.493629 |
| rec-0011 | cellular | -82.4 | false | active | MTR-1010 | 2024-05-01T10:31:05Z | 91.2 | 37.2 | 78.5 | 4 | 2.7.9 | 47.606209 | -122.332069 |
| rec-0012 | cellular | -76.1 | true | maintenance | MTR-1011 | 2024-05-01T10:36:54Z | 88.4 | 73.6 | 200.1 | 7 | 2.7.9 | 25.761681 | -80.191788 |
| rec-0013 | cellular | -97.5 | false | active | MTR-1012 | 2024-05-01T10:42:39Z | 79.2 | 59.8 | 120.1 | 5 | 2.5.3 | 36.169941 | -115.139832 |
| rec-0014 | cellular | -110.5 | true | maintenance | MTR-1013 | 2024-05-01T10:48:23Z | 83.5 | 90.2 | 210.4 | 7 | 2.5.3 | 39.739235 | -104.99025 |
| rec-0015 | rf | -65.4 | false | active | MTR-1014 | 2024-05-01T11:06:07Z | 65.1 | 29.3 | 45.7 | 3 | 3.0.1 | 38.627003 | -90.199402 |
| rec-0016 | rf | -71.2 | false | active | MTR-1015 | 2024-05-01T11:10:44Z | 85.7 | 20.1 | 88.1 | 4 | 3.1.0-beta | 42.360082 | -71.05888 |
| rec-0017 | rf | -90.3 | false | active | MTR-1016 | 2024-05-01T11:15:22Z | 75.2 | 54.1 | 110.2 | 5 | 3.0.1 | 45.512794 | -122.679565 |
| rec-0018 | rf | -65 | false | active | MTR-1017 | 2024-05-01T11:20:07Z | 66.8 | 29.7 | 70.5 | 3 | 3.2.0-rc1 | 41.256538 | -95.934502 |
| rec-0019 | rf | -111.4 | false | inactive | MTR-1018 | 2024-05-01T11:25:55Z | 59.8 | 86.2 | 320.4 | 5 | 2.9.7 | 33.749001 | -84.387978 |
| rec-0020 | rf | -87.1 | false | inactive | MTR-1019 | 2024-05-01T11:31:44Z | 62.5 | 37.6 | 110.3 | 3 | 3.0.1 | 39.768403 | -86.158068 |
What the 200 rows show
from the 200-row sampleEthernet (network type) stands out: mean signal_
- 37%firmware_
update_ pending = true - -97.5median signal_
strength_ rssi_ dbm - 77.6median read_
success_ rate - 64.3median average_
latency_ ms - 138.1median max_
latency_ ms - 4median hop_
count
Median -97.5, from -150.0 to 0.0.
- string 5
- integer 1
- float 6
- datetime 1
- boolean 1
Columns
14 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 5 columns | |||
record_id | string | Unique identifier for each communication metric recordunique | rec-0001 |
meter_id | string | Unique identifier for the smart meter device | MTR-1001 |
firmware_version | string | Current firmware version installed on the meter device | 6.0.0 |
network_type | string | Type of network used by the meter (e.g., mesh, cellular, RF)mesh · cellular · rf · ethernet | ethernet |
device_status | string | Current operational status of the meter deviceactive · inactive · fault · maintenance | active |
| Numbers 7 columns | |||
read_success_rate | float | Percentage of successful meter reads during the collection interval (0-100)0 to 100 | 99.9 |
average_latency_ms | float | Average communication latency in milliseconds for meter reads0 or more | 8.7 |
max_latency_ms | float | Maximum observed communication latency in milliseconds for meter reads0 or more · optional | 19.2 |
signal_strength_rssi_dbm | float | Received Signal Strength Indicator (RSSI) in dBm-150 to 0 | -3.1 |
hop_count | integer | Number of hops in the mesh network from meter to head-end system0 or more | 0 |
location_latitude | float | Latitude of the meter device's installed location-90 to 90 · optional | 41.881832 |
location_longitude | float | Longitude of the meter device's installed location-180 to 180 · optional | -87.623177 |
| Dates and times 1 column | |||
collection_timestamp | datetime | Timestamp when the communication metrics were collected | 2024-05-01T09:04:21Z |
| True or false 1 column | |||
firmware_update_pending | boolean | Indicates if a firmware update is pending for the meter device | false |
Use it for
An energy dashboard
The firmware_
update_ pending rate, signal_ strength_ rssi_ dbm by network_ type and a breakdown of device_ status. Excel, Power BI or Tableau. Why do the 35 ethernet rows have a mean signal_
strength_ rssi_ dbm of -2.4? A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
- Records200rec-0001-3.1ethernetrec-0010-88.2cellularrec-0012-76.1cellular
A software demo
Believable records with meter_
id, collection_ timestamp and read_ success_ rate to fill a screen in front of a buyer.
This dataset200 rows14 columns
Yours1,000 rows14 columnslocation_latitude: UK only
blueprint · ami-head-end-system-hes-communication-metrics
Behind this dataset
Same schema. As many rows as you need.
These 200 rows came out of a blueprint — 14 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.
Rules it was built with
- Meter ID and communication module MAC address
- Read success rate percentage (target >99%)
- Latency in milliseconds for meter-to-HES communication
- RSSI (Received Signal Strength Indicator) in dBm
- Hop count for mesh topology (meters acting as repeaters)
- Parent node/collector ID in mesh network
- Firmware version and Over-The-Air (OTA) update status
- Communication technology (RF mesh, cellular LTE/5G, PLC)
Open the blueprint in Data Factory
1 credit per row. Preview 20 rows free. Buy rows for the full run.
- Exports
- CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
- Licence
- yours to use, including commercially
- API slug
- ami-head-end-system-hes-communication-metrics