IKB
Engineering inside Innsbruck's city-wide IoT build. Infra, devices, codecs. Handed over completely, still on call.
IKB (Innsbrucker Kommunalbetriebe) is the municipal utility of Innsbruck, Austria, water, energy, waste, telecom. They had a Smart City build underway and needed engineering hands to help take it to city scale.
Overview
IKB (Innsbrucker Kommunalbetriebe) is the municipal utility of Innsbruck, Austria, water, energy, waste, telecom. They had a Smart City build underway and needed engineering hands to help take it to city scale.
What's the challenge?
Help take an in-flight Smart City build to city scale. Real streets, real devices from real vendors, none speaking the same dialect. LoRaWAN backbone on Kubernetes to extend and scale. Multi-manufacturer hardware to evaluate and integrate. Per-device uplink and downlink payloads to decode. Datasheets that did not always match the hardware.
Every device, its own dialect. And every device, its own clock.
IKB had work underway when we joined. Extending the LoRaWAN backbone to production scale was tractable. Writing codecs against datasheets that did not match the hardware in front of us was not. Every manufacturer handled packets its own way. Some devices spoke daily, some quarterly, some only when a water meter detected a leak. A wrong byte cost a full cycle to verify. We built a per-vendor codec workbench, captured real packets, replayed them offline.
What We Did
We joined IKB’s in-flight Smart City build as part of the engineering taking it to city scale, against multi-vendor reality where no two devices speak the same dialect. Our lane was infrastructure and devices: extending the Kubernetes cluster running ChirpStack, field-testing water meters and cargo-bike trackers, and writing uplink decoders and downlink encoders. We handed the platform over to IKB’s in-house team completely and stayed on as external support for new device integrations, the Grafana stack, field connectivity, and manufacturer calls.
Outcomes
What We Learned
City-scale IoT is a coordination problem dressed up as a hardware problem. Protocols are tractable. Datasheets are not. Every vendor documents things a little differently, every payload is its own dialect. Tight coordination across the whole stack is the only thing that works. The free LoRaWAN payload codec tester packages the offline fixture workflow we used for those device dialects.
Want outcomes like this?
Tell us what you're building. We'll tell you whether we're the right team for it.
Get in touch