Linkedin

Powered by Blogger.

Labels

Wednesday, August 3, 2022

NOA Data Service - Making IoT device integration easier

Setting up a POC - Proof of Concept or POV - Proof of Value, for IoT devices can be extremely time consuming. If your development team doesnt understand how the devices interact with each other then it is going to take some time to integrate your devices and set up your POC.

At IoTdc, based in Centurion, we have realised that this type of integration takes up more time than most teams realise and when just trying to prove a concept, or trying to prove the value that the ioT solution might bring to your company, time is a commodity that can add up to a considerable amount super fast and in many cases the POC actually doesnt prove value and in that case the project wont progress much further than the POC. So time is not something you want to waste.

The faster you can get your data from your devices to a dashboard or alert system the sooner the end customer can see whether the project will add value to their company or not. 

For this exact reason we have created an integration system that will take your POC development time from months, weeks or days to hours and minutes. At a recent instalation of a few milesight devices at a restaurant , used to measure temeperature and humidity in the walk in fridges the devices were stuck in place and the dashboards were created literally the same day. The LoRaWAN network was setup at the restaurant and within in minutes data was being sent to the NOA Data Service backend (device integration system created by IoTdc) and within the next hour or so the dashoards were created and the client could see within the same day that one of their new fridges was actually not performing as expected and was actually being packed incorrectly. 

This is the insight you can only gain from seeing real data on a dashboard. I have included a snapshot of the dashboard just for clarity.


This data is comprised of a few LoRaWAN based Milesight EM-300TH and EM-300MCS devices. There is a Kerlink iFemto Evolution LoRa basestation with GSM backhaul capability and the data is first sent from the LoRaWAN gateway to a LNS - LoRa Network Server from where it is is then forwarded via an HTTP integration to the NDS backend server. The data is stored in an influx timeseries database and then visualised using Grafana. This layer could have even been the clients own BI system or visualisation layer. 

In many cases an existing client might want to see how the data can be visualised on their own backend system and then NDS - NOA Data Service will send the data in the correct payload format to their server and the client will do their own visualisation.

In all cases though the integration of these devices was already done by our team and the POC took hours to set up and for the client to start seeing the value.

In the case of this restaurant the reasons why this data is valuable is twofold. the first being insurance premiums can be lowered due to the visibility of how the walkin coldroom are being managed, hence lowering the risk and secondly for the maintenance teams that can now do maintenance scheduling based on their insights gained by the data gathered from these devices.





The Milesight EM300 series has many different sensors that are already all pre-integrated into NOA Data Service, which means setting up an y POC using these devices takes hours instead of days or weeks.

Some of these sensors like the Milesight EM300-UDL use and ultrasonic distance level sensor to tell the height of waste in a glass recycling bin as an example. This will allow the recycling company to do waste removel scheduling istead of having to drive to the same sites every day to empty bins that arent even full yet. This is a real use case where value can be measured in rands and cents due to the increase in petrol price here in South Africa. This ability to schedule pickups really is a great benefit for recyclers.
 
Written by johnkweber
NOA Data Service create by IoTdc and johnkweber




NOA Data Service - IoTdc, Gauteng

NOA Data Service 1

 


 NOA Data Service

NOA Data Service removes the complexity of IoT device selection, 
solution specific integration, data visualization and analytics.
We believe that real people can solve real-world problems better than before, 
they only need the right tools to make it happen.
We play our part by making the IoT accessible and easy to use, giving innovators 
what they need, when they need it, without the complexity.
Humanity and technology, working together for a better world. 
A world we’d want to live in.
How simple

Pre-integrated IoT devices and gateways such as Milesight, Minew, Kerlink, Teltonika and many more.
Use NOA Data Service - NDS to integrate your own devices that generate JSON data payloads easily
and extremely fast. Its as easy as selecting the parameters you want from the JSON payload and
press create. Device will be created and integrated in one two easy steps. This means MQTT topics 
will be generated where you can retrieve your data as well as integration URL will be given to you which
you can send your JSON payload to and all the hard work will already have done for you.

Lets say for instance your device sends its data to a LoRa gateway such as Milesight UG67 or UG65
or a Kerlink iStation of iFemtocell, The devices that send data need to be set up on your LNS of choice,
such as TTN, chirpstack or Kerlink WMC. The NOA Data Service generates a URL to which you will
send the device data direct from an LNs HTTP integration. everything else is integrated for you. All you
need to do is add the payload formatter so that the device paramaters get sent out to the unique NDS URL
and the paramaters will get stripped out and visualisation and alerts are then easy to create with just a few 
clicks of your mouse.

Written by johnkweber
NOA Data Service create by IoTdc and johnkweber

Is IOT suitable for every project? By johnkweber, Technical Lead at IoTdc

Article previously posted on ITWeb on 26th July 2022

 

John Weber, Technical Lead at IoTdc.
John Weber, Technical Lead at IoTdc.

Utilising IOT in your business can be one of the most significant levers to pull to achieve measurable value like cost reductions, optimisation or delivering specific outcomes like automated compliance or worker safety.

The definition of IOT can be broad but, put simply, it is many small devices sending tiny payloads of data, all working cohesively, to create actionable data and a solution that allows for remote access and sometimes remote manipulation. An example use case might be using IOT sensors to monitor soil moisture and a rain gauge to trigger irrigation when necessary.

There are multiple applications for IOT, and due to broader adoption, the cost of implementing an IOT project has come down in recent years. Logically, one assumes that with more companies using IOT that the complexity will reduce. In my experience, however, the process of delivering a successful IOT project can still be very complicated. Implementers of IOT often underestimate the scope of work and are surprised by unexpected complications.

IOT is a fantastic field where the growth being experienced is phenomenal. Still, it’s not necessarily the right option for every use case. Encouragingly, the number of devices is growing exponentially and there is an excellent quality sensor for every type of measurement. Some of the most successful projects I have worked on use sensors that are purpose-built for one or two specific measurements, with multiple sensors working together as a whole to make lives easier and businesses more profitable.

Hidden challenges

While IOT’s potential is huge, there are still challenges. Actual implementation and project roll-out can be slowed down significantly by unforeseen complications – usually due to lack of understanding around how the various systems fit together to create a viable solution.

IOT products don’t necessarily follow the same standards, even if they use the same protocols – for instance, LoRa. This is because every product manufacturer develops their product in isolation. To make matters worse, some IOT products are actually rehashed outdated products equipped with LoRa communications chips in the hope that they will be more successful in an IOT era. This means that the products are already old technology and not built with the same principles in mind as IOT predicates.

Therefore, integration can be the biggest challenge: projects that were scoped for weeks of development suddenly take months of preparation just to get to the point where they can be integrated. Something as simple as a LoRa sensor to send temperatures to a server can involve far more integration complexity than expected.

The LoRa devices don't send data directly to a server for consumption. They have to go through an LNS (LoRa Network Server) such as TTN (The Things Network) or Helium and then you first have to understand how each different LNS works in order to figure out which best serves your purpose. The organisation could use Chirpstack, Loriot or WMC (Waney Management Center), but all of these options have costs involved. In the grand scheme of a good sized project, they may seem insignificant; however, they are recurring costs that should not be overlooked.

Hidden costs

Almost every system that sends data to various disparate systems will have been built at a considerable cost and that cost needs to be recouped. The amount of data being sent and stored also needs to be accounted for, meaning more costs. Visualisation of that data has to be realised through even a different system, with yet more costs.

Delivering value

In light of the unexpected challenges and costs, one of the greatest mistakes a company can make is to try and implement IOT just because it's such an industry buzzword.

Whether IOT actually adds value to a company should be the one and only driving factor to implement it. Whether it adds value depends on the use case.

For example, using an IOT solution to monitor a building’s electricity consumption remotely will most likely deliver little in the way of value and savings. However, using the same electricity meter to bill tenants more accurately will save money and deliver value. A use case that could really add to your bottom line would be to distinguish between grid power being supplied to your tenants versus the more expensive diesel generator power provided during load-shedding, and billing tenants accordingly.

Another use case that makes real sense and adds tremendous value is predictive maintenance on regularly serviced machines. A sensor as simple as a LoRa-based accelerometer can use AI to predict when a moving part could be failing. The typical AI-based sensor will run for a short period of time, learning what the normal vibrations mean on a machine; when a bearing is damaged, even the slightest vibration out of kilter can be monitored and an automatic service request can be actioned or some alert can be sent to a maintenance technician to turn the machine off to ensure further damage doesn't occur.

Importantly, the correct parameters need to be measured to ensure the desired outcomes.

IOT not a catch-all

IOT is not a catch-all for every use case or situation. The use case needs to be carefully considered and the outcome should be that it saves money, travelling time or some other costly parameter.

However, this doesn't mean IOT doesn't deliver value. The technology has proven results in thousands of cases around the world and it is becoming more evident that when applied intelligently, IOT provides immense value.

We're seeing more and more standards that are being introduced, and IOT is maturing, with significant advances in IOT products. I view this as a development that could make IOT more viable for more use cases. I believe this will bring stability to what has been a 'wild west' IOT landscape.