OUR OFFICE
Rukan Great Wall, Jl. Green Lake City Boulevard No.63 Blok B, RT.002/RW.008, Petir, Kec. Cipondoh, Kota Tangerang, Banten 15146 Indonesia
Want to learn more?
Contact UsOUR OFFICE
Rukan Great Wall, Jl. Green Lake City Boulevard No.63 Blok B, RT.002/RW.008, Petir, Kec. Cipondoh, Kota Tangerang, Banten 15146 Indonesia
Want to learn more?
Contact UsA water utility may have thousands of meters installed across a city, yet still depend on field personnel to collect consumption readings. A factory can operate dozens of machines without having a centralized view of their energy consumption. Even a modern commercial building may struggle to consolidate data from its electricity meters, water systems, and environmental sensors.
The equipment already exists. What is often missing is a reliable way to connect it, collect usable information, and integrate that information into daily operations.
This is the problem that an IoT solution provider in Indonesia is expected to solve.
Internet of Things (IoT) technology enables physical devices to exchange data with digital systems. Its business value, however, depends on how well that technology fits existing infrastructure, operating conditions, and organizational requirements.
For Indonesian businesses considering IoT adoption, understanding the difference between purchasing connected devices and implementing a complete IoT system is an important starting point.
An IoT solution provider designs, deploys, or integrates connected technologies that allow organizations to monitor physical assets and use the information collected from them.
The National Institute of Standards and Technology (NIST) defines an IoT device in terms of its interaction with the physical world and its ability to communicate through a network interface. Sensors, actuators, and connected monitoring equipment can therefore form part of a much larger IoT system (NIST, n.d.).
In a commercial deployment, a device rarely operates in isolation.
Consider a water meter equipped with a remote reading sensor. The sensor captures consumption information, but that information must still travel through a communication network, reach an application, and become accessible to the people responsible for monitoring or billing.
Someone must ensure that these components work together.
That responsibility may involve a hardware manufacturer, telecommunications provider, software developer, or system integrator. Some companies specialize in one area, while others coordinate several layers of the implementation.
A device supplier focuses primarily on providing equipment. This may include sensors, communication modules, gateways, or controllers.
A connectivity provider supplies the network services through which those devices communicate.
An IoT platform provider develops software for receiving data, managing connected devices, and supporting application-level processing.
A system integrator connects these elements to create a working solution for a particular operational environment.
These roles sometimes overlap. A device manufacturer may also provide software, while a system integrator may distribute hardware from several manufacturers.
For customers, the distinction becomes important when determining who is responsible for compatibility, deployment, troubleshooting, and long-term operation.
A supplier may confirm that a sensor supports LoRaWAN. That alone does not establish whether the sensor will communicate reliably from a basement meter room or an underground installation.
Those questions require network assessment and system-level engineering.
A typical IoT deployment connects physical measurements to software applications through several technical layers.
Sensors and measuring instruments capture physical or operational conditions.
Depending on the application, these measurements can include water consumption, electrical parameters, temperature, humidity, pressure, flow, or equipment status.
Some instruments transmit measurements directly through a built-in communication interface. Others require additional modules or converters to make their data accessible.
Existing industrial equipment may already support interfaces such as Modbus RTU or Modbus TCP. In these cases, integration can sometimes be achieved without replacing the entire instrument.
Compatibility must still be verified. Having a communication port does not guarantee that every required measurement is available or correctly documented.
Once measurements have been collected, they must be transmitted.
The appropriate communication technology depends on the location, frequency, and nature of the data.
A building with established Ethernet infrastructure may have different requirements from a water distribution network covering residential areas.
For battery-powered sensors transmitting relatively small messages over long distances, LoRaWAN may be appropriate.
The LoRa Alliance describes LoRaWAN as a low-power wide-area networking protocol designed to connect battery-operated devices. Its architecture uses gateways to relay messages between end devices and a central network server (LoRa Alliance, n.d.).
This architecture can support applications such as smart metering and distributed environmental monitoring.
However, long-range communication does not mean unlimited coverage.
Buildings, installation depth, antenna placement, interference, and device configuration affect actual performance. Communication coverage should therefore be assessed against the physical conditions of the deployment.
Applications requiring continuous high-bandwidth transmission or strict low-latency control may be better served by other technologies.
Receiving data is only part of the process.
The application must interpret incoming messages, associate readings with the correct devices, store measurements, and present information in a usable format.
A utility operator, for example, may need consumption histories grouped by customer account. A facility manager may need electricity usage by building or tenant. A maintenance engineer may be more interested in equipment abnormalities than historical consumption.
The underlying data can be similar, but the application must reflect the decisions users need to make.
Dashboards may provide historical trends, configurable alerts, reports, and integration with other systems.
The usefulness of these features depends on data quality. A visually sophisticated dashboard cannot compensate for missing readings, incorrect units, or unreliable device communication.
IoT applications differ across industries because the problems they address are different.
In water utilities, the priority may be obtaining dependable meter readings across a geographically distributed customer network. In manufacturing, the objective may be understanding equipment conditions or utility consumption.
A suitable implementation begins with these operational requirements rather than selecting technology first.
Water distribution operators must maintain accurate records while managing infrastructure spread across different locations.
Manual meter reading requires personnel to visit installations, record values, and transfer those readings into an operational or billing system.
Automated Meter Reading (AMR) introduces a method for collecting compatible meter data remotely.
Depending on the meter design, a communication device may be integrated into the meter or installed as an additional reading module.
Collected readings can then be transmitted to a central application for monitoring and further processing.
This can reduce dependence on routine manual collection and provide more consistent access to consumption information.
There is an important distinction, however, between measuring consumption and identifying physical water losses.
A customer meter records consumption at a particular point. Detecting leakage within a distribution network may require additional information, including inlet and outlet measurements, pressure monitoring, time-based consumption patterns, and an appropriate analytical method.
An unusual consumption pattern may suggest a problem. It does not automatically establish the location or cause of a leak.
This distinction matters when organizations evaluate smart water technologies and the outcomes they can realistically deliver.
PT IoT Kreasi Indonesia provides Smart Water Monitoring solutions, covering applications such as water consumption, flow, pressure, and monitoring across utility and industrial environments.
Energy monitoring presents a different challenge.
A commercial facility may already have electricity meters installed, but operators may only review readings periodically. This makes it difficult to understand when and where consumption changes occur.
Connecting compatible meters to a monitoring platform allows teams to examine consumption trends across specific areas or equipment.
The information can support investigations into unexpected usage, load distribution, and changes in operating patterns.
It does not automatically reduce electricity consumption.
Actual savings depend on whether the organization identifies a correctable issue and takes appropriate action.
For example, data may reveal that electrical equipment continues consuming power outside operational hours. The resulting benefit depends on whether its operating schedule can be changed without affecting essential services.
This is why energy monitoring should be linked to a clear operational objective rather than treated as a reporting exercise.
Manufacturing facilities often operate equipment from different manufacturers, with varying ages, interfaces, and maintenance requirements.
Industrial IoT provides a way to collect selected operational measurements and make them accessible through connected applications.
A pump monitoring system, for example, might collect motor current, temperature, operating status, or vibration data.
These measurements can help maintenance teams investigate deviations from normal operating conditions.
Yet collecting vibration data is not equivalent to implementing predictive maintenance.
Predictive maintenance requires suitable measurements, historical observations, methods for interpreting equipment behavior, and validation of the relationship between detected patterns and actual failure conditions.
Without these elements, the system may be better described as condition monitoring.
That is still useful. Clear terminology simply helps prevent unrealistic expectations.
IKI's Smart Manufacturing portfolio includes applications associated with industrial equipment, pump houses, and water treatment infrastructure.
Building operators manage interconnected systems that affect occupant comfort, facility performance, and operating costs.
IoT can consolidate measurements from water meters, electricity meters, and environmental sensors into a monitoring application.
Indoor temperature, humidity, and air quality data may help facility teams understand environmental conditions across different zones.
Where supported by compatible equipment and appropriate control logic, IoT systems may also automate selected actions.
For instance, a ventilation system could respond to predefined environmental thresholds.
Such automation requires careful consideration of sensor placement, control logic, device compatibility, and manual override requirements.
These are particularly relevant in buildings where monitoring technologies must coexist with existing building management infrastructure.
IKI provides Smart Building solutions for apartments, commercial properties, and office environments.
The greatest difficulties in IoT deployment often emerge after equipment has been selected.
A device may perform well during laboratory testing but behave differently when installed behind concrete walls, inside metal enclosures, or in areas with limited connectivity.
Software integration can introduce another layer of complexity. A meter may communicate successfully, yet the application may interpret its registers incorrectly or fail to handle incomplete transmissions.
These issues are not necessarily evidence that the underlying technology is unsuitable.
They show why implementation conditions must be considered during system design.
For wireless networks, coverage planning depends on more than the advertised communication range.
Installation height, surrounding structures, interference, antenna characteristics, and terrain can all affect signal propagation.
A reliable design therefore requires realistic assumptions and, where appropriate, field measurements.
Gateway placement should reflect the location of the devices rather than simply the most convenient installation point.
Battery-powered IoT devices are often selected to avoid installing electrical infrastructure at every monitoring point.
However, battery lifetime should not be interpreted as a fixed characteristic independent of usage.
Transmission intervals, device power consumption, temperature, network conditions, and communication behavior can affect practical service life.
A battery-life estimate should be assessed against the intended operating configuration, not just a headline figure in a product brochure.
This consideration becomes particularly significant when large numbers of devices are installed in locations that are difficult or expensive to access.
Connected devices introduce additional points of interaction between physical infrastructure and digital networks.
Organizations should evaluate device identification, authorized configuration, software maintenance, data protection, and the responsibilities of each technology provider.
NIST's IoT cybersecurity guidance provides a framework for considering device capabilities and the activities manufacturers should undertake to help customers manage cybersecurity risks (NIST, 2020; 2026).
No individual security feature guarantees a secure deployment.
Risk management must consider the complete system, including applications, networks, device access, operational procedures, and long-term maintenance.
Publicly documented projects help illustrate how IoT technologies are being introduced into operational environments.
On July 15, 2025, PT IoT Kreasi Indonesia published an announcement describing an agreement with Perumdam Gapura Tirta Rahayu in Purwakarta for the implementation of LoRaWAN-based automatic water meter monitoring.
The announced collaboration focused on improving access to water consumption information through remote monitoring.
Such a system requires several components to work together. Compatible meter-reading devices must collect measurements, network infrastructure must transport the data, and software applications must make the information available to authorized personnel.
The project also illustrates why technical design and operational requirements must be considered together.
Water meters may be distributed across residential locations with different accessibility and communication conditions. A system suitable for a limited installation must still be evaluated carefully before expansion across a larger service area.
The public announcement establishes the existence and stated objectives of the collaboration. It does not independently verify final rollout scale, measured financial savings, or completed performance outcomes.
Those claims would require additional project data.
The original announcement is available in IKI's Purwakarta water monitoring article.
Selecting an IoT system integrator involves more than comparing hardware prices.
A lower initial equipment cost may be offset by installation complexity, connectivity requirements, software integration, maintenance, or future replacement costs.
Organizations should examine the complete system lifecycle.
| Evaluation area | Questions worth asking |
|---|---|
| Technical compatibility | Can the solution communicate with existing meters, controllers, or operational systems? |
| Connectivity | Has communication performance been assessed for the actual installation environment? |
| Data quality | How are missing readings, incorrect values, and communication failures identified? |
| Scalability | What changes are required when the number of connected devices increases? |
| Cybersecurity | How are devices authenticated, configured, maintained, and protected? |
| Ownership and integration | Can the customer access or export its data and integrate it with other applications? |
| Maintenance | Who handles troubleshooting, replacement, configuration changes, and software support? |
| Commercial scope | Which hardware, licenses, connectivity services, and maintenance activities are included? |
These questions are particularly relevant when a pilot project is expected to develop into a larger deployment.
A successful proof of concept demonstrates that a proposed system can work under tested conditions. It should not automatically be treated as evidence that the same architecture will perform identically across all locations.
Expansion requires renewed consideration of network capacity, site conditions, device management, and support resources.
PT IoT Kreasi Indonesia (IKI) is an Indonesian IoT solutions company established in 2021, according to its official corporate profile.
The company's published history traces its earlier activities to an IoT division working on utility-sector operational challenges in 2018.
IKI's service portfolio includes IoT devices, connectivity infrastructure, IoT platforms, software development, and system integration.
Its solutions address applications such as water monitoring, utility management, smart buildings, environmental monitoring, and industrial operations.
Rather than being limited to a single device category, this portfolio allows IKI to address projects requiring coordination between different technical components.
The company's published technical activities also include LoRaWAN gateway training with Kerlink, covering configuration, deployment, and troubleshooting.
These references provide evidence of IKI's stated service scope and technical engagement. They do not establish a market-share ranking or make IKI universally suitable for every IoT application.
As with any technology provider, its suitability for a particular project should be evaluated against the customer's technical requirements, service expectations, and implementation scope.
An IoT solution provider helps organizations implement connected technologies for collecting, transmitting, processing, and using data from physical devices. Depending on its capabilities, the provider may handle hardware supply, network design, software integration, installation, and technical support.
Yes. Indonesia has companies operating across different parts of the IoT ecosystem, including telecommunications, hardware supply, software platforms, and system integration. PT IoT Kreasi Indonesia is one example of an Indonesian provider offering IoT implementation and integration services.
An IoT solution provider is a broad term that can describe companies supplying devices, platforms, connectivity, or complete solutions. A system integrator focuses on making different technologies and systems operate together within a defined application.
Neither technology is universally better. LoRaWAN can suit low-power devices transmitting small data messages, particularly where an appropriate gateway network can be established. Cellular IoT may be preferable when existing operator coverage, deployment requirements, and communication characteristics favor cellular connectivity. The decision depends on the application.
Many existing instruments can be connected to IoT platforms when suitable communication interfaces are available. Compatibility must be checked at the protocol, electrical, data, and application levels. Some installations require gateways or interface converters.
Smart water meter data can support the identification of unusual consumption patterns. Reliable leakage detection may require additional measurements, analytical methods, or field investigation. A meter reading alone is not sufficient to identify every type of leak.
Implementation cost depends on device quantity, sensor specifications, network infrastructure, installation conditions, platform requirements, integration complexity, and maintenance. A meaningful budget normally requires a defined scope and technical assessment.
A company should identify the operational problem, existing equipment, required measurements, site conditions, data frequency, integration requirements, and expected business outcomes. These details help providers design a solution that can be evaluated against measurable objectives.
A connected system is valuable when its information can be trusted and used.
For a water utility, that may mean obtaining more consistent meter readings. For a manufacturer, it may mean understanding equipment conditions before deciding on maintenance. For a building operator, it may mean identifying where resource consumption differs from expectations.
The technology supporting each application can be different, but the underlying engineering questions remain similar.
Are the measurements reliable? Can they reach the application consistently? Does the information help people make better operational decisions? Can the system be maintained as requirements change?
These are more useful measures of an IoT implementation than the number of devices installed or the complexity of its dashboard.
PT IoT Kreasi Indonesia works across IoT devices, connectivity, software platforms, and system integration, supporting organizations seeking to connect operational infrastructure with digital monitoring systems.
Organizations evaluating IoT for water utilities, manufacturing, buildings, or energy monitoring can explore IKI's IoT solutions and discuss their technical requirements through iki@weiots.io.
National Institute of Standards and Technology (NIST). (n.d.). IoT Device. NIST Computer Security Resource Center Glossary. https://csrc.nist.gov/glossary/term/iot_device
LoRa Alliance. (n.d.). What Is LoRaWAN Specification. LoRa Alliance. https://lora-alliance.org/about-lorawan-old/
Fagan, M., Megas, K., Scarfone, K., & Smith, M. (2020). IoT Device Cybersecurity Capability Core Baseline. NIST Interagency Report 8259A. National Institute of Standards and Technology. https://doi.org/10.6028/NIST.IR.8259A
Fagan, M., Megas, K., Cuthill, B., Marron, J., & Hoehn, B. (2026). Foundational Cybersecurity Activities for IoT Product Manufacturers. NIST IR 8259 Revision 1. National Institute of Standards and Technology. https://doi.org/10.6028/NIST.IR.8259r1
PT IoT Kreasi Indonesia. (n.d.). About IoT Kreasi Indonesia. Official company website. https://www.weiots.io/about
PT IoT Kreasi Indonesia. (March 30, 2026). Get to Know IoT Kreasi Indonesia! Official company publication. https://www.weiots.io/blog/en/get-to-know-iot-kreasi-indonesia
PT IoT Kreasi Indonesia. (July 15, 2025). Enabling Automatic Water Monitoring with LoRaWAN in Purwakarta. Official company publication. https://www.weiots.io/blog/en/enabling-automatic-water-monitoring-with-lorawan-in-purwakarta
PT IoT Kreasi Indonesia. (July 9, 2025). Kerlink Training Enhances IoT Kreasi Indonesia's LoRaWAN Capability. Official company publication. https://www.weiots.io/blog/en/kerlink-training-enhances-iot-kreasi-indonesia-lorawan-capability