IoT Platform Enhanced – User Security & Permissions

IoT Platform Enhanced – User Security & Permissions

Bevywise IoT Platform is a versatile, highly extendable Server Implementation that help Solution providers scale up fast. With the Edge client, Mobile SDK , REST API & all, it helps get your service running in a few weeks. The IoT Platform caters to Industrial and Home needs with flexible charts and widgets and Voice controls. Bevywise IoT Platform enhanced with user security permissions.

Small & Medium business Solutions

When you build solutions targeting a particular industry / market, you will be hosting multiple customers on a single server. Only such a development will make the solution cost effective in maintenance and affordable to your customer. Bevywise IoT Platform by default supports multi tenancy. The Platform also provides enterprise scale dashboard, data visualization, device authentication and rule engine which helps the users to monitor & manage their device individually.

Users & Permissions for each Tenant.

Business of small and medium scale also needs better tracking / control of the operation done by each employee in the organization. With the current update, we are happy to provide a multiple login account for each of your customers (each tenant).

Each Tenant in the System will have a:

  • Super Admin
  • A few Admins
  • Normal Users

Grouping of Things

The new version will provide option to grouping of devices and machines based on departments to provide granular control. Permissions can be provided as read only or read / write based on the grouped devices. In a business organization, a few professionals can be allowed to send commands to the machines / devices while others can monitor the activity and view graphs.

Normal Users will be able to view / operate on single or multiple group of devices / machines for which they have been provided permissions.

Admins will be able to create new widgets & Dashboards (coming soon), provide permissions for users, create and manage created groups.

Super Admin is the account owner who will be able to add new users and do everything else Admin and Normal user can perform.

You can have a look at the complete set of Featurs of the Bevywise IoT Platform in the presentation

Feel free to write to support for a complete Demo.

Industrial IoT Gateway – Early Access

Industrial IoT Gateway – Early Access

We are happy to announce a preview release of the Industrial IoT Gateway. This version collects data  from the industrial machines / equipment that supports Modbus protocol for interfacing. In addition, We designed  gateway  in such a way to pull data out of the machines and convert them into MQTT.  Besides that,  Bevywise IoT Gateway can send the MQTT data to the IoT Platform or MQTT Broker. Above all, You will be able to set up the MQTT Broker / IoT Platform  at your own premises based on the need.  The gateway will also work with all  standard MQTT Platform  like Azure , AWS IoT , Google IoT Core , etc.,

Industrial IoT Gateway

The Industrial IoT Gateway comes with a configurable User Interface. The data location on the Modbus Slaves and the corresponding keys for interpreting the data can be configured easily from a browser window.  In the preview version, you can connect the gateway with a maximum of 10 Slaves. You can configure  the monitored query interval based on the severity of the process / machines. We built the Industrial IoT gateway to  ensures the minimal data loss with local niche making sure the data loss.

Early Access

The Gateway can be run on Linux / Ubuntu , Windows 64 bit & Raspberry pi. We can make it work on any micro operating system based on the need. Do write to support or contact us for getting a preview of the Gateway.

5 Top Benefits – Buy an IoT Cloud Platform

5 Top Benefits – Buy an IoT Cloud Platform

Business today needs to work on multiple verticals to roll out out great IoT Product and a great overall customer experience. IoT Cloud Platform is one of the core component of the Implementation. Business trying to build everything in house faces a lot of challenge. It will be more effective to ride your IoT Implementation over an existing Platform. Here is a five benefits you get when you buy an existing IoT Cloud Platform.

IoT Challenge is Wide – Build expertise on your Core

An IoT Implementation is a challenge that spans from edge hardware, firmware, industrial design, ware housing, logistics, software cloud , hosting, mobile apps, and more.  The challenge for any business that builds devices or provides solution for any enterprise as consultant or system integrator is huge. It is harder to build expertise end to end across all domains vertically and horizontally. Solution business core lies on the Hardware and they should put all their efforts on build a beautiful hardware experience and partner for the other domains which helps them grow bigger and faster.

Get the best of every industry

As an IoT Platform provider, we work with many verticals and ensure the best practices of the different domains. And we put them into the common platform, so that every customer gets the best of world in terms of the cloud platform and building apps over the platform. We bring in the best of the high precision industry like Pharma, aviation to everyone so that you provide the best experience to your customer.

Otherwise you will be building something specific to your industry which is limited in its own context

These expertise knowledge is something you get not only for the Cloud Platform, but also we pass it on to our customer on their application side as well as the edge device development as part of the consulting for our customers.

Scaling up the IoT Cloud Platform

Who will say no to a Hockey stick growth of your business. Building a platform for managing a few hundred of devices will be easy and look lucrative when build using a few pieces here and there. Good products fail when the numbers go up. They will not be able to scale up their platform when the numbers go up quickly than they expect it to grow.  IoT Platforms are build today to scale to millions of devices easily based on the need.

Support and Extended Team

Any IoT Platform provider will provide you with a round the clock support all 365 days to ensure that your Platform is running always. All fixes and upgrades they do will be pushed to your servers as well as make sure your Cloud servers are patched always for the best performance and security. We work as an extended team to with business to ensure that they reach their goal faster and easier.

Save Money & Time

It needs a dedicated team to build , host and scale up the IoT Cloud Platform and the APIs for the application building.  It takes at least an year of time and effort for the team to understand the requirement completely to build a scalable and fail proof System. An equal amount of effort and time is needed scaling up the platform for more devices and more functionality.

We provide the best of both the worlds over our platform providing a ready to run platform and at the same time providing options to extend it at the User interface level and at data analysis level, so that you can build solution to any vertical. 

You can always try our hosted Device manager for FREE which is our IoT Platform

Schedule a call today to know the best practices to scale your IoT Implementation to the next level. 

IoT Cloud Platform Consulting

5 reasons to choose an IoT Platform over MQTT Broker

5 reasons to choose an IoT Platform over MQTT Broker

IoT and Industry 4.0 together pave the way for smart industrial developments and every industry needs a dedicated & personalized IoT/Industry 4.0 implementation. Even within a specific industry in medium and large enterprises, there are cases where the processes may require customization or a custom implementation of the solution. Such requirements result in millions of distinct IoT implementations in the entire world. In order to build cost effective solutions, these million implementations will need a central M2M engine (MQTT Broker) or an IoT Platform.

This blog helps you identify whether you need an IoT Platform or simple MQTT Broker to get start with  implementation.

Save Money on your IoT Implementation :

The IOT Platform provides everything that needs to be a part of the central M2M communication, Data Storage, REST APIs and more, in order to run a complete solution for any IOT automation. Using an IoT Platform as part of your implementation will have more advantages and higher cost savings than using MQTT Broker. This makes your server ready without spending a huge amount of money and time on implementing the same.

Easy scale up:

IoT Platforms are designed and built with scaling up your IOT Solution to handle millions of devices. But, Most platforms are micro services-based allowing you to deploy only the service you need. In the industrial implementation, there are two scenarios.

  1. Less number of devices and more messages per device
  2. Lot of devices and lower frequency of messages per device.

You can deploy higher connections and higher message rates with components of platform accordingly as per the situation. This is something not possible with the broker unless you go for some huge customization of the broker.

Multi tenancy for your IoT Implementation:

Bevywise IoT Platform comes with multi tenancy. Most solutions today require more than one customer and you cannot have one instance per customer. Besides that Most industrial scenarios need Multi tenancy. Platforms implement multi tenancy from devices using different set of authentication keys, data processing & storage, and data analytics based on the organization.

Faster Time to market:

The core of any IoT Implementation is the edge device and the management of the devices using your mobile application. The IoT platforms provide REST based APIs and SDKs for the faster mobile application and other application integration. The platform helps to get you the complete IoT Solution up and running in days.

High Availability of IoT Platform:

IoT Platform comes with an in-built monitoring and self healing tools. The platform monitoring tools help in keeping the Dev-ops team informed of the server health. The self healing tools can be configured in such a way to restart the services based on the CPU and Memory usage, making the service work more reliably.

Try the hosted Bevywise IOT Platform now.

For more information on the Platform, download the brochure here.  Contact support for a hosting a white labeled Platform for your IoT Solution.

MQTT vs REST from IoT Implementation perspective

MQTT vs REST from IoT Implementation perspective

Most of the IoT Implementations today uses REST over HTTP based connectivity from the client to the Server. REST has its own limitation that pops in while your solution scales up to the larger number of devices and more number of translations per second. MQTT, the lightweight protocol based on publish subscribe model designed exclusively for IoT has its advantage over REST in all dimensions. Bevywise MQTT Broker is the perfect middleware for secure mqtt cloud deployment. This blog compares MQTT vs REST to help you finalize your communication protocol.

Instant Response – Need of the hour

REST is a multi-functional architecture that comes up with good flexibility & scalability with low maintenance costs. But the major disadvantage is latency in request processing time and bandwidth usage. This is because, REST is a one-way connection. The connection to the server is intermittent. The client connects to the server when needed to push data from the client and pulls the data down to the client. The server needs to wait for the clients to connect to send the data that is intended for the client. Hence, this makes the user intended action to wait for the client connection. Most solution providers allow their edge server or their gateways to connect every 1 minute or higher so that the server is not loaded.

Take an example of an activating a light from a mobile app. The message from the mobile will hit the server instantly. But the message from the server to the client needs to wait for the time client to connect.

MQTT allows the client to be connected always providing a two way communication between the client and the server. This allows server to push the message to the edge device making the device respond to your command instantly as expected by Customers.

When directly compared MQTT vs REST for the same data transfer, MQTT consumes 20% lesser power. But, In the case of the REST, most energy is lost on the resources used on connecting and disconnection and resource cleanup on both the server and the client. So when you build a battery operated remote device, MQTT helps you with longer battery life than REST.

Highly Secure IoT Device Deployments

Most of the devices today are deployed behind the firewall for security reasons. One of the limitations of the REST is that the server can no way communicate from the server to the client on demand. Even if we put a REST Server on the client devices and try to make connections form the server, it will fail when devices are installed behind the firewall.  But MQTT inherently solves this problem of two-way communication with persistent connections.

MQTT vs REST Performance

MQTT is always-connected against the intermittent REST Calls. Due to the permanent connection, the need to connect and disconnect for every data transfer is not required. The keep-alive ping has a much lesser overhead compared to the reconnection connection calls the REST makes. As per the analysis and test reports, MQTT data transfer can transfer data at a rate 20 to 25 times faster than REST Calls.

The number of message transaction highly depends on the number of connections the server can accept in the stipulated time. The number of concurrent connections that the fastest available web server today will be in the order of 1000s per second. This restricts the data transfer in sequence. MQTT Broker can process up to 40,000 messages per second on a commodity server. The number of parallel connections the broker can hold can again be tweaked based on the hardware. A simple commodity server can hold up to 50,000 connections in parallel.

The key features that make MQTT worth than REST is its error handling functionality, flexibility & scalability. Significantly, An improved error handling provides a more readable information about the error that provides reasons for disconnection. MQTT 5 protocol specification supports an absolute error handling which is favourable for diagnosis to know what actually happened. In addition, MQTT 5 supports perfect load balancing and facile message processing. The major function of this feature packed protocol is that it caters enhancement for scalability & large scale industrial deployments.

In a clear advantage, MQTT wins the MQTT vs REST choice for the IoT Implementation.  Try MQTT Broker the fastest MQTT Broker available today. MQTTRoute also provides MQTT REST API to help you control & manage edge devices. It supports a extensive set of REST API which can be used to control the devices from any external application. To know about the REST API calls that Bevywise MQTT Broker supports navigate to the MQTT Broker API.

The new version of MQTT Broker, MQTTRoute 3.1 is available now with custom authentication & more. Try downloading it for FREE & get the first hand view.

download now

Do write back your queries to Bevywise support.

To test drive the MQTT Broker, use your own client that supports MQTT protocol or download one from our MQTT clients library.

Must Read Other Related Post

IoT Implementation Series – Design the Data

IoT Implementation Series – Design the Data

As part of the IoT Implementation series, this topic covers the best practices in designing the data communication between the edge device and the Central Platform.

IoT Device to Cloud response

Humans always expects a response for every action. The response can be emotional, physical, visual or in any human understandable form. The same is the norm when we interact our intensions via an ioT device. Developers often miss the point that the edge device too need them for a completion of the response back to the humans. The acknowledgement user need is different from what the protocol provides. The protocol level ack message only confirms the receipt of the data at the edge or the server. But the action happens after the protocol ack is sent back. So you need to make sure you send back a message from the device or the server once the intended action is complete. The response should be a success or a fail message based on the outcome. Check the outcome before the message is triggered.

Design the right message handle

All IoT Protocols have an identifier for the event and command messages between device and manager application. MQTT calls it by the name Topic. It is very important to define good and clear topics for the communication. The topics should be very relevant as it should be understandable by the Humans too. It is advisable to have a mandatory device identifiers on the subscriptions, as we will be able to know where the command is going. For the events, it is the implementors choice to use the topic.

Send relevant Data to MQTT Cloud

An half baked data is equivalent to having no data. So make sure you put all the data available into the cloud from the edge. For example, when we collect a machine status from the edge device, the core information is about the health of the machine like temperature, coolant flow, vibration level. But we often loose sight of the time relevance at the edge. It is better to get the time from the edge device than use the time on the server. Add the device identifier also as part of the data which can help a lot during the data analysis. There will some more core information which may not be of interest today. But it is better to have them for future analysis.

Identify & Group the Devices

Different IoT Cloud application has different kind of device identification process. Most of them get this done when they add the device. But this process increases the human effort to add these devices. Bevywise Iot Platform allows any device to connect if they have the right auth keys. The device can send additional data later. Most of the IoT Protocols today does not allow you to send more information while connecting to the server. So identify the register command and the list of data requested by the IoT Platform and send it as a separate message based on the protocol.

On the platform side, you will be able to create device specific user interface for your operators based on their roles. The IoT Platform mostly need to know the type of the device, manufacturer, location, etc. But you can always customise it to have more information as needed for your IoT Device management and inventory.

Mobile integration

One of biggest deceiving point in the IoT Implementation is that the developers tend to use the same protocol to connect your mobile applications. But that is not the right IoT implementation of the mobile application. The mobile application should be built over the REST API of the IoT Platform and should be integrated with messaging system like Firebase Cloud messaging for the notification. As an option, developers can use the protocol based communication when the app is open for instant messages to the server, but should not depend on it end to end.

Bevywise Networks is an end to end solution provider for IoT Implementation for any vertical from Edge devices to IoT Cloud Platform. We would be happy to help you get your solution tailored by us.

Schedule a call

Related Post:
Designing the Edge