# Cascade of isolated systems

The typical architecture of an IoT solution takes the form of a cascade of disconnected systems:

* The connected objects themselves, which integrate sensors and connectivity solutions. They can implement different standards of transmission (LoRa, Sigfox, Kineis...). This also raises the issue of managing multiple IDs within a single device.
* The network cloud, which receives the signal and converts it into digital data. Data received from different platforms and objects. Here too, proprietary protocols are used.
* Platforms, which collect data from objects within range and route it to operators' servers. They use dedicated protocols to communicate with the objects.
* Business applications that exploit this data for specific use cases (predictive maintenance, geolocation, etc.). They interact with the platforms via dedicated APIs.

Each link in this chain has its own technology and communication standards. There is no end-to-end interoperability between the sensor and the final application. It's a stack of compartmentalized systems, where every change of protocol or standard generates significant friction. The CONNECTIFY approach aims to unify this architecture through federating technologies.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://connectify.gitbook.io/iot-protocol/complex-ecosystem/cascade-of-isolated-systems.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.