Core components of IoT Glue®
Affordable Redistribution License Model
- Customer focused business model for license redistribution
- Offer IoT Glue® as your own branded offering
- IoT Glue® is developed using “security by design” principles
Outstanding User Experience
- An easy drag-and-drop UI
- Well-organized dashboards
Single Platform Advantage
- Single platform to connect, collect, process and analyze data
- A highly modular plug-and-play platform
Minimal Change Impact
Full Cycle System Integration
Tailored SME Editions
What is IoT Glue® ?
IoT Glue® is an IoT integration framework. It allows businesses to quickly integrate devices and applications, define rules and take actions. As it is built as a highly extensible framework, IoT Glue® allows users to add adaptors to support more protocols and actions. It is built as a low code, easy to use framework, making it an ideal tool for both the business and the technical community. The ability to build custom dashboards and have macro & micro level reports help users monitor their devices & systems efficiently.
How does IoT Glue® compare with its competitors?
IoT Glue® is a framework which enterprises can build their IoT solutions on. So, unlike most products, IoT Glue® comes with fewer limitations. IoT Glue® comes has out of the box support for HTTP & MQTT protocols. But supporting any industry standard or bespoke protocol is easy as the framework can have adaptors. The product is architected to be extensible and scalable. As an IoT integration platform, IoT Glue® also follows a low code approach with easy-to-use user interfaces. The framework also consists of an API Gateway and service composition capabilities which allow not just devices, but also applications to be seamlessly integrated.
Do you offer professional services for product implementations?
Yes. We believe this is an essential part of product delivery. Any product team must be complemented by a delivery team who can fit the product into the customer’s environment. Any customizations and support are also handled by the System Integration team from THIS
What internal skills do I need to work with IoT Glue® and its modules?
Any IoT initiative needs to have an IoT Architect who understands the business objective and the technical/device landscape of the customer.
To use the IoT Glue®, out of the box, a basic understanding of JSON, XML, REST, devices, and protocols are sufficient. At this level users can create rules, trigger actions, and visualize data.
If you want to extend the framework then you can do so using NodeJS, Java and some database (SQL & NoSQL) skills.
What are the different data sources that IoT Glue® can accommodate?
Out of the box, IoT Glue® currently supports HTTP and MQTT. IoT Glue® is easily extensible with adaptors for any other protocol. The SDK provided allows you to build custom adaptors in quick time. Using the adaptors, any data source can be registered on IoT Glue®. The data source can be a device, an endpoint, an edge device, an IoT Gateway etc.
How are IoT devices/services configured for specific use cases?
The IoT devices/ services can be logically configured with groups based on endpoints (IP Address & Protocol). These groups can be modelled by designing templates based on use cases. For example: In the use case of remotely monitoring a server room, a template can be configured with details like the server room name, server room no, floor no, building name, server room manager details etc. Once device/source groups are configured for this template, the data can be used for processing, creating visualizations and even for triggering actions based on rules that are configured in RT-Builder.
What are the various operations that can be done with the data generated in real time?
IoT Glue® supports Real Time and Near to Real Time Operations:
RT-Builder (Real Time Builder) - gives business users the ability to build business workflows based on their requirements. A business flow contains one or more data sources (aka Source in IoT Glue®), Rules, Actions, Triggers and Visualization Nodes. Based on the rules in the flow, actions will be triggered or analysis can be done on certain KPIs in real time.
X-Builder or experience builder is an API-driven module which allows you to configure widgets, build what-you-see-is-what-you-get dashboards (WYSIWYG) and publish them to particular user roles.
How can the modular package of IoT Glue® help in my use case?
IoT Glue® offers three choices in modules while purchasing the product:
- Commune and RT Builder: Useful if the user wishes to only build rules based on business scenarios which can help trigger real time actions or analyze endpoints and not wish to visualize the data on a dashboard. Commune is used to register and configure users, data sources and devices for these operations
- Commune and X-Builder: Useful if the user wishes to build and generate what-you-see-is-what-you-get dashboards (WYSIWYG) using APIs from data streams generated external to IoT Glue®. Commune is used to register and configure users, services and APIs in this scenario
- Commune with both RT Builder and X-builder: By using a combination of all the 3, the business user has an option to register Devices/Services on Commune, build business flows using RT-Builder from the data streams and generate Dashboards with X-Builder
What are the different dashboards available and how are they configured?
IoT Glue® offers two levels of dashboards: One at the product and another at the Use case or operational level:
- Product level dashboard: View information with regards to IoT Glue® modules and user activities:
- Commune: Visualize number of device groups created, number of active devices and other information regarding services, devices and user management
- RT-Builder: Details of approved flows, number of requests appearing for each flow and more
- X-Builder: Information on the published dashboards, number of visualizations available for each dashboard, and much more
Users can publish the above dashboards using APIs to a particular user role for each module.
- Use Case level – IoT Glue® can be used for different business domains like fleet management, infrastructure management, crowd management etc. Multiple dashboards with insights for every use case can be published by leveraging the X-Builder module where these are composed
What are the different user roles available and how are they configured?
There are no pre-defined user roles with templates regarding access and permissions. Instead, an admin can add user roles in the Commune module of IoT Glue® and configure permissions to each user role like create a source/device group, edit source group, create a flow, edit a flow, approve/publish a flow and many more with regards to X-Builder and RT-Builder.