IoT

Device systems that remain operable when the link does not.

We design IoT programmes around the gateway, the data contract, and the people who have to diagnose a silent node at 2 a.m.

Where it is used

Meters, PLCs and environmental sensors into a store you control, with alerts that mean something.

Retail, estates or multi-building campuses where each site has a gateway and a local fallback, not a single cloud hope.

A device identity, OTA path and operator console for hardware you already manufacture.

Ingestion: MQTT, Modbus, BACnet, REST or a mix — named, versioned, and testable.
Edge: Gateways that buffer, filter and fail visibly rather than drop packets into a void.
Identity: Device certificates or tokens with a revocation story, not a shared password in a firmware blob.
Operations: Dashboards, alert routes and a remote session model your staff can be trained on.
Residency: Singapore or on-premise storage when the data should not leave the building or the jurisdiction.

01
Protocol census
What already speaks, what must be translated, and what we will refuse to scrape from a vendor GUI.
02
Data contract
Payloads, units, retention and who is allowed to change a tag name after go-live.
03
Pilot site
One building or line that is ugly enough to be representative.
04
Fleet operations
Rollout, certificate rotation, and a support runbook.

List the protocols and where the data must live. We will say what a first site should look like.