An IoT Development Company That Designs for Dropped Connections
Yamama Software is an IoT development company that designs connected systems on the assumption that the network will drop. Factories, ports and warehouses rarely offer a perfect link, so devices keep working, buffer what they could not send, and reconcile when the connection returns. Time-sensitive decisions run at the edge, and telemetry flows into data platforms so readings reach real decisions.
The difference between a connected system that works and one that appears to work is what happens when the connection drops. A factory, a port or a warehouse does not provide a perfect network, so we design assuming interruption: the device keeps working, stores what it could not send, and reconciles when it comes back.
Edge computing
Handling time-sensitive decisions on the device itself rather than sending everything to the cloud and waiting, so the line keeps running even when the link is down.
Device protocols and telemetry
Protocols suited to constrained bandwidth and power, and telemetry designed to stay useful without flooding the network or the storage bill.
Hardware-to-cloud integration
Secure device registration and remote update, and connecting the telemetry stream into data and analytics platforms so what the device measures becomes usable in a decision.
Operating over intermittent links
Local buffering, state reconciliation on reconnect, and defined behaviour during long outages — because the worst design is the one that assumes the network never drops.
Frequently asked questions
Quick facts
- Environments
- Factories, ports, warehouses and other low-connectivity sites
- Edge computing
- Time-sensitive decisions handled on the device itself
- Protocols
- Suited to constrained bandwidth and power
- Device management
- Secure registration and remote update
- Integration
- Telemetry streamed into data and analytics platforms
- During outages
- Local buffering, state reconciliation and defined behaviour for long interruptions
In our designs the device keeps working, buffers locally what it could not send, and reconciles its state when the connection returns, with defined behaviour for long outages.
Handling decisions on the device itself instead of sending everything to the cloud and waiting. It is needed when a decision is time-sensitive, so the line keeps running even when the link is down.
Devices are registered and updated remotely through a secure process, so each update does not require someone on site.
Telemetry is streamed into data and analytics platforms, and designed to stay useful without flooding the network or the storage bill.
Hardware that measures something whose readings never reach a decision, or an environment where you already know the network is unreliable. That is the kind of problem we enjoy.
Have another question?Talk to us
If you have hardware measuring something whose readings never reach a decision, or an environment where you already know the network is unreliable, that is the kind of problem we enjoy.
Start your project