Practical tests show that a collective network can reduce development and maintenance cost by 50 times compared to using traditional development methods that use message queues and centralized hubs for IoT distribution.
Hive collective is based on sharing data on changes in the network and only to a recipient that is active in the collective. This reduces network traffic by more than 50% and is a better option when you want to develop a greener smart city solution.
Using Hive collective on Internet of Things devices like TV, smart phone, intelligent coffee machines autonomous vehicle among others, the manufacturer does not need to install any prearranged program into the device on shipment. Instead it can be created as a service and the devices can be integrated into third party service providers ad hoc by just a click. The maintenance cost on the value chain is drastically reduced and simplified. Any upgrade to the device can be done remotely from an online service.
Using Hive tools enables GDPR (General Data Protection Regulation) on communication. This means that the consumer controls his own data in the network. GDPR is one of the main challenges any future ITC project is facing since data from the user needs to be controlled and owned by individuals. Many IT service providers do not take this into account when designing a solution.
Per design the collective network does not persist data so there is nothing to steal if someone is successful to hack the system. The collective uses a kind of blockchain type of storage distribution. Any hacking attempt will be difficult since the data is spread around the network and will make no sense to the hacker. On top of this we use data encryption and dynamic token on the communication. Building security solutions is an ongoing thing and will always be a process to stay on top of the challenges the network is facing.
Using Synx tools will make consumers’ lives easier. Let’s say that you want to move to another apartment in the near future and you have a lot of smart devices that you need to leave behind. Typical intelligent washing machine, TV, fridge, oven, windows, door bell, light system etc. With Hive tools the ownership of these devices can be transferred to a new person. The new person will then be able to control data from these devices and choose which services to add them into. This feature is not possible in an easy way using traditional methods, where the user will end up reprogramming and do new installations manually for each device.
Data providers need to program interfaces (API) when sharing data with each others. Using Hive collective this interface is replaced with links and commands against the network. The effect is that developers can integrate with third party services much quicker (minutes instead of days).
With the Hive collective morphic providers can integrate with past, present and unknown future services (services that do not exist yet). This can be done without changing anything locally. A practical example can be that a service provider is creating a light switch to turn off/on users’ lights in his living room using his mobile app. So one day into the future, the user is purchasing a new intelligent LED light produced by a new company. The mobile application will work together with this new LED light system without any new installation or upgrade to the app. The collective makes it possible to connect past, present and future services together.