iris360

The platform has been designed following the UNE 178104:2017 standard to ensure proper operation and interoperability between systems and technologies. This is essential for Smart Cities or Smart Tourism Destinations that want to harness technology and avoid "vendor lock-in."

UNE’s reference framework distinguishes between Smart and Sensorized Cities, highlighting the ability to acquire data from various sources (sensors, social media, external entities) and turn it into valuable information for complex use cases of many kinds.

Scalability and Adaptability

iris360 is built to scale and adapt, with an architecture that supports continuous growth in elements and functionalities.

Deployed in an "On Cloud" environment, it provides flexibility and efficiency. Development, pre-exploitation, and exploitation stages are clearly defined for smoother implementation and operation.

Key pillars of the platform include:

• Use of open standards and open-source software to boost interoperability and scalability.

• Design based on open technologies and protocols, minimizing vendor lock-in and simplifying maintenance.

• An open, public API enabling third-party integration and application development.

iris360 Data Source Management

Connection to Libelium’s Open API

The Device Manager module connects with Libelium’s open API, enabling device access and configuration using an API KEY from the on-premise iris360 platform.

CRUD Functionality for Bootstrapping Profiles

Users can Create, Read, Update, and Delete bootstrapping profiles, choosing protocol and data destination for better customization and control.

Easy Profile Association

Libelium devices can be easily linked to specific profiles, simplifying configuration and enhancing management.

Support for Multiple Profiles per Device

Each Libelium device can support two profiles (primary and secondary), allowing for flexible behavior and settings.

GUI and API Access

The Device Manager provides a graphical interface and supports direct API interaction, adapting to diverse user needs. The API is documented according to OAS 3.1.0 and supports tools like Swagger or ReDoc.

Integration of Third-Party Solutions

Beyond Libelium devices, the platform can integrate third-party devices using protocols like:

• LoRaWAN

• HTTP(s)/MQTT(s)

Devices not FIWARE-ready use the Libelium Fiware Manager, which converts incoming data to a format compatible with the IoT Agent.

Protocol Compatibility

LoRaWAN devices connect via base stations and are routed through services like Chirpstack in the Acquisition Layer. HTTP(s)/MQTT(s) devices are integrated directly or via the Fiware Manager, depending on their readiness.

Scalable, Inclusive Device Management

iris360’s device management module handles diverse IoT devices, including third-party ones. This reflects the platform’s focus on adaptability and comprehensive IoT management.