Key IoT Implementation Challenges and How to Solve Them

Problem 1. The project starts with a device, not with a business task

The first of our common IoT implementation challenges is a mistake that occurs right at the beginning of a project – choosing to start it by selecting a meter, radio module, or gateway.

This approach may seem like the quick and logical thing to do, but it often leads to the wrong architecture for clients with different requirements. A resource supplier may need to reduce manual meter reading, a developer may be looking to deliver a building with a ready-to-use remote metering system, a municipality would like to see consumption by site and detect emergencies faster, while a homeowners’ association will be wanting to reduce disputed charges and simplify communication with residents. 

These are different tasks, and they require different data transmission scenarios, platform requirements, and service models.

The solution is to start by describing the desired result. It’s necessary to determine in advance what data should enter the system, how often it’s needed, who uses it, where it’s transmitted next, and what actions are triggered after the data is received. 

For a smart metering project, this may include remote reading, loss control, report generation, preparation of data for billing, battery monitoring, tamper detection, or management of service team visits.

In Jooby RDC products, this logic is covered at several levels, with a product line that includes devices for water, gas, heat, and electricity metering, universal radio modules, LoRaWAN base stations, as well as the software layer – Jooby RDC Dashboard. 

This set makes it possible to design the system not as a single device, but as a chain: meter – radio module – network – server – dashboard – management action.

Problem 2. The existing infrastructure is not ready for smart metering

In many projects, meters are already installed, buildings have long been in operation, access to devices is limited, and data is collected manually. A complete replacement of the device fleet can be expensive, time-consuming, and organizationally complex. This is especially true for multi-apartment buildings, where inspectors have to coordinate access to apartments, return to the same addresses repeatedly, and manually transfer data into accounting systems.

The solution is to consider not only new installation, but also retrofit – equipping existing devices with radio modules and sensors. This approach, the building of sensor networks, is especially useful when meters are still suitable for operation, but data collection needs to be transferred to a remote mode. Before implementation, it’s necessary to check device compatibility with specific meter models, installation conditions, radio connectivity, and power supply requirements.

An excellent example is the project for Moldovagaz subscribers. The supplier’s task was to automate gas metering in multi-storey residential buildings because inspectors often found that subscribers were not at home and had to visit the same addresses repeatedly. 

The project included the installation of 12,000 Jooby RM GM-E radio modules, configuring the automatic transmission of readings, and the deployment of LoRaWAN base stations to transmit data to the server. 

After implementation, the company was able to receive readings remotely, issue bills more accurately, and reduce the workload of inspectors.

This case clearly shows how the problem of access to devices can be solved. Instead of keeping inspector visits and manual reading as the main process, the supplier moves metering into automatic mode and receives data without the subscriber’s constant involvement.

Problem 3. Radio coverage is estimated “by eye”

For LoRaWAN, NB-IoT, and other wireless technologies, stable operation cannot be guaranteed in advance based only on a map or the range stated in a datasheet. 

IoT connectivity issues can be caused by basements, shafts, metal doors, dense development, antenna placement, gateway installation height, and interference level. In new buildings, mistakes often occur because the metering system is designed separately from the engineering infrastructure. In existing buildings, they happen because devices are located in places that are difficult for radio communication.

The solution is to conduct a radio survey and a pilot before scaling. During the pilot, real installation points must be checked: apartments, basements, technical rooms, the roof, boiler room, pumping station, and wells. It’s important to evaluate not only the fact of data transmission, but also radio signal quality, delivery stability, retransmissions, missed messages, and device operation in different modes.

For Jooby RDC LoRaWAN projects, base stations and gateways can be used, and then network and device operation can be tracked in the dashboard. This reduces the risk of a situation where the system has formally been launched, but some devices transmit data unstably.

Problem 4. Data is collected but not used

A common mistake is to assume that an IoT project ends with the transmission of readings for real-time data processing. In practice, value appears only when data enters a convenient platform, is linked to sites, devices, and events, and is then used for decisions, such as issuing a bill, checking an anomaly, replacing a battery, sending a team, or clarifying a balance for a building or district.

The solution to these IoT data management challenges is to design the software layer in advance. The dashboard should show not only readings, but also device status, consumption logs, connection quality, alarms, data gaps, and network status. In Jooby RDC, this role is performed by Jooby RDC Dashboard, which provides access to resource consumption reports and data on device and network status.

Another good example is the pilot project in the Voskhod residential complex in Odesa. The task was to reduce the management company’s resource metering costs, automate data collection, and ensure timely remote transmission. The project included 150 multi-tariff single-phase MTX electricity meters with an integrated LoRa radio module and 60 Jooby radio modules with two pulse inputs for water meters. 

The devices were connected to Jooby RDC Dashboard and data transmitted through LoRaWAN base stations. After implementation, the management company was able to receive accurate readings promptly, reconcile balances faster, and prepare reports.

For developers and management companies, this case is important because the metering system was included as part of the site infrastructure. This makes it possible not to “build on” metering manually after the building is commissioned, but to start working with data in a digital environment immediately.

Problem 5. Integration with billing is postponed “until later”

If an IoT system is not connected to billing, CRM, ERP, MDM, or an internal accounting system, the operator gets yet another separate interface. The data may exist, but employees continue to transfer it manually, reconcile spreadsheets, and correct errors. As a result, part of the automation effect is lost.

The solution is to include integration in the project from the beginning. Right from the pilot stage it’s necessary to define the data format, rules for device identification, site structure, export frequency, persons responsible for error handling, and manual verification scenarios. For resource suppliers, it’s essential to describe in advance which data is considered billing data, what to do with gaps, how to record anomalies, and how to prevent incorrect charges.

The practical approach is as follows: first, a pilot is launched on a limited number of sites, then data quality and the logic of exchange with the accounting system are checked, following which the network is scaled. This sequence reduces the risk of costly rework of the integration after mass installation of devices.

Problem 6. The operating model is not defined

An IoT system must be maintained. Devices have batteries, gateways have communication channels and power supply, the network has zones with different coverage quality, and the platform has users, access roles, and regulations. If no responsible parties are assigned after implementation, the system gradually turns into a set of devices whose condition is unmonitored.

The solution is to define the operating model in advance. It’s necessary to decide who monitors the network, responds to missing data, checks batteries, replaces devices, maintains gateways, is responsible for integration, and works with consumer requests. 

For large projects, condition-based maintenance should be used i.e. the system should show which devices have stopped communicating, where signal quality has deteriorated, which batteries are approaching replacement, and where the number of alarm events has increased.

For homeowners’ associations and management companies, this means less manual coordination. For municipalities, it means more transparent control of distributed infrastructure, and for resource suppliers, it means fewer errors and higher data quality for billing.

Problem 7. Security is treated as a secondary task

IoT projects in utility infrastructure work with consumption data, critical infrastructure facilities, network devices, and remote communication channels. Therefore, security cannot be left until the final stage. Risks include unauthorized access, data substitution, weak network segmentation, unmanaged accounts, outdated firmware, and lack of control over the device lifecycle.

The solution is to embed security at the level of devices, network, platform, and processes. Protected data transmission channels, access rights separation, event logging, key management, update control, and IoT infrastructure segmentation should be used. For smart metering projects, this is especially important as data must not only be collected, but also protected against distortion, loss, and unauthorized access.

How to switch to smart metering effectively

The optimal path depends on the type of site, but the general logic is almost always the same when looking at how to implement IoT successfully. First, goals and data must be described, then a survey conducted, equipment selected, a pilot launched, and connection and data quality checked. After that, the dashboard and integration should be configured, and only then should the project be scaled.

For a developer, the right time for implementation of IoT solutions for businesses is the design or commissioning stage of the building. This makes it possible to plan in advance the installation locations for devices, radio modules, gateways, and communication channels. For homeowners’ associations and management companies, retrofit often becomes the more realistic option, equipping existing meters with radio modules and gradually moving a building or residential complex to remote metering. For a municipality or resource supplier, it’s important to calculate the entire network, not just one site: future connections, server infrastructure, maintenance, and integration.

Jooby RDC products cover different scenarios and network scalability. Radio modules and sensors help automate existing metering points, smart meters are suitable for new sites, LoRaWAN base stations provide data collection at the level of a building, district, or network of sites, and Jooby RDC Dashboard helps work with readings, reports, and device status. 

This allows organizations to implement smart metering gradually, moving from a pilot to several buildings, then to a residential complex, district, or network of sites.

The main problem of implementing IoT integration systems is not “connecting a device.” The real task is to build a stable system in which devices are compatible with the site, connectivity has been tested on location, data enters the platform, integration works with accounting systems, and operations follow clear rules. 

Jooby projects show that smart metering delivers results when the technology solves a specific operational problem. It reduces manual work, improves billing accuracy, speeds up reporting, and makes data available at the right moment. 

For homeowners’ associations, municipalities, resource suppliers, and developers, this is the practical meaning of cloud IoT platforms – not more devices, but a more manageable infrastructure.