Introduction

Over the last 6 years, Intwine has been developing the IoT of the future. That future is a decentralized IoT that works at scale, improves system security, and reduces the consumption of communications bandwidth. This IoT will automatically act on information to improve overall system performance without human intervention.

By using a decentralized approach to tackle some of the toughest IoT applications, Intwine has proven that this next generation of IoT networks is now a reality. It has worked at scale in deep space, manufacturing environments, and microgrids. It will work for you.

Tech Image

Intwine's Architecture

Intwine utilizes a decentralized architecture for its IoT networks. Intwine's architecture focuses on allowing devices to communicate in a way that gives them the ability to make decisions at the edge of the network. Nodes of the network no longer rely on a single server to make decisions. Nodes are now capable of making local decisions, which results in less overall bandwidth usage. 

Current IoT architectures are centralized and primarily consist of end-devices streaming all of their data to a central server somewhere.  These architectures are creating MASSIVE amounts of data, but are not scalable, are not secure, and are not optimized for commercial applications.

Parallel with Microgrids

Intwine's IoT systems have been designed to be deployed on the powergrid. The powergrid has hundreds of millions of homes and hundreds of devices in each home. Each of those devices will be collecting data at a high or low rate, devices will be added and removed from the network constantly, and the timescale for important decisions to be made will be very small. No centralized system in the world can handle this complex application. If every power load, tranformer, and solar panel had to report all of it's data back to a centralized server before information is learned and decisions can be made, the powergrid would simply not work.

The only way to connect the powergrid and other complex IoT applications is by distributing the decision making throughout the systems. This is the IoT that Intwine has created.

Advantages of Decentralized Networks

  • Response Time
    • Decentralized networks allow for response times to vary
      • Not all decisions require a central server for input, which increases overall reliability
    • Centralized networks are limited with response times
      • Require a single server for input, creating a single point of failure
  • Scalability
    • IoT networks are becoming significantly larger
      • Decentralized networks technically and commercially scale by spreading the operational load over many devices working in coordination
      • Centralized networks cannot handle complex IoT applications due to the required operational load on a single server
  • Handle Complexity
    • IoT networks are becoming more complex
      • Decentralized networks are easier to test and validate
  • Modular
    • The software pace for devices on a network is much faster than hardware
      • Decentralized networks offer a modular approach to handle software changes efficiently
  • Interoperability
    • IoT networks have widely varied end-devices
      • Decentralized networks are much more capable of handling interoperability between devices on a network

How does this apply to me?

What Intwine has done is directly applicable to your IoT application. Intwine has done the research, knows what works, knows what doesn't work, and Intwine has done it in the most demanding applications imaginable. Instead of solar PV panels and HVAC systems, it is your devices in your environment, for your application. All to reach your business goals today and in the future.


Considerations for your Application

  • Time-scale of operation - When do decisions need to be made?
  • Hierarchy/distributed design - What is the relationship between the devices on the network?
  • Data vs. Information - What data needs to be collected? What information needs to be gained?
  • Flexibility - How often are devices added and removed from the network?
  • Data model - Where does the data need to get to so a decision can be made (edge vs. cloud)?