Singapore PUB Mandates DLMS/COSEM for Smart Valve AMI Direct Connect

Singapore’s Public Utilities Board (PUB) issued the Smart Valve Integration Specification v3.0 on 10 May 2026, requiring all tendered smart gate valves to embed the DLMS/COSEM communication protocol stack and support direct connection to PUB’s Advanced Metering Infrastructure (AMI) main station—without gateway conversion. This specification applies to all water network digitalisation projects from 2026 to 2028 and is expected to drive procurement of over 80,000 units. Suppliers in smart water infrastructure, industrial valve manufacturing, and protocol-compliant device integration should monitor this development closely—as it signals a tightening of interoperability requirements in Southeast Asia’s most advanced utility market.

Event Overview

On 10 May 2026, Singapore’s Public Utilities Board (PUB) published version 3.0 of its Smart Valve Integration Specification. The document mandates that all smart gate valves submitted for PUB tenders must natively implement the DLMS/COSEM communication protocol stack and enable direct, gateway-free connectivity to PUB’s AMI central system. The specification covers all water infrastructure intelligence projects scheduled between 2026 and 2028.

Industries Affected

Smart Water Device Manufacturers

Manufacturers producing smart gate valves for export to Singapore will face immediate compliance pressure: DLMS/COSEM stack integration is now non-negotiable for PUB tenders. Impact manifests in firmware architecture redesign, certification timelines, and potential delays in qualification cycles if legacy stacks (e.g., Modbus-based or proprietary protocols) are still in use.

Protocol Stack Software Providers & Integrators

Vendors licensing or embedding DLMS/COSEM protocol stacks—including certified implementations compliant with IEC 62056—will see increased demand. However, impact is conditional: only those stacks validated for PUB’s specific AMI message profiles and security extensions (e.g., AES-128 encryption, TLS 1.2+ handshake) qualify. Generic DLMS libraries without PUB-aligned conformance testing do not meet the requirement.

Export-Oriented Valve System Integrators

Integrators assembling valve actuators, sensors, and communication modules into turnkey solutions must now verify end-to-end DLMS/COSEM interoperability—not just at component level, but across full system behaviour (e.g., event reporting intervals, firmware update triggers, time-synchronised metering). PUB’s specification includes mandatory conformance test cases; integrators lacking in-house DLMS test capability may need third-party validation support.

What Enterprises and Practitioners Should Monitor and Do Now

Track PUB’s official conformance test documentation and certification roadmap

The specification references conformance requirements but does not yet publish the full test suite or accredited lab list. Enterprises should monitor PUB’s procurement portal and DLMS User Association announcements for updates on approved test laboratories and mandatory certification milestones ahead of Q4 2026 tender windows.

Verify DLMS/COSEM implementation scope against PUB’s AMI interface profile

DLMS/COSEM is a broad standard. PUB’s specification constrains usage to specific object classes (e.g., Profile Generic, Activity Calendar), data access methods (Get/Set with selective access), and security attributes. Suppliers must confirm their implementation aligns precisely—not just “supports DLMS”—to avoid rejection during technical evaluation.

Distinguish between specification release and actual tender activation

The specification took effect on 10 May 2026, but current active tenders may still reference earlier versions. Analysis shows PUB typically allows a 3–6 month transition window before enforcing new specs in live bids. Suppliers should cross-check each tender’s referenced specification version rather than assume automatic applicability.

Assess firmware update pathways for existing valve product lines

For manufacturers with field-deployed or pre-certified valves using alternative protocols, evaluating whether remote firmware upgrades can retrofit DLMS/COSEM—or whether hardware-level changes (e.g., modem replacement, secure element integration) are required—is critical. This affects inventory planning, obsolescence risk, and cost-of-compliance calculations.

Editorial Perspective / Industry Observation

Observably, this move reflects PUB’s strategic shift from ‘connected devices’ to ‘interoperable infrastructure’. Requiring native DLMS/COSEM—and eliminating gateway mediation—reduces integration friction, improves data fidelity, and strengthens cybersecurity control. From an industry perspective, it signals that Southeast Asian utilities are adopting EU- and North American-style AMI governance models, where protocol standardisation is enforced at procurement stage rather than left to vendor discretion. Analysis shows this is less a one-off mandate and more a leading indicator: other ASEAN utilities with active AMI rollouts (e.g., Malaysia’s SYABAS, Thailand’s MWA) are likely to follow similar interoperability frameworks within 12–24 months—but with potentially lower technical thresholds. Current observability suggests PUB’s requirement functions primarily as a policy signal, not yet a fully scaled deployment outcome; actual valve deliveries under v3.0 are expected to begin in H2 2027.

This specification marks a formal step toward utility-grade interoperability in smart water hardware. It does not represent a market expansion or technology breakthrough, but rather a tightening of baseline technical eligibility—raising the bar for participation in high-integrity public infrastructure procurement. For suppliers, the implication is procedural, not transformational: success hinges on precise protocol alignment and timely conformance evidence, not innovation in valve mechanics or sensing capability.

Information Source: Public Utilities Board (PUB) Singapore — Smart Valve Integration Specification v3.0, released 10 May 2026. Note: PUB has not yet published the associated conformance test suite or certified laboratory list; these remain pending items for ongoing observation.