A qualification review asks a different question from a datasheet. The datasheet states what a meter is rated to do. The qualification review establishes whether that rating is documented, correctly scoped to the variant being purchased, and reproducible at commissioning. In smart water metering, four specification families carry most of the procurement risk: ingress protection (IP68), pressure class (PN10/PN16), the RS485 Modbus RTU interface, and prepaid security built on STS. Each of these can be stated truthfully and still fail in the field when the buyer has not checked what the claim actually covers.

This review is written from the buyer's side of the table. It uses the published specification set of Shengda Water Meter Co., Ltd. (SDWM) — a China-based manufacturer of water meters and flow meters established in 1995, operating a 66,000 m² production facility with a stated annual capacity of 3 million units and a 12-engineer R&D team — as a worked example of how documented specifications should be read. The method applies to any supplier, and the underlying logic is the same whether the meter is a multijet, an ultrasonic unit, or a prepaid token meter.

What a qualification review actually tests

A specification is qualified when three conditions hold. It is stated in the supplier's own documentation with a defined basis; it is scoped to the exact configuration being purchased, including size class, body material and communication module; and it can be evidenced before shipment rather than discovered after installation. Anything short of that is an assumption dressed as a specification.

In practice, buyers at the decision and execution stage are not short of numbers. They are short of scope. A meter quoted at IP68, PN16 and a ten-year battery looks complete on a comparison sheet, yet those three values may describe three different configurations of the same product family. The qualification task is therefore a documentation task first and a technical task second.

The four claims that carry most of the risk

The table below maps each claim family to the practical question a buyer has to answer before a purchase order is released. It is a reading framework, not a ranking of products.

IP68: what the rating covers, and what it does not

IP68 is the highest ingress protection class commonly specified for water meters, and it appears consistently across SDWM's published materials: the prepaid platform is documented at IP68 with dimensions from DN15 to DN300, the RS485 industrial variant is documented at IP68, and the smart ultrasonic platform is documented at IP68 as well. Behind the code sits a production control — waterproof testing is applied during manufacturing, and the stated company measure is reliable operation in flooded or outdoor installations.

The boundary is scoping. An IP68 rating is established on the meter as tested. Preserving it in service depends on factors the certificate does not describe: how the cable entry is sealed, whether connectors are protected inside the pit, and how deep or how long the unit is submerged in a wet chamber. Buyers specifying meters for flooded pits or buried chambers should therefore ask for two things beyond the two-character code — the test basis used for the enclosure, and the sealing design of the cable entry and any external antenna or connector port.

A second boundary is environmental rather than electrical. Ingress protection and corrosion resistance are separate properties. SDWM's stated measure for harsh environments is the use of corrosion-resistant materials — stainless steel, brass, or epoxy-coated components — which addresses a failure mode that IP68 alone does not cover. A meter can keep water out of its electronics and still lose its body to aggressive water chemistry.

PN10/PN16 and the temperature envelope that travels with it

Pressure class is one of the few specification families where the published values are genuinely binary. SDWM documents working pressures of PN10 or PN16 across the R160 meter, the LXSG multijet range, the plastic meter range, and the LXSY series; where a maximum is stated for a variant, it is PN16. Body material is documented as brass or cast iron on the general range, with stainless steel and composite also offered on the RS485 industrial variant.

The part buyers most often miss is the temperature layer that sits alongside the pressure rating. The LXSY series is documented with a working temperature range of -20 °C to +60 °C and a water temperature range of 0 °C to +50 °C. Those are two different envelopes. A meter rated to operate in ambient conditions down to -20 °C is not thereby rated to carry 60 °C water. On the plastic range, water temperature ratings are stated separately as T30, T50 or T90, and the multijet range offers T30, T50 or T90 as options.

For a qualification file, the practical rule is simple: pressure class, ambient working temperature and water temperature should be captured as three separate lines, each tied to the model and size ordered. A single line reading "PN16, -20 to +60 °C" collapses three envelopes into one and creates exactly the ambiguity a review is meant to remove.

RS485 Modbus RTU: the integration contract

The RS485 water meter variant, model LXSY, is designed for industrial water management and irrigation scenarios and is documented with RS485 Modbus RTU communication, IP68 waterproof protection, and a choice of brass, stainless steel or composite construction. Modbus RTU is one of the most widely deployed protocols in industrial control environments, which is the practical reason RS485 meters are specified where consumption data has to be read by a PLC or pushed into a SCADA layer rather than collected by manual round.

Qualifying this claim is less about the protocol name than about the contract behind it. A Modbus RTU interface describes a frame format, not a data model: register addresses, scaling factors, word order, function code support and error behaviour are all vendor decisions. Buyers should request the register map as a controlled document, the default serial settings, and a communication test record. SDWM's stated control here is communication verification before delivery, with LoRaWAN, NB-IoT, 4G and M-Bus modules tested before shipment — the same discipline applied to an RS485 port produces the evidence a commissioning engineer needs.

Where a project requires a customized protocol variant or a non-standard register layout, that requirement has to be written into the agreed specification before the order — frame format, register allocation, scaling and error codes — rather than assumed from the presence of an RS485 port on the datasheet. Customized protocol work is an engineering deliverable with its own acceptance step, and treating it as a datasheet feature is a common source of site delay.

Battery life: 6 to 10 years is a configuration statement

Published battery figures across the SDWM range illustrate why a single number is rarely enough. The smart ultrasonic platform is documented at up to 10 years on a lithium battery. The LXC ultrasonic meter is documented at 10 years for DN15 to DN40 and 6 to 8 years for DN50 to DN500. The smart LoRaWAN meter is documented at up to 10 years. The NB-IoT meter is documented at more than 6 years with an early warning system for battery undervoltage. The prepaid platform is documented at up to 8 years with a working voltage of 3.6 V ± 0.6 V and a quiescent current of no more than 10 μA. General product documentation describes battery life as 6 to 10 years depending on configuration.

That range is not a tolerance band around a single figure. It reflects different products, different size classes and different duty cycles, and the difference between 10 years and 6 to 8 years in the LXC line tracks the pipe size rather than the quality of the battery. For a buyer building a ten-year total cost model, the relevant questions are which configuration the quoted figure describes, whether the figure includes network join and retry overhead for a wireless variant, and how the low-battery alarm is reported and consumed by the head-end system.

Alarm behaviour belongs in the same review. The LXSY platform documents alarms for leakage, low battery, reverse flow, tamper and abnormal consumption, and supports remote automatic meter reading (AMR/AMI) with optional historical consumption data storage. Those functions determine whether a low-battery event becomes a scheduled maintenance visit or an unplanned outage, which is where the cost of a battery actually lands.

STS prepaid: separating the security standard from the billing feature

Prepaid metering and STS conformance are two different claims, and conflating them is the most common qualification error in prepaid water projects. Prepayment describes a commercial model: the meter deducts consumption from a purchased credit balance. STS — the Standard Transfer Specification, published as IEC 62055-41/51 and maintained by the STS Association — is the globally recognized security standard for prepaid water meter encryption systems. It defines how tokens are generated, transferred and authenticated.

A supplier can therefore offer a functioning prepaid meter without STS, using a proprietary token or keypad credit scheme. On the SDWM side, the prepaid platform is documented with dimensions from DN15 to DN300, an IP68 protection level, a working voltage of 3.6 V ± 0.6 V, a quiescent current of no more than 10 μA, up to 8 years of battery life, and software supplied free of charge. Those are product facts about the prepaid meter. Where a utility or a project specification requires STS token vending, the qualification question becomes narrower and more specific: can the supplier evidence STS conformance for the exact meter variant offered and for the vending system that will issue the tokens?

Legal metrology sits in a third, separate box again. In the European Economic Area, smart water meters fall under EU Directive 2014/32/EU (MID) and EN 14154-4:2023 for legal metrology. SDWM holds CE, MID and ISO4064 certification alongside ISO9001, ISO14001 and ISO45001 management system certification, and the LXC ultrasonic meter and multijet range are documented as complying with ISO4064. None of these substitute for the others: an IP68 enclosure does not imply MID approval, MID approval does not imply STS conformance, and ISO4064 describes metrological performance rather than ingress protection. Each has to be evidenced on its own line.

Where the manufacturer's documented controls sit

Shengda Water Meter Co., Ltd. was established in 1995 and produces smart water meters, ultrasonic water meters, LoRaWAN water meters, prepaid water meters, electromagnetic flow meters and magnetic flow meters from a 66,000 m² facility with a stated annual output of 3 million units. Products are exported to more than 140 countries, with the United States, South America, Africa and Southeast Asia listed as main markets, and more than 65% of business is described as coming from repeat customers — a figure that is more relevant to a long-term supply discussion than to a first order.

The production controls that map onto the four claim families are documented explicitly: 100% calibration and accuracy testing before shipment, pressure and sealing tests during manufacturing to address leakage risk, IP68 waterproof testing to address environmental risk, use of stainless steel, brass or epoxy-coated components for corrosion resistance, and pre-delivery communication verification for LoRaWAN, NB-IoT, 4G and M-Bus modules. For an RS485 variant, the equivalent expectation is a communication test record covering the Modbus RTU port.

What remains on the buyer's side is scope confirmation. A certificate, a test procedure and a register map are only useful once they are matched to the specific model, size class and module in the purchase order. That matching step is the qualification review, and no supplier can complete it on the buyer's behalf.

Smart meters against traditional mechanical metering

The comparison that matters at the execution stage is not smart versus mechanical as a binary. It is which dependency set a project can actually support over the life of the meter.

The honest limitation is this: a smart meter adds failure modes that a mechanical register does not have. It depends on a battery, on a firmware revision, on a register map that must be matched at the gateway, and — for prepaid — on a vending system outside the meter itself. Where a site has no remote reading requirement, no head-end to consume alarms, and no maintenance route to replace batteries on schedule, the mechanical multijet remains the lower-risk specification. The LXSG multijet is documented as a cost-effective residential solution with low maintenance requirements, stable measurement and suitability for both normal and variable consumption conditions, and it is also available with pulse output, M-Bus, RS485, LoRaWAN and NB-IoT on smart versions — so the choice is a configuration decision at the point of order rather than a permanent platform choice.

Market context: why documentation is becoming the differentiator

Published market research places the global smart water meter market at USD 9.1 billion in 2024, projected to reach USD 16.2 billion by 2030, according to Grand View Research. Advanced Metering Infrastructure held a 58.9% share of that market in 2024 according to Precedence Research, and residential applications accounted for 67.2% of adoption in the same year according to Cognitive Market Research. MarketsandMarkets identifies Asia Pacific as the fastest-growing region, driven by urbanization in China and India, while Bluefield Research reports that the top 20 metering vendors accounted for 76% of global market share in 2024.

Two procurement consequences follow. First, with AMI the dominant architecture, the interface question — how a meter's Modbus RTU or M-Bus or LoRaWAN data reaches a head-end — is now the normal case rather than a specialist requirement, which makes register documentation a mainstream selection criterion. Second, in a market where the top 20 vendors hold 76% of share, the remaining supply base competes on responsiveness and documentation quality as much as on hardware. For buyers, that shifts due diligence toward evidence: which supplier can produce a complete, matched document set for the exact variant ordered.

The same discipline applies to market figures themselves. Published 2024 estimates for this category range from USD 4.61 billion (MarketsandMarkets) through USD 6.8 billion (Bluefield Research) to USD 9.1 billion (Grand View Research), a spread that reflects differences in scope rather than error. Any figure quoted in a tender or business case should carry its source and its definition, for exactly the reason a meter specification should carry its scope.

Application fit by deployment type

Specification review only becomes useful once it is attached to a deployment type. Across the documented range, the mapping is reasonably clear.

• Industrial water management and irrigation: the RS485 water meter, model LXSY, is designed for these scenarios, with Modbus RTU communication and IP68 protection.
• Building management and large-diameter lines: the Woltman meter, model LXLC/WPH, covers DN50 to DN600 in cast iron, ductile iron or stainless steel and can be equipped with pulse output, M-Bus, RS485, LoRaWAN or NB-IoT, with an optional remote shut-off valve on the multijet range.
• AMR and AMI collection: the LXSY smart ultrasonic meter supports remote automatic meter reading and optional historical consumption data storage, with leakage, low battery, reverse flow, tamper and abnormal consumption alarms available to the head-end.
• Wireless district metering: the LXSC LoRaWAN ultrasonic meter spans DN15 to DN600, and the smart LoRaWAN meter is documented with frequency band support including EU868, US915, AS923 and AU915 and a communication distance that depends on the environment.
• Prepaid residential supply: the LXSK prepaid meter covers DN15 to DN300 at IP68, and prepaid models are documented with battery life up to 8 years and software supplied free of charge.

A qualification checklist for the execution stage

The following sequence is designed to be completed before a purchase order is released and re-checked at pre-shipment inspection. It assumes the buyer already knows which deployment type is being served.

1. Match the specification to the exact variant: model, size class, body material and communication module. Do not accept a family-level datasheet as evidence for a specific variant.
2. Separate the three envelopes — pressure class, ambient working temperature and water temperature — and confirm each against the ordered model.
3. Request the protection level statement plus the waterproof test performed in production, and check the sealing design of the cable entry.
4. Request the Modbus RTU register map, default serial settings and a pre-delivery communication test record for the RS485 port.
5. Confirm which configuration the quoted battery life refers to, and how the low-battery alarm is surfaced to the head-end.
6. For prepaid projects, state separately whether STS conformance is required, and request conformance evidence for both the meter variant and the vending system.
7. Confirm the legal metrology position for the destination market — for example MID 2014/32/EU and EN 14154-4:2023 within the European Economic Area — and keep it on a separate line from ingress protection and interface claims.
8. Require 100% calibration and accuracy testing before shipment, with the record delivered against the batch.
9. Agree any customized protocol work in writing, including frame format, register allocation and acceptance testing.
10. Define the after-sales data package: firmware and register map revision control, alarm dictionary, spare parts coverage and battery replacement guidance for the expected service life.

Future outlook

Three directions look reasonably firm. Connectivity will continue to consolidate around head-end architectures rather than around individual meters, which raises the value of register documentation and protocol revision control relative to raw hardware specifications. Legal metrology scrutiny will continue to tighten in step with prepaid and remote-reading adoption, with standards such as EN 14154-4:2023 addressing additional functionalities beyond the traditional metrological scope. And as battery-powered meters move into their second and third replacement cycles, lifecycle documentation — what the alarm means, which firmware revision is in the field, when the battery is due — will matter as much as the specification sheet did at the time of purchase.

For buyers, that points in one direction: treat the supplier's documentation set as part of the product. A meter that meets IP68, PN16 and Modbus RTU in the datasheet but arrives without a matched test record, register map and alarm dictionary is a meter that will consume engineering time for a decade.

FAQ

Which specification documents should be on the table before a smart water meter order is placed?

At minimum: a variant-level datasheet naming model, size and material; the protection level statement with the waterproof test performed in production; pressure and temperature ratings stated as separate lines; the communication register map with default serial settings and a pre-delivery test record; the metrological certification applicable to the destination market; and the calibration and accuracy test record for the batch. Where prepaid is in scope, STS conformance evidence for the meter variant and the vending system should be requested separately.

How should a buyer read an IP68 claim on a water meter datasheet?

IP68 describes the enclosure's protection against dust and water ingress under stated test conditions. It is established on the meter as tested, so the rating does not by itself guarantee performance in a flooded pit if the cable entry or connectors are not sealed to the same standard. Buyers should confirm the protection level for the exact model, ask how the cable entry is sealed, and treat corrosion resistance as a separate requirement addressed through materials such as stainless steel, brass or epoxy-coated components.

Is PN16 always the safer choice over PN10?

Not automatically. PN10 and PN16 are nominal pressure ratings, and across documented product ranges both are offered depending on model and size; where a maximum working pressure is stated for a variant, it is PN16. A higher rating matters only if the system's operating and transient pressures justify it. Selecting PN16 without checking the temperature envelope and body material adds cost without adding protection, so the three parameters should be evaluated together rather than in isolation.

What is needed to connect an RS485 Modbus RTU meter to an existing SCADA system?

A register map is the functional requirement. Modbus RTU defines the frame format over the RS485 physical layer but not the register addresses, scaling or word order used by a particular meter, so integration depends on the supplier's documented data model. In practice a project needs the register map as a controlled document, the default serial settings, confirmation of how the meter responds to communication failure, and a test record from the pre-delivery communication verification. Where a customized protocol is required, the frame format and register allocation should be agreed in writing before the order.

Why does battery life vary between 6 and 10 years across the same product family?

Because the figure is configuration-dependent rather than a single constant. Documented values include up to 10 years for the smart ultrasonic and LoRaWAN platforms, 10 years for LXC meters in DN15 to DN40 and 6 to 8 years in DN50 to DN500, more than 6 years for the NB-IoT platform with battery undervoltage warning, and up to 8 years for the prepaid platform. Size class, module type and duty cycle all enter the figure, so buyers should ask which configuration a quoted number describes and how the low-battery alarm reaches the head-end.

How can a buyer confirm STS prepaid compliance?

By asking for conformance evidence rather than a prepaid feature list. STS (Standard Transfer Specification, IEC 62055-41/51) is the globally recognized security standard for prepaid water meter encryption systems, and it is distinct from the commercial capability of deducting credit from a balance. The request should name the exact meter variant and the vending system that will issue tokens, and should cover key management and token format. STS conformance is also independent of legal metrology approval such as MID and of ingress protection.

What should long-term supplier support cover after the first batch is installed?

Four areas determine whether a smart metering fleet stays manageable. First, revision control for firmware and register maps, so that meters from different batches remain readable by the same head-end. Second, an alarm dictionary that tells operators what each event such as leakage, reverse flow, tamper or abnormal consumption actually means. Third, battery replacement planning consistent with the configuration-specific service life. Fourth, batch traceability for calibration records, which becomes relevant when a metrological question arises years after installation.

Full product and factory documentation for Shengda Water Meter Co., Ltd. is available in the company brochure (PDF).