This document describes the solution for condition monitoring of industrial machines by providing data independently to multiple third-party data partners (OEMs).
In any industrial machine, there are a lot of moving parts that need regular maintenance, and surveillance. The pain point is not about the number of parts, it's about the different manufacturers and vendors who supply these parts as they all need to monitor all the parts they supply. Data collection and distribution to the concerning partners is not an easy job to do, especially when data security and custody need to be taken into consideration.
Moreover, some machines and parts cannot be serviced remotely, they need to be sent to the service stations for service and maintenance. If some repairs are needed, new spare parts have to be ordered which costs downtime and money. Sometimes the service partners have to travel to the site, and if they need to do some repairs, spare parts tools have to be ordered and that comes with a cost.
Exchanging data with multiple third-party data partners (OEMs) with each of them having their own data policies and security regulations is a headache for manufacturers and the users of the machines. To tackle the problem, weeve is creating a data service that will securely supply OEMs with the data they need, and providing data insights that can help in deciding on the maintenance cycle of the machines.
Weeve platform, allows a manufacturer to build data services that pass selected data to the specific OEMs. This means that if a manufacturer wants to share only a specific type of data, or a specific value, or all of the data when a specific event occurs, this is now possible with weeve.
Furthermore, a manufacturer might use the weeve platform to gain specific information from data and set thresholds or triggers for alerts. All of the above mentioned, reduces costs and saves operational time.
The OEM needs the data from the machines into their systems in one of the two ways.
It is not always required to acquire all the data points to the OEM. Some aggregation functions can be used and the data can be stored locally. The aggregated data then can be send using the API or directly to the database. Another option can be to save the data locally in encoded CSV files. The files can be copied later.