Itron: Utility metering, communications and data systems for resource management

Itron supplies utility metering, communications and data systems, including Cyble modules for compatible mechanical water and gas meters.

Best for: Utility meter reading and compatible mechanical-meter retrofits.
Less suited to: Assuming any Itron meter provides open local Modbus access or universal retrofit compatibility.
Deployment: Model-specific field equipment connected to the matching collection or automation system.
Data in: Measurements and statuses through the exact documented model interfaces.
Pricing: Current project pricing was not established in the reviewed sources.

Overview

Itron supplies meters, communications and software for utilities and cities. Its company overview spans electricity, water and related infrastructure, so the company name alone is not a sufficient specification for a building integration. The collection path depends on the meter, communication module, geography and utility deployment.

For existing mechanical water or gas meters, Cyble 5 provides a concrete retrofit example. It adds a communication module to compatible meter hardware rather than replacing the mechanical measuring element. This separates the metrological instrument from the network used to retrieve its index.

Offering

Cyble 5 is a clip-on communication module for Itron Cyble-ready mechanical water meters and c-Series gas meters. The named compatibility boundary matters: it is not a universal optical reader for any meter face. The manufacturer describes wireless M-Bus mobile reading and LoRaWAN or Sigfox collection options for IoT networks.

Specify the exact module variant and enabled collection mode alongside the underlying meter model. A listing of multiple protocols does not establish that every ordered unit exposes every mode simultaneously. The mechanical fit, initial index and installed network must all be checked before the reported total can be trusted.

Technology

The Cyble 5 specification distinguishes drive-by automatic meter reading from infrastructure-based collection. These approaches have different operational consequences. A drive-by round delivers readings when a collector passes; an IoT deployment needs network coverage, device provisioning and a working data-delivery path. Neither method automatically provides a local Modbus endpoint.

Commissioning should compare the received index with the physical meter and retain the volume unit and multiplier. A plausible counter value is not sufficient if it belongs to the wrong meter or represents a different volume increment. Radio availability also does not establish permission to read a utility-owned device or access its encryption material.

Markets

Itron’s company site positions its offering around utility and city infrastructure. Cyble 5 is particularly relevant to a retrofit where a compatible mechanical meter remains in service and the aim is to collect its readings remotely. A building owner should first establish who owns that meter and which party controls the communication system.

This is a different procurement problem from selecting a general-purpose industrial energy meter for an open RS485 bus. The physical measuring technology, radio network, data access and billing arrangement may be supplied by different parties. Comparing those boundaries makes the available integration path clearer than a company-wide protocol badge.

Company

Itron’s history dates its origin to 1977, when engineers in Hauser Lake, Idaho developed more efficient meter-reading methods. The current locations page identifies the corporate headquarters in Liberty Lake, Washington, and distinguishes offices in other countries. Regional catalogue URLs therefore should not be mistaken for separate corporate headquarters.

The same history records acquisitions that expanded the meter and software portfolio. This profile keeps the company identity broad while binding the technical claims to Cyble 5. It does not infer that acquired product families share the same protocol stack, support contract or device configuration procedure.