How Eliona covers ontologies
Introduction
Eliona is a versatile and scalable platform that integrates ontologies such as Brick, Haystack, and RealEstateCore to enable efficient and user-friendly management of smart buildings. With its powerful features and intuitive user interface, Eliona supports the structuring, integration, and management of building data in a way that promotes both flexibility and efficiency. This documentation provides a comprehensive overview of the structure and functions of Eliona, including the use of tag systems, the creation of custom classes (asset templates), the geographical and functional nesting of assets, as well as advanced asset functions and data integration methods. By combining practical solutions with innovative technologies, Eliona ensures that smart buildings can be managed optimally and continuously developed further.
Structure of Eliona
Eliona is a flexible and scalable platform that uses various building blocks from ontologies such as Brick, Haystack, and RealEstateCore. Here is a general and clear representation of how Eliona is structured:
Eliona uses a tag system similar to Haystack. Tags can be assigned to easily identify and organize data points, devices, and assets. These tags are versatile and can be used for many purposes:
Rules for alarms and escalations: Tags can be used to define rules for alarms and escalations.
Access rights: Tags determine which users have which rights to which assets. User roles can also be assigned tags to control access.
Custom classes (Asset Templates)
Eliona offers the ability to create custom classes (asset templates) and assign attributes to them. The templates can represent anything from rooms and buildings to specific types of sensors or abstract concepts. This allows users to create their own templates (classes) and define for themselves which attributes they have, and even create new attributes that are calculated from others.
Instances (Assets)
The created templates are turned into concrete instances (assets). For example:
Room 001
Heat Sensor 001
These instances can also be assigned tags, which can then be used for various purposes.
Assets can be nested geographically and/or functionally by dragging and dropping them into one another. For example:
Sensor Temp 001 can be nested in Room 001 can be nested in.
Room 001 can be nested in Building A can be nested in.
Advanced asset functions
Similar to Brick, assets in Eliona can have various points:
Reviews
Tracker
Attributes and asset characteristics (inherited from the asset template)
Data integration and drag-and-drop formats
Eliona enables the rapid creation of drag-and-drop formats that integrate incoming data into an asset. These formats can be used when connecting MQTT, Webhooks, RESTful, Kafka, UPD, UA, Modbus, and legacy systems to integrate data into asset attributes, such as a temperature reading.
App store and scalability
Eliona offers an app store in which apps can be created efficiently and which also supports other integrations into the platform. All data is stored in a PostgreSQL database, ensuring high scalability and efficiency. Eliona is a web application.
Interoperability and bulk import
Interoperability can be provided through an app as an interface. There is also the option of bulk import, where data can be imported in JSON format. API integration also enables the integration of data into the platform.
Eliona has a ticket system in which tags can be used and assets assigned.
Use of AKS
In an asset's geoinformation (GAI), AKS can be used to convey detailed information at a glance in a string.
Eliona and the use of ontologies
Brick
Components of Brick in Eliona:
Points: Eliona integrates the concept of
Points, from Brick to organize various data points and measured values. These points can represent sensor readings, device states, or other relevant information.
Asset attributes: The attributes of assets in Eliona are inspired by the detailed and specific attributes Brick defines for various building objects.
Benefits of using Brick:
Structured data organization: Brick's clear structure makes it easier to organize and manage building data.
Easy navigation and visualization: The nesting of assets enables intuitive navigation and visualization of the building structure and its components.
Extensibility: The use of points and attributes allows flexible expansion and adaptation to specific requirements.
Haystack
Components of Haystack in Eliona:
Tag system: Eliona adopts Haystack's tagging system, which makes it possible to assign tags and thus easily identify and organize data points, devices, and assets.
Flexibility in data collection: Eliona uses Haystack's flexibility to quickly and efficiently integrate and process incoming data.
Rule-based automation: By using tags, rules for alarms and escalations can be defined in Eliona, enabling an automated response to specific events.
Benefits of using Haystack:
Simplicity and flexibility: The tagging system makes it easier to identify and organize data without complex hierarchies.
Efficient data integration: Haystack's flexible structure enables quick integration and processing of data from various sources.
Automation: Rule-based automation improves the responsiveness and efficiency of building management.
Manage user rights: Tags can be used to control users' access rights to various assets.
RealEstateCore
Components of RealEstateCore in Eliona:
Classes and instances: Eliona uses the concept of classes and instances from RealEstateCore to create specific asset templates that can then be turned into concrete instances.
Users (Agents): Just as RealEstateCore uses the concept of agents to define different users and their roles, Eliona offers a flexible system for managing user roles and access rights.
Interoperability: Eliona uses the interoperability standards of RealEstateCore to facilitate communication and integration between different systems.
Benefits of using RealEstateCore:
Standardization: The standardized terminology ensures consistency and clarity in data management.
Interoperability: Using interoperability standards makes integration and communication between different systems and platforms easier.
Flexibility and adaptability: The ability to define custom classes and instances enables a high degree of adaptability to specific requirements and use cases.
User management: User and access-right management is supported by a flexible and efficient system based on the concept of agents in RealEstateCore.
Problem solving through Eliona
Eliona uses ontologies such as Brick, Haystack, and RealEstateCore to address specific challenges in the smart building context. At the same time, Eliona overcomes the weaknesses of ontologies by providing a flexible and user-friendly platform.
Knowledge management
Problem: Extensive and complex data sets in smart buildings are difficult to organize and search. Solution through Eliona:
Tag system: By using a flexible tag system that makes it possible to identify and organize data points, devices, and assets, Eliona improves the management and searchability of data.
Clear structuring: Eliona enables the creation of custom classes (asset templates) and their instances, resulting in clear and consistent data organization.
Geographical and structural nesting: The nesting of assets makes organization and searchability easier.
Data integration
Problem: Data in smart buildings comes from various sources and systems that are often incompatible with each other. Solution through Eliona:
Common language: Eliona uses standardized terms and structures that enable seamless integration of data from various sources.
Flexible formats: The rapid creation of drag-and-drop formats for integrating data via MQTT, Webhooks, RESTful, Kafka, UPD, UA, Modbus, and legacy systems simplifies data integration.
Interoperability
Problem: Different systems and devices in smart buildings often cannot communicate effectively with each other. Solution through Eliona:
Standardized relationships: By using ontology standards, Eliona promotes interoperability between different systems and devices.
Flexibility: The ability to define and nest custom classes and instances enables effective communication and collaboration between different systems.
Semantic web services
Problem: The integration and use of web services in smart buildings is often complicated and inflexible. Solution through Eliona:
Semantic annotation: Eliona enables the semantic annotation of web services, which makes it easier to search for, access, and integrate web services.
App store: Eliona's app store supports the creation and integration of apps that use various web services and other integrations.
Adaptability and flexibility
Problem: Systems in smart buildings must be able to adapt to changing requirements and technological advances. Solution through Eliona:
Extensibility: The ability to integrate new classes and relationships into the existing framework enables a high degree of adaptability.
Drag-and-drop functionality: The simple adaptation and expansion of data formats and integrations supports continuous innovation and customization.
Solutions to weaknesses of ontologies
Complexity
Weakness: Creating and maintaining ontologies is complex and requires extensive knowledge. Solution through Eliona:
User-friendliness: Eliona offers an intuitive user interface and drag-and-drop functions that simplify the creation and maintenance of data structures.
Automation: The platform automates many of the complex processes associated with ontology management.
Costs
Weakness: The development and implementation of ontologies involve high costs. Solution through Eliona:
Cost efficiency: Eliona reduces costs through user-friendly tools and templates that reduce the need for specialized experts and expensive software tools.
Scalability: Using a scalable PostgreSQL database ensures cost efficiency as data volumes grow.
Inflexibility
Weakness: Ontologies are often rigid and difficult to change. Solution through Eliona:
Flexibility: Eliona enables quick adjustments and expansions of classes and relationships, making changes easy to implement.
Dynamic adaptation: The platform supports continuous adaptation to new requirements and technological advances.
Acceptance
Weakness: Ontologies are often seen as too theoretical and impractical. Solution through Eliona:
Practical application: Eliona offers practical solutions through intuitive user interfaces and application-oriented functions.
Communicating the benefits: Clear presentation and ease of use promote acceptance of the platform.
Maintenance and updates
Weakness: The continuous maintenance and updating of ontologies is challenging. Solution through Eliona:
Easy maintenance: Eliona automates many maintenance processes and provides simple tools for updating data structures.
Regular updates: The platform supports regular updates and adjustments to changing requirements.
Compatibility and standardization
Weakness: Differences in terminology and structure between various ontologies and systems. Solution through Eliona:
Standardized terminology: Eliona uses standardized terms and structures to improve compatibility.
Interoperability standards: The platform promotes integration and communication between different systems through the use of interoperability standards.
Scalability
Weakness: Difficulties scaling to very large data volumes and complex systems. Solution through Eliona:
Scalable architecture: The use of a scalable PostgreSQL database enables the efficient management of large volumes of data.
Powerful query functions: Eliona offers powerful tools for querying and processing data, even in large and complex systems.
Conclusion
Eliona uses ontologies such as Brick, Haystack, and RealEstateCore to address specific challenges in the smart building context while overcoming their weaknesses. By combining flexible tag systems, the ability to create custom classes and instances, nesting of assets, advanced asset functions, efficient data integration, and automated processes, Eliona offers a scalable, user-friendly, and adaptable platform. This makes it easier to organize, integrate, and manage data in intelligent buildings and supports continuous innovation and adaptation.
Was this helpful?