1. Field meter
State the hydraulic duty, DN, pipe orientation, water and temperature conditions, local display, power source, physical access and any valve-control need. Ask for the exact meter model and its interface documentation.
Remote Reading Buyer Guide
Specify the complete reading system before choosing a smart water meter
“Remote reading” can describe very different field devices, networks and platforms. This guide helps utilities, contractors and distributors compare options and send an RFQ that identifies who supplies, operates and tests every link in the data path.
Architecture First
Trace one reading from the meter to the buyer's system
Ask each bidder to draw the exact proposed route. The meter, radio or wired interface, network, collector, server and application may come from different parties.
2. Communications
Name the technology and version, frequency or cellular bands for the destination country, antenna and pit constraints, gateway or mobile operator, activation method, and who pays recurring network charges.
3. Data destination
Identify the head-end, billing system, MDMS or API owner. Request sample messages, field definitions, timestamps, units, event codes, credentials, data retention and a test account before bulk ordering.
Technology Comparison
Compare connection models, not marketing labels
The choices below are procurement paths, not claims that every Xiangyuan model supports every protocol. The quoted device and software version must be checked individually.
NB-IoT: operator-managed cellular route
Confirm service availability and supported bands at each installation site, SIM or eSIM ownership, provisioning, tariff, roaming policy, reporting schedule and downlink needs. Test coverage inside representative meter pits. NB-IoT is standardized by 3GPP; that does not guarantee coverage or battery life for a particular installation.
LoRa radio: clarify whether it is LoRaWAN
A product described only as “LoRa” may use a project-specific radio and concentrator rather than a LoRaWAN network. Ask for the exact stack, gateway, network server, regional channel plan, activation, keys, payload decoder and ownership. LoRa Alliance regional parameters vary by regulatory region; do not assume a device configured for one market works in another.
Wired or wireless M-Bus: require model proof
If a tender specifies M-Bus or OMS, identify the exact wired or wireless profile, gateway, message format and security requirements. The OMS Group publishes specifications for meters, sensors and gateways; this guide does not assert that Xiangyuan's quoted product has OMS certification or any M-Bus interface without model-level evidence.
Legacy-network check: Xiangyuan also lists GPRS remote-reading products. Before choosing a 2G-dependent deployment, obtain the destination operator's current 2G service and sunset policy in writing; the presence of “GPRS” in a catalog is not evidence of long-term service availability.
Site Survey
Test the difficult locations before locking the design
Desktop coverage maps are a starting point, not proof that an underground or shielded meter can transmit at the agreed schedule.
Representative pits
Choose samples from indoor risers, underground chambers, metal-covered boxes and the furthest network edges. Record installation depth, lid material, antenna position, signal observations and whether readings arrive at the target platform.
Power and reporting
Specify the interval for normal readings, alarms and retries, plus the number of required downlink operations. Request a model-specific battery-life calculation using the agreed coverage and message schedule rather than a headline life claim.
Failure and recovery
Agree what happens after loss of coverage, power interruption or gateway outage: local storage, timestamping, retransmission, duplicate handling, alarm priority, maintenance access and whether valve commands require confirmation.
Interoperability
Specify the messages the platform must actually understand
Even where two devices share a radio technology, the application payload and operational responsibilities can differ. Ask for a small end-to-end demonstration using the proposed hardware and software versions.
Data dictionary
Request register or payload maps for cumulative volume, units, meter identity, time, battery state, alarms and any valve status. Define endian order, scaling, encoding and version control where applicable.
System boundary
Document who owns the device keys, SIMs, gateways, network server, decoder, API, hosting, backups and user access. State whether integration deliverables include source documentation, test messages and operating procedures.
Acceptance test
Test a physical reading against the transmitted value, late or missed reports, alarms, replacement of a meter, commissioning and decommissioning, security handover and recovery after an outage. Record pass criteria and a named responsible party.
Ready-to-Send RFQ
Give every supplier the same project brief
Copy these fields into the technical schedule and ask each bidder to answer “included”, “excluded”, “deviation” or “to be confirmed”.
Meter and location
Application, water type, DN and connection, minimum/normal/peak flow, pressure, temperature, orientation, pit or riser details, quantity, destination country and required model-level documents.
Network and data
Proposed technology and version; bands or channel plan; operator or gateway; SIM/key ownership; coverage test; normal and alarm reporting intervals; data map; API or head-end target; cybersecurity responsibilities.
Commercial and acceptance
Meter, communications and platform line items; recurring charges; sample and pilot scope; inspection; installation and commissioning; acceptance tests; spares; warranty; delivery; training and support exclusions.
Buyer Questions
Resolve these before a purchase order
Does “LoRa” mean LoRaWAN?
No. Request the exact protocol stack, LoRaWAN version if applicable, regional parameters, network server and evidence for the quoted model. A private LoRa implementation cannot be assumed to interoperate with a LoRaWAN network.
Is NB-IoT coverage enough to guarantee remote reading?
No. Verify the chosen operator and bands at representative installed locations, then test the agreed reporting and alarm schedule end to end. Pit construction, antenna location and network configuration matter.
Can a protocol label prove platform compatibility?
No. Require the actual payload or register map, decoder or API specification, credentials and a successful test from the meter to the buyer's platform using the proposed versions.
Standards and Source Notes
Check the primary documents against the exact project
These references explain technology and procurement context. They are not certificates for a Xiangyuan product or evidence that a particular model has a specified radio, approval or service life.
Cellular IoT
3GPP: Standards for the Internet of Things covers NB-IoT technology and power-saving concepts. The project must still verify the local operator, bands, site coverage and device configuration.
LoRaWAN and region
LoRa Alliance: standards overview, smart utilities and regional parameters show why protocol version, regional channel plan and network ownership must be specified.
M-Bus and metrology
OMS Group specifications define communication profiles; OIML R 49-1:2024 is a metrology reference for water meters. Request current documents for the exact quoted model and destination.
Model-level verification: Xiangyuan lists NB-IoT and LoRa remote water meter families, but bands, radio stack, approvals, battery life, payload, pricing and delivery vary by configuration. This page makes no unverified claim about a specific unit. Ask sales for the current datasheet, protocol documentation and relevant certificates before tender submission.