Internet of Things is more than mounting a sensor or RFID tags. The best result is achieved by tackling all aspects of an optimal solution in the right context. The various aspects of a successful IoT project are explained below.
A clear scope of the project at the beginning prevents possible wrong choices at a later phase of the project. Therefore it is important to determine in advance where this project should lead (vision) and how we are going to get there (strategy). The project goals are derived from this. See below the possible project goals with regard to introducing the IoT system:
- Legislation compliance
- Process improvement
- Chain improvement
- Corporate Social Responsibility
The most important goal of applying a new vision or strategy combined with an IoT system is to ultimately deliver added value and therefore guarantee the profitability and continuity of the company. In addition to the mandatory legal requirements and the minimum expectations of the consumer, companies are seeking the goals:
- the right products (range)
- in the best possible quality
- at the right time (on-time)
- at a price acceptable to multiple parties (value for money)
When setting up an IoT project, we seem to have the temptation to immediately start searching for a technology (RFID, Lora, ND, Zigbee, Wifi or Ultra Wideband) and start the implementation shortly thereafter. In addition, after the implementation, the expectation lives, that the chosen technology will solve all the bottlenecks in current processes…experience often teaches differently.
Implementing an IoT system with included technology can best be described as a complex transitioning process. Your business processes can be a good guideline to realize the system. First is it necessary to optimize the old situation (with the new working methods in mind) before proceeding to the actual implementation.
The Organization Structure in an IoT project is broadly composed of:
Devision of roles
Certainly with IoT projects it is important to make good agreements about how the roles are distributed among the chain partners.
Central questions for this part:
- Who takes which role in the project?
- Who takes which role in the operation?
Tasks, Responsibilities and Competences
- Prepare clear TRCs
- Focus on IoT exceptions (MBE: Management By Exception)
- Responsibilities are supported by the right authorizations
Communication and consultation structure:
- Consultation structure: with regard to reports, document flows must be coordinated, between departments and chain partners as well.
- Physical consultation: define a clear steering group and working group during the project. Moreover let the steering group continue to review after the project, thereby you can constantly evaluate and adjust the project / collaboration.
- Set up an Incident Management structure.
Considerations in (project) management style to arrive at clear roles, TVBs and consultation structures are shown in the table below. In general, it is a balance between decisiveness and consensus.
Based on our broader experience, we know that the lead time of IoT projects is at least 1 year. As well as that consensus is more important than decisiveness for the system to ultimately work!
To realize the strategies described using an IoT system, it is necessary to have the right information available at the right location at the right moment. The data collection and distribution process has been translated into a schematic representation as shown below. A further elaboration per point is available on request.
Introducing an IoT system is more than applying technology. It concerns all of the elements that are described on this site. It is important that the success of an IoT system stands or falls depending on the least controllable section.
In many projects, it turns out to be system users. Ultimately, it is the users who operate and influence the system. This group is often only involved in the last phases of the Internet of Things project.
Besides this, it is a fact that the people in the operation know exactly how things work and so they can also indicate which bottlenecks must first be remedied before implementing a new system. Therefore they are an important discussion partner when analyzing processes. We have extensive experience in the realization of automation projects in which the users play a key role and are satisfied with the new working methods and systems.