A successful radio transmission is only one step toward a reliable bill. Water-metering projects need a complete data path that preserves device identity, time, units and the relationship between physical assets and customer accounts.

Collection and device operations

A head-end system, or HES, commonly handles communication with devices or network services and receives readings and events. Product boundaries vary, so a procurement specification should describe functions rather than rely only on the HES label. Identify who manages device onboarding, configuration changes and failed communication.

For a WE RICH product comparison, the Head End System (HES) brings collected readings and communication status into an operational view, with interfaces agreed for the project.

For a WE RICH product comparison, the LoRaWAN gateway forms part of the communication path between compatible meters and the application; coverage and backhaul must be planned for the site.

Validation and usable data

Meter data management functions can include validation, estimation, editing and preparation of data for downstream systems. Record the original value and distinguish it from corrected or estimated data. Check timestamps, duplicate messages, resets and unit conversions. A received total should not become a billing input until it is associated with the correct account and period.

Specify interfaces and ownership

Define field mappings, export formats, error responses and reconciliation reports. Test the complete path using representative exceptions, including a meter replacement and a missing reading. Clarify data retention, access roles and export rights. An integration should be accepted on the basis of usable business records, not a screenshot showing that a message arrived.

Practical checklist

  • Map every required data field.
  • Retain original values and quality flags.
  • Test a complete billing cycle.

Frequently asked questions

Are HES and MDM always separate products?

No. Functions may be combined; define the required responsibilities explicitly.

Should estimated data be marked?

Yes. Keep them distinguishable from measured and corrected values.

Does an API guarantee integration?

No. Field mapping, semantics and exception handling still need testing.

Related articles

References and technical reading

Product capabilities depend on the model and its documentation. Confirm installation and performance requirements for the project.

Explore the products for this application

Confirm the selected model’s approved flow range, installation conditions and available communications before specifying it. These options support product evaluation; they do not replace site testing.