For consultants

Specify cloud telemetry the right way.

Drop-in clauses for the cloud monitoring section of your telemetry submittal. Brand-agnostic on RTU, open protocols only, gateway-led — designed to pass SAINS Telemetry approval on the first pass.

Email specs@iotview.io← Back

The principle

Specify the architecture, not the IP address.

A fixed IP or VPN endpoint in the drawing can only be satisfied by the RTU vendor's own monitoring server — so “comply with the drawing” silently becomes “buy that vendor's platform contract.” The RTU brand and the monitoring platform get bundled. Specify open protocols, an outbound-only gateway, and the cloud capabilities the asset owner needs — and the endpoint is issued at commissioning. Any RTU brand still competes; the platform stays owner-controlled.

Reference clauses (v0.2)

Excerpts. Full specification document available on request — also covers I/O sizing, panel rating, power/UPS, and warranty language.

  1. §1

    RTU / PLC — no brand mandated

    No RTU/PLC brand shall be mandated. Any device supporting an open uplink protocol — Modbus RTU/TCP, MQTT, or DNP3 — is acceptable. Proprietary protocols are permitted only where bridged to an open protocol at the gateway. Brand-and-platform bundling shall not be specified.

  2. §2

    IoT Gateway

    Cellular (4G LTE) uplink with optional Ethernet/Wi-Fi backup. TLS-encrypted MQTT. ≥7 days local buffering during connectivity loss, with automatic backfill on restoration. Reference: Benbox.

  3. §3

    Communication — outbound only

    4G LTE SIM with M2M data plan ≥ 1 GB/month. Outbound TCP/443 (HTTPS) and TCP/8883 (MQTT/TLS) only. No fixed public IP address, inbound port-forwarding, or site-to-site VPN shall be specified or required.

  4. §4

    Endpoint — issued at commissioning, not drawn

    The monitoring platform endpoint and project provisioning code shall be issued by the Asset Owner / SAINS Telemetry at commissioning. It shall NOT be specified by IP address or VPN profile on the submission drawing. (Where SAINS has standardised a platform for the project, the drawing may cite the SAINS-nominated platform by reference.)

  5. §5

    Cloud monitoring platform — specified by capability

    Web access without client software or VPN; multi-tier role-based access (operator / consultant / asset-owner admin); ≥12 months trend retention; alarm notification; open data-export API. Specifying these capabilities — rather than a fixed IP or a named RTU-vendor platform — keeps the tender open and the architecture owner-controlled.

  6. §6

    Commissioning

    Per published procedure at https://iotview.io/sains/integrators. Pre-handover checklist includes a simulated outage to verify buffered data backfills correctly.

Want a project-specific draft?

Send us the development name, monitored points (pumps / tanks / flows), and submission deadline. We'll return a project-tailored spec within 2 working days.

specs@iotview.io →