Without automation, IoT solutions offer little more than visualisation dashboards and offline data analysis. As the popular saying goes, nobody really wants a drill, they want their painting on the wall. Similarly, the data itself that is coming from the connected products has little inherent value. What matters and is ultimately the goal of all IoT solutions is that specific actions are taken to solve very specific, real-world challenges, that are unique for each IoT use case.
These actions are defined as business rules, and represent the core business logic of any IoT application and use case. Rules engines are the software tools that are used to build and run business logic, and they come in many shapes and flavours. In the IoT domain, business logic tends to be complex as it crosses many functions to include device data, enterprise data and external services or applications. Different IoT business logic requires different rules engine capabilities, which is why there is no one solution to fit all when it comes to automation for IoT.
There are very few commercial (or open source) tools that have the whole range of capabilities to cover the wide variety of IoT automation requirements across industries and use cases. This is why the IoT automation market nowadays is dominated by either vertical solutions that are custom made to serve the specific automation needs of a single vertical or by solutions where an automation stack is built, made up of a combination of tools and technologies.
When looking at implementing automation logic for you IoT use case, you need to be aware what capabilities your automation tool or stack must have so that it can help you build, run and maintain logic that meets your application’s very specific requirements.
In webinar IoT Rules Engines: How To Build & Run IoT Business Logic, we have a look at how you can evaluate any rules engine by immediately matching your unique business logic requirements with the necessary rules engine capabilities.
We first look at how powerful the technology needs to be to support your automation logic and then at how easy it is to actually work with it. Think everything that makes a build tool developer & operations-friendly.
We are using concrete IoT use cases and IoT business logic examples throughout the whole webinar.
Watch the video here.