Find out what automation tools are best suited to your IoT use case, then test them against the benchmark.
Get StartedIoT application development is fundamentally different from “normal” IT development. It requires bridging the physical world of Operations Technology (OT) with sensors, actuators and gateways to the digital world of Information Technology (IT) with databases, analytics and business tasks.
This bridging of two worlds has important consequences over how business rules are built within the IoT application. Building logic by configuring rules straight into the code is suboptimal, unscalable, costly and time-consuming. To solve these problems, automation is key.
Automating IoT solution development requires using a rules engine or a combination of engines. In order to help you determine what type of rules engine technology best suits your use case, we have defined an evaluation benchmark, made up of seven key evaluation criteria.
Real life is multivariable.
Time adds complexity.
Uncertainty is unavoidable.
The engine should be explainable, allowing users to understand why rules are fired and to identify and correct errors. The engine’s internal complexity should not come in the way of its users being able to easily test, simulate and debug that complexity. Users also require a high level of understanding and transparency into decisions with inherent risk.
The engine should be flexible enough to support both commercial and technical changes with minimum friction, such as changing customer requirements or changes in APIs. In order to account for future growth, the rule engine should be easily extendable and capable to support integration with external systems.
The engine should be operationally scalable. When deploying applications with many thousands or possibly millions of rules running in parallel, the engine should effectively manage the large volumes, by supporting templating, versioning, searchability, bulk upgrades and rules analytics.
The engine should provide a good initial framework and abstractions for distributed computing to enable easy sharding. Sharding refers to components that can be horizontally partitioned, which enables linear scaling – deploying “n” times the same component leads to “n” times improved performance.
Complete with extensive definitions and examples for each of the seven evaluation criteria.
Modeling Complex Logic
Modeling Time
Modeling Uncertainty
Explainability
Adaptability
Operability
Scalability
Modeling Complex Logic
Modeling Time
Modeling Uncertainty
Explainability
Adaptability
Operability
Scalability
Modeling Complex Logic
Modeling Time
Modeling Uncertainty
Explainability
Adaptability
Operability
Scalability
Modeling Complex Logic
Modeling Time
Modeling Uncertainty
Explainability
Adaptability
Operability
Scalability
Modeling Complex Logic
Modeling Time
Modeling Uncertainty
Explainability
Adaptability
Operability
Scalability
Modeling Complex Logic
Modeling Time
Modeling Uncertainty
Explainability
Adaptability
Operability
Scalability
Modeling Complex Logic
Modeling Time
Modeling Uncertainty
Explainability
Adaptability
Operability
Scalability
Modeling Complex Logic
Modeling Time
Modeling Uncertainty
Explainability
Adaptability
Operability
Scalability