For integrators

Got an iotview project? Start here.

Commissioning checklist, gateway compatibility, and answers to the questions every SI asks before bidding.

Contact supportBuy a gateway← Back

Frequently asked

›I'm bidding on a project that specifies iotview. What do I need?

An RTU/PLC speaking Modbus RTU/TCP, MQTT, or DNP3; an iotview-compatible gateway (reference: Benbox); a 4G LTE SIM ≥ 1 GB/month. No public IP, no port forwarding, no SCADA server.

›Can I use my existing RTU brand?

Yes if it speaks Modbus, MQTT, or DNP3 on the uplink. We are protocol-compatible, not vendor-locked. Proprietary protocols can be bridged via Benbox in most cases — email support@iotview.io with the model before bidding.

›How does commissioning work?

Power up, connect to the gateway local UI, enter the project provisioning code, map RTU registers to iotview points (template provided), verify all points on the dashboard, run a simulated outage, hand over.

›Who has access after handover?

Three tiers: end user / operator (daily monitoring), consultant (read-only through defects period), SAINS Telemetry (admin). Contractors do not retain dashboard access after handover — security policy.

›How long does a single-site project take?

Two weeks from project registration to handover for one pump room or tank: 1 day register, 4 days panel + pre-config, 1 day install, 1 day commissioning, 1 day training.

Supported point types

Out of scope: video / camera streams.

Need a project provisioning code?

Provisioning codes are issued only to the appointed consultant or SAINS Telemetry — contractors cannot self-register. If you have one already, head to your gateway's local UI to enter it.