11. Real-time, Time Series & IoT Capabilities
      Back to home
      1. Home
      2. 11. Real-time, Time Series & IoT Capabilities

      Working with Devices, Assets & Real-World Data Sources

      How to configure, manage, and integrate assets, devices, and other real-world data sources into your Rayven applications.

      Overview

      In Rayven, devices, assets, and other real-world data sources are represented as records in your application’s Primary Table. This allows you to store unique identifiers (UIDs) for each asset, alongside structured metadata (e.g., name, location, attributes) and unstructured time-series data captured via workflows.

      By combining table structures, data ingestion workflows, and real-time processing capabilities, you can connect almost any data source—whether it’s a physical IoT sensor, an industrial asset, or a software system—into your Rayven application.

      Representing Devices & Assets in Rayven

      • Primary Table UIDs
        Every device, asset, or data source is represented by a UID in the Primary Table. This UID acts as the anchor for all structured and unstructured data stored in the application.

      • Metadata & Attributes
        You can add columns to store descriptive information such as asset type, model number, latitude/longitude, or any custom fields relevant to your use case.

      • Label-Based Grouping
        Labels can be added to Primary Table columns to enable grouping, filtering, and user-specific data access.

      Connecting Real-World Data Sources

      Data Ingestion

      To connect your devices or assets to Rayven:

      1. Identify the Source Type – This could be an IoT protocol (e.g., MQTT, LoRaWAN), a cloud service (e.g., AWS S3, API), or another system (e.g., ERP via HTTP/FTP).

      2. Use Connector Nodes in a Workflow – Rayven supports a wide range of connectors for both push and pull data flows.

      3. Map Data to UIDs – Incoming payloads should include a device identifier that matches the UID in your Primary Table. This ensures data is stored and processed against the correct record.

      Example Connector Types:

      • MQTT for low-bandwidth IoT telemetry

      • LoRaWAN for long-range, low-power sensors

      • HTTP/API for application-to-application integration

      • SQL for direct database queries

      Processing & Using Device Data

      Once device or asset data is ingested into Rayven, it is automatically stored in the Cassandra time-series database and can be processed in real-time through workflows. This design enables Rayven to handle high-frequency, variable-structure payloads without losing historical context.

      How Device Data is Handled

      • UID-Centric Storage
        All incoming data is stored against the UID of the asset or device in the Primary Table, along with the node ID and timestamp. This ensures every record has a clear origin and history, even if payload structures change over time.

      • Automatic Time-Series Capture
        Rayven does not overwrite incoming values; each payload is stored as a unique timestamped record, creating a historical sequence of data points that can be queried, aggregated, and visualised.

      • Iterative Processing by UID
        Workflows can run once for all data, or iteratively for each UID (or a subset defined by labels). This allows the same logic to be applied individually to every asset in a fleet without duplicating workflow structures.

      Typical Processing Stages

      1. Transformation & Normalisation

        • Parse incoming payloads (e.g., split fields, convert units).

        • Apply formulas, rules, or conditional logic to derive calculated values.

        • Aggregate related readings into a single structure for easier analysis.

      2. Real-Time Analysis & Alerts

        • Apply thresholds to generate alarms (e.g., temperature exceeds safe limit).

        • Compare current readings with historical patterns to detect anomalies.

        • Trigger workflows that escalate events via email, SMS, or external systems.

      3. Control Actions

        • Use output nodes (e.g., MQTT, HTTP, Modbus, API) to send commands back to devices.

        • Enable both manual operator controls from the interface and automated responses based on data conditions.

      4. Interface & Visualisation Updates

        • Push processed data to frontend nodes for live display.

        • Widgets can be configured to refresh automatically, ensuring users always see the latest state of the asset.

        • Time-series charts, gauges, and calculated tables allow both live and historical review of performance.

      Why Rayven’s Time-Series Approach Matters

      • Complete Historical Record – You can analyse and compare data from any time period without having overwritten older values.

      • Flexible Payload Handling – Even if incoming data changes shape over time (e.g., firmware updates adding new fields), Rayven can store and process it without requiring schema changes in the Primary Table.

      • Scalable for High Volume – The Cassandra architecture ensures that even thousands of devices sending frequent updates can be processed in real-time without loss.

      Managing Device & Asset Records

      • Adding New Devices – Create a new row in the Primary Table, assigning a UID and any required metadata.

      • Updating Attributes – Use the Update Table node or edit records directly in the Tables section.

      • Removing Devices – Deleting a UID will orphan historical workflow data linked to it—proceed with caution.

      • Grouping – Organise devices by type, location, or operational unit using labels.

      Example: Real-Time Asset Monitoring

      1. Create a Primary Table with each asset as a UID.

      2. Configure an MQTT connector to receive telemetry data from each asset.

      3. Use workflow logic to process, store, and visualise incoming data.

      4. Set up alerts based on thresholds (e.g., temperature limits, downtime events).

      5. Display asset health and status in an analytics interface.

      Screenshots to Add

      • Primary Table with Device Records – Show UIDs, metadata columns, and labels.

      • Connector Node Example – Display MQTT or API node configuration.

      • Asset Health Dashboard – Example interface showing multiple asset widgets.

      Summary

      Working with devices and assets in Rayven involves defining each real-world source in the Primary Table, connecting it via appropriate ingestion workflows, and processing its data for storage, display, and automation. Whether your source is a sensor, industrial asset, or third-party application, Rayven’s flexible integration and real-time processing capabilities allow you to centralise, analyse, and act on your operational data.

      FAQs

      Do I need an IoT device to use this feature?
      No. Devices and assets can be physical or virtual. You can connect any real-world or software-based data source.

      Can I connect multiple data sources to the same asset?
      Yes. As long as the incoming data maps to the same UID in your Primary Table, it will be associated with that asset.

      What happens if I change a UID in the Primary Table?
      All historical workflow data linked to the old UID will be orphaned. To preserve data continuity, avoid changing UIDs.

      Can I control devices from Rayven?
      Yes. Using output nodes (e.g., Output to MQTT, Output to API), you can send commands or updates back to connected systems.

      Is location tracking supported?
      Yes. You can store fixed locations in Primary Table fields or receive dynamic coordinates in incoming payloads and display them using a Map widget.