When set up correctly, a proof of concept demonstrates the technical feasibility and business benefits of an IoT use case. It helps to minimize project risks and demonstrates the impact on the IT infrastructure and the entire company. Recommendations for industrial companies can be derived from the practice of successful projects. Those who formulate concrete goals right from the start will keep the project on track even in difficult moments.

Quantitative, technical or economic key figures are best suited for this. Only in this way can the success of the project be evaluated beyond doubt after completion. The goals should not be set too high or be unrealistic. However, they can be "ambitious", as the economic benefit increases if the PoC is already strategically anchored and embedded in a roadmap. Even before the first proof of concept, it is therefore important to determine which IoT scenarios are to be implemented one after the other.

Time frame

A maximum of three months is usually sufficient for a PoC - four weeks for preparation, four weeks for technical implementation and four weeks PoC runtime. If pilot projects run for too long, this is often a sign that they are not properly dimensioned. Of course, PoCs can map complete use cases. However, it has proven to be a good idea to keep the project scope manageable. For example, it is advisable to test the feasibility of only one machine with some of the interfaces and data. After successful completion, the solution can then be scaled up.

Of course, the PoC must test and evaluate the interaction of the most important technical components. In addition to pure functionality, the planned architecture and all components must be examined for their performance and potential bottlenecks. First and foremost is the choice of IoT platform. Aspects such as sensor technology, networking, interfaces and data models also need to be put to the test at an early stage.

Simple use case

In order to see quick results, a use case that can be implemented with relatively little technical effort is ideal. If sufficient data already exists, machines are already connected to the internet or the required dashboards can be easily implemented, this is a good starting point.

In practice, it has proven useful to put together a task force of employees and managers at the start of the PoC. This allows the respective requirements and perspectives, concerns and ideas to be incorporated at an early stage.

Equipment as a success factor

Another success factor for PoCs is the human and financial resources. It is crucial to realistically assess and provide the required investments and resources. The IoT knowledge and workload of IT staff should not be underestimated.

Once the PoC has been completed, it is time to take stock. If the project did not go as planned, it is time to investigate the causes. Sometimes it is enough to adjust a few parameters of the sensors or the IoT platform. However, it may also be that technology modules need to be replaced or the IoT architecture as a whole needs to be reconsidered. If the PoC was satisfactory, the next step is to scale the solution and prepare for the go-live.

Larry Terwey, Director Digital Business, ECS Engineering Consulting & Solutions