In the first part of this blog series we have shown why it makes sense for the customer to define performance criteria for the selection of a suitable IoT platform and to prioritize and weight these accordingly in the decision-making process.
In this article, we provide a deeper insight into the basic structure of our criteria catalog, which includes various evaluation criteria.
Some IoT platform evaluation criteria are listed here as examples:
- Overarching criteria for the use of the IoT platform are, for example
- SupportDoes the IoT platform offer support for the solution?
- Community: Is there an active community for the solution that can help users or developers?
- SecurityWhat security concept is the platform based on? How is data encryption implemented?
- Data protection: Where is the data stored? Is data protection legally secure?
- Criteria in relation to software and application development
- Protocols: Which software protocols (e.g. HTTP, Websocket, MQTT...) does the platform support?
- Software Developer Kit (SDK): Is an SDK available to connect new hardware?
- Programming language: Which programming languages are supported by the platform (e.g. C, C#, Java, Javascript)?
- Criteria in relation to the integrated functions in the backend
- User management: Is user management available?
- Data normalization: Is it possible to convert different data units (e.g. conversion from Fahrenheit to Celsius)?
- DashboardIs it possible to display aggregated values from different machines / devices.
Relevant decision-making principles are the basis for selecting the right IoT platform
One Well-founded purchase decision is in the interests of all stakeholders involved. It is therefore important to involve as many relevant parameters on the agenda and evaluate them. The following table shows which areas of the company pursue which interests when selecting the right solution.
As an experienced software integrator, we at doubleSlash attach particular importance to supporting our customers in the very early project phases. This also includes the question of which technology is the right one for the customer. Giving a general answer to this question without knowing the customer's specific (functional and qualitative) requirements is neither sensible nor serious. The development of a catalog of criteria for the deployment and use of an IoT platform closes this gap. The aim is not only to support the customer in integrating the solution, but also to provide advice when evaluating and purchasing technology components.
It is primarily important to know the customer's existing requirements. At the same time, it must also be ensured that the customer's future innovations can dock onto the existing solution as easily and seamlessly as possible in order to guarantee the sustainability of the decision. After all, changing the IoT platform can be very time-consuming due to devices in the field.
Image source: ©Vallepu Fotolia.com
