One city wide operating picture
Parking, waste, lighting, metering, manholes and environmental readings arrive in one platform instead of separate departmental systems.
Smart city solutions
Smart city IoT from battery sensors to city cloud platform
NET WIZARDS designs and delivers municipal IoT programmes for the UAE and the wider GCC: battery powered street sensors, LoRaWAN and NB-IoT connectivity, edge processing and a city cloud platform that turns parking, waste, lighting, drainage, metering and environmental readings into action for municipal teams.
01Battery sensors
02LoRaWAN and NB-IoT
03Edge and network server
04City cloud platform
What a smart city programme changes on the ground
A smart city is not a single product. It is a measurement layer over infrastructure the city already owns, connected so that every department works from the same current data.
Battery devices, no civil works
Most street assets are instrumented with battery powered wireless sensors, so deployment avoids trenching, cabling and long road closures.
Field teams sent on evidence
Crews are dispatched when a bin is full, a lamp fails, a manhole cover moves or a meter reading drifts, rather than on a fixed rota.
Scales district by district
A validated sensor, gateway and platform pattern is repeated across zones, keeping configuration and reporting consistent.
The challenge
City systems that cannot see each other
Cities across the GCC are rapidly evolving, and the next stage of transformation depends on data‑driven infrastructure that improves efficiency, sustainability, and quality of life.
Traditional city systems operate in silos, making it difficult for municipalities to gain real‑time visibility or respond proactively to urban challenges. NET WIZARDS delivers end‑to‑end smart city deployments, from intelligent sensors on the ground to citizen‑facing dashboards in the cloud. Our platform unifies IoT devices, edge analytics, and centralized command centers into a single, integrated ecosystem designed for modern urban environments.
In daily operation this appears as collection vehicles emptying bins that are almost empty, drivers circling for a free bay, lighting faults reported by residents rather than by the network, drainage problems discovered after a flood, and consumption data that arrives too late to influence anything. The engineering answer is a measurement layer that reaches existing assets without rebuilding the street.
What the architecture delivers
- Real‑time visibility across all city assets for faster, data‑driven decisions.
- Reduced operational costs through automation and predictive maintenance.
- Improved service delivery with integrated dashboards for utilities, mobility, and public safety.
- Enhanced citizen satisfaction through transparent, responsive digital services.
- Stronger resilience with early detection of failures and proactive incident response.
- Scalable architecture ready for city‑wide expansion and future smart‑city initiatives.
- Government‑grade security ensuring data protection, compliance, and multi‑agency trust.
IoT architecture
From a battery sensor in the street to the city cloud
Every smart city use case follows the same path. Only the sensor and the rule change. That is what makes parking, waste, lighting, drainage, metering and environmental monitoring deployable on one shared platform instead of seven separate systems.
01
Battery sensors
Bins, bays, chambers, meters, lamps, air
02
LoRaWAN / NB-IoT
Gateways and licensed cellular
03
Network server and edge
Decoding, buffering, local rules
04
City cloud platform
History, rules, alerts, APIs
05
Operations and citizens
Command centre, field crews, services
- Layer 1
Battery powered sensors
Long life batteryIP67 and IP68 housingsInterval and event reportingSolar optionParking occupancy sensors, bin fill level units, manhole cover and level sensors, air and noise stations, water and flood probes, lighting controllers and utility meters. Devices are sealed for outdoor use, sleep between readings and report on interval or on event.
- Layer 2
LoRaWAN and NB-IoT connectivity
LoRaWAN Class ANB-IoT and LTE-MAdaptive data rateDeep indoor penetrationLow power wide area radio carries small telemetry messages over long distances. LoRaWAN uses city owned gateways on buildings, poles and towers. NB-IoT uses the licensed mobile network where coverage already exists and no gateway is wanted.
- Layer 3
Gateways, network server and edge
Network serverPayload decodersStore and forwardEthernet, fibre or 4G backhaulGateways forward radio frames to the network server, which handles device joining, keys, deduplication and payload decoding. Edge computing near the gateway filters noise, buffers during backhaul loss and runs local rules for time sensitive events.
- Layer 4
City cloud platform
MQTT and RESTTime series historyRules and alertingMulti agency tenancyDecoded readings are stored as time series against each asset, enriched with location and ownership, then turned into thresholds, alerts, work orders and reports. Open interfaces publish the same data to GIS, billing, ERP and command centre systems.
- Layer 5
Operations, dashboards and citizens
Command centre viewsMobile field appsReports and KPIsRole based accessMunicipal control rooms, utility operators, contractors and citizen facing services work from the same verified data set, with role based access so each agency sees only what it owns.
The diagram and the layer descriptions are written out in text so the architecture is readable by every visitor and by search engines. Site specific drawings, radio plans and payload definitions are produced during the design stage.
Connectivity choice
LoRaWAN or NB-IoT, chosen per asset group
Low power wide area networking is what makes battery operated city sensors practical. The two technologies we deploy most often solve the same problem in different ways, and a single programme frequently uses both behind one platform.
| Consideration | LoRaWAN | NB-IoT and LTE-M |
|---|---|---|
| Network ownership | Private city owned gateways and network server | Licensed mobile operator network |
| Best suited to | Dense sensor estates, campuses, districts and areas needing full control of the radio layer | Scattered assets, early phases and sites already inside good mobile coverage |
| Typical range | Several kilometres urban, further with clear line of sight | Follows operator cell planning, strong deep indoor and underground performance |
| Power profile | Very low, multi year battery life on interval reporting | Low, with power use influenced by reporting frequency and signal conditions |
| Cost structure | Gateway and network investment, no per device subscription | No gateway investment, per device data subscription |
| Deployment note | Gateway placement modelled during survey | Coverage verified per location before rollout |
Satellite backhaul is added where a site sits outside both gateway and cellular coverage, as described under wireless technologies.
Technical delivery
Engineered for the street, the chamber and the car park deck
Radio behaviour, battery life and data quality all depend on the physical installation. Every programme therefore begins with a survey and ends with acceptance criteria agreed before handover.
Radio planning and survey
Coverage is modelled and then verified in the field with test devices, including underground chambers, car park decks and metal enclosures, before any bulk installation.
Security and data protection
Device keys managed in the network server, encrypted transport, segmented networks, role based platform access and tenant isolation for each participating agency.
Device lifecycle
Asset registry, battery and signal health monitoring, firmware updates over the air where the device supports it, and planned replacement based on measured battery trend.
Integration and reporting
Open APIs and MQTT feeds into GIS, billing, asset management and command centre platforms, with reporting agreed against the measurements that matter to each department.
Who it serves
Sectors using the same city platform
Municipalities
District wide parking, waste, lighting, drainage and environmental programmes reporting into one municipal platform.
Industry detailUtilities and energy
Electricity, water and gas metering, network monitoring and loss investigation using the same connectivity layer.
Industry detailLogistics and transport
Yard, gate and access monitoring, plus vehicle and container movement data around city infrastructure.
Industry detailHealthcare estates
Campus environmental monitoring, plant condition and access visibility for large hospital sites.
Industry detailDelivery path
How a city programme is delivered
01
Survey
Assets, chambers, poles, coverage, ownership and existing systems are surveyed, and the measurements each department needs are agreed.
02
Design
Sensor selection, radio choice per asset group, gateway placement, payload decoding, platform structure and integration points are documented.
03
Pilot
One zone or street is instrumented and validated against agreed acceptance criteria, including battery, signal and data quality checks.
04
Scale
The proven pattern is repeated district by district with central configuration and consistent asset naming.
05
Operate
Dashboards, alerting and work order flows are handed to municipal teams, with monitoring of device health and periodic review.
Frequently asked questions
- Should a city use LoRaWAN or NB-IoT for its sensors?
- Both are used, and the choice is made per asset group. LoRaWAN suits dense sensor estates where the city wants to own the radio layer and avoid per device subscriptions. NB-IoT suits scattered assets and locations already inside strong operator coverage, with no gateway to install. Many deployments combine the two behind one platform.
- How long do battery powered city sensors last?
- Battery life depends on the reporting interval, the radio conditions and the temperature at the installation point. Devices are specified for multi year service on interval reporting, and measured battery trend per device is tracked in the platform so replacement is planned rather than reactive.
- Does a smart city rollout require digging up roads?
- In most cases no. Battery powered wireless sensors are fitted to existing bins, bays, chambers, poles and meters, which avoids trenching and long road closures. Civil works are limited to cases where a sensor type genuinely requires a fixed power or wired connection.
- Can the platform work with systems we already operate?
- Yes. Readings are published through open APIs and MQTT feeds, so GIS, billing, asset management, ERP and existing command centre systems can consume the same data. Integration points are defined during design and tested before handover.
- How is data separated between different agencies?
- The platform uses role based access and tenant isolation, so each municipal department, utility or contractor sees only the assets and areas it owns, while the city retains an overall view.
- Where does NET WIZARDS deliver smart city projects?
- NET WIZARDS delivers smart city, IoT and cloud platform projects across the United Arab Emirates and the wider GCC, supported by more than twenty years of engineering work in the MENA region.
Related solutions and products
Smart city programmes are delivered alongside our Industrial Cloud platform, wireless technologies, AI video analytics and Industry 4.0 engineering. Gateways, sensors and metering hardware used in these deployments are listed under products.